MX Linux Forum

Posted: **Wed Jul 28, 2021 8:11 am**

announcement blog post here: https://mxlinux.org/blog/mx-21-beta-1-n ... -purposes/

Remember to post any error messages and appropriate log files (see blog post) when posting issues.

Thanks!!!!!

Posted: **Wed Jul 28, 2021 10:07 am**

Yea! , the beta is here.

And MX 21 is solidly based on a LTS kernel. A good omen for long term stability and life.

I will DL and test tonight !
Thanks to the whole dev team.

Posted: **Wed Jul 28, 2021 10:37 am**

A very quick look at a live boot. Seems quicker than MX-19. Two small items:

It's not obvious how to select en-gb at the login screen - you have to click en-us for the sub-menu.
The first thing I do is mount my 6 data partitions and add to fstab. Disk Manager seems to be missing, so it's a bit more long-winded.

I'll look in more detail tomorrow - I've had my screen time today.

One little quirk - booting back into MX-19, I had a glimpse of the wildflower wallpaper - presumably in video memory somewhere.

Posted: **Wed Jul 28, 2021 12:14 pm**

Gaer Boy wrote: Wed Jul 28, 2021 10:37 am A very quick look at a live boot. Seems quicker than MX-19. Two small items:

It's not obvious how to select en-gb at the login screen - you have to click en-us for the sub-menu.
The first thing I do is mount my 6 data partitions and add to fstab. Disk Manager seems to be missing, so it's a bit more long-winded.

I'll look in more detail tomorrow - I've had my screen time today.

One little quirk - booting back into MX-19, I had a glimpse of the wildflower wallpaper - presumably in video memory somewhere.

disk manager is no longer maintained as its python2. you might try gnome-disks for a gui that can edit fstab.

Posted: **Wed Jul 28, 2021 12:32 pm**

Gaer Boy wrote: Wed Jul 28, 2021 10:37 am A very quick look at a live boot. Seems quicker than MX-19. Two small items:

It's not obvious how to select en-gb at the login screen - you have to click en-us for the sub-menu.

In the main menu:

live-grub-main.png

after selecting Language-Keyboad-Timezone:

lkt.png

it shows the live-system pre-selected default settings, which are the one if you do not chose another one of those defaults and boot straight from the first menu entry. Submenus for languages are for those where multiple regional languages like French, Spanish, German or English:

en_RR.png

are available to select from.

Posted: **Wed Jul 28, 2021 12:52 pm**

Thanks, @fehlix, I found it quickly enough but it's counter-intuitive on the second screen to click lang=en_us to get to a screen to set lang=en_GB.

Posted: **Wed Jul 28, 2021 1:02 pm**

As a fast test into a VM.
MX21 beta look nice (the nice WildFlowers)
Nice to have the Kernel: 5.10.0-8-amd64 x86_64 bits too.

Code: Select all

root@mx1:/home/demo# inxi -zv8
System:    Host: mx1 Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: lang=fr_FR quiet splasht nosplash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: N/A 
           Chassis: Oracle Corporation type: 1 serial: N/A 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: N/A BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
Memory:    RAM: total: 2.92 GiB used: 1.20 GiB (41.2%) 
           RAM Report: message: No RAM data was found. 
PCI Slots: Message: No PCI slot data found. 
CPU:       Topology: Triple Core model: Intel Core i5-2320 bits: 64 type: MCP arch: Sandy Bridge 
           family: 6 model-id: 2A (42) stepping: 7 microcode: N/A L2 cache: 6144 KiB 
           bogomips: 17958 
           Speed: 2993 MHz min/max: N/A Core speeds (MHz): 1: 2993 2: 2993 3: 2993 
           Flags: aes apic avx clflush cmov constant_tsc cpuid cx16 cx8 de flush_l1d fpu fxsr ht 
           hypervisor lahf_lm lm mca mce md_clear mmx msr mtrr nonstop_tsc nopl nx pae pat 
           pclmulqdq pge pni popcnt pse pse36 pti rdtscp rep_good sep sse sse2 sse4_1 sse4_2 
           ssse3 syscall tsc tsc_known_freq vme x2apic xsave xtopology 
           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: 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: 967x699~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> 
           IP v4: <filter> type: dynamic noprefixroute scope: global broadcast: <filter> 
           IP v6: <filter> type: dynamic noprefixroute scope: global 
           IP v6: <filter> type: noprefixroute scope: link 
           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 
           WAN IP: No WAN IP data found. Connected to the web? SSL issues? 
Drives:    Local Storage: total: N/A used: 507.1 MiB 
           Optical-1: /dev/sr0 vendor: VBOX model: CD-ROM rev: 1.0  dev-links: cdrom,dvd 
           Features: speed: 32 multisession: yes audio: yes dvd: yes rw: none state: running 
RAID:      Message: No RAID data was found. 
Partition: ID-1: / raw size: N/A size: 2.29 GiB used: 507.1 MiB (21.6%) fs: overlay 
           source: ERR-102 label: N/A uuid: N/A 
           ID-2: /live/linux raw size: 1.63 GiB size: N/A (hidden?) used: N/A (hidden?) 
           fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A 
Unmounted: Message: No unmounted partitions found. 
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 12 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
           Device-1: 1-1:2 info: VirtualBox USB Tablet type: HID driver: hid-generic,usbhid 
           interfaces: 1 rev: 1.1 speed: 12 Mb/s chip ID: 80ee:0021 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 12 rev: 2.0 speed: 480 Mb/s 
           chip ID: 1d6b:0002 
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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Processes: CPU top: 5 
           1: cpu: 24.4% command: firefox pid: 28944 mem: 387.9 MiB (12.9%) 
           2: cpu: 4.6% command: firefox-bin pid: 29310 mem: 124.2 MiB (4.1%) 
           3: cpu: 4.4% command: xorg pid: 3117 mem: 93.8 MiB (3.1%) 
           4: cpu: 3.3% command: synaptic pid: 4649 mem: 173.4 MiB (5.8%) 
           5: cpu: 1.6% command: firefox-bin pid: 29257 mem: 124.8 MiB (4.1%) 
           Memory top: 5 
           1: mem: 387.9 MiB (12.9%) command: firefox pid: 28944 cpu: 24.4% 
           2: mem: 173.4 MiB (5.8%) command: synaptic pid: 4649 cpu: 3.3% 
           3: mem: 129.4 MiB (4.3%) command: firefox-bin pid: 29172 cpu: 0.9% 
           4: mem: 124.8 MiB (4.1%) command: firefox-bin pid: 29257 cpu: 1.6% 
           5: mem: 124.2 MiB (4.1%) command: firefox-bin pid: 29310 cpu: 4.6% 
Info:      Processes: 197 Uptime: 14m Init: SysVinit v: 2.96 runlevel: 5 default: 5 Compilers: 
           gcc: 10.2.1 alt: 10 Shell: bash (su) v: 5.1.4 running in: xfce4-terminal inxi: 3.0.36 
root@mx1:/home/demo#

... But neofetch say Debian GNU/Linux 11 (bullseye) x86_64 instead MX21

Code: Select all

neofetch
root@mx1:/home/demo# neofetch --off
demo@mx1 
-------- 
OS: Debian GNU/Linux 11 (bullseye) x86_64 
Host: VirtualBox 1.2 
Kernel: 5.10.0-8-amd64 
Uptime: 16 mins 
Packages: 1967 (dpkg) 
Shell: bash 5.1.4 
Resolution: 967x699 
DE: Xfce 4.16 
WM: Xfwm4 
Theme: Adwaita [GTK3] 
Icons: Adwaita [GTK3] 
Terminal: xfce4-terminal 
Terminal Font: Liberation Mono 11 
CPU: Intel i5-2320 (3) @ 2.993GHz 
GPU: 00:02.0 VMware SVGA II Adapter 
Memory: 1665MiB / 2987MiB

PS: I liked disk-manager too into MX19 (more than gnome-disk)

Posted: **Wed Jul 28, 2021 2:34 pm**

oops wrote: Wed Jul 28, 2021 1:02 pm ... But neofetch say Debian GNU/Linux 11 (bullseye) x86_64 instead MX21

Would this help :

Code: Select all

sudo sed -i.orig  '/type -p lsb_release/,/distro=/s:^:#:' $(which neofetch)

which gives here as text:

Code: Select all

