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 420689 - crash in CD/DVD Creator: Nothing special.
crash in CD/DVD Creator: Nothing special.
Status: RESOLVED DUPLICATE of bug 374002
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-20 20:26 UTC by alwin_bakker
Modified: 2007-03-21 16:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description alwin_bakker 2007-03-20 20:26:49 UTC 
What were you doing when the application crashed?
Nothing special.


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.20-1.2925.fc6 #1 SMP Sat Mar 10 18:38:39 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 477925376 vsize: 477925376 resident: 37376000 share: 20832256 rss: 37376000 rss_rlim: -1
CPU usage: start_time: 1174421757 rtime: 6811 utime: 3121 stime: 3690 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496334768 (LWP 13028)]
(no debugging symbols found)
0x0000003dbbe0d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 120479

Thread 1 (Thread 46912496334768 (LWP 13028))

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


----------- .xsession-errors (15130 sec old) ---------------------
Selected video codec: [mpeg12] vfm: libmpeg2 (MPEG-1 or 2 (libmpeg2))
==========================================================================
==========================================================================
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
AUDIO: 48000 Hz, 2 ch, s16le, 128.0 kbit/8.33% (ratio: 16000->192000)
Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
==========================================================================
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 480 x 360 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
VO: [xv] 480x360 => 480x360 Planar YV12  [fs]
A:   0.5 V:   0.0 A-V:  0.420 ct:  0.386   1/  1 ??% ??% ??,?% 0 0              
A:   0.5 V:   0.4 A-V:  0.031 ct:  0.389   2/  2 ??% ??% ??,?% 0 0              
A:   0.5 V:   0.5 A-V:  0.047 ct:  0.3
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Christian Kirbach 2007-03-21 16:55: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 ***