[SOLVED] Start Gnome wayland session from tty.

AhmadRaniri · 2021-07-17 05:26:53

So, I'm into wayland stuffs right now, I'm trying some wayland compositors and most of it are able to be started from tty (sway, plasma wayland, dwl, etc) except gnome. Actually I can start gnome wayland from tty but it's just the gnome-shell and not the entire gnome desktop. I follow arch wiki to start gnome wayland session but it doesn't work on devuan.

I tried to run this command :

XDG_SESSION_TYPE=wayland dbus-run-session gnome-session

and it doesn't bring me to the desktop and I got complain about Display (seem I need to give Display option), arch linux works fine with that command. Did it has something related to systemd's stuffs? One more, I can't find gnome wayland options from lightdm (I am not a fans of DM btw). Thanks

Last edited by AhmadRaniri (2021-07-17 06:23:11)

AhmadRaniri · 2021-07-17 06:24:43

Sorry, I thought after install gnome-session, I can launch gnome wayland session via tty, turn out I can't. feel free to suggest. Thanks.

Head_on_a_Stick · 2021-07-17 11:34:43

AhmadRaniri wrote:

I got complain about Display (seem I need to give Display option)

Please post the exact, full error message.

AhmadRaniri wrote:

I thought after install gnome-session, I can launch gnome wayland session via tty, turn out I can't

Why not? What happens when you try? Please post any error messages in full.

I presume you're running gnome-session --wayland from a TTY login?

Which version of Devuan is this?

apt policy

AhmadRaniri · 2021-07-17 12:15:37

Which version of Devuan is this?

Devuan 4 Chimaera.

AhmadRaniri · 2021-07-17 12:25:19

Please post the exact, full error message.

Yep, I'll post it soon, my machine ran too long today (work's stuffs), it's currently off.

AhmadRaniri · 2021-07-17 23:47:36

First trial.

[ahmad@devuan ~]$ XDG_SESSION_TYPE=wayland dbus-run-session /usr/bin/gnome-session

** (process:2041): WARNING **: 06:33:23.761: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=GNOME environment variable: Could not connect: Connection refused
gnome-session-binary[2041]: WARNING: Failed to upload environment to DBus: Could not connect: Connection refused
gnome-session-binary[2041]: WARNING: Failed to upload environment to systemd: Could not connect: Connection refused
gnome-session-binary[2041]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Could not connect: Connection refused
gnome-session-binary[2041]: WARNING: Could not make bus activated clients aware of XDG_MENU_PREFIX=gnome- environment variable: Could not connect: Connection refused
gnome-session-binary[2041]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
Gnome-session-binary[2041]: WARNING: Lost name on bus: org.gnome.SessionManager
Unable to init server: Could not connect: Connection refused

** (gnome-session-failed:2064): WARNING **: 06:33:23.781: Cannot open display:

AhmadRaniri · 2021-07-17 23:49:31

Second trial.

[ahmad@devuan ~]$ gnome-session --session=wayland

** (process:2078): WARNING **: 06:38:32.204: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=GNOME environment variable: Could not connect: Connection refused
gnome-session-binary[2078]: WARNING: Failed to upload environment to DBus: Could not connect: Connection refused
gnome-session-binary[2078]: WARNING: Failed to upload environment to systemd: Could not connect: Connection refused
gnome-session-binary[2078]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Could not connect: Connection refused
gnome-session-binary[2078]: WARNING: Could not make bus activated clients aware of XDG_MENU_PREFIX=gnome- environment variable: Could not connect: Connection refused
gnome-session-binary[2078]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
Gnome-session-binary[2078]: WARNING: Lost name on bus: org.gnome.SessionManager
Unable to init server: Could not connect: Connection refused

** (gnome-session-failed:2085): WARNING **: 06:38:32.223: Cannot open display:
Terminated

AhmadRaniri · 2021-07-17 23:50:41

Third trial.

[ahmad@devuan ~]$ dbus-run-session /usr/bin/gnome-session --session=wayland
gnome-session-binary[2089]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does
not exist
gnome-session-binary[2089]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
Gnome-session-binary[2089]: CODE_FILE=../gnome-session/gsm-manager.c:CODE_LINE=1389:start_phase:Entering running state
Unable to init server: Could not connect: Connection refused

** (gnome-session-failed:2097): WARNING **: 06:40:05.866: Cannot open display:

Head_on_a_Stick · 2021-07-18 08:57:54

AhmadRaniri wrote:

[ahmad@devuan ~]gnome-session-binary[2078]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.

^ This.

Check

apt policy elogind
loginctl show-user

AhmadRaniri · 2021-07-18 09:51:46

For elogind.

