446654 2021-12-07 23:18:19 +0000 Feature Request: mirror a panel on all monitors 2026-01-25 22:45:21 +0000 1 1 4 Plasma plasmashell Panel master unspecified Linux CLOSED WONTFIX https://bugs.kde.org/show_bug.cgi?id=412588 https://bugs.kde.org/show_bug.cgi?id=493195 usability HI wishlist 1.0 443036 1 georgetroulis aleixpol 4wy78uwh alpersal235 bbaovanc bencvdv bnafta boredsquirrel boslmari7 bronsonmathews Bugs.kde.org bwbionicle cheery.idea2032 chermnykh2001 clay damaniakaushal4 daninshed dave dcostroff dennis.lissov dharman dr460nf1r3 ducouedicsophie eliott.chytil endrebjorsvik evanc577 fanzhuyifan formularsumo fzwart gameburrow georgetroulis grantgryczan gs2 guyven herzenschein j.chataignon j.straight-kde jackyguo18 jan.selchow jendal jgqehj55 jgrdlgrd joni.hilger justinsojolly kde.bobbed648 kde.levitator555 kde kde keigh.rim kev.metalwave kubek-93 l.allulli lcarmona leereyzhe leonvincenterd luisbocanegra17b mail marek.j.bednarczyk maxim.kukushkin michele.mazza milan minterior natalie_clarius nate natetronn neutralcat niccolo.venerandi niccolo nnikita.beloglazov null pavila10alt ped plasma-bugs-null postix quit-traps-scope r.kunschke raldone01 rexbinary scratch.submerge413 severin.hamader squale ssi16.10.91 sylvainfaivre szauer.mark tani.giovonni tcl_de unkinkedmedal94 v.n.suadicani vlpetrov02 wazhai 0 oldest_to_newest 2083715 0 georgetroulis 2021-12-07 23:18:19 +0000 SUMMARY When using two (or more) monitors, it is convenient to have a panel on each monitor such that all panels are completely identical. Currently, it seems that the only way to accomplish this is to manually create each panel, and customize each one in the exact same way. This is a tedious process for users that enjoy heavily-customized panels. SOFTWARE/OS VERSIONS Linux Kernel: 5.15.2-2-MANJARO (64-bit) (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This feature has been previously requested for KDE Plasma 4, closed due to obsolescence of Plasma 4, and never re-opened on Plasma 5: https://kde-bugs-dist.kde.narkive.com/0Vn46o7h/plasma-bug-342826-new-add-possibility-to-duplicate-panel-to-other-screens This exact feature has been indirectly requested on a few forums, none of which have received adequate responses: - https://www.reddit.com/r/kde/comments/iuq4ld/duplicate_panel_on_all_screens/ - https://forums.fedoraforum.org/showthread.php?324910-Panel-clone-for-each-monitor CURRENT SOLUTION 1) Create a panel on one monitor, and customize manually with widgets/menus until desired 2) Repeat #1 for second monitor, ensuring new panel is identical to that on monitor #1 3) Repeat #1 for third monitor, ensuring new panel is identical to that on monitor #1 4) and so on ... IDEAL SOLUTION 1) Create a single panel on one monitor, and customize manually with widgets/menus until desired 2) Create a new blank panel on second monitor. Right click on it, and select "Mirror Panel." Some selection menu would let the user choose which panel they would like this current panel to mirror. All customizations of the first panel would immediately transfer to the new panel, and changes to one panel will automatically be reflected in the other mirrored panel. 3) Repeat #2 for each monitor 2083744 1 leereyzhe 2021-12-08 03:26:53 +0000 i agree this would be cool. 2083937 2 nate 2021-12-08 20:47:08 +0000 Yes, this is an idea we're pursuing soon! 2085790 3 nate 2021-12-15 17:40:39 +0000 *** Bug 447012 has been marked as a duplicate of this bug. *** 2096076 4 nate 2022-01-20 21:45:39 +0000 *** Bug 448678 has been marked as a duplicate of this bug. *** 2119314 5 nate 2022-04-25 17:19:23 +0000 *** Bug 420854 has been marked as a duplicate of this bug. *** 2127139 6 nate 2022-05-27 14:02:17 +0000 *** Bug 454458 has been marked as a duplicate of this bug. *** 2130928 7 jackyguo18 2022-06-13 21:24:45 +0000 Has there been any progress towards this or are they waiting on someone to make a PR? 2132584 8 lcarmona 2022-06-18 18:50:45 +0000 This option will be really nice. Other possibility would be backup/export the panel (but in this case, the notification area could crash). 2133322 9 squale 2022-06-21 14:46:48 +0000 This would be *really* nice to have. 2158117 10 bnafta 2022-10-03 12:56:10 +0000 This would be very helpful. Better than that, just something that works totally out of the box on multiple monitors like the panel provided by tint2. tint2 is not as powerful and customizable as plasma panels, but at least it works well with multiple screens. 2175169 11 dr460nf1r3 2022-11-19 09:42:45 +0000 Indeed a very helpful feature! 2-3 monitors are currently very time-consuming to set up if everything needs to be created manually. It would also enable distributions to ship multi-monitor configured out of the box rather than leaving users on their own. 2179966 12 kubek-93 2022-12-01 09:00:01 +0000 It would save a lot of time spent on redoing panels on external displays. 2182897 13 niccolo.venerandi 2022-12-08 16:19:54 +0000 *** Bug 462771 has been marked as a duplicate of this bug. *** 2183834 14 bbaovanc 2022-12-10 22:29:06 +0000 Is there anything blocking this? I can see requests from 7+ years ago in KDE 4 asking for this, how has this not been added yet? 2193494 15 nate 2023-01-05 20:56:49 +0000 *** Bug 463260 has been marked as a duplicate of this bug. *** 2195835 16 wazhai 2023-01-11 13:29:30 +0000 "IDEAL SOLUTION Repeat #2 for each monitor" This might be useful for more customized setups, but to cover 95% of use cases a setting similar to other DEs along the lines of "Show this panel on all monitors" seems far more ideal and user-friendly. 2212733 17 nate 2023-02-28 21:48:53 +0000 *** Bug 466558 has been marked as a duplicate of this bug. *** 2215327 18 ducouedicsophie 2023-03-10 11:19:02 +0000 Yes please that would be a nice feature! 2215673 19 dcostroff 2023-03-12 13:16:08 +0000 This would be extremely helpful, would like to see this. 2216756 20 j.chataignon 2023-03-16 03:17:43 +0000 Additional forum posts about this: https://askubuntu.com/questions/1265917/how-to-show-kde-panel-at-all-monitors https://www.reddit.com/r/kde/comments/m2i8fh/taskbar_on_both_monitors/ (related) https://www.kubuntuforums.net/forum/archives/eol-releases/-20-10/software-support-bd/72357-kde-plasma-default-panel-on-multiple-montiors SUGGESTED SOLUTIONS so far: - a "mirror an existing panel" option when creating a new panel - a "duplicate this panel" option in Edit Mode - a "show this panel on all monitors" option in Edit Mode - "show primary screen's panels on this screen" in Display Settings - "export to file"/"import from file" features for panels 2218975 21 natetronn 2023-03-28 18:11:22 +0000 Would love to see this feature added as well; please. 2232056 22 kev.metalwave 2023-05-20 13:07:42 +0000 +1 on this feature 2245867 23 natetronn 2023-08-10 20:50:18 +0000 Please allow me to submit my vote for this feature as well. 2246783 24 4wy78uwh 2023-08-15 18:47:49 +0000 (In reply to Natetronn from comment #23) > Please allow me to submit my vote for this feature as well. https://bugs.kde.org/describecomponents.cgi?product=plasmashell has disabled bug votes. 2254613 25 vlpetrov02 2023-09-21 13:47:47 +0000 I agree, this would be very helpful 2254617 26 natetronn 2023-09-21 14:47:02 +0000 (In reply to third="Beedell", first="Roke", second="Julian Lockhart" from comment #24) > (In reply to Natetronn from comment #23) > > Please allow me to submit my vote for this feature as well. > > https://bugs.kde.org/describecomponents.cgi?product=plasmashell has disabled > bug votes. Thanks. Yeah, I meant it metaphorically :-D 2261107 27 lucasrizzini 2023-10-24 12:05:28 +0000 I think this should be something that could be possible from the beginning. I have a DP and HDMI monitor and I can't just have the panel on the DP monitor, not on Xorg, at least. 2276302 28 tani.giovonni 2023-12-24 08:12:16 +0000 Not certain how related this is behind the scenes (if at all) but a more general way of copying widgets, panels, etc. between monitors would be good as well. Panels and widgets seem to be related to some degree, but I'm not sure quite how much they are or if a generalised method of copying/mirroring would be possible. 2290427 29 justinsojolly 2024-02-20 17:30:19 +0000 What is the status of this?? This is years old, how is it not possible to duplicate a panel for all monitors? This is getting pathetic and extremely frustrating. Please revisit this and push this out to the code base. 2290429 30 alpersal235 2024-02-20 17:37:07 +0000 Yeah, I am waiting for this since `2023-01-10 14:42:16 UTC`. Yesterday I have formatted my PC and even though I do not customize my panels anywhere near avg. Arch user, it was really unsatisfying doing everything from the start. And I only have two monitors. It is really annoying how this is still not implemented. 2290430 31 fanzhuyifan 2024-02-20 17:38:29 +0000 (In reply to justinsojolly from comment #29) > What is the status of this?? This is years old, how is it not possible to > duplicate a panel for all monitors? This is getting pathetic and extremely > frustrating. Please revisit this and push this out to the code base. If you submit a MR for it I am sure it would get reviewed and considered :) Alternately, there is also the sponsored work section where you could post a bounty for this: https://discuss.kde.org/c/development/sponsored-work/31 Unfortunately KDE is driven by volunteers, and there are always more tasks than developers available. So if you really want to see some feature implemented, the best way is to submit a MR (it doesn't have to be perfect), or sponsor someone to do it. 2290722 32 chermnykh2001 2024-02-21 16:20:11 +0000 This probably should depend on https://invent.kde.org/plasma/plasma-desktop/-/issues/113 because duplicating some widgets may break some functionality 2290725 33 fanzhuyifan 2024-02-21 16:22:30 +0000 (In reply to Dmitrii Chermnykh from comment #32) > This probably should depend on > https://invent.kde.org/plasma/plasma-desktop/-/issues/113 because > duplicating some widgets may break some functionality I currently have two screens with duplicate system trays containing the applets, and I don't seem to notice any issues. 2290728 34 chermnykh2001 2024-02-21 16:25:10 +0000 (In reply to fanzhuyifan from comment #33) > (In reply to Dmitrii Chermnykh from comment #32) > > This probably should depend on > > https://invent.kde.org/plasma/plasma-desktop/-/issues/113 because > > duplicating some widgets may break some functionality > > I currently have two screens with duplicate system trays containing the > applets, and I don't seem to notice any issues. I used to have problems with media keys because they were handled by 2 instances of media player applet https://bugs.kde.org/show_bug.cgi?id=391578 https://bugs.kde.org/show_bug.cgi?id=409190 2303630 35 fanzhuyifan 2024-03-21 01:27:11 +0000 *** Bug 484110 has been marked as a duplicate of this bug. *** 2304944 36 boredsquirrel 2024-03-24 13:05:35 +0000 yes a big problem is that every external display needs to get the panel created new, which is especially bad when presenting, or using a TV etc. 2327352 37 unkinkedmedal94 2024-06-13 01:12:14 +0000 Is there really no updates on this? It's the main reason why I haven't switched to kde yet. 2328171 38 squale 2024-06-15 07:04:45 +0000 I dared to change platform as this affects all linux users. I dared to change version as there is no attempt to provide this feature in any branch afaik 2334551 39 damaniakaushal4 2024-07-03 12:46:48 +0000 Yes please, this will be a very useful feature. It's not very imperative to create new panels for each screen. 2336187 40 neutralcat 2024-07-10 09:19:37 +0000 This feature would make the transition for Windows users (like me) much, MUCH smoother. It's one of the most noticeable and arbitrarily worse differences between daily driving Windows vs KDE plasma. 2346442 41 bug-janitor 2024-08-18 10:34:21 +0000 A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4623 2349384 42 niccolo 2024-08-28 12:00:13 +0000 After some investigation, I believe that the technical implementation of this is de-facto impossible; however, a very similar feature - the ability to clone a panel from a monitor to another - was implemented, and thus I'm closing this as wontfix. To elaborate, it's already quite complex to have two different panels who should follow the same set of settings (a major rewrite would be needed for that); but, on top of that, monitors can have different sizes and thus the same panel should have to be mirrored with different looks on different panels, potentially interfering with the settings. There would be a lot of combinations possible, and I believe they would be prone to breakage. 2349389 43 maxim.kukushkin 2024-08-28 12:19:54 +0000 (In reply to Niccolò Venerandi from comment #42) > After some investigation, I believe that the technical implementation of > this is de-facto impossible; however, a very similar feature - the ability > to clone a panel from a monitor to another - was implemented, and thus I'm > closing this as wontfix. > > To elaborate, it's already quite complex to have two different panels who > should follow the same set of settings (a major rewrite would be needed for > that); but, on top of that, monitors can have different sizes and thus the > same panel should have to be mirrored with different looks on different > panels, potentially interfering with the settings. There would be a lot of > combinations possible, and I believe they would be prone to breakage. Could you please elaborate a bit more on the panel cloning? Last time I tried to do this I found it quite complicated. Basically there were no controls to clone a panel and the panels are not stored anywhere in a simple format on a filesystem, so that it could be somehow automated Given the amount of comments in this feature request and points that it's big UI experience downgrade when coming from other platforms, this feature needs to be implemented in one way or another. Even if a panel can be cloned with several clicks, it's still quite cumbersome to do, especially when we're talking about laptops which can be attached to all sorts of monitors and projectors in meeting rooms. Imagine doing this 3-4 times per day, for people who often need to present in different locations. I think when people talk about mirroring a panel, it doesn't mean mirror pixel-by-pixel. It's about the set of widgets and their settings which is hardest to do manually. That aspect doesn't depend on monitor's resolution. 2349391 44 maxim.kukushkin 2024-08-28 12:23:48 +0000 btw, if there's already an option/code to clone an existing panel, why can't this Feature Request be implemented in form of automatically triggering that "clone" feature when a new monitor is added in case doesn't have any panel yet? 2349443 45 unkinkedmedal94 2024-08-28 14:04:14 +0000 (In reply to Niccolò Venerandi from comment #42) > After some investigation, I believe that the technical implementation of > this is de-facto impossible; however, a very similar feature - the ability > to clone a panel from a monitor to another - was implemented, and thus I'm > closing this as wontfix. > > To elaborate, it's already quite complex to have two different panels who > should follow the same set of settings (a major rewrite would be needed for > that); but, on top of that, monitors can have different sizes and thus the > same panel should have to be mirrored with different looks on different > panels, potentially interfering with the settings. There would be a lot of > combinations possible, and I believe they would be prone to breakage. Sir, with all due respect, this is a dealbreaking feature others DEs and OSes have, and it absolutely is a reason why many would never try kde. Thats how important it is. If a major code rewrite of the panels is needed for this, we can wait till its done. 2349450 46 niccolo 2024-08-28 14:15:03 +0000 (In reply to Maxim from comment #43) > Could you please elaborate a bit more on the panel cloning? Last time I > tried to do this I found it quite complicated. Basically there were no > controls to clone a panel and the panels are not stored anywhere in a simple > format on a filesystem, so that it could be somehow automated I implemented a new feature where you just have to click "Clone" on panel settings and then select a screen :) > btw, if there's already an option/code to clone an existing panel, why can't this Feature Request be implemented in form of automatically triggering that "clone" feature when a new monitor is added in case doesn't have any panel yet? This could be done, but I'm a bit worried about the consequences it might have. What if the user has multiple panels? Should we always clone *all* panels from one screen to another? Is that what the user really expects when connecting to a new monitor? 2349452 47 maxim.kukushkin 2024-08-28 14:23:40 +0000 > This could be done, but I'm a bit worried about the consequences it might > have. What if the user has multiple panels? Should we always clone *all* > panels from one screen to another? Is that what the user really expects when > connecting to a new monitor? Not always, I think the original idea was to have a setting for a panel to indicate that it's expected to be mirrored. So the algorithm in the first iteration could be: - when a monitor is connected - for each panel - does it have the "mirror" flag set? (no by default) - if not, do nothing - does the new monitor already have panels? - if yes, do nothing - otherwise, clone the panel The last bit can be modified, depending on what information is available internally. The main idea is to prevent cloning panels endlessly on each connect of the same monitor. I don't know if it's possible to mark a panel as a clone of another one in its metadata (like an ID) to be checked more precisely. However, imho, it would already be a major improvement 2349453 48 4wy78uwh 2024-08-28 14:25:02 +0000 (In reply to Niccolò Venerandi from comment #46) > > btw, if there's already an option/code to clone an existing panel, why can't this Feature Request be implemented in form of automatically triggering that "clone" feature when a new monitor is added in case doesn't have any panel yet? > > This could be done, but I'm a bit worried about the consequences it might have. What if the user has multiple panels? Should we always clone *all* panels from one screen to another? Is that what the user really expects when connecting to a new monitor? It's certainly not what I would expect. (In reply to Maxim from comment #44) > btw, if there's already an option/code to clone an existing panel, why can't this Feature Request be implemented in form of automatically triggering that "clone" feature when a new monitor is added in case doesn't have any panel yet? Because that's different functionality. This FR is about an automatic visual replication by rendering one configuration to other monitors, whereas your proposal would be to automatically duplicate one configuration to all other monitors. Each configuration would then need to be rendered independently, and presumably `plasmashell` would overwrite the 2nd-to-last modified panels with the modifications performed to the last-modified one? 2349454 49 niccolo 2024-08-28 14:26:15 +0000 (In reply to Maxim from comment #47) > > This could be done, but I'm a bit worried about the consequences it might > > have. What if the user has multiple panels? Should we always clone *all* > > panels from one screen to another? Is that what the user really expects when > > connecting to a new monitor? > > Not always, I think the original idea was to have a setting for a panel to > indicate that it's expected to be mirrored. So the algorithm in the first > iteration could be: > - when a monitor is connected > - for each panel > - does it have the "mirror" flag set? (no by default) > - if not, do nothing > - does the new monitor already have panels? > - if yes, do nothing > - otherwise, clone the panel > > The last bit can be modified, depending on what information is available > internally. The main idea is to prevent cloning panels endlessly on each > connect of the same monitor. I don't know if it's possible to mark a panel > as a clone of another one in its metadata (like an ID) to be checked more > precisely. However, imho, it would already be a major improvement I'll give a look at the code. If it's not too complex, some sort of auto-cloning might be a worthy addition. 2349465 50 unkinkedmedal94 2024-08-28 14:50:35 +0000 (In reply to Niccolò Venerandi from comment #46) > (In reply to Maxim from comment #43) > > Could you please elaborate a bit more on the panel cloning? Last time I > > tried to do this I found it quite complicated. Basically there were no > > controls to clone a panel and the panels are not stored anywhere in a simple > > format on a filesystem, so that it could be somehow automated > > I implemented a new feature where you just have to click "Clone" on panel > settings and then select a screen :) > > > btw, if there's already an option/code to clone an existing panel, why can't this Feature Request be implemented in form of automatically triggering that "clone" feature when a new monitor is added in case doesn't have any panel yet? > > This could be done, but I'm a bit worried about the consequences it might > have. What if the user has multiple panels? Should we always clone *all* > panels from one screen to another? Is that what the user really expects when > connecting to a new monitor? I believe the best way to add this would be a checkbox labeled 'Show this panel on all monitors' or something like this, that when checked will do so. That way it will only clone panels the user want. 2354625 51 boredsquirrel 2024-09-15 20:18:23 +0000 thanks Niccolo for your work on this! Yes I agree with the strong feelings some people here expressed. This really is odd. Plasma detects the laptop monitor as primary, so overwriting that with the config of some random other screen should not happen. I only know Windows, and COSMIC, and there this is simply the default. Actually, I guess, sacrificing the option for different panels. I think using a mechanism like described, cloning the panel, if no other exists, if no opt-out exists, makes sense. Otherwise yes, going into panel configuration to have this seemingly basic feature working, is not a nice workflow. Thanks for your time! I would also be a fan of the auto-cloning. 2354745 52 nate 2024-09-16 11:50:20 +0000 Automatically cloning panels (which ones?) on newly-connected monitors is a different request from mirroring, which is what's being requested here and has been deemed infeasible. I would recommend opening a new feature request for that. 2354751 53 jgqehj55 2024-09-16 12:06:26 +0000 I created a separate issue for it: https://bugs.kde.org/show_bug.cgi?id=493195 2379081 54 niccolo 2024-12-05 11:54:04 +0000 Git commit 5fa1c39fa494cc1e0d58160883ae3fb3e9f05ffc by Niccolò Venerandi. Committed on 05/12/2024 at 11:53. Pushed by niccolove into branch 'master'. Add option to clone panels Related: bug 412588 M +5 -0 shell/panelview.cpp M +3 -1 shell/panelview.h M +131 -0 shell/shellcorona.cpp M +2 -0 shell/shellcorona.h https://invent.kde.org/plasma/plasma-workspace/-/commit/5fa1c39fa494cc1e0d58160883ae3fb3e9f05ffc 2381900 55 v.n.suadicani 2024-12-16 18:28:46 +0000 (In reply to Niccolò Venerandi from comment #42) > After some investigation, I believe that the technical implementation of > this is de-facto impossible; however, a very similar feature - the ability > to clone a panel from a monitor to another - was implemented, and thus I'm > closing this as wontfix. > > To elaborate, it's already quite complex to have two different panels who > should follow the same set of settings (a major rewrite would be needed for > that); but, on top of that, monitors can have different sizes and thus the > same panel should have to be mirrored with different looks on different > panels, potentially interfering with the settings. There would be a lot of > combinations possible, and I believe they would be prone to breakage. Okay, but Windows and possibly other OSs deal with this just fine. Cloning a panel is a workaround but not a real solution. An option for mirroring the panel properly is an important feature. If it requires a major rewrite, then so be it. I don't think that's any reason to close this request. This is a major deal-breaker for many users and it should be fixed. 2381913 56 chermnykh2001 2024-12-16 19:02:11 +0000 I think this can be implemented like latte dock did: mark a panel as standalone or clone and then automatically sync the standalone panel with its clones on screen reconnect or panel updates However it might introduce bugs with multiscreen setups when the screens are getting turned on/off or being reconnected 2392754 57 gameburrow 2025-01-26 20:11:02 +0000 (In reply to medalzz from comment #50) > (In reply to Niccolò Venerandi from comment #46) > > (In reply to Maxim from comment #43) > > > Could you please elaborate a bit more on the panel cloning? Last time I > > > tried to do this I found it quite complicated. Basically there were no > > > controls to clone a panel and the panels are not stored anywhere in a simple > > > format on a filesystem, so that it could be somehow automated > > > > I implemented a new feature where you just have to click "Clone" on panel > > settings and then select a screen :) > > > > > btw, if there's already an option/code to clone an existing panel, why can't this Feature Request be implemented in form of automatically triggering that "clone" feature when a new monitor is added in case doesn't have any panel yet? > > > > This could be done, but I'm a bit worried about the consequences it might > > have. What if the user has multiple panels? Should we always clone *all* > > panels from one screen to another? Is that what the user really expects when > > connecting to a new monitor? > > I believe the best way to add this would be a checkbox labeled 'Show this > panel on all monitors' or something like this, that when checked will do so. > That way it will only clone panels the user want. This is the way I would see it handled also and this missing feature is one of my biggest remaining frustrations on KDE (as multi monitor user) 2396142 58 grantgryczan 2025-02-09 08:29:01 +0000 *** Bug 499709 has been marked as a duplicate of this bug. *** 2396153 59 grantgryczan 2025-02-09 10:02:21 +0000 (In reply to v.n.suadicani from comment #55) > If it requires a major rewrite, then so be it. I don't think that's any > reason to close this request. This is a major deal-breaker for many users > and it should be fixed. Strongly agree. Why close this request? There shouldn't be any obligation to resolve this issue anytime soon, but that doesn't mean the issue should be closed, precluding any possibility of it being implemented in the future. 2396400 60 bnafta 2025-02-10 12:31:38 +0000 I'm a bit confused because this thread was "intentionally closed", and the ticket platform doesn't provide a clear way to indicate why. Given the size of this thread, I want to understand: what is the final solution to the main issue of this ticket? To summarize, from what I gather, the core issue is: Currently, Plasma (v6.2.5) lacks (or lacked) the ability to display "same" menu bars and other elements configured on the primary monitor across all additional monitors, whether previously connected or not. Is this issue being addressed in another ticket? If so, could you please share the ticket number so I can follow its progress? Additionally, what is currently blocking this merge request from being approved and merged? https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4623 For context, I would be satisfied if Plasma's behavior were similar to tint2’s approach when handling additional monitors, whether newly connected or previously used. 2396401 61 bnafta 2025-02-10 12:33:56 +0000 >> Additionally, what is currently blocking this merge request from being approved and merged? >> https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4623 My mistake. Apparently it has already been merged. 2397190 62 bnafta 2025-02-12 17:41:01 +0000 Plasma 6.3.0 now includes the ability to clone entire panels—including their settings and applets. You can read more about it in the official announcement: https://kde.org/announcements/plasma/6/6.3.0/ For a quick overview, check out this video demonstration of the new feature in action: https://cdn.kde.org/promo/Announcements/Plasma/6.3/cloning_panels_cc.webm Please note that the feature does not yet support automatic mirroring across all monitors. However, since I rarely connect new screens, this limitation hasn't been a problem for my workflow. Kudos to the KDE team for this great enhancement! 2397285 63 178226 dcostroff 2025-02-12 20:32:28 +0000 Created attachment 178226 attachment-3447885-0.html So it just duplicates a panel on the same monitor? On Wed, Feb 12, 2025, 1:15 PM Fabio C. Barrionuevo <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=446654 > > --- Comment #62 from Fabio C. Barrionuevo <bnafta@gmail.com> --- > Plasma 6.3.0 now includes the ability to clone entire panels—including > their > settings and applets. You can read more about it in the official > announcement: https://kde.org/announcements/plasma/6/6.3.0/ > > For a quick overview, check out this video demonstration of the new > feature in > action: > https://cdn.kde.org/promo/Announcements/Plasma/6.3/cloning_panels_cc.webm > > Please note that the feature does not yet support automatic mirroring > across > all monitors. However, since I rarely connect new screens, this limitation > hasn't been a problem for my workflow. > > Kudos to the KDE team for this great enhancement! > > -- > You are receiving this mail because: > You are on the CC list for the bug. 2397391 64 clay 2025-02-13 03:43:21 +0000 (In reply to Derek from comment #63) > Created attachment 178226 [details] > attachment-3447885-0.html > > So it just duplicates a panel on the same monitor? > No, it can be placed anywhere: top, side, bottom of any screen, from what I tried. 2397448 65 v.n.suadicani 2025-02-13 08:47:00 +0000 (In reply to Fabio C. Barrionuevo from comment #62) > Plasma 6.3.0 now includes the ability to clone entire panels—including their > settings and applets. You can read more about it in the official > announcement: https://kde.org/announcements/plasma/6/6.3.0/ > > For a quick overview, check out this video demonstration of the new feature > in action: > https://cdn.kde.org/promo/Announcements/Plasma/6.3/cloning_panels_cc.webm > > Please note that the feature does not yet support automatic mirroring across > all monitors. However, since I rarely connect new screens, this limitation > hasn't been a problem for my workflow. > > Kudos to the KDE team for this great enhancement! This is a good step in the right direction. However from the description, I am assuming that it doesn't sync the panels if I change one of them? Like I make a panel, clone it so I have two panels, and I edit the first panel again. Does the second one also change? 2399220 66 nate 2025-02-18 03:35:56 +0000 No, it only clones; it does not keep them in sync like they're mirrored. That feature has been rejected for the time being, sorry. 2399242 67 bencvdv 2025-02-18 04:28:09 +0000 To quote the original request: > 2) ... changes to one panel will automatically be reflected in the other mirrored panel. And to quote from the links included in the original request: > ... Also, if I make any change in one, I don't want to have to do it twice (or more, if I add a third screen). > ... if I would want update panel content I would need to update all of them (sometimes 3 sometimes 2). It seems to me that this has been prematurely closed. Cloning is a fantastic feature and a good step forward, but does not address the root of this feature request and what I (and so many others) would really like to see. This feature is instead requesting a mirroring of ongoing changes across multiple panels,*not* cloning. I would not be against the closing of any other "clone" requests but, again, this particular issue has not been resolved and I believe it should stay open as a reflection of the ongoing interest it has, even if it is not currently planned due to present difficulty or development limitations. 2403103 68 nate 2025-02-26 23:49:22 +0000 ...And that feature has been rejected for the time being, sorry. Instead we got cloning, which got tracked with Bug 412588, with this one being used to track mirroring. 2403122 69 bencvdv 2025-02-27 00:28:31 +0000 I would be curious to know the details around why it has been rejected. Given the large amount of interest in having this as a feature, I assume it was a technical limitation. Is there any chance further information could be included here outlining the issues that the developers ran into when attempting to implement it? It may help other programmers who are interested in it (myself included) to experiment a bit more without spending too much time focusing on the blocking issues already encountered. Apologies if this is the wrong place for that request, I'm not well versed in the KDE development cycle :) 2403388 70 nate 2025-02-27 23:12:01 +0000 See comment 42 in this bug report. I don't have any more information than that, so it'll be up to Niccolò to provide more information if he has any and has the time to do so. 2421230 71 dharman 2025-05-05 14:16:54 +0000 (In reply to Nate Graham from comment #70) > See comment 42 in this bug report. I don't have any more information than > that, so it'll be up to Niccolò to provide more information if he has any > and has the time to do so. It seems to me a bad way to handle a problem like this. It's just my opinion, but after reading the thread, I think it could have been better managed. 2433658 72 boslmari7 2025-06-17 15:52:56 +0000 If someone is wondering: Even though this bug report is closed, there is still someone who hasn't given up yet on this basic, long overdue and much requested feature. An open issue is on the Plasma Workspace GitLab: https://invent.kde.org/plasma/plasma-workspace/-/issues/144 178226 2025-02-12 20:32:31 +0000 2025-02-12 20:32:31 +0000 attachment-3447885-0.html attachment-3447885-0.html text/html 1737 dcostroff PHAgZGlyPSJsdHIiPlNvIGl0IGp1c3QgZHVwbGljYXRlcyBhIHBhbmVsIG9uIHRoZSBzYW1lIG1v bml0b3I/IDwvcD4NCjxicj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSBnbWFpbF9xdW90ZV9jb250 YWluZXIiPjxkaXYgZGlyPSJsdHIiIGNsYXNzPSJnbWFpbF9hdHRyIj5PbiBXZWQsIEZlYiAxMiwg MjAyNSwgMToxNeKAr1BNIEZhYmlvIEMuIEJhcnJpb251ZXZvICZsdDs8YSBocmVmPSJtYWlsdG86 YnVnemlsbGFfbm9yZXBseUBrZGUub3JnIj5idWd6aWxsYV9ub3JlcGx5QGtkZS5vcmc8L2E+Jmd0 OyB3cm90ZTo8YnI+PC9kaXY+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0i bWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0 OjFleCI+PGEgaHJlZj0iaHR0cHM6Ly9idWdzLmtkZS5vcmcvc2hvd19idWcuY2dpP2lkPTQ0NjY1 NCIgcmVsPSJub3JlZmVycmVyIG5vcmVmZXJyZXIiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL2J1 Z3Mua2RlLm9yZy9zaG93X2J1Zy5jZ2k/aWQ9NDQ2NjU0PC9hPjxicj4NCjxicj4NCi0tLSBDb21t ZW50ICM2MiBmcm9tIEZhYmlvIEMuIEJhcnJpb251ZXZvICZsdDs8YSBocmVmPSJtYWlsdG86Ym5h ZnRhQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiIHJlbD0ibm9yZWZlcnJlciI+Ym5hZnRhQGdt YWlsLmNvbTwvYT4mZ3Q7IC0tLTxicj4NClBsYXNtYSA2LjMuMCBub3cgaW5jbHVkZXMgdGhlIGFi aWxpdHkgdG8gY2xvbmUgZW50aXJlIHBhbmVsc+KAlGluY2x1ZGluZyB0aGVpcjxicj4NCnNldHRp bmdzIGFuZCBhcHBsZXRzLiBZb3UgY2FuIHJlYWQgbW9yZSBhYm91dCBpdCBpbiB0aGUgb2ZmaWNp YWwgPGJyPg0KYW5ub3VuY2VtZW50OiA8YSBocmVmPSJodHRwczovL2tkZS5vcmcvYW5ub3VuY2Vt ZW50cy9wbGFzbWEvNi82LjMuMC8iIHJlbD0ibm9yZWZlcnJlciBub3JlZmVycmVyIiB0YXJnZXQ9 Il9ibGFuayI+aHR0cHM6Ly9rZGUub3JnL2Fubm91bmNlbWVudHMvcGxhc21hLzYvNi4zLjAvPC9h Pjxicj4NCjxicj4NCkZvciBhIHF1aWNrIG92ZXJ2aWV3LCBjaGVjayBvdXQgdGhpcyB2aWRlbyBk ZW1vbnN0cmF0aW9uIG9mIHRoZSBuZXcgZmVhdHVyZSBpbjxicj4NCmFjdGlvbjo8YnI+DQo8YSBo cmVmPSJodHRwczovL2Nkbi5rZGUub3JnL3Byb21vL0Fubm91bmNlbWVudHMvUGxhc21hLzYuMy9j bG9uaW5nX3BhbmVsc19jYy53ZWJtIiByZWw9Im5vcmVmZXJyZXIgbm9yZWZlcnJlciIgdGFyZ2V0 PSJfYmxhbmsiPmh0dHBzOi8vY2RuLmtkZS5vcmcvcHJvbW8vQW5ub3VuY2VtZW50cy9QbGFzbWEv Ni4zL2Nsb25pbmdfcGFuZWxzX2NjLndlYm08L2E+PGJyPg0KPGJyPg0KUGxlYXNlIG5vdGUgdGhh dCB0aGUgZmVhdHVyZSBkb2VzIG5vdCB5ZXQgc3VwcG9ydCBhdXRvbWF0aWMgbWlycm9yaW5nIGFj cm9zczxicj4NCmFsbCBtb25pdG9ycy4gSG93ZXZlciwgc2luY2UgSSByYXJlbHkgY29ubmVjdCBu ZXcgc2NyZWVucywgdGhpcyBsaW1pdGF0aW9uPGJyPg0KaGFzbiYjMzk7dCBiZWVuIGEgcHJvYmxl bSBmb3IgbXkgd29ya2Zsb3cuPGJyPg0KPGJyPg0KS3Vkb3MgdG8gdGhlIEtERSB0ZWFtIGZvciB0 aGlzIGdyZWF0IGVuaGFuY2VtZW50ITxicj4NCjxicj4NCi0tIDxicj4NCllvdSBhcmUgcmVjZWl2 aW5nIHRoaXMgbWFpbCBiZWNhdXNlOjxicj4NCllvdSBhcmUgb24gdGhlIENDIGxpc3QgZm9yIHRo ZSBidWcuPC9ibG9ja3F1b3RlPjwvZGl2Pg0K