MX Linux Forum

Posted: **Mon Aug 23, 2021 8:25 am**

for feedback of the MX-21 KDE beta 1 iso. Details here:

https://mxlinux.org/blog/mx-21-kde-plas ... r-testing/

MOD: added link to Blog post

Posted: **Mon Aug 23, 2021 9:37 am**

initial boot from USB successful. Initial tests on basic configurations and common software, (Firefox, Yakuake and the like) with no problems. While I configure appearance heavily I do not install exotic software. Any installs are well known alternatives to the existing functional pre-installed software and additional widgets. I will report on any problems with these installations.

Posted: **Mon Aug 23, 2021 10:03 am**

First issue:
After downloading and installing an alternate wallpaper using system settings, No application would start. The any app would flash in the task manager and not start. I do not know if it was related to the wallpaper install. Obviously needs a confirmation by others. The only other changes made beforehand were font and panel sizes.

Posted: **Mon Aug 23, 2021 11:11 am**

signature link in the blog-post would need to be fixed

Posted: **Mon Aug 23, 2021 11:24 am**

I could not duplicate the problem I posted. The downloaded wallpaper was not installed after a reboot, so apparently some glitch occurred during the remaster.
viewtopic.php?p=649599#p649599

Posted: **Mon Aug 23, 2021 11:38 am**

fehlix wrote: Mon Aug 23, 2021 11:11 am signature link in the blog-post would need to be fixed

Fixed.

Posted: **Mon Aug 23, 2021 12:22 pm**

been waiting on this ..... thanks

as rich said.... the default wallpaper disappeared after booting but it was still present in the backgrounds folder and linked via the 'configured desktop and wallpaper' thingy

been playing with it for a few hours now .... installed my favorite apps and added the usual docks and stuff

i am really liking it so far and will probably just continue using it as my daily system

oh .... and as a surprising bonus ..... the rtl8821ce driver is finally included as default (in the kernel?) .... first time i haven't had to plug into the ethernet to install that driver on any distro

Posted: **Mon Aug 23, 2021 12:28 pm**

Minimize, maximize and close buttons on Firefox with KDE default theme on, are invisible.

More visible (though not perfect) on other themes.

Here is grey theme with icons more visible:
https://imgur.com/MuXB0JB

MX default theme looks good with Breeze Dark though:
https://imgur.com/VcmMVjA

Posted: **Mon Aug 23, 2021 12:44 pm**

junoluna wrote: Mon Aug 23, 2021 12:22 pm been waiting on this ..... thanks

as rich said.... the default wallpaper disappeared after booting but it was still present in the backgrounds folder and linked via the 'configured desktop and wallpaper' thingy

been playing with it for a few hours now .... installed my favorite apps and added the usual docks and stuff

i am really liking it so far and will probably just continue using it as my daily system

oh .... and as a surprising bonus ..... the rtl8821ce driver is finally included as default (in the kernel?) .... first time i haven't had to plug into the ethernet to install that driver on any distro

this one and the fluxbox iso should have the rtl88** driver package installed by default. All beta2 isos will also have it.

Posted: **Mon Aug 23, 2021 12:44 pm**

Minimize, maximize and close buttons on Firefox with KDE default theme on, are invisible.

I would agree that those buttons on unfocused windows are very difficult to see.

Posted: **Mon Aug 23, 2021 12:55 pm**

i am not seeing the mx updater icon anywhere in the beta ... only the discover updater

can't find apt-notifier-py in the entries list

Posted: **Mon Aug 23, 2021 1:12 pm**

Just tested a frugal install so far (on MBR-partitioned disk, ivy bridge era desktop), looking very nice !

Some preliminary remarks:

i am pretty sure i picked a keyboard layout (which is indeed active in my frugal session) but which was not activated (yet) through the frugal configuration dialogs, making it a tad difficult to change password etc
i _think_ i chose hwclock=local yet the clock was set to UTC
i noticed task switcher defaults to Breeze, *not* MX
with my ventoy key i could only successfully boot in UEFI mode, MBR ended with "cannot find antix/linuxfs"; this has probably more to do with ventoy than with the ISO, but it works in both modes with an MX19 iso so i mention it just in case

PS: forget the last point above, apparently this is a glitch in this particular Dell'sBIOS - I have booted two other systems in MBR/legacy mode with no issue.

But: the Dell is where i was willing to overwrite a partition with MX21, and the disk is MBR-partitioned. Can I boot the installation key in UEFI mode, start the installer without esp partition and without installing grub at the end ?

Posted: **Mon Aug 23, 2021 2:28 pm**

Opening local video files in various formats causes VLC to open and close very quickly several times before the video plays.

The problem doesn't happen with SMPlayer.

Chris

Posted: **Mon Aug 23, 2021 2:41 pm**

.mp3s open in VLC by default, rather than Clementine.

When Clementine is playing, there is a second icon in the tray named 'Media'.

Chris

Posted: **Mon Aug 23, 2021 3:07 pm**

chrispop99 wrote: Mon Aug 23, 2021 2:41 pm .mp3s open in VLC by default, rather than Clementine.

When Clementine is playing, there is a second icon in the tray named 'Media'.

Chris

thank you, I think I know where to make that change.

Posted: **Mon Aug 23, 2021 3:09 pm**

chrispop99 wrote: Mon Aug 23, 2021 2:28 pm Opening local video files in various formats causes VLC to open and close very quickly several times before the video plays.

The problem doesn't happen with SMPlayer.

Chris

can you remove the ~/.config/vlc configs and see if that makes any difference.

Posted: **Mon Aug 23, 2021 3:25 pm**

dolphin_oracle wrote: Mon Aug 23, 2021 3:09 pm
chrispop99 wrote: Mon Aug 23, 2021 2:28 pm Opening local video files in various formats causes VLC to open and close very quickly several times before the video plays.

The problem doesn't happen with SMPlayer.

Chris
can you remove the ~/.config/vlc configs and see if that makes any difference.

No difference.

Chris

Posted: **Mon Aug 23, 2021 3:26 pm**

junoluna wrote: Mon Aug 23, 2021 12:55 pm i am not seeing the mx updater icon anywhere in the beta ... only the discover updater

can't find apt-notifier-py in the entries list

The release announcement tells you Discover is used for updates.

Chris

Posted: **Mon Aug 23, 2021 4:17 pm**

Finally!!!! Thank you!

Installed in Virtualbox and played around to set things up the way I like them.

I found one annoyance - when I set localization to "Slovenija - slovenščina sl_SI" during setup or even after setup (System Settings -> Regional settings -> Formats), the system translations change to that language without adding or setting the language (only American English was installed). The workaround was to add "Slovenščina", move it to top, click apply, then move American English to top, again apply and then logout. After login everything was back to US English except for date/time, money... formats, which is what I wanted.

Posted: **Mon Aug 23, 2021 5:02 pm**

Private Internet Access from MX package installer failed with missing cheksum error.

Code: Select all

