search

Thinstation / thinstation

A framework for making thin and light Linux based images for x86 based machines and thinclients.
https://www.thinstation.net/
775 stars 188 forks source link

Running XDM as a session #817

Closed AlexanderZhirov closed 2 months ago

AlexanderZhirov commented 3 months ago

Is it possible to run XDM as SESSION_0_TYPE?

I have built the xorg-xdm package. It is possible to start the xdm with hands from under the tiny configure. Is it possible to automate, instead of sh, specify the launch of xdm? Judging by the configurations of the icewm and openbox packages, it is necessary to create cmd files to run. How true and correct is it to set up such a mechanism for xdm?

.
├── bin
│   ├── xdm
│   └── xdmshell
├── build
│   ├── install
│   ├── installed
│   └── remove
├── dependencies
├── etc
│   ├── pam.d
│   │   └── xdm
│   ├── rc.d
│   │   └── xdm
│   └── X11
│       └── xdm
│           ├── TakeConsole -> /lib/X11/xdm/TakeConsole
│           ├── Xaccess
│           ├── xdm-config
│           ├── Xresources
│           ├── Xservers
│           └── Xsession -> /lib/X11/xdm/Xsession
└── lib
    ├── systemd
    │   └── system
    │       └── xdm.service
    └── X11
        ├── app-defaults
        │   └── Chooser
        └── xdm
            ├── chooser
            ├── GiveConsole
            ├── libXdmGreet.so
            ├── pixmaps
            │   ├── xorg-bw.xpm
            │   └── xorg.xpm
            ├── TakeConsole
            ├── Xreset
            ├── Xsession
            ├── Xsetup_0
            ├── Xstartup
            └── Xwilling
Doncuppjr commented 3 months ago

Yes, you will need to make a .wm file in etc/cmd as well as .functions file in /etc The .wm file will let the thinstation.packages know that it is running a wm and to try and load the .functions file to handle some special things that only a wm would do.Then just set the new wm as the Session 0 package. On Thursday, April 4, 2024 at 04:50:38 AM MDT, Alexander Zhirov @.***> wrote:

Is it possible to run XDM as SESSION_0_TYPE?

I have built the xorg-xdm package. It is possible to start the assembly with hands from under the tiny'. Is it possible to automate, instead of sh, specify the launch of xdm'? Judging by the configurations of the icewm and openbox packages, it is necessary to create cmd files to run. How true and correct is it to set up such a mechanism for xdm? . ├── bin │   ├── xdm │   └── xdmshell ├── build │   ├── install │   ├── installed │   └── remove ├── dependencies ├── etc │   ├── pam.d │   │   └── xdm │   ├── rc.d │   │   └── xdm │   └── X11 │   └── xdm │   ├── TakeConsole -> /lib/X11/xdm/TakeConsole │   ├── Xaccess │   ├── xdm-config │   ├── Xresources │   ├── Xservers │   └── Xsession -> /lib/X11/xdm/Xsession └── lib ├── systemd │   └── system │   └── xdm.service └── X11 ├── app-defaults │   └── Chooser └── xdm ├── chooser ├── GiveConsole ├── libXdmGreet.so ├── pixmaps │   ├── xorg-bw.xpm │   └── xorg.xpm ├── TakeConsole ├── Xreset ├── Xsession ├── Xsetup_0 ├── Xstartup └── Xwilling

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

AlexanderZhirov commented 3 months ago

After downloading, it cannot launch xdm, although it tries. The black screen starts and immediately crashes. Here is the result from the logs.

изображение изображение

journalctl

