Artix Linux => Installation / Migration / Configuration => Topic started by: LizziAS on 16 September 2017, 10:24:43
Title: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 16 September 2017, 10:24:43
what does this mean?
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 54, in run check_target_env_call(["dbus-uuidgen", "--ensure"])
File "<string>", line 2, in <module>
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 16 September 2017, 10:40:01
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 54, in run check_target_env_call(["dbus-uuidgen", "--ensure"])
File "<string>", line 2, in <module>
The command dbus-uuidgen --ensure failed to regenerate/validate the machine id in mid-installations.
dbus-uuidgen --ensure generates a uuid in /var/lib/dbus/machine-id . If this file exists then it will be validated, and a failure code returned if it contains the wrong thing, which most likely what happened to your end (That is what I read from manpage anyway)
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: gosia on 16 September 2017, 11:36:51
Ok, and what remains to be done for installation? Sorry for my bad english...
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 16 September 2017, 13:04:27
The command dbus-uuidgen --ensure failed to regenerate/validate the machine id in mid-installations.
dbus-uuidgen --ensure generates a uuid in /var/lib/dbus/machine-id . If this file exists then it will be validated, and a failure code returned if it contains the wrong thing, which most likely what happened to your end (That is what I read from manpage anyway)
Ok, so what's to do about that? I did a fresh format for the /boot, /, and /home directories. UUID regards partitions. So what can i do?
I converted one version of manjaro-xfce-openrc to artix and was hoping to install a couple of other artix desktops on a new install.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: thefallenrat on 16 September 2017, 14:42:27
To be honest I don't know what the exact way to prevent but you can try deleting /var/lib/dbus/machine-id in your target root partition before the command was run
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 16 September 2017, 18:02:04
That would be a prettty tricky thing to do since it runs the script automated once you select the drives for formatting and the user input for name and password... there's really not an opportunity for user input
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: reboant on 17 September 2017, 07:19:27
Its seems to be a python problem probably resulting from either a corrupt download or bad disk burn.
Run checksum against it. Assuming its the lxqt iso you can find sha256 sum here under the list of downloads: https://sourceforge.net/projects/artix-linux/files/iso/lxqt/
Did you burn it to disk or thumbdrive? Did you use an appliclation or dd?
Please understand that I'm no expert just going on past experience. Hope it helps.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 17 September 2017, 09:26:17
Its seems to be a python problem probably resulting from either a corrupt download or bad disk burn.
Run checksum against it. Assuming its the lxqt iso you can find sha256 sum here under the list of downloads: https://sourceforge.net/projects/artix-linux/files/iso/lxqt/
Did you burn it to disk or thumbdrive? Did you use an appliclation or dd?
Please understand that I'm no expert just going on past experience. Hope it helps.
I did in fact use etcher which verifies the file written to the usb matches the one copied from.. i have had great success with it in the recent past and it's available for linux as well as other Oses. I'll see about checking the initial checksum. Honestly, i cant remember the last time i had a bad checksum. But it is worth checking.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 17 September 2017, 10:34:58
so we can see that the checksums match and since i used etcher which verifes the files after it has written them , we can know that they also match so it's not the isos or the usbs
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: reboant on 17 September 2017, 16:12:03
ok cool! Process of elimination.....don't ya just love it?
I used the exact same iso and tried installing to a partition that was formated to btrfs and ended up with a couple of error messages also. Sorry I don't remember them though. After the third or forth try it finally installed but it seems some files where corrupt and wouldn't even boot. Finally reformated to ext4, reinstalled, then booted without a hitch.
Keep trying and don't give up. Youi'll find the solution eventually.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 17 September 2017, 16:44:47
Already tried 4 times... if i cant use the file system i want then it's pointless to install
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: thefallenrat on 18 September 2017, 13:30:20
if os.path.exists(target_dbus_machineid_file): os.remove(target_dbus_machineid_file)
if enable_systemd: if os.path.exists(target_systemd_machineid_file): os.remove(target_systemd_machineid_file) check_target_env_call("systemd-machine-id-setup")
if enable_dbus: if enable_symlink and os.path.exists(target_systemd_machineid_file): check_target_env_call(["ln", "-s", "/etc/machine-id", "/var/lib/dbus/machine-id"]) else: check_target_env_call(["dbus-uuidgen", "--ensure"])
Then try running calamares installer again and see if it works (I hope it does)
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: mandog on 18 September 2017, 14:30:15
Already tried 4 times... if i cant use the file system i want then it's pointless to install
Have you tried anything else but etcher I did my install with imagewriter also try formatting off-line with a live cd. Then again you know me I could rename a bucket of poo as a ISO and it would install, the only problem buckets of poo are always systemd :D
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: robin0800 on 19 September 2017, 10:16:09
if os.path.exists(target_dbus_machineid_file): os.remove(target_dbus_machineid_file)
if enable_systemd: if os.path.exists(target_systemd_machineid_file): os.remove(target_systemd_machineid_file) check_target_env_call("systemd-machine-id-setup")
if enable_dbus: if enable_symlink and os.path.exists(target_systemd_machineid_file): check_target_env_call(["ln", "-s", "/etc/machine-id", "/var/lib/dbus/machine-id"]) else: check_target_env_call(["dbus-uuidgen", "--ensure"])
Then try running calamares installer again and see if it works (I hope it does)
A good find but an easier way? Go to /etc/calamares/modules/machineid.conf which reads false, true and true I changed them all to false seems to work.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: artoo on 19 September 2017, 13:21:29
if os.path.exists(target_dbus_machineid_file): os.remove(target_dbus_machineid_file)
if enable_systemd: if os.path.exists(target_systemd_machineid_file): os.remove(target_systemd_machineid_file) check_target_env_call("systemd-machine-id-setup")
if enable_dbus: if enable_symlink and os.path.exists(target_systemd_machineid_file): check_target_env_call(["ln", "-s", "/etc/machine-id", "/var/lib/dbus/machine-id"]) else: check_target_env_call(["dbus-uuidgen", "--ensure"])
Then try running calamares installer again and see if it works (I hope it does)
What are you doing guys?
This will not fix anything. Machineid is run after chrootcfg, the module which is skipped for whatever reason.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: thefallenrat on 19 September 2017, 13:34:34
if os.path.exists(target_dbus_machineid_file): os.remove(target_dbus_machineid_file)
if enable_systemd: if os.path.exists(target_systemd_machineid_file): os.remove(target_systemd_machineid_file) check_target_env_call("systemd-machine-id-setup")
if enable_dbus: if enable_symlink and os.path.exists(target_systemd_machineid_file): check_target_env_call(["ln", "-s", "/etc/machine-id", "/var/lib/dbus/machine-id"]) else: check_target_env_call(["dbus-uuidgen", "--ensure"])
Then try running calamares installer again and see if it works (I hope it does)
That's essentially the whole file. So I'm commenting out everything that's written there?
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 20 September 2017, 03:18:29
(http://i66.tinypic.com/nx1chy.jpg)
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 20 September 2017, 03:29:02
if os.path.exists(target_dbus_machineid_file): os.remove(target_dbus_machineid_file)
if enable_systemd: if os.path.exists(target_systemd_machineid_file): os.remove(target_systemd_machineid_file) check_target_env_call("systemd-machine-id-setup")
if enable_dbus: if enable_symlink and os.path.exists(target_systemd_machineid_file): check_target_env_call(["ln", "-s", "/etc/machine-id", "/var/lib/dbus/machine-id"]) else: check_target_env_call(["dbus-uuidgen", "--ensure"])
Then try running calamares installer again and see if it works (I hope it does)
both options return the timezone path error
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 20 September 2017, 03:48:13
Have you tried anything else but etcher I did my install with imagewriter also try formatting off-line with a live cd. Then again you know me I could rename a bucket of poo as a ISO and it would install, the only problem buckets of poo are always systemd :D
Tried with calamares and sues image writer, results are the same on install
Mintstick isn't running on my converted system for some reason. (Neither will gparted but that's another post)
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: francesco on 20 September 2017, 09:05:27
I got the same problem while trying to install Artix with plasma+btrfs+LUKS. Nothing change if I try using ext4.
If I launch calamares in debug mode [sudo calamares -d] and I look the log after the machine-id error, I discover that the error is NOT generated from the machine-id command, but from the fact that there is a broken dependency due to the fact that the system is trying to install libpulse version 11.x but in all the repos (I checked them one by one) there is libpulse 10.x.
To replicate the error simply launch calamares in debug mode and look the log.
I install now a virtual machine and in short send you a screenshot of the error.
I tried to install the LXQT version, settiing the machineid.conf parameters all to "false", as suggested, and it work almost correctly. There was some problems with the btrf subvol definition (@home is not mounted correctly, there is a conflict with @/ subvol), but this is another story...
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: francesco on 20 September 2017, 09:26:16
As you see in the attached log, the chrootcfg job is started, at the line 9 you see the first warning related with libpulse wrong version and, after 3 warning the error that crashed the chroot process immediately after. All the process crash with a 127 error code, but probably only the machine-id process visualize a dialog... :)
For the test I used Virtualbox with the Artix iso downloaded 2 days ago from the Sourceforge site.
Quote
07:14:52 [0]: Starting job "chrootcfg" 07:14:53 [1]: Job "chrootcfg" -> "Download and install package selection" 07:14:53 [1]: [PYTHON JOB]: "Create: /tmp/calamares-root-f28os_nx/etc" 07:14:53 [1]: [PYTHON JOB]: "Mode: 0o755" 07:14:53 [1]: [PYTHON JOB]: "Create: /tmp/calamares-root-f28os_nx/var/cache/pacman/pkg" 07:14:53 [1]: [PYTHON JOB]: "Mode: 0o755" 07:14:53 [1]: [PYTHON JOB]: "Create: /tmp/calamares-root-f28os_nx/var/lib/pacman" 07:14:53 [1]: [PYTHON JOB]: "Mode: 0o755" warning: cannot resolve "libpulse=11.1-1", a dependency of "pulseaudio" warning: cannot resolve "pulseaudio=11.1-1", a dependency of "pulseaudio-gconf" warning: cannot resolve "pulseaudio-gconf", a dependency of "plasma-pa" error: failed to prepare transaction (could not satisfy dependencies) 07:15:02 [0]: Running "chroot" ("/tmp/calamares-root-f28os_nx", "pacman-key", "--init") 07:15:02 [0]: Finished. Exit code: 127 07:15:02 [0]: Running "chroot" ("/tmp/calamares-root-f28os_nx", "pacman-key", "--populate", "archlinux", "artix") 07:15:02 [0]: Finished. Exit code: 127 07:15:02 [0]: Starting job "networkcfg" 07:15:02 [1]: Job "networkcfg" -> "Setup network configuration" 07:15:02 [0]: Starting job "machineid" 07:15:02 [1]: Job "machineid" -> "Generate machine-id using dbus and systemd." 07:15:02 [0]: Running "chroot" ("/tmp/calamares-root-f28os_nx", "dbus-uuidgen", "--ensure") 07:15:02 [0]: Finished. Exit code: 127 07:15:02 [1]: tbMsg " File "/usr/lib/calamares/modules/machineid/main.py", line 54, in run\n check_target_env_call(["dbus-uuidgen", "--ensure"])\n\n File "<string>", line 2, in <module>\n" 07:15:02 [0]: Installation failed: 07:15:02 [0]: - message: "Boost.Python error in job \"machineid\"." 07:15:02 [0]: - details: "<div><strong><class 'subprocess.CalledProcessError'></strong></div><div>Command 'dbus-uuidgen --ensure' returned non-zero exit status 127.</div><div>Traceback:</div><div><pre> File "/usr/lib/calamares/modules/machineid/main.py", line 54, in run\n check_target_env_call(["dbus-uuidgen", "--ensure"])\n\n File "<string>", line 2, in <module>\n</pre></div>" 07:15:02 [0]: Calamares will quit when the dialog closes. 07:15:03 [1]: FinishedViewStep::onActivate() 07:15:03 [1]: FinishedPage::setUpRestart() 07:17:20 [8]: Shutting down Calamares... 07:17:20 [8]: Finished shutdown. 07:17:20 [0]: QBasicTimer::start: QBasicTimer can only be used with threads started with QThread 07:17:20 [0]: QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 20 September 2017, 13:20:03
I got the same problem while trying to install Artix with plasma+btrfs+LUKS. Nothing change if I try using ext4.
If I launch calamares in debug mode [sudo calamares -d] and I look the log after the machine-id error, I discover that the error is NOT generated from the machine-id command, but from the fact that there is a broken dependency due to the fact that the system is trying to install libpulse version 11.x but in all the repos (I checked them one by one) there is libpulse 10.x.
To replicate the error simply launch calamares in debug mode and look the log.
I install now a virtual machine and in short send you a screenshot of the error.
I tried to install the LXQT version, settiing the machineid.conf parameters all to "false", as suggested, and it work almost correctly. There was some problems with the btrf subvol definition (@home is not mounted correctly, there is a conflict with @/ subvol), but this is another story...
Yes after i converted my system, i had to uninstall libpulse to run : pacman -Syuu to get the pulse system to downgrade - installed files from my converted system were newer than the files in the repos - so this actually makes sense to me.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: francesco on 21 September 2017, 11:28:32
A question: somebody can tell me how to correct the problem of the libpulse version dependency (as reported in the previous log)? Without the correction of this error I cannot install KDE vesion and, as a primary effect, I must continue to use a systemd OS.
Also a workaround shall be of help. The solution offered till now don't work.
Thanks.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 21 September 2017, 12:17:18
I concur. I still can not install with calamares.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: thefallenrat on 21 September 2017, 12:35:24
Try installing it without selecting any extra packages before hitting install button
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: francesco on 21 September 2017, 15:04:44
Sorry fallenrat, but do you think that, trying to install a new distribution, I didn't have previously searched some different path to discover a solution? To understand that the problem is a dependency problem and not a machineid strange error, require some time. I tested the installer with audio, without audio, with cups, without cups, without KDE apps, etc... etc... In every situations libpulse is requested and the system crash, always, due to the dependency problem, not the machineid.
So, probably, there is some base component that generate this dependency and the solution, the only one that I can imagine, is to replace the 10.x libpulse and pulseaudio version, with the 11.x or to downgrade the component requiring the 11.x version. But this is a developer work not an end user work.
I don't see other solutions, after trying all the possible combinations; if I tell you that I try at least 30 different combinations, probably I forget something :D Question: but the Artix developer team, read this forum or it is used only to "satisfy" the end user? If not I'd like to know how to report the error and to receive an answer. Do you agree with me that this kind of interaction is mandatory and not only for a new environment?
If I'm not wrong this problem is up and running from more than 2 weeks (I got it when I was busy to migrate the Manjaro/Openrc to Antergos) and you teach me that 2 weeks, for a bug of the installation program, is really a long time.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: thefallenrat on 21 September 2017, 15:21:25
I tested the installer with audio, without audio, with cups, without cups, without KDE apps, etc... etc... In every situations libpulse is requested and the system crash, always, due to the dependency problem, not the machineid.
What I meant is do the base install (without selecting any other packages or such)
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: francesco on 21 September 2017, 15:54:45
Done and the error is always there....
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: slblxs on 21 September 2017, 17:22:45
Good to all, I do not know if this is the right place but, I take advantage of not opening another topic. I already made more than one attempt to install, Plasma-desktop and could not install via Calamares appeared an error. So I decided to install Lxqt and install everything fine, I made the minimal installation of Plasma and when I choose the desktop does not start and it comes back again to the sddm. In the installation I installed the Intel and Nouveau drivers. Thank you in advance.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: francesco on 21 September 2017, 19:02:10
What I meant is do the base install (without selecting any other packages or such)
Quote
I retry, another time, with a more minimal installation: nothing, the error is always present and its very annoying that nobody is answering and taking care of a similar situation. As I see, I'm not the only one having this problem and the impression is that this situation is not a good advertising for a new distribution.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: nous on 22 September 2017, 17:34:34
Question: but the Artix developer team, read this forum or it is used only to "satisfy" the end user? If not I'd like to know how to report the error and to receive an answer. Do you agree with me that this kind of interaction is mandatory and not only for a new environment? If I'm not wrong this problem is up and running from more than 2 weeks (I got it when I was busy to migrate the Manjaro/Openrc to Antergos) and you teach me that 2 weeks, for a bug of the installation program, is really a long time.
The team does read this forum and does its best to "satisfy" the end user. However, you must take into consideration a few things:
1. All of the dev team do this in their limited free time. We all have got our daily jobs which bring bread to our families. 2. We are few and can neither answer every post on the forum nor troubleshoot every single problem. 3. This distribution is less than 2 months old and is bound to have bugs. We never gave any warranties of any sort about being bug-free. 4. We are an Arch-derivative distro. This means that our audience is supposed to be more knowledgeable and competent than the average linux user. A certain expertise with the command line is assumed; if the graphical installer fails you should/must know how to use the CLI. Or at least RTFM and follow instructions. Calamares is buggy, but is the only one we've got at the moment - make do with whatever is provided. If all else fails, you can install vanilla arch (or manjaro, but not recommended) and migrate as per https://artixlinux.org/migrate.php - hell, you can migrate from every pacman-based distro to Artix if you put our repos above theirs and follow the guide! 5. Our next ISOs will be far better! 8)
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: mrbrklyn on 22 September 2017, 17:43:53
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 54, in run check_target_env_call(["dbus-uuidgen", "--ensure"])
File "<string>", line 2, in <module>
bingo - that was my error on Calamares
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: mrbrklyn on 22 September 2017, 17:48:43
Have you tried anything else but etcher I did my install with imagewriter also try formatting off-line with a live cd. Then again you know me I could rename a bucket of poo as a ISO and it would install, the only problem buckets of poo are always systemd :D
In my experience, the likihood of coruption in the image is minimal. I used to burn images by the thousands to dvds for distribution.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: mrbrklyn on 22 September 2017, 17:52:02
Is there a CLI?
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: francesco on 22 September 2017, 18:49:30
Actually their might be its called base install ISO fired it up but did not use it. The i3 ISO is newer and installed flawless the other day its just a later installer does the same as the earlier just a newer build
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: mrbrklyn on 23 September 2017, 04:17:49
I am aware that this is a very young distribution and so far, I'm very relaxed and looking forward for the next iso. The main reason for my post of the installation issues is, that I wanted to know, if I made mistakes. I do not have the expectation to get an error-free system immediately. 8)
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: phoenix_king_rus on 23 September 2017, 10:34:05
Maybe some people should be interested in following When i tryed to install artix with base ISO on btrfs subvolume, it coudn't mount btrfs with error "wrong fs type". The solution for me was to use arch install scripts (for example, from arch bootstrap iso) with artix pacman.conf and mirrors. In this case you just need to follow arch wiki page on installation from existing linux and add some commands from artix migration manual (like populate artix keyring and add openrc services)
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: robin0800 on 23 September 2017, 10:58:13
had to run the command several times as the installer was not called or if called segfaulted but eventually it worked. -E preserves your env. and -d is debug so you can see what calamares is doing.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: fungalnet on 23 September 2017, 12:17:12
what is the command for installing grub. grub-install
grub-install /dev/sda (sdb or whatever you want it to go to) otherwise you can update-grub without it being installed on sda, copy the 1st menuentry and its submenus and paste it to the other distribution's grub.cfg in the ##custom 40## area. Supposedly when the other system updates its grub does not alter the entries already in custom.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: robin0800 on 23 September 2017, 12:58:36
grub-install /dev/sda (sdb or whatever you want it to go to) otherwise you can update-grub without it being installed on sda, copy the 1st menuentry and its submenus and paste it to the other distribution's grub.cfg in the ##custom 40## area. Supposedly when the other system updates its grub does not alter the entries already in custom.
Don't think this works on UEFI systems?
If you use UEFI see here half way down the page
https://artixlinux.org/migrate.php
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: fungalnet on 23 September 2017, 14:49:08
No, I keep thinking everyone here works on sub $100 machines still :) Feel free to add the alternative
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 23 September 2017, 15:57:48
i just installed archbang.. it is now running openrc and using artix repos so if you like openbox and dont mind configuring it a bit, it can work. it uses a text based installer called abinstall and i'm thinking that could or should be adapted for using with artix and not even bother with calamares at all..
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 23 September 2017, 16:07:31
i mean you could modify abinstall for artix purposes and then put it in the repos for people to install from the live medum
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: mrbrklyn on 24 September 2017, 00:23:42
I really can't seem to get X working, which is very frustrating because it seems the more that screw with X the worst it works. I need x to do two things, to start from the command line with startx, and to work from an ssh tunnel, which I can't get to seem to function despite efforts with xhost and xwrapper.conf. I don't even know where to start to debug this. I has worked since slackware 3.2 and now it doesn't. BTW I tried to start lxdm and that froze everything.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: gentermnl on 27 September 2017, 22:10:55
I just want to confirm that the apparent machineid error is really secondary to the pulse dependency issue? If so, does anyone know what is pulling in pulse, since I certainly didn't manually select it. Also - is there any way for calamares to save it's confguration and reload it so that if it fails, you don't have to specify every little bit of info again?
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: robin0800 on 27 September 2017, 23:31:22
Yes its plasma-pa that pulls pulseaudio-gconf that pulls pulseaudio that then pulls libpulse and yes that dependency error is what causes the machineid error. Not sure what you can do, leave out pulse-pa perhaps enable the system-testing repo, try another DE and add plasma later?
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: LizziAS on 28 September 2017, 02:21:21
well the work around seems to be to install the base iso packages and then after install of the base system, manually install all the thingies you want to run... you need a few chops to pull that offf though... fortunately, though not too many chops needed....
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: francesco on 28 September 2017, 13:46:48
Yes its plasma-pa that pulls pulseaudio-gconf that pulls pulseaudio that then pulls libpulse and yes that dependency error is what causes the machineid error. Not sure what you can do, leave out pulse-pa perhaps enable the system-testing repo, try another DE and add plasma later?
A question: but is not more simple to replace the 10.x version in the repos with the 11.x requested from plasma-pa?
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: robin0800 on 28 September 2017, 17:15:11
The 11 x is in the testing repo's not sure if you can enable them before starting calamares, it is world testing you need I think.
Title: Re: Installation issues with the 8/8/2017 image lxqt
Post by: francesco on 29 September 2017, 15:27:35
The 11 x is in the testing repo's not sure if you can enable them before starting calamares, it is world testing you need I think.
I tried to replace world repos with world-testing, but without result. It solve (no messages in Calamares log) the problem of the dependency of libpulse 11.x. but crashed in the chroot process pacman-key --init. I completed a Plasma installation with another approach. I did a post.