MX-21 KDE/plasma RC1 feedback

[SwampRabbit]

As to Steam, I'm not so concerned about Steam itself so much as wanting to make sure I see all 32 and 64 bit packages. Again, how would I turn that 32 bit filter off? Or am I misunderstanding things?

Turn off what 32bit filter?

MPXI will install the amd64 (64bit) and i386 (32bit) packages needed for whatever it is you are installing. You don't need to "typically" go hunting for anything or see anything for 32bit or 64bit packages. If you're using a 64bit version of an OS its going to default show you amd64 (64bit) and the opposite if you installed the 32bit version of the OS. If a 64bit application needs 32bit components it will pull it in (hopefully) when installing. If you need to find the i386 (32bit) packages for whatever reason, you can use Synaptic... I have no clue if Discover can do this or not.

Now back on topic MX-21 KDE/plasma RC1 feedback please

[dolphin_oracle]

To be honest, I'm not too bothered about not being able to install Skype (via mxpi favourites) or Freetube (via flatpak) as I can install them using the deb files from their sites and they both seem to work just fine. I don't suppose this happened because I uninstalled plasma-discover and added synaptic and apt-notifier?

shouldn't have. skype is downloaded directly from microsoft. and remove of plasma-discover shouldn't have affected flatpak at all. unless it also removed mx-packageinstaller, which might in turn remove the flatpak backend.

[Arnox]

As to Steam, I'm not so concerned about Steam itself so much as wanting to make sure I see all 32 and 64 bit packages. Again, how would I turn that 32 bit filter off? Or am I misunderstanding things?

Turn off what 32bit filter?

MPXI will install the amd64 (64bit) and i386 (32bit) packages needed for whatever it is you are installing. You don't need to "typically" go hunting for anything or see anything for 32bit or 64bit packages. If you're using a 64bit version of an OS its going to default show you amd64 (64bit) and the opposite if you installed the 32bit version of the OS. If a 64bit application needs 32bit components it will pull it in (hopefully) when installing. If you need to find the i386 (32bit) packages for whatever reason, you can use Synaptic... I have no clue if Discover can do this or not.

Now back on topic MX-21 KDE/plasma RC1 feedback please

Alright, but why was Steam hidden in the stable repo then? It wasn't in 19.4.

[SwampRabbit]

Alright, but why was Steam hidden in the stable repo then? It wasn't in 19.4.

It isn’t and wasn’t ever “hidden”. That screenshot I did for you, that was on MX-19. Search the forum, the internet, the universe… you’ll see this answered the same way over and over.

It’s always been Steam:i386, you always have to search for the i386 (32bit) packages specifically on a amd64 (64bit) OS in Synaptic. I have no clue how Discover shows it.

Also I think we have only ever packed Steam a few times to get ahead of Debian to fix problems, it normally comes from Debian, the MX-21 version is coming from the Debian repos right now. Don’t like the answers, feel free to ask the same questions on their forums, they probably won’t be as accommodating.

[dolphin_oracle]

debian's package just downloads steam from valve anyway.

discover doesn't seem to have a way to show all multi-arch packages. will look into it. @Adrian

BTW, mx-packageinstaller ->popular apps installs the very same debian package, so there is no harm/no foul going that route. good report.

[Arnox]

Alright, but why was Steam hidden in the stable repo then? It wasn't in 19.4.

It isn’t and wasn’t ever “hidden”. That screenshot I did for you, that was on MX-19. Search the forum, the internet, the universe… you’ll see this answered the same way over and over.

It’s always been Steam:i386, you always have to search for the i386 (32bit) packages specifically on a amd64 (64bit) OS in Synaptic. I have no clue how Discover shows it.

Also I think we have only ever packed Steam a few times to get ahead of Debian to fix problems, it normally comes from Debian, the MX-21 version is coming from the Debian repos right now. Don’t like the answers, feel free to ask the same questions on their forums, they probably won’t be as accommodating.

Woah, I'm not trying to start a fight here at all. I also think I see where the misunderstanding is coming from. I said, "why was Steam hidden in the stable repo then? It wasn't in 19.4," but what I should have said was, "why is Steam hidden in the MX21 stable repo? It wasn't hidden in the 19.4 stable repo." I apologize for the bad wording.

But yes, according to @dolphin_oracle it seems that the MX Package Installer in 21 (which I'm assuming is nicknamed Discover, I've never heard that term before yet here) doesn't have any ways to show all the different architectures, so I suppose that explains things.

Oh yes, also another good thing to report. Boot times are now significantly faster than 19.4 both on SysVInit and systemd.

EDIT: Nope, Discover is a completely new application. I really don't know MX that well yet. lol

[sthras]

Hello i am new in this Forum!
I am not sure if it is there by default but although i created a root user during the installation process i have only one administrator user the user i created as normal user!
In KDE settings i ve tried to create a new root user but is impossible! No error at all!

Thanks in advance

Hello!
From the RC1 announcement. (Easy to miss.)

MX-21 Release Candidate 1 now available for testing purposes – MX Linux
https://mxlinux.org/blog/mx-21-release- ... -purposes/

