You are not logged in.
Hi all,
As referenced in the ArchWiki here, https://wiki.archlinux.org/index.php/GN … d_sessions, GNOME 3.24 Wayland can be started up by typing the following from the command line:
XDG_SESSION_TYPE=wayland dbus-run-session gnome-session
In my case, GNOME *does* run, but it throws the following error _repeatedly_ first:
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
(The ArchWiki also mentions some stuff about .bash_profile, but this doesn't help me.)
Any ideas?
Thanks,
Loady
Offline
Sounds like this issue https://bugzilla.gnome.org/show_bug.cgi?id=780801. They also mention a potential work around of appending
&& [[ -z $XDG_SESSION_TYPE ]]
I don't have GNOME setup at the moment to confirm.
Offline
No, sadly that isn't it/doesn't work:(
Last edited by loadlover (2017-06-02 00:27:28)
Offline
systemctl --user status dbus.service
echo $DBUS_SESSION_BUS_ADDRESS
?
Offline
systemctl --user status dbus.service echo $DBUS_SESSION_BUS_ADDRESS
?
Hi Seth,
Yes, I've seen that. That is exactly this problem. A bunch of people are experiencing this. Damn and bloody blast it! No solution yet...
Loady
Offline
And what is the output of the mentioned commands on your side ...?
Offline
Hi Seth,
Here's what I get:
# systemctl --user status dbus.service
dbus.service - D-Bus User Message Bus
Loaded: loaded (/usr/lib/systemd/user/dbus.service; static; vendor preset: enabled)
Drop-In: /usr/lib/systemd/user/dbus.service.d
-flatpak.conf
Active: inactive (dead)
Docs: man:dbus-daemon(1)
# echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/0/bus
Oh, btw I had to do this manually by photographing the screen! Which log can I get this from (i.e. the log of tty1 just after logging in)?
Last edited by loadlover (2017-06-04 19:39:31)
Offline
You can upload the output of commands using a pastebin service...
Offline
unix:path=/run/user/0/bus
Do you login as root??
Offline
unix:path=/run/user/0/bus
Do you login as root??
Yes...
Offline
I'm afraid to ask why, but what happens is you don't? Can you start gnome w/o errors?
Offline
I'm afraid to ask why, but what happens is you don't? Can you start gnome w/o errors?
Exactly the same thing happens if I'm logged in as a user. Exactly the same errors.
The response to # systemctl --user status dbus.service is identical.
The response to # echo $DBUS_SESSION_BUS_ADDRESS is:
unix:path=/run/user/100/bus
Offline
There is a way around this - i.e. to run GNOME Wayland without the errors, but it may introduce problems of its own.
Open up /usr/share/applications/org.gnome.Shell.desktop in a text editor, and scroll down to the line:
Exec=/usr/bin/gnome-shell
And change it to:
Exec=/usr/bin/gnome-shell --wayland
One can now start GNOME Wayland by simply typing:
gnome-session
I do not understand why this works, but it does. However, typing /usr/bin/gnome-shell --wayland directly into the terminal throws an error. Can someone explain why?
Last edited by loadlover (2017-06-03 20:43:48)
Offline
You can upload the output of commands using a pastebin service...
Hiya Slithery,
If I use something like:
command | curl -F c=@- https://ptpb.pw/
How can I make this really easy? Can I use an alias or a symlink or.. something I've defined in .bash_profile?
Thanks for your help,
Loady
Last edited by loadlover (2017-06-04 18:50:22)
Offline
Try
pastebin() {
"$@" | curl -F c=@- https://ptpb.pw/
}
pastebin foo bar
Offline
Wow Seth, thanks. Hey, pastebinning is fun;)
Last edited by loadlover (2017-06-04 21:57:27)
Offline
Hello
It is a long time since the question has been posted but I succeed to launch Gnome by replacing
if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty5 ]] && [[ -z $XDG_SESSION_TYPE ]]; then
XDG_SESSION_TYPE=wayland exec dbus-run-session gnome-session
fi
by
if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty5 ]] && [[ -z $XDG_SESSION_TYPE ]]; then
XDG_SESSION_TYPE=exec dbus-run-session -- gnome-shell --display-server –wayland
fi
It was on tty5/
Hope that it can help somebody
jmcornil
Offline
There is a way around this - i.e. to run GNOME Wayland without the errors, but it may introduce problems of its own.
Open up /usr/share/applications/org.gnome.Shell.desktop in a text editor, and scroll down to the line:
Exec=/usr/bin/gnome-shell
And change it to:
Exec=/usr/bin/gnome-shell --wayland
One can now start GNOME Wayland by simply typing:
gnome-session
I do not understand why this works, but it does. However, typing /usr/bin/gnome-shell --wayland directly into the terminal throws an error. Can someone explain why?
Sorry I cannot answer your question. But appending --wayland as you suggested took care of another error that I was receiving. The one that said
"Unrecoverable failure in required component org.gnome.Shell.desktop"
I've been working to get rid of that error for weeks!! Thanks for the pointer.
Offline