Using Google’s 2-Step authentication
Google's 2-Step authentication is a mechanism to protect your Google accounts by registering access per-computer. Because Geary uses IMAP authentication to access your email, it currently has problems if you have 2-step authentication enabled (see bug #713745).
However, you can configure your account to allow Geary access. Log in to Google with your browser and go to Connected apps & sites. From there, set "Allow less secure apps" to On.
Geary crashes when I run it. What I can do to help the developers?
How do I turn on logging with Geary?
To enable logging, run Geary with the --debug (or -d) command line parameter:
This enables some basic debug output that can be used to track down what Geary is doing.
While debugging mode is active, there are several logging options to log network activity, etc. These options can be listed by running:
Note that the logs may contain personal information like email address and the contents of your messages. Some logging options (such as --log-serializer) dump all information indiscriminantly, including usernames and passwords, so beware when using.
How do I backup Geary mail?
All the mail Geary pulls from your server(s) is stored in ~/.local/share/geary (that is, /home/<username>/.local/share/geary). You should copy or archive that entire directory structure to your backup location.
Why can’t I examine the Geary MessageSearchTable with an SQLite explorer tool (or the sqlite3 command-line app)?
Geary uses SQLite’s full-text search (FTS) feature as well as a Unicode tokenizer and stemmer to improve search performance and results. In order to examine the FTS virtual table, the stemmer/tokenizer must be loaded. Geary is linked with this tokenizer. In order to use the tokenizer/stemmer with another tool or the sqlite3 console program, you must install the tokenizer and load it into memory.
- Run the following from Geary source code directory:
$ cd src/sqlite3-unicodesn $ make $ sudo make install
- With the SQLite command-line application:
$ sqlite3 -cmd '.load unicodesn.sqlext' geary.db
- Check other application's documentation for instructions on loading SQLite extensions at runtime.
The conversation viewer uses WebKit to display an HTML page. To inspect the HTML interactively with WebKit, run Geary with --inspector. Right-click on the conversation viewer to open the WebKit Inspector window.
Customize conversation CSS
You can customize the display of Geary's conversations via CSS. You need to place a custom CSS file at ~/.config/geary/user-message.css. Consult the Geary master CSS file (installed in $(PREFIX)/share/geary/theming/message-viewer.css) when building your custom one to see the various classes and IDs used throughout the conversation. Also use the WebKit Inspector (above) to see how conversations are laid out.
Geary will monitor for changes to your custom CSS file and re-load it when it changes. You should be able to edit it and see the changes immediately in Geary, handy for testing and debugging your CSS.
Custom CSS was added in Geary 0.2.
Building on Ubuntu 12.04 (Precise Pangolin)
The current development version of Geary does not build on Ubuntu 12.04 (Precise Pangolin). Read this page to learn how to upgrade your installation so Geary will build.
How is "Geary" pronounced?
Geary is pronounced with a hard G. It should sound like the word “gear” followed by a long “e” sound.
For an audio example, visit this website