http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 http://bugzilla.opensuse.org/show_bug.cgi?id=1091818#c1 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx@yahoo.com --- Comment #1 from Neil Rickert --- I'm surprised to see this. I ran into this problem a while ago. But it is no longer happening for me. When I first saw the problem, after login to either Plasma-wayland or Gnome-wayland, any attempt to login to Plasma-X or Gnome-X would fail (return to login screen). I have not had that happen for a while now. Perhaps it depends on graphics card. I seem to recall having this problem with both SDDM and with GDM. And I could still login it Icewm. The workaround that I used: CTRL-ALT-F1 to get a command line. Then kill any processes running under my userid that were older than the current login. Usually killing the "systemd" process was enough to take down the rest. After that, I could login to X sessions with Plasma and Gnome. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 http://bugzilla.opensuse.org/show_bug.cgi?id=1091818#c3 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #3 from Wolfgang Bauer --- (In reply to Freek de Kruijf from comment #2)

I tried this and indeed I can start a Plasma session, but I consider this still to be a bug. Closing the Wayland session should end all processes which are part of that session.

And what processes were still running? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 http://bugzilla.opensuse.org/show_bug.cgi?id=1091818#c5 --- Comment #5 from Neil Rickert --- I have just rechecked. I am not having a problem. I tested with both GDM and with SDDM. Logout from plasma-wayland and into plasma X -- no problem. However, gpg-agent is not running here. My understanding is that gpg-agent is not automatically started. Rather, it is started when first needed. So maybe you are doing something to start it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 http://bugzilla.opensuse.org/show_bug.cgi?id=1091818#c7 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #7 from Neil Rickert --- I am marking this as confirmed. I logged into Plasma-wayland. And then I ran a command that use gpg, so that gpg-agent was started. I then logged out, and logged back into Plasma-X. And the session failed to start. So I killed the running gpg-agent, and then I was able to start the X-session. Here's my analysis of what is happening: When running Plasma-X, "gpg-agent" is automatically started as part of X startup. And the X-session is a child of gpg-agent. So when the X-session exits, gpg-agent shuts down. When running Plasma-Wayland, "gpg-agent" is not started. It is, however, started on demand when first used. As such, it is independent of the Wayland session and does not automatically shutdown when the Wayland session ends. But it blocks the startup of X because that fails already when starting gpg-agent. Solution: Both X and Wayland should be handled the same way. Either both should start gpg-agent and make the desktop session a child of that agent -- or neither should start gpg-agent. In either case you would not run into this problem. Temporary workaround: killing gpg-agent in "$HOME/.config/plasma-workspace/shutdown" should work. The man pages for gpg-agent indicate how to kill gpg-agent. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 http://bugzilla.opensuse.org/show_bug.cgi?id=1091818#c9 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #9 from Neil Rickert --- Created attachment 769236 --> http://bugzilla.opensuse.org/attachment.cgi?id=769236&action=edit typescript for checking "gpg-agent" process The "typescript" is from a Wayland session. The first "ps" command shows that "gpg-agent" is not running. The second command "exmh" starts "exmh" running as a GUI application. In "exmh" I read an encrypted email message. That caused "gpg-agent" to be started. The third command is "ps". It shows that gpg-agent is now running with PPID=1. As far as I know, the "gpg-agent is started using dbus activation" only applies to X-sessions, and not to Wayland sessions. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 http://bugzilla.opensuse.org/show_bug.cgi?id=1091818#c11 --- Comment #11 from Neil Rickert --- My understanding, which could be wrong, is that when an application needs to communicate with gpg-agent, it starts it. With recent gpg versions, the agent socket location is at a standard location in the file system, so does not need to be passed via the environment. Because of that, it is not necessary to start the agent at session startup. This should apply to both Tumbleweed and Leap 15.0. However, for Leap 42.3, it still needs to be started as session startup because that's using an older gpg version. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 Oleksandr Orlov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oorlov@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 http://bugzilla.opensuse.org/show_bug.cgi?id=1091818#c14 --- Comment #14 from Neil Rickert --- It does appear to be fixed, but not as you describe. On a fresh login into Plasma-Wayland, gpg-agent is not started. On a fresh login to Plasma-X11, gpg-agent is started. A fresh login to Plasma-Wayland, so gpg-agent is not running. I use a command that requires gpg-agent. And that starts gpg-agent. I then logout. I next login to Plasma-X11. I see that gpg-agent is still running from my previous Wayland session. The command that started the X11 session did not attempt to start gpg-agent this time. It looks as if the startup script for Plasma-X11 is now checking whether gpg-agent is already running, and only attempting to start it if not already running. And that solves the problem reported for this bug. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 http://bugzilla.opensuse.org/show_bug.cgi?id=1091818#c20 Freek de Kruijf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #20 from Freek de Kruijf --- Closing the bug report. -- You are receiving this mail because: You are on the CC list for the bug.