Binary package hint: ubuntuone-client
Ubuntu 11.04 alfa 3, doesn't open a house folder
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.5.5-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
NonfreeKernelModules: wl
Architecture: i386
CheckboxSubmission: 1eea7edbf25d212412b0947c7956b255
CheckboxSystem: 21aa6c17e1fc79cc65eed2169d1b6afc
Date: Tue Mar 8 14:17:02 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANGUAGE=ru_RU:en
LANG=ru_RU.UTF-8
PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-syncdaemon']
SourcePackage: ubuntuone-client
Title: ubuntuone-syncdaemon crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
UbuntuOnePreferencesLog:
2011-02-17 00:31:58,292 - ubuntuone-preferences - INFO - Starting Ubuntu One Preferences
2011-02-17 00:33:05,500 - ubuntuone-preferences - INFO - Got credentials for Ubuntu One
2011-02-17 00:33:52,144 - ubuntuone-preferences - INFO - Got credentials for Ubuntu One
2011-02-21 11:45:58,534 - ubuntuone-preferences - INFO - Starting Ubuntu One Preferences
2011-02-21 11:46:04,356 - ubuntuone-preferences - INFO - Got credentials for Ubuntu One
UbuntuOneSyncdaemonExceptionsLog:
UbuntuOneUserSyncdaemonConfig:
[bandwidth_throttling]
read_limit = 2097152
write_limit = 2097152
on = False
UpgradeStatus: Upgraded to natty on 2011-03-05 (2 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
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 #711221, 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.