GNOME Bugzilla – Bug 476625
crash in Sound Juicer CD Extractor: Attempting to rip an old...
Last modified: 2007-09-30 15:22:19 UTC
Version: 2.16.4 What were you doing when the application crashed? Attempting to rip an old 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.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 78090240 vsize: 78090240 resident: 28397568 share: 22872064 rss: 28397568 rss_rlim: 4294967295 CPU usage: start_time: 1189702497 rtime: 450 utime: 345 stime: 105 cutime:34 cstime: 8 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 -1208624256 (LWP 9684)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 162671
Thread 1 (Thread -1208624256 (LWP 9684))
----------- .xsession-errors (9748 sec old) --------------------- visible window : rx = 0, ry = 0, rw = 1600, rh=1131 visible window in button coords: rx = 0, ry = 2, rw = 45, rh=31 clicked viewport: x=0, y=0 Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp viewportNumH x V = 1 x 1, viewportCurX x Y = 0 x 0 visible window : rx = 0, ry = 0, rw = 1600, rh=1131 visible window in button coords: rx = 0, ry = 2, rw = 45, rh=31 viewportNumH x V = 1 x 1, viewportCurX x Y = 0 x 0 viewportNumH x V = 1 x 1, viewportCurX x Y = 0 x 0 visible window : rx = 0, ry = 0, rw = 1560, rh=1011 visible window in button coords: rx = 0, ry = 2, rw = 43, rh=28 viewportNumH x V = 1 x 1, viewportCurX x Y = 0 x 0 mouse pos: x = 1208, y = 105 ...Too much output, ignoring rest... --------------------------------------------------
*** This bug has been marked as a duplicate of 403870 ***