You are not logged in.
Hello,
I have 2 installations of Arch, One using Cinnamon, the other with LXDE. LXDE was basically cloned from the Cinnamon version and then Cinnamon and Gnome were removed and LXDE was installed. Therefore the guts of the systems are both the same.
I am switching between these two systems and noticed one problem with LXDE. When I do disk heavy operations, like copying of large files, this does block my DE, so it apears to be frozen for a couple of seconds and then it reacts again. This does happen every few seconds and it is super annoying.
It does not happen on the Cinnamon installation.
I have no idea, where to look or what to do about it so if anyone can point me in a direction, I would be grateful. Thanks.
Last edited by Raqua (2013-06-15 23:40:04)
Offline
So, if I understand you right, no messages pop up in your journal while that happens (p.e. kernel complaining about io stuff)?
What do top / iotop say during those freezes?
Does it happen if you use the terminal or just with your file manager / other GUIs?
Are you sure this is an Issue with lxde related or could it be the hardware of a second machine in case you are using 2 different ones (you could try swapping the harddisks - also installing xfce to compare)?
The only times I remember a system freezing like that were related to
a) pulseaudio
or b) smbclient / gvfs problems
Offline
I tried to get some iostat a top info on this, but I was not able to replicate the issue. I will try to get it next time it occurs.
Offline
It is happening again. There is no significant load involved during that and iotop shows that all writes stop, then after a while, it starts writing and my de starts responding again.
It is propably worth mentioning that I do not have pulseaudio installed, do not use samba (although I have in on my system because it was pulled as a dependency)
Offline
It shouldn't be a LXDE related - rather more low level problem. If nothing in logs or iostat as whoops suggested you can try to use another kernel. Sometimes new kernel versions make some "surprises" on different machines. I would try one from LTS and another e.g. pre-compiled linux-pf (as they are quite different). It can also be just some hardware issue - eg. broken ram or hd and now it is visible.
Last edited by nbvcxz (2013-06-29 10:20:41)
Lenovo G50 | LXQT-git | compton | conky
Offline
Well, it should not be related, but it is. If you read my initial post, I have two installations on the same machine with different DE. Kernel is the same and one does, other not have this problem.
Offline
raqua, what command/which program are you using to do those copy operations ?
does the problem also happen if you copy with a different command/program ?
example :
copy with pcmanfm (lxde default filemanager) -- problems
copy from commandine with cp -- no problems
In this case the problem would be with pcmanfm.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I was using combinations of methods, rsync, cp and also krusader.
Offline