Comments
robatino
provided feedback
on firefox-140.0.1-1.fc42
a day ago
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?
I think but am not sure that's a mistake - normally it just says it's necessary to log out and log back in (for example like FEDORA-2025-73690cb454 ). @stransky, is it a mistake? When I tested I didn't notice that and just logged out and back in like usual, I didn't reboot. If necessary I'll test again.
@stransky: Noticed you're building 138.0.3, but only for 40 (EOL tomorrow), 41, and 43, not 42. All 3 builds started about 15 minutes ago.