MX-19 Beta 1 Feedback

Message
Author
User avatar
Jerry3904
Administrator
Posts: 23088
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-19 Beta 1 Feedback

#31 Post by Jerry3904 »

It looks like this is the first time I ran it and exited when it wanted root password:

Code: Select all

2019-08-25 20:15:12.610 DBG default: +++ void MInstall::startup() +++
2019-08-25 20:15:12.611 DBG default: Exec #1: "uname -m | grep -q i686"
2019-08-25 20:15:12.730 DBG default: Exit #1: 1 QProcess::ExitStatus(NormalExit)
2019-08-25 20:15:12.730 DBG default: Exec #2: "test -d /sys/firmware/efi"
2019-08-25 20:15:12.751 DBG default: Exit #2: 0 QProcess::ExitStatus(NormalExit)
2019-08-25 20:15:12.751 DBG default: uefi = true
2019-08-25 20:15:12.751 DBG default: Exec #3: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled'"
2019-08-25 20:15:12.883 DBG default: Exit #3: 0 QProcess::ExitStatus(NormalExit)
2019-08-25 20:15:12.883 DBG default: Exec #4: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled --set false'"
2019-08-25 20:15:12.926 DBG default: Exit #4: 0 QProcess::ExitStatus(NormalExit)
2019-08-25 20:15:12.926 DBG default: Exec #5: "ps -aux |grep -v grep | grep devmon"
2019-08-25 20:15:12.955 DBG default: Exit #5: 1 QProcess::ExitStatus(NormalExit)
2019-08-25 20:15:12.955 DBG default: Exec #6: "grep space /home/$(logname)/.desktop-session/desktop-code.*"
2019-08-25 20:15:12.967 DBG default: SErr #6: "grep: /home/demo/.desktop-session/desktop-code.*: No such file or directory\n"
2019-08-25 20:15:12.967 DBG default: Exit #6: 2 QProcess::ExitStatus(NormalExit)
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin

User avatar
ChrisUK
Posts: 299
Joined: Tue Dec 12, 2017 12:04 pm

Re: MX-19 Beta 1 Feedback

#32 Post by ChrisUK »

dolphin_oracle wrote: Mon Aug 26, 2019 12:07 pm so for you guys running into the installer issue, could you try, from the live usb without launching the installer

Code: Select all

sudo partprobe
sudo blkid -c /dev/null
please and thank you.
...

code]
sudo partprobe

Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
[/code]

Code: Select all

sudo blkid -c /dev/null
/dev/sda1: LABEL="MX18" UUID="51741f74-0727-47ea-a731-63f43e640978" TYPE="ext4" PARTUUID="ce682fae-01"
/dev/sda2: LABEL="MX175" UUID="70cfd9e8-676e-4fa4-86ba-e302fb5ede00" TYPE="ext4" PARTUUID="ce682fae-02"
/dev/sda3: LABEL="Data" UUID="23A7668A02124A50" TYPE="ntfs" PTTYPE="dos" PARTUUID="ce682fae-03"
/dev/sda5: LABEL="DataExt4" UUID="36f9ff28-7a4b-4598-9b1a-363ba6302bd2" TYPE="ext4" PARTUUID="ce682fae-05"
/dev/sda6: LABEL="NTFS1" UUID="3DE1D3681D7E6DBE" TYPE="ntfs" PTTYPE="dos" PARTUUID="ce682fae-06"
/dev/sdb1: UUID="2019-08-25-19-38-05-00" LABEL="MX-Live" TYPE="iso9660" PTUUID="5d95e9ad" PTTYPE="dos" PARTUUID="5d95e9ad-01"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="EFI-LIVE" LABEL="EFI-LIVE" UUID="6CFD-B910" TYPE="vfat" PARTUUID="5d95e9ad-02"
/dev/loop0: TYPE="squashfs"
/dev/sdd5: LABEL="MX172" UUID="bf7cffcc-b28d-49f6-8736-b4da5e5270d6" TYPE="ext4" PARTUUID="b38f0398-05"
/dev/sdd6: LABEL="Data" UUID="0D90E40DA50DEF3B" TYPE="ntfs" PARTUUID="b38f0398-06"
/dev/sdd7: LABEL="DataExt4" UUID="000ec35e-c8c0-4b02-ba91-aa51ed2c6bbe" TYPE="ext4" PTTYPE="dos" PARTUUID="b38f0398-07"
/dev/sdd8: LABEL="rootMX19" UUID="e15eb685-05ad-4247-85c3-0dd1d79914f1" TYPE="ext4" PARTUUID="b38f0398-08"
Chris