neofetch
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMNMMMMMMMMM   demo@mx1 
MMMMMMMMMMNs..yMMMMMMMMMMMMMm: +NMMMMMMM   -------- 
MMMMMMMMMN+    :mMMMMMMMMMNo` -dMMMMMMMM   OS: MX 21 Wildflower x86_64 
MMMMMMMMMMMs.   `oNMMMMMMh- `sNMMMMMMMMM   Host: KVM/QEMU (Standard PC (i440FX + PIIX, 1996) pc-i44 
MMMMMMMMMMMMN/    -hMMMN+  :dMMMMMMMMMMM   Kernel: 5.10.0-8-amd64 
MMMMMMMMMMMMMMh-    +ms. .sMMMMMMMMMMMMM   Uptime: 15 mins 
MMMMMMMMMMMMMMMN+`   `  +NMMMMMMMMMMMMMM   Packages: 1967 (dpkg) 
MMMMMMMMMMMMMMNMMd:    .dMMMMMMMMMMMMMMM   Shell: bash 5.1.4 
MMMMMMMMMMMMm/-hMd-     `sNMMMMMMMMMMMMM   Resolution: 1366x768 
MMMMMMMMMMNo`   -` :h/    -dMMMMMMMMMMMM   DE: Xfce 4.16 
MMMMMMMMMd:       /NMMh-   `+NMMMMMMMMMM   WM: Xfwm4 
MMMMMMMNo`         :mMMN+`   `-hMMMMMMMM   WM Theme: Matcha-azul 
MMMMMMh.            `oNMMd:    `/mMMMMMM   Theme: Matcha-azul [GTK2], Adwaita [GTK3] 
MMMMm/                -hMd-      `sNMMMM   Icons: Papirus-mxblue [GTK2], Adwaita [GTK3] 
MMNs`                   -          :dMMM   Terminal: xfce4-terminal 
Mm:                                 `oMM   Terminal Font: Liberation Mono 11 
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM   CPU: Intel Xeon E3-1240 V2 (4) @ 3.403GHz 
                                           GPU: 00:04.0 Red Hat, Inc. QXL paravirtual graphic card 
                                           Memory: 2306MiB / 11973MiB

or screen dumped:

MX21-noefetch.jpg

Posted: **Wed Jul 28, 2021 2:36 pm**

Gaer Boy wrote: Wed Jul 28, 2021 12:52 pm Thanks, @fehlix, I found it quickly enough but it's counter-intuitive on the second screen to click lang=en_us to get to a screen to set lang=en_GB.

Yes, and do think on all other languages, where the defaults are indicating just this.

Posted: **Wed Jul 28, 2021 2:38 pm**

we actually had a patched neofetch under mx19. forgot about that, will add to the list.

Posted: **Wed Jul 28, 2021 2:56 pm**

Gaer Boy wrote: Wed Jul 28, 2021 12:52 pm it's counter-intuitive on the second screen to click lang=en_us to get to a screen to set lang=en_GB.

I thought so too at first, but after selecting lang=en_NZ, I found the correct timezone was auto-selected too, so the 1 extra step saved 2 more. This is a big step forward.

Posted: **Wed Jul 28, 2021 3:28 pm**

64 bit beta 1: Running ISO directly from VirtualBox giving it 4 GB RAM; loaded VERY fast. Small update went fine. Look and feel too dark for my tastes, but is easily adjusted. Kernel log and dmesg look unusually clean. Appears to be much higher quality than most Beta 1 releases.

Does this matter?

Code: Select all

vboxguest: module verification failed: signature and/or required key missing - tainting kernel

Guest module is loaded and working as expected.

From MXPI, installing the Simple Card Games fails at Hearts (gnome-games hearts). That was just a test. I don't care about games. Nothing was installed. Installed Evince, and went fine.

CSD has become especially ugly. That's not an MX bug, but I feel compelled to mention it. Others may note what one has little control over what the window decorations look like in the XFCE packages and think it's a bug.

Currently making Live-usb with MX Live USB Maker from within the "updated" VirtualBox running ISO on a slow and troublesome flash drive. Will note if and when anything else notable is found.

ADDED: "live-usb-maker took 12 minutes and 45 seconds." Not bad from VirtualBox onto a crumby, know-to-be-slow USB 2.0 flash drive.

Posted: **Wed Jul 28, 2021 3:47 pm**

Running on an old FX-6300 system. Using BIOS boot / MBR partitioning, install wizard complained partition table invalid (it's not) but ran through anyway after I manually formatted a partition for it. Picked up other Linux and Windows partitions and added them to GRUB, no problem.

Nvidia drivers installed OK on second attempt; first one failed when downloading packages was interrupted. This seems to happen to me with anything Debian-based though, it can download 500MB of files and choke on the last 128KB and the whole thing bombs out (we don't all have fast fibre!)

Changed wallpaper to something in my own files, but on reboot it resets to the default.

The fact that action buttons no longer stack in panel in deskbar mode is a pain, but I know this is an XFCE 4.16 "feature", I've had a change request in to them for months to allow the buttons to stack the way they used to.

quick-system-info for reference:

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_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: M5A88-M EVO v: Rev X.0x serial: <filter> 
           BIOS: American Megatrends v: 1901 date: 11/27/2014 
CPU:       Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer 
           family: 15 (21) model-id: 2 stepping: N/A microcode: 6000852 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 41993 
           Speed: 1399 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 1398 
           2: 1399 3: 1399 4: 1399 5: 1621 6: 1835 
           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: Gigabyte driver: nvidia 
           v: 460.73.01 bus ID: 01:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.11 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 460.73.01 
           direct render: Yes 
Audio:     Device-1: AMD SBx00 Azalia vendor: ASUSTeK M5A88-V EVO driver: snd_hda_intel 
           v: kernel bus ID: 00:14.2 chip ID: 1002:4383 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: Gigabyte driver: snd_hda_intel 
           v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK P8P67 and other motherboards driver: r8169 v: kernel port: e800 
           bus ID: 03:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 2.28 TiB used: 6.57 GiB (0.3%) 
           ID-1: /dev/sda vendor: SK Hynix model: HFS250G32TND-3110A size: 232.89 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 0P00 
           scheme: MBR 
           ID-2: /dev/sdb vendor: Seagate model: ST2000DM001-1CH164 size: 1.82 TiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: CC46 scheme: MBR 
           ID-3: /dev/sdc vendor: SK Hynix model: SH920 mSATA 256GB size: 238.47 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 4L00 scheme: MBR 
Partition: ID-1: / raw size: 38.00 GiB size: 37.11 GiB (97.65%) used: 6.57 GiB (17.7%) fs: ext4 
           dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 30.0 C mobo: 25.0 C gpu: nvidia temp: 37 C 
           Fan Speeds (RPM): cpu: 1207 psu: 0 case-1: 1057 gpu: nvidia fan: 0% 
           Voltages: 12v: 12.03 5v: N/A 3.3v: 3.31 vbat: 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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 231 Uptime: 7m Memory: 15.63 GiB used: 1.49 GiB (9.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

Posted: **Wed Jul 28, 2021 3:48 pm**

figueroa wrote: Wed Jul 28, 2021 3:28 pm CSD has become especially ugly. That's not an MX bug, but I feel compelled to mention it. Others may note what one has little control over what the window decorations look like in the XFCE packages and think it's a bug.

I guess its because it just got released, but everyone is just scratching the surface of the things in MX-21 Beta 1.

Check out MX Tweak > Other tab... there's something there to try out.
Although IMHO this "tweak" makes things look worse.

No more hints now

Posted: **Wed Jul 28, 2021 5:20 pm**

figueroa wrote: Wed Jul 28, 2021 3:28 pm CSD has become especially ugly. That's not an MX bug, but I feel compelled to mention it. Others may note what one has little control over what the window decorations look like in the XFCE packages and think it's a bug.

I'm not sure if this is the same thing but Linux Mint 20.2 was release recently with Xfce 4.16 and now has problems with CSD font colors.

https://forums.linuxmint.com/viewtopic. ... 7&t=352656

At least you can change it using a gtk.css file. Might be something MX devs would want to look at.

Posted: **Wed Jul 28, 2021 5:37 pm**

@BV206 please stick to feedback for known/confirmed issues or dislikes on/for the MX-21 Beta1

Edited for clarity... is isn't an CSD opinion thread or thread about things affecting other Distros. Its for those testing the MX-21 Beta1.

Posted: **Wed Jul 28, 2021 6:25 pm**

SwampRabbit wrote: Wed Jul 28, 2021 5:37 pm @BV206 please stick to feedback for known/confirmed issues or dislikes on/for the MX-21 Beta1

Edited for clarity... is isn't an CSD opinion thread or thread about things affecting other Distros. Its for those testing the MX-21 Beta1.

I just made a MX 21 USB to check.

On most themes the CSD title bar font has no color difference between focused and unfocused windows. You can't tell if the window has focus or not. In addition to that on the Arc (light) theme the whole CSD title bar is semi-transparent whether or not the window has focus.

Are those not problems that should be reported during beta testing?

Posted: **Wed Jul 28, 2021 6:34 pm**

BV206 wrote: Wed Jul 28, 2021 6:25 pm
SwampRabbit wrote: Wed Jul 28, 2021 5:37 pm @BV206 please stick to feedback for known/confirmed issues or dislikes on/for the MX-21 Beta1

Edited for clarity... is isn't an CSD opinion thread or thread about things affecting other Distros. Its for those testing the MX-21 Beta1.
I just made a MX 21 USB to check.

On most themes the CSD title bar font has no color difference between focused and unfocused windows. You can't tell if the window has focus or not. In addition to that on the Arc (light) theme the whole CSD title bar is semi-transparent whether or not the window has focus.

Are those not problems that should be reported during beta testing?

you can report them. although the only theme in our set that didn't look like any change at all happened between active and inactive was blackbird (is that even a default? I got so much stuff installed right now I'm not sure TBH).

Arc having a semi-transparent background is just how its built. Not liking the style is not a bug. You will also note its not our default anymore. but we will consider theme reports same as any other.

there is a switch in mx-tweak to disable csd decorations, but its not going to change things like the theme elements, although you will/should get window manager theme elements instead of the gtk theme ones. testing on that switch is another area that we would be obliged on.

Posted: **Wed Jul 28, 2021 6:51 pm**

BV206 wrote: Wed Jul 28, 2021 6:25 pm I just made a MX 21 USB to check.

...

On most themes the CSD title bar font has no color difference between focused and unfocused windows. You can't tell if the window has focus or not. In addition to that on the Arc (light) theme the whole CSD title bar is semi-transparent whether or not the window has focus.

Are those not problems that should be reported during beta testing?

When you actually test, for sure, was your first post before or after actually testing? We just don't need people posting opinions and not actually testing.

The focus is noticeable in my opinion between the focused and unfocused although I can say the difference between some of the styles the focus is not as drastic as could be (see screenshot)

Matcha - kinda had to see the difference, but its there https://i.imgur.com/6qgLhJf.png

Greybird-dark-mx - much better https://i.imgur.com/2rJAvDH.png

Greybird-mx - same as with the dark variant https://i.imgur.com/qxWbrKn.png

Posted: **Wed Jul 28, 2021 7:02 pm**

MX-21 beta 1 is a "no-go" for me.

I downloaded the ISO, confirmed a good download with .sha256 file and made a Live Flash Drive using MX Live USB Maker in the "Full-featured mode...".

I booted up the MX-21 beta 1 Live USB Flash Drive just fine in UEFI mode with CSM disabled.

I ran the installer (21.7.04) and the installation failed at the "Installing GRUB" 95% point with the error "GRUB installation failed. You can reboot to the live medium and use the GRUB Rescue menu to repair the installation". That cannot be done because the installation does not finish - clicking "OK" on the error message simply returns the installer to the beginning of the installation process, aborting the installation.

This is almost the identical problem I detailed in my Post #3 viewtopic.php?p=644796#p644796 "GRUB does not install in EFI with CSM enabled in the BIOS" (dated 19 July 2021) but with a twist - the thread I created was about the problem that occurred ONLY with CSM enabled; with CSM disabled (pure UEFI mode) the installation completed error free and without any problems.

I said it is "almost" the identical problem because now, MX-21 will not install in UEFI mode regardless of CSM being enabled or disabled. The same error message at 95% as detailed in the above link results, so installing in UEFI mode is not an option.

However, I am able to install MX-21 beta 1 in Legacy (BIOS) mode with CSM enabled, of course.

It is interesting to note that MX-21 beta 1 is using mx-installer 21.7.04 that fails to install in UEFI mode while MX-19.4 successfully installs in UEFI mode (with CSM disabled) using mx-installer 21.7.02.

Attached is the minstall.log as copied from the MX-21 beta 1 Live Flash Drive. The error occurs at the same point as identified in the above link, this time on line 550 which is shown in the below code window.

Code: Select all

2021-07-28 18:00:30.285 DBG default: SErr #163: "Installing for x86_64-efi platform.\ngrub-install: warning: Cannot set EFI variable Boot0000.\ngrub-install: warning: efivarfs_set_variable: writing to fd 7 failed: No space left on device.\ngrub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: No space left on device.\ngrub-install: error: failed to register the EFI boot entry: No space left on device.\n"

minstall.log

Posted: **Wed Jul 28, 2021 7:08 pm**

I see a "No space left on device" in the error...

Posted: **Wed Jul 28, 2021 7:25 pm**

Yes, and I believe the answer to that was given here viewtopic.php?p=644875#p644875 which is Post #10 from the same link which identifies the problem more thoroughly, and is where I marked it "SOLVED" on that thread. Post #6 directly above that post also gives some more information that seems to identify part of the reason for the error.

I do not believe the "No space" is referring to the 250GB SSD I am writing to, which is a completely blank and unallocated SSD (that successfully installs in Legacy/BIOS mode).

The problem occurrs regardless of the installation being a custom or a regular/standard installation (with root and home on the same partition).

Posted: **Wed Jul 28, 2021 7:32 pm**

Stuart_M wrote: Wed Jul 28, 2021 7:02 pm

Code: Select all

2021-07-28 18:00:30.285 DBG default: SErr #163: "
Installing for x86_64-efi platform.
grub-install: warning: Cannot set EFI variable Boot0000.
grub-install: warning: efivarfs_set_variable: writing to fd 7 failed: No space left on device.
grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: No space left on device.
grub-install: error: failed to register the EFI boot entry: No space left on device.\n"

Seem some NVRAM space issues
Is the efifarfs mounted at /sys/firmware/efi/efivars
Do you have "dump"- entries in there, which might be some leftover from olded NVRAM entries not used anymore and not cleared:

Code: Select all

ls -l1 /sys/firmware/efi/efivars/dump*

If yes, can you remove unneeded ones:

Code: Select all

sudo rm  /sys/firmware/efi/efivars/dump*

Posted: **Wed Jul 28, 2021 9:11 pm**

fehlix wrote: Wed Jul 28, 2021 7:32 pm Do you have "dump"- entries in there, which might be some leftover from olded NVRAM entries not used anymore and not cleared:
Code: Select all
ls -l1 /sys/firmware/efi/efivars/dump*
If yes, can you remove unneeded ones:
Code: Select all
sudo rm  /sys/firmware/efi/efivars/dump*

That worked - THANKS!

This is exactly what I did:

1. Booted the MX-21 beta1 Live Flash Drive with my MSI B450-A PRO MAX motherboard in pure UEFI mode (CSM disabled).
2. Ran the installer and installed GRUB in EFI for booting up in UEFI mode.
3. The installer stopped at "Installing GRUB" at 95% (as usual) with the same error.
4. I aborted the installer.
5. I ran the ls -l1 /sys/firmware/efi/efivars/dump* command which produced the following 157 lines of text:

Code: Select all

$ ls -l1 /sys/firmware/efi/efivars/dump*
-rw-r--r-- 1 root root 668 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-10-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 450 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-10-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 806 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-10-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 754 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-10-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 837 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-10-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 587 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-10-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 759 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-10-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 572 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-10-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 862 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-10-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 820 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-11-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 922 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-11-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 670 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-11-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 579 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-11-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 710 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-11-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 925 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-11-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 589 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-11-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 930 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-11-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 740 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-11-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 910 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-1-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 911 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-1-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 903 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-1-1-1596730522-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 899 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-1-1-1597321956-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 894 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-1-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 903 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-1-1-1597684435-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 897 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-1-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 905 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-1-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 906 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-1-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 902 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-1-1-1597957531-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 696 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-12-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 711 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-12-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 649 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-12-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 814 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-12-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 636 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-12-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 697 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-12-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 805 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-12-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 692 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-12-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 620 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-12-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 668 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-13-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 585 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-13-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 792 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-13-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 534 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-13-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 785 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-13-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 559 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-13-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 531 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-13-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 556 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-13-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 798 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-13-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 740 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-14-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 744 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-14-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 506 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-14-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 472 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-14-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 446 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-14-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 783 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-14-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 498 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-14-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 803 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-14-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 519 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-14-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 344 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-14-1-1626307085-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 459 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-15-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 640 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-15-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 505 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-15-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 684 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-15-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 628 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-15-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 598 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-15-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 684 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-15-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 562 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-15-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 466 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-15-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 626 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-16-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 427 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-16-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 726 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-16-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 591 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-16-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 708 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-16-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 457 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-16-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 593 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-16-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 506 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-16-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 703 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-16-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 693 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-17-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 647 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-17-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 536 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-17-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 701 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-17-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 636 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-17-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 701 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-17-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 863 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-2-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 870 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-2-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 864 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-2-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 888 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-2-1-1597321956-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 889 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-2-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 868 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-2-1-1597684435-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 883 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-2-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 886 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-2-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 866 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-2-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 868 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-2-1-1597957532-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 585 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-3-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 728 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-3-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 684 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-3-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 714 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-3-1-1597321956-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 748 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-3-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 668 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-3-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 699 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-3-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 733 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-3-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 665 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-3-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 707 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-3-1-1597957532-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 639 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-4-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 643 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-4-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 676 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-4-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 749 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-4-1-1597321956-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 678 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-4-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 545 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-4-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 709 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-4-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 628 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-4-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 819 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-4-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 711 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-4-1-1597957532-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 715 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-5-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 712 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-5-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 612 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-5-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 459 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-5-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 580 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-5-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 739 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-5-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 516 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-5-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 651 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-5-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 617 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-5-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 509 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-5-1-1597957532-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 619 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-6-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 759 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-6-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 345 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-6-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 331 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-6-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 336 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-6-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 760 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-6-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 346 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-6-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 714 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-6-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 400 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-6-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 428 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-6-1-1597957532-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 339 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-7-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 347 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-7-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 346 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-7-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 452 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-7-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 339 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-7-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 338 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-7-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 444 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-7-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 526 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-7-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 330 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-7-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 331 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-8-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 351 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-8-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 464 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-8-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 496 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-8-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 534 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-8-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 333 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-8-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 494 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-8-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 354 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-8-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 433 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-8-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 538 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-9-1-1596492903-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 467 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-9-1-1596637231-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 661 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-9-1-1596730523-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 795 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-9-1-1597321958-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 621 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-9-1-1597331785-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 488 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-9-1-1597684438-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 713 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-9-1-1597779152-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 351 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-9-1-1597783268-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0
-rw-r--r-- 1 root root 605 Jul 28 20:29 /sys/firmware/efi/efivars/dump-type0-9-1-1597957439-C-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0

6. I ran the sudo rm /sys/firmware/efi/efivars/dump* command which did not produce an output.
7. I ran Step 5 ls command again but this time it only had this one line of output:

Code: Select all

ls: cannot access '/sys/firmware/efi/efivars/dump*': Invalid argument

8. With MX-21 still booted up in UEFI mode and CSM disabled, I once again ran the installer on a blank (unallocated) 250GB SSD, selecting EFI (UEFI) as the bootup mode, identical to every previous unsuccessful MX-21 UEFI installation attempt. This time the installation completed successfully and flawlessly.

Edit: Based on the time for each of the "dump" entries, every one was created on the last unsuccessful installation attempt from Step 3 above.

Posted: **Wed Jul 28, 2021 10:34 pm**

SwampRabbit wrote: Wed Jul 28, 2021 3:48 pm
figueroa wrote: Wed Jul 28, 2021 3:28 pm CSD has become especially ugly. That's not an MX bug, but I feel compelled to mention it. Others may note what one has little control over what the window decorations look like in the XFCE packages and think it's a bug.
I guess its because it just got released, but everyone is just scratching the surface of the things in MX-21 Beta 1.

Check out MX Tweak > Other tab... there's something there to try out.
Although IMHO this "tweak" makes things look worse.

No more hints now

Awesome. Great NEW feature that delivers what it promises. With a few additional theme and appearance tweaks, I was able to tune it up to be very pleasant to my eye.

Posted: **Wed Jul 28, 2021 10:44 pm**

interesting.... turn off the csd in mx-tweak also removes the transparency from arc theme, at least for the panel and title bars. color me corrected

Posted: **Wed Jul 28, 2021 10:51 pm**

Have they resumed maintaining arc theme or is the fork now official? www.omgubuntu.co.uk/2020/03/arc-theme-fork/amp

If the version in Debian repos is the original one, that might be another reason it might be wonky on newer gtk3 versions?

Posted: **Thu Jul 29, 2021 1:03 am**

Wow, this is looking good so far.
I downloaded the 64 bit, md5 was good, so burned to USB with the MXLive USBMaker.

That USB booted quickly about 45 seconds to a desktop with a connection and panel.
The sound card selector worked in MX tools, and the sound worked when the generic card was selected.
Internet worked, youtube etc, videos played no problems in the newest firefox 90.0.2.
It suspends and wakes up. All good so ....Install in my testing partition.

No problems with the installer, I could figure it out, I reused nvme0n1p4, and formated to ext4 the 88G partition. A five minute install, installed GRUB to the root.
Rebotted to the existing MX 19.4 to do an update-grub as root, and the new install was found.
So I rebooted into the new MX 21.

All seems fast. Here is the QSI

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_beta1_x64 Wildflower July 27  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: 91032 
           Speed: 2195 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2196 
           2: 2195 3: 2196 4: 2196 5: 2196 6: 2196 7: 2196 8: 2196 9: 2195 10: 2195 11: 2196 
           12: 2195 
           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.73.01 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.73.01 
           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: 537.01 GiB (46.1%) 
           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: 6.55 GiB (7.6%) 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: 44.2 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
           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
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 287 Uptime: 12m Memory: 31.34 GiB used: 1.62 GiB (5.2%) 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 as mentioned by earlier testers do miss the Disk Manager in MX19.
I tried to get d_O's suggestion of gnome-disks, but that was not in synaptic.
So, alas I had to edit fstab manually to access my 1TB data disk. (I cloned the fstab line from the MX-19 installation)
From there I can access my wallpaper collection to change the desktop.

All working like a normal MX release. So, I installed the nvidia driver with the MX tool.
After a reboot, the nvidia 460.73.01-1 is indeed installed.

Installed the usual packages (125 including all the dependencies)
So far no problems or bugs spotted. So easy, I will keep using it as the daily driver.

I am used to using my root PW. But this is using the sudo convention...how can I change that back to the usual root model?
I recommend that some disk manager is included in the iso. I almost forgot how to edit the fstab, the gui tool is so easy.

Posted: **Thu Jul 29, 2021 1:16 am**

entropyfoe wrote: Thu Jul 29, 2021 1:03 am I am used to using my root PW. But this is using the sudo convention...how can I change that back to the usual root model?
I recommend that some disk manager is included in the iso. I almost forgot how to edit the fstab, the gui tool is so easy.

MX Tweak > Other tab > radial button at the bottom labeled accordingly.

I think your looking for gnome-disk-utility ... its there are installed on my end. Let us know if that is good enough, it seems like a small install.

Does anyone have suggestions would be nice for a replacement easy to use disk manager that is reputable, stable, and maintained well?

Posted: **Thu Jul 29, 2021 5:16 am**

fehlix wrote: Wed Jul 28, 2021 2:34 pm

oops wrote: Wed Jul 28, 2021 1:02 pm ... But neofetch says Debian GNU/Linux 11 (bullseye) x86_64 instead MX21

Would this help :

Code: Select all

sudo sed -i.orig  '/type -p lsb_release/,/distro=/s:^:#:' $(which neofetch)

which gives here as text:

Code: Select all

neofetch
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMNMMMMMMMMM   demo@mx1 
MMMMMMMMMMNs..yMMMMMMMMMMMMMm: +NMMMMMMM   -------- 
MMMMMMMMMN+    :mMMMMMMMMMNo` -dMMMMMMMM   OS: MX 21 Wildflower x86_64 
MMMMMMMMMMMs.   `oNMMMMMMh- `sNMMMMMMMMM   Host: KVM/QEMU (Standard PC (i440FX + PIIX, 1996) pc-i44 
MMMMMMMMMMMMN/    -hMMMN+  :dMMMMMMMMMMM   Kernel: 5.10.0-8-amd64 
MMMMMMMMMMMMMMh-    +ms. .sMMMMMMMMMMMMM   Uptime: 15 mins 
MMMMMMMMMMMMMMMN+`   `  +NMMMMMMMMMMMMMM   Packages: 1967 (dpkg) 
MMMMMMMMMMMMMMNMMd:    .dMMMMMMMMMMMMMMM   Shell: bash 5.1.4 
MMMMMMMMMMMMm/-hMd-     `sNMMMMMMMMMMMMM   Resolution: 1366x768 
MMMMMMMMMMNo`   -` :h/    -dMMMMMMMMMMMM   DE: Xfce 4.16 
MMMMMMMMMd:       /NMMh-   `+NMMMMMMMMMM   WM: Xfwm4 
MMMMMMMNo`         :mMMN+`   `-hMMMMMMMM   WM Theme: Matcha-azul 
MMMMMMh.            `oNMMd:    `/mMMMMMM   Theme: Matcha-azul [GTK2], Adwaita [GTK3] 
MMMMm/                -hMd-      `sNMMMM   Icons: Papirus-mxblue [GTK2], Adwaita [GTK3] 
MMNs`                   -          :dMMM   Terminal: xfce4-terminal 
Mm:                                 `oMM   Terminal Font: Liberation Mono 11 
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM   CPU: Intel Xeon E3-1240 V2 (4) @ 3.403GHz 
                                           GPU: 00:04.0 Red Hat, Inc. QXL paravirtual graphic card 
                                           Memory: 2306MiB / 11973MiB

Hello and thank you Fehlix ... it's much better with this logo ;-)
But I see above, than dolphin_oracle already has a workaround: "we actually had a patched neofetch under mx19. forgot about that, will add to the list."

Posted: **Thu Jul 29, 2021 6:05 am**

SwampRabbit wrote: Thu Jul 29, 2021 1:16 am I think your looking for gnome-disk-utility ... its there are installed on my end. Let us know if that is good enough, it seems like a small install.

Does anyone have suggestions would be nice for a replacement easy to use disk manager that is reputable, stable, and maintained well?

I installed gnome-disk-utility and it will do the job. It is much more cumbersome than disk manager on my setup. I have switched authentication to root, which I much prefer, and gdu requires 2 authentications to mount each partition and add an entry to fstab. Disk manager just required authorisation to open. GDU also mounts to /mnt by default and identifies the partition in Thunar by UUID, which is not helpful. Getting it to mount as /media/label needs a number of adjustments to the mount options. I also don't like the fact that there are 3 action buttons for a partition - mount, delete, additional options. That's a cockeyed place to put a delete partition button - thankfully it does give a confirmation message.

In short, gnome-disk-utility will do if nothing better can be found but disk manager is sorely missed.

Posted: **Thu Jul 29, 2021 10:50 am**

Gaer Boy wrote: Thu Jul 29, 2021 6:05 am In short, gnome-disk-utility will do if nothing better can be found but disk manager is sorely missed.

I wholeheartedly agree my friend, sadly the developer decided to no get it ported to python3, not even sure myself if they tried or decided to abandon it. I can look later.

Posted: **Thu Jul 29, 2021 11:03 am**

SwampRabbit wrote: Thu Jul 29, 2021 10:50 am
Gaer Boy wrote: Thu Jul 29, 2021 6:05 am In short, gnome-disk-utility will do if nothing better can be found but disk manager is sorely missed.
I wholeheartedly agree my friend, sadly the developer decided to no get it ported to python3, not even sure myself if they tried or decided to abandon it. I can look later.

he abandoned it. we adopted it, but the migration is beyond my non-existant python skills.

source is here. this would be a good one to get in if someone can take it over. https://github.com/MX-Linux/disk-manager

Posted: **Thu Jul 29, 2021 11:52 am**

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_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASRock model: FM2A88X-ITX+ serial: <filter> 
           UEFI: American Megatrends v: P2.10 date: 01/17/2014 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K270 serial: <filter> 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M185 serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: Quad Core model: AMD A8-6500 APU with Radeon HD Graphics bits: 64 type: MCP 
           arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 microcode: 6001119 
           L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 27946 
           Speed: 1938 MHz min/max: 1700/3500 MHz boost: enabled Core speeds (MHz): 1: 1761 
           2: 1951 3: 1855 4: 1997 
           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: AMD Richland [Radeon HD 8570D] vendor: ASRock driver: radeon v: kernel 
           bus ID: 00:01.0 chip ID: 1002:990e 
           Display: x11 server: X.Org 1.20.11 driver: ati,radeon 
           unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.10.0-8-amd64 LLVM 11.0.1) 
           v: 4.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes 
