[opensuse-kde] KMail2 and related things
Hi all; First of all I myself have been testing KMail2 for long before shipping it as an update, until the 4.7 release day we have been having random problems related to Akonadi, so we decided to switch Akonadi to use SQLite backend instead of MySQL. This resulted in an actually working KMail2. Now, some of you are pissed asking why we switched to SQLite without discussing it, the reason was that MySQL backend simply didn't work for us and we faced a tough decision, either we were going to ship something that doesn't even work on our development machines or ship with SQLite backend accept that some Akonadi operations can block the Graphical User Interface (eg. kmail). I couldn't ship a known-to-be broken software with a straight face, so I changed akonadi to use SQLite backend, which btw Fedora is now defaulting (they did before us). Please don't feel personal about this, this is not about listening to community, discussing with the community. This is about not shipping with known-broken software. I hope this clears up some confusion. Sent from my KMail2. -- İsmail Dönmez - openSUSE Booster SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Freitag 29 Juli 2011 13:53:43 İsmail Dönmez wrote:
First of all I myself have been testing KMail2 for long before shipping it as an update, until the 4.7 release day we have been having random problems related to Akonadi, so we decided to switch Akonadi to use SQLite backend instead of MySQL.
So why is akonaditray only letting me switch between MySQL and PostgreSQL? And why is myseqld still running here? If SQLite is indeed used as Akonadi back-end, I don't see it on my install (from KR47). -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Hi; On Friday, July 29, 2011 03:49:17 PM Markus Slopianka wrote:
On Freitag 29 Juli 2011 13:53:43 İsmail Dönmez wrote:
First of all I myself have been testing KMail2 for long before shipping it as an update, until the 4.7 release day we have been having random problems related to Akonadi, so we decided to switch Akonadi to use SQLite backend instead of MySQL.
So why is akonaditray only letting me switch between MySQL and PostgreSQL? And why is myseqld still running here? If SQLite is indeed used as Akonadi back-end, I don't see it on my install (from KR47).
Your default akonadiserverrc is not overwritten, so SQLite backend is only used for new configs. Regards. -- İsmail Dönmez - openSUSE Booster SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Friday, July 29, 2011 03:56:52 PM İsmail Dönmez wrote:
Hi;
On Friday, July 29, 2011 03:49:17 PM Markus Slopianka wrote:
On Freitag 29 Juli 2011 13:53:43 İsmail Dönmez wrote:
First of all I myself have been testing KMail2 for long before shipping it as an update, until the 4.7 release day we have been having random problems related to Akonadi, so we decided to switch Akonadi to use SQLite backend instead of MySQL.
So why is akonaditray only letting me switch between MySQL and PostgreSQL? And why is myseqld still running here? If SQLite is indeed used as Akonadi back-end, I don't see it on my install (from KR47).
Your default akonadiserverrc is not overwritten, so SQLite backend is only used for new configs.
So, how can we switch from MySQL to SQLite if - as Markus writes - akonaditray does not allow it? Andreas -- Andreas Jaeger, Program Manager openSUSE aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Friday, July 29, 2011 04:02:10 PM Andreas Jaeger wrote:
On Friday, July 29, 2011 03:56:52 PM İsmail Dönmez wrote:
Hi;
On Friday, July 29, 2011 03:49:17 PM Markus Slopianka wrote:
On Freitag 29 Juli 2011 13:53:43 İsmail Dönmez wrote:
First of all I myself have been testing KMail2 for long before shipping it as an update, until the 4.7 release day we have been having random problems related to Akonadi, so we decided to switch Akonadi to use SQLite backend instead of MySQL.
So why is akonaditray only letting me switch between MySQL and PostgreSQL? And why is myseqld still running here? If SQLite is indeed used as Akonadi back-end, I don't see it on my install (from KR47).
Your default akonadiserverrc is not overwritten, so SQLite backend is only used for new configs.
So, how can we switch from MySQL to SQLite if - as Markus writes - akonaditray does not allow it?
You could do that by setting it in ~/.config/akonadi/akonadiserverrc [%General] Driver=QSQLITE3 -- İsmail Dönmez - openSUSE Booster SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Friday, July 29, 2011 04:22:12 PM İsmail Dönmez wrote:
On Friday, July 29, 2011 04:02:10 PM Andreas Jaeger wrote:
[...] So, how can we switch from MySQL to SQLite if - as Markus writes - akonaditray does not allow it?
You could do that by setting it in ~/.config/akonadi/akonadiserverrc
[%General] Driver=QSQLITE3
thanks! And just changing backends works - or will I loose all my data? Andreas -- Andreas Jaeger, Program Manager openSUSE aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Friday, July 29, 2011 04:56:42 PM Andreas Jaeger wrote:
On Friday, July 29, 2011 04:22:12 PM İsmail Dönmez wrote:
On Friday, July 29, 2011 04:02:10 PM Andreas Jaeger wrote:
[...] So, how can we switch from MySQL to SQLite if - as Markus writes - akonaditray does not allow it?
You could do that by setting it in ~/.config/akonadi/akonadiserverrc
[%General] Driver=QSQLITE3
thanks!
And just changing backends works - or will I loose all my data?
You shouldn't be losing any data (I am switching between MySQL/SQLite here for testing) but just in case, database data stays in .local/share/akonadi , you can backup that directory. Regards. -- İsmail Dönmez - openSUSE Booster SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Could you please write a small patch to set SQLite via akonaditray as well? SQLite is a non-localizeable product name, so no string freeze would be broken. While I personally have no problems editing config files, normal users have. And considering that there is not even a drop-down item in akonaditray, accidentally clicking wrong could mean that some user may switch from SQLite to MySQL without any idea to switch back. On Freitag 29 Juli 2011 16:59:53 İsmail Dönmez wrote:
On Friday, July 29, 2011 04:56:42 PM Andreas Jaeger wrote:
On Friday, July 29, 2011 04:22:12 PM İsmail Dönmez wrote:
On Friday, July 29, 2011 04:02:10 PM Andreas Jaeger wrote:
[...] So, how can we switch from MySQL to SQLite if - as Markus writes - akonaditray does not allow it?
You could do that by setting it in ~/.config/akonadi/akonadiserverrc
[%General] Driver=QSQLITE3
thanks!
And just changing backends works - or will I loose all my data?
You shouldn't be losing any data (I am switching between MySQL/SQLite here for testing) but just in case, database data stays in .local/share/akonadi , you can backup that directory.
Regards. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
A few notes and comments. First, I cannot even imagine how much has gone into KDE 4.7. Overwhelmingly, it's a nice improvement over 4.6 and by and large things work really well! Everyone involved should feel proud of the work they have done! With that said, I have encountered some issues. Please do not take this as complaint! Most of my problems seem to deal with nepomuk / akonadi / kmail2. Even after wiping out ~/.local/share/akonadi entirely, and starting over, I had problems. I moved to PostgreSQL (with standard_confirming_strings *on*) and that seemed to go quite well. I had to totally wipe out my kmail settings and such in ~/.kde4/share/kmail*, but once I did that I could at least start kmail (otherwise, it would grump about invalid resources and exit - not very graceful!) One I got kmail up and configured, it brought down my gmail account over IMAP very quickly. More quickly than any other email client I've ever used. Very impressive! However, due to some error (akonadiconsole told me it had to due with trying to select [Gmail] *as a folder*) I couldn't read a mail or do anything, and eventually kmail2 just froze and needed a hard kill -9. So I logged out, logged in via console, and removed the akonadi and kmail configs, again. The next time I logged in, akonadiconsole wouldn't even start -- I'd get a blank dialog and a beep, and nothing akonadi worked at all. Also, not very graceful. A few log outs and log ins later, akonadiconsole worked again. I shut down the server, changed to sqlite (manually, as the config dialog doesn't offer that option) and now things look OK again. kmail2 starts up, I configure my account, and it synchronizes quickly! Wait! Now I have 2 copies of every email. sigh. It looks like kmail / akonadi are *close* but not yet there. The [Gmail] folder issue has been reported on before - I hope it can be fixed soon. The double email thing is new to me. The not-starting-up-at-all thing is also strange, and should be looked into. The inability to configure sqlite in akonadiconsole is an issue, too, especially if it is to be a/the default going forward. "standard_supporting_strings on" needs to be used in each session for the PostgreSQL driver (which should be trivial and would avoid having to have each person manually configure a system-wide param just for akonadi), and so on. The fragility surrounding kmail and akonadi integration, especially with respect to "invalid resources" is a major bummer, and I hope it's improved soon. The lack of google calendar support is a big bummer, too. Using evolution (which is memory efficient, worked the first time, supports google calendars and google contacts *out of the box*) should be considered at least a benchmark to strive for. It's true that evolution was glacially slow syncing compared to kmail, but evolution actually works for me every time I use it - and does more to boot. With respect to nepomuk - I find it frustating that I am reminded *every time I log in* that file indexing is shut off. I know it's shut off. I shut if off! Lastly, *every* time I start kmail does it have to bring up the wizard? What's with that? -- Jon -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Freitag, 29. Juli 2011, 13:53:43 schrieb İsmail Dönmez:
I couldn't ship a known-to-be broken software with a straight face, so I changed akonadi to use SQLite backend, which btw Fedora is now defaulting (they did before us).
So if akonadi is slow it's probably due to using sqlite – I hope users mention their backend when reporting bugs otherwise this will lead to lots of lost time upstream. I'm still searching but I read that sqlite was dumped for a reason, I think locking issues while writing to the db. Were those resolved or did you just assume that sqlite and mysql would fit equally well? Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Sonntag, 31. Juli 2011, 16:41:03 schrieb Sven Burmeister:
I'm still searching but I read that sqlite was dumped for a reason, I think locking issues while writing to the db. Were those resolved or did you just assume that sqlite and mysql would fit equally well?
Found it: http://techbase.kde.org/Projects/PIM/Akonadi/Database#Sqlite "Mutex-based transaction serialization in Akonadi (required due to lack of concurrency support in Sqlite) can block clients while background operations such as a IMAP sync are going on. This is the real killer here, the more clients (including background processes like indexing) are accessing the data, the more blocking you experience. " Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Sun, Jul 31, 2011 at 9:41 AM, Sven Burmeister
Am Freitag, 29. Juli 2011, 13:53:43 schrieb İsmail Dönmez:
I couldn't ship a known-to-be broken software with a straight face, so I changed akonadi to use SQLite backend, which btw Fedora is now defaulting (they did before us).
So if akonadi is slow it's probably due to using sqlite – I hope users mention their backend when reporting bugs otherwise this will lead to lots of lost time upstream.
I'm still searching but I read that sqlite was dumped for a reason, I think locking issues while writing to the db. Were those resolved or did you just assume that sqlite and mysql would fit equally well?
I went back and tried postgresql (with standard_confirming_strings = on) and performance was rather better than sqlite for my two large IMAP mailboxes. I also tried sqlite which worked fine but HAMMERED my system while it synchronized some 100,000 emails. I should look at /how/ sql is being used, though, as it looked like there were some inefficiencies. -- Jon -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (5)
-
Andreas Jaeger -
İsmail Dönmez -
Jon Nelson -
Markus Slopianka -
Sven Burmeister