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 476041 - crash in Gimmie: trying to add a "New Per...
crash in Gimmie: trying to add a "New Per...
Status: RESOLVED DUPLICATE of bug 418829
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-11 22:54 UTC by beesthorpe_hall
Modified: 2007-09-12 19:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description beesthorpe_hall 2007-09-11 22:54:37 UTC 
What were you doing when the application crashed?
trying to add a "New Person"  


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.1 2007-04-10 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: gnome

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 (790 sec old) ---------------------
alarm-queue.c:1837 (check_midnight_refresh)
alarm-queue.c:1837 (check_midnight_refresh)
alarm-queue.c:1837 (check_midnight_refresh)
alarm-queuechecking for valid crashreport now
checking for valid crashreport now
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3600060 (Flute.xls ); these messages lack timestamps and therefore suck.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x340001f (lake1c.gif); these messages lack timestamps and therefore suck.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x340001f (whittingto); these messages lack timestamps and therefore suck.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3201e53 specified for 0x3208f31 (Saving Mes).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3201e53 specified for 0x320aa1b (Saving Mes).
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1a5 specified for 0x3400003 (Initializi).
** (nautilus:7170): WARNING **: Hit unhandled case 46 (Timeout reached) in fm_report_error_loading_directory
--------------------------------------------------
Traceback (most recent call last):

+ Trace 162212

  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_people.py", line 241 in _add_person 
    if gaim_dbus:
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_util.py", line 1094 in __getattr__ 
    raise dbus.DBusException DBusException






Comment 1


Benedikt Henrichs





          2007-09-12 19:37:08 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 418829 ***