GNOME Bugzilla – Bug 533340
crash in Deskbar:
Last modified: 2008-05-16 11:19:12 UTC
What were you doing when the application crashed? Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.1 2008-05-07 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (1168 sec old) --------------------- QSettings: failed to open file '/etc/qt3/qt_plugins_3.3rc' QSettings: failed to open file '/etc/qt3/qt_plugins_3.3rc' kbuildsycoca running... DCOP Cleaning up dead connections. kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x8fc050 ): 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 = 0x8fc050 ): KAccel object already contains an action name "play_pause" QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow QObject::connect: Incompatible sender/receiver arguments StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&) 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 -------------------------------------------------- Traceback (most recent call last):
+ Trace 197818
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
self.beagle.send_request_async(self.beagle_query)
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 530057 ***