![通过 pip 破坏 Python 后无法修复 Arch Linux](https://linux22.com/image/213464/%E9%80%9A%E8%BF%87%20pip%20%E7%A0%B4%E5%9D%8F%20Python%20%E5%90%8E%E6%97%A0%E6%B3%95%E4%BF%AE%E5%A4%8D%20Arch%20Linux.png)
今天更新 2022年11月16日-1520GTM
在我的 pinebook pro 上通过 pip 安装 python 搞砸后,无法再更新和升级系统了。建议的解决方案是:
删除通过pip安装的Python东西,
并运行:
sudo pacman -S manjaro-system
sudo pacman -Syu --overwrite "*"
工作并不顺利。问题:
:: Replace breath2-icon-themes with community/plasma5-themes-breath? [Y/n] y
...
:: Replace plasma5-themes-breath2 with community/plasma5-themes-breath? [Y/n] y
:: Replace sddm-breath2-theme with community/sddm-breath-theme? [Y/n] y
然后我尝试:
...
:: Replace breath2-icon-themes with community/plasma5-themes-breath? [Y/n] n
...
:: Replace plasma5-themes-breath2 with community/plasma5-themes-breath? [Y/n] n
:: Replace sddm-breath2-theme with community/sddm-breath-theme? [Y/n] n
完毕!但之后,出现了失败的 systemd 单元:
journalctl -p 3 -b
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: OF: graph: no port node found in /i2c@ff3d0000/fusb30x@22
Oct 25 13:44:17 lxm kernel: rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
Oct 25 13:44:17 lxm kernel: mmc0: error -110 whilst initialising SDIO card
Nov 16 10:09:39 lxm kernel: rockchip-dp ff970000.edp: no DP phy configured
Nov 16 10:09:39 lxm systemd-udevd[303]: event6: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[303]: event6: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[303]: event6: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[308]: event4: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[308]: event4: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[308]: event4: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[301]: event7: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[301]: event7: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[301]: event7: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[319]: event8: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[319]: event8: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[319]: event8: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[306]: event5: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[306]: event5: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[306]: event5: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Nov 16 10:09:41 lxm bluetoothd[412]: Failed to set mode: Failed (0x03)
Nov 16 10:09:41 lxm systemd[1]: Failed to start PostgreSQL database server.
Nov 16 10:13:16 lxm pulseaudio[853]: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
Nov 16 11:14:33 lxm kernel: .ready
Nov 16 15:10:39 lxm kernel: clk_spi1 already disabled
Nov 16 15:10:39 lxm kernel: Modules linked in: rfcomm bnep zram r8153_ecm cdc_ether usbnet uvcvideo r8152 mii snd_soc_simple_amplifier joydev videobuf2_vmalloc hci_uart panfrost>
Nov 16 15:10:39 lxm kernel: CPU: 0 PID: 5853 Comm: systemd-sleep Tainted: G C 6.0.7-2-MANJARO-ARM #1
如何摆脱上述问题,让系统顺利运行呢?
我应该从头开始重新安装 Manjaro 吗?
或者:
我应该安装 Debian ARM 还是 Ubuntu ARM?