Akonadi fails to start with nvidia binary drivers installed

[Elsevier]

Upon opening Kontact akonadi is supposed to be loaded but fails with the following error: Akonadi fails to register at d-bus session.

I safed the self-test protocoll of the akonadi server and attached the report.

I already deleted all my akonadi config files but it did not resolve the error.

[Glentadakis Dimitrios (dglent)]

Since 1 month, akonadi fails to start after boot
I deleted the content of the folders .local/share/akonadi and .configure/akonadi, it works for a few days and after it stops again

Reproducible: Always

Steps to Reproduce:
After boot
Actual Results:
Akonadi doesn't start

Expected Results:
Akonadi start up

Akonadi Server Self-Test Report
===============================

Test 1: SUCCESS
--------

Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.

File content of '/home/dglent/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/dglent/.local/share/akonadi/socket-localhost.localdomain/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null

Test 2: SUCCESS
--------

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3: SUCCESS
--------

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.

Test 4: SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: 131019 14:08:14 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
/usr/sbin/mysqld Ver 5.5.33a-MariaDB for Linux on x86_64 (Mageia MariaDB Server)

Test 5: SUCCESS
--------

MySQL server log contains no errors.
Details: The MySQL server log file &apos;<a href='/home/dglent/.local/share/akonadi/db_data/mysql.err'>/home/dglent/.local/share/akonadi/db_data/mysql.err</a>&apos; does not contain any errors or warnings.

