Bug 443607 - On X11, d53fd656e8e91835fbb4b5e37e32bb32dfd6e445 in plasma workspace makes splash screen ignore scale factor
Summary: On X11, d53fd656e8e91835fbb4b5e37e32bb32dfd6e445 in plasma workspace makes sp...
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Startup process (show other bugs)
Version: master
Platform: Other Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: regression
: 448710 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-10-11 18:01 UTC by Nate Graham
Modified: 2023-12-08 19:59 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
X11 issue: unscaled titlebar, colorful places icons (1012.60 KB, image/png)
2021-10-11 18:01 UTC, Nate Graham
Details
Wayland issue: some UI elements are blurry (514.10 KB, image/png)
2021-10-11 18:02 UTC, Nate Graham
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2021-10-11 18:01:53 UTC
Created attachment 142339 [details]
X11 issue: unscaled titlebar, colorful places icons

I use 200% scale in KScreen, and this commit introduces the following issues when restarting the computer and logging in.

X11:
1. Window titlebars are unscaled
2. Icons with monochrome and colorful versions (e.g. Places pane icons in Dolphin) inappropriately display colorful versions rather than monochrome versions
3. Splash screen contents are unscaled
4. Folder View moves all icons into the top-left quadrant, as if its initial calculation of the available space is off by a factor of 2

Restarting KWin fixes 1, 2, and 3 but my icons are still in the wrong place and need to be manually moved back


Wayland:
1. Plasmashell UI elements display a mixture of XWayland-style blurriness and sharp icons
2. Folder View is XWayland-style blurry
3. Splash screen contents are unscaled

Restarting plasmashell fixes all of those issues.

It feels like some config file value is not being read at login as expected, and only gets read when `plasmashell` or `kwin_x11` is run manually after the session has already started.
Comment 1 Nate Graham 2021-10-11 18:02:25 UTC
Created attachment 142340 [details]
Wayland issue: some UI elements are blurry
Comment 2 David Edmundson 2021-10-16 23:13:41 UTC
I do understand how this could cause the alleged wayland issue in any way.

The X11 case implies we're not blocking on kcminit phase 0 which is something problematic.
Comment 3 David Edmundson 2021-10-16 23:31:20 UTC
*I do not understand how this could cause the alleged wayland issue in any way.

I do wish we had bugzilla comment editing.
Comment 4 Nate Graham 2021-10-20 22:42:43 UTC
Maybe you're right. The Wayland issues have all somehow disappeared.

However the X11 issues remain.
Comment 5 David Edmundson 2021-10-23 23:31:56 UTC
>However the X11 issues remain.

Ack, that one at least makes some sense.

Can you confirm that

`systemctl --user show plasma-kcminit.service | grep ExecStart`

points to /home/nate/kde/.... and not /usr


If so, can I have a log from: `journalctl --user -b 0`
Comment 6 Nate Graham 2021-10-25 16:39:58 UTC
systemctl --user show plasma-kcminit.service | grep ExecStart
35:ExecStart={ path=/home/nate/kde/usr/bin/kcminit_startup ; argv[]=/home/nate/kde/usr/bin/kcminit_startup ; ignore_errors=no ; start_time=[Mon 2021-10-25 07:41:21 MDT] ; stop_time=[Mon 2021-10-25 07:41:21 MDT] ; pid=9648 ; code=exited ; status=0 }
36:ExecStartEx={ path=/home/nate/kde/usr/bin/kcminit_startup ; argv[]=/home/nate/kde/usr/bin/kcminit_startup ; flags= ; start_time=[Mon 2021-10-25 07:41:21 MDT] ; stop_time=[Mon 2021-10-25 07:41:21 MDT] ; pid=9648 ; code=exited ; status=0 }
Comment 7 Nate Graham 2021-12-02 18:45:11 UTC
All issues on X11 are now fixed except for the splash screen not having the correct scaling. Downgrading priority.
Comment 8 Nate Graham 2022-01-20 21:40:45 UTC
*** Bug 448710 has been marked as a duplicate of this bug. ***
Comment 9 Nate Graham 2022-01-27 15:58:21 UTC
I think what happened here is that the commit I referenced in the title triggered a re-scale on login (or re-arranged things so that it happens later), which caused the manifestation of the issue described here, as well as what's described in Bug 449212.