MX-21 beta 1 feedback thread

[pianokeyjoe]

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!

[Gaer Boy]

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 

[Jerry3904]

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.

[Gaer Boy]

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.

[dolphin_oracle]

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.

[dolphin_oracle]

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).

[Gaer Boy]

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.

[dolphin_oracle]

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.

[i_ri]

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(?)

[SwampRabbit]

@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.