After emergeing latest gnome, nautilus 2.0.8 refuses to start. It crashes without showing up. (Segfault, fatal error pop up window) I tried running Nautilus from gdb and found this (no debugging symbols found)...(no debugging symbols found)... (nautilus:4486): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 4486)] 0x40b756f3 in strlen () from /lib/libc.so.6 Wondering if I messed up somethng. But I dont remeber doing anything nasty. Plz look into this, Thank you.
only nautilus shows this problem ? are you running it as the same user as you are running gnome ? do you have a hostname set ?
This happens with only with nautilus. The KDE console crashes too. DCOPServer up and running. (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 6723)] 0x40a6ef77 in QObject::inherits(char const*) const () from /usr/qt/3/lib/libqt-mt.so.3 I havent upgraded it to 3.0.5a yet, so may be thats the problem, BTW, i have also setup the hostname with proper mapping
hmm if random apps start crashing you might want to check your hardware and tune down on optimisations for a start.
any news here ?
With the new KDE compile, I was able toget rid of konsole segfault. No random applications are not crashing. Somehow only nautilus fails to start with segfault. Let me give you my compilation options too. I guess I am using sane flags. CXXFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer" CFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer" Should that cuase any problem? I tried rebuilding all the dependencies needed by nautilus (by looking at ebuild). But no luck :(
first cut down on optimizations (none for a start), then debugbuild it (add 'inherit debug' to the top of the ebuild) and get me a gdb backtrace .
Ok here is the backtrace: (gdb) bt #0 0x40b866f3 in strlen () from /lib/libc.so.6 #1 0x409b819a in g_strdup () from /usr/lib/libglib-2.0.so.0 #2 0x400c439d in get_removable_volumes (monitor=0x80feac0) at nautilus-volume-monitor.c:577 #3 0x400c3d8b in nautilus_volume_monitor_init (monitor=0x80feac0) at nautilus-volume-monitor.c:294
is that all of the backtrace ? you got any weird mountable devices around or something ? Try cleaning all but the neccessary mounts from /etc/fstab and see if it still segfaults ? You don't have to reboot your machine for that i think.
Ok :), I guess you can close this bug now. There was problem with weird mount. If you are intrested here is the problem...I used supermount patch and had changed fstab for cdrom mount #/dev/cdroms/cdrom0 /mnt/cdrom supermount \ fs=iso9660,noauto,ro,user,unhide 0 0 So I guess supemount and nautilus doesnt go well with each other :( Thank foser :)
i looked upstream and there are already a few bugs open on several types of mountables, so i hope it gets fixed sometime in the future.
