[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #14 from Michail Vourlakos --- (In reply to Alexandre Pereira from comment #13) > Just a heads up, because I think it may be related to this fix, but don't > know for sure. > > Right now, If I change monitor names ( Like switching from Xorg to Wayland > or vice versa ), latte-dock doesn't start ( according to debug log, gets > stuck on "Step 1" ). > > To make it work, I have to edit the layout file and remove the "lastScreen" > lines. ( then works properly after ) 1. I suppose you mean that this is case for an explicit screen set dock and not onPrimary ones If that is the case then this is unfortunate but it does make sense. As plasma is doing it and Latte follows it screens are identified by their name e.g. HDMI-1, eDS-1 etc... but these names returned from Qt arent the same for X11 and Wayland. So HDMI-1 for X11 it could be HDMI-1-wayland for wayland. I havent find also any pattern that could help in their naming. So when a Latte panel/dock is onPrimary set then it just updates its primary screen from X11 to wayland and vice versa. But when the screen is set on an explicit one screen e.g. HDMI-1 then Latte considers that HDMI-1 and HDMI-1-wayland are different screens and they could be also present at the same time and for that reason when working in wayland a dock for HDMI-1 isnt shown for HDMI-1-wayland You can read the recorded screens identifiers at: ~/.config/lattedockrc at ScreenConnectors section The best solution would be the screens to not be identified by their name but rather through their EDID: https://en.wikipedia.org/wiki/Extended_Display_Identification_Data but I dont know how to retrieve it from Qt... -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #13 from Alexandre Pereira --- Just a heads up, because I think it may be related to this fix, but don't know for sure. Right now, If I change monitor names ( Like switching from Xorg to Wayland or vice versa ), latte-dock doesn't start ( according to debug log, gets stuck on "Step 1" ). To make it work, I have to edit the layout file and remove the "lastScreen" lines. ( then works properly after ) -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/09fe5e385b4df76afbd |te-dock/10dfc623478ce21533b |342fab61afe6c642aaaf1 |1806bf945838c7bce9ea6 --- Comment #12 from Michail Vourlakos --- Git commit 10dfc623478ce21533b1806bf945838c7bce9ea6 by Michail Vourlakos. Committed on 04/09/2018 at 16:52. Pushed by mvourlakos into branch 'v0.8'. on startup explicit dock faulty moving onPrimary --multi-screen fix for explicit docks. There were cases that explicit docks during startup were moving to onprimary screen even though they shouldnt based on the new multi-screens implementation. Bug was tracked down at a faulty series of signals that were overwriting dockView config values to default values and that was creating the fault. -- one more fix for multi-screens, a missing return statement in case an explicit dock is called and its edge at that specific screen is occuppied by an onPrimary one. FIXED-IN: 0.8.1 (cherry picked from commit 09fe5e385b4df76afbd342fab61afe6c642aaaf1) M +14 -5app/dock/dockview.cpp M +2-0app/layout.cpp https://commits.kde.org/latte-dock/10dfc623478ce21533b1806bf945838c7bce9ea6 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #11 from Alexandre Pereira --- Just did :) All good ! Besides working properly, I notice that now it says the proper name of the monitor, even if is primary ( usually always said on primary ). To be honest, this has happened to me for a long time, but I remember once starting layout from fresh and it seemed fixed. I guess the only hint I can give is that this layout is old, including testing from Xorg and Wayland ( where the names of the monitors change ). -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #10 from Michail Vourlakos --- (In reply to Alexandre Pereira from comment #7) > Does these attachments help ? > Found it! Please test again with master to confirm in order to apply it also to v0.8 branch... I really dont know why this was happening only in that layout, the fault was tracked down to a more major one and probably it was influencing more systems... -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/lat ||te-dock/09fe5e385b4df76afbd ||342fab61afe6c642aaaf1 Version Fixed In||0.8.1 --- Comment #9 from Michail Vourlakos --- Git commit 09fe5e385b4df76afbd342fab61afe6c642aaaf1 by Michail Vourlakos. Committed on 04/09/2018 at 16:43. Pushed by mvourlakos into branch 'master'. on startup explicit dock faulty moving onPrimary --multi-screen fix for explicit docks. There were cases that explicit docks during startup were moving to onprimary screen even though they shouldnt based on the new multi-screens implementation. Bug was tracked down at a faulty series of signals that were overwriting dockView config values to default values and that was creating the fault. -- one more fix for multi-screens, a missing return statement in case an explicit dock is called and its edge at that specific screen is occuppied by an onPrimary one. FIXED-IN: 0.8.1 M +14 -5app/dock/dockview.cpp M +2-0app/layout.cpp https://commits.kde.org/latte-dock/09fe5e385b4df76afbd342fab61afe6c642aaaf1 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #8 from Michail Vourlakos --- (In reply to Alexandre Pereira from comment #7) > Does these attachments help ? > I can replicate with your layout in my system but with no other layout file :) let me investigate it... -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #7 from Alexandre Pereira --- Does these attachments help ? I can try to make a video also... when OBS emerges :P -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #6 from Alexandre Pereira --- Created attachment 114777 --> https://bugs.kde.org/attachment.cgi?id=114777=edit Latte Dock RC file -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #5 from Alexandre Pereira --- Created attachment 114775 --> https://bugs.kde.org/attachment.cgi?id=114775=edit Latte Dock Layout File -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #4 from Alexandre Pereira --- Created attachment 114774 --> https://bugs.kde.org/attachment.cgi?id=114774=edit Image of System settings screen section -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #3 from Michail Vourlakos --- I tried to replicate in my system and I cant... 1. Can you send here your layout file to check it? 2. Can you try with Default layout to reproduce the faulty behavior? 3. Maybe some screenshots would help a. from your layout how it ends and how it should end b. from plasma systemsettings the screens configuration-layout (that would help to reproduce exactly the same layout in my multi-screen system) -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #2 from Alexandre Pereira --- just tested it with master branch ( using gentoo, so this is very easy to do ). see this pastebin, ran with latte-dock -dr : https://pastebin.com/kkhJr2zc I tried to change one dock from primary to another screen, and restarted latte-dock. All docks still appeared on primary screen: "DVI-0", but it should have appeared on "Display-Port-0". -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398219] Unable to set latte-dock other than on primary monitor upon restart
https://bugs.kde.org/show_bug.cgi?id=398219 --- Comment #1 from Michail Vourlakos --- (In reply to Alexandre Pereira from comment #0) > Hi, I am using latte-dock in a multimonitor environment. I would like to set > latte-dock to show in one of the other monitors ( not primary one ), and am > able to switch to it. But, upon closing and launching again latte-dock, its > always on the primary screen. > > I tried also to switch "onPrimary" to false, and set lastScreen to the > correct one according to the screens on lattedockrc, but it always displays > on the primary one. > > Thanks ! Thanks for your report, some info: For v0.8.0 this should be valid. This is happening because Latte was trying to be too smart and not left you without a taskmanager to work with. As I was exhausted a lot with that mess, I have re-implemented the multi-screens code for upcoming v0.8.1 and master branch. In the new implementation your setting concerning Primary and explicit screen shouldnt change. Also Primary docks/panels now have bigger priority than the explicit ones which also what plasma tries to do with its panels. If you can build Latte from branches: v0.8 or master you could test the new behavior and provide feedback here -- You are receiving this mail because: You are watching all bug changes.
