GNOME Bugzilla – Bug 483868
crash in Gimmie: just crashed
Last modified: 2007-10-05 22:18:46 UTC
What were you doing when the application crashed? just crashed Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: OSX 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 (88 sec old) --------------------- fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 Window manager warning: "Disabled" found in configuration database is not a valid value for keybinding "toggle_shaded" Window manager warning: "Disabled" found in configuration database is not a valid value for keybinding "run_command_9" err:systray:delete_icon invalid tray icon ID specified: 0 (gnome-terminal:19812): Vte-WARNING **: No handler for control sequence `device-control-string' defined. Unable to open desktop file file:///home/michal/Desktop/root.desktop for panel launcher: No such file or directory -------------------------------------------------- Traceback (most recent call last):
+ Trace 168101
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 ***