Page 1 of 1

MX-21 RC1 feedback (Xfce)

Posted: Tue Oct 05, 2021 2:45 pm
by dolphin_oracle
Feedback for RC1 Xfce isos go here. Also general MX stuff can go here.

https://mxlinux.org/blog/mx-21-release- ... -purposes/


Be sure to include proper system data, including the output of quick-system-info.
If posting nvidia-installer (ddm-mx) issues, please post the contents of /var/log/ddm.log.
If posting remaster issues, please include the contents of /var/log/live/live-remaster.log
If posting installer issues, please include the contents of /var/log/minstall.log
If posting issues with MX-PackageInstaller “Popular Apps”, please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 3:09 am
by drogon69
from in mxlinux beta 1 and 2 and in rc1 i have seen that the plug of thunar samba share is install but dont work at all.
in xfce under sysnaptic i have seen that it is install , but not showing in thunar , all 3 versions beta 1 ,2 and know rc1 , is not showing in thunar at all.
but it is install , that is rare , i have reinstall and still not showing , but from the look i have seen , so far , mxlinux 19.4 is far better than 21 sorry but is just a fact.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 3:24 am
by TOMCAT
No matter what theme I choose, there is a blue border outside the active window, which looks bad when using the red theme (Numix). Resolved
Switching the system-language (system-locales) does not update the name of the user folder. This is good in MX19.4
Also, I would like to know where I can add the username and password for samba.



The window border can be set in "tweak" 。This is something that is not in MX19.4

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 3:48 am
by drogon69
TOMCAT wrote: Wed Oct 06, 2021 3:24 am No matter what theme I choose, there is a blue border outside the active window, which looks bad when using the red theme (Numix).
Switching the system-language (system-locales) does not update the name of the user folder. This is good in MX19.4
Also, I would like to know where I can add the username and password for samba.
YESSSS VERY TREU , mxlinux have lost the touch in mxlinux 21 , there are more problem than you thing if you go deep and test things out to the bone.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:07 am
by Eadwine Rose
Change the theme, does it stay blue?

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:17 am
by drogon69
Eadwine Rose wrote: Wed Oct 06, 2021 4:07 am Change the theme, does it stay blue?
9_9 i wonder if they testing the release of rc1 , from my looks they dont , if you see a bug in beta 1 , 2 and knwo rc is the same even samba share plugin under thunar is still not working and that is from beta 1 allready , ask the pro linux users they wil know that i am right
i have test rc1 on triple screen allready and i have never dump a distro so fast. ;)

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:19 am
by TOMCAT
Eadwine Rose wrote: Wed Oct 06, 2021 4:07 am Change the theme, does it stay blue?
Yes. Even if you change the theme the active window's border is always blue . It's especially obvious in the dark theme.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:30 am
by TOMCAT
drogon69 wrote: Wed Oct 06, 2021 4:17 am
Eadwine Rose wrote: Wed Oct 06, 2021 4:07 am Change the theme, does it stay blue?
9_9 i wonder if they testing the release of rc1 , from my looks they dont , if you see a bug in beta 1 , 2 and knwo rc is the same even samba share plugin under thunar is still not working and that is from beta 1 allready , ask the pro linux users they wil know that i am right
i have test rc1 on triple screen allready and i have never dump a distro so fast. ;)
Take it easy, we've got plenty of time.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:35 am
by Eadwine Rose
Tried in VB, changed themes in MX Tweak

greybird dark - gray
greybird mx - gray
mx dark - blue
mx dark thick borders - black
mx light - blue
mx light thick borders - blue
numix - black

Oh, did find something. The dropdown does not drop down under application - window manager - icons. I have to click that spot repeatedly to change the content (as in: it then rolls through the options).

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:51 am
by drogon69
Eadwine Rose wrote: Wed Oct 06, 2021 4:35 am Tried in VB, changed themes in MX Tweak

greybird dark - gray
greybird mx - gray
mx dark - blue
mx dark thick borders - black
mx light - blue
mx light thick borders - blue
numix - black

Oh, did find something. The dropdown does not drop down under application - window manager - icons. I have to click that spot repeatedly to change the content (as in: it then rolls through the options).
testing distro's in on real hardware not in virtualbox by the way 9_9

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:55 am
by Eadwine Rose
Thanks for the positive input :happy:

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 6:43 am
by dolphin_oracle
Eadwine Rose wrote: Wed Oct 06, 2021 4:35 am
Oh, did find something. The dropdown does not drop down under application - window manager - icons. I have to click that spot repeatedly to change the content (as in: it then rolls through the options).
I don't understand this comment. got a screenshot?

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 6:52 am
by Eadwine Rose
Oh.. now that is interesting.. I go back in MX Tweak to make a screenshot, and I am seeing windows with scrollbars underneath those three titles in the Theme tab. *scratches head* Crooked volt. ;)

I was seeing, instead of windows, only 1 line, with a little mini spot where I guess the scrollbar would have been, and clicking on that spot would make the options roll by one by one.


But yeah, no matter, glitch I guess.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 7:29 am
by thinkpadx
Dolpin Oracle: i assume that mx21 rc 1 will auto update to final version as it did in mx 19 when installed rc1? correct me if i am wrong.

and congrats and moving forward on this work as you devs have done!

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 8:38 am
by dolphin_oracle
thinkpadx wrote: Wed Oct 06, 2021 7:29 am Dolpin Oracle: i assume that mx21 rc 1 will auto update to final version as it did in mx 19 when installed rc1? correct me if i am wrong.

and congrats and moving forward on this work as you devs have done!
yes.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 9:00 am
by thinkpadx
thank you!

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 9:27 am
by gsm
Live XFCE RC1 system on a HP Mini 110.
After 10 minutes of no activity the screen is turned off. When resuming by moving the mouse a little, only the cursor returns, in a black screen. No reaction at mouse or keyboard buttons, except:
The rest can be recovered by Ctrl + Alt+F7 after pressing first e.g. Ctrl+Alt+F2

EDIT:
Same problem with the installed MX-21 RC1 system.
After resume only a moving mouse cursor. I need to do the trick with the key combinations to get back all the functionality.

Kernel 5.x does not support the RTL8101 Ethernet adapter: Connected but no Ethernet connection.
Also it would have been nice when a lower kernel version (e.g. 4.9) could be selected before or during the installation of MX-Linux.
This is because the 5.x kernels do not correctly support the RTL8101 Ethernet adapter of my very handy HP mini 110, which is unfortunately also a problem with many other distributions.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 9:27 am
by manyroads
FWIW. in MXPI, kernel 5.10 is mislabeled as 4.19

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 9:36 am
by fehlix
TOMCAT wrote: Wed Oct 06, 2021 3:24 am Switching the system-language (system-locales) does not update the name of the user folder.
Thanks.
Actually you would not need to switch system language, but just login with the chosen locale at the login screen.
A fix is identified and after some testing will be come soonish as an update... :snail:

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 9:53 am
by dolphin_oracle
manyroads wrote: Wed Oct 06, 2021 9:27 am FWIW. in MXPI, kernel 5.10 is mislabeled as 4.19
nice catch thanks.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 10:34 am
by markol
I preferer KDE edition but this XFCE release is fantastic. Everything (and I really mean everything) worked out of the box except for some minor customization / fine tuning / OCD stuff :D

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 10:39 am
by SwampRabbit
@markol by everything working OOTB, do you mean hardware? Can you please explain a bit more what worked OOTB for you so we can tell what we need to sustain moving forward?
If its hardware, care to share your QSI please? Thanks!

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 11:50 am
by Sigi
OK, after installation and update/upgrade, size of MX21-RC1.vdi is 6.7 GiB. But, default VirtualBox HDD size for Linux Debian 64 Bit (my default) is 8 GiB, on keep this default, MX 21-RC1 installation fails oi my system (MX 19.4) at 4 % with msg "Failed to prepare required partitions. Increase e.g. to 10 GiB (dynamic alloc), brings installation to end. On both Beta MX 21 this did not happen.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 11:52 am
by bigbenaugust
I installed B2 and then did an update, not realizing that RC1 was out.

If that's at all the same as RC1, I was able to confirm that Thunar SMB is indeed functional, at least to our Synology NAS (using smb://user@host/share syntax). It prompts for workgroup and password , then connects. Like Thunar has done since practically forever.

Seems to me someone was asking for UEFI install feedback, and that works, too.

I may grab an RC1 image and reinstall to try some disk partitioning things.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 11:58 am
by dolphin_oracle
Sigi wrote: Wed Oct 06, 2021 11:50 am OK, after installation and update/upgrade, size of MX21-RC1.vdi is 6.7 GiB. But, default VirtualBox HDD size for Linux Debian 64 Bit (my default) is 8 GiB, on keep this default, MX 21-RC1 installation fails oi my system (MX 19.4) at 4 % with msg "Failed to prepare required partitions. Increase e.g. to 10 GiB (dynamic alloc), brings installation to end. On both Beta MX 21 this did not happen.
you are better off with the generic linux or linux/oracle than the debian presets. virtualbox doens't keep up with the times very well with those...

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 11:59 am
by manyroads
It's probably too late for this... but given my weird MX use, I wanted to install thunar & thunar's dropbox plugin. I noticed that thunar is not available on MXPI Popular Packages list. :frown: xfce4 is also not available in the Desktop Environments area. :eek: :(

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 12:05 pm
by Sigi
dolphin_oracle wrote: Wed Oct 06, 2021 11:58 am you are better off with the generic linux or linux/oracle than the debian presets. virtualbox doens't keep up with the times very well with those...
Thanks, didn't know this. Ok, there is the default disk size 12 GiB.. 9_9

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 2:03 pm
by Stuart_M
mx-installer 21.10.03 in MX-21 will not install if the swap size is edited.

I am installing MX-21_rc1 in a 250GB SSD that is completely unallocated. The ISO integrity checked okay with both (sha256 and signature).

The installation was successful using the Template for an encrypted system, accepting all the default settings for a 250GB SSD. The resulting partition sizes are:
  • sda1 256.0 MB
  • sda2 512.0 MB
  • sda3 224.1 GB
  • sda4 8.0 GB
Here is the problem. I used the same Template and conditions that produced the successful installation above, but made just one change - the swap size was changed. I tried four different sizes, all producing the same error.
  • 512MB
  • 1000MB
  • 2GB
  • no swap (the swap partition was removed with the installer)
At the 9% mark ("Creating encrypted volume: sda3") an error message appears "Failed to prepare required partitions". (Note that the error was at the 10% mark when installing without swap.)
Install 9% Error.png
Below are two minstall.log files after a failed installation. After each failed installation I rebooted to start fresh.



The below is the minstall.log file after a failed installation with a 2GB swap size:

Code: Select all

2021-10-06 12:52:16.220 DBG default: Installer version: 21.10.03
2021-10-06 12:52:16.337 DBG default: +++ void MInstall::startup() +++
2021-10-06 12:52:16.342 DBG default: check for remastered home demo folder: false
2021-10-06 12:52:16.342 DBG default: Exec #1: du -sb /live/aufs/boot
2021-10-06 12:52:16.398 DBG default: Exit #1: 0 QProcess::NormalExit
2021-10-06 12:52:16.398 DBG default: linuxfs file is at :  "/live/boot-dev/antiX/linuxfs"
2021-10-06 12:52:16.398 DBG default: Exec #2: dd if=/live/boot-dev/antiX/linuxfs bs=1 skip=20 count=2 status=none 2>/dev/null | od -An -tdI
2021-10-06 12:52:16.408 DBG default: Exit #2: 0 QProcess::NormalExit
2021-10-06 12:52:16.408 DBG default: linuxfs compression type is  "6" compression factor is  25
2021-10-06 12:52:16.408 DBG default: Exec #3: df /live/linux --output=used --total |tail -n1
2021-10-06 12:52:16.416 DBG default: Exit #3: 0 QProcess::NormalExit
2021-10-06 12:52:16.416 DBG default: linuxfs file size is  7312769024  rootfs file size is  0
2021-10-06 12:52:16.417 DBG default: Minimum space: 268435456 (boot), 8386510848 (root)
2021-10-06 12:52:16.417 DBG default: Exec #4: uname -m | grep -q i686
2021-10-06 12:52:16.423 DBG default: Exit #4: 1 QProcess::NormalExit
2021-10-06 12:52:16.423 DBG default: uefi = true
2021-10-06 12:52:16.423 DBG default: +++ void MInstall::setupAutoMount(bool) +++
2021-10-06 12:52:16.424 DBG default: Exec #5: ps -e | grep 'udisksd'
2021-10-06 12:52:16.443 DBG default: SOut #5: "   9459 ?        00:00:00 udisksd\n"
2021-10-06 12:52:16.443 DBG default: Exit #5: 0 QProcess::NormalExit
2021-10-06 12:52:16.443 DBG default: Exec #6: egrep -l '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d
2021-10-06 12:52:16.456 DBG default: SErr #6: "grep: /lib/udev/rules.d: Is a directory\n"
2021-10-06 12:52:16.456 DBG default: Exit #6: 2 QProcess::NormalExit
2021-10-06 12:52:16.456 DBG default: Exec #7: systemctl list-units --full --all -t mount --no-legend 2>/dev/null | grep -v masked | cut -f1 -d' ' | egrep -v '^(dev-hugepages|dev-mqueue|proc-sys-fs-binfmt_misc|run-user-.*-gvfs|sys-fs-fuse-connections|sys-kernel-config|sys-kernel-debug)'
2021-10-06 12:52:16.465 DBG default: Exit #7: 1 QProcess::NormalExit
2021-10-06 12:52:16.466 DBG default: MkPath(SUCCESS): "/run/udev/rules.d"
2021-10-06 12:52:16.466 DBG default: Exec #8: echo 'SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1"' > /run/udev/rules.d/91-mx-udisks-inhibit.rules
2021-10-06 12:52:16.471 DBG default: Exit #8: 0 QProcess::NormalExit
2021-10-06 12:52:16.471 DBG default: Exec #9: udevadm control --reload
2021-10-06 12:52:16.480 DBG default: Exit #9: 0 QProcess::NormalExit
2021-10-06 12:52:16.480 DBG default: Exec #10: udevadm trigger --subsystem-match=block
2021-10-06 12:52:16.490 DBG default: Exit #10: 0 QProcess::NormalExit
2021-10-06 12:52:16.490 DBG default: Exec #11: /bin/ls -1 /home | grep -Ev '(lost\+found|demo|snapshot)' | grep -q [a-zA-Z0-9]
2021-10-06 12:52:16.498 DBG default: Exit #11: 1 QProcess::NormalExit
2021-10-06 12:52:16.498 DBG default: check for possible snapshot: false
2021-10-06 12:52:16.561 DBG default: +++ void MInstall::setupkeyboardbutton() +++
2021-10-06 12:52:16.562 DBG default: Exec #12: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
2021-10-06 12:52:16.573 DBG default: Exit #12: 0 QProcess::NormalExit
2021-10-06 12:52:16.575 DBG default: Exec #13: locale -a | grep -Ev '^(C|POSIX)\.?' | grep -E 'utf8|UTF-8'
2021-10-06 12:52:16.583 DBG default: Exit #13: 0 QProcess::NormalExit
2021-10-06 12:52:16.584 DBG default: Exec #14: grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus
2021-10-06 12:52:16.652 DBG default: Exit #14: 1 QProcess::NormalExit
2021-10-06 12:52:16.652 DBG default: Exec #15: dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'
2021-10-06 12:52:16.682 DBG default: Exit #15: 0 QProcess::NormalExit
2021-10-06 12:52:16.682 DBG default: +++ void MInstall::buildServiceList() +++
2021-10-06 12:52:16.689 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 12:52:16.690 DBG default: Exec #16: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 12:52:16.703 DBG default: Exit #16: 0 QProcess::NormalExit
2021-10-06 12:52:16.703 DBG default: Exec #17: partprobe -s
2021-10-06 12:52:16.837 DBG default: SOut #17: "/dev/sda: gpt partitions 1 2 3 4\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:52:16.837 DBG default: Exit #17: 0 QProcess::NormalExit
2021-10-06 12:52:16.837 DBG default: Exec #18: blkid -c /dev/null
2021-10-06 12:52:16.877 DBG default: SOut #18: "/dev/sda1: LABEL_FATBOOT=\"EFI System\" LABEL=\"EFI System\" UUID=\"3213-3F0E\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTLABEL=\"primary\" PARTUUID=\"b6cb2e10-f793-4490-9e81-9c8b8c20c89e\"\n/dev/sda2: LABEL=\"boot\" UUID=\"5a269835-0830-44d2-b214-5156592c74fb\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTLABEL=\"primary\" PARTUUID=\"bda2eb7a-ead9-41a9-bc2c-31b28c620246\"\n/dev/sda3: UUID=\"3b4dbee4-1427-4894-8f3a-c71ae8b47122\" TYPE=\"crypto_LUKS\" PARTLABEL=\"primary\" PARTUUID=\"0a3ae745-f740-426f-a021-0ea6d42bb25f\"\n/dev/sda4: UUID=\"fa6d9afe-8c56-45d3-95f9-090c0ebd3088\" TYPE=\"crypto_LUKS\" PARTLABEL=\"primary\" PARTUUID=\"0b806862-b50e-40ab-abbc-e280f8cedbae\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 12:52:16.877 DBG default: Exit #18: 0 QProcess::NormalExit
2021-10-06 12:52:16.877 DBG default: Exec #19: parted -lm
2021-10-06 12:52:16.915 DBG default: Exit #19: 0 QProcess::NormalExit
2021-10-06 12:52:16.916 DBG default: Exec #20: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 12:52:16.925 DBG default: Exit #20: 32 QProcess::NormalExit
2021-10-06 12:52:21.989 DBG default: Exec #21: /usr/sbin/gparted
2021-10-06 12:52:34.405 DBG default: SOut #21: "GParted 1.2.0\nconfiguration --enable-libparted-dmraid --enable-online-resize\nlibparted 3.4\n"
2021-10-06 12:52:34.405 DBG default: Exit #21: 0 QProcess::NormalExit
2021-10-06 12:52:34.405 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 12:52:34.407 DBG default: Exec #22: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 12:52:34.415 DBG default: Exit #22: 0 QProcess::NormalExit
2021-10-06 12:52:34.415 DBG default: Exec #23: partprobe -s
2021-10-06 12:52:34.529 DBG default: SOut #23: "/dev/sda: gpt partitions\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:52:34.529 DBG default: Exit #23: 0 QProcess::NormalExit
2021-10-06 12:52:34.529 DBG default: Exec #24: blkid -c /dev/null
2021-10-06 12:52:34.569 DBG default: SOut #24: "/dev/sda: PTUUID=\"4ca2c105-553d-4a8b-b88b-6c1fff6b56a9\" PTTYPE=\"gpt\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 12:52:34.569 DBG default: Exit #24: 0 QProcess::NormalExit
2021-10-06 12:52:34.569 DBG default: Exec #25: parted -lm
2021-10-06 12:52:34.607 DBG default: Exit #25: 0 QProcess::NormalExit
2021-10-06 12:52:34.607 DBG default: Exec #26: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 12:52:34.617 DBG default: Exit #26: 32 QProcess::NormalExit
2021-10-06 12:53:13.967 DBG default: Mount points:
2021-10-06 12:53:13.968 DBG default:  - "/" - "sda3" "root.fsm" "/dev/mapper/root.fsm"
2021-10-06 12:53:13.968 DBG default:  - "/boot" - "sda2" "sda2" "/dev/sda2"
2021-10-06 12:53:13.968 DBG default:  - "SWAP" - "sda4" "swap" "/dev/mapper/swap"
2021-10-06 12:53:15.383 DBG default: +++ bool MInstall::saveHomeBasic() +++
2021-10-06 12:53:15.393 WRN qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2822, resource id: 18885531, major code: 40 (TranslateCoords), minor code: 0
2021-10-06 12:53:15.420 DBG default: - Preparing to install MX Linux -
2021-10-06 12:53:15.422 DBG default: Exec #27: smartctl -H /dev/sda
2021-10-06 12:53:15.456 DBG default: SOut #27: "smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-8-amd64] (local build)\nCopyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org\n\n=== START OF READ SMART DATA SECTION ===\nSMART overall-health self-assessment test result: PASSED\n\n"
2021-10-06 12:53:15.456 DBG default: Exit #27: 0 QProcess::NormalExit
2021-10-06 12:53:15.456 DBG default: Exec #28: smartctl -A /dev/sda| grep -E "^  5|^196|^197|^198" | awk '{ if ( $10 != 0 ) { print $1,$2,$10} }'
2021-10-06 12:53:15.484 DBG default: Exit #28: 0 QProcess::NormalExit
2021-10-06 12:53:15.484 DBG default: +++ void MInstall::cleanup(bool) +++
2021-10-06 12:53:15.487 DBG default: Exec #29: /bin/umount -l /mnt/antiX/boot/efi
2021-10-06 12:53:15.497 DBG default: SErr #29: "umount: /mnt/antiX/boot/efi: no mount point specified.\n"
2021-10-06 12:53:15.498 DBG default: Exit #29: 32 QProcess::NormalExit
2021-10-06 12:53:15.498 DBG default: Exec #30: /bin/umount -l /mnt/antiX/proc
2021-10-06 12:53:15.507 DBG default: SErr #30: "umount: /mnt/antiX/proc: no mount point specified.\n"
2021-10-06 12:53:15.507 DBG default: Exit #30: 32 QProcess::NormalExit
2021-10-06 12:53:15.507 DBG default: Exec #31: /bin/umount -l /mnt/antiX/sys
2021-10-06 12:53:15.516 DBG default: SErr #31: "umount: /mnt/antiX/sys: no mount point specified.\n"
2021-10-06 12:53:15.516 DBG default: Exit #31: 32 QProcess::NormalExit
2021-10-06 12:53:15.516 DBG default: Exec #32: /bin/umount -l /mnt/antiX/dev/shm
2021-10-06 12:53:15.523 DBG default: SErr #32: "umount: /mnt/antiX/dev/shm: no mount point specified.\n"
2021-10-06 12:53:15.523 DBG default: Exit #32: 32 QProcess::NormalExit
2021-10-06 12:53:15.523 DBG default: Exec #33: /bin/umount -l /mnt/antiX/dev
2021-10-06 12:53:15.532 DBG default: SErr #33: "umount: /mnt/antiX/dev: no mount point specified.\n"
2021-10-06 12:53:15.532 DBG default: Exit #33: 32 QProcess::NormalExit
2021-10-06 12:53:15.532 DBG default: Exec #34: swapoff /dev/sda2
2021-10-06 12:53:15.543 DBG default: SErr #34: "swapoff: /dev/sda2: swapoff failed: No such file or directory\n"
2021-10-06 12:53:15.543 DBG default: Exit #34: 4 QProcess::NormalExit
2021-10-06 12:53:15.543 DBG default: Exec #35: /bin/umount -l /mnt/antiX/boot
2021-10-06 12:53:15.553 DBG default: SErr #35: "umount: /mnt/antiX/boot: no mount point specified.\n"
2021-10-06 12:53:15.553 DBG default: Exit #35: 32 QProcess::NormalExit
2021-10-06 12:53:15.553 DBG default: Exec #36: swapoff /dev/mapper/root.fsm
2021-10-06 12:53:15.562 DBG default: SErr #36: "swapoff: /dev/mapper/root.fsm: swapoff failed: No such file or directory\n"
2021-10-06 12:53:15.562 DBG default: Exit #36: 4 QProcess::NormalExit
2021-10-06 12:53:15.562 DBG default: Exec #37: /bin/umount -l /mnt/antiX/
2021-10-06 12:53:15.570 DBG default: SErr #37: "umount: /mnt/antiX/: no mount point specified.\n"
2021-10-06 12:53:15.571 DBG default: Exit #37: 32 QProcess::NormalExit
2021-10-06 12:53:15.571 DBG default: Exec #38: cryptsetup close /dev/mapper/root.fsm
2021-10-06 12:53:15.786 DBG default: SErr #38: "Device /dev/mapper/root.fsm is not active.\n"
2021-10-06 12:53:15.786 DBG default: Exit #38: 4 QProcess::NormalExit
2021-10-06 12:53:15.786 DBG default: +++ bool PartMan::preparePartitions() +++
2021-10-06 12:53:15.789 DBG default: Exec #39: lsblk -nro name /dev/sda
2021-10-06 12:53:15.798 DBG default: Exit #39: 0 QProcess::NormalExit
2021-10-06 12:53:15.798 DBG default: Exec #40: swapoff /dev/sda
2021-10-06 12:53:15.805 DBG default: SErr #40: "swapoff: /dev/sda: swapoff failed: Invalid argument\n"
2021-10-06 12:53:15.805 DBG default: Exit #40: 4 QProcess::NormalExit
2021-10-06 12:53:15.806 DBG default: Exec #41: /bin/umount /dev/sda
2021-10-06 12:53:15.814 DBG default: SErr #41: "umount: /dev/sda: not mounted.\n"
2021-10-06 12:53:15.814 DBG default: Exit #41: 32 QProcess::NormalExit
2021-10-06 12:53:15.814 DBG default: - Preparing partition tables -
2021-10-06 12:53:15.818 DBG default: Exec #42: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda
2021-10-06 12:53:15.831 DBG default: SErr #42: "64+0 records in\n64+0 records out\n4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.00343248 s, 1.2 GB/s\n"
2021-10-06 12:53:15.831 DBG default: Exit #42: 0 QProcess::NormalExit
2021-10-06 12:53:15.831 DBG default: Exec #43: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda seek=3815539
2021-10-06 12:53:15.839 DBG default: SErr #43: "dd: error writing '/dev/sda': No space left on device\n64+0 records in\n63+0 records out\n4186112 bytes (4.2 MB, 4.0 MiB) copied, 0.00186469 s, 2.2 GB/s\n"
2021-10-06 12:53:15.839 DBG default: Exit #43: 1 QProcess::NormalExit
2021-10-06 12:53:15.839 DBG default: Exec #44: parted -s /dev/sda mklabel gpt
2021-10-06 12:53:15.905 DBG default: Exit #44: 0 QProcess::NormalExit
2021-10-06 12:53:15.905 DBG default: - Preparing required partitions -
2021-10-06 12:53:15.910 DBG default: Exec #45: parted -s --align optimal /dev/sda mkpart primary 1MiB 257MiB
2021-10-06 12:53:15.965 DBG default: Exit #45: 0 QProcess::NormalExit
2021-10-06 12:53:15.969 DBG default: Exec #46: parted -s --align optimal /dev/sda mkpart primary 257MiB 769MiB
2021-10-06 12:53:16.045 DBG default: Exit #46: 0 QProcess::NormalExit
2021-10-06 12:53:16.049 DBG default: Exec #47: parted -s --align optimal /dev/sda mkpart primary 769MiB 230276MiB
2021-10-06 12:53:16.125 DBG default: Exit #47: 0 QProcess::NormalExit
2021-10-06 12:53:16.128 DBG default: Exec #48: parted -s --align optimal /dev/sda mkpart primary 230276MiB 232276MiB
2021-10-06 12:53:16.205 DBG default: Exit #48: 0 QProcess::NormalExit
2021-10-06 12:53:16.209 DBG default: Exec #49: parted -s /dev/sda set 2 legacy_boot on
2021-10-06 12:53:16.285 DBG default: Exit #49: 0 QProcess::NormalExit
2021-10-06 12:53:16.296 DBG default: Exec #50: partprobe -s
2021-10-06 12:53:16.429 DBG default: SOut #50: "/dev/sda: gpt partitions 1 2 3 4\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:53:16.429 DBG default: Exit #50: 0 QProcess::NormalExit
2021-10-06 12:53:16.429 DBG default: +++ bool PartMan::formatPartitions() +++
2021-10-06 12:53:16.433 DBG default: - Formatting: EFI System Partition -
2021-10-06 12:53:16.438 DBG default: Exec #51: mkfs.msdos -F 32 -n "EFI System" /dev/sda1
2021-10-06 12:53:16.497 DBG default: SOut #51: "mkfs.fat 4.2 (2021-01-31)\n"
2021-10-06 12:53:16.497 DBG default: SErr #51: "mkfs.fat: Warning: lowercase labels might not work properly on some systems\n"
2021-10-06 12:53:16.497 DBG default: Exit #51: 0 QProcess::NormalExit
2021-10-06 12:53:16.498 DBG default: Exec #52: parted -s /dev/sda set 1 esp on
2021-10-06 12:53:16.641 DBG default: Exit #52: 0 QProcess::NormalExit
2021-10-06 12:53:16.641 DBG default: - Formatting: /boot -
2021-10-06 12:53:16.646 DBG default: Exec #53: mkfs.ext4 -F /dev/sda2 -L "boot"
2021-10-06 12:53:16.713 DBG default: SOut #53: "Discarding device blocks:   4096/131072\b\b\b\b\b\b\b\b\b\b\b\b\b             \b\b\b\b\b\b\b\b\b\b\b\b\bdone                            \nCreating filesystem with 131072 4k blocks and 32768 inodes\nFilesystem UUID: ad312201-fcc2-4d65-8fb9-592efeab0748\nSuperblock backups stored on blocks: \n\t32768, 98304\n\nAllocating group tables: 0/4\b\b\b   \b\b\bdone                            \nWriting inode tables: 0/4\b\b\b   \b\b\bdone                            \nCreating journal (4096 blocks): done\nWriting superblocks and filesystem accounting information: 0/4\b\b\b   \b\b\bdone\n\n"
2021-10-06 12:53:16.713 DBG default: SErr #53: "mke2fs 1.46.2 (28-Feb-2021)\n"
2021-10-06 12:53:16.713 DBG default: Exit #53: 0 QProcess::NormalExit
2021-10-06 12:53:16.713 DBG default: Exec #54: /sbin/tune2fs -c0 -C0 -i1m /dev/sda2
2021-10-06 12:53:16.729 DBG default: SOut #54: "tune2fs 1.46.2 (28-Feb-2021)\nSetting maximal mount count to -1\nSetting current mount count to 0\nSetting interval between checks to 2592000 seconds\n"
2021-10-06 12:53:16.729 DBG default: Exit #54: 0 QProcess::NormalExit
2021-10-06 12:53:16.729 DBG default: - Creating encrypted volume: sda3 -
2021-10-06 12:53:16.738 DBG default: Exec #55: cryptsetup --batch-mode --key-size 512 --hash sha512 --pbkdf argon2id --sector-size=1358828544 luksFormat /dev/sda3
2021-10-06 12:53:16.747 DBG default: SErr #55: "Usage: cryptsetup [-?Vvyrq] [-?|--help] [--usage] [-V|--version]\n        [-v|--verbose] [--debug] [--debug-json] [-c|--cipher=STRING]\n        [-h|--hash=STRING] [-y|--verify-passphrase] [-d|--key-file=STRING]\n        [--master-key-file=STRING] [--dump-master-key] [-s|--key-size=BITS]\n        [-l|--keyfile-size=bytes] [--keyfile-offset=bytes]\n        [--new-keyfile-size=bytes] [--new-keyfile-offset=bytes]\n        [-S|--key-slot=INT] [-b|--size=SECTORS] [--device-size=bytes]\n        [-o|--offset=SECTORS] [-p|--skip=SECTORS] [-r|--readonly]\n        [-q|--batch-mode] [-t|--timeout=secs] [--progress-frequency=secs]\n        [-T|--tries=INT] [--align-payload=SECTORS]\n        [--header-backup-file=STRING] [--use-random] [--use-urandom]\n        [--shared] [--uuid=STRING] [--allow-discards] [--header=STRING]\n        [--test-passphrase] [--tcrypt-hidden] [--tcrypt-system]\n        [--tcrypt-backup] [--veracrypt] [--veracrypt-pim=INT]\n        [--veracrypt-query-pim] [-M|--type=STRING] [--force-password]\n        [--perf-same_cpu_crypt] [--perf-submit_from_crypt_cpus]\n        [--perf-no_read_workqueue] [--perf-no_write_workqueue] [--deferred]\n        [--serialize-memory-hard-pbkdf] [-i|--iter-time=msecs]\n        [--pbkdf=STRING] [--pbkdf-memory=kilobytes]\n        [--pbkdf-parallel=threads] [--pbkdf-force-iterations=LONG]\n        [--priority=STRING] [--disable-locks] [--disable-keyring]\n        [-I|--integrity=STRING] [--integrity-no-journal]\n        [--integrity-no-wipe] [--integrity-legacy-padding] [--token-only]\n        [--token-id=INT] [--key-description=STRING] [--sector-size=INT]\n        [--iv-large-sectors] [--persistent] [--label=STRING]\n        [--subsystem=STRING] [--unbound] [--json-file=STRING]\n        [--luks2-metadata-size=bytes] [--luks2-keyslots-size=bytes]\n        [--refresh] [--keyslot-key-size=BITS] [--keyslot-cipher=STRING]\n        [--encrypt] [--decrypt] [--init-only] [--resume-only]\n        [--reduce-device-size=bytes] [--hotzone-size=bytes]\n        [--resilience=STRING] [--resilience-hash=STRING]\n        [--active-name=STRING] [OPTION...] <action> <action-specific>\n/usr/sbin/cryptsetup: Unsupported encryption sector size.\n"
2021-10-06 12:53:16.747 DBG default: Exit #55: 1 QProcess::NormalExit
2021-10-06 12:53:16.747 DBG default: +++ void MInstall::failUI(const QString&) +++
2021-10-06 12:53:16.750 DBG default: Phase 1 - "Failed to prepare required partitions."


The below is the minstall.log file after a failed installation without swap:

Code: Select all

2021-10-06 12:59:50.284 DBG default: Installer version: 21.10.03
2021-10-06 12:59:50.395 DBG default: +++ void MInstall::startup() +++
2021-10-06 12:59:50.399 DBG default: check for remastered home demo folder: false
2021-10-06 12:59:50.399 DBG default: Exec #1: du -sb /live/aufs/boot
2021-10-06 12:59:50.452 DBG default: Exit #1: 0 QProcess::NormalExit
2021-10-06 12:59:50.452 DBG default: linuxfs file is at :  "/live/boot-dev/antiX/linuxfs"
2021-10-06 12:59:50.452 DBG default: Exec #2: dd if=/live/boot-dev/antiX/linuxfs bs=1 skip=20 count=2 status=none 2>/dev/null | od -An -tdI
2021-10-06 12:59:50.462 DBG default: Exit #2: 0 QProcess::NormalExit
2021-10-06 12:59:50.462 DBG default: linuxfs compression type is  "6" compression factor is  25
2021-10-06 12:59:50.463 DBG default: Exec #3: df /live/linux --output=used --total |tail -n1
2021-10-06 12:59:50.470 DBG default: Exit #3: 0 QProcess::NormalExit
2021-10-06 12:59:50.471 DBG default: linuxfs file size is  7312769024  rootfs file size is  0
2021-10-06 12:59:50.471 DBG default: Minimum space: 268435456 (boot), 8386510848 (root)
2021-10-06 12:59:50.471 DBG default: Exec #4: uname -m | grep -q i686
2021-10-06 12:59:50.478 DBG default: Exit #4: 1 QProcess::NormalExit
2021-10-06 12:59:50.478 DBG default: uefi = true
2021-10-06 12:59:50.478 DBG default: +++ void MInstall::setupAutoMount(bool) +++
2021-10-06 12:59:50.479 DBG default: Exec #5: ps -e | grep 'udisksd'
2021-10-06 12:59:50.493 DBG default: SOut #5: "   9366 ?        00:00:00 udisksd\n"
2021-10-06 12:59:50.493 DBG default: Exit #5: 0 QProcess::NormalExit
2021-10-06 12:59:50.493 DBG default: Exec #6: egrep -l '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d
2021-10-06 12:59:50.509 DBG default: SErr #6: "grep: /lib/udev/rules.d: Is a directory\n"
2021-10-06 12:59:50.509 DBG default: Exit #6: 2 QProcess::NormalExit
2021-10-06 12:59:50.509 DBG default: Exec #7: systemctl list-units --full --all -t mount --no-legend 2>/dev/null | grep -v masked | cut -f1 -d' ' | egrep -v '^(dev-hugepages|dev-mqueue|proc-sys-fs-binfmt_misc|run-user-.*-gvfs|sys-fs-fuse-connections|sys-kernel-config|sys-kernel-debug)'
2021-10-06 12:59:50.517 DBG default: Exit #7: 1 QProcess::NormalExit
2021-10-06 12:59:50.518 DBG default: MkPath(SUCCESS): "/run/udev/rules.d"
2021-10-06 12:59:50.518 DBG default: Exec #8: echo 'SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1"' > /run/udev/rules.d/91-mx-udisks-inhibit.rules
2021-10-06 12:59:50.522 DBG default: Exit #8: 0 QProcess::NormalExit
2021-10-06 12:59:50.522 DBG default: Exec #9: udevadm control --reload
2021-10-06 12:59:50.533 DBG default: Exit #9: 0 QProcess::NormalExit
2021-10-06 12:59:50.533 DBG default: Exec #10: udevadm trigger --subsystem-match=block
2021-10-06 12:59:50.542 DBG default: Exit #10: 0 QProcess::NormalExit
2021-10-06 12:59:50.542 DBG default: Exec #11: /bin/ls -1 /home | grep -Ev '(lost\+found|demo|snapshot)' | grep -q [a-zA-Z0-9]
2021-10-06 12:59:50.548 DBG default: Exit #11: 1 QProcess::NormalExit
2021-10-06 12:59:50.548 DBG default: check for possible snapshot: false
2021-10-06 12:59:50.606 DBG default: +++ void MInstall::setupkeyboardbutton() +++
2021-10-06 12:59:50.608 DBG default: Exec #12: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
2021-10-06 12:59:50.618 DBG default: Exit #12: 0 QProcess::NormalExit
2021-10-06 12:59:50.622 DBG default: Exec #13: locale -a | grep -Ev '^(C|POSIX)\.?' | grep -E 'utf8|UTF-8'
2021-10-06 12:59:50.633 DBG default: Exit #13: 0 QProcess::NormalExit
2021-10-06 12:59:50.634 DBG default: Exec #14: grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus
2021-10-06 12:59:50.702 DBG default: Exit #14: 1 QProcess::NormalExit
2021-10-06 12:59:50.702 DBG default: Exec #15: dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'
2021-10-06 12:59:50.730 DBG default: Exit #15: 0 QProcess::NormalExit
2021-10-06 12:59:50.730 DBG default: +++ void MInstall::buildServiceList() +++
2021-10-06 12:59:50.734 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 12:59:50.734 DBG default: Exec #16: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 12:59:50.747 DBG default: Exit #16: 0 QProcess::NormalExit
2021-10-06 12:59:50.748 DBG default: Exec #17: partprobe -s
2021-10-06 12:59:50.871 DBG default: SOut #17: "/dev/sda: gpt partitions 1 2 3\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:59:50.871 DBG default: Exit #17: 0 QProcess::NormalExit
2021-10-06 12:59:50.871 DBG default: Exec #18: blkid -c /dev/null
2021-10-06 12:59:50.911 DBG default: SOut #18: "/dev/sda1: LABEL_FATBOOT=\"EFI System\" LABEL=\"EFI System\" UUID=\"5916-AAC4\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTLABEL=\"primary\" PARTUUID=\"6523564d-16d9-4611-ad78-b3b42dad3449\"\n/dev/sda2: LABEL=\"boot\" UUID=\"1c1acc9d-b433-48ca-b650-620dd85eb9a4\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTLABEL=\"primary\" PARTUUID=\"2c957374-cb60-4f5e-b7be-c45ebdb2fb82\"\n/dev/sda3: UUID=\"3b4dbee4-1427-4894-8f3a-c71ae8b47122\" TYPE=\"crypto_LUKS\" PARTLABEL=\"primary\" PARTUUID=\"315647f8-f2ca-4e4a-a4b8-b761774acc54\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 12:59:50.911 DBG default: Exit #18: 0 QProcess::NormalExit
2021-10-06 12:59:50.911 DBG default: Exec #19: parted -lm
2021-10-06 12:59:50.961 DBG default: Exit #19: 0 QProcess::NormalExit
2021-10-06 12:59:50.961 DBG default: Exec #20: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 12:59:50.970 DBG default: Exit #20: 32 QProcess::NormalExit
2021-10-06 13:00:08.882 DBG default: Exec #21: /usr/sbin/gparted
2021-10-06 13:00:22.308 DBG default: SOut #21: "GParted 1.2.0\nconfiguration --enable-libparted-dmraid --enable-online-resize\nlibparted 3.4\n"
2021-10-06 13:00:22.308 DBG default: Exit #21: 0 QProcess::NormalExit
2021-10-06 13:00:22.308 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 13:00:22.310 DBG default: Exec #22: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 13:00:22.317 DBG default: Exit #22: 0 QProcess::NormalExit
2021-10-06 13:00:22.317 DBG default: Exec #23: partprobe -s
2021-10-06 13:00:22.407 DBG default: SOut #23: "/dev/sda: gpt partitions\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 13:00:22.407 DBG default: Exit #23: 0 QProcess::NormalExit
2021-10-06 13:00:22.407 DBG default: Exec #24: blkid -c /dev/null
2021-10-06 13:00:22.447 DBG default: SOut #24: "/dev/sda: PTUUID=\"2b9b6f10-a554-42f5-a3bc-95778e1afffa\" PTTYPE=\"gpt\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 13:00:22.447 DBG default: Exit #24: 0 QProcess::NormalExit
2021-10-06 13:00:22.447 DBG default: Exec #25: parted -lm
2021-10-06 13:00:22.482 DBG default: Exit #25: 0 QProcess::NormalExit
2021-10-06 13:00:22.482 DBG default: Exec #26: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 13:00:22.493 DBG default: Exit #26: 32 QProcess::NormalExit
2021-10-06 13:02:11.854 DBG default: Mount points:
2021-10-06 13:02:11.854 DBG default:  - "/" - "sda3" "root.fsm" "/dev/mapper/root.fsm"
2021-10-06 13:02:11.854 DBG default:  - "/boot" - "sda2" "sda2" "/dev/sda2"
2021-10-06 13:02:13.260 DBG default: +++ bool MInstall::saveHomeBasic() +++
2021-10-06 13:02:13.272 WRN qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4257, resource id: 18887372, major code: 40 (TranslateCoords), minor code: 0
2021-10-06 13:02:13.301 DBG default: - Preparing to install MX Linux -
2021-10-06 13:02:13.303 DBG default: Exec #27: smartctl -H /dev/sda
2021-10-06 13:02:13.339 DBG default: SOut #27: "smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-8-amd64] (local build)\nCopyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org\n\n=== START OF READ SMART DATA SECTION ===\nSMART overall-health self-assessment test result: PASSED\n\n"
2021-10-06 13:02:13.339 DBG default: Exit #27: 0 QProcess::NormalExit
2021-10-06 13:02:13.339 DBG default: Exec #28: smartctl -A /dev/sda| grep -E "^  5|^196|^197|^198" | awk '{ if ( $10 != 0 ) { print $1,$2,$10} }'
2021-10-06 13:02:13.367 DBG default: Exit #28: 0 QProcess::NormalExit
2021-10-06 13:02:13.367 DBG default: +++ void MInstall::cleanup(bool) +++
2021-10-06 13:02:13.368 DBG default: Exec #29: /bin/umount -l /mnt/antiX/boot/efi
2021-10-06 13:02:13.377 DBG default: SErr #29: "umount: /mnt/antiX/boot/efi: no mount point specified.\n"
2021-10-06 13:02:13.377 DBG default: Exit #29: 32 QProcess::NormalExit
2021-10-06 13:02:13.377 DBG default: Exec #30: /bin/umount -l /mnt/antiX/proc
2021-10-06 13:02:13.385 DBG default: SErr #30: "umount: /mnt/antiX/proc: no mount point specified.\n"
2021-10-06 13:02:13.385 DBG default: Exit #30: 32 QProcess::NormalExit
2021-10-06 13:02:13.385 DBG default: Exec #31: /bin/umount -l /mnt/antiX/sys
2021-10-06 13:02:13.393 DBG default: SErr #31: "umount: /mnt/antiX/sys: no mount point specified.\n"
2021-10-06 13:02:13.393 DBG default: Exit #31: 32 QProcess::NormalExit
2021-10-06 13:02:13.393 DBG default: Exec #32: /bin/umount -l /mnt/antiX/dev/shm
2021-10-06 13:02:13.401 DBG default: SErr #32: "umount: /mnt/antiX/dev/shm: no mount point specified.\n"
2021-10-06 13:02:13.401 DBG default: Exit #32: 32 QProcess::NormalExit
2021-10-06 13:02:13.401 DBG default: Exec #33: /bin/umount -l /mnt/antiX/dev
2021-10-06 13:02:13.408 DBG default: SErr #33: "umount: /mnt/antiX/dev: no mount point specified.\n"
2021-10-06 13:02:13.408 DBG default: Exit #33: 32 QProcess::NormalExit
2021-10-06 13:02:13.408 DBG default: Exec #34: swapoff /dev/sda2
2021-10-06 13:02:13.419 DBG default: SErr #34: "swapoff: /dev/sda2: swapoff failed: No such file or directory\n"
2021-10-06 13:02:13.419 DBG default: Exit #34: 4 QProcess::NormalExit
2021-10-06 13:02:13.419 DBG default: Exec #35: /bin/umount -l /mnt/antiX/boot
2021-10-06 13:02:13.428 DBG default: SErr #35: "umount: /mnt/antiX/boot: no mount point specified.\n"
2021-10-06 13:02:13.428 DBG default: Exit #35: 32 QProcess::NormalExit
2021-10-06 13:02:13.428 DBG default: Exec #36: swapoff /dev/mapper/root.fsm
2021-10-06 13:02:13.436 DBG default: SErr #36: "swapoff: /dev/mapper/root.fsm: swapoff failed: No such file or directory\n"
2021-10-06 13:02:13.436 DBG default: Exit #36: 4 QProcess::NormalExit
2021-10-06 13:02:13.436 DBG default: Exec #37: /bin/umount -l /mnt/antiX/
2021-10-06 13:02:13.446 DBG default: SErr #37: "umount: /mnt/antiX/: no mount point specified.\n"
2021-10-06 13:02:13.446 DBG default: Exit #37: 32 QProcess::NormalExit
2021-10-06 13:02:13.446 DBG default: Exec #38: cryptsetup close /dev/mapper/root.fsm
2021-10-06 13:02:13.674 DBG default: SErr #38: "Device /dev/mapper/root.fsm is not active.\n"
2021-10-06 13:02:13.674 DBG default: Exit #38: 4 QProcess::NormalExit
2021-10-06 13:02:13.674 DBG default: +++ bool PartMan::preparePartitions() +++
2021-10-06 13:02:13.677 DBG default: Exec #39: lsblk -nro name /dev/sda
2021-10-06 13:02:13.685 DBG default: Exit #39: 0 QProcess::NormalExit
2021-10-06 13:02:13.685 DBG default: Exec #40: swapoff /dev/sda
2021-10-06 13:02:13.692 DBG default: SErr #40: "swapoff: /dev/sda: swapoff failed: Invalid argument\n"
2021-10-06 13:02:13.693 DBG default: Exit #40: 4 QProcess::NormalExit
2021-10-06 13:02:13.693 DBG default: Exec #41: /bin/umount /dev/sda
2021-10-06 13:02:13.701 DBG default: SErr #41: "umount: /dev/sda: not mounted.\n"
2021-10-06 13:02:13.701 DBG default: Exit #41: 32 QProcess::NormalExit
2021-10-06 13:02:13.701 DBG default: - Preparing partition tables -
2021-10-06 13:02:13.705 DBG default: Exec #42: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda
2021-10-06 13:02:13.727 DBG default: SErr #42: "64+0 records in\n64+0 records out\n4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.012817 s, 327 MB/s\n"
2021-10-06 13:02:13.727 DBG default: Exit #42: 0 QProcess::NormalExit
2021-10-06 13:02:13.727 DBG default: Exec #43: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda seek=3815539
2021-10-06 13:02:13.739 DBG default: SErr #43: "dd: error writing '/dev/sda': No space left on device\n64+0 records in\n63+0 records out\n4186112 bytes (4.2 MB, 4.0 MiB) copied, 0.00190751 s, 2.2 GB/s\n"
2021-10-06 13:02:13.739 DBG default: Exit #43: 1 QProcess::NormalExit
2021-10-06 13:02:13.739 DBG default: Exec #44: parted -s /dev/sda mklabel gpt
2021-10-06 13:02:13.795 DBG default: Exit #44: 0 QProcess::NormalExit
2021-10-06 13:02:13.795 DBG default: - Preparing required partitions -
2021-10-06 13:02:13.802 DBG default: Exec #45: parted -s --align optimal /dev/sda mkpart primary 1MiB 257MiB
2021-10-06 13:02:13.855 DBG default: Exit #45: 0 QProcess::NormalExit
2021-10-06 13:02:13.859 DBG default: Exec #46: parted -s --align optimal /dev/sda mkpart primary 257MiB 769MiB
2021-10-06 13:02:13.931 DBG default: Exit #46: 0 QProcess::NormalExit
2021-10-06 13:02:13.935 DBG default: Exec #47: parted -s --align optimal /dev/sda mkpart primary 769MiB 238468MiB
2021-10-06 13:02:14.007 DBG default: Exit #47: 0 QProcess::NormalExit
2021-10-06 13:02:14.014 DBG default: Exec #48: parted -s /dev/sda set 2 legacy_boot on
2021-10-06 13:02:14.088 DBG default: Exit #48: 0 QProcess::NormalExit
2021-10-06 13:02:14.095 DBG default: Exec #49: partprobe -s
2021-10-06 13:02:14.219 DBG default: SOut #49: "/dev/sda: gpt partitions 1 2 3\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 13:02:14.219 DBG default: Exit #49: 0 QProcess::NormalExit
2021-10-06 13:02:14.219 DBG default: +++ bool PartMan::formatPartitions() +++
2021-10-06 13:02:14.223 DBG default: - Formatting: EFI System Partition -
2021-10-06 13:02:14.231 DBG default: Exec #50: mkfs.msdos -F 32 -n "EFI System" /dev/sda1
2021-10-06 13:02:14.295 DBG default: SOut #50: "mkfs.fat 4.2 (2021-01-31)\n"
2021-10-06 13:02:14.296 DBG default: SErr #50: "mkfs.fat: Warning: lowercase labels might not work properly on some systems\n"
2021-10-06 13:02:14.296 DBG default: Exit #50: 0 QProcess::NormalExit
2021-10-06 13:02:14.296 DBG default: Exec #51: parted -s /dev/sda set 1 esp on
2021-10-06 13:02:14.344 DBG default: Exit #51: 0 QProcess::NormalExit
2021-10-06 13:02:14.344 DBG default: - Formatting: /boot -
2021-10-06 13:02:14.351 DBG default: Exec #52: mkfs.ext4 -F /dev/sda2 -L "boot"
2021-10-06 13:02:14.423 DBG default: SOut #52: "Discarding device blocks:   4096/131072\b\b\b\b\b\b\b\b\b\b\b\b\b             \b\b\b\b\b\b\b\b\b\b\b\b\bdone                            \nCreating filesystem with 131072 4k blocks and 32768 inodes\nFilesystem UUID: 153d3647-0d8e-4d59-9f41-0e4799cdfc32\nSuperblock backups stored on blocks: \n\t32768, 98304\n\nAllocating group tables: 0/4\b\b\b   \b\b\bdone                            \nWriting inode tables: 0/4\b\b\b   \b\b\bdone                            \nCreating journal (4096 blocks): done\nWriting superblocks and filesystem accounting information: 0/4\b\b\b   \b\b\bdone\n\n"
2021-10-06 13:02:14.423 DBG default: SErr #52: "mke2fs 1.46.2 (28-Feb-2021)\n"
2021-10-06 13:02:14.423 DBG default: Exit #52: 0 QProcess::NormalExit
2021-10-06 13:02:14.423 DBG default: Exec #53: /sbin/tune2fs -c0 -C0 -i1m /dev/sda2
2021-10-06 13:02:14.439 DBG default: SOut #53: "tune2fs 1.46.2 (28-Feb-2021)\nSetting maximal mount count to -1\nSetting current mount count to 0\nSetting interval between checks to 2592000 seconds\n"
2021-10-06 13:02:14.439 DBG default: Exit #53: 0 QProcess::NormalExit
2021-10-06 13:02:14.439 DBG default: - Creating encrypted volume: sda3 -
2021-10-06 13:02:14.446 DBG default: Exec #54: cryptsetup --batch-mode --key-size 512 --hash sha512 --pbkdf argon2id --sector-size=353437696 luksFormat /dev/sda3
2021-10-06 13:02:14.457 DBG default: SErr #54: "Usage: cryptsetup [-?Vvyrq] [-?|--help] [--usage] [-V|--version]\n        [-v|--verbose] [--debug] [--debug-json] [-c|--cipher=STRING]\n        [-h|--hash=STRING] [-y|--verify-passphrase] [-d|--key-file=STRING]\n        [--master-key-file=STRING] [--dump-master-key] [-s|--key-size=BITS]\n        [-l|--keyfile-size=bytes] [--keyfile-offset=bytes]\n        [--new-keyfile-size=bytes] [--new-keyfile-offset=bytes]\n        [-S|--key-slot=INT] [-b|--size=SECTORS] [--device-size=bytes]\n        [-o|--offset=SECTORS] [-p|--skip=SECTORS] [-r|--readonly]\n        [-q|--batch-mode] [-t|--timeout=secs] [--progress-frequency=secs]\n        [-T|--tries=INT] [--align-payload=SECTORS]\n        [--header-backup-file=STRING] [--use-random] [--use-urandom]\n        [--shared] [--uuid=STRING] [--allow-discards] [--header=STRING]\n        [--test-passphrase] [--tcrypt-hidden] [--tcrypt-system]\n        [--tcrypt-backup] [--veracrypt] [--veracrypt-pim=INT]\n        [--veracrypt-query-pim] [-M|--type=STRING] [--force-password]\n        [--perf-same_cpu_crypt] [--perf-submit_from_crypt_cpus]\n        [--perf-no_read_workqueue] [--perf-no_write_workqueue] [--deferred]\n        [--serialize-memory-hard-pbkdf] [-i|--iter-time=msecs]\n        [--pbkdf=STRING] [--pbkdf-memory=kilobytes]\n        [--pbkdf-parallel=threads] [--pbkdf-force-iterations=LONG]\n        [--priority=STRING] [--disable-locks] [--disable-keyring]\n        [-I|--integrity=STRING] [--integrity-no-journal]\n        [--integrity-no-wipe] [--integrity-legacy-padding] [--token-only]\n        [--token-id=INT] [--key-description=STRING] [--sector-size=INT]\n        [--iv-large-sectors] [--persistent] [--label=STRING]\n        [--subsystem=STRING] [--unbound] [--json-file=STRING]\n        [--luks2-metadata-size=bytes] [--luks2-keyslots-size=bytes]\n        [--refresh] [--keyslot-key-size=BITS] [--keyslot-cipher=STRING]\n        [--encrypt] [--decrypt] [--init-only] [--resume-only]\n        [--reduce-device-size=bytes] [--hotzone-size=bytes]\n        [--resilience=STRING] [--resilience-hash=STRING]\n        [--active-name=STRING] [OPTION...] <action> <action-specific>\n/usr/sbin/cryptsetup: Unsupported encryption sector size.\n"
2021-10-06 13:02:14.457 DBG default: Exit #54: 1 QProcess::NormalExit
2021-10-06 13:02:14.457 DBG default: +++ void MInstall::failUI(const QString&) +++
2021-10-06 13:02:14.463 DBG default: Phase 1 - "Failed to prepare required partitions."
By the way, MX-21_beta2 installed fine.

Edit1 (6 October 2021): About an hour after I posted this I did a short test using mx-installer 21.10.04 to install using 512 MB of swap and the problem remains (that is the latest version as of this posting).

Edit2 (8 October 2021): I made a successful installation without any swap by eliminating the swap partition with the installer. Even though I did not test the other swap sizes mentioned above, I presume the problem was resolved with mx-installer 21.10.05 (dolphin_oracle said he though the issue was was found (viewtopic.php?p=655964#p655964)).

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 2:10 pm
by dolphin_oracle
Stuart_M wrote: Wed Oct 06, 2021 2:03 pm mx-installer 21.10.03 in MX-21 will not install if the swap size is edited.

I am installing MX-21_rc1 in a 250GB SSD that is completely unallocated. The ISO integrity checked okay with both (sha256 and signature).

The installation was successful using the Template for an encrypted system, accepting all the default settings for a 250GB SSD. The resulting partition sizes are:
  • sda1 256.0 MB
  • sda2 512.0 MB
  • sda3 224.1 GB
  • sda4 8.0 GB
Here is the problem. I used the same Template and conditions that produced the successful installation above, but made just one change - the swap size was changed. I tried four different sizes, all producing the same error.
  • 512MB
  • 1000MB
  • 2GB
  • no swap (the swap partition was removed with the installer)
At the 9% mark ("Creating encrypted volume: sda3") an error message appears "Failed to prepare required partitions". (Note that the error was at the 10% mark when installing without swap.)Install 9% Error.png

Below are two minstall.log files after a failed installation. After each failed installation I rebooted to start fresh.



The below is the minstall.log file after a failed installation with a 2GB swap size:

Code: Select all

2021-10-06 12:52:16.220 DBG default: Installer version: 21.10.03
2021-10-06 12:52:16.337 DBG default: +++ void MInstall::startup() +++
2021-10-06 12:52:16.342 DBG default: check for remastered home demo folder: false
2021-10-06 12:52:16.342 DBG default: Exec #1: du -sb /live/aufs/boot
2021-10-06 12:52:16.398 DBG default: Exit #1: 0 QProcess::NormalExit
2021-10-06 12:52:16.398 DBG default: linuxfs file is at :  "/live/boot-dev/antiX/linuxfs"
2021-10-06 12:52:16.398 DBG default: Exec #2: dd if=/live/boot-dev/antiX/linuxfs bs=1 skip=20 count=2 status=none 2>/dev/null | od -An -tdI
2021-10-06 12:52:16.408 DBG default: Exit #2: 0 QProcess::NormalExit
2021-10-06 12:52:16.408 DBG default: linuxfs compression type is  "6" compression factor is  25
2021-10-06 12:52:16.408 DBG default: Exec #3: df /live/linux --output=used --total |tail -n1
2021-10-06 12:52:16.416 DBG default: Exit #3: 0 QProcess::NormalExit
2021-10-06 12:52:16.416 DBG default: linuxfs file size is  7312769024  rootfs file size is  0
2021-10-06 12:52:16.417 DBG default: Minimum space: 268435456 (boot), 8386510848 (root)
2021-10-06 12:52:16.417 DBG default: Exec #4: uname -m | grep -q i686
2021-10-06 12:52:16.423 DBG default: Exit #4: 1 QProcess::NormalExit
2021-10-06 12:52:16.423 DBG default: uefi = true
2021-10-06 12:52:16.423 DBG default: +++ void MInstall::setupAutoMount(bool) +++
2021-10-06 12:52:16.424 DBG default: Exec #5: ps -e | grep 'udisksd'
2021-10-06 12:52:16.443 DBG default: SOut #5: "   9459 ?        00:00:00 udisksd\n"
2021-10-06 12:52:16.443 DBG default: Exit #5: 0 QProcess::NormalExit
2021-10-06 12:52:16.443 DBG default: Exec #6: egrep -l '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d
2021-10-06 12:52:16.456 DBG default: SErr #6: "grep: /lib/udev/rules.d: Is a directory\n"
2021-10-06 12:52:16.456 DBG default: Exit #6: 2 QProcess::NormalExit
2021-10-06 12:52:16.456 DBG default: Exec #7: systemctl list-units --full --all -t mount --no-legend 2>/dev/null | grep -v masked | cut -f1 -d' ' | egrep -v '^(dev-hugepages|dev-mqueue|proc-sys-fs-binfmt_misc|run-user-.*-gvfs|sys-fs-fuse-connections|sys-kernel-config|sys-kernel-debug)'
2021-10-06 12:52:16.465 DBG default: Exit #7: 1 QProcess::NormalExit
2021-10-06 12:52:16.466 DBG default: MkPath(SUCCESS): "/run/udev/rules.d"
2021-10-06 12:52:16.466 DBG default: Exec #8: echo 'SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1"' > /run/udev/rules.d/91-mx-udisks-inhibit.rules
2021-10-06 12:52:16.471 DBG default: Exit #8: 0 QProcess::NormalExit
2021-10-06 12:52:16.471 DBG default: Exec #9: udevadm control --reload
2021-10-06 12:52:16.480 DBG default: Exit #9: 0 QProcess::NormalExit
2021-10-06 12:52:16.480 DBG default: Exec #10: udevadm trigger --subsystem-match=block
2021-10-06 12:52:16.490 DBG default: Exit #10: 0 QProcess::NormalExit
2021-10-06 12:52:16.490 DBG default: Exec #11: /bin/ls -1 /home | grep -Ev '(lost\+found|demo|snapshot)' | grep -q [a-zA-Z0-9]
2021-10-06 12:52:16.498 DBG default: Exit #11: 1 QProcess::NormalExit
2021-10-06 12:52:16.498 DBG default: check for possible snapshot: false
2021-10-06 12:52:16.561 DBG default: +++ void MInstall::setupkeyboardbutton() +++
2021-10-06 12:52:16.562 DBG default: Exec #12: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
2021-10-06 12:52:16.573 DBG default: Exit #12: 0 QProcess::NormalExit
2021-10-06 12:52:16.575 DBG default: Exec #13: locale -a | grep -Ev '^(C|POSIX)\.?' | grep -E 'utf8|UTF-8'
2021-10-06 12:52:16.583 DBG default: Exit #13: 0 QProcess::NormalExit
2021-10-06 12:52:16.584 DBG default: Exec #14: grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus
2021-10-06 12:52:16.652 DBG default: Exit #14: 1 QProcess::NormalExit
2021-10-06 12:52:16.652 DBG default: Exec #15: dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'
2021-10-06 12:52:16.682 DBG default: Exit #15: 0 QProcess::NormalExit
2021-10-06 12:52:16.682 DBG default: +++ void MInstall::buildServiceList() +++
2021-10-06 12:52:16.689 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 12:52:16.690 DBG default: Exec #16: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 12:52:16.703 DBG default: Exit #16: 0 QProcess::NormalExit
2021-10-06 12:52:16.703 DBG default: Exec #17: partprobe -s
2021-10-06 12:52:16.837 DBG default: SOut #17: "/dev/sda: gpt partitions 1 2 3 4\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:52:16.837 DBG default: Exit #17: 0 QProcess::NormalExit
2021-10-06 12:52:16.837 DBG default: Exec #18: blkid -c /dev/null
2021-10-06 12:52:16.877 DBG default: SOut #18: "/dev/sda1: LABEL_FATBOOT=\"EFI System\" LABEL=\"EFI System\" UUID=\"3213-3F0E\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTLABEL=\"primary\" PARTUUID=\"b6cb2e10-f793-4490-9e81-9c8b8c20c89e\"\n/dev/sda2: LABEL=\"boot\" UUID=\"5a269835-0830-44d2-b214-5156592c74fb\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTLABEL=\"primary\" PARTUUID=\"bda2eb7a-ead9-41a9-bc2c-31b28c620246\"\n/dev/sda3: UUID=\"3b4dbee4-1427-4894-8f3a-c71ae8b47122\" TYPE=\"crypto_LUKS\" PARTLABEL=\"primary\" PARTUUID=\"0a3ae745-f740-426f-a021-0ea6d42bb25f\"\n/dev/sda4: UUID=\"fa6d9afe-8c56-45d3-95f9-090c0ebd3088\" TYPE=\"crypto_LUKS\" PARTLABEL=\"primary\" PARTUUID=\"0b806862-b50e-40ab-abbc-e280f8cedbae\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 12:52:16.877 DBG default: Exit #18: 0 QProcess::NormalExit
2021-10-06 12:52:16.877 DBG default: Exec #19: parted -lm
2021-10-06 12:52:16.915 DBG default: Exit #19: 0 QProcess::NormalExit
2021-10-06 12:52:16.916 DBG default: Exec #20: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 12:52:16.925 DBG default: Exit #20: 32 QProcess::NormalExit
2021-10-06 12:52:21.989 DBG default: Exec #21: /usr/sbin/gparted
2021-10-06 12:52:34.405 DBG default: SOut #21: "GParted 1.2.0\nconfiguration --enable-libparted-dmraid --enable-online-resize\nlibparted 3.4\n"
2021-10-06 12:52:34.405 DBG default: Exit #21: 0 QProcess::NormalExit
2021-10-06 12:52:34.405 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 12:52:34.407 DBG default: Exec #22: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 12:52:34.415 DBG default: Exit #22: 0 QProcess::NormalExit
2021-10-06 12:52:34.415 DBG default: Exec #23: partprobe -s
2021-10-06 12:52:34.529 DBG default: SOut #23: "/dev/sda: gpt partitions\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:52:34.529 DBG default: Exit #23: 0 QProcess::NormalExit
2021-10-06 12:52:34.529 DBG default: Exec #24: blkid -c /dev/null
2021-10-06 12:52:34.569 DBG default: SOut #24: "/dev/sda: PTUUID=\"4ca2c105-553d-4a8b-b88b-6c1fff6b56a9\" PTTYPE=\"gpt\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 12:52:34.569 DBG default: Exit #24: 0 QProcess::NormalExit
2021-10-06 12:52:34.569 DBG default: Exec #25: parted -lm
2021-10-06 12:52:34.607 DBG default: Exit #25: 0 QProcess::NormalExit
2021-10-06 12:52:34.607 DBG default: Exec #26: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 12:52:34.617 DBG default: Exit #26: 32 QProcess::NormalExit
2021-10-06 12:53:13.967 DBG default: Mount points:
2021-10-06 12:53:13.968 DBG default:  - "/" - "sda3" "root.fsm" "/dev/mapper/root.fsm"
2021-10-06 12:53:13.968 DBG default:  - "/boot" - "sda2" "sda2" "/dev/sda2"
2021-10-06 12:53:13.968 DBG default:  - "SWAP" - "sda4" "swap" "/dev/mapper/swap"
2021-10-06 12:53:15.383 DBG default: +++ bool MInstall::saveHomeBasic() +++
2021-10-06 12:53:15.393 WRN qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2822, resource id: 18885531, major code: 40 (TranslateCoords), minor code: 0
2021-10-06 12:53:15.420 DBG default: - Preparing to install MX Linux -
2021-10-06 12:53:15.422 DBG default: Exec #27: smartctl -H /dev/sda
2021-10-06 12:53:15.456 DBG default: SOut #27: "smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-8-amd64] (local build)\nCopyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org\n\n=== START OF READ SMART DATA SECTION ===\nSMART overall-health self-assessment test result: PASSED\n\n"
2021-10-06 12:53:15.456 DBG default: Exit #27: 0 QProcess::NormalExit
2021-10-06 12:53:15.456 DBG default: Exec #28: smartctl -A /dev/sda| grep -E "^  5|^196|^197|^198" | awk '{ if ( $10 != 0 ) { print $1,$2,$10} }'
2021-10-06 12:53:15.484 DBG default: Exit #28: 0 QProcess::NormalExit
2021-10-06 12:53:15.484 DBG default: +++ void MInstall::cleanup(bool) +++
2021-10-06 12:53:15.487 DBG default: Exec #29: /bin/umount -l /mnt/antiX/boot/efi
2021-10-06 12:53:15.497 DBG default: SErr #29: "umount: /mnt/antiX/boot/efi: no mount point specified.\n"
2021-10-06 12:53:15.498 DBG default: Exit #29: 32 QProcess::NormalExit
2021-10-06 12:53:15.498 DBG default: Exec #30: /bin/umount -l /mnt/antiX/proc
2021-10-06 12:53:15.507 DBG default: SErr #30: "umount: /mnt/antiX/proc: no mount point specified.\n"
2021-10-06 12:53:15.507 DBG default: Exit #30: 32 QProcess::NormalExit
2021-10-06 12:53:15.507 DBG default: Exec #31: /bin/umount -l /mnt/antiX/sys
2021-10-06 12:53:15.516 DBG default: SErr #31: "umount: /mnt/antiX/sys: no mount point specified.\n"
2021-10-06 12:53:15.516 DBG default: Exit #31: 32 QProcess::NormalExit
2021-10-06 12:53:15.516 DBG default: Exec #32: /bin/umount -l /mnt/antiX/dev/shm
2021-10-06 12:53:15.523 DBG default: SErr #32: "umount: /mnt/antiX/dev/shm: no mount point specified.\n"
2021-10-06 12:53:15.523 DBG default: Exit #32: 32 QProcess::NormalExit
2021-10-06 12:53:15.523 DBG default: Exec #33: /bin/umount -l /mnt/antiX/dev
2021-10-06 12:53:15.532 DBG default: SErr #33: "umount: /mnt/antiX/dev: no mount point specified.\n"
2021-10-06 12:53:15.532 DBG default: Exit #33: 32 QProcess::NormalExit
2021-10-06 12:53:15.532 DBG default: Exec #34: swapoff /dev/sda2
2021-10-06 12:53:15.543 DBG default: SErr #34: "swapoff: /dev/sda2: swapoff failed: No such file or directory\n"
2021-10-06 12:53:15.543 DBG default: Exit #34: 4 QProcess::NormalExit
2021-10-06 12:53:15.543 DBG default: Exec #35: /bin/umount -l /mnt/antiX/boot
2021-10-06 12:53:15.553 DBG default: SErr #35: "umount: /mnt/antiX/boot: no mount point specified.\n"
2021-10-06 12:53:15.553 DBG default: Exit #35: 32 QProcess::NormalExit
2021-10-06 12:53:15.553 DBG default: Exec #36: swapoff /dev/mapper/root.fsm
2021-10-06 12:53:15.562 DBG default: SErr #36: "swapoff: /dev/mapper/root.fsm: swapoff failed: No such file or directory\n"
2021-10-06 12:53:15.562 DBG default: Exit #36: 4 QProcess::NormalExit
2021-10-06 12:53:15.562 DBG default: Exec #37: /bin/umount -l /mnt/antiX/
2021-10-06 12:53:15.570 DBG default: SErr #37: "umount: /mnt/antiX/: no mount point specified.\n"
2021-10-06 12:53:15.571 DBG default: Exit #37: 32 QProcess::NormalExit
2021-10-06 12:53:15.571 DBG default: Exec #38: cryptsetup close /dev/mapper/root.fsm
2021-10-06 12:53:15.786 DBG default: SErr #38: "Device /dev/mapper/root.fsm is not active.\n"
2021-10-06 12:53:15.786 DBG default: Exit #38: 4 QProcess::NormalExit
2021-10-06 12:53:15.786 DBG default: +++ bool PartMan::preparePartitions() +++
2021-10-06 12:53:15.789 DBG default: Exec #39: lsblk -nro name /dev/sda
2021-10-06 12:53:15.798 DBG default: Exit #39: 0 QProcess::NormalExit
2021-10-06 12:53:15.798 DBG default: Exec #40: swapoff /dev/sda
2021-10-06 12:53:15.805 DBG default: SErr #40: "swapoff: /dev/sda: swapoff failed: Invalid argument\n"
2021-10-06 12:53:15.805 DBG default: Exit #40: 4 QProcess::NormalExit
2021-10-06 12:53:15.806 DBG default: Exec #41: /bin/umount /dev/sda
2021-10-06 12:53:15.814 DBG default: SErr #41: "umount: /dev/sda: not mounted.\n"
2021-10-06 12:53:15.814 DBG default: Exit #41: 32 QProcess::NormalExit
2021-10-06 12:53:15.814 DBG default: - Preparing partition tables -
2021-10-06 12:53:15.818 DBG default: Exec #42: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda
2021-10-06 12:53:15.831 DBG default: SErr #42: "64+0 records in\n64+0 records out\n4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.00343248 s, 1.2 GB/s\n"
2021-10-06 12:53:15.831 DBG default: Exit #42: 0 QProcess::NormalExit
2021-10-06 12:53:15.831 DBG default: Exec #43: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda seek=3815539
2021-10-06 12:53:15.839 DBG default: SErr #43: "dd: error writing '/dev/sda': No space left on device\n64+0 records in\n63+0 records out\n4186112 bytes (4.2 MB, 4.0 MiB) copied, 0.00186469 s, 2.2 GB/s\n"
2021-10-06 12:53:15.839 DBG default: Exit #43: 1 QProcess::NormalExit
2021-10-06 12:53:15.839 DBG default: Exec #44: parted -s /dev/sda mklabel gpt
2021-10-06 12:53:15.905 DBG default: Exit #44: 0 QProcess::NormalExit
2021-10-06 12:53:15.905 DBG default: - Preparing required partitions -
2021-10-06 12:53:15.910 DBG default: Exec #45: parted -s --align optimal /dev/sda mkpart primary 1MiB 257MiB
2021-10-06 12:53:15.965 DBG default: Exit #45: 0 QProcess::NormalExit
2021-10-06 12:53:15.969 DBG default: Exec #46: parted -s --align optimal /dev/sda mkpart primary 257MiB 769MiB
2021-10-06 12:53:16.045 DBG default: Exit #46: 0 QProcess::NormalExit
2021-10-06 12:53:16.049 DBG default: Exec #47: parted -s --align optimal /dev/sda mkpart primary 769MiB 230276MiB
2021-10-06 12:53:16.125 DBG default: Exit #47: 0 QProcess::NormalExit
2021-10-06 12:53:16.128 DBG default: Exec #48: parted -s --align optimal /dev/sda mkpart primary 230276MiB 232276MiB
2021-10-06 12:53:16.205 DBG default: Exit #48: 0 QProcess::NormalExit
2021-10-06 12:53:16.209 DBG default: Exec #49: parted -s /dev/sda set 2 legacy_boot on
2021-10-06 12:53:16.285 DBG default: Exit #49: 0 QProcess::NormalExit
2021-10-06 12:53:16.296 DBG default: Exec #50: partprobe -s
2021-10-06 12:53:16.429 DBG default: SOut #50: "/dev/sda: gpt partitions 1 2 3 4\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:53:16.429 DBG default: Exit #50: 0 QProcess::NormalExit
2021-10-06 12:53:16.429 DBG default: +++ bool PartMan::formatPartitions() +++
2021-10-06 12:53:16.433 DBG default: - Formatting: EFI System Partition -
2021-10-06 12:53:16.438 DBG default: Exec #51: mkfs.msdos -F 32 -n "EFI System" /dev/sda1
2021-10-06 12:53:16.497 DBG default: SOut #51: "mkfs.fat 4.2 (2021-01-31)\n"
2021-10-06 12:53:16.497 DBG default: SErr #51: "mkfs.fat: Warning: lowercase labels might not work properly on some systems\n"
2021-10-06 12:53:16.497 DBG default: Exit #51: 0 QProcess::NormalExit
2021-10-06 12:53:16.498 DBG default: Exec #52: parted -s /dev/sda set 1 esp on
2021-10-06 12:53:16.641 DBG default: Exit #52: 0 QProcess::NormalExit
2021-10-06 12:53:16.641 DBG default: - Formatting: /boot -
2021-10-06 12:53:16.646 DBG default: Exec #53: mkfs.ext4 -F /dev/sda2 -L "boot"
2021-10-06 12:53:16.713 DBG default: SOut #53: "Discarding device blocks:   4096/131072\b\b\b\b\b\b\b\b\b\b\b\b\b             \b\b\b\b\b\b\b\b\b\b\b\b\bdone                            \nCreating filesystem with 131072 4k blocks and 32768 inodes\nFilesystem UUID: ad312201-fcc2-4d65-8fb9-592efeab0748\nSuperblock backups stored on blocks: \n\t32768, 98304\n\nAllocating group tables: 0/4\b\b\b   \b\b\bdone                            \nWriting inode tables: 0/4\b\b\b   \b\b\bdone                            \nCreating journal (4096 blocks): done\nWriting superblocks and filesystem accounting information: 0/4\b\b\b   \b\b\bdone\n\n"
2021-10-06 12:53:16.713 DBG default: SErr #53: "mke2fs 1.46.2 (28-Feb-2021)\n"
2021-10-06 12:53:16.713 DBG default: Exit #53: 0 QProcess::NormalExit
2021-10-06 12:53:16.713 DBG default: Exec #54: /sbin/tune2fs -c0 -C0 -i1m /dev/sda2
2021-10-06 12:53:16.729 DBG default: SOut #54: "tune2fs 1.46.2 (28-Feb-2021)\nSetting maximal mount count to -1\nSetting current mount count to 0\nSetting interval between checks to 2592000 seconds\n"
2021-10-06 12:53:16.729 DBG default: Exit #54: 0 QProcess::NormalExit
2021-10-06 12:53:16.729 DBG default: - Creating encrypted volume: sda3 -
2021-10-06 12:53:16.738 DBG default: Exec #55: cryptsetup --batch-mode --key-size 512 --hash sha512 --pbkdf argon2id --sector-size=1358828544 luksFormat /dev/sda3
2021-10-06 12:53:16.747 DBG default: SErr #55: "Usage: cryptsetup [-?Vvyrq] [-?|--help] [--usage] [-V|--version]\n        [-v|--verbose] [--debug] [--debug-json] [-c|--cipher=STRING]\n        [-h|--hash=STRING] [-y|--verify-passphrase] [-d|--key-file=STRING]\n        [--master-key-file=STRING] [--dump-master-key] [-s|--key-size=BITS]\n        [-l|--keyfile-size=bytes] [--keyfile-offset=bytes]\n        [--new-keyfile-size=bytes] [--new-keyfile-offset=bytes]\n        [-S|--key-slot=INT] [-b|--size=SECTORS] [--device-size=bytes]\n        [-o|--offset=SECTORS] [-p|--skip=SECTORS] [-r|--readonly]\n        [-q|--batch-mode] [-t|--timeout=secs] [--progress-frequency=secs]\n        [-T|--tries=INT] [--align-payload=SECTORS]\n        [--header-backup-file=STRING] [--use-random] [--use-urandom]\n        [--shared] [--uuid=STRING] [--allow-discards] [--header=STRING]\n        [--test-passphrase] [--tcrypt-hidden] [--tcrypt-system]\n        [--tcrypt-backup] [--veracrypt] [--veracrypt-pim=INT]\n        [--veracrypt-query-pim] [-M|--type=STRING] [--force-password]\n        [--perf-same_cpu_crypt] [--perf-submit_from_crypt_cpus]\n        [--perf-no_read_workqueue] [--perf-no_write_workqueue] [--deferred]\n        [--serialize-memory-hard-pbkdf] [-i|--iter-time=msecs]\n        [--pbkdf=STRING] [--pbkdf-memory=kilobytes]\n        [--pbkdf-parallel=threads] [--pbkdf-force-iterations=LONG]\n        [--priority=STRING] [--disable-locks] [--disable-keyring]\n        [-I|--integrity=STRING] [--integrity-no-journal]\n        [--integrity-no-wipe] [--integrity-legacy-padding] [--token-only]\n        [--token-id=INT] [--key-description=STRING] [--sector-size=INT]\n        [--iv-large-sectors] [--persistent] [--label=STRING]\n        [--subsystem=STRING] [--unbound] [--json-file=STRING]\n        [--luks2-metadata-size=bytes] [--luks2-keyslots-size=bytes]\n        [--refresh] [--keyslot-key-size=BITS] [--keyslot-cipher=STRING]\n        [--encrypt] [--decrypt] [--init-only] [--resume-only]\n        [--reduce-device-size=bytes] [--hotzone-size=bytes]\n        [--resilience=STRING] [--resilience-hash=STRING]\n        [--active-name=STRING] [OPTION...] <action> <action-specific>\n/usr/sbin/cryptsetup: Unsupported encryption sector size.\n"
2021-10-06 12:53:16.747 DBG default: Exit #55: 1 QProcess::NormalExit
2021-10-06 12:53:16.747 DBG default: +++ void MInstall::failUI(const QString&) +++
2021-10-06 12:53:16.750 DBG default: Phase 1 - "Failed to prepare required partitions."


The below is the minstall.log file after a failed installation without swap:

Code: Select all

2021-10-06 12:59:50.284 DBG default: Installer version: 21.10.03
2021-10-06 12:59:50.395 DBG default: +++ void MInstall::startup() +++
2021-10-06 12:59:50.399 DBG default: check for remastered home demo folder: false
2021-10-06 12:59:50.399 DBG default: Exec #1: du -sb /live/aufs/boot
2021-10-06 12:59:50.452 DBG default: Exit #1: 0 QProcess::NormalExit
2021-10-06 12:59:50.452 DBG default: linuxfs file is at :  "/live/boot-dev/antiX/linuxfs"
2021-10-06 12:59:50.452 DBG default: Exec #2: dd if=/live/boot-dev/antiX/linuxfs bs=1 skip=20 count=2 status=none 2>/dev/null | od -An -tdI
2021-10-06 12:59:50.462 DBG default: Exit #2: 0 QProcess::NormalExit
2021-10-06 12:59:50.462 DBG default: linuxfs compression type is  "6" compression factor is  25
2021-10-06 12:59:50.463 DBG default: Exec #3: df /live/linux --output=used --total |tail -n1
2021-10-06 12:59:50.470 DBG default: Exit #3: 0 QProcess::NormalExit
2021-10-06 12:59:50.471 DBG default: linuxfs file size is  7312769024  rootfs file size is  0
2021-10-06 12:59:50.471 DBG default: Minimum space: 268435456 (boot), 8386510848 (root)
2021-10-06 12:59:50.471 DBG default: Exec #4: uname -m | grep -q i686
2021-10-06 12:59:50.478 DBG default: Exit #4: 1 QProcess::NormalExit
2021-10-06 12:59:50.478 DBG default: uefi = true
2021-10-06 12:59:50.478 DBG default: +++ void MInstall::setupAutoMount(bool) +++
2021-10-06 12:59:50.479 DBG default: Exec #5: ps -e | grep 'udisksd'
2021-10-06 12:59:50.493 DBG default: SOut #5: "   9366 ?        00:00:00 udisksd\n"
2021-10-06 12:59:50.493 DBG default: Exit #5: 0 QProcess::NormalExit
2021-10-06 12:59:50.493 DBG default: Exec #6: egrep -l '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d
2021-10-06 12:59:50.509 DBG default: SErr #6: "grep: /lib/udev/rules.d: Is a directory\n"
2021-10-06 12:59:50.509 DBG default: Exit #6: 2 QProcess::NormalExit
2021-10-06 12:59:50.509 DBG default: Exec #7: systemctl list-units --full --all -t mount --no-legend 2>/dev/null | grep -v masked | cut -f1 -d' ' | egrep -v '^(dev-hugepages|dev-mqueue|proc-sys-fs-binfmt_misc|run-user-.*-gvfs|sys-fs-fuse-connections|sys-kernel-config|sys-kernel-debug)'
2021-10-06 12:59:50.517 DBG default: Exit #7: 1 QProcess::NormalExit
2021-10-06 12:59:50.518 DBG default: MkPath(SUCCESS): "/run/udev/rules.d"
2021-10-06 12:59:50.518 DBG default: Exec #8: echo 'SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1"' > /run/udev/rules.d/91-mx-udisks-inhibit.rules
2021-10-06 12:59:50.522 DBG default: Exit #8: 0 QProcess::NormalExit
2021-10-06 12:59:50.522 DBG default: Exec #9: udevadm control --reload
2021-10-06 12:59:50.533 DBG default: Exit #9: 0 QProcess::NormalExit
2021-10-06 12:59:50.533 DBG default: Exec #10: udevadm trigger --subsystem-match=block
2021-10-06 12:59:50.542 DBG default: Exit #10: 0 QProcess::NormalExit
2021-10-06 12:59:50.542 DBG default: Exec #11: /bin/ls -1 /home | grep -Ev '(lost\+found|demo|snapshot)' | grep -q [a-zA-Z0-9]
2021-10-06 12:59:50.548 DBG default: Exit #11: 1 QProcess::NormalExit
2021-10-06 12:59:50.548 DBG default: check for possible snapshot: false
2021-10-06 12:59:50.606 DBG default: +++ void MInstall::setupkeyboardbutton() +++
2021-10-06 12:59:50.608 DBG default: Exec #12: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
2021-10-06 12:59:50.618 DBG default: Exit #12: 0 QProcess::NormalExit
2021-10-06 12:59:50.622 DBG default: Exec #13: locale -a | grep -Ev '^(C|POSIX)\.?' | grep -E 'utf8|UTF-8'
2021-10-06 12:59:50.633 DBG default: Exit #13: 0 QProcess::NormalExit
2021-10-06 12:59:50.634 DBG default: Exec #14: grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus
2021-10-06 12:59:50.702 DBG default: Exit #14: 1 QProcess::NormalExit
2021-10-06 12:59:50.702 DBG default: Exec #15: dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'
2021-10-06 12:59:50.730 DBG default: Exit #15: 0 QProcess::NormalExit
2021-10-06 12:59:50.730 DBG default: +++ void MInstall::buildServiceList() +++
2021-10-06 12:59:50.734 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 12:59:50.734 DBG default: Exec #16: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 12:59:50.747 DBG default: Exit #16: 0 QProcess::NormalExit
2021-10-06 12:59:50.748 DBG default: Exec #17: partprobe -s
2021-10-06 12:59:50.871 DBG default: SOut #17: "/dev/sda: gpt partitions 1 2 3\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:59:50.871 DBG default: Exit #17: 0 QProcess::NormalExit
2021-10-06 12:59:50.871 DBG default: Exec #18: blkid -c /dev/null
2021-10-06 12:59:50.911 DBG default: SOut #18: "/dev/sda1: LABEL_FATBOOT=\"EFI System\" LABEL=\"EFI System\" UUID=\"5916-AAC4\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTLABEL=\"primary\" PARTUUID=\"6523564d-16d9-4611-ad78-b3b42dad3449\"\n/dev/sda2: LABEL=\"boot\" UUID=\"1c1acc9d-b433-48ca-b650-620dd85eb9a4\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTLABEL=\"primary\" PARTUUID=\"2c957374-cb60-4f5e-b7be-c45ebdb2fb82\"\n/dev/sda3: UUID=\"3b4dbee4-1427-4894-8f3a-c71ae8b47122\" TYPE=\"crypto_LUKS\" PARTLABEL=\"primary\" PARTUUID=\"315647f8-f2ca-4e4a-a4b8-b761774acc54\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 12:59:50.911 DBG default: Exit #18: 0 QProcess::NormalExit
2021-10-06 12:59:50.911 DBG default: Exec #19: parted -lm
2021-10-06 12:59:50.961 DBG default: Exit #19: 0 QProcess::NormalExit
2021-10-06 12:59:50.961 DBG default: Exec #20: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 12:59:50.970 DBG default: Exit #20: 32 QProcess::NormalExit
2021-10-06 13:00:08.882 DBG default: Exec #21: /usr/sbin/gparted
2021-10-06 13:00:22.308 DBG default: SOut #21: "GParted 1.2.0\nconfiguration --enable-libparted-dmraid --enable-online-resize\nlibparted 3.4\n"
2021-10-06 13:00:22.308 DBG default: Exit #21: 0 QProcess::NormalExit
2021-10-06 13:00:22.308 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 13:00:22.310 DBG default: Exec #22: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 13:00:22.317 DBG default: Exit #22: 0 QProcess::NormalExit
2021-10-06 13:00:22.317 DBG default: Exec #23: partprobe -s
2021-10-06 13:00:22.407 DBG default: SOut #23: "/dev/sda: gpt partitions\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 13:00:22.407 DBG default: Exit #23: 0 QProcess::NormalExit
2021-10-06 13:00:22.407 DBG default: Exec #24: blkid -c /dev/null
2021-10-06 13:00:22.447 DBG default: SOut #24: "/dev/sda: PTUUID=\"2b9b6f10-a554-42f5-a3bc-95778e1afffa\" PTTYPE=\"gpt\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 13:00:22.447 DBG default: Exit #24: 0 QProcess::NormalExit
2021-10-06 13:00:22.447 DBG default: Exec #25: parted -lm
2021-10-06 13:00:22.482 DBG default: Exit #25: 0 QProcess::NormalExit
2021-10-06 13:00:22.482 DBG default: Exec #26: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 13:00:22.493 DBG default: Exit #26: 32 QProcess::NormalExit
2021-10-06 13:02:11.854 DBG default: Mount points:
2021-10-06 13:02:11.854 DBG default:  - "/" - "sda3" "root.fsm" "/dev/mapper/root.fsm"
2021-10-06 13:02:11.854 DBG default:  - "/boot" - "sda2" "sda2" "/dev/sda2"
2021-10-06 13:02:13.260 DBG default: +++ bool MInstall::saveHomeBasic() +++
2021-10-06 13:02:13.272 WRN qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4257, resource id: 18887372, major code: 40 (TranslateCoords), minor code: 0
2021-10-06 13:02:13.301 DBG default: - Preparing to install MX Linux -
2021-10-06 13:02:13.303 DBG default: Exec #27: smartctl -H /dev/sda
2021-10-06 13:02:13.339 DBG default: SOut #27: "smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-8-amd64] (local build)\nCopyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org\n\n=== START OF READ SMART DATA SECTION ===\nSMART overall-health self-assessment test result: PASSED\n\n"
2021-10-06 13:02:13.339 DBG default: Exit #27: 0 QProcess::NormalExit
2021-10-06 13:02:13.339 DBG default: Exec #28: smartctl -A /dev/sda| grep -E "^  5|^196|^197|^198" | awk '{ if ( $10 != 0 ) { print $1,$2,$10} }'
2021-10-06 13:02:13.367 DBG default: Exit #28: 0 QProcess::NormalExit
2021-10-06 13:02:13.367 DBG default: +++ void MInstall::cleanup(bool) +++
2021-10-06 13:02:13.368 DBG default: Exec #29: /bin/umount -l /mnt/antiX/boot/efi
2021-10-06 13:02:13.377 DBG default: SErr #29: "umount: /mnt/antiX/boot/efi: no mount point specified.\n"
2021-10-06 13:02:13.377 DBG default: Exit #29: 32 QProcess::NormalExit
2021-10-06 13:02:13.377 DBG default: Exec #30: /bin/umount -l /mnt/antiX/proc
2021-10-06 13:02:13.385 DBG default: SErr #30: "umount: /mnt/antiX/proc: no mount point specified.\n"
2021-10-06 13:02:13.385 DBG default: Exit #30: 32 QProcess::NormalExit
2021-10-06 13:02:13.385 DBG default: Exec #31: /bin/umount -l /mnt/antiX/sys
2021-10-06 13:02:13.393 DBG default: SErr #31: "umount: /mnt/antiX/sys: no mount point specified.\n"
2021-10-06 13:02:13.393 DBG default: Exit #31: 32 QProcess::NormalExit
2021-10-06 13:02:13.393 DBG default: Exec #32: /bin/umount -l /mnt/antiX/dev/shm
2021-10-06 13:02:13.401 DBG default: SErr #32: "umount: /mnt/antiX/dev/shm: no mount point specified.\n"
2021-10-06 13:02:13.401 DBG default: Exit #32: 32 QProcess::NormalExit
2021-10-06 13:02:13.401 DBG default: Exec #33: /bin/umount -l /mnt/antiX/dev
2021-10-06 13:02:13.408 DBG default: SErr #33: "umount: /mnt/antiX/dev: no mount point specified.\n"
2021-10-06 13:02:13.408 DBG default: Exit #33: 32 QProcess::NormalExit
2021-10-06 13:02:13.408 DBG default: Exec #34: swapoff /dev/sda2
2021-10-06 13:02:13.419 DBG default: SErr #34: "swapoff: /dev/sda2: swapoff failed: No such file or directory\n"
2021-10-06 13:02:13.419 DBG default: Exit #34: 4 QProcess::NormalExit
2021-10-06 13:02:13.419 DBG default: Exec #35: /bin/umount -l /mnt/antiX/boot
2021-10-06 13:02:13.428 DBG default: SErr #35: "umount: /mnt/antiX/boot: no mount point specified.\n"
2021-10-06 13:02:13.428 DBG default: Exit #35: 32 QProcess::NormalExit
2021-10-06 13:02:13.428 DBG default: Exec #36: swapoff /dev/mapper/root.fsm
2021-10-06 13:02:13.436 DBG default: SErr #36: "swapoff: /dev/mapper/root.fsm: swapoff failed: No such file or directory\n"
2021-10-06 13:02:13.436 DBG default: Exit #36: 4 QProcess::NormalExit
2021-10-06 13:02:13.436 DBG default: Exec #37: /bin/umount -l /mnt/antiX/
2021-10-06 13:02:13.446 DBG default: SErr #37: "umount: /mnt/antiX/: no mount point specified.\n"
2021-10-06 13:02:13.446 DBG default: Exit #37: 32 QProcess::NormalExit
2021-10-06 13:02:13.446 DBG default: Exec #38: cryptsetup close /dev/mapper/root.fsm
2021-10-06 13:02:13.674 DBG default: SErr #38: "Device /dev/mapper/root.fsm is not active.\n"
2021-10-06 13:02:13.674 DBG default: Exit #38: 4 QProcess::NormalExit
2021-10-06 13:02:13.674 DBG default: +++ bool PartMan::preparePartitions() +++
2021-10-06 13:02:13.677 DBG default: Exec #39: lsblk -nro name /dev/sda
2021-10-06 13:02:13.685 DBG default: Exit #39: 0 QProcess::NormalExit
2021-10-06 13:02:13.685 DBG default: Exec #40: swapoff /dev/sda
2021-10-06 13:02:13.692 DBG default: SErr #40: "swapoff: /dev/sda: swapoff failed: Invalid argument\n"
2021-10-06 13:02:13.693 DBG default: Exit #40: 4 QProcess::NormalExit
2021-10-06 13:02:13.693 DBG default: Exec #41: /bin/umount /dev/sda
2021-10-06 13:02:13.701 DBG default: SErr #41: "umount: /dev/sda: not mounted.\n"
2021-10-06 13:02:13.701 DBG default: Exit #41: 32 QProcess::NormalExit
2021-10-06 13:02:13.701 DBG default: - Preparing partition tables -
2021-10-06 13:02:13.705 DBG default: Exec #42: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda
2021-10-06 13:02:13.727 DBG default: SErr #42: "64+0 records in\n64+0 records out\n4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.012817 s, 327 MB/s\n"
2021-10-06 13:02:13.727 DBG default: Exit #42: 0 QProcess::NormalExit
2021-10-06 13:02:13.727 DBG default: Exec #43: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda seek=3815539
2021-10-06 13:02:13.739 DBG default: SErr #43: "dd: error writing '/dev/sda': No space left on device\n64+0 records in\n63+0 records out\n4186112 bytes (4.2 MB, 4.0 MiB) copied, 0.00190751 s, 2.2 GB/s\n"
2021-10-06 13:02:13.739 DBG default: Exit #43: 1 QProcess::NormalExit
2021-10-06 13:02:13.739 DBG default: Exec #44: parted -s /dev/sda mklabel gpt
2021-10-06 13:02:13.795 DBG default: Exit #44: 0 QProcess::NormalExit
2021-10-06 13:02:13.795 DBG default: - Preparing required partitions -
2021-10-06 13:02:13.802 DBG default: Exec #45: parted -s --align optimal /dev/sda mkpart primary 1MiB 257MiB
2021-10-06 13:02:13.855 DBG default: Exit #45: 0 QProcess::NormalExit
2021-10-06 13:02:13.859 DBG default: Exec #46: parted -s --align optimal /dev/sda mkpart primary 257MiB 769MiB
2021-10-06 13:02:13.931 DBG default: Exit #46: 0 QProcess::NormalExit
2021-10-06 13:02:13.935 DBG default: Exec #47: parted -s --align optimal /dev/sda mkpart primary 769MiB 238468MiB
2021-10-06 13:02:14.007 DBG default: Exit #47: 0 QProcess::NormalExit
2021-10-06 13:02:14.014 DBG default: Exec #48: parted -s /dev/sda set 2 legacy_boot on
2021-10-06 13:02:14.088 DBG default: Exit #48: 0 QProcess::NormalExit
2021-10-06 13:02:14.095 DBG default: Exec #49: partprobe -s
2021-10-06 13:02:14.219 DBG default: SOut #49: "/dev/sda: gpt partitions 1 2 3\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 13:02:14.219 DBG default: Exit #49: 0 QProcess::NormalExit
2021-10-06 13:02:14.219 DBG default: +++ bool PartMan::formatPartitions() +++
2021-10-06 13:02:14.223 DBG default: - Formatting: EFI System Partition -
2021-10-06 13:02:14.231 DBG default: Exec #50: mkfs.msdos -F 32 -n "EFI System" /dev/sda1
2021-10-06 13:02:14.295 DBG default: SOut #50: "mkfs.fat 4.2 (2021-01-31)\n"
2021-10-06 13:02:14.296 DBG default: SErr #50: "mkfs.fat: Warning: lowercase labels might not work properly on some systems\n"
2021-10-06 13:02:14.296 DBG default: Exit #50: 0 QProcess::NormalExit
2021-10-06 13:02:14.296 DBG default: Exec #51: parted -s /dev/sda set 1 esp on
2021-10-06 13:02:14.344 DBG default: Exit #51: 0 QProcess::NormalExit
2021-10-06 13:02:14.344 DBG default: - Formatting: /boot -
2021-10-06 13:02:14.351 DBG default: Exec #52: mkfs.ext4 -F /dev/sda2 -L "boot"
2021-10-06 13:02:14.423 DBG default: SOut #52: "Discarding device blocks:   4096/131072\b\b\b\b\b\b\b\b\b\b\b\b\b             \b\b\b\b\b\b\b\b\b\b\b\b\bdone                            \nCreating filesystem with 131072 4k blocks and 32768 inodes\nFilesystem UUID: 153d3647-0d8e-4d59-9f41-0e4799cdfc32\nSuperblock backups stored on blocks: \n\t32768, 98304\n\nAllocating group tables: 0/4\b\b\b   \b\b\bdone                            \nWriting inode tables: 0/4\b\b\b   \b\b\bdone                            \nCreating journal (4096 blocks): done\nWriting superblocks and filesystem accounting information: 0/4\b\b\b   \b\b\bdone\n\n"
2021-10-06 13:02:14.423 DBG default: SErr #52: "mke2fs 1.46.2 (28-Feb-2021)\n"
2021-10-06 13:02:14.423 DBG default: Exit #52: 0 QProcess::NormalExit
2021-10-06 13:02:14.423 DBG default: Exec #53: /sbin/tune2fs -c0 -C0 -i1m /dev/sda2
2021-10-06 13:02:14.439 DBG default: SOut #53: "tune2fs 1.46.2 (28-Feb-2021)\nSetting maximal mount count to -1\nSetting current mount count to 0\nSetting interval between checks to 2592000 seconds\n"
2021-10-06 13:02:14.439 DBG default: Exit #53: 0 QProcess::NormalExit
2021-10-06 13:02:14.439 DBG default: - Creating encrypted volume: sda3 -
2021-10-06 13:02:14.446 DBG default: Exec #54: cryptsetup --batch-mode --key-size 512 --hash sha512 --pbkdf argon2id --sector-size=353437696 luksFormat /dev/sda3
2021-10-06 13:02:14.457 DBG default: SErr #54: "Usage: cryptsetup [-?Vvyrq] [-?|--help] [--usage] [-V|--version]\n        [-v|--verbose] [--debug] [--debug-json] [-c|--cipher=STRING]\n        [-h|--hash=STRING] [-y|--verify-passphrase] [-d|--key-file=STRING]\n        [--master-key-file=STRING] [--dump-master-key] [-s|--key-size=BITS]\n        [-l|--keyfile-size=bytes] [--keyfile-offset=bytes]\n        [--new-keyfile-size=bytes] [--new-keyfile-offset=bytes]\n        [-S|--key-slot=INT] [-b|--size=SECTORS] [--device-size=bytes]\n        [-o|--offset=SECTORS] [-p|--skip=SECTORS] [-r|--readonly]\n        [-q|--batch-mode] [-t|--timeout=secs] [--progress-frequency=secs]\n        [-T|--tries=INT] [--align-payload=SECTORS]\n        [--header-backup-file=STRING] [--use-random] [--use-urandom]\n        [--shared] [--uuid=STRING] [--allow-discards] [--header=STRING]\n        [--test-passphrase] [--tcrypt-hidden] [--tcrypt-system]\n        [--tcrypt-backup] [--veracrypt] [--veracrypt-pim=INT]\n        [--veracrypt-query-pim] [-M|--type=STRING] [--force-password]\n        [--perf-same_cpu_crypt] [--perf-submit_from_crypt_cpus]\n        [--perf-no_read_workqueue] [--perf-no_write_workqueue] [--deferred]\n        [--serialize-memory-hard-pbkdf] [-i|--iter-time=msecs]\n        [--pbkdf=STRING] [--pbkdf-memory=kilobytes]\n        [--pbkdf-parallel=threads] [--pbkdf-force-iterations=LONG]\n        [--priority=STRING] [--disable-locks] [--disable-keyring]\n        [-I|--integrity=STRING] [--integrity-no-journal]\n        [--integrity-no-wipe] [--integrity-legacy-padding] [--token-only]\n        [--token-id=INT] [--key-description=STRING] [--sector-size=INT]\n        [--iv-large-sectors] [--persistent] [--label=STRING]\n        [--subsystem=STRING] [--unbound] [--json-file=STRING]\n        [--luks2-metadata-size=bytes] [--luks2-keyslots-size=bytes]\n        [--refresh] [--keyslot-key-size=BITS] [--keyslot-cipher=STRING]\n        [--encrypt] [--decrypt] [--init-only] [--resume-only]\n        [--reduce-device-size=bytes] [--hotzone-size=bytes]\n        [--resilience=STRING] [--resilience-hash=STRING]\n        [--active-name=STRING] [OPTION...] <action> <action-specific>\n/usr/sbin/cryptsetup: Unsupported encryption sector size.\n"
2021-10-06 13:02:14.457 DBG default: Exit #54: 1 QProcess::NormalExit
2021-10-06 13:02:14.457 DBG default: +++ void MInstall::failUI(const QString&) +++
2021-10-06 13:02:14.463 DBG default: Phase 1 - "Failed to prepare required partitions."
By the way, MX-21_beta2 installed fine.
thanks. this is a very good bug report too. :happy:

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 2:47 pm
by markol
SwampRabbit wrote: Wed Oct 06, 2021 10:39 am @markol by everything working OOTB, do you mean hardware? Can you please explain a bit more what worked OOTB for you so we can tell what we need to sustain moving forward?
If its hardware, care to share your QSI please? Thanks!
This was my test VM. Complete setup was done in less than 20 minutes (including personalization). It detected and installed printer(s), detected UPS (!), and other HW connected to host system
I do prefer KDE, but this installation was superb!

I will install the 32bit version to Asus EEE tonight and report. I'm afraid I don't have any recent laptops at home.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
Battery:   ID-1: BAT0 charge: 50.0 Wh condition: 50.0/50.0 Wh (100%) volts: 10.0/10.0 
           model: innotek 1 type: Unknown serial: N/A status: Full 
CPU:       Topology: Single Core model: Intel Core i7-4720HQ bits: 64 type: MCP arch: Haswell 
           family: 6 model-id: 3C (60) stepping: 3 microcode: N/A L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 5187 
           Speed: 2594 MHz min/max: N/A Core speed (MHz): 1: 2594 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds mitigation: Clear CPU buffers; SMT Host state unknown 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Unknown: Dependent on hypervisor status 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 
           chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.11 driver: vmware unloaded: fbdev,modesetting,vesa 
           resolution: 1630x881~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 20.01 GiB used: 8.20 GiB (41.0%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 20.01 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 18.88 GiB size: 18.41 GiB (97.54%) used: 8.20 GiB (44.5%) fs: ext4 
           dev: /dev/sda1 
           ID-2: swap-1 size: 1.12 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/microsoft-edge-beta.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://ftp.arnes.si/mirrors/mxlinux/packages/mx/repo/ bullseye main non-free
Info:      Processes: 193 Uptime: 2m Memory: 5.17 GiB used: 626.9 MiB (11.9%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 2:49 pm
by Eadwine Rose
I have a to-snort-about thing going on.

When you have logged in MX Welcome appears, I leave that there for convenience until I am done setting things up.
I have save session ticked when I go to reboot, and I have to do that a few times after installing stuff.

My MX Welcome appears anew each time after I log in. So.. you can see where this is going:
Screenshot_2021-10-06_20-43-50.png

I didn't see this at first because they are stacked exactly on top of each other.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 1607 date: 06/17/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball 
           serial: <filter> charge: 55% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ 
           family: 17 (23) model-id: 8 stepping: 2 microcode: 800820D L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 102207 
           Speed: 1395 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1375 
           2: 1374 3: 1371 4: 1370 5: 1270 6: 1807 7: 1269 8: 2790 9: 1373 10: 1372 11: 1270 
           12: 1670 13: 1268 14: 2794 15: 1372 16: 1374 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nouveau 
           v: kernel bus ID: 08:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: NV137 v: 4.3 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D 
           Comb 
           vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus ID: 07:00.0 chip ID: 14f1:8880 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 08:00.1 chip ID: 10de:0fb9 
           Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 0a:00.3 chip ID: 1022:1457 
           Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 1-7:3 chip ID: 046d:09a4 serial: <filter> 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: f000 bus ID: 03:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 1-1:2 
           chip ID: 148f:7601 serial: <filter> 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.82 TiB used: 94.34 GiB (5.1%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
           ID-4: /dev/sdd type: USB vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B rotation: 5400 rpm serial: <filter> 
           rev: 0109 scheme: MBR 
           ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
Partition: ID-1: / raw size: 58.59 GiB size: 57.37 GiB (97.92%) used: 5.99 GiB (10.4%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /home raw size: 165.99 GiB size: 162.33 GiB (97.79%) used: 61.3 MiB (0.0%) 
           fs: ext4 dev: /dev/sda4 
           ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 41.1 C mobo: N/A gpu: nouveau temp: 33 C 
           Fan Speeds (RPM): N/A gpu: nouveau fan: 879 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://nl.mxrepo.com/mx/repo/ bullseye main non-free
Info:      Processes: 360 Uptime: 1m Memory: 31.36 GiB used: 1.20 GiB (3.8%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
I know about the nvidia driver. Haven't gotten around to that bit yet ;)

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:06 pm
by figueroa
No longer any way around having client side decorations? My favorite feature of MX-21 betas was being able to turn off CSD.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:08 pm
by SwampRabbit
@markol awesome thank you for the info! old hardware working OOTB is just as important as new hardware ;)

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:12 pm
by SwampRabbit
figueroa wrote: Wed Oct 06, 2021 4:06 pm No longer any way around having client side decorations? My favorite feature of MX-21 betas was being able to turn off CSD.
you can still do it I believe, just not OOTB

last I knew, there wasn't a reliable and stable way around it, I know others were looking at the options and what not.

that feature may have been a favorite for many, until all hell broke loose and it caused more issues than it did anything else

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:27 pm
by dolphin_oracle
figueroa wrote: Wed Oct 06, 2021 4:06 pm No longer any way around having client side decorations? My favorite feature of MX-21 betas was being able to turn off CSD.
the switches in mx-tweak are still available, but you'll need to install gtk3-nocsd on your own. performance of that library was iffy and I do not consider it good enough to ship by default.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:35 pm
by Stuart_M
Here is an anomaly with the keyboard in LibreOffice, Featherpad, and Geany in MX-21_rc1.

In a text document using any of the above applications, the correct behavior when using Shift+Ctrl+Arrow is to highlight and advance the cursor left or right one word at a time.

The problem in MX-21_rc1 is that the right Shift+Ctrl+Arrow key combination will highlight and advance the cursor left or right only one character at a time.

The right Ctrl+Arrow works correctly, advancing the cursor one word at a time but without highlighting.

The left Shift+Ctrl+Arrow and LCtrl+Arrow combination works correctly.

This was not a problem in MX-21_beta1 or beta2, only rc1.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:45 pm
by dreamer
figueroa wrote: Wed Oct 06, 2021 4:06 pm No longer any way around having client side decorations? My favorite feature of MX-21 betas was being able to turn off CSD.
Just use libxfce4ui-nocsd like everyone else. Even SwampRabbit posted a screenshot showing libxfce4ui-nocsd so I don't know why he pretends it doesn't exist.

viewtopic.php?p=653087#p653087
https://imgur.com/a/pwJO0Pb

I explained it here so everyone (including MX devs) would understand how easy it is to turn off CSDs in Xfce 4.16 without any bugs or side effects. Sigh.
viewtopic.php?p=652602#p652602
:turtle:

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:50 pm
by dolphin_oracle
Stuart_M wrote: Wed Oct 06, 2021 4:35 pm Here is an anomaly with the keyboard in LibreOffice, Featherpad, and Geany in MX-21_rc1.

In a text document using any of the above applications, the correct behavior when using Shift+Ctrl+Arrow is to highlight and advance the cursor left or right one word at a time.

The problem in MX-21_rc1 is that the right Shift+Ctrl+Arrow key combination will highlight and advance the cursor left or right only one character at a time.

The right Ctrl+Arrow works correctly, advancing the cursor one word at a time but without highlighting.

The left Shift+Ctrl+Arrow and LCtrl+Arrow combination works correctly.

This was not a problem in MX-21_beta1 or beta2, only rc1.
right shift + rcntrol is the X keyboard command to shift keyboards, I thought that was also true on beta2. you can change that in the system keyboard app

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:54 pm
by markol
SwampRabbit wrote: Wed Oct 06, 2021 4:08 pm @markol awesome thank you for the info! old hardware working OOTB is just as important as new hardware ;)
No problems here, Asus EEE 1000HG. Took me just over an hour to set things up.
Performance is ok as long as I don't use the machine for anything video related

Oh... and one more thing regarding the small screen: Alt+click now works (I have no idea why it didn't work before)

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-686-pae i686 bits: 32 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-686-pae 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_386 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: ASUSTeK product: 1000HG v: x.x serial: <filter> 
           Chassis: ASUSTek Computer INC. type: 10 v: x.x serial: <filter> 
           Mobo: ASUSTeK model: 1000HG v: x.xx serial: <filter> BIOS: American Megatrends 
           v: 0703 date: 06/11/2009 
Battery:   ID-1: BAT0 charge: 45.8 Wh condition: 45.8/55.3 Wh (83%) volts: 8.4/8.4 
           model: ASUS 1000HG type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell 
           family: 6 model-id: 1C (28) stepping: 2 microcode: 218 L2 cache: 512 KiB 
           flags: nx pae sse sse2 sse3 ssse3 bogomips: 6399 
           Speed: 1503 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 1148 2: 1015 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass status: Not affected 
           Type: spectre_v1 status: Not affected 
           Type: spectre_v2 status: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Mobile 945GSE Express Integrated Graphics vendor: ASUSTeK 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:27ae 
           Display: x11 server: X.Org 1.20.11 driver: intel unloaded: fbdev,modesetting,vesa 
           resolution: 1024x600~65Hz 
           OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 
           Sound Server: ALSA v: k5.10.0-8-686-pae 
Network:   Device-1: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter 
           vendor: AzureWave AW-GE780 802.11bg driver: ath5k v: kernel port: ffa0 
           bus ID: 01:00.0 chip ID: 168c:001c 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet 
           vendor: ASUSTeK driver: ATL1E v: N/A port: ec00 bus ID: 03:00.0 chip ID: 1969:1026 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 223.57 GiB used: 5.70 GiB (2.5%) 
           ID-1: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: B1E1 
           scheme: MBR 
Partition: ID-1: / raw size: 220.56 GiB size: 216.04 GiB (97.95%) used: 5.70 GiB (2.6%) fs: ext4 
           dev: /dev/sda1 
           ID-2: swap-1 size: 3.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 61.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 1160 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://ftp.arnes.si/mirrors/mxlinux/packages/mx/repo/ bullseye main non-free
Info:      Processes: 189 Uptime: 21m Memory: 1.96 GiB used: 727.3 MiB (36.3%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 4:59 pm
by figueroa
dolphin_oracle wrote: Wed Oct 06, 2021 4:27 pm
figueroa wrote: Wed Oct 06, 2021 4:06 pm No longer any way around having client side decorations? My favorite feature of MX-21 betas was being able to turn off CSD.
the switches in mx-tweak are still available, but you'll need to install gtk3-nocsd on your own. performance of that library was iffy and I do not consider it good enough to ship by default.
Thank you DO. I've been quite pleased with it. I thought it was like having a magic key, though I did not realize it was a separate library. I'll experiment with it in the rc1. Will advise of any issues.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 5:22 pm
by Stuart_M
dolphin_oracle wrote: Wed Oct 06, 2021 4:50 pm right shift + rcntrol is the X keyboard command to shift keyboards, I thought that was also true on beta2. you can change that in the system keyboard app
Changing the keyboard layout is not the solution, and I highly doubt this issue is specific to just me.

It was never a problem using the right Ctrl+Shift+Arrow key combination to highlight complete words in a text document (LibreOffice, Featherpad, Geany) in MX-18, MX-19, MX-21_beta1 and beta2.

All of a sudden that right-side key combination no longer functions correctly in MX-21_rc1.

It's a simple test. I wonder how many others experience the same problem as detailed in my Post #36 viewtopic.php?p=655886#p655886.

MX-19 is looking better the more MX-21 progresses.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 5:38 pm
by dolphin_oracle
Stuart_M wrote: Wed Oct 06, 2021 5:22 pm
dolphin_oracle wrote: Wed Oct 06, 2021 4:50 pm right shift + rcntrol is the X keyboard command to shift keyboards, I thought that was also true on beta2. you can change that in the system keyboard app
Changing the keyboard layout is not the solution, and I highly doubt this issue is specific to just me.

It was never a problem using the right Ctrl+Shift+Arrow key combination to highlight complete words in a text document (LibreOffice, Featherpad, Geany) in MX-18, MX-19, MX-21_beta1 and beta2.

All of a sudden that right-side key combination no longer functions correctly in MX-21_rc1.

It's a simple test. I wonder how many others experience the same problem as detailed in my Post #36 viewtopic.php?p=655886#p655886.

MX-19 is looking better the more MX-21 progresses.
we did change the keyboard shift key. its not the layout per se, its a key combo used by all layouts. it used to be just "rcontrol". so that is the solution.

given that arrows are on the right and their are control and shifts on the left, which would be natural for two-handed use, I bet few have run across it. but I see your point. We actually changed it from something I considered even worse which was alt+space.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 5:39 pm
by SwampRabbit
dreamer wrote: Wed Oct 06, 2021 4:45 pm Just use libxfce4ui-nocsd like everyone else. Even SwampRabbit posted a screenshot showing libxfce4ui-nocsd so I don't know why he pretends it doesn't exist.

viewtopic.php?p=653087#p653087
https://imgur.com/a/pwJO0Pb

I explained it here so everyone (including MX devs) would understand how easy it is to turn off CSDs in Xfce 4.16 without any bugs or side effects. Sigh.
viewtopic.php?p=652602#p652602
:turtle:
Cool it! Did I say or pretend it doesn't exist? No I did not, no one has. The post of mine that you are linking to has nothing to do with CSD or no CSD... we were talking about Docklike Taskbar.

As already stated by dolphin, myself, and many other people since the Betas... the whole thing is flaky.... there's like 90 different nocsd implementations spread across the universe right now.

You know how to get it to perfectly work perfectly on MX... please explain to us dummies again and show us exactly how "everyone else" does it then... prove it works without any issues in any way on MX 21.

Right now we're working tons of different so called "easy" things for this RC .... we don't need no roundabout snide attitudes. I won't stand for this childish nonsense, noCSD can shove it for all I personally care, and I won't touch anything related to it until people grow up. Don't type my screen name... don't talk about the dev team or the community... RAWR! :soapbox:

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 5:41 pm
by dolphin_oracle
SwampRabbit wrote: Wed Oct 06, 2021 5:39 pm
dreamer wrote: Wed Oct 06, 2021 4:45 pm Just use libxfce4ui-nocsd like everyone else. Even SwampRabbit posted a screenshot showing libxfce4ui-nocsd so I don't know why he pretends it doesn't exist.

viewtopic.php?p=653087#p653087
https://imgur.com/a/pwJO0Pb

I explained it here so everyone (including MX devs) would understand how easy it is to turn off CSDs in Xfce 4.16 without any bugs or side effects. Sigh.
viewtopic.php?p=652602#p652602
:turtle:
Cool it! Did I say or pretend it doesn't exist? No I did not, no one has. The post of mine that you are linking to has nothing to do with CSD or no CSD... we were talking about Docklike Taskbar.

As already stated by dolphin, myself, and many other people since the Betas... the whole thing is flaky.... there's like 90 different nocsd implementations spread across the universe right now.

You know how to get it to perfectly work perfectly on MX... please explain to us dummies again and show us exactly how "everyone else" does it then... prove it works without any issues in any way on MX 21.

Right now we're working tons of different so called "easy" things for this RC .... we don't need no roundabout snide attitudes. I won't stand for this childish nonsense, noCSD can shove it for all I personally care, and I won't touch anything related to it until people grow up. Don't type my screen name... don't talk about the dev team or the community... RAWR! :soapbox:
I dont pretend it doesn't exist either, it just doesn't actually do what we wanted as it only affects Xfce apps that use libxfce4ui. but more power to you, it is an option.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 5:48 pm
by Stuart_M
dolphin_oracle wrote: Wed Oct 06, 2021 5:38 pm ...we did change the keyboard shift key. ...so that is the solution.
Thank you for the explanation and especially thanks (!) for making is such an easy decision to remain on MX-19.4.

My testing is finished.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 5:50 pm
by dolphin_oracle
Stuart_M wrote: Wed Oct 06, 2021 5:48 pm
dolphin_oracle wrote: Wed Oct 06, 2021 5:38 pm ...we did change the keyboard shift key. ...so that is the solution.
Thank you for the explanation and especially thanks (!) for making is such an easy decision to remain on MX-19.4.

My testing is finished.
nothing wrong with 19.4 who knows, your comment here may change my mind. I've been known to take user feedback. :p

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 6:41 pm
by dreamer
dolphin_oracle wrote: Wed Oct 06, 2021 5:41 pm I dont pretend it doesn't exist either, it just doesn't actually do what we wanted as it only affects Xfce apps that use libxfce4ui. but more power to you, it is an option.
No, but honestly d_o. I absolutely think it's you who are kidding me and not the other way around. It works perfectly on MX-21, even better than on MX-19 - zero issues. I have no clue what kind of issues you may have run into with libxfce4ui-nocsd. I will continue using it with MX-21. I'm pretty confident it will continue to provide exactly what I want - the Xfce 4.14 experience.

I wanted to make sure you are aware of libxfce4ui-nocsd and as I said it is impossible for me to understand that you experience issues with it. I have no clue what those issues could be.

Anyway, I hope you (or SwampRabbit) don't block libxfce4ui-nocsd with special updates, because this is the thing that makes Xfce 4.16 usable IMO. The dev has done a great job with it and he pushes forward with Xfce 4.17. I think it is here to stay and it is already kind of established. I won't mention it again, because now I know you are aware and the purpose isn't to annoy people - just to show people that the Xfce 4.14 experience is possible with Xfce 4.16.

I can post any screenshot from my MX-21 virtual machine, because it's all working smoothly and looking good with libxfce4ui-nocsd.
:happy:
SwampRabbit wrote: Wed Oct 06, 2021 5:39 pm Cool it!
I'm pretty cool actually. ;) I'm not emotional about this.
SwampRabbit wrote: Wed Oct 06, 2021 5:39 pm You know how to get it to perfectly work perfectly on MX... please explain to us dummies again and show us exactly how "everyone else" does it then... prove it works without any issues in any way on MX 21.
I have it working in MX-21, that's why it has always been a mystery to me why libxfce4ui-nocsd seemed like an alien concept to the MX devs. For people that don't like CSDs, libxfce4ui-nocsd is what they use on any Xfce distro. Tell me what kind of problems you have with it and I will see if I can replicate them.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 7:46 pm
by thinkpadx
wish some of you would chill a bit. the devs work very hard - nothing is so-called 'perfect'. busting chops is not a class act IMHO.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 7:56 pm
by richb
From the rules:
Keep personal problems off the forums. Let's try to keep peace among the community and for visitors. Before submitting a post, pause and consider KNIT. Is the post Kind. Necessary, Informed, True.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 8:27 pm
by dolphin_oracle
thinkpadx wrote: Wed Oct 06, 2021 7:46 pm wish some of you would chill a bit. the devs work very hard - nothing is so-called 'perfect'. busting chops is not a class act IMHO.
thanks for the reminder. I was feeling myself getting cranky. it all good now. :happy:

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 9:16 pm
by thinkpadx
was not directed at you DO or any devs. you guys are slogging away trying to turn out a finished distro. i admire you people.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 06, 2021 11:45 pm
by Jamesthedisciple
Screenshot_2021-10-07_15-40-42-small.png
Greetings,
My experience:
Clean Install Beta2 & upgrade to RC1.
I've had a quick look to mack sure I wasn't repeating, apologies if I do.
Installed cleanly and saved "Home".

Grub os-prober doesn't propergate enteries for Arch/Antix linux, so it fails to boot. OK for Devuan, Gentoo and Obarun.
The last line of entry being:
initrd /boot/intel-ucode.img
When it should be:
initrd /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux.img
I've manually edited with grub-customiser. However, apparently grub-tools solves the problem, but not available in repos.

As mentioned before about themes. They can be changed in xfce settings/appearance and all but the MX apps will conform. The MX stay with the blue border.

Firefox browser only: Right button mouse menu is too close to the pointer and opens new window when button lifted. To stop this annoying feature either the mouse needs to move or button held down to select another option.

TLP settings fail to be acted upon. Battery charging values set to 25-80% and it charges to 100%. I think I noticed this when I upgraded from mx 19.4 to Beta 1.

New Topic

Posted: Wed Oct 06, 2021 11:53 pm
by roy
appimage do not run on double click, unlike MX-19

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 1:11 am
by entropyfoe
Looking good here so far.

Downloaded iso from sourceforge, 64 bit. md5 was good, so burned to a USB stick with the MX USB Creator in the beta2.
Booted and hit install, 7 minutes later rebooted to the new MX21.

Installer was no problem, installing to my testing partition. Reused the existing swap.
I updated grub in MX 19.4, and rebooted.

All working so far, configured sound card with the MX tool, works, installed nvidia driver (460.91.03-1) with the MX tool. Rebooted.
No problem.
USB unmounter behavior normal.
Suspends to RAM and wakes up properly.
Synaptic installed the usual list, with dependencies, libs... 161 packages
The data drive was automatically mounted, though in tweak ->other I did enable mounting of internal drives by non-root users and Root for administrative tasks.

Bleachbit only removed 11MB, and another reboot for testing stability after all the changes. Still have to tweak firefox, but the usual stuff is working. :happy:

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME X470-PRO v: Rev X.0x serial: <filter> 
           UEFI [Legacy]: American Megatrends v: 5204 date: 07/29/2019 
CPU:       Topology: 6-Core model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen 
           family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701013 
           L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 91026 
           Speed: 3809 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2196 
           2: 2196 3: 2195 4: 2196 5: 2195 6: 2195 7: 2195 8: 2195 9: 2193 10: 2195 11: 2195 
           12: 2196 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: always-on, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Micro-Star MSI driver: nvidia 
           v: 460.91.03 bus ID: 09:00.0 chip ID: 10de:128b 
           Display: x11 server: X.Org 1.20.11 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 460.91.03 
           direct render: Yes 
Audio:     Device-1: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI driver: snd_hda_intel 
           v: kernel bus ID: 09:00.1 chip ID: 10de:0e0f 
           Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 0b:00.4 chip ID: 1022:1487 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: e000 
           bus ID: 07:00.0 chip ID: 8086:1539 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.14 TiB used: 540.11 GiB (46.4%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB 
           block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: 2B2QEXM7 scheme: MBR 
           ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR 
Partition: ID-1: / raw size: 88.35 GiB size: 86.41 GiB (97.80%) used: 7.27 GiB (8.4%) fs: ext4 
           dev: /dev/nvme0n1p4 
           ID-2: swap-1 size: 32.23 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/nvme0n1p2 
Sensors:   System Temperatures: cpu: 51.6 C mobo: N/A gpu: nvidia temp: 49 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 50% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
Info:      Processes: 303 Uptime: 1h 53m Memory: 31.34 GiB used: 2.23 GiB (7.1%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 2:23 am
by i_ri
hello dolphin_oracle
hello chrispop99
hello gsm

turns OFF every ten minutes.
beta1 did this; then, user changed some power manager settings to Never and never looked back on the problem after [#199,#222,##603-614,#648]reporting it in the beta1 thread. gsm, look to those posts in beta1 thread for discussion.(?)
Now here it is in rc1. it turns off every ten minutes with its default settings.
Four machines tested , all same behavior, ten minute idle blanking leads to lost session or special intervention cntrl alt F1, F2, F7, F10, or the tweak set to use intel seems to work, chrispop99, but it changes settings when two displays are in use.

post rc1 number 17 by member gsm indicates this. cursor only.

I think chrispop99 mention three machines, i mention four machines, gsm one mention.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A serial: <filter> 
           Chassis: Hewlett-Packard type: 3 serial: <filter> 
           Mobo: MSI model: IONA v: 1.0 serial: <filter> BIOS: American Megatrends v: 5.15 
           date: 06/25/2010 
CPU:       Topology: Dual Core model: Intel Core i3 530 bits: 64 type: MT MCP arch: Nehalem 
           family: 6 model-id: 25 (37) stepping: 2 microcode: 11 L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 23410 
           Speed: 1621 MHz min/max: 1200/2933 MHz Core speeds (MHz): 1: 1869 2: 1769 3: 2023 
           4: 1666 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0042 
           Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Hewlett-Packard driver: r8169 v: kernel port: d800 bus ID: 01:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 29.11 GiB used: 6.67 GiB (22.9%) 
           ID-1: /dev/sda type: USB vendor: SanDisk model: Cruzer Glide size: 29.11 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.27 scheme: MBR 
RAID:      Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: c080 
           bus ID: 00:1f.2 chip ID: 8086.2822 rev: 06 
Partition: ID-1: / raw size: 27.61 GiB size: 27.00 GiB (97.82%) used: 6.67 GiB (24.7%) fs: ext4 
           dev: /dev/sda1 
           ID-2: swap-1 size: 1.50 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 37.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
Info:      Processes: 215 Uptime: 5m Memory: 7.64 GiB used: 927.0 MiB (11.9%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 4:40 am
by gnze796
I recently found out MX Linux and it's been a joy to use on my main Laptop, couldn't ask for anything better performance and easy to install interface.
The only issue I have with this is that even RC1 doesn't seem to work with my Intel Celeron N4500 HTPC, even with the new kernel.
But Ubuntu flavours work somehow (currently stuck on Lubuntu 21.04 on this machine), my guess is that it has to do something with the graphical driver itself, since I can't change resolutions either

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 6:32 am
by dolphin_oracle
Jamesthedisciple wrote: Wed Oct 06, 2021 11:45 pm Screenshot_2021-10-07_15-40-42-small.pngGreetings,
My experience:
Clean Install Beta2 & upgrade to RC1.
I've had a quick look to mack sure I wasn't repeating, apologies if I do.
Installed cleanly and saved "Home".

Grub os-prober doesn't propergate enteries for Arch/Antix linux, so it fails to boot. OK for Devuan, Gentoo and Obarun.
The last line of entry being:
initrd /boot/intel-ucode.img
When it should be:
initrd /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux.img
I've manually edited with grub-customiser. However, apparently grub-tools solves the problem, but not available in repos.

As mentioned before about themes. They can be changed in xfce settings/appearance and all but the MX apps will conform. The MX stay with the blue border.

Firefox browser only: Right button mouse menu is too close to the pointer and opens new window when button lifted. To stop this annoying feature either the mouse needs to move or button held down to select another option.

TLP settings fail to be acted upon. Battery charging values set to 25-80% and it charges to 100%. I think I noticed this when I upgraded from mx 19.4 to Beta 1.
On Firefox menu issue remove gtk3-nocsd package. This was still present on beta2 but has been removed from rc1. The library is responsible for all sorts of weird little gtk an window manager issues.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 7:07 am
by gsm
Because of a resume problem, where only the cursor is returned after the screen was turned of, i used MX Tweak to select the intel driver for my HP Mini 110 netbook.
Resume, after the screen was turned off is working now.

However, i have now a new more serious problem:
Several functions from the control panel do not start, e.g. MX Tweak, Window decorations and also MX Tools cannot be opened.
Also instead of auto-login i need now to type my password to log in. The system seems to work slower.
In the Start Menu, Settings, i changed MX Tweak to start it in a terminal window.
It shows that a theme module for clearlooks could not be found in the module path.
No clearlooks packages can be found with Synaptic or with the MX Package Manager either.
Any ideas how to fix this.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 7:19 am
by chrispop99
gnze796 wrote: Thu Oct 07, 2021 4:40 am I recently found out MX Linux and it's been a joy to use on my main Laptop, couldn't ask for anything better performance and easy to install interface.
The only issue I have with this is that even RC1 doesn't seem to work with my Intel Celeron N4500 HTPC, even with the new kernel.
But Ubuntu flavours work somehow (currently stuck on Lubuntu 21.04 on this machine), my guess is that it has to do something with the graphical driver itself, since I can't change resolutions either
Welcome to the forum.

Please reply with your Quick System Information, and more details about how it doesn't work.

Chris

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 7:34 am
by AdamK
Small bug report:
Using F4 for the Drop down terminal only works on the Primary Display. Even though my cursor is on another display, the drop down appears on the primary. Move to monitor with pointer is checked in Preferences -> Drop-down tab -> Position.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 7:42 am
by Jamesthedisciple
dolphin_oracle wrote: Thu Oct 07, 2021 6:32 am
On Firefox menu issue remove gtk3-nocsd package. This was still present on beta2 but has been removed from rc1. The library is responsible for all sorts of weird little gtk an window manager issues.
Sorted, thank you.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 8:33 am
by TOMCAT
gsm wrote: Thu Oct 07, 2021 7:07 am Because of a resume problem, where only the cursor is returned after the screen was turned of, i used MX Tweak to select the intel driver for my HP Mini 110 netbook.
Resume, after the screen was turned off is working now.

However, i have now a new more serious problem:
Several functions from the control panel do not start, e.g. MX Tweak, Window decorations and also MX Tools cannot be opened.
Also instead of auto-login i need now to type my password to log in. The system seems to work slower.
In the Start Menu, Settings, i changed MX Tweak to start it in a terminal window.
It shows that a theme module for clearlooks could not be found in the module path.
No clearlooks packages can be found with Synaptic or with the MX Package Manager either.
Any ideas how to fix this.
Several functions from the control panel do not start, e.g. MX Tweak, Window decorations and also MX Tools cannot be opened.

This happens when I turn off the "policykit" boot startup item. Not sure if it's the same reason .

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 8:38 am
by dolphin_oracle
TOMCAT wrote: Thu Oct 07, 2021 8:33 am
gsm wrote: Thu Oct 07, 2021 7:07 am Because of a resume problem, where only the cursor is returned after the screen was turned of, i used MX Tweak to select the intel driver for my HP Mini 110 netbook.
Resume, after the screen was turned off is working now.

However, i have now a new more serious problem:
Several functions from the control panel do not start, e.g. MX Tweak, Window decorations and also MX Tools cannot be opened.
Also instead of auto-login i need now to type my password to log in. The system seems to work slower.
In the Start Menu, Settings, i changed MX Tweak to start it in a terminal window.
It shows that a theme module for clearlooks could not be found in the module path.
No clearlooks packages can be found with Synaptic or with the MX Package Manager either.
Any ideas how to fix this.
Several functions from the control panel do not start, e.g. MX Tweak, Window decorations and also MX Tools cannot be opened.

This happens when I turn off the "policykit" boot startup item. Not sure if it's the same reason .
Yea you need to keep policykit. It’s a necessary component

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 8:46 am
by thinkpadx

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 9:00 am
by gsm
TOMCAT wrote: Thu Oct 07, 2021 8:33 am
gsm wrote: Thu Oct 07, 2021 7:07 am Because of a resume problem, where only the cursor is returned after the screen was turned of, i used MX Tweak to select the intel driver for my HP Mini 110 netbook.
Resume, after the screen was turned off is working now.

However, i have now a new more serious problem:
Several functions from the control panel do not start, e.g. MX Tweak, Window decorations and also MX Tools cannot be opened.
Also instead of auto-login i need now to type my password to log in. The system seems to work slower.
In the Start Menu, Settings, i changed MX Tweak to start it in a terminal window.
It shows that a theme module for clearlooks could not be found in the module path.
No clearlooks packages can be found with Synaptic or with the MX Package Manager either.
Any ideas how to fix this.
Several functions from the control panel do not start, e.g. MX Tweak, Window decorations and also MX Tools cannot be opened.

This happens when I turn off the "policykit" boot startup item. Not sure if it's the same reason .
I did not turn anything off. PolicyKit Authentication Agent is still enabled as an auto start item.
The system is almost totally broken, so i will try a clean reinstall.

After the reinstall:
Same problem with resume and when Intel driver is selected, followed by a reboot, then quite a few things are broken and i cannot start MX Tweak again to revert from the Intel driver.
Note that Manjaro Grub is used at MBR and MX Grub is as PBR at the root partition.

EDIT
I don't know how it happened, but like magic everything is resumed now, after the screen went off and moving the mouse, so not only the cursor.
There were many updates just before. Looks like an update solved this issue at least
I will once more reinstall RC1 and try to figure out what happened exactly.
The intel driver problem remains however.

EDIT 2
Ending up with only a cursor on the black screen is related to the Xfmw Compositor.
The screen is resumed with only a moving cursor, after a timeout period without action.
When a laptop is closed (screen folded down), the screen is also turned off by default, but will resume normally with full functionality, when the laptop is opened again.
I found that the odd behavior resuming after timeout only happens when the Xfmw (Xfce) Compositor is active.
When no Compositor or when Compton is selected and applied, then my HP mini 110 laptop will resume the screen normally in any case.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 9:46 am
by dolphin_oracle
to manually revert the intel driver, you can delete the /etc/X11/Xorg.conf.d/20-intel.conf and reboot.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 10:13 am
by gsm
dolphin_oracle wrote: Thu Oct 07, 2021 9:46 am to manually revert the intel driver, you can delete the /etc/X11/Xorg.conf.d/20-intel.conf and reboot.
Thanks!
In the meantime i was trying Beta2. Same symptoms!
After deleting 20-intel.conf and reboot, everything is back to as it was before without the Intel driver.
Also only cursor after resume.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 10:21 am
by dolphin_oracle
gsm wrote: Thu Oct 07, 2021 10:13 am
dolphin_oracle wrote: Thu Oct 07, 2021 9:46 am to manually revert the intel driver, you can delete the /etc/X11/Xorg.conf.d/20-intel.conf and reboot.
Thanks!
In the meantime i was trying Beta2. Same symptoms!
After deleting 20-intel.conf and reboot, everything is back to as it was before without the Intel driver.
Also only cursor after resume.
I'm going to play around with switching to the intel driver tonight and see if I can replicate the issue.

It almost sounds like your Xsession is crashing though. you might try disabling Display Power Management in the Xfce power settings.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 10:42 am
by i_ri
hello dolphin_oracle and gsm
When I tried the "use intel" tweak to solve the blanking
it was running live on two displays. I saw right away the change upon logging out ; no need to restart. It mirrored instead of extending displays. It was possible to uncheck the tweak box and revert the intel checkbox by log-out and log-in. There were no problems alike gsm's machine's issue in accessing mxtweak.Other.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 10:44 am
by dolphin_oracle
Stuart_M wrote: Wed Oct 06, 2021 2:03 pm mx-installer 21.10.03 in MX-21 will not install if the swap size is edited.

I am installing MX-21_rc1 in a 250GB SSD that is completely unallocated. The ISO integrity checked okay with both (sha256 and signature).

The installation was successful using the Template for an encrypted system, accepting all the default settings for a 250GB SSD. The resulting partition sizes are:
  • sda1 256.0 MB
  • sda2 512.0 MB
  • sda3 224.1 GB
  • sda4 8.0 GB
Here is the problem. I used the same Template and conditions that produced the successful installation above, but made just one change - the swap size was changed. I tried four different sizes, all producing the same error.
  • 512MB
  • 1000MB
  • 2GB
  • no swap (the swap partition was removed with the installer)
At the 9% mark ("Creating encrypted volume: sda3") an error message appears "Failed to prepare required partitions". (Note that the error was at the 10% mark when installing without swap.)Install 9% Error.png

Below are two minstall.log files after a failed installation. After each failed installation I rebooted to start fresh.



The below is the minstall.log file after a failed installation with a 2GB swap size:

Code: Select all

2021-10-06 12:52:16.220 DBG default: Installer version: 21.10.03
2021-10-06 12:52:16.337 DBG default: +++ void MInstall::startup() +++
2021-10-06 12:52:16.342 DBG default: check for remastered home demo folder: false
2021-10-06 12:52:16.342 DBG default: Exec #1: du -sb /live/aufs/boot
2021-10-06 12:52:16.398 DBG default: Exit #1: 0 QProcess::NormalExit
2021-10-06 12:52:16.398 DBG default: linuxfs file is at :  "/live/boot-dev/antiX/linuxfs"
2021-10-06 12:52:16.398 DBG default: Exec #2: dd if=/live/boot-dev/antiX/linuxfs bs=1 skip=20 count=2 status=none 2>/dev/null | od -An -tdI
2021-10-06 12:52:16.408 DBG default: Exit #2: 0 QProcess::NormalExit
2021-10-06 12:52:16.408 DBG default: linuxfs compression type is  "6" compression factor is  25
2021-10-06 12:52:16.408 DBG default: Exec #3: df /live/linux --output=used --total |tail -n1
2021-10-06 12:52:16.416 DBG default: Exit #3: 0 QProcess::NormalExit
2021-10-06 12:52:16.416 DBG default: linuxfs file size is  7312769024  rootfs file size is  0
2021-10-06 12:52:16.417 DBG default: Minimum space: 268435456 (boot), 8386510848 (root)
2021-10-06 12:52:16.417 DBG default: Exec #4: uname -m | grep -q i686
2021-10-06 12:52:16.423 DBG default: Exit #4: 1 QProcess::NormalExit
2021-10-06 12:52:16.423 DBG default: uefi = true
2021-10-06 12:52:16.423 DBG default: +++ void MInstall::setupAutoMount(bool) +++
2021-10-06 12:52:16.424 DBG default: Exec #5: ps -e | grep 'udisksd'
2021-10-06 12:52:16.443 DBG default: SOut #5: "   9459 ?        00:00:00 udisksd\n"
2021-10-06 12:52:16.443 DBG default: Exit #5: 0 QProcess::NormalExit
2021-10-06 12:52:16.443 DBG default: Exec #6: egrep -l '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d
2021-10-06 12:52:16.456 DBG default: SErr #6: "grep: /lib/udev/rules.d: Is a directory\n"
2021-10-06 12:52:16.456 DBG default: Exit #6: 2 QProcess::NormalExit
2021-10-06 12:52:16.456 DBG default: Exec #7: systemctl list-units --full --all -t mount --no-legend 2>/dev/null | grep -v masked | cut -f1 -d' ' | egrep -v '^(dev-hugepages|dev-mqueue|proc-sys-fs-binfmt_misc|run-user-.*-gvfs|sys-fs-fuse-connections|sys-kernel-config|sys-kernel-debug)'
2021-10-06 12:52:16.465 DBG default: Exit #7: 1 QProcess::NormalExit
2021-10-06 12:52:16.466 DBG default: MkPath(SUCCESS): "/run/udev/rules.d"
2021-10-06 12:52:16.466 DBG default: Exec #8: echo 'SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1"' > /run/udev/rules.d/91-mx-udisks-inhibit.rules
2021-10-06 12:52:16.471 DBG default: Exit #8: 0 QProcess::NormalExit
2021-10-06 12:52:16.471 DBG default: Exec #9: udevadm control --reload
2021-10-06 12:52:16.480 DBG default: Exit #9: 0 QProcess::NormalExit
2021-10-06 12:52:16.480 DBG default: Exec #10: udevadm trigger --subsystem-match=block
2021-10-06 12:52:16.490 DBG default: Exit #10: 0 QProcess::NormalExit
2021-10-06 12:52:16.490 DBG default: Exec #11: /bin/ls -1 /home | grep -Ev '(lost\+found|demo|snapshot)' | grep -q [a-zA-Z0-9]
2021-10-06 12:52:16.498 DBG default: Exit #11: 1 QProcess::NormalExit
2021-10-06 12:52:16.498 DBG default: check for possible snapshot: false
2021-10-06 12:52:16.561 DBG default: +++ void MInstall::setupkeyboardbutton() +++
2021-10-06 12:52:16.562 DBG default: Exec #12: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
2021-10-06 12:52:16.573 DBG default: Exit #12: 0 QProcess::NormalExit
2021-10-06 12:52:16.575 DBG default: Exec #13: locale -a | grep -Ev '^(C|POSIX)\.?' | grep -E 'utf8|UTF-8'
2021-10-06 12:52:16.583 DBG default: Exit #13: 0 QProcess::NormalExit
2021-10-06 12:52:16.584 DBG default: Exec #14: grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus
2021-10-06 12:52:16.652 DBG default: Exit #14: 1 QProcess::NormalExit
2021-10-06 12:52:16.652 DBG default: Exec #15: dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'
2021-10-06 12:52:16.682 DBG default: Exit #15: 0 QProcess::NormalExit
2021-10-06 12:52:16.682 DBG default: +++ void MInstall::buildServiceList() +++
2021-10-06 12:52:16.689 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 12:52:16.690 DBG default: Exec #16: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 12:52:16.703 DBG default: Exit #16: 0 QProcess::NormalExit
2021-10-06 12:52:16.703 DBG default: Exec #17: partprobe -s
2021-10-06 12:52:16.837 DBG default: SOut #17: "/dev/sda: gpt partitions 1 2 3 4\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:52:16.837 DBG default: Exit #17: 0 QProcess::NormalExit
2021-10-06 12:52:16.837 DBG default: Exec #18: blkid -c /dev/null
2021-10-06 12:52:16.877 DBG default: SOut #18: "/dev/sda1: LABEL_FATBOOT=\"EFI System\" LABEL=\"EFI System\" UUID=\"3213-3F0E\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTLABEL=\"primary\" PARTUUID=\"b6cb2e10-f793-4490-9e81-9c8b8c20c89e\"\n/dev/sda2: LABEL=\"boot\" UUID=\"5a269835-0830-44d2-b214-5156592c74fb\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTLABEL=\"primary\" PARTUUID=\"bda2eb7a-ead9-41a9-bc2c-31b28c620246\"\n/dev/sda3: UUID=\"3b4dbee4-1427-4894-8f3a-c71ae8b47122\" TYPE=\"crypto_LUKS\" PARTLABEL=\"primary\" PARTUUID=\"0a3ae745-f740-426f-a021-0ea6d42bb25f\"\n/dev/sda4: UUID=\"fa6d9afe-8c56-45d3-95f9-090c0ebd3088\" TYPE=\"crypto_LUKS\" PARTLABEL=\"primary\" PARTUUID=\"0b806862-b50e-40ab-abbc-e280f8cedbae\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 12:52:16.877 DBG default: Exit #18: 0 QProcess::NormalExit
2021-10-06 12:52:16.877 DBG default: Exec #19: parted -lm
2021-10-06 12:52:16.915 DBG default: Exit #19: 0 QProcess::NormalExit
2021-10-06 12:52:16.916 DBG default: Exec #20: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 12:52:16.925 DBG default: Exit #20: 32 QProcess::NormalExit
2021-10-06 12:52:21.989 DBG default: Exec #21: /usr/sbin/gparted
2021-10-06 12:52:34.405 DBG default: SOut #21: "GParted 1.2.0\nconfiguration --enable-libparted-dmraid --enable-online-resize\nlibparted 3.4\n"
2021-10-06 12:52:34.405 DBG default: Exit #21: 0 QProcess::NormalExit
2021-10-06 12:52:34.405 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 12:52:34.407 DBG default: Exec #22: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 12:52:34.415 DBG default: Exit #22: 0 QProcess::NormalExit
2021-10-06 12:52:34.415 DBG default: Exec #23: partprobe -s
2021-10-06 12:52:34.529 DBG default: SOut #23: "/dev/sda: gpt partitions\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:52:34.529 DBG default: Exit #23: 0 QProcess::NormalExit
2021-10-06 12:52:34.529 DBG default: Exec #24: blkid -c /dev/null
2021-10-06 12:52:34.569 DBG default: SOut #24: "/dev/sda: PTUUID=\"4ca2c105-553d-4a8b-b88b-6c1fff6b56a9\" PTTYPE=\"gpt\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 12:52:34.569 DBG default: Exit #24: 0 QProcess::NormalExit
2021-10-06 12:52:34.569 DBG default: Exec #25: parted -lm
2021-10-06 12:52:34.607 DBG default: Exit #25: 0 QProcess::NormalExit
2021-10-06 12:52:34.607 DBG default: Exec #26: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 12:52:34.617 DBG default: Exit #26: 32 QProcess::NormalExit
2021-10-06 12:53:13.967 DBG default: Mount points:
2021-10-06 12:53:13.968 DBG default:  - "/" - "sda3" "root.fsm" "/dev/mapper/root.fsm"
2021-10-06 12:53:13.968 DBG default:  - "/boot" - "sda2" "sda2" "/dev/sda2"
2021-10-06 12:53:13.968 DBG default:  - "SWAP" - "sda4" "swap" "/dev/mapper/swap"
2021-10-06 12:53:15.383 DBG default: +++ bool MInstall::saveHomeBasic() +++
2021-10-06 12:53:15.393 WRN qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2822, resource id: 18885531, major code: 40 (TranslateCoords), minor code: 0
2021-10-06 12:53:15.420 DBG default: - Preparing to install MX Linux -
2021-10-06 12:53:15.422 DBG default: Exec #27: smartctl -H /dev/sda
2021-10-06 12:53:15.456 DBG default: SOut #27: "smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-8-amd64] (local build)\nCopyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org\n\n=== START OF READ SMART DATA SECTION ===\nSMART overall-health self-assessment test result: PASSED\n\n"
2021-10-06 12:53:15.456 DBG default: Exit #27: 0 QProcess::NormalExit
2021-10-06 12:53:15.456 DBG default: Exec #28: smartctl -A /dev/sda| grep -E "^  5|^196|^197|^198" | awk '{ if ( $10 != 0 ) { print $1,$2,$10} }'
2021-10-06 12:53:15.484 DBG default: Exit #28: 0 QProcess::NormalExit
2021-10-06 12:53:15.484 DBG default: +++ void MInstall::cleanup(bool) +++
2021-10-06 12:53:15.487 DBG default: Exec #29: /bin/umount -l /mnt/antiX/boot/efi
2021-10-06 12:53:15.497 DBG default: SErr #29: "umount: /mnt/antiX/boot/efi: no mount point specified.\n"
2021-10-06 12:53:15.498 DBG default: Exit #29: 32 QProcess::NormalExit
2021-10-06 12:53:15.498 DBG default: Exec #30: /bin/umount -l /mnt/antiX/proc
2021-10-06 12:53:15.507 DBG default: SErr #30: "umount: /mnt/antiX/proc: no mount point specified.\n"
2021-10-06 12:53:15.507 DBG default: Exit #30: 32 QProcess::NormalExit
2021-10-06 12:53:15.507 DBG default: Exec #31: /bin/umount -l /mnt/antiX/sys
2021-10-06 12:53:15.516 DBG default: SErr #31: "umount: /mnt/antiX/sys: no mount point specified.\n"
2021-10-06 12:53:15.516 DBG default: Exit #31: 32 QProcess::NormalExit
2021-10-06 12:53:15.516 DBG default: Exec #32: /bin/umount -l /mnt/antiX/dev/shm
2021-10-06 12:53:15.523 DBG default: SErr #32: "umount: /mnt/antiX/dev/shm: no mount point specified.\n"
2021-10-06 12:53:15.523 DBG default: Exit #32: 32 QProcess::NormalExit
2021-10-06 12:53:15.523 DBG default: Exec #33: /bin/umount -l /mnt/antiX/dev
2021-10-06 12:53:15.532 DBG default: SErr #33: "umount: /mnt/antiX/dev: no mount point specified.\n"
2021-10-06 12:53:15.532 DBG default: Exit #33: 32 QProcess::NormalExit
2021-10-06 12:53:15.532 DBG default: Exec #34: swapoff /dev/sda2
2021-10-06 12:53:15.543 DBG default: SErr #34: "swapoff: /dev/sda2: swapoff failed: No such file or directory\n"
2021-10-06 12:53:15.543 DBG default: Exit #34: 4 QProcess::NormalExit
2021-10-06 12:53:15.543 DBG default: Exec #35: /bin/umount -l /mnt/antiX/boot
2021-10-06 12:53:15.553 DBG default: SErr #35: "umount: /mnt/antiX/boot: no mount point specified.\n"
2021-10-06 12:53:15.553 DBG default: Exit #35: 32 QProcess::NormalExit
2021-10-06 12:53:15.553 DBG default: Exec #36: swapoff /dev/mapper/root.fsm
2021-10-06 12:53:15.562 DBG default: SErr #36: "swapoff: /dev/mapper/root.fsm: swapoff failed: No such file or directory\n"
2021-10-06 12:53:15.562 DBG default: Exit #36: 4 QProcess::NormalExit
2021-10-06 12:53:15.562 DBG default: Exec #37: /bin/umount -l /mnt/antiX/
2021-10-06 12:53:15.570 DBG default: SErr #37: "umount: /mnt/antiX/: no mount point specified.\n"
2021-10-06 12:53:15.571 DBG default: Exit #37: 32 QProcess::NormalExit
2021-10-06 12:53:15.571 DBG default: Exec #38: cryptsetup close /dev/mapper/root.fsm
2021-10-06 12:53:15.786 DBG default: SErr #38: "Device /dev/mapper/root.fsm is not active.\n"
2021-10-06 12:53:15.786 DBG default: Exit #38: 4 QProcess::NormalExit
2021-10-06 12:53:15.786 DBG default: +++ bool PartMan::preparePartitions() +++
2021-10-06 12:53:15.789 DBG default: Exec #39: lsblk -nro name /dev/sda
2021-10-06 12:53:15.798 DBG default: Exit #39: 0 QProcess::NormalExit
2021-10-06 12:53:15.798 DBG default: Exec #40: swapoff /dev/sda
2021-10-06 12:53:15.805 DBG default: SErr #40: "swapoff: /dev/sda: swapoff failed: Invalid argument\n"
2021-10-06 12:53:15.805 DBG default: Exit #40: 4 QProcess::NormalExit
2021-10-06 12:53:15.806 DBG default: Exec #41: /bin/umount /dev/sda
2021-10-06 12:53:15.814 DBG default: SErr #41: "umount: /dev/sda: not mounted.\n"
2021-10-06 12:53:15.814 DBG default: Exit #41: 32 QProcess::NormalExit
2021-10-06 12:53:15.814 DBG default: - Preparing partition tables -
2021-10-06 12:53:15.818 DBG default: Exec #42: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda
2021-10-06 12:53:15.831 DBG default: SErr #42: "64+0 records in\n64+0 records out\n4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.00343248 s, 1.2 GB/s\n"
2021-10-06 12:53:15.831 DBG default: Exit #42: 0 QProcess::NormalExit
2021-10-06 12:53:15.831 DBG default: Exec #43: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda seek=3815539
2021-10-06 12:53:15.839 DBG default: SErr #43: "dd: error writing '/dev/sda': No space left on device\n64+0 records in\n63+0 records out\n4186112 bytes (4.2 MB, 4.0 MiB) copied, 0.00186469 s, 2.2 GB/s\n"
2021-10-06 12:53:15.839 DBG default: Exit #43: 1 QProcess::NormalExit
2021-10-06 12:53:15.839 DBG default: Exec #44: parted -s /dev/sda mklabel gpt
2021-10-06 12:53:15.905 DBG default: Exit #44: 0 QProcess::NormalExit
2021-10-06 12:53:15.905 DBG default: - Preparing required partitions -
2021-10-06 12:53:15.910 DBG default: Exec #45: parted -s --align optimal /dev/sda mkpart primary 1MiB 257MiB
2021-10-06 12:53:15.965 DBG default: Exit #45: 0 QProcess::NormalExit
2021-10-06 12:53:15.969 DBG default: Exec #46: parted -s --align optimal /dev/sda mkpart primary 257MiB 769MiB
2021-10-06 12:53:16.045 DBG default: Exit #46: 0 QProcess::NormalExit
2021-10-06 12:53:16.049 DBG default: Exec #47: parted -s --align optimal /dev/sda mkpart primary 769MiB 230276MiB
2021-10-06 12:53:16.125 DBG default: Exit #47: 0 QProcess::NormalExit
2021-10-06 12:53:16.128 DBG default: Exec #48: parted -s --align optimal /dev/sda mkpart primary 230276MiB 232276MiB
2021-10-06 12:53:16.205 DBG default: Exit #48: 0 QProcess::NormalExit
2021-10-06 12:53:16.209 DBG default: Exec #49: parted -s /dev/sda set 2 legacy_boot on
2021-10-06 12:53:16.285 DBG default: Exit #49: 0 QProcess::NormalExit
2021-10-06 12:53:16.296 DBG default: Exec #50: partprobe -s
2021-10-06 12:53:16.429 DBG default: SOut #50: "/dev/sda: gpt partitions 1 2 3 4\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:53:16.429 DBG default: Exit #50: 0 QProcess::NormalExit
2021-10-06 12:53:16.429 DBG default: +++ bool PartMan::formatPartitions() +++
2021-10-06 12:53:16.433 DBG default: - Formatting: EFI System Partition -
2021-10-06 12:53:16.438 DBG default: Exec #51: mkfs.msdos -F 32 -n "EFI System" /dev/sda1
2021-10-06 12:53:16.497 DBG default: SOut #51: "mkfs.fat 4.2 (2021-01-31)\n"
2021-10-06 12:53:16.497 DBG default: SErr #51: "mkfs.fat: Warning: lowercase labels might not work properly on some systems\n"
2021-10-06 12:53:16.497 DBG default: Exit #51: 0 QProcess::NormalExit
2021-10-06 12:53:16.498 DBG default: Exec #52: parted -s /dev/sda set 1 esp on
2021-10-06 12:53:16.641 DBG default: Exit #52: 0 QProcess::NormalExit
2021-10-06 12:53:16.641 DBG default: - Formatting: /boot -
2021-10-06 12:53:16.646 DBG default: Exec #53: mkfs.ext4 -F /dev/sda2 -L "boot"
2021-10-06 12:53:16.713 DBG default: SOut #53: "Discarding device blocks:   4096/131072\b\b\b\b\b\b\b\b\b\b\b\b\b             \b\b\b\b\b\b\b\b\b\b\b\b\bdone                            \nCreating filesystem with 131072 4k blocks and 32768 inodes\nFilesystem UUID: ad312201-fcc2-4d65-8fb9-592efeab0748\nSuperblock backups stored on blocks: \n\t32768, 98304\n\nAllocating group tables: 0/4\b\b\b   \b\b\bdone                            \nWriting inode tables: 0/4\b\b\b   \b\b\bdone                            \nCreating journal (4096 blocks): done\nWriting superblocks and filesystem accounting information: 0/4\b\b\b   \b\b\bdone\n\n"
2021-10-06 12:53:16.713 DBG default: SErr #53: "mke2fs 1.46.2 (28-Feb-2021)\n"
2021-10-06 12:53:16.713 DBG default: Exit #53: 0 QProcess::NormalExit
2021-10-06 12:53:16.713 DBG default: Exec #54: /sbin/tune2fs -c0 -C0 -i1m /dev/sda2
2021-10-06 12:53:16.729 DBG default: SOut #54: "tune2fs 1.46.2 (28-Feb-2021)\nSetting maximal mount count to -1\nSetting current mount count to 0\nSetting interval between checks to 2592000 seconds\n"
2021-10-06 12:53:16.729 DBG default: Exit #54: 0 QProcess::NormalExit
2021-10-06 12:53:16.729 DBG default: - Creating encrypted volume: sda3 -
2021-10-06 12:53:16.738 DBG default: Exec #55: cryptsetup --batch-mode --key-size 512 --hash sha512 --pbkdf argon2id --sector-size=1358828544 luksFormat /dev/sda3
2021-10-06 12:53:16.747 DBG default: SErr #55: "Usage: cryptsetup [-?Vvyrq] [-?|--help] [--usage] [-V|--version]\n        [-v|--verbose] [--debug] [--debug-json] [-c|--cipher=STRING]\n        [-h|--hash=STRING] [-y|--verify-passphrase] [-d|--key-file=STRING]\n        [--master-key-file=STRING] [--dump-master-key] [-s|--key-size=BITS]\n        [-l|--keyfile-size=bytes] [--keyfile-offset=bytes]\n        [--new-keyfile-size=bytes] [--new-keyfile-offset=bytes]\n        [-S|--key-slot=INT] [-b|--size=SECTORS] [--device-size=bytes]\n        [-o|--offset=SECTORS] [-p|--skip=SECTORS] [-r|--readonly]\n        [-q|--batch-mode] [-t|--timeout=secs] [--progress-frequency=secs]\n        [-T|--tries=INT] [--align-payload=SECTORS]\n        [--header-backup-file=STRING] [--use-random] [--use-urandom]\n        [--shared] [--uuid=STRING] [--allow-discards] [--header=STRING]\n        [--test-passphrase] [--tcrypt-hidden] [--tcrypt-system]\n        [--tcrypt-backup] [--veracrypt] [--veracrypt-pim=INT]\n        [--veracrypt-query-pim] [-M|--type=STRING] [--force-password]\n        [--perf-same_cpu_crypt] [--perf-submit_from_crypt_cpus]\n        [--perf-no_read_workqueue] [--perf-no_write_workqueue] [--deferred]\n        [--serialize-memory-hard-pbkdf] [-i|--iter-time=msecs]\n        [--pbkdf=STRING] [--pbkdf-memory=kilobytes]\n        [--pbkdf-parallel=threads] [--pbkdf-force-iterations=LONG]\n        [--priority=STRING] [--disable-locks] [--disable-keyring]\n        [-I|--integrity=STRING] [--integrity-no-journal]\n        [--integrity-no-wipe] [--integrity-legacy-padding] [--token-only]\n        [--token-id=INT] [--key-description=STRING] [--sector-size=INT]\n        [--iv-large-sectors] [--persistent] [--label=STRING]\n        [--subsystem=STRING] [--unbound] [--json-file=STRING]\n        [--luks2-metadata-size=bytes] [--luks2-keyslots-size=bytes]\n        [--refresh] [--keyslot-key-size=BITS] [--keyslot-cipher=STRING]\n        [--encrypt] [--decrypt] [--init-only] [--resume-only]\n        [--reduce-device-size=bytes] [--hotzone-size=bytes]\n        [--resilience=STRING] [--resilience-hash=STRING]\n        [--active-name=STRING] [OPTION...] <action> <action-specific>\n/usr/sbin/cryptsetup: Unsupported encryption sector size.\n"
2021-10-06 12:53:16.747 DBG default: Exit #55: 1 QProcess::NormalExit
2021-10-06 12:53:16.747 DBG default: +++ void MInstall::failUI(const QString&) +++
2021-10-06 12:53:16.750 DBG default: Phase 1 - "Failed to prepare required partitions."


The below is the minstall.log file after a failed installation without swap:

Code: Select all

2021-10-06 12:59:50.284 DBG default: Installer version: 21.10.03
2021-10-06 12:59:50.395 DBG default: +++ void MInstall::startup() +++
2021-10-06 12:59:50.399 DBG default: check for remastered home demo folder: false
2021-10-06 12:59:50.399 DBG default: Exec #1: du -sb /live/aufs/boot
2021-10-06 12:59:50.452 DBG default: Exit #1: 0 QProcess::NormalExit
2021-10-06 12:59:50.452 DBG default: linuxfs file is at :  "/live/boot-dev/antiX/linuxfs"
2021-10-06 12:59:50.452 DBG default: Exec #2: dd if=/live/boot-dev/antiX/linuxfs bs=1 skip=20 count=2 status=none 2>/dev/null | od -An -tdI
2021-10-06 12:59:50.462 DBG default: Exit #2: 0 QProcess::NormalExit
2021-10-06 12:59:50.462 DBG default: linuxfs compression type is  "6" compression factor is  25
2021-10-06 12:59:50.463 DBG default: Exec #3: df /live/linux --output=used --total |tail -n1
2021-10-06 12:59:50.470 DBG default: Exit #3: 0 QProcess::NormalExit
2021-10-06 12:59:50.471 DBG default: linuxfs file size is  7312769024  rootfs file size is  0
2021-10-06 12:59:50.471 DBG default: Minimum space: 268435456 (boot), 8386510848 (root)
2021-10-06 12:59:50.471 DBG default: Exec #4: uname -m | grep -q i686
2021-10-06 12:59:50.478 DBG default: Exit #4: 1 QProcess::NormalExit
2021-10-06 12:59:50.478 DBG default: uefi = true
2021-10-06 12:59:50.478 DBG default: +++ void MInstall::setupAutoMount(bool) +++
2021-10-06 12:59:50.479 DBG default: Exec #5: ps -e | grep 'udisksd'
2021-10-06 12:59:50.493 DBG default: SOut #5: "   9366 ?        00:00:00 udisksd\n"
2021-10-06 12:59:50.493 DBG default: Exit #5: 0 QProcess::NormalExit
2021-10-06 12:59:50.493 DBG default: Exec #6: egrep -l '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d
2021-10-06 12:59:50.509 DBG default: SErr #6: "grep: /lib/udev/rules.d: Is a directory\n"
2021-10-06 12:59:50.509 DBG default: Exit #6: 2 QProcess::NormalExit
2021-10-06 12:59:50.509 DBG default: Exec #7: systemctl list-units --full --all -t mount --no-legend 2>/dev/null | grep -v masked | cut -f1 -d' ' | egrep -v '^(dev-hugepages|dev-mqueue|proc-sys-fs-binfmt_misc|run-user-.*-gvfs|sys-fs-fuse-connections|sys-kernel-config|sys-kernel-debug)'
2021-10-06 12:59:50.517 DBG default: Exit #7: 1 QProcess::NormalExit
2021-10-06 12:59:50.518 DBG default: MkPath(SUCCESS): "/run/udev/rules.d"
2021-10-06 12:59:50.518 DBG default: Exec #8: echo 'SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1"' > /run/udev/rules.d/91-mx-udisks-inhibit.rules
2021-10-06 12:59:50.522 DBG default: Exit #8: 0 QProcess::NormalExit
2021-10-06 12:59:50.522 DBG default: Exec #9: udevadm control --reload
2021-10-06 12:59:50.533 DBG default: Exit #9: 0 QProcess::NormalExit
2021-10-06 12:59:50.533 DBG default: Exec #10: udevadm trigger --subsystem-match=block
2021-10-06 12:59:50.542 DBG default: Exit #10: 0 QProcess::NormalExit
2021-10-06 12:59:50.542 DBG default: Exec #11: /bin/ls -1 /home | grep -Ev '(lost\+found|demo|snapshot)' | grep -q [a-zA-Z0-9]
2021-10-06 12:59:50.548 DBG default: Exit #11: 1 QProcess::NormalExit
2021-10-06 12:59:50.548 DBG default: check for possible snapshot: false
2021-10-06 12:59:50.606 DBG default: +++ void MInstall::setupkeyboardbutton() +++
2021-10-06 12:59:50.608 DBG default: Exec #12: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
2021-10-06 12:59:50.618 DBG default: Exit #12: 0 QProcess::NormalExit
2021-10-06 12:59:50.622 DBG default: Exec #13: locale -a | grep -Ev '^(C|POSIX)\.?' | grep -E 'utf8|UTF-8'
2021-10-06 12:59:50.633 DBG default: Exit #13: 0 QProcess::NormalExit
2021-10-06 12:59:50.634 DBG default: Exec #14: grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus
2021-10-06 12:59:50.702 DBG default: Exit #14: 1 QProcess::NormalExit
2021-10-06 12:59:50.702 DBG default: Exec #15: dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'
2021-10-06 12:59:50.730 DBG default: Exit #15: 0 QProcess::NormalExit
2021-10-06 12:59:50.730 DBG default: +++ void MInstall::buildServiceList() +++
2021-10-06 12:59:50.734 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 12:59:50.734 DBG default: Exec #16: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 12:59:50.747 DBG default: Exit #16: 0 QProcess::NormalExit
2021-10-06 12:59:50.748 DBG default: Exec #17: partprobe -s
2021-10-06 12:59:50.871 DBG default: SOut #17: "/dev/sda: gpt partitions 1 2 3\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 12:59:50.871 DBG default: Exit #17: 0 QProcess::NormalExit
2021-10-06 12:59:50.871 DBG default: Exec #18: blkid -c /dev/null
2021-10-06 12:59:50.911 DBG default: SOut #18: "/dev/sda1: LABEL_FATBOOT=\"EFI System\" LABEL=\"EFI System\" UUID=\"5916-AAC4\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTLABEL=\"primary\" PARTUUID=\"6523564d-16d9-4611-ad78-b3b42dad3449\"\n/dev/sda2: LABEL=\"boot\" UUID=\"1c1acc9d-b433-48ca-b650-620dd85eb9a4\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTLABEL=\"primary\" PARTUUID=\"2c957374-cb60-4f5e-b7be-c45ebdb2fb82\"\n/dev/sda3: UUID=\"3b4dbee4-1427-4894-8f3a-c71ae8b47122\" TYPE=\"crypto_LUKS\" PARTLABEL=\"primary\" PARTUUID=\"315647f8-f2ca-4e4a-a4b8-b761774acc54\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 12:59:50.911 DBG default: Exit #18: 0 QProcess::NormalExit
2021-10-06 12:59:50.911 DBG default: Exec #19: parted -lm
2021-10-06 12:59:50.961 DBG default: Exit #19: 0 QProcess::NormalExit
2021-10-06 12:59:50.961 DBG default: Exec #20: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 12:59:50.970 DBG default: Exit #20: 32 QProcess::NormalExit
2021-10-06 13:00:08.882 DBG default: Exec #21: /usr/sbin/gparted
2021-10-06 13:00:22.308 DBG default: SOut #21: "GParted 1.2.0\nconfiguration --enable-libparted-dmraid --enable-online-resize\nlibparted 3.4\n"
2021-10-06 13:00:22.308 DBG default: Exit #21: 0 QProcess::NormalExit
2021-10-06 13:00:22.308 DBG default: +++ void MInstall::updatePartitionWidgets(bool) +++
2021-10-06 13:00:22.310 DBG default: Exec #22: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2021-10-06 13:00:22.317 DBG default: Exit #22: 0 QProcess::NormalExit
2021-10-06 13:00:22.317 DBG default: Exec #23: partprobe -s
2021-10-06 13:00:22.407 DBG default: SOut #23: "/dev/sda: gpt partitions\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 13:00:22.407 DBG default: Exit #23: 0 QProcess::NormalExit
2021-10-06 13:00:22.407 DBG default: Exec #24: blkid -c /dev/null
2021-10-06 13:00:22.447 DBG default: SOut #24: "/dev/sda: PTUUID=\"2b9b6f10-a554-42f5-a3bc-95778e1afffa\" PTTYPE=\"gpt\"\n/dev/sdb1: LABEL=\"MX-Live-usb\" UUID=\"69c12998-ac56-4e82-b3ff-7de8b4fc8d85\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"d79e0a2c-01\"\n/dev/sdb2: LABEL_FATBOOT=\"MX-UEFI\" LABEL=\"MX-UEFI\" UUID=\"2C9D-BF5D\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"d79e0a2c-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2021-10-06 13:00:22.447 DBG default: Exit #24: 0 QProcess::NormalExit
2021-10-06 13:00:22.447 DBG default: Exec #25: parted -lm
2021-10-06 13:00:22.482 DBG default: Exit #25: 0 QProcess::NormalExit
2021-10-06 13:00:22.482 DBG default: Exec #26: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
2021-10-06 13:00:22.493 DBG default: Exit #26: 32 QProcess::NormalExit
2021-10-06 13:02:11.854 DBG default: Mount points:
2021-10-06 13:02:11.854 DBG default:  - "/" - "sda3" "root.fsm" "/dev/mapper/root.fsm"
2021-10-06 13:02:11.854 DBG default:  - "/boot" - "sda2" "sda2" "/dev/sda2"
2021-10-06 13:02:13.260 DBG default: +++ bool MInstall::saveHomeBasic() +++
2021-10-06 13:02:13.272 WRN qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4257, resource id: 18887372, major code: 40 (TranslateCoords), minor code: 0
2021-10-06 13:02:13.301 DBG default: - Preparing to install MX Linux -
2021-10-06 13:02:13.303 DBG default: Exec #27: smartctl -H /dev/sda
2021-10-06 13:02:13.339 DBG default: SOut #27: "smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-8-amd64] (local build)\nCopyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org\n\n=== START OF READ SMART DATA SECTION ===\nSMART overall-health self-assessment test result: PASSED\n\n"
2021-10-06 13:02:13.339 DBG default: Exit #27: 0 QProcess::NormalExit
2021-10-06 13:02:13.339 DBG default: Exec #28: smartctl -A /dev/sda| grep -E "^  5|^196|^197|^198" | awk '{ if ( $10 != 0 ) { print $1,$2,$10} }'
2021-10-06 13:02:13.367 DBG default: Exit #28: 0 QProcess::NormalExit
2021-10-06 13:02:13.367 DBG default: +++ void MInstall::cleanup(bool) +++
2021-10-06 13:02:13.368 DBG default: Exec #29: /bin/umount -l /mnt/antiX/boot/efi
2021-10-06 13:02:13.377 DBG default: SErr #29: "umount: /mnt/antiX/boot/efi: no mount point specified.\n"
2021-10-06 13:02:13.377 DBG default: Exit #29: 32 QProcess::NormalExit
2021-10-06 13:02:13.377 DBG default: Exec #30: /bin/umount -l /mnt/antiX/proc
2021-10-06 13:02:13.385 DBG default: SErr #30: "umount: /mnt/antiX/proc: no mount point specified.\n"
2021-10-06 13:02:13.385 DBG default: Exit #30: 32 QProcess::NormalExit
2021-10-06 13:02:13.385 DBG default: Exec #31: /bin/umount -l /mnt/antiX/sys
2021-10-06 13:02:13.393 DBG default: SErr #31: "umount: /mnt/antiX/sys: no mount point specified.\n"
2021-10-06 13:02:13.393 DBG default: Exit #31: 32 QProcess::NormalExit
2021-10-06 13:02:13.393 DBG default: Exec #32: /bin/umount -l /mnt/antiX/dev/shm
2021-10-06 13:02:13.401 DBG default: SErr #32: "umount: /mnt/antiX/dev/shm: no mount point specified.\n"
2021-10-06 13:02:13.401 DBG default: Exit #32: 32 QProcess::NormalExit
2021-10-06 13:02:13.401 DBG default: Exec #33: /bin/umount -l /mnt/antiX/dev
2021-10-06 13:02:13.408 DBG default: SErr #33: "umount: /mnt/antiX/dev: no mount point specified.\n"
2021-10-06 13:02:13.408 DBG default: Exit #33: 32 QProcess::NormalExit
2021-10-06 13:02:13.408 DBG default: Exec #34: swapoff /dev/sda2
2021-10-06 13:02:13.419 DBG default: SErr #34: "swapoff: /dev/sda2: swapoff failed: No such file or directory\n"
2021-10-06 13:02:13.419 DBG default: Exit #34: 4 QProcess::NormalExit
2021-10-06 13:02:13.419 DBG default: Exec #35: /bin/umount -l /mnt/antiX/boot
2021-10-06 13:02:13.428 DBG default: SErr #35: "umount: /mnt/antiX/boot: no mount point specified.\n"
2021-10-06 13:02:13.428 DBG default: Exit #35: 32 QProcess::NormalExit
2021-10-06 13:02:13.428 DBG default: Exec #36: swapoff /dev/mapper/root.fsm
2021-10-06 13:02:13.436 DBG default: SErr #36: "swapoff: /dev/mapper/root.fsm: swapoff failed: No such file or directory\n"
2021-10-06 13:02:13.436 DBG default: Exit #36: 4 QProcess::NormalExit
2021-10-06 13:02:13.436 DBG default: Exec #37: /bin/umount -l /mnt/antiX/
2021-10-06 13:02:13.446 DBG default: SErr #37: "umount: /mnt/antiX/: no mount point specified.\n"
2021-10-06 13:02:13.446 DBG default: Exit #37: 32 QProcess::NormalExit
2021-10-06 13:02:13.446 DBG default: Exec #38: cryptsetup close /dev/mapper/root.fsm
2021-10-06 13:02:13.674 DBG default: SErr #38: "Device /dev/mapper/root.fsm is not active.\n"
2021-10-06 13:02:13.674 DBG default: Exit #38: 4 QProcess::NormalExit
2021-10-06 13:02:13.674 DBG default: +++ bool PartMan::preparePartitions() +++
2021-10-06 13:02:13.677 DBG default: Exec #39: lsblk -nro name /dev/sda
2021-10-06 13:02:13.685 DBG default: Exit #39: 0 QProcess::NormalExit
2021-10-06 13:02:13.685 DBG default: Exec #40: swapoff /dev/sda
2021-10-06 13:02:13.692 DBG default: SErr #40: "swapoff: /dev/sda: swapoff failed: Invalid argument\n"
2021-10-06 13:02:13.693 DBG default: Exit #40: 4 QProcess::NormalExit
2021-10-06 13:02:13.693 DBG default: Exec #41: /bin/umount /dev/sda
2021-10-06 13:02:13.701 DBG default: SErr #41: "umount: /dev/sda: not mounted.\n"
2021-10-06 13:02:13.701 DBG default: Exit #41: 32 QProcess::NormalExit
2021-10-06 13:02:13.701 DBG default: - Preparing partition tables -
2021-10-06 13:02:13.705 DBG default: Exec #42: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda
2021-10-06 13:02:13.727 DBG default: SErr #42: "64+0 records in\n64+0 records out\n4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.012817 s, 327 MB/s\n"
2021-10-06 13:02:13.727 DBG default: Exit #42: 0 QProcess::NormalExit
2021-10-06 13:02:13.727 DBG default: Exec #43: dd conv=notrunc bs=64K count=64 if=/dev/zero of=/dev/sda seek=3815539
2021-10-06 13:02:13.739 DBG default: SErr #43: "dd: error writing '/dev/sda': No space left on device\n64+0 records in\n63+0 records out\n4186112 bytes (4.2 MB, 4.0 MiB) copied, 0.00190751 s, 2.2 GB/s\n"
2021-10-06 13:02:13.739 DBG default: Exit #43: 1 QProcess::NormalExit
2021-10-06 13:02:13.739 DBG default: Exec #44: parted -s /dev/sda mklabel gpt
2021-10-06 13:02:13.795 DBG default: Exit #44: 0 QProcess::NormalExit
2021-10-06 13:02:13.795 DBG default: - Preparing required partitions -
2021-10-06 13:02:13.802 DBG default: Exec #45: parted -s --align optimal /dev/sda mkpart primary 1MiB 257MiB
2021-10-06 13:02:13.855 DBG default: Exit #45: 0 QProcess::NormalExit
2021-10-06 13:02:13.859 DBG default: Exec #46: parted -s --align optimal /dev/sda mkpart primary 257MiB 769MiB
2021-10-06 13:02:13.931 DBG default: Exit #46: 0 QProcess::NormalExit
2021-10-06 13:02:13.935 DBG default: Exec #47: parted -s --align optimal /dev/sda mkpart primary 769MiB 238468MiB
2021-10-06 13:02:14.007 DBG default: Exit #47: 0 QProcess::NormalExit
2021-10-06 13:02:14.014 DBG default: Exec #48: parted -s /dev/sda set 2 legacy_boot on
2021-10-06 13:02:14.088 DBG default: Exit #48: 0 QProcess::NormalExit
2021-10-06 13:02:14.095 DBG default: Exec #49: partprobe -s
2021-10-06 13:02:14.219 DBG default: SOut #49: "/dev/sda: gpt partitions 1 2 3\n/dev/sdb: msdos partitions 1 2\n"
2021-10-06 13:02:14.219 DBG default: Exit #49: 0 QProcess::NormalExit
2021-10-06 13:02:14.219 DBG default: +++ bool PartMan::formatPartitions() +++
2021-10-06 13:02:14.223 DBG default: - Formatting: EFI System Partition -
2021-10-06 13:02:14.231 DBG default: Exec #50: mkfs.msdos -F 32 -n "EFI System" /dev/sda1
2021-10-06 13:02:14.295 DBG default: SOut #50: "mkfs.fat 4.2 (2021-01-31)\n"
2021-10-06 13:02:14.296 DBG default: SErr #50: "mkfs.fat: Warning: lowercase labels might not work properly on some systems\n"
2021-10-06 13:02:14.296 DBG default: Exit #50: 0 QProcess::NormalExit
2021-10-06 13:02:14.296 DBG default: Exec #51: parted -s /dev/sda set 1 esp on
2021-10-06 13:02:14.344 DBG default: Exit #51: 0 QProcess::NormalExit
2021-10-06 13:02:14.344 DBG default: - Formatting: /boot -
2021-10-06 13:02:14.351 DBG default: Exec #52: mkfs.ext4 -F /dev/sda2 -L "boot"
2021-10-06 13:02:14.423 DBG default: SOut #52: "Discarding device blocks:   4096/131072\b\b\b\b\b\b\b\b\b\b\b\b\b             \b\b\b\b\b\b\b\b\b\b\b\b\bdone                            \nCreating filesystem with 131072 4k blocks and 32768 inodes\nFilesystem UUID: 153d3647-0d8e-4d59-9f41-0e4799cdfc32\nSuperblock backups stored on blocks: \n\t32768, 98304\n\nAllocating group tables: 0/4\b\b\b   \b\b\bdone                            \nWriting inode tables: 0/4\b\b\b   \b\b\bdone                            \nCreating journal (4096 blocks): done\nWriting superblocks and filesystem accounting information: 0/4\b\b\b   \b\b\bdone\n\n"
2021-10-06 13:02:14.423 DBG default: SErr #52: "mke2fs 1.46.2 (28-Feb-2021)\n"
2021-10-06 13:02:14.423 DBG default: Exit #52: 0 QProcess::NormalExit
2021-10-06 13:02:14.423 DBG default: Exec #53: /sbin/tune2fs -c0 -C0 -i1m /dev/sda2
2021-10-06 13:02:14.439 DBG default: SOut #53: "tune2fs 1.46.2 (28-Feb-2021)\nSetting maximal mount count to -1\nSetting current mount count to 0\nSetting interval between checks to 2592000 seconds\n"
2021-10-06 13:02:14.439 DBG default: Exit #53: 0 QProcess::NormalExit
2021-10-06 13:02:14.439 DBG default: - Creating encrypted volume: sda3 -
2021-10-06 13:02:14.446 DBG default: Exec #54: cryptsetup --batch-mode --key-size 512 --hash sha512 --pbkdf argon2id --sector-size=353437696 luksFormat /dev/sda3
2021-10-06 13:02:14.457 DBG default: SErr #54: "Usage: cryptsetup [-?Vvyrq] [-?|--help] [--usage] [-V|--version]\n        [-v|--verbose] [--debug] [--debug-json] [-c|--cipher=STRING]\n        [-h|--hash=STRING] [-y|--verify-passphrase] [-d|--key-file=STRING]\n        [--master-key-file=STRING] [--dump-master-key] [-s|--key-size=BITS]\n        [-l|--keyfile-size=bytes] [--keyfile-offset=bytes]\n        [--new-keyfile-size=bytes] [--new-keyfile-offset=bytes]\n        [-S|--key-slot=INT] [-b|--size=SECTORS] [--device-size=bytes]\n        [-o|--offset=SECTORS] [-p|--skip=SECTORS] [-r|--readonly]\n        [-q|--batch-mode] [-t|--timeout=secs] [--progress-frequency=secs]\n        [-T|--tries=INT] [--align-payload=SECTORS]\n        [--header-backup-file=STRING] [--use-random] [--use-urandom]\n        [--shared] [--uuid=STRING] [--allow-discards] [--header=STRING]\n        [--test-passphrase] [--tcrypt-hidden] [--tcrypt-system]\n        [--tcrypt-backup] [--veracrypt] [--veracrypt-pim=INT]\n        [--veracrypt-query-pim] [-M|--type=STRING] [--force-password]\n        [--perf-same_cpu_crypt] [--perf-submit_from_crypt_cpus]\n        [--perf-no_read_workqueue] [--perf-no_write_workqueue] [--deferred]\n        [--serialize-memory-hard-pbkdf] [-i|--iter-time=msecs]\n        [--pbkdf=STRING] [--pbkdf-memory=kilobytes]\n        [--pbkdf-parallel=threads] [--pbkdf-force-iterations=LONG]\n        [--priority=STRING] [--disable-locks] [--disable-keyring]\n        [-I|--integrity=STRING] [--integrity-no-journal]\n        [--integrity-no-wipe] [--integrity-legacy-padding] [--token-only]\n        [--token-id=INT] [--key-description=STRING] [--sector-size=INT]\n        [--iv-large-sectors] [--persistent] [--label=STRING]\n        [--subsystem=STRING] [--unbound] [--json-file=STRING]\n        [--luks2-metadata-size=bytes] [--luks2-keyslots-size=bytes]\n        [--refresh] [--keyslot-key-size=BITS] [--keyslot-cipher=STRING]\n        [--encrypt] [--decrypt] [--init-only] [--resume-only]\n        [--reduce-device-size=bytes] [--hotzone-size=bytes]\n        [--resilience=STRING] [--resilience-hash=STRING]\n        [--active-name=STRING] [OPTION...] <action> <action-specific>\n/usr/sbin/cryptsetup: Unsupported encryption sector size.\n"
2021-10-06 13:02:14.457 DBG default: Exit #54: 1 QProcess::NormalExit
2021-10-06 13:02:14.457 DBG default: +++ void MInstall::failUI(const QString&) +++
2021-10-06 13:02:14.463 DBG default: Phase 1 - "Failed to prepare required partitions."
By the way, MX-21_beta2 installed fine.

Edit: About an hour after I posted this I did a short test using mx-installer 21.10.04 to install using 512 MB of swap and the problem remains (that is the latest version as of this posting).
we think we found the issue with this, thanks for the exceptional bug report!

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 12:27 pm
by Senpai
Hi:
During the installation in the window where you see the active services, it seems that there is a problem with the Spanish accents, it only happens in that window. Attached image.

By necessity from MX Tweak in "Appearance ->Letter" I increase to "125" the PPP, the tabs and buttons of MX Tweak and the Welcome box are not resized well, and the text inside the buttons and tabs is cut. Although when restarting it is corrected...
EDITED:
This same problem is seen in RC1 installation with Fluxbox in Spanish.

Greetings from Senpai

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 2:20 pm
by dr-kart
just first impressions

1. (in fonts tab) incorrect dpi resolution automatically detected for my 27' display (beta antix 21 does it correctly though)

2. hopelessly hoping to have this option that isn't available for mx21 yet (both antix21 and antix19 have it)

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 2:40 pm
by fladd
I think the default theme is pretty bad. Both visually (that is of course subjective, as I just don't like this modern flat design), but also ergonomically (which is objective). So let's focus on the ergonomic ones:

1. There seems to only be a 1 px border around the windows at which the cursor changes such that the window can be resized. Why not just make this area large, especially in the corners?
2. Moving (and enlarging) windows to the right leaves a 5 px border on the right (tested with the terminal). Why not allow the window to be fully to the right?
3. It would be great to also have a default light theme. The current hybrid default is very confusing, especially since there is no visual separation between the window title bar and the menu.
4. Xfce mixes normal window title bars (e.g. file manger, terminal) with CSD window title bars (e.g. the settings panel).
5. Even worse, there are Gnome3 applications included (e.g. the archive manager), which come even with their own hamburger menus and the general phone optimized UI. I am, however, not using MX on a phone, but on a desktop/laptop. It would be better for consistency, to not mix vastly different paradigms here.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 2:44 pm
by mdintisar
So far I faced the following issues:

1. Touchpad did not support reverse scrolling. I had to use synclient to fix it.
2. Redshift-gtk needed geoclue 2 to fix location.
3. Virtualbox did not follow the global theme but vlc did.
4. After trying kvantum Virtualbox followed theme but all mx tools stopped following theme.
5. Mx grub theme looks too old.
7. Could not change the cursor size.
8. Needed to use compton with plank to remove a bar like glitch. But then screen tearing issues emerged. I used

Code: Select all

/usr/bin/compton --backend glx --paint-on-overlay --vsync opengl-swc
in the startup to fix compton.

using mx linux 21 rc1 on real hardware.

Code: Select all

[code]
System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel, plank wm: xfwm4 
           dm: LightDM 1.26.0 Distro: MX-21_rc1_x64 Wildflower October 5  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: Inspiron 5459 v: N/A serial: <filter> Chassis: 
           type: 10 serial: <filter> 
           Mobo: Dell model: 0F1J0W v: A00 serial: <filter> UEFI: Dell v: 1.9.0 date: 09/07/2020 
Battery:   ID-1: BAT0 charge: 3.1 Wh condition: 3.1/32.6 Wh (10%) volts: 16.6/14.8 
           model: LGC-LGC2.8 DELL VN3N047 type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i7-6500U bits: 64 type: MT MCP arch: Skylake 
           family: 6 model-id: 4E (78) stepping: 3 microcode: EA L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20799 
           Speed: 500 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 500 2: 500 3: 500 4: 500 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Dell driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:1916 
           Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 
           Mobile] 
           vendor: Dell driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:6660 
           Display: x11 server: X.Org 1.20.11 driver: ati,modesetting,radeon 
           unloaded: fbdev,vesa compositor: compton v: 1 resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel 
           v: kernel bus ID: 00:1f.3 chip ID: 8086:9d70 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel Wireless 3160 driver: iwlwifi v: kernel port: e000 bus ID: 02:00.0 
           chip ID: 8086:08b3 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 
           v: kernel port: d000 bus ID: 03:00.0 chip ID: 10ec:8136 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 436.36 GiB (46.8%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000LM024 HN-M101MBB size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: 0003 scheme: GPT 
Partition: ID-1: / raw size: 90.00 GiB size: 88.03 GiB (97.81%) used: 13.57 GiB (15.4%) fs: ext4 
           dev: /dev/sda7 
           ID-2: /home raw size: 82.00 GiB size: 80.16 GiB (97.75%) used: 1.70 GiB (2.1%) 
           fs: ext4 dev: /dev/sda9 
           ID-3: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda8 
Sensors:   System Temperatures: cpu: 47.0 C mobo: 42.0 C sodimm: 39.0 C gpu: radeon temp: 47 C 
           Fan Speeds (RPM): cpu: 0 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://mirror.0x.sg/debian/ bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://mirror.0x.sg/debian/ bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.piconets.webwerks.in/mx-mirror/packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/mxpitemp.list 
           1: deb http://deb.debian.org/debian bullseye-backports main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list 
           1: deb https://download.onlyoffice.com/repo/debian squeeze main
           Active apt repos in: /etc/apt/sources.list.d/vscode.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/vscode stable main
Info:      Processes: 274 Uptime: 1h 43m Memory: 7.66 GiB used: 1.68 GiB (22.0%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
[/code]

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 2:44 pm
by SwampRabbit
dr-kart wrote: Thu Oct 07, 2021 2:20 pm 2. hopelessly hoping to have this option that isn't available for mx21 yet (both antix21 and antix19 have it)
"hopelessly"? :footinmouth:

I see antiX has a alsamixer-equalizer-antix package, not sure if this has anything to do with it or not?
@anticapitalista do you know if this provides a "Pre-Amp option" per the linked post above?

I can work on packaging this over to MX in the next few days.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 2:47 pm
by bigbenaugust
Is it normal for PulseAudio to take a nap when the screen is locked? In a fresh install of MX21RC1 Xfce, upon unlocking the screen, xfce4-mixer shows as muted with a message that it can't contact the PulseAudio server. Click on the systray icon after a few seconds and it comes right back to normal.

I installed awesome and pnmixer to see if it was an Xfce-only thing, and got a window from pnmixer that reads:

Code: Select all

Warning: Connection to sound system failed 
Do you want to re-initialize the audio connection?
If you do not, you will either need to restart PNMixer or select the 'Reload Audio' option in the right-click menu in order for PNMixer to function.
I've not seen that behavior on unlock in any other distro before.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 3:19 pm
by dolphin_oracle
fladd wrote: Thu Oct 07, 2021 2:40 pm I think the default theme is pretty bad. Both visually (that is of course subjective, as I just don't like this modern flat design), but also ergonomically (which is objective). So let's focus on the ergonomic ones:

1. There seems to only be a 1 px border around the windows at which the cursor changes such that the window can be resized. Why not just make this area large, especially in the corners?
2. Moving (and enlarging) windows to the right leaves a 5 px border on the right (tested with the terminal). Why not allow the window to be fully to the right?
3. It would be great to also have a default light theme. The current hybrid default is very confusing, especially since there is no visual separation between the window title bar and the menu.
4. Xfce mixes normal window title bars (e.g. file manger, terminal) with CSD window title bars (e.g. the settings panel).
5. Even worse, there are Gnome3 applications included (e.g. the archive manager), which come even with their own hamburger menus and the general phone optimized UI. I am, however, not using MX on a phone, but on a desktop/laptop. It would be better for consistency, to not mix vastly different paradigms here.
Thanks for the comments

1. there are thick-border variants of the window manager theme available.

2. I could use a screenshot of #2. I snap to right and left all the time and I haven't seen any gaps, but I haven't been looking for them either. I'm not seeing a gap with thunar or terminal, but maybe I'm not catching what you are throwing :happy:

3. there are plenty of alternate themes available preinstalled. tweak even has a few extra theme sets defined if folks want to switch to something like greybird or greybird dark across all the various settings (gtk, wm, icons). the current default (mx-comfort) is home grown, and is light with dark accents (panel, menubars).

4. yes, yes it does.

5. except for the Xfce settings apps (not
thunar and terminal) I don't think any other apps changed their use of CSD between mx19 and mx21. (even between mx17 and mx21). I agree that the Qt world is a little more consistent than the gtk world.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 3:46 pm
by entropyfoe
fladd...I have to agree the default theme is not that pretty for my taste.
I don't like how some of the elements are red, which usually denotes something wrong.

But it is easy to change, and tonight I will try some different themes. I did some trials in the betas and found some more to my taste.

The narrow window edge for grabbing has been seen in MX 19, and there are fixes on the forum as I recall.

I agree with title bars, they need an edge to visually separate them when windows overlap and the title bars merge, creating a visually hard to decode view of where one window begins and the other ends. Again, I think trying different themes can address this.

I did not list these theme items as problems as they are subject to personal preferences and easy to change with selecting different themes or using some tweaks.

But they could influence some who try MX the first time or for superficial reviewers.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 4:01 pm
by fladd
dolphin_oracle wrote: Thu Oct 07, 2021 3:19 pm
fladd wrote: Thu Oct 07, 2021 2:40 pm I think the default theme is pretty bad. Both visually (that is of course subjective, as I just don't like this modern flat design), but also ergonomically (which is objective). So let's focus on the ergonomic ones:

1. There seems to only be a 1 px border around the windows at which the cursor changes such that the window can be resized. Why not just make this area large, especially in the corners?
2. Moving (and enlarging) windows to the right leaves a 5 px border on the right (tested with the terminal). Why not allow the window to be fully to the right?
3. It would be great to also have a default light theme. The current hybrid default is very confusing, especially since there is no visual separation between the window title bar and the menu.
4. Xfce mixes normal window title bars (e.g. file manger, terminal) with CSD window title bars (e.g. the settings panel).
5. Even worse, there are Gnome3 applications included (e.g. the archive manager), which come even with their own hamburger menus and the general phone optimized UI. I am, however, not using MX on a phone, but on a desktop/laptop. It would be better for consistency, to not mix vastly different paradigms here.
Thanks for the comments

1. there are thick-border variants of the window manager theme available.

2. I could use a screenshot of #2. I snap to right and left all the time and I haven't seen any gaps, but I haven't been looking for them either. I'm not seeing a gap with thunar or terminal, but maybe I'm not catching what you are throwing :happy:

3. there are plenty of alternate themes available preinstalled. tweak even has a few extra theme sets defined if folks want to switch to something like greybird or greybird dark across all the various settings (gtk, wm, icons). the current default (mx-comfort) is home grown, and is light with dark accents (panel, menubars).

4. yes, yes it does.

5. except for the Xfce settings apps (not
thunar and terminal) I don't think any other apps changed their use of CSD between mx19 and mx21. (even between mx17 and mx21). I agree that the Qt world is a little more consistent than the gtk world.
1. If it is even available, why would this not be the default? Also, the thick-border theme is buggy (look at the left and right sides): https://imgur.com/gLKa5rQ
2. https://imgur.com/LQAxozo
5. As mentioned, archive manager has. And even since several versions of MX. There are non-Gnome3 alternatives available, such as Xarchiver. One of those alternatives should be the default. It would add a lot for a consistent desktop.

I also just found another issue: When the panel is switched to horizontal, then in the default theme the blue and orange markers for which application is active and how many windows it has, stay on the sides (i.e. they are still vertical bars, instead of horizontal ones).

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 4:08 pm
by SwampRabbit
entropyfoe wrote: Thu Oct 07, 2021 3:46 pm fladd...I have to agree the default theme is not that pretty for my taste.
I don't like how some of the elements are red, which usually denotes something wrong.
This was discussed a bit just before the RC release, the "red" elements seem to be isolated to Qt apps (least what I saw).

The mx-comfort themes (as already stated) are home grown, they need some refinement, but in due time as there really was only one person working on it.
Would be nice to have some folks who know Gtk themes and CSS ... offered to help.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 4:16 pm
by dolphin_oracle
fladd wrote: Thu Oct 07, 2021 4:01 pm
dolphin_oracle wrote: Thu Oct 07, 2021 3:19 pm
fladd wrote: Thu Oct 07, 2021 2:40 pm I think the default theme is pretty bad. Both visually (that is of course subjective, as I just don't like this modern flat design), but also ergonomically (which is objective). So let's focus on the ergonomic ones:

1. There seems to only be a 1 px border around the windows at which the cursor changes such that the window can be resized. Why not just make this area large, especially in the corners?
2. Moving (and enlarging) windows to the right leaves a 5 px border on the right (tested with the terminal). Why not allow the window to be fully to the right?
3. It would be great to also have a default light theme. The current hybrid default is very confusing, especially since there is no visual separation between the window title bar and the menu.
4. Xfce mixes normal window title bars (e.g. file manger, terminal) with CSD window title bars (e.g. the settings panel).
5. Even worse, there are Gnome3 applications included (e.g. the archive manager), which come even with their own hamburger menus and the general phone optimized UI. I am, however, not using MX on a phone, but on a desktop/laptop. It would be better for consistency, to not mix vastly different paradigms here.
Thanks for the comments

1. there are thick-border variants of the window manager theme available.

2. I could use a screenshot of #2. I snap to right and left all the time and I haven't seen any gaps, but I haven't been looking for them either. I'm not seeing a gap with thunar or terminal, but maybe I'm not catching what you are throwing :happy:

3. there are plenty of alternate themes available preinstalled. tweak even has a few extra theme sets defined if folks want to switch to something like greybird or greybird dark across all the various settings (gtk, wm, icons). the current default (mx-comfort) is home grown, and is light with dark accents (panel, menubars).

4. yes, yes it does.

5. except for the Xfce settings apps (not
thunar and terminal) I don't think any other apps changed their use of CSD between mx19 and mx21. (even between mx17 and mx21). I agree that the Qt world is a little more consistent than the gtk world.
1. If it is even available, why would this not be the default? Also, the thick-border theme is buggy (look at the left and right sides): https://imgur.com/gLKa5rQ
2. https://imgur.com/LQAxozo
5. As mentioned, archive manager has. And even since several versions of MX. There are non-Gnome3 alternatives available, such as Xarchiver. One of those alternatives should be the default. It would add a lot for a consistent desktop.

I also just found another issue: When the panel is switched to horizontal, then in the default theme the blue and orange markers for which application is active and how many windows it has, stay on the sides (i.e. they are still vertical bars, instead of horizontal ones).
1. that's why its not the default.
2. thanks for the image. I cannot duplicate that, but its certainly weird. But will look into it.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 4:18 pm
by SwampRabbit
fladd wrote: Thu Oct 07, 2021 4:01 pm ....
2. https://imgur.com/LQAxozo
....
I also just found another issue: When the panel is switched to horizontal, then in the default theme the blue and orange markers for which application is active and how many windows it has, stay on the sides (i.e. they are still vertical bars, instead of horizontal ones).
Can confirm the odd invisible pixels on the right side, does it with xfce4-terminal, but not Thunar or Firefox.
Edit: I only tested in a VM.

The docklike issue is known its because the default theme has a issue with the CSS (those orange bars) that needs to be removed, if you change the theme and switch the docklike indicator orientation to "Automatic" it will be as expected. One update was pushed for docklike already, the rest of the fixes will come soon.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 4:22 pm
by entropyfoe
There are many themes available. If I can find one that checks all the boxes, I will use it.

It is easy to change, so If I can find a satisfactory theme, this is not a big issue for me.
Hopefully I can try some tonight. In the betas I think it was some greybird variant. (Was an earlier MX default a greybird? -so for those looking for the MX -legacy appearance...)

But new users, less adventurous users reluctant to explore, or superficial reviewers might judge more harshly.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 4:28 pm
by SwampRabbit
entropyfoe wrote: Thu Oct 07, 2021 4:22 pm But new users, less adventurous users reluctant to explore, or superficial reviewers might judge more harshly.
The mx-comfort theme will get fixed, thats the real solution, not switching to a different one.

The person who created them deserves the opportunity (and support) to fix it... not just throw it out because it needs some small refinements.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 9:01 pm
by Leodudu
Greetings,

Clean Install RC1. The Nvidia driver has been installed.
Monitors connected to HDMI and mini displayport are detected but not working.
When I run "xrandr --setprovideroutputsource NVIDIA-G0 modesetting" then the monitors work.

How to make these changes permanent?
Thanks

(I did this: "This pair of commands can be added to your X session startup scripts, for example by putting them in $HOME/.xinitrc before running startx.", but it didn't work)

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: G3 3500 v: N/A serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: Dell model: 0W4V06 v: A00 serial: <filter> UEFI: Dell v: 1.9.0 date: 06/01/2021 
Battery:   ID-1: BAT0 charge: 44.1 Wh condition: 67.9/68.0 Wh (100%) volts: 15.3/15.2 
           model: SMP DELL 72WGV13 type: Li-poly serial: <filter> status: Unknown 
CPU:       Topology: 6-Core model: Intel Core i7-10750H bits: 64 type: MT MCP arch: N/A 
           family: 6 model-id: A5 (165) stepping: 2 microcode: EA L2 cache: 12.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62399 
           Speed: 3500 MHz min/max: 800/5000 MHz Core speeds (MHz): 1: 3500 2: 3499 3: 3500 
           4: 3499 5: 3500 6: 3500 7: 3500 8: 3500 9: 3500 10: 3501 11: 3500 12: 3501 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Dell driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:9bc4 
           Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Dell driver: nvidia 
           v: 460.91.03 bus ID: 01:00.0 chip ID: 10de:1f15 
           Display: x11 server: X.Org 1.20.11 driver: modesetting,nvidia 
           unloaded: fbdev,nouveau,vesa alternate: nv 
           resolution: 1920x1080~144Hz, 1600x900~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel Comet Lake PCH cAVS vendor: Dell driver: sof-audio-pci 
           bus ID: 00:1f.3 chip ID: 8086:06c8 
           Device-2: NVIDIA TU106 High Definition Audio vendor: Dell driver: snd_hda_intel 
           v: kernel bus ID: 01:00.1 chip ID: 10de:10f9 
           Device-3: Texas Instruments PCM2902 Audio Codec type: USB 
           driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-1.1.2:8 chip ID: 08bb:2902 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel port: 5000 
           bus ID: 00:14.3 chip ID: 8086:06f0 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Realtek vendor: Dell driver: r8169 v: kernel port: 3000 bus ID: 3c:00.0 
           chip ID: 10ec:2502 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 224.82 GiB (24.1%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: 2B2QEXM7 scheme: GPT 
           ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: 3B2QEXM7 scheme: GPT 
Partition: ID-1: / raw size: 923.25 GiB size: 907.69 GiB (98.31%) used: 6.87 GiB (0.8%) fs: ext4 
           dev: /dev/nvme1n1p2 
           ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/nvme1n1p3 
Sensors:   System Temperatures: cpu: 63.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirror.ufam.edu.br/mx/mx/repo/ bullseye main non-free
Info:      Processes: 299 Uptime: 10m Memory: 15.40 GiB used: 1.49 GiB (9.7%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Code: Select all

criando bloqueio ...
===================================
ddm-mx: 21.09.02
===================================
===================================
Instalar controladores (drivers) para: nvidia
Iniciar em (m/d/a): 10/05/2021 23:41:43
===================================

========================================
========================================

Para restaurar controladores de código aberto, usar: 
sudo ddm-mx -p nvidia

========================================
========================================

A atualizar as fontes/origens com 'apt-get update'
Candidato: nvidia-driver 460.91.03-1
Instalado:  nvidia-driver (none)
Verificar se há uma versão mais recente no repositório de Teste do MX (MX Test Repo)?
Aceitar...
Candidato: nvidia-driver 460.91.03-1
Instalado:  nvidia-driver (none)

Este é um sistema NVIDIA / INTEL Optimus?
  1) sim (default)
  2) não
Pressionar <Enter> para a predefinição (padrão) entrada
Usar 'q' para sair
Você pode usar o novo controlador PRIMUS, integrado nos controladores da Nvidia.
Use "nvidia-run-mx" followed by your application command to use the nvidia graphics
If you want to force the older bumblebee optimus drivers,
 quit and restart with sudo ddm-mx -i nvidia -f bumblebee-nvidiaCandidato: nvidia-driver 460.91.03-1
Instalado:  nvidia-driver (none)
Candidato: nvidia-driver 460.91.03-1
Instalado:  nvidia-driver (none)
Necessário controlador (driver):nvidia-driver 460.91.03-1 
Os pacotes NVIDIA para instalar são nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1
Frontend: 
Comando Nvidia = apt-get install --install-recommends --reinstall -y    nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1
Lendo listas de pacotes...
Construindo árvore de dependências...
Lendo informação de estado...
0 pacotes atualizados, 0 pacotes novos instalados, 2 reinstalados, 0 a serem removidos e 0 não atualizados.
É preciso baixar 861 kB de arquivos.
Depois desta operação, 0 B adicionais de espaço em disco serão usados.
Obter:1 http://security.debian.org/debian-security bullseye-security/main amd64 linux-headers-5.10.0-8-amd64 amd64 5.10.46-5 [853 kB]
Obter:2 http://deb.debian.org/debian bullseye/main amd64 build-essential amd64 12.9 [7.704 B]
Baixados 861 kB em 0s (3.323 kB/s)
(Lendo banco de dados ... 
(Lendo banco de dados ... 5%
(Lendo banco de dados ... 10%
(Lendo banco de dados ... 15%
(Lendo banco de dados ... 20%
(Lendo banco de dados ... 25%
(Lendo banco de dados ... 30%
(Lendo banco de dados ... 35%
(Lendo banco de dados ... 40%
(Lendo banco de dados ... 45%
(Lendo banco de dados ... 50%
(Lendo banco de dados ... 55%
(Lendo banco de dados ... 60%
(Lendo banco de dados ... 65%
(Lendo banco de dados ... 70%
(Lendo banco de dados ... 75%
(Lendo banco de dados ... 80%
(Lendo banco de dados ... 85%
(Lendo banco de dados ... 90%
(Lendo banco de dados ... 95%
(Lendo banco de dados ... 100%
(Lendo banco de dados ... 294778 ficheiros e directórios actualmente instalados.)
A preparar para desempacotar .../build-essential_12.9_amd64.deb ...
A descompactar build-essential (12.9) sobre (12.9) ...
A preparar para desempacotar .../linux-headers-5.10.0-8-amd64_5.10.46-5_amd64.deb ...
A descompactar linux-headers-5.10.0-8-amd64 (5.10.46-5) sobre (5.10.46-5) ...
Configurando linux-headers-5.10.0-8-amd64 (5.10.46-5) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 5.10.0-8-amd64:.
Configurando build-essential (12.9) ...
Lendo listas de pacotes...
Construindo árvore de dependências...
Lendo informação de estado...
The following additional packages will be installed:
  glx-alternative-mesa glx-alternative-nvidia glx-diversions libatomic1:i386
  libbsd0:i386 libcuda1 libcuda1:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386
  libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386
  libegl-mesa0:i386 libegl-nvidia0 libegl-nvidia0:i386 libegl1:i386
  libelf1:i386 libexpat1:i386 libffi7:i386 libgbm1:i386 libgl1:i386
  libgl1-mesa-dri:i386 libgl1-nvidia-glvnd-glx libgl1-nvidia-glvnd-glx:i386
  libglapi-mesa:i386 libgles-nvidia1 libgles-nvidia1:i386 libgles-nvidia2
  libgles-nvidia2:i386 libgles1 libgles1:i386 libgles2:i386 libglvnd0:i386
  libglx-mesa0:i386 libglx-nvidia0 libglx-nvidia0:i386 libglx0:i386
  libllvm11:i386 libmd0:i386 libnvcuvid1 libnvcuvid1:i386 libnvidia-cbl
  libnvidia-cfg1 libnvidia-eglcore libnvidia-eglcore:i386
  libnvidia-encode1:i386 libnvidia-glcore libnvidia-glcore:i386
  libnvidia-glvkspirv libnvidia-glvkspirv:i386 libnvidia-ml1
  libnvidia-ptxjitcompiler1 libnvidia-ptxjitcompiler1:i386 libnvidia-rtcore
  libopengl0 libopengl0:i386 libpciaccess0:i386 libsensors5:i386
  libstdc++6:i386 libtinfo6:i386 libvulkan1:i386 libwayland-client0:i386
  libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-randr0:i386 libxcb-shm0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386
  libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386
  libxshmfence1:i386 libxxf86vm1:i386 libz3-4:i386 libzstd1:i386
  mesa-vulkan-drivers:i386 nvidia-alternative nvidia-driver-bin
  nvidia-driver-libs nvidia-driver-libs:i386 nvidia-egl-common nvidia-egl-icd
  nvidia-egl-icd:i386 nvidia-installer-cleanup nvidia-kernel-common
  nvidia-kernel-support nvidia-legacy-check nvidia-modprobe nvidia-smi
  nvidia-support nvidia-vdpau-driver nvidia-vulkan-common nvidia-vulkan-icd
  nvidia-vulkan-icd:i386 update-glx xserver-xorg-video-nvidia zlib1g:i386
Pacotes sugeridos:
  nvidia-cuda-mps lm-sensors:i386 vulkan-utils vulkan-utils:i386
Pacotes recomendados:
  nvidia-persistenced
Os NOVOS pacotes a seguir serão instalados:
  glx-alternative-mesa glx-alternative-nvidia glx-diversions libatomic1:i386
  libbsd0:i386 libcuda1 libcuda1:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386
  libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386
  libegl-mesa0:i386 libegl-nvidia0 libegl-nvidia0:i386 libegl1:i386
  libelf1:i386 libexpat1:i386 libffi7:i386 libgbm1:i386 libgl1:i386
  libgl1-mesa-dri:i386 libgl1-nvidia-glvnd-glx libgl1-nvidia-glvnd-glx:i386
  libglapi-mesa:i386 libgles-nvidia1 libgles-nvidia1:i386 libgles-nvidia2
  libgles-nvidia2:i386 libgles1 libgles1:i386 libgles2:i386 libglvnd0:i386
  libglx-mesa0:i386 libglx-nvidia0 libglx-nvidia0:i386 libglx0:i386
  libllvm11:i386 libmd0:i386 libnvcuvid1 libnvcuvid1:i386 libnvidia-cbl
  libnvidia-cfg1 libnvidia-eglcore libnvidia-eglcore:i386 libnvidia-encode1
  libnvidia-encode1:i386 libnvidia-glcore libnvidia-glcore:i386
  libnvidia-glvkspirv libnvidia-glvkspirv:i386 libnvidia-ml1
  libnvidia-ptxjitcompiler1 libnvidia-ptxjitcompiler1:i386 libnvidia-rtcore
  libopengl0 libopengl0:i386 libpciaccess0:i386 libsensors5:i386
  libstdc++6:i386 libtinfo6:i386 libvulkan1:i386 libwayland-client0:i386
  libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-randr0:i386 libxcb-shm0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386
  libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386
  libxshmfence1:i386 libxxf86vm1:i386 libz3-4:i386 libzstd1:i386
  mesa-vulkan-drivers:i386 nvidia-alternative nvidia-driver nvidia-driver-bin
  nvidia-driver-libs nvidia-driver-libs:i386 nvidia-egl-common nvidia-egl-icd
  nvidia-egl-icd:i386 nvidia-installer-cleanup nvidia-kernel-common
  nvidia-kernel-dkms nvidia-kernel-support nvidia-legacy-check nvidia-modprobe
  nvidia-settings nvidia-smi nvidia-support nvidia-vdpau-driver
  nvidia-vulkan-common nvidia-vulkan-icd nvidia-vulkan-icd:i386 update-glx
  xserver-xorg-video-nvidia zlib1g:i386
0 pacotes atualizados, 110 pacotes novos instalados, 0 a serem removidos e 0 não atualizados.
É preciso baixar 151 MB de arquivos.
Depois desta operação, 554 MB adicionais de espaço em disco serão usados.
Obter:1 http://deb.debian.org/debian bullseye/contrib amd64 update-glx amd64 1.2.0 [10,5 kB]
Obter:2 http://deb.debian.org/debian bullseye/contrib amd64 glx-alternative-mesa amd64 1.2.0 [9.824 B]
Obter:3 http://deb.debian.org/debian bullseye/contrib amd64 nvidia-installer-cleanup amd64 20151021+13 [19,3 kB]
Obter:4 http://deb.debian.org/debian bullseye/contrib amd64 glx-diversions amd64 1.2.0 [12,1 kB]
Obter:5 http://deb.debian.org/debian bullseye/contrib amd64 glx-alternative-nvidia amd64 1.2.0 [10,8 kB]
Obter:6 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-legacy-check amd64 460.91.03-1 [234 kB]
Obter:7 http://deb.debian.org/debian bullseye/contrib amd64 nvidia-support amd64 20151021+13 [20,2 kB]
Obter:8 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-alternative amd64 460.91.03-1 [231 kB]
Obter:9 http://deb.debian.org/debian bullseye/non-free amd64 libnvidia-ptxjitcompiler1 amd64 460.91.03-1 [4.865 kB]
Obter:10 http://deb.debian.org/debian bullseye/non-free amd64 libcuda1 amd64 460.91.03-1 [2.627 kB]
Obter:11 http://deb.debian.org/debian bullseye/non-free amd64 libnvidia-glcore amd64 460.91.03-1 [7.570 kB]
Obter:12 http://deb.debian.org/debian bullseye/non-free amd64 libglx-nvidia0 amd64 460.91.03-1 [443 kB]
Obter:13 http://deb.debian.org/debian bullseye/non-free amd64 libgl1-nvidia-glvnd-glx amd64 460.91.03-1 [393 kB]
Obter:14 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-egl-common amd64 460.91.03-1 [229 kB]
Obter:15 http://deb.debian.org/debian bullseye/non-free amd64 libnvidia-eglcore amd64 460.91.03-1 [7.464 kB]
Obter:16 http://deb.debian.org/debian bullseye/non-free amd64 libegl-nvidia0 amd64 460.91.03-1 [487 kB]
Obter:17 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-egl-icd amd64 460.91.03-1 [229 kB]
Obter:18 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-driver-libs amd64 460.91.03-1 [229 kB]
Obter:19 http://deb.debian.org/debian bullseye/non-free amd64 libnvidia-ml1 amd64 460.91.03-1 [693 kB]
Obter:20 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-driver-bin amd64 460.91.03-1 [321 kB]
Obter:21 http://deb.debian.org/debian bullseye/non-free amd64 xserver-xorg-video-nvidia amd64 460.91.03-1 [2.432 kB]
Obter:22 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-vdpau-driver amd64 460.91.03-1 [721 kB]
Obter:23 http://deb.debian.org/debian bullseye/contrib amd64 nvidia-kernel-common amd64 20151021+13 [11,0 kB]
Obter:24 http://deb.debian.org/debian bullseye/contrib amd64 nvidia-modprobe amd64 460.32.03-1 [20,3 kB]
Obter:25 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-kernel-support amd64 460.91.03-1 [230 kB]
Obter:26 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-kernel-dkms amd64 460.91.03-1 [25,0 MB]
Obter:27 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-driver amd64 460.91.03-1 [559 kB]
Obter:28 http://deb.debian.org/debian bullseye/contrib amd64 nvidia-settings amd64 460.91.03-1 [784 kB]
Obter:29 http://deb.debian.org/debian bullseye/main i386 libatomic1 i386 10.2.1-6 [9.508 B]
Obter:30 http://deb.debian.org/debian bullseye/main i386 libmd0 i386 1.0.3-3 [28,9 kB]
Obter:31 http://deb.debian.org/debian bullseye/main i386 libbsd0 i386 0.11.3-1 [111 kB]
Obter:32 http://deb.debian.org/debian bullseye/non-free i386 libnvidia-ptxjitcompiler1 i386 460.91.03-1 [5.079 kB]
Obter:33 http://deb.debian.org/debian bullseye/non-free i386 libcuda1 i386 460.91.03-1 [2.602 kB]
Obter:34 http://deb.debian.org/debian bullseye/main i386 libdrm2 i386 2.4.104-1 [44,3 kB]
Obter:35 http://deb.debian.org/debian bullseye/main i386 libdrm-amdgpu1 i386 2.4.104-1 [31,5 kB]
Obter:36 http://deb.debian.org/debian bullseye/main i386 zlib1g i386 1:1.2.11.dfsg-2 [93,1 kB]
Obter:37 http://deb.debian.org/debian bullseye/main i386 libpciaccess0 i386 0.16-1 [55,7 kB]
Obter:38 http://deb.debian.org/debian bullseye/main i386 libdrm-intel1 i386 2.4.104-1 [74,5 kB]
Obter:39 http://deb.debian.org/debian bullseye/main i386 libdrm-nouveau2 i386 2.4.104-1 [28,5 kB]
Obter:40 http://deb.debian.org/debian bullseye/main i386 libdrm-radeon1 i386 2.4.104-1 [31,4 kB]
Obter:41 http://deb.debian.org/debian bullseye/main i386 libtinfo6 i386 6.2+20201114-2 [342 kB]
Obter:42 http://deb.debian.org/debian bullseye/main i386 libedit2 i386 3.1-20191231-2+b1 [101 kB]
Obter:43 http://deb.debian.org/debian bullseye/main i386 libexpat1 i386 2.2.10-2 [98,8 kB]
Obter:44 http://deb.debian.org/debian bullseye/main i386 libffi7 i386 3.3-6 [21,4 kB]
Obter:45 http://deb.debian.org/debian bullseye/main i386 libwayland-server0 i386 1.18.0-2~exp1.1 [36,0 kB]
Obter:46 http://deb.debian.org/debian bullseye/main i386 libgbm1 i386 20.3.5-1 [74,7 kB]
Obter:47 http://deb.debian.org/debian bullseye/main i386 libglapi-mesa i386 20.3.5-1 [71,9 kB]
Obter:48 http://deb.debian.org/debian bullseye/main i386 libwayland-client0 i386 1.18.0-2~exp1.1 [27,7 kB]
Obter:49 http://deb.debian.org/debian bullseye/main i386 libxau6 i386 1:1.0.9-1 [20,0 kB]
Obter:50 http://deb.debian.org/debian bullseye/main i386 libxdmcp6 i386 1:1.1.2-3 [26,7 kB]
Obter:51 http://deb.debian.org/debian bullseye/main i386 libxcb1 i386 1.14-3 [144 kB]
Obter:52 http://deb.debian.org/debian bullseye/main i386 libx11-6 i386 2:1.7.2-1 [794 kB]
Obter:53 http://deb.debian.org/debian bullseye/main i386 libx11-xcb1 i386 2:1.7.2-1 [203 kB]
Obter:54 http://deb.debian.org/debian bullseye/main i386 libxcb-dri2-0 i386 1.14-3 [103 kB]
Obter:55 http://deb.debian.org/debian bullseye/main i386 libxcb-dri3-0 i386 1.14-3 [103 kB]
Obter:56 http://deb.debian.org/debian bullseye/main i386 libxcb-present0 i386 1.14-3 [101 kB]
Obter:57 http://deb.debian.org/debian bullseye/main i386 libxcb-sync1 i386 1.14-3 [105 kB]
Obter:58 http://deb.debian.org/debian bullseye/main i386 libxcb-xfixes0 i386 1.14-3 [105 kB]
Obter:59 http://deb.debian.org/debian bullseye/main i386 libxshmfence1 i386 1.3-1 [8.976 B]
Obter:60 http://deb.debian.org/debian bullseye/main i386 libegl-mesa0 i386 20.3.5-1 [148 kB]
Obter:61 http://deb.debian.org/debian bullseye/non-free i386 libnvidia-eglcore i386 460.91.03-1 [7.322 kB]
Obter:62 http://deb.debian.org/debian bullseye/non-free i386 libegl-nvidia0 i386 460.91.03-1 [497 kB]
Obter:63 http://deb.debian.org/debian bullseye/main i386 libelf1 i386 0.183-1 [171 kB]
Obter:64 http://deb.debian.org/debian bullseye/main i386 libstdc++6 i386 10.2.1-6 [527 kB]
Obter:65 http://deb.debian.org/debian bullseye/main i386 libz3-4 i386 4.8.10-1 [7.737 kB]
Obter:66 http://deb.debian.org/debian bullseye/main i386 libllvm11 i386 1:11.0.1-2 [17,7 MB]
Obter:67 http://deb.debian.org/debian bullseye/main i386 libsensors5 i386 1:3.6.0-7 [53,2 kB]
Obter:68 http://deb.debian.org/debian bullseye/main i386 libvulkan1 i386 1.2.162.0-1 [110 kB]
Obter:69 http://deb.debian.org/debian bullseye/main i386 libzstd1 i386 1.4.8+dfsg-2.1 [308 kB]
Obter:70 http://deb.debian.org/debian bullseye/main i386 libgl1-mesa-dri i386 20.3.5-1 [9.948 kB]
Obter:71 http://deb.debian.org/debian bullseye/main i386 libglvnd0 i386 1.3.2-1 [44,1 kB]
Obter:72 http://deb.debian.org/debian bullseye/main i386 libxcb-glx0 i386 1.14-3 [120 kB]
Obter:73 http://deb.debian.org/debian bullseye/main i386 libxcb-shm0 i386 1.14-3 [102 kB]
Obter:74 http://deb.debian.org/debian bullseye/main i386 libxdamage1 i386 1:1.1.5-2 [15,9 kB]
Obter:75 http://deb.debian.org/debian bullseye/main i386 libxext6 i386 2:1.3.3-1.1 [55,2 kB]
Obter:76 http://deb.debian.org/debian bullseye/main i386 libxfixes3 i386 1:5.0.3-2 [22,6 kB]
Obter:77 http://deb.debian.org/debian bullseye/main i386 libxxf86vm1 i386 1:1.1.4-1+b2 [21,7 kB]
Obter:78 http://deb.debian.org/debian bullseye/main i386 libglx-mesa0 i386 20.3.5-1 [195 kB]
Obter:79 http://deb.debian.org/debian bullseye/main i386 libglx0 i386 1.3.2-1 [39,1 kB]
Obter:80 http://deb.debian.org/debian bullseye/main i386 libgl1 i386 1.3.2-1 [83,6 kB]
Obter:81 http://deb.debian.org/debian bullseye/non-free i386 libnvidia-glcore i386 460.91.03-1 [7.451 kB]
Obter:82 http://deb.debian.org/debian bullseye/non-free i386 libglx-nvidia0 i386 460.91.03-1 [430 kB]
Obter:83 http://deb.debian.org/debian bullseye/non-free i386 libgl1-nvidia-glvnd-glx i386 460.91.03-1 [393 kB]
Obter:84 http://deb.debian.org/debian bullseye/main i386 libgles1 i386 1.3.2-1 [12,5 kB]
Obter:85 http://deb.debian.org/debian bullseye/non-free i386 libgles-nvidia1 i386 460.91.03-1 [250 kB]
Obter:86 http://deb.debian.org/debian bullseye/main amd64 libgles1 amd64 1.3.2-1 [12,6 kB]
Obter:87 http://deb.debian.org/debian bullseye/non-free amd64 libgles-nvidia1 amd64 460.91.03-1 [249 kB]
Obter:88 http://deb.debian.org/debian bullseye/main i386 libgles2 i386 1.3.2-1 [17,3 kB]
Obter:89 http://deb.debian.org/debian bullseye/non-free i386 libgles-nvidia2 i386 460.91.03-1 [257 kB]
Obter:90 http://deb.debian.org/debian bullseye/non-free amd64 libgles-nvidia2 amd64 460.91.03-1 [257 kB]
Obter:91 http://deb.debian.org/debian bullseye/non-free amd64 libnvcuvid1 amd64 460.91.03-1 [1.206 kB]
Obter:92 http://deb.debian.org/debian bullseye/non-free i386 libnvcuvid1 i386 460.91.03-1 [1.200 kB]
Obter:93 http://deb.debian.org/debian bullseye/non-free amd64 libnvidia-cbl amd64 460.91.03-1 [477 kB]
Obter:94 http://deb.debian.org/debian bullseye/non-free amd64 libnvidia-cfg1 amd64 460.91.03-1 [301 kB]
Obter:95 http://deb.debian.org/debian bullseye/non-free amd64 libnvidia-encode1 amd64 460.91.03-1 [262 kB]
Obter:96 http://deb.debian.org/debian bullseye/non-free i386 libnvidia-encode1 i386 460.91.03-1 [265 kB]
Obter:97 http://deb.debian.org/debian bullseye/non-free amd64 libnvidia-glvkspirv amd64 460.91.03-1 [4.046 kB]
Obter:98 http://deb.debian.org/debian bullseye/non-free i386 libnvidia-glvkspirv i386 460.91.03-1 [4.559 kB]
Obter:99 http://deb.debian.org/debian bullseye/non-free amd64 libnvidia-rtcore amd64 460.91.03-1 [12,0 MB]
Obter:100 http://deb.debian.org/debian bullseye/main i386 libxcb-randr0 i386 1.14-3 [114 kB]
Obter:101 http://deb.debian.org/debian bullseye/main i386 mesa-vulkan-drivers i386 20.3.5-1 [4.162 kB]
Obter:102 http://deb.debian.org/debian bullseye/main i386 libegl1 i386 1.3.2-1 [36,7 kB]
Obter:103 http://deb.debian.org/debian bullseye/non-free i386 nvidia-egl-icd i386 460.91.03-1 [229 kB]
Obter:104 http://deb.debian.org/debian bullseye/non-free i386 nvidia-driver-libs i386 460.91.03-1 [229 kB]
Obter:105 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-smi amd64 460.91.03-1 [445 kB]
Obter:106 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-vulkan-common amd64 460.91.03-1 [230 kB]
Obter:107 http://deb.debian.org/debian bullseye/non-free i386 nvidia-vulkan-icd i386 460.91.03-1 [229 kB]
Obter:108 http://deb.debian.org/debian bullseye/non-free amd64 nvidia-vulkan-icd amd64 460.91.03-1 [229 kB]
Obter:109 http://deb.debian.org/debian bullseye/main amd64 libopengl0 amd64 1.3.2-1 [31,5 kB]
Obter:110 http://deb.debian.org/debian bullseye/main i386 libopengl0 i386 1.3.2-1 [29,9 kB]
Pré-configurando pacotes ...
Baixados 151 MB em 15s (10,1 MB/s)
A seleccionar pacote anteriormente não seleccionado update-glx.
(Lendo banco de dados ... 
(Lendo banco de dados ... 5%
(Lendo banco de dados ... 10%
(Lendo banco de dados ... 15%
(Lendo banco de dados ... 20%
(Lendo banco de dados ... 25%
(Lendo banco de dados ... 30%
(Lendo banco de dados ... 35%
(Lendo banco de dados ... 40%
(Lendo banco de dados ... 45%
(Lendo banco de dados ... 50%
(Lendo banco de dados ... 55%
(Lendo banco de dados ... 60%
(Lendo banco de dados ... 65%
(Lendo banco de dados ... 70%
(Lendo banco de dados ... 75%
(Lendo banco de dados ... 80%
(Lendo banco de dados ... 85%
(Lendo banco de dados ... 90%
(Lendo banco de dados ... 95%
(Lendo banco de dados ... 100%
(Lendo banco de dados ... 294778 ficheiros e directórios actualmente instalados.)
A preparar para desempacotar .../update-glx_1.2.0_amd64.deb ...
A descompactar update-glx (1.2.0) ...
A seleccionar pacote anteriormente não seleccionado glx-alternative-mesa.
A preparar para desempacotar .../glx-alternative-mesa_1.2.0_amd64.deb ...
A descompactar glx-alternative-mesa (1.2.0) ...
A seleccionar pacote anteriormente não seleccionado nvidia-installer-cleanup.
A preparar para desempacotar .../nvidia-installer-cleanup_20151021+13_amd64.deb ...
A descompactar nvidia-installer-cleanup (20151021+13) ...
Configurando nvidia-installer-cleanup (20151021+13) ...
A seleccionar pacote anteriormente não seleccionado glx-diversions.
(Lendo banco de dados ... 
(Lendo banco de dados ... 5%
(Lendo banco de dados ... 10%
(Lendo banco de dados ... 15%
(Lendo banco de dados ... 20%
(Lendo banco de dados ... 25%
(Lendo banco de dados ... 30%
(Lendo banco de dados ... 35%
(Lendo banco de dados ... 40%
(Lendo banco de dados ... 45%
(Lendo banco de dados ... 50%
(Lendo banco de dados ... 55%
(Lendo banco de dados ... 60%
(Lendo banco de dados ... 65%
(Lendo banco de dados ... 70%
(Lendo banco de dados ... 75%
(Lendo banco de dados ... 80%
(Lendo banco de dados ... 85%
(Lendo banco de dados ... 90%
(Lendo banco de dados ... 95%
(Lendo banco de dados ... 100%
(Lendo banco de dados ... 294918 ficheiros e directórios actualmente instalados.)
A preparar para desempacotar .../glx-diversions_1.2.0_amd64.deb ...
A descompactar glx-diversions (1.2.0) ...
A seleccionar pacote anteriormente não seleccionado glx-alternative-nvidia.
A preparar para desempacotar .../glx-alternative-nvidia_1.2.0_amd64.deb ...
A descompactar glx-alternative-nvidia (1.2.0) ...
A seleccionar pacote anteriormente não seleccionado nvidia-legacy-check.
A preparar para desempacotar .../nvidia-legacy-check_460.91.03-1_amd64.deb ...
A descompactar nvidia-legacy-check (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-support.
A preparar para desempacotar .../nvidia-support_20151021+13_amd64.deb ...
A descompactar nvidia-support (20151021+13) ...
Configurando nvidia-legacy-check (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-alternative.
(Lendo banco de dados ... 
(Lendo banco de dados ... 5%
(Lendo banco de dados ... 10%
(Lendo banco de dados ... 15%
(Lendo banco de dados ... 20%
(Lendo banco de dados ... 25%
(Lendo banco de dados ... 30%
(Lendo banco de dados ... 35%
(Lendo banco de dados ... 40%
(Lendo banco de dados ... 45%
(Lendo banco de dados ... 50%
(Lendo banco de dados ... 55%
(Lendo banco de dados ... 60%
(Lendo banco de dados ... 65%
(Lendo banco de dados ... 70%
(Lendo banco de dados ... 75%
(Lendo banco de dados ... 80%
(Lendo banco de dados ... 85%
(Lendo banco de dados ... 90%
(Lendo banco de dados ... 95%
(Lendo banco de dados ... 100%
(Lendo banco de dados ... 294956 ficheiros e directórios actualmente instalados.)
A preparar para desempacotar .../000-nvidia-alternative_460.91.03-1_amd64.deb ...
A descompactar nvidia-alternative (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-ptxjitcompiler1:amd64.
A preparar para desempacotar .../001-libnvidia-ptxjitcompiler1_460.91.03-1_amd64.deb ...
A descompactar libnvidia-ptxjitcompiler1:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libcuda1:amd64.
A preparar para desempacotar .../002-libcuda1_460.91.03-1_amd64.deb ...
A descompactar libcuda1:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-glcore:amd64.
A preparar para desempacotar .../003-libnvidia-glcore_460.91.03-1_amd64.deb ...
A descompactar libnvidia-glcore:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libglx-nvidia0:amd64.
A preparar para desempacotar .../004-libglx-nvidia0_460.91.03-1_amd64.deb ...
A descompactar libglx-nvidia0:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libgl1-nvidia-glvnd-glx:amd64.
A preparar para desempacotar .../005-libgl1-nvidia-glvnd-glx_460.91.03-1_amd64.deb ...
A descompactar libgl1-nvidia-glvnd-glx:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-egl-common.
A preparar para desempacotar .../006-nvidia-egl-common_460.91.03-1_amd64.deb ...
A descompactar nvidia-egl-common (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-eglcore:amd64.
A preparar para desempacotar .../007-libnvidia-eglcore_460.91.03-1_amd64.deb ...
A descompactar libnvidia-eglcore:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libegl-nvidia0:amd64.
A preparar para desempacotar .../008-libegl-nvidia0_460.91.03-1_amd64.deb ...
A descompactar libegl-nvidia0:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-egl-icd:amd64.
A preparar para desempacotar .../009-nvidia-egl-icd_460.91.03-1_amd64.deb ...
A descompactar nvidia-egl-icd:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-driver-libs:amd64.
A preparar para desempacotar .../010-nvidia-driver-libs_460.91.03-1_amd64.deb ...
A descompactar nvidia-driver-libs:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-ml1:amd64.
A preparar para desempacotar .../011-libnvidia-ml1_460.91.03-1_amd64.deb ...
A descompactar libnvidia-ml1:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-driver-bin.
A preparar para desempacotar .../012-nvidia-driver-bin_460.91.03-1_amd64.deb ...
A descompactar nvidia-driver-bin (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado xserver-xorg-video-nvidia.
A preparar para desempacotar .../013-xserver-xorg-video-nvidia_460.91.03-1_amd64.deb ...
A descompactar xserver-xorg-video-nvidia (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-vdpau-driver:amd64.
A preparar para desempacotar .../014-nvidia-vdpau-driver_460.91.03-1_amd64.deb ...
A descompactar nvidia-vdpau-driver:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-kernel-common.
A preparar para desempacotar .../015-nvidia-kernel-common_20151021+13_amd64.deb ...
A descompactar nvidia-kernel-common (20151021+13) ...
A seleccionar pacote anteriormente não seleccionado nvidia-modprobe.
A preparar para desempacotar .../016-nvidia-modprobe_460.32.03-1_amd64.deb ...
A descompactar nvidia-modprobe (460.32.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-kernel-support.
A preparar para desempacotar .../017-nvidia-kernel-support_460.91.03-1_amd64.deb ...
A descompactar nvidia-kernel-support (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-kernel-dkms.
A preparar para desempacotar .../018-nvidia-kernel-dkms_460.91.03-1_amd64.deb ...
A descompactar nvidia-kernel-dkms (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-driver.
A preparar para desempacotar .../019-nvidia-driver_460.91.03-1_amd64.deb ...
A descompactar nvidia-driver (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-settings.
A preparar para desempacotar .../020-nvidia-settings_460.91.03-1_amd64.deb ...
A descompactar nvidia-settings (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libatomic1:i386.
A preparar para desempacotar .../021-libatomic1_10.2.1-6_i386.deb ...
A descompactar libatomic1:i386 (10.2.1-6) ...
A seleccionar pacote anteriormente não seleccionado libmd0:i386.
A preparar para desempacotar .../022-libmd0_1.0.3-3_i386.deb ...
A descompactar libmd0:i386 (1.0.3-3) ...
A seleccionar pacote anteriormente não seleccionado libbsd0:i386.
A preparar para desempacotar .../023-libbsd0_0.11.3-1_i386.deb ...
A descompactar libbsd0:i386 (0.11.3-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-ptxjitcompiler1:i386.
A preparar para desempacotar .../024-libnvidia-ptxjitcompiler1_460.91.03-1_i386.deb ...
A descompactar libnvidia-ptxjitcompiler1:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libcuda1:i386.
A preparar para desempacotar .../025-libcuda1_460.91.03-1_i386.deb ...
A descompactar libcuda1:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libdrm2:i386.
A preparar para desempacotar .../026-libdrm2_2.4.104-1_i386.deb ...
A descompactar libdrm2:i386 (2.4.104-1) ...
A seleccionar pacote anteriormente não seleccionado libdrm-amdgpu1:i386.
A preparar para desempacotar .../027-libdrm-amdgpu1_2.4.104-1_i386.deb ...
A descompactar libdrm-amdgpu1:i386 (2.4.104-1) ...
A seleccionar pacote anteriormente não seleccionado zlib1g:i386.
A preparar para desempacotar .../028-zlib1g_1%3a1.2.11.dfsg-2_i386.deb ...
A descompactar zlib1g:i386 (1:1.2.11.dfsg-2) ...
A seleccionar pacote anteriormente não seleccionado libpciaccess0:i386.
A preparar para desempacotar .../029-libpciaccess0_0.16-1_i386.deb ...
A descompactar libpciaccess0:i386 (0.16-1) ...
A seleccionar pacote anteriormente não seleccionado libdrm-intel1:i386.
A preparar para desempacotar .../030-libdrm-intel1_2.4.104-1_i386.deb ...
A descompactar libdrm-intel1:i386 (2.4.104-1) ...
A seleccionar pacote anteriormente não seleccionado libdrm-nouveau2:i386.
A preparar para desempacotar .../031-libdrm-nouveau2_2.4.104-1_i386.deb ...
A descompactar libdrm-nouveau2:i386 (2.4.104-1) ...
A seleccionar pacote anteriormente não seleccionado libdrm-radeon1:i386.
A preparar para desempacotar .../032-libdrm-radeon1_2.4.104-1_i386.deb ...
A descompactar libdrm-radeon1:i386 (2.4.104-1) ...
A seleccionar pacote anteriormente não seleccionado libtinfo6:i386.
A preparar para desempacotar .../033-libtinfo6_6.2+20201114-2_i386.deb ...
A descompactar libtinfo6:i386 (6.2+20201114-2) ...
A seleccionar pacote anteriormente não seleccionado libedit2:i386.
A preparar para desempacotar .../034-libedit2_3.1-20191231-2+b1_i386.deb ...
A descompactar libedit2:i386 (3.1-20191231-2+b1) ...
A seleccionar pacote anteriormente não seleccionado libexpat1:i386.
A preparar para desempacotar .../035-libexpat1_2.2.10-2_i386.deb ...
A descompactar libexpat1:i386 (2.2.10-2) ...
A seleccionar pacote anteriormente não seleccionado libffi7:i386.
A preparar para desempacotar .../036-libffi7_3.3-6_i386.deb ...
A descompactar libffi7:i386 (3.3-6) ...
A seleccionar pacote anteriormente não seleccionado libwayland-server0:i386.
A preparar para desempacotar .../037-libwayland-server0_1.18.0-2~exp1.1_i386.deb ...
A descompactar libwayland-server0:i386 (1.18.0-2~exp1.1) ...
A seleccionar pacote anteriormente não seleccionado libgbm1:i386.
A preparar para desempacotar .../038-libgbm1_20.3.5-1_i386.deb ...
A descompactar libgbm1:i386 (20.3.5-1) ...
A seleccionar pacote anteriormente não seleccionado libglapi-mesa:i386.
A preparar para desempacotar .../039-libglapi-mesa_20.3.5-1_i386.deb ...
A descompactar libglapi-mesa:i386 (20.3.5-1) ...
A seleccionar pacote anteriormente não seleccionado libwayland-client0:i386.
A preparar para desempacotar .../040-libwayland-client0_1.18.0-2~exp1.1_i386.deb ...
A descompactar libwayland-client0:i386 (1.18.0-2~exp1.1) ...
A seleccionar pacote anteriormente não seleccionado libxau6:i386.
A preparar para desempacotar .../041-libxau6_1%3a1.0.9-1_i386.deb ...
A descompactar libxau6:i386 (1:1.0.9-1) ...
A seleccionar pacote anteriormente não seleccionado libxdmcp6:i386.
A preparar para desempacotar .../042-libxdmcp6_1%3a1.1.2-3_i386.deb ...
A descompactar libxdmcp6:i386 (1:1.1.2-3) ...
A seleccionar pacote anteriormente não seleccionado libxcb1:i386.
A preparar para desempacotar .../043-libxcb1_1.14-3_i386.deb ...
A descompactar libxcb1:i386 (1.14-3) ...
A seleccionar pacote anteriormente não seleccionado libx11-6:i386.
A preparar para desempacotar .../044-libx11-6_2%3a1.7.2-1_i386.deb ...
A descompactar libx11-6:i386 (2:1.7.2-1) ...
A seleccionar pacote anteriormente não seleccionado libx11-xcb1:i386.
A preparar para desempacotar .../045-libx11-xcb1_2%3a1.7.2-1_i386.deb ...
A descompactar libx11-xcb1:i386 (2:1.7.2-1) ...
A seleccionar pacote anteriormente não seleccionado libxcb-dri2-0:i386.
A preparar para desempacotar .../046-libxcb-dri2-0_1.14-3_i386.deb ...
A descompactar libxcb-dri2-0:i386 (1.14-3) ...
A seleccionar pacote anteriormente não seleccionado libxcb-dri3-0:i386.
A preparar para desempacotar .../047-libxcb-dri3-0_1.14-3_i386.deb ...
A descompactar libxcb-dri3-0:i386 (1.14-3) ...
A seleccionar pacote anteriormente não seleccionado libxcb-present0:i386.
A preparar para desempacotar .../048-libxcb-present0_1.14-3_i386.deb ...
A descompactar libxcb-present0:i386 (1.14-3) ...
A seleccionar pacote anteriormente não seleccionado libxcb-sync1:i386.
A preparar para desempacotar .../049-libxcb-sync1_1.14-3_i386.deb ...
A descompactar libxcb-sync1:i386 (1.14-3) ...
A seleccionar pacote anteriormente não seleccionado libxcb-xfixes0:i386.
A preparar para desempacotar .../050-libxcb-xfixes0_1.14-3_i386.deb ...
A descompactar libxcb-xfixes0:i386 (1.14-3) ...
A seleccionar pacote anteriormente não seleccionado libxshmfence1:i386.
A preparar para desempacotar .../051-libxshmfence1_1.3-1_i386.deb ...
A descompactar libxshmfence1:i386 (1.3-1) ...
A seleccionar pacote anteriormente não seleccionado libegl-mesa0:i386.
A preparar para desempacotar .../052-libegl-mesa0_20.3.5-1_i386.deb ...
A descompactar libegl-mesa0:i386 (20.3.5-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-eglcore:i386.
A preparar para desempacotar .../053-libnvidia-eglcore_460.91.03-1_i386.deb ...
A descompactar libnvidia-eglcore:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libegl-nvidia0:i386.
A preparar para desempacotar .../054-libegl-nvidia0_460.91.03-1_i386.deb ...
A descompactar libegl-nvidia0:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libelf1:i386.
A preparar para desempacotar .../055-libelf1_0.183-1_i386.deb ...
A descompactar libelf1:i386 (0.183-1) ...
A seleccionar pacote anteriormente não seleccionado libstdc++6:i386.
A preparar para desempacotar .../056-libstdc++6_10.2.1-6_i386.deb ...
A descompactar libstdc++6:i386 (10.2.1-6) ...
A seleccionar pacote anteriormente não seleccionado libz3-4:i386.
A preparar para desempacotar .../057-libz3-4_4.8.10-1_i386.deb ...
A descompactar libz3-4:i386 (4.8.10-1) ...
A seleccionar pacote anteriormente não seleccionado libllvm11:i386.
A preparar para desempacotar .../058-libllvm11_1%3a11.0.1-2_i386.deb ...
A descompactar libllvm11:i386 (1:11.0.1-2) ...
A seleccionar pacote anteriormente não seleccionado libsensors5:i386.
A preparar para desempacotar .../059-libsensors5_1%3a3.6.0-7_i386.deb ...
A descompactar libsensors5:i386 (1:3.6.0-7) ...
A seleccionar pacote anteriormente não seleccionado libvulkan1:i386.
A preparar para desempacotar .../060-libvulkan1_1.2.162.0-1_i386.deb ...
A descompactar libvulkan1:i386 (1.2.162.0-1) ...
A seleccionar pacote anteriormente não seleccionado libzstd1:i386.
A preparar para desempacotar .../061-libzstd1_1.4.8+dfsg-2.1_i386.deb ...
A descompactar libzstd1:i386 (1.4.8+dfsg-2.1) ...
A seleccionar pacote anteriormente não seleccionado libgl1-mesa-dri:i386.
A preparar para desempacotar .../062-libgl1-mesa-dri_20.3.5-1_i386.deb ...
A descompactar libgl1-mesa-dri:i386 (20.3.5-1) ...
A seleccionar pacote anteriormente não seleccionado libglvnd0:i386.
A preparar para desempacotar .../063-libglvnd0_1.3.2-1_i386.deb ...
A descompactar libglvnd0:i386 (1.3.2-1) ...
A seleccionar pacote anteriormente não seleccionado libxcb-glx0:i386.
A preparar para desempacotar .../064-libxcb-glx0_1.14-3_i386.deb ...
A descompactar libxcb-glx0:i386 (1.14-3) ...
A seleccionar pacote anteriormente não seleccionado libxcb-shm0:i386.
A preparar para desempacotar .../065-libxcb-shm0_1.14-3_i386.deb ...
A descompactar libxcb-shm0:i386 (1.14-3) ...
A seleccionar pacote anteriormente não seleccionado libxdamage1:i386.
A preparar para desempacotar .../066-libxdamage1_1%3a1.1.5-2_i386.deb ...
A descompactar libxdamage1:i386 (1:1.1.5-2) ...
A seleccionar pacote anteriormente não seleccionado libxext6:i386.
A preparar para desempacotar .../067-libxext6_2%3a1.3.3-1.1_i386.deb ...
A descompactar libxext6:i386 (2:1.3.3-1.1) ...
A seleccionar pacote anteriormente não seleccionado libxfixes3:i386.
A preparar para desempacotar .../068-libxfixes3_1%3a5.0.3-2_i386.deb ...
A descompactar libxfixes3:i386 (1:5.0.3-2) ...
A seleccionar pacote anteriormente não seleccionado libxxf86vm1:i386.
A preparar para desempacotar .../069-libxxf86vm1_1%3a1.1.4-1+b2_i386.deb ...
A descompactar libxxf86vm1:i386 (1:1.1.4-1+b2) ...
A seleccionar pacote anteriormente não seleccionado libglx-mesa0:i386.
A preparar para desempacotar .../070-libglx-mesa0_20.3.5-1_i386.deb ...
A descompactar libglx-mesa0:i386 (20.3.5-1) ...
A seleccionar pacote anteriormente não seleccionado libglx0:i386.
A preparar para desempacotar .../071-libglx0_1.3.2-1_i386.deb ...
A descompactar libglx0:i386 (1.3.2-1) ...
A seleccionar pacote anteriormente não seleccionado libgl1:i386.
A preparar para desempacotar .../072-libgl1_1.3.2-1_i386.deb ...
A descompactar libgl1:i386 (1.3.2-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-glcore:i386.
A preparar para desempacotar .../073-libnvidia-glcore_460.91.03-1_i386.deb ...
A descompactar libnvidia-glcore:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libglx-nvidia0:i386.
A preparar para desempacotar .../074-libglx-nvidia0_460.91.03-1_i386.deb ...
A descompactar libglx-nvidia0:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libgl1-nvidia-glvnd-glx:i386.
A preparar para desempacotar .../075-libgl1-nvidia-glvnd-glx_460.91.03-1_i386.deb ...
A descompactar libgl1-nvidia-glvnd-glx:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libgles1:i386.
A preparar para desempacotar .../076-libgles1_1.3.2-1_i386.deb ...
A descompactar libgles1:i386 (1.3.2-1) ...
A seleccionar pacote anteriormente não seleccionado libgles-nvidia1:i386.
A preparar para desempacotar .../077-libgles-nvidia1_460.91.03-1_i386.deb ...
A descompactar libgles-nvidia1:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libgles1:amd64.
A preparar para desempacotar .../078-libgles1_1.3.2-1_amd64.deb ...
A descompactar libgles1:amd64 (1.3.2-1) ...
A seleccionar pacote anteriormente não seleccionado libgles-nvidia1:amd64.
A preparar para desempacotar .../079-libgles-nvidia1_460.91.03-1_amd64.deb ...
A descompactar libgles-nvidia1:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libgles2:i386.
A preparar para desempacotar .../080-libgles2_1.3.2-1_i386.deb ...
A descompactar libgles2:i386 (1.3.2-1) ...
A seleccionar pacote anteriormente não seleccionado libgles-nvidia2:i386.
A preparar para desempacotar .../081-libgles-nvidia2_460.91.03-1_i386.deb ...
A descompactar libgles-nvidia2:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libgles-nvidia2:amd64.
A preparar para desempacotar .../082-libgles-nvidia2_460.91.03-1_amd64.deb ...
A descompactar libgles-nvidia2:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvcuvid1:i386.
A preparar para desempacotar .../083-libnvcuvid1_460.91.03-1_i386.deb ...
A descompactar libnvcuvid1:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvcuvid1:amd64.
A preparar para desempacotar .../084-libnvcuvid1_460.91.03-1_amd64.deb ...
A descompactar libnvcuvid1:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-cbl:amd64.
A preparar para desempacotar .../085-libnvidia-cbl_460.91.03-1_amd64.deb ...
A descompactar libnvidia-cbl:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-cfg1:amd64.
A preparar para desempacotar .../086-libnvidia-cfg1_460.91.03-1_amd64.deb ...
A descompactar libnvidia-cfg1:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-encode1:amd64.
A preparar para desempacotar .../087-libnvidia-encode1_460.91.03-1_amd64.deb ...
A descompactar libnvidia-encode1:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-encode1:i386.
A preparar para desempacotar .../088-libnvidia-encode1_460.91.03-1_i386.deb ...
A descompactar libnvidia-encode1:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-glvkspirv:amd64.
A preparar para desempacotar .../089-libnvidia-glvkspirv_460.91.03-1_amd64.deb ...
A descompactar libnvidia-glvkspirv:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-glvkspirv:i386.
A preparar para desempacotar .../090-libnvidia-glvkspirv_460.91.03-1_i386.deb ...
A descompactar libnvidia-glvkspirv:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libnvidia-rtcore:amd64.
A preparar para desempacotar .../091-libnvidia-rtcore_460.91.03-1_amd64.deb ...
A descompactar libnvidia-rtcore:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libxcb-randr0:i386.
A preparar para desempacotar .../092-libxcb-randr0_1.14-3_i386.deb ...
A descompactar libxcb-randr0:i386 (1.14-3) ...
A seleccionar pacote anteriormente não seleccionado mesa-vulkan-drivers:i386.
A preparar para desempacotar .../093-mesa-vulkan-drivers_20.3.5-1_i386.deb ...
A descompactar mesa-vulkan-drivers:i386 (20.3.5-1) ...
A seleccionar pacote anteriormente não seleccionado libegl1:i386.
A preparar para desempacotar .../094-libegl1_1.3.2-1_i386.deb ...
A descompactar libegl1:i386 (1.3.2-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-egl-icd:i386.
A preparar para desempacotar .../095-nvidia-egl-icd_460.91.03-1_i386.deb ...
A descompactar nvidia-egl-icd:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-driver-libs:i386.
A preparar para desempacotar .../096-nvidia-driver-libs_460.91.03-1_i386.deb ...
A descompactar nvidia-driver-libs:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-smi.
A preparar para desempacotar .../097-nvidia-smi_460.91.03-1_amd64.deb ...
A descompactar nvidia-smi (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-vulkan-common.
A preparar para desempacotar .../098-nvidia-vulkan-common_460.91.03-1_amd64.deb ...
A descompactar nvidia-vulkan-common (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-vulkan-icd:i386.
A preparar para desempacotar .../099-nvidia-vulkan-icd_460.91.03-1_i386.deb ...
A descompactar nvidia-vulkan-icd:i386 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado nvidia-vulkan-icd:amd64.
A preparar para desempacotar .../100-nvidia-vulkan-icd_460.91.03-1_amd64.deb ...
A descompactar nvidia-vulkan-icd:amd64 (460.91.03-1) ...
A seleccionar pacote anteriormente não seleccionado libopengl0:amd64.
A preparar para desempacotar .../101-libopengl0_1.3.2-1_amd64.deb ...
A descompactar libopengl0:amd64 (1.3.2-1) ...
A seleccionar pacote anteriormente não seleccionado libopengl0:i386.
A preparar para desempacotar .../102-libopengl0_1.3.2-1_i386.deb ...
A descompactar libopengl0:i386 (1.3.2-1) ...
Configurando nvidia-support (20151021+13) ...
Configurando libnvidia-glvkspirv:amd64 (460.91.03-1) ...
Configurando libnvidia-glvkspirv:i386 (460.91.03-1) ...
Configurando libexpat1:i386 (2.2.10-2) ...
Configurando libnvidia-eglcore:amd64 (460.91.03-1) ...
Configurando libnvidia-eglcore:i386 (460.91.03-1) ...
Configurando libzstd1:i386 (1.4.8+dfsg-2.1) ...
Configurando libnvidia-cbl:amd64 (460.91.03-1) ...
Configurando libxau6:i386 (1:1.0.9-1) ...
Configurando nvidia-egl-common (460.91.03-1) ...
Configurando nvidia-kernel-common (20151021+13) ...
Configurando libglvnd0:i386 (1.3.2-1) ...
Configurando libffi7:i386 (3.3-6) ...
Configurando zlib1g:i386 (1:1.2.11.dfsg-2) ...
Configurando update-glx (1.2.0) ...
Configurando libopengl0:amd64 (1.3.2-1) ...
Configurando libopengl0:i386 (1.3.2-1) ...
Configurando nvidia-modprobe (460.32.03-1) ...
Configurando libgles2:i386 (1.3.2-1) ...
Configurando libgles1:amd64 (1.3.2-1) ...
Configurando libgles1:i386 (1.3.2-1) ...
Configurando libatomic1:i386 (10.2.1-6) ...
Configurando libsensors5:i386 (1:3.6.0-7) ...
Configurando libnvidia-glcore:amd64 (460.91.03-1) ...
Configurando libnvidia-glcore:i386 (460.91.03-1) ...
Configurando libglapi-mesa:i386 (20.3.5-1) ...
Configurando libvulkan1:i386 (1.2.162.0-1) ...
Configurando libnvidia-ptxjitcompiler1:amd64 (460.91.03-1) ...
Configurando libnvidia-ptxjitcompiler1:i386 (460.91.03-1) ...
Configurando libdrm2:i386 (2.4.104-1) ...
Configurando libmd0:i386 (1.0.3-3) ...
Configurando nvidia-vulkan-common (460.91.03-1) ...
Configurando libxshmfence1:i386 (1.3-1) ...
Configurando libbsd0:i386 (0.11.3-1) ...
Configurando libelf1:i386 (0.183-1) ...
Configurando libstdc++6:i386 (10.2.1-6) ...
Configurando libtinfo6:i386 (6.2+20201114-2) ...
Configurando libnvidia-rtcore:amd64 (460.91.03-1) ...
Configurando libdrm-amdgpu1:i386 (2.4.104-1) ...
Configurando libwayland-client0:i386 (1.18.0-2~exp1.1) ...
Configurando libwayland-server0:i386 (1.18.0-2~exp1.1) ...
Configurando libpciaccess0:i386 (0.16-1) ...
Configurando libxdmcp6:i386 (1:1.1.2-3) ...
Configurando libdrm-nouveau2:i386 (2.4.104-1) ...
Configurando libxcb1:i386 (1.14-3) ...
Configurando libxcb-xfixes0:i386 (1.14-3) ...
Configurando libgbm1:i386 (20.3.5-1) ...
Configurando libdrm-radeon1:i386 (2.4.104-1) ...
Configurando libxcb-glx0:i386 (1.14-3) ...
Configurando libedit2:i386 (3.1-20191231-2+b1) ...
Configurando libdrm-intel1:i386 (2.4.104-1) ...
Configurando glx-alternative-mesa (1.2.0) ...
Configurando libxcb-shm0:i386 (1.14-3) ...
Configurando libxcb-present0:i386 (1.14-3) ...
Configurando libz3-4:i386 (4.8.10-1) ...
Configurando libllvm11:i386 (1:11.0.1-2) ...
Configurando libxcb-sync1:i386 (1.14-3) ...
Configurando glx-diversions (1.2.0) ...
Configurando libxcb-dri2-0:i386 (1.14-3) ...
Configurando libxcb-randr0:i386 (1.14-3) ...
Configurando libx11-6:i386 (2:1.7.2-1) ...
Configurando libxcb-dri3-0:i386 (1.14-3) ...
Configurando libx11-xcb1:i386 (2:1.7.2-1) ...
Configurando libxdamage1:i386 (1:1.1.5-2) ...
Configurando libgl1-mesa-dri:i386 (20.3.5-1) ...
Configurando libxext6:i386 (2:1.3.3-1.1) ...
Configurando libxxf86vm1:i386 (1:1.1.4-1+b2) ...
Configurando libegl-mesa0:i386 (20.3.5-1) ...
Configurando libxfixes3:i386 (1:5.0.3-2) ...
Configurando libegl1:i386 (1.3.2-1) ...
Configurando mesa-vulkan-drivers:i386 (20.3.5-1) ...
Configurando libglx-mesa0:i386 (20.3.5-1) ...
Configurando libglx0:i386 (1.3.2-1) ...
Configurando libgl1:i386 (1.3.2-1) ...
A processar 'triggers' para mailcap (3.69) ...
A processar 'triggers' para desktop-file-utils (0.26-1) ...
A processar 'triggers' para initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64
I: The initramfs will attempt to resume from /dev/nvme0n1p3
I: (UUID=18979e1f-3189-4beb-ad74-710ed9f87be8)
I: Set the RESUME variable to override this.
A processar 'triggers' para hicolor-icon-theme (0.17-2) ...
A processar 'triggers' para libc-bin (2.31-13) ...
A processar 'triggers' para man-db (2.9.4-2) ...
A processar 'triggers' para glx-alternative-mesa (1.2.0) ...
update-alternatives: a usar /usr/lib/mesa-diverted para disponibilizar /usr/lib/glx (glx) em modo auto
Configurando glx-alternative-nvidia (1.2.0) ...
A processar 'triggers' para glx-alternative-nvidia (1.2.0) ...
Configurando nvidia-alternative (460.91.03-1) ...
A processar 'triggers' para nvidia-alternative (460.91.03-1) ...
update-alternatives: a usar /usr/lib/nvidia/current para disponibilizar /usr/lib/nvidia/nvidia (nvidia) em modo auto
Configurando libnvidia-ml1:amd64 (460.91.03-1) ...
Configurando libcuda1:amd64 (460.91.03-1) ...
Configurando libcuda1:i386 (460.91.03-1) ...
Configurando libnvidia-cfg1:amd64 (460.91.03-1) ...
Configurando libglx-nvidia0:amd64 (460.91.03-1) ...
Configurando libglx-nvidia0:i386 (460.91.03-1) ...
Configurando nvidia-kernel-support (460.91.03-1) ...
Configurando xserver-xorg-video-nvidia (460.91.03-1) ...
Configurando nvidia-vulkan-icd:amd64 (460.91.03-1) ...
Configurando nvidia-vulkan-icd:i386 (460.91.03-1) ...
Configurando nvidia-vdpau-driver:amd64 (460.91.03-1) ...
Configurando libgl1-nvidia-glvnd-glx:amd64 (460.91.03-1) ...
Configurando libgl1-nvidia-glvnd-glx:i386 (460.91.03-1) ...
Configurando libgles-nvidia1:amd64 (460.91.03-1) ...
Configurando libgles-nvidia1:i386 (460.91.03-1) ...
Configurando libegl-nvidia0:amd64 (460.91.03-1) ...
Configurando libegl-nvidia0:i386 (460.91.03-1) ...
Configurando nvidia-settings (460.91.03-1) ...
Configurando nvidia-smi (460.91.03-1) ...
Configurando libgles-nvidia2:amd64 (460.91.03-1) ...
Configurando libgles-nvidia2:i386 (460.91.03-1) ...
Configurando nvidia-driver-bin (460.91.03-1) ...
Configurando libnvcuvid1:amd64 (460.91.03-1) ...
Configurando libnvcuvid1:i386 (460.91.03-1) ...
Configurando nvidia-egl-icd:amd64 (460.91.03-1) ...
Configurando nvidia-egl-icd:i386 (460.91.03-1) ...
Configurando libnvidia-encode1:amd64 (460.91.03-1) ...
Configurando libnvidia-encode1:i386 (460.91.03-1) ...
Configurando nvidia-driver-libs:amd64 (460.91.03-1) ...
Configurando nvidia-driver-libs:i386 (460.91.03-1) ...
A processar 'triggers' para nvidia-alternative (460.91.03-1) ...
update-alternatives: a actualizar a alternativa /usr/lib/nvidia/current porque a ligação do grupo nvidia alterou os links slave
Configurando nvidia-kernel-dkms (460.91.03-1) ...
Loading new nvidia-current-460.91.03 DKMS files...
Building for 5.10.0-8-amd64
Building initial module for 5.10.0-8-amd64
Done.

nvidia-current.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation

   - Installing to /lib/modules/5.10.0-8-amd64/updates/dkms/

nvidia-current-modeset.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.10.0-8-amd64/updates/dkms/

nvidia-current-drm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.10.0-8-amd64/updates/dkms/

nvidia-current-uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.10.0-8-amd64/updates/dkms/

depmod...

DKMS: install completed.
Configurando nvidia-driver (460.91.03-1) ...
A processar 'triggers' para libc-bin (2.31-13) ...
A processar 'triggers' para initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64
I: The initramfs will attempt to resume from /dev/nvme0n1p3
I: (UUID=18979e1f-3189-4beb-ad74-710ed9f87be8)
I: Set the RESUME variable to override this.
A processar 'triggers' para update-glx (1.2.0) ...
A processar 'triggers' para glx-alternative-nvidia (1.2.0) ...
update-alternatives: a usar /usr/lib/nvidia para disponibilizar /usr/lib/glx (glx) em modo auto
A processar 'triggers' para glx-alternative-mesa (1.2.0) ...
A processar 'triggers' para libc-bin (2.31-13) ...
A processar 'triggers' para initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64
I: The initramfs will attempt to resume from /dev/nvme0n1p3
I: (UUID=18979e1f-3189-4beb-ad74-710ed9f87be8)
I: Set the RESUME variable to override this.
Finalizado


Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 07, 2021 9:38 pm
by oops
Here, does not keep after a reboot the "icon notification setting" (icône de notification)

Code: Select all

xfce4-power-manager --customize

Re: MX-21 RC1 feedback (Xfce)-themes

Posted: Thu Oct 07, 2021 10:12 pm
by entropyfoe
OK, I reverted to greybird-MX. It nicely solves the title bar problem. The default theme had a single blue pixel boarder to the active window, making it possible to see each title bar when overlapping. But when the window is no longer active (has focus?) that blue boarder line goes away, and overlapping title bars are hard to tell which is where.

greybird has the edges of the title bars white or lighter weather active of not, so overlaps are always clear.

But I still get that weird red highlighting, now I only see it in clementine for example the song that is playing is highlighted in red. In MX-19.4 the highlighted song is blue. As a interface device, something in red usually is a warning or error, so I don't like it. Or is this just a clementine version thing? I see no controls in the application for colors.

Edit: OK, that was strange, I rebooted, and now clementine is back to normal (like MX-19.4) where the highlighted song playing is blue. 9_9

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 1:41 am
by hebelwirkung
Small thing, but panel opacity can't be set. Whatever I do, it stays 100% opaque. Compositing is turned on in Window Manager Tweaks.

Also I saw the discussion above about theming, and am wondering whether the wildflower background, coupled with the barely visible conky, is going to persuade first time users it's classy. That may be changed of course with a few clicks, and of course esthetics is a very personal thing, but I was thinking first impressions matter etc, so perhaps a slightly less wild default background might be worth considering.

Other than that, so far I haven't found anything not working. Oh, one other thing. On first install (in Virtualbox), after rebooting and entering my password in the login box, I was taken to the login prompt again if you see what I mean - I entered my password about a dozen times without being able to log in. Reinstalled and found that problem was fixed.

### EDIT: After reboot, panel opacity is now working. ######

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 1:53 am
by SwampRabbit
@entropyfoe we got it, dolphin already fixed the red elements in the default theme issue and the extra docklike indicator showing up, I confirmed the fixes work…

Everyone just needs to be patient for the updates to come down.

There is only one other unintended docklike theming change that we want to work because of the other fixes.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 1:55 am
by SwampRabbit
@Leodudu when you installed the Nvidia drivers you used the Nvidia Driver Installer and selected that you have an Optimus enabled system?

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 1:57 am
by SwampRabbit
hebelwirkung wrote: Fri Oct 08, 2021 1:41 am Small thing, but panel opacity can't be set. Whatever I do, it stays 100% opaque. Compositing is turned on in Window Manager Tweaks.
Please post your Quick System Info so we can identify if it’s something system specific.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 2:43 am
by TOMCAT
I can't find where the screen saver is.
There is no 'xfce4-screensaver' in the software repository.
But the user manual tells me 'Click Application Menu > Settings > Screensaver'
I don't know if it was discarded or just not in the software sources I use

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 4:51 am
by gsm
When after a timeout period of no activity, the screen is resumed with only a cursor on a black screen, then this behavior is related to the default selected Xfmw Compositor (MX Tweak).
Refer also to my reply #65, EDIT 2.
XFWM4 Composite only seems to become a problem when it is selected as a Compositor with MX Tweaks.
It does not cause the "resume with cursor only" problem when composite is activated with the Windows tweaks settings from the settings panel (xfwm4-tweaks-settings).

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 6:21 am
by scratchcat1
There appears to be a bug with MX Tweak > Display > Hardware Backlight.
Moving the slider around quickly with the mouse results in bar length not matching with the number displayed and actual brightness.
The faster the slider is moved the more wrong the bar is compared to the actual number/brightness.
Making a small adjustment either with the mouse or keyboard fixes the problem.
Closing and opening MX Tweak moves the slider to the correct position.
Screenshot_2021-10-08_11-12-17.png

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: persist_all quiet splasht nosplash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Acer product: TravelMate 8372 v: V1.10 serial: <filter> Chassis: 
           type: 10 serial: <filter> 
           Mobo: Acer model: TravelMate 8372 v: PSMBOU-1234567 serial: <filter> BIOS: Acer 
           v: 1.10 date: 04/29/2011 
Battery:   ID-1: BAT0 charge: 62.9 Wh condition: 64.6/86.4 Wh (75%) volts: 16.6/14.4 
           model: Panasonic AS10I5E type: Li-ion serial: <filter> status: Charging 
CPU:       Topology: Dual Core model: Intel Core i5 M 450 bits: 64 type: MT MCP arch: Nehalem 
           family: 6 model-id: 25 (37) stepping: 5 microcode: 7 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19201 
           Speed: 1875 MHz min/max: 1199/2400 MHz boost: enabled Core speeds (MHz): 1: 1487 
           2: 1452 3: 1485 4: 1425 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Acer Incorporated ALI 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0046 
           Device-2: NVIDIA GT218M [GeForce 310M] vendor: Acer Incorporated ALI driver: N/A 
           bus ID: 01:00.0 chip ID: 10de:0a75 
           Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio 
           vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:3b56 
           Device-2: NVIDIA High Definition Audio driver: snd_hda_intel v: kernel 
           bus ID: 01:00.1 chip ID: 10de:0be3 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Broadcom and subsidiaries BCM43225 802.11b/g/n 
           vendor: Foxconn T77H103.00 Wireless Half-size Mini PCIe Card driver: wl v: kernel 
           port: 4000 bus ID: 02:00.0 chip ID: 14e4:4357 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Broadcom and subsidiaries NetXtreme BCM57760 Gigabit Ethernet PCIe 
           vendor: Acer Incorporated ALI driver: tg3 v: kernel port: 4000 bus ID: 04:00.0 
           chip ID: 14e4:1690 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 495.12 GiB used: 4.62 GiB (0.9%) 
           ID-1: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 023 scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer Blade size: 14.91 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.27 scheme: MBR 
           ID-3: /dev/sde type: USB vendor: Generic model: Flash Disk size: 14.45 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 8.07 scheme: MBR 
Partition: ID-1: / raw size: N/A size: 5.91 GiB used: 957.4 MiB (15.8%) fs: overlay 
           source: ERR-102 
Sensors:   System Temperatures: cpu: 54.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
Info:      Processes: 239 Uptime: 54m Memory: 7.45 GiB used: 1.52 GiB (20.4%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
Video Tweaks:
Detected possible Hybrid Graphics
pre-sandybridge UXA acceleration

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 6:47 am
by dolphin_oracle
hebelwirkung wrote: Fri Oct 08, 2021 1:41 am Small thing, but panel opacity can't be set. Whatever I do, it stays 100% opaque. Compositing is turned on in Window Manager Tweaks.

Also I saw the discussion above about theming, and am wondering whether the wildflower background, coupled with the barely visible conky, is going to persuade first time users it's classy. That may be changed of course with a few clicks, and of course esthetics is a very personal thing, but I was thinking first impressions matter etc, so perhaps a slightly less wild default background might be worth considering.

Other than that, so far I haven't found anything not working. Oh, one other thing. On first install (in Virtualbox), after rebooting and entering my password in the login box, I was taken to the login prompt again if you see what I mean - I entered my password about a dozen times without being able to log in. Reinstalled and found that problem was fixed.
There is some bug in the panel that when you first set a custom color with opacity other than 100 percent the panel requires a restart for the change to go into effect.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 6:48 am
by dolphin_oracle
scratchcat1 wrote: Fri Oct 08, 2021 6:21 am There appears to be a bug with MX Tweak > Display > Hardware Backlight.
Moving the slider around quickly with the mouse results in bar length not matching with the number displayed and actual brightness.
The faster the slider is moved the more wrong the bar is compared to the actual number/brightness.
Making a small adjustment either with the mouse or keyboard fixes the problem.
Closing and opening MX Tweak moves the slider to the correct position.

Screenshot_2021-10-08_11-12-17.png

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: persist_all quiet splasht nosplash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Acer product: TravelMate 8372 v: V1.10 serial: <filter> Chassis: 
           type: 10 serial: <filter> 
           Mobo: Acer model: TravelMate 8372 v: PSMBOU-1234567 serial: <filter> BIOS: Acer 
           v: 1.10 date: 04/29/2011 
Battery:   ID-1: BAT0 charge: 62.9 Wh condition: 64.6/86.4 Wh (75%) volts: 16.6/14.4 
           model: Panasonic AS10I5E type: Li-ion serial: <filter> status: Charging 
CPU:       Topology: Dual Core model: Intel Core i5 M 450 bits: 64 type: MT MCP arch: Nehalem 
           family: 6 model-id: 25 (37) stepping: 5 microcode: 7 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19201 
           Speed: 1875 MHz min/max: 1199/2400 MHz boost: enabled Core speeds (MHz): 1: 1487 
           2: 1452 3: 1485 4: 1425 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Acer Incorporated ALI 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0046 
           Device-2: NVIDIA GT218M [GeForce 310M] vendor: Acer Incorporated ALI driver: N/A 
           bus ID: 01:00.0 chip ID: 10de:0a75 
           Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio 
           vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:3b56 
           Device-2: NVIDIA High Definition Audio driver: snd_hda_intel v: kernel 
           bus ID: 01:00.1 chip ID: 10de:0be3 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Broadcom and subsidiaries BCM43225 802.11b/g/n 
           vendor: Foxconn T77H103.00 Wireless Half-size Mini PCIe Card driver: wl v: kernel 
           port: 4000 bus ID: 02:00.0 chip ID: 14e4:4357 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Broadcom and subsidiaries NetXtreme BCM57760 Gigabit Ethernet PCIe 
           vendor: Acer Incorporated ALI driver: tg3 v: kernel port: 4000 bus ID: 04:00.0 
           chip ID: 14e4:1690 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 495.12 GiB used: 4.62 GiB (0.9%) 
           ID-1: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 023 scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer Blade size: 14.91 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.27 scheme: MBR 
           ID-3: /dev/sde type: USB vendor: Generic model: Flash Disk size: 14.45 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 8.07 scheme: MBR 
Partition: ID-1: / raw size: N/A size: 5.91 GiB used: 957.4 MiB (15.8%) fs: overlay 
           source: ERR-102 
Sensors:   System Temperatures: cpu: 54.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
Info:      Processes: 239 Uptime: 54m Memory: 7.45 GiB used: 1.52 GiB (20.4%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
Video Tweaks:
Detected possible Hybrid Graphics
pre-sandybridge UXA acceleration
Hmmm thanks will look into it.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 7:04 am
by hebelwirkung
SwampRabbit wrote: Fri Oct 08, 2021 1:57 am
hebelwirkung wrote: Fri Oct 08, 2021 1:41 am Small thing, but panel opacity can't be set. Whatever I do, it stays 100% opaque. Compositing is turned on in Window Manager Tweaks.
Please post your Quick System Info so we can identify if it’s something system specific.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
CPU:       Topology: Dual Core model: AMD A8-6500T APU with Radeon HD Graphics bits: 64 
           type: MCP arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 
           microcode: 6000626 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 8441 
           Speed: 2110 MHz min/max: N/A Core speeds (MHz): 1: 2110 2: 2110 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 
           chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.11 driver: vmware unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 118.97 GiB used: 819.21 GiB (688.6%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 118.97 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 24.41 GiB size: 23.86 GiB (97.74%) used: 5.83 GiB (24.4%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 101.4 MiB (5.3%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 2.39 GiB (2.8%) 
           fs: ext4 dev: /dev/sda4 
           ID-4: swap-1 size: 6.25 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda1 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
Info:      Processes: 195 Uptime: 7m Memory: 3.02 GiB used: 1.10 GiB (36.4%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

I amended my earlier post saying that after a reboot, the panel opacity is now working as intended. Sorry to cause confusion - but on 19.4 or earlier, and in the beta versions of 21, changes took effect immediately, I assume it may be a tiny glitch which will be ironed out before final release.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 7:51 am
by Leodudu
SwampRabbit wrote: Fri Oct 08, 2021 1:55 am @Leodudu when you installed the Nvidia drivers you used the Nvidia Driver Installer and selected that you have an Optimus enabled system?
Yes.

It seems to me that in both Pop!-Os and MX Linux, the main monitor is controlled by the Intel adapter, and the other two monitors are controlled by the Nvidia adapter.

The commands I would like to make permanent are:

xrandr --setprovideroutputsource NVIDIA-G0 modesetting
xrandr --output eDP-1 --primary --mode 1920x1080 --pos 1600x0 --rotate normal --reflect normal --output HDMI-1-0 --mode 1600x900 --pos 0x0 --rotate normal --output DP-1-0 --mode 1920x1080 --pos 3520x0 --rotate normal

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 10:23 am
by SwampRabbit
@hebelwirkung take a look at dolphin’s reply to you and let us know.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 10:30 am
by SwampRabbit
@Leodudu i personally don’t have any Nvidia hardware, used to, but Optimus systems can be tricky in way the GPU connects to the the outputs. Vendor integration can vary from laptop to laptop.

Give everyone a bit of time to look at your issue please, it may take someone knowing more and being able to reproduce this exactly.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 10:37 am
by dolphin_oracle
hebelwirkung wrote: Fri Oct 08, 2021 7:04 am
SwampRabbit wrote: Fri Oct 08, 2021 1:57 am
hebelwirkung wrote: Fri Oct 08, 2021 1:41 am Small thing, but panel opacity can't be set. Whatever I do, it stays 100% opaque. Compositing is turned on in Window Manager Tweaks.
Please post your Quick System Info so we can identify if it’s something system specific.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
CPU:       Topology: Dual Core model: AMD A8-6500T APU with Radeon HD Graphics bits: 64 
           type: MCP arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 
           microcode: 6000626 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 8441 
           Speed: 2110 MHz min/max: N/A Core speeds (MHz): 1: 2110 2: 2110 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 
           chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.11 driver: vmware unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 118.97 GiB used: 819.21 GiB (688.6%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 118.97 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 24.41 GiB size: 23.86 GiB (97.74%) used: 5.83 GiB (24.4%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 101.4 MiB (5.3%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 2.39 GiB (2.8%) 
           fs: ext4 dev: /dev/sda4 
           ID-4: swap-1 size: 6.25 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda1 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
Info:      Processes: 195 Uptime: 7m Memory: 3.02 GiB used: 1.10 GiB (36.4%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

I amended my earlier post saying that after a reboot, the panel opacity is now working as intended. Sorry to cause confusion - but on 19.4 or earlier, and in the beta versions of 21, changes took effect immediately, I assume it may be a tiny glitch which will be ironed out before final release.
they xfce dev that takes care of the panel is slightly hard to work with, but there is a bug report filed at Xfce on this issue. I set up a automatic restart of the panel when the panel preferences are called up from inside MX-Tweak, but I suspect that almost no one pulls up the preferences that way.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 11:18 am
by hebelwirkung
dolphin_oracle wrote: Fri Oct 08, 2021 10:37 am
hebelwirkung wrote: Fri Oct 08, 2021 7:04 am
SwampRabbit wrote: Fri Oct 08, 2021 1:57 am

Please post your Quick System Info so we can identify if it’s something system specific.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
CPU:       Topology: Dual Core model: AMD A8-6500T APU with Radeon HD Graphics bits: 64 
           type: MCP arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 
           microcode: 6000626 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 8441 
           Speed: 2110 MHz min/max: N/A Core speeds (MHz): 1: 2110 2: 2110 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 
           chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.11 driver: vmware unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 118.97 GiB used: 819.21 GiB (688.6%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 118.97 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 24.41 GiB size: 23.86 GiB (97.74%) used: 5.83 GiB (24.4%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 101.4 MiB (5.3%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 2.39 GiB (2.8%) 
           fs: ext4 dev: /dev/sda4 
           ID-4: swap-1 size: 6.25 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda1 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
Info:      Processes: 195 Uptime: 7m Memory: 3.02 GiB used: 1.10 GiB (36.4%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

I amended my earlier post saying that after a reboot, the panel opacity is now working as intended. Sorry to cause confusion - but on 19.4 or earlier, and in the beta versions of 21, changes took effect immediately, I assume it may be a tiny glitch which will be ironed out before final release.
they xfce dev that takes care of the panel is slightly hard to work with, but there is a bug report filed at Xfce on this issue. I set up a automatic restart of the panel when the panel preferences are called up from inside MX-Tweak, but I suspect that almost no one pulls up the preferences that way.
Yes, probably most people will edit the panel via the panel menu itself. But I'm sure if you catch the panel dev at an opportune moment, he'll agree to fix this :-)

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 11:56 am
by Eadwine Rose
When I have changed things in the panel and I select in tweak to restore the default I am still (like in B2) left with no panel at all. I have to reboot (logout login, wager works too) and then it shows up.

Restore backup panel from tweak DOES work. It takes a number of seconds, I was thinking it was a goner and then as I was about to hit the logout button it suddenly popped up. Maybe that was the programmed panel restart that kicked in?

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 12:09 pm
by dolphin_oracle
Eadwine Rose wrote: Fri Oct 08, 2021 11:56 am When I have changed things in the panel and I select in tweak to restore the default I am still (like in B2) left with no panel at all. I have to reboot (logout login, wager works too) and then it shows up.

Restore backup panel from tweak DOES work. It takes a number of seconds, I was thinking it was a goner and then as I was about to hit the logout button it suddenly popped up. Maybe that was the programmed panel restart that kicked in?
both should take around 7 seconds to happen. the routines are very similar but there is obviously a hiccup somewhere. could be that my restart routine is too agressive, will look at that.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 12:13 pm
by dolphin_oracle
if you restore a panel while the preferences dialog is open, there could be strange effects.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 12:34 pm
by Eadwine Rose
Just MX Tweak IIRC.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 12:43 pm
by dirkduplooy
Hi, how do I do an in-place upgrade of Beta 2 to RC1? When I installed Beta 2 it was alleged it will be possible and currently, I suffer from bandwidth availability issues and it will help a lot if I can do as such. Thanks

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 12:52 pm
by dolphin_oracle
Just do regular updates. We won’t change the name of the ISO until they release final although

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 12:57 pm
by dirkduplooy
dolphin_oracle wrote: Fri Oct 08, 2021 12:52 pm Just do regular updates. We won’t change the name of the ISO until they release final although
Hi dolphin thanks for the reply, I do the updates regulary still this is the system info:

System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta2_x64 Wildflower September 4 2021
base: Debian GNU/Linux 11 (bullseye)

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 1:05 pm
by dolphin_oracle
dirkduplooy wrote: Fri Oct 08, 2021 12:57 pm
dolphin_oracle wrote: Fri Oct 08, 2021 12:52 pm Just do regular updates. We won’t change the name of the ISO until they release final although
Hi dolphin thanks for the reply, I do the updates regulary still this is the system info:

System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta2_x64 Wildflower September 4 2021
base: Debian GNU/Linux 11 (bullseye)
As I said we don’t change the name till final release so that’s good.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 1:15 pm
by Roberto
I have found that switching the mouse wheel scroll direction does not work everywhere.
In Firefox it works without problems, but in Libreoffice and in Thunar the scroll direction is not reversed.

Here is my configuration:

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: LENOVO product: 4291IR6 v: ThinkPad X220 serial: <filter> 
           Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 4291IR6 serial: <filter> UEFI: LENOVO v: 8DET76WW (1.46 ) 
           date: 06/21/2018 
Battery:   ID-1: BAT0 charge: 8.3 Wh condition: 21.9/47.5 Wh (46%) volts: 11.1/10.8 
           model: Panasonic 42T4875 type: Li-ion serial: <filter> status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i5-2430M bits: 64 type: MT MCP 
           arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F 
           L2 cache: 3072 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19137 
           Speed: 1167 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 1098 2: 973 3: 1003 
           4: 1095 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
           vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0116 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Lenovo 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Lenovo ThinkPad T520 driver: e1000e 
           v: kernel port: 6080 bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eth0 state: down mac: <filter> 
           Device-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce v: kernel 
           port: 5000 bus ID: 03:00.0 chip ID: 10ec:8176 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 223.57 GiB used: 6.58 GiB (2.9%) 
           ID-1: /dev/sda vendor: SanDisk model: SDSSDHII240G size: 223.57 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 00RL scheme: GPT 
Partition: ID-1: / raw size: 80.00 GiB size: 78.19 GiB (97.74%) used: 6.38 GiB (8.2%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /home raw size: 135.10 GiB size: 131.92 GiB (97.65%) used: 200.7 MiB (0.1%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: swap-1 size: 7.97 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda4 
Sensors:   System Temperatures: cpu: 49.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 1976 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
Info:      Processes: 223 Uptime: 1h 41m Memory: 7.66 GiB used: 1.53 GiB (20.0%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 1:25 pm
by Huckleberry Finn
@dirkduplooy Just this file is staying the same (purposely, as Dolphin mentioned) /etc/mx-version

So, nothing to worry.. Shortly, you just go on updating & upgrading as always and when final release is in repos, that one will be updated (changed) , too , to show MX-21_x64 Wildflower ...

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 5:13 pm
by Leodudu
SwampRabbit wrote: Fri Oct 08, 2021 10:30 am @Leodudu i personally don’t have any Nvidia hardware, used to, but Optimus systems can be tricky in way the GPU connects to the the outputs. Vendor integration can vary from laptop to laptop.

Give everyone a bit of time to look at your issue please, it may take someone knowing more and being able to reproduce this exactly.
I have a Pop!OS with Nvidia driver 470.63.01. If any configuration files help with any information, I can send them to you.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 5:25 pm
by SwampRabbit
Leodudu wrote: Fri Oct 08, 2021 5:13 pm I have a Pop!OS with Nvidia driver 470.63.01. If any configuration files help with any information, I can send them to you.
Is it acting the same on Pop as it is on MX-21 or is it functioning how expected?

I honestly don't know enough about Optimus setups to help and like I said I don't have Nvidia hardware at all anymore.
@Huckleberry Finn or @JayM have become pretty good at these issues though. And dolphin_oracle is the go-to for the Nvidia Installer, I'm sure he has seen your posts, but like I said people need some time.

There is a ton of information and lists on Optimus laptops out there, I'm searching for Dell G3 3500, is that the the common (friendly) Model of this laptop or is it a G3 35## or other?

Edit: from what you explained earlier (if I remember it right), you may need to use Reverse Prime.
https://wiki.archlinux.org/title/PRIME#Reverse_PRIME

Also before messing around with all these settings and config files, it'd be good to have a fresh TimeShift Snapshot BEFORE and AFTER running the Nvidia Driver Installer. Cause troubleshooting can get messy with Optimus laptops (I think we had a dedicated thread for one person that was 100 posts long or some junk).

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 7:33 pm
by entropyfoe
I just saw and installed the latest RC1 synaptic upgrades.

Code: Select all

Upgraded the following packages:
desktop-defaults-mx-xfce (21.09.02mx21) to 21.10.01mx21
desktop-defaults-mx-xfce-desktop (21.09.02mx21) to 21.10.01mx21
desktop-defaults-mx-xfce-system (21.09.02mx21) to 21.10.01mx21
mx-comfort-themes (21.09.10) to 21.10.01
mx-installer (21.10.04) to 21.10.05
mx-remaster (21.09.01mx21) to 21.10.01mx21
Do I need to reboot to make them all official for testing?

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 7:40 pm
by thinkpadx
brief comments: A quick walk through the wildflowers


i finally had a chance to burn the rc1 and try it a bit. burned it onto a dvd to run it live via a memorex cd/dvd usb writer (/player). i did not get a chance to look through everything and i generally don't when i check out a live version. need to make sure trackpad and wireless works and i can begin tweaking things as i need them. I am picky and once i set it up i leave stuff - so trying to find all the settings stuff takes time which is a pain to redo a system for me. however, looks nice and runs nicely and i did not see anything re: glitches. some of the pwer and window settings seem to work though there seems to be a bit of difference vs 19. maybe different looks or options and settings. sorry for not being specific or documenting the little variables but as i said it looks nice and useable for daily use. i did not try the wireless hp 8600 but with hplip stuff it should load and work nicely. the quick system info

Code: Select all

System:    Host: <filter> Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.4_x64 patito feo October 15  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: LENOVO product: 3626F5U v: ThinkPad X201 serial: <filter> 
           Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 3626F5U serial: <filter> BIOS: LENOVO v: 6QET46WW (1.16 ) 
           date: 06/07/2010 
Battery:   ID-1: BAT0 charge: 45.4 Wh condition: 45.5/48.8 Wh (93%) volts: 12.3/11.1 
           model: JingYi 08K8193 type: Li-ion serial: <filter> status: Unknown 
CPU:       Topology: Dual Core model: Intel Core i5 M 540 bits: 64 type: MT MCP arch: Nehalem 
           family: 6 model-id: 25 (37) stepping: 2 microcode: 11 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20216 
           Speed: 1419 MHz min/max: 1199/2534 MHz boost: enabled Core speeds (MHz): 1: 1414 
           2: 1434 3: 1385 4: 1373 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full generic retpoline, IBRS_FW, STIBP: conditional, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Lenovo driver: i915 
           v: kernel bus ID: 00:02.0 chip ID: 8086:0046 
           Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1280x800~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 18.3.6 
           direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Lenovo 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel 82577LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k 
           port: 1820 bus ID: 00:19.0 chip ID: 8086:10ea 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel port: 1880 
           bus ID: 02:00.0 chip ID: 8086:4239 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 298.09 GiB used: 21.66 GiB (7.3%) 
           ID-1: /dev/sda vendor: Hitachi model: HTS725032A9A364 size: 298.09 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: C70F scheme: MBR 
Partition: ID-1: / raw size: 296.06 GiB size: 290.41 GiB (98.09%) used: 21.66 GiB (7.5%) 
           fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 48.0 C mobo: 0.0 C 
           Fan Speeds (RPM): cpu: 1988 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 211 Uptime: 42m Memory: 3.66 GiB used: 815.1 MiB (21.8%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

it's an old thinkpad x 201 my slower but daily beater workhorse. i have a faster nicer x220 in my office - trackpad is glitchier on that one using mx19 and did not try 21 on it.

i tried the mx19 rc1 the same way as such, and installed and never looked back. so generally from my walk through the widlflowers i can say it is rather sweet and fresh and looks and smells great - heh heh !!!


it also shutdown in less than a second which is the quickest shutdown i have seen esp whe running from a live cd/dvd.
there are usually a lot of files neede to be read etc to cloe it and end the trial.

wish i had a bit more time to try a bit more but as stated earlier - i did not see anything wrong or bad jump out at me! Nice work! Thanks to everyone. now to find the time and all of the areas that need to be tweak to install it for my likes.

10

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 7:43 pm
by SwampRabbit
entropyfoe wrote: Fri Oct 08, 2021 7:33 pm I just saw and installed the latest RC1 synaptic upgrades.
....

Do I need to reboot to make them all official for testing?
I "think" a log out and login will work, but I know that rebooting works, since your testing an RC.... do whatever you want lol

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 7:54 pm
by thinkpadx
I wanted to add that i did not try the suspend which i use everyday.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 8:11 pm
by Leodudu
SwampRabbit wrote: Fri Oct 08, 2021 5:25 pm Also before messing around with all these settings and config files, it'd be good to have a fresh TimeShift Snapshot BEFORE and AFTER running the Nvidia Driver Installer. Cause troubleshooting can get messy with Optimus laptops (I think we had a dedicated thread for one person that was 100 posts long or some junk).
I now have a fresh new installation, without the Nvidia driver.
The notebook is a g3 15 3500.
Which configuration files should I upload before installing the Nvidia driver?

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: G3 3500 v: N/A serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: Dell model: 0W4V06 v: A00 serial: <filter> UEFI: Dell v: 1.9.0 date: 06/01/2021 
Battery:   ID-1: BAT0 charge: 44.0 Wh condition: 67.9/68.0 Wh (100%) volts: 15.3/15.2 
           model: SMP DELL 72WGV13 type: Li-poly serial: <filter> status: Unknown 
CPU:       Topology: 6-Core model: Intel Core i7-10750H bits: 64 type: MT MCP arch: N/A 
           family: 6 model-id: A5 (165) stepping: 2 microcode: EA L2 cache: 12.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62399 
           Speed: 800 MHz min/max: 800/5000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
           5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Dell driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:9bc4 
           Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Dell driver: N/A 
           bus ID: 01:00.0 chip ID: 10de:1f15 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1080~144Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel Comet Lake PCH cAVS vendor: Dell driver: sof-audio-pci 
           bus ID: 00:1f.3 chip ID: 8086:06c8 
           Device-2: NVIDIA TU106 High Definition Audio vendor: Dell driver: snd_hda_intel 
           v: kernel bus ID: 01:00.1 chip ID: 10de:10f9 
           Device-3: Texas Instruments PCM2902 Audio Codec type: USB 
           driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-1.1.2:9 chip ID: 08bb:2902 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel port: 5000 
           bus ID: 00:14.3 chip ID: 8086:06f0 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Realtek vendor: Dell driver: r8169 v: kernel port: 3000 bus ID: 3c:00.0 
           chip ID: 10ec:2502 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 223.77 GiB (24.0%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: 2B2QEXM7 scheme: GPT 
           ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: 3B2QEXM7 scheme: GPT 
Partition: ID-1: / raw size: 923.25 GiB size: 907.69 GiB (98.31%) used: 5.97 GiB (0.7%) fs: ext4 
           dev: /dev/nvme1n1p2 
           ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/nvme1n1p3 
Sensors:   System Temperatures: cpu: 70.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirror.ufam.edu.br/mx/mx/repo/ bullseye main non-free
Info:      Processes: 291 Uptime: 14m Memory: 15.40 GiB used: 1.17 GiB (7.6%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 8:12 pm
by ronbu
I am unable to install MX-21 RC1 Xfce on a Lenovo Ideapad 3 Laptop. The touchpad isn't working. While I do know the code to get touchpad to work on an already installed distro. I am unable to partition the hard drive without touchpad working. I'd like to do a dual boot of MX Linux with Windows 10.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 8:32 pm
by SwampRabbit
Leodudu wrote: Fri Oct 08, 2021 8:11 pm I now have a fresh new installation, without the Nvidia driver.
The notebook is a g3 15 3500.
Which configuration files should I upload before installing the Nvidia driver?
I’d use Timeshift to make a snapshot before anything.

I don’t think (could be wrong) but I don’t think You need to provide anything before you install the Nvidia driver.

The point of a fresh install and Timeshift snapshots BEFORE and AFTER using Nvidia Driver Installer is so you can roll back if changing things afterwards gets messy.

Like I said I’m not the person to help with identifying what needs adjusted after the Nvidia driver gets installed.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 8:35 pm
by dolphin_oracle
@Leodudu @SwampRabbit I'm a little late to the conversation on this one, but after installing the nvidia drivers uploading the /var/log/ddm.log will show exactly what happens.

also if you just want to make those commands run when you log in, then create a script with the commands and make a startup entry for it.

example: make a file called "xrandr-start-commands.sh" with the following connents:

Code: Select all

#!/bin/bash

xrandr --setprovideroutputsource NVIDIA-G0 modesetting
xrandr --output eDP-1 --primary --mode 1920x1080 --pos 1600x0 --rotate normal --reflect normal --output HDMI-1-0 --mode 1600x900 --pos 0x0 --rotate normal --output DP-1-0 --mode 1920x1080 --pos 3520x0 --rotate normal
make the file executable (you can do this from the thunar properties dialog when you right click a file).

then create a startup entry in "Session & Startup" Set the script to run at login.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 8:43 pm
by SwampRabbit
@dolphin_oracle I don’t think the installer is the problem (Optimus seemed set up right from their QSI), I think it’s a post configuration problem with this specific laptop. The user has issues getting the external displays working. The nvidia deiver “should” handle that GPU I think, it’s not super new.

So I recommended they start fresh, get Timeshift snapshots so we could test necessary adjustments and be able to roll back.

But the ddm.log might identify something for sure.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 8:47 pm
by entropyfoe
But SwampRabbit, I hate rebooting ! Usually a waste of time and it stresses the hardware. ;)

But in the name of rc1 testing, Rebooted ...
The desktop defaults and comfort theme upgrades do seem to have eliminated those weird red highlights. All else seems OK in quick testing after the reboot.

I still will change to greybird as the overlapping window title bars are all black and merge together when not the focus window. (no blue pixel line edge).

Is there anything else I need to put the defaults in place, besides selecting the themes?
BTW the comfort wide edges works well and is an improvement on other non wide themes in my opinion.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 11:19 pm
by SwampRabbit
entropyfoe wrote: Fri Oct 08, 2021 8:47 pm But SwampRabbit, I hate rebooting ! Usually a waste of time and it stresses the hardware. ;)

But in the name of rc1 testing, Rebooted ...
The desktop defaults and comfort theme upgrades do seem to have eliminated those weird red highlights. All else seems OK in quick testing after the reboot.

I still will change to greybird as the overlapping window title bars are all black and merge together when not the focus window. (no blue pixel line edge).

Is there anything else I need to put the defaults in place, besides selecting the themes?
BTW the comfort wide edges works well and is an improvement on other non wide themes in my opinion.
Thanks, messing with it some more, it seems that with the mx-comfort theme... when CSD apps are out of focus the title bars change to a light gray color with a thin black outline, but non-CSD apps the title bars don't change at all. Was that part of what you don't like, that unfocused windows need some sort of edging around the title bar area?

Maybe the unfocused non-CSD windows should act like the CSD windows, would that make it gel better?

Edit: I agree, I like mx-comfot-thick-border myself a lot.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 08, 2021 11:27 pm
by SwampRabbit
Just sent a updated docklike taskbar up for inclusion in the repos, it'll be a bit before it shows up.

This will be version 0.4.0, it fixes the automatic indicator orientation to work like expected if you change the panel orientation and location.

dolphin_oracle gets huge credit for making this possible

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 1:33 am
by mcdagan
I have a slightly complicated setup. I'm using an HP 840 G6 laptop with an HP G5 docking station. I have three monitored connected to the docking station, two Dell 2k monitors and 1 Samsung TV. When I plug the laptop to the docking station the display will show on the Samsung TV and in Monitor configuration I see the other two monitors; they are set to disabled. When I try to enable them nothing happens. Interestingly when I reboot and as the laptop is booting up all three monitors work but the displays are mirrored. When it fully boots though only the one monitor works.

Other notes: I have the new RC 21 of Xfce MXLinux installed. Previously I had Linux Mint installed on this laptop and all monitors worked without issue.

Any help would be appreciated.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 1:59 am
by seifenprinz
MX-21 beta 2 wie erstelle ich eine anfrage oder hilfe ? Bin neu hier und habe keine ahnung, was ich machen muß um, da der login sound nicht läuft beim starten von mx linux, wo kann ich mein problem reinschreiben ? Bitte um hilfe !

MX-21 Beta 2 How do I create a request or help? I'm new here and have no idea what I have to do, as the login sound does not run when starting MX Linux, where can I write my problem? Please help !

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 3:49 am
by gsm
My HP mini 110 netbook, with 2GB RAM, is now running very well with MX-21 RC1 XFCE 64-bit.
The driver for my RTL8811CU (RTL8821CU) was finally available in the repository. Unfortunately i had some trouble with the RTL8101 Ethernet adapter: Connected, but no internet. I needed to download and install a correctly working driver (latest version) from the Realtek website. It would be nice if that driver would also be made available in the repository.
Thanks for all the good work :happy:

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP Mini 110-3100 
           v: 058F110000202B00000300100 serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Hewlett-Packard model: 148A v: 79.4B serial: <filter> BIOS: Hewlett-Packard 
           v: F.15 date: 01/14/2011 
Battery:   ID-1: BAT0 charge: 36.0 Wh condition: 37.1/47.5 Wh (78%) volts: 12.4/10.8 
           model: Hewlett-Packard 4400 type: Unknown serial: <filter> status: Charging 
           Device-1: hidpp_battery_0 model: Logitech M215 serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: Single Core model: Intel Atom N455 bits: 64 type: MT arch: Bonnell 
           family: 6 model-id: 1C (28) stepping: A (10) microcode: 107 L2 cache: 512 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6650 
           Speed: 998 MHz min/max: 1000/1666 MHz Core speeds (MHz): 1: 998 2: 998 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass status: Not affected 
           Type: spectre_v1 status: Not affected 
           Type: spectre_v2 status: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
           vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:a011 
           Display: x11 server: X.Org 1.20.11 driver: intel compositor: compton v: 1 
           resolution: 1024x600~60Hz 
           OpenGL: renderer: Mesa DRI Intel Pineview M v: 1.4 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard 
           driver: r8101 v: 1.036.00-NAPI port: 2000 bus ID: 01:00.0 chip ID: 10ec:8136 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Broadcom and subsidiaries BCM4313 802.11bgn Wireless Network Adapter 
           vendor: Hewlett-Packard driver: wl v: kernel port: 2000 bus ID: 02:00.0 
           chip ID: 14e4:4727 
           IF: wlan0 state: up mac: <filter> 
           Device-3: Realtek 802.11ac NIC type: USB driver: rtl8821cu bus ID: 3-3:4 
           chip ID: 0bda:c811 serial: <filter> 
           IF: wlan1 state: down mac: <filter> 
Drives:    Local Storage: total: 111.79 GiB used: 10.31 GiB (9.2%) 
           ID-1: /dev/sda vendor: OCZ model: VERTEX3 size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 2.25 scheme: MBR 
Partition: ID-1: / raw size: 42.59 GiB size: 41.63 GiB (97.73%) used: 10.31 GiB (24.8%) fs: ext4 
           dev: /dev/sda3 
           ID-2: swap-1 size: 2.11 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda4 
Sensors:   System Temperatures: cpu: 46.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://nl.mxrepo.com/mx/repo/ bullseye main non-free
Info:      Processes: 199 Uptime: 16m Memory: 1.92 GiB used: 820.9 MiB (41.7%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 3:59 am
by vanguard28
Hello,
I installed MX 21 RC1 on my laptop and desktop PC. I can connect to internet on my main router's wifi network and have no issues there, but both devices refuse to connect to my Wifi extender's network (TP-Link TLWA855 RE). I searched online and found a solution. Add dhcp=dhclient in /etc/NetworkManager/NetworkManager.conf file and restart NetworkManager.service, and both connected to the wifi extender instantly. Previosly I ran MX19.4, which didnt require any such modifications and worked out of the box on the same network. This problem is only with Wifi Extender network and not the main router's network. All other devices - my windows 10 PC, Android phones work fine on the extender Wifi, so no issue with the device itself.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 6:20 am
by Huckleberry Finn
@Leodudu after trying @dolphin_oracle 's suggestion above : (in case it still doesn't work) have a look at this thread: viewtopic.php?p=646697#p646697

(Summary: Sometimes it requires to first turn off them all, then turn on which are wanted, one by one .. )

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 6:53 am
by dr-kart
SwampRabbit wrote: Thu Oct 07, 2021 2:44 pm
dr-kart wrote: Thu Oct 07, 2021 2:20 pm 2. hopelessly hoping to have this option that isn't available for mx21 yet (both antix21 and antix19 have it)
"hopelessly"? :footinmouth:

I see antiX has a alsamixer-equalizer-antix package, not sure if this has anything to do with it or not?
@anticapitalista do you know if this provides a "Pre-Amp option" per the linked post above?

I can work on packaging this over to MX in the next few days.
there is a ray of hope :supercool:

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 7:27 am
by SwampRabbit
@dr-kart i packaged it, but it has issues running, so need to iron that out, also don’t know if this provides what you want… but one thing at a time.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 7:37 am
by SwampRabbit
@gsm i searched for RTL8101 on Repology and nothing came back, doesn’t look like this specifically isn’t in any Distro, might have to do some research this one a bit cause I read quick that it should be handled by the r8169 driver already.

Did it work OOTB on MX-19?

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 8:05 am
by gsm
SwampRabbit wrote: Sat Oct 09, 2021 7:37 am @gsm i searched for RTL8101 on Repology and nothing came back, doesn’t look like this specifically isn’t in any Distro, might have to do some research this one a bit cause I read quick that it should be handled by the r8169 driver already.

Did it work OOTB on MX-19?
I use the RTL8101 driver from here: https://www.realtek.com/en/component/zo ... s-software
The r8169 driver does not work correctly with kernel 5.x. It will automatically first be removed when rtl8101 driver is installed.

I try MX-19 64-bit Live right now on the same HP mini 110:
I have internet OOTB using MX-19 64-bit Live (with driver r8169), which was not the case with MX-21 64-bit Live, where i did have a connection, but no internet.
With MX-21 Live i have to remove the UTP cable and then have only a good WiFi connection to the internet router.
Note:
Over time the r8169 driver appears to be restored and rtl8101 is uninstalled again. The rtl8101 driver which i used is not a dkms version. The question now is how to avoid that r8169 is restored and make rtl8101 permanent.
So i blacklisted r8169 and will see what happens.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 8:26 am
by dr-kart
SwampRabbit wrote: Sat Oct 09, 2021 7:27 am @dr-kart i packaged it, but it has issues running, so need to iron that out, also don’t know if this provides what you want… but one thing at a time.
:crossfingers:

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 9:59 am
by Huckleberry Finn
gsm wrote: Sat Oct 09, 2021 8:05 amI have internet OOTB with MX-19 64-bit Live,
... and that's with r8169 ?

Meanwhile, it looks ok with 5.10 ( or 5.x) according to here:

https://linux-hardware.org/index.php?id ... -17aa-3975

i.e. https://linux-hardware.org/?probe=466576f64f ( 10ec:8136 & 5.10 & r8169 )

Manjaro 21.0.5
Arch x86_64
Kernel 5.10.36

Code: Select all

10ec:8136:17aa:3975 »
/ 02-00	Realtek Semiconductor Co., Ltd.	RTL810xE PCI Express Fast Ethernet controller	network	r8169	works

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 2:55 pm
by Huckleberry Finn
@mcdagan : I was just replying to that thread :D

Maybe this works: First do everything according to your taste (also try ARandR from Menu), when all are just as you wanted: ARandR => save the current situation as a .sh file, then put it in Autostart. i.e. viewtopic.php?p=646697#p646697

(The created file by ARandR is already executable, so, no need to chmod +x etc... )

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 3:05 pm
by Huckleberry Finn
@waldmattis : download/file.php?id=14531&mode=view

Menu => MX Tweak => "Other" tab : "Enable mounting of ..."

Apply.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 3:44 pm
by waldmattis
no write access to built-in second hard disk


Good evening.
I have installed a second hard drive in my laptop instead of the DVD drive with a caddy.
MX is installed and booted from the first hard drive.

Write access works through the file manager when I open the hard drive in Thunar with root privileges.

But when I try to save a file from a program, I get the message
"The file could not be saved because you do not have the proper permissions. Choose another save directory".

How can I permanently organize for programs to access this second hard drive?

Thanks for any tips.

Regards
Karl

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_beta2_x64 Wildflower September 4  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: Latitude E6320 v: 01 serial: <filter> Chassis: 
           type: 9 serial: <filter> 
           Mobo: Dell model: 0GJF11 v: A01 serial: <filter> BIOS: Dell v: A06 date: 07/11/2011 
Battery:   ID-1: BAT0 charge: 9.4 Wh condition: 9.4/60.0 Wh (16%) volts: 12.6/11.1 
           model: SMP DELL HGKH01A type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i5-2520M bits: 64 type: MT MCP 
           arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F 
           L2 cache: 3072 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19956 
           Speed: 2761 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 2999 2: 2993 3: 3005 
           4: 2993 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Dell 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0126 
           Display: x11 server: X.Org 1.20.11 driver: i915 resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Dell 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e v: kernel 
           port: 4080 bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Broadcom and subsidiaries BCM4313 802.11bgn Wireless Network Adapter 
           vendor: Dell Inspiron M5010 / XPS 8300 driver: wl v: kernel port: 4040 
           bus ID: 02:00.0 chip ID: 14e4:4727 
           IF: wlan0 state: dormant mac: <filter> 
           IF-ID-1: wg-mullvad state: unknown speed: N/A duplex: N/A mac: N/A 
Drives:    Local Storage: total: 4.32 TiB used: 440.94 GiB (10.0%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR 
           ID-2: /dev/sdb vendor: Samsung model: HM500JI size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 01C4 scheme: MBR 
           ID-3: /dev/sdc type: USB vendor: Toshiba model: EXTERNAL USB size: 3.64 TiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 5438 scheme: GPT 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 
           port: 4060 bus ID: 00:1f.2 chip ID: 8086.282a rev: 04 
Partition: ID-1: / raw size: 50.00 GiB size: 48.91 GiB (97.83%) used: 27.33 GiB (55.9%) fs: ext4 
           dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 66.0 C mobo: 26.0 C sodimm: 29.0 C 
           Fan Speeds (RPM): cpu: 3279 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/opera-stable.list 
           1: deb https://deb.opera.com/opera-stable/ stable non-free
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/spotify.list 
           1: deb http://repository.spotify.com stable non-free
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb https://linux.teamviewer.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 291 Uptime: 9h 35m Memory: 7.65 GiB used: 5.33 GiB (69.6%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 4:00 pm
by Huckleberry Finn
:lipsrsealed:

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 4:16 pm
by mcdagan
Huckleberry Finn wrote: Sat Oct 09, 2021 2:55 pm @mcdagan : I was just replying to that thread :D

Maybe this works: First do everything according to your taste (also try ARandR from Menu), when all are just as you wanted: ARandR => save the current situation as a .sh file, then put it in Autostart. i.e. viewtopic.php?p=646697#p646697

(The created file by ARandR is already executable, so, no need to chmod +x etc... )
Hi Huckelberry. I used ARandR but when I try to apply the configuration I get the below error:

XRandR failed: XRandR returned error code 1: b'xrandr: cannot find crtc for output DP-1-3\n'

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 4:17 pm
by towwire
In Thunar where you want to make your Folders or files, right click and open a Terminal.

In the Terminal enter this:

Code: Select all

sudo chown -R $USER:$USER /top-level/path/to/files
Replace all of this /top-level/path/to/files with your path that is shown at the top of Thunar, it should look something like this which is my Video partition:

/media/towwire/Video/

This changes the read/write permissions from root to user.

If you want to have it mounted when you start your computer then that means either editing "fstab" or using "Disk Manager

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 4:24 pm
by Eadwine Rose
towwire wrote: Sat Oct 09, 2021 4:17 pm or using "Disk Manager
Unfortunately that program isn't there anymore. It is being worked on, I hear, but.. hopefully it will come back. :crossfingers:

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 4:33 pm
by Huckleberry Finn
mcdagan wrote: Sat Oct 09, 2021 4:16 pmI get the below error:

XRandR failed: XRandR returned error code 1: b'xrandr: cannot find crtc for output DP-1-3\n'
https://unix.stackexchange.com/question ... for-output

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 09, 2021 10:24 pm
by Richard
Eadwine Rose wrote: Fri Oct 08, 2021 11:56 am When I have changed things in the panel and I select in tweak to restore the default I am still (like in B2) left with no panel at all. I have to reboot (logout login, wager works too) and then it shows up.

Restore backup panel from tweak DOES work. It takes a number of seconds, I was thinking it was a goner and then as I was about to hit the logout button it suddenly popped up. Maybe that was the programmed panel restart that kicked in?
I've been seeing that in the Xfce rc1. (and before)

Ctrl-Alt-BkSp brings the panel back {I think...}.
I didn't think to wait a few seconds; I'll try that if it repeats. Thanks @Eadwine Rose.
It's a nuisance. Hopefully a fix can be found.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 1:03 am
by hebelwirkung
This morning I found that overnight, my keyboard layout - which usually is German - had been changed back to US. I had to manually change this back to German, then reboot for the change to take effect. This is on desktop in Virtualbox. Not sure what was going on there - I had not shut down the system, nor touched anything overnight, due to being asleep :-)

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel, cairo-dock wm: xfwm4 
           dm: LightDM 1.26.0 Distro: MX-21_rc1_x64 Wildflower October 5  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
CPU:       Topology: Dual Core model: AMD A8-6500T APU with Radeon HD Graphics bits: 64 
           type: MCP arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 
           microcode: 6000626 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 8441 
           Speed: 2110 MHz min/max: N/A Core speeds (MHz): 1: 2110 2: 2110 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 
           chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.11 driver: vmware unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 118.97 GiB used: 858.51 GiB (721.6%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 118.97 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 24.41 GiB size: 23.86 GiB (97.74%) used: 7.16 GiB (30.0%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 183.9 MiB (9.5%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 19.17 GiB (22.7%) 
           fs: ext4 dev: /dev/sda4 
           ID-4: swap-1 size: 6.25 GiB used: 2.3 MiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda1 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 198 Uptime: 6m Memory: 3.02 GiB used: 1.86 GiB (61.6%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 10:53 am
by NGIB
Installed and used it for a few days. Except for not being able to make it look how I wanted, everything worked OK. I will not be moving to MX21.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 11:01 am
by Eadwine Rose
If you were to share the not being able to bit, we might help you to be able to ;)

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 11:10 am
by dolphin_oracle
NGIB wrote: Sun Oct 10, 2021 10:53 am Installed and used it for a few days. Except for not being able to make it look how I wanted, everything worked OK. I will not be moving to MX21.
thanks for checking it out.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 11:37 am
by Leodudu
dolphin_oracle wrote: Fri Oct 08, 2021 8:35 pm @Leodudu @SwampRabbit I'm a little late to the conversation on this one, ...
The monitors are working. Thanks.

Another issue is that after my analog audio output is buzzing when not playing.
After commenting out the line
"load-module module-suspend-on-idle"
in /etc/pulse/default.pa and /etc/pulse/system.pa, the problem is solved.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 11:53 am
by Somewhat Reticent
As noted here [ viewtopic.php?f=94&t=66622 ] I haven't figured out how to get Kaffeine to use a USB dongle for TV reception/recording on MX21beta/rc1.
The device is listed by System Profiler, so the system's aware of the device, which uses ATSC_1.0; I can't predict how much longer broadcasters here will use legacy tech.
On the upside, VLC doesn't go bananas and crash like it does in my current MX19 install.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 12:40 pm
by mmikeinsantarosa
These comments are for RC1 installs on Virtualbox-6.1.22-dfsg-1 MX19 x64 host only:

1) both 386 & x64 installs eject the ISO at the end so no more accidental restarting from the ISO used to install from. - Nice!

2) I use kgpg to manage my key for signing packages and the kgpg icon (padlock) no longer shows up in the notification area. This is for both 386 & x64 installs.
edit: I see the same issue for an install on my older laptop. It could just be a bug in kgpg on bullseye.

3) Sharing files from host to VM and back has been fixed in x64 ( zero issues so far) but after copying files between the host and 386 VM, the files are unusable. md5 checksums don't match after a copy either from host to VM or VM to host. If I copy a text file from host to VM or VM to host, after execution, the copied file is no good. The same happens for compressed files.

- mike

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 1:10 pm
by entropyfoe
SwampRabbit

Exactly, you got it
Was that part of what you don't like, that unfocused windows need some sort of edging around the title bar area?
I often have a lot of windows open, so of course many overlap, especially the title bars, often there is an area of black screen where 3-5 title bars overlap, creating a large undifferentiated black area on the screen.

To grab a window to work on it, make it active, it is hard for the user (at least me) to know where one window begins and ends, so which was that thunar window with the search...

Some line or edge must be on ALL windows no matter which application it spawns from.

Then the user easily sees which title bar goes with each window. It may be a subtle point, but it improves ease of use.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 3:42 pm
by dolphin_oracle
mmikeinsantarosa wrote: Sun Oct 10, 2021 12:40 pm These comments are for RC1 installs on Virtualbox-6.1.22-dfsg-1 MX19 x64 host only:

1) both 386 & x64 installs eject the ISO at the end so no more accidental restarting from the ISO used to install from. - Nice!

2) I use kgpg to manage my key for signing packages and the kgpg icon (padlock) no longer shows up in the notification area. This is for both 386 & x64 installs. I'll try an install on HW and see if the problem still exists.

3) Sharing files from host to VM and back has been fixed in x64 ( zero issues so far) but after copying files between the host and 386 VM, the files are unusable. md5 checksums don't match after a copy either from host to VM or VM to host. If I copy a text file from host to VM or VM to host, after execution, the copied file is no good. The same happens for compressed files.

- mike
out of curiosity, did you install the guest additions on the 32 bit VM?

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 4:10 pm
by mmikeinsantarosa
dolphin_oracle wrote: Sun Oct 10, 2021 3:42 pm
mmikeinsantarosa wrote: Sun Oct 10, 2021 12:40 pm These comments are for RC1 installs on Virtualbox-6.1.22-dfsg-1 MX19 x64 host only:

1) both 386 & x64 installs eject the ISO at the end so no more accidental restarting from the ISO used to install from. - Nice!

2) I use kgpg to manage my key for signing packages and the kgpg icon (padlock) no longer shows up in the notification area. This is for both 386 & x64 installs. I'll try an install on HW and see if the problem still exists.

3) Sharing files from host to VM and back has been fixed in x64 ( zero issues so far) but after copying files between the host and 386 VM, the files are unusable. md5 checksums don't match after a copy either from host to VM or VM to host. If I copy a text file from host to VM or VM to host, after execution, the copied file is no good. The same happens for compressed files.

- mike
out of curiosity, did you install the guest additions on the 32 bit VM?
No. I executed Device->Insert Guest Additions and executed the .run file that shows up there. I do the same for the 64 bit VM.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 4:56 pm
by Richard
Installed & running Mx21rc1 Xfce since yesterday.
Got all the Bullseye 11.1 updates as well.
Everything is running great.
Thanks to all the devs!!

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: LENOVO product: 2349DG5 v: ThinkPad T430 serial: <filter> 
           Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 2349DG5 serial: <filter> UEFI [Legacy]: LENOVO 
           v: G1ET92WW (2.52 ) date: 02/14/2013 
Battery:   ID-1: BAT0 charge: 40.3 Wh condition: 41.0/56.2 Wh (73%) volts: 12.2/10.8 
           model: LGC 45N1005 type: Li-ion serial: <filter> status: Unknown 
CPU:       Topology: Dual Core model: Intel Core i5-3380M bits: 64 type: MT MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 21 L2 cache: 3072 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 23147 
           Speed: 1438 MHz min/max: 1200/3600 MHz Core speeds (MHz): 1: 1518 2: 1474 3: 1419 
           4: 1471 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Lenovo driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0166 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           compositor: compton v: 1 resolution: 1600x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e v: kernel 
           port: 5080 bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel 
           port: efa0 bus ID: 03:00.0 chip ID: 8086:0085 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 2.20 TiB used: 16.20 GiB (0.7%) 
           ID-1: /dev/mmcblk0 model: SC128 size: 119.08 GiB block size: physical: 512 B 
           logical: 512 B serial: <filter> scheme: MBR 
           ID-2: /dev/sda model: Acer GT500A SATA3 256G size: 238.47 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1A0 scheme: MBR 
           ID-3: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive size: 28.91 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1100 scheme: MBR 
           ID-4: /dev/sdc type: USB vendor: Western Digital model: WD Elements 2621 
           size: 1.82 TiB block size: physical: 512 B logical: 512 B serial: <filter> rev: 1026 
           scheme: GPT 
Partition: ID-1: / raw size: 25.10 GiB size: 24.54 GiB (97.76%) used: 8.16 GiB (33.3%) fs: ext4 
           dev: /dev/sda1 
           ID-2: /home raw size: 209.36 GiB size: 205.02 GiB (97.92%) used: 8.03 GiB (3.9%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: swap-1 size: 4.02 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 47.0 C mobo: 0.0 C 
           Fan Speeds (RPM): cpu: 2470 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
Info:      Processes: 260 Uptime: 6h 23m Memory: 7.46 GiB used: 1.84 GiB (24.7%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 5:01 pm
by SwampRabbit
entropyfoe wrote: Sun Oct 10, 2021 1:10 pm Some line or edge must be on ALL windows no matter which application it spawns from.
Let’s see what we can do.

The theme is on GitHub for those willing and able to take time to see if they can do it.
https://github.com/MX-Linux/mx-comfort-themes

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 10, 2021 10:57 pm
by figueroa
Upon finishing today's updates, I see this error (new to me) at the end of the terminal screen output:

Code: Select all

install-info: warning: no info dir entry in `/usr/share/info/gtkdialog.info.gz'
The file does exist:

Code: Select all

$ ls -l /usr/share/info/gtk*
-rw-r--r-- 1 root root 6170 Feb  6  2020 /usr/share/info/gtkdialog.info.gz
How can "Your message contains too few characters" What is that about at the top of this window?

ADDED: Maybe it's significant that I'm running the LXDE desktop remotely logged in via X2GO. On the other hand, that's been my norm on multiple machines ever since MX-19 came out.

Re: MX-21 RC1 feedback (Xfce)

Posted: Mon Oct 11, 2021 9:35 am
by entropyfoe
I got all the synaptic upgrades to the RC1 yesterday including the new kernel. 5.10-0-8 to the -9.
I accepted all upgrades. I rebooted, but it remained on the old kernel.
So, I went back to the MX 19.4 install and update-grub as root.
Then when going back to rc1, the new kernel is loaded.

I guess this is the expected behavior, right?

One other minor thing.
When I suspend to RAM, when I wake, if firefox was the active window, it is all pixelated. Not a big problem, when you touch it with the cursor, it redraws correctly.
This only seems to affect firefox, so maybe it is a firefox problem (though minor).
If firefox is not the active window, it seems OK.

As for those theme things with the title bars, a nice to have, making the comfort theme look better, but if there is no fix, it is easy to select another theme like greybird that has the white title bar edge, delineating the window edges.

Re: MX-21 RC1 feedback (Xfce)

Posted: Mon Oct 11, 2021 9:38 am
by dolphin_oracle
entropyfoe wrote: Mon Oct 11, 2021 9:35 am I got all the synaptic upgrades to the RC1 yesterday including the new kernel. 5.10-0-8 to the -9.
I accepted all upgrades. I rebooted, but it remained on the old kernel.
So, I went back to the MX 19.4 install and update-grub as root.
Then when going back to rc1, the new kernel is loaded.

I guess this is the expected behavior, right?
yes. the grub update that happens during kernel update will not affect a grub menu that is controlled by a different installation.

Re: MX-21 RC1 feedback (Xfce)

Posted: Mon Oct 11, 2021 11:20 am
by AdamK
AdamK wrote: Thu Oct 07, 2021 7:34 am Small bug report:
Using F4 for the Drop down terminal only works on the Primary Display. Even though my cursor is on another display, the drop down appears on the primary. Move to monitor with pointer is checked in Preferences -> Drop-down tab -> Position.
Bump.
Anyone experiencing the same?

Re: MX-21 RC1 feedback (Xfce)

Posted: Mon Oct 11, 2021 6:05 pm
by Stuart_M
AdamK wrote: Mon Oct 11, 2021 11:20 am
AdamK wrote: Thu Oct 07, 2021 7:34 am Small bug report:
Using F4 for the Drop down terminal only works on the Primary Display. Even though my cursor is on another display, the drop down appears on the primary. Move to monitor with pointer is checked in Preferences -> Drop-down tab -> Position.
Bump.
Anyone experiencing the same?
I thought I'd try on my dual-monitor setup and yes, the same incorrect behavior exists with me as well.

After pressing F4, the Terminal drop-down will only appear on my primary monitor regardless of which monitor my mouse pointer is on, and yes, the "Move to monitor with pointer" is enabled in the drop-down Terminal Preferences > "Drop-down" tab as shown in the below image. That setting does not have any affect, hence the problem.
Drop-down_Terminal_Preferences_drop-down_tab.png



As a side note, MX-19.4 works wonderfully well in this regard - enabling or disabling "Move to monitor with pointer" does just as it says it will.

Re: MX-21 RC1 feedback (Xfce)

Posted: Mon Oct 11, 2021 6:13 pm
by Eadwine Rose
Confirmed here as well, just tried.

Re: MX-21 RC1 feedback (Xfce)

Posted: Tue Oct 12, 2021 3:30 pm
by Sigi
May be could wireguard 1.0.20210223-1 in Stable Repo update to 1.0.20210606 / tools 1.0.20210914?

https://www.wireguard.com/install/

Re: MX-21 RC1 feedback (Xfce)

Posted: Tue Oct 12, 2021 8:34 pm
by Feuerkl1nge
I am experiencing bugs with libguestfs-tools.
As linked on https://libguestfs.org/ I reported the bug to https://bugzilla.redhat.com/.
I inform the MX devs here to please be aware of it.

answer on bugzilla.redhat.com
Richard W.M. Jones 2021-10-12 20:31:08 UTC

Thanks for providing the information. The libguestfs-test-tool
output certainly suggests a major problem with the package on MX Linux
(derived from Debian).

I think it's very likely that the following upstream package
should fix the problem:

https://github.com/libguestfs/libguestf ... 5100853890

It's best to inform your distribution of the problem so they
can try including this patch, but in the meantime you can try
this workaround:

echo mount > /usr/lib/x86_64-linux-gnu/guestfs/supermin.d/zz-mount
edit
Richard W.M. Jones 2021-10-12 20:31:55 UTC

> I think it's very likely that the following upstream package

patch, not package

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 13, 2021 12:24 am
by SwampRabbit
Feuerkl1nge wrote: Tue Oct 12, 2021 8:34 pm I am experiencing bugs with libguestfs-tools.
As linked on https://libguestfs.org/ I reported the bug to https://bugzilla.redhat.com/.
I inform the MX devs here to please be aware of it.

answer on bugzilla.redhat.com
Richard W.M. Jones 2021-10-12 20:31:08 UTC

Thanks for providing the information. The libguestfs-test-tool
output certainly suggests a major problem with the package on MX Linux
(derived from Debian).

I think it's very likely that the following upstream package
should fix the problem:

https://github.com/libguestfs/libguestf ... 5100853890

It's best to inform your distribution of the problem so they
can try including this patch, but in the meantime you can try
this workaround:

echo mount > /usr/lib/x86_64-linux-gnu/guestfs/supermin.d/zz-mount
Thanks for that!

I just checked to see if Debian added this patch to libguestfs (1:1.44.2-1) that is in Bookworm and Sid, looks like they haven't.

I see that the fix commit is on 1.46.0 master, Debian doesn't have that version yet, but....

I wonder if we can package 1.44.2 with it. Give me some time to test build 1.44.2 and create a patch.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 13, 2021 9:29 am
by hebelwirkung
I've been using RC1 since it was released and have had next to no problems; it's amazing how smoothly everything is working already (in Virtualbox anyway). The thing that grates - okay, takes a little getting used to - is the CSD in some apps, but that's XFCE and has nothing to do with MX21.

One small thing though - for the second time in a few days, my keyboard layout has set itself back from German, which I usually use, to English (US) which is what I use for my system defaults. First time this happened was overnight when I wasn't at the computer. Just now, it occurred while I was working. I had to reset it manually and reboot. German layout is active again, but oddly enough, when I checked after rebooting, the keyboard layout option for English (US), formerly displayed, has now vanished from the display. It's still in the drop down list but I'm not going to set it as an option again for now.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel, cairo-dock wm: xfwm4 
           dm: LightDM 1.26.0 Distro: MX-21_rc1_x64 Wildflower October 5  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
CPU:       Topology: Dual Core model: AMD A8-6500T APU with Radeon HD Graphics bits: 64 
           type: MCP arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 
           microcode: 6000626 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 8441 
           Speed: 2110 MHz min/max: N/A Core speeds (MHz): 1: 2110 2: 2110 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 
           chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.11 driver: vmware unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 118.97 GiB used: 866.24 GiB (728.1%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 118.97 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 24.41 GiB size: 23.86 GiB (97.74%) used: 7.88 GiB (33.0%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 183.9 MiB (9.5%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 20.32 GiB (24.1%) 
           fs: ext4 dev: /dev/sda4 
           ID-4: swap-1 size: 6.25 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda1 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 209 Uptime: 2m Memory: 3.02 GiB used: 745.8 MiB (24.1%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 13, 2021 11:19 am
by dolphin_oracle
hebelwirkung wrote: Wed Oct 13, 2021 9:29 am I've been using RC1 since it was released and have had next to no problems; it's amazing how smoothly everything is working already (in Virtualbox anyway). The thing that grates - okay, takes a little getting used to - is the CSD in some apps, but that's XFCE and has nothing to do with MX21.

One small thing though - for the second time in a few days, my keyboard layout has set itself back from German, which I usually use, to English (US) which is what I use for my system defaults. First time this happened was overnight when I wasn't at the computer. Just now, it occurred while I was working. I had to reset it manually and reboot. German layout is active again, but oddly enough, when I checked after rebooting, the keyboard layout option for English (US), formerly displayed, has now vanished from the display. It's still in the drop down list but I'm not going to set it as an option again for now.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel, cairo-dock wm: xfwm4 
           dm: LightDM 1.26.0 Distro: MX-21_rc1_x64 Wildflower October 5  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
CPU:       Topology: Dual Core model: AMD A8-6500T APU with Radeon HD Graphics bits: 64 
           type: MCP arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 
           microcode: 6000626 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 8441 
           Speed: 2110 MHz min/max: N/A Core speeds (MHz): 1: 2110 2: 2110 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 
           chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.11 driver: vmware unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 118.97 GiB used: 866.24 GiB (728.1%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 118.97 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 24.41 GiB size: 23.86 GiB (97.74%) used: 7.88 GiB (33.0%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 183.9 MiB (9.5%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 20.32 GiB (24.1%) 
           fs: ext4 dev: /dev/sda4 
           ID-4: swap-1 size: 6.25 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda1 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 209 Uptime: 2m Memory: 3.02 GiB used: 745.8 MiB (24.1%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
there is a keyboard flag switcher that should be running when more than one keyboard is defined. X also has a keycombo that will do a switch, currently set at rcontrol+rshift.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 13, 2021 2:35 pm
by hebelwirkung
dolphin_oracle wrote: Wed Oct 13, 2021 11:19 am
hebelwirkung wrote: Wed Oct 13, 2021 9:29 am I've been using RC1 since it was released and have had next to no problems; it's amazing how smoothly everything is working already (in Virtualbox anyway). The thing that grates - okay, takes a little getting used to - is the CSD in some apps, but that's XFCE and has nothing to do with MX21.

One small thing though - for the second time in a few days, my keyboard layout has set itself back from German, which I usually use, to English (US) which is what I use for my system defaults. First time this happened was overnight when I wasn't at the computer. Just now, it occurred while I was working. I had to reset it manually and reboot. German layout is active again, but oddly enough, when I checked after rebooting, the keyboard layout option for English (US), formerly displayed, has now vanished from the display. It's still in the drop down list but I'm not going to set it as an option again for now.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel, cairo-dock wm: xfwm4 
           dm: LightDM 1.26.0 Distro: MX-21_rc1_x64 Wildflower October 5  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
CPU:       Topology: Dual Core model: AMD A8-6500T APU with Radeon HD Graphics bits: 64 
           type: MCP arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 
           microcode: 6000626 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 8441 
           Speed: 2110 MHz min/max: N/A Core speeds (MHz): 1: 2110 2: 2110 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 
           chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.11 driver: vmware unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 118.97 GiB used: 866.24 GiB (728.1%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 118.97 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 24.41 GiB size: 23.86 GiB (97.74%) used: 7.88 GiB (33.0%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 183.9 MiB (9.5%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 20.32 GiB (24.1%) 
           fs: ext4 dev: /dev/sda4 
           ID-4: swap-1 size: 6.25 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda1 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 209 Uptime: 2m Memory: 3.02 GiB used: 745.8 MiB (24.1%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
there is a keyboard flag switcher that should be running when more than one keyboard is defined. X also has a keycombo that will do a switch, currently set at rcontrol+rshift.
Yes, I'm aware of the switcher; the thing puzzling me is that without my doing anything, a keyboard layout may suddenly switch from one to another. It's no big deal - just somewhat mysterious. The fact that now, one of my two defined keyboard settings is no longer displayed, seems odd as well. I've never had that happen with MX19. Again, it's trifling but weird :-)

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 13, 2021 3:04 pm
by fehlix
hebelwirkung wrote: Wed Oct 13, 2021 9:29 am One small thing though - for the second time in a few days, my keyboard layout has set itself back from German, which I usually use, to English (US) which is what I use for my system defaults. First time this happened was overnight when I wasn't at the computer. Just now, it occurred while I was working. I had to reset it manually and reboot. German layout is active again, but oddly enough, when I checked after rebooting, the keyboard layout option for English (US), formerly displayed, has now vanished from the display. It's still in the drop down list but I'm not going to set it as an option again for now.
Not really clear to me what this is about. Is keyboard different after login? From what display has it vanished?
System wide keyboard layout definition are different to user-session defined one and are applied depending on user-keyboard settings...
+++EDIT+++ ... and depends on whether autologin is enabled, b/c at login screen the default keyboard pre-selected would be the 1st layout from system-wide defined keyboard layouts...

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 13, 2021 4:07 pm
by hebelwirkung
fehlix wrote: Wed Oct 13, 2021 3:04 pm
hebelwirkung wrote: Wed Oct 13, 2021 9:29 am One small thing though - for the second time in a few days, my keyboard layout has set itself back from German, which I usually use, to English (US) which is what I use for my system defaults. First time this happened was overnight when I wasn't at the computer. Just now, it occurred while I was working. I had to reset it manually and reboot. German layout is active again, but oddly enough, when I checked after rebooting, the keyboard layout option for English (US), formerly displayed, has now vanished from the display. It's still in the drop down list but I'm not going to set it as an option again for now.
Not really clear to me what this is about. Is keyboard different after login? From what display has it vanished?
System wide keyboard layout definition are different to user-session defined one and are applied depending on user-keyboard settings...
+++EDIT+++ ... and depends on whether autologin is enabled, b/c at login screen the default keyboard pre-selected would be the 1st layout from system-wide defined keyboard layouts...
Login on this machine requires password. The keyboard layout I have set (German in my case) is the one I unfailingly get after I've logged in, which is as it should be. Expected behavior would be for this layout to be maintained throughout the session.

Twice, however, in mid-session the layout changed from the top one in my list of active layouts to the second one (in my case, English US) without my doing anything to prompt that.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 13, 2021 4:23 pm
by fehlix
hebelwirkung wrote: Wed Oct 13, 2021 4:07 pm
fehlix wrote: Wed Oct 13, 2021 3:04 pm
hebelwirkung wrote: Wed Oct 13, 2021 9:29 am One small thing though - for the second time in a few days, my keyboard layout has set itself back from German, which I usually use, to English (US) which is what I use for my system defaults. First time this happened was overnight when I wasn't at the computer. Just now, it occurred while I was working. I had to reset it manually and reboot. German layout is active again, but oddly enough, when I checked after rebooting, the keyboard layout option for English (US), formerly displayed, has now vanished from the display. It's still in the drop down list but I'm not going to set it as an option again for now.
Not really clear to me what this is about. Is keyboard different after login? From what display has it vanished?
System wide keyboard layout definition are different to user-session defined one and are applied depending on user-keyboard settings...
+++EDIT+++ ... and depends on whether autologin is enabled, b/c at login screen the default keyboard pre-selected would be the 1st layout from system-wide defined keyboard layouts...
Login on this machine requires password. The keyboard layout I have set (German in my case) is the one I unfailingly get after I've logged in, which is as it should be. Expected behavior would be for this layout to be maintained throughout the session.

Twice, however, in mid-session the layout changed from the top one in my list of active layouts to the second one (in my case, English US) without my doing anything to prompt that.
OK, let's have look. Please run these commands within terminal and post command and text output:

Code: Select all

cat /etc/default/keyboard
and

Code: Select all

setxkbmap -query
and

Code: Select all

grep  XkbDisable ~/.config/xfce4/xfconf/xfce-perchannel-xml/keyboard-layout.xml

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 13, 2021 9:48 pm
by Slayhill
Been using MX21 RC1 since it was released and all of the bugs I noticed in the beginning have already been corrected. I'm not a power user but MX is my daily driver. The only issue that I am still experiencing is the behavior of the suspend power mode. I have the power manager set to suspend when laptop lid is closed. But when I do that I am unable to log back in after waking the system up. When I enter my password and hit Unlock the screen goes blank. No mouse cursor or anything. Ctrl+Alt+Delete gets me back to the login screen but when I try again, same result. The only way to get out of it is to restart. If I select suspend from the shutdown menu it works fine. Only happens when I shut the lid while running.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Portable System: Dell product: Inspiron 1764 v: A13 serial: <filter> 
           Mobo: Dell model: 0TKV96 v: A13 serial: <filter> BIOS: Dell v: A13 date: 03/29/2011 
Battery:   ID-1: BAT0 charge: 3.0 Wh condition: 3.0/4.4 Wh (68%) volts: 12.3/11.1 
           model: SIMPLO Dell type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i5 M 430 bits: 64 type: MT MCP arch: Nehalem 
           family: 6 model-id: 25 (37) stepping: 2 microcode: 11 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 18088 
           Speed: 1333 MHz min/max: 1199/2267 MHz boost: enabled Core speeds (MHz): 1: 1299 
           2: 1316 3: 1299 4: 1366 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Dell driver: i915 
           v: kernel bus ID: 00:02.0 chip ID: 8086:0046 
           Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1600x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Dell 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Broadcom and subsidiaries BCM43224 802.11a/b/g/n 
           vendor: Dell Wireless 1520 Half-size Mini PCIe Card driver: wl v: kernel port: 1840 
           bus ID: 03:00.0 chip ID: 14e4:4353 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 
           v: kernel port: 2000 bus ID: 04:00.0 chip ID: 10ec:8136 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 8.24 GiB (1.8%) 
           ID-1: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 023 scheme: MBR 
Partition: ID-1: / raw size: 457.75 GiB size: 449.50 GiB (98.20%) used: 8.24 GiB (1.8%) fs: ext4 
           dev: /dev/sda1 
           ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 44.0 C mobo: 0.0 C 
           Fan Speeds (RPM): cpu: 3227 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           No active apt repos in: /etc/apt/sources.list.d/microsoft-edge-beta.list 
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.genesisadaptive.com/mxlinux/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb https://linux.teamviewer.com/deb stable main
Info:      Processes: 295 Uptime: 13m Memory: 7.57 GiB used: 924.7 MiB (11.9%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 14, 2021 1:51 am
by hebelwirkung
fehlix wrote: Wed Oct 13, 2021 4:23 pm
hebelwirkung wrote: Wed Oct 13, 2021 4:07 pm
fehlix wrote: Wed Oct 13, 2021 3:04 pm
Not really clear to me what this is about. Is keyboard different after login? From what display has it vanished?
System wide keyboard layout definition are different to user-session defined one and are applied depending on user-keyboard settings...
+++EDIT+++ ... and depends on whether autologin is enabled, b/c at login screen the default keyboard pre-selected would be the 1st layout from system-wide defined keyboard layouts...
Login on this machine requires password. The keyboard layout I have set (German in my case) is the one I unfailingly get after I've logged in, which is as it should be. Expected behavior would be for this layout to be maintained throughout the session.

Twice, however, in mid-session the layout changed from the top one in my list of active layouts to the second one (in my case, English US) without my doing anything to prompt that.
OK, let's have look. Please run these commands within terminal and post command and text output:

Code: Select all

cat /etc/default/keyboard
and

Code: Select all

setxkbmap -query
and

Code: Select all

grep  XkbDisable ~/.config/xfce4/xfconf/xfce-perchannel-xml/keyboard-layout.xml
Okay, here's the output:

$ cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="de,us"
XKBVARIANT=","
XKBOPTIONS="terminate:ctrl_alt_bksp,grp_led:scroll,grp:rctrl_rshift_toggle"

BACKSPACE="guess"



$ setxkbmap -query
rules: evdev
model: pc105
layout: de
options: terminate:ctrl_alt_bksp



$ grep XkbDisable ~/.config/xfce4/xfconf/xfce-perchannel-xml/keyboard-layout.xml
<property name="XkbDisable" type="bool" value="false"/>

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 14, 2021 5:16 am
by jbernardo
Hello,
I have Xiaomi EBs Basic 2 earplugs. On 19.4, they work well. On 21RC1, they pair, but bluez only (tries to) connect to the serial port profile, and ignores the audio. I first noticed it on AHS, but it also happens on "normal" XFCE.
First machine, with AHS:

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: CHUWIInnovationAnd(ShenZhen) product: GemiBook Pro v: N/A 
           serial: <filter> 
           Mobo: N/A model: N/A serial: <filter> UEFI: American Megatrends 
           v: JXX-BI-14.1-W133GWR300-058-D date: 03/12/2021 
Battery:   ID-1: BAT0 charge: 38.0 Wh condition: 38.0/38.0 Wh (100%) volts: 8.7/N/A model: N/A 
           type: Unknown serial: <filter> status: Charging 
CPU:       Topology: Quad Core model: Intel Celeron J4125 bits: 64 type: MCP arch: Goldmont Plus 
           family: 6 model-id: 7A (122) stepping: 8 microcode: 1A L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 15974 
           Speed: 1134 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1422 2: 1550 3: 1462 
           4: 1522 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel GeminiLake [UHD Graphics 600] driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:3185 
           Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: fbdev,vesa 
           resolution: 2160x1440~60Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics 600 (GLK 2) v: 4.6 Mesa 21.2.2 
           direct render: Yes 
Audio:     Device-1: Intel Celeron/Pentium Silver Processor High Definition Audio 
           driver: snd_hda_intel v: kernel bus ID: 00:0e.0 chip ID: 8086:3198 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: f040 bus ID: 01:00.0 
           chip ID: 8086:2723 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 
           bus ID: 2-1.3:5 chip ID: 0bda:8153 serial: <filter> 
           IF: eth0 state: down mac: <filter> 
           IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:    Local Storage: total: 704.24 GiB used: 259.53 GiB (36.9%) 
           ID-1: /dev/sda vendor: Western Digital model: WDS500G2B0B-00YS70 size: 465.76 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 30WD 
           scheme: GPT 
           ID-2: /dev/sdb vendor: Netac model: SSD 256GB size: 238.47 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 0A0 scheme: GPT 
Partition: ID-1: / raw size: 29.32 GiB size: 28.69 GiB (97.85%) used: 12.16 GiB (42.4%) fs: ext4 
           dev: /dev/sda5 
           ID-2: /home raw size: 292.54 GiB size: 286.95 GiB (98.09%) used: 247.18 GiB (86.1%) 
           fs: ext4 dev: /dev/sda7 
           ID-3: swap-1 size: 9.01 GiB used: 132.8 MiB (1.4%) fs: swap 
           swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda8 
Sensors:   System Temperatures: cpu: 54.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://nl.mxrepo.com/mx/repo/ bullseye main non-free
           2: deb http://nl.mxrepo.com/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/signal-xenial-added-by-mxpi.list 
           1: deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/teams.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
           Active apt repos in: /etc/apt/sources.list.d/vscode.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/vscode stable main
Info:      Processes: 309 Uptime: 19h 31m Memory: 11.51 GiB used: 4.78 GiB (41.5%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 
           Shell: quick-system-in running in: quick-system-in inxi: 3.0.36 
Second machine, RC1-XFCE:

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: FUJITSU product: LIFEBOOK E544 v: 10601736654 serial: <filter> 
           Chassis: type: 10 v: LIFEBOOK E544 serial: <filter> 
           Mobo: FUJITSU model: FJNB281 v: F2 serial: <filter> UEFI [Legacy]: FUJITSU // Phoenix 
           v: Version 1.06 date: 03/12/2015 
Battery:   ID-1: CMB1 charge: 32.0 Wh condition: 32.0/48.6 Wh (66%) volts: 12.2/10.8 
           model: Fujitsu CP671396-01 type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i3-4000M bits: 64 type: MT MCP arch: Haswell 
           family: 6 model-id: 3C (60) stepping: 3 microcode: 28 L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156 
           Speed: 889 MHz min/max: 800/2400 MHz Core speeds (MHz): 1: 798 2: 799 3: 823 4: 802 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Fujitsu Limited. 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0416 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
           vendor: Fujitsu Limited. driver: snd_hda_intel v: kernel bus ID: 00:03.0 
           chip ID: 8086:0c0c 
           Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Fujitsu Limited. 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Fujitsu Limited. driver: r8169 v: kernel port: 3000 bus ID: 02:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: 3000 bus ID: 03:00.0 
           chip ID: 8086:08b1 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 119.24 GiB used: 79.06 GiB (66.3%) 
           ID-1: /dev/sda vendor: Samsung model: MZ7TE128HMGR-00004 size: 119.24 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 300Q scheme: MBR 
Partition: ID-1: / raw size: 17.93 GiB size: 17.48 GiB (97.49%) used: 6.57 GiB (37.6%) fs: ext4 
           dev: /dev/sda1 
           ID-2: /home raw size: 95.28 GiB size: 93.66 GiB (98.30%) used: 72.50 GiB (77.4%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda4 
           ID-4: swap-2 size: 4.03 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 51.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://nl.mxrepo.com/mx/repo/ bullseye main non-free
Info:      Processes: 213 Uptime: 8m Memory: 7.67 GiB used: 625.0 MiB (8.0%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
Device info from blueman:

Code: Select all

20:1B:88:04:D8:68
public
Mi True Wireless EBs Basic 2
Mi True Wireless EBs Basic 2
0x240418
0x0000
audio-card
yes
no
no
no
no
00001101-0000-1000-8000-00805f9b34fb Serial Port
00001108-0000-1000-8000-00805f9b34fb Headset
0000110b-0000-1000-8000-00805f9b34fb Audio Sink
0000110c-0000-1000-8000-00805f9b34fb Remote Control Target
0000110e-0000-1000-8000-00805f9b34fb Remote Control
0000111e-0000-1000-8000-00805f9b34fb Handsfree
00001200-0000-1000-8000-00805f9b34fb PnP Information
bluetooth:v005Dp223Bd0100
/org/bluez/hci0
This headset still works (and doesn't have the "Serial Port" profile):

Code: Select all

5C:FB:7C:0B:ED:2C
public
JBL TUNE600BTNC
JBL TUNE600BTNC
0x240404
0x0000
audio-card
yes
no
no
no
no
00001108-0000-1000-8000-00805f9b34fb Headset
0000110b-0000-1000-8000-00805f9b34fb Audio Sink
0000110c-0000-1000-8000-00805f9b34fb Remote Control Target
0000110e-0000-1000-8000-00805f9b34fb Remote Control
0000111e-0000-1000-8000-00805f9b34fb Handsfree
/org/bluez/hci0
As I wrote, both work well on 19.4, on different machines.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 14, 2021 5:48 am
by fehlix
hebelwirkung wrote: Thu Oct 14, 2021 1:51 am $ grep XkbDisable ~/.config/xfce4/xfconf/xfce-perchannel-xml/keyboard-layout.xml
<property name="XkbDisable" type="bool" value="false"/>
OK, this tells us, you disabled system-layout within (user) Keyboard Settings
and with MX-21 Xfce the only one keyboard which is selected at the login screen
will be made active/available by some dbus-calls during login.
Not sure why it resets itself during a session, seems somehow related to dbus.
If you want to avoid this effect, I guess if you set back to use "System keyboard" it shall stay with the select layout.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 14, 2021 6:16 am
by hebelwirkung
fehlix wrote: Thu Oct 14, 2021 5:48 am
hebelwirkung wrote: Thu Oct 14, 2021 1:51 am $ grep XkbDisable ~/.config/xfce4/xfconf/xfce-perchannel-xml/keyboard-layout.xml
<property name="XkbDisable" type="bool" value="false"/>
OK, this tells us, you disabled system-layout within (user) Keyboard Settings
and with MX-21 Xfce the only one keyboard which is selected at the login screen
will be made active/available by some dbus-calls during login.
Not sure why it resets itself during a session, seems somehow related to dbus.
If you want to avoid this effect, I guess if you set back to use "System keyboard" it shall stay with the select layout.
Yes, I'd actually disabled the system defaults setting, but only after the second time the keyboard hat reset itself. I've now re-enabled it which, after a reboot, brought back the English US option as the second one, with German, as intended, on top. Thanks for looking at this. If it continues to act up, I'll report :-)

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 15, 2021 8:55 am
by SwampRabbit
@entropyfoe and @fladd when you update next time, please take a moment to look around, a change was specifically done to address an item you both provided feedback on.

I won’t spoil the surprise, if you don’t find it, your not testing enough or properly. :p

Edie: that last part is a joke if the smiley didn't give it away, added clarity to keep Eadwine Rose off my back! :footinmouth:

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 15, 2021 9:05 am
by Eadwine Rose
SwampRabbit wrote: Fri Oct 15, 2021 8:55 am if you don’t find it, your not testing enough or properly. :p
If you said that to me I would say something like bye.

Please be careful in your wordings, you're chasing them off ;)

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 15, 2021 9:08 am
by SwampRabbit
Eadwine Rose wrote: Fri Oct 15, 2021 9:05 am Please be careful in your wordings, you're chasing them off ;)
I used a :p

If you have to locate the fish please do so, I haven't been beaten up in awhile. :lipsrsealed:

I edited the post for clarity though ;)

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 15, 2021 9:10 am
by Eadwine Rose
Bend over please.

*giggles*

:fishslap:

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 15, 2021 10:16 am
by entropyfoe
SwampRabbit,

OK, I will update and test tonight or tomorrow. (with a reboot !) Thanks.

Re: MX-21 RC1 feedback (Xfce)

Posted: Fri Oct 15, 2021 8:08 pm
by entropyfoe
SwampRabbit, yes that is perfect. All the windows have a line of 2 pixels of grey against the window header's black. There is a visible end where each overlapping window begins. For me, and I think many, it is an easier user visual interface, because you know where to grasp a specific window.

I had rotating wallpaper images, and one came up with a large black area, along with those overlapped black window headers, it was like a whole part of the screen went black.

I think this default is easy to use, and still has the blue line on the active window.

These are subtle things for usability, but they matter, as Jobs showed.
Thanks for the tweak, though as I said, it is not only for me. There are many themes available with tweak and it is easy to change them and experiment. Greybirds were working fine.

But we want the default look to be good and have good usability. For users and picky reviewers. ;)

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 16, 2021 5:03 am
by markol
I just noticed that on Slovenian (sl_SI) localization MX Updater popup says "Na voljo je [num] posodobitev" (not replacing num with actual number of updates)

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 16, 2021 5:24 am
by fehlix
markol wrote: Sat Oct 16, 2021 5:03 am I just noticed that on Slovenian (sl_SI) localization MX Updater popup says "Na voljo je [num] posodobitev" (not replacing num with actual number of updates)
I guess someone needs to adjust the Slovenian translation on transifex
as the translations on transifex have not been made properly:

The English text: contains "{num}" in curly brackets

"You have {num} new updates avaialble"

But Slovenian translated text contains square brackets [num] within the translated plural forms
So the translation system based on gettext cannot find and substitude the placeholder "{num}" with the actual number.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 16, 2021 6:09 am
by computerworm01001
fladd wrote: Thu Oct 07, 2021 4:01 pm 5. As mentioned, archive manager has. And even since several versions of MX. There are non-Gnome3 alternatives available, such as Xarchiver. One of those alternatives should be the default. It would add a lot for a consistent desktop.
I second the motion to use xarchiver in lieu of file-roller. Xarchiver has the exact same functionality as file-roller and looks more consistent with XFCE, even with XFCE 4.16's recent half-assed attempt at CSD.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 16, 2021 7:26 am
by computerworm01001
dolphin_oracle wrote: Wed Oct 06, 2021 5:41 pm
SwampRabbit wrote: Wed Oct 06, 2021 5:39 pm
dreamer wrote: Wed Oct 06, 2021 4:45 pm Just use libxfce4ui-nocsd like everyone else. Even SwampRabbit posted a screenshot showing libxfce4ui-nocsd so I don't know why he pretends it doesn't exist.

viewtopic.php?p=653087#p653087
https://imgur.com/a/pwJO0Pb

I explained it here so everyone (including MX devs) would understand how easy it is to turn off CSDs in Xfce 4.16 without any bugs or side effects. Sigh.
viewtopic.php?p=652602#p652602
:turtle:
Cool it! Did I say or pretend it doesn't exist? No I did not, no one has. The post of mine that you are linking to has nothing to do with CSD or no CSD... we were talking about Docklike Taskbar.

As already stated by dolphin, myself, and many other people since the Betas... the whole thing is flaky.... there's like 90 different nocsd implementations spread across the universe right now.

You know how to get it to perfectly work perfectly on MX... please explain to us dummies again and show us exactly how "everyone else" does it then... prove it works without any issues in any way on MX 21.

Right now we're working tons of different so called "easy" things for this RC .... we don't need no roundabout snide attitudes. I won't stand for this childish nonsense, noCSD can shove it for all I personally care, and I won't touch anything related to it until people grow up. Don't type my screen name... don't talk about the dev team or the community... RAWR! :soapbox:
I dont pretend it doesn't exist either, it just doesn't actually do what we wanted as it only affects Xfce apps that use libxfce4ui. but more power to you, it is an option.
Hello dolphin_oracle, SwampRabbit, dreamer, and everyone else this may concern. I know that this is a very emotionally charged topic, and I'm not trying to reignite any fires here. I simply want to let you all in on my experience with gtk3-nocsd, which I understand to have been the noCSD default for the previous iterations of MX-21. Here is a link to a couple of screenshots: https://postimg.cc/gallery/NFj3hVB (I tried to attach them, but they were too large).

Both of these were shot on the same day, with the most up-to-date software per the respective distro repos. The first image shows XFCE 4.16 with gtk3-nocsd in Artix (Arch-based linux without systemd components).The second image shows XFCE 4.16 with gtk3-nocsd in MX-21-beta2. As you can see, gtk3-nocsd works perfectly in Artix, but abysmally in MX-21. So I think that maybe the problem is in Debian's packaging of gtk3-nocsd. It may not be much of a clue to work on, however, I very much hope this helps you in some way.

I strongly believe that we should have the option to turn off CSD in XFCE, especially since the XFCE devs did such a (in my opinion) half-assed job of implementing CSD. Why did they have to do it? XFCE was perfectly fine without this feature. And if they absolutely felt that they must do it, why didn't they do it for all of the XFCE apps, instead of giving CSD to the System Settings dialogs, and ignoring the rest? Or they could have added a toggle themselves to give users the choice to use CSD or not use it. The current iteration of XFCE-CSD is almost as messy as Windows 10's mishmash of UWP and Win32 apps. Why, why, why did they have to do it???

Okay, so that went a bit beyond just sharing my experience, and veered into the realm of opinion. I'm sorry, MX devs. I know none of this is your fault. You're just doing the best you can with the mess that the XFCE devs have made. I'm sorry you have to deal with complaints and arguments about this. As always, I have nothing but love and respect for dolphin_oracle, Adrian, SwampRabbit, and all the rest of the MX devs. Thank you for all you do for us, the MX users. I need to get some sleep now, so I will post my more extensive review of MX-21-RC1 several hours from now.

Kind regards,
computerworm01001

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 16, 2021 8:12 am
by hebelwirkung
computerworm01001 wrote: Sat Oct 16, 2021 7:26 am
dolphin_oracle wrote: Wed Oct 06, 2021 5:41 pm
SwampRabbit wrote: Wed Oct 06, 2021 5:39 pm

Cool it! Did I say or pretend it doesn't exist? No I did not, no one has. The post of mine that you are linking to has nothing to do with CSD or no CSD... we were talking about Docklike Taskbar.

As already stated by dolphin, myself, and many other people since the Betas... the whole thing is flaky.... there's like 90 different nocsd implementations spread across the universe right now.

You know how to get it to perfectly work perfectly on MX... please explain to us dummies again and show us exactly how "everyone else" does it then... prove it works without any issues in any way on MX 21.

Right now we're working tons of different so called "easy" things for this RC .... we don't need no roundabout snide attitudes. I won't stand for this childish nonsense, noCSD can shove it for all I personally care, and I won't touch anything related to it until people grow up. Don't type my screen name... don't talk about the dev team or the community... RAWR! :soapbox:
I dont pretend it doesn't exist either, it just doesn't actually do what we wanted as it only affects Xfce apps that use libxfce4ui. but more power to you, it is an option.
Hello dolphin_oracle, SwampRabbit, dreamer, and everyone else this may concern. I know that this is a very emotionally charged topic, and I'm not trying to reignite any fires here. I simply want to let you all in on my experience with gtk3-nocsd, which I understand to have been the noCSD default for the previous iterations of MX-21. Here is a link to a couple of screenshots: https://postimg.cc/gallery/NFj3hVB (I tried to attach them, but they were too large).

Both of these were shot on the same day, with the most up-to-date software per the respective distro repos. The first image shows XFCE 4.16 with gtk3-nocsd in Artix (Arch-based linux without systemd components).The second image shows XFCE 4.16 with gtk3-nocsd in MX-21-beta2. As you can see, gtk3-nocsd works perfectly in Artix, but abysmally in MX-21. So I think that maybe the problem is in Debian's packaging of gtk3-nocsd. It may not be much of a clue to work on, however, I very much hope this helps you in some way.

I strongly believe that we should have the option to turn off CSD in XFCE, especially since the XFCE devs did such a (in my opinion) half-assed job of implementing CSD. Why did they have to do it? XFCE was perfectly fine without this feature. And if they absolutely felt that they must do it, why didn't they do it for all of the XFCE apps, instead of giving CSD to the System Settings dialogs, and ignoring the rest? Or they could have added a toggle themselves to give users the choice to use CSD or not use it. The current iteration of XFCE-CSD is almost as messy as Windows 10's mishmash of UWP and Win32 apps. Why, why, why did they have to do it???

Okay, so that went a bit beyond just sharing my experience, and veered into the realm of opinion. I'm sorry, MX devs. I know none of this is your fault. You're just doing the best you can with the mess that the XFCE devs have made. I'm sorry you have to deal with complaints and arguments about this. As always, I have nothing but love and respect for dolphin_oracle, Adrian, SwampRabbit, and all the rest of the MX devs. Thank you for all you do for us, the MX users. I need to get some sleep now, so I will post my more extensive review of MX-21-RC1 several hours from now.

Kind regards,
computerworm01001
computerworm01001 wrote: Sat Oct 16, 2021 7:26 am
dolphin_oracle wrote: Wed Oct 06, 2021 5:41 pm
SwampRabbit wrote: Wed Oct 06, 2021 5:39 pm

Cool it! Did I say or pretend it doesn't exist? No I did not, no one has. The post of mine that you are linking to has nothing to do with CSD or no CSD... we were talking about Docklike Taskbar.

As already stated by dolphin, myself, and many other people since the Betas... the whole thing is flaky.... there's like 90 different nocsd implementations spread across the universe right now.

You know how to get it to perfectly work perfectly on MX... please explain to us dummies again and show us exactly how "everyone else" does it then... prove it works without any issues in any way on MX 21.

Right now we're working tons of different so called "easy" things for this RC .... we don't need no roundabout snide attitudes. I won't stand for this childish nonsense, noCSD can shove it for all I personally care, and I won't touch anything related to it until people grow up. Don't type my screen name... don't talk about the dev team or the community... RAWR! :soapbox:
I dont pretend it doesn't exist either, it just doesn't actually do what we wanted as it only affects Xfce apps that use libxfce4ui. but more power to you, it is an option.
Hello dolphin_oracle, SwampRabbit, dreamer, and everyone else this may concern. I know that this is a very emotionally charged topic, and I'm not trying to reignite any fires here. I simply want to let you all in on my experience with gtk3-nocsd, which I understand to have been the noCSD default for the previous iterations of MX-21. Here is a link to a couple of screenshots: https://postimg.cc/gallery/NFj3hVB (I tried to attach them, but they were too large).

Both of these were shot on the same day, with the most up-to-date software per the respective distro repos. The first image shows XFCE 4.16 with gtk3-nocsd in Artix (Arch-based linux without systemd components).The second image shows XFCE 4.16 with gtk3-nocsd in MX-21-beta2. As you can see, gtk3-nocsd works perfectly in Artix, but abysmally in MX-21. So I think that maybe the problem is in Debian's packaging of gtk3-nocsd. It may not be much of a clue to work on, however, I very much hope this helps you in some way.

I strongly believe that we should have the option to turn off CSD in XFCE, especially since the XFCE devs did such a (in my opinion) half-assed job of implementing CSD. Why did they have to do it? XFCE was perfectly fine without this feature. And if they absolutely felt that they must do it, why didn't they do it for all of the XFCE apps, instead of giving CSD to the System Settings dialogs, and ignoring the rest? Or they could have added a toggle themselves to give users the choice to use CSD or not use it. The current iteration of XFCE-CSD is almost as messy as Windows 10's mishmash of UWP and Win32 apps. Why, why, why did they have to do it???

Okay, so that went a bit beyond just sharing my experience, and veered into the realm of opinion. I'm sorry, MX devs. I know none of this is your fault. You're just doing the best you can with the mess that the XFCE devs have made. I'm sorry you have to deal with complaints and arguments about this. As always, I have nothing but love and respect for dolphin_oracle, Adrian, SwampRabbit, and all the rest of the MX devs. Thank you for all you do for us, the MX users. I need to get some sleep now, so I will post my more extensive review of MX-21-RC1 several hours from now.

Kind regards,
computerworm01001
The option to turn off CSD would be very welcome. I've read elsewhere that this apparently would be difficult to implement and, not having a clue about how these things are programmed, there's nothing useful I can say on that. I wish though a toggle were possible. I can sort of live with the esthetic aspects of it. What does annoy me is that windows using CSD can no longer be rolled up, which is a feature I use frequently. Now obviously, most of this is just a question of getting used to and retraining the hand not to resort to gestures one's become so used to. And some design decisions in XFCE 16 I quite like, for example the way they've made changes to the "save file as" dialogue.

That said, I agree with @computerworm01001 that I can't see a convincing answer to the question of why they made those changes in the first place. It feels like they got all excited over the gnome antics but decided half way through that it wasn't worth pursuing.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 16, 2021 2:08 pm
by SwampRabbit
@entropyfoe you're welcome and you are absolutely right, it needs some refinement. I actually changed all 4 themes and made some minor nitpicking adjustments. I'd like to work on them more in the future, but we'll see.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 16, 2021 2:27 pm
by SwampRabbit
@computerworm01001 and @hebelwirkung the ability to use gtk3-nocsd still exists, you just have to install it yourself, I believe the toggle then shows up in MX Tweak. But when you do this you take responsibility to all the issues that arise with it such as this one viewtopic.php?p=655928#p655928

Its not like this feedback is being ignored, but right now there are bigger priorities than fixing workarounds for workarounds.

In fact, these things are better addressed at the root of the concern so that a good long term solution, rather than workarounds that constantly need attention. Which it actually looks like people are taking notice where they should, case in point ... https://forum.xfce.org/viewtopic.php?pid=64476#p64476 and here https://gitlab.xfce.org/xfce/libxfce4ui ... note_38517. MX Linux isn't going to change Xfce as a whole, but our users can voice their opinion where it matters, at the Xfce level.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 16, 2021 4:15 pm
by hebelwirkung
SwampRabbit wrote: Sat Oct 16, 2021 2:27 pm @computerworm01001 and @hebelwirkung the ability to use gtk3-nocsd still exists, you just have to install it yourself, I believe the toggle then shows up in MX Tweak. But when you do this you take responsibility to all the issues that arise with it such as this one viewtopic.php?p=655928#p655928

Its not like this feedback is being ignored, but right now there are bigger priorities than fixing workarounds for workarounds.

In fact, these things are better addressed at the root of the concern so that a good long term solution, rather than workarounds that constantly need attention. Which it actually looks like people are taking notice where they should, case in point ... https://forum.xfce.org/viewtopic.php?pid=64476#p64476 and here https://gitlab.xfce.org/xfce/libxfce4ui ... note_38517. MX Linux isn't going to change Xfce as a whole, but our users can voice their opinion where it matters, at the Xfce level.
Yes, I'd read about gtk3-nocsd causing a variety of problems in 21, which is why I won't be installing it. And of course I understand this is an XFCE thing, not one created by MX, so my remarks weren't meant to be critical of MX. And let's face it, it's not a deal breaker by any stretch of the imagination, especially in a distro like MX which has so much good stuff to offer. And anyone who can't live with XFCE 4.16 can of course stay with MX 19 for three more years by which time, judging from the XFCE forum you provided the links for, they may well have added that opt out toggle anyway.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 16, 2021 4:28 pm
by figueroa
I've read the continuing saga of CSD and have even posted here about it when I couldn't find the option to turn it off, which was much appreciated early on. Given that the nocsd options are work-arounds that cause problems, I've decided it's time for me to move on and live with CSD when running XFCE on the desktop. It's baked into the pie. Why ask for problems.

I have a suggestion. Users wanting a more traditional no CSD option desktop, even lighter, and competent, might consider installing LXDE via MXPI. It's a very small DE, usable out-of-the-box, and easy to configure and make quite beautiful. I use it under 19.4, betas, and RC1 and vouch for its goodness.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 16, 2021 5:37 pm
by computerworm01001
SwampRabbit wrote: Sat Oct 16, 2021 2:27 pm @computerworm01001 and @hebelwirkung the ability to use gtk3-nocsd still exists, you just have to install it yourself, I believe the toggle then shows up in MX Tweak. But when you do this you take responsibility to all the issues that arise with it such as this one viewtopic.php?p=655928#p655928

Its not like this feedback is being ignored, but right now there are bigger priorities than fixing workarounds for workarounds.

In fact, these things are better addressed at the root of the concern so that a good long term solution, rather than workarounds that constantly need attention. Which it actually looks like people are taking notice where they should, case in point ... https://forum.xfce.org/viewtopic.php?pid=64476#p64476 and here https://gitlab.xfce.org/xfce/libxfce4ui ... note_38517. MX Linux isn't going to change Xfce as a whole, but our users can voice their opinion where it matters, at the Xfce level.
Yeah, I was aware the option still exists. I tried manually installing it in RC1, and it still made everything look weird, so I decided not to use it, same as I decided in beta2 after trying it. Truthfully, the only time it draws my notice or bothers me at all is when I open the System Settings window or any of the Settings dialogs. However, when it does bother me, it bothers me a LOT. :mad:

Nevertheless, I understand and respect your reasons for not making it a priority to fix, because in the grand scheme of things, it truly is not a critical bug. I can make my peace with it if I continue to use XFCE, or I may just switch to Cinnamon (which has always been my favorite desktop, regardless of XFCE's relationship with CSD). I'm aware that KDE has similar functionality to Cinnamon, and is officially supported by MX; I tried it and found a lot to love. Unfortunately, KDE Wallet doesn't work with Protonmail-Bridge, gnome-keyring is to hard to make work in KDE, and pass has to be manually unlocked after every login. Therefore, KDE is not a viable option for me right now. :sad:

Once again, thank you for your good work, and for reading and considering our feedback. :yay:

Re: MX-21 RC1 feedback (Xfce)

Posted: Sat Oct 16, 2021 11:04 pm
by computerworm01001
figueroa wrote: Sat Oct 16, 2021 4:28 pm I've read the continuing saga of CSD and have even posted here about it when I couldn't find the option to turn it off, which was much appreciated early on. Given that the nocsd options are work-arounds that cause problems, I've decided it's time for me to move on and live with CSD when running XFCE on the desktop. It's baked into the pie. Why ask for problems.

I have a suggestion. Users wanting a more traditional no CSD option desktop, even lighter, and competent, might consider installing LXDE via MXPI. It's a very small DE, usable out-of-the-box, and easy to configure and make quite beautiful. I use it under 19.4, betas, and RC1 and vouch for its goodness.
I actually tried LXDE last year on MX-19.4 because I was curious. It definitely lived up to its reputation for lightness, however I found it to be a bit too bare-bones. I especially missed having a comprehensive Settings Manager. Of course, MX Tools picked up a little of the slack, but it's not a complete stand-in, as it was designed to be used in concert with XFCE Settings Manager, not on its own. However, I might give it another chance. And I'm certain that other users will find it to be a perfect (or at least close to perfect) substitute for XFCE. Thank you for the suggestion, @figueroa . :smile:

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 17, 2021 1:41 am
by Rodney
MX Linux XFCE RC1

Looks fabulous, love the icons, wallpapers and theme, I am using MX Comfort Dark.

Fast, uses 6% memory, roughly 600 Mb's and just 1% CPU on boot.

All my favourite programs installed fine along with NVIDIA drivers.

The software I like to use - Firefox, Asunder, Sound Converter DeadBeef, Gimp, DarkTable, Rapid Photo Downloader, Steam, Lutris, Chromium BSU, 0AD, Gnome Chess and Mahjong. Most are the latest versions.

Safe after using Firewall Configuration, Full Stealth @ https://www.grc.com/shieldsup

Did I say It looks good, beautiful, fantastic effort from the Developers, Thank You.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 17, 2021 8:39 pm
by Somewhat Reticent
computerworm01001 wrote: Sat Oct 16, 2021 11:04 pm… LXDE a bit too bare-bones… MX Tools picked up a little of the slack, but it's not a complete stand-in, as it was designed to be used in concert with XFCE Settings Manager
Many parts of the XFCE DE work well with others.

Imagine a DE composed of a window-manager and a collection of independent utilities, all free of complications compromising-conveniences like gtk/qt. (sigh) If only.

Re: MX-21 RC1 feedback (Xfce)

Posted: Sun Oct 17, 2021 9:19 pm
by SwampRabbit
Somewhat Reticent wrote: Sun Oct 17, 2021 8:39 pm
Many parts of the XFCE DE work well with others.

Imagine a DE composed of a window-manager and a collection of independent utilities, all free of complications compromising-conveniences like gtk/qt. (sigh) If only.
[/quote]

I think you just described MX LInux Fluxbox.

Back to feedback on the RC 1 folks.

Re: MX-21 RC1 feedback (Xfce)

Posted: Mon Oct 18, 2021 7:36 am
by Boone777
I have a little GUI bug with the installer from a live usb.
But it seems to run fine once installed.
https://i.imgur.com/0h4VaxY.png

Re: MX-21 RC1 feedback (Xfce)

Posted: Mon Oct 18, 2021 7:41 am
by anticapitalista
@Boone777 Care to tell us exactly what this gui bug is?

Re: MX-21 RC1 feedback (Xfce)

Posted: Mon Oct 18, 2021 8:04 am
by richb
Moderator

@Boone777
img tags removed. Clicking link will show image.
Images added to post via hot links from other websites will be limited to a 640 x 620 pixel size as they appear in the Forum post. Large images take up large areas of the post and thread space, are distracting and impede the flow of the thread. You can post the link to the full image without the [img] tags. Animated images, such as gifs, shall be no larger than 120 x 120 pixels.

Re: MX-21 RC1 feedback (Xfce)

Posted: Mon Oct 18, 2021 12:40 pm
by Vipul88
system info

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: H61M-CS v: Rev X.0x serial: <filter> 
           BIOS: American Megatrends v: 0503 date: 07/21/2014 
CPU:       Topology: Quad Core model: Intel Core i5-3450 bits: 64 type: MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 21 L2 cache: 6144 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 24744 
           Speed: 1787 MHz min/max: 1600/3500 MHz Core speeds (MHz): 1: 1887 2: 1923 3: 1842 
           4: 1977 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: disabled, RSB filling 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics vendor: ASUSTeK 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0152 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 2500 (IVB GT1) v: 4.2 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK P8 series driver: r8169 v: kernel port: e000 bus ID: 03:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 60.58 GiB (6.5%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: CC43 temp: 39 C scheme: MBR 
Partition: ID-1: / raw size: 131.42 GiB size: 128.29 GiB (97.62%) used: 60.58 GiB (47.2%) 
           fs: ext4 dev: /dev/sda2 
           ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda12 
           ID-3: swap-2 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda10 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
Info:      Processes: 224 Uptime: 14m Memory: 3.72 GiB used: 950.8 MiB (25.0%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
i am facing this problem for the first time after using mx 19.4, 21 beta 1 , beta 2 all worked fine except rc1.
i use mpd to run songs locally. heres my mpd.conf that was succesfully working in all these mx variants except rc1.

Code: Select all

music_directory		"~/Music"
playlist_directory	"~/.config/mpd/playlists"
bind_to_address		"~/.config/mpd/socket"
auto_update "yes"
#bind_to_address "0.0.0.0"
bind_to_address "any"
restore_paused "yes"
max_output_buffer_size "16384"

audio_output {
	type "pulse"
	name "pulse"
	#type  "alsa"
	#name  "ALSA"
}

audio_output {
       type	"fifo"
       name	"Visualizer feed"
       path	"/tmp/mpd.fifo"
       format	"44100:16:2"
}
it worked in previous mx variants in the following manner. after every login i have to run this command everytime.

Code: Select all

 sudo pkill mpd && mpd -v
 
however in rc1,
here's the output of

Code: Select all

sudo pkill mpd && mpd -v

Code: Select all

config_file: loading file /home/primavipul/.config/mpd/mpd.conf
exception: bind to '[::]:6600' failed (continuing anyway, because binding to '/home/primavipul/.config/mpd/socket' succeeded): Failed to bind socket: Address already in use
exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '/home/primavipul/.config/mpd/socket' succeeded): Failed to bind socket: Address already in use
libsamplerate: libsamplerate converter 'Fastest Sinc Interpolator'
vorbis: Xiph.Org libVorbis 1.3.7
opus: libopus 1.3.1
sndfile: libsndfile-1.0.31
hybrid_dsd: The Hybrid DSD decoder is disabled because it was not explicitly enabled
exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
adplug: adplug 2.3.3
simple_db: reading DB
exception: Input plugin 'tidal' is not configured: No Tidal application token configured
exception: Input plugin 'qobuz' is not configured: No Qobuz app_id configured
curl: version 7.74.0
curl: with GnuTLS/3.7.1
now mpd daemon is running succesfully. and i am out of clues as to what is casuing this problem.
output of

Code: Select all

netstat -tlnp | grep 6600
is

Code: Select all

tcp6       0      0 :::6600                 :::*                    LISTEN      -                 
the main problem i am facing is. mpd -v after killing mpd when done previously and then if i ran ncmpcpp then i could see the songs after pressing 2 in ncmpcpp.
the things i have done in order to solve it but didnt solve it for me.
1. restarting the mpd service.
2. changing the address to 0.0.0.0.
3. reinstalling mpd and repeating 1 & 2.

Re: MX-21 RC1 feedback (Xfce)

Posted: Tue Oct 19, 2021 4:58 am
by Boone777
anticapitalista wrote: Mon Oct 18, 2021 7:41 am @Boone777 Care to tell us exactly what this gui bug is?
Doted or blured lines in the installer. Maybe it is meant to be that way but I don't think so. Same thing on both laptop and pc. At the very least it feels awkward, undefined separation between different disks and partitions.
The dropdown menu for selecting root partition blends with the rest it looks like it is already part of the board. Not sure how to explain but maybe it's just me.

https://i.imgur.com/0h4VaxY.png?1

Re: MX-21 RC1 feedback (Xfce)

Posted: Tue Oct 19, 2021 10:33 am
by Stuart_M
Boone777 wrote: Tue Oct 19, 2021 4:58 am Doted or blured lines in the installer. ...it feels awkward, undefined separation between different disks and partitions.
The dropdown menu for selecting root partition blends with the rest it looks like it is already part of the board. ...
I completely agree. I think it makes the MX-21 installer (mx-installer 21.10.09) drive/partition table look absolutely awful (I'm being generous). The installer looked much, much better before those weird lines appeared.

MX-19 had a MUCH better looking installer in v21.7.02mx19, and that version does NOT show the Live USB Flash Drive as another drive, which is the way it should be in my opinion (key word in this statement is "had").

Unfortunately, sometime after v21.7.02 that awful look made its way into the latest MX-19 installer (21.10.04mx19 as of this posting).

To get a better understanding of what I am talking about, look at the screenshots of the three mx-installers mentioned above. All the screenshots are using the Template for an Encrypted installation at their default settings. I also removed the installer "help" column on the left side of the installer window in order to expand the main window for a more simple display.

MX-21_RC1 mx-installer 21.10.09 (newest MX-21 installer)
MX-21_mx-installer_21.10.09.png


MX-19.4 mx-installer 21.7.02mx19 (installer included with the MX-19.4 15July2021 (downloaded) snapshot)
There is a Live MX-19.4 USB Flash Drive connected for the installation and notice that this drive (sdb) is absent in this window, which is good (in my opinion)
MX-19_mx-installer_21.7.02mx19.png


MX-19.4 mx-installer 21.10.04mx19 (newest MX-19 installer) - it got worse...
MX-19_mx-installer_21.10.04mx19.png


Edit: All three screenshots were made with the installer seeing the same 250GB unformatted SSD.

To the credit of the newer installers, the correct partition size for sda3 is displayed (224.1 GB) as well as displaying it in gigabytes vice megabytes whereas the older installer (21.7.02) shows an incorrect sda3 size of 229483 MB which is impossible when sda4 adds an additional 8.192 GB when there is only 232.9 GB available. And it still using megabytes vice gigabytes. So the newer installers are better overall.

Re: MX-21 RC1 feedback (Xfce)

Posted: Wed Oct 20, 2021 9:39 am
by Paul..
Curious why the installer has flagged the partition of MX-21 RC1 as "legacy_boot"?
Perhaps something I missed on the installer screen?

https://imgur.com/4QM6RrS.png


Otherwise, all is well with the installation...BTW, I am running AHS but that was applied after the install...and I did not want to confuse the situation.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 2606 date: 08/13/2020 
CPU:       Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 
           family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701021 
           L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 114991 
           Speed: 2196 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2196 
           2: 2196 3: 2196 4: 2196 5: 2203 6: 2195 7: 2196 8: 2189 9: 2196 10: 2196 11: 2196 
           12: 2196 13: 2189 14: 2196 15: 2196 16: 2196 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: ASUSTeK 
           driver: amdgpu v: kernel bus ID: 09:00.0 chip ID: 1002:731f 
           Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,radeon,vesa resolution: 2560x1440~144Hz 
           OpenGL: 
           renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.40.0 5.10.0-9-amd64 LLVM 12.0.1) 
           v: 4.6 Mesa 21.2.2 direct render: Yes 
Audio:     Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus ID: 09:00.1 
           chip ID: 1002:ab38 
           Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 0b:00.4 chip ID: 1022:1487 
           Device-3: Logitech Logitech Webcam C925e type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 1-2:3 chip ID: 046d:085b serial: <filter> 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: f000 
           bus ID: 03:00.0 chip ID: 8086:1539 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 931.52 GiB used: 198.34 GiB (21.3%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 4B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
Partition: ID-1: / raw size: 218.97 GiB size: 214.48 GiB (97.95%) used: 7.11 GiB (3.3%) fs: ext4 
           dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 63.1 C mobo: N/A gpu: amdgpu temp: 54 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
           2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
Info:      Processes: 357 Uptime: 7m Memory: 15.60 GiB used: 1.06 GiB (6.8%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 


Moderator: image changed to link, see forum rules for maximum size (640x620)

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 21, 2021 2:49 am
by Vipul88
Vipul88 wrote: Mon Oct 18, 2021 12:40 pm system info

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: H61M-CS v: Rev X.0x serial: <filter> 
           BIOS: American Megatrends v: 0503 date: 07/21/2014 
CPU:       Topology: Quad Core model: Intel Core i5-3450 bits: 64 type: MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 21 L2 cache: 6144 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 24744 
           Speed: 1787 MHz min/max: 1600/3500 MHz Core speeds (MHz): 1: 1887 2: 1923 3: 1842 
           4: 1977 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: disabled, RSB filling 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics vendor: ASUSTeK 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0152 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 2500 (IVB GT1) v: 4.2 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK P8 series driver: r8169 v: kernel port: e000 bus ID: 03:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 60.58 GiB (6.5%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: CC43 temp: 39 C scheme: MBR 
Partition: ID-1: / raw size: 131.42 GiB size: 128.29 GiB (97.62%) used: 60.58 GiB (47.2%) 
           fs: ext4 dev: /dev/sda2 
           ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda12 
           ID-3: swap-2 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda10 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
Info:      Processes: 224 Uptime: 14m Memory: 3.72 GiB used: 950.8 MiB (25.0%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
i am facing this problem for the first time after using mx 19.4, 21 beta 1 , beta 2 all worked fine except rc1.
i use mpd to run songs locally. heres my mpd.conf that was succesfully working in all these mx variants except rc1.

Code: Select all

music_directory		"~/Music"
playlist_directory	"~/.config/mpd/playlists"
bind_to_address		"~/.config/mpd/socket"
auto_update "yes"
#bind_to_address "0.0.0.0"
bind_to_address "any"
restore_paused "yes"
max_output_buffer_size "16384"

audio_output {
	type "pulse"
	name "pulse"
	#type  "alsa"
	#name  "ALSA"
}

audio_output {
       type	"fifo"
       name	"Visualizer feed"
       path	"/tmp/mpd.fifo"
       format	"44100:16:2"
}
it worked in previous mx variants in the following manner. after every login i have to run this command everytime.

Code: Select all

 sudo pkill mpd && mpd -v
 
however in rc1,
here's the output of

Code: Select all

sudo pkill mpd && mpd -v

Code: Select all

config_file: loading file /home/primavipul/.config/mpd/mpd.conf
exception: bind to '[::]:6600' failed (continuing anyway, because binding to '/home/primavipul/.config/mpd/socket' succeeded): Failed to bind socket: Address already in use
exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '/home/primavipul/.config/mpd/socket' succeeded): Failed to bind socket: Address already in use
libsamplerate: libsamplerate converter 'Fastest Sinc Interpolator'
vorbis: Xiph.Org libVorbis 1.3.7
opus: libopus 1.3.1
sndfile: libsndfile-1.0.31
hybrid_dsd: The Hybrid DSD decoder is disabled because it was not explicitly enabled
exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
adplug: adplug 2.3.3
simple_db: reading DB
exception: Input plugin 'tidal' is not configured: No Tidal application token configured
exception: Input plugin 'qobuz' is not configured: No Qobuz app_id configured
curl: version 7.74.0
curl: with GnuTLS/3.7.1
now mpd daemon is running succesfully. and i am out of clues as to what is casuing this problem.
output of

Code: Select all

netstat -tlnp | grep 6600
is

Code: Select all

tcp6       0      0 :::6600                 :::*                    LISTEN      -                 
the main problem i am facing is. mpd -v after killing mpd when done previously and then if i ran ncmpcpp then i could see the songs after pressing 2 in ncmpcpp.
the things i have done in order to solve it but didnt solve it for me.
1. restarting the mpd service.
2. changing the address to 0.0.0.0.
3. reinstalling mpd and repeating 1 & 2.
i dont know why or how but a reinstall solved the problem. so no need to investigate further :number1:

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 21, 2021 3:11 am
by Somewhat Reticent
Vipul88 wrote: Thu Oct 21, 2021 2:49 ami dont know why or how but a reinstall solved the problem. so no need to investigate further
Reinstall of MX21rc1, or mpd?

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 21, 2021 4:44 am
by Fritx
An Energyicon a bit smaller, as in MX19, would be nice, on occasion.

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 21, 2021 6:51 am
by markol
Fritx wrote: Thu Oct 21, 2021 4:44 am An Energyicon a bit smaller, as in MX19, would be nice, on occasion.
You can remove it from the panel and then enable (a much smaller) tray icon in Settings > Power Manager

Re: MX-21 RC1 feedback (Xfce)

Posted: Thu Oct 21, 2021 7:31 am
by Fritx
[/quote]
You can remove it from the panel and then enable (a much smaller) tray icon in Settings > Power Manager
[/quote]
I did exactly this in MX19 and it was nice. But in MX21 there is no difference.