GNOME Bugzilla – Bug 466132
crash in Sound Juicer CD Extractor:
Last modified: 2007-08-13 14:48:10 UTC
Version: 2.16.4 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 71917568 vsize: 71917568 resident: 25190400 share: 20049920 rss: 25190400 rss_rlim: 4294967295 CPU usage: start_time: 1186981057 rtime: 750 utime: 471 stime: 279 cutime:5 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 -1209054336 (LWP 7646)] (no debugging symbols found) 0x00253402 in __kernel_vsyscall ()
+ Trace 154791
Thread 1 (Thread -1209054336 (LWP 7646))
----------- .xsession-errors (987495 sec old) --------------------- Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". ...Too much output, ignoring rest... --------------------------------------------------
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 457609 ***