Get:1 http://deb.debian.org/debian bullseye-updates InRelease [36.8 kB]
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://mxrepo.com/mx/repo bullseye InRelease
Ign:4 http://repo.vivaldi.com/stable/deb stable InRelease
Hit:5 http://repo.vivaldi.com/stable/deb stable Release
Fetched 36.8 kB in 1s (35.8 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Suggested packages:
  ssh-askpass-gnome
The following NEW packages will be installed:
  piavpn-downloader-installer
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 17.4 kB of archives.
After this operation, 61.4 kB of additional disk space will be used.
Get:1 http://mxrepo.com/mx/repo bullseye/main amd64 piavpn-downloader-installer amd64 19.07.01 [17.4 kB]
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
QCommandLineParser: already having an option named "v"
Fetched 17.4 kB in 0s (43.6 kB/s)
Selecting previously unselected package piavpn-downloader-installer.
(Reading database ... 298155 files and directories currently installed.)
Preparing to unpack .../piavpn-downloader-installer_19.07.01_amd64.deb ...
Unpacking piavpn-downloader-installer (19.07.01) ...
Setting up piavpn-downloader-installer (19.07.01) ...
Downloading Private Internet Access for Linux 64bit :   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

100   243    0   243    0     0    428      0 --:--:-- --:--:-- --:--:--   428
[ OK ] downloaded ''
[ ERROR ] Missing checksum

Posted: **Mon Aug 23, 2021 5:35 pm**

richb wrote: Mon Aug 23, 2021 5:02 pm Private Internet Access from MX package installer failed with missing cheksum error.

[ ERROR ] Missing checksum[/code]

There's a /usr/share/pia-downloader-installer/install_piavpn.sh file part of the piavpn-downloader-installer package that tries to download from a site with curl and that site returns a "301 Moved Permanently"

@fehlix The piavpn-downloader-installer needs to be fixed.

Posted: **Mon Aug 23, 2021 7:42 pm**

baldyeti wrote: Mon Aug 23, 2021 1:12 pm Just tested a frugal install so far (on MBR-partitioned disk, ivy bridge era desktop), looking very nice !

Some preliminary remarks:

i am pretty sure i picked a keyboard layout (which is indeed active in my frugal session) but which was not activated (yet) through the frugal configuration dialogs, making it a tad difficult to change password etc

Password change dialog is run within a console. The console keymap is driven by the chosen language. The X-keyboard layout can be set by kbd= parameter. But the kbd-boot parameter would not change the console keymap.
Example: If I choose lang=en_US and kbd=de. I would be prompted for changing demo/root password with en_US keymap, but when finally getting to KDE the actual keyboard would be German keyboard layout.
OK, not optimal ... My workaround: disabale password change at the console with "pw=none" boot parameter.
You can change password later, e.g with MX User managemenr.

baldyeti wrote: Mon Aug 23, 2021 1:12 pm PS: forget the last point above, apparently this is a glitch in this particular Dell'sBIOS - I have booted two other systems in MBR/legacy mode with no issue.

But: the Dell is where i was willing to overwrite a partition with MX21, and the disk is MBR-partitioned. Can I boot the installation key in UEFI mode, start the installer without esp partition and without installing grub at the end ?

Not clear to me, why you want booting in UEFI mode with MBR-partitions. But yes, you can boot in UEFI-mode and tick off/disable the GRUB installation. Not clear how you to boot into the system without boot loader. Actually you can boot in UEFI-mode and do GRUB-bootloader installation in BIOS/MBR mode.

Posted: **Mon Aug 23, 2021 8:08 pm**

richb wrote: Mon Aug 23, 2021 5:02 pm Private Internet Access from MX package installer failed with missing cheksum error.

That's not a specific KDE issue. They changed the URL and taken away to verify the download with a checksum. I'll have a look.

Posted: **Mon Aug 23, 2021 8:31 pm**

Installed to my old beater Acer laptop, flawless install as expected. Fought with date and time but that resolved itself. Did some minor UI configs in the live session, and will do some more once I'm done playing and exploring. Warren's legacy appears to be holding up: this beta is better than most finals. Kudos to all.

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: KDE Plasma 5.20.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-21_x64 Wildflower August 22  2021 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Laptop System: Acer product: Aspire 5250 v: V1.01 
  serial: <filter> 
  Mobo: Acer model: Aspire 5250 v: V1.01 serial: <filter> BIOS: Acer 
  v: 1.01 date: 04/21/2011 
Battery:
  ID-1: BAT1 charge: 28.4 Wh condition: 48.1/47.5 Wh (101%) 
  volts: 12.3/10.8 model: Panasonic AS10D51 type: Li-ion 
  serial: <filter> status: Charging 
  Device-1: hidpp_battery_0 model: Logitech M215 serial: <filter> 
  charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:
  Topology: Dual Core model: AMD C-50 bits: 64 type: MCP arch: Bobcat 
  family: 14 (20) model-id: 1 stepping: N/A microcode: 5000029 
  L2 cache: 512 KiB 
  flags: lm nx pae sse sse2 sse3 sse4a ssse3 svm bogomips: 3990 
  Speed: 922 MHz min/max: 800/1000 MHz Core speeds (MHz): 1: 922 2: 906 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass status: Vulnerable 
  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 Wrestler [Radeon HD 6250] vendor: Acer Incorporated ALI 
  driver: radeon v: kernel bus ID: 00:01.0 chip ID: 1002:9804 
  Display: x11 server: X.Org 1.20.11 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
  resolution: 1366x768~60Hz 
  OpenGL: renderer: AMD PALM (DRM 2.50.0 / 5.10.0-8-amd64 LLVM 11.0.1) 
  v: 3.3 Mesa 21.1.5 compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: Acer Incorporated ALI 
  driver: snd_hda_intel v: kernel bus ID: 00:14.2 chip ID: 1002:4383 
  Sound Server: ALSA v: k5.10.0-8-amd64 
Network:
  Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet 
  vendor: Acer Incorporated ALI driver: atl1c v: kernel port: 2000 
  bus ID: 06:00.0 chip ID: 1969:2062 
  IF: eth0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros AR9285 Wireless Network Adapter 
  vendor: Lite-On driver: ath9k v: kernel port: 2000 bus ID: 07:00.0 
  chip ID: 168c:002b 
  IF: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 111.79 GiB used: 6.95 GiB (6.2%) 
  ID-1: /dev/sda vendor: Kingston model: SV300S37A120G size: 111.79 GiB 
  block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
  serial: <filter> rev: BBF0 scheme: MBR 
Partition:
  ID-1: / raw size: 106.38 GiB size: 104.15 GiB (97.90%) 
  used: 6.95 GiB (6.7%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 5.37 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) 
  dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 68.6 C mobo: N/A gpu: radeon temp: 69 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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
  2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
Info:
  Processes: 168 Uptime: 9m Memory: 3.57 GiB used: 994.9 MiB (27.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: **Mon Aug 23, 2021 8:46 pm**

fehlix wrote: Mon Aug 23, 2021 8:08 pm
richb wrote: Mon Aug 23, 2021 5:02 pm Private Internet Access from MX package installer failed with missing cheksum error.
That's not a specific KDE issue. They changed the URL and taken away to verify the download with a checksum. I'll have a look.

I understand. However someone trying to install PIA in MX-21 KDE would encounter this error, So I believe the report is valid.

Posted: **Mon Aug 23, 2021 9:09 pm**

uncle mark wrote: Mon Aug 23, 2021 8:31 pm Installed to my old beater Acer laptop, flawless install as expected. Fought with date and time but that resolved itself. Did some minor UI configs in the live session, and will do some more once I'm done playing and exploring. Warren's legacy appears to be holding up: this beta is better than most finals. Kudos to all.

Dolphin is crashing hard. Won't open. It tries, but never gets there.

Wifi does not reconnect automatically on restart. If there's a checkmark to tell it to I sure haven't seen it.

I'm not going to spend any more time on it this evening. Just offering up data points. Heck, I might have a funky install. I didn't bother checking the ISO or the disk I burned.

Posted: **Mon Aug 23, 2021 9:14 pm**

or the disk I burned.

I suspect that, I always use flashdrives... even those are not that reliable.

Posted: **Mon Aug 23, 2021 9:29 pm**

Wifi does not reconnect automatically on restart. If there's a checkmark to tell it to I sure haven't seen it.

I have the same issue. There is a n option in the Network Connections setting to start automatically and a priority number under the wifi tab. I have it ticked with a priority of 5 but it still needs to be started manually. It probably is a native KDE application issue. I doubt it can be fixed by our developers. ( But they have surprised me in the past).

Posted: **Mon Aug 23, 2021 9:59 pm**

richb wrote: Mon Aug 23, 2021 9:29 pm
Wifi does not reconnect automatically on restart. If there's a checkmark to tell it to I sure haven't seen it.
I have the same issue. There is a n option in the Network Connections setting to start automatically and a priority number under the wifi tab. I have it ticked with a priority of 5 but it still needs to be started manually. It probably is a native KDE application issue. I doubt it can be fixed by our developers. ( But they have surprised me in the past).

My priority was set to 0; I changed it to 1 (not knowing what I was actually doing). No joy.

Posted: **Mon Aug 23, 2021 10:01 pm**

Adrian wrote: Mon Aug 23, 2021 9:14 pm
or the disk I burned.
I suspect that, I always use flashdrives... even those are not that reliable.

I usually use flash drives too, but this old beater usually does better with disks.

Posted: **Mon Aug 23, 2021 11:03 pm**

wifi: try setting your connection to allow all users to connect.

Posted: **Tue Aug 24, 2021 12:15 am**

chrispop99 wrote: Mon Aug 23, 2021 3:26 pm

The release announcement tells you Discover is used for updates.

Chris

thanks chris...feel pretty dumb now...

I did read the release notes honestly ...maybe more a skim than a read

i went ahead and installed apt-notifier .... should i get rid of it again?

Posted: **Tue Aug 24, 2021 12:48 am**

i went ahead and installed apt-notifier .... should i get rid of it again?

It's not needed, you'll get 2 notifications that you have updates pending, at the same time if you prefer some of its features you could use it instead of discover, I think you could set up discover to never check for updates.

Posted: **Tue Aug 24, 2021 2:57 am**

fehlix wrote: Mon Aug 23, 2021 7:42 pm Not clear to me, why you want booting in UEFI mode with MBR-partitions. But yes, you can boot in UEFI-mode and tick off/disable the GRUB installation. Not clear how you to boot into the system without boot loader. Actually you can boot in UEFI-mode and do GRUB-bootloader installation in BIOS/MBR mode.

Thanks fehlix. The resaon is this particular machine (at least with this particular USB key) will only boot the (ventoy) live system in UEFI mode. This way I could install then fix grub later from the MX18 instance which owns the MBR on this PC. I will probably rather make some free space on another system to run a more realistic test for the installer but that may take a couple days.

Posted: **Tue Aug 24, 2021 4:44 am**

baldyeti wrote: Tue Aug 24, 2021 2:57 am
fehlix wrote: Mon Aug 23, 2021 7:42 pm Not clear to me, why you want booting in UEFI mode with MBR-partitions. But yes, you can boot in UEFI-mode and tick off/disable the GRUB installation. Not clear how you to boot into the system without boot loader. Actually you can boot in UEFI-mode and do GRUB-bootloader installation in BIOS/MBR mode.
Thanks fehlix. The resaon is this particular machine (at least with this particular USB key) will only boot the (ventoy) live system in UEFI mode. This way I could install then fix grub later from the MX18 instance which owns the MBR on this PC. I will probably rather make some free space on another system to run a more realistic test for the installer but that may take a couple days.

As mentioned, even when booting in UEFI mode, the Installer allows to have GRUB installed into MBR or PBR, instead into the ESP (EFI System Partition).
If chosen PBR, this would not overwrite the MBR, but would still create GRUB menu at the KDE installation .
Just select PBR at the GRUB installation window, this would make it easier for MX18-GRUB to find the GRUB-menu of the MX21-KDE installation and to extract the menu-entries found. Not installing GRUB from with the Installer is also possible. In the case of not having installed GRUB (to the PBR), the MX18-GRUB would need to create (based on a bare template) one menu entry for MX-KDE. If having GRUB installed to the PBR, it would allow the MX18-GRUB to properly extract all menu entries from the MX21-KDE grub menu including the menu entry to boot with systemd.
Another advantage of having installed GRUB even to the PBR only would be that you could boot into the installed system using "Boot Rescue" tool from the LiveUSB boot menu and select "Grub menu" to search and find the PBR-installed GRUB menu on the MX-KDE installation.

Posted: **Tue Aug 24, 2021 4:59 am**

Alright thanks for the clarification - i did not realise the installer would allow installing grub to MBR or PBR even when the installation media is booted in UEFI mode. I barely ever use UEFI as i mostly have older HW and often swap disks between systems.

Posted: **Tue Aug 24, 2021 5:38 am**

I really don't like Discover. I spent a while just looking at a rotating logo waiting to discover what was going to happen next, and it never did! It may prove useful for installing Plasmoids but when I tried to get Event Calendar it denied its existence. I'll have another look later, maybe it will win me over in the end! For now, MX-installer and update, in conjunction with Synaptic is my preferred way of doing things. If it ain't broke...

I used MX installer to add a number of packages, and it reported an error while installing Google Earth. I had to recheck a number of packages that hadn't installed, and click Install again. Strangely enough though, Google Earth is installed and working perfectly.

My only real complaint is not directed at MX devs, but the tendency of the developers of Desktop Environments to keep fixing stuff until it's broke!

Posted: **Tue Aug 24, 2021 5:45 am**

Another thing: Debian seems to have dropped "Disk Manager", so I'm having to do /etc/fstab by hand. Any advice?

Posted: **Tue Aug 24, 2021 5:52 am**

davemx wrote: Tue Aug 24, 2021 5:45 am Another thing: Debian seems to have dropped "Disk Manager", so I'm having to do /etc/fstab by hand. Any advice?

Install gnome-disk-utility.

Note that you may need, after using the above tool to mount whichever partition you want, to edit it a little (it may mount by default on /mnt instead of /media, for instance, so if you want to change mount points before saving the fstab entry, you have to edit the mount settings from within the said tool)

I thought the above tool was going to be included by default, but I guess not in the beta1 for now.

Disk Manager was not maintained for yonks but continued to work up till MX19.

I think it's based on python2 which is no longer in Debian Bullseye so it's gone.

I'm very sad to see it die off, as it was a good, quick and useful little tool.

Posted: **Tue Aug 24, 2021 5:57 am**

asqwerth wrote: Tue Aug 24, 2021 5:52 am Install gnome-disk-utility

I thought it was going to be included by default, but I guess not in the beta1 for now.

Disk Manager was not maintained for yonks but continued to work up till MX19.

I think it's based on python2 which is no longer in Debian Bullseye so it's gone.

I'm very sad to see it die off, as it was a good, quick and useful little tool.

When I tested the XFCE beta, I think I did install that. I spent ages looking at it and eventually did fstab by hand!

Posted: **Tue Aug 24, 2021 6:00 am**

davemx wrote: Tue Aug 24, 2021 5:38 am I really don't like Discover. I spent a while just looking at a rotating logo waiting to discover what was going to happen next, and it never did! It may prove useful for installing Plasmoids but when I tried to get Event Calendar it denied its existence. I'll have another look later, maybe it will win me over in the end! For now, MX-installer and update, in conjunction with Synaptic is my preferred way of doing things. If it ain't broke...

I don't like Discover as the default updater as well. I hate that you can't tell at the top level, without drilling down to individual packages being updated, whether the updates are from:

1. main repos
2. flatpaks
3. icons/themes/customisation packages where newer versions are available from KDE Online Store

I prefer to update 2 and 3 above manually, when I want to.

Posted: **Tue Aug 24, 2021 6:03 am**

davemx wrote: Tue Aug 24, 2021 5:57 am
asqwerth wrote: Tue Aug 24, 2021 5:52 am Install gnome-disk-utility

I thought it was going to be included by default, but I guess not in the beta1 for now.

Disk Manager was not maintained for yonks but continued to work up till MX19.

I think it's based on python2 which is no longer in Debian Bullseye so it's gone.

I'm very sad to see it die off, as it was a good, quick and useful little tool.
When I tested the XFCE beta, I think I did install that. I spent ages looking at it and eventually did fstab by hand!

It's not the most intuitive, as a fstab GUI editor. You have to look for the little edit icon (I think it's a gear).

Some people like it because it's a huge jack of all trades, being able to do Gparted's work as well. For me, Gparted and Disk Manager each did its individual tasks in an easy to understand GUI.

Posted: **Tue Aug 24, 2021 6:34 am**

dolphin_oracle wrote: Mon Aug 23, 2021 11:03 pm wifi: try setting your connection to allow all users to connect.

I had tried that but had not remastered, so of course the change did not register on a reboot. (I am running on a USB). That is most likely the solution as wifi did connect when I suspended only.

Posted: **Tue Aug 24, 2021 6:45 am**

@dolphin_oracle
this download link is unbelievably slow. Is there any possibility to download from a better repo/server?
I am in the UK ....

Posted: **Tue Aug 24, 2021 6:52 am**

Vanitarium wrote: Tue Aug 24, 2021 6:45 am this download link is unbelievably slow. Is there any possibility to download from a better repo/server?
I am in the UK ....

If you mean the download from sourceforge, you can change server by clicking the "Problems Downloading?" button

Posted: **Tue Aug 24, 2021 7:19 am**

I can't find the normal mx updater anywhere in either MX-install or synaptic! As for Discover, you can't block it from starting in the background, it seems to be hardwired in at root level. So I've uninstalled it (plasma-discover, not to be confused with another program called discover).

Posted: **Tue Aug 24, 2021 7:26 am**

asqwerth wrote: Tue Aug 24, 2021 6:03 am
It's not the most intuitive, as a fstab GUI editor. You have to look for the little edit icon (I think it's a gear).

Some people like it because it's a huge jack of all trades, being able to do Gparted's work as well. For me, Gparted and Disk Manager each did its individual tasks in an easy to understand GUI.

+1 with bells on.

Yes, this is the one that threw me before. I really don't like it but next time I'll have to use it. You need to edit each mount point separately. Disk Manager was so easy to use!!

Posted: **Tue Aug 24, 2021 7:27 am**

@davemx

Search for apt-notifier in mxpi

I have always steered clear of discover in the past... It always seemed clunky.. Maybe it is better now but I feel happier with mx updater handling stuff

Posted: **Tue Aug 24, 2021 8:02 am**

Installed pretty fast and without problems on my hard drive next to MX 19.4 (separate partitions without shared /home) The wallpaper disappears on reboot, but I put the ones I like; I was able to configure all my applications, I like how Ksnip works, I will no longer use Flameshot. With Discover learning how to handle it for updates, it doesn't bother me, it's something new to me that I was used to. I thought I was going to have trouble reading and writing to NTFS disks (no Disk Manager) but for now it works without a problem, I would have liked to have used Amarok instead of Clementine. I have the impression that it works smoother and faster than MX 19.4. I leave you a screenshot.

Posted: **Tue Aug 24, 2021 8:26 am**

In previous releases, right out of the box Alt + right-click allowed for resizing windows.

This does not appear to hold with MX 21 KDE .... unless I'm doing something wrong.

A little exploration shows that it's now the "windows power key" + right-click that facilitates window re-sizing. I can live with that.

Posted: **Tue Aug 24, 2021 9:37 am**

Just noticed backports has inxi 3.3 whereas the beta currently ships 3.0, perhaps worth the upgrade ?

Posted: **Tue Aug 24, 2021 10:33 am**

junoluna wrote: Tue Aug 24, 2021 7:27 am @davemx

Search for apt-notifier in mxpi

I have always steered clear of discover in the past... It always seemed clunky.. Maybe it is better now but I feel happier with mx updater handling stuff

I was looking for something with both mx and notifier in its name! That's why I didn't find it. Anyway, apt-notifier is installed and plasma-discover is gone. And all is well with the world!

Posted: **Tue Aug 24, 2021 12:48 pm**

I had not used the installer in quite a while; it is sleek & fast !

Installed twice without any issue so far (once to a reformatted partition, another one preserving /home from a plain bullseye/kde i had), both working very well.

@AK-47: One small enhancement request for the installer: when installing grub to PBR, the partition drop-down does *not* default to the partition which was used as root (but i guess to the 1st linux partition on the disk, ext3 from another distro in my case).

Posted: **Tue Aug 24, 2021 1:13 pm**

I noticed a couple error lines when booting in systemd mode:

[ +0.000028] systemd[1]: System cannot boot: Missing /etc/machine-id and /etc is mounted read-only.
[ +0.000007] systemd[1]: Booting up is supported only when:
[ +0.000005] systemd[1]: 1) /etc/machine-id exists and is populated.
[ +0.000004] systemd[1]: 2) /etc/machine-id exists and is empty.
[ +0.000004] systemd[1]: 3) /etc/machine-id is missing and /etc is writable.

yet the PC proceeds to boot and everything apparently works as expected

Posted: **Tue Aug 24, 2021 2:07 pm**

There's one thing I do like about the installer (though this is not specific to the KDE Beta). "Preserve" now works on the root directory whether or not you have /home present on it. This means I can install a new system without changing the UUID. This is really good when you have multiple partitions with different systems on them, it saves you having to make changes to /etc/fstab

