Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

21.04: Encryption prompt off center #19

Closed
leviport opened this issue May 17, 2021 · 14 comments · Fixed by #25
Closed

21.04: Encryption prompt off center #19

leviport opened this issue May 17, 2021 · 14 comments · Fixed by #25

Comments

@leviport
Copy link
Member

I upgraded my personal desktop over the weekend, and this started happening every time I boot. I'm suspecting it's related to my monitor layout. The left display is a 2560x1440p 144Hz display connected over DisplayPort, and the right display is a 1920x1080 in portrait mode connected over HDMI. My GPU is an AMD RX Vega64.

I didn't do any further testing since there were video games that needed playing, but I'll test different display configurations soon.

PXL_20210514_234350065

@jackpot51
Copy link
Member

Strange it doesn't seem to line up on either monitor. And pre-X11 it shouldn't know the right one is rotated yet.

@bflanagin
Copy link

Also happens on galp5 and the lemp9. Possibly due to the different native display resolutions of the screens?

@ianhundere
Copy link

ianhundere commented Jul 6, 2021

happening to me after updating to 21.04 from 20.10.

doesn't show up at all via my laptop screen, but us off-center via my external monitors.

i have to press esc twice to see it centered again.

@ianhundere
Copy link

weird, i did a update-initramfs -c -k all and got an error saying cryptsetup: WARNING: cryptdata: ignoring unknown option 'nofail'

so i looked at my crypttab file and found nofail in it. i ended up removing it and not i don't have issues with the encryption prompt not showing up.

@ianhundere
Copy link

just to chime in again, this is still happening on my external monitor as per @leviport

@gjrtimmer
Copy link

gjrtimmer commented Jul 17, 2021

I have the same problem, I've also put it here Reddit

So right now we have also figured out that if I remove my additional two screens, and just use my laptop screen I do not have the issue. What makes it weird is that is started since my upgrade to 21.04.

20210714_081618

@gjrtimmer
Copy link

gjrtimmer commented Aug 11, 2021

So I was searching; can this commit be the culprit ba4edf1#diff-d91a29052a1e731ad56359dd4031575130be146c057e16b385241073c2f647a1 ?

So anybody and suggestion how I can test this ?

@gjrtimmer
Copy link

Another one I found was for the pop-os upgrade.

cc2b8ae#diff-d91a29052a1e731ad56359dd4031575130be146c057e16b385241073c2f647a1L20-L21

@gjrtimmer
Copy link

Any update ?

So can somebody please share how I can run this in some kind of development / testing mode ?
I would like to contribute because this issue has been open since May.

@jacobgkau
Copy link
Member

So can somebody please share how I can run this in some kind of development / testing mode ?

After you clone the repository and make any changes you want to test, you can install the build dependencies with sudo apt build-dep pop-plymouth-theme, then build the package with dpkg-buildpackage -b -uc -us.

@gjrtimmer
Copy link

@jacobgkau Thank you very much, just for clarity, after I build the package I can install it, is there an easy way / command to revert to the official / current ?

@jacobgkau
Copy link
Member

@jacobgkau Thank you very much, just for clarity, after I build the package I can install it, is there an easy way / command to revert to the official / current ?

You would install the package with sudo dpkg -i ./package.deb and revert to current with sudo apt upgrade.

@gjrtimmer
Copy link

@jacobgkau Thank you

@13r0ck
Copy link
Contributor

13r0ck commented Nov 12, 2021

Should be closed because of #25

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 a pull request may close this issue.

7 participants