Skip to main content ↑ ↓
Topic: Artix installation (Read 4296 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Artix installation

Artix iso test installation report:
artix-xfce-s6-20201128-x86_64.iso: install successful, boot successful.
artix-xfce-s6-20201211-x86_64.iso: install successful, boot fail.

Xorg.0.log
Code: [Select]
[    32.837] (WW) Failed to open protocol names file lib/xorg/protocol.txt
[    32.837] 
X.Org X Server 1.20.10
X Protocol Version 11, Revision 0
[    32.837] Build Operating System: Linux Artix Linux
[    32.837] Current Operating System: Linux Inspiron 5.9.12-artix1-1 #1 SMP PREEMPT Wed, 02 Dec 2020 22:03:38 +0000 x86_64
[    32.837] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=13adf478-dadc-45ad-b4b0-eea38a4031d7 rw net.ifnames=0 quiet
[    32.838] Build Date: 01 December 2020  09:01:21PM
[    32.838]  
[    32.838] Current version of pixman: 0.40.0
[    32.838] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    32.838] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    32.838] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 13 13:59:22 2020
[    32.838] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    32.838] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    32.838] (==) No Layout section.  Using the first Screen section.
[    32.838] (==) No screen section available. Using defaults.
[    32.838] (**) |-->Screen "Default Screen Section" (0)
[    32.838] (**) |   |-->Monitor "<default monitor>"
[    32.838] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    32.838] (==) Automatically adding devices
[    32.838] (==) Automatically enabling devices
[    32.838] (==) Automatically adding GPU devices
[    32.838] (==) Automatically binding GPU devices
[    32.838] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    32.838] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/misc".
[    32.838] 	Entry deleted from font path.
[    32.838] 	(Run 'mkfontdir' on "/usr/share/fonts/misc").
[    32.839] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF".
[    32.839] 	Entry deleted from font path.
[    32.839] 	(Run 'mkfontdir' on "/usr/share/fonts/TTF").
[    32.839] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    32.839] 	Entry deleted from font path.
[    32.839] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    32.839] 	Entry deleted from font path.
[    32.839] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    32.839] 	Entry deleted from font path.
[    32.839] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    32.839] 	Entry deleted from font path.
[    32.839] (==) FontPath set to:
	
[    32.839] (==) ModulePath set to "/usr/lib/xorg/modules"
[    32.839] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    32.839] (II) Module ABI versions:
[    32.839] 	X.Org ANSI C Emulation: 0.4
[    32.839] 	X.Org Video Driver: 24.1
[    32.839] 	X.Org XInput driver : 24.1
[    32.839] 	X.Org Server Extension : 10.0
[    32.840] (++) using VT number 7

[    32.840] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    32.840] (II) xfree86: Adding drm device (/dev/dri/card0)
[    32.840] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
[    32.844] (--) PCI:*(0@0:2:0) 8086:2a42:1028:02aa rev 7, Mem @ 0xf6c00000/4194304, 0xe0000000/268435456, I/O @ 0x0000efe8/8, BIOS @ 0x????????/131072
[    32.845] (--) PCI: (0@0:2:1) 8086:2a43:1028:02aa rev 7, Mem @ 0xf6b00000/1048576
[    32.845] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    32.846] (II) LoadModule: "glx"
[    32.846] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    32.848] (II) Module glx: vendor="X.Org Foundation"
[    32.848] 	compiled for 1.20.10, module version = 1.0.0
[    32.848] 	ABI class: X.Org Server Extension, version 10.0
[    32.848] (==) Matched intel as autoconfigured driver 0
[    32.848] (==) Matched modesetting as autoconfigured driver 1
[    32.848] (==) Matched fbdev as autoconfigured driver 2
[    32.848] (==) Matched vesa as autoconfigured driver 3
[    32.848] (==) Assigned the driver to the xf86ConfigLayout
[    32.848] (II) LoadModule: "intel"
[    32.848] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[    32.849] (II) Module intel: vendor="X.Org Foundation"
[    32.849] 	compiled for 1.20.9, module version = 2.99.917
[    32.849] 	Module class: X.Org Video Driver
[    32.849] 	ABI class: X.Org Video Driver, version 24.1
[    32.849] (II) LoadModule: "modesetting"
[    32.849] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    32.849] (II) Module modesetting: vendor="X.Org Foundation"
[    32.849] 	compiled for 1.20.10, module version = 1.20.10
[    32.849] 	Module class: X.Org Video Driver
[    32.850] 	ABI class: X.Org Video Driver, version 24.1
[    32.850] (II) LoadModule: "fbdev"
[    32.850] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    32.850] (II) Module fbdev: vendor="X.Org Foundation"
[    32.850] 	compiled for 1.20.8, module version = 0.5.0
[    32.850] 	Module class: X.Org Video Driver
[    32.850] 	ABI class: X.Org Video Driver, version 24.1
[    32.850] (II) LoadModule: "vesa"
[    32.850] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[    32.850] (II) Module vesa: vendor="X.Org Foundation"
[    32.850] 	compiled for 1.20.9, module version = 2.5.0
[    32.850] 	Module class: X.Org Video Driver
[    32.850] 	ABI class: X.Org Video Driver, version 24.1
[    32.850] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
	i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
	915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
	Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
	GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[    32.850] (II) intel: Driver for Intel(R) HD Graphics
