Bug 368247 – crash in Home Folder: upgrading to edgy

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 368247 - crash in Home Folder: upgrading to edgy


Summary:	crash in Home Folder: upgrading to edgy


Status:	RESOLVED DUPLICATE of bug 349697

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-31 12:01 UTC by ionocatabi
Modified:	2006-10-31 13:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description ionocatabi 2006-10-31 12:01:39 UTC

What were you doing when the application crashed?
upgrading to edgy	


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 42729472 vsize: 0 resident: 42729472 share: 0 rss: 14585856 rss_rlim: 0
CPU usage: start_time: 1162301223 rtime: 0 utime: 41 stime: 0 cutime:36 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0

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 -1226742096 (LWP 7661)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 80930

Thread 1 (Thread -1226742096 (LWP 7661))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gtk_menu_shell_insert
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_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#10 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_ui_manager_get_ui
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#13 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#14 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#15 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#16 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#17 POA_Nautilus_MetafileFactory__fini
#18 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#19 ??
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-31 13:54:42 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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