You are not logged in.

#1 2025-04-05 19:50:24

Dark_Prelate
Member
Registered: 2025-04-05
Posts: 4

[SOLVED] ly-dm incorrectly rendered box

After messing with many different DEs and zsh and its themes (especially the powerelevel10 one) and razing every unneeded package, ly main box uses wrong characters when trying to draw its box, but it only does so on startup (i.e. starting it manually or logging out after passing the ly screen, it renders as expected). So far, I have tried reinstalling it and removing the config files but to no avail.

On the web, I haven't found anyone with the same issue, so it's either really obscure or I am missing something obvious.

Thanks in advance.

Last edited by Dark_Prelate (2025-04-07 06:41:17)

Offline

#2 2025-04-06 13:36:45

seth
Member
Registered: 2012-09-03
Posts: 62,698

Re: [SOLVED] ly-dm incorrectly rendered box

https://wiki.archlinux.org/title/Linux_console#Fonts
You're using the wrong console font, perhaps in your initramfs? And only later somehow sanitize it.

nb. https://codeberg.org/AnErrupTion/ly/issues/384 and countless others, ly has notorious issues integrating w/ logind and maintaining the session bus.

Offline

#3 2025-04-06 17:53:39

Dark_Prelate
Member
Registered: 2025-04-05
Posts: 4

Re: [SOLVED] ly-dm incorrectly rendered box

OK, I've disabled the hook "sd-vconsole", and the problem seems to have solved itself. But the strange thing is that, after enabling it again, ly renders correctly still? Which is really odd - I can post my /etc/vconsole.conf to confirm that I'm not causing potential issues by using a peculiar font, but this behaviour is really strange. The only thing that could, potentially, matter is that I'm not using a second monitor right now, and that could be alleviating some of the possible weird behaviours?

If the readout of vconsole.conf is not necessary, I will mark this topic as solved, but I am not sure if the behaviour will reemerge after being able to connect to a second monitor (I won't have access to one for a few days).

Offline

#4 2025-04-06 19:30:15

seth
Member
Registered: 2012-09-03
Posts: 62,698

Re: [SOLVED] ly-dm incorrectly rendered box

But the strange thing is that, after enabling it again

The key is likely that you recreated the initramfs, regardless of the settings, and that sanitized the setup by removing either a stale font or (stale) reference to a stale font?

he only thing that could, potentially, matter is that I'm not using a second monitor right now, and that could be alleviating some of the possible weird behaviours?

Does the other output have a vastly different DPI (ie. you've a 96dpi and a 200 "high" dpi monitor?)

Offline

#5 2025-04-06 20:02:21

Dark_Prelate
Member
Registered: 2025-04-05
Posts: 4

Re: [SOLVED] ly-dm incorrectly rendered box

seth wrote:

Does the other output have a vastly different DPI (ie. you've a 96dpi and a 200 "high" dpi monitor?)

The laptop's screen is a 2k 16" screen, and the external monitor is a 2k 24" screen. I'm not sure if that qualifies as "having a vastly different DPI".

Offline

#6 2025-04-06 20:42:38

seth
Member
Registered: 2012-09-03
Posts: 62,698

Re: [SOLVED] ly-dm incorrectly rendered box

So roughly 100dpi and 160dpi - "kinda".
You'll want to check that in case you're conditionally using a different (smaller) consolefont when the external output is there.
But I doubt that's the cause.

Offline

#7 2025-04-06 21:55:01

Dark_Prelate
Member
Registered: 2025-04-05
Posts: 4

Re: [SOLVED] ly-dm incorrectly rendered box

I also doubt it because the output was mirrored on both screens and was broken on both of them.

And, honestly, I didn't even know that you could conditionally set console fonts based on the DPI of a display.

Since the problem is "solved" for now, should I just mark this as solved and open a new topic if it reoccurs when connecting to second monitor, or should I just leave it open until I can test it with the second monitor?

Offline

#8 2025-04-07 06:20:56

seth
Member
Registered: 2012-09-03
Posts: 62,698

Re: [SOLVED] ly-dm incorrectly rendered box

You'd have to check the resolution and then (manually/scriptually) set a font based on that result.

Since the problem is "solved" for now, should I just mark this as solved and open a new topic if it reoccurs when connecting to second monitor, or should I just leave it open until I can test it with the second monitor?

Up to you. I guess it's easier to not forget the thread if you run into the problem again, so I'd tag it solved now (based on the premise that the initramfs regernation fixed it) and then simply re-open (and indeed bump) it in case it re-emerges (w/ your second output)

Offline

Board footer

Powered by FluxBB