https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #259 from Nate Graham ---
PLEASE NOTE!
If you are using Plasma 5.27 or later and you believe you are still
experiencing the bug, please file a new bug report for it, rather than
commenting in here. This is because in 5.27 and beyond, the co
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #258 from Derek ---
Same issue. Everything was working and somewhere I along the way I was trying
to switch back to nouveau drivers it didnt boot because I didnt realize nvidia
driver installed blacklisting. either way I reverted back to t
https://bugs.kde.org/show_bug.cgi?id=353975
Derek changed:
What|Removed |Added
CC||dcostr...@gmail.com
--- Comment #257 from Derek ---
Sa
https://bugs.kde.org/show_bug.cgi?id=353975
Nate Graham changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #256 from Nate Graham ---
PLE
https://bugs.kde.org/show_bug.cgi?id=353975
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.27
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=353975
Nate Graham changed:
What|Removed |Added
CC||cjd...@brokensolstice.com
--- Comment #255 from N
https://bugs.kde.org/show_bug.cgi?id=353975
Nate Graham changed:
What|Removed |Added
CC||gendi...@gmail.com
--- Comment #254 from Nate Gra
https://bugs.kde.org/show_bug.cgi?id=353975
postix changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |
|ug.cgi?id=450068|
--
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #253 from Nate Graham ---
Yes, the issue will continue to recur until we fix Bug 450068. It's just not
really possible to fix 100% with the current system. That's why we're re-doing
it to make this kind of bug possible to actually fix!
--
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #252 from Fushan Wen ---
(In reply to Alexey Chernyak from comment #251)
> (In reply to Fushan Wen from comment #248)
> > (In reply to Bug Janitor Service from comment #247)
> > > A possibly relevant merge request was started @
> > > https:/
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #251 from Alexey Chernyak ---
(In reply to Fushan Wen from comment #248)
> (In reply to Bug Janitor Service from comment #247)
> > A possibly relevant merge request was started @
> > https://invent.kde.org/plasma/plasma-workspace/-/merge_req
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #250 from Fushan Wen ---
(In reply to H.G.Blob from comment #249)
> I have no problem testing it, but I'm not sure what I need to do. I suppose
> I need to recompile something?
> I'm currently on neon testing, so shouldn't be too far from th
https://bugs.kde.org/show_bug.cgi?id=353975
mira...@mirandastreeter.com changed:
What|Removed |Added
CC||mira...@mirandastreeter.com
--
Yo
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #249 from H.G.Blob ---
I have no problem testing it, but I'm not sure what I need to do. I suppose I
need to recompile something?
I'm currently on neon testing, so shouldn't be too far from the commit.
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #248 from Fushan Wen ---
(In reply to Bug Janitor Service from comment #247)
> A possibly relevant merge request was started @
> https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2186
Could people seeing the bug try this patch
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #247 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2186
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #246 from Fushan Wen ---
Git commit 579075f53a49c4e248b5d83a43ee83a903b06272 by Fushan Wen.
Committed on 21/09/2022 at 06:54.
Pushed by fusionfuture into branch 'Plasma/5.24'.
Revert "Revert "Prevent panel going out of screen boundaries""
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #245 from Ben ---
I have 2 installations of opensuse tumblesweed on the same PC:
Main OS:
I dont know if this is relevant at all
But on my main OS (which i use all the time) upon booting up, i get a grey
background with three small green sq
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #244 from Fushan Wen ---
Git commit df793b9bbd874776ad65808893717517c1c0e5ec by Fushan Wen.
Committed on 16/09/2022 at 14:35.
Pushed by fusionfuture into branch 'Plasma/5.26'.
Revert "Revert "Prevent panel going out of screen boundaries""
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #243 from Marco Martin ---
Git commit 9c7ac7061c5c85d63875eaee70793ba04334c1d0 by Marco Martin, on behalf
of Fushan Wen.
Committed on 16/09/2022 at 14:34.
Pushed by mart into branch 'master'.
Revert "Revert "Prevent panel going out of scree
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #242 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2125
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353975
Nate Graham changed:
What|Removed |Added
CC||globalun...@disroot.org
--- Comment #241 from Nat
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #240 from Nate Graham ---
*** Bug 353722 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=353975
galder changed:
What|Removed |Added
CC||lestofant...@gmail.com
--- Comment #239 from galder -
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #238 from H.G.Blob ---
(In reply to Trent M from comment #236)
For whatever is worth, I see the same issue on _Wayland_ with 2 monitors where
one is rotated 90o. I can see the main screen partially overlapped, but when I
click on that artef
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #237 from Lukas Sommer ---
> Lukas, on your right monitor, do you sometimes see the wallpapers partially
> overlapped when this problem is occurring?
Yes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #236 from Trent M ---
Gene C is right; be careful that your window titles aren't showing any
sensitive information when you share your results. It is my bad for not
cautioning against that as well. I apologize.
Lukas, your test case proves
https://bugs.kde.org/show_bug.cgi?id=353975
Nate Graham changed:
What|Removed |Added
CC||facun...@gmail.com
--- Comment #235 from Nate Gra
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #234 from Lukas Sommer ---
I have a main monitor (1920x1080) the one in the laptop). And an external
monitor, connected by HDMI output via a HDMI-to-VGA adapter (1280x1024). The
external monitor is on the left in the screen layout, while the
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 and eac
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...
Hiya Nate - yeh sorry
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #231 from Claus-Justus Heine ---
(In reply to gene c from comment #229)
> Folks - bit off-topic but a small suggestion - you may want to remove any
> potentially sensitive info before pasting it here.
Oops. BTW, is it possible to edit com
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #230 from Nate Graham ---
(In reply to gene c from comment #228)
> 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 w
https://bugs.kde.org/show_bug.cgi?id=353975
Markus Heß changed:
What|Removed |Added
CC|hess...@googlemail.com |
--
You are receiving this mail because:
You are
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 their methodology
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #227 from Claus-Justus Heine ---
(In reply to Trent M from comment #218)
> Before you all move to a different DE for the time being, can we get some
> `wmctrl -lG` outputs from people being affected by this issue, along with
> your monitor a
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #226 from Trent M ---
That's my bad, I should have been more specific when I asked for the wmctrl
output. This will only be relevant if you are running Plasma on X11. Output
from other DEs won't be helpful because this bug is only relevant f
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.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #224 from H.G.Blob ---
Looks like it's X11 tool, if you are running like me on Wayland then there
would be only Xwayland windows, I suppose
--
You are receiving this mail because:
You are watching all bug changes.
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 #222 from H.G.Blob ---
Forgot to add the output wmctrl output:
wmctrl -lG
0x0183 0 3840 511 1440 1507 hssl-MACHC-WAX9 Spotify
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #221 from H.G.Blob ---
[ScreenConnectors]
0=DP-4
1=DP-2-1
10=eDP-1
11=DP-6
2=DP-2-2
3=:0.0
4=DP-1
5=DP-8
6=DP-7
7=DP-2
8=DP-2-1-6
9=DP-2-1-5
Currently HDMI through Thunrderbolt(DP-6 above) is main screen horizontal and
secondary screen turn
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.
0x04c00051 0 056 2160 3784 lively weco-server – celery.py
0x0043 0 056 2160 3784 lively New Tab - Brave
0x0045 0 056 2160 3784 lively [plasmashell] [Bug 353975] Black
screen on second display (no wallpaper, can't get a context menu on
right-click) - gwh...@kupula
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #218 from Trent M ---
Before you all move to a different DE for the time being, can we get some
`wmctrl -lG` outputs from people being affected by this issue, along with your
monitor arrangements? I believe I have made a strong case for the
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #217 from Nate Graham ---
Plasma fully supports multiple screens, it's just that this design error causes
that support to be buggy for certain combinations of screens, graphics cards,
connection methods, kernels, physical positioning, whethe
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #216 from Claus-Justus Heine ---
(In reply to Nate Graham from comment #204)
> I suspect all the issues here are 99% the same as Bug 450068, which indeed
> hits DisplayPort users harder than HDMI users, since it seems like the
> screen conne
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #215 from Nate Graham ---
The issue is more common with DisplayPort monitors because DisplayPort
connector IDs are extremely volatile, more so than HDMI connector IDs. But HDMI
connector IDs aren't immune to it, so the issues happen there to
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #214 from flan_suse ---
(In reply to Fushan Wen from comment #203)
> Can anyone confirm they can still reproduce this bug without any DP ports
> connected? I only have HDMI port connected and currently I can't reproduce
> black screen on bot
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #213 from naumenko.dmit...@gmail.com ---
(In reply to Greg White from comment #211)
> FWIW, on my machine, I'd say this bug has significantly regressed. I used
> to only very rarely have black screen issues. Now they are common. It is
> ve
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #212 from a ---
(In reply to Greg White from comment #211)
> FWIW, on my machine, I'd say this bug has significantly regressed. I used
> to only very rarely have black screen issues. Now they are common. It is
> very disappointing that th
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #211 from Greg White ---
FWIW, on my machine, I'd say this bug has significantly regressed. I used to
only very rarely have black screen issues. Now they are common. It is very
disappointing that this bug has been treated as such a low-pr
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #210 from a ---
(In reply to gene c from comment #209)
> 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
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=353975
--- Comment #208 from a ---
(In reply to Lukas Sommer from comment #207)
> A workaround that works for me is:
>
> 1.) Go to the system settings, screen/display configuration
>
> 2.) In the diagram which shows the relative position of your two screens,
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #207 from Lukas Sommer ---
A workaround that works for me is:
1.) Go to the system settings, screen/display configuration
2.) In the diagram which shows the relative position of your two screens, move
slightly the position of the screen th
https://bugs.kde.org/show_bug.cgi?id=353975
pingo-po...@hotmail.fr changed:
What|Removed |Added
CC||pingo-po...@hotmail.fr
--- Comment #206
https://bugs.kde.org/show_bug.cgi?id=353975
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #204 from Nate Graham ---
I suspect all the issues here are 99% the same as Bug 450068, which indeed hits
DisplayPort users harder than HDMI users, since it seems like the screen
connector IDs are much more volatile for DisplayPort monitors,
https://bugs.kde.org/show_bug.cgi?id=353975
Fushan Wen changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED
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
Fushan Wen 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 to gnome
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #201 from mikro ---
(In reply to mikro from comment #124)
> I am on Fedora 35 with KDE 5.24.2
> I have two monitors, connected to the same Graphic adapter (Radeon RX 580)
> and they are utilizing one HDMI and one Display Port connection.
> I
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #200 from roworu ---
Today faced same issue on laptop, without any additional monitors ever
connected.
~/.config/plasmashellrc doesn't contain [ScreenConnectors] section.
Arch linux , nvidia 515.65.01-2 , plasma-desktop 5.25.4-1 , xorg-serv
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 displ
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 this:
[ScreenCon
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 #196 from Nate Graham ---
People who are affected: can you open your ~/.config/plasmashellrc file and
paste everything under [ScreenConnectors]?
I'm starting to suspect that basically all of these issues are caused by Bug
450068.
--
You a
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #195 from Trent M ---
Hi there. I actually have managed to fix my version of the issue, and even
though it is different from what the rest of you are experiencing, what I
discovered may provide a hint for fixing it, so I thought I would stop
https://bugs.kde.org/show_bug.cgi?id=353975
Devon Hollowood changed:
What|Removed |Added
CC||devonhollow...@gmail.com
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=353975
Zamundaaa changed:
What|Removed |Added
CC||aappdde...@gmail.com
--- Comment #194 from Zamundaa
https://bugs.kde.org/show_bug.cgi?id=353975
Marc Mezzarobba changed:
What|Removed |Added
CC|marc+b...@mezzarobba.net|
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=353975
Nate Graham changed:
What|Removed |Added
Assignee|aleix...@kde.org|plasma-b...@kde.org
Keywords|multiscree
https://bugs.kde.org/show_bug.cgi?id=353975
postix changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=353975
Alexey Chernyak changed:
What|Removed |Added
CC||alexey_...@chernyak.id.au
--- Comment #193 fr
https://bugs.kde.org/show_bug.cgi?id=353975
Nate Graham changed:
What|Removed |Added
CC||sommer...@gmail.com
--- Comment #192 from Nate Gr
https://bugs.kde.org/show_bug.cgi?id=353975
Samuel García changed:
What|Removed |Added
CC||k...@samueldgv.com
--- Comment #191 from Samuel
https://bugs.kde.org/show_bug.cgi?id=353975
tuppa+...@tuppa.org changed:
What|Removed |Added
CC||tuppa+...@tuppa.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=353975
Fushan Wen changed:
What|Removed |Added
Status|NEEDSINFO |CONFIRMED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #189 from Claus-Justus Heine ---
(In reply to Bug Janitor Service from comment #188)
> 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
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #188 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=353975
--- Comment #187 from Claus-Justus Heine ---
(In reply to Claus-Justus Heine from comment #184)
> (In reply to Fushan Wen from comment #181)
> > Could any people test
> > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1781 fixes
> > you
https://bugs.kde.org/show_bug.cgi?id=353975
agilob changed:
What|Removed |Added
CC|kde...@agilob.net |
--
You are receiving this mail because:
You are watc
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #186 from H.G.Blob ---
I feel like we are perhaps talking about 2 different issues here:
* one for Wayland
* one for Xorg
The fix present in comment #181 seems to appply to Xorg only.
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #185 from H.G.Blob ---
I feel like we are perhaps talking about 2 different issues here:
* one for Wayland
* one for Xorg
The fix present in comment comment #181 seems to appply to Xorg only.
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #184 from Claus-Justus Heine ---
(In reply to Fushan Wen from comment #181)
> Could any people test
> https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1781 fixes
> your issue? Thanks in advance.
I fear not, but I need to do m
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #183 from Trent M ---
Created attachment 149682
--> https://bugs.kde.org/attachment.cgi?id=149682&action=edit
xprop output of the zombie desktop / black window
Here's that xprop output.
Sorry, I forgot to mention a couple things. My star
https://bugs.kde.org/show_bug.cgi?id=353975
Trent M changed:
What|Removed |Added
CC||twilightinz...@gmail.com
--- Comment #182 from Trent
https://bugs.kde.org/show_bug.cgi?id=353975
Fushan Wen changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=353975
kdeb...@accounts.rubenvanerk.nl changed:
What|Removed |Added
CC||kdebugs@accounts.rubenvaner
https://bugs.kde.org/show_bug.cgi?id=353975
Nate Graham changed:
What|Removed |Added
CC||mamorue...@gmail.com
--- Comment #180 from Nate G
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #179 from Miguel Guthridge ---
I think I managed to reproduce this when tweaking display settings (not just
connecting the monitor).
I have two external monitors (1920x1080) and a laptop screen (1920x1200).
Usually when the external display
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #178 from Fushan Wen ---
(In reply to lebr0nk from comment #177)
> Hi I'm using the following Neon distro:
> ~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Neon
> Description:KDE neon User - 5.24
> Release:2
https://bugs.kde.org/show_bug.cgi?id=353975
lebr0nk changed:
What|Removed |Added
CC||bunker_...@outlook.com
--- Comment #177 from lebr0nk
https://bugs.kde.org/show_bug.cgi?id=353975
Nate Graham changed:
What|Removed |Added
CC||qydwhotm...@gmail.com
--- Comment #176 from Nate
https://bugs.kde.org/show_bug.cgi?id=353975
--- Comment #175 from Jacek Wieczorek ---
I've been using Plasma 5.25.80 (package version 5.24.5.r11810.g1e498d074-1)
from Manjaro's kde-unstable repository for a couple of days now. The behavior
is still quite similar. After my screens wake up, the loc
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 in
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 upda
1 - 100 of 318 matches
Mail list logo
