https://bugs.kde.org/show_bug.cgi?id=459085
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #21 from Alexander Reinholdt ---
Cool, it works again! Even the faulty logout behavior is gone. Thanks! The only
thing I noticed is that under certain circumstances the mouse now drags a tail
behind it (minor display glitch). But I can live
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #20 from Zamundaaa ---
Looks like this is the same underlying problem as bug 459929. Can you check if
putting KWIN_FORCE_SW_CURSOR=1 into /etc/environment also works around the
issue for you?
(In reply to Alexander Reinholdt from comment
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #19 from Alexander Reinholdt ---
What I just wanted to mention - because it confuses me quite a bit - is that
when I am in the wayland session and log out, I will immediately be logged back
in without sddm asking me for my password. I guess
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #18 from Alexander Reinholdt ---
Created attachment 153359
--> https://bugs.kde.org/attachment.cgi?id=153359=edit
dmesg drm debug output
Here is the requested output.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #17 from Zamundaaa ---
We get this in a loop:
> Okt 31 14:59:45 pulse kwin_wayland[1847]: kwin_wayland_drm:
> drmModeAddFB2WithModifiers is supported on GPU "/dev/dri/card0"
> Okt 31 14:59:45 pulse kwin_wayland_wrapper[1847]: MESA-LOADER:
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #16 from Alexander Reinholdt ---
Created attachment 153357
--> https://bugs.kde.org/attachment.cgi?id=153357=edit
journalctl output with debug
Here is the output. I ran the command without sudo. If that is needed as well,
please let me
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #15 from Zamundaaa ---
There are some suspicious things in that log:
> kwin_wayland_drm: Atomic commit failed! This should never happen! Das Gerät
> oder die Ressource ist belegt
also this one repeats quite often:
> Okt 24 07:50:46 pulse
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #14 from Alexander Reinholdt ---
Created attachment 153222
--> https://bugs.kde.org/attachment.cgi?id=153222=edit
New journalctl output
journalctl output (after running kwriteconfig5 command as normal user and with
sudo)
--
You are
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #13 from Alexander Reinholdt ---
(In reply to Zamundaaa from comment #12)
> Your journalctl output is empty. Did you change the systemd boot setting? If
> so, you can re-enable it with "kwriteconfig5 --file startkderc --group
> General
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #12 from Zamundaaa ---
Your journalctl output is empty. Did you change the systemd boot setting? If
so, you can re-enable it with "kwriteconfig5 --file startkderc --group General
--key systemdBoot true"
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #11 from Alexander Reinholdt ---
Created attachment 153159
--> https://bugs.kde.org/attachment.cgi?id=153159=edit
dmesg output after running systemsettings
Collected after opening systemsettings where I was told that one display was
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #10 from Alexander Reinholdt ---
Created attachment 153158
--> https://bugs.kde.org/attachment.cgi?id=153158=edit
dmesg output
Collected directly after reboot and login into the wayland session.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #9 from Alexander Reinholdt ---
Created attachment 153157
--> https://bugs.kde.org/attachment.cgi?id=153157=edit
journalctl output
Collected directly after reboot and login into the wayland session.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #8 from Alexander Reinholdt ---
Created attachment 153156
--> https://bugs.kde.org/attachment.cgi?id=153156=edit
drm_info output
Collected directly after reboot and login into the wayland session.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=459085
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #7 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #6 from Alexander Reinholdt ---
Today, I upgraded to plasma 5.26 (Manjaro testing). The problem persists. Under
X11, fortunately, my setup works somehow (I always have to re-adjust my
settings on startup), but under Wayland, my external
https://bugs.kde.org/show_bug.cgi?id=459085
Alexander Reinholdt changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #5 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #4 from Alexander Reinholdt ---
If you need some more information, please let me know.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459085
--- Comment #3 from Alexander Reinholdt ---
I created a new test user. After logging into the account with Plasma Wayland,
it takes a few seconds and the second monitor is recognized and seems to work.
However, only the background is seen. No panel or
https://bugs.kde.org/show_bug.cgi?id=459085
Alexander Reinholdt changed:
What|Removed |Added
CC||alexander.reinholdt@kdemail
https://bugs.kde.org/show_bug.cgi?id=459085
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
23 matches
Mail list logo
