GNOME Bugzilla – Bug 470921
crash in Gimmie: nothing
Last modified: 2007-08-28 12:44:43 UTC
What were you doing when the application crashed? nothing 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-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Tangerine 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 --------------------- ** (gsynaptics-init:5974): WARNING **: Using synclient Unknown parameter CoastingSpeedThreshold Initializing nautilus-open-terminal extension Initializing gnome-mount extension ** Message: <information> Vous êtes connecté au réseau sans fil 'Wireless@SG'. (mail-notification:5972): mail-notification-WARNING **: spouilly@imap.myrealbox.com: impossible de démarrer l'authentification SASL : SASL(-4): no mechanism available: No worthy mechs found (mail-notification:5972): mail-notification-WARNING **: spouilly@imap.myrealbox.com: impossible de démarrer l'authentification SASL : SASL(-4): no mechanism available: No worthy mechs found (mail-notification:5972): mail-notification-WARNING **: spouilly@imap.myrealbox.com: impossible de démarrer l'authentification SASL : SASL(-4): no mechanism available: No worthy mechs found (mail-notification:5972): mail-notification-WARNING **: spouilly@imap.myrealbox.com: impossible de démarrer l'authentification SASL : SASL(-4): no mechanism available: No worthy mechs found current dist not found in meta-release file -------------------------------------------------- Traceback (most recent call last):
+ Trace 158353
acct_doc = parse(self.accounts_path)
from xml.dom import expatbuilder
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 ***