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 578853 - crash in Audio CD Extractor: Post exraction ejection ...
crash in Audio CD Extractor: Post exraction ejection ...
Status: RESOLVED DUPLICATE of bug 553324
Product: sound-juicer
Classification: Applications
Component: general
2.24.x
Other All
: High critical
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-04-13 17:41 UTC by Dwayne Bailey
Modified: 2009-04-13 20:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Dwayne Bailey 2009-04-13 17:41:26 UTC
Version: 2.24.0

What were you doing when the application crashed?
Post exraction ejection crash


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.21-170.2.56.fc10.i686 #1 SMP Mon Mar 23 23:37:54 EDT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 220692480 vsize: 220692480 resident: 40009728 share: 17338368 rss: 40009728 rss_rlim: 18446744073709551615
CPU usage: start_time: 1239641500 rtime: 105327 utime: 102581 stime: 2746 cutime:12 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb7ed5770 (LWP 27986)]
[New Thread 0xb35ffb90 (LWP 29266)]
0x00f34416 in __kernel_vsyscall ()

Thread 1 (Thread 0xb7ed5770 (LWP 27986))

  • #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 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 <signal handler called>
  • #8 _gtk_file_system_volume_free
    at gtkfilesystem.c line 1758
  • #9 model_free_row_data
    at gtkfilechooserbutton.c line 1584
  • #10 model_remove_rows
    at gtkfilechooserbutton.c line 2037
  • #11 fs_volumes_changed_cb
    at gtkfilechooserbutton.c line 2392
  • #12 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #13 IA__g_closure_invoke
    at gclosure.c line 767
  • #14 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #15 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #16 IA__g_signal_emit
    at gsignal.c line 3034
  • #17 volumes_changed
    at gtkfilesystem.c line 161
  • #18 IA__g_cclosure_marshal_VOID__OBJECT
    at gmarshal.c line 636
  • #19 IA__g_closure_invoke
    at gclosure.c line 767
  • #20 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #21 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #22 IA__g_signal_emit_by_name
    at gsignal.c line 3071
  • #23 child_volume_changed
    at gunionvolumemonitor.c line 270
  • #24 IA__g_cclosure_marshal_VOID__OBJECT
    at gmarshal.c line 636
  • #25 IA__g_closure_invoke
    at gclosure.c line 767
  • #26 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #27 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #28 IA__g_signal_emit_by_name
    at gsignal.c line 3071
  • #29 ??
    from /usr/lib/gio/modules/libgioremote-volume-monitor.so
  • #30 g_idle_dispatch
    at gmain.c line 4235
  • #31 g_main_dispatch
    at gmain.c line 2144
  • #32 IA__g_main_context_dispatch
    at gmain.c line 2697
  • #33 g_main_context_iterate
    at gmain.c line 2778
  • #34 IA__g_main_loop_run
    at gmain.c line 2986
  • #35 IA__gtk_main
    at gtkmain.c line 1200
  • #36 main
    at sj-main.c line 1848


----------- .xsession-errors ---------------------
warning: the debug information found in "/usr/lib/debug//usr/lib/libk5crypto.so.3.1.debug" does not match "/usr/lib/libk5crypto.so.3" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib/libk5crypto.so.3.1.debug" does not match "/usr/lib/libk5crypto.so.3" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libkrb5support.so.0.1.debug" does not match "/usr/lib/libkrb5support.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib/libkrb5support.so.0.1.debug" does not match "/usr/lib/libkrb5support.so.0" (CRC mismatch).
Cannot access memory at address 0x5
Cannot access memory at address 0x5
--------------------------------------------------
Comment 1 Gianluca Borello 2009-04-13 20:40:30 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 553324 ***