https://bugs.kde.org/show_bug.cgi?id=472676
Zamundaaa changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #5 from ist...@gmail.com ---
Created attachment 160745
--> https://bugs.kde.org/attachment.cgi?id=160745&action=edit
dmesg-drm-debug.log
Okay, im not sure if i did it right, since the script described in the link
seems hard to execute with
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #6 from ist...@gmail.com ---
oh, after running the dmesg -w command i also tabbed back into kde moved the
mouse around abit, in that buggy state thingy, shown in the screenshot
--
You are receiving this mail because:
You are watching all bu
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #7 from ist...@gmail.com ---
Created attachment 160746
--> https://bugs.kde.org/attachment.cgi?id=160746&action=edit
kwin-drm-debug.tmp
i tried to do
systemctl stop display-manager.service
and then the
kwin_wayland > kwin-drm-debug.tmp
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #8 from ist...@gmail.com ---
I've tested gnome out, and it seems to have similarly problem, not exactly the
same, with the trailing mouse, but certainly not a functioning desktop either
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #9 from Zamundaaa ---
That is already very useful, and the problem is visible in the log - the driver
claims the output needs a modeset. It seems to be missing the cause though;
could you record the log again, but this time start recording b
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #10 from ist...@gmail.com ---
Created attachment 160797
--> https://bugs.kde.org/attachment.cgi?id=160797&action=edit
drm-debug.20230807.log
What i did
logged out out kde to login screen.
ctrl alt to tty 1, run the
echo 0x1FF | sudo tee
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #11 from ist...@gmail.com ---
probably not relevant, but i dont know
part of my configuration.nix file, i have cut it down to what seems to be
relevant to me atleast to either nvidia or kde/plasma, if it turns out to be a
nixos problem, i'll
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #12 from ist...@gmail.com ---
Created attachment 160856
--> https://bugs.kde.org/attachment.cgi?id=160856&action=edit
drm-debug.20230809.log
Was a big update thingy, running plasma 5.27.7 now, not sure if kwin also got
updated, but new drm
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #13 from ist...@gmail.com ---
Created attachment 160857
--> https://bugs.kde.org/attachment.cgi?id=160857&action=edit
screenshot of display after boot, with window moved around abit
if you ignore all the flickering stuff that's everything
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #14 from Zamundaaa ---
Okay, the original issue is gone.
What happens if you kill plasmashell when you see these glitches?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #15 from ist...@gmail.com ---
What i did, reboot so i had a clean start, at login screen ctrl alt to tty 1
run
echo 0x1FF | sudo tee /sys/module/drm/parameters/debug
sudo dmesg -w | grep drm > dmesg-drm-debug.log
then back into kde/plasma p
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #16 from Zamundaaa ---
The dmesg log is not needed for this.
To kill plasmashell in the running session (so that we can exclude potential
issues being triggered by tty switching), you can just use ctrl+meta+esc and
click on the panel.
--
Y
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #17 from ist...@gmail.com ---
Okay, so what i did reboot to have clean slate kinda thing, login using
wayland, opened firefox i have something open after the sleep... slept pc,
waited abit, woke again.
first i tried the ctrl meta escape beca
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #18 from ist...@gmail.com ---
i think i wrote that badly, first time after ctrl meta escape on secondary
monitor, primary screen worked as i would expect, firefox was responsive, no
glitching when moving it around, but that was all. Secondary
https://bugs.kde.org/show_bug.cgi?id=472676
Zamundaaa changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #20 from ist...@gmail.com ---
https://www.youtube.com/watch?v=W_Dwz3nMyyQ
took video of it coming up from boot, sleep, then wake, and then finally the
ctrl meta escape kill plasma thingy
this is with nvidia-persistenced installed, i think c
https://bugs.kde.org/show_bug.cgi?id=472676
Zamundaaa changed:
What|Removed |Added
CC||knd...@outlook.com
--- Comment #21 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #22 from ist...@gmail.com ---
I've tested without nvidia open (no idea what that is) now, and same issue,
both with nvidia persistenced and without, although pc comes up from sleep a
lot faster without nvidia open. No idea if this makes any s
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #23 from ist...@gmail.com ---
(In reply to Zamundaaa from comment #19)
> hmm, that is unexpected, it suggests that not all Plasma desktop windows get
> closed... It does confirm what's happening though - plasmashell gets
> corrupted by the NV
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #1 from ist...@gmail.com ---
Created attachment 160546
--> https://bugs.kde.org/attachment.cgi?id=160546&action=edit
drm_info
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #2 from ist...@gmail.com ---
Created attachment 160547
--> https://bugs.kde.org/attachment.cgi?id=160547&action=edit
image of how the error looks on wake
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472676
--- Comment #3 from ist...@gmail.com ---
Created attachment 160548
--> https://bugs.kde.org/attachment.cgi?id=160548&action=edit
neofetch, not sure if it matters? but more information is better i guess
--
You are receiving this mail because:
You are
23 matches
Mail list logo
