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 447353 - crash in Gimmie: Opening a .ini file with...
crash in Gimmie: Opening a .ini file with...
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-06-13 23:16 UTC by David Graham
Modified: 2007-06-23 17:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description David Graham 2007-06-13 23:16:36 UTC 
What were you doing when the application crashed?
Opening a .ini file with Gnome text editor


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-386 #2 Thu Jun 7 20:16:13 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Outdoors
Icon Theme: glass-icons

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 (58 sec old) ---------------------
** Message: Failed to close thumbnail pixbuf loader for /home/david/.amsn/alchemystik_hotmail_com/displaypic/cache/46a44505b69453a6248536353367833744677313658635a5c42776d3.png: Unrecognised image file
** Message: Failed to close thumbnail pixbuf loader for /home/david/.amsn/alchemystik_hotmail_com/displaypic/cache/0305a7a44714475444f68387435485e6059646f4c6171447f6e603d3.png: Unrecognised image file
** Message: Failed to close thumbnail pixbuf loader for /home/david/.amsn/alchemystik_hotmail_com/displaypic/cache/46a44505b69453a6248536353367833744677313658635a5c42776d3.png: Unrecognised image file
** Message: Failed to close thumbnail pixbuf loader for /home/david/.amsn/alchemystik_hotmail_com/displaypic/cache/0305a7a44714475444f68387435485e6059646f4c6171447f6e603d3.png: Unrecognised image file
** Message: Failed to close thumbnail pixbuf loader for /home/david/.amsn/alchemystik_hotmail_com/displaypic/cache/46a44505b69453a6248536353367833744677313658635a5c42776d3.png: Unrecognised image file
** Message: Failed to close thumbnail pixbuf loader for /home/david/.amsn/alchemystik_hotmail_com/displaypic/cache/0305a7a44714475444f68387435485e6059646f4c6171447f6e603d3.png: Unrecognised image file
** Message: Failed to close thumbnail pixbuf loader for /home/david/.amsn/alchemystik_hotmail_com/displaypic/cache/46a44505b69453a6248536353367833744677313658635a5c42776d3.png: Unrecognised image file
** Message: Failed to close thumbnail pixbuf loader for /home/david/.amsn/alchemystik_hotmail_com/displaypic/cache/0305a7a44714475444f68387435485e6059646f4c6171447f6e603d3.png: Unrecognised image file
** Message: Failed to close thumbnail pixbuf loader for /home/david/.amsn/alchemystik_hotmail_com/displaypic/cache/46a44505b69453a6248536353367833744677313658635a5c42776d3.png: Unrecognised image file
No whitepoint found
No whitepoint found
sox: Can't open output file '/dev/dsp': Device or resource busy
** (update-notifier:17403): WARNING **: no cdrom: disk
--------------------------------------------------
Traceback (most recent call last):

+ Trace 140806

  • File "/usr/local/lib/python2.4/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


Pedro Villavicencio





          2007-06-23 17:28:04 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 ***