апр 04 16:46:56 ts_0800274a3104 audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D6600747375736572
апр 04 16:46:56 ts_0800274a3104 kernel: audit: type=1101 audit(1712238416.425:783): pid=51264 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_succeed_if acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:46:56 ts_0800274a3104 kernel: audit: type=1006 audit(1712238416.428:784): pid=51264 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967295 ses=75 res=1
апр 04 16:46:56 ts_0800274a3104 kernel: audit: type=1300 audit(1712238416.428:784): arch=c000003e syscall=1 success=yes exit=4 a0=4 a1=7ffd867bf820 a2=4 a3=7f36cdace558 items=0 ppid=1 pid=51264 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=75 comm="login" exe="/bin/busybox" key=(null)
апр 04 16:46:56 ts_0800274a3104 kernel: audit: type=1327 audit(1712238416.428:784): proctitle=2F62696E2F6C6F67696E002D6600747375736572
апр 04 16:46:56 ts_0800274a3104 systemd-logind[2235]: New session 75 of user tsuser.
апр 04 16:46:56 ts_0800274a3104 systemd[1]: Started Session 75 of user tsuser.
апр 04 16:46:56 ts_0800274a3104 audit[51264]: USER_START pid=51264 uid=0 auid=1000 ses=75 msg='op=PAM:session_open grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:46:56 ts_0800274a3104 audit[51264]: CRED_ACQ pid=51264 uid=0 auid=1000 ses=75 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:46:57 ts_0800274a3104 pulseaudio[51628]: Daemon already running.
апр 04 16:46:58 ts_0800274a3104 systemd[1]: session-74.scope: Succeeded.
апр 04 16:46:58 ts_0800274a3104 systemd[1]: session-74.scope: Consumed 1.033s CPU time.
апр 04 16:46:58 ts_0800274a3104 systemd-logind[2235]: Removed session 74.
апр 04 16:46:59 ts_0800274a3104 audit[51264]: CRED_DISP pid=51264 uid=0 auid=1000 ses=75 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:46:59 ts_0800274a3104 audit[51264]: USER_END pid=51264 uid=0 auid=1000 ses=75 msg='op=PAM:session_close grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:46:59 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:46:59 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:46:59 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:46:59 ts_0800274a3104 systemd[1]: display-manager.service: Succeeded.
апр 04 16:46:59 ts_0800274a3104 systemd-logind[2235]: Session 75 logged out. Waiting for processes to exit.
апр 04 16:46:59 ts_0800274a3104 systemd[1]: display-manager.service: Scheduled restart job, restart counter is at 74.
апр 04 16:46:59 ts_0800274a3104 systemd[1]: Stopped ThinStation Display Manager.
апр 04 16:46:59 ts_0800274a3104 systemd[1]: Started ThinStation Display Manager.
апр 04 16:46:59 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:46:59 ts_0800274a3104 audit[51918]: USER_ACCT pid=51918 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_succeed_if acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:46:59 ts_0800274a3104 audit[51918]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=4 a1=7fffb7210e80 a2=4 a3=7f8ccc709558 items=0 ppid=1 pid=51918 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=76 comm="login" exe="/bin/busybox" key=(null)
апр 04 16:46:59 ts_0800274a3104 audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D6600747375736572
апр 04 16:46:59 ts_0800274a3104 systemd[1]: Started Session 76 of user tsuser.
апр 04 16:46:59 ts_0800274a3104 systemd-logind[2235]: New session 76 of user tsuser.
апр 04 16:46:59 ts_0800274a3104 audit[51918]: USER_START pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:session_open grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:46:59 ts_0800274a3104 audit[51918]: CRED_ACQ pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:46:59 ts_0800274a3104 pulseaudio[52282]: Daemon already running.
апр 04 16:47:01 ts_0800274a3104 audit[51918]: CRED_DISP pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:01 ts_0800274a3104 kernel: kauditd_printk_skb: 14 callbacks suppressed
апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1104 audit(1712238421.324:797): pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:01 ts_0800274a3104 systemd[1]: session-75.scope: Succeeded.
апр 04 16:47:01 ts_0800274a3104 systemd[1]: session-75.scope: Consumed 1.640s CPU time.
апр 04 16:47:01 ts_0800274a3104 systemd-logind[2235]: Removed session 75.
апр 04 16:47:01 ts_0800274a3104 audit[51918]: USER_END pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:session_close grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1106 audit(1712238421.478:798): pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:session_close grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:01 ts_0800274a3104 systemd[1]: display-manager.service: Succeeded.
апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1131 audit(1712238421.479:799): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:01 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:01 ts_0800274a3104 systemd[1]: display-manager.service: Scheduled restart job, restart counter is at 75.
апр 04 16:47:01 ts_0800274a3104 systemd-logind[2235]: Session 76 logged out. Waiting for processes to exit.
апр 04 16:47:01 ts_0800274a3104 systemd[1]: Stopped ThinStation Display Manager.
апр 04 16:47:01 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:01 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1130 audit(1712238421.481:800): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1131 audit(1712238421.481:801): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:01 ts_0800274a3104 systemd[1]: Started ThinStation Display Manager.
апр 04 16:47:01 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1130 audit(1712238421.490:802): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:01 ts_0800274a3104 audit[52571]: USER_ACCT pid=52571 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_succeed_if acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1101 audit(1712238421.498:803): pid=52571 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_succeed_if acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:01 ts_0800274a3104 audit[52571]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=4 a1=7ffe5ea396a0 a2=4 a3=7f8321076558 items=0 ppid=1 pid=52571 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=77 comm="login" exe="/bin/busybox" key=(null)
апр 04 16:47:01 ts_0800274a3104 audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D6600747375736572
апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1006 audit(1712238421.500:804): pid=52571 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967295 ses=77 res=1
апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1300 audit(1712238421.500:804): arch=c000003e syscall=1 success=yes exit=4 a0=4 a1=7ffe5ea396a0 a2=4 a3=7f8321076558 items=0 ppid=1 pid=52571 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=77 comm="login" exe="/bin/busybox" key=(null)
апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1327 audit(1712238421.500:804): proctitle=2F62696E2F6C6F67696E002D6600747375736572
апр 04 16:47:01 ts_0800274a3104 systemd-logind[2235]: New session 77 of user tsuser.
апр 04 16:47:01 ts_0800274a3104 systemd[1]: Started Session 77 of user tsuser.
апр 04 16:47:01 ts_0800274a3104 audit[52571]: USER_START pid=52571 uid=0 auid=1000 ses=77 msg='op=PAM:session_open grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:01 ts_0800274a3104 audit[52571]: CRED_ACQ pid=52571 uid=0 auid=1000 ses=77 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:02 ts_0800274a3104 pulseaudio[52935]: Daemon already running.
апр 04 16:47:03 ts_0800274a3104 systemd[1]: session-76.scope: Succeeded.
апр 04 16:47:03 ts_0800274a3104 systemd-logind[2235]: Removed session 76.
апр 04 16:47:04 ts_0800274a3104 audit[52571]: CRED_DISP pid=52571 uid=0 auid=1000 ses=77 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:04 ts_0800274a3104 audit[52571]: USER_END pid=52571 uid=0 auid=1000 ses=77 msg='op=PAM:session_close grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:04 ts_0800274a3104 systemd[1]: display-manager.service: Succeeded.
апр 04 16:47:04 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:04 ts_0800274a3104 systemd-logind[2235]: Session 77 logged out. Waiting for processes to exit.
апр 04 16:47:04 ts_0800274a3104 systemd[1]: display-manager.service: Scheduled restart job, restart counter is at 76.
апр 04 16:47:04 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:04 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:04 ts_0800274a3104 systemd[1]: Stopped ThinStation Display Manager.
апр 04 16:47:04 ts_0800274a3104 systemd[1]: Started ThinStation Display Manager.
апр 04 16:47:04 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
апр 04 16:47:04 ts_0800274a3104 audit[53224]: USER_ACCT pid=53224 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_succeed_if acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:04 ts_0800274a3104 audit[53224]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=4 a1=7fff1d93f220 a2=4 a3=7f351d538558 items=0 ppid=1 pid=53224 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=78 comm="login" exe="/bin/busybox" key=(null)
апр 04 16:47:04 ts_0800274a3104 audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D6600747375736572
апр 04 16:47:04 ts_0800274a3104 systemd-logind[2235]: New session 78 of user tsuser.
апр 04 16:47:04 ts_0800274a3104 systemd[1]: Started Session 78 of user tsuser.
апр 04 16:47:04 ts_0800274a3104 audit[53224]: USER_START pid=53224 uid=0 auid=1000 ses=78 msg='op=PAM:session_open grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:04 ts_0800274a3104 audit[53224]: CRED_ACQ pid=53224 uid=0 auid=1000 ses=78 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success'
апр 04 16:47:05 ts_0800274a3104 pulseaudio[53588]: Daemon already running.
апр 04 16:47:06 ts_0800274a3104 systemd[1]: session-77.scope: Succeeded.
апр 04 16:47:06 ts_0800274a3104 systemd[1]: session-77.scope: Consumed 1.680s CPU time.
апр 04 16:47:06 ts_0800274a3104 systemd-logind[2235]: Removed session 77.

