Skip to content

Conversation

@Cyanoxygen
Copy link
Member

No description provided.

Since we rebooted before first-boot-complete.target, the machine ID
generated during this boot may not be committed to the file system.
Thus this step must be performed manually.

This also makes sure the machine-id is generated before launching the
graphical environment, so the D-Bus and the rest of the system can live
happily.
This logic uses 768 as the base of vertical resolution and sets the DPI
to 125%, 150%, 200% or 300% according to the vertical resolution of the
screen, to scale the wizard to the proper size.
This prevents the script from jamming if the system is powered through
battery since oma will wait for input of the user if in such condition.
If font DPI is scaled up using GDK_DPI_SCALE, the layout will be totally
disrupted. Launching the wizard fullscreen fixes the problem, since the
window dimension should change according to the scale.
It looks like webkit2gtk applications does not honor Xft.dpi. We need to
set the scaling factor for GTK.
To prevent the word “否则” from being cut off mid line.
@Cyanoxygen
Copy link
Member Author

Tested good on Asahi and generic pc-efi.

@Cyanoxygen Cyanoxygen merged commit 64ff960 into master Oct 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants