Ubuntu
ubuntuone-client package

ubuntu one crashed on successive connecting and disconnecting action

Bug #521052 reported by Uttam Pal on 2010-02-12

This bug report is a duplicate of: Bug #457147: BadTransition: SYS_CONNECTION_MADE - Ubuntu One crashes coming out of sleep/hibernate. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ubuntuone-client (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: ubuntuone-client

ubuntu one was creating problem since i've switched to Kubuntu desktop. it started asking for password on every boot, which is very annoying. moreover i could not remove this from startup programs on KDE.

ProblemType: Bug
.home.uttam..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = False
connect = 0
show_applet = 1
bookmarked = True
Architecture: i386
Date: Fri Feb 12 21:32:05 2010
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-19-generic i686
XsessionErrors:
(polkit-gnome-authentication-agent-1:1550): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(firefox:1883): GLib-WARNING **: g_set_prgname() called multiple times

Tags:

Revision history for this message

Uttam Pal (uttam2707) wrote on 2010-02-12:

.home.uttam..cache.ubuntuone.log.oauth.login.log.txt Edit (5.6 KiB, text/plain; charset="utf-8")
.home.uttam..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (493 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.9 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")

Revision history for this message

Mitch Towner (kermiac) wrote on 2010-02-13:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 457147, so it 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.