GNOME doesn't launch when resolving snap cgroup error.

AimForNaN · 2024-06-27 21:22:51

Exporting DBUS_SESSION_BUS_ADDRESS in my .zprofile to try to solve the snap cgroup error causes GNOME to not launch when running XDG_SESSION_TYPE=wayland dbus-run-session gnome-session.

Is there no way to achieve compatibility between the two?

V1del · 2024-06-27 22:09:44

Yes stop running dbus-run-session nor exporting DBUS_SESSION_BUS_ADDRESS this way. All of this should be "default" without an explicit export nor a dbus-run-session

AimForNaN · 2024-06-27 23:26:10

V1del wrote:

Yes stop running dbus-run-session nor exporting DBUS_SESSION_BUS_ADDRESS this way. All of this should be "default" without an explicit export nor a dbus-run-session

Yes, but then I'm stuck having to set DBUS_SESSION_BUS_ADDRESS whenever I want to run a snap app.

DBUS_SESSION_BUS_ADDRESS="unix:path=$XDG_RUNTIME_DIR/bus" <snap-app> &

It gets very tedious very quickly having to do that each time I want to launch a snap app.

V1del · 2024-06-28 15:43:24

That should not be necessary. it should be properly set by default when you log in assuming you haven't manually overridden this with incompatible PAM/shell init files. In doubt post your .zprofile/.zshrc and maybe

printenv

before and after starting GNOME

AimForNaN · 2024-06-28 19:45:21

V1del wrote:

That should not be necessary. it should be properly set by default when you log in assuming you haven't manually overridden this with incompatible PAM/shell init files. In doubt post your .zprofile/.zshrc and maybe
printenv
before and after starting GNOME

In both Hyprland and KDE everything works. So, it's just GNOME. My guess is dbus-run-session is overriding the bus address. However, GNOME doesn't launch without dbus-run-session, so I'm kind of stuck here.

V1del · 2024-06-28 22:24:40

What "doesn't launch"? do you see error messages? If not directly in the terminal, does something land in the journal?

sudo journalctl -b

AimForNaN · 2024-06-28 22:47:38

V1del wrote:

What "doesn't launch"? do you see error messages? If not directly in the terminal, does something land in the journal?
sudo journalctl -b

Running XDG_SESSION_TYPE=wayland gnome-session doesn't launch GNOME. I'm just returned to the prompt without an error message. Even journalctl -b doesn't have anything relating to gnome-session. Without dbus-run-session, nothing happens.

seth · 2024-06-29 08:01:57

Certainly not if you're exporting DBUS_SESSION_BUS_ADDRESS - or are using ly.
However, https://wiki.archlinux.org/title/GNOME#Wayland_sessions which always read odd and is disputed because it's stupid, so let's see why that is:

1. how do you login
2. what's the output of "echo $DBUS_SESSION_BUS_ADDRESS" before running gnome?
3. gnome's probably posting errors to your journal, in doubt post your complete system journal for the boot after the failed gnome session start:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

It gets very tedious very quickly having to do that each time I want to launch a snap app.

"man alias"…

AimForNaN · 2024-06-29 09:59:22

seth wrote:

1. how do you login

Terminal prompt.

2. what's the output of "echo $DBUS_SESSION_BUS_ADDRESS" before running gnome?

Exactly the same as $XDG_RUNTIME_DIR/bus

3. gnome's probably posting errors to your journal, in doubt post your complete system journal for the boot after the failed gnome session start

https://0x0.st/Xm6M.txt

"man alias"…

Hoping for a solution, though.

seth · 2024-06-29 14:28:32

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

Jun 29 05:51:30 truefusion gnome-shell[1826]: Running GNOME Shell (using mutter 46.2) as a Wayland display server
Jun 29 05:51:30 truefusion gnome-shell[1826]: Failed to setup: Could not get session ID: Session '1' is not a graphical session (type: 'tty')
Jun 29 05:51:30 truefusion systemd[1620]: org.gnome.Shell@wayland.service: Failed with result 'protocol'.
Jun 29 05:51:30 truefusion systemd[1620]: Failed to start GNOME Shell on Wayland.

This doesn't look like XDG_SESSION_TYPE=wayland was properly exported, it's important to know how and when exactly you start gnome, how you login (ly, agetty, autologin) basically, how you end up with

Jun 29 05:51:17 truefusion systemd-logind[968]: New session 1 of user reeko5k.
Jun 29 05:51:17 truefusion systemd[1]: Created slice User Slice of UID 1000.
Jun 29 05:51:17 truefusion systemd[1]: Starting User Runtime Directory /run/user/1000...
Jun 29 05:51:17 truefusion systemd[1]: Finished User Runtime Directory /run/user/1000.
Jun 29 05:51:17 truefusion systemd[1]: Starting User Manager for UID 1000...
Jun 29 05:51:17 truefusion (systemd)[1620]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[reeko5k] ruser=[<unknown>] rhost=[<unknown>]
Jun 29 05:51:17 truefusion (systemd)[1620]: pam_unix(systemd-user:session): session opened for user reeko5k(uid=1000) by reeko5k(uid=0)
Jun 29 05:51:17 truefusion systemd-logind[968]: New session 2 of user reeko5k.

Starting two sessions in one second.

AimForNaN · 2024-06-30 02:47:32

seth wrote:

This doesn't look like XDG_SESSION_TYPE=wayland was properly exported

Does that mean I can leave that out when trying to launch gnome? Since the log shows that it tried to run a wayland session anyway.

it's important to know how and when exactly you start gnome, how you login (ly, agetty, autologin) basically, how you end up with

Jun 29 05:51:17 truefusion systemd-logind[968]: New session 1 of user reeko5k.
Jun 29 05:51:17 truefusion systemd[1]: Created slice User Slice of UID 1000.
Jun 29 05:51:17 truefusion systemd[1]: Starting User Runtime Directory /run/user/1000...
Jun 29 05:51:17 truefusion systemd[1]: Finished User Runtime Directory /run/user/1000.
Jun 29 05:51:17 truefusion systemd[1]: Starting User Manager for UID 1000...
Jun 29 05:51:17 truefusion (systemd)[1620]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[reeko5k] ruser=[<unknown>] rhost=[<unknown>]
Jun 29 05:51:17 truefusion (systemd)[1620]: pam_unix(systemd-user:session): session opened for user reeko5k(uid=1000) by reeko5k(uid=0)
Jun 29 05:51:17 truefusion systemd-logind[968]: New session 2 of user reeko5k.

Starting two sessions in one second.

I manually type in XDG_SESSION_TYPE=wayland gnome-session at the prompt after logging in. After executing, I am immediately returned to prompt. Looks exactly like this:

$ XDG_SESSION_TYPE=wayland gnome-session
$

I log in without any DM. After the system boots, I am presented with the typical login prompt. Whether or not it is ly, agetty, autologin, etc, I do not know. Whatever a base install of Arch gives you via archinstall, I would suspect that is it. I don't know how to be more specific than this. I'd record it if I could.

seth · 2024-06-30 06:59:45

systemctl --user list-unit-files

Also try to disable gkr-pam, you're running it right away, before starting gnome.

Arch Linux

#1 2024-06-27 21:22:51

GNOME doesn't launch when resolving snap cgroup error.

#2 2024-06-27 22:09:44

Re: GNOME doesn't launch when resolving snap cgroup error.

#3 2024-06-27 23:26:10

Re: GNOME doesn't launch when resolving snap cgroup error.

#4 2024-06-28 15:43:24

Re: GNOME doesn't launch when resolving snap cgroup error.

#5 2024-06-28 19:45:21

Re: GNOME doesn't launch when resolving snap cgroup error.

#6 2024-06-28 22:24:40

Re: GNOME doesn't launch when resolving snap cgroup error.

#7 2024-06-28 22:47:38

Re: GNOME doesn't launch when resolving snap cgroup error.

#8 2024-06-29 08:01:57

Re: GNOME doesn't launch when resolving snap cgroup error.

#9 2024-06-29 09:59:22

Re: GNOME doesn't launch when resolving snap cgroup error.

#10 2024-06-29 14:28:32

Re: GNOME doesn't launch when resolving snap cgroup error.

#11 2024-06-30 02:47:32

Re: GNOME doesn't launch when resolving snap cgroup error.

#12 2024-06-30 06:59:45

Re: GNOME doesn't launch when resolving snap cgroup error.

Board footer