GNOME Bugzilla – Bug 490898
crash in Gimmie: I had just added gimmie ...
Last modified: 2007-10-27 23:25:08 UTC
What were you doing when the application crashed? I had just added gimmie to the panel. After i clicked on "linux" and "recently used" i got this error-message, so i don't realy wanted to do something exotic :( Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 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 (139 sec old) --------------------- 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. Fenstermanager-Warnung: Ungültiges WM_TRANSIENT_FOR-Fenster 0x76 festgelegt für 0x220009c (). QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * ) X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 Minor opcode: 0 Resource id: 0x240009a kded: ERROR: : couldn't create slave : Kein Kontakt zu klauncher Fenstermanager-Warnung: Ungültiges WM_TRANSIENT_FOR-Fenster 0x76 festgelegt für 0x220008a (). (gnome-panel:5793): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 173306
printer.connect("attributes_changed", lambda p: self.emit("reload"))
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 475020 ***