GNOME Bugzilla – Bug 555071
crash in Home Folder: I think I closed the Fol...
Last modified: 2008-10-08 16:03:39 UTC
What were you doing when the application crashed? I think I closed the Folder, but I`m not sure. Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Thu May 8 01:29:10 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Nuvola Icon Theme: Nuvola Memory status: size: 104595456 vsize: 104595456 resident: 34418688 share: 14520320 rss: 34418688 rss_rlim: 4294967295 CPU usage: start_time: 1223143618 rtime: 6944 utime: 6602 stime: 342 cutime:1 cstime: 5 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6bf5720 (LWP 2857)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 207779
Thread 1 (Thread 0xb6bf5720 (LWP 2857))
----------- .xsession-errors --------------------- ** (evolution:5027): CRITICAL **: source_changed_cb: assertion `source != NULL' failed DEBUG: Uploads (mbox:/home/jann/.evolution/mail/local#Uploads) (evolution:5027): gtkhtml-WARNING **: oo (synaptic:15997): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (gnome-terminal:16076): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. ** Message: <info> Sie sind nun mit dem Kabelnetzwerk verbunden. ** ** ERROR:(fm-tree-model.c:1527):fm_tree_model_unref_node: assertion failed: (parent->dummy_child_ref_count > 0) warning: .dynamic section for "/lib/libpopt.so.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 356672 ***