Posted: **Tue Aug 24, 2021 2:30 pm**

davemx wrote: Tue Aug 24, 2021 5:45 am Another thing: Debian seems to have dropped "Disk Manager", so I'm having to do /etc/fstab by hand. Any advice?

KDE Partition Manager -> Right-click on the partition and select "Edit Mount Point". Isn't that doing what you need?

Posted: **Tue Aug 24, 2021 5:50 pm**

dolphin_oracle wrote: Mon Aug 23, 2021 11:03 pm wifi: try setting your connection to allow all users to connect.

(New install from USB with new ISO downloaded)

Did the above in the Live session, told the installer to save live config changes, and on reboot to the newly installed system the wifi connected automagically. Thanks.

Dolphin still crashing on newly installed system. It tries, but craps out, followed by a "Dolphin closed unexpectantly" popup. When launching from the Panel, nothing comes up on screen. When launching from the application menu, the top window bar appears but the username one would expect to see is truncated.

Very very weird.

Posted: **Tue Aug 24, 2021 5:58 pm**

@uncle mark did you check the ISO, also might want to test the installation medium too. I haven't seen anything like that.

Posted: **Tue Aug 24, 2021 6:12 pm**

Adrian wrote: Tue Aug 24, 2021 5:58 pm @uncle mark did you check the ISO, also might want to test the installation medium too. I haven't seen anything like that.

What's the md5sum? All I see on the download page is a *.sig file that won't open as a text file.

Posted: **Tue Aug 24, 2021 6:21 pm**

It's all here:
https://sourceforge.net/projects/mx-lin ... sting/KDE/
MD5: 3ee5b88f35d73afd2ce3d3b394dae59e

Also remember to check medium from boot menu, that's probably more important because it checks the MD5 of the linuxfs file. I'm sorry but I distrust your DVD

Posted: **Tue Aug 24, 2021 6:36 pm**

Also have a Dolphin issue. Home and all the folders in home give the result shown in pic when attempt to open them. I chose save live configuration in the install procedure. I can access those folders from rootmx21/home/richb.

Posted: **Tue Aug 24, 2021 6:40 pm**

That implies there is a configuration being saved that need me to no excluded thanks

Posted: **Tue Aug 24, 2021 7:28 pm**

Adrian wrote: Tue Aug 24, 2021 6:21 pm It's all here:
https://sourceforge.net/projects/mx-lin ... sting/KDE/
MD5: 3ee5b88f35d73afd2ce3d3b394dae59e

Also remember to check medium from boot menu, that's probably more important because it checks the MD5 of the linuxfs file. I'm sorry but I distrust your DVD

Downloaded ISO md5 checks out. I'm too old and senile anymore to know how to check the DVD or USB. (I used the DVD last night, USB today.)

[Does anyone else remember a time long ago when I was reasonably proficient with this stuff, or am I just imagining it?]

Posted: **Tue Aug 24, 2021 7:40 pm**

No worry: we remember everything about you from a long time ago...

Posted: **Tue Aug 24, 2021 7:42 pm**

Still using the computer you helped me spec and build.

Posted: **Tue Aug 24, 2021 7:52 pm**

richb wrote: Tue Aug 24, 2021 6:36 pm Also have a Dolphin issue. Home and all the folders in home give the result shown in pic when attempt to open them. I chose save live configuration in the install procedure. I can access those folders from rootmx21/home/richb.

Haven't see that without saving the save live configuration, that's probably something wrong with that procedure.

Posted: **Tue Aug 24, 2021 8:02 pm**

Adrian wrote: Tue Aug 24, 2021 7:52 pm
richb wrote: Tue Aug 24, 2021 6:36 pm Also have a Dolphin issue. Home and all the folders in home give the result shown in pic when attempt to open them. I chose save live configuration in the install procedure. I can access those folders from rootmx21/home/richb.
Haven't see that without saving the save live configuration, that's probably something wrong with that procedure.

Dolphin worked in the live session. I think I changed the Dolphin settings to show hidden files and changed the default view to details while Live, and did tell the installer to save changes made while Live.

Posted: **Tue Aug 24, 2021 8:06 pm**

Jerry3904 wrote: Tue Aug 24, 2021 7:40 pm No worry: we remember everything about you from a long time ago...

I thought the statue of limitations might have passed...

Posted: **Tue Aug 24, 2021 8:08 pm**

on home folders: take a look at the ~/.local/share/users-places.xbel and see if the /home/demo is referenced in there

Posted: **Tue Aug 24, 2021 8:19 pm**

dolphin_oracle wrote: Tue Aug 24, 2021 8:08 pm on home folders: take a look at the ~/.local/share/users-places.xbel and see if the /home/demo is referenced in there

It is as an example: <bookmark href="file:///home/demo/Desktop">
As well as all the other home folders.

Posted: **Tue Aug 24, 2021 8:19 pm**

dolphin_oracle wrote: Tue Aug 24, 2021 8:08 pm on home folders: take a look at the ~/.local/share/users-places.xbel and see if the /home/demo is referenced in there

Kinda hard for a dummy like me to do that if the file manager doesn't work. :-)

Okay....

cd /home/.local/share/users-places
No such file or directory

cd /home/.local/share/users-places.xbel
No such file or directory

Posted: **Tue Aug 24, 2021 8:22 pm**

uncle mark wrote: Tue Aug 24, 2021 8:19 pm
dolphin_oracle wrote: Tue Aug 24, 2021 8:08 pm on home folders: take a look at the ~/.local/share/users-places.xbel and see if the /home/demo is referenced in there
Kinda hard for a dummy like me to do that if the file manager doesn't work. :-)

Okay....

cd /home/.local/share/users-places
No such file or directory

cd /home/.local/share/users-places.xbel
No such file or directory

its a file. it would also be $HOME/.local/share/user-places.xbel

but I was more referencing @richb report.

edit** actually now I crash can dolphin easily. and my file is fine, so its somethine else...

Posted: **Tue Aug 24, 2021 8:28 pm**

I accessed home from root to find it.

Posted: **Tue Aug 24, 2021 10:58 pm**

short workaound on dolphin crashing.

from konsole, trying

Code: Select all

dolphin --new-window

and see if dolphin launches

Posted: **Wed Aug 25, 2021 8:49 am**

dolphin_oracle wrote: Tue Aug 24, 2021 10:58 pm short workaound on dolphin crashing.

from konsole, trying
Code: Select all
dolphin --new-window
and see if dolphin launches

Does here.

Posted: **Wed Aug 25, 2021 9:46 am**

Here's another oddity: In the main menu, at the bottom of the Favorites, instead of the three buttons/icons for Logout/Reboot/Shutdown, there is only the Logout button/icon.

Posted: **Wed Aug 25, 2021 10:57 am**

baldyeti wrote: Tue Aug 24, 2021 1:13 pm I noticed a couple error lines when booting in systemd mode:

[ +0.000028] systemd[1]: System cannot boot: Missing /etc/machine-id and /etc is mounted read-only.
[ +0.000007] systemd[1]: Booting up is supported only when:
[ +0.000005] systemd[1]: 1) /etc/machine-id exists and is populated.
[ +0.000004] systemd[1]: 2) /etc/machine-id exists and is empty.
[ +0.000004] systemd[1]: 3) /etc/machine-id is missing and /etc is writable.

yet the PC proceeds to boot and everything apparently works as expected

Yes, this seems to be carried forward from MX19...

I think the MX installer should run this in chroot at the end of installation:

Code: Select all

systemd-machine-id-setup --commit

Worth a look for devs.

Questions:
1. Is it OK to install KDE beta1 and update (to get all relevant transient fixes reported in this thread) or wait for beta2 maybe?
2. Does samba sharing work in systemd boot as of now?
3. Is it based on xfce beta base or separate AHS base?

Posted: **Wed Aug 25, 2021 5:16 pm**

Installed with no issues. Installed aircrack-ng's rtl8814 drivers to get my Netgear A7000 up and running. Played around with Discovery. Installed and removed packages with no problem. Installed and setup a global theme (Noir-Dark-Global), tweaked some other settings for look and feel. One thing caught my attention...Boot time is cut in half. 19.4 KDE (Plasma 4.19.5) took from grub screen to desktop 2:02 minutes. Now it takes 58 seconds. Haven't really taking it for a run as I'm testing Flux 1.3.7 on this machine also.

Global Theme
Noir-Dark-Global

Plasma Style
Breeze-Noir-Dark

Application Style
MS Windows 9x

Window Decorations
Breeze-Noir-Dark-Color-Aurorae

Colors
Breeze-Noir-Dark-1

Icons
Breeze-Noir-White-Blue

Cursors
Oxygen Black

Posted: **Thu Aug 26, 2021 11:20 am**

Adrian wrote: Tue Aug 24, 2021 2:30 pm
davemx wrote: Tue Aug 24, 2021 5:45 am Another thing: Debian seems to have dropped "Disk Manager", so I'm having to do /etc/fstab by hand. Any advice?
KDE Partition Manager -> Right-click on the partition and select "Edit Mount Point". Isn't that doing what you need?

NICE! That looks good. Bit late now I've got everything done, but for future MX installs, it does look the part. Covers both Disk Manager and GParted but looks far more user friendly for the setting of mount points than Gnome Disk Manager! Thank you!

Posted: **Thu Aug 26, 2021 1:12 pm**

Installed on my old Sun Ultra 27. 48 hours and everything is running smoothly. Installed the full kdepim suite (Kontact) and for the first time in years everything works as it should. I'll be attempting an install on my old HP Notebook later. So far I'm extremely impressed, even Steam loads and runs quicker.

