Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Authorization required, but no authorization protocol specified #823

Open
AlexanderZhirov opened this issue May 5, 2024 · 11 comments
Open

Authorization required, but no authorization protocol specified #823

AlexanderZhirov opened this issue May 5, 2024 · 11 comments

Comments

@AlexanderZhirov
Copy link

I run several utilities from under icewm-session in startup, including 'nm-applet'. As soon as I try to manually connect via nm-applet to a wi-fi network, any GUI applications stop opening for me. They seem to lose DISPLAY and cannot be rendered on the desktop, while the error in the logs is `Authorization required, but no authorization protocol specified'.

2024-05-06_02-22-01.mp4

At the same time, as you can see, the hostname changes after connecting to a wi-fi network.

An Internet search gave the following result:

# /etc/NetworkManager/NetworkManager.conf
[main]
hostname-mode=none

The problem with opening windows was avoided. But the hostname does not change. Accordingly, when connecting, something happens that breaks the user environment.

As I understand it, neither polkit nor anything else will help here. How can this problem be fixed?

laptop:~$ whoami
tsuser
laptop:~$ id
uid=1000(tsuser) gid=1000(tsuser) groups=5(tty),6(disk),7(lp),14(dialout),16(audio),17(video),19(tape),21(cdrom),24(storage),25(fuse),26(uucp),28(sudo),40(network),91(pulse-access),100(users),112(pkcs11),125(docker),996(termidesk),1000(tsuser)
@AlexanderZhirov
Copy link
Author

AlexanderZhirov commented May 5, 2024 •
edited
Loading

NetworkManager is breaking something. But the user is in the network group, but this does not help to avoid the problem.

There is an assumption that execution fails at root (or is executed from under another user), and there, in turn, there is no access to DISPLAY. Although this is absurd. How can child processes affect parent processes?

@AlexanderZhirov
Copy link
Author

Most likely, the problem is related to the icewm session.

@Doncuppjr
Copy link
Contributor

Doncuppjr commented May 6, 2024 via email •
edited by Thinstation
Loading

@AlexanderZhirov
Copy link
Author

@Doncuppjr I don't quite understand what you mean.

изображение

мая 06 15:39:39 ts_0800274a3104 polkitd[4108]: 15:39:39.923: Registered Authentication Agent for unix-process:4181:22774 (system bus name :1.35 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale ru_RU.utf8)
мая 06 15:39:39 ts_0800274a3104 polkitd[4108]: 15:39:39.931: /etc/polkit-1/rules.d/00-log-access.rules:2: action=[Action id='org.freedesktop.hostname1.set-static-hostname']
мая 06 15:39:39 ts_0800274a3104 polkitd[4108]: 15:39:39.931: /etc/polkit-1/rules.d/00-log-access.rules:3: subject=[Subject pid=4181 user='tsuser' groups=tsuser,tty,disk,lp,dialout,audio,video,tape,cdrom,storage,fuse,uucp,sudo,network,users,pkcs11,docker,pulse-access,termidesk seat=null session=null local=false active=false]
мая 06 15:39:39 ts_0800274a3104 polkitd[4108]: 15:39:39.937: Unregistered Authentication Agent for unix-process:4181:22774 (system bus name :1.35, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale ru_RU.utf8) (disconnected from bus)
мая 06 15:40:05 ts_0800274a3104 NetworkManager[1194]: <info>  [1714999205.3980] policy: set-hostname: current hostname was changed outside NetworkManager: 'ts_0800274a3104'
мая 06 15:40:05 ts_0800274a3104 NetworkManager[1194]: <info>  [1714999205.3983] policy: set-hostname: set hostname to 'ts_0800274a3104.Dlink' (from address lookup)
мая 06 15:40:05 ts_0800274a3104 NetworkManager[1194]: <warn>  [1714999205.3999] hostname: couldn't set the system hostname to 'ts_0800274a3104.Dlink' using hostnamed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid hostname 'ts_0800274a3104.Dlink'
мая 06 15:40:05 ts_0800274a3104 NetworkManager[1194]: <warn>  [1714999205.4000] policy: set-hostname: couldn't set the system hostname to 'ts_0800274a3104.Dlink': (1) Operation not permitted
мая 06 15:40:05 ts_0800274a3104 NetworkManager[1194]: <warn>  [1714999205.4000] policy: set-hostname: you should use hostnamed when systemd hardening is in effect!
мая 06 15:40:55 ts_0800274a3104 NetworkManager[1194]: <info>  [1714999255.4232] policy: set-hostname: current hostname was changed outside NetworkManager: 'ts_0800274a3104'
мая 06 15:40:55 ts_0800274a3104 NetworkManager[1194]: <info>  [1714999255.4234] policy: set-hostname: set hostname to 'ts_0800274a3104.Dlink' (from address lookup)
мая 06 15:40:55 ts_0800274a3104 NetworkManager[1194]: <warn>  [1714999255.4253] hostname: couldn't set the system hostname to 'ts_0800274a3104.Dlink' using hostnamed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid hostname 'ts_0800274a3104.Dlink'
мая 06 15:40:55 ts_0800274a3104 NetworkManager[1194]: <warn>  [1714999255.4254] policy: set-hostname: couldn't set the system hostname to 'ts_0800274a3104.Dlink': (1) Operation not permitted
мая 06 15:40:55 ts_0800274a3104 NetworkManager[1194]: <warn>  [1714999255.4254] policy: set-hostname: you should use hostnamed when systemd hardening is in effect!
мая 06 15:41:02 ts_0800274a3104 audit[4191]: USER_AUTH pid=4191 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_unix acct="tsuser" exe="/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
мая 06 15:41:02 ts_0800274a3104 audit[4191]: USER_ACCT pid=4191 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_unix acct="tsuser" exe="/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
мая 06 15:41:02 ts_0800274a3104 audit[4191]: CRED_REFR pid=4191 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
мая 06 15:41:02 ts_0800274a3104 kernel: audit: type=1100 audit(1714999262.716:82): pid=4191 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_unix acct="tsuser" exe="/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
мая 06 15:41:02 ts_0800274a3104 kernel: audit: type=1101 audit(1714999262.716:83): pid=4191 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_unix acct="tsuser" exe="/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
мая 06 15:41:02 ts_0800274a3104 kernel: audit: type=1110 audit(1714999262.717:84): pid=4191 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
мая 06 15:41:02 ts_0800274a3104 systemd[1]: Created slice User Slice of UID 0.
мая 06 15:41:02 ts_0800274a3104 systemd[1]: Starting User Runtime Directory /run/user/0...
мая 06 15:41:02 ts_0800274a3104 systemd-logind[927]: New session c1 of user root.
мая 06 15:41:02 ts_0800274a3104 systemd[1]: Started User Runtime Directory /run/user/0.
мая 06 15:41:02 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@0 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:02 ts_0800274a3104 kernel: audit: type=1130 audit(1714999262.753:85): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@0 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:02 ts_0800274a3104 systemd[1]: Starting User Manager for UID 0...
мая 06 15:41:02 ts_0800274a3104 audit[4193]: USER_ACCT pid=4193 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_unix acct="root" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:02 ts_0800274a3104 audit[4193]: SYSCALL arch=c000003e syscall=1 success=yes exit=1 a0=7 a1=7fff9eebdb80 a2=1 a3=7fab0315d558 items=0 ppid=1 pid=4193 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="(systemd)" exe="/lib/systemd/systemd" key=(null)
мая 06 15:41:02 ts_0800274a3104 kernel: audit: type=1101 audit(1714999262.767:86): pid=4193 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_unix acct="root" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:02 ts_0800274a3104 kernel: audit: type=1006 audit(1714999262.767:87): pid=4193 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=1 res=1
мая 06 15:41:02 ts_0800274a3104 kernel: audit: type=1300 audit(1714999262.767:87): arch=c000003e syscall=1 success=yes exit=1 a0=7 a1=7fff9eebdb80 a2=1 a3=7fab0315d558 items=0 ppid=1 pid=4193 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="(systemd)" exe="/lib/systemd/systemd" key=(null)
мая 06 15:41:02 ts_0800274a3104 kernel: audit: type=1327 audit(1714999262.767:87): proctitle="(systemd)"
мая 06 15:41:02 ts_0800274a3104 kernel: audit: type=1105 audit(1714999262.768:88): pid=4193 uid=0 auid=0 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_systemd acct="root" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:02 ts_0800274a3104 audit: PROCTITLE proctitle="(systemd)"
мая 06 15:41:02 ts_0800274a3104 audit[4193]: USER_START pid=4193 uid=0 auid=0 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_systemd acct="root" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:02 ts_0800274a3104 audit: AUDIT1334 prog-id=23 op=LOAD
мая 06 15:41:02 ts_0800274a3104 audit[4193]: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7fffe5cf3fa0 a2=70 a3=7f4426424c60 items=0 ppid=1 pid=4193 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="systemd" exe="/lib/systemd/systemd" key=(null)
мая 06 15:41:02 ts_0800274a3104 audit: PROCTITLE proctitle="(systemd)"
мая 06 15:41:02 ts_0800274a3104 kernel: audit: type=1334 audit(1714999262.776:89): prog-id=23 op=LOAD
мая 06 15:41:02 ts_0800274a3104 audit: AUDIT1334 prog-id=23 op=UNLOAD
мая 06 15:41:02 ts_0800274a3104 audit: AUDIT1334 prog-id=24 op=LOAD
мая 06 15:41:02 ts_0800274a3104 audit[4193]: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7fffe5cf4070 a2=70 a3=7f4426424c60 items=0 ppid=1 pid=4193 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="systemd" exe="/lib/systemd/systemd" key=(null)
мая 06 15:41:02 ts_0800274a3104 audit: PROCTITLE proctitle="(systemd)"
мая 06 15:41:02 ts_0800274a3104 audit: AUDIT1334 prog-id=24 op=UNLOAD
мая 06 15:41:02 ts_0800274a3104 systemd[4193]: Reached target Paths.
мая 06 15:41:02 ts_0800274a3104 systemd[4193]: Reached target Sockets.
мая 06 15:41:02 ts_0800274a3104 systemd[4193]: Reached target Timers.
мая 06 15:41:02 ts_0800274a3104 systemd[4193]: Reached target Basic System.
мая 06 15:41:02 ts_0800274a3104 systemd[4193]: Reached target Main User Target.
мая 06 15:41:02 ts_0800274a3104 systemd[4193]: Startup finished in 83ms.
мая 06 15:41:02 ts_0800274a3104 systemd[1]: Started User Manager for UID 0.
мая 06 15:41:02 ts_0800274a3104 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@0 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:02 ts_0800274a3104 systemd[1]: Started Session c1 of user root.
мая 06 15:41:03 ts_0800274a3104 audit[4191]: USER_START pid=4191 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
мая 06 15:41:03 mypc.local systemd-hostnamed[4178]: Changed static host name to 'mypc.local'
мая 06 15:41:03 mypc.local NetworkManager[1194]: <info>  [1714999263.4035] hostname: hostname changed from (none) to "mypc.local"
мая 06 15:41:03 mypc.local systemd-hostnamed[4178]: Changed host name to 'mypc.local'
мая 06 15:41:03 mypc.local NetworkManager[1194]: <info>  [1714999263.4037] policy: set-hostname: current hostname was changed outside NetworkManager: 'ts_0800274a3104'
мая 06 15:41:03 mypc.local NetworkManager[1194]: <info>  [1714999263.4041] dns-mgr: Writing DNS information to /usr/sbin/resolvconf
мая 06 15:41:03 mypc.local audit[4191]: USER_END pid=4191 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
мая 06 15:41:03 mypc.local audit[4191]: CRED_DISP pid=4191 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
мая 06 15:41:03 mypc.local systemd[1]: Starting Network Manager Script Dispatcher Service...
мая 06 15:41:03 mypc.local systemd[1]: session-c1.scope: Succeeded.
мая 06 15:41:03 mypc.local systemd-logind[927]: Session c1 logged out. Waiting for processes to exit.
мая 06 15:41:03 mypc.local systemd-logind[927]: Removed session c1.
мая 06 15:41:03 mypc.local systemd[1]: Started Network Manager Script Dispatcher Service.
мая 06 15:41:03 mypc.local audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:03 mypc.local NetworkManager[1194]: <info>  [1714999263.4869] policy: set-hostname: set hostname to 'mypc.local' (from system configuration)
мая 06 15:41:13 mypc.local systemd[1]: Stopping User Manager for UID 0...
мая 06 15:41:13 mypc.local systemd[4193]: Stopped target Main User Target.
мая 06 15:41:13 mypc.local systemd[4193]: Stopped target Basic System.
мая 06 15:41:13 mypc.local systemd[4193]: Stopped target Paths.
мая 06 15:41:13 mypc.local systemd[4193]: Stopped target Sockets.
мая 06 15:41:13 mypc.local systemd[4193]: Reached target Shutdown.
мая 06 15:41:13 mypc.local systemd[4193]: Stopped target Timers.
мая 06 15:41:13 mypc.local systemd[4193]: systemd-exit.service: Succeeded.
мая 06 15:41:13 mypc.local systemd[4193]: Started Exit the Session.
мая 06 15:41:13 mypc.local systemd[4193]: Reached target Exit the Session.
мая 06 15:41:13 mypc.local audit[4194]: USER_END pid=4194 uid=0 auid=0 ses=1 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_systemd acct="root" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:13 mypc.local systemd[1]: [email protected]: Succeeded.
мая 06 15:41:13 mypc.local systemd[1]: Stopped User Manager for UID 0.
мая 06 15:41:13 mypc.local audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@0 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:13 mypc.local kernel: kauditd_printk_skb: 12 callbacks suppressed
мая 06 15:41:13 mypc.local kernel: audit: type=1106 audit(1714999273.548:98): pid=4194 uid=0 auid=0 ses=1 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_systemd acct="root" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:13 mypc.local kernel: audit: type=1131 audit(1714999273.548:99): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@0 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:13 mypc.local systemd[1]: Stopping User Runtime Directory /run/user/0...
мая 06 15:41:13 mypc.local systemd[1]: run-user-0.mount: Succeeded.
мая 06 15:41:13 mypc.local systemd[1]: [email protected]: Succeeded.
мая 06 15:41:13 mypc.local systemd[1]: Stopped User Runtime Directory /run/user/0.
мая 06 15:41:13 mypc.local audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@0 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:13 mypc.local kernel: audit: type=1131 audit(1714999273.568:100): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@0 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:13 mypc.local systemd[1]: Removed slice User Slice of UID 0.
мая 06 15:41:14 mypc.local systemd[1]: NetworkManager-dispatcher.service: Succeeded.
мая 06 15:41:14 mypc.local audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:14 mypc.local kernel: audit: type=1131 audit(1714999274.171:101): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:33 mypc.local systemd[1]: systemd-hostnamed.service: Succeeded.
мая 06 15:41:33 mypc.local audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:33 mypc.local kernel: audit: type=1131 audit(1714999293.519:102): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:33 mypc.local audit: AUDIT1334 prog-id=22 op=UNLOAD
мая 06 15:41:33 mypc.local audit: AUDIT1334 prog-id=21 op=UNLOAD
мая 06 15:41:33 mypc.local audit: AUDIT1334 prog-id=20 op=UNLOAD
мая 06 15:41:33 mypc.local kernel: audit: type=1334 audit(1714999293.581:103): prog-id=22 op=UNLOAD
мая 06 15:41:33 mypc.local kernel: audit: type=1334 audit(1714999293.581:104): prog-id=21 op=UNLOAD
мая 06 15:41:33 mypc.local kernel: audit: type=1334 audit(1714999293.581:105): prog-id=20 op=UNLOAD
мая 06 15:41:36 mypc.local audit: AUDIT1334 prog-id=25 op=LOAD
мая 06 15:41:36 mypc.local audit: AUDIT1334 prog-id=26 op=LOAD
мая 06 15:41:36 mypc.local audit: AUDIT1334 prog-id=27 op=LOAD
мая 06 15:41:36 mypc.local kernel: audit: type=1334 audit(1714999296.632:106): prog-id=25 op=LOAD
мая 06 15:41:36 mypc.local kernel: audit: type=1334 audit(1714999296.632:107): prog-id=26 op=LOAD
мая 06 15:41:36 mypc.local kernel: audit: type=1334 audit(1714999296.632:108): prog-id=27 op=LOAD
мая 06 15:41:36 mypc.local systemd[1]: Starting Hostname Service...
мая 06 15:41:36 mypc.local systemd[1]: Started Hostname Service.
мая 06 15:41:36 mypc.local audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:41:36 mypc.local kernel: audit: type=1130 audit(1714999296.685:109): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:42:06 mypc.local systemd[1]: systemd-hostnamed.service: Succeeded.
мая 06 15:42:06 mypc.local audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:42:06 mypc.local kernel: audit: type=1131 audit(1714999326.735:110): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
мая 06 15:42:07 mypc.local audit: AUDIT1334 prog-id=27 op=UNLOAD
мая 06 15:42:07 mypc.local audit: AUDIT1334 prog-id=26 op=UNLOAD
мая 06 15:42:07 mypc.local audit: AUDIT1334 prog-id=25 op=UNLOAD
мая 06 15:42:07 mypc.local kernel: audit: type=1334 audit(1714999327.046:111): prog-id=27 op=UNLOAD
мая 06 15:42:07 mypc.local kernel: audit: type=1334 audit(1714999327.046:112): prog-id=26 op=UNLOAD
мая 06 15:42:07 mypc.local kernel: audit: type=1334 audit(1714999327.046:113): prog-id=25 op=UNLOAD

@Thinstation
Copy link
Owner

Thinstation commented May 6, 2024 via email •
edited
Loading

@AlexanderZhirov
Copy link
Author

@Doncuppjr The fact is that this also happens when calling hostnamectl set-hostname <name> . This does not affect the invocation of the script that you specified.

@AlexanderZhirov
Copy link
Author

For the sake of experiment, I deleted the script and called hostnamectl. The result is the same.

ts_0800274a3104:~# rm /etc/NetworkManager/dispatcher.d/00-update-status
ts_0800274a3104:~# systemctl restart NetworkManager
ts_0800274a3104:~# hostnamectl set-hostname abc.local
abc:~# hostnamectl 
   Static hostname: abc.local
         Icon name: computer-vm
           Chassis: vm
        Machine ID: b9324f822b8042b585bc9c927671e7b2
           Boot ID: 1456b427f4e341089ebda4a36666ec68
    Virtualization: oracle
  Operating System: ThinStation 6.2 Alice
       CPE OS Name: cpe:/o:thinstation:thinstation:6.2
            Kernel: Linux 6.1.63TS
      Architecture: x86-64

Most likely a question for the icewm session

@Doncuppjr
Copy link
Contributor

Doncuppjr commented May 6, 2024 via email •
edited by Thinstation
Loading

@AlexanderZhirov
Copy link
Author

@Doncuppjr With these edits, it was possible to assemble an image. Now IceWM does not crash. But, as I understand it, the problem in IceWM still persists.

@Doncuppjr
Copy link
Contributor

Doncuppjr commented May 7, 2024 via email •
edited by Thinstation
Loading

@AlexanderZhirov
Copy link
Author

The IceWM session starts after authorization via xdm. Accordingly, somewhere in the intermediate stage, most likely, it is necessary to somehow throw in the settings or updates of the session?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Doncuppjr @Thinstation @AlexanderZhirov