[    32.850] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[    32.850] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[    32.850] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    32.850] (II) FBDEV: driver for framebuffer: fbdev
[    32.850] (II) VESA: driver for VESA chipsets: vesa
[    32.850] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[    32.851] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20200715
[    32.851] (II) intel(0): SNA compiled from 2.99.917-913-g9236c582
[    32.867] (WW) Falling back to old probe method for modesetting
[    32.867] (WW) Falling back to old probe method for fbdev
[    32.867] (II) Loading sub module "fbdevhw"
[    32.867] (II) LoadModule: "fbdevhw"
[    32.867] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    32.867] (II) Module fbdevhw: vendor="X.Org Foundation"
[    32.867] 	compiled for 1.20.10, module version = 0.0.2
[    32.867] 	ABI class: X.Org Video Driver, version 24.1
[    35.110] (EE) intel(0): [drm] failed to set drm interface version: Permission denied [13].
[    35.110] (II) intel(0): [drm] Contents of '/sys/kernel/debug/dri/0/clients':
[    35.110] (II) intel(0): [drm]              command   pid dev master a   uid      magic
[    35.110] (II) intel(0): [drm]                 Xorg   788   0   y    y     0          0
[    35.110] (II) intel(0): [drm]                 Xorg  1012   0   n    y     0          0
[    35.110] (II) intel(0): [drm]                 Xorg  1083   0   n    y     0          0
[    35.110] (EE) intel(0): Failed to claim DRM device.
[    35.110] (II) UnloadModule: "intel"
[    35.110] (EE) Screen(s) found, but none have a usable configuration.
[    35.110] (EE) 
Fatal server error:
[    35.110] (EE) no screens found(EE) 
[    35.110] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    35.110] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    35.110] (EE) 
[    35.131] (EE) Server terminated with error (1). Closing log file.
Thank you.

Re: Artix installation

Reply #1 –
Is the log from booting straight after installation? Have you tweaked anything? If not, please post the output of:
Code: [Select]
$ cat /etc/hostname
$ cat /etc/hosts
$ id
Several times lately I've encountered problems with the latest Xorg. Does lightdm start OK if you restart it? Try as root:
Code: [Select]
# s6-rc -d change lightdm
# s6-rc -u change lightdm

[EDIT] In a virtualbox test installation, I have to switch to a text console and back in order to see the login manager (Ctrl-Alt-F2 -> Alt-F7). Definitely a problem, probably  s6-related.

Re: Artix installation

Reply #2 –
Hi all, hi nous,
this seems the place to report, then:
I have tested a fresh install of this iso: artix-cinnamon-openrc-20201207-x86_64.iso
on a Dell Optiplex 780 PC (BIOS/MBR), and it went wonderfully well.
No problems with lightdm, cinnamon, gpg-keys for updating, all goes well. Congratulations.
It really looks like a very well polished and solid distro now.
Thank you and greetings, Andre

Re: Artix installation

Reply #3 –
Thanks for the reports. There seems to be a problem with s6 currently, which ironically stems from its booting too fast: my guess is udev hasn't properly initialized some subsystems and Xorg misbehaves.
We are (@Dudemanguy, that is) working on it.

