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 381385 - crash in CD/DVD Creator: Opening a folder.
crash in CD/DVD Creator: Opening a folder.
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: 2006-12-01 19:56 UTC by G. Michael Carter
Modified: 2006-12-01 20:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description G. Michael Carter 2006-12-01 19:56:09 UTC
What were you doing when the application crashed?
Opening a folder.


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 (51580 sec old) ---------------------
Selected video codec: [ffmjpeg] vfm: ffmpeg (FFmpeg MJPEG decoder)
==========================================================================
==========================================================================
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 8000 Hz, 1 ch, u8, 64.0 kbit/100.00% (ratio: 8000->8000)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
AO: [alsa] 48000Hz 1ch u8 (1 bytes per sample)
Starting playback...
VDec: vo config request - 640 x 480 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 3)
Movie-Aspect is undefined - no prescaling applied.
VO: [xv] 640x480 => 640x480 Planar YV12 
A:   0.1 V:   0.0 A-V:  0.066 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
A:   0.1 V:   0.0 A-V:  0.033 ct:  0.000   2/  2 ??% ??% ??,?% 0 0              
A:   0.1 V:   0.1 A-V:  0.021 ct:  0.000   3/  3 ??% ??% ??,?% 0 0              
A:   0.1 V:   0.1 A-V:  0.009 ct:  0.001   4/  4 ??% ??% ??,?% 0 0              
...Too much output, ignoring rest...
--------------------------------------------------

Memory status: size: 167075840 vsize: 0 resident: 167075840 share: 0 rss: 51609600 rss_rlim: 0
CPU usage: start_time: 1164951295 rtime: 0 utime: 9153 stime: 0 cutime:7030 cstime: 0 timeout: 2123 it_real_value: 0 frequency: 428

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 -1208329472 (LWP 24048)]
(no debugging symbols found)
0x00b9c402 in __kernel_vsyscall ()

Thread 1 (Thread -1208329472 (LWP 24048))

  • #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 Germán Poo-Caamaño 2006-12-01 20:11:23 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 ***