Audio:     Device-1: AMD Trinity HDMI Audio vendor: ASRock driver: snd_hda_intel v: kernel 
           bus ID: 00:01.1 chip ID: 1002:9902 
           Device-2: AMD FCH Azalia vendor: ASRock driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1022:780d 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: AzureWave 
           driver: ath9k v: kernel port: f100 bus ID: 01:00.0 chip ID: 168c:0034 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros QCA8171 Gigabit Ethernet vendor: ASRock driver: alx 
           v: kernel port: e000 bus ID: 03:00.0 chip ID: 1969:10a1 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 2.05 TiB used: 176.36 GiB (8.4%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Seagate model: ST1000DM005 HD103SJ size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: 00E5 scheme: MBR 
           ID-3: /dev/sdc vendor: Toshiba model: HDWD110 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: A8J0 scheme: MBR 
Partition: ID-1: / raw size: 30.00 GiB size: 29.36 GiB (97.87%) used: 7.66 GiB (26.1%) fs: ext4 
           dev: /dev/sda4 
           ID-2: swap-1 size: 7.81 GiB used: 268 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sdb11 
Sensors:   System Temperatures: cpu: 15.9 C mobo: N/A gpu: radeon temp: 13 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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 229 Uptime: 3h 48m Memory: 6.71 GiB used: 1.47 GiB (21.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

I'm very impressed with the Beta - it's as stable and fault-free as my MX-19 install. I have more or less fleshed it out to my usual standard and found few faults. The following items have been installed, mainly via MX Package Manager:

Gnome-disk-utility, Vivaldi, KMyMoney (+110 packages) Quodlibet, Gwenview, Audacity, Calibre, Inkscape, Shotwell, MuseScore 3, MasterPDF Editor 4, VirtualBox. I was surprised that I also had to install gscan2pdf.

Almost all seem to work as expected. My HP X451DW was installed automatically, although I still have to change the default paper size to A4. I had 3 problems:

I use 2 alternative profiles in Thunderbird, both stored on my data partition. I edit profiles.ini to access them and have to use thunderbird --ProfileManager in the terminal for the first start. This gave me an error, which doesn't seem to affect operation:

tbird error.png

My virtual XP wouldn't use the existing machine file. The error message showed that the data partition was mounted at /mnt instead of /media. This despite taking care in gnome-disk-utility. Easily corrected, but I would love to have disk manager back.

vbox-error.png

My Epson scanner is only detected by sane-find-scanner run as root. As user, it returns:

Code: Select all

$ sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

could not open USB device 0x1d6b/0x0001 at 009:001: Access denied (insufficient permissions)
found USB scanner (vendor=0x03f0 [HP], product=0xaa11 [HP Officejet Pro X451dw Printer]) at libusb:003:002
could not open USB device 0x1d6b/0x0002 at 003:001: Access denied (insufficient permissions)
could not open USB device 0x13d3/0x3393 at 008:003: Access denied (insufficient permissions)
could not open USB device 0x046d/0xc52b at 008:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 008:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 005:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0003 at 007:001: Access denied (insufficient permissions)
could not open USB device 0x04b8/0x013a at 006:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 006:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0003 at 004:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 002:001: Access denied (insufficient permissions)
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

It's at 006:002. This lack of permission for the USB devices is probably also the reason why I can't access printer or scanner in VirtualBox. I haven't had this problem in other versions.

My only major criticism is one of appearance, which is often a matter of personal preference. I find almost everything too faint and indistinguishable. I don't usually make many changes to themes, fonts, etc, but it will certainly be necessary with this version. The extreme case is LibreOffice, where the icons are virtually invisible.

libreoffice display.png

That's the sum total of my problems. If it wasn't for the display issue, I would be happy to use this Beta as my daily system. I doubt I could say that about any other distro. Congratulations and thanks to the whole Development Team.

Phil

Posted: **Thu Jul 29, 2021 11:58 am**

One small item I forgot. I turn off all window snapping, rollover, etc. I want my windows to go and stay where I put them! I've stopped most of the irritating behaviour but one feature eludes me. When a window touches the top of the screen (only), it maximises. I've failed to stop this - help would be welcome.

Posted: **Thu Jul 29, 2021 12:02 pm**

I wonder if the LibreOffice needs a different set of icons for "light" themes.

Posted: **Thu Jul 29, 2021 12:02 pm**

Gaer Boy wrote: Thu Jul 29, 2021 11:58 am One small item I forgot. I turn off all window snapping, rollover, etc. I want my windows to go and stay where I put them! I've stopped most of the irritating behaviour but one feature eludes me. When a window touches the top of the screen (only), it maximises. I've failed to stop this - help would be welcome.

window manager tweaks, accessbility tab, there is a tiling option.

Posted: **Thu Jul 29, 2021 12:11 pm**

Thanks, D-O. I would never had connected that description.

Posted: **Thu Jul 29, 2021 12:18 pm**

Gaer Boy wrote: Thu Jul 29, 2021 12:11 pm Thanks, D-O. I would never had connected that description.

no worries @Gaer Boy thanks for all the feedback!

on the libreoffice theme issue, did you reuse a libreoffice config from your home folder by any chance? this is what the writer looks like by default on the live media.

Posted: **Thu Jul 29, 2021 12:37 pm**

No - as far as I remember, that's the appearance on first opening. I looked at a setting or two but changed nothing. I usually alter many of the locations from /home to my data partition but I haven't tried any of that yet.

Posted: **Thu Jul 29, 2021 12:56 pm**

The package installer failed (three times) when trying to use it by double clicking on a .deb install package downloaded from the web. There was nothing wrong with the package since it did successfully install from the command line with "sudo apt install code_1.58.2-1626302803_amd64.deb". The binary I was installing was the latest visual studio code.
The package installer gui would load and did indicate that all dependencies were met. When 'install' was clicked, the process would just silently fail. Since I do not know where to look for possible error logs, I cannot provide one for you.

Posted: **Thu Jul 29, 2021 12:59 pm**

@Gaer Boy you've changed the icons LibreOffice is using somehow, you can tell from comparing your pic to the one d.o. just shared.
It looks like you have Breeze Dark set. I checked and OOTB it's fine.

Can you go to Tools> Options > LibreOffice - View > Icon style to "Automatic (Colibre)

Posted: **Thu Jul 29, 2021 1:01 pm**

grg wrote: Thu Jul 29, 2021 12:56 pm The package installer failed (three times) when trying to use it by double clicking on a .deb install package downloaded from the web. There was nothing wrong with the package since it did successfully install from the command line with "sudo apt install code_1.58.2-1626302803_amd64.deb". The binary I was installing was the latest visual studio code.
The package installer gui would load and did indicate that all dependencies were met. When 'install' was clicked, the process would just silently fail. Since I do not know where to look for possible error logs, I cannot provide one for you.

Please provide a link to where you got this .deb.

There does seem to be an issue with the pkexec and gdebi-gtk when doubleclicking on a .deb file, but running it manually in a terminal works.

I've been installing .debs for weeks on all our internal Alphas and Betas without issue by Right Clicking and selecting "Install Deb Files" ... so that can be used in the meantime if someone needs it.

Have you tried using MX Package Installer (MXPI) > Popular Applications > Development?
I just tried it, it installs the exact version without issue.

Edit: don't need a link to the .deb, just install VSCode using MXPI, installing .debs via right click menu, something is up with GDebi though

Posted: **Thu Jul 29, 2021 1:06 pm**

grg wrote: Thu Jul 29, 2021 12:56 pm The package installer failed (three times) when trying to use it by double clicking on a .deb install package downloaded from the web. There was nothing wrong with the package since it did successfully install from the command line with "sudo apt install code_1.58.2-1626302803_amd64.deb". The binary I was installing was the latest visual studio code.
The package installer gui would load and did indicate that all dependencies were met. When 'install' was clicked, the process would just silently fail. Since I do not know where to look for possible error logs, I cannot provide one for you.

thank you. I presume you mean "gdebi" when you say package installer.

Posted: **Thu Jul 29, 2021 1:08 pm**

@dolphin_oracle please see my edit above, yep its a gdebi issue but only seems an issue when double clicking a .deb file

Posted: **Thu Jul 29, 2021 1:13 pm**

SwampRabbit wrote: Thu Jul 29, 2021 1:08 pm @dolphin_oracle please see my edit above, yep its a gdebi issue but only seems an issue when double clicking a .deb file

ok thanks.

I hate gdebi...

Posted: **Thu Jul 29, 2021 1:16 pm**

dolphin_oracle wrote: Thu Jul 29, 2021 11:03 amWe adopted it, but the migration is beyond my non-existant python skills.
source is here. this would be a good one to get in if someone can take it over. https://github.com/MX-Linux/disk-manager

Not only would it need to be ported to python3 but to Gtk3/GIO (or Qt5) from Gtk2 since bullseye doesn't have python3-gtk.
The pure python parts look pretty easy to fix (without digging too far into it - there could always be a hidden monster) - the GUI parts not so easy.

Posted: **Thu Jul 29, 2021 1:47 pm**

WARNING:

I was installing the beta to test it. With the new way of organising partitions, I thought I'd see what happened if I set a partition other than that which I was installing on, to something like /mnt/otherdistro and the type to "preserve". The next screen advised me that, indeed, the partition would be mounted at /mnt/otherdistro and the partition would not be formatted. So, I went back, added a partition which has all my data on at /mnt/Data to be preserved. Which the next screen assured me was going to happen. Guess what? All my data has been wiped! (and the partition wasn't even mounted!) My fault for not backing it up, but to save anyone else from testing that feature I'm posting this here. I will double post at the forum on this occasion because it's important.

Posted: **Thu Jul 29, 2021 1:49 pm**

davemx wrote: Thu Jul 29, 2021 1:47 pm WARNING:

I was installing the beta to test it. With the new way of organising partitions, I thought I'd see what happened if I set a partition other than that which I was installing on, to something like /mnt/otherdistro and the type to "preserve". The next screen advised me that, indeed, the partition would be mounted at /mnt/otherdistro and the partition would not be formatted. So, I went back, added a partition which has all my data on at /mnt/Data to be preserved. Which the next screen assured me was going to happen. Guess what? All my data has been wiped! (and the partition wasn't even mounted!) My fault for not backing it up, but to save anyone else from testing that feature I'm posting this here. I will double post at the forum on this occasion because it's important.

we need your /var/log/minstall.log please. it will have been copied to the installed system.

Posted: **Thu Jul 29, 2021 2:02 pm**

dolphin_oracle wrote: Thu Jul 29, 2021 1:49 pm

we need your /var/log/minstall.log please. it will have been copied to the installed system.

Can't help with that. I initially thought that the problem was elsewhere so I installed another Linux over it in a vain attempt to get access to my other partitions. I didn't realise that they were empty!

Posted: **Thu Jul 29, 2021 2:10 pm**

@all - if you have precious data, do NOT install a beta release. Wait until it is released as final.

Posted: **Thu Jul 29, 2021 2:14 pm**

SwampRabbit wrote: Thu Jul 29, 2021 12:59 pm @Gaer Boy you've changed the icons LibreOffice is using somehow, you can tell from comparing your pic to the one d.o. just shared.
It looks like you have Breeze Dark set. I checked and OOTB it's fine.

Can you go to Tools> Options > LibreOffice - View > Icon style to "Automatic (Colibre)

Confirmed that I have the Breeze Dark, but I didn't change it. That was how it was. I'll try the change tomorrow - I'm back in MX-19 for today because I don't have my backup routines set in MX-21 yet.

Posted: **Thu Jul 29, 2021 2:21 pm**

Megasync won't install from MX Package Installer, says "megasync : Depends: libraw19 (>= 0.16.0) but it is not installable". Downloaded the deb file for Debian testing from Mega.nz, open with gdebi which says it will install dependencies, but it just bombs out with no error. Tried installing with dpkg, again complains about dependencies, but apt-get -f install fixed it. Version 4.5.3 now running OK.

No alias for python - it's good that python3 is the default now, but I've struggled to remember to type python3 rather than just python for years!

Posted: **Thu Jul 29, 2021 3:34 pm**

MX Date & Time>Network Time tab - there are no network servers in the list.

Chris

Posted: **Thu Jul 29, 2021 3:43 pm**

There is an entry in the Whisker menu - conky - that starts a second basic Conky on the top-left of the screen. Is that by accident? If intentional, what is its purpose?

Chris

Posted: **Thu Jul 29, 2021 3:55 pm**

ARandR opens with the menu bar squashed, so you can't close it.

Chris

Posted: **Thu Jul 29, 2021 3:56 pm**

chrispop99 wrote: Thu Jul 29, 2021 3:43 pm There is an entry in the Whisker menu - conky - that starts a second basic Conky on the top-left of the screen. Is that by accident? If intentional, what is its purpose?

Chris

well color me surprised, conky is packaged with a desktop file now. didn't catch that earlier...

Posted: **Thu Jul 29, 2021 3:59 pm**

chrispop99 wrote: Thu Jul 29, 2021 3:55 pm ARandR opens with the menu bar squashed, so you can't close it.

Chris

Alt+F4 should, but I'll take a look.

Posted: **Thu Jul 29, 2021 4:00 pm**

Jerry3904 wrote: Thu Jul 29, 2021 3:59 pm
chrispop99 wrote: Thu Jul 29, 2021 3:55 pm ARandR opens with the menu bar squashed, so you can't close it.

Chris
Alt+F4 should, but I'll take a look.

Indeed it does.

Chris

Posted: **Thu Jul 29, 2021 4:01 pm**

... Tried again MX-21 beta 1, and the .iso is fast to decompress and to load on VM (faster than MX19) ... is this iso is compressed with zstd?

Posted: **Thu Jul 29, 2021 4:07 pm**

oops wrote: Thu Jul 29, 2021 4:01 pm ... Tried again MX-21 beta 1, and the .iso is fast to decompress and to load on VM (faster than MX19) ... is this iso is compressed with zstd?

yes

Posted: **Thu Jul 29, 2021 4:08 pm**

chrispop99 wrote: Thu Jul 29, 2021 4:00 pm
Jerry3904 wrote: Thu Jul 29, 2021 3:59 pm
chrispop99 wrote: Thu Jul 29, 2021 3:55 pm ARandR opens with the menu bar squashed, so you can't close it.

Chris
Alt+F4 should, but I'll take a look.
Indeed it does.

Chris

This is a victim of CSD, I guess. When I turned that off in Tweak and logged out/in it was fine. I noticed problems with arandr during mxfb development and switched to lxrandr to avoid them.

Posted: **Thu Jul 29, 2021 4:08 pm**

chrispop99 wrote: Thu Jul 29, 2021 3:34 pm MX Date & Time>Network Time tab - there are no network servers in the list.

Chris

I know what the problem is, a fix will come shortly from the repos.

Posted: **Thu Jul 29, 2021 4:18 pm**

Trying to boot the live 64-bit system from a Ventoy hdd:
After the kernel was loaded a Fatal error occurred: Could not find antiX/linuxfs

Edit july 30th:
Tried again on a different system with GA-MA770-DS3 (rev. 1.0) mobo and with different SSD (Samsung 850 EVO instead of Crucial BX500) to install MX Linux on, but booting from the same Ventoy hdd.
This time the live system booted quickly, without any long delay after the kernel was loaded. Will try later on the previous system again.
Installation, to a MBR partition, on a SSD 850 EVO and reboot went also without any problems. No long delays, as with MX19 on a SSD BX500!
MX21 seems to be a little faster than MX19.

I tried again on the first system, again without success: MX19.3, MX19.4 and MX21 Beta cannot be loaded with the same failure: Could not find antiX/linuxfs
This system is a HP Pavilion m8180nl-a, which i use already a long time and mostly without any serious problems.
The live systems of several other Linux distributions then MX can be loaded without any problem from the same Ventoy external hdd.
The HP computer is known for its limitations in the BIOS addressing too large partitions.
I tried exfat partitions of 127GB and 100GB. Still too big perhaps?

Machine:
Type: Desktop Mobo: ASUSTeK model: Berkeley v: 1.xx
serial: <superuser required> BIOS: American Megatrends v: 5.04
date: 06/23/2007
CPU:
Info: Quad Core model: Intel Core2 Quad bits: 64 type: MCP cache:
L2: 4 MiB
Speed: 1596 MHz min/max: 1596/2394 MHz Core speeds (MHz): 1: 1596 2: 1602
3: 1596 4: 1596

Final update

.
I updated the Ventoy disk from 1.0.37 to the latest 1.0.47 version of Ventoy and now MX Live can be booted again from the Ventoy disk, connected to my HP system.
MX21 Beta is running fine. So no problems anymore sofar.

Posted: **Thu Jul 29, 2021 4:20 pm**

dolphin_oracle wrote: Thu Jul 29, 2021 4:07 pm
oops wrote: Thu Jul 29, 2021 4:01 pm ... Tried again MX-21 beta 1, and the .iso is fast to decompress and to load on VM (faster than MX19) ... is this iso is compressed with zstd?
yes

What was MX using before the switch? xz or gzip?

Posted: **Thu Jul 29, 2021 4:21 pm**

anticapitalista wrote: Thu Jul 29, 2021 4:20 pm
dolphin_oracle wrote: Thu Jul 29, 2021 4:07 pm
oops wrote: Thu Jul 29, 2021 4:01 pm ... Tried again MX-21 beta 1, and the .iso is fast to decompress and to load on VM (faster than MX19) ... is this iso is compressed with zstd?
yes
What was MX using before the switch? xz or gzip?

xz

snapshot has been defaulting to lz4, but zstd is almost as fast to compress and about 450 MB smaller than lz4 for the shipping isos.

Posted: **Thu Jul 29, 2021 4:27 pm**

arandr may be removed by default, but for those testing it, you can use "gtk3-nocsd arandr" to run it with its normal decorations without logging out/logging in.

Posted: **Thu Jul 29, 2021 4:36 pm**

dolphin_oracle wrote: Thu Jul 29, 2021 4:21 pm
anticapitalista wrote: Thu Jul 29, 2021 4:20 pm
dolphin_oracle wrote: Thu Jul 29, 2021 4:07 pm

yes
What was MX using before the switch? xz or gzip?
xz

snapshot has been defaulting to lz4, but zstd is almost as fast to compress and about 450 MB smaller than lz4 for the shipping isos.

Thanks. We at antiX have been using gzip for the full so version. So as not to derail the thread, email me if you have any data about gzip v zstd.

Posted: **Thu Jul 29, 2021 5:26 pm**

Arbuthnot wrote: Thu Jul 29, 2021 2:21 pm Megasync won't install from MX Package Installer, says "megasync : Depends: libraw19 (>= 0.16.0) but it is not installable". Downloaded the deb file for Debian testing from Mega.nz, open with gdebi which says it will install dependencies, but it just bombs out with no error. Tried installing with dpkg, again complains about dependencies, but apt-get -f install fixed it. Version 4.5.3 now running OK.

No alias for python - it's good that python3 is the default now, but I've struggled to remember to type python3 rather than just python for years!

Thanks, there was already an issue reported for GDebi, I wouldn't use it for now.

It looks like the entry for Mega may need updated in MXPI though cause it tries to pull the Debian 10.0 version and thats why the depends issue with libraw19 pops

I just downloaded the Mega desktop app, right-clicked and choose "Install Deb Files" and it installed and opened without doing anything else.

Posted: **Thu Jul 29, 2021 6:40 pm**

My Epson scanner is only detected by sane-find-scanner run as root. As user, it returns:

@Gaer Boy could you check to see if adding the saned user to lp and/or plugdev groups helps with your scanner setup issue. you might need to reboot for the changes to take affect.

Code: Select all

sudo usermod -a -G lp saned
sudo usermod -a -G plugdev saned

Posted: **Thu Jul 29, 2021 8:08 pm**