File content of '/home/dglent/.local/share/akonadi/db_data/mysql.err':
131019 13:59:17 InnoDB: The InnoDB memory heap is disabled
131019 13:59:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131019 13:59:17 InnoDB: Compressed tables use zlib 1.2.7
131019 13:59:17 InnoDB: Using Linux native AIO
131019 13:59:17 InnoDB: Initializing buffer pool, size = 80.0M
131019 13:59:17 InnoDB: Completed initialization of buffer pool
131019 13:59:17 InnoDB: highest supported file format is Barracuda.
131019 13:59:18 InnoDB: Waiting for the background threads to start
131019 13:59:19 Percona XtraDB (http://www.percona.com) 5.5.33a-MariaDB-31.1 started; log sequence number 21404448
131019 13:59:19 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.33a-MariaDB' socket: '/home/dglent/.local/share/akonadi/socket-localhost.localdomain/mysql.socket' port: 0 Mageia MariaDB Server

Test 6: SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global A...

[Dvratil (dvratil)]

Can you please provide output of "ps x | grep -i akonadi" ?

[Graeme Hewson (ghewson)]

I have this problem after upgrading Kubuntu 13.04 to 13.10, but not always. Sometimes after rebooting and logging in, Akonadi starts properly, but most often, although akonadi_control and akonadiserver are running, I see the messages in tests 10 and 11:

Akonadi control process not registered at D-Bus.
Akonadi server process not registered at D-Bus.

(Unlike the above log, though, test 12 for me says "Nepomuk search service registered at D-Bus.")

The solution for me is:

pkill akonadi_control
pkill akonadiserver
akonadictl start

I guess it's a timing problem.

[Graeme Hewson (ghewson)]

I forgot to mention that I had the KDE 4.11.2 PPA installed under Kubuntu 13.04, so the KDE version didn't change with the upgrade to 13.10.

[Cgiboudeaux (cgiboudeaux)]

(In reply to comment #3)
> I forgot to mention that I had the KDE 4.11.2 PPA installed under Kubuntu
> 13.04, so the KDE version didn't change with the upgrade to 13.10.

no message from apparmor in the dmesg output ?
can you also check if the mysql version changed when your switched to kubuntu 13.10 ?
are the mysql-upgrade and mysqladmin still installed ?

[Graeme Hewson (ghewson)]

Messages from apparmor are:

apparmor="DENIED" operation="file_perm" info="Failed name lookup - disconnected path" error=-13 parent=1 profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name=".local/share/akonadi/db_data/mysql.err" pid=2813 comm="mysqld" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
apparmor="DENIED" operation="file_perm" info="Failed name lookup - disconnected path" error=-13 parent=1 profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name=".local/share/akonadi/db_data/mysql.err" pid=2813 comm="mysqld" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000

Mysql changed from 5.5.32 to 5.5.34.

mysqladmin is installed, but not mysql-upgrade.

[Cgiboudeaux (cgiboudeaux)]

ok, please try:
sudo aa-complain mysqld-akonadi
sudo /etc/init.d/apparmor reload
akonadictl start

[webmarwell (webmarwell)]

Same here. Sometimes it works, sometimes not. If it doesn't work self-test protocol says:

Test 10: ERROR
--------
Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 11: ERROR
--------
Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Logout user and login again sometimes works, sometimes not. It's about one fourth of logins it doesn't work.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[siyman (siyman)]

This affects me as well. Akonadi is not able to register the control process at D-Bus. I tried to copy and reown my configuration data into a new user account and the same behaviour reappeared. A fresh account is working. Therefore it must have something to do with my and the other's configs.

[Giovanni Escobar Sosa (mu-tazila)]

After installing Kubuntu 13.10 from Kubuntu 13.04 I have found the same problem with Akonadi. After deleting ~/.local/share/akonadi and ~/.config/akonadi I could reload the calendar I have in KOrganizer, but the events are not loaded until I restart the session. I too had KDE 4.11.2, but from a PPA, ppa:kubuntu-ppa/backports.

Just today the same happened after several days of normal use.

[Graeme Hewson (ghewson)]

(In reply to comment #6)
> ok, please try:
> sudo aa-complain mysqld-akonadi
> sudo /etc/init.d/apparmor reload
> akonadictl start

I didn't try this because the apparmor messages haven't reappeared after several reboots. I guess they only appeared because I was struggling to get kmail working after the Kubuntu upgrade.

Still akonadi sometimes starts properly after rebooting and logging in, but mostly it doesn't.

[Giovanni Escobar Sosa (mu-tazila)]

Again Akonadi fail to load. After using
$ pkill akonadi_control
$ pkill akonadiserver
$ akonadictl start
I got this exit
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths: ("/home/giovanni/bin", "/usr/lib/lightdm/lightdm", "/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin", "/usr/games", "/usr/local/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.general_log OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.servers OK
mysql.slow_log OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths: ("/home/giovanni/bin", "/usr/lib/lightdm/lightdm", "/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin", "/usr/games", "/usr/local/games")
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
Fon...

[Giovanni Escobar Sosa (mu-tazila)]

I have this problem after making a fresh install from 13.04 (upgrading is not for me). From https://bugs.kde.org/show_bug.cgi?id=326480 I just followed the instructions
$ pkill akonadi_control
$ pkill akonadiserver
$ akonadictl start
And I get
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths: ("/home/giovanni/bin", "/usr/lib/lightdm/lightdm", "/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin", "/usr/games", "/usr/local/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.general_log OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.servers OK
mysql.slow_log OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths: ("/home/giovanni/bin", "/usr/lib/lightdm/lightdm", "/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin", "/usr/games", "/usr/local/games")
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
...

[Graeme Hewson (ghewson)]

I've noticed that akonadi usually starts OK when I log in after being logged in previously for several days. When this happens, nepomuk seems to be working hard (catching up on the work it didn't do in the previous login session?).

Incidentally, in comment 2 I neglected to show a clean shutdown of mysql. The full sequence of commands is:

pkill akonadi_control
pkill akonadiserver
mysqladmin shutdown --socket ~/.local/share/akonadi/socket-$(hostname)/mysql.socket
akonadictl start

[Glentadakis Dimitrios (dglent)]

The output of ps x | grep -i akonadi:

[dglent@localhost ~]$ ps x | grep -i akonadi
 1673 ? Sl 0:00 /usr/bin/akonadi_control
 1675 ? Sl 0:00 akonadiserver
 1677 ? Sl 0:00 /usr/sbin/mysqld --defaults-file=/home/dglent/.local/share/akonadi/mysql.conf --datadir=/home/dglent/.local/share/akonadi/db_data/ --socket=/home/dglent/.local/share/akonadi/socket-localhost.localdomain/mysql.socket

[Glentadakis Dimitrios (dglent)]

I can reproduce it with mariadb 5.5.33a but i cannot reproduce it with mariadb-5-5-28.
I will continue the test and i will confirm it later.

I remarked with mariadb 5.5.33a i have the process mysqlcheck as zombie

[Glentadakis Dimitrios (dglent)]

This morning i had again the symptome with mariadb 5.5.28 :(

[Dvratil (dvratil)]

The problem appears to be that sometimes (?) Akonadi is unable to start any resources or agents. Akonadi requires at least one agent or resource to run.

Apparently the resources are available (judging from content of /usr/share/akonadi/agents). Please enable ibakonadi in kdebugdialog and start Akonadi from console (akonadictl start) and paste here the output.

[Michal (mikeos)]

The workaround works for me too.

$ pkill akonadi_control
$ pkill akonadiserver
$ akonadictl start

[Elsevier (kofferpc)]

Ok, that workaround got kontact working in full at once here!

Thanks Giovanni!

Will report if it keeps working after reboot or not.

brotaffe

[webmarwell (webmarwell)]

The way in comment #5 starts akonadi here too.
But whats the problem with akonadi?

I still have every 4 or 5 times starting kubuntu the problem.

[siyman (siyman)]

I had to manually remove my ~/.config/akonadi/akonadiserverrc first. Afterwards the commands from comment #5 worked like a charm and now I have my akonadi back working.
Thanks a lot!

[japs_it88 (j-nespolo)]

*** Bug 327159 has been marked as a duplicate of this bug. ***

[Elsevier (kofferpc)]

Well, even after deleting the akonadiserverrc before using the three commands as Michal proposed will not repair my akonadi. After reboot same problem of akonadi not registering to the D-Bus session.

[Glentadakis Dimitrios (dglent)]

The output of akonadictl start:

[dglent@localhost ~]$ akonadictl start
Unable to register service as "org.freedesktop.Akonadi.Control.lock" Maybe it's already running?
"[
0: /usr/bin/akonadi_control(_Z11akBacktracev+0x33) [0x43e943]
1: /usr/bin/akonadi_control() [0x43ec9a]
2: /lib64/libc.so.6(+0x34ae0) [0x7f949291bae0]
3: /lib64/libc.so.6(gsignal+0x35) [0x7f949291ba65]
4: /lib64/libc.so.6(abort+0x148) [0x7f949291d0c8]
5: /lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f949392a224]
6: /usr/bin/akonadi_control(_ZN15FileDebugStream9writeDataEPKcx+0x9b) [0x440a0b]
7: /lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb4) [0x7f94939c4af4]
8: /lib64/libQtCore.so.4(+0x11682f) [0x7f94939cf82f]
9: /lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x7f94939d7e2b]
10: /usr/bin/akonadi_control(_ZN6QDebugD1Ev+0x3f) [0x41c48f]
11: /usr/bin/akonadi_control(main+0x350) [0x419230]
12: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f9492908ba5]
13: /usr/bin/akonadi_control() [0x4193f9]
]
"
Error: akonadi_control was started but didn't register at D-Bus session bus.
Make sure your system is set up correctly!