Things that are new in MX-21 RC1:

User password (sudo) for admin tasks by default. You can switch this in mx-tweak->Other tab

Thanks Paul1149 my fault didnt see that..Maybe is important to have the possibility to change that in the installation Process!

Thanks a lot!

[Discostu]

On my Suface Pro 3 (in live usb mode) I can't connect to WiFi:
ksnip_20211009-025602.png

Code: Select all

System:
  Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash 
  lang=de_DE kbd=de tz=Europe/Berlin persist_all splasht 
  Desktop: KDE Plasma 5.20.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-21_KDE_RC1_x64 Wildflower October 5  2021 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Laptop System: Microsoft product: Surface Pro 3 v: 1 
  serial: <filter> 
  Mobo: Microsoft model: Surface Pro 3 v: 1 serial: <filter> 
  UEFI: American Megatrends v: 3.11.2550 date: 06/12/2018 
Battery:
  ID-1: BAT0 charge: 10.8 Wh condition: 36.9/42.2 Wh (88%) 
  volts: 6.8/7.6 model: LGC-LGC X883815 type: Li-ion serial: <filter> 
  status: Discharging cycles: 386 
CPU:
  Topology: Dual Core model: Intel Core i7-4650U bits: 64 type: MT MCP 
  arch: Haswell family: 6 model-id: 45 (69) stepping: 1 microcode: 24 
  L2 cache: 4096 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 18357 
  Speed: 2129 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 2129 
  2: 1729 3: 1505 4: 2058 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, 
  SMT vulnerable 
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no 
  microcode; SMT vulnerable 
  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: conditional, RSB filling 
  Type: srbds status: Vulnerable: No microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel Haswell-ULT Integrated Graphics vendor: Microsoft 
  driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0a26 
  Display: x11 server: X.Org 1.20.13 driver: modesetting 
  unloaded: fbdev,vesa compositor: kwin_x11 resolution: 2160x1440~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 5000 (HSW GT3) 
  v: 4.5 Mesa 21.2.1 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel v: kernel 
  bus ID: 00:03.0 chip ID: 8086:0a0c 
  Device-2: Intel 8 Series HD Audio vendor: Microsoft 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:9c20 
  Sound Server: ALSA v: k5.10.0-8-amd64 
Network:
  Device-1: Marvell 88W8897 [AVASTAR] 802.11ac Wireless vendor: SafeNet 
  driver: mwifiex_pcie v: 1.0 port: 3040 bus ID: 01:00.0 
  chip ID: 11ab:2b38 
  IF: mlan0 state: down mac: <filter> 
  Device-2: Marvell Bluetooth and Wireless LAN Composite Device 
  type: USB driver: btusb bus ID: 1-6:5 chip ID: 1286:204b 
  serial: <filter> 
Drives:
  Local Storage: total: 592.63 GiB used: 5.07 GiB (0.9%) 
  ID-1: /dev/sda vendor: Samsung model: MZMTE512HMHP-000MV 
  size: 476.94 GiB block size: physical: 512 B logical: 512 B 
  speed: 6.0 Gb/s serial: <filter> rev: 1M0Q scheme: GPT 
  ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra USB 3.0 
  size: 115.69 GiB block size: physical: 512 B logical: 512 B 
  serial: <filter> rev: 1.00 scheme: MBR 
Partition:
  ID-1: / raw size: N/A size: 6.08 GiB used: 54.4 MiB (0.9%) fs: overlay 
  source: ERR-102 
Sensors:
  System Temperatures: cpu: 47.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://security.debian.org/debian-security bullseye-security main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
  2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye ahs
Info:
  Processes: 220 Uptime: 5m Memory: 7.68 GiB used: 756.0 MiB (9.6%) 
  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 

It works in MX 19.

Network device 2 doesn't exist in my installation of MX 19. I don't know if the problem is related to that, that it tries connect via a wrong device.

[markol]

Spectacle in RC1 crashes every time I close it (verified on 2 machines)

Code: Select all

Application: Spectacle (spectacle), signal: Segmentation fault

[KCrash Handler]
#4  0x00005627d8928b00 in ?? ()
#5  0x00007f9cbc660b2b in ?? () from /lib/x86_64-linux-gnu/libkImageAnnotator.so.0
#6  0x00007f9cbc660d39 in ?? () from /lib/x86_64-linux-gnu/libkImageAnnotator.so.0
#7  0x00007f9cbc626e35 in ?? () from /lib/x86_64-linux-gnu/libkImageAnnotator.so.0
#8  0x00007f9cbc626f79 in ?? () from /lib/x86_64-linux-gnu/libkImageAnnotator.so.0
#9  0x00007f9cbc622cec in ?? () from /lib/x86_64-linux-gnu/libkImageAnnotator.so.0
#10 0x00007f9cbc622d89 in ?? () from /lib/x86_64-linux-gnu/libkImageAnnotator.so.0
#11 0x00007f9cbc6226fb in ?? () from /lib/x86_64-linux-gnu/libkImageAnnotator.so.0
#12 0x00007f9cbc621979 in kImageAnnotator::KImageAnnotator::~KImageAnnotator() () from /lib/x86_64-linux-gnu/libkImageAnnotator.so.0
#13 0x00007f9cbc621a09 in kImageAnnotator::KImageAnnotator::~KImageAnnotator() () from /lib/x86_64-linux-gnu/libkImageAnnotator.so.0
#14 0x00007f9cbacfcbde in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f9cbb7d2736 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00005627d848fafd in ?? ()
#17 0x00007f9cbacfcbde in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f9cbb7d2736 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00005627d8490c75 in ?? ()
#20 0x00005627d848be5b in ?? ()
#21 0x00007f9cba6b9d0a in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#22 0x00005627d848c71a in ?? ()
[Inferior 1 (process 22872) detached]

