MX Modified - Latest MX KDE 5.22 Using MX21 beta

[MAYBL8]

Unless I am mis reading something that will work as long as "Bullseye" is considered "testing". Once it leaves testing and becomes stable MX-21 won't get KDE updates that norbert has.

[SwampRabbit]

A potential downside to using Norbert’s repos is any conflicts with Qt packages in the Stable Bullseye, especially building any of the ones we do for users. We don’t want to jump to these repos and find out we have long term issues with non-KDE packages in a Stable Bullseye. Remember Debian supports all packages, not just the KDE specific ones.

Norbert would know if this could be a problem really or not, but for the Stable MX-KDE, I’d prefer to stick with the KDE in Bullseye to reduce any headaches.

[andyprough]

Unless I am mis reading something that will work as long as "Bullseye" is considered "testing". Once it leaves testing and becomes stable MX-21 won't get KDE updates that norbert has.

I don't think it will matter - norbert just uses "testing" as part of his repo name. From what he said yesterday, he "will provide builds for *bullseye* as long as possible (that is, as long as Plasma doesn't switch to Qt6, but that is far off)." So, since Bullseye will soon be stable, I would assume there's no problem with his repos continuing to work on it.

[andyprough]

A potential downside to using Norbert’s repos is any conflicts with Qt packages in the Stable Bullseye, especially building any of the ones we do for users. We don’t want to jump to these repos and find out we have long term issues with non-KDE packages in a Stable Bullseye. Remember Debian supports all packages, not just the KDE specific ones.

Norbert would know if this could be a problem really or not, but for the Stable MX-KDE, I’d prefer to stick with the KDE in Bullseye to reduce any headaches.

Yup, and it's very late to switch just prior to the MX21 launch, and it's really not in keeping with MX's philosophy of providing the stable base PLUS other stuff. I was thinking that maybe MX could make all of norbert's stuff available as a big backport meta-update, subject to testing and so forth. Similar to how the newer LibreOffice stuff is made available as a backport meta-update, only in this case it would be much bigger.

[norbert]

Unless I am mis reading something that will work as long as "Bullseye" is considered "testing". Once it leaves testing and becomes stable MX-21 won't get KDE updates that norbert has.

No, that is not the intention. I will continue building for bullseye even after it was released. I only mentioned that bullseye is the current testing to make clear that I cannot support the **current** stable (buster).

[MAYBL8]

Guys I am having an issue with my laptop. I thought I would post it here since I am on experimental and dev's won't help.
It seems that when I close the lid on my laptop, after I open it back up DNS is not working. I can ping an ip address but web pages won't load.
I have done some research but can't come up with anything.
Thanks
Dan

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-1-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1-amd64 root=UUID=<filter> 
           ro quiet splash model=hp model=laptop modprobe.nouveau=0 "acpi_osi=!Windows 2017" 
           Desktop: KDE Plasma 5.22.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 dm: SDDM 
           Distro: MX-19.4_KDE_x64 patito feo November 11 2020 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Convertible System: HP product: HP Spectre x360 Convertible 15-df1xxx v: N/A 
           serial: <filter> Chassis: type: 31 serial: <filter> 
           Mobo: HP model: 863F v: 54.24 serial: <filter> UEFI: AMI v: F.25 date: 04/01/2021 
