Bug 12055

Summary: akonadi doesn't work after starting kde (nvidia)
Product: Mageia Reporter: Florian Bauer <alfaflo>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: balcaen.john, doktor5000, ennael1, lmenut, mageia
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Bug Depends on:    
Bug Blocks: 12079    
Attachments: akonadi after starting kde
failure report of system settings
akonadi works after starting manually with "akonadictrl start"
Log/output of akonadi test
akonadi test output

Description Florian Bauer 2013-12-19 19:02:25 CET
Description of problem:
After booting and starting KDE, Akonadi doesn't work.
In process list I can see 3 processes related to akonadi:
akonadi_ctrl
akonadiserver
mysqld

KDE systemsettings show that akonadi doesn't run.
If I press "start", I get a failure that akonadi control isn't registered to dbus (see screenshots attached).

When I "kill" the 3 akonadi processes above and start again Akonadi by "akonadictrl start" it works fine (see result attached as screenshot).

Version-Release number of selected component (if applicable):
MGA4 Beta1 and 2

How reproducible:
Fresh install via DVD installer.




Reproducible: 

Steps to Reproduce:
Comment 1 Florian Bauer 2013-12-19 19:03:04 CET
Created attachment 4645 [details]
akonadi after starting kde
Comment 2 Florian Bauer 2013-12-19 19:03:43 CET
Created attachment 4646 [details]
failure report of system settings
Comment 3 Florian Bauer 2013-12-19 19:04:19 CET
Created attachment 4647 [details]
akonadi works after starting manually with "akonadictrl start"
David Walser 2013-12-19 22:01:52 CET

CC: (none) => balcaen.john, mageia

Manuel Hiebel 2013-12-22 20:03:12 CET

CC: (none) => lmenut
Blocks: (none) => 12079

Comment 4 Manuel Hiebel 2013-12-23 12:00:24 CET
Do you have an nvidia card ?
Comment 5 Florian Hubold 2013-12-23 13:53:47 CET
Cannot reproduce with beta2. Default KDE install from x86_64 DVD with all updates, seems akonadi is running properly:

[doktor5000@localhost ~]$ ps -ef | grep -v grep | grep -i -e ako -e sql
500       3363     1  0 13:40 ?        00:00:00 /usr/bin/akonadi_control
500       3365  3363  0 13:40 ?        00:00:00 akonadiserver
500       3367  3365  0 13:40 ?        00:00:00 /usr/sbin/mysqld --defaults-file=/home/doktor5000/.local/share/akonadi/mysql.conf --datadir=/home/doktor5000/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-doktor5000.Tborhx/mysql.socket
500       3489  3363  0 13:40 ?        00:00:00 /usr/bin/akonadi_agent_launcher akonadi_akonotes_resource akonadi_akonotes_resource_0
500       3490  3363  0 13:40 ?        00:00:00 /usr/bin/akonadi_archivemail_agent --identifier akonadi_archivemail_agent
500       3491  3363  0 13:40 ?        00:00:00 /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_0
500       3492  3363  0 13:40 ?        00:00:00 /usr/bin/akonadi_agent_launcher akonadi_ical_resource akonadi_ical_resource_0
500       3494  3363  0 13:40 ?        00:00:00 /usr/bin/akonadi_agent_launcher akonadi_maildir_resource akonadi_maildir_resource_0
500       3495  3363  0 13:40 ?        00:00:00 /usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agent
500       3496  3363  0 13:40 ?        00:00:00 /usr/bin/akonadi_mailfilter_agent --identifier akonadi_mailfilter_agent
500       3497  3363  0 13:40 ?        00:00:00 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
500       3498  3363  0 13:40 ?        00:00:00 /usr/bin/akonadi_newmailnotifier_agent --identifier akonadi_newmailnotifier_agent
500       3499  3363  0 13:40 ?        00:00:00 /usr/bin/akonadi_sendlater_agent --identifier akonadi_sendlater_agent


[doktor5000@localhost ~]$ akonadictl status
Akonadi Control: running
Akonadi Server: running
Akonadi Server Search Support: not available

