ubuntu one crash on startup (after upgrade from 9.04 to 9.10 / wubi ubuntu)

Bug #441159 reported by RichardN on 2009-10-03
This bug report is a duplicate of:  Bug #441039: Ubuntu One crashed on launch. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: ubuntuone-client

The applet crashes in save_config() when started from the gnome menu (system->preferences).
Firefox 3.5 is already running.

When starting ubuntuone-client-applet (0.96.0-0ubuntu1)
 from a command prompt it seems to work fine. A new tab is opened in firefox and I have to authenticate with my launchpad id.

(
Upgraded ubuntu 9.04 to 9.10 (development branch). Running ubuntu in virtual disk (wubi).

)

ProblemType: Crash
Architecture: amd64
Date: Sat Oct 3 10:02:51 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/ubuntuone-client-preferences
InterpreterPath: /usr/bin/python2.6
Package: ubuntuone-client-gnome 0.96.0-0ubuntu1
ProcCmdline: /usr/bin/python /usr/bin/hostnameone-client-preferences
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
PythonArgs: ['/usr/bin/hostnameone-client-preferences']
SourcePackage: ubuntuone-client
Title: ubuntuone-client-preferences crashed with IOError in save_config()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1709): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1709): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1755): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1784): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

RichardN (ricnmn) wrote :

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 #441039, 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  Edit
Everyone can see this information.

Other bug subscribers