[Graeme Hewson (ghewson)]

Created attachment 83470
libakonadi debug output

[Graeme Hewson (ghewson)]

I directed libakonadi debug output to disk while I logged in to KDE (file attached).

The messages make reference to /tmp/akonadi-ghewson.ws0sFY/akonadiserver.socket, but there is no such file. This is after a reboot (on Kubuntu, where /tmp is cleared between reboots). However, the file /did/ exist in the previous session, and in the current session ~/.local/share/akonadi/socket-$(hostname) is a link to /tmp/akonadi-ghewson.ws0sFY/akonadiserver.socket.

The messages also say "Akonadi server is already starting up", but before logging in to KDE I started a terminal session and verified that Akonadi wasn't running. (It's very hard to see how it could have been!)

To reiterate: sometimes Akonadi does start properly. In fact, while I was debugging, it usually did (presumably due to a change in the timing), and I had to try several times before it failed to start properly.

[Dvratil (dvratil)]

Could any of you please try whether the problem is fixed with this [0] patch for kdepimlibs? The patch addresses a DBus-timing problem that could be the same as yours. I'm just not very happy about how it fixes the problem. We will work on it with Guy this weekend on the PIM sprint and get it to next KDE update.

[0] https://git.reviewboard.kde.org/r/112062/

[Elsevier (kofferpc)]