Re: Artix installation

Reply #4 –
Quote from: nous – on
Is the log from booting straight after installation? Have you tweaked anything? If not, please post the output of:
Code: [Select]
$ cat /etc/hostname
$ cat /etc/hosts
$ id
Several times lately I've encountered problems with the latest Xorg. Does lightdm start OK if you restart it? Try as root:
Code: [Select]
# s6-rc -d change lightdm
# s6-rc -u change lightdm

[EDIT] In a virtualbox test installation, I have to switch to a text console and back in order to see the login manager (Ctrl-Alt-F2 -> Alt-F7). Definitely a problem, probably  s6-related.
Code: [Select]
Inspiron1545:[sukha]:/run/media/sukha/02-Artix.s-01213/etc$ cat hostname
Inspiron

Inspiron1545:[sukha]:/run/media/sukha/02-Artix.s-01213/etc$ cat hosts
# Host addresses
127.0.0.1  localhost
127.0.1.1  Inspiron
::1        localhost ip6-localhost ip6-loopback
ff02::1    ip6-allnodes
ff02::2    ip6-allrouters

When booting, tty7 was left with blank screen with a blinking cursor on top left corner, non-responsive.
Switched to tty2, login and issue
Code: [Select]
Inspiron: [sukha]:~$ sudo s6-rc -d change lightdm
We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things:

        #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.

[sudo] password for sukha:

typed in password and no more response.

This situation happens if /var folder is in on a separate partition.
Thank you.

The log was of the first boot attempt. No tweaking applied.

Re: Artix installation

Reply #5 –
OK, here are a few things I'd like you to try:

1. Disable lightdm from the startup services list of s6, reboot into console and start it manually. If this works, then we should debug s6. If it doesn't, GOTO 2.
2. This error from Xorg.0.log is the showstopper:
Code: [Select]
[    35.110] (EE) intel(0): [drm] failed to set drm interface version: Permission denied [13].
...
[    35.110] (EE) intel(0): Failed to claim DRM device.
[    35.110] (II) UnloadModule: "intel"
[    35.110] (EE) Screen(s) found, but none have a usable configuration.
If #1 fails, install xorg-xwrapper from [world] to make Xorg run as root, which shouldn't be needed if your user is a member of "video" group. Your /dev/dri/ should look like this:
Code: [Select]
 ls -l /dev/dri/card*
crw-rw----+ 1 root video 226, 0 Dec 13 22:46 /dev/dri/card0
crw-rw----+ 1 root video 226, 1 Dec 13 22:46 /dev/dri/card1

Re: Artix installation

Reply #6 –
Quote from: nous – on

[EDIT] In a virtualbox test installation, I have to switch to a text console and back in order to see the login manager (Ctrl-Alt-F2 -> Alt-F7). Definitely a problem, probably  s6-related.

Hmm, I tried it in virtualbox just a while ago and it worked normally.

Quote from: Pebble – on

This situation happens if /var folder is in on a separate partition.

Well that might be a clue. All s6 logging goes to /var/log of course. That being said, as long as your /var is mounted, every daemon should eventually start correctly.

Re: Artix installation

Reply #7 –
Code: [Select]
[quote author=nous link=msg=13913 date=1607977435]
OK, here are a few things I'd like you to try:

1. Disable lightdm from the startup services list of s6, reboot into console and start it manually. If this works, then we should debug s6. If it doesn't, GOTO 2.
[/quote]

On tty2:
Code: [Select]
$ sudo s6-rc-bundle-update delete default lightdm-log lightdm-srv
$ sudo reboot

Next boot on tty7:
Code: [Select]
$ sudo s6-rc -u change lightdm

Boot into xfce desktop successful.
Please let me know if there is something more to verify.
Thank you.

Re: Artix installation

Reply #8 –
Test installation report
iso: artix-xfce-s6-20201215-x86_64.iso
Code: [Select]
artix:[artix]:~$ pkexec env DISPLAY=:0 XAUTHORITY=/home/artix/.Xauthority QT_QPA_PLATFORMTHEME=gtk2 calamares
calamares: error while loading shared libraries: libboost_python39.so.1.74.0: cannot open shared object file: No such file or directory
artix:[artix]:~$ sudo find / -type f -name "libboost_python39.so.*"
/run/artix/sfs/livefs/usr/lib/libboost_python39.so.1.75.0
/usr/lib/libboost_python39.so.1.75.0
artix:[artix]:~$