Posted: **Thu Aug 26, 2021 1:32 pm**

Probably a KDE issue and NOT an MX issue. While my HP printer was recognized during the install it would not print. I had to install, (reinstall?) the driver for the printer

Posted: **Thu Aug 26, 2021 1:41 pm**

I use Evolution for my email. I am unable to print the email on my printers. I receive a message Printing failed.The printer replied "Printer not found"
Using MX19 I used Evolution and had no issues. I tried from Thunderbird and all worked ok. No other issues using MX21.

Posted: **Thu Aug 26, 2021 1:54 pm**

richb wrote: Thu Aug 26, 2021 1:32 pm Probably a KDE issue and NOT an MX issue. While my HP printer was recognized during the install it would not print. I had to install, (reinstall?) the driver for the printer

HP printer recognised and printed OK here without intervention.

Chris

Posted: **Thu Aug 26, 2021 2:04 pm**

chrispop99 wrote: Thu Aug 26, 2021 1:54 pm
richb wrote: Thu Aug 26, 2021 1:32 pm Probably a KDE issue and NOT an MX issue. While my HP printer was recognized during the install it would not print. I had to install, (reinstall?) the driver for the printer
HP printer recognised and printed OK here without intervention.

Chris

Good to know. It was not a big deal and the driver installed easily.

Posted: **Thu Aug 26, 2021 3:02 pm**

richb wrote: Mon Aug 23, 2021 5:02 pm Private Internet Access from MX package installer failed with missing cheksum error.

PIA VPN installer should now work with the adjusted pia-installer helper, which by now should be in the repos already or soonish.

Posted: **Thu Aug 26, 2021 3:10 pm**

fehlix wrote: Thu Aug 26, 2021 3:02 pm
richb wrote: Mon Aug 23, 2021 5:02 pm Private Internet Access from MX package installer failed with missing cheksum error.
PIA VPN installer should now work with the adjusted pia-installer helper, which by now should be in the repos already or soonish.

It does. Thank you.

Posted: **Thu Aug 26, 2021 3:14 pm**

The KDE Application Launcher is nearer to Whisker than the 'last century' Application Menu, but it shows the function in a larger bold font, and the actual program name smaller. This seems counter-intuitive to me; I expected there would be a way to swap them around, but can't find it. Am I missing something, or is it not possible to switch to what seems a more sensible arrangement?

Chris

Posted: **Thu Aug 26, 2021 3:22 pm**

chrispop99 wrote: Thu Aug 26, 2021 3:14 pm The KDE Application Launcher is nearer to Whisker than the 'last century' Application Menu, but it shows the function in a larger bold font, and the actual program name smaller. This seems counter-intuitive to me; I expected there would be a way to swap them around, but can't find it. Am I missing something, or is it not possible to switch to what seems a more sensible arrangement?

Chris

I just switch to the alternate Application Menu rather than Application Launcher which is indeed more whisker like.

Posted: **Thu Aug 26, 2021 5:52 pm**

I have a problem in dark mode. I set Breeze Dark theme but some gtk apps do not follow theme settings: Audacious, Synaptic, and even MX Package Installer and MX Tools.
Looks like it's a known problem since plasma 5.17 (or is it 5.19?) because there is no more Breeze Dark, but only Breeze and it is expected gtk3+ apps to follow settings. But they don't :)
If I change gtk theme (Settings -> Application Style -> Configure GNOME/GTK....) to Adwaita Dark, Audacious changes but both package managers do not (even after reboot)
Same problem exists in Debian 11 KDE

Oh, almost forgot... no problems installing HP network printer (HP OfficeJet Pro 8710) via Settings -> Printers :)

Posted: **Thu Aug 26, 2021 6:13 pm**

Code: Select all

[code]
System:
  Host: <filter> 
  Kernel: 5.10.0-8-amd64 x86_64 
  bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/antiX/vmlinuz 
  quiet splasht nosplash 
  Desktop: KDE Plasma 5.20.5 
  wm: kwin_x11 dm: SDDM Distro: MX-21_x64 
  Wildflower August 22 2021 
  base: Debian GNU/Linux 11 
  (bullseye) 
Machine:
  Type: Desktop Mobo: Gigabyte 
  model: B450 AORUS ELITE 
  v: x.x serial: <filter> 
  UEFI: American Megatrends 
  v: F41 date: 07/22/2019 
CPU:
  Topology: 8-Core 
  model: AMD Ryzen 7 2700X 
  bits: 64 type: MT MCP 
  arch: Zen+ family: 17 (23) 
  model-id: 8 stepping: 2 
  microcode: 800820D 
  L2 cache: 4096 KiB 
  flags: avx avx2 lm nx pae sse 
  sse2 sse3 sse4_1 sse4_2 sse4a 
  ssse3 svm 
  bogomips: 118165 
  Speed: 1922 MHz 
  min/max: 2200/3700 MHz 
  boost: disabled 
  Core speeds (MHz): 1: 1922 
  2: 1949 3: 1890 4: 1916 
  5: 1883 6: 1977 7: 2194 
  8: 2194 9: 1896 10: 2102 
  11: 1919 12: 1977 13: 2195 
  14: 2191 15: 1938 16: 2147 
  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 Baffin [Radeon 
  RX 550 640SP / RX 560/560X] 
  vendor: XFX Pine 
  driver: amdgpu v: kernel 
  bus ID: 06:00.0 
  chip ID: 1002:67ff 
  Display: x11 
  server: X.Org 1.20.11 
  driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa 
  compositor: kwin_x11 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Radeon RX 
  550 Series (POLARIS11 DRM 
  3.40.0 5.10.0-8-amd64 LLVM 
  11.0.1) 
  v: 4.6 Mesa 21.1.5 
  direct render: Yes 
Audio:
  Device-1: AMD Baffin HDMI/DP 
  Audio [Radeon RX 550 640SP / 
  RX 560/560X] 
  vendor: XFX Pine 
  driver: snd_hda_intel 
  v: kernel bus ID: 06:00.1 
  chip ID: 1002:aae0 
  Device-2: AMD Family 17h HD 
  Audio 
  vendor: Gigabyte 
  driver: snd_hda_intel 
  v: kernel bus ID: 08:00.3 
  chip ID: 1022:1457 
  Sound Server: ALSA 
  v: k5.10.0-8-amd64 
Network:
  Device-1: Realtek 
  RTL8111/8168/8411 PCI Express 
  Gigabit Ethernet 
  vendor: Gigabyte 
  driver: r8169 v: kernel 
  port: f000 bus ID: 03:00.0 
  chip ID: 10ec:8168 
  IF: eth0 state: up 
  speed: 100 Mbps duplex: full 
  mac: <filter> 
Drives:
  Local Storage: 
  total: 7.31 TiB 
  used: 3.00 GiB (0.0%) 
  ID-1: /dev/sda 
  vendor: HGST (Hitachi) 
  model: HUS728T8TALE6L4 
  size: 7.28 TiB block size: 
  physical: 4096 B 
  logical: 512 B 
  speed: 6.0 Gb/s 
  rotation: 7200 rpm 
  serial: <filter> rev: W414 
  scheme: GPT 
  ID-2: /dev/sdb type: USB 
  vendor: SanDisk 
  model: Cruzer Glide 
  size: 29.25 GiB block size: 
  physical: 512 B 
  logical: 512 B 
  serial: <filter> rev: 1.00 
  scheme: MBR 
Partition:
  ID-1: / raw size: N/A 
  size: 18.71 GiB 
  used: 650.1 MiB (3.4%) 
  fs: overlay source: ERR-102 
Sensors:
  System Temperatures: 
  cpu: 36.6 C mobo: N/A 
  gpu: amdgpu temp: 43 C 
  Fan Speeds (RPM): N/A 
  gpu: amdgpu fan: 276 
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
  2: deb http://mxrepo.com/mx/repo/ bullseye ahs
Info:
  Processes: 307 Uptime: 1h 08m 
  Memory: 23.49 GiB 
  used: 1.74 GiB (7.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

[/code] I am running MX21 KDE on a live USB. So far so good except, I have a recommendation on avoiding a problem with right clicking in Dolphin Root Actions > (Ownership to Root) that it will cause breakage as what was experienced in older versions of MX Linux that was corrected in MX 19 by having that action disabled by default but can be easily changed in MX Tweak.

Posted: **Thu Aug 26, 2021 11:01 pm**

markol wrote: Thu Aug 26, 2021 5:52 pm I have a problem in dark mode. I set Breeze Dark theme but some gtk apps do not follow theme settings: Audacious, Synaptic, and even MX Package Installer and MX Tools.
Looks like it's a known problem since plasma 5.17 (or is it 5.19?) because there is no more Breeze Dark, but only Breeze and it is expected gtk3+ apps to follow settings. But they don't :)
If I change gtk theme (Settings -> Application Style -> Configure GNOME/GTK....) to Adwaita Dark, Audacious changes but both package managers do not (even after reboot)
Same problem exists in Debian 11 KDE

Oh, almost forgot... no problems installing HP network printer (HP OfficeJet Pro 8710) via Settings -> Printers :)

Note that the mx apps are not gtk but qt based.

Posted: **Fri Aug 27, 2021 2:47 am**

