After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 723281 - messages are never sent
messages are never sent
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: outbox
master
Other Linux
: Normal critical
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-01-30 13:18 UTC by Adam Dingle
Modified: 2014-01-30 18:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Adam Dingle 2014-01-30 13:18:39 UTC
With the latest master, if I send a message it appears to work (the message is not visible in my Outbox) but the message is never sent: it doesn't show up in Sent Mail in Gmail.

If I run 'geary --debug', the console shows errors like these:

 [deb] 08:16:32 0.000076 db-connection.vala:351: Connection.exec_transaction: transaction threw error: (Statement.ctor /home/adam/.local/share/geary/adam@ongoing.ly/geary.db) [err=1] - no such column: sent (
                    SELECT id, ordering, message, sent
                    FROM SmtpOutboxTable
                    ORDER BY ordering DESC
                    LIMIT ?
                )

 [deb] 08:16:32 0.000067 app-conversation-monitor.vala:462: Error while assembling conversations in Gmail:adam@ongoing.ly:$GearyOutbox$: (Statement.ctor /home/adam/.local/share/geary/adam@ongoing.ly/geary.db) [err=1] - no such column: sent (
                    SELECT id, ordering, message, sent
                    FROM SmtpOutboxTable
                    ORDER BY ordering DESC
                    LIMIT ?
                )
Comment 1 Adam Dingle 2014-01-30 13:28:09 UTC
From the message above I thought this might be a database schema upgrade problem, so I deleted my Geary directory (/home/adam/.local/share/geary), ran Geary again and recreated my mail account.  But this problem is still occurring.
Comment 2 Charles Lindsay 2014-01-30 18:40:15 UTC
Looks like once again I forgot to add the new SQL file to the list of installed files.

This should be fixed as of 6631ed9.  Can you try again?
Comment 3 Adam Dingle 2014-01-30 18:48:36 UTC
Working fine now.  Thanks for the quick fix!
Comment 4 Charles Lindsay 2014-01-30 18:54:28 UTC
Great, glad to hear it.  Thanks for testing the install path, which as you can tell I rarely do!  :)