Ok guys.

I just installed the Kubuntu 13.10 updates from 4.11.2 to KDE 4.11.3 and to Kernel 3.11.0-13.

The first thing is that the above described three commands now lead to crashes of Kontact and Akonadi AND that Kontact now works normal again, even after rebooting. I hope it stays this way - will give feedback on this.

[Elsevier (kofferpc)]

Well the joy did not last long - after third rebootthe D-Bus problem occurs again and I had to pkill and restart everything like above.

[webmarwell (webmarwell)]

The problem still continues.
$ pkill akonadi_control
$ pkill akonadiserver
$ akonadictl start
works, but its only a workaround. I dont see a reason to delete this akonadiserverrc:

[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-mlinux.xgvO7g/mysql.socket"
ServerPath=/usr/sbin/mysqld-akonadi
StartServer=true

[Debug]
Tracer=null

Or is there anything wrong with it? The problem still occurs every some logins.

[siyman (siyman)]

Yesterday I killed nepomuk and akonadi via sigterm, today after logging in I have to manually use the three commands (pkill plus akonadictl) again. Now it's working as expexted. I had to sigterm akonadi and nepomuk because they paused the system shutdown process.
Any ideas what is actually happening in here?

[Tsu Jan (tsujan2000)]

This isn't specific to Ubuntu; I have exactly the same problem in Debian Unstable. Perhaps we should post a bug report against Akonadi at bugs.kde.org.

[siyman (siyman)]

I'ld appreciate it, though it would be nice if you could do that =)

[Tsu Jan (tsujan2000)]

Done: https://bugs.kde.org/show_bug.cgi?id=328201
Please see if it's a good description of the problem and add extra info if needed!

[Tsu Jan (tsujan2000)]

BTW, it's better to add an extra command to the temporary workaround suggested in this report:

pkill akonadi_control
pkill akonadiserver
pkill mysqld
akonadictl start

Without killing mysqld, I'd have two mysqld processes running, which doesn't seem correct.

[Tsu Jan (tsujan2000)]

*** Bug 328201 has been marked as a duplicate of this bug. ***

[Andreas H. (andreas30451)]

Got this on a fresh kubuntu installation. Come from Mint15/KDE because i had this bug there too.
Installed kubuntu , removed all hidden directorys on old Home-partition,, remounted my /home-partition, installed Nvidia-Drivers and some software.

Akonadi keeps crashing with this d-bus message.
Weird thing is, here and then it starts after a reboot. Some sort of timing-problem perhaps ?

[Joerg-schuck (joerg-schuck)]

Ok. I at least have a nvidia card in my system and the 331.20 driver installed.

[Weigelt-bernd (weigelt-bernd)]

ok, also a nvidia card with manually installed 331.20 driver

[Tsu Jan (tsujan2000)]

I also have nvidia 331-20, installed from Debian Experimental.

[Graeme Hewson (ghewson)]

Nvidia 319.60 here!

[Fuchs (fuchs)]

For all of those who now commented with "yes, nvidia here!" and similar: it would probably be more helpful both for you and others if you actually did downgrade to the version I mentioned and see if the problem persists.

If not: you got rid of the problem, people know what the cause is and they know a workaround until nvidia releases a new driver.

Kind regards,

Fuchs

[Tsu Jan (tsujan2000)]

I downgraded to 325.15 and Akonadi started OK after two reboots and a logout-login. I'll tell you if the problem still happens with this driver. It'll take some time to be sure.

BTW, nvidia-319.X may have bugs (https://devtalk.nvidia.com/default/topic/638521/linux/gnome-terminal-problems-ctrl-c-and-exit/).

[webmarwell (webmarwell)]

Me too, NVIDIA and 331.20 - since today. Before I was using 319.60. and had the problem.

[Tsu Jan (tsujan2000)]

With nvidia-325.15, I've had several reboots, cold boots and log-ins, and Akonadi started well every time.

BTW, most of the random problems I mentioned in Comment 25 were caused by nvidia-331.20 too. Even Amarok didn't exit on quitting sometimes. Thank you, Fuchs!

[Graeme Hewson (ghewson)]

I removed my nVidia card and the driver, and Akonadi starts OK now.

I didn't experience the problems in the other reports in comment 52 of ^C not working in xterm (or Konsole, either).

I have a suspicion that I was mistaken in comment 32 when I said that Akonadi only started 4 out of 5 times after renaming /usr/share/dbus-1/services/org.freedesktop.Akonadi.Control.service. Testing now, I found I wasn't always allowing enough time, so "akonadictl status" might say "stopped", but a moment later it would say "running".

[T-kleindienst (t-kleindienst)]

.
.
I removed all proprietary Nvidia stuff and switched to using Nouveau drivers.
Akonadi starts o.k.. No problems whatsoever so far.
Seems the current Nvidia drivers were causing the troubles.
Still I need the proprietary drivers for my CAD stuff. Maybe using Nvidia 325.15 is an "interim" option...

[Joerg-schuck (joerg-schuck)]

No problems after the nvidia driver downgrade so far. Akonadi started consistently the last days.

[Neutrino-0 (neutrino-0)]

WTF is this bug? every month I can't use kontact because something is broken (akonadi, kmail, nepomuk, ...) and now it is the Nvidia driver? I have upgraded the nvidia driver to 331.20-3 on archlinux and upgraded to the newes kernel 3.12.6-1 after reboot akonadi seems to work now...

[Tsu Jan (tsujan2000)]

@neutrino
As you see, many users have confirmed that it's an nVidia bug, and it affects other apps too. So, the Akonadi devs can do nothing about it.

[Faah (faah)]

I just wanted to point out, I'm affected by this bug and I'm not using the broken 331.20 nividia driver, I'm still on 319.60. This driver was working fine with KDE 4.10 and also akonadi was ok for me with KDE 4.10 and now I'm on KDE 4.11 and I'm encountering the problem.

I have also no problems of other programs not starting, only akonadi needs a kick after a reboot of the system and on my system I can see akonadi processes running, they are just not responding properly.

So there are actually two problems in this bug here.
* One with the broken nvidia driver where the akonadi devs can't do anything
* And the one that some others here and I'm facing where akonadi fails to register/respond properly at the dbus where I think the akonadi devs can do something, because this looks like a racing condition in the startup phase.

[Glentadakis Dimitrios (dglent)]

I downgraded to 319.60 and i can still reproduce it
I could n't reproduce it with nouveau (tested 1 time)

I have this configuration:

dkms-nvidia-current-319.60-1.mga3.nonfree
nvidia-current-doc-html-319.60-1.mga3.nonfree
nvidia-current-kernel-3.10.24-desktop-2.mga3-319.60-8.mga3.nonfree
nvidia-current-kernel-3.10.25-desktop-1.mga3-319.60-9.mga3.nonfree
nvidia-current-kernel-desktop-latest-319.60-9.mga3.nonfree
x11-driver-video-nvidia-current-319.60-1.mga3.nonfree
[dglent@localhost ~]$ uname -r
3.10.25-desktop-1.mga3
[dglent@localhost ~]$

[Fuchs (fuchs)]

Hi again,

as mentioned in the reports linked, there are lots of different drivers affected, not only 331.20. So people experiencing this should down- / update to the also mentioned 325.15, as that is the only halfway recent driver that is known to work. If the problem still persists, then it's a different bug. Else it's quite probably this one, as it got confirmed not only by lots of users on different distributions but also by nvidia.

Kind regards,

Fuchs

[Hussam-v (hussam-v)]

331.20 was released on november 6 so it's probably not too long till we see a new driver.

[Jens-westemeier (jens-westemeier)]

Here some more data points:
I got the problem when migrating from OpenSuSE 12.3 to 13.1. I upgraded KDE from 4.11.4 to 4.12.0, the problem remained.
I have installed Nvidia nvidia-gfxG03-kmp-desktop-331.20_k3.11.6_4-22.2.x86_64, nvidia-computeG03-331.20-22.1.x86_64 and x11-video-nvidiaG03-331.20-22.1.x86_64 from the OpenSuSE Build Service.
But:
I can run K-Mail (including the implicit start of akonadi) immediately (<10s) after having started the system and logged into my KDE session. Later than that akonadi does not start. So it might be a raise condition with other services.

[Giovanni Escobar Sosa (mu-tazila)]

Two days ago (2013.12.29) there were an update of akonadi in Kubuntu 13.10, from 1.10.3-0ubuntu1 (saucy) to 1.11.0-0ubuntu1~ubuntu13.10~ppa1 (saucy), and after several reboots I could say there had been no more problems with Akonadi, even with NVIDIA driver 319.60.

Hopefully the problem is fixed.

[Tsu Jan (tsujan2000)]

>Two days ago (2013.12.29) there were an update of akonadi in Kubuntu 13.10... and after several reboots I could say there had been no more problems

Sadly the bugs in nvidia 319.x and 331.20 can cause several other problems too (in Ark, Amarok and kwin effects, for example). Only nvidia 325.15 is OK.

[Dvratil (dvratil)]

Thanks everyone for the input and for confirming this is caused by the nvidia driver.

Those who still experience the bug with nvidia-319.xx (which reportedly should work) could you please try nouveau to make sure it's not yet another issue in the binary drivers? If you can reproduce the problem with nouveau, please open a new bug report. We will use this one to track only the nvidia-related issue.

I'll close this as UPSTREAM, since we can't do anything about it. As recommended in comments above, either wait for nvidia to release an update, downgrade to nvdia-319.xx or switch to the open source nouveau driver.

[Fuchs (fuchs)]

(In reply to comment #70)
> Thanks everyone for the input and for confirming this is caused by the
> nvidia driver.
>
> Those who still experience the bug with nvidia-319.xx (which reportedly
> should work)

Minor sidenote, I'd recommend 325.15 which works according to several bug reports and on my system here, and probably supports a bit more hardware.

Kind regards,

Christian

[Harald Sitter (apachelogger)]

I am a bit confused.

According to upstream <= 325.15 (including 319.32) should be fine and yet this report is about 13.10 which defaults to 304.108 and has as newest available option the 319.32. So if both are supposed to work, what is this bug report about then?

[Shinji (thorsten-reichelt)]

I have exactly the same problem after upgrading to Ubuntu 13.10.
But I DO NOT have an NVIDIA card installed!!
I am using the integrated

"Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02)"

of my DELL Optiplex 755.

[Fifoxtasy (philipp-foerster)]

this affects me on 2 devices.
on my computer with an nvidia card
on my zbox which does not have a nvidia card!!!

i don't think this is linked to nvidia cards

[Tsu Jan (tsujan2000)]

> i don't think this is linked to nvidia cards

Strange! For me, all issues (in Akonadi and other apps as well) disappeared with nVidia-325-15. In Debian, after upgrading to KDE-4.11.3, at first I though the new KDE was buggy but all those bugs turned out to be related to nVidia.

[Harald Sitter (apachelogger)]

Right. So, I think this report may have been a bit of a mix of different issue causes. There is a number of things that can cause Akonadi to fail to start. One of them apparently has to do with the graphics driver (oddly enough). Since some of you reported problems regardless of driver version and others suggested that a down/upgrade resolved the issue I am left to assume that not everyone is having the same cause although the result is the same (akonadi not starting, error dialog coming up and so forth).

Talking about different things at the same time is not very helpful so I am going to close this bug report as invalid in accordance with the upstream report that indicates that the nvidia driver versions available in 13.10 should not cause any problems (please also make sure that you do not use a PPA with unoffical driver versions - such as the xorg edgers PPA).

Everyone who has Akonadi startup problems even with a supposed to be working version of the nvidia driver or a whole different driver to begin with, please report new bugs at bugs.kde.org using the Akonadi error dialog. They may look like the same bug but really they are not and warrant investigation on their own.

Thanks all.

[T-kleindienst (t-kleindienst)]

Nvidia released their binary driver version 331.38 on Jan 13th. Did anybody check it already?
(last time I checked was with 331.20 which was giving troubles)

[T-kleindienst (t-kleindienst)]

(In reply to comment #72)

Just checked it myself. No Suse packages yet. I used the binary installation file from Nvidia. So far it seems to work. Akonadi is up and running...

[Quinn Balazs (qbalazs)]

In theory 331.38 "should" work. The signal processing issues were dealt with in an unreleased predecessor to 331.38.

[Hussam-v (hussam-v)]

does it still happen with this driver?
http://us.download.nvidia.com/XFree86/Linux-x86_64/331.38/NVIDIA-Linux-x86_64-331.38-no-compat32.run

[Jacob Greenstein (jgrnst)]

I installed it about an hour ago (needless to say, there is no package for Fedora yet). Akonadi started seamlessly after a reboot.

[Hussam-v (hussam-v)]

I updated to new driver from archlinux repository and i tried everything from logging off/logging back on and rebooting. no akonadi failures so far.

[Mfraz74+kde (mfraz74+kde)]

Kubuntu 13.10 with KDE 4.12, just added the xorg-edgers PPA and updated to 331.38 and Akonadi is still not starting.

[Weigelt-bernd (weigelt-bernd)]

openSUSE 13.1 with KDE 4.12.1 and Nvidia 331.38
driver installed 3 days ago and akonadi starts without any problem

my problem is fixed

thx
Bernd

[Mfraz74+kde (mfraz74+kde)]

Kubuntu 13.10 with KDE 4.12, just added the xorg-edgers PPA and updated to 331.38 and Akonadi is still not starting.

[Eli-hiw (eli-hiw)]

Confirmed the fix on Fedora 20. As indicated no rpms yet.

[Tsu Jan (tsujan2000)]

I also confirm that the issue is fixed, on Debian and with nVidia 331.38 from its Experimental repository.

[Quinn Balazs (qbalazs)]

xorg-edgers isn't officialy supported. Is there a reason that your using xorg-edgers over the binary file from nvidia? Since this issue was resolved for most others by installing the driver directly from nvidia, I urge you to remove xorg-edgers and download the file directly from nvidia. If after that you are still experiencing the issue, please file a new bug against Akonadi in Ubuntu.

[adaptee (adaptee)]

*** Bug 327411 has been marked as a duplicate of this bug. ***