Bug 382759 – crash in CD/DVD Creator: Closing down Instant Mes...

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 382759 - crash in CD/DVD Creator: Closing down Instant Mes...


Summary:	crash in CD/DVD Creator: Closing down Instant Mes...


Status:	RESOLVED DUPLICATE of bug 374002

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-12-05 21:03 UTC by G. Michael Carter
Modified:	2006-12-05 22:16 UTC

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

Description G. Michael Carter 2006-12-05 21:03:55 UTC

What were you doing when the application crashed?
Closing down Instant Messaging.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors (50246 sec old) ---------------------
(evolution:16815): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `start <= end' failed
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000021 has recurrences
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000083 has recurrences
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000102 has recurrences
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000105 has recurrences
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000113 has recurrences
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000242 has recurrences
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000219 has recurrences
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000106 has recurrences
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000249 has recurrences
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000303 has recurrences
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000270 has recurrences
WEBCALENDAR-CARTERFAMILY-CA-MCARTER-0000000405 has recurrences
...Too much output, ignoring rest...
--------------------------------------------------

Memory status: size: 143704064 vsize: 0 resident: 143704064 share: 0 rss: 28233728 rss_rlim: 0
CPU usage: start_time: 1165336429 rtime: 0 utime: 3700 stime: 0 cutime:3478 cstime: 0 timeout: 222 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 -1209025792 (LWP 18702)]
(no debugging symbols found)
0x00651402 in __kernel_vsyscall ()

+ Trace 91869

Thread 1 (Thread -1209025792 (LWP 18702))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gtk_ui_manager_remove_ui
from /usr/lib/libgtk-x11-2.0.so.0
#5 nautilus_marshal_BOOLEAN__POINTER
#6 fm_directory_view_bump_zoom_level
#7 fm_directory_view_bump_zoom_level
#8 fm_directory_view_update_menus
#9 fm_directory_view_bump_zoom_level
#10 g_source_get_current_time
from /lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#12 g_main_context_check
from /lib/libglib-2.0.so.0
#13 g_main_loop_run
from /lib/libglib-2.0.so.0
#14 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#15 POA_Nautilus_MetafileMonitor__init
#16 __libc_start_main
from /lib/libc.so.6
#17 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 Susana 2006-12-05 22:16:17 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 374002 ***