Will MX21-KDE have it's own separate beta series? Would that be expected after the Xfce version is at or near final?

Posted: **Thu Jul 29, 2021 8:26 pm**

yes, MX-21 Fluxbox as well (I'm sure you wanted to know that)

Posted: **Thu Jul 29, 2021 8:33 pm**

@uncle mark Jerry already answered it, but just to expand on it, Adrian told me that MX-KDE will still be based on AHS, so one main thing keeping the MX-KDE Beta on hold is me finishing the AHS stuffs.

Not too much longer for the AHS to be ready to go through internal testing. But Adrian is the one to answer on the rest.

But again, really the answer is … when it’s ready.

Posted: **Thu Jul 29, 2021 8:59 pm**

Sorry I butted in there...

Posted: **Thu Jul 29, 2021 9:12 pm**

@Jerry3904 oh no it’s all good. I just wanted to expand on it, really it’s not my place to talk about MX-KDE either lol.
Cats out of the bag though, users know work is being done.

It’s going to be interesting with 3 major standalone versions with so much to offer, really a huge accomplishment. Especially on MXFB.

Posted: **Thu Jul 29, 2021 9:23 pm**

Mxfb is taking a lot of work, and I don't have the skills everybody else does...

Posted: **Thu Jul 29, 2021 9:59 pm**

Jerry3904 wrote: Thu Jul 29, 2021 9:23 pm Mxfb is taking a lot of work, and I don't have the skills everybody else does...

You have a lot of skills

Posted: **Fri Jul 30, 2021 3:29 am**

Adrian wrote: Thu Jul 29, 2021 4:08 pm
chrispop99 wrote: Thu Jul 29, 2021 3:34 pm MX Date & Time>Network Time tab - there are no network servers in the list.

Chris
I know what the problem is, a fix will come shortly from the repos.

mx-timedate has updated from 21.3 to 21.7, and the servers are now in the list. However, running 'Update Now' results in the message 'The system clock could not be updated.' A reboot didn't help.

EDIT

The machine I was testing this on has an encrypted install. When testing on other hardware without encryption, Date & Time work as expected.

Chris

Posted: **Fri Jul 30, 2021 5:08 am**

Making my usual adjustments/preferences to MX, I found the following:

1. Using Conky Manager to turn off the blue roboto and switch on MX Full, does switch off the former but does not turn on the latter. (it does seem to turn others on when selected).

2. using synaptic package manager to install proftpd-basic, gives an error in proftpd-basic. The error messages displayed are proftpd-core post installation script subprocess returned error exit status 1. proftpd-mod-crypto dependency problems - leaving unconfigured. proftpd-mod-wrap dependency problems - leaving unconfigured. proftpd-basic dependency problems - leaving unconfigured.
Looking through the details afterwards it seems that it can't run because the system was not booted with systemd. This appears to be the reason why core did not complete and everything else is dependent on core.
This didn't seem to be a problem with MX19 (though I may have changed something without realising/remembering).

3. Installing Kindle from a pre-downloaded exe, installing on a fresh 32bit wine, it installs but then when run it can't find the internet. (I've seen this problem before but not on a fresh wine install. I also tried the Kindle version included in winetricks and that did the same.) I realise this could be for a whole range of reasons and could be more to do with wine than MX. But it was working fine in MX19.4.

Posted: **Fri Jul 30, 2021 5:31 am**

I also note that with the default theme settings, when typing into the search box on MX(start) menu there is no highlight bar to show which item will be run when I press enter.

Also after having typed, the mousepad takes a long time to 'wake up'.

Posted: **Fri Jul 30, 2021 6:32 am**

MX21 live system on,

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: persist_static_root tz=America/Phoenix quiet splasht nosplash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP EliteBook 8440p v: N/A 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Hewlett-Packard model: 172A v: KBC Version 30.35 serial: <filter> 
           BIOS: Hewlett-Packard v: 68CCU Ver. F.60 date: 11/11/2015 
Battery:   ID-1: BAT0 charge: 45.6 Wh condition: 47.0/47.0 Wh (100%) volts: 12.3/11.1 
           model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Unknown 
CPU:       Topology: Dual Core model: Intel Core i5 M 560 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 bogomips: 21284 
           Speed: 1655 MHz min/max: 1199/2667 MHz boost: enabled Core speeds (MHz): 1: 1499 
           2: 1376 3: 1402 4: 1412 
           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 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: Hewlett-Packard 
           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, 1280x1024~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: Intel 82577LM Gigabit Network vendor: Hewlett-Packard driver: e1000e 
           v: kernel port: 5020 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: 5000 
           bus ID: 43:00.0 chip ID: 8086:4239 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 7.27 GiB used: 2.03 GiB (27.9%) 
           ID-1: /dev/sda type: USB vendor: Kingston model: DataTraveler 2.0 size: 7.27 GiB 
           block size: physical: 512 B logical: 512 B speed: <unknown> serial: <filter> 
           rev: PMAP scheme: MBR 
Partition: ID-1: / raw size: N/A size: 3.86 GiB used: 149.6 MiB (3.8%) fs: overlay 
           source: ERR-102 
Sensors:   System Temperatures: cpu: 42.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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 224 Uptime: 2m Memory: 3.64 GiB used: 611.1 MiB (16.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:
pre-sandybridge UXA acceleration

Posted: **Fri Jul 30, 2021 6:43 am**

MX21 live system on,

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: persist_static_root tz=America/Phoenix quiet splasht nosplash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: P5L8L-SE v: Rev 1.xx serial: <filter> 
           BIOS: American Megatrends v: 0201 date: 10/09/2007 
CPU:       Topology: Single Core model: Intel Pentium 4 bits: 64 type: MT arch: Netburst Presler 
           family: F (15) model-id: 6 stepping: 5 microcode: B L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 bogomips: 13599 
           Speed: 3400 MHz min/max: N/A Core speeds (MHz): 1: 3400 2: 3400 
           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 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 82945G/GZ Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:2772 
           Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1280x1024~60Hz 
           OpenGL: renderer: Mesa DRI Intel 945G v: 1.4 Mesa 20.3.5 direct render: Yes 
Audio:     Message: No Device data found. 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK P5B 
           driver: r8169 v: kernel port: e800 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Realtek RTL8191SU 802.11n WLAN Adapter type: USB driver: r8712u 
           bus ID: 5-5:3 chip ID: 0bda:8172 serial: <filter> 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 160.66 GiB used: 2.07 GiB (1.3%) 
           ID-1: /dev/sda vendor: Western Digital model: WD1600YS-01SHB1 size: 153.39 GiB 
           block size: physical: 512 B logical: 512 B speed: <unknown> serial: <filter> 
           rev: 6C06 scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 2.0 size: 7.27 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: PMAP scheme: MBR 
Partition: ID-1: / raw size: N/A size: 3.86 GiB used: 164.9 MiB (4.2%) fs: overlay 
           source: ERR-102 
           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:   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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 196 Uptime: 3m Memory: 1.93 GiB used: 756.9 MiB (38.3%) 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:
pre-sandybridge UXA acceleration

Posted: **Fri Jul 30, 2021 6:56 am**

Stufe wrote: Fri Jul 30, 2021 5:31 am I also note that with the default theme settings, when typing into the search box on MX(start) menu there is no highlight bar to show which item will be run when I press enter.

Also after having typed, the mousepad takes a long time to 'wake up'.

wakup time is configurable in the Mouse & Touchpad settings. by dfeaul its 2 seconds I think. I usually change mine to about .5 seconds.

in whisker, only the first search result doesn't have a highlight. navigating the menu puts a box around other items.

Posted: **Fri Jul 30, 2021 6:58 am**

MX21live system on,

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash lang=en_US kbd=us 
           tz=America/Phoenix 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Acer product: Aspire E5-571 v: V1.04 serial: <filter> Chassis: 
           type: 10 serial: <filter> 
           Mobo: Acer model: EA50_HB v: V1.04 serial: <filter> UEFI: Insyde v: 1.04 
           date: 05/06/2014 
Battery:   ID-1: BAT1 charge: 47.8 Wh condition: 47.8/55.9 Wh (86%) volts: 13.0/11.1 
           model: SANYO 0032334134314C41 type: Li-ion serial: <filter> status: Charging 
CPU:       Topology: Dual Core model: Intel Core i3-4030U bits: 64 type: MT MCP arch: Haswell 
           family: 6 model-id: 45 (69) stepping: 1 microcode: 17 L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 15165 
           Speed: 898 MHz min/max: 800/1900 MHz Core speeds (MHz): 1: 943 2: 954 3: 954 4: 939 
           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: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics vendor: Acer Incorporated ALI 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0a16 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Haswell-ULT HD Audio vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0a0c 
           Device-2: Intel 8 Series HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 chip ID: 8086:9c20 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 3000 bus ID: 01:00.1 
           chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter vendor: Lite-On 
           driver: ath9k v: kernel port: 3000 bus ID: 02:00.0 chip ID: 168c:0036 
           IF: wlan0 state: up mac: <filter> 
           Device-3: Lite-On Atheros AR3012 Bluetooth type: USB driver: btusb bus ID: 2-5:5 
           chip ID: 04ca:300b 
Drives:    Local Storage: total: 473.03 GiB used: 1.95 GiB (0.4%) 
           ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> 
           rev: SDM1 scheme: GPT 
           ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 2.0 size: 7.27 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: PMAP scheme: MBR 
Partition: ID-1: / raw size: N/A size: 6.06 GiB used: 64.5 MiB (1.0%) fs: overlay 
           source: ERR-102 
Sensors:   System Temperatures: cpu: 48.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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 227 Uptime: 5m Memory: 7.66 GiB used: 955.3 MiB (12.2%) 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

Posted: **Fri Jul 30, 2021 7:01 am**

dolphin_oracle wrote: Thu Jul 29, 2021 6:40 pm
My Epson scanner is only detected by sane-find-scanner run as root. As user, it returns:
@Gaer Boy could you check to see if adding the saned user to lp and/or plugdev groups helps with your scanner setup issue. you might need to reboot for the changes to take affect.

@dolphin_oracle This had no effect. I think a udev rules entry may work - I'll have to work out where to put it.

Posted: **Fri Jul 30, 2021 7:09 am**

dolphin_oracle wrote: Fri Jul 30, 2021 6:56 am
Stufe wrote: Fri Jul 30, 2021 5:31 am I also note that with the default theme settings, when typing into the search box on MX(start) menu there is no highlight bar to show which item will be run when I press enter.

Also after having typed, the mousepad takes a long time to 'wake up'.
wakup time is configurable in the Mouse & Touchpad settings. by dfeaul its 2 seconds I think. I usually change mine to about .5 seconds.

in whisker, only the first search result doesn't have a highlight. navigating the menu puts a box around other items.

On the fresh install of 19.4 the mouse does not seem to 'go to sleep' immediately after typing in the search box on the menu.

For the other themes, there is a highlight on even the first search result in the menu.

Posted: **Fri Jul 30, 2021 7:10 am**

Gaer Boy wrote: Thu Jul 29, 2021 2:14 pm
SwampRabbit wrote: Thu Jul 29, 2021 12:59 pm @Gaer Boy you've changed the icons LibreOffice is using somehow, you can tell from comparing your pic to the one d.o. just shared.
It looks like you have Breeze Dark set. I checked and OOTB it's fine.

Can you go to Tools> Options > LibreOffice - View > Icon style to "Automatic (Colibre)
Confirmed that I have the Breeze Dark, but I didn't change it. That was how it was. I'll try the change tomorrow - I'm back in MX-19 for today because I don't have my backup routines set in MX-21 yet.

@SwampRabbit OK, that sorted the problem. It occurs to me that when I first opened LO i had a new version dialog. I thought I just closed it but I could have changed something.

Posted: **Fri Jul 30, 2021 7:22 am**

Hello dolphin_oracle
This machine, "WallE", will not start MX21,

Code: Select all

System:    Host: <filter> Kernel: 4.19.0-16-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-16-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 21  2019 base: Debian GNU/Linux 10 (buster) 
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 vmx bogomips: 23409 
           Speed: 1320 MHz min/max: 1200/2933 MHz Core speeds (MHz): 1: 1301 2: 1286 3: 1283 
           4: 1235 
           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, 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.4 driver: intel resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ironlake Desktop v: 2.1 Mesa 18.3.6 
           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: k4.19.0-16-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: 1.82 TiB used: 16.66 GiB (0.9%) 
           ID-1: /dev/sda vendor: Toshiba model: DT01ACA200 size: 1.82 TiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: ABB0 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: 1.82 TiB size: 1.79 TiB (98.38%) used: 16.66 GiB (0.9%) 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: 29.8 C mobo: 15.2 C 
           Fan Speeds (RPM): cpu: 873 fan-2: 893 fan-3: 0 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.34 vbat: 3.28 
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/ 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: 208 Uptime: 3m Memory: 7.66 GiB used: 827.3 MiB (10.6%) 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

WallE runs mxkde, antiX19, mx19xfce [this qsi.]
The same usb that runs in those other three machines
stops at the bios splash.
With internal drive plugged in it will not give boot menu.
With no internal drive hooked up it will not start nor give boot menu. ;
it is blocked from seeing any bootable devices (but no message cunclusion comes)
it is just locked on the bios splash and goes no further.
usb image is by both mx and antiX live-usb-maker. have done full and dd.; always the same= it starts in three machines and it fails in WallE.

Posted: **Fri Jul 30, 2021 8:01 am**

Stufe wrote: Fri Jul 30, 2021 7:09 am
dolphin_oracle wrote: Fri Jul 30, 2021 6:56 am
Stufe wrote: Fri Jul 30, 2021 5:31 am I also note that with the default theme settings, when typing into the search box on MX(start) menu there is no highlight bar to show which item will be run when I press enter.

Also after having typed, the mousepad takes a long time to 'wake up'.
wakup time is configurable in the Mouse & Touchpad settings. by dfeaul its 2 seconds I think. I usually change mine to about .5 seconds.

in whisker, only the first search result doesn't have a highlight. navigating the menu puts a box around other items.
On the fresh install of 19.4 the mouse does not seem to 'go to sleep' immediately after typing in the search box on the menu.

For the other themes, there is a highlight on even the first search result in the menu.

the sleep time on touchpads (not mouse) is new on mx21.

Posted: **Fri Jul 30, 2021 8:09 am**

Hi, I tried installing on an existing MX-19 machine with encrypted root filesystem (and no separate /home partition): although the installer help on the left mentions the "Preserve /home" option, I actually couldn't see that in the drop down list, so I aborted installation. Am I missing something, is the installer unable to preserve /home if root is encrypted, or is this a bug in the installer?
Thanks

Posted: **Fri Jul 30, 2021 9:21 am**

i_ri wrote: Fri Jul 30, 2021 7:22 am Hello dolphin_oracle
This machine, "WallE", will not start MX21,

WallE runs mxkde, antiX19, mx19xfce [this qsi.]
The same usb that runs in those other three machines
stops at the bios splash.
With internal drive plugged in it will not give boot menu.

Would you try this boot parameter:
blab=MX-Live-usb
added to the first setparams line within the Grub menu entry.
Press »e« to edit, press »End« key to jump to the end of the first line.
Press space bar and type:
blab=MX-Live-usb
Press F10 or Ctrl-x to boot.

Posted: **Fri Jul 30, 2021 9:39 am**

i_ri wrote: Fri Jul 30, 2021 7:22 am This machine, "WallE", will not start MX21,
Code: Select all
[...]
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
[...]
Drives:    Local Storage: total: 1.82 TiB used: 16.66 GiB (0.9%) 
           ID-1: /dev/sda vendor: Toshiba model: DT01ACA200 size: 1.82 TiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: ABB0 scheme: MBR
[...]
[...]
stops at the bios splash.
With internal drive plugged in it will not give boot menu.
With no internal drive hooked up it will not start nor give boot menu. ;
it is blocked from seeing any bootable devices (but no message cunclusion comes)
it is just locked on the bios splash and goes no further.

So, you cannot even get to the live boot menus? This is a Legacy-BIOS (non-EFI) machine, at least how it is configured, with MBR boot.
I am sure fehlix would like to know if this machine can only boot in Legacy_BOOT mode and non-UEFI mode. Can you temporarily change the BIOS options to boot UEFI (if available) just to test? You can then restore it to Legacy(non UEFI) mode after testing the USB device again.

Posted: **Fri Jul 30, 2021 9:44 am**

nXecure wrote: Fri Jul 30, 2021 9:39 am
i_ri wrote: Fri Jul 30, 2021 7:22 am This machine, "WallE", will not start MX21,
Code: Select all
[...]
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
[...]
Drives:    Local Storage: total: 1.82 TiB used: 16.66 GiB (0.9%) 
           ID-1: /dev/sda vendor: Toshiba model: DT01ACA200 size: 1.82 TiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: ABB0 scheme: MBR
[...]
[...]
stops at the bios splash.
With internal drive plugged in it will not give boot menu.
With no internal drive hooked up it will not start nor give boot menu. ;
it is blocked from seeing any bootable devices (but no message cunclusion comes)
it is just locked on the bios splash and goes no further.
So, you cannot even get to the live boot menus? This is a Legacy-BIOS (non-EFI) machine, at least how it is configured, with MBR boot.
I am sure fehlix would like to know if this machine can only boot in Legacy_BOOT mode and non-UEFI mode. Can you temporarily change the BIOS options to boot UEFI (if available) just to test? You can then restore it to Legacy(non UEFI) mode after testing the USB device again.

Oops ... on BIOS boot mode: add the mentioned boot parameter into the boot option field,
or switch to GRUB.
I wonder whether blab= helps to not have the live-search stop/hangs at the RAID device.

Posted: **Fri Jul 30, 2021 11:00 am**

Gaer Boy wrote: Fri Jul 30, 2021 7:01 am
dolphin_oracle wrote: Thu Jul 29, 2021 6:40 pm
My Epson scanner is only detected by sane-find-scanner run as root. As user, it returns:
@Gaer Boy could you check to see if adding the saned user to lp and/or plugdev groups helps with your scanner setup issue. you might need to reboot for the changes to take affect.
@dolphin_oracle This had no effect. I think a udev rules entry may work - I'll have to work out where to put it.

OK - This is resolved. Mention of a udev rules entry triggered my memory. When I got this scanner last year I had a problem getting it to work. The solution was a driver download from Epson, an entry in /etc/udev/rules.d/ and a symlink to the location of the epkowa driver. Reboot and all works as expected.

Posted: **Fri Jul 30, 2021 12:22 pm**

I wanted an encrypted disk, so went for the MX21 Beta option with fresh install. I am no nerd, but have used linux for over ten years and MX LInux 3 years. So far all good, but I found one issue when wanting to install Ocenaudio from a deb package. It failed with the package installer-just hung, do not know why. Yet when I installed from a terminal, it installed as expected.
Other packages installed include Megasync, Ardour and have not encountered any issues.
Sorry I am no guru, but hope this may help someone.
Other than that, I have found the look to be an improvement, though have adjusted background to my taste.
Regards
GMT

Posted: **Fri Jul 30, 2021 12:38 pm**

gmt wrote: Fri Jul 30, 2021 12:22 pm ... So far all good, but I found one issue when wanting to install Ocenaudio from a deb package. It failed with the package installer-just hung, do not know why. Yet when I installed from a terminal, it installed as expected.
...

Thanks

When you say "package installer" do you mean the one that opens when you double click the .deb?

This issue has been reported already
viewtopic.php?p=646183#p646183
viewtopic.php?p=646245#p646245

Posted: **Fri Jul 30, 2021 1:00 pm**

chrispop99 wrote: Fri Jul 30, 2021 3:29 am
Adrian wrote: Thu Jul 29, 2021 4:08 pm
chrispop99 wrote: Thu Jul 29, 2021 3:34 pm MX Date & Time>Network Time tab - there are no network servers in the list.

Chris
I know what the problem is, a fix will come shortly from the repos.
mx-timedate has updated from 21.3 to 21.7, and the servers are now in the list. However, running 'Update Now' results in the message 'The system clock could not be updated.' A reboot didn't help.

EDIT

The machine I was testing this on has an encrypted install. When testing on other hardware without encryption, Date & Time work as expected.

Chris

I tested the command, you might get this error if one of the debian.pool.ntp.org fails, it runs the command with all of them and if one fails for some reason the command fails, I think I will change that to check in order and return once it gets a good result.

Posted: **Fri Jul 30, 2021 1:08 pm**

Brightness Systray in Settings Manager fails to start.

Posted: **Fri Jul 30, 2021 1:19 pm**

SwampRabbit wrote: Fri Jul 30, 2021 12:38 pm
gmt wrote: Fri Jul 30, 2021 12:22 pm ... So far all good, but I found one issue when wanting to install Ocenaudio from a deb package. It failed with the package installer-just hung, do not know why. Yet when I installed from a terminal, it installed as expected.
...
Thanks

When you say "package installer" do you mean the one that opens when you double click the .deb?

This issue has been reported already
viewtopic.php?p=646183#p646183
viewtopic.php?p=646245#p646245

Yes, sorry for my error, but wanted to provide positive feedback. Im addition the set up of my HP printer went like a dream, whereas previous it was an issue with a binary plugin required.

Posted: **Fri Jul 30, 2021 1:25 pm**

gmt wrote: Fri Jul 30, 2021 1:19 pm Yes, sorry for my error, but wanted to provide positive feedback. Im addition the set up of my HP printer went like a dream, whereas previous it was an issue with a binary plugin required.

Its ok, but that is what you are talking about right?

Double clicking a .deb and Gebi failing to install it?

Posted: **Fri Jul 30, 2021 1:35 pm**

Gaer Boy wrote: Fri Jul 30, 2021 1:08 pm Brightness Systray in Settings Manager fails to start.

@Gaer Boy thanks. so no icon in the systray? Looks like a little half-sun type icon

Posted: **Fri Jul 30, 2021 3:34 pm**

More testing...
All working so far.

Lots of sleep and wake, no problems.
Took all synaptic upgrades.
disabled sudo per I think swamprabit's tip.
compositor changed to compton.
installed Warpinator, it works.
Audacity works.
conky changed and edited all with normal operation.
The usual firefox customization

I changed the theme and stuff. It was a black window title bar, right?
That makes it hard if two title bars overlap, it is hard to see what is what.
The old MX greybird has a row of pixels at the window edge with a different color to differentiate the edge.

Fortunately there are many options to choose from.
But what should be the default for wide appeal to reviewers and new MX users?

Posted: **Fri Jul 30, 2021 3:39 pm**

During the install you can go to advanced, and disable services.
I do that and take off sudo and bluetooth.

So what does that un-checking sudo do ?

I go and had to change it in the MX Tweak ---> Other to turn off the sudo authentication for admin tasks like synaptic. (SwampRabit's tip)

Posted: **Fri Jul 30, 2021 3:40 pm**

entropyfoe wrote: Fri Jul 30, 2021 3:39 pm During the install you can go to advanced, and disable services.
I do that and take off sudo and bluetooth.

So what does that un-checking sudo do ?

I go and had to change it in the MX Tweak ---> Other to turn off the sudo authentication for admin tasks like synaptic. (SwampRabit's tip)

unchecking sudo disables the sudo service, but it does not affect the gui authentication prompts because that is polkit not sudo.

Posted: **Fri Jul 30, 2021 3:40 pm**

entropyfoe wrote: Fri Jul 30, 2021 3:39 pm So what does that un-checking sudo do ?

https://askubuntu.com/questions/228288/ ... service-do

Posted: **Fri Jul 30, 2021 4:25 pm**

Thanks Adrian and d_O.

A little bench-marking now, since I have MX 21 and MX 19.4, both full updated on the same machine, different partitions.
So running the System Profiler and Benchmark tool, the only difference is the OS, and therefore the kernel.
MX 21 5.10.0-8
MX 19.4 5.10.0-5mx
Significant means the difference on OS is much greater than the difference from repeated running of the test. Testing after fresh reboots, only a terminal open besides the Profiler. The system is in the signature.

Test ..............MX21 .....MX 19.4
CPU Blow fish ..... 0.47 .....0.48 seconds
Cryptohash ......5339 ....1953 (wow that's a big difference, it is repeatable and significant)
Fibonacci .........0.30 .....0.49 sec MX21 faster, it is repeatable and significant)
n-Queens ........4.62 ......4.54 sec
CPU z-lib ........2.93 .....3.00 High Mark score
fft ...............0.71 ......0.69
fpu ray tracing ....4.2 .....2.25 sec (wow MX 21 much slower it is repeatable, and significant)
gpu drawing .....13298 .....14663

Posted: **Fri Jul 30, 2021 4:37 pm**

Interesting. I wouldn't use the System Profiler and Benchmark tool as a measure of benchmarking too much... good, bad, or indifferent.

1) Debian's version of hardinfo is really old in the stock Debians (don't know if we updated it for MX-19 after)... something to look at later
2) Everything in Buster/MX-19 has gone through so many updates/tweaks over their lifespan that its kinda unfair to compare it to both Debian and MX Betas.