MX 18 MX 19 - Manjaro

User avatar
dolphin_oracle
Developer
Posts: 22080
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-19 Beta 1 Feedback

#33 Post by dolphin_oracle »

ChrisUK wrote: Mon Aug 26, 2019 12:30 pm
dolphin_oracle wrote: Mon Aug 26, 2019 12:07 pm so for you guys running into the installer issue, could you try, from the live usb without launching the installer

Code: Select all

sudo partprobe
sudo blkid -c /dev/null
please and thank you.
...

code]
sudo partprobe

Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
[/code]

Code: Select all

sudo blkid -c /dev/null
/dev/sda1: LABEL="MX18" UUID="51741f74-0727-47ea-a731-63f43e640978" TYPE="ext4" PARTUUID="ce682fae-01"
/dev/sda2: LABEL="MX175" UUID="70cfd9e8-676e-4fa4-86ba-e302fb5ede00" TYPE="ext4" PARTUUID="ce682fae-02"
/dev/sda3: LABEL="Data" UUID="23A7668A02124A50" TYPE="ntfs" PTTYPE="dos" PARTUUID="ce682fae-03"
/dev/sda5: LABEL="DataExt4" UUID="36f9ff28-7a4b-4598-9b1a-363ba6302bd2" TYPE="ext4" PARTUUID="ce682fae-05"
/dev/sda6: LABEL="NTFS1" UUID="3DE1D3681D7E6DBE" TYPE="ntfs" PTTYPE="dos" PARTUUID="ce682fae-06"
/dev/sdb1: UUID="2019-08-25-19-38-05-00" LABEL="MX-Live" TYPE="iso9660" PTUUID="5d95e9ad" PTTYPE="dos" PARTUUID="5d95e9ad-01"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="EFI-LIVE" LABEL="EFI-LIVE" UUID="6CFD-B910" TYPE="vfat" PARTUUID="5d95e9ad-02"
/dev/loop0: TYPE="squashfs"
/dev/sdd5: LABEL="MX172" UUID="bf7cffcc-b28d-49f6-8736-b4da5e5270d6" TYPE="ext4" PARTUUID="b38f0398-05"
/dev/sdd6: LABEL="Data" UUID="0D90E40DA50DEF3B" TYPE="ntfs" PARTUUID="b38f0398-06"
/dev/sdd7: LABEL="DataExt4" UUID="000ec35e-c8c0-4b02-ba91-aa51ed2c6bbe" TYPE="ext4" PTTYPE="dos" PARTUUID="b38f0398-07"
/dev/sdd8: LABEL="rootMX19" UUID="e15eb685-05ad-4247-85c3-0dd1d79914f1" TYPE="ext4" PARTUUID="b38f0398-08"
thank you.

I'm starting to think that the automount-disable happens too fast for some systems, and xfconf hasn't caught up before we probe for drives. fehlix is working on it.

