Re: [Fink-beginners] Nautilus wont start

[Alexander K. H. <ak...@co...>]

On Jul 14, 2005, at 4:40 AM, Gregory Dodwell wrote:

> Got bounced ... for a 1.8Kb payload!
>
> Here's the message again with a link to the zipped file in my  
> personal web-space:
>
> Thanks:
>
> here's the dialogue when I try to launch Nautilus from the Apple  
> X11 Applications menu:
> being mindful that the xterm for X11 for me is no good for Fink  
> usage (I use the OSX Terminal).
>
> XFree86 Version 4.4.0 / X Window System
> (protocol Version 11, revision 0, vendor release 6600)
> _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
> [DRI] screen 0 installation complete
> Screen 0 added: 1440x900 @ (0,0)
> Could not init font path element /usr/X11R6/lib/X11/fonts/CID/,  
> removing from list!
> bash: no job control in this shell
> Jul 14 00:32:47 greg01 crashdump[4993]: gnome-vfs-daemon crashed
> Jul 14 00:32:48 greg01 crashdump[4993]: crash report written to: / 
> Users/greg/Library/Logs/CrashReporter/gnome-vfs-daemon.crash.log
>
>
> link: http://www.users.on.net/~gregreedee/gnome-vfs- 
> daemon.crash.log.zip
>
> Thanks in advance for your time.
>
> Greg./
>
>
>

I think my server bounces _all_ zip files as a matter of course  
(because of windows viruses).

I can't say that the error looked obvious to me, unfortunately.  I'll  
go ahead and post this to the list as well, in case others have more  
insight into this than I.

My best suggestion at this point is to figure out what packages (not  
just files) are involved in the crash by running dpkg -S <filename>:

$ dpkg -S /sw/lib/libglib-2.0.0.dylib
glib2-shlibs: /sw/lib/libglib-2.0.0.dylib

and see if rebuilding those packages helps.  I wish I had something  
more substantive than that.

I can, however get xterm working for Fink--change the Application  
menu command to use "xterm -ls" rather than just "xterm".

--AH

>
> On 14/07/2005, at 12:03 AM, Alexander K. Hansen wrote:
>
>>
>> On Jul 13, 2005, at 9:59 AM, Gregory Dodwell wrote:
>>
>>> Alex,
>>>
>>> I usually don't write directly to a responder. I tried posting my  
>>> console.log file, which is too large an attachment for the list.  
>>> If it's OK, could I mail it directly to this address?
>>>
>>> Greg./
>>>
>>
>> OK--though I've got a limit to attachment size, too.
>>
>