https://bugs.kde.org/show_bug.cgi?id=486374
Bug ID: 486374
Summary: External monitors not detected
Classification: Plasma
Product: KScreen
Version: 5.27.5
Platform: Debian stable
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=477941
gene c changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |
|ug.cgi?id=443708
https://bugs.kde.org/show_bug.cgi?id=443708
gene c changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |
|ug.cgi?id=477941
https://bugs.kde.org/show_bug.cgi?id=435715
gene c changed:
What|Removed |Added
CC|gj...@sapience.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=439470
gene c changed:
What|Removed |Added
CC|gj...@sapience.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #232 from gene c ---
(In reply to Nate Graham from comment #230)
> (In reply to gene c from comment #228)
> ...
> have to lose customizable desktops, customizable panels, desktop widgets,
> desktop icons, and so on...
Hiy
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #229 from gene c ---
Folks - bit off-topic but a small suggestion - you may want to remove any
potentially sensitive info before pasting it here.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #228 from gene c ---
Kind of obvious question: since gnome is working extremely well, and is open
source, have kde devs looked at gnome code to see what they do to handle
multiple monitors with a view to potentially follow
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #225 from gene c ---
(In reply to H.G.Blob from comment #224)
> Looks like it's X11 tool, if you are running like me on Wayland then there
> would be only Xwayland windows, I suppose
Ok thanks - all wayland here too.
-
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #223 from gene c ---
does wmctrl need to be run once or on each monitor?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #220 from gene c ---
(In reply to Trent M from comment #218)
I tried running this in gnome in a gnome-terminal and got no output - sorry.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #209 from gene c ---
I found a work around that works fine - i installed gnome (yes I know) and if
kde every gets to a usable state can always use gdm to launch plasma. gdm is
native wayland and seems more stable than sddm which also helps
https://bugs.kde.org/show_bug.cgi?id=450068
gene c changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=353975
gene c changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #202 from gene c ---
Indeed it is quite disheartening that a bug of this obviously very high
importance sees no feedback. Neither this or 450068 have been assigned - so
that means no-one is working on it.
Really hate to switch back
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #199 from gene c ---
If I use kcm to split the displays into 2 (left and right) plasmashell the
plasmashellrc doesn't change - and it crashes shortly after hitting apply and
backgrounds go black and its back in mirror mode again.
Both
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #197 from gene c ---
2 x identical monitors both LG 4k - one connected via USB-C the second via
HDMI.
[ScreenConnectors]
0=
1=DP-2
2=:0.0
The behavior after 5.25.4 - now after screen lock is woken up - both monitors
show same info (mirror
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #173 from gene c ---
I can regularly crash plasmashell by simply editing (1 of the 2) panel and
adding (or trying to add) applications from kmenu - not convinced this wasn't
commonplace in released version though.
I did this as after
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #171 from gene c ---
Per my last test - this is wayland desktop started by sddm running wayland. So
no Xorg involved anywhere.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #170 from gene c ---
Hi @Nate:
Results of testing with Archlinux 5.24.90 from kde-unstable repo.
Good:
- Both monitor desktops continue to work after idle and wake cycle (yay) which
means the major bug is fixed.
Bad (ish):
- After idle
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #161 from gene c ---
Forgot to say (sorry for being obvious) -but the fact that it crashes when
being woken up after things go to sleep - suggests that this is perhaps case
(i)
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #160 from gene c ---
Since restarting plasmashell always "fixed" the desktop I don't think your test
validates that anything is fixed.
I suppose there are 2 possibilities:
(i) If the crash is a result of the "fix" and
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #154 from gene c ---
Understood and thanks for feedback.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #152 from gene c ---
Alex / Nate - can either of you provide any information on where things stand
with regard to repairing this (annoying) lil bug?
thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #135 from gene c ---
Reporting back - with no screen lock at all - problem persists. And same with
sddm or lightdm.
Clearly seems related to powering off and resuming of monitors for our case
anyway.
I suppose since gdm is wayland capable
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #134 from gene c ---
My comment above may not be right - trigger may relate to hardware sleep/wake
as well. If I turn off the plasma screen locker that might provide additional
information.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #133 from gene c ---
I tried lightdm - and if i manually start light-locker everything is fine.
If I leave the plasma wayland session - then the plasma locker kicks in and
things are once again broken.
So this tells me that is the trigger
https://bugs.kde.org/show_bug.cgi?id=353975
gene c changed:
What|Removed |Added
CC||gj...@sapience.com
--- Comment #130 from gene c
https://bugs.kde.org/show_bug.cgi?id=439470
gene c changed:
What|Removed |Added
CC||gj...@sapience.com
--- Comment #6 from gene c
https://bugs.kde.org/show_bug.cgi?id=435715
gene c changed:
What|Removed |Added
CC||gj...@sapience.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=443708
--- Comment #4 from gene c ---
My comment text got lost - here it is again:
I too see plasmashell core dump after I upgraded from 5.22.5 5o 5.23.0
Downgrading back to 5.22.5 makes all fine again
This occurred on
intel NUC10i5 with CPU / graphics card
https://bugs.kde.org/show_bug.cgi?id=443708
--- Comment #3 from gene c ---
Distro: I'm running on Arch Linux fully updated with testing repo.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443708
gene c changed:
What|Removed |Added
CC||gj...@sapience.com
--- Comment #2 from gene c
33 matches
Mail list logo