Do let us know if you see real world differences or do more benchmarking.

Posted: **Fri Jul 30, 2021 5:46 pm**

SwampRabbit,

Yup, I don't attribute any absolute signifficance to the Bench marking numbers. But a relative comparison should be valid.
But assuming the benchmark code is the same in MX19.4 and Mx21, on the exact same hardware, then what is the differences?
The OS, libraries, the kernel maybe some flags set different.

It is interesting some benchmarks are almost identical and some have big changes.
The crypto hash, for example, if it has any relevance to actual mining, then you are making twice as much money per day.

Posted: **Fri Jul 30, 2021 5:53 pm**

What is that Thunar icon?
How anti-intuitive !

I tried different icon sets in the MX Tweak, but they are all the same for Thunar.
Can we get a new one?

Posted: **Fri Jul 30, 2021 6:02 pm**

Leo C. wrote: Fri Jul 30, 2021 8:09 am Hi, I tried installing on an existing MX-19 machine with encrypted root filesystem (and no separate /home partition): although the installer help on the left mentions the "Preserve /home" option, I actually couldn't see that in the drop down list, so I aborted installation. Am I missing something, is the installer unable to preserve /home if root is encrypted, or is this a bug in the installer?
Thanks

@Leo C. There is no bug, just a new process. Scroll down in the help and you'll see what to do. It's relatively straightforward and it helps a lot if you have the naming schema already in use on your existing install. This is not strictly necessary, but the names you give to the encrypted partitions will be used in /dev/mapper/

To get the naming convention in use, start by looking in /dev/mapper/ on your existing installation. Here you'll find a control file and symlinks to the partition names used when you last installed MX Linux. if you want to re-use these names, write them down, commit them to memory and when you're asked to provide a name for the encrypted partition, type it in.

When selecting your partitions, right click the encrypted partition and select unlock or add to crypt tab, then type in the name you wish to use and the encryption password.

One issue with re-using the swap file though is after unlocking and re-using it through the installer, you will end up with a password prompt to unlock every encrypted partition you reused through the installer, so if you reused 2 partions, you will have to type each partitions password at login and if you reused 3 encrypted partitions, you will be asked 3 times at boot for the password for each partition.

This may be a either a bug or an omission in the new installer, or an error in the process I tested with. Maybe others can chip in here to give some clarity.

Posted: **Fri Jul 30, 2021 6:05 pm**

entropyfoe wrote: Fri Jul 30, 2021 5:53 pm What is that Thunar icon?
How anti-intuitive !

I tried different icon sets in the MX Tweak, but they are all the same for Thunar.
Can we get a new one?

That is on our list, in fact, we're just not far along yet.

Posted: **Fri Jul 30, 2021 6:26 pm**

entropyfoe wrote: Fri Jul 30, 2021 5:53 pm What is that Thunar icon?
How anti-intuitive !

I tried different icon sets in the MX Tweak, but they are all the same for Thunar.
Can we get a new one?

That’s the stock icon for Xfce, like already stated that’s on the list of changes, you don’t have to ! about it.

It should be the home folder icon, it’ll get fixed soon.

Posted: **Fri Jul 30, 2021 6:36 pm**

I understand it is the stock icon.

But what is it? What were the xfce folks thinking of?

Posted: **Fri Jul 30, 2021 6:41 pm**

Thunar is the Old Saxon name of god of thunder in Norse mythology, and uses Mjölnir, Thor's hammer, as its icon.

Posted: **Fri Jul 30, 2021 6:56 pm**

Right--which almost no one knows anything about (I actually studied Old Norse at one point, no idea why)! As a sign for "File manager" however it is IMO too clever by half.

Posted: **Fri Jul 30, 2021 7:12 pm**

Hello fehlix
hold on to your hats, i hate to do this to you:
created a live media using rufus3.14.1788 and MX21 starts in WallE, p6330f.
full-featured mode from rufus goes past bios splash normally.

