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
完璧！しかし、失敗したシステムデバイスが現れました。
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をインストールする必要がありますか？