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 575808 - crash in Audio CD Extractor: Crash in Sound Juicer wh...
crash in Audio CD Extractor: Crash in Sound Juicer wh...
Status: RESOLVED DUPLICATE of bug 572145
Product: sound-juicer
Classification: Applications
Component: general
2.26.x
Other All
: High critical
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-18 09:59 UTC by elektrobank01
Modified: 2009-03-18 12:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description elektrobank01 2009-03-18 09:59:59 UTC
Version: 2.26.0

What were you doing when the application crashed?
Crash in Sound Juicer while started to Extract


Distribution: Mandriva Linux release 2009.1 (Cooker) for i586
Gnome Release: 2.26.0 2009-03-16 (Mandriva)
BugBuddy Version: 2.26.0

System: Linux 2.6.29-desktop586-0.rc8.1mnb #1 SMP Fri Mar 13 15:41:04 BRT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10600000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Dust
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 161267712 vsize: 161267712 resident: 26509312 share: 16113664 rss: 26509312 rss_rlim: 18446744073709551615
CPU usage: start_time: 1237370213 rtime: 66 utime: 58 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/sound-juicer'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb67be6f0 (LWP 10526)]
[New Thread 0xafad3b90 (LWP 10534)]
[New Thread 0xb5004b90 (LWP 10533)]
(no debugging symbols found)
0xffffe430 in __kernel_vsyscall ()

Thread 1 (Thread 0xb67be6f0 (LWP 10526))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 ??
  • #8 filepath_parse_pattern
  • #9 ??
  • #10 ??
  • #11 on_extract_activate
  • #12 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 ??
    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 IA__gtk_button_clicked
    at gtkbutton.c line 1106
  • #18 gtk_real_button_released
    at gtkbutton.c line 1702
  • #19 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #22 ??
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #25 IA__gtk_button_released
    at gtkbutton.c line 1098
  • #26 gtk_button_button_release
    at gtkbutton.c line 1594
  • #27 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #28 ??
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #30 ??
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #33 gtk_widget_event_internal
    at gtkwidget.c line 4761
  • #34 IA__gtk_propagate_event
    at gtkmain.c line 2396
  • #35 IA__gtk_main_do_event
    at gtkmain.c line 1601
  • #36 gdk_event_dispatch
    at gdkevents-x11.c line 2364
  • #37 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #38 ??
    from /usr/lib/libglib-2.0.so.0
  • #39 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #40 IA__gtk_main
    at gtkmain.c line 1205
  • #41 main
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


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

** Gtk **: gtk_entry_set_text: assertion `text != NULL' failed 
** Gtk **: gtk_entry_set_text: assertion `text != NULL' failed 
** sound-juicer **: musicbrainz_submit_message_area_new: assertion `title != NULL' failed 
** GLib-GObject **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed 
** sound-juicer **: gedit_message_area_set_default_response: assertion `GEDIT_IS_MESSAGE_AREA (message_area)' failed 
** Gtk **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed 


----------- .xsession-errors ---------------------
(sound-juicer:10526): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
** (sound-juicer:10526): CRITICAL **: gedit_message_area_set_default_response: assertion `GEDIT_IS_MESSAGE_AREA (message_area)' failed
(sound-juicer:10526): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed
gnome-session[3450]: WARNING: Unable to find watch for alarm 12583270
gnome-session[3450]: WARNING: Unable to find watch for alarm 12583271
/home/amd/.themes/Dust/gtk-2.0/gtkrc:708: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/home/amd/.themes/Dust/gtk-2.0/gtkrc:709: Murrine configuration option "lightborder_ratio" will be deprecated in future releases. Please use "lightborder_shade" instead.
warning: the debug information found in "/usr/lib/debug//usr/bin/sound-juicer.debug" does not match "/usr/bin/sound-juicer" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/bin/sound-juicer.debug" does not match "/usr/bin/sound-juicer" (CRC mismatch).
--------------------------------------------------
Comment 1 Gianluca Borello 2009-03-18 12:13:19 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 572145 ***