sakaki- / sakaki-tools

Overlay containing various utility ebuilds for Gentoo on EFI.
78 stars 53 forks source link

gnome login issue (EFI guide related?) #24

Open sarnold opened 4 years ago

sarnold commented 4 years ago

This has been somewhat intermittent, and even when it shows up (like now) I don't see any errors in the logs other than the gdm/greeter.log which is pretty much all errors (except nothing that points to a login freeze). What happens is this:

  1. after boot up, gdm looks fine
  2. try to login, as soon as you hit <enter> on the password the GUI freezes
  3. poke at ctl-alt-F1 (or F2) a couple of times before it switches
  4. Hmm..
  5. switch back to vt7 and try to "unlock"
  6. watch it freeze
  7. repeat

At some point you can come back and login (maybe). Right now I haven't been able to use the GUI since I rebooted the machine several days ago. Just rebooted a few minutes ago, still locked out of GDM. Recent greeter log looks like this:

Have you possibly seen this before? Any thoughts? I'm out of ideas (and almost out of a job). Thanks!

The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error:   Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server
dbus-daemon[4105]: [session uid=994 pid=4105] Activating service name='org.a11y.Bus' requested by ':1.11' (uid=994 pid=4115 comm="/usr/bin/gnome-shell " label="kernel")
dbus-daemon[4105]: [session uid=994 pid=4105] Successfully activated service 'org.a11y.Bus'
GNOME Shell-Message: 14:33:27.647: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
GNOME Shell-Message: 14:33:27.647: Will monitor session c1
dbus-daemon[4105]: [session uid=994 pid=4105] Activating service name='org.freedesktop.portal.IBus' requested by ':1.13' (uid=994 pid=4204 comm="ibus-daemon --panel disable " label="kernel")
dbus-daemon[4105]: [session uid=994 pid=4105] Successfully activated service 'org.freedesktop.portal.IBus'
dbus-daemon[4188]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=994 pid=4115 comm="/usr/bin/gnome-shell " label="kernel")
dbus-daemon[4188]: Successfully activated service 'org.a11y.atspi.Registry'
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
GNOME Shell-Message: 14:33:28.658: Failed to get PolKit permission: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.bolt.enroll is not registered
dbus-daemon[4105]: [session uid=994 pid=4105] Activating service name='org.freedesktop.portal.IBus' requested by ':1.21' (uid=994 pid=4282 comm="ibus-daemon --panel disable -r --xim " label="kernel")
dbus-daemon[4105]: [session uid=994 pid=4105] Successfully activated service 'org.freedesktop.portal.IBus'

(gnome-shell:4115): Clutter-WARNING **: 14:33:28.789: Getting invalid resource scale property

** (gnome-shell:4115): WARNING **: 14:33:28.803: Could not issue 'StartUnit' systemd call

(gnome-shell:4115): IBUS-WARNING **: 14:33:28.853: Unable to connect to ibus: The connection is closed

** (gnome-shell:4115): WARNING **: 14:33:28.854: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.bolt.enroll is not registered

(gsd-dummy:4316): GLib-GIO-CRITICAL **: 14:33:28.875: g_bus_own_name: assertion 'g_dbus_is_name (name) && !g_dbus_is_unique_name (name)' failed

(gsd-dummy:4332): GLib-GIO-CRITICAL **: 14:33:28.877: g_bus_own_name: assertion 'g_dbus_is_name (name) && !g_dbus_is_unique_name (name)' failed

(gsd-sharing:4315): sharing-plugin-WARNING **: 14:33:28.883: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files

(gsd-sharing:4315): sharing-plugin-WARNING **: 14:33:28.883: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files

(gsd-sharing:4315): sharing-plugin-WARNING **: 14:33:28.884: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files

(gsd-sharing:4315): sharing-plugin-WARNING **: 14:33:28.884: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 569, clipping.
>                   X11 cannot support keycodes above 255.
> Internal error:   Could not resolve keysym Invalid
Errors from xkbcomp are not fatal to the X server
Gjs-Message: 14:33:28.959: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1637]: reference to undefined property "MetaWindowXwayland"
openConnection: connect: No such file or directory
cannot connect to braille devices daemon brltty at :0

(gsd-media-keys:4340): media-keys-plugin-WARNING **: 14:33:29.217: Failed to grab accelerator for keybinding settings:playback-random

(gsd-media-keys:4340): media-keys-plugin-WARNING **: 14:33:29.217: Failed to grab accelerator for keybinding settings:playback-repeat

(gsd-media-keys:4340): media-keys-plugin-WARNING **: 14:33:29.217: Failed to grab accelerator for keybinding settings:hibernate

(gsd-media-keys:4340): media-keys-plugin-WARNING **: 14:33:29.217: Failed to grab accelerator for keybinding settings:rfkill
GNOME Shell-Message: 14:33:29.595: Registering session with GDM
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 569, clipping.
>                   X11 cannot support keycodes above 255.
> Internal error:   Could not resolve keysym Invalid
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 569, clipping.
>                   X11 cannot support keycodes above 255.
> Internal error:   Could not resolve keysym Invalid
Errors from xkbcomp are not fatal to the X server
sarnold commented 4 years ago

Disabling wayland for the greeter gives the same result (except the screen goes black instead of freezing). I switched that back and enabled debug in gdm/custom.conf but that seems not so helpful either.

greeter.log

sarnold commented 4 years ago

aaand I had to wait this long before I could login. Rebooted the machine, can't login again...

sarnold commented 4 years ago

Also, .xinitrc with dbus-launch and gnome-session works, along with sddm. I'm about out of ideas what to look for.

sakaki- commented 4 years ago

This isn't something I've seen on any of my own systems I'm afraid. Your best bet might be to post on the Gentoo forums (if you haven't already) to see if anyone there can assist. The keymap compiler errors have been reported elsewhere (e.g. here) and are probably not the root issue.

sarnold commented 4 years ago

Thanks, after the latest updates there are several gnome pkg versions (I think 3.36.x is the latest?) and sddm goes black screen/dead keyboard now. I tried the startx thing again and then tried gdm, and it let me login (but I haven't done another reboot/login test yet). I haven't filtered through the log noise yet, but I made a bug i'm still collecting logs for: https://bugs.gentoo.org/738284

sakaki- commented 3 years ago

31 Oct 2020: sadly, due to legal obligations arising from a recent change in my 'real world' job, I must announce I am standing down as maintainer of this project with immediate effect. For the meantime, I will leave the repo up (for historical interest, and since the ebuilds etc. may be of use to others); however, I plan no further updates, nor will I be accepting / actioning further pull requests or bug reports from this point. Email requests for support will also have to be politely declined, so, please treat this as an effective EOL notice.

For further details, please see my post here.

If you have used my EFI Guide (and this repo) to install your PC-based Gentoo system, it should still continue to work for some time, but you should now take steps to migrate to a baseline Gentoo Handbook install (since the underlying tools, such as buildkernel, will also now no longer be supported and may eventually fail as more modern kernels etc. are released).

With sincere apologies, sakaki ><