messages

Apr  4 16:59:16 thinstation-linux syslog.info syslogd started: BusyBox v1.34.1
Apr  4 16:59:16 thinstation-linux cron.info crond[2506]: crond (busybox 1.34.1) started, log level 8
Apr  4 16:59:17 thinstation-linux authpriv.info login[3486]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser"
Apr  4 16:59:18 thinstation-linux authpriv.info login[3486]: pam_unix(login:session): session opened for user tsuser by (uid=0)
Apr  4 16:59:18 thinstation-linux user.warn gnome-keyring-daemon: Libgcrypt warning: custom allocation handler - FIPS mode inactivated
Apr  4 16:59:18 thinstation-linux authpriv.info login[3486]: gkr-pam: gnome-keyring-daemon started properly
Apr  4 16:59:19 thinstation-linux daemon.info dbus-daemon[3852]: [session uid=1000 pid=3850] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=1000 pid=4034 comm="dconf write /system/p
roxy/mode 'none' ")
Apr  4 16:59:19 thinstation-linux daemon.info dbus-daemon[3852]: [session uid=1000 pid=3850] Successfully activated service 'ca.desrt.dconf'
Apr  4 16:59:20 thinstation-linux authpriv.info login[3486]: pam_unix(login:session): session closed for user tsuser
Apr  4 16:59:20 thinstation-linux authpriv.info login[4150]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser"
Apr  4 16:59:20 thinstation-linux authpriv.info login[4150]: pam_unix(login:session): session opened for user tsuser by LOGIN(uid=0)
Apr  4 16:59:20 thinstation-linux authpriv.err login[4150]: gkr-pam: couldn't unlock the login keyring.
Apr  4 16:59:21 thinstation-linux daemon.info dbus-daemon[4508]: [session uid=1000 pid=4506] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=4688 comm="dconf write /system/p
roxy/mode 'none' ")
Apr  4 16:59:21 thinstation-linux daemon.info dbus-daemon[4508]: [session uid=1000 pid=4506] Successfully activated service 'ca.desrt.dconf'
Apr  4 16:59:22 thinstation-linux authpriv.info login[4150]: pam_unix(login:session): session closed for user tsuser
Apr  4 16:59:22 thinstation-linux authpriv.info login[4803]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser"
Apr  4 16:59:22 thinstation-linux authpriv.info login[4803]: pam_unix(login:session): session opened for user tsuser by LOGIN(uid=0)
Apr  4 16:59:23 thinstation-linux authpriv.err login[4803]: gkr-pam: couldn't unlock the login keyring.
Apr  4 16:59:24 thinstation-linux daemon.info dbus-daemon[5161]: [session uid=1000 pid=5159] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=5341 comm="dconf write /system/p
roxy/mode 'none' ")
Apr  4 16:59:24 thinstation-linux daemon.info dbus-daemon[5161]: [session uid=1000 pid=5159] Successfully activated service 'ca.desrt.dconf'
Apr  4 16:59:25 thinstation-linux authpriv.info login[4803]: pam_unix(login:session): session closed for user tsuser
Apr  4 16:59:25 thinstation-linux authpriv.info login[5456]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser"
Apr  4 16:59:25 thinstation-linux authpriv.info login[5456]: pam_unix(login:session): session opened for user tsuser by LOGIN(uid=0)
Apr  4 16:59:26 thinstation-linux authpriv.err login[5456]: gkr-pam: couldn't unlock the login keyring.
Apr  4 16:59:27 thinstation-linux daemon.info dbus-daemon[5814]: [session uid=1000 pid=5812] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=5994 comm="dconf write /system/p
roxy/mode 'none' ")
Apr  4 16:59:27 thinstation-linux daemon.info dbus-daemon[5814]: [session uid=1000 pid=5812] Successfully activated service 'ca.desrt.dconf'
Apr  4 16:59:28 thinstation-linux authpriv.info login[5456]: pam_unix(login:session): session closed for user tsuser
Apr  4 16:59:28 thinstation-linux authpriv.info login[6109]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser"
Apr  4 16:59:28 thinstation-linux authpriv.info login[6109]: pam_unix(login:session): session opened for user tsuser by LOGIN(uid=0)
Apr  4 16:59:28 thinstation-linux authpriv.err login[6109]: gkr-pam: couldn't unlock the login keyring.
Apr  4 16:59:29 thinstation-linux daemon.info dbus-daemon[6467]: [session uid=1000 pid=6465] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=6647 comm="dconf write /system/p
roxy/mode 'none' ")
Apr  4 16:59:29 thinstation-linux daemon.info dbus-daemon[6467]: [session uid=1000 pid=6465] Successfully activated service 'ca.desrt.dconf'
Apr  4 16:59:31 thinstation-linux authpriv.info login[6109]: pam_unix(login:session): session closed for user tsuser
Apr  4 16:59:32 thinstation-linux authpriv.info login[6762]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser"
Apr  4 16:59:32 thinstation-linux authpriv.info login[6762]: pam_unix(login:session): session opened for user tsuser by LOGIN(uid=0)
Apr  4 16:59:32 thinstation-linux authpriv.err login[6762]: gkr-pam: couldn't unlock the login keyring.
Apr  4 16:59:32 thinstation-linux daemon.info dbus-daemon[7120]: [session uid=1000 pid=7118] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=7300 comm="dconf write /system/p
roxy/mode 'none' ")
Doncuppjr commented 3 months ago

