GNOME Bugzilla – Bug 436695
crash in Gimmie:
Last modified: 2007-05-23 22:33:40 UTC
What were you doing when the application 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-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Tango 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 (38 sec old) --------------------- to Mon May 7 22:01:47 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80c6dd0: Received at thread b3553b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80cac30 alarm-notify.c:337 (alarm_msgport_replied) - 0x80c3220: ReplNiet in staat om bureaublad-bestand file:///home/thijs/Desktop/IE6.0.desktop voor paneelstarter : Bestand of map bestaat niet te openen Niet in staat om bureaublad-bestand file:///home/thijs/Desktop/Servoy%20Client.desktop voor paneelstarter : Bestand of map bestaat niet te openen Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml Windowmanager waarschuwing: Verbinding is verbroken met display ':0.0'; waarschijnlijk is de X-server uitgezet of heeft u de window-manager vernietigd. Windowmanager waarschuwing: "" in de configuratiedatabase is geen geldige waarde voor toetsbinding "toggle_shaded" ** Message: <information> U bent nu verbonden met het draadloos netwerk 'WLAN'. -------------------------------------------------- Traceback (most recent call last):
+ Trace 132958
self.scroll.connect("size-request", lambda w, req: self._scroll_get_best_size(w, req))
upper = min(upper, int(self.get_screen().get_height() * 0.7))
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 417988 ***