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 395746 - crash in CD/DVD Creator: ubdisk did not appear in...
crash in CD/DVD Creator: ubdisk did not appear in...
Status: RESOLVED DUPLICATE of bug 367101
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-12 11:36 UTC by zoeneal
Modified: 2007-01-14 02:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description zoeneal 2007-01-12 11:36:25 UTC
What were you doing when the application crashed?
ubdisk did not appear in the "places" section (on the left) of nautilus window.  I wanted it there, so I dragged the icon from the destop to the "places" at which point it crash.

oh by the way, the nautilus window was run as root from an xterm. 


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

Memory status: size: 72957952 vsize: 0 resident: 72957952 share: 0 rss: 25387008 rss_rlim: 0
CPU usage: start_time: 1168576415 rtime: 0 utime: 98 stime: 0 cutime:94 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227102544 (LWP 6782)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227102544 (LWP 6782))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 nautilus_file_ref
  • #11 POA_Nautilus_MetafileMonitor__init
  • #12 _gtk_marshal_BOOLEAN__OBJECT_INT_INT_UINT
    from /usr/lib/libgtk-x11-2.0.so.0
  • #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_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #17 gtk_drag_highlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 _gtk_drag_dest_handle_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #28 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #31 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 POA_Nautilus_MetafileMonitor__init
  • #33 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #34 ??
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2007-01-14 02:42:53 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 (and reopen that bug report) by installing some debugging packages [1], start Nautilus as normal, and try to reproduce the crash in order to help the developers?

[1] Please install the following debug packages provided by Ubuntu: nautilus-dbg, libglib2.0-0-dbg, libgtk2.0-0-dbg, libpango1.0-0-dbg, libgnomevfs2-0-dbg, and libgnomeui-0-dbg.

More details can be found here: http://live.gnome.org/GettingTraces


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