[Bug 1022727] yast2 problem: Window does not open if started remotely via ssh

http://bugzilla.suse.com/show_bug.cgi?id=1022727 http://bugzilla.suse.com/show_bug.cgi?id=1022727#c10 --- Comment #10 from Rainer Krienke <krienke@uni-koblenz.de> --- Thanks for your answer. The local user was not the problem nor NFS. I myself was the problem, so first of all sorry for wasting your time... I tried a lot since yesterday eg installed a new SLES12SP2, a new 42.2 system with NFS and with rootfs-encryption like my desktop where I have this problem. Doing so I suddenly remembered that when I first used 42.2 there was an annoying keyring dialog upon kde login asking me to unlock it. Its grabbing the keyboard and since I use kde wallet I now had to unlock two keyrings gnome and kde, which is of course nonsense. So I wanted to get rid of the gnome-keyring tried several hints I could google quickly but non of them help and finally I decided to commit a "murder" at gnome-keyring. I uninstalled the rpm gnome-keyring using --nodepos to ignore shown dependencies. The annoying keyring dialog upon login was gone from there on, but its revenge haunted me from this time on, because the removal caused the ssh problem with yast2. I verified this in between by re-installing gnome-keyring (remote yast2 works after kde-relogin) and removing gnome-keyring again (remote yast2 no longer works on SLES12SP2). Strange enough I can login remotely anywhere and everything works except for SLES12SP2. So this is the problem is know and not a real 42.2 problem, since ignoring dependencies is dangerous, I know... Does perhaps by chance someone know how to avoid the modal gnome-keyring unlock window upon kde login ....? So you can close this bug. Thanks a lot again. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com