MX Linux Forum

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.

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?

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?

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

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.

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!!!

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

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.

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

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.