GNOME Bugzilla – Bug 349551
crash in nautilus_ui_unmerge_ui / real_update_menus
Last modified: 2007-10-19 22:10:06 UTC
What were you doing when the app crashed?: I simply tried to lgon for the first time after a fresh install of Fedora Core development. Distribution: Fedora Core release 5.91 (FC6 Test2) Gnome Release: 2.15.4 2006-07-12 (Red Hat, Inc) BugBuddy Version: 2.15.0 Memmory status: size: 87478272 vsize: 0 resident: 87478272 share: 0 rss: 14671872 rss_rlim: 0 CPU usage: start_time: 1154447814 rtime: 0 utime: 33 stime: 0 cutime:19 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0 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 -1208682800 (LWP 2684)] (no debugging symbols found) 0xb7f73402 in __kernel_vsyscall ()
+ Trace 69869
Thread 1 (Thread -1208682800 (LWP 2684))
I have a very similar bug. Distribution: gentoo gnome-base/nautilus (2.15.91) gnome-extra/nautilus-cd-burner (2.15.6) The trace I got with bug-buddy, also incomplete comparing to the one provided, is very similar. I didn't compile the whole stack with debugging symbols. The crash happens when I click on about any icons on the desktop (computer, home, some folders). Nautilus crashes and bug-buddy opens saying that nautilus-cd-burner has crashed.
Forgot to mention that there is no crash if I use the places menu or when I click on already opened windows.
*** Bug 351345 has been marked as a duplicate of this bug. ***
*** Bug 352167 has been marked as a duplicate of this bug. ***
*** Bug 352678 has been marked as a duplicate of this bug. ***
*** Bug 354187 has been marked as a duplicate of this bug. ***
*** Bug 349795 has been marked as a duplicate of this bug. ***
*** Bug 352938 has been marked as a duplicate of this bug. ***
Confirming as per duplicates. Can somebody please help the developers to fix this bug by trying to reproduce this crash with debugging packages of at least nautilus installed? See http://live.gnome.org/GettingTraces/DistroSpecificInstructions for more information. Thanks a lot in advance!
*** Bug 365277 has been marked as a duplicate of this bug. ***
*** Bug 374757 has been marked as a duplicate of this bug. ***
with nautilus & nautilus-cd-burner debuginfo installed i get the following trace. Distribution: Fedora Core release 6 (Rawhide) Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc) BugBuddy Version: 2.16.0 Memory status: size: 79310848 vsize: 0 resident: 79310848 share: 0 rss: 27746304 rss_rlim: 0 CPU usage: start_time: 1164543365 rtime: 0 utime: 339 stime: 0 cutime:307 cstime: 0 timeout: 32 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208128768 (LWP 12372)] 0x00a2e402 in __kernel_vsyscall ()
+ Trace 89476
Thread 1 (Thread -1208128768 (LWP 12372))
hope this helps
*** Bug 384444 has been marked as a duplicate of this bug. ***
*** Bug 384532 has been marked as a duplicate of this bug. ***
*** Bug 390933 has been marked as a duplicate of this bug. ***
*** Bug 394790 has been marked as a duplicate of this bug. ***
*** Bug 397334 has been marked as a duplicate of this bug. ***
*** Bug 399269 has been marked as a duplicate of this bug. ***
Lars G, can you still reproduce that crash? If so, can you please also install glib2-debuginfo and gtk2-debuginfo? Thanks in advance (and sorry for the late answer).
Hi, I think this bug happened to me when i killed a remote server (Closed the vmplayer) which i was connected to using samba. I have no cdrom so it s not linked to a cd writer. Hope it helps.
copying from bug 416386:
+ Trace 117683
*** Bug 416386 has been marked as a duplicate of this bug. ***
*** Bug 416710 has been marked as a duplicate of this bug. ***
from bug 417416:
+ Trace 118361
*** Bug 417416 has been marked as a duplicate of this bug. ***
*** Bug 416195 has been marked as a duplicate of this bug. ***
*** Bug 390534 has been marked as a duplicate of this bug. ***
*** Bug 408293 has been marked as a duplicate of this bug. ***
please also see http://bugzilla.gnome.org/show_bug.cgi?id=408293#c9 to track this down!
From bug 390534: ** (nautilus:20100): CRITICAL **: nautilus_window_info_get_window_type: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:20100): CRITICAL **: nautilus_window_info_get_ui_manager: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed Likely what happens is that view->details->window is NULL, which happens in fm_directory_view_destroy. However, all menu updates are cancelled in destroy, maybe we somehow schedule a menu update after the view is destroyed?
I believe this is fixed with: 2007-03-14 Alexander Larsson <alexl@redhat.com> * src/file-manager/fm-directory-view.c (schedule_update_menus) (schedule_update_status): Make sure we never schedule an update after the window has been destroyed. Likely fixes #349551 Reopen if you see with any version > 2.18.0.1
thanks! trackback: http://svn.gnome.org/viewcvs/nautilus/trunk/src/file-manager/fm-directory-view.c?r1=12802&r2=12801
*** Bug 418651 has been marked as a duplicate of this bug. ***
*** Bug 419870 has been marked as a duplicate of this bug. ***
*** Bug 419517 has been marked as a duplicate of this bug. ***
*** Bug 422731 has been marked as a duplicate of this bug. ***
*** Bug 423800 has been marked as a duplicate of this bug. ***
*** Bug 424826 has been marked as a duplicate of this bug. ***
*** Bug 424825 has been marked as a duplicate of this bug. ***
*** Bug 426149 has been marked as a duplicate of this bug. ***
*** Bug 427504 has been marked as a duplicate of this bug. ***
*** Bug 428765 has been marked as a duplicate of this bug. ***
*** Bug 430568 has been marked as a duplicate of this bug. ***
*** Bug 436147 has been marked as a duplicate of this bug. ***
*** Bug 437749 has been marked as a duplicate of this bug. ***
*** Bug 438273 has been marked as a duplicate of this bug. ***
*** Bug 443470 has been marked as a duplicate of this bug. ***
*** Bug 443733 has been marked as a duplicate of this bug. ***
*** Bug 431253 has been marked as a duplicate of this bug. ***
*** Bug 452397 has been marked as a duplicate of this bug. ***
*** Bug 454535 has been marked as a duplicate of this bug. ***
*** Bug 457059 has been marked as a duplicate of this bug. ***
*** Bug 458207 has been marked as a duplicate of this bug. ***
*** Bug 458217 has been marked as a duplicate of this bug. ***
*** Bug 466513 has been marked as a duplicate of this bug. ***
*** Bug 468402 has been marked as a duplicate of this bug. ***
*** Bug 467874 has been marked as a duplicate of this bug. ***
*** Bug 465851 has been marked as a duplicate of this bug. ***
*** Bug 463563 has been marked as a duplicate of this bug. ***
*** Bug 469207 has been marked as a duplicate of this bug. ***
*** Bug 480479 has been marked as a duplicate of this bug. ***
*** Bug 464465 has been marked as a duplicate of this bug. ***