From: nobody@haph.org   
      
   =?UTF-8?Q?St=C3=A9phane?= CARPENTIER    
   news:6974a718$0$31871$426a74cc@news.free.fr Sat, 24 Jan 2026 11:03:52 GMT   
   in comp.os.linux.advocacy, wrote:   
      
   > Le 21-01-2026, DFS  a écrit :   
   >> "So as the title suggests, this morning i updated the system using   
   >> Discovery, but after reboot, the system is just not working. I can log   
   >> in just fine, but after login, everything is crashing. Open dolphin -   
   >> crash, open discovery - crash, right click on desktop - crash, right   
   >> click taskbar - crash, open start menu - crash, cant open console,   
   >> because crash… open console with CTRL+ALT+T - crash, cant even get   
   >> any kind of error log, because crash…"   
   >>   
   >> https://discussion.fedoraproject.org/t/fedora-42-everything-crashes-afte   
   >> r-update/156660   
   >>   
   >>   
   >> Linux just works!   
   >   
   > Even FF/DG/FR/LP/whatever manages to make Linux work. And his level is   
   > bellow the ground. You managed to find someone bellow his level. It's   
   > impressive. There are distros designed for beginners whose purpose is to   
   > avoid issues like that. Fedora is not one of them, so if he avoids a   
   > beginner distro, he has to know what he does. And obviously he doesn't.   
      
   His entire post is skewed. The article he selected is for an older version   
   of a not exactly for n00bs distro that has already been updated to another   
   version. The individual who reported the problem opted to fix it   
   themselves before proceeding any further via the forum post so some log   
   files which might have alluded to the actual problem had been erased.   
   People who do what the OP did aren't very helpful to the authors/coders   
   who are attempting to fix a reported issue.   
      
   Imo, if someone is going to take the time to write a forum post, They   
   should be willing to wait for responses and be willing to participate in   
   the discussion. Not only will they most likely get the help they asked for,   
   they'll be contributing debug/diagnostic information which might reveal an   
   issue that wasn't caught during testing that other people might run into.   
   It's also possible the information will reveal a hardware incompatability   
   as well as show early signs of hardware failure in progress on the   
   computer where the error took place.   
      
   Jumping the gun and reloading as the OP indicated they did might not help   
   them resolve the issue in the long term. Whatever caused the issue could   
   come and rear it's ugly head again if the actual cause hasn't been   
   determined and a fix applied for it. Log files are handy things to have   
   when you're attempting to properly fix a problem.   
      
   > If I'm far from a fan of Ubuntu, I saw people trying to break the update   
   > without being able to do it. Once someone told me that since the upgrade   
   > the computer was unable to launch the GUI. I was surprised and after a   
   > few questions I understood what happened. As the upgrade was taking too   
   > long, the computer was shut down in the middle of the upgrade. And guess   
   > what, after launching the update commands the upgrade ended well and   
   > everything was fine. I was pretty impressed and if I don't like Ubuntu   
   > for a lot of reasons, I have to admit they have really improved the   
   > upgrade of the system. And when I'm speaking about the upgrade of the   
   > system, I'm speaking about the Ubuntu 22.04 toward 24.04, not about a   
   > security update.   
      
   They've put a lot of work into improving the update stability and ability   
   to recover from an unexpected power failure.   
      
   > And from what I heard about Windows, I'm far from that sure it would   
   > manges a shut of power in the middle of its upgrade that well.   
      
   It's about the same as it was with XP in so far as gracefully recovering   
   from a power related incident while applying updates. Depending on how far   
   along it was and it's last completed operation - it might after several   
   reboots straighten out for the most part or enter one of the reboot loop   
   conditions. To be fair, I have seen Windows 10 sort of gracefully recover   
   on three seperate occasions so far. :)   
      
   Windows 11 is about the same as 10 with the graceful recovery. Atleast   
   from what I've seen. I haven't seen any specific flavor of Windows recover   
   as well as this Linux distro has for me on two seperate occasions where I   
   goofed and caused a power loss issue. I'm still waiting for the crew   
   behind this distro to release a bad update and then have to release an   
   emergency one to fix it. I've been waiting for that to happen since the   
   early v18 editions though and they're on 25.1 now I think it is. I'm still   
   running v23.6 on this rig though. I suppose I could go ahead and upgrade   
   since I've got all the data backed up, but, I'm waiting until this new   
   version matures a little more. Maybe when 25.3 is released...   
      
   I was always told that you should never run any programs, let alone an OS   
   that's at major version xx and minor zero or 1 or 2. Atleast wait until   
   they iron most of the kinks out. By major xx and minor 3 that should be   
   mostly the case.   
      
      
   --   
   Liar, lawyer; mirror show me, what's the difference?   
   Kangaroo done hung the guilty with the innocent   
   Liar, lawyer; mirror for ya', what's the difference?   
   Kangaroo be stoned. He's guilty as the government   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)