https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #53 from SP ---
(In reply to Zamundaaa from comment #44)
> The only suspicious thing I can see here is that in some areas of the log
> there's commits without any pipelines printed:
> > kwin_wayland_drm: committing pipelines
> >
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #52 from Zamundaaa ---
Git commit 6e41d7288a7032a2479d72287dfd8794d761eb87 by Xaver Hugl.
Committed on 21/03/2022 at 21:10.
Pushed by zamundaaa into branch 'Plasma/5.24'.
backends/drm: set max bpc in DrmPipeline
If it's only set in
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #51 from SP ---
(In reply to SP from comment #50)
> > 2. if you uninstall xf86-video-amdgpu, reboot and let the default Xorg
> > driver take over, which uses the same driver interface as kwin_wayland, do
> > sddm and the Plasma X11 session
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #50 from SP ---
> 2. if you uninstall xf86-video-amdgpu, reboot and let the default Xorg
> driver take over, which uses the same driver interface as kwin_wayland, do
> sddm and the Plasma X11 session start exhibiting broken behavior as
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #49 from SP ---
Created attachment 147650
--> https://bugs.kde.org/attachment.cgi?id=147650=edit
drm-info of both monitors active but mirroring the display of only one
@Zamudaaa I ran drm_info again on broken sessions and they are the
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #48 from Zamundaaa ---
Git commit 7384405add47be4f81faef66f364bffc9c710349 by Xaver Hugl.
Committed on 21/03/2022 at 13:33.
Pushed by zamundaaa into branch 'master'.
backends/drm: set max bpc in DrmPipeline
If it's only set in
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #47 from Zamundaaa ---
I did find another difference, which is that the maximum bit depth the driver
is allowed to use was set to 8 in the broken session, instead of 16. I doubt
that it's the cause of your problems as it's what's used on
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #46 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin/-/merge_requests/2165
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #45 from SP ---
Created attachment 147632
--> https://bugs.kde.org/attachment.cgi?id=147632=edit
Tar containing three text files results of drm_info
@Zamundaaa I have attached drm_info_reports,tgz which contains three text
files:
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #44 from Zamundaaa ---
The only suspicious thing I can see here is that in some areas of the log
there's commits without any pipelines printed:
> kwin_wayland_drm: committing pipelines
> kwin_wayland_drm: (list done)
but the rest of the log
https://bugs.kde.org/show_bug.cgi?id=448220
Dennis Schridde changed:
What|Removed |Added
CC||dennis.schri...@freiheit.co
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #43 from SP ---
Created attachment 147482
--> https://bugs.kde.org/attachment.cgi?id=147482=edit
compressed journalctl log
I downloaded kwin from git a second time and reapplied the patchfile ran cmake
etc - rebooted with only one
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #42 from SP ---
(In reply to Zamundaaa from comment #39)
> Tbh I don't know a thing about how to build patched packages for rpm based
> distros either.
> For building and installing directly though,
> git clone
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #41 from SP ---
Created attachment 147473
--> https://bugs.kde.org/attachment.cgi?id=147473=edit
log of journalctl --boot 0 | grep kwin_wayland_drm
Here is the result of journalctl --boot 0 | grep kwin_wayland_drm >
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #40 from SP ---
(In reply to Zamundaaa from comment #39)
> Tbh I don't know a thing about how to build patched packages for rpm based
> distros either.
> For building and installing directly though,
> git clone
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #39 from Zamundaaa ---
Tbh I don't know a thing about how to build patched packages for rpm based
distros either.
For building and installing directly though,
git clone https://invent.kde.org/plasma/kwin.git --branch Plasma/5.24
cd kwin
git
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #38 from SP ---
(In reply to Zamundaaa from comment #37)
> Created attachment 147448 [details]
> very verbose logging
>
> Sigh, Dolphin hid the ".local" folder in the archive...
> Looking at the configs, they're exactly the same :/
>
>
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #37 from Zamundaaa ---
Created attachment 147448
--> https://bugs.kde.org/attachment.cgi?id=147448=edit
very verbose logging
Sigh, Dolphin hid the ".local" folder in the archive...
Looking at the configs, they're exactly the same :/
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #36 from SP ---
Possibly related bug 450871 KDE Plasma Multi-Monitor BUG - No Video Output on
one Monitor (No Output Signal) & Display Issue on other monitor after update to
5.24.2
https://bugs.kde.org/show_bug.cgi?id=450871
--
You are
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #35 from SP ---
(In reply to Zamundaaa from comment #34)
> (In reply to SP from comment #29)
> > Created attachment 147380 [details]
> > Files in ./local/share/kscreen
> >
> > Files generated in ./local/share/kscreen after directory was
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #34 from Zamundaaa ---
(In reply to SP from comment #29)
> Created attachment 147380 [details]
> Files in ./local/share/kscreen
>
> Files generated in ./local/share/kscreen after directory was removed and
> computer rebooted
That archive
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #33 from SP ---
On my other computer with almost identical hardware, OS and updates both
monitors remained powered on after login to KDE after first boot. This is not
always the case.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
Version|5.24.2 |5.24.3
--- Comment #32 from SP ---
It took more than
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #31 from SP ---
(In reply to SP from comment #30)
> (In reply to Zamundaaa from comment #28)
> > The output of the script directly is not useful, only the files that it
> > generates are.
> >
> > > Did so but it makes no difference
> > ok,
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #30 from SP ---
(In reply to Zamundaaa from comment #28)
> The output of the script directly is not useful, only the files that it
> generates are.
>
> > Did so but it makes no difference
> ok, that should more or less exclude KWin not
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #29 from SP ---
Created attachment 147380
--> https://bugs.kde.org/attachment.cgi?id=147380=edit
Files in ./local/share/kscreen
Files generated in ./local/share/kscreen after directory was removed and
computer rebooted
--
You are
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #28 from Zamundaaa ---
The output of the script directly is not useful, only the files that it
generates are.
> Did so but it makes no difference
ok, that should more or less exclude KWin not being able to set up the
displays.
Something
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #27 from SP ---
> > One thing you could try as a workaround is forcing the legacy driver mode,
> > by putting KWIN_DRM_NO_AMS=1 into /etc/environment and rebooting
Did so but it makes no difference
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #26 from SP ---
(In reply to Zamundaaa from comment #19)
> As they make a difference, could you upload the configuration files?
>
> Your dmesg output doesn't tell that anything is wrong at all :/
> Can you try getting that output with
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #25 from SP ---
Created attachment 147374
--> https://bugs.kde.org/attachment.cgi?id=147374=edit
Output of script drm-debug
The output of script drm-debug
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #24 from SP ---
Created attachment 147372
--> https://bugs.kde.org/attachment.cgi?id=147372=edit
tar director of .local/share/kscreen
Attached is the compressed directory ".local/share/kscreen". In a previous
experiment I had removed
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #23 from SP ---
(In reply to Zamundaaa from comment #19)
> As they make a difference, could you upload the configuration files?
>
> Your dmesg output doesn't tell that anything is wrong at all :/
> Can you try getting that output with
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #22 from SP ---
@ZamundaaaI have attached to outputs of "journalctl --boot 0 | grep
kwin_wayland_drm" - one with only one monitor display powered on after login
from SDDM to KDE and the other with both monitors remaining powered on after
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #21 from SP ---
Created attachment 147371
--> https://bugs.kde.org/attachment.cgi?id=147371=edit
drm-dmesg log with both monitors powered on after login to KDE
Output of journalctl --boot 0 | grep kwin_wayland_drm with both monitors
https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
Attachment #147010|0 |1
is obsolete||
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #19 from Zamundaaa ---
As they make a difference, could you upload the configuration files?
Your dmesg output doesn't tell that anything is wrong at all :/
Can you try getting that output with kernel 5.16 again? On my PC there is a
pretty
https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
Version|5.23.4 |5.24.2
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #18 from SP ---
Following an update of mesa libraries yesterday it is taking numerous reboots
to be able to login to a KDE Plasma Wayland session with both monitors powered
on. Incredibly frustrating. Is it possible to configure the
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #17 from SP ---
I suspect this has something to do with the way the files in
./local/share/kscreen are addressed.
I experimented:
1. Moving all files and the output directory in kscreen to a backup directory
and rebooting. Result - only
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #16 from SP ---
Does anyone have further suggestions on this bug? It is very erratic. After
some updates it appears to vanish - with both monitors powered on after logging
into a desktop session from SDDM. Then after a few days it
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #15 from SP ---
(In reply to Zamundaaa from comment #13)
> Doesn't matter. It'll do its thing on the tty, no running sessions are
> affected
ran your script - thanks. Could it be this?
dce110_link_encoder_construct: Failed to get
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #14 from SP ---
Created attachment 147076
--> https://bugs.kde.org/attachment.cgi?id=147076=edit
dmesg-drm-debug.log
Attached is the dmesg-drm-debug.log requested by @Zamundaaa
--
You are receiving this mail because:
You are watching
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=448220
--- Comment #12 from SP ---
Just to be clear - should I run the script from a tty before logging in with
SDDM or after?
(In reply to Zamundaaa from comment #11)
> Okay, so KWin fails to find a configuration that works with both monitors...
> I don't
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 created
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #10 from SP ---
Created attachment 147051
--> https://bugs.kde.org/attachment.cgi?id=147051=edit
Additional output from login to wayland session
The output from logging into a wayland session today has more information than
the previous
https://bugs.kde.org/show_bug.cgi?id=448220
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #9 from SP ---
There also appears to be no difference with the output of kwin_wayland_drm
taken after logging in to Wayland KDE with only one monitor powered on and
second (after reboot) with both monitors powered on after logging in from
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #8 from SP ---
(In reply to SP from comment #7)
> (In reply to Zamundaaa from comment #5)
> > Please enable debug logging and upload a log from when you log in and KWin
> > fails to enable the outputs correctly. Then we can see if it's
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #7 from SP ---
(In reply to Zamundaaa from comment #5)
> Please enable debug logging and upload a log from when you log in and KWin
> fails to enable the outputs correctly. Then we can see if it's KWins fault,
> if KScreen is acting up or
https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
CC||scp.stj...@gmail.com
--- Comment #6 from SP ---
Created
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=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
SP changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #2 from SP ---
@Vlad Zahorodnii Thanks - good to know that it is resolved in the next release.
I will wait until February for the finished release. Cannot run beta or
downgrade on these production machines.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=448220
Vlad Zahorodnii changed:
What|Removed |Added
Resolution|--- |WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
Keywords||accessibility, multiscreen,
|
58 matches
Mail list logo