What happens if you start it manually? On Thursday, April 4, 2024 at 08:02:32 AM MDT, Alexander Zhirov @.***> wrote:

After downloading, it cannot launch xdm, although it tries. The black screen starts and immediately crashes. Here is the result from the logs.

default.png (view on web) default.png (view on web)

journalctl апр 04 16:46:56 ts_0800274a3104 audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D6600747375736572 апр 04 16:46:56 ts_0800274a3104 kernel: audit: type=1101 audit(1712238416.425:783): pid=51264 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_succeed_if acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:46:56 ts_0800274a3104 kernel: audit: type=1006 audit(1712238416.428:784): pid=51264 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967295 ses=75 res=1 апр 04 16:46:56 ts_0800274a3104 kernel: audit: type=1300 audit(1712238416.428:784): arch=c000003e syscall=1 success=yes exit=4 a0=4 a1=7ffd867bf820 a2=4 a3=7f36cdace558 items=0 ppid=1 pid=51264 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=75 comm="login" exe="/bin/busybox" key=(null) апр 04 16:46:56 ts_0800274a3104 kernel: audit: type=1327 audit(1712238416.428:784): proctitle=2F62696E2F6C6F67696E002D6600747375736572 апр 04 16:46:56 ts_0800274a3104 systemd-logind[2235]: New session 75 of user tsuser. апр 04 16:46:56 ts_0800274a3104 systemd[1]: Started Session 75 of user tsuser. апр 04 16:46:56 ts_0800274a3104 audit[51264]: USER_START pid=51264 uid=0 auid=1000 ses=75 msg='op=PAM:session_open grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:46:56 ts_0800274a3104 audit[51264]: CRED_ACQ pid=51264 uid=0 auid=1000 ses=75 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:46:57 ts_0800274a3104 pulseaudio[51628]: Daemon already running. апр 04 16:46:58 ts_0800274a3104 systemd[1]: session-74.scope: Succeeded. апр 04 16:46:58 ts_0800274a3104 systemd[1]: session-74.scope: Consumed 1.033s CPU time. апр 04 16:46:58 ts_0800274a3104 systemd-logind[2235]: Removed session 74. апр 04 16:46:59 ts_0800274a3104 audit[51264]: CRED_DISP pid=51264 uid=0 auid=1000 ses=75 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:46:59 ts_0800274a3104 audit[51264]: USER_END pid=51264 uid=0 auid=1000 ses=75 msg='op=PAM:session_close grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:46:59 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:46:59 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:46:59 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:46:59 ts_0800274a3104 systemd[1]: display-manager.service: Succeeded. апр 04 16:46:59 ts_0800274a3104 systemd-logind[2235]: Session 75 logged out. Waiting for processes to exit. апр 04 16:46:59 ts_0800274a3104 systemd[1]: display-manager.service: Scheduled restart job, restart counter is at 74. апр 04 16:46:59 ts_0800274a3104 systemd[1]: Stopped ThinStation Display Manager. апр 04 16:46:59 ts_0800274a3104 systemd[1]: Started ThinStation Display Manager. апр 04 16:46:59 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:46:59 ts_0800274a3104 audit[51918]: USER_ACCT pid=51918 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_succeed_if acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:46:59 ts_0800274a3104 audit[51918]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=4 a1=7fffb7210e80 a2=4 a3=7f8ccc709558 items=0 ppid=1 pid=51918 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=76 comm="login" exe="/bin/busybox" key=(null) апр 04 16:46:59 ts_0800274a3104 audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D6600747375736572 апр 04 16:46:59 ts_0800274a3104 systemd[1]: Started Session 76 of user tsuser. апр 04 16:46:59 ts_0800274a3104 systemd-logind[2235]: New session 76 of user tsuser. апр 04 16:46:59 ts_0800274a3104 audit[51918]: USER_START pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:session_open grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:46:59 ts_0800274a3104 audit[51918]: CRED_ACQ pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:46:59 ts_0800274a3104 pulseaudio[52282]: Daemon already running. апр 04 16:47:01 ts_0800274a3104 audit[51918]: CRED_DISP pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:01 ts_0800274a3104 kernel: kauditd_printk_skb: 14 callbacks suppressed апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1104 audit(1712238421.324:797): pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:01 ts_0800274a3104 systemd[1]: session-75.scope: Succeeded. апр 04 16:47:01 ts_0800274a3104 systemd[1]: session-75.scope: Consumed 1.640s CPU time. апр 04 16:47:01 ts_0800274a3104 systemd-logind[2235]: Removed session 75. апр 04 16:47:01 ts_0800274a3104 audit[51918]: USER_END pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:session_close grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1106 audit(1712238421.478:798): pid=51918 uid=0 auid=1000 ses=76 msg='op=PAM:session_close grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:01 ts_0800274a3104 systemd[1]: display-manager.service: Succeeded. апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1131 audit(1712238421.479:799): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:01 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:01 ts_0800274a3104 systemd[1]: display-manager.service: Scheduled restart job, restart counter is at 75. апр 04 16:47:01 ts_0800274a3104 systemd-logind[2235]: Session 76 logged out. Waiting for processes to exit. апр 04 16:47:01 ts_0800274a3104 systemd[1]: Stopped ThinStation Display Manager. апр 04 16:47:01 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:01 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1130 audit(1712238421.481:800): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1131 audit(1712238421.481:801): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:01 ts_0800274a3104 systemd[1]: Started ThinStation Display Manager. апр 04 16:47:01 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1130 audit(1712238421.490:802): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:01 ts_0800274a3104 audit[52571]: USER_ACCT pid=52571 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_succeed_if acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1101 audit(1712238421.498:803): pid=52571 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_succeed_if acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:01 ts_0800274a3104 audit[52571]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=4 a1=7ffe5ea396a0 a2=4 a3=7f8321076558 items=0 ppid=1 pid=52571 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=77 comm="login" exe="/bin/busybox" key=(null) апр 04 16:47:01 ts_0800274a3104 audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D6600747375736572 апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1006 audit(1712238421.500:804): pid=52571 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967295 ses=77 res=1 апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1300 audit(1712238421.500:804): arch=c000003e syscall=1 success=yes exit=4 a0=4 a1=7ffe5ea396a0 a2=4 a3=7f8321076558 items=0 ppid=1 pid=52571 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=77 comm="login" exe="/bin/busybox" key=(null) апр 04 16:47:01 ts_0800274a3104 kernel: audit: type=1327 audit(1712238421.500:804): proctitle=2F62696E2F6C6F67696E002D6600747375736572 апр 04 16:47:01 ts_0800274a3104 systemd-logind[2235]: New session 77 of user tsuser. апр 04 16:47:01 ts_0800274a3104 systemd[1]: Started Session 77 of user tsuser. апр 04 16:47:01 ts_0800274a3104 audit[52571]: USER_START pid=52571 uid=0 auid=1000 ses=77 msg='op=PAM:session_open grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:01 ts_0800274a3104 audit[52571]: CRED_ACQ pid=52571 uid=0 auid=1000 ses=77 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:02 ts_0800274a3104 pulseaudio[52935]: Daemon already running. апр 04 16:47:03 ts_0800274a3104 systemd[1]: session-76.scope: Succeeded. апр 04 16:47:03 ts_0800274a3104 systemd-logind[2235]: Removed session 76. апр 04 16:47:04 ts_0800274a3104 audit[52571]: CRED_DISP pid=52571 uid=0 auid=1000 ses=77 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:04 ts_0800274a3104 audit[52571]: USER_END pid=52571 uid=0 auid=1000 ses=77 msg='op=PAM:session_close grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:04 ts_0800274a3104 systemd[1]: display-manager.service: Succeeded. апр 04 16:47:04 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:04 ts_0800274a3104 systemd-logind[2235]: Session 77 logged out. Waiting for processes to exit. апр 04 16:47:04 ts_0800274a3104 systemd[1]: display-manager.service: Scheduled restart job, restart counter is at 76. апр 04 16:47:04 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:04 ts_0800274a3104 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:04 ts_0800274a3104 systemd[1]: Stopped ThinStation Display Manager. апр 04 16:47:04 ts_0800274a3104 systemd[1]: Started ThinStation Display Manager. апр 04 16:47:04 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=display-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' апр 04 16:47:04 ts_0800274a3104 audit[53224]: USER_ACCT pid=53224 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_succeed_if acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:04 ts_0800274a3104 audit[53224]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=4 a1=7fff1d93f220 a2=4 a3=7f351d538558 items=0 ppid=1 pid=53224 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=78 comm="login" exe="/bin/busybox" key=(null) апр 04 16:47:04 ts_0800274a3104 audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D6600747375736572 апр 04 16:47:04 ts_0800274a3104 systemd-logind[2235]: New session 78 of user tsuser. апр 04 16:47:04 ts_0800274a3104 systemd[1]: Started Session 78 of user tsuser. апр 04 16:47:04 ts_0800274a3104 audit[53224]: USER_START pid=53224 uid=0 auid=1000 ses=78 msg='op=PAM:session_open grantors=pam_loginuid,pam_systemd,pam_unix,pam_env,pam_hooks,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:04 ts_0800274a3104 audit[53224]: CRED_ACQ pid=53224 uid=0 auid=1000 ses=78 msg='op=PAM:setcred grantors=pam_securetty,pam_tally,pam_shells,pam_unix,pam_gnome_keyring acct="tsuser" exe="/bin/busybox" hostname=ts_0800274a3104 addr=? terminal=tty1 res=success' апр 04 16:47:05 ts_0800274a3104 pulseaudio[53588]: Daemon already running. апр 04 16:47:06 ts_0800274a3104 systemd[1]: session-77.scope: Succeeded. апр 04 16:47:06 ts_0800274a3104 systemd[1]: session-77.scope: Consumed 1.680s CPU time. апр 04 16:47:06 ts_0800274a3104 systemd-logind[2235]: Removed session 77.

