GNOME Bugzilla – Bug 525952
crash in Home Folder:
Last modified: 2008-04-04 10:21:24 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Mon Feb 11 13:47:43 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: Noia Memory status: size: 469172224 vsize: 469172224 resident: 27234304 share: 17870848 rss: 27234304 rss_rlim: 18446744073709551615 CPU usage: start_time: 1207227534 rtime: 260 utime: 225 stime: 35 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b175fa15b80 (LWP 4011)] (no debugging symbols found) 0x00002b175952334f in waitpid () from /lib/libpthread.so.0
+ Trace 194115
Thread 1 (Thread 0x2b175fa15b80 (LWP 4011))
----------- .xsession-errors (9 sec old) --------------------- (npviewer.bin:4574): Gtk-WARNING **: Loading IM context type 'cedilla' failed Playing WAVE '/usr/share/amsn/skins/default/sounds/online.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo Aviso do gerenciador de janelas: last_user_time (2069418656) is greater than comparison timestamp (342466082). This most likely represents a buggy client sending inaccurate timestamps in messages suc Aviso do gerenciador de janelas: 0x3400081 (Synaptic) appears to be one of the offending windows with a timestamp of 2069418656. Working around... (synaptic:4804): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (synaptic:4804): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (synaptic:4804): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
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 developers? *** This bug has been marked as a duplicate of 525181 ***