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 475777 - crash in Gimmie: Clicked People and then ...
crash in Gimmie: Clicked People and then ...
Status: RESOLVED DUPLICATE of bug 421620
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-11 09:17 UTC by markus.olausson
Modified: 2007-09-11 20:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description markus.olausson 2007-09-11 09:17:06 UTC 
What were you doing when the application crashed?
Clicked People and then Gmail


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.19.92 2007-09-04 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-11-generic #1 SMP Fri Sep 7 05:07:05 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70000000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaAquaIsh
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 (148 sec old) ---------------------
nvidia_new restricted driver is already enabled
Checking for Xgl: present. \nChecking for nVidia: not present. \nChecking for Xgl: present. \nEnabling Xgl with nVidia drivers...\n/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disa
(gnome-panel:17648): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80f2160
(gnome-panel:17648): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80f2160
(gnome-panel:17648): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80f2160
(gnome-panel:17648): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80f2160
(gnome-panel:17648): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80f2160
(gnome-panel:17648): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80f2160
--------------------------------------------------
Gimmie Version: 0.2.7

Traceback (most recent call last):

+ Trace 162022

  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 636 in _idle_load_items 
    for i in items:
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_base.py", line 249 in get_items 
    for i in self.get_items_uncached():
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_gmail.py", line 201 in get_items_uncached 
    for item in gmail_reader.get_contacts():
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_gmail.py", line 313 in get_contacts 
    self._login()
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_gmail.py", line 250 in _login 
    self.account_settings.do_open()
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_gmail.py", line 163 in do_open 
    self.account_win.show()
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_gmail.py", line 147 in show 
    self._init_account_settings()
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_gmail.py", line 106 in _init_account_settings 
    self.keyring = gnomekeyring.get_default_keyring_sync() NoKeyringDaemonError






Comment 1


Benedikt Henrichs





          2007-09-11 20:21:23 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 421620 ***