messages Apr 4 16:59:16 thinstation-linux syslog.info syslogd started: BusyBox v1.34.1 Apr 4 16:59:16 thinstation-linux cron.info crond[2506]: crond (busybox 1.34.1) started, log level 8 Apr 4 16:59:17 thinstation-linux authpriv.info login[3486]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser" Apr 4 16:59:18 thinstation-linux authpriv.info login[3486]: pam_unix(login:session): session opened for user tsuser by (uid=0) Apr 4 16:59:18 thinstation-linux user.warn gnome-keyring-daemon: Libgcrypt warning: custom allocation handler - FIPS mode inactivated Apr 4 16:59:18 thinstation-linux authpriv.info login[3486]: gkr-pam: gnome-keyring-daemon started properly Apr 4 16:59:19 thinstation-linux daemon.info dbus-daemon[3852]: [session uid=1000 pid=3850] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=1000 pid=4034 comm="dconf write /system/p roxy/mode 'none' ") Apr 4 16:59:19 thinstation-linux daemon.info dbus-daemon[3852]: [session uid=1000 pid=3850] Successfully activated service 'ca.desrt.dconf' Apr 4 16:59:20 thinstation-linux authpriv.info login[3486]: pam_unix(login:session): session closed for user tsuser Apr 4 16:59:20 thinstation-linux authpriv.info login[4150]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser" Apr 4 16:59:20 thinstation-linux authpriv.info login[4150]: pam_unix(login:session): session opened for user tsuser by LOGIN(uid=0) Apr 4 16:59:20 thinstation-linux authpriv.err login[4150]: gkr-pam: couldn't unlock the login keyring. Apr 4 16:59:21 thinstation-linux daemon.info dbus-daemon[4508]: [session uid=1000 pid=4506] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=4688 comm="dconf write /system/p roxy/mode 'none' ") Apr 4 16:59:21 thinstation-linux daemon.info dbus-daemon[4508]: [session uid=1000 pid=4506] Successfully activated service 'ca.desrt.dconf' Apr 4 16:59:22 thinstation-linux authpriv.info login[4150]: pam_unix(login:session): session closed for user tsuser Apr 4 16:59:22 thinstation-linux authpriv.info login[4803]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser" Apr 4 16:59:22 thinstation-linux authpriv.info login[4803]: pam_unix(login:session): session opened for user tsuser by LOGIN(uid=0) Apr 4 16:59:23 thinstation-linux authpriv.err login[4803]: gkr-pam: couldn't unlock the login keyring. Apr 4 16:59:24 thinstation-linux daemon.info dbus-daemon[5161]: [session uid=1000 pid=5159] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=5341 comm="dconf write /system/p roxy/mode 'none' ") Apr 4 16:59:24 thinstation-linux daemon.info dbus-daemon[5161]: [session uid=1000 pid=5159] Successfully activated service 'ca.desrt.dconf' Apr 4 16:59:25 thinstation-linux authpriv.info login[4803]: pam_unix(login:session): session closed for user tsuser Apr 4 16:59:25 thinstation-linux authpriv.info login[5456]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser" Apr 4 16:59:25 thinstation-linux authpriv.info login[5456]: pam_unix(login:session): session opened for user tsuser by LOGIN(uid=0) Apr 4 16:59:26 thinstation-linux authpriv.err login[5456]: gkr-pam: couldn't unlock the login keyring. Apr 4 16:59:27 thinstation-linux daemon.info dbus-daemon[5814]: [session uid=1000 pid=5812] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=5994 comm="dconf write /system/p roxy/mode 'none' ") Apr 4 16:59:27 thinstation-linux daemon.info dbus-daemon[5814]: [session uid=1000 pid=5812] Successfully activated service 'ca.desrt.dconf' Apr 4 16:59:28 thinstation-linux authpriv.info login[5456]: pam_unix(login:session): session closed for user tsuser Apr 4 16:59:28 thinstation-linux authpriv.info login[6109]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser" Apr 4 16:59:28 thinstation-linux authpriv.info login[6109]: pam_unix(login:session): session opened for user tsuser by LOGIN(uid=0) Apr 4 16:59:28 thinstation-linux authpriv.err login[6109]: gkr-pam: couldn't unlock the login keyring. Apr 4 16:59:29 thinstation-linux daemon.info dbus-daemon[6467]: [session uid=1000 pid=6465] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=6647 comm="dconf write /system/p roxy/mode 'none' ") Apr 4 16:59:29 thinstation-linux daemon.info dbus-daemon[6467]: [session uid=1000 pid=6465] Successfully activated service 'ca.desrt.dconf' Apr 4 16:59:31 thinstation-linux authpriv.info login[6109]: pam_unix(login:session): session closed for user tsuser Apr 4 16:59:32 thinstation-linux authpriv.info login[6762]: pam_succeed_if(login:account): requirement "user = tsuser" was met by user "tsuser" Apr 4 16:59:32 thinstation-linux authpriv.info login[6762]: pam_unix(login:session): session opened for user tsuser by LOGIN(uid=0) Apr 4 16:59:32 thinstation-linux authpriv.err login[6762]: gkr-pam: couldn't unlock the login keyring. Apr 4 16:59:32 thinstation-linux daemon.info dbus-daemon[7120]: [session uid=1000 pid=7118] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=7300 comm="dconf write /system/p roxy/mode 'none' ")

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

