After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 426244 - crash in Gimmie: tried to open the Applic...
crash in Gimmie: tried to open the Applic...
Status: RESOLVED DUPLICATE of bug 417988
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-04 14:32 UTC by minimec
Modified: 2007-04-04 22:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description minimec 2007-04-04 14:32:04 UTC 
What were you doing when the application crashed?
tried to open the Application button of gimmie with a beryl running.


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-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
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 (101 sec old) ---------------------
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 856 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
checking for valid crashreport now
checking for valid crashreport now
checking for valid crashreport now
checking for valid crashreport now
checking for valid crashreport now
checking for valid crashreport now
beryl: core: Received winTypeAtom but unable to find the window for the event
  warnings.warn("apt API not stable yet", FutureWarning)
--------------------------------------------------
Traceback (most recent call last):

+ Trace 124944

  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 935 in <lambda> 
    self.scroll.connect("size-request", lambda w, req: self._scroll_get_best_size(w, req))
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 954 in _scroll_get_best_size 
    upper = min(upper, int(self.get_screen().get_height() * 0.7))
TypeError: <lambda>() takes exactly 1 argument (2 given) 






Comment 1


Tony Tsui





          2007-04-04 22:38:20 UTC
        



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 ***