Double login after suspend

Hi there,
so these are my current power settings and they are working out, expect that sometimes when I wake up fedora and log in.
Right after unlocking my desktop, I see all my application windows (which are usually spreaded over several spaces) rendered on one space. It’s just for about 1-2 seconds, then the login mask returns and I have to login again. I can’t make sense of this. It doesn’t happen on a regular basis. so the pattern isn’t obvious yet…
image
image

Has anyone experienced something similar already?

Thanks in advance

I think this is a Gnome bug. I have ran into it previously, and it was related to the Gnome-Session but I cannot remember having solved it, it just disappeared after updates. Perhaps check some Gnome issues (https://bugzilla.gnome.org/) and see if it is already reported.

Just to be sure, check if you have a .profile file in your home directory with this line inside:
export DESKTOP_LOCKED=yes
I use it to lock my session because I use autologin, but when I remove the autologin, I need to login twice: one for starting session, the other for unlock the session.

@jakfrost thanks for your reply. I couldn’t find a related bug on bugzilla.
I then searched on the gnome-gitlab-site since they are in the process of migrating to gitlab, but then I lost track cause there is a lot of stuff and I didn’t know on which subproject to file an issue… any ideas? (:
Thanks anyways.

Hey @tartare thanks for your reply. I don’t have a .profile in my home yet.
Hmm, as you mentioned it, I remember experiencing something similar on xubuntu, when using autologin, but that’s not the case here.
So no activated autologin nor .profile on my side.
I can’t see why creating a .profile would make a difference then, but I will check it out. :thinking:

@locke No need to create this file, the tip is to remove the line from the file, but if you don’t have a .profile file … you don’t have a line to remove :wink:
It was worth a try.

@locke You’re welcome. My first thought is that it is related to Gnome’s handling of the Desktop state when you recover from a hibernate state. I believe it to be an artifact of that process, and not entirely certain it isn’t just inelegant handling of that process. I would file it as a bug at Gnomes GitLab site with as much detail (like you have here) outlining the problem. One thing you could try for curiosity sake, is to wait a minute or two before logging in to see if it behaves the same.

@jakfrost Ok, that could be the case.
The app window arrangement restores properly if I switch to another space.
Also the gnome-shell crashes usually during that event.
I opened an issue in the gnome-shell project on gitlab here.
Hope they can make sense of this.
I just waited a few seconds this time before I triggered the unlock event and it worked without crashes this time. I’m curious if this approach will completely solve the situation. Will keep you posted then.

Update:
It seems to be related to another process which isn’t finished when I login too quickly.
I noticed after the described problem occurs and the gnome-shell crashes that also the entry for “Hibernate” isn’t present under my power settings anymore. Instead “2 seconds” is then preselected and seems to take over the place of “Hibernate”.

If I wait a few seconds it seems to function as expected.

I think there has been some efforts to make the start up, and restart states appear more fluent for the user. I remember a discussion about it, just not sure where. Basically it was in an effort to get rid of those extended pauses that you would get when starting the gnome session for login. I find in my case, I still have issues with the Gnome session sometimes kicking me out to the login screen if I close Evolution (only Evolution so far) by clicking on the window close button in the top right corner of the window. This comes and goes as updates flow from upstream, so I am uncertain what causes it, maybe dbus?

Hmm, I’m kinda used to going in hibernate mode, leaving everything as it is and coming back on the next day to continue working where I left off. (that’s how I used to work on macOS).
Since session restore doesn’t seem to work, Hibernate was my next bet.
If I keep the “wait a few seconds till you tryin’ to login” approach in mind, I think I’m good for now.

Could it also related to the size of my swap partition? I got 16gb ram but my swap is just 8gb :thinking:

You could be right about dbus. At least my var_log_messages refers to dbug:

    var_log_messages
    --Jun 02 20:26:28 smittie gnome-shell[4462]: st_widget_get_theme_node called on the widget [0x563b87651c80 StBin:insensitive] which is not in the stage.
    Jun 02 20:26:28 smittie gnome-shell[4462]: st_widget_get_theme_node called on the widget [0x563b87651c80 StBin:insensitive] which is not in the stage.
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.229/org/ayatana/NotificationItem/Joplin1
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.79/org/ayatana/NotificationItem/indicator_solaar
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.69/org/ayatana/NotificationItem/Skype1
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.82/StatusNotifierItem
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.81/StatusNotifierItem
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:28 smittie gnome-shell[4462]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:30 smittie gnome-shell[4462]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
    Jun 02 20:26:32 smittie org.gnome.Shell.desktop[31337]: current session already has an ibus-daemon.
    Jun 02 20:26:32 smittie gnome-shell[31337]: g_dir_open_with_errno: assertion 'path != NULL' failed
    Jun 02 20:26:32 smittie gnome-shell[31337]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
    Jun 02 20:26:32 smittie gnome-shell[31337]: g_dir_open_with_errno: assertion 'path != NULL' failed
    Jun 02 20:26:32 smittie gnome-shell[31337]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
    Jun 02 20:26:32 smittie gnome-shell[31337]: Telepathy is not available, chat integration will be disabled.
    Jun 02 20:26:32 smittie gnome-shell[31337]: loading user theme: /home/smittie/.themes/Juno/gnome-shell/gnome-shell.css
    Jun 02 20:26:33 smittie gnome-shell[31337]: Extension user-theme@gnome-shell-extensions.gcampax.github.com already installed in /home/smittie/.local/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com will not be loaded
    Jun 02 20:26:33 smittie gnome-shell[31337]: meta_sound_player_play_from_theme: assertion 'META_IS_SOUND_PLAYER (player)' failed
    Jun 02 20:26:33 smittie gnome-shell[31337]: Ignoring length property that isn't a number at line 69, col 13
    Jun 02 20:26:33 smittie gnome-shell[31337]: Ignoring length property that isn't a number at line 69, col 13
    Jun 02 20:26:33 smittie gnome-shell[31337]: Actor StBoxLayout (0x55b53577a070) received the invalid value nan as minimum/natural size
    Jun 02 20:26:33 smittie gnome-shell[31337]: st_widget_get_theme_node called on the widget [0x55b53576c920 StBin:insensitive] which is not in the stage.
    Jun 02 20:26:33 smittie gnome-shell[31337]: st_widget_get_theme_node called on the widget [0x55b53576c920 StBin:insensitive] which is not in the stage.
    Jun 02 20:26:33 smittie gnome-shell[31337]: Ignoring length property that isn't a number at line 69, col 13
    Jun 02 20:26:34 smittie gnome-shell[31337]: Ignoring length property that isn't a number at line 69, col 13
    Jun 02 20:26:34 smittie gnome-shell[31337]: Ignoring excess values in shadow definition
    Jun 02 20:26:34 smittie gnome-shell[31337]: Ignoring excess values in shadow definition
    Jun 02 20:26:34 smittie gnome-shell[31337]: Ignoring excess values in shadow definition
    Jun 02 20:26:34 smittie gnome-shell[31337]: Ignoring excess values in shadow definition
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.79/org/ayatana/NotificationItem/indicator_solaar
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.69/org/ayatana/NotificationItem/Skype1
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.82/StatusNotifierItem
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.81/StatusNotifierItem
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.229/org/ayatana/NotificationItem/Joplin1
    Jun 02 20:26:34 smittie gnome-shell[31337]: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36)
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: [AppIndicatorSupport-FATAL] unable to update overlay icon
    Jun 02 20:26:34 smittie gnome-shell[31337]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
    --

My guess is that it’s related to the “time ++” gnome extension.
Since I disabled it the crashes are almost gone. No double login anymore. Yay.

2 Likes