[Bug 1091818] New: After starting a Wayland Plasma session and leaving the session, login into a normal Plasma session does not work
http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 Bug ID: 1091818 Summary: After starting a Wayland Plasma session and leaving the session, login into a normal Plasma session does not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: freek@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I started a Wayland Plasma session. Because being unable to enter certain characters in that session I finished that session and got the login screen. I changed the type of session to a classic Plasma session and entered the password. After a while I did not enter the session, but the system returned to the login screen. I needed to reboot, to be able to start a normal Plasma session. -- 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#c1 Neil Rickert <nwr10cst-oslnx@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx@yahoo.com --- Comment #1 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- 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#c2 --- Comment #2 from Freek de Kruijf <freek@opensuse.org> --- (In reply to Neil Rickert from comment #1)
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.
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. -- 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 <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #3 from Wolfgang Bauer <wbauer@tmo.at> --- (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#c4 --- Comment #4 from Freek de Kruijf <freek@opensuse.org> --- (In reply to Wolfgang Bauer from comment #3)
(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?
After loging in into a Plasma Wayland session, and logging out immediately, choosing a normal Plasma session and trying to log in, the login screen reappeared. So I went to tty1 logged in into my account and gave the command "ps ux", which showed the following output: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND freek 2576 0.0 0.2 72992 8272 ? Ss 09:52 0:00 /usr/lib/systemd/systemd --user freek 2577 0.0 0.0 118736 3540 ? S 09:52 0:00 (sd-pam) freek 2837 0.1 0.5 268759112 22128 ? SNl 09:52 0:00 /usr/bin/baloo_file freek 2923 0.0 0.0 241520 3440 ? Ss 09:52 0:00 gpg-agent --homedir /home/freek/.gnupg --use-standard-socket --daem on freek 2982 0.0 0.0 113028 3576 ? SLl 09:52 0:00 scdaemon --multi-server freek 6100 0.7 0.1 17952 7652 tty1 Ss 09:54 0:00 -bash freek 9029 50.0 0.0 29812 1588 tty1 R+ 09:54 0:00 ps ux I noticed /usr/bin/baloo_file and did a "lsof -p 2837" which showed some log files of which .local/share/sddm/xorg-session.log contains: gpg-agent: a gpg-agent is already running - not starting a new one After that I killed process 2923 and tried to log in again into the normal Plasma session, which succeeded. So it seems gpg-agent is the culprit. -- 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 <nwr10cst-oslnx@yahoo.com> --- 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#c6 --- Comment #6 from Freek de Kruijf <freek@opensuse.org> --- (In reply to Neil Rickert from comment #5)
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.
KMail or rather akonadi stores passwords in a gpg protected KWallet. Akonadi starts immediately at session start, so I get immediately a prompt for the gpg password phrase. -- 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 <nwr10cst-oslnx@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #7 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- 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#c8 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com Flags| |needinfo? --- Comment #8 from Fabian Vogt <fvogt@suse.com> --- AFAIK gpg-agent is started using dbus activation on the session bus. What's the PPID of the remaining 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 <nwr10cst-oslnx@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #9 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- 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#c10 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tchvatal@suse.com Flags| |needinfo?(tchvatal@suse.com | |) --- Comment #10 from Fabian Vogt <fvogt@suse.com> --- @gpg2 bugowner: How is gpg-agent supposed to start and stop itself in a X session and Wayland session? -- 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 <nwr10cst-oslnx@yahoo.com> --- 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 http://bugzilla.opensuse.org/show_bug.cgi?id=1091818#c12 Tomáš Chvátal <tchvatal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|tchvatal@suse.com |pmonrealgonzalez@suse.com Flags|needinfo?(tchvatal@suse.com |needinfo?(pmonrealgonzalez@ |) |suse.com) --- Comment #12 from Tomáš Chvátal <tchvatal@suse.com> --- I am not really the gpg2 bugowner, Pedro is taking care of it, so Pedro? :)) -- 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 <oorlov@suse.com> 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 Pedro Monreal Gonzalez <pmonrealgonzalez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|opensuse-kde-bugs@opensuse. |pmonrealgonzalez@suse.com |org | -- 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 <nwr10cst-oslnx@yahoo.com> --- 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#c16 --- Comment #16 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- Responding to c#15
It doesn't seem that wayland is supported in 42.3.
Now Wayland is supported in Leap 15.0 and in Tumbleweed, but not in 42.3 The tests that I described in c#14 were with Tumbleweed, and this bug was reported for Tumbleweed. It might still be broken for 15.0, which I did not test. If it works for Tumbleweed, that's good enough for me, because that's the future. -- 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 <freek@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #20 from Freek de Kruijf <freek@opensuse.org> --- Closing the bug report. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com