GNOME Bugzilla – Bug 494566
crash in Gimmie: printed a pdf
Last modified: 2007-11-07 23:02:08 UTC
What were you doing when the application crashed? printed a pdf 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: Clearlooks Icon Theme: gnome 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 (60 sec old) --------------------- CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... (mail-notification:6149): mail-notification-WARNING **: 60310786@popstore.nuim.ie: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found Opening: /home/nmurphy/work/references/my-refs.bib Opening: /home/nmurphy/work/references/my-unread-refs.bib Opening: /home/nmurphy/work/references/me-refs.bib Opening: /home/nmurphy/work/references/membranes/P-Bibliography.bib Opening: /home/nmurphy/work/reports/conversion/trunk/bibfile.bib Opening: /home/nmurphy/work/papers/wodiss/trunk/wodiss.bib Opening: /home/nmurphy/work/papers/p-conj/trunk/pcong.bib (mail-notification:6149): mail-notification-WARNING **: 60310786@popstore.nuim.ie: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 176022
printer.connect("attributes_changed", lambda p: 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 ***