GNOME Bugzilla – Bug 534266
crash in Gimmie: selecting "Linux -> Rece...
Last modified: 2008-05-26 00:52:50 UTC
What were you doing when the application crashed? selecting "Linux -> Recently Used" menu button 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 13:23:42 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: aero-clone 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 (39 sec old) --------------------- Starting gtk-window-decorator /home/tamati/.themes/aero-clone/gtk-2.0/toolbar-custom.rc:21: Unable to locate image file in pixmap_path: "Toolbar/toolbar-black.png" /home/tamati/.themes/aero-clone/gtk-2.0/toolbar-custom.rc:24: Background image options specified without filename /home/tamati/.themes/aero-clone/gtk-2.0/gtkrc:187: Unable to locate image file in pixmap_path: "Arrows/arrow-up.png" /home/tamati/.themes/aero-clone/gtk-2.0/gtkrc:191: Overlay image options specified without filename /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format I/O warning : failed to load external entity "/home/tamati/.compiz/session/default0" PID TTY TIME CMD 5984 ? 00:00:00 pulseaudio Launched application : 6386 /home/tamati/.themes/aero-clone/gtk-2.0/toolbar-custom.rc:21: Unable to locate image file in pixmap_path: "Toolbar/toolbar-black.png" /home/tamati/.themes/aero-clone/gtk-2.0/toolbar-custom.rc:24: Background image options specified without filename /home/tamati/.themes/aero-clone/gtk-2.0/gtkrc:187: Unable to locate image file in pixmap_path: "Arrows/arrow-up.png" /home/tamati/.themes/aero-clone/gtk-2.0/gtkrc:191: Overlay image options specified without filename -------------------------------------------------- Gimmie Version: 0.2.8 Traceback (most recent call last):
+ Trace 198351
printer.connect("attributes_changed", lambda *args: self.emit("reload"))
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 475020 ***