will make a symlink and keep install.
After installation, boot stuck with blank screen. Not be able to switch to tty2 (in hope to see which partition was mounted, may will be too late by then).
Caps Lock and Num Lock cause the led to switch, assume keyboard works. Re inserted keyboard (wired usb), stopped working altogether.
Ctrl+Alt+Del no effect. Short pressed power button (Dell Inspiron1545), Artix recognized and powered down.

Re: Artix installation

Reply #9 –
Quote from: Pebble – on
Test installation report
iso: artix-xfce-s6-20201215-x86_64.iso
Code: [Select]
artix:[artix]:~$ pkexec env DISPLAY=:0 XAUTHORITY=/home/artix/.Xauthority QT_QPA_PLATFORMTHEME=gtk2 calamares
calamares: error while loading shared libraries: libboost_python39.so.1.74.0: cannot open shared object file: No such file or directory
artix:[artix]:~$ sudo find / -type f -name "libboost_python39.so.*"
/run/artix/sfs/livefs/usr/lib/libboost_python39.so.1.75.0
/usr/lib/libboost_python39.so.1.75.0
artix:[artix]:~$


will make a symlink and keep install.
thanks for report!
 

Re: Artix installation

Reply #10 –
                                                                   2020.12.17.22:06:34 UT

Artix iso test installation report:

artix-lxqt-s6-20201207-x86_64.iso: install successful, boot successful.
artix-lxqt-s6-20201211-x86_64.iso: install fail.
artix-lxqt-s6-20201215-x86_64.iso: install fail.
artix-lxqt-s6-20201216-x86_64.iso: install fail.

    My (small) problems with these ISO's are:

    1) s6-init not correctly starting sddm,
    2) CMST unable to set up interface to connman,
    3) calamares installer calling wrong python-lib in
        ISO's from this past week.

    Please go easy on me.  I'm a NOOB.

    My box is a 20AWS3MS00 ThinkPad T440p with Intel i5-4300M(x4) 3.3GHz CPU
and Intel HD4600 GPU.  I've been installing artix /-directory to a btrfs
partition on an MDM242 M.2 240 GBt SSD, and using a second ext4fs partition
on a Toshiba ATA 930 GBt HDD as /home.  The partition tables on my drives are
MSDOS type because I'm multi-booting several linux distro's, and this scheme is
much more straightforward than it would be were I to use GPT/UEFI.  My other
three distro's are Slackware-current, Debian-testing and Elementary Linux.

    I've been running Artix lxqt-s6 since February 2020, but this one began
to give me trouble in late November as it seems the s6-init is not dealing
with sddm appropriately.  I have little experience with s6, and my attempt
at squirming out of the trouble was to try re-installing with one of the
weekly ISO's.

    The lxqt-s6 ISO from 20201207 installed fine, and then booted OK and
started sddm, but the sddm would not log me in when I supplied my uname:psswd.
I pursued the path described in this thread by pebble, and issued commands
from the Ctl-Alt-F1 runlevel:

    root:> s6-rc-bundle-update delete default sddm sddm-log
    root:> reboot

    -----------------------

    root:> s6-rc -u change sddm

At this point the sddm/lxqt desktop started successfully, and so I have to
figure as per the post from nous that there is some minor problem with the
way in which s6-init tries to start sddm.  I've attached my /var/log/sddm.log.

