Hi.

First timer here.
After about 2 years of happily (VERY HAPPILY) using kubuntu I am facing a wall.
My company has changed the network, now we use a proxy with user name and password authentication. I get a "blabla@blabla.com" username for that proxy.

Firefox configuration was easy and works ok.
Configuring system proxy is a nightmare because of the "@" in the user name. I have try to escape it several ways and in several files but still no success.

The point is that plasma freezes when the network is connected
The freezes last for about 5 minutes, then works for about 1 minute, and then freezes again. If I pull the network cable, everything works ok again.

By freeze I mean that the applications still work (I can still work with firefox, konsole, gvim, etc) but I cannot switch between them because alt-tab and the panels do not work, you can see the panels but when you click on them, they do nothing until the freeze ends.


I have try disabling the update manager notifications (I though maybe it was tring to connect somewhere).

Please, help.

Alt + Tab is provided by KWin while the panel is provided by Plasma Desktop. While Plasma Desktop could be frozen due to a badly behaving applet, it should not be possible for this to affect KWin - which should have no reason to engage in network access.

The only way something could affect both Plasma Desktop and KWin is if it were a common process which they both interact with. The most likely candidate for this is KDE Daemon (kded4).

If you have a operational Konsole window, can you check if running "qdbus" and "qdbus org.kde.kded" yields workable responses during one of these freezes? (It should be virtually instant).

bcooksley wrote:Alt + Tab is provided by KWin while the panel is provided by Plasma Desktop. While Plasma Desktop could be frozen due to a badly behaving applet, it should not be possible for this to affect KWin - which should have no reason to engage in network access.

The only way something could affect both Plasma Desktop and KWin is if it were a common process which they both interact with. The most likely candidate for this is KDE Daemon (kded4).

If you have a operational Konsole window, can you check if running "qdbus" and "qdbus org.kde.kded" yields workable responses during one of these freezes? (It should be virtually instant).

Thanks for the comment bcooksley.

You are right, most of the times alt+tab still works, but the panels dont.
Now, I am on holidays so I cannot execute the test, but as soon as I get back to work, I will let you know.