GNOME Bugzilla – Bug 494487
crash in File Browser: rigth click - properties
Last modified: 2009-05-15 00:14:40 UTC
Version: 2.18.3 What were you doing when the application crashed? rigth click - properties Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 74145792 vsize: 74145792 resident: 24879104 share: 15396864 rss: 24879104 rss_rlim: 4294967295 CPU usage: start_time: 1194428673 rtime: 668 utime: 608 stime: 60 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e2e6b0 (LWP 3649)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 175966
Thread 1 (Thread 0xb6e2e6b0 (LWP 3649))
----------- .xsession-errors --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 /usr/lib/python2.4/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) current dist not found in meta-release file (nautilus:3649): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 76156928 vsize: 76156928 resident: 26087424 share: 15642624 rss: 26087424 rss_rlim: 4294967295 CPU usage: start_time: 1194601994 rtime: 588 utime: 545 stime: 43 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6d606b0 (LWP 3820)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 176523
Thread 1 (Thread 0xb6d606b0 (LWP 3820))
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 (epiphany:5507): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed ** Message: drive = 0 ** Message: volume = 0 (nautilus:3820): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed --------------------------------------------------
*** Bug 506234 has been marked as a duplicate of this bug. ***
Reopening, as a decent stacktrace was given.
*** Bug 506363 has been marked as a duplicate of this bug. ***
*** Bug 506325 has been marked as a duplicate of this bug. ***
*** Bug 506536 has been marked as a duplicate of this bug. ***
*** Bug 515931 has been marked as a duplicate of this bug. ***
*** Bug 513987 has been marked as a duplicate of this bug. ***
No duplicates from 2.22 so far - anybody still seeing this running 2.22?
*** Bug 550884 has been marked as a duplicate of this bug. ***
*** Bug 556220 has been marked as a duplicate of this bug. ***
*** Bug 560045 has been marked as a duplicate of this bug. ***
*** Bug 564219 has been marked as a duplicate of this bug. ***
*** Bug 564478 has been marked as a duplicate of this bug. ***
*** Bug 566534 has been marked as a duplicate of this bug. ***
This should be obsolete, noting the stacktrace from Bug 566534
+ Trace 211298
The crash is occurring due to owner_text being 0x0, which was checked for in revision 13928 (see patch http://svn.gnome.org/viewvc/nautilus/trunk/src/file-manager/fm-properties-window.c?r1=13927&r2=13928) which is present in Nautilus >= 2.22.1. If we see crashes from those revisions, then it's something else, otherwise I'd say mark this as obsolete.
*** Bug 570388 has been marked as a duplicate of this bug. ***
Tom: Feel free to close as OBSOLETE, and thanks for investigating.
(In reply to comment #19) > Tom: Feel free to close as OBSOLETE, and thanks for investigating. Ok, doing.
*** Bug 582663 has been marked as a duplicate of this bug. ***