Yes nXecure 6330 WalllE is legacy bios, no uefi, and
the six usb media trials made with mx and antiX live-usb-maker do not get to the boot menu. It stops at the bios splash under any circumstance that the live media is plugged-in to the 6330 machine.
The same media will start in the other machines, asus tubb is legacy, hp8440 heap is uefi booting legacy, acer idca is booting uefi with a "secure boot" text in lower left displayed on the booting screen.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: tz=America/Phoenix quiet splasht nosplash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_beta1_x64 Wildflower July 27  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: 23411 
           Speed: 1237 MHz min/max: 1200/2933 MHz Core speeds (MHz): 1: 1347 2: 1233 3: 1294 
           4: 1334 
           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 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: 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: 14.91 GiB used: 2.09 GiB (14.0%) 
           ID-1: /dev/sdb type: USB vendor: SanDisk model: Cruzer Glide size: 14.91 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 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: N/A size: 6.06 GiB used: 428.0 MiB (6.9%) fs: overlay 
           source: ERR-102 
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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 212 Uptime: 26m Memory: 7.64 GiB used: 976.5 MiB (12.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 
Video Tweaks:
pre-sandybridge UXA acceleration

Posted: **Fri Jul 30, 2021 8:45 pm**

RE: I have retested MX21 (amd64 and x86) and so far I have not find some issue, so congratulations.
Only missing for me are (Orage, the ical (.ics). calendar, (disk-manager already said and the alternative is gnome-utilities), and a useful tool for all .deb : multibootusb_python3/python3-multibootusb_9.2.0-1_all.deb

Posted: **Fri Jul 30, 2021 9:44 pm**

i_ri wrote: Fri Jul 30, 2021 7:12 pm created a live media using rufus3.14.1788 and MX21 starts in WallE, p6330f.
full-featured mode from rufus goes past bios splash normally.

Good. The question was whether a boot parameter like blab=MX-Live-usb, which is the label
of the first (of two) partitions made by MX Live USB Maker, would have made it boot.

Posted: **Fri Jul 30, 2021 10:35 pm**

@Stufe

Stufe wrote: Fri Jul 30, 2021 5:08 am Making my usual adjustments/preferences to MX, I found the following:
\

2. using synaptic package manager to install proftpd-basic, gives an error in proftpd-basic. The error messages displayed are proftpd-core post installation script subprocess returned error exit status 1. proftpd-mod-crypto dependency problems - leaving unconfigured. proftpd-mod-wrap dependency problems - leaving unconfigured. proftpd-basic dependency problems - leaving unconfigured.
Looking through the details afterwards it seems that it can't run because the system was not booted with systemd. This appears to be the reason why core did not complete and everything else is dependent on core.
This didn't seem to be a problem with MX19 (though I may have changed something without realising/remembering).

the package maintainers of proftp have royally screwed it up. technically it still supports sysVinit and systemd,however, their maintainer postinst script still tries to enable the systemd service when systemd isn't running, and the script doesn't allow a graceful failure. the thing is actually set up, but hte package is not marked as such.

the short answer is to install the package while systemd is running. I think it will still work under sysVinit after. that's pretty sloppy work but no one at debian is going to notice since they use system.

there isn't much we can do about it on mx, except allow boot up with systemd, or supply our own proftpd packages with the postinst scripts fixed.

Posted: **Fri Jul 30, 2021 11:35 pm**

oops wrote: Fri Jul 30, 2021 8:45 pm RE: I have retested MX21 (amd64 and x86) and so far I have not find some issue, so congratulations.
Only missing for me are (Orage, the ical (.ics). calendar, (disk-manager already said and the alternative is gnome-utilities), and a useful tool for all .deb : multibootusb_python3/python3-multibootusb_9.2.0-1_all.deb

Orage is dead, it’s probably never coming back unless someone picks it up, this will be for every Distro running Xfce 4.16.

python3-multibootusb Also seems abandoned by the developer, the GitHub has been stagnant almost a year and a half, the website has been taken over by someone as looks to be just a sink hole, a GitHub issue for it not working with MX-19 was opened back in November of last year.

Posted: **Sat Jul 31, 2021 1:18 am**

hello fehlix
In the cases of freeze at bios splash,
Unable to try e adding a boot parameter on boot screen. It did not progress that far.
Can the parameter be added into some file?
still here. it can be tested?
if you wish testing by adding blab= somewhere besides the boot screen, then i can happpily try it. add parameter to a file?

Posted: **Sat Jul 31, 2021 1:21 am**

hello dolphin_oracle
MX21 installed system on, [WallE]

Code: Select all

System:    Host: WallE Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A Desktop: Xfce 4.16.0 
           tk: Gtk 3.24.24 wm: xfwm4 dm: LightDM 
           Distro: MX-21_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A 
           serial: <root required> Chassis: Hewlett-Packard type: 3 serial: <root required> 
           Mobo: MSI model: IONA v: 1.0 serial: <root required> BIOS: American Megatrends 
           v: 5.15 date: 06/25/2010 
CPU:       Dual Core: Intel Core i3 530 type: MT MCP arch: Nehalem speed: 1208 MHz 
           min/max: 1200/2933 MHz 
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 
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 
Drives:    Local Storage: total: 29.11 GiB used: 5.78 GiB (19.9%) 
Info:      Processes: 203 Uptime: 8m Memory: 7.64 GiB used: 589.0 MiB (7.5%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: bash v: 5.1.4 
           running in: xfce4-terminal inxi: 3.0.36

Posted: **Sat Jul 31, 2021 1:52 am**

Can't find the nvidia driver with the MX tool as no candidate is found. Tried the Tauronga NZ repo and the Salt Lake City...

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_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: Latitude E6410 v: 0001 serial: <filter> Chassis: 
           type: 9 serial: <filter> 
           Mobo: Dell model: 07XJP9 v: A01 serial: <filter> BIOS: Dell v: A05 date: 08/10/2010 
Battery:   ID-1: BAT0 charge: 37.2 Wh condition: 37.2/48.8 Wh (76%) volts: 12.1/11.1 
           model: Samsung SDI DELL PT43699 type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i5 M 540 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: 20217 
           Speed: 1460 MHz min/max: 1199/2534 MHz boost: enabled Core speeds (MHz): 1: 1436 
           2: 1388 3: 1414 4: 1396 
           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: NVIDIA GT218M [NVS 3100M] vendor: Dell driver: nouveau v: kernel 
           bus ID: 01:00.0 chip ID: 10de:0a6c 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1440x900~60Hz, 1280x1024~60Hz 
           OpenGL: renderer: NVA8 v: 3.3 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio 
           vendor: Dell Latitude E6410 driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:3b56 
           Device-2: NVIDIA High Definition Audio vendor: Dell 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: Intel 82577LM Gigabit Network vendor: Dell Latitude E6410 driver: e1000e 
           v: kernel port: 8040 bus ID: 00:19.0 chip ID: 8086:10ea 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel port: 7000 
           bus ID: 03:00.0 chip ID: 8086:422b 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 5.83 GiB (0.6%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 
           port: 8020 bus ID: 00:1f.2 chip ID: 8086.282a rev: 05 
Partition: ID-1: / raw size: 24.37 GiB size: 23.82 GiB (97.74%) used: 5.83 GiB (24.5%) fs: ext4 
           dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 61.0 C mobo: N/A sodimm: 44.0 C gpu: nouveau temp: 70 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://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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 236 Uptime: 18m Memory: 7.76 GiB used: 1.23 GiB (15.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

Posted: **Sat Jul 31, 2021 3:51 am**

Posted: **Sat Jul 31, 2021 5:42 am**

dolphin_oracle wrote: Fri Jul 30, 2021 1:35 pm
Gaer Boy wrote: Fri Jul 30, 2021 1:08 pm Brightness Systray in Settings Manager fails to start.
@Gaer Boy thanks. so no icon in the systray? Looks like a little half-sun type icon

@dolphin_oracle Forget I ever mentioned it! I was expecting a more visible reaction and didn't notice the new icon appear.

Posted: **Sat Jul 31, 2021 6:05 am**

SwampRabbit wrote: Fri Jul 30, 2021 11:35 pm Orage is dead, it’s probably never coming back unless someone picks it up, this will be for every Distro running Xfce 4.16.

python3-multibootusb Also seems abandoned by the developer, the GitHub has been stagnant almost a year and a half, the website has been taken over by someone as looks to be just a sink hole, a GitHub issue for it not working with MX-19 was opened back in November of last year.

Thanks for the info, it is not so easier to find a small .ics calendar into Linux (I used Rainlendar in the past, then Orage, and now ???) ... tryed also a yad calendar (without ics) here https://www.antixforum.com/forums/topic ... ed-update/ ... Yad is a good idea too for a calendar.

For python3-multibootusb is sad too than this project is at this level. But I will try to find a workaround.

Posted: **Sat Jul 31, 2021 8:13 am**

I installed on two machines and also in VirtualBox. I noticed this on all. I open Thunar in my normal user and then open another with "open root thunar here". I went to MX Tweak > Window Manager > Theme and made a change.It changes in the one that I opened a root thunar here, but NOT in the normal user thunar. Seems a bit odd.
Earl

Posted: **Sat Jul 31, 2021 8:18 am**

old_guy wrote: Sat Jul 31, 2021 8:13 am I installed on two machines and also in VirtualBox. I noticed this on all. I open Thunar in my normal user and then open another with "open root thunar here". I went to MX Tweak > Window Manager > Theme and made a change.It changes in the one that I opened a root thunar here, but NOT in the normal user thunar. Seems a bit odd.
Earl

I believe you, but I can't duplicate that here.

Posted: **Sat Jul 31, 2021 8:19 am**

Shifu wrote: Sat Jul 31, 2021 1:52 am Can't find the nvidia driver with the MX tool as no candidate is found. Tried the Tauronga NZ repo and the Salt Lake City...

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_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: Latitude E6410 v: 0001 serial: <filter> Chassis: 
           type: 9 serial: <filter> 
           Mobo: Dell model: 07XJP9 v: A01 serial: <filter> BIOS: Dell v: A05 date: 08/10/2010 
Battery:   ID-1: BAT0 charge: 37.2 Wh condition: 37.2/48.8 Wh (76%) volts: 12.1/11.1 
           model: Samsung SDI DELL PT43699 type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i5 M 540 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: 20217 
           Speed: 1460 MHz min/max: 1199/2534 MHz boost: enabled Core speeds (MHz): 1: 1436 
           2: 1388 3: 1414 4: 1396 
           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: NVIDIA GT218M [NVS 3100M] vendor: Dell driver: nouveau v: kernel 
           bus ID: 01:00.0 chip ID: 10de:0a6c 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1440x900~60Hz, 1280x1024~60Hz 
           OpenGL: renderer: NVA8 v: 3.3 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio 
           vendor: Dell Latitude E6410 driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:3b56 
           Device-2: NVIDIA High Definition Audio vendor: Dell 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: Intel 82577LM Gigabit Network vendor: Dell Latitude E6410 driver: e1000e 
           v: kernel port: 8040 bus ID: 00:19.0 chip ID: 8086:10ea 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel port: 7000 
           bus ID: 03:00.0 chip ID: 8086:422b 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 5.83 GiB (0.6%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 
           port: 8020 bus ID: 00:1f.2 chip ID: 8086.282a rev: 05 
Partition: ID-1: / raw size: 24.37 GiB size: 23.82 GiB (97.74%) used: 5.83 GiB (24.5%) fs: ext4 
           dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 61.0 C mobo: N/A sodimm: 44.0 C gpu: nouveau temp: 70 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://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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 236 Uptime: 18m Memory: 7.76 GiB used: 1.23 GiB (15.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

@Shifu please attach the output of "nvidia-detect" and "nvidia-detect-mx" please.

Posted: **Sat Jul 31, 2021 9:02 am**

dolphin_oracle wrote: Sat Jul 31, 2021 8:19 am
@Shifu please attach the output of "nvidia-detect" and "nvidia-detect-mx" please.

Here you go. Hope it helps:

$ vidia-detect
Command 'vidia-detect' not found, did you mean:
command 'nvidia-detect' from deb nvidia-detect
Try: sudo apt install <deb name>

$ vidia-detect-mx
vidia-detect-mx: command not found

Posted: **Sat Jul 31, 2021 9:06 am**

DeepL I'm using a translation tool.

When I select the Japanese Input Fcitx installation from the MX package installer language, I get E: No installation candidate for package 'fcitx-config-gtk2' and E: Package fcitx-frontend-gtk not found. I could not install it.

Also, since 19.X, if you install Japanese Input Fcitx, the dependency mozc-utils-gui is missing and needs to be installed additionally.

In MX-21, I installed it with sudo apt install --install-recommends fcitx fcitx-mozc from a terminal, but it would be helpful if the MX package installer could install it without excess or deficiency.

Translated with www.DeepL.com/Translator (free version)

Posted: **Sat Jul 31, 2021 9:12 am**

Runs very nice on my real computer for a first beta. I've installed on a whole disk while two other physical storage disks are plugged. Windows 10 on one of them.
(M2 SSD for Windows; SATA HDD for Storage)
Still everything boots fine as usual.

At this point I remember a big issue earlier on mx 18 two years ago.
I don't know if it's fixed now but I also don't want to test it.
Two years ago (same setup as described) but when I started Windows 10 through mxlinux' grub installation, it worked once but as soon as I've rebooted from there on I only saw a broken Windows boot instead.
Solution was to only boot windows through it's own boot partition.
I just have to select the Windows SSD at uefi-bios boot selection and never use mxlinux' grub to avoid that.
I guess it has something to do with the real physical disks grub can't manage properly and instead just handling it as virtual partitions. Anyway I consider it a huge bug I would like to get fixed if not happened yet.

For sure related to MX 21 beta1 I only noticed some minor issues yet...
1. Custom application bar transpareny settings only applies after reboot. Colorchange applies immediately as usual.
2. Especially when clicking, Firefox still cut off / cancel casually the navigation through the bookmarks in the menu bar. Long term bug and very annoying.
3. When reinstalling Firefox to Firefox ESR, application bar symbol unindentently doubles while application is open. It probably also affects other applications.
3.1. At that point minimizing through clicking on the active symbol will also not work anymore.
4. Installed packages at mx-package-installer -> stable repository show uninstall/install instead of uninstall/renew-install. Maybe just an incomplete german translation. Very minor.

Nice things I already noticed:
1. Date and time area at the upper panel is now affected by changes of color and transpareny of the application bar. Unfortunately the workspaces symbols at the bottom do not yet.
2. As soon as issue #3 get fixed I appreciate the new Windows10-like symbol management of the panel. *Application bar
3. I like the layout and design changes.

Nice to have people developing such a great OS.
*=Edits

Posted: **Sat Jul 31, 2021 9:13 am**

Shifu wrote: Sat Jul 31, 2021 9:02 am
dolphin_oracle wrote: Sat Jul 31, 2021 8:19 am
@Shifu please attach the output of "nvidia-detect" and "nvidia-detect-mx" please.
Here you go. Hope it helps:

$ vidia-detect
Command 'vidia-detect' not found, did you mean:
command 'nvidia-detect' from deb nvidia-detect
Try: sudo apt install <deb name>

$ vidia-detect-mx
vidia-detect-mx: command not found

@Shifu you spelled the commands wrong

Posted: **Sat Jul 31, 2021 9:19 am**

D'oh
And here's the problem...

$ nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2)

Checking card: NVIDIA Corporation GT218M [NVS 3100M] (rev a2)
Your card is only supported by the 340 legacy drivers series, which is only available up to buster.

$ nvidia-detect-mx
Latest = 460.73.01
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2)

Checking card: NVIDIA Corporation GT218M [NVS 3100M] (rev a2)
Uh oh. Your card is only supported by the 340 legacy drivers series, which is not in any current Debian suite.

Posted: **Sat Jul 31, 2021 9:21 am**

@Shifu yep thanks for the output.

Posted: **Sat Jul 31, 2021 9:25 am**

DO
I redownloaded and checked iso (md5sum), then just ran the live usb. It would act as I stated before only if I:

Opened MX Tools
Selected Tweak
Selected Window Manager (at the bottom)
In the Style tab under Theme made a selection

If I went to Setting Manager > Appearance > Style it seems to work OK

Earl

Posted: **Sat Jul 31, 2021 9:47 am**

Tried to install PIA VPN from MX Package Installer:

Hit:1 http://mxlinux.mirrors.uk2.net/packages/mx/repo bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://deb.debian.org/debian bullseye InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package piavpn-downloader-installer

@dolphin_oracle Install goes further now but does not complete:

[ OK ] downloaded ''
[ ERROR ] Missing checksum

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 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP EliteBook 2560p v: A0001C02 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Hewlett-Packard model: 162B v: KBC Version 04.21 serial: <filter> 
           BIOS: Hewlett-Packard v: 68SSU Ver. F.22 date: 12/22/2011 
Battery:   ID-1: BAT0 charge: 32.8 Wh condition: 47.4/47.4 Wh (100%) volts: 11.4/11.1 
           model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i7-2620M bits: 64 type: MT MCP 
           arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F 
           L2 cache: 4096 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 21550 
           Speed: 1005 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 1053 2: 970 3: 913 4: 936 
           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: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
           vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0126 
           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: Hewlett-Packard 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: Hewlett-Packard driver: e1000e 
           v: kernel port: 4060 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: 4040 bus ID: 24:00.0 chip ID: 8086:0085 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 298.09 GiB used: 5.90 GiB (2.0%) 
           ID-1: /dev/sda vendor: Toshiba model: MK3261GSYN size: 298.09 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: 0C scheme: MBR 
Partition: ID-1: / raw size: 289.54 GiB size: 283.94 GiB (98.06%) used: 5.80 GiB (2.0%) fs: ext4 
           dev: /dev/dm-0 
           ID-2: /boot raw size: 512.0 MiB size: 487.2 MiB (95.16%) used: 101.7 MiB (20.9%) 
           fs: ext4 dev: /dev/sda1 
           ID-3: swap-1 size: 7.98 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/dm-1 
Sensors:   System Temperatures: cpu: 44.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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 230 Uptime: 10m Memory: 7.68 GiB used: 1.43 GiB (18.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

Posted: **Sat Jul 31, 2021 10:06 am**

@jerry525 thanks! we will move that package over to the new repo.

@Toku update coming soon, thank you for the solutions.

Posted: **Sat Jul 31, 2021 11:21 am**

oops wrote: Sat Jul 31, 2021 6:05 am Thanks for the info, it is not so easier to find a small .ics calendar into Linux (I used Rainlendar in the past, then Orage, and now ???) ... tryed also a yad calendar (without ics) here https://www.antixforum.com/forums/topic ... ed-update/ ... Yad is a good idea too for a calendar.

Thanks for sharing the info on yad-calendar. I can look at it more later, we’ll see what we can do, the replacement for orage was pretty high on the list of things.

Posted: **Sat Jul 31, 2021 11:31 am**

Feuerkl1nge wrote: Sat Jul 31, 2021 9:12 am For sure related to MX 21 beta1 I only noticed some minor issues yet...
1. Custom application bar transpareny settings only applies after reboot. Colorchange applies immediately as usual.
3. When reinstalling Firefox to Firefox ESR, application bar symbol unindentently doubles while application is open. It probably also affects other applications.
3.1. At that point minimizing through clicking on the active symbol will also not work anymore.

1. You should be able to “logout” and “log back” in rather than restarting, that or restart the panel manually. I can look at why this is happening, I don’t think we tested transparent panels much. It’s probably a bug in the Xfce panel.

3. This is probably because Firefox-ESR is a different application than Firefox. You can remove the original Firefox and “pin” Firefox-ESR. If you install NEW applications and want them to stick in the panel, you have to “pin” them.
https://mxlinux.org/wiki/docklike-taskbar/

Not sure what you mean with 3.1, but I’ll try an install of Firefox-ESR and try to reproduce.

Posted: **Sat Jul 31, 2021 12:18 pm**

@Feuerkl1nge wrote:

...
3.1. At that point minimizing through clicking on the active symbol will also not work anymore.

Yes, I have experimented this bug too, probably a bug into XFCE4 with the new docklike function for pinned apps (missings or removed after the pinned action).
Maybe a workaround already exits to cancel/kill this old pinned app icon ?

@SwampRabbit

Thanks for sharing the info on yad-calendar. I can look at it more later, we’ll see what we can do, the replacement for orage was pretty high on the list of things.

... Good news.

Posted: **Sat Jul 31, 2021 12:52 pm**

SwampRabbit wrote: Sat Jul 31, 2021 11:31 am 3. This is probably because Firefox-ESR is a different application than Firefox. You can remove the original Firefox and “pin” Firefox-ESR. If you install NEW applications and want them to stick in the panel, you have to “pin” them.
https://mxlinux.org/wiki/docklike-taskbar/

Not sure what you mean with 3.1, but I’ll try an install of Firefox-ESR and try to reproduce.

No to prevent exactly that I've removed the pin manually after uninstalling Firefox and before installing Firefox ESR.
3.1. Comes along with 3. and it means minimizing by clicking the application on the bar does not work anymore. Clicking/activating applications on the bar usually minimize/maximize them.

Posted: **Sat Jul 31, 2021 12:58 pm**

Installed on a fresh WD black HDD on my wimpy HP thin client, boots and seems faster, a quite working iso apparently. I have started to note down issues/points that I'll post later concisely.

Just to confirm if it is a missing/crippled feature for the beta: does it have working folder sharing? I see no samba config app and rt clicking folder>share folder on network asks for password then does nothing. No shares are shown when browsed from thunar network page.
Yes, samba was enabled while installing and iso hash verified.

Posted: **Sat Jul 31, 2021 1:03 pm**

@Feuerkl1nge give me time to try and reproduce and debug this.

Posted: **Sat Jul 31, 2021 1:04 pm**

@agnivo007 the Thunar Samba plugin may be missing, it was just packaged recently, not sure if that is the problem or not.
Can you see if it’s installed?

Posted: **Sat Jul 31, 2021 1:30 pm**

Not sure if this is helpful or not, but I have attempted to install on a Surface Pro + ( 2013 version )

I have fedora installed on it.

Live boot boots to Grub and I get a message of :
error: Secure Boot Forbids loading module from
(hd0,msdos1)/boot/grub/x86_64-efi/eval.mod.

It was a MOTHER to get Fedora on this little guy, and I believe it should load MX ok, however .... there it is.

Bios:
Trusted Platform Module (TPM) = Enabled
Secure Boot Control = Enabled.

If this is anything of use please let me know and I will continue, otherwise I will just put it back on the shelf and leave it on Fedora (ie = unused ;-/ )

Posted: **Sat Jul 31, 2021 1:47 pm**

@CharlesV we do not support secure boot.

Posted: **Sat Jul 31, 2021 1:59 pm**

CharlesV wrote: Sat Jul 31, 2021 1:30 pm Not sure if this is helpful or not, but I have attempted to install on a Surface Pro + ( 2013 version )

I have fedora installed on it.

Live boot boots to Grub and I get a message of :
error: Secure Boot Forbids loading module from
(hd0,msdos1)/boot/grub/x86_64-efi/eval.mod.

It was a MOTHER to get Fedora on this little guy, and I believe it should load MX ok, however .... there it is.

Bios:
Trusted Platform Module (TPM) = Enabled
Secure Boot Control = Enabled.

If this is anything of use please let me know and I will continue, otherwise I will just put it back on the shelf and leave it on Fedora (ie = unused ;-/ )

If you are not dual-booting with Windows, you can turn off Secure Boot. Info is online.

Chris

Posted: **Sat Jul 31, 2021 2:09 pm**

Thanks gents

Posted: **Sat Jul 31, 2021 2:35 pm**

SwampRabbit wrote: Sat Jul 31, 2021 1:04 pm @agnivo007 the Thunar Samba plugin may be missing, it was just packaged recently, not sure if that is the problem or not.
Can you see if it’s installed?

@agnivo007 @SwampRabbit that thunar function used to call system-config-samba, which is not longer available due to the migration away from python 2. Thanks for finding the bogus thunar entry.

which brings up...is there something to replace the function with?

Posted: **Sat Jul 31, 2021 3:51 pm**

Why is the default configuration "User password (sudo) for admin tasks?

The Tramp

Posted: **Sat Jul 31, 2021 4:01 pm**

You can switch back to su in Tweak.

Posted: **Sat Jul 31, 2021 4:04 pm**

demo, root,
possibly, I think - it worked last night.

Posted: **Sat Jul 31, 2021 4:04 pm**

which brings up...is there something to replace the function with?

Filezilla?

Posted: **Sat Jul 31, 2021 4:13 pm**

Installed on a ThinkPad. TouchPad is a little jumpy but it is like that in Windows, too. I put in %P in the last clock property's field to get AM/PM. Some things are new and a few older things are in different places but all in all, I can't find much to complain about. If you decide to change the sudo default to the way it was before, who do I write the check to?

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_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: LENOVO product: 20B20011US v: ThinkPad Edge E545 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 20B20011US v: 0B98401 Pro serial: <filter> UEFI [Legacy]: LENOVO 
           v: HRET30WW (1.18) date: 04/24/2018 
Battery:   ID-1: BAT0 charge: 31.3 Wh condition: 31.6/38.9 Wh (81%) volts: 10.8/10.8 
           model: SANYO 45N1043 type: Li-ion serial: <filter> status: Unknown 
CPU:       Topology: Dual Core model: AMD A6-5350M APU with Radeon HD Graphics bits: 64 
           type: MCP arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 
           microcode: 600111F L2 cache: 1024 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 11578 
           Speed: 1377 MHz min/max: 1400/2900 MHz boost: enabled Core speeds (MHz): 1: 1317 
           2: 1290 
           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: AMD Richland [Radeon HD 8450G] vendor: Lenovo driver: radeon v: kernel 
           bus ID: 00:01.0 chip ID: 1002:9995 
           Display: x11 server: X.Org 1.20.11 driver: ati,radeon 
           unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz 
           OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.10.0-8-amd64 LLVM 11.0.1) 
           v: 4.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes 
Audio:     Device-1: AMD Trinity HDMI Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:01.1 chip ID: 1002:9902 
           Device-2: AMD FCH Azalia vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1022:780d 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo 
           driver: r8169 v: kernel port: 2000 bus ID: 01:00.0 chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Realtek RTL8188EE Wireless Network Adapter vendor: Lenovo driver: rtl8188ee 
           v: kernel port: 1000 bus ID: 02:00.0 chip ID: 10ec:8179 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 232.89 GiB used: 5.50 GiB (2.4%) 
           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: 3B6Q scheme: MBR 
Partition: ID-1: / raw size: 115.90 GiB size: 113.52 GiB (97.95%) used: 5.50 GiB (4.8%) fs: ext4 
           dev: /dev/sda4 
Sensors:   System Temperatures: cpu: 57.6 C mobo: N/A 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://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
           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
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 191 Uptime: 1h 41m Memory: 6.93 GiB used: 1.06 GiB (15.3%) 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

Posted: **Sat Jul 31, 2021 4:53 pm**

Agree, SwampRabbit gave the tip, MX Tweak --> Other_check the radio button

Changes to a classic root PW model. Which I prefer.
It was the Mepis and MX way earlier, right? Am I remembering correctly?

The question is which should be default. I would vote root.
I realize the devs cant ask for votes on everything.

But PhantomTramp asks a fair question.

Testing update,
Over two days of heavy use,installing, took another 23 synapic upgrades. Reboots, sleep and wake, heavy data transfer, has a real Debian stable feel to it, but with all the nice toys and tools added on.

A remarkable beta, worthy of a Warren beta level

Posted: **Sat Jul 31, 2021 5:14 pm**

..worthy of a Warren beta level..

Hear, hear!

EDIT: https://grammarist.com/spelling/hear-hear/

Posted: **Sat Jul 31, 2021 5:15 pm**

dolphin_oracle wrote: Sat Jul 31, 2021 2:35 pm
SwampRabbit wrote: Sat Jul 31, 2021 1:04 pm @agnivo007 the Thunar Samba plugin may be missing, it was just packaged recently, not sure if that is the problem or not.
Can you see if it’s installed?
@agnivo007 @SwampRabbit that thunar function used to call system-config-samba, which is not longer available due to the migration away from python 2. Thanks for finding the bogus thunar entry.

which brings up...is there something to replace the function with?

So how do I set up a network share/folder on mx 21 host? Is the important feature being permanently dropped? How does upstream bullseye handle this? Instead of thunar rt click, we could setup shares using another app in mx19 if I remember. Please elaborate, have been bugged a lot by this on mx19kde systemd too. Hoped network sharing would work well this time.

Posted: **Sat Jul 31, 2021 5:46 pm**

@agnivo007 upstream debian tells you to edit smb.conf directly.

we are looking into it.

Posted: **Sat Jul 31, 2021 6:25 pm**

I think we should stay, with the change to sudo as default. It took me a day to get my brain reprogrammed. Older Mepis users <,hand in air> know what they liked AND know how to change it.

Posted: **Sat Jul 31, 2021 6:25 pm**

hello dolphin_oracle
firefox 90.0.2-mozillabinaries-mx21+1(mx)

Right-click in firefox web page
context-menu
behavior; feels click upon release of right-click.

it is not the same right-click as in version 90.0.2-mx19+1

Posted: **Sat Jul 31, 2021 8:27 pm**

Jerry3904 wrote: Sat Jul 31, 2021 6:25 pm I think we should stay, with the change to sudo as default. It took me a day to get my brain reprogrammed. Older Mepis users <,hand in air> know what they liked AND know how to change it.

So please tell me where the root password is needed besides loging into the system as root and changing from sudo to su or the reverse. I have not tried everything but then I will stick with su. Why not just make your password and root the same? So are we become like more widows?

Posted: **Sat Jul 31, 2021 8:52 pm**

towwire wrote: Sat Jul 31, 2021 8:27 pm
Jerry3904 wrote: Sat Jul 31, 2021 6:25 pm I think we should stay, with the change to sudo as default. It took me a day to get my brain reprogrammed. Older Mepis users <,hand in air> know what they liked AND know how to change it.
So please tell me where the root password is needed besides loging into the system as root and changing from sudo to su or the reverse. I have not tried everything but then I will stick with su. Why not just make your password and root the same? So are we become like more widows?

its not needed unless you want it to be. also, you do not have to even set a root password in the installer. if you don't the root account will be disabled. which some folks like.

this also gets us in line with both debian and antiX's defaults.

Posted: **Sat Jul 31, 2021 11:01 pm**

@dolphin_oracle at the moment, entering no password for root runs this: passwd -d root
I believe this doesn't lock out the root account, but allows you to log into root without a password.

Posted: **Sun Aug 01, 2021 12:07 am**

I have just had some fun with MX21 beta 1 64bit. So far everything looks to be like MX19.4 with a few differences which have already been discussed here. Now the thing that struck me almost instantly was the "window manager" themes setting in the XFCE settings panel. While you can see the selection of themes, when you click on one them or another you do not get a visual confirmation the theme is applied as any open windows do not get affected. Also, Thunar and Firefox so far as I know and noticed, stay with a thick tall GNOME like Window title bar style instead of the selected Window manager theme. So for instance, I select DEFAULT as my window manager theme, all newly opened apps like clementine and VLC player will have the new look but Firefox and Thunar are stuck with this thick tall top title bar, no change! That is not an MX issue but a XFCE 4.16 issue I am thinking..

So far all the key functions I look for in MX are still there with only the sudo being implemented by default having you use your user password for all options and settings that normally require a root password instead. While this is very convenient it can be a security risk but I have a feeling, only on publicly accessible computers and not so much your private computer in your man cave or she shed

I did not try to install or uninstall things other than set my visual preferences and I did test the thunar volume management feature and it still works so I do not know what this disk management that is missing is.. Frankly gparted, volume management and gsmartmon tools are still working in MX21 beta 1 so I am confused about the missing disk management??

I saw alot of apps that were testing repo in MX19 being as standard repo apps now.. A wonderful thing!

I did not try the custom respin iso snapshot feature yet but I will do so in a few days when I have more time and will report on that.

So far, great work MX team!! Loving the MX goodness that has moved up to Bullseye!

Posted: **Sun Aug 01, 2021 12:12 am**

davemx wrote: Thu Jul 29, 2021 2:02 pm
dolphin_oracle wrote: Thu Jul 29, 2021 1:49 pm

we need your /var/log/minstall.log please. it will have been copied to the installed system.
Can't help with that. I initially thought that the problem was elsewhere so I installed another Linux over it in a vain attempt to get access to my other partitions. I didn't realise that they were empty!

@davemx we think we found the issue with wiping partitions. thanks for the report. this one took awhile. only affected partitions mounted under /media. partitions mounted under /mnt were not affected.

Posted: **Sun Aug 01, 2021 12:15 am**

AK-47 wrote: Sat Jul 31, 2021 11:01 pm @dolphin_oracle at the moment, entering no password for root runs this: passwd -d root
I believe this doesn't lock out the root account, but allows you to log into root without a password.

confirmed. that's not what I thought was supposed to happen, obviously.

Posted: **Sun Aug 01, 2021 12:48 am**

I'll be updating this post with my observations so that it's easy to track.

Bug report 1: Samba feature missing: (noted by dev)
Broken thunar share on network functionality. Installing thunar extension doesn't help either. No standalone samba app as alternative.

Bug report 2: Weird vanishing panel:
Choose a menu item say brave browser from menu>rt click>add to panel. Then hover over added item in panel>rt click>remove (yes)>full panel vanishes. Relogin needed to get back panel.

Bug report 3: Wallpaper at start should be in "stretch mode":
Affects custom monitor resolution. After login, wallpaper is shown in tiled way, then later stretches to full screen when loading of system is complete. Looks odd and particularly visible for longer period on a weaker system than newer, latest ones. Design inconsistency IMO.

Bug report 4: Default theme matcha odd color scheme:
Appearance> list of themes. Hovering on list items is highlighted in black/grey that's difficult to read.

Bug report 5: Whisker menu unusual backtracking movement:
When menu button clicked or activated by key, whisker menu appears, then shifts leftward a few pixels to "snap-on" to panel creating a backtracking movement that's weird to the eye.
Something with shadows/compositor setting? Visible delay on old systems in painting the menu, is this latency adjustable? Maybe saw this in MX19 too.

Bug? report 6: Hddtemp notice for sensors plugin:
Thought this was to be resolved on a default install as per earlier forum conversations, by changing hddtemp permissions. Adding sensors plugin to panel still throws up that old notice and suggests the dirty hack.

Question 1: Is the widely known infamous xfce4-screensaver package and lock issue thought about in this beta build?

Posted: **Sun Aug 01, 2021 1:37 am**

Small interface things:
No drop shadows under non-CSD windows with xfwm compositor;
Compton and CSD windows are incompatible (is it still worth including this?);
Root Thunar is non-CSD, which seems odd.

Posted: **Sun Aug 01, 2021 1:59 am**

Added report#6 viewtopic.php?p=646560#p646560

Posted: **Sun Aug 01, 2021 2:11 am**

pianokeyjoe wrote: Sun Aug 01, 2021 12:07 am I have just had some fun with MX21 beta 1 64bit. So far everything looks to be like MX19.4 with a few differences which have already been discussed here. Now the thing that struck me almost instantly was the "window manager" themes setting in the XFCE settings panel. While you can see the selection of themes, when you click on one them or another you do not get a visual confirmation the theme is applied as any open windows do not get affected. Also, Thunar and Firefox so far as I know and noticed, stay with a thick tall GNOME like Window title bar style instead of the selected Window manager theme. So for instance, I select DEFAULT as my window manager theme, all newly opened apps like clementine and VLC player will have the new look but Firefox and Thunar are stuck with this thick tall top title bar, no change! That is not an MX issue but a XFCE 4.16 issue I am thinking..
...

From what I can see, this seems to be caused by the gtk-nocsd package, which gives users (under the MX tweak >> Others tab) the choice to add a xfwm theme window border around those unabashedly CSD gtk apps like Archive Manager, gthumb or Simple Scan.

I discovered this because I've been trying different themes in an alpha1 iso VM all this while (my PC is old school MBR legacy BIOS and installer testing for UEFI at this stage is not my focus) , which does not come with the gtk-nocsd package. Without it:

1. Thunar file manager main window will follow whatever xfwm theme you choose [the thunar preferences/settings windows though will not)
2. any other gtk3 app that still chooses to have a traditiional look (eg geany) and doesn't come with the hardcore CSD look (see the 3 programs I listed above) will follow xfwm theme.

Then I realised from this feedback thread that @dolphin_oracle had added the noCSD option to MX Tweak. So I installed the gtk-nocsd package to continue my trialing of themes so that my VM is more faithful to current beta.

That made a HUGE difference.

Say you stick to the default setting with gtk-nocsd package installed, ie for CSD apps to use their own CSD theming:

If a gtk theme - and most modern gtk themes do - includes a built-in "fake" version of the included xfwm theme (since their themes are used in other DEs besides XFCE), then switching the xfwm theme won't change the look of the gtk3 app. It'll still use the baked in gtk3 theme's window decorations. That's what happened to Thunar. The main window of Thunar is still using your current gtk theme's window borders that were made to appear to have a xfwm look. It's no longer using the xfwm theme you set. So it will get its window border look from the gtk3 theme and not the xfwm theme. This seems to be caused by the gtk-nocsd package being installed.

However, all your Qt apps (eg all the MX apps, clementine, etc) will change to the xfwm theme you choose, leaving to non-matching window decorations between gtk3 and Qt applications.

RAM usage of these themes also appeared to increase once I installed the no-csd package.

If you then choose to disable CSD themeing from MX-Tweak, so that noCSD is in use, yes, you get your xfwm borders back on Thunar main window and other gtk3 apps that allow you to do that, and for hardcore CSD apps you get the xfwm theme surrounding the existing CSD thick style window bar.

However from what I see, RAM consumption increases even more.

My view is that the gtk-nocsd package causes more problems than it solves.

Just having it on the system messes with xfwm choices for gtk3 apps that actually were allowing xfwm themes to be used. I think we should not have it preinstalled in MX21. That way, only hardcore CSD apps will have the thick window bar, and other gtk3 apps can still use xfwm themes of your choice, including Thunar main window and geany. Then there will be less change from MX19.

Things like Archive Manager and Simple scan have been default on MX since MX 16, I think, and have been hardcore CSD apps all this time. I don't see why users should suddenly be upset if they remain as that in MX21.

Posted: **Sun Aug 01, 2021 2:23 am**

I finally got around to testing MX-21b1 on a live USB with persist_all. It's pretty snappy except for Firefox which is rather slow. A remaster and the subsequent rsync upon rebooting were also very slow, but then I am using one of my old 16GB USB2 sticks.

The default conky's hard to see against the default wallpaper (which I love BTW.) I suggest using MX Cowan more sys small instead as the colors are darker, even if they don't match the wallpaper.

It works OOTB on my Ryzen 7 system. PulseAudio even defaulted to my correct sound card, the one built in to the motherboard, rather than HDMI audio. Sound works, video's at the correct 1920x1080 resolution, Ethernet works. My RTL8821CU USB wifi dongle doesn't work though: lsusb shows it but Network Manager doesn't have wifi available. It still needs a driver installed.

At this point I wonder is a beta 2 will even be necessary. Good job, everyone!

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash lang=en_US kbd=us 
           tz=Asia/Manila persist_all 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450M-PRO GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 3002 date: 03/11/2021 
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: 114982 
           Speed: 2196 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2195 
           2: 2195 3: 2195 4: 2195 5: 2195 6: 2195 7: 2195 8: 2196 9: 2194 10: 2196 11: 2195 
           12: 2196 13: 2196 14: 2196 15: 2191 16: 2197 
           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 Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] 
           driver: amdgpu v: kernel bus ID: 07:00.0 chip ID: 1002:67ef 
           Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,vesa tty: N/A 
           OpenGL: 
           renderer: Radeon RX 560 Series (POLARIS11 DRM 3.40.0 5.10.0-8-amd64 LLVM 11.0.1) 
           v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] 
           driver: snd_hda_intel v: kernel bus ID: 07:00.1 chip ID: 1002:aae0 
           Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 09:00.4 chip ID: 1022:1487 
           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: 04:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Realtek 802.11ac NIC type: USB driver: usb-network bus ID: 1-6:2 
           chip ID: 0bda:c811 serial: <filter> 
Drives:    Local Storage: total: 4.22 TiB used: 236.16 GiB (5.5%) 
           ID-1: /dev/nvme0n1 vendor: PNY model: CS3030 500GB SSD size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: CS303321 scheme: GPT 
           ID-2: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 61.3 scheme: GPT 
           ID-3: /dev/sdb vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5425 rpm serial: <filter> 
           rev: 0001 
           ID-4: /dev/sdc type: USB vendor: Toshiba model: TransMemory size: 14.45 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: GPT 
Partition: ID-1: / raw size: N/A size: 24.99 GiB used: 6.2 MiB (0.0%) fs: overlay 
           source: ERR-102 
Sensors:   System Temperatures: cpu: 45.4 C mobo: N/A gpu: amdgpu temp: 46 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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.pregi.net/mx-linux-packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 338 Uptime: 17m Memory: 31.33 GiB used: 1.46 GiB (4.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

Next test: a frugal install.

Posted: **Sun Aug 01, 2021 2:28 am**

agnivo007 wrote: Sun Aug 01, 2021 12:48 am Bug report 2: Weird vanishing panel:
Choose a menu item say brave browser from menu>rt click>add to panel. Then hover over added item in panel>rt click>remove (yes)>full panel vanishes. Relogin needed to get back panel.

Bug report 5: Whisker menu unusual backtracking movement:
When menu button clicked or activated by key, whisker menu appears, then shifts leftward a few pixels to "snap-on" to panel creating a backtracking movement that's weird to the eye.
Something with shadows/compositor setting? Visible delay on old systems in painting the menu, is this latency adjustable? Maybe saw this in MX19 too.

Bug? report 6: Hddtemp notice for sensors plugin:
Thought this was to be resolved on a default install as per earlier forum conversations, by changing hddtemp permissions. Adding sensors plugin to panel still throws up that old notice and suggests the dirty hack.

2) I can confirm something odd is happening when doing this, but for me it worked once, then the second time the panel froze. Already looking at updating Xfce components to hopefully fix some issues with the panel.

5) can't confirm this, no such issues using a mouse or via keyboard on my end, would like someone else to confirm

6) make sure you're updated, a update was pushed for the sensors plugin recently. I tested the sensors plugin on two systems without issue prior to sending the new version up
I can check again, but someone else will probably have the opportunity before I do

