Comments
robatino
provided feedback
on mozilla-ublock-origin-1.65.0-1.fc42
2 hours ago
Same problem, no 42 updates compose at all. They're still doing repeated 41 updates-testing composes at https://kojipkgs.fedoraproject.org/compose/updates/ and the STATUS shows success but the 41 updates-testing version of the Firefox update FEDORA-2025-592a8c9553 never actually gets to testing. There was a mention of them working on it at https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org last night but obviously not fixed yet.
BTW, 140.0.4 is in Bodhi now at FEDORA-2025-2432dfbcf1 (but not signed yet).
There have been repeated 41 updates-testing pushes which have succeeded according to the STATUS code. And yet the 41 version of this update ( FEDORA-2025-67c7dab2d1 ) still hasn't even gotten to testing. So something's broken with that.
There hasn't been a 42 updates compose at all, see https://kojipkgs.fedoraproject.org/compose/updates/ . The last one was the night of July 6 in EDT (20250707 in UTC). Don't know what's going on.
There's a 140.0.2 released today but the fix appears to be Windows-only: https://www.mozilla.org/en-US/firefox/140.0.2/releasenotes/
There's a 140.0.2 released today but the fix appears to be Windows-only: https://www.mozilla.org/en-US/firefox/140.0.2/releasenotes/
See updated #2374194, this actually appears to be the fault of the libblockdev update FEDORA-2025-af7ba2696c from June 18. That explains why other people saw the bug earlier, updating udisks2 merely triggered it, logging in or rebooting probably would have had the same effect.
This appears to trigger #2374194 which causes the error "DISK IS LIKELY TO FAIL SOON" in gnome-disks despite no failing pre-fail attributes.
Command-line smartctl is lower-level so I'm inclined to believe that when it says the disk is healthy. Unfortunately, downgrading udisks2 didn't revert the error, even after rebooting, so I just upgraded back to the current version. Windows on the same box says the disk is healthy, as usual. In my case, I'm sure the udisks2 upgrade was the trigger, since I upgraded with command-line dnf and the error started just before I got the prompt back. But other people have reported starting to see the error with the older version 2.10.90-2.
Literally during the update to this version, suddenly got a warning about my disk being likely to fail soon, and gnome-disks now says "DISK IS LIKELY TO FAIL SOON" despite no actual change in the HDD status. Filed #2374194. It's an 11-year old HDD, but it's been fine. The 6 bad sectors it has were there shortly after I installed it in 2014 so it was probably shipped with them. Am guessing this is not intentional so am giving -1.
Are those Reboot/Logout Required messages generated automatically and can they be removed?