Registered Member
|
hi,
during the last days, I hunted down an annoying behavior of the my plasma desktop: during network-connection-problems it freezes completely. it boiled down to the SOHO-plasmoid not beeing able to connect to it's servers (OT: they are ALL offline at the moment, because NASA don't want us to see what's going on) during the update & timeout phase, my desktop was frozen for 3 min. every 5 min.!!!! logged in the .xsession-errors: > Failed to get chart. <urlopen error timed out>Updating... > Failed to get chart. <urlopen error timed out>Updating... > Failed to get chart. <urlopen error timed out>Updating... > Failed to get chart. <urlopen error timed out>Updating... > Failed to get chart. <urlopen error timed out>Updating... > Failed to get chart. <urlopen error timed out>Updating... > Failed to get chart. <urlopen error timed out>Updating... > Failed to get chart. <urlopen error timed out>Updating... > Failed to get chart. <urlopen error timed out>Updating... > Failed to get chart. <urlopen error timed out>Updating... > Failed to get chart. <urlopen error timed out>Updating... > Failed to get chart. <urlopen error timed out>Updating... after removing all six soho-plasmoids from the desktop-activity, I still had these freezes. double checked with xsession-errors, there had been still 6 failures (not 12 like before) logged, every 5 minutes! I found leftovers from the soho-plugin in the ~/.kde/share/configplasma-desktop-appletsrc (attached). I can't tell how the config got corrupted, but during the last half year - following the debian-testing updates towards 4.8.4, it corrupted/scrambled my desktop & activities more than one time during updates! and I was forced to start twice with a empty ~/.kde. what a pain! so at the bottom line: there are 2 BUGS: 1. plasma-desktop should not freeze on failed plasmoid aka: Failed to get chart. <urlopen error timed out>Updating... freezes the complete plasma-desktop 2. ~/.kde/share/configplasma-desktop-appletsrc gets corrupted plasma-desktop 4:4.8.4-2 debian testing for me, it's definitely a design flaw, to allow a plasmoid/add-on (or any part of a desktop-system) to freeze the desktop every 5 min! and my 2 cents rant: your users and reputation should be worth, makeing a real stable version, bevor thinking of 5.0 and releasing unstable software to the public - again. (this is M$-behavior, not Linux!) If you wouldn't have created THE BEST LINUX-Desktop, you would have lost much more user, next to your reputation. rant off please adapt the debian paradigma: it's ready, when it's ready! cheers günter
@reini, sure, codetags - there are
Last edited by chymian on Mon Jul 02, 2012 4:25 pm, edited 1 time in total.
|
Registered Member
|
Could you at the very least wrap your full-quoted configs in code tags so that the reader isn't forced to scroll through that stuff in hopes of finding any more useful content? I know what you mean, though. I've experienced this myself, and it makes plasma-desktop quite unusable. |
Administrator
|
You should post a bug on bugs.kde.org along with the corrupted configuration that causes the issue. Otherwise, given the magnitude of corner cases that can happen, no one of the developers may be able to encounter it him/herself.
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
Actually, the desktop hang bug is pretty easy to reproduce:
During the KDE start, there will be at least one very noticable hang of the entire plasma-desktop, while everything else still works. The one tricky part is that KDE needs to think that it's online. Otherwise, no connection attempt is made and no hanging occurs. (Fortunately, the online/offline detection is terribly unreliable, so there should be a way to trick it if necessary.) Just for the record, I don't have any corrupt config files that I know about - I'm simply hitting the design flaw where unstable plasmoids can crash/hang the entire plasma-desktop. |
Administrator
|
If the hang is caused by network connection, then it's a bug in the plasmoid because it uses somehow synchronous connections rather than asynchronous (and thus freezes Plasma, since it runs in the same process). Please indeed file a bug on bugs.kde.org.
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
I've opend the two bugs: Bug 303105 - widget-SOHO: hangs plasma on lost network-connection against plasma. since there was no widget-soho component-entry, I opend it against general - correct? Bug 303106 - PLASMA corrupted ~/.kde/share/configplasma-desktop-appletsrc - System hangs against plasma-desktop. |
Registered Member
|
after staring over with a new ~/.kde
the same behavior shows up on weak network connection, or changing the wlan network. ergo: has nothing to do with a corrupt config. I can reproduce: having wicd connected to a wlan, only a rescan hangs the desktop same with trying to connect to another wlan. |
Administrator
|
In this case the hang is due to an attempt of network connection. Can you check the following:
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
hello einar, thx for your reply & interest in this case: Show events was turned on. turned it off and will trace behavior widgets are:
I'm not using plugin newspaper, so it must be a leftover from a try and in the moment, I change wlan, the desktop blocks for a "endless" minute - or so. note: just in case this is relevant – since I started over with a new config, there is no more KDEPIM involved. |
Registered Member
|
and in case that helps, here is the relevant part of the syslog during "block while changing wlan" time.
activated change of wlans at the first "date" command. 19:03:25 desktop was blocking up till second "date" command. 19:04:13 both wlans are availlable with 55 - 65% connection-strength.
|
Registered Member
|
I do not know how the wicd plasmoid works, but it is using synchronous dbus calls when scanning then it may block the entire desktop.
Update: I have just checked wicd-kde plasmoid and it indeed does synchronous dbus calls when scanning, so that is the problem.
Software engineer at Petrobrás http://www.petrobras.com.br/en/about-us/
KDE's Network Management maintainer |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]