Code: [Select]
[11:26:03.063] (II) DAEMON: Initializing...
[11:26:03.066] (II) DAEMON: Starting...
[11:26:03.066] (II) DAEMON: No session manager found
[11:26:03.067] (II) DAEMON: Adding new display on vt 7 ...
[11:26:03.067] (II) DAEMON: Loading theme configuration from ""
[11:26:03.067] (II) DAEMON: Display server starting...
[11:26:03.067] (II) DAEMON: Adding cookie to "/var/run/sddm/{e8be1884-e10c-48c8-a7fa-dec35c13cd13}"
[11:26:03.081] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{e8be1884-e10c-48c8-a7fa-dec35c13cd13} -background none -noreset -displayfd 17 -seat seat0 vt7
[11:26:03.828] (II) DAEMON: Setting default cursor
[11:26:03.829] (WW) DAEMON: Could not setup default cursor
[11:26:03.829] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[11:26:03.837] (II) DAEMON: Display server started.
[11:26:03.837] (II) DAEMON: Socket server starting...
[11:26:03.837] (II) DAEMON: Socket server started.
[11:26:03.837] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/artix/theme.conf"
[11:26:03.837] (II) DAEMON: Greeter starting...
[11:26:03.845] (II) HELPER: [PAM] Starting...
[11:26:03.845] (II) HELPER: [PAM] Authenticating...
[11:26:03.845] (II) HELPER: [PAM] returning.
[11:26:03.851] (II) DAEMON: Greeter session started successfully
[11:26:04.045] (II) DAEMON: Message received from greeter: Connect
[11:26:13.471] (II) DAEMON: Message received from greeter: Login
[11:26:13.471] (II) DAEMON: Reading from "/usr/share/xsessions/lxqt.desktop"
[11:26:13.471] (II) DAEMON: Reading from "/usr/share/xsessions/lxqt.desktop"
[11:26:13.471] (II) DAEMON: Session "/usr/share/xsessions/lxqt.desktop" selected, command: "startlxqt"
[11:26:13.483] (II) HELPER: [PAM] Starting...
[11:26:13.483] (II) HELPER: [PAM] Authenticating...
[11:26:13.487] (II) HELPER: [PAM] Preparing to converse...
[11:26:13.487] (II) HELPER: [PAM] Conversation with 1 messages
[11:26:13.495] (II) HELPER: [PAM] returning.
[11:26:13.496] (II) DAEMON: Authenticated successfully
[11:26:13.515] (II) HELPER: [PAM] Closing session
[11:26:13.516] (II) HELPER: [PAM] Ended.
[11:26:13.517] (II) DAEMON: Auth: sddm-helper exited successfully
[11:26:13.517] (II) DAEMON: Greeter stopped.
[11:26:13.534] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession \"startlxqt\""
[11:26:13.567] (II) HELPER: Adding cookie to "/home/gbarrick/.Xauthority"
[11:26:13.581] (II) DAEMON: Session started
[11:27:10.935] (WW) DAEMON: Signal received: SIGTERM
[11:27:10.936] (II) DAEMON: Socket server stopping...
[11:27:10.936] (II) DAEMON: Socket server stopped.
[11:27:10.936] (II) DAEMON: Display server stopping...
[11:27:10.938] (II) HELPER: [PAM] Closing session
[11:27:10.942] (II) HELPER: [PAM] Ended.
[11:27:11.321] (II) DAEMON: Display server stopped.
[11:27:11.321] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[11:27:11.322] (WW) DAEMON: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
[11:28:03.032] (II) DAEMON: Initializing...
[11:28:03.034] (II) DAEMON: Starting...
[11:28:03.035] (II) DAEMON: No session manager found
[11:28:03.035] (II) DAEMON: Adding new display on vt 7 ...
[11:28:03.035] (II) DAEMON: Loading theme configuration from ""
[11:28:03.035] (II) DAEMON: Display server starting...
[11:28:03.035] (II) DAEMON: Adding cookie to "/var/run/sddm/{b83e501c-7f6c-4a6f-8300-f417bd770f23}"
[11:28:03.048] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{b83e501c-7f6c-4a6f-8300-f417bd770f23} -background none -noreset -displayfd 17 -seat seat0 vt7
[11:28:03.677] (II) DAEMON: Setting default cursor
[11:28:03.679] (WW) DAEMON: Could not setup default cursor
[11:28:03.679] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[11:28:03.685] (II) DAEMON: Display server started.
[11:28:03.685] (II) DAEMON: Socket server starting...
[11:28:03.685] (II) DAEMON: Socket server started.
[11:28:03.686] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/artix/theme.conf"
[11:28:03.686] (II) DAEMON: Greeter starting...
[11:28:03.695] (II) HELPER: [PAM] Starting...
[11:28:03.695] (II) HELPER: [PAM] Authenticating...
[11:28:03.695] (II) HELPER: [PAM] returning.
[11:28:03.701] (II) DAEMON: Greeter session started successfully
[11:28:03.915] (II) DAEMON: Message received from greeter: Connect
[11:28:08.399] (II) DAEMON: Message received from greeter: Login
[11:28:08.400] (II) DAEMON: Reading from "/usr/share/xsessions/lxqt.desktop"
[11:28:08.400] (II) DAEMON: Reading from "/usr/share/xsessions/lxqt.desktop"
[11:28:08.400] (II) DAEMON: Session "/usr/share/xsessions/lxqt.desktop" selected, command: "startlxqt"
[11:28:08.411] (II) HELPER: [PAM] Starting...
[11:28:08.411] (II) HELPER: [PAM] Authenticating...
[11:28:08.415] (II) HELPER: [PAM] Preparing to converse...
[11:28:08.415] (II) HELPER: [PAM] Conversation with 1 messages
[11:28:08.421] (II) HELPER: [PAM] returning.
[11:28:08.421] (II) DAEMON: Authenticated successfully
[11:28:08.441] (II) HELPER: [PAM] Closing session
[11:28:08.443] (II) HELPER: [PAM] Ended.
[11:28:08.444] (II) DAEMON: Auth: sddm-helper exited successfully
[11:28:08.444] (II) DAEMON: Greeter stopped.
[11:28:08.460] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession \"startlxqt\""
[11:28:08.469] (II) HELPER: Adding cookie to "/home/gbarrick/.Xauthority"
[11:28:08.485] (II) DAEMON: Session started
[11:28:48.389] (II) HELPER: [PAM] Closing session
[11:28:48.392] (II) HELPER: [PAM] Ended.
[11:28:48.394] (II) DAEMON: Auth: sddm-helper exited successfully
[11:28:48.394] (II) DAEMON: Socket server stopping...
[11:28:48.394] (II) DAEMON: Socket server stopped.
[11:28:48.394] (II) DAEMON: Display server stopping...
[11:28:48.939] (II) DAEMON: Display server stopped.
[11:28:48.939] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[11:28:48.941] (II) DAEMON: Removing display ":0" ...
[11:28:48.941] (II) DAEMON: Adding new display on vt 7 ...
[11:28:48.941] (II) DAEMON: Loading theme configuration from ""
[11:28:48.941] (II) DAEMON: Display server starting...
[11:28:48.941] (II) DAEMON: Adding cookie to "/var/run/sddm/{c8a3c4d8-b8b7-463a-9e3b-a25827ab4ef7}"
[11:28:48.943] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{c8a3c4d8-b8b7-463a-9e3b-a25827ab4ef7} -background none -noreset -displayfd 18 -seat seat0 vt7
[11:28:49.472] (II) DAEMON: Setting default cursor
[11:28:49.473] (WW) DAEMON: Could not setup default cursor
[11:28:49.473] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[11:28:49.475] (II) DAEMON: Display server started.
[11:28:49.475] (II) DAEMON: Socket server starting...
[11:28:49.475] (II) DAEMON: Socket server started.
[11:28:49.475] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/artix/theme.conf"
[11:28:49.476] (II) DAEMON: Greeter starting...
[11:28:49.476] (WW) DAEMON: Signal received: SIGTERM
[11:28:49.476] (II) DAEMON: Socket server stopping...
[11:28:49.476] (II) DAEMON: Socket server stopped.
[11:28:49.476] (II) DAEMON: Display server stopping...
[11:28:49.484] (II) HELPER: [PAM] Starting...
[11:28:49.484] (II) HELPER: [PAM] Authenticating...
[11:28:49.484] (II) HELPER: [PAM] returning.
[11:28:50.039] (II) DAEMON: Display server stopped.
[11:28:50.039] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[11:28:50.041] (WW) DAEMON: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
[16:25:20.157] (II) DAEMON: Initializing...
[16:25:20.158] (II) DAEMON: Starting...
[16:25:20.159] (II) DAEMON: No session manager found
[16:25:20.159] (II) DAEMON: Adding new display on vt 7 ...
[16:25:20.159] (II) DAEMON: Loading theme configuration from ""
[16:25:20.159] (II) DAEMON: Display server starting...
[16:25:20.159] (II) DAEMON: Adding cookie to "/var/run/sddm/{c4e07191-b112-4a2b-8db2-5c133e415dee}"
[16:25:20.172] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{c4e07191-b112-4a2b-8db2-5c133e415dee} -background none -noreset -displayfd 17 -seat seat0 vt7
[16:25:20.947] (II) DAEMON: Setting default cursor
[16:25:20.948] (WW) DAEMON: Could not setup default cursor
[16:25:20.948] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[16:25:20.953] (II) DAEMON: Display server started.
[16:25:20.953] (II) DAEMON: Socket server starting...
[16:25:20.953] (II) DAEMON: Socket server started.
[16:25:20.953] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/artix/theme.conf"
[16:25:20.953] (II) DAEMON: Greeter starting...
[16:25:20.962] (II) HELPER: [PAM] Starting...
[16:25:20.962] (II) HELPER: [PAM] Authenticating...
[16:25:20.963] (II) HELPER: [PAM] returning.
[16:25:20.970] (II) DAEMON: Greeter session started successfully
[16:25:21.445] (II) DAEMON: Message received from greeter: Connect
[16:25:25.951] (II) DAEMON: Message received from greeter: Login
[16:25:25.952] (II) DAEMON: Reading from "/usr/share/xsessions/lxqt.desktop"
[16:25:25.952] (II) DAEMON: Reading from "/usr/share/xsessions/lxqt.desktop"
[16:25:25.952] (II) DAEMON: Session "/usr/share/xsessions/lxqt.desktop" selected, command: "startlxqt"
[16:25:25.963] (II) HELPER: [PAM] Starting...
[16:25:25.963] (II) HELPER: [PAM] Authenticating...
[16:25:25.967] (II) HELPER: [PAM] Preparing to converse...
[16:25:25.967] (II) HELPER: [PAM] Conversation with 1 messages
[16:25:25.974] (II) HELPER: [PAM] returning.
[16:25:25.974] (II) DAEMON: Authenticated successfully
[16:25:25.991] (II) HELPER: [PAM] Closing session
[16:25:25.992] (II) HELPER: [PAM] Ended.
[16:25:25.994] (II) DAEMON: Auth: sddm-helper exited successfully
[16:25:25.994] (II) DAEMON: Greeter stopped.
[16:25:26.007] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession \"startlxqt\""
[16:25:26.017] (II) HELPER: Adding cookie to "/home/gbarrick/.Xauthority"
[16:25:26.030] (II) DAEMON: Session started
[16:27:08.119] (II) HELPER: [PAM] Closing session
[16:27:08.123] (II) HELPER: [PAM] Ended.
[16:27:08.126] (II) DAEMON: Auth: sddm-helper exited successfully
[16:27:08.127] (II) DAEMON: Socket server stopping...
[16:27:08.127] (II) DAEMON: Socket server stopped.
[16:27:08.127] (II) DAEMON: Display server stopping...
[16:27:08.584] (II) DAEMON: Display server stopped.
[16:27:08.584] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[16:27:08.586] (II) DAEMON: Removing display ":0" ...
[16:27:08.586] (II) DAEMON: Adding new display on vt 7 ...
[16:27:08.586] (II) DAEMON: Loading theme configuration from ""
[16:27:08.586] (II) DAEMON: Display server starting...
[16:27:08.586] (II) DAEMON: Adding cookie to "/var/run/sddm/{08334d8e-a92d-45b4-99ae-742504ebc335}"
[16:27:08.589] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{08334d8e-a92d-45b4-99ae-742504ebc335} -background none -noreset -displayfd 18 -seat seat0 vt7
[16:27:09.234] (II) DAEMON: Setting default cursor
[16:27:09.235] (WW) DAEMON: Could not setup default cursor
[16:27:09.235] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[16:27:09.237] (II) DAEMON: Display server started.
[16:27:09.237] (II) DAEMON: Socket server starting...
[16:27:09.237] (II) DAEMON: Socket server started.
[16:27:09.237] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/artix/theme.conf"
[16:27:09.237] (II) DAEMON: Greeter starting...
[16:27:09.238] (WW) DAEMON: Signal received: SIGTERM
[16:27:09.238] (II) DAEMON: Socket server stopping...
[16:27:09.238] (II) DAEMON: Socket server stopped.
[16:27:09.238] (II) DAEMON: Display server stopping...
[16:27:09.245] (II) HELPER: [PAM] Starting...
[16:27:09.245] (II) HELPER: [PAM] Authenticating...
[16:27:09.245] (II) HELPER: [PAM] returning.
[16:27:09.717] (II) DAEMON: Display server stopped.
[16:27:09.717] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[16:27:09.722] (WW) DAEMON: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.

    I then logged-in to lxqt (on the 20201207 installation), and found that