AlexanderZhirov commented 3 months ago

Most likely, it's about rights. Shouldn't WM be run as root?

изображение

Doncuppjr commented 3 months ago

Possibly. Try a root session. Some adjustments would need to be made to init if that is required. 

Sent from Yahoo Mail for iPhone

On Thursday, April 4, 2024, 11:36 AM, Alexander Zhirov @.***> wrote:

Most likely, it's about rights. Shouldn't WM be run as root?

default.png (view on web)

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

Doncuppjr commented 3 months ago

Look at the lightdm package

Sent from Yahoo Mail for iPhone

On Thursday, April 4, 2024, 11:36 AM, Alexander Zhirov @.***> wrote:

Most likely, it's about rights. Shouldn't WM be run as root?

default.png (view on web)

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

AlexanderZhirov commented 3 months ago

It was possible to solve the startup problem at startup in this way. I looked at how this is implemented in lightdm, added the finalize file to the xorg-xdm package.

packages/xorg-xdm/build/finalize:

#xdm 29

cat << EOF >> /etc/group
autologin:!:621:tsuser
EOF

rm /etc/systemd/system/display-manager.service
systemctl enable xdm

xdm.service:

Description=X-Window Display Manager
After=getty@tty1.service systemd-user-sessions.service

[Service]
ExecStart=/usr/bin/xdm -nodaemon -config /etc/X11/xdm/antsy/xdm-config
Type=notify
NotifyAccess=all
Restart=always

