GNOME Bugzilla – Bug 593748
crash in Open Folder: s
Last modified: 2009-09-02 09:47:20 UTC
Version: 2.26.3 What were you doing when the application crashed? s Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.30.3-6224w2 #2 SMP Tue Aug 25 18:52:46 CEST 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: SlicknesS Icon Theme: black-white_2-Gloss GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 317698048 vsize: 317698048 resident: 19439616 share: 13873152 rss: 19439616 rss_rlim: 18446744073709551615 CPU usage: start_time: 1251785489 rtime: 162 utime: 140 stime: 22 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] 0x00007f4df674f28f in __libc_waitpid (pid=5682, stat_loc=0x7fffdc54d4b0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 217263
Thread 1 (Thread 0x7f4dfaeb1800 (LWP 4229))
The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- Shutting down nautilus-open-terminal extension --- Hash table keys for warning below: --> file:///home/tredsoul/Desktop --> x-nautilus-desktop:/// (nautilus:4229): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 2 elements at quit time (keys above) (nautilus:4229): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 3 elements at quit time PID TTY STAT TIME COMMAND 4184 ? S 0:00 keytouchd PID TTY STAT TIME COMMAND 4184 ? R 0:00 keytouchd /usr/bin/keytouchd-launch: line 34: kill: (4184) - Processen finns inte PID TTY STAT TIME COMMAND --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the develope *** This bug has been marked as a duplicate of bug 584745 ***
I just sent away the report becuase the last time I tried to write something X got killed while I was typing (another type of "bug" perhaps? Should the X-killing be halted until one cancels or sends the report?). Anyway, it's the same as everytime , only happens at every shutdown/reboot (not suspend though). At least gnome has stopped to die spontaneously during sessions since a couple of updates ago. As soon as I choose shutdown/reboot, gnome crashes, exit to console, nothing happens, then after a while (I guess gdm TRIES TO) an X-init (but only the pure X screen, nothing more, and the mouse pointer shows loading going on, without anything ever happening, this is not a slow computer, laptop with T7250/2G 800Mhz DDR2). Other times I have to kill X myself after the crash, but same result, even if I logon in console and run reboot or shutdown -h/r now, if gives the immediate reboot/etc response with nothing ever happening, think I've even had X starting after the command. What I see often the while idling in the console idling is those damn annoying CIFS VFS messages I used a lot of updates ago. I've also tried prior to shutdown/reboots from gnome to close down everything, disconnect and umount -a. I guess next step would be to disable everything CIFS but that has to wait until I have time.
hmm, lots of typos but I hope it helps anyway.