Mageia forum

Since the last round of updates a few days ago, I am having a problem that appears to be a KDE problem, and it manifests itself in at least two different ways. One way is that on startup akonadi does not work, and the other way is that any KDE component that needs to go on the internet fails to do so.

When I start KDE, akonadi and akonadi control will show as running, but any attempt to communicate with them fails. After I manually kill them, then restart with akonadictl start, they work. Also, Kopete only partly starts up then hangs with a blank window. After a force quit, I can restart it successfully.

After I do this, for some period of time (hours to days) KDE functions normally. At some point, for an unknown reason, kmail stops checking the mail server (though it attempts to check the mail server...seems to hang), and kopete also stops talking on the internet, though it claims to be online. I have not tested konqueror or ktorrent, but I bet they also won't connect to the network. However, tor, firefox, chromium, and skype still connect with the network. It seems like the KDE components only won't communicate.

When the KDE components stop communicating on the net, I cannot restore their functionality by restarting X or by logging out/logging back in. I also cannot restore functionality by stopping and restarting network services (service network restart). I can, however, restore their functionality by logging out, doing a telinit 1, then doing a telinit 5, and logging back in. Thus, the component causing the problem is shut down and restarted when I change runlevels.

Does anyone have any idea what is causing this?

By any chance, which nvidia driver version do you use? One of the more recent ones, 331.20 or at least > 325.15?
Check https://bugs.mageia.org/show_bug.cgi?id=12079#c3 and https://bugs.mageia.org/show_bug.cgi?id=12055

Best downgrade nvidia driver to 325.15.

Wow. Just wow. I never would have suspected the video driver for this.

I upgraded from 319 to 331 with this upgrade, since changing kernels made it a convenient time.

Guess I'll have to roll back.

When I get around to doing that I will let you know how it went.

You could also wait for Nvidia, they already have the fix in an unreleased driver. But I wouldn't bet on them releasing it in the next few days or even this year.

I rolled back to the 325 driver a couple of days ago, and the problems seem to be gone.

As a followup on this, I just installed the 331.49 driver which was released about 5 days ago, and the symptoms I was observing with 331.20 are gone. So far, 331.49 is working fine.

Now I will see if some other problems I have had are gone. Notably, gkrellm would periodically crash - and I long ago tracked that into the NVidia driver, and gkrellm did NOT crash with 33.120. I am also wondering whether or not the new driver will have any effect on memory leaks that get blamed on X and flash. We will see...