the new system was having a problem communicating with the connman network
manager:

    CMST-Critical Error: Unable to create an interface to connman on the
          system bus.  CMST will not be able to communicate with connman.

I have not pursued this little problem further, but can supply readers with
log-files if you indicate which ones I should grab.

    Finally, I also found the error in the calamares installer mentioned by
pebble in the more recent (past week) ISO's:

    artix:[artix]:~$ pkexec env DISPLAY=:0 XAUTHORITY=/home/artix/.Xauthority \\
                         QT_QPA_PLATFORMTHEME=gtk2 calamares
                     calamares: error while loading shared libraries:         \\
                         libboost_python39.so.1.74.0: cannot open shared      \\
                         object file: No such file or directory

I tried creating a sym-link named "libboost_python39.so.1.74.0" that points to
the /usr/lib/libboost_python39.so.1.75.0, but this is (of course) a livefs system,
and so I'm not able to write new files either as user artix or user root.

    O.K.  There's my installation report.  Sorry about its length.  Again, go
easy on me.  I'm a NOOB.

gbarrick

Re: Artix installation

Reply #11 –
Quote from: gbarrick – on
artix-lxqt-s6-20201207-x86_64.iso: install successful, boot successful.
artix-lxqt-s6-20201211-x86_64.iso: install fail.
artix-lxqt-s6-20201215-x86_64.iso: install fail.
artix-lxqt-s6-20201216-x86_64.iso: install fail.
[....]
O.K.  There's my installation report.  Sorry about its length.  Again, go
easy on me.  I'm a NOOB.
We wish more "noobs" were so well-intending and helpful. That was an excellent report.
The calamares issue is minor, it'll only take a rebuild to link against the correct python lib. The s6 issue is trickier, it's got to do with s6 booting very fast (who could think that would ever be a problem). Our s6 guy is on it.

