Created attachment 114583 [details] screenshot when first opening elisa Hello On a Debian Testing desktop running plasma on wayland, and using the version 0.2.1 of elisa from flathub, elisa starts with its window being much larger than its UI. (See attached screenshot) flatpak info org.kde.elisa Ref: app/org.kde.elisa/x86_64/stable ID: org.kde.elisa Arch: x86_64 Branch: stable Origin: flathub Collection ID: org.flathub.Stable Date: 2018-07-11 10:19:34 +0000 Subject: upgrade to 0.2.1 stable version of Elisa (0ccfce1e) Commit: 64bf7b02151b8699696b6ad0fb13f1ac00d871cf8dc9a7f3b54ad46dd4fb8cbb Parent: c2ef0d2cc160a69a1f03d5d5fee9f89d0fddb3d8ea6b6b716c9c7b8751f6cab9 Location: /var/lib/flatpak/app/org.kde.elisa/x86_64/stable/64bf7b02151b8699696b6ad0fb13f1ac00d871cf8dc9a7f3b54ad46dd4fb8cbb Installed size: 9.9 MB Runtime: org.kde.Platform/x86_64/5.11 Sdk: org.kde.Sdk/x86_64/5.11 Potentially relevant Debian desktop component version: ii kwin-wayland 4:5.13.1-1+b amd64 KDE window manager, wayland version ii libwayland-serv 1.15.0-2 amd64 wayland compositor infrastructure - ii plasma-workspac 4:5.13.2-1 amd64 Plasma Workspace for KF5
Hm. This could be a kwin bug. I tried starting the task manager config panel and it also started with a large amount of extra space around the UI elements.
I don't see this on wayland on Manjaro testing, elisa 0.2.1.
Apparently it because I'm using dual screens. The laptop has a highdpi 3200x1800 13" screen, and I had it plugged in as in "extend the desktop" mode into a 20" 1600x1200 monitor. When I have elisa opening on just a single desktop it seems to open correctly.
Thanks for the information. I know where is the bug now.
Elisa opened with a correctly sized window with a two displays on wayland with the following flatpak version Date: 2018-09-30 07:43:48 +0000 Subject: build stable 0.3 version of Elisa (1d346801) Commit: 50efbf9079880e1f1a6ff9b1306912a8f37d66538ba86a136f8095bdd033c5c4
(In reply to Diane Trout from comment #5) > Elisa opened with a correctly sized window with a two displays on wayland > with the following flatpak version > > Date: 2018-09-30 07:43:48 +0000 > Subject: build stable 0.3 version of Elisa (1d346801) > Commit: 50efbf9079880e1f1a6ff9b1306912a8f37d66538ba86a136f8095bdd033c5c4 Thanks for your report. I am not sure from where the fix came. I did not had time to look at it. I am also lacking proper hardware to test. If the bug is fixed, you can mark it as fixed or I can do it for you.
The flatpak platform updated, and the host Plasma instance has also seen updates. Maybe that's helped? Or maybe it was rebooting first, and with the screens already configured correctly I'll close the bug for now, You had an idea of where the bug might've been? Could you point me toward it? So, if it happens again I can try to build from source and see if I can spot the problem.
(In reply to Diane Trout from comment #7) > The flatpak platform updated, and the host Plasma instance has also seen > updates. > > Maybe that's helped? Or maybe it was rebooting first, and with the screens > already configured correctly > > I'll close the bug for now, > > You had an idea of where the bug might've been? Could you point me toward > it? So, if it happens again I can try to build from source and see if I can > spot the problem. I am not really sure. I had been thinking that maybe we would scaling the UI the wrong waybecause of the following line in src/main.cpp: engine.rootContext()->setContextProperty(QStringLiteral("logicalDpi"), QGuiApplication::primaryScreen()->logicalDotsPerInch()); This is only an hypothesis and I have not had enough time to really understand the problem.