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 411882 - crash in CD/DVD Creator: Inserted Audio CD. Nauti...
crash in CD/DVD Creator: Inserted Audio CD. Nauti...
Status: RESOLVED DUPLICATE of bug 351366
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-25 12:41 UTC by Peter Heckert
Modified: 2007-02-28 15:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Peter Heckert 2007-02-25 12:41:21 UTC 
What were you doing when the application crashed?
Inserted Audio CD. Nautilus popped up.
Clicked "Audio Disc" in left pane "Tree" of nautilus.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-athlon-preempt #1 PREEMPT Sat Jan 6 20:21:24 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 136736768 vsize: 0 resident: 136736768 share: 0 rss: 34897920 rss_rlim: 0
CPU usage: start_time: 1172407131 rtime: 0 utime: 352 stime: 0 cutime:316 cstime: 0 timeout: 36 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 -1209010480 (LWP 11228)]
(no debugging symbols found)
0x00dbf402 in __kernel_vsyscall ()

+ Trace 113757

Thread 1 (Thread -1209010480 (LWP 11228))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/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_directory_async_state_changed
  • #6 nautilus_undo_transaction_unregister_object
  • #7 nautilus_directory_async_state_changed
  • #8 fm_directory_view_bump_zoom_level
  • #9 fm_directory_view_bump_zoom_level
  • #10 g_source_is_destroyed
    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 


----------- .xsession-errors (133835 sec old) ---------------------
(nautilus:3475): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x100e163 (complete -); these messages lack timestamps and therefore suck.
MPlayer 1.0rc1-rpm.livna.org-4.1.1 (C) 2000-2006 MPlayer Team
CPU: AMD Duron(tm) Processor (Family: 6, Model: 7, Stepping: 1)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 0
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
Window manager warning: Window 0x2000019 (MPlayer) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 440 x 120; this doesn't make much sense.
Playing /home/peter/gtk-gnutella-downloads/complete/Sumi Jo and Vincenzo Scalera - Nel cor piu non mi sento.wma.

Cache fill:  0.78% (16384 bytes)   
Cache fill:  0.78% (16384 bytes)   
Cache fill:  0.78% (16384 bytes)   
Cache fill:  0.78% (16384 bytes)   
Cache fill:  0.78% (16384 bytes)   
Cache fill:  0.78% 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-02-28 15:33:47 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 351366 ***