Bug 368849 – after upgrading uduntu

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 368849 - after upgrading uduntu


Summary:	after upgrading uduntu


Status:	RESOLVED DUPLICATE of bug 349697

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

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

URL:
Whiteboard:

Duplicates:	409986 (view as bug list)
Depends on:
Blocks:

Reported:	2006-11-01 13:27 UTC by romasg
Modified:	2010-07-06 21:13 UTC

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

Description romasg 2006-11-01 13:26:15 UTC

Distribution: Ubuntu 6.10 (edgy)
Package: nautilus
Severity: Normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Ubuntu
Synopsis: after upgrading uduntu
Bugzilla-Product: nautilus
Bugzilla-Component: Accessibility
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


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 -1225345344 (LWP 6809)]
[New Thread -1226732624 (LWP 6810)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 81418

Thread 1 (Thread -1225345344 (LWP 6809))

#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 13:27 -------

Comment 1 Behdad Esfahbod 2006-11-01 13:37:07 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 ***

Comment 2 palfrey 2007-02-20 17:20:42 UTC

*** Bug 409986 has been marked as a duplicate of this bug. ***

Comment 3 Allan Day 2010-07-06 21:12:50 UTC

Changing component as a part of ongoing reorganisation work.

Comment 4 Allan Day 2010-07-06 21:13:22 UTC

Changing component as a part of ongoing reorganisation work.