Test Case: 1. Created a state where metadata rescan would re-create the root issue. 2. confirmed that the release client encountered the described behavior on login. 3. Upgraded to the maverick-release package. 4. re-ran the simple file creation script to ensure that metadata would still be in rescan on restart. 5. Restarted, verified that client behavior is now normal in this case. 6. removed client from automatically started applications 7. restarted, verified that client was not started. 8. manually started client, verified that startup and connection occurred correctly.
VERIFICATION DONE. This bug is fixed in the version of packages in maverick-proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/651237 Title: ubuntuone-launch fails to start syncdaemon if dbus call times out -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
