GNOME Bugzilla – Bug 158308
Nautilus browser window fails to close correctly
Last modified: 2005-10-03 11:16:40 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: nautilus Severity: normal Version: GNOME2.8.0 2.8.x Gnome-Distributor: Red Hat, Inc Synopsis: Nautilus browser window fails to close correctly Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.8.x BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: The nautilus browser window crashes when the X in the corner is clicked, or when 'Close' is selected from the file menu. This yields an error message saying "The Application 'nautilus' has quit unexpectedly." Clicking 'Close' causes nautilus to restart, without exception. Steps to reproduce the crash: 1. Open a file browser window by double-clicking on the home directory icon the desktop or selecting "Browse Filesystem" from the GNOME menu. 2. Try to close the window. 3. Expected Results: Window should close without giving an error message and restarting nautilus. How often does this happen? Every time I try to close a browser window. Additional Information: This does not happen under the spatial view. If there are two or more browser windows open, all windows will close, yielding the same error message; however, nautilus will not always restart. This occurs under nautilus 2.8.1, on a system running Fedora Core 3. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151161152 (LWP 6519)] [New Thread -165155920 (LWP 6524)] [Thread debugging using libthread_db enabled] [New Thread -151161152 (LWP 6519)] [New Thread -165155920 (LWP 6524)] [Thread debugging using libthread_db enabled] [New Thread -151161152 (LWP 6519)] [New Thread -165155920 (LWP 6524)] [New Thread -164889680 (LWP 6523)] [New Thread -164623440 (LWP 6522)] [New Thread -164357200 (LWP 6521)] [New Thread -153855056 (LWP 6520)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x005677a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52001
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-14 17:23 ------- 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 david.puglielli@gmail.com. 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. Moving to the accessibility component based on the atk_ functions in the stack trace. David: Is there any chance you could install the atk, glib2, gtk2, gnome-vfs2, and nautilus debuginfo rpms from http://download.fedora.redhat.com/pub/fedora/linux/core/3/i386/debug/, get the crash to occur again, and then cut and paste the stack trace that bug-buddy gets into this bug report?
Additional debugging info: Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -151161152 (LWP 3142)] [New Thread -165155920 (LWP 3165)] [Thread debugging using libthread_db enabled] [New Thread -151161152 (LWP 3142)] [New Thread -165155920 (LWP 3165)] [Thread debugging using libthread_db enabled] [New Thread -151161152 (LWP 3142)] [New Thread -165155920 (LWP 3165)] [New Thread -164889680 (LWP 3164)] [New Thread -164623440 (LWP 3163)] [New Thread -164357200 (LWP 3162)] [New Thread -153855056 (LWP 3156)] 0x005677a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52003
Thread 6 (Thread -153855056 (LWP 3156))
Looks like the stack trace in bug 159745 and bug 159762--atk bug?
Is accessibility key /desktop/gnome/interface/accessibility set to true?
No, the accessibility key is not set to true.
The reason why code in atk is being called without accessibility being enabled is that nautilus_location_bar_init() calls eel_accessibility_set_up_label_widget() which creates the AtkRelations. I do not know why the crash is occuriing. I am not able to reproduce it.
Reassigning to eel. The relation set of both objects is unrefed, although it wasn't refed before. eel_accessibility_set_up_label_widget_relation should rather use the atk relation setup helper instead of messing around with the internals on its own.
Created attachment 52877 [details] [review] Proposed patch This patch makes eel use the ATK+ wrapper around these internals. I've also submitted it to the nautilus mailing list for review: http://mail.gnome.org/archives/nautilus-list/2005-September/msg00220.html
Hrm eel doesn't have target milestones :/.
atk_object_ref_relation_set() ref:s the return value, so the unref is right. So, while this patch is nice (and i commited it), its unlikely to have fixed the problem.
Alex: Something IMHO must have invalidated the ATK relation reference, although I totally fail to see where it happened. However, since Nautilus 2.8 is really pretty old now, and we don't have any new bug report on the issue, I'm marking this as OBSOLETE.