GNOME Bugzilla – Bug 420696
crash in Gimmie: I clicked on the recentl...
Last modified: 2007-03-20 22:11:27 UTC
What were you doing when the application crashed? I clicked on the recently used button and tried to increase the time window of dates for which it showed files. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 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 (34 sec old) --------------------- ** (yelp:31782): WARNING **: IOR not set. ** (yelp:31782): WARNING **: Could not locate registry /var/lib/python-support/python2.5/apport/report.py: inconsistent use of tabs and spaces in indentation /var/lib/python-support/python2.5/problem_report.py: inconsistent use of tabs and spaces in indentation /var/lib/python-support/python2.5/apport/fileutils.py: inconsistent use of tabs and spaces in indentation /var/lib/python-support/python2.5/apport/packaging_impl.py: inconsistent use of tabs and spaces in indentation /var/lib/python-support/python2.5/apport/python_hook.py: inconsistent use of tabs and spaces in indentation (gnome-terminal:6853): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-panel:5881): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80ca048 (gnome-panel:5881): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80ca048 -------------------------------------------------- Traceback (most recent call last):
+ Trace 120487
self.spark.connect("zoom-changed", lambda w, num_days: self.set_zoom_level(num_days))
self.label.set_text(label)
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 416920 ***