Fedora 37 hangs after graphical login

[Karlderletzte]

Hello, since yesterday i do have a big problem.
After some updates and a succesfull reboot, i first could not login 
anymore. Alsways a wrong password.
I solved this with resetting root password and my two user passwords.
Now i could login.
Root account works,
one user account (the empty one) also.
But my usually working account freezes, after i login.
If i login via terminal Ctrl-Alt-F3 it works.
So i think that something is crashed during the load after graphical 
login.
How could i See, what is going on after graphical login? The different 
steps and programs i mean. Any logfiles?

I know that one of the first thing is loading gdm? Or am i wrong?

Btw: i use wayland and GNOME. An update via dnf brings nothing.

Hope someone does have an idea.
Thanks
Jens

[karlderletzte]

Am Fr, 2023-01-06, 14:33 +0100, Karlderletzte <karlderletzte(a)holnishaus.de&gt;
schrieb:

hello,
i find out some additional info.
if i disable network before login, then the graphical login works.
perhaps someting with my autofs.
but i dont know how to read something in logs.

>  Hello, since yesterday i do have a big problem.
>  After some updates and a succesfull reboot, i first could not login
>  anymore. Alsways a wrong password.
>  I solved this with resetting root password and my two user passwords.
>  Now i could login.
>  Root account works,
>  one user account (the empty one) also.
>  But my usually working account freezes, after i login.
>  If i login via terminal Ctrl-Alt-F3 it works.
>  So i think that something is crashed during the load after graphical
>  login.
>  How could i See, what is going on after graphical login? The different
>  steps and programs i mean. Any logfiles?
>
>  I know that one of the first thing is loading gdm? Or am i wrong?
>
>  Btw: i use wayland and GNOME. An update via dnf brings nothing.
>
>  Hope someone does have an idea.
>  Thanks
>  Jens
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>  
-- 
Jens Reimer

[karlderletzte]

hurray,
i find out the source of pain.
it is the autofs.service.
after disabling it, its working.
but i do not know, why this service freeze my laptop.
i use autofs since fedora 35 and do not edit anything.

does anybody knows something about configuration of autofs, especially
changes the last month?

[stan]

On Fri, 06 Jan 2023 19:47:40 +0100
karlderletzte <karlderletzte(a)holnishaus.de&gt; wrote:

>  hurray,
>  i find out the source of pain.
>  it is the autofs.service.
>  after disabling it, its working.
>  but i do not know, why this service freeze my laptop.
>  i use autofs since fedora 35 and do not edit anything.
>  
>  does anybody knows something about configuration of autofs, especially
>  changes the last month? 
I don't have any autofs mounted filesystems, but it seems that it is
trying to mount a filesystem that isn't available.  When it happens,
try the command
journalctl -r
to see what was logged to the journal in reverse order.  So, most
recent will be first.

I think this must be something particular to your system.  I looked at
the redhat bugzilla page, and didn't find anything that seemed to be
related to your problem.  Here is the page of open bugs.

https://bugzilla.redhat.com/buglist.cgi?quicksearch=autofs

[Tim]

On Fri, 2023-01-06 at 19:47 +0100, karlderletzte wrote:
>  it is the autofs.service.
>  after disabling it, its working.
>  but i do not know, why this service freeze my laptop.
>  i use autofs since fedora 35 and do not edit anything. 
As far as I was aware, autofs didn't do anything unless you did edit
something.  If I want it to automount something I had to customise
something.  I believe things like USB drives and optical discs were
usually handled by something else.

And my past experience with mounting things via some kind of rule or
/etc/fstab entry, was that the system would foul up at boot and
shutdown if the thing listed wasn't present for the system to act on.

I just use autofs for accessing NFS exports on another PC.  e.g. I set
the /net directory to be an automount point, then if I try to access
something like /net/rocky/home/tim autofs will mount my home directory
on the "rocky" server (that being its hostname).  That automount will
gracefully disappear after some time, rather than wedge my system (as
it would if I had made an entry in my /etc/fstab and tried to boot or
shutdown the client when the server wasn't available).
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.

[karlderletzte]

hello there,

here is my auto.master
#
# Sample auto.master file
# This is a 'master' automounter map and it has the following format:
# mount-point [map-type[,format]:]map [options]
# For details of the format look at auto.master(5).
#
#/misc	/etc/auto.misc
#
# NOTE: mounts done from a hosts map will be mounted with the
#	"nosuid" and "nodev" options unless the "suid" and
"dev"
#	options are explicitly given.
#
#/net	-hosts
#
# Include /etc/auto.master.d/*.autofs
# To add an extra map using this mechanism you will need to add
# two configuration items - one /etc/auto.master.d/extra.autofs file
# (using the same line format as the auto.master file)
# and a separate mount map (e.g. /etc/auto.extra or an auto.extra NIS map)
# that is referred to by the extra.autofs file.
#
#+dir:/etc/auto.master.d
#
# If you have fedfs set up and the related binaries, either
# built as part of autofs or installed from another package,
# uncomment this line to use the fedfs program map to access
# your fedfs mounts.
#/nfs4  /usr/sbin/fedfs-map-nfs4 nobind
#
# Include central master map if it can be found using
# nsswitch sources.
#
# Note that if there are entries for /net or /misc (as
# above) in the included master map any keys that are the
# same will not be seen as the first read key seen takes
# precedence.
#/cifs  /etc/auto.smb --timeout=300
#
/- /etc/auto.musik --timeout=60 --ghost
#/- /etc/auto.videos --timeout=60 --ghost
#/- /etc/auto.doku --timeout=60 --ghost
#/- /etc/auto.android --timeout=60 --ghost
+auto.master


and my auto.musik
/home/held/Musik/grosshirn/heldenmusik   
-fstype=cifs,rw,username=held,password=XXXXXX,gid=1000,uid=1000
://192.168.178.35/Heldenhome/Musik

perhaps this helps.

[karlderletzte]

Good news,
after update to kernel 6.0.18 problem is gone!

now autofs works as in the past.

[José María Terry Jiménez]

El 6/1/23 a las 14:33, Karlderletzte escribió:
>  Hello, since yesterday i do have a big problem.
>  After some updates and a succesfull reboot, i first could not login 
>  anymore. Alsways a wrong password.
>  I solved this with resetting root password and my two user passwords.
>  Now i could login.
>  Root account works,
>  one user account (the empty one) also.
>  But my usually working account freezes, after i login.
>  If i login via terminal Ctrl-Alt-F3 it works.
>  So i think that something is crashed during the load after graphical 
>  login.
>  How could i See, what is going on after graphical login? The different 
>  steps and programs i mean. Any logfiles?
>
>  I know that one of the first thing is loading gdm? Or am i wrong?
>
>  Btw: i use wayland and GNOME. An update via dnf brings nothing.
>
>  Hope someone does have an idea.
>  Thanks
>  Jens 
Hello

I'm having the same with F36 and kernel 6.0.16-200.fc36.x86_64, going to 
previous (6.0.15-200.fc36.x86_64) works fine.

Happens with and without Wayland, Gnome and MATE.

Hope helps someone

[Alessio]

I think that it could be related to this:

https://bugzilla.redhat.com/show_bug.cgi?id=2158977

https://bugzilla.kernel.org/show_bug.cgi?id=216895