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 432244 - crash in Gimmie: I have manually edited a...
crash in Gimmie: I have manually edited a...
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-22 12:54 UTC by c.schnober
Modified: 2007-04-22 22:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description c.schnober 2007-04-22 12:54:15 UTC 
What were you doing when the application crashed?
I have manually edited a the name of a custom menu entry with the menu editor. Afterwards Gimme crashed. It remains visible in the panel but does not react anymore.


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: 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 (246 sec old) ---------------------
seahorse nautilus module initialized
evolution-alarm-notify-Message: Setting timeout for 47321 1177286400 1177239079
evolution-alarm-notify-Message:  Mon Apr 23 02:00:00 2007
evolution-alarm-notify-Message:  Sun Apr 22 12:51:19 2007
(gnome-panel:5690): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 24
Fenstermanager-Warnung: Ungültiges WM_TRANSIENT_FOR-Fenster 0x137 festgelegt für 0x3a00003 (Initialisi).
Fenstermanager-Warnung: Ungültiges WM_TRANSIENT_FOR-Fenster 0x137 festgelegt für 0x3a00003 (Initialisi).
Fenstermanager-Warnung: Ungültiges WM_TRANSIENT_FOR-Fenster 0x137 festgelegt für 0x3a00003 (Initialisi).
Fenstermanager-Warnung: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000062 (OpenOffice)
Fenstermanager-Warnung: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Fenstermanager-Warnung: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000062 (OpenOffice)
Fenstermanager-Warnung: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Traceback (most recent call last):

+ Trace 129720

  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_util.py", line 865 in _model_changed 
    self.recent_items[recent_item.get_uri()] = recent_item
TypeError: <lambda>() takes exactly 1 argument (2 given) 






Comment 1


Tony Tsui





          2007-04-22 22:20:46 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 ***