[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #10 from Zamundaaa --- yes, please do report it to Mesa. Other compositors have different renderer architectures, use other buffer formats (10 bit per color with KWin vs 8 bit per color with others), different effects and so on and will trigger different driver code paths and thus different driver bugs than KWin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #9 from airisama...@gmail.com --- ? but I feel like it's more about the way the driver is used since gnome, sway and cinnamon has almost no graphical glitches so maybe reporting there is not the right move although it kinda of gets better every new version of mesa so, to clarify you line of thought, you just use their api's and expect it to work? if yes then maybe I should report it there -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #8 from Zamundaaa --- Okay. In case that doesn't exist yet, I'd still recommend you to make a bug report about the driver issue you have problems with here: https://gitlab.freedesktop.org/mesa/mesa/-/issues -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #7 from airisama...@gmail.com --- anyway don't sweat about this and just make sure the MESA_LOADER_DRIVER_OVERRIDE=llvmpipe env still works on future updates. it's not a big deal -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #6 from airisama...@gmail.com --- because of the graphical glitches if I recall correctly the output says it ran out shaders or instructions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #5 from Zamundaaa --- What do you mean with "sometimes you just have to switch to llvmpipe"? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #4 from airisama...@gmail.com --- yeah but on 3rd gen intel gpu sometimes you just have to switch to llvmpipe not having a clear way to do so like on cinammon is a pain. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #3 from Zamundaaa --- What do you mean, "llvmpipe trick"? If hardware acceleration isn't available on the kms node, Mesa automatically uses llvmpipe? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #2 from airisama...@gmail.com --- then how are you supposed to deal with things like sway refusing to run because llvmpipe is not a file there is pixman renderer but are we not going to make a universal way for software rendering? I am 4 year linux user but I just found that llvmpipe trick a few months ago and it wasn't on arch wiki or anything like that I dont't really remember but maybe stack overflow or reddit. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Zamundaaa --- That sounds like KWin is working fine, but plasmashell doesn't start. Which is the same situation as you have on Gnome, and also expected, since kms_swrast tries to allocate dumb buffers for rendering, which only KWin has permissions to do. Because of that there is no point in running the session with kms_swrast. It's simply not suitable for that purpose. -- You are receiving this mail because: You are watching all bug changes.