asqwerth wrote: Thu Aug 26, 2021 11:01 pm
markol wrote: Thu Aug 26, 2021 5:52 pm I have a problem in dark mode. I set Breeze Dark theme but some gtk apps do not follow theme settings: Audacious, Synaptic, and even MX Package Installer and MX Tools.
Looks like it's a known problem since plasma 5.17 (or is it 5.19?) because there is no more Breeze Dark, but only Breeze and it is expected gtk3+ apps to follow settings. But they don't :)
If I change gtk theme (Settings -> Application Style -> Configure GNOME/GTK....) to Adwaita Dark, Audacious changes but both package managers do not (even after reboot)
Same problem exists in Debian 11 KDE

Oh, almost forgot... no problems installing HP network printer (HP OfficeJet Pro 8710) via Settings -> Printers :)
Note that the mx apps are not gtk but qt based.

Thank you for clarification!

But the question remains, how to unify the looks of all apps? Not a real problem, but annoying af.

Posted: **Fri Aug 27, 2021 2:50 am**

I did the upgrade, as detailed here, from MX 19 ahs kde to MX 21 kde.
https://mxlinux.org/wiki/upgrading-from ... nstalling/
I had a little problem with bluetooth: I have BOSE bluetooth headphones, and when I switched them to headset mode (that's the mode in which the mic works), and did a Google Meet session with someone, he heard loud interference that made it hard to understand what I was saying. When I switched to the high fidelity mode (in which the mic does not work) and I used a USB-connected mic, the screeching noise stopped.

I tested the headphones afterwards on a different OS, and they worked as expected, so I am ruling out hardware failure.

I have since then rolled back to MX 19, but if anyone out there has a bluetooth headphone, please test for this issue. Preferably on a real (not VM) system.

Posted: **Fri Aug 27, 2021 3:27 am**

@shmu26 Try lowering the mic input level and check.

Posted: **Fri Aug 27, 2021 3:31 am**

markol wrote: Fri Aug 27, 2021 2:47 am
asqwerth wrote: Thu Aug 26, 2021 11:01 pm
markol wrote: Thu Aug 26, 2021 5:52 pm I have a problem in dark mode. I set Breeze Dark theme but some gtk apps do not follow theme settings: Audacious, Synaptic, and even MX Package Installer and MX Tools.
Looks like it's a known problem since plasma 5.17 (or is it 5.19?) because there is no more Breeze Dark, but only Breeze and it is expected gtk3+ apps to follow settings. But they don't :)
If I change gtk theme (Settings -> Application Style -> Configure GNOME/GTK....) to Adwaita Dark, Audacious changes but both package managers do not (even after reboot)
Same problem exists in Debian 11 KDE

...
Note that the mx apps are not gtk but qt based.
Thank you for clarification!

But the question remains, how to unify the looks of all apps? Not a real problem, but annoying af.

Question 1: are you sure the main MX Tools window does not follow the Plasma Breeze theming (with dark colour scheme) ? I've not installed MX KDE yet as I've not had time. All I know is that my MX XFCE alpha, which I installed plasma onto, does have MX Tools follow the Breeze theming with the same dark colour scheme I set. As do the NON-ROOT mx apps. These are all Qt.

Question 2: is adwaita dark preinstalled in MX21 KDE beta? If it's not, how did you install it? It's preinstalled in the xfce alpha and beta but I'm unsure about the KDE version.

Package managers run as root, so if your themes are installed in your home folder your root applications (both package managers) won't apply those themes. You will need to move your gtk themes to /usr/share/themes for root gtk apps to use them.

Because my adwaita dark is in root, Synaptic does use that theme if I set it in (Settings -> Application Style -> Configure GNOME/GTK....) .

MXPI won't be changed by that gtk theme in root since it's Qt. However, I confirm that changing to Breeze Dark colour scheme (which is in /usr/share) does not seem to make MXPI follow the dark colours. Not sure why.

Perhaps someone else on KDE beta can chip in. I won't have time to test it until next week.

It might be that some env setting needs to be changed in root, so that root apps are also affected?

Posted: **Fri Aug 27, 2021 4:50 am**

asqwerth wrote: Fri Aug 27, 2021 3:31 am
markol wrote: Fri Aug 27, 2021 2:47 am
asqwerth wrote: Thu Aug 26, 2021 11:01 pm Note that the mx apps are not gtk but qt based.
Thank you for clarification!

But the question remains, how to unify the looks of all apps? Not a real problem, but annoying af.
Question 1: are you sure the main MX Tools window does not follow the Plasma Breeze theming (with dark colour scheme) ? I've not installed MX KDE yet as I've not had time. All I know is that my MX XFCE alpha, which I installed plasma onto, does have MX Tools follow the Breeze theming with the same dark colour scheme I set. As do the NON-ROOT mx apps. These are all Qt.

Question 2: is adwaita dark preinstalled in MX21 KDE beta? If it's not, how did you install it? It's preinstalled in the xfce alpha and beta but I'm unsure about the KDE version.

Package managers run as root, so if your themes are installed in your home folder your root applications (both package managers) won't apply those themes. You will need to move your gtk themes to /usr/share/themes for root gtk apps to use them.

Because my adwaita dark is in root, Synaptic does use that theme if I set it in (Settings -> Application Style -> Configure GNOME/GTK....) .

MXPI won't be changed by that gtk theme in root since it's Qt. However, I confirm that changing to Breeze Dark colour scheme (which is in /usr/share) does not seem to make MXPI follow the dark colours. Not sure why.

Perhaps someone else on KDE beta can chip in. I won't have time to test it until next week.

It might be that some env setting needs to be changed in root, so that root apps are also affected?

1. It started when I changed colors (Settings -> Colors... or was it Application Style?) to something else and then back. However apps still use the light (default?) theme

2. Adwaita Dark is not included by default, I installed it via PM (gnome-themes-extra)

3. Regarding your comment "Package managers run as root, so if your themes are installed in your home folder your root applications (both package managers) won't apply those themes." I ran System Settings as root

Code: Select all

/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu systemsettings5

and tried to set Breeze Dark. Theme was set, but colors did not change so I checked the "Colors". There was an error message stating "The color scheme 'Breeze Dark' is not installed. Selecting the default theme instead.". I also noticed that there was no "Configure GNOME/GTK Application Style" button in Settings -> Application Style.
Nothing else could be done so I closed it.

I added the row

Code: Select all

gtk-application-prefer-dark-theme=true

to /usr/share/themes/Breeze-Dark/settings.ini and MX tools (including MX PM) went dark. Great success!

No luck with Audacious so I installed Breeze-Darker gtk theme, which works fine for now.

Only Synaptic remains untouched by the dark :)

Posted: **Fri Aug 27, 2021 5:06 am**

@markol

I can't help any further, since I'm not on KDE beta.

All I can say is that a normal install of plasma onto Xfce alpha was able to get Synaptic on Adwaita dark (preinstalled) using Plasma Settings Manager run as user, with the GTK applications setting.

I also didn't need to mess around to get MX Tools (non root main window and the non-root mx apps) to follow the Breeze theme plus colour scheme (which is my own mod made from Breeze Dark colour scheme). [ADDED - I also switched back to original Breeze Dark colour scheme to test - no problem with non-root MX apps]

I don't really mind MXPI (and root mx apps) showing up in breeze light (which it has been doing in MX19 KDE) since I like to have a differentiation between root and user apps.

Posted: **Fri Aug 27, 2021 8:16 am**

If the programs running as root don't match the theme I guess you could do something like "sudo systemsettings5" and set the theme there to match the theme for regular apps. I don't know if that's the recommended way, probably not, but it worked when I tried.

Posted: **Fri Aug 27, 2021 9:11 am**

KDE5.20 — Lock and Unlock the desktop — The moderator has asked me to repost this here. It will still be a valid idea after MX21KDE has gone final:

I know that MX21KDE hasn't gone final yet, but here's an idea you might want to try if you are testing it, and it will still work after it's gone final:

One of the better things about the version of KDE being used in MX21 Beta, is the absence of the hamburger or its b*st*rd offspring, the ham sandwich. More than anything, I really didn't like that, in the older version shipped with MX19, there were multiple menus all over the place with the option to lock/unlock the plasmoid layout. But with the new version, there is no way at all! What this post describes is a way to put a single Lock/Unlock applet on a panel.

Anyway, I did a search on Google and some clever person at Reddit had the solution to a lock which I then adapted using the "Configurable Button" plasmoid which you can get from the KDE store. Maybe you can get it from "Discover" but I've already deleted that.

You add a "Configurable Button" to your desktop or panel. This enables you to add two alternating scripts, an On-script and Off script, each with their own icon. The Off script should be your start-up mode, so if you want to start the desktop with the desktop locked, your Off-Script will be:

Code: Select all

qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(true)"

To unlock the desktop, the On-Script is:

Code: Select all

qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(false)"

For the icons, I've looked in "all" and searched on lock, and found an open padlock icon for the on-script, and a closed one for the off-script. Don't add a Plasmoid Label (leave it blank) because that will appear as text on the panel next to the Icon which will take up space. It would have been nice if the Configurable Button's author made that a Pop-Up text instead.

To allow for the desktop to start Locked you need to create two scripts, I put them in /usr/local/bin/ and saved them as root. Once saved, right-click on their icons in a Root Dolphin in order to set the properties to allow them to be executed.

First is lock-desktop

Code: Select all

#!/bin/bash

sleep 10

qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(true)"

Second is lock-desktop-startup

Code: Select all

#!/bin/bash

lock-desktop &

Having two executable files might appear complicated, but doing it this way allows the locking to be delayed by the number of seconds after "sleep", while control is handed back to the system to get on with other stuff. Otherwise the KDE start-up sequence will unlock the desktop again. You have to add the lock-desktop-startup in the KDE System Settings under Startup and Shutdown > Autostart > Login Scripts