Re: Artix installation

Reply #12 –
From the sddm log:

Quote
[11:28:03.035] (II) DAEMON: No session manager found

I don't know how this could have happened. sddm depends on elogind and is a dependency. This message would indicate that elogind isn't running which could cause problems. The sddm-s6 package depends on elogind-s6 though.

Re: Artix installation

Reply #13 –
Quote from: nous – on
The s6 issue is trickier, it's got to do with s6 booting very fast (who could think that would ever be a problem). Our s6 guy is on it.
I also experienced problems related to s6 startup with login through the tty, without a display manager. If I login too soon, immediately after the login prompt pops up, sometimes I will get the message that the system can't chdir to ~ and the startx command (which I have in my .bashrc) fails. If I wait for the startup to finish before logging in, this issue won't manifest. If I recall correctly, there was already a discussion about s6 startup and I think services not waiting for others to finish loading being a deliberate decision, "as everyone will be using a display manager".

Re: Artix installation

Reply #14 –
Quote from: strajder – on
I also experienced problems related to s6 startup with login through the tty, without a display manager. If I login too soon, immediately after the login prompt pops up, sometimes I will get the message that the system can't chdir to ~ and the startx command (which I have in my .bashrc) fails. If I wait for the startup to finish before logging in, this issue won't manifest. If I recall correctly, there was already a discussion about s6 startup and I think services not waiting for others to finish loading being a deliberate decision, "as everyone will be using a display manager".

This is because s6 has an early getty that starts before the service-manager. If you login really fast (which was always possible), you can login before services start (which includes mounting drives). It doesn't have anything to do with display managers or not. The rule of thumb is to just wait until udev is done (the screen flickers).