Hey guys, I recently got a harddrive for my Toshiba laptop & tried to install Artix, but I ran into a familiar error.
https://artixlinux.org/forum/index.php?topic=155 <-- is related, I think.
The previous problem ended up being solved on my end by updating the /etc/pacman.d/mirrorlist & adding in the new mirrors & running a sudo pacman -Syyu, but it would seem that this is not working this time around... The computer I am trying to install Artix on is a Toshiba Satellite L850D - I have Artix installed on my L745D no problem though, only difference between the two is that L850D is UEFI & L745D isn't. for some reason the USB is recognized as /dev/sda & the HDD is recognized as /dev/sdb, but I'm gonna assume that shouldn't really make much of a difference... Right?
And when I try to do F2FS, if I open up gparted afterwards it'll show a EXT4 filesystem where the F2FS should've been.
This is the error when I choose EXT4:
Installation Failed
Boost.Python error in job "machineid".
<class 'subprocess.CalledProcessError'>
Command 'dbus-uuidgen --ensure' returned non-zero exit status 127.
Traceback:
File "/usr/lib/calamares/modules/machineid/main.py", line 64, in run
check_target_env_call(["dbus-uuidgen", "--ensure"])
File "<string>", line 2, in <module>
This is the error when I choose F2FS:
Installation Failed
The installer failed to create file system on partition /dev/sdb1
===================================================
Command: mkfs.f2fs /dev/sdb1
===================================================
F2FS-tools: mkfs.f2fs Ver: 1.9.0 (2017-09-21) Info: Disable heap-based policy info: Debug level = 0 info:
Label = Info: Trim is enabled /dev/sdb1 appears to contain an existing filesystem (ext4). Use the -f option to force overwrite.
And, when I try BTRFS, then I get this error:
Installation Failed
Boost.Python error in job "mount".
<class 'subprocess.CalledProcessError'>
Command '['btrfs', 'subvolume', 'create', '/tmp/calamares-root-wpn1btxe/@']'
returned non-zero exit status 1.
Traceback:
File "/usr/lib/calamares/modules/mount/main.py", line 132, in run
mount_partitions(root_mount_point, partitions)
File "/usr/lib/calamares/modules/mount/main.py", line 78, in mount_partitions
root_mount_point + '/@'])
File "/usr/lib/python3.6/subprocess.py" line 291, in check_call
raise CalledProcessError(retcode, cmd)
I'm trying to do an EFI installation on a computer that has no operating system. It does not have Windows on it.
I'm just supposed to make my partitions as normal & make a FAT32 /boot/efi partition, right? I think I'm doing this right.... Am I missing something? I'm going to attetmpt XFS, JFS & Reiser to see what happens, as some of the error messages are different.
For XFS:
Installation Failed
Boost.Python error in job "machineid".
<class 'subprocess.CalledProcessError'>
Command 'dbus-uuidgen --ensure' returned non-zero exit status 127.
Traceback:
File "/usr/lib/calamares/modules/machineid/main.py", line 64, in run
check_target_env_call(["dbus-uuidgen", "--ensure"])
File "<string>", line 2, in <module>
for JFS:
Boost.Python error in job "machineid".
<class 'subprocess.CalledProcessError'>
Command 'dbus-uuidgen --ensure' returned non-zero exit status 127.
Traceback:
File "/usr/lib/calamares/modules/machineid/main.py", line 64, in run
check_target_env_call(["dbus-uuidgen", "--ensure"])
File "<string>", line 2, in <module>
and,
For ReiserFS its the exact same as those ^
Its probably that there is relevant information in the lines previous to the log that you are pasting, can you upload the whole log?
I don't know what you mean by "the whole log", these are just the errors that pop up...
I don't know if this is what you're looking for, but here.
sudo calamares
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
13:57:31 [1]: Calamares version: 3.1.8rc1.20171101-git-makepkg-783b0dc
Translation: Calamares: Using system locale: "en_US"
13:57:32 [1]: Default font =====
Pixel size: -1
Point size: 9
Point sizeF: 9
Font family: "Sans Serif"
Metric height: 15
13:57:32 [1]: Font height: 15
13:57:32 [1]: Available languages: ("ar", "ast", "bg", "ca", "cs_CZ", "da", "de",
"el", "en", "en_GB", "es_MX", "es", "eu", "fr", "he", "hi", "hr", "hu", "id",
"is", "it_IT", "ja", "lt", "mr", "nl", "pl", "pt_BR", "pt_PT", "ro", "ru", "sk",
"sv", "th", "tr_TR", "zh_CN", "zh_TW")
13:57:32 [1]: CalamaresApplication thread: 0x55c36b83ad10
13:57:32 [1]: Using log file: "/root/.cache/Calamares/Calamares/Calamares.log"
13:57:32 [1]: Using Calamares settings file at "/etc/calamares/settings.conf"
13:57:32 [1]: Using Calamares branding file at
"/usr/share/calamares/branding/artix/branding.desc"
13:57:32 [1]: WARNING: the selected branding component does not ship translations.
13:57:32 [1]: Loaded branding component "artix"
13:57:32 [1]: STARTUP: initQmlPath, initSettings, initBranding done
13:57:32 [1]: STARTUP: initModuleManager: module init started
13:57:32 [1]: STARTUP: initModuleManager: all modules init done
13:57:32 [1]: STARTUP: initJobQueue done
13:57:32 [1]: Available size QSize(1366, 736)
13:57:32 [1]: Proposed window size: 1024 540
13:57:32 [1]: STARTUP: CalamaresWindow created; loadModules started
13:57:32 [1]: Initial locale "en_US"
13:57:32 [1]: Welcome string false "Artix Linux \"rolling\""
13:57:32 [1]: ViewModule "welcome@welcome" loading complete.
13:57:32 [1]: WARNING: guessLocaleConfiguration can't guess from an empty list.
13:57:32 [1]: ViewModule "locale@locale" loading complete.
13:57:32 [1]: WARNING: ckbcomp not found , keyboard preview disabled
13:57:32 [1]: WARNING: ckbcomp not found , keyboard preview disabled
13:57:32 [1]: ViewModule "keyboard@keyboard" loading complete.
13:57:32 [1]: ViewModule "partition@partition" loading complete.
13:57:32 [1]: ViewModule "users@users" loading complete.
13:57:33 [1]: ViewModule "netinstall@netinstall" loading complete.
13:57:33 [1]: ViewModule "summary@summary" loading complete.
13:57:33 [1]: Module "partition@partition" already loaded.
13:57:33 [1]: QML import paths: ("/usr/share/calamares/qml", "/usr/bin",
"qrc:/qt-project.org/imports", "/usr/lib/qt/qml")
13:57:33 [1]: Module "locale@locale" already loaded.
13:57:33 [1]: Module "keyboard@keyboard" already loaded.
13:57:33 [1]: Module "users@users" already loaded.
13:57:33 [1]: FinishedPage()
13:57:33 [1]: ViewModule "finished@finished" loading complete.
13:57:33 [1]: STARTUP: loadModules for all modules done
13:57:33 [1]: STARTUP: Window now visible and ProgressTreeView populated
13:57:33 [1]: Need at least storage bytes: 8482560409
13:57:34 [1]: Need at least ram bytes: 1073741824
13:57:34 [1]: A battery exists, checking for mains power.
13:57:34 [1]: RequirementsChecker output: enoughStorage: true enoughRam: true
hasPower: true hasInternet: true isRoot: true
13:57:34 [1]: xkbmap selection changed to: "us" - ""
13:57:35 [1]: WARNING: guessLocaleConfiguration can't guess from an empty list.
13:57:35 [1]: WARNING: guessLocaleConfiguration can't guess from an empty list.
13:57:35 [1]: WARNING: guessLocaleConfiguration can't guess from an empty list.
13:57:35 [1]: WARNING: guessLocaleConfiguration can't guess from an empty list.
13:57:35 [1]: Removing unsuitable devices: 2 candidates.
13:57:35 [1]: .. Removing device with iso9660 filesystem (probably a CD) on it
"/dev/sda"
13:57:35 [1]: LIST OF DETECTED DEVICES:
13:57:35 [1]: node capacity name prettyName
13:57:35 [1]: "/dev/sdb" 160039272960 "ATA WDC WD1600BEVT-7" "ATA WDC WD1600BEVT-7
– 149.05 GiB (/dev/sdb)"
13:57:35 [1]: .. 1 devices detected.
13:57:36 [1]: "Osprober lines, clean:\n"
13:57:36 [1]: Found EFI system partition at "/dev/sdb3"
13:57:36 [1]: Updating partitioning state widgets.
13:57:36 [0]: QObject::setParent: Cannot set parent, new parent is in a different
thread
13:57:36 [1]: Required storage B: 11166914969 "(10.4GB)"
13:57:36 [1]: Available storage B: 141167672320 "(131GB)" for "/dev/sdb1"
length: 275718110 sectorsUsed: 0 fsType: "reiser"
13:57:36 [1]: Partition "/dev/sdb1" authorized for resize + autopartition install.
13:57:36 [1]: Required storage B: 9019431321 "(8GB)"
13:57:36 [1]: Storage capacity B: 141167672320 "(131GB)" for "/dev/sdb1"
length: 275718110
13:57:36 [1]: Partition "/dev/sdb1" authorized for replace install.
13:57:36 [1]: Required storage B: 11166914969 "(10.4GB)"
13:57:36 [1]: Available storage B: 420285952 "(0GB)" for "/dev/sdb3" length:
820879 sectorsUsed: 8 fsType: "fat32"
13:57:36 [1]: Required storage B: 9019431321 "(8GB)"
13:57:36 [1]: Storage capacity B: 420290048 "(0GB)" for "/dev/sdb3" length:
820879
13:57:36 [1]: Updating partitioning preview widgets.
13:57:57 [1]: Updating partitioning preview widgets.
13:57:59 [1]: Choice applied: 4
13:58:02 [1]: WARNING: system is EFI but no EFI system partitions found.
13:58:04 [1]: WARNING: system is EFI but no EFI system partitions found.
13:58:06 [1]: WARNING: system is EFI but no EFI system partitions found.
13:58:28 [1]: WARNING: system is EFI but no EFI system partitions found.
13:58:28 [0]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2123, resource
id: 8389701, major code: 40 (TranslateCoords), minor code: 0
13:58:37 [1]: WARNING: system is EFI but no EFI system partitions found.
13:58:49 [1]: WARNING: system is EFI but no EFI system partitions found.
13:59:06 [1]: WARNING: system is EFI but no EFI system partitions found.
13:59:33 [1]: Found EFI system partition at ""
14:00:06 [1]: Leaving netinstall, adding packages to be installed to global
storage
14:00:06 [1]: Processing 136 packages from netinstall.
14:00:06 [1]: .. 136 non-critical packages.
14:00:06 [0]: QLayout: Attempting to add QLayout "" to QWidget "", which already
has a layout
14:00:06 [0]: QObject::setParent: Cannot set parent, new parent is in a different
thread
14:00:06 [1]: Creating FillGlobalStorageJob with bootLoader path ""
14:00:06 [1]: PartitionCodeModule has been asked for jobs. About to return: "Clear
all temporary mounts.\nClear mounts for partitioning operations on
/dev/sdb\nDelete partition /dev/sdb3.\nDelete partition /dev/sdb2.\nDelete
partition /dev/sdb1.\nCreate new 134627MB partition on /dev/sdb (ATA WDC
WD1600BEVT-7) with file system btrfs.\nCreate new 17799MB partition on /dev/sdb
(ATA WDC WD1600BEVT-7) with file system linuxswap.\nCreate new 200MB partition on
/dev/sdb (ATA WDC WD1600BEVT-7) with file system fat32.\nSet flags on 200MB fat32
partition.\nSet partition information"
14:00:06 [1]: Gathering UUIDs for partitions that exist now.
14:00:06 [1]: QHash(("", ""))
14:00:06 [1]: Writing to GlobalStorage["partitions"]
14:00:06 [1]: "" mtpoint: "/" fs: QVariant(QString, "btrfs") ( QVariant(QString,
"btrfs") ) ""
14:00:06 [1]: "" mtpoint: "" fs: QVariant(QString, "linuxswap") (
QVariant(QString, "linuxswap") ) ""
14:00:06 [1]: "" mtpoint: "/boot/efi" fs: QVariant(QString, "fat32") (
QVariant(QString, "fat32") ) ""
14:00:06 [1]: Gathering UUIDs for partitions that exist now.
14:00:06 [1]: QHash(("", ""))
14:00:06 [1]: Writing to GlobalStorage["partitions"]
14:00:06 [1]: "" mtpoint: "/" fs: QVariant(QString, "btrfs") ( QVariant(QString,
"btrfs") ) ""
14:00:06 [1]: "" mtpoint: "" fs: QVariant(QString, "linuxswap") (
QVariant(QString, "linuxswap") ) ""
14:00:06 [1]: "" mtpoint: "/boot/efi" fs: QVariant(QString, "fat32") (
QVariant(QString, "fat32") ) ""
14:00:06 [1]: Summary widget is larger than viewport, enlarge by 96 to QSize(826,
589)
14:00:07 [0]: file:///usr/share/calamares/branding/artix/show.qml:50:
ReferenceError: root is not defined
14:00:08 [1]: Creating FillGlobalStorageJob with bootLoader path ""
14:00:08 [1]: PartitionCodeModule has been asked for jobs. About to return: "Clear
all temporary mounts.\nClear mounts for partitioning operations on
/dev/sdb\nDelete partition /dev/sdb3.\nDelete partition /dev/sdb2.\nDelete
partition /dev/sdb1.\nCreate new 134627MB partition on /dev/sdb (ATA WDC
WD1600BEVT-7) with file system btrfs.\nCreate new 17799MB partition on /dev/sdb
(ATA WDC WD1600BEVT-7) with file system linuxswap.\nCreate new 200MB partition on
/dev/sdb (ATA WDC WD1600BEVT-7) with file system fat32.\nSet flags on 200MB fat32
partition.\nSet partition information"
14:00:08 [0]: Starting job "Clear all temporary mounts."
14:00:08 [1]: Opened mtab. Lines:
14:00:08 [1]: "proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0"
14:00:08 [1]: "sys /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0"
14:00:08 [1]: "dev /dev devtmpfs
rw,nosuid,relatime,size=10240k,nr_inodes=1980604,mode=755 0 0"
14:00:08 [1]: "run /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0"
14:00:08 [1]: "efivarfs /sys/firmware/efi/efivars efivarfs
rw,nosuid,nodev,noexec,relatime 0 0"
14:00:08 [1]: "/dev/sda1 /run/artix/bootmnt iso9660 ro,relatime 0 0"
14:00:08 [1]: "cowspace /run/artix/cowspace tmpfs
rw,relatime,size=262144k,mode=755 0 0"
14:00:08 [1]: "overlay_root /run/artix/overlay_root tmpfs
rw,relatime,size=11914068k,mode=755 0 0"
14:00:08 [1]: "/dev/loop0 /run/artix/sfs/livefs squashfs ro,relatime 0 0"
14:00:08 [1]: "/dev/loop1 /run/artix/sfs/desktopfs squashfs ro,relatime 0 0"
14:00:08 [1]: "/dev/loop2 /run/artix/sfs/rootfs squashfs ro,relatime 0 0"
14:00:08 [1]: "overlay / overlay
rw,relatime,lowerdir=/run/artix/sfs/livefs:/run/artix/sfs/desktopfs:/run/artix/sfs/rootfs,upperdir=/run/artix/overlay_root/upper,workdir=/run/artix/overlay_root/work
0 0"
14:00:08 [1]: "mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0"
14:00:08 [1]: "devpts /dev/pts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0"
14:00:08 [1]: "shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime 0 0"
14:00:08 [1]: "securityfs /sys/kernel/security securityfs
rw,nosuid,nodev,noexec,relatime 0 0"
14:00:08 [1]: "debugfs /sys/kernel/debug debugfs rw,nosuid,nodev,noexec,relatime 0
0"
14:00:08 [1]: "configfs /sys/kernel/config configfs
rw,nosuid,nodev,noexec,relatime 0 0"
14:00:08 [1]: "pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0"
14:00:08 [1]: "cgroup_root /sys/fs/cgroup tmpfs
rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755 0 0"
14:00:08 [1]: "openrc /sys/fs/cgroup/openrc cgroup
rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/openrc/sh/cgroup-release-agent.sh,name=openrc
0 0"
14:00:08 [1]: "none /sys/fs/cgroup/unified cgroup2 rw,nosuid,nodev,noexec,relatime
0 0"
14:00:08 [1]: "cpuset /sys/fs/cgroup/cpuset cgroup
rw,nosuid,nodev,noexec,relatime,cpuset 0 0"
14:00:08 [1]: "cpu /sys/fs/cgroup/cpu cgroup rw,nosuid,nodev,noexec,relatime,cpu 0
0"
14:00:08 [1]: "cpuacct /sys/fs/cgroup/cpuacct cgroup
rw,nosuid,nodev,noexec,relatime,cpuacct 0 0"
14:00:08 [1]: "blkio /sys/fs/cgroup/blkio cgroup
rw,nosuid,nodev,noexec,relatime,blkio 0 0"
14:00:08 [1]: "memory /sys/fs/cgroup/memory cgroup
rw,nosuid,nodev,noexec,relatime,memory 0 0"
14:00:08 [1]: "devices /sys/fs/cgroup/devices cgroup
rw,nosuid,nodev,noexec,relatime,devices 0 0"
14:00:08 [1]: "freezer /sys/fs/cgroup/freezer cgroup
rw,nosuid,nodev,noexec,relatime,freezer 0 0"
14:00:08 [1]: "net_cls /sys/fs/cgroup/net_cls cgroup
rw,nosuid,nodev,noexec,relatime,net_cls 0 0"
14:00:08 [1]: "net_prio /sys/fs/cgroup/net_prio cgroup
rw,nosuid,nodev,noexec,relatime,net_prio 0 0"
14:00:08 [1]: "pids /sys/fs/cgroup/pids cgroup
rw,nosuid,nodev,noexec,relatime,pids 0 0"
14:00:08 [1]: "binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc
rw,nosuid,nodev,noexec,relatime 0 0"
14:00:08 [1]: "tmpfs /etc/pacman.d/gnupg tmpfs rw,relatime,size=10240k,mode=755 0
0"
14:00:08 [1]: "tmpfs /run/user/1002 tmpfs
rw,nosuid,nodev,relatime,size=1588540k,mode=700,uid=1002,gid=1002 0 0"
14:00:08 [1]: ClearTempMountsJob finished. Here's what was done:
""
14:00:08 [0]: Starting job "Clear mounts for partitioning operations on /dev/sdb"
14:00:08 [1]: ClearMountsJob finished. Here's what was done:
"Successfully disabled swap /dev/sdb2."
14:00:08 [0]: Starting job "Delete partition /dev/sdb3."
14:00:09 [0]: Starting job "Delete partition /dev/sdb2."
14:00:09 [0]: Starting job "Delete partition /dev/sdb1."
14:00:09 [0]: Starting job "Create new 134627MB partition on /dev/sdb (ATA WDC
WD1600BEVT-7) with file system btrfs."
14:00:10 [0]: Starting job "Create new 17799MB partition on /dev/sdb (ATA WDC
WD1600BEVT-7) with file system linuxswap."
14:00:10 [0]: Starting job "Create new 200MB partition on /dev/sdb (ATA WDC
WD1600BEVT-7) with file system fat32."
14:00:12 [0]: Starting job "Set flags on partition /dev/sdb3."
14:00:12 [0]: Starting job "Set partition information"
14:00:12 [1]: Gathering UUIDs for partitions that exist now.
14:00:13 [1]: QHash(("/dev/sdb2",
"74591ad8-818d-404d-acfc-3e6dd1ff228d")("/dev/sdb3", "96B0-441E")("/dev/sdb1",
"5a232de7-9801-4510-903e-ff105f579112"))
14:00:13 [1]: Writing to GlobalStorage["partitions"]
14:00:13 [1]: "/dev/sdb1" mtpoint: "/" fs: QVariant(QString, "btrfs") (
QVariant(QString, "btrfs") ) "5a232de7-9801-4510-903e-ff105f579112"
14:00:13 [1]: "/dev/sdb2" mtpoint: "" fs: QVariant(QString, "linuxswap") (
QVariant(QString, "linuxswap") ) "74591ad8-818d-404d-acfc-3e6dd1ff228d"
14:00:13 [1]: "/dev/sdb3" mtpoint: "/boot/efi" fs: QVariant(QString, "fat32") (
QVariant(QString, "fat32") ) "96B0-441E"
14:00:13 [1]: FillGlobalStorageJob writing empty bootLoader value
14:00:13 [0]: Starting job "mount"
14:00:13 [1]: Job file "/usr/lib/calamares/modules/mount/main.py"
14:00:13 [1]: Job "mount" (doc) -> "Define mountpoints."
mount: /tmp/calamares-root-i3tjndf4: unknown filesystem type 'btrfs'.
ERROR: not a btrfs filesystem: /tmp/calamares-root-i3tjndf4
14:00:13 [1]: tbMsg " File "/usr/lib/calamares/modules/mount/main.py",
line 132, in run\n mount_partitions(root_mount_point, partitions)\n\n File
"/usr/lib/calamares/modules/mount/main.py", line 78, in
mount_partitions\n root_mount_point + '/@'])\n\n File
"/usr/lib/python3.6/subprocess.py", line 291, in check_call\n raise
CalledProcessError(retcode, cmd)\n"
14:00:13 [0]: Installation failed:
14:00:13 [0]: - message: "Boost.Python error in job \"mount\"."
14:00:13 [0]: - details: "<div><strong><class
'subprocess.CalledProcessError'></strong></div><div>Command '['btrfs',
'subvolume', 'create', '/tmp/calamares-root-i3tjndf4/@']' returned non-zero exit
status 1.</div><div>Traceback:</div><div><pre> File
"/usr/lib/calamares/modules/mount/main.py", line 132, in run\n
mount_partitions(root_mount_point, partitions)\n\n File
"/usr/lib/calamares/modules/mount/main.py", line 78, in
mount_partitions\n root_mount_point + '/@'])\n\n File
"/usr/lib/python3.6/subprocess.py", line 291, in check_call\n raise
CalledProcessError(retcode, cmd)\n</pre></div>"
14:00:13 [0]: Calamares will quit when the dialog closes.
14:00:13 [1]: FinishedPage::setUpRestart()
[Edited by an admin: code blocks]
[Sorry, I'm still really new to using forums, I tried to figure that out but couldn't do it right & was in a rush]
Hello,
I can confirm this error:
Installation Failed
Boost.Python error in job "machineid".
<class 'subprocess.CalledProcessError'>
Command 'dbus-uuidgen --ensure' returned non-zero exit status 127.
Traceback:
File "/usr/lib/calamares/modules/machineid/main.py", line 64, in run
check_target_env_call(["dbus-uuidgen", "--ensure"])
File "<string>", line 2, in <module>
I've tried to install from a Stick with current lxqt iso
1) I've select whole ssd for installation with automatic partitioning and get this error
2) I've select whole ssd and do a manual partitioning with GPT, bios_grub, ext4 and swap and get this error
I'll try it with another stick amd will give further feedback.
Kind regards,
Holger
Sorry, but also with another USB-Stick no success, same error.
Hmm, is there a possibility to install artix without calamares?
Please try to do with the installation again. The issue was more likely coming from this and should have been fixed by now...
Ok, I'll attempt it again, thanks.
After numerous unsuccessful attempts to install I gave up and tried instead to convert my Manjaro OpenRc partition to Artix .
Everything seemed to work except I was unable to install Artix keyring due to Criss Crommer's signature error.
What is the fix for that?
I can download and installed from the mirror just fine :
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
artix-keyring-20170805-1-any 30.4 KiB 85.0K/s 00:00 [------------------------------------------------------------] 100%
(1/1) checking keys in keyring [------------------------------------------------------------] 100%
(1/1) checking package integrity [------------------------------------------------------------] 100%
(1/1) loading package files [------------------------------------------------------------] 100%
(1/1) checking for file conflicts [------------------------------------------------------------] 100%
(1/1) checking available disk space [------------------------------------------------------------] 100%
:: Processing package changes...
(1/1) reinstalling artix-keyring [------------------------------------------------------------] 100%
==> Appending keys from artix.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signing key 8AC1470E584E6AAB0BBBAC3FED587B6247A4152D...
-> Locally signing key 2C69BCE8163847BC56401FD2CF18A351C0705F6A...
-> Locally signing key 664187F32A958D0ED06530067BFAD0C0864DA8E8...
-> Locally signing key 80E461C30BE40AD3EFB57E18EA690BC73A4F1094...
==> Importing owner trust values...
==> Updating trust database...
gpg: next trustdb check due at 2018-06-01
Can you at least give the full output of pacman failed command here. Is it invalid error or marginal error?
This is what I get:
error: could not register 'extra' database (database already registered)
error: could not register 'community' database (database already registered)
resolving dependencies...
looking for conflicting packages...
Packages (1) artix-keyring-20170805-1
Total Download Size: 0.03 MiB
Total Installed Size: 0.06 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
artix-keyring-20170... 30.4 KiB 253K/s 00:00 [######################] 100%
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
error: artix-keyring: signature from "Chris Cromer <chris@cromer.cl>" is unknown trust
:: File /var/cache/pacman/pkg/artix-keyring-20170805-1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
Its still not working... Not sure why, seems I can't install Artix on this laptop... exact same errors.
@7of9 @kenny_w Please enable
world-testing in your
/etc/pacman.conf before doing installations again..
Now I am getting this when installing keyring
pacman -S artix-keyring
:: Some packages should be upgraded first...
resolving dependencies...
looking for conflicting packages...
Packages (1) archlinux-keyring-20171020-1
Total Download Size: 0.60 MiB
Total Installed Size: 0.86 MiB
Net Upgrade Size: -0.03 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
archlinux-keyring-2... 619.4 KiB 474K/s 00:01 [######################] 100%
(1/1) checking keys in keyring [######################] 100%
downloading required keys...
error: key "1247D995F165BBAC" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
resolving dependencies...
looking for conflicting packages...
Packages (1) artix-keyring-20170805-1
Total Download Size: 0.03 MiB
Total Installed Size: 0.06 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
artix-keyring-20170... 30.4 KiB 212K/s 00:00 [######################] 100%
(1/1) checking keys in keyring [######################] 100%
downloading required keys...
error: key "FA91071797BEEEC2" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
[EDIT: code tags]
Toshiba laptops sometimes have a lock down of the file system and can be funky. Years ago, they were the subject of the windows refund movement due to this. I don't know if it is still the case. (https://www.theinquirer.net/inquirer/news/1045348/toshiba-court-windows-refund-ginger ). I never use Toshibas because of this and this error with the FS sounds familiar from way back.
Sure! Let's blame computer manufacturers for complete failure of this project thus far. Devs have no answers as they don't have a clue of what they are doing. Too bad that this project ended up in wrong hands.
Why are you here then?
Why don' t you tell us where there is a better chance to use Arch without systemd.
Do you know exactly how and why ms together with a few other hw/sw industrialists developed uefi to lock low budget OS out of the access of the average user?
Who said that because this forum exists developers will come here and solve peoples' problems? If you read such thing in your customer contract let me know. It sounds very interesting.
I can only verify that I have gotten my money's worth of customer support and then some.
I never use UEFI, have dual bios systam. And I never will if I have a choice. I really regret having to be rude, but this project is hopeless at the moment. Tried installing at least 50 times, succeeded only once. And there is no help here. Only denial that there is anything wrong.
1st you seem to have constipation giving any usable information how do you expect any help?
1st check if their is a pacman.conf pac new if their is compare them. also check the artix mirror lisr list remove any sourceforge entries completely
Did you refresh the keyring.
sudo pacman -Sy archlinux-keyring
sudo pacman-key --populate archlinux
sudo pacman-key --refresh-keys
If then you still have a problem open /etc/pacman.conf SigLevel = Required DatabaseOptional look for this line edit it to look like this.
#SigLevel = Required DatabaseOptional edit it like this save try again don't forget to alter it back after you have done then ask the correct question some thing like "corrupt sig trying to update with pacman"
Or admit you do not have a clue what the F you are doing. and shout like a 5yr old does not work on adult forum frustration we take in our stride.
Seeing its the same installer by the same dev as Manjaro get it.
oh fuck off. Nobody owes you shit.
when did you become kennyw. Why don't you start your own thread if your having trouble instead of interjecting into this one.
He is having same, identical issue, you idiot!
No he is not. Your just trolling and piling on. You are nothing more than a troll. You entered into this thread and then disrupted it with your total bullshit. No one owes you shit. If you don't like artix, then use something else. But don't enter someone elses attempt to get some community help and disrupt and hijack the thread. Do something more useful like poke your eyes out with chop sticks. I hate when pricks like you enter forums under anonymous psunamons and then piss all over everyone.
This was your penultimate such post. Next one will be your last. No need to explain why.
Why don't you treat the other idiot the same, the one above who first used "oh fuck off. Nobody owes you shit. "
anyway fuck you too!
Really dude? It looks like to me you could fix it by adding the signature manually with gpg or maybe refresh/repopulate the keys. Possibly a little annoying but hardly anything to throw a tantrum on the forum about. Personally, I'm quite grateful that some devs have stepped up to provide Arch without systemd. It's unfortunately not as simple as just building a few packages yourself. systemd has infected a huge amount of software and you pretty much need a team of people to follow upstream to make sure nothing new breaks. Artix is obviously more of a "hobbyist" distro which means you might get some breakage and bugs from time to time. It's just the nature of the beast.
Because that was his first time, you're a repeat offender.
We don't want or need such users, please move elsewhere.
Alrighty, I've enabled world-testing & ran sudo pacman -Syyu , I am now going to try running Calamares....
Aaand I'm getting the same error :(
Edit: I'm getting an identical error while trying to install it in non-UEFI mode. identical error below every time I attempt to install with BTRFS, similar error for EXT4 too.
Boost.Python error in job "mount".
<class 'subprocess.CalledProcessError'>
Command '['btrfs', 'subvolume', 'create', '/tmp/calamares-root-wpn1btxe/@']'
returned non-zero exit status 1.
Traceback:
File "/usr/lib/calamares/modules/mount/main.py", line 132, in run
mount_partitions(root_mount_point, partitions)
File "/usr/lib/calamares/modules/mount/main.py", line 78, in mount_partitions
root_mount_point + '/@'])
File "/usr/lib/python3.6/subprocess.py" line 291, in check_call
raise CalledProcessError(retcode, cmd)
Well I managed to install Artix onto my non-UEFI Toshiba L745D, but I can't make it install on the UEFI L850D..
Although I still believe I should be able to get Artix working, but perhaps for now I'll go with Debian x64, or maybe give Fedora 27 a shot when it comes out.
Also, where did the drama come from? :(
7of9 these guys have helped me big time in getting Artix Linux to run on multiple computers & continue to help me with all my problems, just have patience... I don't think they're blaming it on the hardware alone, but I think its definitely relevant for mrbrklyn to bring up... I am going to attempt another installation of Artix in BIOS mode I suppose, but I did get Artix to work on my desktop which is UEFI, so...
Edit: I tried to install it in BIOS mode but it gave me the exact same error as posted above, that's not good... I have tried enabling world-testing & doing a sudo pacman -Syyu & then also trying to repopulate the key things as Mandog suggested, but still I am getting an identical error.
Artix Linux team are nice people, I'm not going to tell you what to do or anything, but you are probably better off apologising & being polite, I don't think anyone here is saying "oh well its your hardware & we're not going to help you".. Please, lets keep this thread civil, I know its really frustrating trying to install Artix Linux just for it to fail & then your harddrive is wiped & you have to re-install your last OS, I know it sucks, but we have to try to be civil if we're going to work out all of these kinks in the system.
Artix is a new project still, of course there are going to be lots of kinks that need to be worked out! Rome wasn't built in a day, neither was any Linux distribution.
I figure if you're going to use a new OS you should expect bugs here and there, but over-all Artix Linux is awesome once you get past the installer!!
When I enable world-testing before updating world, I get this:
https://pastebin.com/4Df8PreH
I am currently trying to install it with just [world] & if it fails again I'll enable [world-testing] & see what happens.
The error is seen as packages not found.
After adding world-testing did you run "sudo pacman -Syy" to populate the new repo to the database?
Also please post your /etc/pacman.conf to make sure you have amended it correctly.
Yes I did that, I did sudo pacman -Syyu too to make sure the packages all upgraded just to see if that makes a difference
I did the pacman-key --repopulate commands too.
https://pastebin.com/mHd5TY0s
and here is the pacman.conf file
https://pastebin.com/g72S8iEv
Don't delete the [world] repo. When I said `enable [world-testing]` just create the [world-testing] repo above [world]. Testing repo aren't behave like manjaro as in stable, testing, and unstable. They behave like arch whos packages are purged in testing (meaning not exist anymore) upon pushed into stable. So you must enable [world-testing] alongside [world] (applies to
@dbvu0 as well )
[world-testing]
Include = /etc/pacman.d/mirrorlist
[world]
Include = /etc/pacman.d/mirrorlist
Ohhh, ok. I've never changed repositories on Manjaro or Arch Linux. I only ever used Arch for a short time before deciding to switch to Manjaro, then to Artix. Thank you thefallenrat, I will attempt this again... Now I'm getting the same error on different lines, making a pastebin right now.
https://pastebin.com/LqWT412y
I really hope with the next ISO you guys make that it will work better than this... I feel like these kinds of issues really hurt the Artix user-base because many people just give up on trying to solve errors like this.
I think I'm gonna try to install Arch OpenRC then convert it to Artix, wish me luck lol.
how do you set up your partitions?
Please try to do it simple
I make a UEFI FAT32 drive /boot/efi, a / drive, and a SWAP. I was able to install Artix alongside Win10 on my UEFI desktop no problem by doing it like this, minus making a /boot/efi drive because one already existed, so it just had to be mounted at /boot/efi.
I've got Manjaro running on it - I'm currently SSH'ed into it working on converting it from Manjaro to Artix... And the error 7of9 was getting about the corrupted package, I got that but I was able to solve it fairly easy by downloading the package off of sourceforge in Artix's repos.. one google search
https://cytranet.dl.sourceforge.net/project/artix-linux/repos/system/os/x86_64/artix-keyring-20170805-1-any.pkg.tar.xz
Edit: Second try now & I've ended up with a kernel panic upon reboot, looks like I can't go from Manjaro OpenRC to Artix...
Any other possible solutions to make Artix install?
Have you tried doing acli (https://artixlinux.org/forum/index.php?topic=41.0) install? That guide might be a little dated, but it shouldn't be too different. With all the issues with the Calamares installer, I feel like Artix devs should recommend/encourage installing via cli. I mean this is an Arch fork; it's not like we're trying to be user friendly or anything.
The sad part is that it was advertised as a Manjaro-OpenRc-xfce continuation, not fork.
So this arch-user-friendly culture may be totally unknown to some of us.
Manjaro may be a user-friendly arch-fork, but that is all it was.
Look this getting totally off topic
But for your information Manjaro OpenRC was never a supported project, I was a community spin and the brain child of artoo and auditita never can get the name right, nothing more artoo did virtualy everything on the project by himself.
The net installer is the same one that artoo worked for Manjaro, Artix is not a Manjaro fork its Arch Linux openRC or Arch without systemd.
artoo is a great developer and Artix is just newborn it needs time to settle down and patience from users with problems remember not all users have problems and like its big brother needs intermediate users to test and give proper support to the project,
That means a proper description of the problem, system info as much as is needed you can get all the info you need in a terminal I'm not going to tell you read it its in the Arch wiki in fact virtually every distro wiki gives the information needed
@mandog You may have missed the other topic today but for you to be told to switch to arch-testing to get a missing dependency may be trivial. To people who had never used arch it is not. For a distribution that was called an easy switch from manjaro-openrc a few lines of detailed instruction is not too much to ask.
If I have respect for artix it is for a team called artix. I couldn't care less who is in and who is out of it. Developers can be distribution hoppers just like users are.
If you look up #33 this is the same person who seemed most helpful to me while trying to get accustomed with Manjaro.
Am I stepping off topic? Ever since the new installer came out all I see is people being frustrated to make it work.
What you say about arch and systemd is true, I now realize this. What I had not realized is how much of arch experience is required before you get to artix. This should have been a warning ever since the DIY switch manjaro to artix was published.
PS I have asked to be deleted from the moderators list since yesterday, and it is pissing me off that my wish is not respected. Privileges and responsibilities under some title should be shared both ways. It seems that here we have yet another example of an alternative definition of things. It must be an arch thing. I refuse to be a moderator under this conditions.
@fungalnet I don't like inserting myself into forum drama, but I feel that you are being unreasonable. I realize that as someone who migrated from Arch-Openrc; I have a different perspective than someone who came from Manjaro. However, the core of this project has always been Arch without systemd. That is not a trivial thing and the audience that cares about init systems can reasonably be expected to be more "advanced" linux users than the norm. I feel like any blame for having incorrect expectations should really be directed at the Manjaro folks more than anyone else.
I'm reluctant to lose a good team member, however I cannot force anyone against their will.
The "Artix philosophy OP" deteriorated into political and religious analogies and all posts about politics and religion are bound to offend people with different opinions and that was why I asked all of you to stop.
Eventually, one post went way out of line and it just so happened to be yours. You shouldn't get angry for being told that the line was crossed and start posting sarcastic messages, because you made a lot bigger a deal than it initially was. Κρίμα.
IMPORTANT! Due to the fact that, as reported from Artoo, the support of the graphical DE (Desktop Environment) is not completed in Artix, because it require a lot of time and a lot of resources, the better way that I find to install almost all the DE, is to start with the LXQT installation and, when completed, to reboot in LXQT and to install the preferred DE. Below you'll find the steps that I managed to install KDE/Plasma.
Not all the problems has been solved, to remove systemd is not a trivial goal, but with few efforts I was able to install BIOS and EFI notebook.Finally I was able to install KDE/Plasma with btrfs and LUKS, starting from a scratch situation and not with a conversion.
A) Boot the live iso
A1) Open the terminal and update the repos:
sudo pacman -SyyYou don't need to upgrade the ISO program so, don't do it.
A2) Verify that you have the right mirrors pointing to the right repos:
sudo nano /etc/pacman.d/mirrorlistThis must be the content of the mirrorlist file:
##
## Artix Linux repository mirrorlist
## Generated on 2017-10-21
##
# Artix mirrors
Server = http://mirror1.artixlinux.org/repos/$repo/os/$arch
Server = http://artix.wheaton.edu/repos/$repo/os/$arch/
Server = http://mirror.strits.dk/artix-linux/repos/$repo/os/$arch
Server = https://mirrors.dotsrc.org/artix-linux/repos/$repo/os/$arch
Server = https://www.uex.dk/public/artix/$repo/os/$arch
A3) launch calamares from the terminal with the command:
sudo calamares -dWith this command you'll be able to see, inside the terminal, the calamares messages and, if needed, to cut and paste them for a help.
HINT: due to the fact that the terminal buffer is limited to 1.000 lines, growth it to 10.000 so you'll be sure not to loose any message.
A4) go ahead with the installation using ght calamares gui. Obviously if you have to install an EFI PC you must define a FAT32 boot partition, you find it between the choice list, and to set the correct flags.
HINT: ok, I'm and ancient user, but if the BIOS of the PC permit me to do it, I prefer to remove the EFI support and I to use the old BIOS approach...
A5) When the installation is completed you can reboot and to login in LXQT
B) Install PLASMA: preparation
B1) Install the libsystemd-dummy library, otherwise the call to the libsystemd.so (NOT used from Artix) generate an error pushing you back to the login screen:
sudo pacman -S libsystemd-dummyB2) Now, before to proceed I added the system-testing and the world-testing repos in pacman.conf:
sudo nano /etc/pacman.confThis is my pacman.conf (I activated also the lib32 and the multilib repos)
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
[system-testing]
Include = /etc/pacman.d/mirrorlist
[system]
Include = /etc/pacman.d/mirrorlist
[world-testing]
Include = /etc/pacman.d/mirrorlist
[world]
Include = /etc/pacman.d/mirrorlist
#[galaxy-testing]
#Include = /etc/pacman.d/mirrorlist
[galaxy]
Include = /etc/pacman.d/mirrorlist
# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.
#[lib32-testing]
#Include = /etc/pacman.d/mirrorlist
[lib32]
Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
[extra]
Include = /etc/pacman.d/mirrorlist-arch
[community]
Include = /etc/pacman.d/mirrorlist-arch
#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist-arch
[multilib]
Include = /etc/pacman.d/mirrorlist-arch
B3) when done upgrade the repos:
sudo pacman -SyyB4) update the keys DB. Sometime appear a key error or corrupted file about the buildbot Artix digital sign. To avoid the problem you can tell at your Artix to accept the key. The commands are:
1) open the terminal
2) [b]sudo pacman-key --edit-key 0A3EB6BB142C56653300420C1247D995F165BBAC[/b]
3) appear the command line: [b]gpg> [/b]
4) digit the [b]trust[/b] command
5) Enter
6) Select the option [b]5) trust ultimately [/b] (digit the 5)
7) confirm your decision
7) exit using the [b]quit[/b] command
when done launch:
sudo pacman-key --populate archlinux artix
sudo pacman-key --refresh-keyC) Install the Plasma DE.
*
sudo pacman -S plasma or
*
sudo pacman -S plasma-met* install the graphical login:
sudo plasma -S sddm-kcm to configure KDE with SDDM
C2) to complete the installation, install the kde applications that you prefer. You can start with:
*
sudo pacman -S kdebase*
sudo pacman -S kdeadminor if you want a more complete set of the KDE applications
*
sudo pacman -S kde-applicationsC3) Your KDE/Plasma Environment has been installed. Reboot and enjoy, without systemd ;)
That's all, by now. I'll update this little tutorial step by step, while repeating the installation step by step.
If I did some errors, please, tell me. I tried to be more clear as possible, but the perfection is not of this world.
Thank you Francesco, I will attempt this again later on today.
edit: I'm STILL getting errors :/ I tried to enable system-testing as well as world-testing too and I just can't seem to make it install...
I was getting stuck because of qt5-base package, but now its failing to install the EFI boot manager... -.-
https://pastebin.com/EhQx7Huz
Edit: and yes I have made a FAT32 /boot/efi drive. I've tried to make one before the / drive & one after the / drive... Maybe if I disable the -testing repos it might make a difference, I dunno...
2nd edit: I have managed to get it installed but no UEFI, just BIOS, and I had to fight with that for quite some time. We have a big problem with files becoming "corrupted", I really think the ISO's should contain the necessary installation files to avoid this insane problem, I don't know much about Linux but I think this is definitely something the Artix team should do.
Kenny, please, can you post the COMMANDS that you used to install Artix? Just the copy and paste of the terminal.
Without the list of the commands and only with the log, is almost impossible to understand what happen.
Thank you :)
Kenny, I update the installation description . You can find it here with a description of all the steps:
https://artixlinux.org/forum/index.php?topic=88.msg631#msg631
List of commands??? I don't know what you're talking about... I open up Calamares in the terminal and click stuff... ????????
I'm sorry but you really can't expect new-ish users to know what you're talking about all the time.. I don't understand what you're asking for... like, at all... I just post the errors and the stuff that goes on in the terminal when I open up Calamares..
think this thread has become unnecessarily confusing
I didn't know that calamares had terminal commands to do the installation, I thought it was all menus and arrows.
Interesting though if it does, for anyone running like a production run of similar installation to similar equipment, you make a script and off you go to coffee and begels.
Kenny,
1) yes, calamares don't support command
2) I simply wanted to know how you launched calamares: using the GUI Menu or from the terminal?
3) forgive me if I wasn't clear to explain. :D
In the post n° 48, I pasted the link at a post that explain, step by step, how to manage the installation. Did you read it?
No I am not using commands to do the calamares installation! I just use sudo calamares to open calamares up...
Hi, I have the same problem - it is not possible to install Artix via Calamares.
After some investigation I found there is at least one problem in "galaxy":
Package virtualbox-guest-modules-artix-5.2.0-7 is defined in pacman "galaxy" database but no relevant files exists on any of the pacman mirrors in galaxy subfolder.
This package is required by Calamares (even if I am installing Artix on "physical" PC) and this is probably the reason why some python scripts fails.
5.2.0-7 is in galaxy
5.2.2 exists in galaxy-testing but I don't see why this would be required by the installer
it also conflicts with virtualbox-guest-dkms if you want vb installed.
I used the early lxqt image to install artix a few days ago without QT, which I dislike.
I only had to edit the mirrorlists to the new ones manually and it all worked flawlessly.
You must also upgrade and populate the new keyrings and then refresh/update again.
Sorry, I cannot agree. The reality is little bit different:
The package virtualbox-guest-modules-artix-5.2.0-7 is included/defined ONLY in galaxy DATABASE file galaxy.db.
But there are missing relevant files (.xz and .sig) in /repos/galaxy/os/x86_64, there are only files:
virtualbox-ck-guest-modules-5.2.0-8-x86_64.pkg.tar.xz 154K 19-Nov-2017 11:59
virtualbox-ck-guest-modules-5.2.0-8-x86_64.pkg.tar.xz.sig 566 19-Nov-2017 11:59
virtualbox-ck-host-modules-5.2.0-8-x86_64.pkg.tar.xz 184K 19-Nov-2017 11:59
virtualbox-ck-host-modules-5.2.0-8-x86_64.pkg.tar.xz.sig 566 19-Nov-2017 11:59
virtualbox-guest-utils-openrc-20170919-1-any.pkg.tar.xz 2312 21-Sep-2017 12:05
virtualbox-guest-utils-openrc-20170919-1-any.pkg.tar.xz.sig 566 21-Sep-2017 12:07
nothing else.
The situation does not depend on the mirror, I checked all four currently accessible mirrors.