Skip to main content ↑ ↓
Topic: Installation issues with the 8/8/2017 image lxqt (Read 9889 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Installation issues with the 8/8/2017 image lxqt

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>

Re: Installation issues with the 8/8/2017 image lxqt

Reply #1 –
inxi -Fxzc0
System:    Host: artix Kernel: 4.9.44-1-lts x86_64 (64 bit gcc: 7.1.1) Desktop: N/A Distro: Artix rolling
Machine:   Device: laptop Mobo: GIGABYTE model: M1M3XCP-00 v: 1.x BIOS: American Megatrends v: F3 date: 10/30/2015
CPU:       Quad core AMD A8-5557M APU with Radeon HD Graphics (Piledriver rev.1) (-MCP-) cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 16768
           clock speeds: max: 2100 MHz 1: 1400 MHz 2: 1400 MHz 3: 1400 MHz 4: 1400 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Richland [Radeon HD 8550G] bus-ID: 00:01.0
           Display Server: x11 (X.Org 1.19.3) drivers: ati,radeon (unloaded: modesetting)
           Resolution: [email protected]
           OpenGL: renderer: Gallium 0.4 on AMD ARUBA (DRM 2.49.0 / 4.9.44-1-lts, LLVM 4.0.1)
           version: 4.1 Mesa 17.1.8 Direct Render: Yes
Audio:     Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller driver: snd_hda_intel bus-ID: 00:14.2
           Card-2 Advanced Micro Devices [AMD/ATI] Trinity HDMI Audio Controller
           driver: snd_hda_intel bus-ID: 00:01.1
           Sound: Advanced Linux Sound Architecture v: k4.9.44-1-lts
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8168 v: 8.044.02-NAPI port: e000 bus-ID: 05:00.0
           IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
           Card-2: Intel Wireless 3160 driver: iwlwifi bus-ID: 06:00.0
           IF: wlp6s0 state: up mac: <filter>
Drives:    HDD Total Size: 628.1GB (6.5% used)
           ID-1: /dev/sda model: MT size: 128.0GB
           ID-2: /dev/sdb model: TOSHIBA_MK5075GS size: 500.1GB
Partition: ID-1: / size: 16G used: 6.7G (47%) fs: f2fs dev: /dev/sda2
           ID-2: /home size: 26G used: 551M (3%) fs: f2fs dev: /dev/sda4
           ID-3: /boot size: 248M used: 209M (89%) fs: ext2 dev: /dev/sda3
           ID-4: swap-1 size: 17.17GB used: 0.00GB (0%) fs: swap dev: /dev/sdb1
Sensors:   System Temperatures: cpu: 52.8C mobo: N/A gpu: 51.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 169 Uptime: 7 min Memory: 691.4/11207.8MB
           Init: N/A rc: OpenRC runlevel: default Gcc sys: 7.1.1 Client: Shell (bash 4.4.121) inxi: 2.3.27

Re: Installation issues with the 8/8/2017 image lxqt

Reply #2 –
Quote from: LizziAS – on
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>

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)
If I can hit that bullseye, the rest of the dominoes will fall like a house of cards. Checkmate!

Re: Installation issues with the 8/8/2017 image lxqt

Reply #3 –
Ok, and what remains to be done for installation? Sorry for my bad english...

Re: Installation issues with the 8/8/2017 image lxqt

Reply #4 –
Quote from: thefallenrat – on
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.

Re: Installation issues with the 8/8/2017 image lxqt

Reply #5 –
@LizziAS @gosia

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

If I can hit that bullseye, the rest of the dominoes will fall like a house of cards. Checkmate!

Re: Installation issues with the 8/8/2017 image lxqt

Reply #6 –
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

Re: Installation issues with the 8/8/2017 image lxqt

Reply #7 –
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.

Re: Installation issues with the 8/8/2017 image lxqt

Reply #8 –
Quote from: reboant – on
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.

Re: Installation issues with the 8/8/2017 image lxqt

Reply #9 –
so these are those sums:

SHA256 sums
2c3aec9f75c28434fd1ce1bfa295bf2ca816957e3efc388c60ad441807a2618d artix-base-rolling-x86_64.iso
b861deacb42011423e0f1c8d6f1476ba5589778117eddfc898737b161289655d artix-i3-rolling-x86_64.iso
df8e292b7a882ed7e325534056e0f1c7b165d9c9dc4a34255d686a6f48aba3ec artix-lxqt-rolling-x86_64.iso


and here are my results:

[lizzias@artix ISOs]$ sha256sum artix-base-rolling-x86_64.iso
2c3aec9f75c28434fd1ce1bfa295bf2ca816957e3efc388c60ad441807a2618d  artix-base-rolling-x86_64.iso

[lizzias@artix ISOs]$ sha256sum artix-i3-rolling-x86_64.iso
b861deacb42011423e0f1c8d6f1476ba5589778117eddfc898737b161289655d  artix-i3-rolling-x86_64.iso

[lizzias@artix ISOs]$ sha256sum artix-lxqt-rolling-x86_64.iso
df8e292b7a882ed7e325534056e0f1c7b165d9c9dc4a34255d686a6f48aba3ec  artix-lxqt-rolling-x86_64.iso

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


Re: Installation issues with the 8/8/2017 image lxqt

Reply #10 –
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.

Re: Installation issues with the 8/8/2017 image lxqt

Reply #11 –
Already tried 4 times... if i cant use the file system i want then it's pointless to install

Re: Installation issues with the 8/8/2017 image lxqt

Reply #12 –
Wanna try this, @LizziAS ?

Edit /usr/lib/calamares/modules/machineid/main.py , and comment this part of the file :

Code: [Select]
    root_mount_point = libcalamares.globalstorage.value("rootMountPoint")
    enable_systemd = libcalamares.job.configuration["systemd"]
    enable_dbus = libcalamares.job.configuration["dbus"]
    enable_symlink = libcalamares.job.configuration["symlink"]
    target_systemd_machineid_file = root_mount_point + "/etc/machine-id"
    target_dbus_machineid_file = root_mount_point + "/var/lib/dbus/machine-id"

    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)
If I can hit that bullseye, the rest of the dominoes will fall like a house of cards. Checkmate!

Re: Installation issues with the 8/8/2017 image lxqt

Reply #13 –
Quote from: LizziAS – on
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

Re: Installation issues with the 8/8/2017 image lxqt

Reply #14 –
Quote from: thefallenrat – on
Wanna try this, @LizziAS ?

Edit /usr/lib/calamares/modules/machineid/main.py , and comment this part of the file :

Code: [Select]
    root_mount_point = libcalamares.globalstorage.value("rootMountPoint")
    enable_systemd = libcalamares.job.configuration["systemd"]
    enable_dbus = libcalamares.job.configuration["dbus"]
    enable_symlink = libcalamares.job.configuration["symlink"]
    target_systemd_machineid_file = root_mount_point + "/etc/machine-id"
    target_dbus_machineid_file = root_mount_point + "/var/lib/dbus/machine-id"

    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.