Bug 360700 – crash in Home Folder: aptitude dist-upgrade (f...

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 360700 - crash in Home Folder: aptitude dist-upgrade (f...


Summary:	crash in Home Folder: aptitude dist-upgrade (f...


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:

Duplicates:	360701 360702 360703 (view as bug list)
Depends on:
Blocks:

Reported:	2006-10-08 17:51 UTC by davidpoca
Modified:	2006-10-08 17:56 UTC

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

Description davidpoca 2006-10-08 17:51:29 UTC

What were you doing when the application crashed?
aptitude dist-upgrade (from dapper to edgy)


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

Memory status: size: 74981376 vsize: 0 resident: 74981376 share: 0 rss: 14217216 rss_rlim: 0
CPU usage: start_time: 1160329815 rtime: 0 utime: 39 stime: 0 cutime:36 cstime: 0 timeout: 3 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 -1226496336 (LWP 5000)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75278

Thread 1 (Thread -1226496336 (LWP 5000))

#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 Elijah Newren 2006-10-08 17:55:07 UTC

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

Comment 2 Elijah Newren 2006-10-08 17:55:13 UTC

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

Comment 3 Elijah Newren 2006-10-08 17:55:15 UTC

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

Comment 4 Elijah Newren 2006-10-08 17:56:17 UTC

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 ***