Siduction Forum

Siduction Forum => Software - Support => Thema gestartet von: Lanzi in 2016/09/07, 10:44:38

Titel: Plasma Abstürze
Beitrag von: Lanzi in 2016/09/07, 10:44:38
Habe seit einiger Zeit gelegentlich Abstürze von Plasma, so dass der komplette Arbeitsbereich schwarz ist. offene Programme sind aber nach wie vor sichtbar und bedienbar.

Hat das noch jemand? Und vor allem, wie starte ich Plasma neu so das die offenen Programme nicht auch neu gestartet werden?


journalctl -u plasma
-- No entries --


Titel: Re: Plasma Abstürze
Beitrag von: finotti in 2016/09/07, 11:32:58
I have similar problems with my two monitor set up, although it's not clear we have the same problem... 

I made a script


kquitapp5 plasmashell ; /usr/bin/plasmashell --shut-up &


and call it with "Alt + F2", which still works for me, and it fixes the problem.  I have to do it after every log in, though.

Titel: Re: Plasma Abstürze
Beitrag von: Lanzi in 2016/09/07, 12:24:51
I also have a two Monitor-Setup.
Thanks for the script.

Works like a charm :-)
Titel: Re: Plasma Abstürze
Beitrag von: Lanzi in 2016/09/07, 14:14:11
BTW: with the script I got this errormessage a lot of times... maybe its an overflow that crashes after some time plasma



kde.systemtray: Wrong IconThemePath "~/.dropbox-dist/dropbox-lnx.x86_64-9.4.49/images" : too short or does not end with 'icons'



Titel: Re: Plasma Abstürze
Beitrag von: musca in 2016/09/07, 15:13:49
Hello,

I use default themes and have no issues with a two monitor setup.
~$ inxi -xGc0
Graphics:  Card: NVIDIA GF108 [GeForce GT 530] bus-ID: 01:00.0
           Display Server: X.Org 1.18.4 drivers: nvidia,fbdev,vesa,nouveau
           Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
           GLX Renderer: GeForce GT 530/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 361.45.18 Direct Rendering: Yes


greetings
musca
Titel: Re: Plasma Abstürze
Beitrag von: finotti in 2016/09/07, 17:51:59
I don't know what it is, but my two systems running two screens (work and home) have problems.  One of them gives me one black screen and one screen in the wrong monitor.  The other gives me two black screens.

I wonder if it could be the driver...  Both of mine are running intel cards and drivers.  Here is the one at work:


$ inxi -xGc0
Graphics:  Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 driver: intel Resolution: 1920x1200@59.95hz, 1280x1024@60.02hz
           GLX Renderer: Mesa DRI Intel Haswell Desktop GLX Version: 3.0 Mesa 12.0.2 Direct Rendering: Yes


The one at home (thorugh ssh):


$ inxi -xGc0
Graphics:  Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0
           Display Server: X.org 1.18.4 driver: intel tty size: 132x74 Advanced Data: N/A out of X


Titel: Re: Plasma Abstürze
Beitrag von: agaida in 2016/09/07, 18:13:35
@finotti - sounds like the "normal" libkscreen behaviour to be honest. It is a little bit unstable right now. No joke, we struggle with the same things in LXQt if i understand your issue right.
Titel: Re: Plasma Abstürze
Beitrag von: Lanzi in 2016/09/08, 09:41:48
I tested a bit...
I put the widget für Memoryuse on my desktop (Speicherstatus) and saw that prior to the plasmacrash my physical memory and my swapmemory were completly full (32Gbyte). So plasma crashes because ot the memoryleak.
Unfortunatly this is quite unpredictable... It always happnes when I am not working with my computer.
I will try to identify the cause.

Titel: Re: Plasma Abstürze
Beitrag von: melmarker in 2016/09/08, 20:01:26
rule of thumb - buy more memory and remove the widget
Titel: Re: Plasma Abstürze
Beitrag von: Lanzi in 2016/09/08, 23:42:24

;D ;D ;D ;D
Titel: Re: Plasma Abstürze
Beitrag von: devil in 2016/09/10, 23:22:30
I never even got close to filling up 32 GByte of RAM. But I am not working with really huge files, just hundreds of tabs and a couple virtual machines at most. That might fill 16 - 20 Gbyte, but that's it for me.
Titel: Re: Plasma Abstürze
Beitrag von: Lanzi in 2016/09/11, 15:33:07
exactly, and this happed by itself. without working on the computer. We need to wait, until I can reproduce the error.
Maybe its already gone.