Also systemsettings -> "personal information" shows all four Akonadi ressources as "Ready". Although the weird thing is I'm missing the kcm module for akonadi itself in systemsettings. It is installed (akonadi-kde) and can be called via "kcmshell4 kcm_akonadi" but does not appear in systemsettings nor kcmshell4 --list.

[doktor5000@localhost ~]$ kcmshell4 --list 2>/dev/null | grep -i ako
kcm_akonadi_resources      - Einrichtung des persönlichen Informationsmanagement von Akonadi

PS: this is with an nvidia card and proprietary driver.

CC: (none) => doktor5000

Comment 6 Florian Hubold 2013-12-23 13:55:30 CET
Created attachment 4661 [details]
Log/output of akonadi test
Comment 7 Florian Bauer 2013-12-24 08:13:20 CET
Yes, I'm using Nvidia card incl. proprietary driver.
By that way, I've deleted every akonadi item found in ".config/akonadi/" and created them new via systemsettings - pim but after restart akonadi failed either to start properly.
But again, it works fine after "killing" it and starting new manually.
Comment 8 Florian Bauer 2013-12-24 09:56:04 CET
just tested: changed graphics driver to nouveau -> restart -> akonadi starts properly
also other failures are gone (amarok collection scanner freeze: bug 11742; kwrite fails to start: bug 11946)
Comment 9 Florian Bauer 2013-12-24 10:39:24 CET
switching back to proprietary driver -> akonadi fails to start (see attached output of "akonadi test"
Comment 10 Florian Bauer 2013-12-24 10:40:52 CET
Created attachment 4665 [details]
akonadi test output
Manuel Hiebel 2013-12-24 11:42:20 CET

Summary: akonadi doesn't work after starting kde => akonadi doesn't work after starting kde (nvidia)

Comment 11 Anne Nicolas 2014-01-19 21:35:22 CET
Reporter can you please test again using RC isos or up-to-date cauldron?

CC: (none) => ennael1

Comment 12 Florian Bauer 2014-01-20 20:08:39 CET
Hello,

I've updated to latest cauldron (20.1.2014) and afterwards I've installed the proprietary Nvidia driver via MCC. After reboot Akonadi didn't start properly, so it isn't fixed. Sorry :-(

I've switched back to nouveau via MCC and did a reboot -> Akonadi works!

However, thank you for working to fix that issue. Good luck!

Florian
Comment 13 Manuel Hiebel 2014-01-20 20:19:04 CET
rpm -qa | grep nvidia ?
Comment 14 Florian Bauer 2014-01-21 19:32:32 CET
nvidia-current-doc-html-331.20-10.mga4.nonfree
nvidia-current-kernel-3.12.8-desktop-1.mga4-325.15-5.mga4.nonfree
dkms-nvidia-current-331.20-10.mga4.nonfree
nvidia-current-kernel-desktop-latest-325.15-5.mga4.nonfree
x11-driver-video-nvidia-current-331.20-10.mga4.nonfree
Comment 15 Florian Bauer 2014-01-21 19:35:12 CET
question: might this bug be linked to bug 11946 resp. 11742?

regards
Florian
Comment 16 Manuel Hiebel 2014-01-21 19:37:02 CET
yes every bug in https://bugs.mageia.org/show_bug.cgi?id=12079 with nvidia on the summary are related, for amarok no ideas
Comment 17 Florian Hubold 2014-02-03 13:30:38 CET
Amarok starts fine here with 325.15. But please only one program per bug.
Comment 18 Florian Hubold 2014-02-21 00:00:58 CET
This should be fixed since 5 days with the p11-kit updates:
https://wiki.mageia.org/en/Mageia_4_Errata#nvidia_proprietary_drivers

Please reopen if problem persists.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 19 Florian Bauer 2014-02-21 18:12:03 CET
Thanks for the information.
I can't test it at the moment as I've installed opensuse 13.1 now as I've no Nvidia related bugs with this distro.
But I prefere the Mageia control center against Yast and I like the Mageia community so it's good to here that failure has been found.
So again great thanks to developers for hard work!