GNOME Bugzilla – Bug 743839
Better user error message when keyring doesn't open (was: Unable to open local mailbox)
Last modified: 2017-10-30 21:31:38 UTC
When I open Geary v0.8.3, I get the following message: --------- Unable to open local mailbox for charles.goodwin@gmail.com There was an error opening the local account. This is probably due to connectivity issues. Please check your network connection and restart Geary. --------- In case it isn't obvious, I am connected to the Internet (hence able to post this bug report). I believe the first time this message was displayed, it was correct (I was not connected to my wireless network at home). However, I immediately connected but the message still shows whenever I try to start Geary. I put it as a 'blocker' because this renders Geary inoperable. The dialog has one option (the OK button) and pressing this closes Geary.
Please run Geary like this from the console: $ geary > geary.log and reproduce the problem. Then attach that file to this ticket. (It may contain sensitive or private information, please redact first before posting.)
charles@charles-mint-Z500 ~ $ geary No bp log location saved, using default. [000:000] Cpu: 6.58.9, x4, 2601Mhz, 3814MB [000:000] Computer model: Not available [000:000] Browser XEmbed support present: 1 [000:000] Browser toolkit is Gtk2. [000:002] Using Gtk2 toolkit No bp log location saved, using default. [000:000] Cpu: 6.58.9, x4, 2601Mhz, 3814MB [000:000] Computer model: Not available [000:015] Warning(optionsfile.cc:30): Load: Could not open file, err=2 [000:015] No bp log location saved, using default. [000:016] Cpu: 6.58.9, x4, 2601Mhz, 3814MB [000:016] Computer model: Not available [000:016] Browser XEmbed support present: 1 [000:016] Browser toolkit is Gtk2. [000:016] Using Gtk2 toolkit [000:013] Warning(optionsfile.cc:30): Load: Could not open file, err=2 [000:013] No bp log location saved, using default. [000:013] Cpu: 6.58.9, x4, 2601Mhz, 3814MB [000:013] Computer model: Not available java version "1.7.0_75" OpenJDK Runtime Environment (IcedTea 2.5.4) (7u75-2.5.4-1~trusty1) OpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode) That's it. It exits at that point. Your command (geary > geary.log) produced an empty file, so I assumed this console output is what you were after.
My error. What I should have asked for is: $ geary --debug > geary.log
Created attachment 295989 [details] Log file as requested
Do you have libsecret installed? You need to have libsecret and a compatible keyring manager installed for Geary to operate.
Yes, libsecret is installed. Both ubuntu-keyring and linuxmint-keyring are installed. I'm on Mint 17.1 Rebecca.
These lines in the log: [msg] 01:19:20 0.005943 Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files [deb] 01:19:20 0.000172 geary-controller.vala:995: Unable to open account Gmail:charles.goodwin@gmail.com: The name org.freedesktop.secrets was not provided by any .service files tell me that either it's not installed properly or somehow stopped running. I'm also unsure if you can have both keyrings installed at the same time. Can you run Seahorse? You might try reinstalling libsecret and the keyrings. You shouldn't lose your data doing that.
I did not have seahorse installed (!) and installing it enables Geary to run again. Geary did run fine the first time. It was only after I rebooted that this error came about. I humbly suggest the solution to this issue (if you think it needs solving) is to detect whether a password was successfully saved via the running keyring.
Forgot to add: thanks for the prompt response and help. :)
We've had a couple of people with keyring problems, we could do a better job with the error message. I'm re-titling this ticket to reflect that.
According to Bug 772721 and https://forums.freebsd.org/threads/50155/, 0.9 was crashing if this was the case. We want to make sure that doesn't happen, either.
The crash was taken care of in Bug 776139, and there's some ongoing discussion about notification of the error over there - so closing this in favour of that bug. *** This bug has been marked as a duplicate of bug 776139 ***