Bug 368945 – Nautilus Crashes during login

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 368945 - Nautilus Crashes during login


Summary:	Nautilus Crashes during login


Status:	RESOLVED DUPLICATE of bug 349697

Product:	nautilus
Classification:	Core
Component:	Desktop
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-01 17:01 UTC by pcampbell
Modified:	2006-11-01 17:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description pcampbell 2006-11-01 17:00:23 UTC

Distribution: Ubuntu 6.10 (edgy)
Package: nautilus
Severity: Normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Nautilus Crashes during login
Bugzilla-Product: nautilus
Bugzilla-Component: Desktop
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. Change Ubuntu apt/sources from dapper to edgy
2. apt-get upgrade
3. Restart gdm
4. Login

Expected Results:
Desktop icons appear.

How often does this happen?
So far, once.

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225352832 (LWP 10024)]
[New Thread -1227244624 (LWP 10025)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 81503

Thread 1 (Thread -1225352832 (LWP 10024))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#5 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#6 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#7 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#8 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_ui_manager_ensure_update
from /usr/lib/libgtk-x11-2.0.so.0
#10 g_child_watch_add
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#14 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#15 POA_Nautilus_MetafileFactory__fini
#16 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#17 ??
#0 __kernel_vsyscall





------- Bug created by bug-buddy at 2006-11-01 17:01 -------

Comment 1 Behdad Esfahbod 2006-11-01 17:31:24 UTC

Thanks for taking the time to report this bug.
Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 349697 ***