Bug 395406 – crash in CD/DVD Creator: I don't know why Bug Bud...

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 395406 - crash in CD/DVD Creator: I don't know why Bug Bud...


Summary:	crash in CD/DVD Creator: I don't know why Bug Bud...


Status:	RESOLVED INCOMPLETE

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:	2007-01-11 14:36 UTC by rebecca.palmer
Modified:	2007-03-15 11:18 UTC

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

Description rebecca.palmer 2007-01-11 14:36:14 UTC

What were you doing when the application crashed?
I don't know why Bug Buddy wants to file a crash report for CD/DVD Creator when I haven't even opened said application.  The only thing that has crashed today (a few minutes ago) is Firefox, which I am preparing to report.


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

Memory status: size: 86663168 vsize: 0 resident: 86663168 share: 0 rss: 6430720 rss_rlim: 0
CPU usage: start_time: 1168501651 rtime: 0 utime: 4974 stime: 0 cutime:4526 cstime: 0 timeout: 448 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 -1226549584 (LWP 4127)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 101262

Thread 1 (Thread -1226549584 (LWP 4127))

#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 nautilus_directory_async_state_changed
#5 nautilus_clipboard_monitor_emit_changed
#6 nautilus_clipboard_monitor_emit_changed
#7 nautilus_directory_unref
#8 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#9 nautilus_directory_ref
#10 nautilus_directory_ref
#11 nautilus_marshal_BOOLEAN__POINTER
#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_MetafileMonitor__init
#18 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#19 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-01-11 18:50:13 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!

Comment 2 rebecca.palmer 2007-03-15 09:08:25 UTC

I haven't been able to get a trace with debugging symbols as this crash hasn't recurred since I installed them, though several other applications (usually Firefox-Ubuntu bug https://launchpad.net/bugs/78809) have crashed.

Since I am now having similar problems in Xfce (Bug Buddy showing an evolution-alarm-notify crash on every startup and the same Firefox problem), I suspect this isn't a GNOME bug at all.

Comment 3 palfrey 2007-03-15 11:18:56 UTC

As nautilus isn't crashing currently, I'm closing this bug for now. Please feel free to re-open if you can get a better stacktrace in the future.