Also, please don't post just to link a updated post that's two posts up.... its just silly, it creates unneeded posts, and it makes the horrible process of tracking issues in a forum thread harder.

A side note for anyone testing.... please:
- keep your Beta install updated, not only are MX fixes coming down but Debian Bullseye fixes are coming down (there's technically 2 Betas being worked here)
- READ the whole thread, try not to post about issues already reported if you can
- if you're testing on hardware and have a hardware item to report, post your QSI and post anything relevant to it
- if you're testing in a VM, verify on hardware before you report
- you can also report bugs/issues here https://bugs.mxlinux.org/buglist.cgi?ch ... eldfrom=7d (noticed how many have NOT been reported in the last week?)
- feel free to also identify or find the solution/options for the item/issue you report (it isn't like dolphin_oracle fixes all this stuff as his full time job, doesn't have a family, and gets paid for it all

)

Posted: **Sun Aug 01, 2021 2:39 am**

Firefox is fast and fine on a frugal_static installation on my spare 120GB SATA SSD so the prior slowness was apparently due to the USB2.0 stick.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash lang=en_US kbd=us 
           tz=Asia/Manila frugal_static gfxsave 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450M-PRO GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 3002 date: 03/11/2021 
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: 114984 
           Speed: 2187 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2201 
           2: 2192 3: 2189 4: 2195 5: 2195 6: 2194 7: 2196 8: 2195 9: 2194 10: 2192 11: 2195 
           12: 2195 13: 2196 14: 2194 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 Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] 
           driver: amdgpu v: kernel bus ID: 07:00.0 chip ID: 1002:67ef 
           Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
           OpenGL: 
           renderer: Radeon RX 560 Series (POLARIS11 DRM 3.40.0 5.10.0-8-amd64 LLVM 11.0.1) 
           v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] 
           driver: snd_hda_intel v: kernel bus ID: 07:00.1 chip ID: 1002:aae0 
           Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 09:00.4 chip ID: 1022:1487 
           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: 04:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Realtek 802.11ac NIC type: USB driver: usb-network bus ID: 1-6:2 
           chip ID: 0bda:c811 serial: <filter> 
Drives:    Local Storage: total: 4.22 TiB used: 234.52 GiB (5.4%) 
           ID-1: /dev/nvme0n1 vendor: PNY model: CS3030 500GB SSD size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: CS303321 scheme: GPT 
           ID-2: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 61.3 scheme: GPT 
           ID-3: /dev/sdb vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5425 rpm serial: <filter> 
           rev: 0001 
           ID-4: /dev/sdc type: USB vendor: Toshiba model: TransMemory size: 14.45 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: GPT 
Partition: ID-1: / raw size: N/A size: 7.78 GiB used: 4.9 MiB (0.1%) fs: overlay source: ERR-102 
Sensors:   System Temperatures: cpu: 44.2 C mobo: N/A gpu: amdgpu temp: 45 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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.pregi.net/mx-linux-packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 358 Uptime: 10m Memory: 31.33 GiB used: 1.29 GiB (4.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

EDIT: I just noticed that Window Buttons was missing from the panel, which I had moved to the bottom using MX Tweak. I could have sworn there were Window Buttons when I first booted and when the panel was on the left. I wonder what happened? What I've done so far: booted live with persist_all, changed my MX mirror to the LA MX one, checked for and installed updates, changed my conky, did a personal remaster, rebooted, posted my QSI from the persistent live USB, rebooted, did a frugal_static install. (Also my mirror change didn't survive and was set back to pregi.net in the Philippines, probably because a frugal install is, well, an install of sorts.)

EDIT 2: Another thing I noticed is that LUM wants to burn the MX-21 beta1 ISO in dd mode by default rather than in full-featured mode. I have to manually change it.

Posted: **Sun Aug 01, 2021 2:40 am**

Should I resubmit reports to the tracker? I aggregated and updated the issues to a single post as this thread will get long and will surely lose track. That's not good for you guys as it seems.

Yes, I keep things updated; thanks for mentioning. Yet, currently sensors plugin behave as I have reported.

Is it OK to report about missing wifi dongle support (RTL8811) that's very popular and sold in millions worldwide over last 7 years? Need to compile driver manually from git and install on MX19 too.
Ref: viewtopic.php?t=64013

Posted: **Sun Aug 01, 2021 2:53 am**

@agnivo007 well what you got going on with that one post should be ok, it’s good the centralize it, but if it gets to huge maybe not… I guess just use your best judgement.

I don’t think you have to open bug reports now, honestly I should let d.o. or Adrian make that call.

I thought we took care of the RTL8811, obviously not though. Maybe that was for AHS… will follow up.

I just posted that list of stuff to try to remember when testing the Beta because we’re already 18 pages into it and some stuff people brought up aren’t bugs, can’t be confirmed, or are kinda vague. That’s all.

Posted: **Sun Aug 01, 2021 3:01 am**

Praise the good time and effort of the team... I'm trying in my own way. Thanks for everything so far (and future too).
Yes, much of half baking will be done fully at the end I hope.

Posted: **Sun Aug 01, 2021 3:21 am**

