Bug 368344 - specify and check hardware requirements for the plasma 5 desktop at startup
Summary: specify and check hardware requirements for the plasma 5 desktop at startup
Status: RESOLVED DUPLICATE of bug 368275
Alias: None
Product: libplasma
Classification: Frameworks and Libraries
Component: libplasma (show other bugs)
Version: 5.24.0
Platform: Other Linux
: NOR grave
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-06 17:01 UTC by Elmar Stellnberger (AT/K)
Modified: 2016-09-19 11:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar Stellnberger (AT/K) 2016-09-06 17:01:49 UTC
Having tried to test the Plasma 5 desktop on many different machines I soon got very frustrated. On traditional i686 / Pentium 4 based systems plasma5 simply hangs producing a black screen. Even on newer hardware as my UHD-ready Core 2 Quad notebook with an NVIDIA Corporation G96GLM [Quadro FX 770M] it is largely unusable producing weird screen distortions. Finally on a relatively new intel Atombook Plasma 5 did run but was extremely slow until I disabled all desktop effects. That even though plasma5 was initially advertised to be less resource intense than plasma4 (However quite the opposite is true).
  My request would be to simply check hardware requirements at startup and exit if they are not met. That would safe unsuspecting users from frustration and testers from huge amounts of lost time. I remember it was like this for Plasma 4 which did output on a Pentium 3 system to the console that it requires SSE2 and thus a Pentium 4.

Reproducible: Always
Comment 1 Elmar Stellnberger (AT/K) 2016-09-07 07:31:07 UTC
Perhaps not just an issue of KDE5 but an issue of Mesa or any other underlying library framework; - having discovered similar issues with the newest Gnome as well as Cinnamon. Please have a look.
Comment 2 Marco Martin 2016-09-19 11:20:23 UTC
same issue as the previously reported one

*** This bug has been marked as a duplicate of bug 368275 ***