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 386867 - crash in CD/DVD Creator:
crash in CD/DVD Creator:
Status: RESOLVED DUPLICATE of bug 363417
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-17 17:56 UTC by hydra
Modified: 2006-12-17 20:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description hydra 2006-12-17 17:56:56 UTC
What were you doing when the application crashed?



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.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors ---------------------
(nautilus:2731): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists.
(nautilus:2731): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists.
(nautilus:2731): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x0 specified for 0x4a02d50 (About Amar).
(nautilus:2731): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists.
(nautilus:2731): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists.
(nautilus:2731): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists.
** (bug-buddy:26902): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 90304512 vsize: 0 resident: 90304512 share: 0 rss: 24670208 rss_rlim: 0
CPU usage: start_time: 1166353536 rtime: 0 utime: 19634 stime: 0 cutime:17497 cstime: 0 timeout: 2137 it_real_value: 0 frequency: 124

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 -1208232240 (LWP 2731)]
(no debugging symbols found)
0x00421402 in __kernel_vsyscall ()

Thread 1 (Thread -1208232240 (LWP 2731))

  • #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 g_type_check_instance
    from /lib/libgobject-2.0.so.0
  • #5 g_signal_handlers_disconnect_matched
    from /lib/libgobject-2.0.so.0
  • #6 fm_directory_view_bump_zoom_level
  • #7 fm_directory_view_bump_zoom_level
  • #8 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #9 POA_Nautilus_MetafileMonitor__init
  • #10 POA_Nautilus_MetafileMonitor__init
  • #11 POA_Nautilus_MetafileMonitor__init
  • #12 POA_Nautilus_MetafileMonitor__init
  • #13 POA_Nautilus_MetafileMonitor__init
  • #14 nautilus_undo_transaction_unregister_object
  • #15 fm_directory_view_bump_zoom_level
  • #16 nautilus_clipboard_monitor_emit_changed
  • #17 nautilus_directory_async_state_changed
  • #18 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #20 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 POA_Nautilus_MetafileMonitor__init
  • #24 __libc_start_main
    from /lib/libc.so.6
  • #25 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall

Comment 1 palfrey 2006-12-17 20:39:36 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 363417 ***