Version: 2.16.4

What were you doing when the application crashed?
Ho tentato di aprire SoundJuicer da shell:
soundjuicer -d /dev/hdc


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 60207104 vsize: 60207104 resident: 15458304 share: 11841536 rss: 15458304 rss_rlim: 4294967295
CPU usage: start_time: 1191079035 rtime: 55 utime: 46 stime: 9 cutime:0 cstime: 0 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e6db10 (LWP 17022)]
(no debugging symbols found)
0xb7eb9bf1 in waitpid () from /lib/libpthread.so.0

+ Trace 166424

----------- .xsession-errors (160 sec old) ---------------------
        that we're *trying* to run your application.
        This dialog box will automatically disappear after 30 seconds,
        or after your application finishes.
        You can permanently disable this dialog by selecting
        the option below.
        " 2>/dev/null
closing
closing
closing
** (sound-juicer:16909): WARNING **: hal_initialize failed: (null)
** (sound-juicer:16919): WARNING **: hal_initialize failed: (null)
--------------------------------------------------