for now, workaround is to manually disable automounting before launching for those machines so affected (mine isn't one, but my hardware is slow, which might actually help if timing is the issue).
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
BV206
Posts: 476
Joined: Sat Mar 09, 2019 10:55 am

Re: MX-19 Beta 1 Feedback

#34 Post by BV206 »

I want to use zsync to download the beta (and the August 18.3 iso).
I see the zsync "files" listed on sourceforge.net but because of their mirrors or something the .zsync url doesn't link to the actual file.
Is there an easy way to do that?

User avatar
fehlix
Developer
Posts: 12626
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-19 Beta 1 Feedback

#35 Post by fehlix »

BV206 wrote: Mon Aug 26, 2019 1:05 pm I want to use zsync to download the beta (and the August 18.3 iso).
I see the zsync "files" listed on sourceforge.net but because of their mirrors or something the .zsync url doesn't link to the actual file.
Is there an easy way to do that?
Yea, zsync-ing from sourcefourge is a bit tricky.
The attached zsync-helper script will get first closest mirror before the actually zsync is taking place:
The best result you would have with "binary" close iso.
Ok just testing how it would go, using MX18.3 iso (which is not very "binary" close):

Code: Select all

./zsync-mx-19-testing.sh  MX-19beta-1_x64.iso MX-18.3_August_x64.iso 
Well at least it tells us that "Target 22.5% complete."

Code: Select all

./zsync-mx-19-testing.sh  MX-19beta-1_x64.iso MX-18.3_August_x64.iso 
Downloading "MX-19beta-1_x64.iso" file
MX-19beta-1_x64.iso
Using input file: MX-18.3_August_x64.iso

Executing zsync command
#################### 100.0% 601.4 kBps DONE     

reading seed file MX-18.3_August_x64.iso: *****************************
**************
++++
***Read MX-18.3_August_x64.iso. Target 22.5% complete.
 *******************************************************
downloading from http://iweb.dl.sourceforge.net/project/mx-linux/Testing/MX-19/MX-19beta-1_x64.iso:
######-------------- 32.2% 7147.5 kBps 2:16 ETA   

Attached the zsync helper script:
zsync-mx-19-testing.sh

Code: Select all

#!/bin/bash

# zsync helper script 
# for MX-19-beta Testing

# filename zsync-mx-19-testing.sh


usage()
{
	echo "Usage $0 script"
	echo "$0 download_filename.iso inputfile.iso"
	echo "	Where inputfile.iso is the file you already have that's similar to the one you download"
	echo
	echo "$0 download_filename.iso"
	echo "	This command format will search automatically for the most recent MX*x64.iso file in the current folder"
	exit
}

[[ "$1" == "--help" || "$1" == "-h" ]] && usage


TARGET="$1"
[[ -z "$1" ]] && {
	echo "You need to specify a file name to download. exiting..."
	echo
	usage
}
echo "Downloading \"$1\" file"

grep "x64" <<< "$1" && ARCH="x64" || ARCH="386"

# add available local ISO-sources here - newest first
# check latest ISO-sources are available
SOURCE="$2"

[[ -f "$SOURCE" ]] && echo "Using input file:" "$SOURCE" || {
	[[ "$SOURCE" == "" ]] && echo "Input source not specified, trying to find a useful ISO in current path"
	[[ "$SOURCE" != "" ]] && echo "Input file \"$SOURCE\" not found, trying to find a useful ISO in current path"
	SOURCE=$(find . -iname "MX*$ARCH*.iso" -printf "%T+\t%p\n" | sort -r | head -1 | cut -f2)
	[[ "$SOURCE" != "" ]] && echo "Using "$SOURCE" source file" || {
		echo "Could not found an appropriate input file, exiting..."
		echo
		usage
	}
}

# do we have zsync
command -v zsync >&- || {
	# opps we need to and install zsync
	sudo apt-get update
	sudo apt-get install zsync
}

ZSYNC="${TARGET}".zsync

# get closest sourceforge server for zsync

DOWNLD=https://sourceforge.net/projects/mx-linux/files/Testing/MX-19/"${ZSYNC}"/download
SPIDER=$(wget -nv --spider "${DOWNLD}" 2>&1 | grep -Eo https.*iso.zsync | sed 's/https/http/')

[[ -z "$SPIDER" ]] && {
	 echo; echo "Could not find \"$1\" file on SourceForge server, please check the name. Exiting..."
	 echo
	 usage
}

# let's do zsync
[[ -f "${TARGET}" ]] || echo; echo "Executing zsync command"; zsync -i "$SOURCE" "${SPIDER}" || {
	echo
	usage
}

HTH
:puppy:

franksmcb

Re: MX-19 Beta 1 Feedback

#36 Post by franksmcb »

The beta is looking good.

No issues booting into systemd and install snapd.
Snaps seem to be working well.

First impressions are very good.

User avatar
Gerson
Posts: 879
Joined: Sun Nov 12, 2017 9:58 am

Re: MX-19 Beta 1 Feedback

#37 Post by Gerson »

dolphin_oracle wrote: Mon Aug 26, 2019 11:55 am
Gerson wrote: Mon Aug 26, 2019 11:54 am The ugly duckling for now has flaws in the panel, does not have the time and the conky is not transparent, I miss Docky and Openastro that was in the test repository, I congratulate them for placing FreeOffice, I hope to test it soon. Are there two types of screensavers?
did you turn off the compositor? you need the compositor on for transparency on the new Xfce. or are you using an existing home folder perhaps?
I'm sorry, it's my mistake, I used the old /home folder.
I reinstalled from zeros and now everything works normally, I just hope to have Openastro back in the repository.
Great job, thank you.
No todos ignoramos las mismas cosas. :confused:

User avatar
penguin
Posts: 262
Joined: Wed Jan 04, 2017 2:15 pm

Re: MX-19 Beta 1 Feedback

#38 Post by penguin »

How to import MX-19 GPG key ?

Tried to verify MX-19beta-1_x64.iso (Highly recommended to verify MX iso file that you download , these days that MX Linux keeps continuously first position :number1: ) . Why ? I remember, times ago, someone altered iso files of Manjaro or Mint on their original repositories(website) and that was noticed by admins, hours later!

Code: Select all

gpg --verify MX-19beta-1_x64.iso.sig
gpg: assuming signed data in 'MX-19beta-1_x64.iso'
gpg: Signature made Sun 25 Aug 2019 09:38:38 PM CEST
gpg:                using RSA key F62EDEAA3AE70A9C99DAC4189B68A1E8B9B6375C
gpg: Can't check signature: No public key
Seems GPGkey is missing in my laptop.
Commands
gpg --list-keys and gpg --list-secret-keys in Terminal

returns empty result, meanwhile FiX GPG Keys in MX Tools gives :

Code: Select all

Checking security.debian.org_dists_stretch_updates_InRelease
    Good GPG signature found.

Checking it.mxrepo.com_antix_stretch_dists_stretch_InRelease
    Good GPG signature found.

Checking ftp.bg.debian.org_debian_dists_stretch_Release
    Good GPG signature found.

Checking ftp.bg.debian.org_debian_dists_stretch-updates_InRelease
    Good GPG signature found.

Checking repo.skype.com_deb_dists_stable_InRelease
    Good GPG signature found.

Checking download.mono-project.com_repo_debian_dists_stable-stretch_InRelease
    Good GPG signature found.

Checking it.mxrepo.com_mx_repo_dists_stretch_InRelease
    Good GPG signature found.

Checking deb.opera.com_opera-stable_dists_stable_InRelease
    Good GPG signature found.

P.S

Some GPG tuts for folks.

Code: Select all

https://wiki.manjaro.org/index.php?title=How-to_verify_GPG_key_of_official_.ISO_images

Code: Select all

http://irtfweb.ifa.hawaii.edu/~lockhart/gpg/
Last edited by penguin on Mon Aug 26, 2019 2:42 pm, edited 2 times in total.

User avatar
dolphin_oracle
Developer
Posts: 22080
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-19 Beta 1 Feedback

#39 Post by dolphin_oracle »

penguin wrote: Mon Aug 26, 2019 2:35 pm How to import MX-19 GPG key ?

Tried to verify MX-19beta-1_x64.iso

Code: Select all

gpg --verify MX-19beta-1_x64.iso.sig
gpg: assuming signed data in 'MX-19beta-1_x64.iso'
gpg: Signature made Sun 25 Aug 2019 09:38:38 PM CEST
gpg:                using RSA key F62EDEAA3AE70A9C99DAC4189B68A1E8B9B6375C
gpg: Can't check signature: No public key
Seems GPGkey is missing in my laptop.
Commands
gpg --list-keys and gpg --list-secret-keys in Terminal

returns empty result, meanwhile FiX GPG Keys in MX Tools gives :

Code: Select all

Checking security.debian.org_dists_stretch_updates_InRelease
    Good GPG signature found.

Checking it.mxrepo.com_antix_stretch_dists_stretch_InRelease
    Good GPG signature found.

Checking ftp.bg.debian.org_debian_dists_stretch_Release
    Good GPG signature found.

Checking ftp.bg.debian.org_debian_dists_stretch-updates_InRelease
    Good GPG signature found.

Checking repo.skype.com_deb_dists_stable_InRelease
    Good GPG signature found.

Checking download.mono-project.com_repo_debian_dists_stable-stretch_InRelease
    Good GPG signature found.

Checking it.mxrepo.com_mx_repo_dists_stretch_InRelease
    Good GPG signature found.

Checking deb.opera.com_opera-stable_dists_stable_InRelease
    Good GPG signature found.

P.S

Some GPG tuts for folks.

Code: Select all

https://wiki.manjaro.org/index.php?title=How-to_verify_GPG_key_of_official_.ISO_images

Code: Select all

http://irtfweb.ifa.hawaii.edu/~lockhart/gpg/
per wiki

https://mxlinux.org/wiki/system/signed-iso-files/#MX-17
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
penguin
Posts: 262
Joined: Wed Jan 04, 2017 2:15 pm

Re: MX-19 Beta 1 Feedback

#40 Post by penguin »

dolphin_oracle wrote: Mon Aug 26, 2019 2:39 pm
penguin wrote: Mon Aug 26, 2019 2:35 pm How to import MX-19 GPG key ?

Tried to verify MX-19beta-1_x64.iso

Code: Select all

gpg --verify MX-19beta-1_x64.iso.sig
gpg: assuming signed data in 'MX-19beta-1_x64.iso'
gpg: Signature made Sun 25 Aug 2019 09:38:38 PM CEST
gpg:                using RSA key F62EDEAA3AE70A9C99DAC4189B68A1E8B9B6375C
gpg: Can't check signature: No public key
Seems GPGkey is missing in my laptop.
Commands
gpg --list-keys and gpg --list-secret-keys in Terminal

returns empty result, meanwhile FiX GPG Keys in MX Tools gives :

Code: Select all

Checking security.debian.org_dists_stretch_updates_InRelease
    Good GPG signature found.

Checking it.mxrepo.com_antix_stretch_dists_stretch_InRelease
    Good GPG signature found.

Checking ftp.bg.debian.org_debian_dists_stretch_Release
    Good GPG signature found.

Checking ftp.bg.debian.org_debian_dists_stretch-updates_InRelease
    Good GPG signature found.

Checking repo.skype.com_deb_dists_stable_InRelease
    Good GPG signature found.

Checking download.mono-project.com_repo_debian_dists_stable-stretch_InRelease
    Good GPG signature found.

Checking it.mxrepo.com_mx_repo_dists_stretch_InRelease
    Good GPG signature found.

Checking deb.opera.com_opera-stable_dists_stable_InRelease
    Good GPG signature found.

P.S
and
Some GPG tuts for folks.

Code: Select all

https://wiki.manjaro.org/index.php?title=How-to_verify_GPG_key_of_official_.ISO_images

Code: Select all

http://irtfweb.ifa.hawaii.edu/~lockhart/gpg/
per wiki

https://mxlinux.org/wiki/system/signed-iso-files/#MX-17
Thanks dolphin_oracle !
Before writing my post I made a search on MX Linux using GPG key as word for my search , but I have been not strictly cautious. And I remembered that have read this info before ...

Code: Select all

gpg --keyserver hkp://keys.gnupg.net --recv-keys B9B6375C 0679EE98 892C32F1
gpg: key 13C74A22892C32F1: public key "Steven Pusser <stevep@mxlinux.org>" imported
gpg: key 70938C780679EE98: public key "Adrian <adrian@mxlinux.org>" imported
gpg: key 9B68A1E8B9B6375C: public key "Dolphin Oracle (mxlinux) <dolphinoracle@gmail.com>" imported
gpg: Total number processed: 3
gpg:               imported: 3
and

Code: Select all

gpg --list-keys
/home/penguin/.gnupg/pubring.kbx
--------------------------------
pub   rsa2048 2016-10-20 [SC]
      09DA59435EF8C739C8ED615613C74A22892C32F1
uid           [ unknown] Steven Pusser <stevep@mxlinux.org>
sub   rsa2048 2016-10-20 [E]

pub   rsa2048 2015-10-29 [SC] [expires: 2019-10-08]
      F27753A18E92E3937E6335E770938C780679EE98
uid           [ unknown] Adrian <adrian@mxlinux.org>
sub   rsa2048 2015-10-29 [E] [expires: 2019-10-08]

pub   rsa4096 2017-09-06 [SC]
      F62EDEAA3AE70A9C99DAC4189B68A1E8B9B6375C
uid           [ unknown] Dolphin Oracle (mxlinux) <dolphinoracle@gmail.com>
sub   rsa4096 2017-09-06 [E]
and

Code: Select all

gpg --verify MX-19beta-1_x64.iso.sig
gpg: assuming signed data in 'MX-19beta-1_x64.iso'
gpg: Signature made Sun 25 Aug 2019 09:38:38 PM CEST
gpg:                using RSA key F62EDEAA3AE70A9C99DAC4189B68A1E8B9B6375C
gpg: Good signature from "Dolphin Oracle (mxlinux) <dolphinoracle@gmail.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: F62E DEAA 3AE7 0A9C 99DA  C418 9B68 A1E8 B9B6 375C
Thanks for your time and effort, Mx Linux Team !

Locked

Return to “General”