[Install]
Alias=display-manager.service

In thinstation.conf.buildtime left the setting intact SESSION_0_TYPE=sh.

Here is the result, as it turned out (YouTube)

The problem remains that a user profile is not being created from /etc/skel. Thus, it is not possible to log in via xdm.

How well have I set up the configuration to run XDM?

Doncuppjr commented 3 months ago

So when we come in with the default display-manager.service, pam uses the login file which calls pam_hooks.so which calls another script that creates the homedir and copies /etc/skel. @._chroot]/build/packages/base# cat etc/pam.d/login#%PAM-1.0auth required pam_securetty.soauth include system-local-loginauth sufficient pam_succeed_if.so  user = root#auth optional pam_gnome_keyring.soaccount include system-local-loginaccount         sufficient      pam_succeed_if.so  user = rootpassword include system-local-loginpassword        sufficient      pam_succeed_if.so  user = rootsession include system-local-loginsession optional pam_hooks.so /sbin/session#session optional pam_gnome_keyring.so auto_start#-session optional pam_ck_connector.so nox11 You could add that line to whatever file xdm is using for pam instead. On Thursday, April 4, 2024 at 04:21:13 PM MDT, Alexander Zhirov @.> wrote:

It was possible to solve the startup problem at startup in this way. I looked at how this is implemented in lightdm, added the finalize file to the xorg-xdm package.