Battery:   ID-1: BAT0 charge: 51.5 Wh condition: 67.2/67.2 Wh (100%) volts: 12.2/11.6 model: HP Primary 
           type: Li-ion serial: <filter> status: Unknown cycles: 157 
           Device-1: hid-0018:04F3:2992.0001-battery model: ELAN2514:00 04F3:2992 serial: N/A charge: N/A 
           status: N/A 
           Device-2: hidpp_battery_0 model: Logitech Wireless Mouse M325 serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: Quad Core model: Intel Core i7-10510U bits: 64 type: MT MCP arch: Kaby Lake family: 6 
           model-id: 8E (142) stepping: C (12) microcode: EA L2 cache: 8192 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 36799 
           Speed: 800 MHz min/max: 400/4900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 799 5: 800 6: 800 
           7: 799 8: 799 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           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: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds mitigation: TSX disabled 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: Hewlett-Packard driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:9b41 
           Device-2: NVIDIA GP108M [GeForce MX250] vendor: Hewlett-Packard driver: nvidia v: 470.57.02 
           bus ID: 3b:00.0 chip ID: 10de:1d13 
           Display: x11 server: X.Org 1.20.11 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa 
           alternate: nv compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel Comet Lake PCH-LP cAVS vendor: Hewlett-Packard driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:02c8 
           Device-2: DisplayLink Dell Universal Dock D6000 type: USB driver: cdc_ncm,snd-usb-audio 
           bus ID: 4-1.1:3 chip ID: 17e9:6006 serial: <filter> 
           Sound Server: ALSA v: k5.10.0-1-amd64 
Network:   Device-1: Intel Comet Lake PCH-LP CNVi WiFi driver: iwlwifi v: kernel port: 4000 bus ID: 00:14.3 
           chip ID: 8086:02f0 
           IF: wlan0 state: up mac: <filter> 
           IF-ID-1: usb0 state: up speed: N/A duplex: N/A mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 213.46 GiB (22.9%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 2B2QEXM7 
           scheme: GPT 
Partition: ID-1: / raw size: 40.00 GiB size: 39.12 GiB (97.81%) used: 11.95 GiB (30.5%) fs: ext4 
           dev: /dev/nvme0n1p6 
           ID-2: /home raw size: 564.57 GiB size: 554.71 GiB (98.25%) used: 201.44 GiB (36.3%) fs: ext4 
           dev: /dev/nvme0n1p7 
           ID-3: swap-1 size: 16.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/nvme0n1p9 
Sensors:   System Temperatures: cpu: 58.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/anydesk-stable.list 
           1: deb http://deb.anydesk.com/ all main
           No active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.us.debian.org/debian/ unstable main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/home:stevenpusser:QCAD.list 
           1: deb http://download.opensuse.org/repositories/home:/stevenpusser:/QCAD/Debian_Unstable/ /
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           2: deb http://mxrepo.com/mx/repo/ buster ahs
           Active apt repos in: /etc/apt/sources.list.d/npreining.list 
           1: deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/frameworks/Debian_Unstable/ ./
           2: deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/plasma522/Debian_Unstable/ ./
           3: deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/apps2104/Debian_Unstable/ ./
           4: deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other/Debian_Unstable/ ./
           5: deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other-deps/Debian_Unstable/ ./
           Active apt repos in: /etc/apt/sources.list.d/various.list 
           1: deb http://mxrepo.com/mx/repo/ buster ahs-staging
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 277 Uptime: 1h 33m Memory: 15.28 GiB used: 3.05 GiB (20.0%) Init: systemd v: 241 
           runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10/8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

[asqwerth]

You can't be using mx21 beta if your mx repos are buster?

[andyprough]

You can't be using mx21 beta if your mx repos are buster?

He doesn't need mx21 beta, he knows how to run Norbert's KDE packages with the MX Buster repos.

It's hard to do though. Not surprising that he's having the networking issue. Networking is usually the first thing that goes out for me. @MAYBL8, have you been able to re-establish your network connection through the normal method of killing the NetworkManager process and re-starting it?

[MAYBL8]

No killing the process doesn't work if you mean running :
sudo service NetworkManager restart.

Only restarting the laptop seems to work.

[andyprough]

No killing the process doesn't work if you mean running :
sudo service NetworkManager restart.

Only restarting the laptop seems to work.

No, you have to run 'ps -A | grep Net' (or something like that), find the NetworkManager process ID number, then 'sudo kill -KILL [processID#]'. Then do a 'sudo NetworkManager start'. Trying it with restart never worked for me. And even finding and killing the process and starting from scratch didn't work all the time.

But then again, I don't ever use hybernate or close the laptop lid, so you are working in territory I have not explored at all. What I have done on all my machines is use the tlpui program to set networking so that it is not ever put to sleep. My big problems have come when the wifi card on my Asus laptop would be put to sleep by some power management utility.