https://bugs.kde.org/show_bug.cgi?id=465712
Zamundaaa changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=468715
Zamundaaa changed:
What|Removed |Added
Component|wayland-generic |platform-drm
CC
https://bugs.kde.org/show_bug.cgi?id=467138
--- Comment #15 from Zamundaaa ---
Git commit 8ca38fb328606f8a0bababea2e07b36fd775768f by Xaver Hugl.
Committed on 21/04/2023 at 15:35.
Pushed by zamundaaa into branch 'master'.
backends/drm: fix buffer orientation check for direct scanou
https://bugs.kde.org/show_bug.cgi?id=468844
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=468146
--- Comment #4 from Zamundaaa ---
What specific hardware are you using? There's
https://gitlab.freedesktop.org/drm/amd/-/issues/2516, which may be related
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468146
--- Comment #6 from Zamundaaa ---
Yes, it seems so. You can check by downgrading to Linux 6.1 or earlier
If you change the latency policy in the compositor settings to "Force smoothest
animations", does the stutter go away?
--
You are rece
https://bugs.kde.org/show_bug.cgi?id=468146
--- Comment #8 from Zamundaaa ---
Right, we changed the default in 5.27.
> Well i dunno it's kernel issue, Because on gnome 43.4 I have no issues
That's not really relevant, the upstream bug report says the same. Please test
with Linux 6
https://bugs.kde.org/show_bug.cgi?id=468146
--- Comment #10 from Zamundaaa ---
Okay, then it's a different thing from the amd bug.
Does anything change if you set the latency policy to balanced (which was the
default in 5.26)?
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=450327
--- Comment #6 from Zamundaaa ---
Please create a separate bug report for the freeze
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468895
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #1 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=468817
--- Comment #1 from Zamundaaa ---
That sounds a lot like plasmashell misbehaving. After reproducing the bug, can
you check in the kwin debug console (type "kwin" into krunner to open it), if
there's any windows called "Desktop"
https://bugs.kde.org/show_bug.cgi?id=468817
Zamundaaa changed:
What|Removed |Added
CC||aleix...@kde.org
https://bugs.kde.org/show_bug.cgi?id=468715
--- Comment #4 from Zamundaaa ---
> Could it be possible that the open source Mesa stack for example does a
> pause/resume device
It's possible that upstream kernel drivers don't signal the last pageflip
signal until the VT is swi
https://bugs.kde.org/show_bug.cgi?id=469764
Zamundaaa changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=450327
Zamundaaa changed:
What|Removed |Added
Resolution|UPSTREAM|FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=468895
Zamundaaa changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=440397
--- Comment #18 from Zamundaaa ---
Running the plasma session as root is not supported
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470334
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #2 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=470629
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #1 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=470581
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=470718
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #3 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=470718
--- Comment #6 from Zamundaaa ---
okay, so I assume the EDID of the two screens is identical, so KScreen uses the
connector name as a fallback way of identifying the monitors. Due to MST
weirdness and possibly some kernel bug, the old connectors stick
https://bugs.kde.org/show_bug.cgi?id=470746
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #2 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=470590
--- Comment #4 from Zamundaaa ---
Please attach the output of drm_info when the output isn't working correctly
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469590
--- Comment #17 from Zamundaaa ---
Please answer my question: did you have both monitors plugged in while getting
the drm_info output, or just one of them?
If you don't remember, attaching a new output of drm_info while only having one
di
https://bugs.kde.org/show_bug.cgi?id=470628
--- Comment #3 from Zamundaaa ---
The scaling mode property stays as it is, it's quite broken, at least with
amdgpu.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469590
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=470742
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #6 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=470440
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=470497
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #2 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=402858
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=464990
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=446115
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #1 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=443022
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=402857
Zamundaaa changed:
What|Removed |Added
CC||aadeshkanna28022000@gmail.c
https://bugs.kde.org/show_bug.cgi?id=470979
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #1 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=466725
Zamundaaa changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=470629
--- Comment #6 from Zamundaaa ---
> On MS Windows, when setting "IT Content = Enabled", it is probably using
> "HDMI Content Type = Graphics".
If that automatically triggers the PC mode, then this bug report shouldn't
https://bugs.kde.org/show_bug.cgi?id=470979
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=470742
--- Comment #11 from Zamundaaa ---
While it's not great, that one is expected. When there's no existing config for
a given combination of outputs, KScreen generates a completely new config from
scratch. The current logic in KWin does th
https://bugs.kde.org/show_bug.cgi?id=471089
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #1 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=468744
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #2 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=468715
Zamundaaa changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=468895
--- Comment #3 from Zamundaaa ---
There's still no GAMMA_LUT property, so I'm not sure how night color would be
related. Can you attach your full KWin log? So
> journalctl --user-unit plasma-kwin_wayland --boot 0
after causing the issue a
https://bugs.kde.org/show_bug.cgi?id=466238
--- Comment #27 from Zamundaaa ---
Do you ever get artifacts with an app in windowed mode?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466238
--- Comment #29 from Zamundaaa ---
Do you know if this has happened with native Wayland apps, or only with
Xwayland?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466238
--- Comment #31 from Zamundaaa ---
Can you describe the flicker in more detail? With KWIN_DRM_NO_DIRECT_SCANOUT=1
set, there should be no difference for native Wayland apps vs windowed, at
least on the KWin and driver side.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=466238
--- Comment #33 from Zamundaaa ---
ok, that sounds like a driver bug then. Are you using adaptive sync? If so,
does disabling that change anything?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468744
Zamundaaa changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=148902
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=107600
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=252699
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=305437
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=315855
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
CC
https://bugs.kde.org/show_bug.cgi?id=326283
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=338123
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=339484
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=311497
Zamundaaa changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
CC
https://bugs.kde.org/show_bug.cgi?id=296092
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=351122
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=466238
--- Comment #37 from Zamundaaa ---
I've seen glitches similar to that before, they were caused by sort of broken
hardware acceleration. Can you check if playing a video without hardware
acceleration triggers the glitches and/or the freeze?
--
Yo
https://bugs.kde.org/show_bug.cgi?id=440397
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=459373
Zamundaaa changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=459373
--- Comment #41 from Zamundaaa ---
Yes, there is at least one known additional issue, which will (usually) only be
between the panel and the window. Please create a separate bug report for that,
with the resolution + scale + if it happens with Wayland
https://bugs.kde.org/show_bug.cgi?id=459373
Zamundaaa changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=469623
Zamundaaa changed:
What|Removed |Added
Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org
Target Milestone
https://bugs.kde.org/show_bug.cgi?id=469745
Zamundaaa changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC
https://bugs.kde.org/show_bug.cgi?id=469707
Zamundaaa changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--- Comment #1 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=468280
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=469280
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #2 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=469818
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #2 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=469764
Zamundaaa changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=469590
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #8 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=469818
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=466454
Zamundaaa changed:
What|Removed |Added
CC||jacobstephens...@gmail.com
--- Comment #27 from
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #4 from Zamundaaa ---
Please attach the output of
> journalctl --user-unit plasma-kwin_wayland --boot 0
after running the Wayland session for a bit.
The output of drm_info (https://gitlab.freedesktop.org/emersion/drm_info) would
also
https://bugs.kde.org/show_bug.cgi?id=469353
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=469590
--- Comment #10 from Zamundaaa ---
you have simpledrm and NVidia at the same time, which might explain the
problem. Does your CPU have an integrated GPU, and did you change any kernel
boot arguments?
Can you attach the output of drm_info executed
https://bugs.kde.org/show_bug.cgi?id=469764
--- Comment #5 from Zamundaaa ---
The log doesn't contain any warnings about commits failing or anything like
that, so this is likely a driver problem. To make sure, can you enable drm
debug logging and record a dmesg log while causing the pr
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #8 from Zamundaaa ---
Okay, so KWin is using OpenGL, and not using software rendering. If you run
> udevadm monitor
are there any events being printed?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469590
--- Comment #14 from Zamundaaa ---
Did you have both monitors plugged in while getting that output, or only one?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466342
--- Comment #26 from Zamundaaa ---
if you rename or move (not delete!) the ~/.local/share/kscreen folder, does it
still happen?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469623
Zamundaaa changed:
What|Removed |Added
CC||notm...@gmail.com
Component|effects
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #10 from Zamundaaa ---
Okay, so udev events triggering stuff in KWin can be ruled out. Can you try
putting
> KWIN_DRM_PREFER_COLOR_DEPTH=24
and
> KWIN_DRM_USE_MODIFIERS=0
and
> KWIN_DRM_NO_AMS=1
into /etc/environment and see if t
https://bugs.kde.org/show_bug.cgi?id=469280
Zamundaaa changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=458291
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=459679
Zamundaaa changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=456306
Zamundaaa changed:
What|Removed |Added
CC||ken20...@ukr.net
--- Comment #6 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=459951
Zamundaaa changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=449989
Zamundaaa changed:
What|Removed |Added
CC||fischerfeli...@gmail.com
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=460118
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=459814
--- Comment #2 from Zamundaaa ---
What do you mean with
> The mouse cursor only appears on the second monitor
? Is the monitor gone from display settings and no longer usable, or is it
frozen but still detected?
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=459814
--- Comment #6 from Zamundaaa ---
Please attach the output of
> journalctl --user-unit plasma-kwin_wayland --boot 0
once the problem happens
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459908
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=459929
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=460082
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=460288
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #5 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=459778
--- Comment #12 from Zamundaaa ---
Can you check dmesg for any messages of GPU resets once the screen froze once?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456873
Zamundaaa changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=455429
--- Comment #15 from Zamundaaa ---
*** Bug 456873 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
201 - 300 of 4614 matches
Mail list logo