[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2023-02-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||shallp...@gmail.com --- Comment #87 from Nate

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2023-01-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED Version Fixed In|

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2023-01-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||supg...@gmail.com --- Comment #85 from Nate

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2023-01-14 Thread Iyán Méndez Veiga
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #84 from Iyán Méndez Veiga --- (In reply to Gábor Katona from comment #83) > Which Plasma version will contain the fix? Plasma 5.27, which should be released in exactly one month. And next week you can already try it out in the beta. --

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2023-01-14 Thread Gábor Katona
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #83 from Gábor Katona --- Which Plasma version will contain the fix? -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-12-25 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=450068 Fushan Wen changed: What|Removed |Added CC||hasez...@gmail.com --- Comment #82 from Fushan

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-12-15 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=450068 Marco Martin changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-12-15 Thread Dmitry Nezhevenko
https://bugs.kde.org/show_bug.cgi?id=450068 Dmitry Nezhevenko changed: What|Removed |Added CC||d...@inhex.net -- You are receiving this

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-12-10 Thread Thomas Capricelli
https://bugs.kde.org/show_bug.cgi?id=450068 Thomas Capricelli changed: What|Removed |Added CC||kdebugs.20.orzelf@spamgourm

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-12-08 Thread Alex
https://bugs.kde.org/show_bug.cgi?id=450068 Alex changed: What|Removed |Added CC||nilwaech...@web.de -- You are receiving this mail

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-12-05 Thread Pawel
https://bugs.kde.org/show_bug.cgi?id=450068 Pawel changed: What|Removed |Added CC||bednarczyk.pa...@outlook.co |

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-12-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||perezme...@gmail.com --- Comment #80 from Nate

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-30 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #79 from Nate Graham --- > Interestingly, restarting Plasma is enough to get the desktop back (and > usually the panel, too). So it > can't just be about the connector names, there seems to be some additional > state confusion in plasma >

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-24 Thread Victoria
https://bugs.kde.org/show_bug.cgi?id=450068 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #78 from Victoria ---

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-23 Thread Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #77 from Kai Krakow --- For me it seems to be fixed or at least works as expected after I disabled the kscreen service in the system settings. With each plasma updates, the behavior seems to change in random and unpredictable ways.

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #76 from cellst...@gmail.com --- Due to many bugs being merged into one, I am not sure if the below is relevant here, I just received the following notification on another bug marked as duplicate of one of the many linked here: --- Comment

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #75 from cellst...@gmail.com --- As in the case of Stephen Ackerman: * displays are always connected (1 hdmi and 1 DP) * my default setup is primary on (DP) secondary off (hdmi) * if monitor (either or DP/hdmi) goes into deep sleep, when

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-22 Thread Stephen Ackerman
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #74 from Stephen Ackerman --- I've observed the "Desktop disappearing" behavior with just 2 LG monitors connected to a desktop. It seems they go into "Deep sleep" which registers as, to some extent, disconnecting (Previously had crashing

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #73 from cellst...@gmail.com --- For completeness: * I run wayland * also the widgets associated to the primary monitor are recovered after 'in-session' restart -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #72 from cellst...@gmail.com --- Yes, I confirm that restarting plasmashell (i tried from konsole) actually recovers the 'notion of primary monitor': the background associated to the primary monitor is back (in place of the background

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-22 Thread David Marzal
https://bugs.kde.org/show_bug.cgi?id=450068 David Marzal changed: What|Removed |Added CC||mundoli...@tutanota.com -- You are receiving

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-21 Thread Ralf Jung
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #71 from Ralf Jung --- Interestingly, restarting Plasma is enough to get the desktop back (and usually the panel, too). So it can't just be about the connector names, there seems to be some additional state confusion in plasma that gets

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-21 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #70 from Nate Graham --- Same bug. The desktop (which handles right-clicks) is mapped to screens by Plasma, and that being buggy is what this Bugzilla ticket is about. -- You are receiving this mail because: You are watching all bug

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-21 Thread Ralf Jung
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #69 from Ralf Jung --- When I just unplugged my external screen, plasma lost my *destop*. It is all black and there's not even a context menu. Is that the same bug or a different issue? -- You are receiving this mail because: You are

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-21 Thread S.Trzmiel
https://bugs.kde.org/show_bug.cgi?id=450068 S.Trzmiel changed: What|Removed |Added CC||x...@x-s.com.pl -- You are receiving this mail

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-16 Thread Charles Brockman
https://bugs.kde.org/show_bug.cgi?id=450068 Charles Brockman changed: What|Removed |Added CC||k...@cbpwd.com -- You are receiving this

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-16 Thread John Miller
https://bugs.kde.org/show_bug.cgi?id=450068 John Miller changed: What|Removed |Added CC||neuromance...@yahoo.com -- You are receiving

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-16 Thread Gurenko Alex
https://bugs.kde.org/show_bug.cgi?id=450068 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-16 Thread Yaroslav Sidlovsky
https://bugs.kde.org/show_bug.cgi?id=450068 Yaroslav Sidlovsky changed: What|Removed |Added CC||zawer...@gmail.com -- You are receiving

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b |

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-11 Thread Peter Tselios
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #68 from Peter Tselios --- Honestly, as developers you must have some discussions with developers from other DEs. How do they handle this? -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-11 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=450068 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-10 Thread Tuomas Suutari
https://bugs.kde.org/show_bug.cgi?id=450068 Tuomas Suutari changed: What|Removed |Added CC||tuo...@nepnep.net -- You are receiving this

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #67 from Nate Graham --- I can happen anyway with the current system, unfortunately. -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-10 Thread Ralf Jung
https://bugs.kde.org/show_bug.cgi?id=450068 Ralf Jung changed: What|Removed |Added CC||p...@ralfj.de --- Comment #66 from Ralf Jung ---

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||mlud...@logix.net.nz --- Comment #65 from Nate

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||k...@sjrx.net --- Comment #64 from Nate Graham

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-10 Thread Stephen Ackerman
https://bugs.kde.org/show_bug.cgi?id=450068 Stephen Ackerman changed: What|Removed |Added CC||stephenackerma...@gmail.com -- You are

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||bernhard.schert...@pm.me --- Comment #63 from

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #62 from Nate Graham --- Plasma's containment mapping builds on top of the information that KScreen provides. When KScreen is at fault, it can mess up Plasma, but Plasma's mapping can get messed up independent of KScreen too. And that part

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-09 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #61 from Bernd Steinhauser --- (In reply to Nate Graham from comment #60) > This bug report is only about Plasmashell's mapping of containments to > screens; if any screens are themselves not turning on properly, that's an > issue in

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-09 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #60 from Nate Graham --- (In reply to lrdarknesss from comment #57) > I am also constantly having problems with resume from sleep. > For me it's always that one monitor stays completely black (no connection) > and the other one has it's

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-09 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #59 from Bernd Steinhauser --- (In reply to Nate Graham from comment #53) > Unfortunately EDID/serial number are not reliable either. Some monitors have > the serial number set to the same value for every monitor in a particular > product

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #58 from lrdarkne...@yahoo.de --- Created attachment 153614 --> https://bugs.kde.org/attachment.cgi?id=153614=edit Journalctl logs when resuming from sleep -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #57 from lrdarkne...@yahoo.de --- I am also constantly having problems with resume from sleep. For me it's always that one monitor stays completely black (no connection) and the other one has it's backlight enabled (so it seems to have some

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 lrdarkne...@yahoo.de changed: What|Removed |Added CC||lrdarkne...@yahoo.de -- You are

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #56 from Nate Graham --- *** Bug 459448 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||p...@extreg.com --- Comment #55 from Nate Graham

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-07 Thread Henrik Hudson
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #54 from Henrik Hudson --- (In reply to Peter Tselios from comment #52) > I have issues with multi-monitor setups for as long as I remember and some > of those issues are reported by me and other but other issues are simply so > random that

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-07 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #53 from Nate Graham --- Unfortunately EDID/serial number are not reliable either. Some monitors have the serial number set to the same value for every monitor in a particular product line, for example. But yes, the problem with

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-07 Thread Peter Tselios
https://bugs.kde.org/show_bug.cgi?id=450068 Peter Tselios changed: What|Removed |Added CC||ptsel...@outlook.com --- Comment #52 from

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-11-05 Thread petrk
https://bugs.kde.org/show_bug.cgi?id=450068 petrk changed: What|Removed |Added CC||pepk...@gmail.com -- You are receiving this mail

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-28 Thread networkException
https://bugs.kde.org/show_bug.cgi?id=450068 networkException changed: What|Removed |Added CC||k...@nwex.de -- You are receiving this

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||kato...@gmail.com --- Comment #51 from Nate

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 cellst...@gmail.com changed: What|Removed |Added CC||cellst...@gmail.com --- Comment #50 from

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-26 Thread Henrik Hudson
https://bugs.kde.org/show_bug.cgi?id=450068 Henrik Hudson changed: What|Removed |Added CC||rhav...@rhavenn.net --- Comment #49 from

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-25 Thread Àlex García
https://bugs.kde.org/show_bug.cgi?id=450068 Àlex García changed: What|Removed |Added CC||alex.garcia@enterprise-net. |

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 ide...@protonmail.com changed: What|Removed |Added CC||ide...@protonmail.com -- You are

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-24 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #47 from Nate Graham --- A different bug, yes. See Bug 460341. -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-22 Thread Viktor
https://bugs.kde.org/show_bug.cgi?id=450068 Viktor changed: What|Removed |Added CC||hajit...@gmail.com -- You are receiving this mail

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 bertil.bo...@gmail.com changed: What|Removed |Added CC||bertil.bo...@gmail.com --- Comment #46

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-21 Thread Felix Miata
https://bugs.kde.org/show_bug.cgi?id=450068 Felix Miata changed: What|Removed |Added CC||k...@zaister.de --- Comment #45 from Felix Miata

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-20 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=450068 Fushan Wen changed: What|Removed |Added CC||poperi...@mailbox.org --- Comment #44 from Fushan

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-19 Thread Jacek Wieczorek
https://bugs.kde.org/show_bug.cgi?id=450068 Jacek Wieczorek changed: What|Removed |Added CC||mrj...@gmail.com -- You are receiving this

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=450068 postix changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=353975| --

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||eugene.bee...@yandex.ru --- Comment #43 from

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||sp...@gmx.com --- Comment #42 from Nate Graham

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-15 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #41 from Bernd Steinhauser --- (In reply to arne anka from comment #11) > So, what's the idea of a "primary screen" and what is it to do with the > placement of widgets, panels etc? Being a multi-monitor user for decades now, for me it's

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com -- You are receiving this

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-14 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #40 from Nate

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-14 Thread Raman Gupta
https://bugs.kde.org/show_bug.cgi?id=450068 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-14 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added Blocks||385135 Referenced Bugs:

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-14 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||nik.kaise...@googlemail.com --- Comment #39 from

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-13 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=450068 Konrad Materka changed: What|Removed |Added CC||mate...@gmail.com -- You are receiving this

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-11 Thread Rafael Jesús Alcántara Pérez
https://bugs.kde.org/show_bug.cgi?id=450068 Rafael Jesús Alcántara Pérez changed: What|Removed |Added CC||rafaelalcantaraperez@gmail.

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-08 Thread Daniel Noga
https://bugs.kde.org/show_bug.cgi?id=450068 Daniel Noga changed: What|Removed |Added CC||noga.d...@gmail.com -- You are receiving this

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-10-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #38 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.

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-29 Thread Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #37 from Kai Krakow --- (In reply to Nate Graham from comment #35) > Unfortunately this is exactly right. [...] > The current system needs to be thrown away and replaced with > something better-engineered from the start, which is in

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-29 Thread Iyán Méndez Veiga
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #36 from Iyán Méndez Veiga --- (In reply to Nate Graham from comment #35) > (In reply to Iyán Méndez Veiga from comment #32) > > I can have both screen in duplicate mode > That was indeed a separate issue, and it's already been fixed. See

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-28 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #35 from Nate Graham --- (In reply to Iyán Méndez Veiga from comment #32) > I can have both screen in duplicate mode That was indeed a separate issue, and it's already been fixed. See Bug 459253. Your other Bug 459368 is being separately

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #34 from dinumar...@gmail.com --- I too agree to this; in https://bugs.kde.org/show_bug.cgi?id=458667 I noted that some of the random issues don't sort out with a plasmashell --replace or even after a logout/login again, which strongly seems

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-28 Thread Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #33 from Kai Krakow --- (In reply to Iyán Méndez Veiga from comment #32) > Plasma 5.25.90 has a new issue and it's really unstable and difficult to > replicate. Every morning when I connect the laptop to the docking station I > have no idea

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-27 Thread Iyán Méndez Veiga
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #32 from Iyán Méndez Veiga --- The problem of marking "all similar" issues as duplicates of this one is that there are two different things going on here: one old from Plasma <=5.25, and one new from 5.26. Perhaps, the new screen mapping

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-27 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||ki...@neoteroi.org --- Comment #31 from Nate

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-27 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 tomash...@gmail.com changed: What|Removed |Added CC||tomash...@gmail.com -- You are receiving

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com --

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-22 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #30 from Nate Graham --- *** Bug 459532 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-21 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=450068 Fushan Wen changed: What|Removed |Added CC||m...@iyanmv.com --- Comment #29 from Fushan Wen

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #28 from Nate Graham --- Kai: there's ongoing discussion at https://invent.kde.org/plasma/plasma-workspace/-/issues/52 and I believe your idea is essentially included in the current plan of action. If you feel like you have something

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450068 tcb...@protonmail.com changed: What|Removed |Added CC||tcb...@protonmail.com -- You are

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-10 Thread Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #27 from Kai Krakow --- We probably need a system which stores a containment layout per number of monitors connecting. If an additional monitor gets connected, clone the next "lower count" layout. Then, sort the primary monitor to the

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-10 Thread Carlo
https://bugs.kde.org/show_bug.cgi?id=450068 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-09-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||dinumar...@gmail.com --- Comment #26 from Nate

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-08-23 Thread Bryan Pedini
https://bugs.kde.org/show_bug.cgi?id=450068 Bryan Pedini changed: What|Removed |Added CC||b.ped...@bjphoster.com -- You are receiving

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-08-22 Thread phrxmd
https://bugs.kde.org/show_bug.cgi?id=450068 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #25 from

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-08-17 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=450068 Bernd Steinhauser changed: What|Removed |Added CC||li...@bernd-steinhauser.de -- You are

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-08-15 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=450068 Nate Graham changed: What|Removed |Added CC||dener@gmail.com --- Comment #24 from Nate

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-08-11 Thread H.G.Blob
https://bugs.kde.org/show_bug.cgi?id=450068 H.G.Blob changed: What|Removed |Added CC||hgb...@mrs.ro -- You are receiving this mail

[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else

2022-08-11 Thread Felix Miata
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #23 from Felix Miata --- (In reply to a from comment #18) > Any workaround? has one possibility: driver switch (at its bottom). Those not familiar with graphics drivers may wish to visit

  1   2   >