kdeinit4 crashed with TypeError in readAccountData()

Bug #468402 reported by bauerj
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)
New
Undecided
Unassigned

Bug Description

All programs crashed after starting SoftwareCenter.

ProblemType: Crash
Architecture: i386
Date: Sun Nov 1 12:52:31 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
Package: kdelibs-bin 4:4.3.2-0ubuntu7
ProcCmdline: kdeinit4:\ plasma-desktop\ [kdeinit]
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: kde4libs
Title: kdeinit4 crashed with TypeError in readAccountData()
Traceback:
 Traceback (most recent call last):
   File "/home/username/.kde/share/apps/plasma/plasmoids/gmail-plasmoid/contents/code/main.py", line 473, in readAccountData
     message = "<table><tr><td><b>"+i18n("From")+"</b>: </td><td>"+newentries[0]["authorname"]+"</td></tr><tr><td><b>"+i18n("Subject")+"</b>: </td><td>"+newentries[0]["subject"]+"</td></tr></table>"
 TypeError: unsupported operand type(s) for +: 'QString' and 'unicode'
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:5391): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #465189, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.