[SOLVED] Updates make my system unusable (LM 20 and 20.1)

[blueberrymint]

My general approach to maintainig my system was to apply updates as soon as they come out.

After several months of using Linux Mint 20.1 and then a few days of using Linux Mint 20, I experience a pattern with the same problem: one day there appears some update(s), I apply them, I reboot the system, and I get the following:

• login loop

• dmesg packed with countless wlp1s0 fail messages and I/O errors:

  Code: Select all

  wpa_supplicant[766]: wlp1s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
  rtkit-daemon[1127]: Failed to make ourselves RT: Operation not permitted

The login loop problem isn't caused by changed permissions of .Xauthority or any other similar file. I checked.

The problem isn't caused by my hard drive, since I run tests and there are zero bad blocks, and there's more than enough free memory.

On the 7th of March 2021, after several days of using freshly installed Linux Mint 20, I received an update for wpasupplicant (2:2.9-1ubuntu4.3). I created a snapshot with Timeshift. I installed the update. I rebooted. And, again, I got the same problem as I described above. So what did I do? I booted up from live usb LM 20 and restored that saved snapshot through Timeshift. I rebooted. The problem was gone. The wpasupplicant is, of course, still staying on version 2:2.9-1ubuntu4.2.

It's been now two months since I haven't installed any updates whatsoever, and my system works with no problem. Unfortunately, my new uproach to maintaining the system is to simply turn off updates completely.

If anyone knows or has theories as to what is causing this problem, please share with me. I'll apreciate any help.

Thank you.

Additionally I add my system info:

Code: Select all

System:    Kernel: 5.4.0-26-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.6.7 
           wm: muffin dm: LightDM Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: <filter> Chassis: 
           type: 9 serial: <filter> 
           Mobo: Dell model: 0R2XKN v: A00 serial: <filter> UEFI [Legacy]: Dell v: 2.7.0 
           date: 07/19/2018 
Battery:   ID-1: BAT0 charge: 38.7 Wh condition: 38.7/41.4 Wh (94%) volts: 14.7/14.8 
           model: LGC-LGC2.80 DELL 7PY0D8A serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i3-7020U bits: 64 type: MT MCP arch: Amber Lake 
           rev: 9 L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 18399 
           Speed: 2300 MHz min/max: 400/2300 MHz Core speeds (MHz): 1: 2300 2: 2300 3: 2300 
           4: 2300 
Graphics:  Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5921 
           Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2F) v: 4.6 Mesa 20.2.6 
           direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:9d71 
           Sound Server: ALSA v: k5.4.0-26-generic 
Network:   Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel port: f040 bus ID: 01:00.0 
           chip ID: 8086:3165 
           IF: wlp1s0 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell 
           driver: r8169 v: kernel port: e000 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 118.50 GiB (12.7%) 
           ID-1: /dev/sda vendor: Toshiba model: MQ01ABD100 size: 931.51 GiB speed: 6.0 Gb/s 
           serial: <filter> 
Partition: ID-1: / size: 97.93 GiB used: 11.36 GiB (11.6%) fs: ext4 dev: /dev/sda5 
           ID-2: /home size: 522.17 GiB used: 12.31 GiB (2.4%) fs: ext4 dev: /dev/sda6 
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 12 rev: 2.0 chip ID: 1d6b:0002 
           Device-1: 1-2:2 info: Logitech M105 Optical Mouse type: Mouse 
           driver: hid-generic,usbhid rev: 2.0 chip ID: 046d:c077 
           Device-2: 1-5:3 info: Realtek Integrated_Webcam_HD type: Video driver: uvcvideo 
           rev: 2.0 chip ID: 0bda:5769 
           Device-3: 1-6:4 info: Realtek RTS5129 Card Reader Controller type: <vendor specific> 
           driver: rtsx_usb,rtsx_usb_ms,rtsx_usb_sdmmc rev: 2.0 chip ID: 0bda:0129 
           Device-4: 1-8:5 info: Intel type: Bluetooth driver: N/A rev: 2.0 chip ID: 8087:0a2a 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 3.0 chip ID: 1d6b:0003 
Sensors:   System Temperatures: cpu: 42.0 C mobo: 39.0 C 
           Fan Speeds (RPM): cpu: 0 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/atareao-telegram-focal.list 
           1: deb http: //ppa.launchpad.net/atareao/telegram/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http: //packages.linuxmint.com ulyana main upstream import backport #id:linuxmint_main
           2: deb http: //archive.ubuntu.com/ubuntu focal main restricted universe multiverse
           3: deb http: //archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
           4: deb http: //archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
           5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
           6: deb http: //archive.canonical.com/ubuntu/ focal partner
           Active apt repos in: /etc/apt/sources.list.d/sublime-text.list 
           1: deb https: //download.sublimetext.com/ apt/stable/
Info:      Processes: 209 Uptime: 36m Memory: 7.56 GiB used: 1.55 GiB (20.5%) Init: systemd v: 245 
           runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Client: Unknown python3.8 client inxi: 3.0.38 

[SMG]

Welcome to the forum, blueberrymint.

• dmesg packed with countless wlp1s0 fail messages and I/O errors:

  Code: Select all

  wpa_supplicant[766]: wlp1s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
  rtkit-daemon[1127]: Failed to make ourselves RT: Operation not permitted

That seems to be related to your computer's WiFi driver.

On the 7th of March 2021, after several days of using freshly installed Linux Mint 20, I received an update for wpasupplicant (2:2.9-1ubuntu4.3). I created a snapshot with Timeshift. I installed the update. I rebooted. And, again, I got the same problem as I described above. So what did I do? I booted up from live usb LM 20 and restored that saved snapshot through Timeshift. I rebooted. The problem was gone. The wpasupplicant is, of course, still staying on version 2:2.9-1ubuntu4.2.

