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 586540 - crash in Open Folder: nautilus crashes after I...
crash in Open Folder: nautilus crashes after I...
Status: RESOLVED FIXED
Product: brasero
Classification: Applications
Component: general
git master
Other All
: High critical
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-06-21 15:44 UTC by Hussam Al-Tayeb
Modified: 2009-08-01 08:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26

Attachments
crash log (21.25 KB, text/plain)
2009-08-01 08:04 UTC, Hussam Al-Tayeb 		Details

Description Hussam Al-Tayeb 2009-06-21 15:44:05 UTC 
Version: 2.26.3

What were you doing when the application crashed?
nautilus crashes after I successfully burn a data cd and eject the cd using cd/dvd creator with brasero nautilus extension.


Distribution: Unknown
Gnome Release: 2.26.2 2009-05-21 (Archlinux)
BugBuddy Version: 2.26.0

System: Linux 2.6.30-ARCH #1 SMP PREEMPT Fri Jun 19 21:25:17 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10601901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 91697152 vsize: 91697152 resident: 29831168 share: 17375232 rss: 29831168 rss_rlim: 18446744073709551615
CPU usage: start_time: 1245586357 rtime: 3970 utime: 3456 stime: 514 cutime:45 cstime: 297 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6efb930 (LWP 31425)]
[New Thread 0xb646eb70 (LWP 32610)]
[New Thread 0xb4c61b70 (LWP 32604)]
0xb7fac424 in __kernel_vsyscall ()

+ Trace 216111

Thread 1 (Thread 0xb6efb930 (LWP 31425))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #4 run_bug_buddy
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 bugbuddy_segv_handle
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 brasero_data_session_disc_removed_cb
    at brasero-data-session.c line 553
  • #8 IA__g_cclosure_marshal_VOID__OBJECT
    at gmarshal.c line 636
  • #9 IA__g_closure_invoke
    at gclosure.c line 767
  • #10 signal_emit_unlocked_R
    at gsignal.c line 3247
  • #11 IA__g_signal_emit_valist
    at gsignal.c line 2980
  • #12 IA__g_signal_emit
    at gsignal.c line 3037
  • #13 brasero_medium_monitor_medium_removed_cb
    at brasero-medium-monitor.c line 308
  • #14 IA__g_cclosure_marshal_VOID__OBJECT
    at gmarshal.c line 636
  • #15 IA__g_closure_invoke
    at gclosure.c line 767
  • #16 signal_emit_unlocked_R
    at gsignal.c line 3247
  • #17 IA__g_signal_emit_valist
    at gsignal.c line 2980
  • #18 IA__g_signal_emit
    at gsignal.c line 3037
  • #19 brasero_drive_check_medium_inside
    at brasero-drive.c line 866
  • #20 brasero_marshal_VOID__STRING_STRING
    at libbrasero-marshal.c line 91
  • #21 IA__g_closure_invoke
    at gclosure.c line 767
  • #22 signal_emit_unlocked_R
    at gsignal.c line 3247
  • #23 IA__g_signal_emit_valist
  • #24 IA__g_signal_emit
    at gsignal.c line 3037
  • #25 brasero_hal_watch_property_changed_cb
    at burn-hal-watch.c line 93
  • #26 filter_func
    from /usr/lib/libhal.so.1
  • #27 dbus_connection_dispatch
    from /usr/lib/libdbus-1.so.3
  • #28 message_queue_dispatch
    from /usr/lib/libdbus-glib-1.so.2
  • #29 IA__g_main_context_dispatch
    at gmain.c line 1814
  • #30 g_main_context_iterate
    at gmain.c line 2445
  • #31 IA__g_main_loop_run
    at gmain.c line 2653
  • #32 IA__gtk_main
    at gtkmain.c line 1205
  • #33 main
    at nautilus-main.c line 518
  • #0 __kernel_vsyscall 


---- Critical and fatal warnings logged during execution ----

** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** Gtk **: gtk_box_pack: assertion `child->parent == NULL' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** nautilus **: murrine_style_draw_box: assertion `width >= -1' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 


----------- .xsession-errors (61072 sec old) ---------------------
(firefox-bin:9117): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:9117): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:9117): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:9117): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:9117): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:9117): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:9117): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Hussam Al-Tayeb 2009-06-21 15:45:22 UTC 
This crash happens with brasero git (2.27.3)
Comment 2 Philippe Rouquier 2009-07-30 11:11:56 UTC 
Thanks for the report. I think it has been fixed with the latest tree. Could you check that please? Thanks in advance.
Comment 3 Hussam Al-Tayeb 2009-07-30 11:32:07 UTC 
Can't test. I get this error:

Running autoconf...
configure.in:417: warning: GTK_DOC_CHECK was called before AC_PROG_LIBTOOL
aclocal.m4:750: GTK_DOC_CHECK is expanded from...
configure.in:417: the top level
configure.in:417: warning: GTK_DOC_CHECK was called before AM_PROG_LIBTOOL
configure:1702: error: possibly undefined macro: _m4_text_wrap_word
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
Comment 4 Hussam Al-Tayeb 2009-08-01 08:04:06 UTC 
Created attachment 139672 [details]
crash log

Still crashes :(
Comment 5 Philippe Rouquier 2009-08-01 08:49:11 UTC 
As discussed with Hussam on IRC. This bug is now fixed.