Bugs
Size: 16811
Comment:
|
Size: 18017
Comment: New tomboy problems with oneiric beta.
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
<<TableOfContents(6)>> | <<Include(UbuntuOne/MenuBar)>> ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 1em 0em 0em 0em; padding: 1em;"><<TableOfContents(2)>>|| <<Include(UbuntuOne/Bugs/ReleaseMenu)>> This page lists issues that were identified in Ubuntu One client shipped in '''Ubuntu 10.10 (Maverick Meerkat)''' See also [[UbuntuOne/Status|The Ubuntu One status page]] for fresh info about current problems. |
Line 8: | Line 14: |
* '''357395 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/357395|Not using NetworkManager]]''' - Currently, UbuntuOne requires the use of NetworkManager. Errors related to this will often have "NetworkManager" in either the oauth-login.log or syncdaemon-exceptions.log. But, sometimes, there is no error. Like when a user has NetworkManager installed but is using an alternative connection like a tethered mobile device that uses a different connection manager. * '''462828 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/462828|Capabilities Mismatch error]]''' - While this is an older error, it still affects a number of users, mostly those who have installed Karmic and haven't updated after the install. The client will display a "capabilities mismatch" error. This was done intentionally and updating the client and restarting it fix this issue. * '''467397 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/467397|KeyError: 'ROUND_CEiLiNG' in oauth-login.log]]''' - Look for that error message in oauth-login.log. It is related to a Python Turkish locale bug. A possible workaround is to start syncdaemon from a terminal session with a different locale: LANG=en_US.UTF-8 /usr/lib/ubuntuone-client/ubuntuon-syncdaemon |
|
Line 13: | Line 15: |
* '''488413 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/488413|NoAccessToken: No access token found]]''' - Look for NoAccessToken in the syncdaemon-exception.log file and/or the bug description. | |
Line 15: | Line 16: |
* '''509740 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/509740|Maximum upload speed does not save consistently in client GUI]]''' - Look for a syncdaemon.conf entry (provided by apport in the bug description) similar to the one below (the key being that bandwidth throttling is on = True and one of the limits is set to 0): {{{ [bandwidth_throttling] read_limit = 0 write_limit = 0 on = True}}} * '''461614 - [[https://bugs.launchpad.net/ubuntuone-client/+bug/461614|Connect on start setting does not work]]''' - Look for ''UbuntuOne.Client.Applet DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.'' in the oauth-login.log file. |
* '''576263 - [[https://bugs.edge.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/576263|ubuntuone-preferences - ERROR - Got empty result for devices list.]]''' - Look for this in the u1-prefs.log file. |
Line 26: | Line 21: |
* '''455544 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/455544|Protocol version error]]''' - There are two ways to spot this error. First, the syncdaemon-exceptions.log will have ''ERROR - Protocol version error'' in it. Second, when the bug is reported via apport, the description will include the following: {{{ [bandwidth_throttling] on = True read_limit = -1 write_limit = -1}}} The problem is that setting the bandwidth preferences to the defaults (clicking on the checkboxes and not changing the values) results in the read and write limits to be set to -1. The workaround is to delete the ~/.config/ubuntuone/syncdaemon.conf, restart the client, and don't set the bandwidth settings to the defaults. * '''368626 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/368626|Invalid UTF-8 Characters]]''' - Look for ''UnicodeDecodeError: 'utf8' codec can't decode bytes'' in the syncdaemon-exceptions.log for bugs affected by this issue. * '''490988 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/490988|A lot of MakeDir and MakeFile errors]]''' - Look for a number of repeated ''ERROR - MakeFile'' and ''ERROR - MakeDir'' entries in the syncdaemon-exceptions.log file. These errors appear to be caused by a user switching Ubuntu One users on their computer without cleaning out their ~/Ubuntu One folder and meta data folder (~/.local/share/ubuntuone). |
The files with invalid utf8 names will not be synced and the information about these files will be available in syncdaemon-invalid-names.log. * '''490988 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/490988|A lot of MakeDir and MakeFile errors]]''' - Look for a number of repeated ''ERROR - !MakeFile'' and ''ERROR - !MakeDir'' entries in the syncdaemon-exceptions.log file. These errors appear to be caused by a user switching Ubuntu One users on their computer without cleaning out their ~/Ubuntu One folder and meta data folder (~/.local/share/ubuntuone). * '''480069 - [[https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/480069|AttributeError: WaitForCondition - ubuntuone client not updating to server]]''' - Files won't sync and the following errors will be in the syncdaemon-exceptions.log file: {{{ AttributeError: 'WaitForCondition' object has no attribute 'share_id'}}} * '''ROOT_MISMATCH in syncdaemon.log''' - This normally indicates that there may be two Ubuntu One accounts, one in the local cache and another setup in the keyring. This happens if the user installed Ubuntu One with one account and then sets up the computer again with a different account (but all the old Ubuntu One files in ~/.local/share/ubuntuone are still there under the old account). Working around this: 1. Open Applications->Accessories->Terminal and run: {{{ u1sdtool -q; killall ubuntuone-login ubuntuone-preferences; sudo rm -rf ~/.local/share/ubuntuone rm -rf ~/.cache/ubuntuone rm -rf ~/.config/ubuntuone mv ~/Ubuntu\ One/ ~/Ubuntu\ One_old/ }}} 2. Open Applications->Accessories->Passwords and Encryption Keys, go to the Passwords tab, delete the Ubuntu One and Desktopcouch tokens by right-clicking on them and selecting "Delete" 3. Back in a terminal session, run: {{{ u1sdtool -q; killall ubuntuone-login; u1sdtool -c }}} 4. After doing all this syncing notes with tomboy still won't work until you make tomboy re-authentificate with ubuntuone (see the tomboy section of this page). |
Line 41: | Line 44: |
* '''457147 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/457147|BadTransition: SYS_CONNECTION_MADE]]''' - If the crash occurs after the computer comes out of sleep or hibernate, then this is likely the bug. You can verify this by looking for ''!BadTransition'' followed by ''SYS_CONNECTION_MADE event'' in the syncdaemon-exceptions.log file. * '''458393 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/458393|BadTransition: SYS_SERVER_RESCAN_DONE event]]''' - Look for this in the syncdaemon-exceptions.log file. * '''478653 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/478653|BadTransition: SYS_OAUTH_ERROR]]''' - Look for this in the syncdaemon-exceptions.log file. * '''462055 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/462055|BadTransition: SYS_SET_CAPABILITIES_ERROR]]''' - Look for this in the syncdaemon-exceptions.log file. * '''414371 - [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/414371|IOError: [Errno 13] Permission denied in syncdaemon/file_shelf.py]]''' - Look for ''IOError: [Errno 13] Permission denied'' in the syncdaemon-exceptions.log file. * '''506559 - [[https://bugs.edge.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/506559|Syncdaemon KeyError: Client opens apport whenever I click on the applet]]''' - Look for an entry similar to one like this in the syncdaemon-exceptions.log file: {{{ File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/file_shelf.py", line 124, in _load_pickle raise KeyError(key) KeyError: '617e813d-0891-47b6-b9d4-c5719a4703af'}}} |
* '''517505 - [[https://bugs.launchpad.net/ubuntuone-client/+bug/517505| AttributeError:'MetadataUpgrader' object has no attribute '_upgrade_metadata_6']]''' - Look for this in the syncdaemon-exceptions.log file. Common symptom is crashing when clicking on applet. === Permission-related issues === These are not really bugs in UbuntuOne, though syncdaemon should present a better error message to the user. * '''414371 - [[https://launchpad.net/bugs/414371|IOError: [Errno 13] Permission denied in syncdaemon/file_shelf.py]]''' - Look for ''IOError: [Errno 13] Permission denied'' in the syncdaemon-exceptions.log file. * '''407762 - [[https://launchpad.net/bugs/407762|ubuntuone-syncdaemon maxes out system resources when trying to hash a file with root permissions]]''' Look for "Hasher: hash error [Errno 13] Permission denied" DEBUG messages in syncdaemon.log * '''522030 - [[https://launchpad.net/bugs/522030|Syncdaemon crashes when ~/.local/share/ubuntuone has invalid permissions]]''' - Look for OSError: [Errno 1] Operation not permitted: '/home/$USER/.local/share/ubuntuone/...' in syncdaemon.exceptions.log |
Line 59: | Line 57: |
== Notes (tomboy) == * '''709378 - [[http://pad.lv/709378|Tomboy fails to sync after editing note via web: "String was not recognized as a valid DateTime."]]''' - The server-side is already fixed; see [[https://lists.launchpad.net/ubuntuone-users/msg00717.html|the ubuntuone-users announcement]] for the details. * '''757841 - [[http://pad.lv/757841|Tomboy can use outdated SSO tokens]]'''. The bug report contains the link to the script that copies the SSO token to tomboy gconf. === Making tomboy re-authenticate to the server === If tomboy completely refuses to sync notes with ubuntuone you can try the following: 1. close tomboy 1. open {{{gconf-editor}}} 1. unset the key ''/apps/tomboy/sync/sync_selected_service_addin'' 1. unset all keys in ''/apps/tomboy/sync/ubuntuone'' 1. restart tomboy and tell it (from its preferences menu) that you want to sync notes with ubuntuone. === Tomboy tells that synchronization is not set up even if "ubuntu one" has been selected as sync service === - close tomboy - Make sure you are logged in into ubuntu one e.G. using ubuntuone-control-panel-gtk - start gconf-editor - select the key /apps/tomboy/sync/sync_selected_service_addin - change it's value to the following word: ubuntuone - close gconf-editor - start tomboy - preferences/sync preferences - synchronize now - sync Works. See [[http://bugs.launchpad.net/ubuntu/+source/bindwood/+bug/855257 | Bug #855257]] for details. |
|
Line 61: | Line 81: |
* '''443121 - [[https://bugs.edge.launchpad.net/bindwood/+bug/443121|Firefox freezes/becomes unresponsive when bindwood is installed]]''' - Users who installed bindwood (the Ubuntu One bookmarks sync Firefox plugin) will experience this issue. There is a fix but it has not been released in the Karmic universe repository. == Repeatedly asking for authorization == All the relevant bugs are now duplicates of #437165: * [[https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/437165|UbuntuOne stuck in an endless authentication loop (always changes to «Authentication failed»)]] |
Localhost request name and password for a "bookmarkable user auth" 1. Open the file {{{.local/share/desktop-couch/couchdb.html}}} in your home folder. The "." at the beginning of the name of the directory ".local" indicates that this directory is hidden. If this is a problem when trying to open is open a terminal (Applications/accessoires/Terminal) and type "gedit .local/share/desktop-couch/couchdb.html" 1. Search for a line that looks like the following one (It should be near the end of the file): <a id="there" href="http://XXXXXXXXXX:YYYYYYYYYY@localhost:55849/_utils">take me there straight away from now on</a> (remember to bookmark this page first!)</p> 1. The XXXXXXXXXX now stands for the user name 1. The YYYYYYYYYY stands for the password instead. Seems like this problem can be triggered somehow when trying to use bindwood behind a proxy. See [[http://bugs.launchpad.net/ubuntu/+source/bindwood/+bug/774821 | Bug #774821]] for details. |
Line 69: | Line 90: |
Line 77: | Line 97: |
FIXME: Needs to be updated with SSO info. |
|
Line 103: | Line 126: |
1. Open (or create if it doesn't exist): ~/.config/ubuntuone/syncdaemon.conf 1. Add the following 2 lines to this file and save: <<BR>>[__main__] <<BR>> log_level = DEBUG <<BR>> 1. Restart the Ubuntu One client |
1. Open Applications->Accessories->Terminal and run: echo -e "[logging]\nlevel = DEBUG" > ~/.config/ubuntuone/logging.conf; u1sdtool -q; u1sdtool -c |
Line 122: | Line 142: |
Line 129: | Line 150: |
You can browse through your local couchdb contacts by going to ~/.local/share/desktop-couch/couchdb.html and opening contacts databases. You may search through the contacts using CouchDb Temporary View. For example, to search for the entries that have "John" as the first name, use the following map function: {{{ function(doc) { if (doc.first_name == "John") { emit(null, doc); } } }}} You can explore the properties of the doc object by clicking on any contacts database entry. See [[http://www.freedesktop.org/wiki/Specifications/desktopcouch/contact|contact record description]] for the list of all fields. |
|
Line 130: | Line 161: |
'''This does not work on Maverick and e-addressbook-factory does not seem to be the same. Ideas?''' | |
Line 133: | Line 165: |
1. if /usr/lib/evolution/evolution-data-server-2.28 doesn't exist try /usr/lib/evolution/e-addressbook-factory > ~/evolution_debug.log |
|
Line 136: | Line 170: |
== CouchDB == | == CouchDB/Desktopcouch == === Desktopcouch === [[http://www.freedesktop.org/wiki/Specifications/desktopcouch/Documentation/Troubleshooting]] |
Line 145: | Line 181: |
=== How to kill the client and syncdaemon from a terminal session === Sometimes the Ubuntu One client is not visible to the user when the user needs to quit the client. In this situation, run this command from a terminal session: killall ubuntuone-syncdaemon ubuntuone-client-applet |
=== Turning debug mode on for Ubuntu SSO client (oauth-login.log) === FIXME: DEBUG envvar needs to be set for ubuntuone-sso-login. Is it {{{ killall ubuntu-sso-login env DEBUG=1 /usr/lib/ubuntu-sso-client/ubuntu-sso-login }}} The log will be in ~/.cache/sso/oauth-login.log === How to kill syncdaemon from a terminal session === Run this command from a terminal session: killall ubuntuone-syncdaemon |
Line 151: | Line 196: |
=== Which files are already synced on the local computer? === Run [[http://launchpadlibrarian.net/36063440/u1sdstatus.py|this script]] from [[https://bugs.edge.launchpad.net/ubuntuone-client/+bug/488232|bug 488232]] to show which files are already synced and what files are still present on the local computer only. |
|
Line 162: | Line 210: |
sudo killall ubuntuone-client-applet ubuntuone-syncdaemon | sudo killall ubuntuone-syncdaemon |
Line 164: | Line 212: |
1. Start the Ubuntu One client from the menu as you normally would | 1. Connect Ubuntu One client from Preferences applet or u1sdtool --connect |
Line 169: | Line 217: |
1. Open (or create if it doesn't exist): ~/.config/ubuntuone/syncdaemon.conf 1. Add the following 2 lines to this file and save: {{{ [__main__] log_level = DEBUG }}} |
1. Open Applications->Accessories->Terminal and run: echo -e "[logging]\nlevel = DEBUG" > ~/.config/ubuntuone/logging.conf; u1sdtool -q; u1sdtool -c |
Line 176: | Line 219: |
=== Client can't open a web browser window (URL) === Run this command from a terminal session to see if Ubuntu can properly open URLs: gnome-open https://one.ubuntu.com/ If the command fails, then check the System->Preferences->Preferred Applications and what the browser is set to. |
|
Line 186: | Line 224: |
=== How to install the beta PPA on Karmic === Sometimes users may want to run the beta PPA on Karmic. Examples would be the removal of NetworkManager as a requirement and the NoAccessToken fix. Both of these were fixed in the beta PPA quite a bit before they made (or will make it) into an SRU. The FAQ to point users at for how to use the beta PPA can be found at: https://answers.edge.launchpad.net/ubuntuone-client/+faq/836 |
|
Line 206: | Line 242: |
See '''[[FAQ 836|https://answers.edge.launchpad.net/ubuntuone-client/+faq/836]]''' for steps on how to do this. | See '''[[https://answers.edge.launchpad.net/ubuntuone-client/+faq/836|FAQ 836]]''' for steps on how to do this. |
Line 220: | Line 256: |
=== How to remove the note from the server === See LP:563920 https://bugs.launchpad.net/ubuntuone-servers/+bug/563920/comments/3 |
This page lists issues that were identified in Ubuntu One client shipped in Ubuntu 10.10 (Maverick Meerkat) See also The Ubuntu One status page for fresh info about current problems.
Common (Duplicate) Bugs
Finding bugs that have already been reported before can be difficult for a variety of reasons. The list below is meant to help identify common bugs:
Ubuntu One Won't Connect
There are quite a few reasons Ubuntu One will not connect, so the bugs below are the most common known issues:
387308 - Proxy servers are not supported - Look for [Errno socket error] [Errno 8] _ssl.c:480: EOF occurred in violation of protocol error or other _ssl related errors in oauth-login.log, which indicates the user is behind a proxy server.
479687 - Token was not successfully retrieved: data was Expired timestamp - Look for this in the oauth-login.log file.
576263 - ubuntuone-preferences - ERROR - Got empty result for devices list. - Look for this in the u1-prefs.log file.
Files not syncing
The following bugs cover times where Ubuntu One is not syncing properly or at all.
The files with invalid utf8 names will not be synced and the information about these files will be available in syncdaemon-invalid-names.log.
490988 - A lot of MakeDir and MakeFile errors - Look for a number of repeated ERROR - MakeFile and ERROR - MakeDir entries in the syncdaemon-exceptions.log file. These errors appear to be caused by a user switching Ubuntu One users on their computer without cleaning out their ~/Ubuntu One folder and meta data folder (~/.local/share/ubuntuone).
480069 - AttributeError: WaitForCondition - ubuntuone client not updating to server - Files won't sync and the following errors will be in the syncdaemon-exceptions.log file:
AttributeError: 'WaitForCondition' object has no attribute 'share_id'
ROOT_MISMATCH in syncdaemon.log - This normally indicates that there may be two Ubuntu One accounts, one in the local cache and another setup in the keyring. This happens if the user installed Ubuntu One with one account and then sets up the computer again with a different account (but all the old Ubuntu One files in ~/.local/share/ubuntuone are still there under the old account). Working around this:
Open Applications->Accessories->Terminal and run:
u1sdtool -q; killall ubuntuone-login ubuntuone-preferences; sudo rm -rf ~/.local/share/ubuntuone rm -rf ~/.cache/ubuntuone rm -rf ~/.config/ubuntuone mv ~/Ubuntu\ One/ ~/Ubuntu\ One_old/
Open Applications->Accessories->Passwords and Encryption Keys, go to the Passwords tab, delete the Ubuntu One and Desktopcouch tokens by right-clicking on them and selecting "Delete"
- Back in a terminal session, run:
u1sdtool -q; killall ubuntuone-login; u1sdtool -c
- After doing all this syncing notes with tomboy still won't work until you make tomboy re-authentificate with ubuntuone (see the tomboy section of this page).
Ubuntu One client crashes
The client can crash for a variety of reasons and it's not unusual for the user to not understand why the crash occurred (no meaningful error message). The syncdaemon-exceptions.log is key to verifying these bugs. If there is a syncdaemon-exceptions.log attached to a bug, start there and look at the list below.
517505 - AttributeError:'MetadataUpgrader' object has no attribute '_upgrade_metadata_6' - Look for this in the syncdaemon-exceptions.log file. Common symptom is crashing when clicking on applet.
Permission-related issues
These are not really bugs in UbuntuOne, though syncdaemon should present a better error message to the user.
414371 - IOError: [Errno 13] Permission denied in syncdaemon/file_shelf.py - Look for IOError: [Errno 13] Permission denied in the syncdaemon-exceptions.log file.
407762 - ubuntuone-syncdaemon maxes out system resources when trying to hash a file with root permissions Look for "Hasher: hash error [Errno 13] Permission denied" DEBUG messages in syncdaemon.log
522030 - Syncdaemon crashes when ~/.local/share/ubuntuone has invalid permissions - Look for OSError: [Errno 1] Operation not permitted: '/home/$USER/.local/share/ubuntuone/...' in syncdaemon.exceptions.log
Ubuntu One performance issues
Performance issues are normally categorized in two areas: a user's computer is slowed down as a result of Ubuntu One and syncing files is slow.
407762 - Really high CPU and growing memory usage by syncdaemon - At least one cause is when syncdaemon gets a "permission denied" error when trying to hash a file.
461963 - Slow upload syncing from client - The work to fix the root cause of this issue can be found in bug 485004
Notes (tomboy)
709378 - Tomboy fails to sync after editing note via web: "String was not recognized as a valid DateTime." - The server-side is already fixed; see the ubuntuone-users announcement for the details.
757841 - Tomboy can use outdated SSO tokens. The bug report contains the link to the script that copies the SSO token to tomboy gconf.
Making tomboy re-authenticate to the server
If tomboy completely refuses to sync notes with ubuntuone you can try the following:
- close tomboy
open gconf-editor
unset the key /apps/tomboy/sync/sync_selected_service_addin
unset all keys in /apps/tomboy/sync/ubuntuone
- restart tomboy and tell it (from its preferences menu) that you want to sync notes with ubuntuone.
Tomboy tells that synchronization is not set up even if "ubuntu one" has been selected as sync service
- - close tomboy - Make sure you are logged in into ubuntu one e.G. using ubuntuone-control-panel-gtk - start gconf-editor - select the key /apps/tomboy/sync/sync_selected_service_addin - change it's value to the following word: ubuntuone - close gconf-editor - start tomboy - preferences/sync preferences - synchronize now - sync Works.
See Bug #855257 for details.
Bookmarks (bindwood) issues
Localhost request name and password for a "bookmarkable user auth"
Open the file .local/share/desktop-couch/couchdb.html in your home folder. The "." at the beginning of the name of the directory ".local" indicates that this directory is hidden. If this is a problem when trying to open is open a terminal (Applications/accessoires/Terminal) and type "gedit .local/share/desktop-couch/couchdb.html"
- Search for a line that looks like the following one (It should be near the end of the file):
<a id="there" href="http://XXXXXXXXXX:YYYYYYYYYY@localhost:55849/_utils">take me there straight away from now on</a> (remember to bookmark this page first!)</p>
- The XXXXXXXXXX now stands for the user name
- The YYYYYYYYYY stands for the password instead.
Seems like this problem can be triggered somehow when trying to use bindwood behind a proxy. See Bug #774821 for details.
Procedures and Responses
Files (ubuntuone-client)
Connection problems
First look at the common bugs listed above to see if this is a known issue. If you can't find anything there, then use the response below which provides steps to try to work through the connection issue as well as requests the appropriate log files if the steps don't result in success.
Response
FIXME: Needs to be updated with SSO info.
I'm sorry to hear Ubuntu One isn't working properly for you. Can you try the following and let me know the results?
- Quit the Ubuntu One client
Open Applications->Accessories->Passwords and Encryption Keys
- Click on the arrow next to "Passwords"
- Right-click on the Ubuntu One token and select "Delete"
- Click on the checkbox next to your computer
- Click the "Remove selected computers" button
Open Applications->Internet->Ubuntu One
- A web page should open, prompting you to add your computer to your Ubuntu One account
- Add your computer
You should be connected after you follow these steps. If you are not connected, can you please attach the following files to this bug report?
~/.cache/ubuntuone/log/oauth-login.log
~/.cache/ubuntuone/log/syncdaemon-exceptions.log
Thank you,
Syncing problems (not syncing completely, conflicts, etc.)
First look at the common bugs listed above to see if this is a known issue. If you can't find anything there, then use the response below which provides steps to get the appropriate debug file the developers will need to troubleshoot the issue.
Response
I'm sorry to hear Ubuntu One is not working properly for you. Can you do the following in order to provide us with important details that will help us determine the root cause of this issue?
Open Applications->Accessories->Terminal and run: echo -e "[logging]\nlevel = DEBUG" > ~/.config/ubuntuone/logging.conf; u1sdtool -q; u1sdtool -c
- Copy files into your ~/Ubuntu One folder
- Attach ~/.cache/ubuntuone/log/syncdaemon.log and ~/.cache/ubuntuone/log/syncdaemon-exception.log to this bug report
Note that attaching syncdaemon.log will show filenames you are attempting to sync with Ubuntu One. If you do not want this to be public, please mark the bug as private and this bug report will only be available to you and the Ubuntu One team.
Thank you,
Troubleshooting/Debugging Tips
Account Related
How to change the email address associated with your Ubuntu One account
Please see FAQ #810 which gives the steps. If these steps need to change, well change them in the FAQ.
Contacts
First of all, make sure that evolution-couchdb package is installed, the visible presence of Ubuntu One address book is not enough: Ghost CouchDB addressbook after evolution-couchdb removal
$ apt-cache policy evolution-couchdb evolution-couchdb: Installed: 0.3.4-0ubuntu2
You can browse through your local couchdb contacts by going to ~/.local/share/desktop-couch/couchdb.html and opening contacts databases. You may search through the contacts using CouchDb Temporary View. For example, to search for the entries that have "John" as the first name, use the following map function:
function(doc) { if (doc.first_name == "John") { emit(null, doc); } }
You can explore the properties of the doc object by clicking on any contacts database entry. See contact record description for the list of all fields.
Getting debug info
This does not work on Maverick and e-addressbook-factory does not seem to be the same. Ideas?
Applications->Accessories->Terminal, and run:
- evolution --force-shutdown
/usr/lib/evolution/evolution-data-server-2.28 > ~/evolution_debug.log
- evolution --force-shutdown
- if /usr/lib/evolution/evolution-data-server-2.28 doesn't exist try
/usr/lib/evolution/e-addressbook-factory > ~/evolution_debug.log
Applications->Internet->Evolution Mail
- Try to reproduce bug and then attach ~/evolution_debug.log to a bug report
CouchDB/Desktopcouch
Desktopcouch
http://www.freedesktop.org/wiki/Specifications/desktopcouch/Documentation/Troubleshooting
Debug log for CouchDB syncing
~/.cache/desktop-couch/log/desktop-couch-replication.log This likely has some private information so if you request it to be attached to a bug, please let the user know about this and state something like:
Note that attaching desktop-couch-replication.log will show information about what you are attempting to sync with Ubuntu One. If you do not want this to be public, please mark the bug as private and this bug report will only be available to you and the Ubuntu One team.
Files (Ubuntu One client & syncdaemon)
Turning debug mode on for Ubuntu SSO client (oauth-login.log)
FIXME: DEBUG envvar needs to be set for ubuntuone-sso-login. Is it
killall ubuntu-sso-login env DEBUG=1 /usr/lib/ubuntu-sso-client/ubuntu-sso-login
The log will be in ~/.cache/sso/oauth-login.log
How to kill syncdaemon from a terminal session
Run this command from a terminal session: killall ubuntuone-syncdaemon
Is Ubuntu One syncing files?
One way to check this is from a terminal session: u1sdtool --current-transfers
Which files are already synced on the local computer?
Run this script from bug 488232 to show which files are already synced and what files are still present on the local computer only.
Running syncdaemon in debug mode
DEBUG mode is often necessary for sync related issues. Think of times where files don't appear to sync correctly (incomplete, unexpected .u1conflict files, etc.) This will generate a more detailed (and bigger in size) ~/.cache/ubuntuone/log/syncdaemon.log
If you need to request the syncdaemon.log file, please use some wording like this in the request:
Note that attaching syncdaemon.log will show filenames you are attempting to sync with Ubuntu One. If you do not want this to be public, please mark the bug as private and this bug report will only be available to you and the Ubuntu One team.
Temporary debug mode
When you don't want debug mode on all the time, use this method:
Applications->Accessories->Terminal, and run:
- sudo killall ubuntuone-syncdaemon
/usr/lib/ubuntuone-client/ubuntuone-syncdaemon --debug > ~/syncdaemon-debug.log
- sudo killall ubuntuone-syncdaemon
- Connect Ubuntu One client from Preferences applet or u1sdtool --connect
Permanent debug mode
If you want to keep the syncdaemon in debug mode all the time, then use this method:
Open Applications->Accessories->Terminal and run: echo -e "[logging]\nlevel = DEBUG" > ~/.config/ubuntuone/logging.conf; u1sdtool -q; u1sdtool -c
- Restart the Ubuntu One client
How to completely remove and reinstall the client
Please see FAQ #778 which gives the steps. If these steps need to change, we'll change them in the FAQ.
General
What version of Ubuntu One is installed?
From a terminal session: sudo apt-cache policy package-name-goes-here Output will show what version is installed, which versions are available.
Requesting apport info for an Ubuntu One project bug
Sometimes users file a bug without any debug information that normally comes from apport. The following is the command the user needs to run in a terminal session to send this information (replace XXXXXX with the appropriate bug number): apport-collect -p ubuntuone-client XXXXXX
Fixing Launchpad permissions for Apport
Some users will be requested to send more information via apport. If they haven't used apport before, they have to give apport permission on Launchpad to change anything on their behalf. Sometimes users get confused and select the wrong permission and will receive a (401) error when they run apport. In order to fix this (replace XXXXXX with the appropriate bug number):
Applications->Accessories->Terminal, and run:
- rm ~/.cache/apport/launchpad.credentials apport-collect -p ubuntuone-client XXXXXX
- When prompted in your web browser, click the "Change Anything" button (the last one in the list)
- Go back to your terminal session and press "Enter"
Updating from the Ubuntu One Karmic package to the PPA
See FAQ 836 for steps on how to do this.
Notes (Tomboy)
Getting debug info
- Quit Tomboy
Applications->Accessories->Terminal, and run:
tomboy --debug > ~/tomboy_debug.log
- Try to reproduce the bug and then attach ~/tomboy_debug.log to a bug report
If you're requesting this log to be attached to a bug, you should provide this notice to the user:
Note that attaching the Tomboy debug log will show information about what you are attempting to sync with Ubuntu One. If you do not want this to be public, please mark the bug as private and this bug report will only be available to you and the Ubuntu One team.
How to remove the note from the server
See 563920 https://bugs.launchpad.net/ubuntuone-servers/+bug/563920/comments/3