QSI

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 
           init=/lib/systemd/systemd 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 dm: SDDM Distro: MX-21_KDE_RC1_x64 Wildflower October 5  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: LENOVO product: 20378 v: Lenovo Y50-70 serial: <filter> Chassis: type: 10 v: Lenovo Y50-70 
           serial: <filter> 
           Mobo: LENOVO model: Lenovo Y50-70 v: 31900058WIN serial: <filter> UEFI: LENOVO v: 9ECN36WW(V2.00) date: 01/12/2015 
Battery:   ID-1: BAT1 charge: 44.0 Wh condition: 44.0/54.8 Wh (80%) volts: 8.0/7.4 model: LENOVO PABAS0241231 type: Li-ion 
           serial: <filter> status: Full 
           Device-1: hidpp_battery_0 model: Logitech MK700 serial: <filter> charge: 70% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: Quad Core model: Intel Core i7-4720HQ bits: 64 type: MT MCP arch: Haswell family: 6 model-id: 3C (60) 
           stepping: 3 microcode: 28 L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 41499 
           Speed: 2384 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 2384 2: 2911 3: 2536 4: 2582 5: 2207 6: 2103 7: 2386 
           8: 2991 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           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: conditional, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:0416 
           Device-2: NVIDIA GM107M [GeForce GTX 960M] vendor: Lenovo driver: N/A bus ID: 01:00.0 chip ID: 10de:139b 
           Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 21.2.1 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:03.0 chip ID: 8086:0c0c 
           Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:8c20 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8723BE PCIe Wireless Network Adapter vendor: Lenovo Z50-75 driver: rtl8723be v: kernel 
           port: 4000 bus ID: 08:00.0 chip ID: 10ec:b723 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo driver: r8169 v: kernel port: 3000 
           bus ID: 09:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 191.67 GiB (41.2%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB block size: physical: 512 B logical: 512 B 
           speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
Partition: ID-1: / raw size: 457.50 GiB size: 449.25 GiB (98.20%) used: 191.67 GiB (42.7%) fs: ext4 dev: /dev/sda2 
           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/sda3 
Sensors:   System Temperatures: cpu: 48.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://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://ftp.arnes.si/mirrors/mxlinux/packages/mx/repo/ bullseye main non-free
           2: deb https://ftp.arnes.si/mirrors/mxlinux/packages/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb http://linux.teamviewer.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/vscode.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/vscode stable main
Info:      Processes: 275 Uptime: 1h 59m Memory: 15.54 GiB used: 1.55 GiB (9.9%) 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 

[Arnox]

A small update. I seem to be getting weird installation issues left and right.

First, it was Kdenlive and not being able to use NVENC. Fixed using the flatpak version though. Thought the NVENC options in the Debian stable release were just dummied out Then it was WINE, seemingly installing correctly, but some features and menu entries weirdly seemed to be missing. Installing from the Popular Applications tab seemed to fix it though. Kind of... And then finally, what really made me suspicious, is that when I installed Virt-Manager, it didn't seem to install libvirtd. And when I look for QEMU and install it from either the MX Package Installer, Discover, or even apt-get as instructed by the QEMU site itself, it would only download the dummy file and NOTHING else.

Is this still me? Am I being stupid again? Is this just RC bugs? What is going on?

EDIT: Looking at the Debian package list on the official site again, it looks like libvirtd is not the correct "meta-package" name anymore. libvirt-daemon-system seems to be it. (https://packages.debian.org/bullseye/virt-manager) Also, the usual qemu package one would download to get all the other necessary packages seems to have been phased out as well and turned into a dummy package that doesn't do anything. (https://packages.debian.org/stable/qemu) So, the good news is, this doesn't seem to be an MX problem for those. The bad news is this is obviously incredibly frustrating. It's like, we've had these package names for years, and now suddenly, Debian's changing them all, and nobody has updated on their sites or the programs themselves what the package is ACTUALLY named in the repo anymore for fetching. And I wonder how far this goes too. How many packages are there that have been renamed but a package that depends on that package hasn't updated its dependency list at all?

Now, this is certainly not the end of the world, and in some cases like QEMU, it looks like they wanted to split up the main package and give users a choice of what versions they wanted. Nevertheless though, I just feel like Debian could have handled this better. I only found out the answer here myself because I'm a very persistent bastard. So many others might have just gotten super frustrated and given up entirely.