I've only had KDE installed for a few weeks (on Debian Wheezy, before that was using Squeeze and GNOME, but a new mobo necessitated a newer kernel) but in that time it has locked up several times (most notably when I've been away from the computer for several hours). When I come back, I can't wake the screen, and the caps-lock and num-lock keys do not light up when pressed, so I guess it's a complete hang.

At this point it could be distro-related, but I'm asking here in case this is a known issue that might be fixed one day (currently doing an apt-get upgrade in the background as I type, to get the latest updates).

What seems strange is the greater than 60-second wait for KDE-based apps to start after logging in. Starting non-KDE/Qt stuff isn't a problem, it's only Kontact, KTorrent, Dolphin, and Konsole that have this strange delay and the busy X cursor for a while until it gives up, then the application decides to appear in its own time. If I reboot again, the apps are fine. It's only after it boots after one of these mysterious lock-ups that KDE/Qt-based apps are on a "go slow".

Any ideas? Thanks.

Also, when this strange behaviour occurs, KTorrent doesn't show an icon in the system tray panel applet. Not sure how relevant that is.

Anyway, after rebooting, things are better. It did occur to me that it might be related to Deluge (which I use only for Magnet links, because KTorrent won't start them, even with DHT enabled). If I'm away from the computer for an hour or so (but no longer), sometimes when I come back, everything has ground to an almost complete halt, and when I click File > Quit Deluge (which takes about 2 minutes to accomplish!!), the system is much more responsive. Maybe Deluge has a memory leak and after more than 2-3 hours it gets so bad that the whole system just freezes?

These are unusual problems you have here. I am using Debian Wheezy right now and did not had any of similar problems.

What graphic card and driver are you using?
Does your system support suspending (to RAM and/or disk)? It could be that after some inactivity KDE goes to power saving mode, which does not work on your system, causing problems.
Also, have you made complete Nepomuk indexing run? Depending on number of your files, it may take a while. It should leak anymore, though, so this is perhaps unrelated.

As for KTorrent:
- check Settings → Configure if "Show system tray icon" is turned on
- Magnet links works perfect here. Don't know what can be wrong.

If you suspect Deluge, the best would be running it and checking it's memory usage (every while). You can use KDE system monitor or any external tool, like htop.

In regards to the 60 second start time - this sounds suspiciously like a D-Bus timeout. Can you try running "qdbus" and see if that returns instantly (it should, with a long list of names).

@Minio: I'm using the default/FOSS video drivers since I understand that the proprietary/binary ones don't work with wheezy (yet).

I also don't think it has suspend-to-RAM enabled (I've never had a Linux setup where this worked - by itself - out of the box) and I certainly haven't tried to enable it.

As for Nepomuk, I disabled that the moment my system was brought to its knees after installing Wheezy+KDE (I googled and eventually removed it from akonadiconsole (which now lists only Address Book, Nepomuk Contact Feeder (Nepomuk not operational), Mail Dispatcher Agent, and Local Folders) in its list of agents. My Nepomuk/strigi configuration happily says that the Nepomuk installation is not complete, so hopefully Nepomuk won't bother me again

KTorrent's inability to show a tray icon only happens the first boot after a calamitous freeze, so I'm not too fussed about that. I'm more peeved at lack of magnet support. I have no idea why it's so recalcitrant in that regard, so I only let Deluge out of the box on rare occasions.


@bcooksley: as forecast, "qdbus" lists lots of goodness detailing org.kde stuff. I'll try to remember that after my next calamity. Thanks.

Does the go-slow persist after login, or if you logout and back in again after having recieved a go-slow session?

bcooksley wrote:Does the go-slow persist after login, or if you logout and back in again after having recieved a go-slow session?

I just came back from being away from the PC for a good three hours and it had utterly frozen, no way to wake it except the ultimate reboot. I also hadn't been using Deluge. However, after the reboot there was no 60-second delay this time, so who knows what's going on. Nothing worse that an infrequent problem that's hard to reproduce It may not even be KDE's fault, either. Who can say.

I suspect this issue was related to the D-Bus session bus, and communication issues with it.