https://bugs.kde.org/show_bug.cgi?id=449958
--- Comment #1 from Zamundaaa ---
Are native Wayland applications also affected? You could for example test
Xonotic with
$ GALLIUM_HUD=fps SDL_VIDEODRIVER=wayland xonotic-sdl
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449958
--- Comment #2 from Zamundaaa ---
Or does it really only affect Vulkan applications?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449958
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=450174
Zamundaaa changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=450327
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=449331
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=449797
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #23 from
https://bugs.kde.org/show_bug.cgi?id=450358
--- Comment #7 from Zamundaaa ---
Git commit e9db27d05d7b76c8a4fc12a6f5c059680917052f by Xaver Hugl.
Committed on 18/02/2022 at 17:13.
Pushed by zamundaaa into branch 'master'.
backends/drm: ignore enabled state of outputs for the lifetime
https://bugs.kde.org/show_bug.cgi?id=450501
Zamundaaa changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=450501
Zamundaaa changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma
https://bugs.kde.org/show_bug.cgi?id=450358
--- Comment #8 from Zamundaaa ---
Git commit 29bc1173c70b2a31753c791aa60fb33ee320440a by Xaver Hugl.
Committed on 18/02/2022 at 19:50.
Pushed by zamundaaa into branch 'Plasma/5.24'.
backends/drm: ignore enabled state of outputs for the l
https://bugs.kde.org/show_bug.cgi?id=448173
Zamundaaa changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #4 from Zamundaaa ---
*** Bug 448173 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448220
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #5 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=449797
--- Comment #32 from Zamundaaa ---
510 is known to work:
https://www.reddit.com/r/linux_gaming/comments/su5dmb/kde_wayland_nvidia_issues/
Can you test putting "KWIN_DRM_USE_MODIFIERS=1" into /etc/environment, and
launching the session aga
https://bugs.kde.org/show_bug.cgi?id=449285
Zamundaaa changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=450606
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=424896
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #3 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=450511
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #3 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #11 from Zamundaaa ---
Okay, so KWin fails to find a configuration that works with both monitors... I
don't see much more useful information in that log though, we'll need drm
kernel logging to find out more.
I cre
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #13 from Zamundaaa ---
Doesn't matter. It'll do its thing on the tty, no running sessions are affected
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449878
--- Comment #3 from Zamundaaa ---
Is some kernel argument set, like amdgpu.dc=0? And are you using any
environment variables for KWin?
This sounds a lot like the legacy driver bug that
https://invent.kde.org/plasma/kwin/-/merge_requests/2019 fixes
https://bugs.kde.org/show_bug.cgi?id=450779
Zamundaaa changed:
What|Removed |Added
Ever confirmed|0 |1
CC
https://bugs.kde.org/show_bug.cgi?id=450737
--- Comment #2 from Zamundaaa ---
I'm relatively certain that the MR should fix it but could you test it to make
sure? I don't have a multi-gpu system
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450779
--- Comment #3 from Zamundaaa ---
Could you please test the MR without KWIN_DRM_PREFER_COLOR_DEPTH set and check
with drm_info which format gets used with it? The bug should've only caused 8
bit color to be used, instead of 10 bit color, there cou
https://bugs.kde.org/show_bug.cgi?id=450779
Zamundaaa changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=450737
Zamundaaa changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=454445
--- Comment #1 from Zamundaaa ---
It would indeed be nice, sadly the driver doesn't currently expose that sort of
information to us. It's a known problem and will hopefully be tackled soon™
with all the other color management stuff being
https://bugs.kde.org/show_bug.cgi?id=454433
--- Comment #1 from Zamundaaa ---
Please add
QT_LOGGING_RULES="kwin_wayland_*.debug=true"
into your /etc/environment and reboot. Then attach your monitor and
journalctl --boot 0 --user-unit plasma-kwin_wayland | grep kwin_wayland_drm
here
https://bugs.kde.org/show_bug.cgi?id=454086
--- Comment #3 from Zamundaaa ---
> kwin_wayland_drm: Failed to find a working setup for new outputs!
That is the culprit, there is however no information about why it failed.
To get more information, please execute the script from
ht
https://bugs.kde.org/show_bug.cgi?id=454387
--- Comment #1 from Zamundaaa ---
Please add
QT_LOGGING_RULES="kwin_wayland_*.debug=true"
into your /etc/environment and reboot. Then reproduce the bug and afterwards
attach the output of
journalctl --boot 0 --user-unit plasma-kwin_wayl
https://bugs.kde.org/show_bug.cgi?id=454387
--- Comment #4 from Zamundaaa ---
(In reply to Chema from comment #2)
> it does not return any result from the terminal.
Right, sorry - as you're still on 5.24 you'll need to first change the session
to use systemd boot:
kwriteconfig5 --fi
https://bugs.kde.org/show_bug.cgi?id=454433
--- Comment #6 from Zamundaaa ---
When the monitor is not detected, KWin is unable to access the GPU:
> kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
When the monitor is not detected, what does "ls /dev/dri&
https://bugs.kde.org/show_bug.cgi?id=454387
--- Comment #7 from Zamundaaa ---
The actual output detection stuff takes less than a second, but then it appears
to fail to set the mode (which should never ever happen).
Weirdly, after that it also seems to do nothing at all for an entire minute,
and
https://bugs.kde.org/show_bug.cgi?id=454086
--- Comment #6 from Zamundaaa ---
Confusingly, the drm / kernel log doesn't mention any failed commits, it should
have something like "Atomic check failed with err" in it.
Are you using some kernel boot flags like amdgpu.dc=0?
--
Yo
https://bugs.kde.org/show_bug.cgi?id=454433
--- Comment #8 from Zamundaaa ---
If you run an app on the dGPU before you connect the external monitor, does
that make a difference?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454433
--- Comment #10 from Zamundaaa ---
The problem is that KWin completely stops bothering the GPU and driver when
there's no outputs connected to it. When you're not running any apps on it
while on battery, it'll be completely shut dow
https://bugs.kde.org/show_bug.cgi?id=453864
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=454433
--- Comment #13 from Zamundaaa ---
> I also don't see any line with "kwin_wayland_core"
Oh, sorry, it's only "kwin_core". With that, you do need to adjust the
environment variable to be
QT_LOGGING_RULES="kwin_*.d
https://bugs.kde.org/show_bug.cgi?id=453860
--- Comment #12 from Zamundaaa ---
Can someone with an affected system check if the merge request makes a
difference vs git master? I'd rather not introduce the hack if not necessary
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=454433
--- Comment #15 from Zamundaaa ---
No need, I think this is a logind bug then. Can you open an issue at
https://github.com/systemd/systemd/issues about TakeDevice failing with
"Permission denied" despite KWin having the needed permissions, a
https://bugs.kde.org/show_bug.cgi?id=453860
--- Comment #14 from Zamundaaa ---
What the first merge request did is that it makes KWin reliably fall back to
rendering the cursor manually whenever using the hardware cursor fails. As you
already noticed though, this reduces performance.
The new
https://bugs.kde.org/show_bug.cgi?id=454433
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=454626
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=454527
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
CC
https://bugs.kde.org/show_bug.cgi?id=454660
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=453984
--- Comment #13 from Zamundaaa ---
The UI for it is correctly not shown - the relevant functionality does not
properly speaking exist on Wayland. Fixing that is planned, once that's done we
can enable it: https://invent.kde.org/plasma/kwin/-/issu
https://bugs.kde.org/show_bug.cgi?id=454387
--- Comment #10 from Zamundaaa ---
I'm sorry, I made a mistake: when enabling drm debug logging
> echo 0xFE | sudo tee /sys/module/drm/parameters/debug
leaves out some important messages. Can you try again with
> echo 0xFF | sudo tee /sys
https://bugs.kde.org/show_bug.cgi?id=454086
--- Comment #8 from Zamundaaa ---
Sorry, this was my mistake - the flags for which debug messages to enable was
wrong, it needs to be 0xFF instead of 0xFE. I adjusted the script accordingly.
Can you try again with the correct flags?
--
You are
https://bugs.kde.org/show_bug.cgi?id=453984
Zamundaaa changed:
What|Removed |Added
Resolution|--- |MOVED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=454902
Zamundaaa changed:
What|Removed |Added
Product|kwin|KScreen
Component|general
https://bugs.kde.org/show_bug.cgi?id=454902
--- Comment #3 from Zamundaaa ---
Can you upload the old, and the new folder for comparison?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454961
Zamundaaa changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=454961
Zamundaaa changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma
https://bugs.kde.org/show_bug.cgi?id=454755
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #3 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=454843
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=444536
Zamundaaa changed:
What|Removed |Added
CC||bizy...@zoho.com
--- Comment #8 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=454755
--- Comment #7 from Zamundaaa ---
hmm, the driver is reporting hotplugs when the screen has been turned off for a
bit. While I have never heard of it happening with eDP, it is somewhat common
with external monitors.
I think this one can be sanely
https://bugs.kde.org/show_bug.cgi?id=454755
--- Comment #8 from Zamundaaa ---
However, in the 4 seconds in between two hotplugs, I don't see KWin doing
anything... So it might not be KWin's doing after all.
Do you have the Xorg driver xf86-video-intel installed? If so, if you remove
i
https://bugs.kde.org/show_bug.cgi?id=455126
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=455261
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=455300
Zamundaaa changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=454086
Zamundaaa changed:
What|Removed |Added
CC||globalun...@disroot.org
--- Comment #12 from
https://bugs.kde.org/show_bug.cgi?id=454086
Zamundaaa changed:
What|Removed |Added
CC||andrewammerl...@gentoo.org
--- Comment #13 from
https://bugs.kde.org/show_bug.cgi?id=454086
--- Comment #15 from Zamundaaa ---
Testing that MR may also help, even though using the buffer for outputs should
fail completely (and show in the logs), I faintly remember debugging a similar
problem in the past
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=454086
--- Comment #16 from Zamundaaa ---
Git commit 34ce3dde87efef745c864b78bc1db541080552cb by Xaver Hugl.
Committed on 16/06/2022 at 15:02.
Pushed by zamundaaa into branch 'master'.
backends/drm: use GBM_BO_USE_SCANOUT when importing buffers for
https://bugs.kde.org/show_bug.cgi?id=454086
--- Comment #17 from Zamundaaa ---
Git commit 9baa2c3ee4fef11a5df92fb43fa39ba2ef141709 by Xaver Hugl.
Committed on 16/06/2022 at 20:08.
Pushed by zamundaaa into branch 'Plasma/5.25'.
backends/drm: use GBM_BO_USE_SCANOUT when importing b
https://bugs.kde.org/show_bug.cgi?id=454086
--- Comment #32 from Zamundaaa ---
Unfortunately the kernel doesn't seem to do any logging for when the buffers
are still on the wrong GPU, but this MR should finally fix the problem
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=454086
Zamundaaa changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=454086
Zamundaaa changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma
https://bugs.kde.org/show_bug.cgi?id=454086
Zamundaaa changed:
What|Removed |Added
Version Fixed In||5.25.1
--- Comment #35 from Zamundaaa ---
The fix
https://bugs.kde.org/show_bug.cgi?id=465640
Bug ID: 465640
Summary: KDevelop ignores build target paths
Classification: Applications
Product: kdevelop
Version: git master
Platform: Other
OS: Linux
Status: REPORT
https://bugs.kde.org/show_bug.cgi?id=465742
Zamundaaa changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC
https://bugs.kde.org/show_bug.cgi?id=466094
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
CC
https://bugs.kde.org/show_bug.cgi?id=465936
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
CC
https://bugs.kde.org/show_bug.cgi?id=465809
--- Comment #2 from Zamundaaa ---
Bug 452219 is more about NVidia GPUs specifically, but yeah it's most likely
the same underlying issue.
Please attach the output of drm_info
(https://gitlab.freedesktop.org/emersion/drm_info), whether or not KWin
https://bugs.kde.org/show_bug.cgi?id=466094
Zamundaaa changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=466094
Zamundaaa changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma
https://bugs.kde.org/show_bug.cgi?id=466094
--- Comment #6 from Zamundaaa ---
Git commit 4cd25cf571d5a350b5e62e612a990bfdfa934bff by Xaver Hugl.
Committed on 20/02/2023 at 21:01.
Pushed by zamundaaa into branch 'master'.
cursor: make position, hotspot and size floating point
This
https://bugs.kde.org/show_bug.cgi?id=465971
Zamundaaa changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=466227
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=466302
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #1 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=466302
Zamundaaa changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=466302
Zamundaaa changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma
https://bugs.kde.org/show_bug.cgi?id=466430
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #1 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=466430
Zamundaaa changed:
What|Removed |Added
Product|kwayland-integration|kwin
Component|general
https://bugs.kde.org/show_bug.cgi?id=409040
Zamundaaa changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=452219
Zamundaaa changed:
What|Removed |Added
CC||carlon.l...@gmail.com
--- Comment #22 from
https://bugs.kde.org/show_bug.cgi?id=452614
--- Comment #45 from Zamundaaa ---
If you select "Save displays' properties: For only this specific display
arrangement" in the display settings, does the rotation still reset?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466430
--- Comment #6 from Zamundaaa ---
In that backtrace there's a custom effect. Just to be sure that the problem
isn't binary incompatibility, can you rebuild it against the new kwin version?
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=466454
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=466633
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #2 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=466747
Zamundaaa changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=466747
Zamundaaa changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma
https://bugs.kde.org/show_bug.cgi?id=466238
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #8 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=465973
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=466238
--- Comment #11 from Zamundaaa ---
That's odd, there's not even a single relevant warning in that log. To narrow
down where to go from here, please attach the output of drm_info
(https://gitlab.freedesktop.org/emersion/drm_info)
- once befor
https://bugs.kde.org/show_bug.cgi?id=455720
Zamundaaa changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=466636
Zamundaaa changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=427060
--- Comment #35 from Zamundaaa ---
Please attach the output of
> drm_info
and
> journalctl --user-unit plasma-kwin_wayland --boot 0
from in the VM
--
You are receiving this mail because:
You are watching all bug changes.
1 - 100 of 4102 matches
Mail list logo
