Hi
I am experiencing a lot of crashes just after logging in into GNOME. I am using Fedora 28 fully updated and upgraded from 27.
I have already tried to remove all the extensions from .local/share/gnome-shell/extensions
But it still happens. It does not happens always, but as soon as it happens I have to reboot.
Any ideas?
On 05/31/2018 11:23 AM, andrea via users wrote:
I am experiencing a lot of crashes just after logging in into GNOME. I am using Fedora 28 fully updated and upgraded from 27.
I have already tried to remove all the extensions from .local/share/gnome-shell/extensions
But it still happens. It does not happens always, but as soon as it happens I have to reboot.
Any ideas?
Have you checked the journal to see if there's a message or stack trace about what happened?
On 31/05/18 19:27, Samuel Sieb wrote:
Have you checked the journal to see if there's a message or stack trace about what happened?
Here is it
username connecting is "jackie"
this is the only thing I can see between the login and logout
Jun 03 16:10:27 bomba gnome-session[9922]: gnome-session-binary[9922]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary Jun 03 16:10:27 bomba gnome-session-binary[9922]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
here is the list
Jun 03 16:10:27 bomba audit[9900]: USER_AUTH pid=9900 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_unix,pam_gnome_keyring acct="jackie" exe="/usr/libexec/gdm-session-worker" hostname=bomba addr=? terminal=/dev/tty1 res=success' Jun 03 16:10:27 bomba audit[9900]: USER_ACCT pid=9900 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="jackie" exe="/usr/libexec/gdm-session-worker" hostname=bomba addr=? terminal=/dev/tty1 res=success' Jun 03 16:10:27 bomba audit[9900]: CRED_ACQ pid=9900 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_unix,pam_gnome_keyring acct="jackie" exe="/usr/libexec/gdm-session-worker" hostname=bomba addr=? terminal=/dev/tty1 res=success' Jun 03 16:10:27 bomba audit[9900]: USER_ROLE_CHANGE pid=9900 uid=0 auid=1001 ses=16 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='pam: default-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 selected-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 exe="/usr/libexec/gdm-session-worker" hostname=bomba addr=? terminal=/dev/tty7 res=success' Jun 03 16:10:27 bomba systemd-logind[888]: New session 16 of user jackie. -- Subject: A new session 16 has been created for user jackie -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
On 03/06/18 16:16, andrea via users wrote:
On 31/05/18 19:27, Samuel Sieb wrote:
Have you checked the journal to see if there's a message or stack trace about what happened?
Here is it
username connecting is "jackie"
this is the only thing I can see between the login and logout
Jun 03 16:10:27 bomba gnome-session[9922]: gnome-session-binary[9922]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary Jun 03 16:10:27 bomba gnome-session-binary[9922]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
here is the list
Jun 03 16:10:27 bomba audit[9900]: USER_AUTH pid=9900 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_unix,pam_gnome_keyring acct="jackie" exe="/usr/libexec/gdm-session-worker" hostname=bomba addr=? terminal=/dev/tty1 res=success' Jun 03 16:10:27 bomba audit[9900]: USER_ACCT pid=9900 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="jackie" exe="/usr/libexec/gdm-session-worker" hostname=bomba addr=? terminal=/dev/tty1 res=success' Jun 03 16:10:27 bomba audit[9900]: CRED_ACQ pid=9900 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_unix,pam_gnome_keyring acct="jackie" exe="/usr/libexec/gdm-session-worker" hostname=bomba addr=? terminal=/dev/tty1 res=success' Jun 03 16:10:27 bomba audit[9900]: USER_ROLE_CHANGE pid=9900 uid=0 auid=1001 ses=16 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='pam: default-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 selected-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 exe="/usr/libexec/gdm-session-worker" hostname=bomba addr=? terminal=/dev/tty7 res=success' Jun 03 16:10:27 bomba systemd-logind[888]: New session 16 of user jackie. -- Subject: A new session 16 has been created for user jackie -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
Opened a bug report
On 03/06/18 16:40, andrea via users wrote:
On 03/06/18 16:16, andrea via users wrote:
On 31/05/18 19:27, Samuel Sieb wrote:
Have you checked the journal to see if there's a message or stack trace about what happened?
Here is it
username connecting is "jackie"
this is the only thing I can see between the login and logout
Jun 03 16:10:27 bomba gnome-session[9922]: gnome-session-binary[9922]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary Jun 03 16:10:27 bomba gnome-session-binary[9922]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
Have performed a full reinstall of Fedora 28. Deleted (for some users) every single . file. After a few day it stated again.
Have now reluctantly switched to KDE + SDDM.
Il giorno ven 8 giu 2018 alle 21:49, andrea via users users@lists.fedoraproject.org ha scritto:
On 03/06/18 16:40, andrea via users wrote:
On 03/06/18 16:16, andrea via users wrote:
On 31/05/18 19:27, Samuel Sieb wrote:
Have you checked the journal to see if there's a message or stack trace about what happened?
Here is it
username connecting is "jackie"
this is the only thing I can see between the login and logout
Jun 03 16:10:27 bomba gnome-session[9922]: gnome-session-binary[9922]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary Jun 03 16:10:27 bomba gnome-session-binary[9922]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
Have performed a full reinstall of Fedora 28. Deleted (for some users) every single . file. After a few day it stated again.
Have now reluctantly switched to KDE + SDDM.
I haven't followed all the thread... Have you tried GNOME Classic?
I guess I'm having the same problem on Fedora 28, but I didn't have the time to debug it yet so I switched to GNOME Classic, which works fine.
On 14/06/18 05:27, Federico Bruni wrote:
I haven't followed all the thread... Have you tried GNOME Classic?
I guess I'm having the same problem on Fedora 28, but I didn't have the time to debug it yet so I switched to GNOME Classic, which works fine.
When you say "same problem" and "works fine": is your problem 100% reproducible?
Difficult to tell if it works or not as the problem seems to appear only after hours from the boot. And I did read that GNOME improved garbage collection in javascript...
If you have 100% login crash, it is probably something else.
Which one are you?
Il giorno gio 14 giu 2018 alle 8:34, andrea via users users@lists.fedoraproject.org ha scritto:
On 14/06/18 05:27, Federico Bruni wrote:
I haven't followed all the thread... Have you tried GNOME Classic?
I guess I'm having the same problem on Fedora 28, but I didn't have the time to debug it yet so I switched to GNOME Classic, which works fine.
When you say "same problem" and "works fine": is your problem 100% reproducible?
Difficult to tell if it works or not as the problem seems to appear only after hours from the boot.
Ok, then it's different.
And I did read that GNOME improved garbage collection in javascript...
If you have 100% login crash, it is probably something else.
Which one are you?
The first time I upgraded to Fedora 28, about 10 days ago, it crashed at login only at first try, not the second try. Recently it crashed 100% of times, so I changed to GNOME Classic, which works.