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 462962 - crash in Sound Juicer CD Extractor:
crash in Sound Juicer CD Extractor:
Status: RESOLVED DUPLICATE of bug 426935
Product: sound-juicer
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-03 01:51 UTC by tomatosukisukisuki
Modified: 2007-08-03 21:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description tomatosukisukisuki 2007-08-03 01:51:01 UTC 
Version: 2.16.4

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 117637120 vsize: 117637120 resident: 33775616 share: 22638592 rss: 33775616 rss_rlim: 4294967295
CPU usage: start_time: 1186105090 rtime: 55274 utime: 50360 stime: 4914 cutime:1 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208154400 (LWP 14847)]
[New Thread -1233716336 (LWP 14872)]
(no debugging symbols found)
0x0035e402 in __kernel_vsyscall ()

+ Trace 152439

Thread 1 (Thread -1208154400 (LWP 14847))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_list_store_set_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_list_store_set
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #11 ??
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #14 ??
  • #15 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #20 gst_bus_async_signal_func
    from /usr/lib/libgstreamer-0.10.so.0
  • #21 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #22 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #23 ??
    from /lib/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
warning: .dynamic section for "/lib/libattr.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libbeagle.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libFLAC.so.8" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libspeex.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Iestyn Pryce 2007-08-03 21:24:50 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 in order to help the developers?


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