(Plasma dev here.) I don't think it's something the user is "doing". A crash is never the user's fault.

I will say it's atypical though. We measure session uptimes in months. There is probably a very specific cause that can be addressed or mitigated.

▲

lifetimerubyist 4 days ago | parent | next [-]

If it means anything, I always make sure to send in a report when it crashes.

I use Opensuse tumbleweed and update compulsively so I should have the newest package versions with all of the latest fixes too.

▲

small_scombrus 4 days ago | parent [-]

Not to it works for me, but I'm on tumbleweed and can't say I'm even crashing once a week

	▲	yjftsjthsd-h 3 days ago \| parent [-]
		I'll do you one better: I daily-drive Kalpa (so effectively tumbleweed packages) and I can't recall it ever crashing.

▲

com2kid 4 days ago | parent | prev | next [-]

Plasma doesn't crash for me but it definitely bugs out and I need to log out and log back in to fix things.

That said I'm running a shader as my desktop wall paper on Nvidia drivers so I don't feel like any of my complaints are all that justified. :D

	▲	dpacmittal 3 days ago \| parent [-]
		Have you tried killing plasmashell and restarting it? That way you won't have to close your apps and logout

▲

addy34 4 days ago | parent | prev | next [-]

I'm guessing this doesn't capture manual restarts? I have the same experience as the commenter below: Plasma requires a restart a few times per day for me, as the panels disappear and one monitor's (of two) desktop goes black - usually after wake from sleep. This occurs on both machines that I run it on (only common component is Radeon graphics).

That said, it's a single command and not a big deal, and it's a great DE, so thanks for your work.

▲

tonyhart7 4 days ago | parent | prev [-]

could you fix when ram is full and DE would always hang/freeze in there?????

(rust analyzer and java eat all my ram)