https://bugs.kde.org/show_bug.cgi?id=475173
Allistar changed:
What|Removed |Added
CC||allista...@gmail.com
--- Comment #10 from Allistar
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #18 from Allistar ---
If it identifies monitors by something unique (e.g. the GPU or screen number
they're on appended with the QScreen name) then it's likely that when
plasmashell starts up it will start on both xscreens which would
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #16 from Allistar ---
My fix as provided in the patch works for me but it's not a good general
purpose fix. I filter out monitors by their serial number as that's unique, but
the only easy way I could find the serial number was to add
https://bugs.kde.org/show_bug.cgi?id=454621
Allistar changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=454621
Allistar changed:
What|Removed |Added
Attachment #150133|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #13 from Allistar ---
I have tried with 5.27.4.1 (the currently stable version on Gentoo) and the
problem is still there. I have fixed this locally by modifying
plasma-workspace/shell/screenpool.cpp by telling it to ignore two of my
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #12 from Allistar ---
Hi all. 5.27 is now available on Gentoo so I'm installing that from source.
I'll update here if it now handles multiple xscreens properly or not when it's
completed.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #10 from Allistar ---
Thanks. I'll wait for my distro (Gentoo) to stabilise Plasma 5.27.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #233 from Allistar ---
I face a separate issue caused by Plasma identifying monitors by their xrandr
connector name. Plasma seems to assume that these are unique in a system but
they aren't. In my case I have 6 monitors across 2 GPUs
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #198 from Allistar ---
I know there's a bug in the way ScreenConnectors works because of how the
screens are identified. Screen names aren't unique as they're identified by
xrandr output name. My ScreenConnectors looks like
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #8 from Allistar ---
(In reply to Andreas Sturmlechner from comment #7)
> Please create an MR over at https://invent.kde.org/plasma/plasma-workspace
> instead of attaching here, it will get much more attention.
Thanks. My patch fi
https://bugs.kde.org/show_bug.cgi?id=290424
Allistar changed:
What|Removed |Added
CC||allista...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #6 from Allistar ---
Comment on attachment 150133
--> https://bugs.kde.org/attachment.cgi?id=150133
Allows monitors to be blacklisted from Plasma by their serial number
Note: this patch is from a gentoo system and is made for
pla
https://bugs.kde.org/show_bug.cgi?id=454621
Allistar changed:
What|Removed |Added
CC||allista...@gmail.com
--- Comment #5 from Allistar
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #4 from Allistar ---
I have identified that this issue is caused by the change between 5.23 and 5.24
in screenpool.cpp ScreenPool::load.
I have fixed this with a patch which allows me to blacklist monitors from
Plasma by their serial
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #3 from Allistar ---
Could this be due to this code in ScreenPool::load
// Populate allthe screen based on what's connected at startup
for (QScreen *screen : qGuiApp->screens()) {
// On some devices QGuiApp::screenAd
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #2 from Allistar ---
I wonder if this is related to one of these issues:
https://bugreports.qt.io/browse/QTBUG-101203
https://codereview.qt-project.org/c/qt/qtbase/+/412385
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #1 from Allistar ---
I suspect this may be related to how [ScreenConnectors] work. In my
.config/plasmashellrc file I have this:
[ScreenConnectors]
0=DVI-I-1
1=HDMI-1
2=DVI-D-0
3=HDMI-0
When running "xrandr --listmonitors"
https://bugs.kde.org/show_bug.cgi?id=454621
Bug ID: 454621
Summary: Plasmashell doesn't start on all monitors in a multi
xscreen environment
Product: plasmashell
Version: master
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #174 from Allistar ---
I'm running Gentoo and after upgrading plasma from 5.24.4 to 5.24.5 I'm facing
the same issue as before: I run two xscreens and I only want plasma to run on
xscreen0. It now tries to run on both xscreens and does so
https://bugs.kde.org/show_bug.cgi?id=353975
Allistar changed:
What|Removed |Added
CC||allista...@gmail.com
--- Comment #155 from Allistar
21 matches
Mail list logo