Now when you log in, your Panels will be locked, and you have to click on the padlock icon to unlock them.

P.S. Don't try this with MX19. I did, and some icons on my panels became permanently locked! And you're still stuck with the Lock/Unlock options on the panel in any case.

Posted: **Fri Aug 27, 2021 9:26 am**

Choice of Package Managers

I've half-raised this and others have mentioned it too, but I think that MX-KDE should stick with apt-notifier to work alongside mx-package-installer, with synaptic as backup. Although Discover is part of KDE, apt-notifier is part of MX linux, and I think that should be the default.

I remember adding a Plasmoid from the KDE store that didn't work in MX19KDE, but found if I used a slightly earlier version it worked just fine. If Discover automatically updates Plasmoids (something that the MX developers would have no control over), we may find that as the KDE version advances, but Debian and therefore MX stick with 5.20, that many plasmoids will suddenly stop working as they've been updated to a version that is incompatible with KDE5.20. Perhaps Discover takes the KDE version into account when updating plasmoids, but, again, it's something that MX has no control over. The time to look for updated plasmoids is when MX22 or 23 is released and we have a later version of KDE. Until then, I prefer to have control over my own plasmoids!

P.S. I do approve of dropping muon. When I installed MX19KDE it was the first thing I got rid of!

Posted: **Fri Aug 27, 2021 11:03 am**

Adrian wrote: Fri Aug 27, 2021 8:16 am If the programs running as root don't match the theme I guess you could do something like "sudo systemsettings5" and set the theme there to match the theme for regular apps. I don't know if that's the recommended way, probably not, but it worked when I tried.

I did, but there was an error message stating "The color scheme 'Breeze Dark' is not installed."

Edit: Since sudo systemsettings5 doesn't really change anything (in this case), I logged in as root (edited sddm.conf to allow it) and installed breeze-gtk theme. Synaptic has finally fallen to the dark side.

Posted: **Fri Aug 27, 2021 12:52 pm**

Great job with this MX-KDE release MX team! Many thanks!

Some notes:
Installed without any errors on my desktop.
Sharing folders using Dolphin is super easy :-)
Accessing samba shares on my network with Dolphin also worked very well.
After reading several posts here I decided to install MX Updater and uninstalled plasma-discover. Hopefully that won't cause issues. I havn't noticed any so far.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 root=UUID=<filter> ro quiet 
           splash init=/lib/systemd/systemd 
           Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM Distro: MX-21_x64 Wildflower August 22  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASRock model: N/A serial: <filter> UEFI: American Megatrends v: L0.01 date: 07/17/2019 
CPU:       Topology: Quad Core model: Intel Core i3-9100 bits: 64 type: MCP arch: Kaby Lake family: 6 model-id: 9E (158) 
           stepping: B (11) microcode: EA L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 
           Speed: 2802 MHz min/max: 800/4200 MHz Core speeds (MHz): 1: 2802 2: 1949 3: 3636 4: 3774 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] 
           vendor: ASRock 8th Gen Core Processor Gaussian Mixture Model driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:3e91 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 21.1.5 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:a348 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel port: efa0 bus ID: 00:1f.6 
           chip ID: 8086:15bc 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 4.78 TiB used: 1.21 TiB (25.2%) 
           ID-1: /dev/nvme0n1 vendor: Patriot model: P300 256GB size: 238.47 GiB block size: physical: 512 B 
           logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: S06148B0 scheme: GPT 
           ID-2: /dev/sda vendor: Seagate model: ST4000DM000-1F2168 size: 3.64 TiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: 5900 rpm serial: <filter> rev: CC54 scheme: GPT 
           ID-3: /dev/sdb vendor: Western Digital model: WD10EZRX-00A8LB0 size: 931.51 GiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1A01 scheme: MBR 
