Open ghost opened 4 years ago
I'm not sure I follow - at what point did you have full access without entering a password? 1 - Started PC 2 - recognized wrong monitor as main 3 - you unplugged hdmi, other monitor became primary 4 - you entered your password? and logged in to decrypt and work with your pc?
Or you didn't have to enter your password, and it just logged you in (and decrypted your home folder)?
At the 3. point. If the vga became primary it automaticaly login without entered password.
My settings are i ve to enter password after start for login. NoT automaticaly.
Am 19.01.20 um 02:08 schrieb Michael Webster
I'm not sure I follow - at what point did you have full access without entering a password? 1 - Started PC 2 - recognized wrong monitor as main 3 - you unplugged hdmi, other monitor became primary 4 - you entered your password? and logged in to decrypt and work with your pc?
Or you didn't have to enter your password, and it just logged you in (and decrypted your home folder)?
-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/linuxmint/cinnamon/issues/9123#issuecomment-575954477
You can understand the big problem and waht's going on now?
Wouldn't this be an issue with lightDM? If you're not logged in and have no session, this has nothing to do with Cinnamon right?
Can you reproduce the problem with other DEs?
I find it very hard to believe the DM would log you in like that without a password, and even if it did, that it would have access to the passphrase to decrypt your data (there's a technical limitation at play here)... PAM just can't do that afaik.
Or do you mean you already logged in? and this is a locked or resumed session maybe? If so, then we're looking at the screensaver... not the display manager.
Sorry, it's not clear at all to me what is going on.
Wouldn't this be an issue with lightDM? If you're not logged in and have no session, this has nothing to do with Cinnamon right?
This smells of LightDM...
Can confirm, sometimes after hibernation I see this issue with external display connected. Experiencing this bug since 2016.