GNOME Bugzilla – Bug 169980
nautilus continue crash
Last modified: 2005-09-11 20:53:16 UTC
Distribution: SuSE Linux 9.2 (i586) Package: nautilus Severity: normal Version: GNOME2.10.0 2.10.0 Gnome-Distributor: GARNOME Synopsis: nautilus continue crash Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.10.0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Nautilus crashes continue, it only starts with: nautilus --no-desktop --browser %U (from the panel) Steps to reproduce the crash: 1. just start gnome 2. or start nautilus 3. How often does this happen? always Additional Information: Gnome 2.10, build with garnome, on suse 9.2 Debugging Information: Backtrace was generated from '/home/fvos/garnome/bin/nautilus' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1090610752 (LWP 13739)] [New Thread 1097935792 (LWP 13741)] [Thread debugging using libthread_db enabled] [New Thread 1090610752 (LWP 13739)] [New Thread 1097935792 (LWP 13741)] [New Thread 1095580592 (LWP 13740)] [Thread debugging using libthread_db enabled] [New Thread 1090610752 (LWP 13739)] [New Thread 1097935792 (LWP 13741)] 0xffffe410 in ?? ()
+ Trace 56719
Thread 1 (Thread 1090610752 (LWP 13739))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-11 11:46 ------- Unknown version 2.10.0 in product nautilus. Setting version to "2.10.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was frederik.vos@l4l.be. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. This appears to be a unique stack trace, according to the simple-dup-finder.
Created attachment 38575 [details] stack trace I'm seeing this crash as well. Nautilus was started on a new user account. Thus, there was no previous GNOME settings or GNOME files in the home directory. Nautilus was built with GARNOME 2.10.0 on Fedora Core 3. Attached is my stack trace
I'm also having this problem with 2.10. I dropped back to 2.9.91 and the problem goes away, so I think this bug might have been introduced very recently. Crashes for all users, even with purged gconf files.
Created attachment 38580 [details] BUG source: GARNOME patch After racking my brain trying to find the problematic code, I realized GARNOME 2.10 is applying a patch to the 2.10 code. After compiling the raw 2.10 code (without the GARNOME patch), this bug disappears. Does anyone know where this patch is from? I can't find any notice of it in the mailing lists.
This looks like an attempt to reduce the memory usage wrt to the background image. Bug 169347 is related. Reassigning to Garnome.
Latest patch in bug 169347 should fix the problem. Please, test it. If not, it would be nice to see more detailed backtrace, since I can't really reproduce it. g_object_unref on NULL pointer for produces only warning, not crash. Probably, you have some glib optimizations in GARNOME?
I manually patched the 2.10 source with the patch in bug 169347 instead of the GARNOME patch, and the problem is FIXED. It appears to be a NULL pointer causing the problem. I'm compiling glib with GARNOME, so I'm not compiling glib with any special optimizations...any other clues to why this would cause a segfault only on our machines?
*** Bug 170647 has been marked as a duplicate of this bug. ***
Fixed in GARNOME 2.10.0.1.
*** Bug 315789 has been marked as a duplicate of this bug. ***