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 383055 - crash in CD/DVD Creator: rien
crash in CD/DVD Creator: rien
Status: RESOLVED DUPLICATE of bug 371237
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-06 16:56 UTC by bernard.langlois
Modified: 2006-12-06 19:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description bernard.langlois 2006-12-06 16:56:22 UTC
What were you doing when the application crashed?
rien


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 304451584 vsize: 304451584 resident: 35274752 share: 22863872 rss: 35274752 rss_rlim: -1
CPU usage: start_time: 1165345475 rtime: 2307 utime: 2110 stime: 197 cutime:390 cstime: 80 timeout: 0 it_real_value: 0 frequency: 100

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 47915865905744 (LWP 19244)]
[New Thread 1098918224 (LWP 20960)]
(no debugging symbols found)
0x00002b94442d4eef in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47915865905744 (LWP 19244))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #8 nautilus_file_ref
  • #9 fm_directory_view_bump_zoom_level
  • #10 fm_directory_view_bump_zoom_level
  • #11 POA_Nautilus_MetafileMonitor__init
  • #12 POA_Nautilus_MetafileMonitor__init
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #17 fm_directory_view_bump_zoom_level
  • #18 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #22 nautilus_file_get_uri
  • #23 nautilus_directory_async_state_changed
  • #24 nautilus_clipboard_monitor_emit_changed
  • #25 nautilus_clipboard_monitor_emit_changed
  • #26 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #31 gnome_vfs_volume_monitor_emit_pre_unmount
    from /usr/lib/libgnomevfs-2.so.0
  • #32 gnome_vfs_volume_monitor_client_get_type
    from /usr/lib/libgnomevfs-2.so.0
  • #33 dbus_connection_dispatch
    from /usr/lib/libdbus-1.so.3
  • #34 dbus_server_setup_with_g_main
    from /usr/lib/libdbus-glib-1.so.2
  • #35 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #36 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #37 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #38 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 POA_Nautilus_MetafileMonitor__init
  • #40 __libc_start_main
    from /lib/libc.so.6
  • #41 ??
  • #42 ??
  • #43 ??
  • #0 waitpid
    from /lib/libpthread.so.0

Comment 1 Jonathon Jongsma 2006-12-06 19:06:56 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 371237 ***