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 464851 - crash in Sound Juicer CD Extractor: Ripping a CD
crash in Sound Juicer CD Extractor: Ripping a CD
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-08 22:24 UTC by adc_w
Modified: 2007-08-09 17:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description adc_w 2007-08-08 22:24:20 UTC 
Version: 2.16.4

What were you doing when the application crashed?
Ripping a CD


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:19 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 517509120 vsize: 517509120 resident: 37793792 share: 21708800 rss: 37793792 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186611209 rtime: 31119 utime: 30462 stime: 657 cutime:3 cstime: 1 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496377632 (LWP 31611)]
[New Thread 1126189392 (LWP 32112)]
(no debugging symbols found)
0x000000395480d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 153822

Thread 1 (Thread 46912496377632 (LWP 31611))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__VOID
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_list_store_set_valist
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #4 gtk_list_store_set
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #5 ??
  • #6 ??
  • #7 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #8 g_cclosure_marshal_VOID__VOID
    from /lib64/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #11 g_cclosure_marshal_VOID__VOID
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #13 g_cclosure_marshal_VOID__VOID
    from /lib64/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #16 g_cclosure_marshal_VOID__VOID
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 g_cclosure_marshal_VOID__VOID
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #18 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #19 g_cclosure_marshal_VOID__VOID
    from /lib64/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #22 g_cclosure_marshal_VOID__VOID
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #23 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #24 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #25 g_cclosure_marshal_VOID__VOID
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #26 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #27 g_cclosure_marshal_VOID__VOID
    from /lib64/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #29 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #30 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (14611 sec old) ---------------------
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
/bin/bash: line: command not found
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Iestyn Pryce 2007-08-09 17:38:42 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 ***