MX-21 KDE beta 1 feedback thread

[markol]

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.

[VCR58]

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 

[richb]

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.

[markol]

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?

[davemx]

But how do you disable Discovery notifications?

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

[richb]

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.

[VCR58]

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.

[Adrian]

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

[VCR58]

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

[uncle mark]

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.