On 06/12/2019 08:30, Carlos E. R. wrote:
On 06/12/2019 14.05, Anton Aylward wrote:
I've just met another 'woe" in the form of getting the SDDM login to work.
Under 42.3 I used XDM, and part of the 'anton' login was to have a ~anton/.bash_profile that set up a lot of shell variables and ran 'keychain' the set up the PGP agent and GPG agent.
SDDM did not like this. As far as I can tell, anything in the .bash_profile that prompts for input (I've turned of things like 'lxrandr' now I have DID working) causes SDDM to hang.
You can not ask for user input in the graphical login process.
Granted, but these do not get called until I fire up the Konsole application, and after I login there. Or that was was the way it worked when I used XDM as a graphical login. More to the point, this is supposed to use a smart prompt mechanism that identifies the input and there are graphitic input tools for the PGP prompt. Such as 'pinentry' pinentry, pinentry-qt4, pinentry-tty, pinentry-curses, pinentry-qt, pinentry-qt5
There are various shell start scripts, each one running on different circumstances. Me, I don't do anything PGP related, that is done by the desktop start procedure.
Yes, that's my point. Why is SDDM doing this? Why isn't it deferred until the Konsole starts? I'm forced to conclude that SDDM runs a shell initially
I do not like this. I now have to manually run ~anton/.bash_profile,old after login.
I've tried googling but my google-fo hasn't met anything to do with this.
-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org