packages/xorg-xdm/build/finalize:

xdm 29

cat << EOF >> /etc/group autologin:!:621:tsuser EOF

rm /etc/systemd/system/display-manager.service systemctl enable xdm

In thinstation.conf.buildtime left the setting intact SESSION_0_TYPE=sh.

Here is the result, as it turned out (YouTube)

The problem remains that a user profile is not being created from /etc/skel. Thus, it is not possible to log in via xdm.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

AlexanderZhirov commented 3 months ago

Yes, after correcting the file, authorization is successful! Thank you!

echo 'session optional pam_hooks.so /sbin/session' >> /etc/pam.d/xdm

изображение

The necessary services are started under the user tsuser. The only problem is that the service does not start in VirtualBox after authorization (you can see in the screenshot).

изображение

● vboxadd-service.service
     Loaded: loaded (/etc/init.d/vboxadd-service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-04-09 01:39:59 MSK; 5min ago
    Process: 929 ExecStart=/etc/init.d/vboxadd-service start (code=exited, status=1/FAILURE)
        CPU: 8ms

апр 09 01:39:59 thinstation-linux systemd[1]: Starting vboxadd-service.service...
апр 09 01:39:59 thinstation-linux vboxadd-service[929]: vboxadd-service.sh: Starting VirtualBox Guest Addition service.
апр 09 01:39:59 thinstation-linux vboxadd-service.sh[936]: Starting VirtualBox Guest Addition service.
апр 09 01:39:59 thinstation-linux vboxadd-service[929]: VirtualBox Additions module not loaded!
апр 09 01:39:59 thinstation-linux systemd[1]: vboxadd-service.service: Control process exited, code=exited, status=1/FAILURE
апр 09 01:39:59 thinstation-linux systemd[1]: vboxadd-service.service: Failed with result 'exit-code'.
апр 09 01:39:59 thinstation-linux systemd[1]: Failed to start vboxadd-service.service.

At the same time, it is manually started. Do I understand correctly that it is necessary to change the priority of launching the systems service, which will depend on the start of DisplayManager?

AlexanderZhirov commented 3 months ago

P.S. And if I add the networkmanager package to the existing assembly, then the screen resolution setting breaks. It is not possible to configure dynamically, even if there is a virtualbox guest package.

AlexanderZhirov commented 2 months ago

@Doncuppjr I updated the VirtualBox source in the build.urls file to version 7.0.14. I changed it in the service file vboxadd-service.service

...
Restart=on-failure
RestartSec=5s
...

Now the guest add-on is running and working correctly.

Also made the launch of xdm.service dependent on the launch of NetworkManager.service

Description=X-Window Display Manager
After=getty@tty1.service systemd-user-sessions.service NetworkManager.service

[Service]
ExecStart=/usr/bin/xdm -nodaemon -config /etc/X11/xdm/antsy/xdm-config
Type=notify
NotifyAccess=all
Restart=always

[Install]
Alias=display-manager.service

At first glance, everything works as intended 👍