| View previous topic :: View next topic |
| Author |
Message |
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
 Posted: Wed Apr 07, 2021 5:42 am Post subject: [Solved] GDM Freezes | Can't Start Gnome in Wayland |
 |
|
Hi everyone,
I'm facing this weird issue on "GDM freezing" and becoming unresponsive when launched from xdm while booting. Startx works ok, & exec gnome-session works ok in X after login.
I'm unable to fall back to tty using "Alt+Ctrl+F2" when this happens & have to power off my laptop & reboot into live usb iso to remove the gdm entry in xdm conf.
I have the following use flags:
| Code: | | USE="elogind X wayland egl gnome gtk dbus bluetooth thunderbolt branding networkmanager pulseaudio bash-completion acl -kde -qt4 -qt5 -systemd -dvd -cdr -floppy -qtwebengine -webengine" |
Would really appreciate advise on how to move forward from here. I enabled gdm debugging and this is the error message I get:
| Code: | a@gentoo $ cat /var/log/messages | grep gdm
Apr 6 16:17:13 gentoo gdm: GdmDisplay: Session never registered, failing
Apr 6 16:17:13 gentoo gdm: Child process -2622 was already dead.
Apr 6 16:17:15 gentoo gdm: Child process -2647 was already dead.
Apr 6 16:19:46 gentoo gdm: GdmDisplay: Session never registered, failing
Apr 6 16:19:46 gentoo gdm: Child process -2279 was already dead.
Apr 6 16:19:48 gentoo gdm: Child process -2305 was already dead.
Apr 6 22:53:08 gentoo gdm: GdmDisplay: Session never registered, failing
Apr 6 22:53:08 gentoo gdm: Child process -2287 was already dead.
Apr 6 22:53:08 gentoo gdm: Child process -2313 was already dead.
Apr 7 06:20:33 gentoo gdm: GdmDisplay: Session never registered, failing
Apr 7 06:20:33 gentoo gdm: Child process -2292 was already dead.
Apr 7 06:20:33 gentoo gdm: Child process -2317 was already dead.
Apr 7 06:22:04 gentoo pulseaudio[2998]: [pulseaudio] authkey.c: Failed to open cookie file '/var/lib/gdm/.config/pulse/cookie': No such file or directory
Apr 7 06:22:04 gentoo pulseaudio[2998]: [pulseaudio] authkey.c: Failed to load authentication key '/var/lib/gdm/.config/pulse/cookie': No such file or directory
Apr 7 06:22:04 gentoo pulseaudio[2998]: [pulseaudio] authkey.c: Failed to open cookie file '/var/lib/gdm/.pulse-cookie': No such file or directory
Apr 7 06:22:04 gentoo pulseaudio[2998]: [pulseaudio] authkey.c: Failed to load authentication key '/var/lib/gdm/.pulse-cookie': No such file or directory |
[Moderator edit: added [code] tags to preserve output layout. -Hu]
Last edited by the_actuary on Wed Apr 14, 2021 5:27 pm; edited 3 times in total |
|
| Back to top |
|
 |
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Wed Apr 07, 2021 7:32 am Post subject: |
|
|
| Light DM works. However, it still uses the X11 windowing system when I select default "gnome" option in light dm login. Is the issue related to wayland? How do I make gnome run on wayland? |
|
| Back to top |
|
|
kikko
Apprentice
Joined: 29 Apr 2014
Posts: 276
Location: Milan, IT
|
| Posted: Wed Apr 07, 2021 9:02 am Post subject: |
|
|
Hi the_actuary
Have you tried to start GDM using rc-service?
My suggestion is to login in a tty (using e.g. ctrl+alt+f2) and try to start it using rc-service start xdm
Moreover, as far as I know Gnome is "systemd friendly" and require some attention when using OpenRC
See the "Gnome without systemd" article in the wiki
_________________
Regards
root is the root of all evil |
|
| Back to top |
|
|
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Wed Apr 07, 2021 9:10 am Post subject: |
|
|
| kikko wrote: | Hi the_actuary
Have you tried to start GDM using rc-service?
My suggestion is to login in a tty (using e.g. ctrl+alt+f2) and try to start it using rc-service start xdm
Moreover, as far as I know Gnome is "systemd friendly" and require some attention when using OpenRC
See the "Gnome without systemd" article in the wiki |
Hi kikko,
I haven't started GDM has a rc-service. Instead I edited the xdm conf file to have the display manager as GDM & started the xdm service - like the gnome without systemd article mentions. |
|
| Back to top |
|
|
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Thu Apr 08, 2021 6:39 am Post subject: |
|
|
Can confirm it's an issue with wayland and not gdm as such. I manually launched the following and the wayland session is dead unresponsive:
| Code: | | $ XDG_SESSION_TYPE=wayland dbus-run-session gnome-session |
Am I missing something in the kernel parameters to enable wayland? |
|
| Back to top |
|
|
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Thu Apr 08, 2021 4:37 pm Post subject: |
|
|
Shifted profile to gnome/systemd from gnome, changed useflag to systemd and removed elogind useflag. Emerged packages with new use.
Problem still persists with wayland with systemd.
Good part of this change is microsoft teams works with systemd & previously didn't with openrc. |
|
| Back to top |
|
|
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Fri Apr 09, 2021 6:45 am Post subject: |
|
|
I get these errors in journalctl when during the gdm boot:
| Code: | -- Boot 9f95d30027164267a64d4dd50f9952fe --
Apr 09 12:00:06 gentoo kernel: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
Apr 09 12:00:06 gentoo kernel: tpm tpm0: tpm_try_transmit: send(): error -62
Apr 09 12:00:06 gentoo kernel: tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
Apr 09 12:00:09 gentoo systemd[1732]: Failed to start Application launched by gnome-session-binary.
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275f5
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275f4
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275f3
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275f2
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275f1
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275f0
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275ef
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275ee
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275ed
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275ec
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275eb
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275ea
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275e9
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275e8
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275e7
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127604
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127603
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127602
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127601
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127600
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275ff
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275fe
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275fd
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275fc
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275fb
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275fa
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275f9
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275f8
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275f7
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:1275f6
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127613
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127612
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127611
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127610
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12760f
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12760e
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12760d
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12760c
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12760b
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12760a
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127609
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127608
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127607
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127606
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127605
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127622
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127621
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127620
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12761f
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12761e
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12761d
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12761c
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12761b
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:12761a
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127619
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127618
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127617
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127616
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127615
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127614
Apr 09 12:00:18 gentoo kernel: kernel BUG at include/linux/mm.h:707!
Apr 09 12:00:18 gentoo kernel: kernel BUG at include/linux/mm.h:707!
Apr 09 12:00:29 gentoo kernel: [drm:drm_atomic_helper_setup_commit] *ERROR* [CRTC:33:crtc-0] cleanup_done timed out
Apr 09 12:00:29 gentoo kernel: kernel BUG at include/linux/mm.h:707!
Apr 09 12:00:39 gentoo kernel: [drm:drm_atomic_helper_setup_commit] *ERROR* [CRTC:33:crtc-0] cleanup_done timed out
Apr 09 12:00:39 gentoo kernel: kernel BUG at include/linux/mm.h:707!
Apr 09 12:00:58 gentoo kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Apr 09 12:01:57 gentoo kernel: [drm:drm_atomic_helper_setup_commit] *ERROR* [CRTC:33:crtc-0] cleanup_done timed out
Apr 09 12:01:57 gentoo kernel: kernel BUG at include/linux/mm.h:707! |
Would anyone have any idea what's going on? This is the last (currently) pending issue in my gentoo shiftover  |
|
| Back to top |
|
|
kikko
Apprentice
Joined: 29 Apr 2014
Posts: 276
Location: Milan, IT
|
| Posted: Fri Apr 09, 2021 4:56 pm Post subject: |
|
|
Hi the_actuary
Since you posted a lot of updates, it's not clear to me: do you still have issues with wayland+GDM? Or is only wayland that gives you problems?
Personally I'm not a wayland user (and neither a GNOME user), so I can be of little help in reproducing the issue myself...
Have you followed the troubleshooting session for GDM in the wiki?
This could also be a hint for your analysis:
| Quote: | | Code: | | Apr 09 12:00:09 gentoo systemd[1732]: Failed to start Application launched by gnome-session-binary |
|
You could try to launch gnome-session in debug, like
| Code: | | dbus-launch --exit-with-session gnome-session --builtin --session=gnome-classic --disable-acceleration-check --debug & |
_________________
Regards
root is the root of all evil |
|
| Back to top |
|
|
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Sat Apr 10, 2021 3:28 am Post subject: |
|
|
| kikko wrote: | Hi the_actuary
Since you posted a lot of updates, it's not clear to me: do you still have issues with wayland+GDM? Or is only wayland that gives you problems?
Personally I'm not a wayland user (and neither a GNOME user), so I can be of little help in reproducing the issue myself...
Have you followed the troubleshooting session for GDM in the wiki?
This could also be a hint for your analysis:
| Quote: | | Code: | | Apr 09 12:00:09 gentoo systemd[1732]: Failed to start Application launched by gnome-session-binary |
|
You could try to launch gnome-session in debug, like
| Code: | | dbus-launch --exit-with-session gnome-session --builtin --session=gnome-classic --disable-acceleration-check --debug & |
|
Hi kikko,
Thanks for your reply. This is what I get as debug info:
| Code: | $ gnome-session-binary[2669]: DEBUG(+): Enabling debugging
gnome-session-binary[2669]: DEBUG(+): hardware acceleration check is disabled
gnome-session-binary[2669]: DEBUG(+): Could not make systemd aware of QT_IM_MODULE=ibus environment variable: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
gnome-session-binary[2669]: DEBUG(+): Could not make systemd aware of XMODIFIERS=@im=ibus environment variable: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
gnome-session-binary[2669]: DEBUG(+): Could not make systemd aware of XDG_MENU_PREFIX=gnome- environment variable: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
gnome-session-binary[2669]: DEBUG(+): Finding a graphical session for user 1000
gnome-session-binary[2669]: DEBUG(+): Considering session '1'
gnome-session-binary[2669]: DEBUG(+): Found session ID: 1
gnome-session-binary[2669]: DEBUG(+): Using systemd for session tracking
gnome-session-binary[2669]: GLib-GIO-DEBUG(+): _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
gnome-session-binary[2669]: DEBUG(+): GsmManager: setting client store 0x55ed74a18ad0
gnome-session-binary[2669]: DEBUG(+): Could not make systemd aware of SESSION_MANAGER=local/gentoo:@/tmp/.ICE-unix/2669,unix/gentoo:/tmp/.ICE-unix/2669 environment variable: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
gnome-session-binary[2669]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/gentoo:@/tmp/.ICE-unix/2669,unix/gentoo:/tmp/.ICE-unix/2669
gnome-session-binary[2669]: DEBUG(+): emitting SessionIsActive
gnome-session-binary[2669]: DEBUG(+): fill: *** Getting session 'gnome-classic'
gnome-session-binary[2669]: DEBUG(+): fill: *** Looking if /home/a/.config/gnome-session/sessions/gnome-classic.session is a valid session file
gnome-session-binary[2669]: DEBUG(+): Cannot use session '/home/a/.config/gnome-session/sessions/gnome-classic.session': non-existing or invalid file.
gnome-session-binary[2669]: DEBUG(+): fill: *** Looking if /etc/xdg/gnome-session/sessions/gnome-classic.session is a valid session file
gnome-session-binary[2669]: DEBUG(+): Cannot use session '/etc/xdg/gnome-session/sessions/gnome-classic.session': non-existing or invalid file.
gnome-session-binary[2669]: DEBUG(+): fill: *** Looking if /usr/share/gnome/gnome-session/sessions/gnome-classic.session is a valid session file
gnome-session-binary[2669]: DEBUG(+): Cannot use session '/usr/share/gnome/gnome-session/sessions/gnome-classic.session': non-existing or invalid file.
gnome-session-binary[2669]: DEBUG(+): fill: *** Looking if /usr/local/share/gnome-session/sessions/gnome-classic.session is a valid session file
gnome-session-binary[2669]: DEBUG(+): Cannot use session '/usr/local/share/gnome-session/sessions/gnome-classic.session': non-existing or invalid file.
gnome-session-binary[2669]: DEBUG(+): fill: *** Looking if /usr/share/gnome-session/sessions/gnome-classic.session is a valid session file
gnome-session-binary[2669]: DEBUG(+): Cannot use session '/usr/share/gnome-session/sessions/gnome-classic.session': non-existing or invalid file.
gnome-session-binary[2669]: DEBUG(+): fill: *** Looking if /usr/share/gdm/gnome-session/sessions/gnome-classic.session is a valid session file
gnome-session-binary[2669]: DEBUG(+): Cannot use session '/usr/share/gdm/gnome-session/sessions/gnome-classic.session': non-existing or invalid file.
gnome-session-binary[2669]: DEBUG(+): GsmManager: GSM starting to manage
gnome-session-binary[2669]: DEBUG(+): GsmManager: App startup summary
gnome-session-binary[2669]: DEBUG(+): GsmManager: Phase EARLY_INITIALIZATION
gnome-session-binary[2669]: DEBUG(+): GsmManager: Phase PRE_DISPLAY_SERVER
gnome-session-binary[2669]: DEBUG(+): GsmManager: Phase DISPLAY_SERVER
gnome-session-binary[2669]: DEBUG(+): GsmManager: Phase INITIALIZATION
gnome-session-binary[2669]: DEBUG(+): GsmManager: Phase WINDOW_MANAGER
gnome-session-binary[2669]: DEBUG(+): GsmManager: Phase PANEL
gnome-session-binary[2669]: DEBUG(+): GsmManager: Phase DESKTOP
gnome-session-binary[2669]: DEBUG(+): GsmManager: Phase APPLICATION
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase EARLY_INITIALIZATION
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase EARLY_INITIALIZATION
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase PRE_DISPLAY_SERVER
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase PRE_DISPLAY_SERVER
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase DISPLAY_SERVER
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase DISPLAY_SERVER
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase INITIALIZATION
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase INITIALIZATION
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase WINDOW_MANAGER
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase WINDOW_MANAGER
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase PANEL
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase PANEL
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase DESKTOP
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase DESKTOP
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase APPLICATION
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase APPLICATION
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase RUNNING
gnome-session-binary[2669]: DEBUG(+): gsm_xsmp_server_start
gnome-session-binary[2669]: DEBUG(+): GsmPresence: adding idle watch (1) for 300 secs
gnome-session-binary[2669]: DEBUG(+): Caught SIGINT/SIGTERM, shutting down normally.
gnome-session-binary[2669]: DEBUG(+): GsmManager: requesting logout
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase RUNNING
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase QUERY_END_SESSION
gnome-session-binary[2669]: DEBUG(+): gsm_xsmp_server_stop_accepting_new_clients
gnome-session-binary[2669]: DEBUG(+): GsmManager: sending query-end-session to clients (logout mode: forceful)
gnome-session-binary[2669]: DEBUG(+): GsmManager: Logout called
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase QUERY_END_SESSION
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase END_SESSION
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase END_SESSION
gnome-session-binary[2669]: DEBUG(+): GsmSessionSave: Clearing saved session
gnome-session-binary[2669]: DEBUG(+): GsmSessionSave: clearing currently saved session at /home/a/.config/gnome-session/saved-session
gnome-session-binary[2669]: DEBUG(+): GsmManager: starting phase EXIT
gnome-session-binary[2669]: DEBUG(+): Finding a graphical session for user 1000
gnome-session-binary[2669]: DEBUG(+): Considering session '1'
gnome-session-binary[2669]: DEBUG(+): GsmManager: reloading user bus failed: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
gnome-session-binary[2669]: DEBUG(+): GsmManager: ending phase EXIT
gnome-session-binary[2669]: DEBUG(+): GsmManager: disposing manager
gnome-session-binary[2669]: DEBUG(+): GsmStore: Clearing object store
gnome-session-binary[2669]: DEBUG(+): GsmStore: Clearing object store
gnome-session-binary[2669]: DEBUG(+): GsmStore: Clearing object store
^C
[1]+ Done dbus-launch --exit-with-session gnome-session --builtin --session=gnome-classic --disable-acceleration-check --debug
|
When this happens, I'm unable to reboot or poweroff. I have to press the power button to shutdown. |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21635
|
| Posted: Sat Apr 10, 2021 4:12 pm Post subject: |
|
|
| the_actuary wrote: | | When this happens, I'm unable to reboot or poweroff. I have to press the power button to shutdown. |
Do you mean you are using the long-press that forcibly stops the machine, or the brief tap that initiates an ACPI based graceful shutdown? If the machine is so broken that it cannot perform a graceful shutdown, that is a serious problem. If your issue is only that your GUI has gotten stuck and you need root privilege (which ACPI shutdowns have) to initiate a shutdown, that is a minor problem. |
|
| Back to top |
|
|
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Sat Apr 10, 2021 4:27 pm Post subject: |
|
|
| Hu wrote: | | the_actuary wrote: | | When this happens, I'm unable to reboot or poweroff. I have to press the power button to shutdown. |
Do you mean you are using the long-press that forcibly stops the machine, or the brief tap that initiates an ACPI based graceful shutdown? If the machine is so broken that it cannot perform a graceful shutdown, that is a serious problem. If your issue is only that your GUI has gotten stuck and you need root privilege (which ACPI shutdowns have) to initiate a shutdown, that is a minor problem. |
Hi Hu,
I'm 100% sure it's the gui - the problem occurs in gnome-wayland as well as weston-wayland but not in X. This is a new laptop & I installed arch linux last week to test out gentoo in a VM for the first time before installing it as my daily driver this week - and arch worked well with gnome-wayland (of course, it's a binary distro and I have no idea with what options they compiled the kernel/software with). I can still work with gnome-X without issues, which I'll continue to do till hopefully the solution is found. |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21635
|
| Posted: Sat Apr 10, 2021 6:04 pm Post subject: |
|
|
| If you would prefer to use GNOME-Wayland, and the problem is just in the GUI, then as a workaround you could use a root shell (or sudo) to initiate the reboot/shutdown. |
|
| Back to top |
|
|
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Sun Apr 11, 2021 3:05 am Post subject: |
|
|
| Hu wrote: | | If you would prefer to use GNOME-Wayland, and the problem is just in the GUI, then as a workaround you could use a root shell (or sudo) to initiate the reboot/shutdown. |
Hi Hu,
The issue is, when I launch the wayland session (gnome or weston), everything freezes & I'm unable move the cursor or even fall back into tty. |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21635
|
| Posted: Sun Apr 11, 2021 4:03 am Post subject: |
|
|
I see. I had forgotten that statement in the opening post, and was looking solely at the more recent posts, where it was unclear to me how severely the system had hung.
Is the system panicked at this point? Does it still respond over the network? Does a soft ACPI-off work, or are you required to long-press the power button? |
|
| Back to top |
|
|
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Sun Apr 11, 2021 5:02 am Post subject: |
|
|
| Hu wrote: | I see. I had forgotten that statement in the opening post, and was looking solely at the more recent posts, where it was unclear to me how severely the system had hung.
Is the system panicked at this point? Does it still respond over the network? Does a soft ACPI-off work, or are you required to long-press the power button? |
Hi Hu,
Journalctl log has a bunch of entries that seem to point to the kernel panicking when wayland is launched:
| Code: | -----
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127616
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127615
Apr 09 12:00:12 gentoo kernel: BUG: Bad page state in process kworker/u16:6 pfn:127614
----- |
If I soft ACPI it, the system either tries to power off but gets struck at shutdown or on reboot, all the gnome services crash :-
| Code: | Apr 11 07:22:33 gentoo systemd[461]: Failed to start Application launched by gnome-session-binary.
Apr 11 07:22:33 gentoo systemd[461]: Failed to start GNOME Shell on Wayland.
Apr 11 07:23:02 gentoo gnome-session-binary[555]: Unrecoverable failure in required component org.gnome.Shell.desktop
Apr 11 07:23:02 gentoo gnome-session-binary[555]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Wacom.desktop
Apr 11 07:23:08 gentoo gnome-session-binary[468]: Unrecoverable failure in required component org.gnome.Shell.desktop
Apr 11 07:23:21 gentoo systemd[461]: Failed to start Application launched by gnome-session-binary.
Apr 11 07:23:21 gentoo systemd[461]: Failed to start Application launched by gnome-session-binary.
Apr 11 07:24:52 gentoo systemd[461]: Failed to start GNOME accessibility service.
Apr 11 07:24:52 gentoo systemd[461]: Failed to start GNOME printer notifications service.
Apr 11 07:24:52 gentoo systemd[461]: Failed to start GNOME date & time service.
--------------------
Apr 11 08:28:13 gentoo systemd[461]: Failed to start GNOME sound sample caching service.
Apr 11 08:28:13 gentoo systemd[461]: Failed to start GNOME USB protection service.
Apr 11 08:28:43 gentoo systemd[1]: Code should not be reached 'Uh, main process died at wrong time.' at>
Apr 11 08:28:43 gentoo systemd-coredump[6361]: Process 6360 (systemd) of user 0 dumped core.
|
I noticed I had a couple of features on in the kernel framebuffer that were tagged as experimental. I'll remove those & recompile to see if it makes a diff. |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21635
|
| Posted: Sun Apr 11, 2021 3:42 pm Post subject: |
|
|
| What kernel version are you using? |
|
| Back to top |
|
|
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Sun Apr 11, 2021 3:55 pm Post subject: |
|
|
| Hu wrote: | | What kernel version are you using? |
5.10.27
Genkernel + added features described in the intel page of gentoo wiki. Unfortunately, disabling the two experimental features didn't help. |
|
| Back to top |
|
|
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Wed Apr 14, 2021 1:17 pm Post subject: |
|
|
The problem seems to be with something related to drm_atomic_helper_setup_commit. Anyone have any idea what this is?
| Code: |
Apr 14 18:43:45 gentoo kernel: kernel BUG at include/linux/mm.h:707!
Apr 14 18:43:45 gentoo kernel: [drm:drm_atomic_helper_setup_commit] *ERROR* [CRTC:33:crtc-0] cleanup_done timed out
Apr 14 18:42:02 gentoo kernel: kernel BUG at include/linux/mm.h:707!
.......................
Apr 14 18:39:18 gentoo kernel: [drm:drm_atomic_helper_setup_commit] *ERROR* [CRTC:33:crtc-0] cleanup_done timed out
Apr 14 18:39:13 gentoo kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Apr 14 18:39:08 gentoo kernel: kernel BUG at include/linux/mm.h:707!
Apr 14 18:39:08 gentoo kernel: [drm:drm_atomic_helper_setup_commit] *ERROR* [CRTC:33:crtc-0] cleanup_done timed out
Apr 14 18:38:58 gentoo kernel: kernel BUG at include/linux/mm.h:707!
Apr 14 18:38:57 gentoo kernel: kernel BUG at include/linux/mm.h:707!
Apr 14 18:38:52 gentoo kernel: BUG: Bad page state in process kworker/u16:5 pfn:19ccb6
....................
Apr 14 18:38:52 gentoo kernel: BUG: Bad page state in process kworker/u16:5 pfn:19ccab |
|
|
| Back to top |
|
|
the_actuary
n00b
Joined: 04 Apr 2021
Posts: 48
|
| Posted: Wed Apr 14, 2021 5:26 pm Post subject: |
|
|
Solved! It was indeed a kernel issue. It looks like support for intel iris xe was added only in kernel 5.11 & 5.10 lacked it.
I pulled in 5.11.13 & built the kernel now wayland now works like a charm! It now makes sense why wayland worked in Arch Linux kernel but not gentoo dist kernel - since Arch used the 5.11 kernel.
Thanks to everyone who contributed to solve this! |
|
| Back to top |
|
|
|
Desktop Environments
