GNOME Bugzilla – Bug 426436
crash in Gimmie:
Last modified: 2007-05-26 01:51:55 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-13-386 #2 Sun Mar 25 00:18:53 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 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 (147 sec old) --------------------- alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midOops: malloc_video_bufs is 1 (expected 0) [utils/linux/capture/libng/grab-ng.c:malloc_bufs_check:231] Oops: processes is 1 (expected 0) [utils/linux/capture/libng/convert.c:process_check:179] beryl: core: Received winTypeAtom but unable to find the window for the event (gnome-terminal:11148): Vte-WARNING **: Can not find appropiate font for character U+0000. libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files -------------------------------------------------- Traceback (most recent call last):
+ Trace 125104
self.spark.connect("zoom-changed", lambda w, num_days: self.set_zoom_level(num_days))
self.label.set_text(label)
Sorry, additional details. When adjusting the timespan under the library tab, if you click directly on on a blank area (i.e. no graph in that spot) of the timeline/sparkline, it crashes the applet. Once in a while it requires a killall before you get the option to reload it, but it usually reloads on its own. This is definitely repeatable, it happens every time. Only the blank areas on the line that correspond to earlier then three months back seem to trigger the crash. Using the plus and minus signs to scroll through the timeline does NOT trigger the crash, only clicking on the timeline will.
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 ***