---- Reported by patrick.ohly@intel.com 2010-04-09 05:20:20 +0000 ---- To reproduce: - start sync-ui - run "syncevolution --run --sync-property password=- <some config>" - once the sync-ui pops up it's password dialog, cancel the sync or enter a password Actual: - command line stuck in password prompt Expected: - command line should stop waiting for password input and proceed with displaying the sync result Implementing this may be hard. We would need a means to keep the mainloop running (to handle further InfoRequest signals) while handling keyboard input. A simpler solution would be to accept an empty password, then check if the password was provided by someone else in the meantime, if not, cancel the sync. I find that acceptable. It also fixes the current (minor) problem that entering an empty password proceeds with the sync session, then fails with an authentication error. ---- Additional Comments From patrick.ohly@intel.com 2010-04-09 05:25:59 +0000 ---- Another potential solution would be to delay entering the password input code a bit (a second would be long enough). If some other user interface (like the sync-ui) pops up a dialog, it should notify the daemon, which should notify the command line - if I remember correctly, we have that in our design. Just a thought. Perhaps not such a good idea after all, because of the race condition and because the user might want to enter the password on the command line (likely to have his focus). --- Bug imported by patrick.ohly@gmx.de 2012-07-29 20:36 UTC --- This bug was previously known as _bug_ 616 at https://bugs.meego.com/show_bug.cgi?id=616
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/39.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.