Created attachment 1843481 [details] Picture of the restart prompt that does not function as expected Created attachment 1843481 [details] Picture of the restart prompt that does not function as expected Description of problem: When updates are available in Discover (on Fedora KDE 35), applying them and using the restart prompt does nothing. The update appears to download in Discover, but nothing happens during the reboot, and once logged back in, the exact same updates show as available, and the process is repeated. Version-Release number of selected component (if applicable): discover 5.23.0 How reproducible: I have tried to update my system seven times now using Discover, but the result has been the same. I've also reinstalled twice to confirm. Steps to Reproduce: 1. Find updates in Discover 2. Apply updates 3. Press restart Actual results: Discover appears to download updates but nothing gets applied to the system. Expected results: Updates should be applied on restart. Additional info: ---Some detailed system information in case it is useful--- System: Kernel: 5.14.10-300.fc35.x86_64 x86_64 bits: 64 compiler: gcc v: 2.37-10.fc35 Desktop: KDE Plasma 5.22.5 Distro: Fedora release 35 (Thirty Five) Machine: Type: Laptop System: System76 product: Oryx Pro v: oryp4-b serial: <filter> Mobo: System76 model: Oryx Pro v: oryp4-b serial: <filter> UEFI: American Megatrends v: 1.07.05RSA3-1 date: 06/14/2018 Battery: ID-1: BAT0 charge: 51.0 Wh (97.3%) condition: 52.4/66.6 Wh (78.7%) volts: 17.0 min: 15.0 model: Notebook BAT status: Charging CPU: Info: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP arch: Kaby Lake note: check rev: A cache: L2: 9 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 52799 Speed: 800 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 826 9: 854 10: 800 11: 800 12: 800 Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK driver: i915 v: kernel bus-ID: 00:02.0 Device-2: NVIDIA GP104M [GeForce GTX 1070 Mobile] vendor: CLEVO/KAPOK driver: nouveau v: kernel bus-ID: 01:00.0 Device-3: SunplusIT Chicony USB 2.0 Camera type: USB driver: uvcvideo bus-ID: 1-9:5 Display: wayland server: X.Org 1.21.1.2 compositor: kwin_wayland driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1920x1080~144Hz OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 21.2.3 direct render: Yes Audio: Device-1: Intel Cannon Lake PCH cAVS vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Device-2: NVIDIA GP104 High Definition Audio driver: snd_hda_intel v: kernel bus-ID: 01:00.1 Sound Server-1: ALSA v: k5.14.10-300.fc35.x86_64 running: yes Sound Server-2: PipeWire v: 0.3.38 running: yes Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK driver: r8169 v: kernel port: 3000 bus-ID: 6f:00.0 IF: enp111s0 state: down mac: <filter> Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: 3000 bus-ID: 71:00.0 IF: wlp113s0 state: up mac: <filter> Bluetooth: Device-1: N/A type: USB driver: btusb v: 0.8 bus-ID: 1-14:6 Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends Drives: Local Storage: total: 476.94 GiB used: 3.89 GiB (0.8%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 950 PRO 512GB size: 476.94 GiB temp: 42.9 C Partition: ID-1: / size: 475.35 GiB used: 3.73 GiB (0.8%) fs: btrfs dev: /dev/nvme0n1p3 ID-2: /boot size: 973.4 MiB used: 153.4 MiB (15.8%) fs: ext4 dev: /dev/nvme0n1p2 ID-3: /boot/efi size: 598.8 MiB used: 13.8 MiB (2.3%) fs: vfat dev: /dev/nvme0n1p1 ID-4: /home size: 475.35 GiB used: 3.73 GiB (0.8%) fs: btrfs dev: /dev/nvme0n1p3 Swap: ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0 Sensors: System Temperatures: cpu: 63.0 C mobo: N/A gpu: nouveau temp: 41.0 C Fan Speeds (RPM): N/A Info: Processes: 338 Uptime: 25m Memory: 23.32 GiB used: 3.28 GiB (14.0%) Init: systemd runlevel: 5 Compilers: gcc: 11.2.1 Packages: N/A note: see --pkg Shell: Bash v: 5.1.8 inxi: 3.3.06
If you have multilib rpms (e.g. both i686 and x86_64) in your update transaction, this is likely a dup of bug #1963770
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.