Bug 352232

Summary:	Can't add a panel to a secondary display
Product:	[Plasma] plasmashell	Reporter:	Victor B. Gonzalez <bugs.kde.org.id324>
Component:	Panel	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	bugs.kde.org.id324, gerd, nate, notuxius, pinnerite, rdieter
Priority:	NOR
Version First Reported In:	5.12.2
Target Milestone:	1.0
Platform:	Mageia RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Victor B. Gonzalez 2015-09-03 18:02:16 UTC

It's currently impossible to add a panel to a secondary display. Adding a panel, whether default or empty onto another display requires killing plasmashell. If it's a default panel, after you kill and restore plasmashell, it shows up on the correct display.

If it's an empty panel, after you kill and restore plasmashell, it shows up on the main display.

Reproducible: Always

Steps to Reproduce:
1. Mouse into secondary display
2. Add a panel


Actual Results:  
If the panel was empty to begin with, it goes from the secondary monitor to the main. If it was default, it'll show up correctly (both results require you kill plasmashell).

Expected Results:  
For panel empty or default to work as advertised. Immediately available on the correct display without having to kill plasmashell.

Comment 1 Victor B. Gonzalez 2015-09-03 18:04:12 UTC

Sorry, it's not impossible , just definitely buggy.

Comment 2 Victor B. Gonzalez 2015-09-03 18:46:02 UTC

The reason I found this bug was because having a second panel on a secondary display that only contains a task manager for that screen is quite valuable. I may have found a way to add a second panel that doesn't clobber the main display (but unfortunately still requires restarting plasmashell).

Instead of adding an empty panel to the second display, add a default panel and then remove everything from it. Why this works I am not clear but it works for me. I'm hoping it's not a fluke, I love the second panel **only** working on the second display.

Comment 3 Gerd v. Egidy 2015-10-22 12:35:57 UTC

I can confirm this problem.

Fedora 22, x86_64, Intel graphics, plasma-workspace-5.4.2-4.fc22.x86_64
(from updates-testing)

Comment 4 Alexander Mentyu 2018-03-05 14:32:37 UTC

Can you still reproduce it?

Comment 5 Alan 2018-05-14 20:05:11 UTC

Still the same in 5.12.2

Comment 6 Nate Graham 2022-06-25 18:41:12 UTC

A lot has changed since this bug was filed. Is it still reproducible for you in Plasma 5.24 (the latest LTS version) or 5.25 (the latest version, period)?

Comment 7 Bug Janitor Service 2022-07-10 04:36:42 UTC

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 bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 8 Bug Janitor Service 2022-07-25 04:36:21 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!