Bug 493755

Summary: Wayland is extremely laggy
Product: [Plasma] plasmashell Reporter: thingone314
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WAITINGFORINFO    
Severity: critical CC: francisco278herrera, kde, kde, kdedev
Priority: NOR    
Version First Reported In: master   
Target Milestone: 1.0   
Platform: Solus   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description thingone314 2024-09-27 21:40:52 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
Wayland is extremely buggy and colors glitch over the screen, it's unusuable

STEPS TO REPRODUCE
1. Use wayland
2. Log in
3. The desktop environment doesn't work

OBSERVED RESULT
The desktop environment not working

EXPECTED RESULT
The desktop environment to work

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Latest
KDE Plasma Version: Latest
KDE Frameworks Version: Latest
Qt Version: Latest

ADDITIONAL INFORMATION
My laptop is an Acer Chromebook 315 (Gemini Lake) Blorb
Comment 1 thingone314 2024-09-27 21:50:19 UTC
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.8-arch1-1 (64 bit)
Comment 2 Francisco H 2024-09-28 06:40:45 UTC
Does it also happen if you use Gnome on Wayland? What distro is it, and what version of that distro are you using?
Comment 3 Francisco H 2024-09-28 06:48:05 UTC
Sorry, I didn't notice you are using Arch. You don't have any issues using X instead of Wayland right?
Comment 4 TraceyC 2024-09-30 14:46:30 UTC
Waiting for reply
Comment 5 thingone314 2024-10-02 20:22:13 UTC
No, just on x11 the taskbar doesn't show up. I already reported that in another bug.
Comment 6 TraceyC 2024-10-03 19:35:30 UTC
Resetting status since the question was answered
Comment 7 David Edmundson 2024-10-16 15:31:18 UTC
This report is too vague to be actionable in the current state.