Bug 362128 - Panel restored to wrong screen
Summary: Panel restored to wrong screen
Status: RESOLVED DUPLICATE of bug 362051
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (show other bugs)
Version: 5.6.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-23 09:05 UTC by Daniel Lichtenberger
Modified: 2016-05-04 11:34 UTC (History)
2 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 Daniel Lichtenberger 2016-04-23 09:05:46 UTC
Since 5.6.2, my task manager bar is always restored to screen 1 (which is left-of screen 0) instead of screen 0. I can drag it back to screen 0 (and the lastScreen config entry is updated correctly), but on restart it's back on screen 1. I guess this could be related to this commit:

commit 046260f397491c185e77b72110f7a2a0dfadb82b
Author: Marco Martin <notmart@gmail.com>
Date:   Thu Feb 4 15:50:28 2016 +0100

    insist to have lastScreen -1
    
    never risk to go in a panel by itself

diff --git a/systemtray.cpp b/systemtray.cpp
index 1e10f66..79f6c82 100644
--- a/systemtray.cpp
+++ b/systemtray.cpp
@@ -56,6 +56,7 @@ SystemTray::~SystemTray()
 
 void SystemTray::init()
 {
+    config().writeEntry("lastScreen", -1);
     Containment::init();
     actions()->removeAction(actions()->action("add widgets"));
     actions()->removeAction(actions()->action("add panel"));


Reproducible: Always

Steps to Reproduce:
1. Drag task manager to screen 1
2. Restart the computer
3.

Actual Results:  
Task manager is restored on screen 0.

Expected Results:  
Task manager should be restored on screen 1.
Comment 1 Eike Hein 2016-04-24 12:08:13 UTC
Not a Task Manager issue, reassigning to panel.
Comment 2 Daniel Lichtenberger 2016-05-03 01:08:33 UTC
I still have this issue, but I noticed that the commit I mentioned was not part of 5.6.2 and does not seem to be related to my problem.
Comment 3 Marco Martin 2016-05-04 11:32:53 UTC
no, the commit is not related
Comment 4 Marco Martin 2016-05-04 11:34:00 UTC

*** This bug has been marked as a duplicate of bug 362051 ***