It's been now two months since I haven't installed any updates whatsoever, and my system works with no problem. Unfortunately, my new uproach to maintaining the system is to simply turn off updates completely.

I do not understand the connection to stopping all updates because one package caused a problem. That seems a bit severe. You can block that one package from updating and test newer ones as they come out to see if the issue is fixed.

It appears while you have some files updated, you do not have an updated kernel. That is the original kernel. Perhaps that is part of the problem. The current kernel is 5.4.0-72.

System:
Kernel: 5.4.0-26-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.6.7
wm: muffin dm: LightDM Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal

[SMG]

This appears to be the issue you are experiencing wpa_supplicant CTRL-EVENT-SCAN-FAILED error. See if the solutions mentioned there help your situation.

[blueberrymint]

I do not understand the connection to stopping all updates because one package caused a problem.

It was a just concrete example that I documented of how an update package breaks something in my system. The same situation happened before when I did other updates for LM 20.1 (when updating multiple packages for multiple apps).

This appears to be the issue you are experiencing wpa_supplicant CTRL-EVENT-SCAN-FAILED error. See if the solutions mentioned there help your situation.

I can't check if it works since right now I don't have any error messages, they appear only after the system is already broken due to updates. I don't have enough time right now to risk the stability of my system by doing an update again. What if I'm not able to recover it? Which by the way is what hapenned to a previous Linux Mint 20.1, I'm now on the 20th version.

That is the original kernel. Perhaps that is part of the problem.

I really doubt that kernel has anything to do with this, it's just a suite of drivers. If the previous versions of wpasupplicant worked, doesn't it mean that something is wrong with the new version of it? But who knows, maybe you're right, when I do have some time on my hands, I'll try to test this.

Thank you, @SMG.

[SMG]

This appears to be the issue you are experiencing wpa_supplicant CTRL-EVENT-SCAN-FAILED error. See if the solutions mentioned there help your situation.

I can't check if it works since right now I don't have any error messages, they appear only after the system is already broken due to updates. I don't have enough time right now to risk the stability of my system by doing an update again. What if I'm not able to recover it? Which by the way is what hapenned to a previous Linux Mint 20.1, I'm now on the 20th version.

I thought you posted that reverting to a Timeshift snapshot got you back to the earlier package?

That is why we recommend taking Timeshift snapshots. It makes it easy to roll back to prior packages. One can roll back to older kernels quite easily, but one usually needs to use a snapshot for packages or PPAs.

I really doubt that kernel has anything to do with this, it's just a suite of drivers. If the previous versions of wpasupplicant worked, doesn't it mean that something is wrong with the new version of it? But who knows, maybe you're right, when I do have some time on my hands, I'll try to test this.

A kernel has bug fixes and patches. That is why we recommend updating to newer versions. The iwlwifi driver used by your wireless card is a very common one so there are often firmware changes as well as patches/fixes for it.

[blueberrymint]

I thought you posted that reverting to a Timeshift snapshot got you back to the earlier package?

Yes, that is correct. But what if this time it won't be able to do the recovery for some unexpected reason?

The iwlwifi driver used by your wireless card is a very common one so there are often firmware changes as well as patches/fixes for it.

I understand that. However, I do not understand how is it that right now with the older version of wpasupplicant I don't have any error messages, shouldn't I get them now if something is wrong with the iwlwifi driver (which comes with the older kernel I currenly use)?

[SMG]

Yes, that is correct. But what if this time it won't be able to do the recovery for some unexpected reason?

Usually, when someone posts with an issue, the way to correct the issue is to make a change. If you are not wanting to make any changes, then I'm a bit perplexed as to why you asked for help.

The iwlwifi driver used by your wireless card is a very common one so there are often firmware changes as well as patches/fixes for it.

I understand that. However, I do not understand how is it that right now with the older version of wpasupplicant I don't have any error messages, shouldn't I get them now if something is wrong with the iwlwifi driver (which comes with the older kernel I currenly use)?

I did not research the specific package version with which you experienced an issue, but usually changes are made to packages to fix bugs or close vulnerabilities. Same for drivers. It is possible there have been changes to both and if you updated both then they might work. Just because you are not getting errors does not mean the package is working properly.

The open source community is dependent on people reporting bugs and problems so developers know they exist. That is the only way they are likely to be fixed.

[blueberrymint]

Usually, when someone posts with an issue, the way to correct the issue is to make a change. If you are not wanting to make any changes, then I'm a bit perplexed as to why you asked for help.

I actually already wrote you previously that I'm going to test your theory when I have enough time, because at the moment I need a working system. If that is all you can advise me with right now, that's perfectly fine, I appreciate it.

[blueberrymint]

So, I did it! I had time today to make all the necessary data backups and Timeshift snapshot. I installed the newest kernel first, rebooted, and then installed the wpasupplicant update. It works! Everything works. I then installed the rest of the updates. And, again, everything is working fine. It turns out that kernel updates really do matter.

Thank you very much, @SMG.

I'm going to go now and mark this post as solved.

[SMG]

So, I did it! I had time today to make all the necessary data backups and Timeshift snapshot. I installed the newest kernel first, rebooted, and then installed the wpasupplicant update. It works! Everything works. I then installed the rest of the updates. And, again, everything is working fine. It turns out that kernel updates really do matter.

So you did not need to make any of the changes in the link I provided? That's good news. I guess whatever the issue had been was fixed so workarounds were no longer necessary. That is the best scenario.

Glad all is working and your system is up-to-date.
You are welcome.