Ubuntu One Client

ubuntuone told me it crashed

Bug #417005 reported by Mark Shuttleworth on 2009-08-21

This bug report is a duplicate of: Bug #420354: BadTransition in ubuntuone-syncdaemon. Edit Remove

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu One Client	Triaged	High	John Lenton

Bug Description

Hard to tell if this is a dup, I just got the crash indicator in the panel.

ProblemType: Bug
Architecture: i386
CrashDB: ubuntuone
Date: Fri Aug 21 16:18:32 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 0.92.0+r163-0ubuntu1~ppa1~karmic
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
SourcePackage: ubuntuone-client
ThirdParty: True
Uname: Linux 2.6.31-6-generic i686

Tags:

Revision history for this message

Mark Shuttleworth (sabdfl) wrote on 2009-08-21:

.home.mark..cache.ubuntuone.log.oauth.login.log.txt Edit (121.1 KiB, text/plain; charset="utf-8")
.home.mark..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (940 bytes, text/plain; charset="utf-8")
.home.mark..cache.ubuntuone.log.syncdaemon.log.txt Edit (16.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.8 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (278 bytes, text/plain; charset="utf-8")

Revision history for this message

John Lenton (chipaca) wrote on 2009-08-21: Re: [Bug 417005] [NEW] ubuntuone told me it crashed

On Fri, Aug 21, 2009 at 04:00:23PM -0000, Mark Shuttleworth wrote:
> Public bug reported:
>
> Hard to tell if this is a dup, I just got the crash indicator in the
> panel.

I think it's a dupe; you're getting an oauth error (not sure why). The
strange thing is that the syncdaemon should restart when it gets into
that state ("UNKNOWN_ERROR"), but it's not. I've got to hunt that down.

Meanwhile, you can try restarting the syncdaemon manually (quitting
and restaring the applet should do that).

Please let me know how it goes.

Rick McBride (rmcbride) on 2009-08-21

Changed in ubuntuone-client:
status:	New → Triaged
importance:	Undecided → High
assignee:	nobody → John Lenton (chipaca)

Revision history for this message

Rick McBride (rmcbride) wrote on 2009-08-21:

Yea this is definitely not a dupe of some of the other "Crash indicator" reports we've had recently. I haven't seen that oauth UNKNOWN_ERROR issue in any of those cases, including the one I was able to reproduce on one out of three test systems on the same account.

Changing to Critical.