Xfce Forum

Sub domains
 

You are not logged in.

#1 2020-07-19 14:05:24

semanis
Member
Registered: 2020-04-06
Posts: 4

Have to login twice on cold boot

Running Fedora 31,  I have to login twice on cold/warm boot.   After the first login attempt,  the screen blanks as if it's going to load the desktop, then I'm taken right back to the login prompt,  where the second login works as expected.   On logout,  I can re-login again with a single/normal login.   But anytime I boot the system,  a double login is required. 

This problem occurs on a fresh install of Fedora.

OS: Fedora release 31 (Thirty One)
kernel: Linux computer 5.7.8-100.fc31.x86_64 #1 SMP Thu Jul 9 15:16:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
xfce version: 4.14
CPU: Intel Core i7-7820X
GPU:NVIDIA GTX 1070
GPU Driver: NVIDIA proprietary 440.100

~/.xsession-errors shows this:

(xfce4-session:4283): xfce4-session-WARNING **: 09:42:56.892: xfsm_manager_load_session: Something wrong with /home/semanis/.cache/sessions/xfce4-session-computer:0, Does it exist? Permissions issue?

(wrapper-2.0:4714): Gtk-WARNING **: 09:42:58.048: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner PulseaudioButton)

(wrapper-2.0:4715): Gtk-WARNING **: 09:42:58.412: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner XfceArrowButton)
xscreensaver: 09:43:13: no keyboard or mouse data in /proc/interrupts?

Any feedback appreciate,

Thanks.

Offline

#2 2020-07-19 15:59:36

ToZ
Moderator
From: Canada
Registered: 2011-06-02
Posts: 6,865

Re: Have to login twice on cold boot

If fedora is like other distros, it will make a backup of the ~/.xsession-errors file before creating a new one for the current session. The file you'd want to review is ~/.xsession-errors.old (or .bak). Feel free to post the content of that file.

Offline

#3 2020-07-23 15:37:44

semanis
Member
Registered: 2020-04-06
Posts: 4

Re: Have to login twice on cold boot

Here's the contents of .xsession-errors.old:

/usr/bin/iceauth:  creating new authority file /run/user/1000/ICEauthority
xfce4-session-Message: 09:26:36.211: SSH authentication agent is already running
gpg-agent[1817]: WARNING: "--write-env-file" is an obsolete option - it has no effect
gpg-agent[1818]: gpg-agent (GnuPG) 2.2.20 started

(xfce4-session:1378): xfce4-session-WARNING **: 09:26:36.218: gpg-agent returned no PID in the variables

(xfce4-session:1378): xfce4-session-WARNING **: 09:26:36.220: xfsm_manager_load_session: Something wrong with /home/semanis/.cache/sessions/xfce4-session-computer:0, Does it exist? Permissions issue?

(wrapper-2.0:1840): Gtk-WARNING **: 09:26:37.506: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner PulseaudioButton)

(wrapper-2.0:1841): Gtk-WARNING **: 09:26:37.789: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner XfceArrowButton)
[2161:27:0723/092655.965040:ERROR:webrtc_video_engine.cc(3333)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
xscreensaver: 09:26:57: no keyboard or mouse data in /proc/interrupts?
[2161:27:0723/092735.742051:ERROR:stun_port.cc(96)] Binding request timed out from [0:0:0:x:x:x:x:x]:49736 (any)
IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

[0723/102745.199817:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly

(Thunar:1834): Gtk-CRITICAL **: 10:27:48.959: gtk_main_quit: assertion 'main_loops != NULL' failed
gpg-agent[1818]: SIGTERM received - shutting down ...
gpg-agent[1818]: gpg-agent (GnuPG) 2.2.20 stopped

Offline

#4 2020-07-23 15:55:08

ToZ
Moderator
From: Canada
Registered: 2011-06-02
Posts: 6,865

Re: Have to login twice on cold boot

Doesn't look like its happening from Xfce.

Which display manager are you using? You might want to have a look through it's logs. Also review the Xorg.0.log.old file.

Offline

#5 2020-07-23 17:32:05

semanis
Member
Registered: 2020-04-06
Posts: 4

Re: Have to login twice on cold boot

Fedora defaults to lightdm. I'll do some digging through the logs, thanks.

Offline

#6 2020-07-24 05:09:12

peter.48
Member
Registered: 2017-01-31
Posts: 39

Re: Have to login twice on cold boot

Some time ago I had the same problem (since F25), in my case this double login was caused by leaving "localhost.localdomain" during installation. Check if in /etc/hostname you have "localhost.localdomain" or your machine name. I don't know why but it seems that without a machine name LightDM launches two sessions...

Offline

Board footer

Powered by FluxBB