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 381855 - [6x gtk_menu_is_empty] crash in CD/DVD Creator: DVD in de brander gedaan...
[6x gtk_menu_is_empty] crash in CD/DVD Creator: DVD in de brander gedaan...
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 371823 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-03 12:05 UTC by johan
Modified: 2007-07-30 02:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description johan 2006-12-03 12:05:35 UTC
What were you doing when the application crashed?
DVD in de brander gedaan en lade gesloten
Daarna verscheen een pop up
Bij pop-up "DVD branden" gekozen
Daarna foutmelding



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

Memory status: size: 109920256 vsize: 0 resident: 109920256 share: 0 rss: 28872704 rss_rlim: 0
CPU usage: start_time: 1165147342 rtime: 0 utime: 198 stime: 0 cutime:178 cstime: 0 timeout: 20 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 -1227233616 (LWP 9270)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227233616 (LWP 9270))

  • #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 _gtk_menu_is_empty
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 _gtk_menu_is_empty
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 _gtk_menu_is_empty
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 _gtk_menu_is_empty
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 _gtk_menu_is_empty
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 gtk_widget_show
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 POA_Nautilus_MetafileMonitor__init
  • #17 nautilus_undo_transaction_unregister_object
  • #18 fm_directory_view_bump_zoom_level
  • #19 nautilus_clipboard_monitor_emit_changed
  • #20 nautilus_directory_async_state_changed
  • #21 nautilus_directory_async_state_changed
  • #22 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
    from /usr/lib/libgthread-2.0.so.0
  • #27 ??
  • #28 ??
    from /usr/lib/libglib-2.0.so.0
  • #29 ??
  • #30 g_slice_alloc
    from /usr/lib/libglib-2.0.so.0
  • #31 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #32 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #33 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #34 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #35 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 POA_Nautilus_MetafileMonitor__init
  • #37 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #38 ??
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2007-01-26 19:43:36 UTC
*** Bug 371823 has been marked as a duplicate of this bug. ***
Comment 2 palfrey 2007-02-22 15:22:55 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 3 Pedro Villavicencio 2007-07-30 02:12:26 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!