MX-21 KDE/plasma beta 2 feedback thread

[dolphin_oracle]

Minimize, maximize and close icons on Firefox still an issue.
They appear as expected with Breeze Dark.

Fail to appear (or slightly) with MX global themes.

Thanks I think I found the issue

[uncle mark]

Just another comment... I normally don't like bright or colorful or flashy or busy wallpapers and rarely like photographs... but the default wallpaper for KDE B2 is gorgeous. I might even keep it. :-)

Obligatory:

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_KDE_beta2_x64 Wildflower September 4  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: 48.1 Wh condition: 48.1/47.5 Wh (101%) 
  volts: 12.5/10.8 model: Panasonic AS10D51 type: Li-ion 
  serial: <filter> status: Full 
  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: 3989 
  Speed: 820 MHz min/max: 800/1000 MHz Core speeds (MHz): 1: 887 2: 814 
  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: 8.32 GiB (7.4%) 
  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: 105.93 GiB size: 103.70 GiB (97.90%) 
  used: 8.32 GiB (8.0%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 5.86 GiB used: 1.8 MiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) 
  dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 66.6 C mobo: N/A gpu: radeon temp: 66 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
  2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ 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: 173 Uptime: 5h 51m Memory: 3.57 GiB used: 1.37 GiB (38.3%) 
  Init: SysVinit v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 
  alt: 10 Shell: quick-system-in running in: quick-system-in 
  inxi: 3.0.36 

[danielson]

@dolphin_oracle - and thank you for this new beta release!
Previous one was too hard for me.
Hopefully, this beta will be less of a challenge.

@uncle mark - wallpaper is a definite keeper.
Trying to find a conky that blends in well with it can be a challenge though.

[uncle mark]

@uncle mark - wallpaper is a definite keeper.
Trying to find a conky that blends in well with it can be a challenge though.

Isn't that what Conky Toggle [off] is for?

[gsm]

Two problems:
1) Downloaded new global themes take a long time to be installed and don't display icons correctly after apply.
After a complete re installation of MX-21 KDE Beta 2, it seemed to be ok.
Maybe things got corrupted, when i closed the global theme installation windows to early, before all themes had been installed, or i changed to a new theme, while other themes still being installed.
2) At the taskbar the widget for the virtual desktops is initially not displaying the desktop numbers correctly, after clicking with the right mouse button and then adding a desktop. The desktop numbers are shifted downwards or not aligned correctly. This can be avoided by increasing the taskbar height to 40 or more. After a reboot the numbers are placed at the correct position again.

[danielson]

Took at least 2 minutes to install a new global theme here.

Firefox minimize, maximize and close icons were just fine this a.m. until after playing around with a new global theme.
Maybe a reboot will fix the looks?

Workspace icon no.1 gives me the impression of being of 2:
https://imgur.com/YREfx6U

- - - - -


@uncle mark trying to match a conky like a tie with a shirt is sometimes a bit of a challenge.

[richb]

Took at least 2 minutes to install a new global theme here.

Firefox minimize, maximize and close icons were just fine this a.m. until after playing around with a new global theme.
Maybe a reboot will fix the looks?

Workspace icon no.1 gives me the impression of being of 2:
https://imgur.com/YREfx6U

- - - - -


@uncle mark trying to match a conky like a tie with a shirt is sometimes a bit of a challenge.

Global theme changes most everything theme wise. To get minimize, maximize and close icons back use Application Style>Window decorations.

[dolphin_oracle]

if the global theme does not define a kwin theme, or if the theme it defines is missing, you'll get missing icons in gtk3 apps like firefox. I think Qt apps will default back to breeze.

[danielson]

if the global theme does not define a kwin theme, or if the theme it defines is missing, you'll get missing icons in gtk3 apps like firefox. I think Qt apps will default back to breeze.

Is this what got Dominic Hayes frustrated?

"I’m writing this to announce a change that’ll be hitting Feren OS next year, a significant change at that. I’m writing this also because I, Dominic, am frustrated — frustrated with the situation with GTK+ being janky and thus having broken theming functionality (of whom they blame themes themselves for) despite Qt doing all of that, even with custom/complex controls, just fine, and frustrated about users not getting to know it’s not all sunshine and rainbows when it comes to theming in GTK+, much as many will try to make everyone else think it is.
I could also mention how some GTK+ developers even go out calling stylesheets out for issues, that could just be bug reported, to further incriminate ‘themes’ in GTK+ instead of adding a proper theme API to fix all that, but… that’d be a discussion for elsewhere.
I hope you’re happy, said GTK+ developers, with what’s being announced below, and with no further ado:
There is no future for the Feren OS GTK+ theme beyond GTK+ 3
I’ve been tossing this idea around for a while now, and honestly with the GTK+ theme situation just getting worse and worse now I can confidently make this decision: Feren OS’s GTK theme will NOT be developed for GTK+ 4 and beyond.
There, honestly, just is no future for it, nor is there future for any theme really outside of Adwaita if GTK+ keeps going the direction it is going nowadays..."

https://medium.com/feren-os/the-future- ... 051a64e6de

[dolphin_oracle]

Nah, I think we is upset over gtk4 supposedly more limited theming avenues.