*** Bug 327411 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
Akonadi fails to start with nvidia binary drivers installe
I also confirm that the issue is fixed, on Debian and with nVidia 331.38
from its Experimental repository.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
Akonadi fails
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 t
Confirmed the fix on Fedora 20. As indicated no rpms yet.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
Akonadi fails to start with nvidia binary drivers installed
St
Kubuntu 13.10 with KDE 4.12, just added the xorg-edgers PPA and updated
to 331.38 and Akonadi is still not starting.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
Akon
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
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.
Kubuntu 13.10 with KDE 4.12, just added the xorg-edgers PPA and updated
to 331.38 and Akonadi is still not starting.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
Akon
I installed it about an hour ago (needless to say, there is no package
for Fedora yet). Akonadi started seamlessly after a reboot.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
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.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad
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
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs
(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...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubu
In theory 331.38 "should" work. The signal processing issues were dealt
with in an unreleased predecessor to 331.38.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
Akon
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)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs
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
> 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
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 Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs
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 mem
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)
** Changed in: akonadi
Status: Unknown => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, 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-
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
wi
(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
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-
>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
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.
331.20 was released on november 6 so it's probably not too long till we
see a new driver.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10
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
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-cu
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
@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.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchp
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...
--
You receiv
No problems after the nvidia driver downgrade so far. Akonadi started
consistently the last days.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubunt
.
.
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
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 afte
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!
--
You received this bug notifi
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 Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10 a
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-a
Nvidia 319.60 here!
--
You received this bug notification because you are a member of Desktop
Packages, 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
session, making kde-pim suit unus
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 kn
I also have nvidia 331-20, installed from Debian Experimental.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10 akondai fails to register a
ok, also a nvidia card with manually installed 331.20 driver
--
You received this bug notification because you are a member of Desktop
Packages, 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
It is 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-
terminal-problems-ctrl-c-and-exit/ a
Ok. I at least have a nvidia card in my system and the 331.20 driver
installed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10 akondai fa
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-
term
In case it helps, I am using Qt 4.8.5 and dbus 1.6.18
--
You received this bug notification because you are a member of Desktop
Packages, 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'm not using Fedora, but I haven't found it necessary to remove
Akonadi's config files to get it working.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade
I have the same problem on Fedora 20 (KDE 4.11.4), and had it on Fedora
19 for about a month. The only way to get akonadi work again is to
remove all its config files, kill all akonadi-related processes and
restart it.
--
You received this bug notification because you are a member of Desktop
Pack
Hi all !!
same problem after 13.10 upgrade (from 13.04). update 4.12 not solved
it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10 akond
I can confirm this bug on Arch Linux with KDE 4.11.4.
Killing akonadi_control, akonadiserver and mysqld processes and
restarting akonadi afterwards let akonadi run fine until the next reboot
:)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
I'm running 4.11.3 on opensuse 13.1. After running kontact about 2-3
times, it refuses to start.
Test 10: ERROR Akonadi control process not registered at D-Bus.
Test 11: ERROR Akonadi server process not registered at D-Bus.
I did a fresh install of suse 13.1 yesterday. I also started with a fre
after update to KDE 4.12.0 same problem, but ideas about the PIDs are
completely useless
so please ignore them
It doesn't matter whether, if the PIDs are higher or lower
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
Hi all!
Recently I updated KDE to version 4.11.4 (Gentoo Linux). So far, every time
akonadi start without any problem.
I also check PID. The Akonadi PID is higer than dbus.
Very odd issue.
Regards,
Simon
--
You received this bug notification because you are a member of Desktop
Packages, wh
i've two system with the latest 4.12 installed. on one machine (at work)
the problem occurs on every system start and on the second machine (at
home) the problem does not occur at all.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akona
@Jörg: i have no mysql zombies
--
You received this bug notification because you are a member of Desktop
Packages, 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
session, making kde-pi
@Jörg:
yes, most(all) starts after reboot are successful, after cold boot not
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10 akondai fa
@Jörg: possible two different problems?
I just made a reboot after some updates from opensuse, akonadi has started
successful
the akonadi-*-PID (4759) are higher then dbus (4614)
my akonadi-starts are fifty-fifty successful in the last days, so i can't find
a solution for me
:(
--
You received
@Bernd: Interesting. My rate is about 50/50 as well. But i noticed it working
everytime after a reboot but not always after a cold boot.
@Simon: Mmh. Well 4.12 should be hitting my repos pretty soon. Let's see if
that changes anything.
--
You received this bug notification because you are a mem
@Bernd: Can't confirm that theory, unfortunately. The problem is
occuring on my systems at random. I look at my Arch box and dbus-daemon
has the PID 837 while akonadi_control has 1059 and akonadiserver1061 and
still it fails to start any agents at random.
And i still have a mysqlcheck zombie proc
Hi
i take a look at the process list on my systems, btw found a second system with
this problem.
on the systems with this problem the PID of akonadi_control(4858) and
akonadiserver (4859) is lower then the PID of dbus-daemon (4702) started by KDE
both systems are updated from openSUSE 12.3 with
just installed KDE 4.12 on kubuntu 13.10 amd64 and the problem still appears.
sending SIGTERM to all akonadi processes (incl. mysql) and restarting kontact
akonadi works again (until restarting the machine).
--
You received this bug notification because you are a member of Desktop
Packages, whi
I have the same problem on a system running Kubuntu 13.10, with KDE
4.11.3 from the Kubuntu Backports PPA.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade
pkill !
This helps me too
--
You received this bug notification because you are a member of Desktop
Packages, 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
session, making kde-pim su
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
https://help.launc
** 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 Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
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.
W
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 notification
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
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 Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubuntu 13.10 akondai fails to regis
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 Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launch
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 happe
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"
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 Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/124
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 - wi
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 Desktop
Packages, which is subs
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 Desktop
Packages, which is subscribed to akona
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 Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.ne
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 Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/
The workaround works for me too.
$ pkill akonadi_control
$ pkill akonadiserver
$ akonadictl start
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245979
Title:
After Upgrade to Kubun
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
QDBusConnectionInter
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.
--
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 Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1245
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 erro
Public bug reported:
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 r
82 matches
Mail list logo
