GNOME Bugzilla – Bug 477399
crash in Volume Control: I'm just changed volume ...
Last modified: 2007-09-16 21:51:30 UTC
Version: 2.18.0 What were you doing when the application crashed? I'm just changed volume and add new channels to mixer Distribution: Mandriva Linux release 2007.1 (Official) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 44584960 vsize: 44584960 resident: 14536704 share: 11022336 rss: 14536704 rss_rlim: 4294967295 CPU usage: start_time: 1189923800 rtime: 123 utime: 109 stime: 14 cutime:3 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-volume-control' (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227457664 (LWP 5949)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 163254
Thread 1 (Thread -1227457664 (LWP 5949))
----------- .xsession-errors (112 sec old) --------------------- starting indexing... indexing #1 - /home/ntrl/tmp/virtual-ntrl.u836zT flushing all words Finished indexing. Waiting for new events... DCOPClient::attachInternal. Attach failed Could not open network socket kbuildsycoca running... kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x8092c90 ): KAccel object already contains an action name "play_pause" QLayout "unnamed" added to QVBox "unnamed", which already has a layout kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x8092c90 ): KAccel object already contains an action name "play_pause" QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow Amarok: [Loader] Starting amarokapp.. Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp. QColor::setRgb: RGB parameter(s) out of range QColor::setRgb: RGB parameter(s) out of range QColor::setRgb: RGB parameter(s) out of range --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 471133 ***