Partition: ID-1: / raw size: 230.19 GiB size: 225.52 GiB (97.97%) used: 10.85 GiB (4.8%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 46.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
           2: deb http://deb.debian.org/debian-security/ bullseye/updates main contrib non-free
           3: deb-src http://deb.debian.org/debian/ bullseye main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/microsoft-edge-beta.list 
           1: deb [arch=amd64] http://packages.microsoft.com/repos/edge/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
           2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
Info:      Processes: 195 Uptime: 3h 40m Memory: 15.30 GiB used: 989.4 MiB (6.3%) Init: systemd v: 247 runlevel: 5 
           default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in running in: quick-system-in inxi: 3.0.36

Posted: **Fri Aug 27, 2021 3:41 pm**

I've half-raised this and others have mentioned it too, but I think that MX-KDE should stick with apt-notifier to work alongside mx-package-installer, with synaptic as backup. Although Discover is part of KDE, apt-notifier is part of MX linux, and I think that should be the default.

To the best of my knowledge, if one has added widgets from the KDE store via Discover, any updates to those widgets will not show up in apt-notifier. I could be wrong and welcome a confirmation or correction. Personally I do install apt-notifier but leave Discover installed.

Posted: **Fri Aug 27, 2021 4:31 pm**

richb wrote: Fri Aug 27, 2021 3:41 pm
I've half-raised this and others have mentioned it too, but I think that MX-KDE should stick with apt-notifier to work alongside mx-package-installer, with synaptic as backup. Although Discover is part of KDE, apt-notifier is part of MX linux, and I think that should be the default.
To the best of my knowledge, if one has added widgets from the KDE store via Discover, any updates to those widgets will not show up in apt-notifier. I could be wrong and welcome a confirmation or correction. Personally I do install apt-notifier but leave Discover installed.

But how do you disable Discovery notifications?

Posted: **Fri Aug 27, 2021 4:39 pm**

markol wrote: Fri Aug 27, 2021 4:31 pm
But how do you disable Discovery notifications?

I couldn't work that out either, which is why I ended up removing it.

Posted: **Fri Aug 27, 2021 4:43 pm**

davemx wrote: Fri Aug 27, 2021 4:39 pm
markol wrote: Fri Aug 27, 2021 4:31 pm
But how do you disable Discovery notifications?
I couldn't work that out either, which is why I ended up removing it.

I don't. Does not bother be.
EDIT: You could disable popups for Discover in System Settings>Notifications.

Posted: **Fri Aug 27, 2021 8:22 pm**

richb wrote: Fri Aug 27, 2021 4:43 pm
davemx wrote: Fri Aug 27, 2021 4:39 pm
markol wrote: Fri Aug 27, 2021 4:31 pm
But how do you disable Discovery notifications?
I couldn't work that out either, which is why I ended up removing it.
I don't. Does not bother be.
EDIT: You could disable popups for Discover in System Settings>Notifications.

I found the above mentioned setting for Discovery does indeed prevent Discovery notifications. I can get notifications from only from MX Updater and still have Discovery installed.

One reason for keeping Discovery for me is it's easy to install an application from a downloaded deb installer. Just click on the deb installer and Discovery opens and allows you to install the app with a button click. Of course you can always just right click on the deb installer and choose "Install deb files" which is just as easy without Discovery installed.

Posted: **Sat Aug 28, 2021 8:36 am**

Is anybody still having Dolphin issues? Can you please remove the .config/session/dolphin_dolphin_dolphin file and let me know if fixes it?

Posted: **Sat Aug 28, 2021 9:34 am**

VCR58 wrote: Fri Aug 27, 2021 8:22 pm
...I found the above mentioned setting for Discovery does indeed prevent Discover notifications. I can get notifications from only from MX Updater and still have Discovery installed.

I was wrong. I just got some updates today and both Discover and MX Updater notifications showed up in the tray even though popups were disabled for Discovery.

Posted: **Sat Aug 28, 2021 11:37 am**

Adrian wrote: Sat Aug 28, 2021 8:36 am Is anybody still having Dolphin issues? Can you please remove the .config/session/dolphin_dolphin_dolphin file and let me know if fixes it?

Very weird. I hadn't booted the testing machine up since bringing this up, and successfully launching Dolphin from the terminal per DO's suggestion: dolphin --new-window.

So I see your post and fire it up again. Dolphin is now launching just fine, multiple times, without applying your fix.

Posted: **Sat Aug 28, 2021 11:39 am**

uncle mark wrote: Sat Aug 28, 2021 11:37 am
Adrian wrote: Sat Aug 28, 2021 8:36 am Is anybody still having Dolphin issues? Can you please remove the .config/session/dolphin_dolphin_dolphin file and let me know if fixes it?
Very weird. I hadn't booted the testing machine up since bringing this up, and successfully launching Dolphin from the terminal per DO's suggestion: dolphin --new-window.

So I see your post and fire it up again. Dolphin is now launching just fine, multiple times, without applying your fix.

doing the --new-window essential resets that session file, so likely same effect anyway.

however we plan to remove the session file as part of the installer's setup routines when saving desktop changes.

Posted: **Sat Aug 28, 2021 12:04 pm**

dolphin_oracle wrote: Sat Aug 28, 2021 11:39 am
uncle mark wrote: Sat Aug 28, 2021 11:37 am
Adrian wrote: Sat Aug 28, 2021 8:36 am Is anybody still having Dolphin issues? Can you please remove the .config/session/dolphin_dolphin_dolphin file and let me know if fixes it?
Very weird. I hadn't booted the testing machine up since bringing this up, and successfully launching Dolphin from the terminal per DO's suggestion: dolphin --new-window.

So I see your post and fire it up again. Dolphin is now launching just fine, multiple times, without applying your fix.
doing the --new-window essential resets that session file, so likely same effect anyway.

however we plan to remove the session file as part of the installer's setup routines when saving desktop changes.

Gotchya.

Any idea about the missing menu buttons for Reboot and Shutdown in the main menu?

Posted: **Sat Aug 28, 2021 12:47 pm**

uncle mark wrote: Sat Aug 28, 2021 12:04 pm
dolphin_oracle wrote: Sat Aug 28, 2021 11:39 am
uncle mark wrote: Sat Aug 28, 2021 11:37 am

Very weird. I hadn't booted the testing machine up since bringing this up, and successfully launching Dolphin from the terminal per DO's suggestion: dolphin --new-window.

So I see your post and fire it up again. Dolphin is now launching just fine, multiple times, without applying your fix.
doing the --new-window essential resets that session file, so likely same effect anyway.

however we plan to remove the session file as part of the installer's setup routines when saving desktop changes.
Gotchya.

Any idea about the missing menu buttons for Reboot and Shutdown in the main menu?

you mean these?

Posted: **Sat Aug 28, 2021 12:50 pm**

Yes. On my new fresh install, only the Logout button appears.

Posted: **Sat Aug 28, 2021 1:37 pm**

uncle mark wrote: Sat Aug 28, 2021 12:50 pm Yes. On my new fresh install, only the Logout button appears.

That’s not one I can duplicate yet. Is there space for those buttons or just no buttons at all?

Posted: **Sat Aug 28, 2021 1:39 pm**

dolphin_oracle wrote: Sat Aug 28, 2021 1:37 pm
uncle mark wrote: Sat Aug 28, 2021 12:50 pm Yes. On my new fresh install, only the Logout button appears.
That’s not one I can duplicate yet. Is there space for those buttons or just no buttons at all?

Not there and no space for them. There's a divider just above the one Logout button.

Not a big deal for me, I usually don't even use those buttons, and this is a beta after all, but it's an anomaly that I felt should be reported.

Posted: **Sat Aug 28, 2021 2:18 pm**

dolphin_oracle wrote: Sat Aug 28, 2021 1:37 pm
uncle mark wrote: Sat Aug 28, 2021 12:50 pm Yes. On my new fresh install, only the Logout button appears.
That’s not one I can duplicate yet. Is there space for those buttons or just no buttons at all?

All three appear on my install.

Posted: **Sat Aug 28, 2021 2:27 pm**

uncle mark wrote: Sat Aug 28, 2021 1:39 pm
dolphin_oracle wrote: Sat Aug 28, 2021 1:37 pm
uncle mark wrote: Sat Aug 28, 2021 12:50 pm Yes. On my new fresh install, only the Logout button appears.
That’s not one I can duplicate yet. Is there space for those buttons or just no buttons at all?
Not there and no space for them. There's a divider just above the one Logout button.

Not a big deal for me, I usually don't even use those buttons, and this is a beta after all, but it's an anomaly that I felt should be reported.

it would be interesting to know two things in this order:

1. do they show up if you boot in systemd mode.
2. do they show up if you start up a live session, delete the session folder on the hard drive install, home/user/.config/session, and then boot back into your hard drive install.

Posted: **Sat Aug 28, 2021 3:48 pm**

problems in kde plasma beta 1 , where ? there are none that i know of i have tested it allready for 30 days , everthing works perfect
this respin of kde plasma beta 1 was allready finish the day after xfce beta 1 was released and there is nothing wrong with the damn thing at all.
https://www.youtube.com/watch?v=58AAIQ-LBy8

Posted: **Sat Aug 28, 2021 6:55 pm**

drogon69 wrote: Sat Aug 28, 2021 3:48 pm problems in kde plasma beta 1 , where ? there are none that i know of i have tested it allready for 30 days , everthing works perfect
this respin of kde plasma beta 1 was allready finish the day after xfce beta 1 was released and there is nothing wrong with the damn thing at all.
https://www.youtube.com/watch?v=58AAIQ-LBy8

Nice, but it looks like the only issue is theming consistency. Qt apps are dark while Gtk apps are light.

Posted: **Sat Aug 28, 2021 7:20 pm**

dolphin_oracle wrote: Sat Aug 28, 2021 2:27 pm
uncle mark wrote: Sat Aug 28, 2021 1:39 pm
dolphin_oracle wrote: Sat Aug 28, 2021 1:37 pm

That’s not one I can duplicate yet. Is there space for those buttons or just no buttons at all?
Not there and no space for them. There's a divider just above the one Logout button.

Not a big deal for me, I usually don't even use those buttons, and this is a beta after all, but it's an anomaly that I felt should be reported.
it would be interesting to know two things in this order:

1. do they show up if you boot in systemd mode.
2. do they show up if you start up a live session, delete the session folder on the hard drive install, home/user/.config/session, and then boot back into your hard drive install.

1. No
2. No

No change at all.

Posted: **Sat Aug 28, 2021 8:09 pm**

In a live-usb w/persistence, does this matter at the end of upgrade in terminal with apt-get full-upgrade?

Code: Select all

update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
I: The initramfs will attempt to resume from /dev/sdb1
I: (UUID=d88c19de-a940-423d-ae50-5e34a23d37ea)
I: Set the RESUME variable to override this.
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate temporary mdadm.conf file.

The initrd in /boot did get rebuilt:

Code: Select all

ls -l /boot/init*
-rw-r--r-- 1 root root 80315147 Aug 28 17:26 initrd.img-5.10.0-8-amd64

ADDED #1: I see that I posted this to the wrong thread. I'm not using the KDE beta, but just the main beta. I would have removed the post, but it doesn't look like removing is an option.
ADDED #2: I figured out the right thing to search for and see that this is the result of mdadm being installed but not being used. (mdadm is for raid)

Posted: **Sun Aug 29, 2021 12:35 am**

I've been using Xfce since v2.x then 3.x now 4.x.
Was a big fan, even a devotee of Kde 3.x but never Kde 4!

Have MX-21-Xfce-b1 installed on my daily ride.
Voted for only Xfce thinking that I wasn't interested in Kde.
Reading the forum I decided that perhaps it was worth a look.

Looking forward to giving KDE5 & Qt some space.

Posted: **Sun Aug 29, 2021 1:17 am**

Mauser wrote: Sat Aug 28, 2021 6:55 pm
drogon69 wrote: Sat Aug 28, 2021 3:48 pm problems in kde plasma beta 1 , where ? there are none that i know of i have tested it allready for 30 days , everthing works perfect
this respin of kde plasma beta 1 was allready finish the day after xfce beta 1 was released and there is nothing wrong with the damn thing at all.
https://www.youtube.com/watch?v=58AAIQ-LBy8
Nice, but it looks like the only issue is theming consistency. Qt apps are dark while Gtk apps are light.

Qt apps are dark while Gtk apps are light .
what if qt apps are light and gtk apps are dark , XXXXX..
or bout dark is that an issue !! the only issue that i know of is people that say there is a problem with kde plasma 5 in mxlinux that is my issue , there are none.
in alot of cases mxlinux wil run on amd athlon like a charme , but the problem with alot is people need the last drivers on new pc like nvidia drivers under linux or the last kernels but that do not work like that under some hardware , why the XXXX you need nvidia drivers on open source linux distro , that is a big issue for me if people do this.

moderator comment: Please follow the forum rules and don't attack other users. Some passages deleted or X:ed out.
Utopia

Posted: **Sun Aug 29, 2021 1:49 am**

drogon69 wrote: Sun Aug 29, 2021 1:17 am
Mauser wrote: Sat Aug 28, 2021 6:55 pm
drogon69 wrote: Sat Aug 28, 2021 3:48 pm problems in kde plasma beta 1 , where ? there are none that i know of i have tested it allready for 30 days , everthing works perfect
this respin of kde plasma beta 1 was allready finish the day after xfce beta 1 was released and there is nothing wrong with the damn thing at all.
https://www.youtube.com/watch?v=58AAIQ-LBy8
Nice, but it looks like the only issue is theming consistency. Qt apps are dark while Gtk apps are light.
Qt apps are dark while Gtk apps are light .
what if qt apps are light and gtk apps are dark , o man you dont now what you are talking about.
or bout dark is that an issue !! the only issue that i know of is people that say there is a problem with kde plasma 5 in mxlinux that is my issue , there are none.
in alot of cases mxlinux wil run on amd athlon like a charme , but the problem with alot is people need the last drivers on new pc like nvidia drivers under linux or the last kernels but that do not work like that under some hardware , why the hell you need nvidia drivers on open source linux distro , that is a big issue for me if people do this.
if you want to run nvidia driver stay with windoze

Blocked for violating forum rules!

Posted: **Sun Aug 29, 2021 1:28 pm**

uncle mark wrote: Sat Aug 28, 2021 12:50 pm Yes. On my new fresh install, only the Logout button appears.

This is weird because I had this exact problem when I installed Debian11ß KDE, and I'm convinced it was a permissions problem because I logged in as root and all three icons were there. But I've not had this problem in MXß21-KDE at all.

Posted: **Thu Sep 02, 2021 12:32 am**

mx 21 kde- 64 beta working beautiful for me ... I downloaded several new wallpapers with no problems ... I have it installed on two different usb drives ... For some reason no uefi showed up on the installation disk.

Posted: **Sun Sep 05, 2021 7:26 am**

There is now a beta 2 thread available, this thread has been locked.

MX Linux Forum

MX-21 KDE beta 1 feedback thread

MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread

Re: MX-21 KDE beta 1 feedback thread