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
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
--
You received
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.
--
You received this bug notification because you are a
** Changed in: akonadi
Status: Unknown = Won't Fix
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus
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?
** Changed in: akonadi (Ubuntu)
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.
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
Dear all,
This is quite likely due to an nvidia signal processing issue which has
been solved in a (yet unreleased) driver, see
https://devtalk.nvidia.com/default/topic/659230/linux/331-20-on-x86_64
-breaks-signal-processing-/
(and https://devtalk.nvidia.com/default/topic/638521/linux/gnome-
Me too, NVIDIA and 331.20 - since today. Before I was using 319.60. and
had the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10 akondai fails to
pkill !
This helps me too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus
session, making kde-pim suit unusable
To
** Also affects: akonadi via
https://bugs.kde.org/show_bug.cgi?id=326480
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade
Launchpad has imported 35 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=326480.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
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.
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'ld appreciate it, though it would be nice if you could do that =)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus
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!
** Bug watch added: KDE Bug Tracking System #328201
https://bugs.kde.org/show_bug.cgi?id=328201
--
You received this bug notification because you are a member
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.
--
You received this bug
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
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
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 -
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The workaround works for me too.
$ pkill akonadi_control
$ pkill akonadiserver
$ akonadictl start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10
Ok, that workaround got kontact working in full at once here!
Thanks Giovanni!
Will report if it keeps working after reboot or not.
brotaffe
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to akonadi in Ubuntu.
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245979
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
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.
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: akonadi (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
31 matches
Mail list logo
