Re: both X11 and XQuartz encounter similar error
Re: both X11 and XQuartz encounter similar error
- Subject: Re: both X11 and XQuartz encounter similar error
- From: David Borman <email@hidden>
- Date: Sat, 11 Sep 2010 17:45:18 -0500
On Sep 11, 2010, at 12:21 PM, Jeremy Huddleston wrote:
>
> On Sep 11, 2010, at 10:03, Michael Lachman wrote:
>
>> Jeremy,
>>
>>>> dd if=/dev/urandom bs=16 count=1 2> /dev/null | hexdump -e \"x\"
>>
>> running this by itself in Terminal simply returns another prompt with no other discernible effect. Is it writing to a file and if so where is it located? Am I missing the point entirely? (likely) :-)
>
> Yes, you should get a random hexadecimal string printed:
>
> ~ $ dd if=/dev/urandom bs=16 count=1 2> /dev/null | hexdump -e \"x\"
> a4d5e10eb3136b8228daf59e0e4955e2
So Michael, run the command again without "2> /dev/null", and then you can see if the dd command is generating an error, and hence no output. Here's what I get:
sh-3.2$ dd if=/dev/urandom bs=16 count=1 | hexdump -e \"x\"
1+0 records in
1+0 records out
16 bytes transferred in 0.000026 secs (615678 bytes/sec)
dde0dcdc90175b081a3a898619d94897sh-3.2$
Make sure /dev/urandom exists and has correct permissions and major/minor number:
sh-3.2$ ls -l /dev/urandom
crw-rw-rw- 1 root wheel 9, 1 Sep 7 16:03 /dev/urandom
You can also try the command with absolute paths:
/bin/dd if=/dev/urandom bs=16 count=1 | /usr/bin/hexdump -e \"x\"
to make sure you get the right executables. If that produces different results, then use "which dd hexdump" to find out where in your $PATH it is selecting the executables from:
sh-3.2$ which dd hexdump
/bin/dd
/usr/bin/hexdump
sh-3.2$
-David Borman
>
>
>> Ken,
>>
>> echo $PATH in Terminal returns:
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/bin:/Library/Frameworks/Python.framework/Versions/Current/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/X11/bin
>>
>> which looks normal to me, but from what you said, it would.
>>
>> Launching XQuartz 2.5.3 from the shell rather than the dock does not produce the loop. However, launching Inkscape.app (an SVG-based Illustrator substitute) from the dock afterwards does. Could this be a third-party culprit?
>
> Probably. If you can launch X11 from Terminal.app but not the dock, the only effective difference is the environment.
>
>
>> Launching X11.app 2.3.5 from the shell produces the loop immediately.
>
> Was this *after* trying to start Inkscape? If so, that is consistent.
>
>
>> You're all welcome to keep working on figuring this one out, but I may just opt for completely clean reinstall of 10.6 at this point and see if that makes the problems disappear - I'm also dealing with a separate system bug that has disabled cd reading on my optical drive.
>
>
> It would be quicker and cleaner to do:
>
> mv ~/.MacOSX/environment.plist ~/.MacOSX/environment.plist.bak
> mv ~/.profile ~/.profile.bak
> mv ~/.bash_profile ~/.bash_profile.bak
> mv ~/.bashrc ~/.bashrc.bak
>
> Then logout and log back in.
>
> If that fixes it, you should look at each of those files to see which was the culprit.
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list (email@hidden)
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden