You are not logged in.
Pages: 1
I made a fresh install of arch and still on the early process to set everything according to my wishes. My install is very basic with no fancy tricks.
At first glance everything is working fine, but looking at journalctl entries, I found this warning:
gnome-session-binary[948]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login.I start my gnome session from a login shell this way:
$ XDG_SESSION_TYPE=wayland dbus-run-session gnome-sessionWhat shall I check/do to fix this issue?
Last edited by gabx (2024-07-15 11:48:07)
Offline
Drop the dbus-run-session, it shouldn't be necessary and will create a disjoint DBUS in relation to your login session.
Offline
If I drop it, the session doesn't start. After I enter the command, I come back to the login prompt.
How can I debug this issue and know why the command does not launch the session?
Offline
Same as https://bbs.archlinux.org/viewtopic.php?id=297181
Gnome probably depends on GDM ![]()
Offline
Ah that slipped past me... I'd not be the least surprised if that was the case.
Offline
It looks like this is the correct way to go. The trick is I have been running arch for long now and on many occasions I was happy to to access command line to fix some issues from my desktop environment. Loging directly to gnome annoys me.
In your opinion, is there any potential serious damage to keep my current set up?
Last edited by gabx (2024-07-10 15:58:32)
Offline
https://man.archlinux.org/man/core/dbus … ssion.1.en will break integration w/ the logind provided session bus.
This isn't a good approach and it seriously should needs to be possible to start gnome regardless of any DM (so far I was just joking, though…)
Do you get the same errors as in https://bbs.archlinux.org/viewtopic.php … 4#p2180724 ?
It's not an ideal solution either, but you could try to set XDG_SESSION_TYPE in the getty service, https://wiki.archlinux.org/title/Getty#Virtual_console (ignore the autologin/start part - unless you want that ![]()
Does that
1. combat the error from the other thread?
2. allow you to start gnome w/o dbus-run-session ?
Last edited by seth (2024-07-10 19:07:13)
Offline
Here is part of journalctl
Jul 11 16:20:39 magnolia gnome-session-binary[19328]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
Jul 11 16:20:39 magnolia gnome-session[19328]: gnome-session-binary[19328]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
Jul 11 16:20:39 magnolia gnome-session[19328]: gnome-session-binary[19328]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Jul 11 16:20:39 magnolia gnome-session-binary[19328]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Jul 11 16:20:39 magnolia gnome-session-binary[19328]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Jul 11 16:20:39 magnolia gnome-session[19328]: gnome-session-binary[19328]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Jul 11 16:20:39 magnolia gnome-session-binary[19328]: WARNING: Could not check if unit gnome-session-wayland@gnome.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Jul 11 16:20:39 magnolia gnome-session[19328]: gnome-session-binary[19328]: WARNING: Could not check if unit gnome-session-wayland@gnome.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited w>
Jul 11 16:20:39 magnolia gnome-session-binary[19328]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Jul 11 16:20:39 magnolia gnome-session[19328]: gnome-session-binary[19328]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not existNow, when using a drop in file :
# systemctl edit getty@tty1.service --drop-in=wayland.conf
[Service]
XDG_SESSION_TYPE=waylanddoes not change at login prompt. Just running gnome-session will not start the session
Last edited by gabx (2024-07-11 15:00:55)
Offline
That looks like a session started w/ dbus-run-session?
YOu're looking for sth. like "is not a graphical session (type: 'tty')"
Offline
yes journalctl output is when running a dbus-session.
From journalctl with the drop in file, I found this entry:
/etc/systemd/system/getty@tty1.service.d/wayland.conf:2: Unknown key 'XDG_SESSION_TYPE' in section [Service], ignoring.So it looks like my drop in file has not been correctly written.
How shall I write your suggestion?
Offline
The wiki actually lists the correct line, "Environment=XDG_SESSION_TYPE=wayland" (yes, there're two "=")
Offline
I decided to use gdm, as all the apps are now working right of the box, when before they were broken.
I mark the topic as solved, even if it is not really solved as I don't have a clean way to start gnome-session from login prompt.
Offline
exporting the XDG_SESSION_TYPE in the getty didn't work? Or didn't help?
Offline
Pages: 1