Cannot login anymore/GNOME crashes after switching user

[rugk]

I experience the following issue in Fedora 28:
1. Login as usual.
2. Lock the user session. (not logout, just "switch user"/lock)
3. Login to another user.
4. Logout of that user session.

What happens:
I cannot login to the first session anymore. GNOME or so does not seem to only crash once,
but any time I try to login afterwards. This is very strange, because I'd expect it to
just start a new session if the old one crashed.
I also cannot login to any other user anymore, afterwards.

The only way to work around the problem is to restart the whole device.

This is what the system protcols application shows me after a restart:

12:44:25 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
12:44:22 spice-vdagent: Cannot access vdagent virtio channel
/dev/virtio-ports/com.redhat.spice.0
12:44:22 spice-vdagent: Cannot access vdagent virtio channel
/dev/virtio-ports/com.redhat.spice.0
12:44:13 spice-vdagent: Cannot access vdagent virtio channel
/dev/virtio-ports/com.redhat.spice.0
12:44:13 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
12:44:11 abrtd: '/var/spool/abrt/oops-2018-06-03-12:00:15-1618-0' is not a problem
directory
12:44:11 abrtd: '/var/spool/abrt/oops-2018-06-03-12:00:15-1618-0' is not a problem
directory
12:44:11 abrtd: '/var/spool/abrt/oops-2018-06-03-11:17:54-1540-0' is not a problem
directory
12:44:10 abrtd: '/var/spool/abrt/ccpp-2017-07-30-11:57:17.340786-1525' is not a
problem directory
12:44:10 abrtd: '/var/spool/abrt/oops-2018-06-03-12:00:11-1618-0' is not a problem
directory
12:44:09 abrtd: '/var/spool/abrt/oops-2018-02-15-21:29:20-22584-0' is not a
problem directory
12:44:09 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
12:44:09 avahi-daemon: chroot.c: open() failed: No such file or directory
14:44:05 systemd-tty-ask: Failed to show password: Bad message
14:44:05 systemd-tty-ask: Failed to show password: Bad message
14:44:05 systemd-tty-ask: Invalid password file /run/systemd/ask-password/ask.au1rSh
14:43:46 kernel: rtc_cmos 00:02: nvmem registration failed

So may I report it as a bug? If so where? Rather GNOME or gdm or something at Fedora what?

[andrea]

On 01/07/18 15:00,  rugk wrote:
>  I experience the following issue in Fedora 28:
>  1. Login as usual.
>  2. Lock the user session. (not logout, just "switch user"/lock)
>  3. Login to another user.
>  4. Logout of that user session.
>  
>  What happens:
>  I cannot login to the first session anymore. GNOME or so does not seem to only crash
> once, but any time I try to login afterwards. This is very strange, because I'd expect
> it to just start a new session if the old one crashed.
>  I also cannot login to any other user anymore, afterwards.
>  
>  The only way to work around the problem is to restart the whole device.
>  
>  This is what the system protcols application shows me after a restart: 
I have been experiencing "similar" issues in GNOME, although with some
differences where not all 
users at the same time and it might take hours to trigger.

Only solution is to reboot.

I opened a bug report here with no luck so far.
https://bugzilla.redhat.com/show_bug.cgi?id=1585491

I have switched to SDDM /KDE, which have still a looooong way to go for a smooth user
experience 
around login and user switch.

Andrea

[rugk]

Okay, seems System-Monitor GNOME extension causes the issue. I've got it installed,
too. Just what to do now?

[rugk]

So, no it's not the fault. I've disabled **all my extensions** and it still
happens.

I'll post to your bug.