plasma desktop hangs
hi everybody, since a while now (at least a year), KDE does have the following behavior: while the WLAN-connection is stable, every thing is good. moving my laptop (i.e. to the terrasse) where it often still has a 50% signal, the pbls. begin: while it rechecks/reconnect to the wlan, plasma hangs (menues, systray, etc all frozen, kwin still is responsable, can move windows) for a minute or 2! that happens on movment and also, while I don't move the box - just out of the sky on rechecking the connection. first, I used Network-Manager + plasmoid, which often was not able to reconnect. I had to manual stop the manager, sometimes reload the module & restart the manager, then wait till KDE realises, that there is network again. after it had lost the connection once, it's keeping me asking over and over for the WLAN-secret, which was already in kwallet and too often, the only way out was to complety remove the connection and configure it new. then I moved to WICD, (for the price of loosing my comfortable VPN's setup). WICD is MUCH more stable, never asks for the password but still hangs plasma now and then. but seems to be 80% more stable. since I swapped hardware 4 weeks ago, it dosen't look like a driver/module-pbl. to me. (b43 before, iwlwifi now). I also see this on some laptops of friends, all KDE 4.4 - 4.8, wheezy. and I checked it with three different WLAN-routers - all same behavior. so, even if it's a driver-/network-pbl. the basic line here: plasma should definitly NOT freeze on a lost network connection. running on KDE-SC 4.8.4, wheezy, wicd 1.7.2.4-2, wicd-kde 0.3.0-2 kernel 3.0 ... .3.5-rc2 (all show the same behavior) all I see in the syslog is: wlan dropped connection and is trying to reconnect for a while. any hint's, how to prevent KDE from freezing? anybody sees the same behavior? and who get's the bug-report? kde for freezing?, kernel for dropping, one (or both) of the network-managers? since I didn't got an answeer on debian-user for a week, I cross post it to the kde-list. sorry for that, but I think I should have done this in the first place. update: since plasma hangs on the described network-problem quit often, it also hangs sometimes after switching activities for a minute or so. any hint, how to hunt it down? cheers, günter log starts, with unpluging my ext. HDD before I move the laptop: Jun 26 14:28:41 merkaba acpid: input device has been disconnected, fd 12 Jun 26 14:28:45 merkaba kernel: [ 3982.161109] ata5: hard resetting link Jun 26 14:28:46 merkaba kernel: [ 3982.465661] ata5: SATA link down (SStatus 0 SControl 310) Jun 26 14:28:46 merkaba kernel: [ 3982.465672] ata5.00: disabled Jun 26 14:28:46 merkaba kernel: [ 3982.476617] ata5: EH complete Jun 26 14:28:46 merkaba kernel: [ 3982.476635] ata5.00: detaching (SCSI 4:0:0:0) Jun 26 14:28:46 merkaba kernel: [ 3982.477260] sd 4:0:0:0: [sdc] Synchronizing SCSI cache Jun 26 14:28:46 merkaba kernel: [ 3982.477336] sd 4:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Jun 26 14:28:46 merkaba kernel: [ 3982.477347] sd 4:0:0:0: [sdc] Stopping disk Jun 26 14:28:46 merkaba kernel: [ 3982.477367] sd 4:0:0:0: [sdc] START_STOP FAILED Jun 26 14:28:46 merkaba kernel: [ 3982.477372] sd 4:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Jun 26 14:29:44 merkaba anacron[20062]: Anacron 2.3 started on 2012-06-26 Jun 26 14:29:44 merkaba anacron[20062]: Normal exit (0 jobs run) Jun 26 14:30:07 merkaba init: Switching to runlevel: 5 Jun 26 14:30:07 merkaba acpid: client connected from 20382[0:0] Jun 26 14:30:07 merkaba acpid: 1 client rule loaded Jun 26 14:30:07 merkaba kdm_greet[20406]: Cannot set locale. Translations will not work. Jun 26 14:30:07 merkaba kdm_greet[20406]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory Jun 26 14:33:05 merkaba kdm: :0[20520]: pam_ecryptfs: Passphrase file wrapped Jun 26 14:35:33 merkaba amd[3608]: No fs type specified (key = "/defaults", map = ""root"") Jun 26 14:35:33 merkaba amd[3608]: Unknown host: .Trash Jun 26 14:35:33 merkaba amd[3608]: No fs type specified (key = "/defaults", map = ""root"") Jun 26 14:35:33 merkaba amd[3608]: Unknown host: .Trash-1000 Jun 26 14:35:48 merkaba pulseaudio[21647]: [pulseaudio] pid.c: Daemon already running. Jun 26 14:35:48 merkaba pulseaudio[21654]: [pulseaudio] pid.c: Daemon already running. Jun 26 14:36:48 merkaba kernel: [ 4464.281193] cfg80211: Calling CRDA to update world regulatory domain Jun 26 14:36:51 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2 Jun 26 14:36:51 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium. Jun 26 14:36:51 merkaba dhclient: All rights reserved. Jun 26 14:36:51 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/ Jun 26 14:36:51 merkaba dhclient: Jun 26 14:36:52 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60 Jun 26 14:36:52 merkaba dhclient: Sendin
Re: plasma desktop hangs
On Sunday, 2012-07-01, chymian wrote: > hi everybody, > > since a while now (at least a year), KDE does have the following behavior: > > while the WLAN-connection is stable, every thing is good. > moving my laptop (i.e. to the terrasse) where it often still has a 50% > signal, the pbls. begin: > > while it rechecks/reconnect to the wlan, plasma hangs (menues, systray, etc > all frozen, kwin still is responsable, can move windows) for a minute or > 2! that happens on movment and also, while I don't move the box - just out > of the sky on rechecking the connection. > > first, I used Network-Manager + plasmoid, which often was not able to > reconnect. I had to manual stop the manager, sometimes reload the module & > restart the manager, then wait till KDE realises, that there is network > again. after it had lost the connection once, it's keeping me asking over > and over for the WLAN-secret, which was already in kwallet and too often, > the only way out was to complety remove the connection and configure it > new. > > then I moved to WICD, (for the price of loosing my comfortable VPN's > setup). WICD is MUCH more stable, never asks for the password but > still hangs plasma now and then. but seems to be 80% more stable. > > > since I swapped hardware 4 weeks ago, it dosen't look like a > driver/module-pbl. to me. (b43 before, iwlwifi now). I also see this on > some laptops of friends, all KDE 4.4 - 4.8, wheezy. and I checked it with > three different WLAN-routers - all same behavior. Maybe it is a certain applet that triggers this behavior, e.g. something that gets data from a web service? I've never had any problem with dropping network connections, neither WLAN nor mobile broadband (where this happens a lot more often, e.g. when on a train). Cheers, Kevin signature.asc Description: This is a digitally signed message part.
Re: plasma desktop hangs
Hi again, Am So, 1. Juli 2012, 15:39:43 schrieb Kevin Krammer: > On Sunday, 2012-07-01, chymian wrote: > > hi everybody, > > it seems to be, as kevin wrote: > Maybe it is a certain applet that triggers this behavior, e.g. something > that gets data from a web service? I found the following appear every 5 min in my .xsession-errors Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... which could come from my SOHO-plasmoids. and is EXACT the time, when the desktop freezes for 3 minutes. BUT: the point here: >> plasma should definitly NOT freeze on a lost network connection. or even, if a plasmoid can't update it's content! > I've never had any problem with dropping network connections, neither WLAN > nor mobile broadband (where this happens a lot more often, e.g. when on a > train). so, what's the difference? mine freezes every 5 min because of a couple of plasmoids cannot update it's self, even when I have a network-connection. aka. on a web-server-pbl. they connect to? > > Cheers, > Kevin cheers günter
BUG: plasma desktop hangs on corrupted configplasma-desktop-appletsrc
further update & workaround: 2 BUGs found. Am So, 1. Juli 2012, 16:48:13 schrieb chymian: > Hi again, > > Am So, 1. Juli 2012, 15:39:43 schrieb Kevin Krammer: > > On Sunday, 2012-07-01, chymian wrote: > > > hi everybody, > > it seems to be, as kevin wrote: > > Maybe it is a certain applet that triggers this behavior, e.g. something > > that gets data from a web service? > > I found the following appear every 5 min in my .xsession-errors > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > > which could come from my SOHO-plasmoids. > and is EXACT the time, when the desktop freezes for 3 minutes. > > BUT: the point here: > >> plasma should definitly NOT freeze on a lost network connection. > > or even, if a plasmoid can't update it's content! > > > I've never had any problem with dropping network connections, neither > > WLAN nor mobile broadband (where this happens a lot more often, e.g. > > when on a train). > > so, what's the difference? > mine freezes every 5 min because of a couple of plasmoids cannot update > it's self, even when I have a network-connection. aka. on a > web-server-pbl. they connect to? indeed, the soho-plasmoids could not connect to it's server. but even more strange: I removed all but one weather-plasmoid, which works flawlessly - and I still get the same error & behavior as before. errorlogs & desktop-freeze, but only 6 times in a row now. I checked the ~/.kde/share/configplasma-desktop-appletsrc and again, it was corrupted, which happend quite a few times in the last months. after I removed the aktiv soho-plasmoids, I found 6 leftovers in the config file. removing these in between KDE newstarts resolved the problem. corrupted config attached. do the KDE-maintainers want me to open 2 bugs on that, or do you take it from here? 1. plasma-desktop should not freeze on failed plasmoid aka: Failed to get chart. Updating... freezes plasma-desktop 2. ~/.kde/share/configplasma-desktop-appletsrc gets corrupted plasma-desktop 4:4.8.4-2 günter [ActionPlugins] LeftButton;NoModifier=applauncher MidButton;NoModifier=paste RightButton;NoModifier=contextmenu wheel:Vertical;NoModifier=switchdesktop [AppletGlobals][plasma_applet_pager] rows=2 [Containments][1] activity= activityId= desktop=-1 formfactor=2 geometry=0,-41,1600,35 immutability=1 lastDesktop=-1 lastScreen=0 location=4 plugin=panel screen=0 zvalue=0 [Containments][1][ActionPlugins] RightButton;NoModifier=contextmenu [Containments][1][Applets][15] geometry=0,3,32,32 immutability=2 plugin=simplelauncher zvalue=2 [Containments][1][Applets][15][LayoutInformation] Order=0 [Containments][1][Applets][15][Shortcuts] global= [Containments][1][Applets][3] geometry=144,3,32,32 immutability=2 plugin=org.kde.showActivityManager zvalue=0 [Containments][1][Applets][3][LayoutInformation] Order=4 [Containments][1][Applets][31] geometry=36,3,32,32 immutability=2 plugin=icon zvalue=1 [Containments][1][Applets][31][Configuration] Url=file:///usr/share/applications/iceweasel.desktop [Containments][1][Applets][31][LayoutInformation] Order=1 [Containments][1][Applets][32] geometry=108,3,32,32 immutability=2 plugin=icon zvalue=4 [Containments][1][Applets][32][Configuration] Url=file:///usr/share/applications/kde4/dolphin.desktop [Containments][1][Applets][32][LayoutInformation] Order=3 [Containments][1][Applets][4] geometry=180,3,231,32 immutability=2 plugin=pager zvalue=0 [Containments][1][Applets][4][Configuration] Share=false currentDesktopSelected=0 displayedText=2 showWindowIcons=false [Containments][1][Applets][4][LayoutInformation] Order=5 [Containments][1][Applets][5] geometry=415,3,831,32 immutability=1 plugin=tasks zvalue=1 [Containments][1][Applets][5][Configuration] Share=false forceRows=false groupWhenFull=true groupingStrategy=2 highlightWindows=false maxRows=2 showOnlyCurrentActivity=true showOnlyCurrentDesktop=false showOnlyCurrentScreen=false showOnlyMinimized=false showTooltip=true sortingStrategy=2 [Containments][1][Applets][5][Configuration][Launchers] Items=file:///usr/share/applications/virt-manager.desktop?wmClass=Virt-manager,file:///usr/share/applications/iceweasel.desktop?wmClass=Iceweasel,file:///usr/share/applications/kde4/basket.desktop?wmClass=Basket,file:///usr/share/applications/kde4/konsole.desktop?wmClass=Konsole [Containments][1][Applets][5][LayoutInformation] Order=6 [Containments][1][Applets][6] geometry=1250,3,258,32 immutability=1 plugin=systemtray zvalue=0 [Containments][1][Applets][6][Configuration] DefaultAppletsAdded=true Share=false ShowApplicationStatus=true ShowCommunications=true ShowHardware=tr
Re: plasma desktop hangs
In data domenica 1 luglio 2012 13:49:31, chymian ha scritto: > any hint's, how to prevent KDE from freezing? Package ifupdown is installed? -- Marco Valli -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201207011917.42484.ma...@bastardi.net
Re: plasma desktop hangs
On 01/07/2012 at 16:48, chymian wrote: > BUT: the point here: > >> plasma should definitly NOT freeze on a lost network connection. > > or even, if a plasmoid can't update it's content! This is probably caused by plasma design - i.e. all plasmoids run under single process. So, if one plasmoid tries to connect, it virtually hangs whole desktop for that time. This issue was discussed some time ago on planet KDE, but I can't find that post right now. I have found that brainstorm discussion from few years back: http://forum.kde.org/viewtopic.php?f=90&t=45255 It seems that rationale was: plasmoid crash causes whole desktop to crash, so we should run them in separate processes. But plasmoids don't crash that often now, so we do not have to run them in separate processes. Your case shows that there is still pretty strong reason to run plasmoids in separate processes (if only my suppositions are right). You should definitely post your findings in KDE forums - either in linked thread, or in new thread (which may get more attention). But you should not post a bug report to Debian's BTS - there is really not much that Debian's KDE packaging team can do about it. As for corrupted configplasma-desktop-appletsrc file - it would be nice if you could provide step-by-step instructions how to reproduce that. I will check on Arch Linux with KDE to ensure that this is Debian issue. As KDE packaging team recently said on that mailing list, they prefer that KDE bugs goes directly to KDE, not Debian BTS. Debian BTS is appropriate for packaging issues and things that do not happen outside Debian. -- Best regards Mirosław Zalewski -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201207020044.40863.mini...@poczta.onet.pl