JayM wrote: Sun Aug 01, 2021 2:39 am EDIT: I just noticed that Window Buttons was missing from the panel, which I had moved to the bottom using MX Tweak. I could have sworn there were Window Buttons when I first booted and when the panel was on the left. I wonder what happened?

Window Buttons have been replace by Doclike.

https://mxlinux.org/wiki/docklike-taskbar/

Chris

Posted: **Sun Aug 01, 2021 4:34 am**

chrispop99 wrote: Sun Aug 01, 2021 3:21 am
JayM wrote: Sun Aug 01, 2021 2:39 am EDIT: I just noticed that Window Buttons was missing from the panel, which I had moved to the bottom using MX Tweak. I could have sworn there were Window Buttons when I first booted and when the panel was on the left. I wonder what happened?
Window Buttons have been replace by Doclike.

https://mxlinux.org/wiki/docklike-taskbar/

Chris

Oh, neat! From a quick glance I think I see how it works, kind of a combination of panel launchers and Window buttons? If one of the apps in Doclike is opened it adds a little blue doomaflotchy at the right of the icon. I'll have to play with it some more tomorrow and figure out how to add apps to it.

Posted: **Sun Aug 01, 2021 4:54 am**

as usual, right click is your friend. :)

Posted: **Sun Aug 01, 2021 5:03 am**

asqwerth wrote: Sun Aug 01, 2021 4:54 am as usual, right click is your friend. :)

That's what i thought, but I had to boot back into MX-19.4 so Viber would be available as SWMBO will probably want to message me soon and I can't abide Viber on smartphones. Besides, I want to watch airplanes flying around on my ADS-B software. :) (And I need to stop having fun with MX-21 (hey, it rhymes!) and think about preparing dinner.)

Edit: right-clicking didn't help but searching the web for "docklike taskbar" how to add pinned apps did, taking me to https://soundwrx.net/how-to-install-and ... inux-hint/. Basically, when you open an application from the Whisker Menu its icon will appear in the Docklike Taskbar, then you right-click on that icon and click "pin to taskbar" to create the functional equivalent of a launcher on the panel. I was trying to right-click on the icons in the Whisker Menu and pin them, but the proggies have to be running first.

Posted: **Sun Aug 01, 2021 6:23 am**

m_pav wrote: Fri Jul 30, 2021 6:02 pmOne issue with re-using the swap file though is after unlocking and re-using it through the installer, you will end up with a password prompt to unlock every encrypted partition you reused through the installer, so if you reused 2 partions, you will have to type each partitions password at login and if you reused 3 encrypted partitions, you will be asked 3 times at boot for the password for each partition.

This may be a either a bug or an omission in the new installer, or an error in the process I tested with. Maybe others can chip in here to give some clarity.

Sounds like something went wrong with adding the common system key material to your volumes. Do you have the /var/log/minstall.log and /etc/crypttab files handy?

Posted: **Sun Aug 01, 2021 7:18 am**

Please make a choice the targeted initrd like in original Debian 11 by expert install mode:

I really like MX-linux, but because of the impossibility of such a choice, I choose Debian “bullseye”! But maybe I'm wrong. The point is to make the kernel as lightweight as possible, without unnecessary drivers. Please clarify this point. Am I right or wrong?

Posted: **Sun Aug 01, 2021 7:30 am**

I installed MX21 beta with standard installation except for amending to separate home partition, and I know see that I have a swap partition of 7.61GB.
Why so large and how can I amend without reinstalling. I tried in Gparted having turned the swap off and it failed to execute!

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 usbcore.autosuspend=-1
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_beta1_x64 Wildflower July 27 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: Hewlett-Packard product: 500-141ea v: N/A serial: <filter>
Chassis: type: 3 serial: <filter>
Mobo: MSI model: 2AE0 v: 1.0 serial: <filter> UEFI: AMI v: 80.46 date: 10/03/2013
CPU: Topology: Quad Core model: AMD A8-6500 APU with Radeon HD Graphics bits: 64 type: MCP
arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 microcode: 6001119
L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 27944
Speed: 3493 MHz min/max: 1700/3500 MHz boost: enabled Core speeds (MHz): 1: 3493
2: 3493 3: 3493 4: 3493
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: AMD Richland [Radeon HD 8570D] vendor: Hewlett-Packard driver: radeon
v: kernel bus ID: 00:01.0 chip ID: 1002:990e
Device-2: AMD Caicos XT [Radeon HD 7470/8470 / R5 235/310 OEM] vendor: Micro-Star MSI
driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:6778
Display: x11 server: X.Org 1.20.11 driver: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 5.10.0-8-amd64 LLVM 11.0.1)
v: 3.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes
Audio: Device-1: AMD FCH Azalia vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1022:780d
Device-2: DigiTech Lexicon Alpha type: USB driver: snd-usb-audio bus ID: 8-1:2
chip ID: 1210:000a
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Qualcomm Atheros AR8161 Gigabit Ethernet vendor: Hewlett-Packard
driver: alx v: kernel port: d000 bus ID: 02:00.0 chip ID: 1969:1091
IF: eth0 state: down mac: <filter>
Device-2: Qualcomm Atheros AR9485 Wireless Network Adapter
vendor: Hewlett-Packard AR9485/HB125 802.11bgn 1×1 Wi-Fi driver: ath9k v: kernel
port: d000 bus ID: 05:00.0 chip ID: 168c:0032
IF: wlan0 state: up mac: <filter>
Device-3: NetGear WNDA3100v2 802.11abgn [Broadcom BCM4323] type: USB
driver: usb-network bus ID: 1-1:2 chip ID: 0846:9011
Drives: Local Storage: total: 279.46 GiB used: 14.63 GiB (5.2%)
ID-1: /dev/sda vendor: Seagate model: ST3300820SCE size: 279.46 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: E temp: 38 C
scheme: GPT
Partition: ID-1: / raw size: 18.96 GiB size: 18.49 GiB (97.54%) used: 6.25 GiB (33.8%) fs: ext4
dev: /dev/dm-0
ID-2: /boot raw size: 512.0 MiB size: 487.2 MiB (95.16%) used: 103.6 MiB (21.3%)
fs: ext4 dev: /dev/sda2
ID-3: /home raw size: 252.07 GiB size: 247.05 GiB (98.01%) used: 8.27 GiB (3.3%)
fs: ext4 dev: /dev/dm-2
ID-4: swap-1 size: 7.61 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60)
cache pressure: 100 (default) dev: /dev/dm-1
Sensors: Missing: Required tool sensors not installed. Check --recommends
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
Active apt repos in: /etc/apt/sources.list.d/megasync.list
1: deb https://mega.nz/linux/MEGAsync/Debian_testing/ ./
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 236 Uptime: 23m Memory: 5.01 GiB used: 1.48 GiB (29.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
[/code]
Thanks
gmt

Posted: **Sun Aug 01, 2021 7:45 am**

simwin wrote: Sun Aug 01, 2021 7:18 am Please make a choice the targeted initrd like in original Debian 11 by expert install mode:
I really like MX-linux, but because of the impossibility of such a choice, I choose Debian “bullseye”! But maybe I'm wrong. The point is to make the kernel as lightweight as possible, without unnecessary drivers. Please clarify this point. Am I right or wrong?

This thread is for beta testing and not for proposing reworks and extra options on the installer. Open a new thread or a issue in github's gazelle installer asking if this option is even viable or even of interest (considering that MX has a snapshot tool, and we don't know if this change would affect the snapshot tool).
Also, it doesn't make the "kernel" lightweight, but the initrd file associated to the booting kernel. On my computer non of them take more than 40MBs. I don't see you saving that little space for the initrd file force you to choose Debian with less driver compatibility and less specialized tools vs MX-feature-rich Linux.

Posted: **Sun Aug 01, 2021 7:56 am**

nXecure wrote: Sun Aug 01, 2021 7:45 amAlso, it doesn't make the "kernel" lightweight, but the initrd file associated to the booting kernel. On my computer non of them take more than 40MBs, so I don't see you saving that much space force you to choose Debian with less driver compatibility and less specialized tools vs MX-feature-rich Linux.

Perhaps You are right... Thank you!!!

Posted: **Sun Aug 01, 2021 8:08 am**

@asqwerth Thankyou for pointing out the Thick window border issue! Seeing as I am all about looks in Linux(my main reason to try Linux in the past in the first place), that was my biggest glaring issue. So what is this CSD? I keep seeing that term used here but I have no clue what that is at quick reading glance. What I DO know, is GNOME 3 based apps do not follow XFWM theme scheme or ANY WM theme scheme and hence I tend to try to stay away from most of those apps when I can. Are you saying that now GNOME 3 style theme overriding of gtk3 apps is present in MX21/Debian 11? So Thunar file manager and firefox are now both no longer Windowborder themeable by WMs in this new version of Linux? That sucks!

The package you speak of to use to override the GNOME 3 border on those GTK3 apps like Thunar and firefox, reminds me of Windowblinds in Windows 7. Yes it will use more ram. I need to find a filemanager as good as thunar that still lets me have the uniform look of what ever theme I apply in what ever DE/WM I choose. I like XFCE as my DE along with CDE desktop which is an older DE with all of its own themes, borders,apps,etc. Windowmanagers like Windowmaker,Enlightenment and MWM which I love too will look broken with this CSD app issue. MPV and BLEACHBIT are apps that do not theme well either.. I have lived with those for a while but they are not system critical or main use apps like file managers and web browsers though.. so this sucks. Well time to search alternate apps to keep things looking right or I just stick with MX19 for years as most of my custom respins and snapshots for embedding MX to SSD readonly drives is with MX19. I am going to try more options and tweaks,etc in MX21 along with snapshots and finally installs later as time allows but so far I would say other than the Looks issue, MX21 seems solid.

Posted: **Sun Aug 01, 2021 8:18 am**

I'm saying it started happening to my alpha VM only after I installed gtk-nocsd package which is preinstalled in beta1 but not in alpha.

Posted: **Sun Aug 01, 2021 8:26 am**

@gmt PLEASE read the forum rules and don't copy/paste system info, log file contents, terminal outputs and so on as plain text. Now you get to edit your post and fix it.

Please edit your post using the pencil icon

to wrap the information inside of code tags as per the forum rules (which please read.) Example: [code]log file contents, configuration file contents and terminal text go here[/code]
Code: Select all
to make it look like this, which is a lot easier to read for large amounts of text:
1. It really stands out as being separate from the text that you're typing due to the different background and font colors
2. It also puts it inside of its own little frame with its own scrollbars, making it easier to navigate.
To do this, select the text by dragging your mouse over it while holding the left button down then click the </> icon in the forum's editor's toolbar and click the Submit button.

Thanks.

Posted: **Sun Aug 01, 2021 8:29 am**

Let me clarify my previously mangled explanation. @pianokeyjoe

Some gtk3 apps still allow xfce to apply xfwm themes for window decorations. Only hardcore csd applications (yes, many originating from gnome) have their own client side decorations that ignore xfwm.

Most gtk themes nowadays have built-in window decorations within their gtk theming files that look similar to their provided xfwm theme.

It appears to me that once gtk-nocsd is installed and enabled, even gtk3 apps (like geany and thunar main window) that actually permit xfwm to be used in xfce, no longer look to xfwm but the inbuilt gtk3 window decoration.

So, switching the xfwm theme won't change the look of those gtk3 apps.

But your Qt apps will change to the xfwm theme you choose, leaving to non-matching window decorations between the 2 types of applications.

RAM usage of these themes also went up once I installed the no-csd package.

Posted: **Sun Aug 01, 2021 9:44 am**

asqwerth wrote: Sun Aug 01, 2021 8:29 am Let me clarify my previously mangled explanation. @pianokeyjoe

Some gtk3 apps still allow xfce to apply xfwm themes for window decorations. Only hardcore csd applications (yes, many originating from gnome) have their own client side decorations that ignore xfwm.

Most gtk themes nowadays have built-in window decorations within their gtk theming files that look similar to their provided xfwm theme.

It appears to me that once gtk-nocsd is installed and enabled, even gtk3 apps (like geany and thunar main window) that actually permit xfwm to be used in xfce, no longer look to xfwm but the inbuilt gtk3 window decoration.

So, switching the xfwm theme won't change the look of those gtk3 apps.

But your Qt apps will change to the xfwm theme you choose, leaving to non-matching window decorations between the 2 types of applications.

RAM usage of these themes also went up once I installed the no-csd package.

I went ahead and tried MX21 tweak and was able to uncheck the box for client side decorations(CSD lol,found it!)and that disabled the annoying non XFWM theme overrides. Now all my windows look uniform as they should. Mind you I only stayed with XFCE and did not try out any other DE or WM. But since I normally default to XFCE anyways, that is a good workaround. The ram usage is only higher due to having to override the annoying GTK3/GNOME look. Since I have plenty o ram, I accept the trade off. For my future MX snapshots for embedding and so on, I will just have to select apps that will have a uniform look and feel to keep things looking right and light on ram too. But for now, I am happy. Thankyou sir, for the direction!

Posted: **Sun Aug 01, 2021 9:56 am**

Is there a reason for gscan2pdf being left off the ISO? It's no bother to install it, so it's not a major issue, but I find it much the best and most comprehensive scanning application.

My first major hiccup. The machine doesn't recover from Suspend and I had to power off. This is an issue for me at present - I have to wait some hours after shutdown before the machine will restart. I'm running 24/7 but using Suspend overnight.

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_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASRock model: FM2A88X-ITX+ serial: <filter> 
           UEFI: American Megatrends v: P2.10 date: 01/17/2014 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K270 serial: <filter> 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M185 serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: Quad Core model: AMD A8-6500 APU with Radeon HD Graphics bits: 64 type: MCP 
           arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 microcode: 6001119 
           L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 27950 
           Speed: 2686 MHz min/max: 1700/3500 MHz boost: enabled Core speeds (MHz): 1: 2423 
           2: 2688 3: 3344 4: 3305 
           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: AMD Richland [Radeon HD 8570D] vendor: ASRock driver: radeon v: kernel 
           bus ID: 00:01.0 chip ID: 1002:990e 
           Display: x11 server: X.Org 1.20.11 driver: ati,radeon 
           unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.10.0-8-amd64 LLVM 11.0.1) 
           v: 4.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes 
Audio:     Device-1: AMD Trinity HDMI Audio vendor: ASRock driver: snd_hda_intel v: kernel 
           bus ID: 00:01.1 chip ID: 1002:9902 
           Device-2: AMD FCH Azalia vendor: ASRock driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1022:780d 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: AzureWave 
           driver: ath9k v: kernel port: f100 bus ID: 01:00.0 chip ID: 168c:0034 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros QCA8171 Gigabit Ethernet vendor: ASRock driver: alx 
           v: kernel port: e000 bus ID: 03:00.0 chip ID: 1969:10a1 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 2.05 TiB used: 5.72 GiB (0.3%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Seagate model: ST1000DM005 HD103SJ size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: 00E5 scheme: MBR 
           ID-3: /dev/sdc vendor: Toshiba model: HDWD110 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: A8J0 scheme: MBR 
           ID-4: /dev/sde type: USB vendor: Lexar model: USB Flash Drive size: 3.66 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1100 scheme: MBR 
Partition: ID-1: / raw size: 30.00 GiB size: 29.36 GiB (97.87%) used: 5.72 GiB (19.5%) fs: ext4 
           dev: /dev/sda4 
           ID-2: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sdb11 
Sensors:   System Temperatures: cpu: 23.2 C mobo: N/A gpu: radeon temp: 18 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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 209 Uptime: 11m Memory: 6.71 GiB used: 668.9 MiB (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

Posted: **Sun Aug 01, 2021 10:02 am**

Is there a reason for gscan2pdf being left off the ISO? It's no bother to install it, so it's not a major issue, but I find it much the best and most comprehensive scanning application.

It's in MXPI, of course, but has been replaced by SimpleScan which is more intuitive and works wonderfully for most purposes.

Posted: **Sun Aug 01, 2021 10:08 am**

I would like to reinforce my previous comment about the quality of this first Beta. Minor issues aside, it's running very well on this machine and I've been using it as my workhorse for the last 3 days, switching back to MX-19 for the evenings for my auto backup to run.

Posted: **Sun Aug 01, 2021 10:13 am**

JayM wrote: Sun Aug 01, 2021 2:39 am

EDIT 2: Another thing I noticed is that LUM wants to burn the MX-21 beta1 ISO in dd mode by default rather than in full-featured mode. I have to manually change it.

I cannot duplicate that here.

Posted: **Sun Aug 01, 2021 10:15 am**

JayM wrote: Sun Aug 01, 2021 4:34 am
chrispop99 wrote: Sun Aug 01, 2021 3:21 am
JayM wrote: Sun Aug 01, 2021 2:39 am EDIT: I just noticed that Window Buttons was missing from the panel, which I had moved to the bottom using MX Tweak. I could have sworn there were Window Buttons when I first booted and when the panel was on the left. I wonder what happened?
Window Buttons have been replace by Doclike.

https://mxlinux.org/wiki/docklike-taskbar/

Chris
Oh, neat! From a quick glance I think I see how it works, kind of a combination of panel launchers and Window buttons? If one of the apps in Doclike is opened it adds a little blue doomaflotchy at the right of the icon. I'll have to play with it some more tomorrow and figure out how to add apps to it.

you got it. and the KDE release has the same setup with the KDE tasklist (actually their new default is like that).

Posted: **Sun Aug 01, 2021 10:18 am**

Jerry3904 wrote: Sun Aug 01, 2021 10:02 am
Is there a reason for gscan2pdf being left off the ISO? It's no bother to install it, so it's not a major issue, but I find it much the best and most comprehensive scanning application.
It's in MXPI, of course, but has been replaced by SimpleScan which is more intuitive and works wonderfully for most purposes.

Thanks, @Jerry3904. I'll continue with gscan2pdf.

Posted: **Sun Aug 01, 2021 10:19 am**

simwin wrote: Sun Aug 01, 2021 7:18 am Please make a choice the targeted initrd like in original Debian 11 by expert install mode:

I really like MX-linux, but because of the impossibility of such a choice, I choose Debian “bullseye”! But maybe I'm wrong. The point is to make the kernel as lightweight as possible, without unnecessary drivers. Please clarify this point. Am I right or wrong?

that option won't change the kernel but it might remove a bunch of ancillary packages. I don't think debian's installer recompiles the kernel. and anyway, given the flexible live system, I don't think that feature will be added.

Posted: **Sun Aug 01, 2021 10:38 am**

Hello Gaer Boy
"The machine doesn't recover from Suspend and I had to power off"
same thing here. I did cntrl+alt+backspace lose session and log-in.
it happens in a short time.
It happened during installation.
It was necessary to visit power manager settings to negate the power and display sleep
to get through the installation.
I tend to think it is more about display settings than power system. , because it sometimes returns with display not at full brightness(?)

Posted: **Sun Aug 01, 2021 10:44 am**

@JayM and for anyone else wanting to know about the new dock plugin, as always did you look at any MX documentation?

Seems like we kinda prepared for these questions
https://mxlinux.org/?s=Docklike

I know the MX Manual in the Beta is still for MX-19.2, the manual will be updated at some point.

MX Linux Forum

MX-21 beta 1 feedback thread

MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread

Re: MX-21 beta 1 feedback thread