Bug 482811 - On X11 with NVIDIA GPU panel always moves moved from one screen to another one after screen unlock
Summary: On X11 with NVIDIA GPU panel always moves moved from one screen to another on...
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Desktop Containment (show other bugs)
Version: 6.0.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: multiscreen
: 483419 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-03-08 04:05 UTC by Samuel
Modified: 2024-04-26 17:33 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Samuel 2024-03-08 04:05:21 UTC
SUMMARY

I have dual monitor setup, when I lock the screen and login 

STEPS TO REPRODUCE
1. Set monitor 2 as primary
2. Lock screen with Super + L
3. Unlock and login again

OBSERVED RESULT

Task manager bar that was set in the monitor 2, is now on monitor 1, besides that in the Screen configuration, the primary one has not changed.

EXPECTED RESULT

Task manager should stay in monitor 2, as it was configured.

SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.8-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.

ADDITIONAL INFORMATION

kde-accessibility-meta 24.02-2
kde-cli-tools 6.0.1-1
kde-graphics-meta 24.02-2
kde-gtk-config 6.0.1-1
kde-system-meta 24.02-2
kde-utilities-meta 24.02-2
kdebugsettings 24.02.0-1
kdeclarative 6.0.0-1
kdeclarative5 5.115.0-1
kdecoration 6.0.1-1
kded 6.0.0-1
kded5 5.115.0-1
kdegraphics-mobipocket 24.02.0-1
kdegraphics-thumbnailers 24.02.0-1
kdelibs4support 5.115.0-1
kdepim-addons 24.02.0-1
kdepim-runtime 24.02.0-1
kdeplasma-addons 6.0.1-1
kdesu 6.0.0-1
kdesu5 5.115.0-1
plasma-activities 6.0.1-1
plasma-activities-stats 6.0.1-1
plasma-desktop 6.0.1-1
plasma-framework5 5.115.0-3
plasma-integration 6.0.1-2
plasma-nm 6.0.1-1
plasma-pa 6.0.1-1
plasma-sdk 6.0.1-1
plasma-thunderbolt 6.0.1-1
plasma-workspace 6.0.1-1
plasma5support 6.0.1-1
Comment 1 Nate Graham 2024-03-08 23:40:40 UTC
Does it happen on Wayland too, or only X11?

Is the actual primary screen changing, or is the panel the only thing that's moving?

Are the wallpapers or any desktop icons on the screens also changing, or are they remaining the same?
Comment 2 Samuel 2024-03-09 02:44:16 UTC
(In reply to Nate Graham from comment #1)
> Does it happen on Wayland too, or only X11?
> 
> Is the actual primary screen changing, or is the panel the only thing that's
> moving?
> 
> Are the wallpapers or any desktop icons on the screens also changing, or are
> they remaining the same?

This happens on X11 only, wayland does not work for me, black screen is the only output. I found the solution for this wayland issue, haven't tweaked my system yet. 

Only the panel is changing, background images and desktop icons stay in place. I checked the screen configs after the bug, all screen configs did not changed, primary one was the same, but taskbar was in the non primary one.
Comment 3 Nate Graham 2024-03-10 22:27:24 UTC
Thanks. Is this consistent? Does it happen every time you do it? Or did it just happen once?
Comment 4 Samuel 2024-03-10 22:55:29 UTC
(In reply to Nate Graham from comment #3)
> Thanks. Is this consistent? Does it happen every time you do it? Or did it
> just happen once?

It's happening constantly, specially after first login of the day,  if I reset primary mon few times, it stops.
Comment 5 Nate Graham 2024-03-13 16:42:43 UTC
Thanks. Can I ask you to set up a new user account and replicate your panel setup, and see if it's still happening there? Basically I want to see if it was caused by an issue upgrading old configs from Plasma 5 to Plasma 6.
Comment 6 Samuel 2024-03-14 03:59:59 UTC
(In reply to Nate Graham from comment #5)
> Thanks. Can I ask you to set up a new user account and replicate your panel
> setup, and see if it's still happening there? Basically I want to see if it
> was caused by an issue upgrading old configs from Plasma 5 to Plasma 6.

I did the following tests:

Created a 2 users via KDE Settings, a standard and an administrator. Updated and restarted the machine, then logged into the new ones and set the second monitor as primary. 

In the standard one the bug happened again, and  in addition, the second output was not recognized after second screen lock, so suddenly only one monitor was available in that account.

In the administrator one all worked without issues, bug did not happen.
Comment 7 Nate Graham 2024-03-14 16:33:45 UTC
Thanks a lot for testing those!
Comment 8 Nate Graham 2024-03-14 16:48:19 UTC
Oh I have one more question, if you don't mind:

When this happens, can you make the issue go away by restarting plasmashell with `systemctl restart --user plasma-plasmashell.service` (assuming you're using the systemd boot; if not, try `plasmashell --replace`)?
Comment 9 Samuel 2024-03-16 16:35:24 UTC
(In reply to Nate Graham from comment #8)
> Oh I have one more question, if you don't mind:
> 
> When this happens, can you make the issue go away by restarting plasmashell
> with `systemctl restart --user plasma-plasmashell.service` (assuming you're
> using the systemd boot; if not, try `plasmashell --replace`)?

Gonna test that, as soon as I get back. Just give me a cuple of days
Comment 10 Samuel 2024-03-19 23:25:08 UTC
(In reply to Nate Graham from comment #8)
> Oh I have one more question, if you don't mind:
> 
> When this happens, can you make the issue go away by restarting plasmashell
> with `systemctl restart --user plasma-plasmashell.service` (assuming you're
> using the systemd boot; if not, try `plasmashell --replace`)?

Got back and test it, used systemctl restart --user plasma-plasmashell.service when it happened, and totally worked, also, when the bug appeared again, entering in edit mode got the taskbar back too.
Comment 11 Samuel 2024-03-26 15:27:04 UTC
I have updated the system to the latest KDE packages available in Arch repos, the bug it's still happening in the original user and the new non privileged one.
Comment 12 Nate Graham 2024-04-01 15:18:58 UTC
Ok great. One final question:

Do you see the issue when:
- You manually lock the screen with Meta+L and then unlock?
- When you disable the lock screen and let the monitor go into power save mode automatically?
- Only when the monitor goes into power save while the screen is locked?
Comment 13 Nate Graham 2024-04-01 15:19:06 UTC
*** Bug 483419 has been marked as a duplicate of this bug. ***
Comment 14 Bug Janitor Service 2024-04-16 03:52:30 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 15 Samuel 2024-04-17 05:17:53 UTC
(In reply to Nate Graham from comment #12)
> Ok great. One final question:
> 
> Do you see the issue when:
> - You manually lock the screen with Meta+L and then unlock?
> - When you disable the lock screen and let the monitor go into power save
> mode automatically?
> - Only when the monitor goes into power save while the screen is locked?

Sorry for the delay, and the answer is yes to all, it happens when I lock screen via META + L, I disabled the screen lock in all the accounts  and, when the monitor goes power save, it happens again.