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 424200 - crash in CD/DVD Creator: In the tree view of the ...
crash in CD/DVD Creator: In the tree view of the ...
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-03-29 17:39 UTC by rodrigorivascosta
Modified: 2007-03-31 14:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rodrigorivascosta 2007-03-29 17:39:18 UTC 
What were you doing when the application crashed?
In the tree view of the left, I expanded the little triangle of an "Audio Disc", first it said: "unable to access to cdda://whatever" and then it crashed.


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.2933.fc6 #1 SMP Mon Mar 19 11:38:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 147501056 vsize: 0 resident: 147501056 share: 0 rss: 35921920 rss_rlim: 0
CPU usage: start_time: 1175101660 rtime: 0 utime: 4812 stime: 0 cutime:4356 cstime: 0 timeout: 456 it_real_value: 0 frequency: 384

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 -1208231168 (LWP 2991)]
(no debugging symbols found)
0x00474402 in __kernel_vsyscall ()

+ Trace 123279

Thread 1 (Thread -1208231168 (LWP 2991))

  • #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 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 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (784 sec old) ---------------------
and may be very slow or crash. This is not a bug in libavcodec,
but in the compiler. Do not report crashes to FFmpeg developers.
Compiler did not align stack variables. Libavcodec has been miscompiled
and may be very slow or crash. This is not a bug in libavcodec,
but in the compiler. Do not report crashes to FFmpeg developers.
Compiler did not align stack variables. Libavcodec has been miscompiled
and may be very slow or crash. This is not a bug in libavcodec,
but in the compiler. Do not report crashes to FFmpeg developers.
[mpeg4 @ 0x1144b64]looks like this file was encoded with (divx4/(old)xvid/opendivx) -> forcing low_delay flag
[mpeg4 @ 0x1144b64]looks like this file was encoded with (divx4/(old)xvid/opendivx) -> forcing low_delay flag
Compiler did not align stack variables. Libavcodec has been miscompiled
and may be very slow or crash. This is not a bug in libavcodec,
but in the compiler. Do not report crashes to FFmpeg developers.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-03-31 14:14:32 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 ***