[ahmad@devuan s2]$ apt policy elogind
elogind:
  Installed: 246.10-2
  Candidate: 246.10-2
  Version table:
 *** 246.10-2 500
        500 http://deb.devuan.org/merged testing/main amd64 Packages
        100 /var/lib/dpkg/status

For loginctl show-user

EnableWallMessages=no
KillUserProcesses=no
RebootToFirmwareSetup=no
RebootToBootLoaderMenu=18446744073709551615
IdleHint=yes
IdleSinceHint=1626599384450429
IdleSinceHintMonotonic=2793292978
BlockInhibited=handle-power-key:handle-suspend-key:handle-hibernate-key
DelayInhibited=sleep
InhibitDelayMaxUSec=5s
UserStopDelayUSec=0
HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
HandleLidSwitchDocked=ignore
HoldoffTimeoutUSec=30s
IdleAction=ignore
IdleActionUSec=30min
PreparingForShutdown=no
PreparingForSleep=no
Docked=no
LidClosed=no
OnExternalPower=yes
RemoveIPC=no
RuntimeDirectorySize=401960960
RuntimeDirectoryInodesMax=98135
InhibitorsMax=8192
NCurrentInhibitors=6
SessionsMax=8192
NCurrentSessions=1

Head_on_a_Stick · 2021-07-18 10:19:30

Hmm. How about https://bbs.archlinux.org/viewtopic.php … 2#p1684912? A bit of a stab in the dark but a possibility if you've installed GNOME on top of Xfce.

AhmadRaniri · 2021-07-18 12:30:01

Head_on_a_Stick wrote:

Hmm. How about https://bbs.archlinux.org/viewtopic.php … 2#p1684912? A bit of a stab in the dark but a possibility if you've installed GNOME on top of Xfce.

I don't think its related, I wonder if Debian suffers the same case.

Head_on_a_Stick · 2021-07-18 12:48:29

So is the policykit-1-gnome package installed?

AhmadRaniri · 2021-07-18 20:51:20

So is the policykit-1-gnome package installed?

I have it.

[ahmad@devuan ~]$ apt search policykit-1-gnome                                                                                                                     
Sorting... Done                                                                                                                                                    
Full Text Search... Done                                                                                                                                           
policykit-1-gnome/testing,now 0.105-7 amd64 [installed]                                                                                                            
  authentication agent for PolicyKit                                                                                                                               
                                                                                                                                                                   
[ahmad@devuan ~]$

AhmadRaniri · 2021-07-19 18:28:27

Well, Finally I can enter wayland session using another user I create. It's so strange that my primary user can't enter it. Guess I need to reset all my gnome setting and start from beginning or clean all setting.

AhmadRaniri · 2021-07-20 09:49:03

Reset gnome's settings (via gnome tweaks, dconf) seems still not works, even
perform renaming config folder (~/.config) still gives same error.

AhmadRaniri · 2021-07-20 19:39:54

I end up rename my old directory to something else, then create new home directory, now I can launch gnome wayland session. I feel happy.

The officially official Devuan Forum!

#1 2021-07-17 05:26:53

[SOLVED] Start Gnome wayland session from tty.

#2 2021-07-17 06:24:43

Re: [SOLVED] Start Gnome wayland session from tty.

#3 2021-07-17 11:34:43

Re: [SOLVED] Start Gnome wayland session from tty.

#4 2021-07-17 12:15:37

Re: [SOLVED] Start Gnome wayland session from tty.

#5 2021-07-17 12:25:19

Re: [SOLVED] Start Gnome wayland session from tty.

#6 2021-07-17 23:47:36

Re: [SOLVED] Start Gnome wayland session from tty.

#7 2021-07-17 23:49:31

Re: [SOLVED] Start Gnome wayland session from tty.

#8 2021-07-17 23:50:41

Re: [SOLVED] Start Gnome wayland session from tty.

#9 2021-07-18 08:57:54

Re: [SOLVED] Start Gnome wayland session from tty.

#10 2021-07-18 09:51:46

Re: [SOLVED] Start Gnome wayland session from tty.

#11 2021-07-18 10:19:30

Re: [SOLVED] Start Gnome wayland session from tty.

#12 2021-07-18 12:30:01

Re: [SOLVED] Start Gnome wayland session from tty.

#13 2021-07-18 12:48:29

Re: [SOLVED] Start Gnome wayland session from tty.

#14 2021-07-18 20:51:20

Re: [SOLVED] Start Gnome wayland session from tty.

#15 2021-07-19 18:28:27

Re: [SOLVED] Start Gnome wayland session from tty.

#16 2021-07-20 09:49:03

Re: [SOLVED] Start Gnome wayland session from tty.

#17 2021-07-20 19:39:54

Re: [SOLVED] Start Gnome wayland session from tty.

Board footer