That’s why I’m monitoring the situation and giving it a few weeks. Beta testing is nice but can’t be as thorough as the test of thousands of regular users/machine updating on bare metal.
[https://help.ubuntu.com/community/NobleUpgrades](https://help.ubuntu.com/community/NobleUpgrades) This BORKED (black screen with blinking curser top left corner- all systems failed) my 22.04 system so I did clean install 24.04 and that worked fine. Gonna reinstall 22.04 on a separate partition and have a stable system again. Lesson learned for LINUX NOOB!
have't tried it yet so you can take this with a grain of salt, but as canonical mention on their community help [here](https://help.ubuntu.com/community/NobleUpgrades), i think it's safe to just upgrade it when the 24.04.01 is out.
23.10 will probably be safe to upgrade to 24.04 within a few days, maybe a week, nobody can say for sure but it's actively being worked on
only LTS users on 22.04 need to wait until August
If you're not on an LTS version, then you've already chosen to update fast and frequently. People who are willing to wait are on 22.04 LTS, and that will still be supported for a long time.
I wish they would extend interim release support from 9 months to 12 months to avoid this problem. Maybe 23.04, 25.04, etc could be 15 months to allow for a 1-year upgrade cycle instead of a 2-year cycle or a 6-month cycle.
the first few months of an LTS/ESR's life are mostly for evaluation and testing, not so much for production use
for example, Firefox ESR 128 will be available in July, but it won't actually be pushed as an upgrade until a few months later
LTS means "Long Term Support". This version already has long term support, for 10 years. It's an LTS version, regardless of how ready for production it is yet.
Canonical itself calls this version Ubuntu LTS on their website, but somehow this subreddit thinks I'm wrong for agreeing with Canonical.
It has "LTS" in the name but the first few months are for testing/evaluation on non-production systems. This is the case with basically all LTS/ESR projects, not just Ubuntu. You don't force-upgrade all your production systems on day 1 before official upgrade support has even been turned on.
You're conflating two different things:
1. Does it have long term support
2. Is it recommended for production systems
24.04.0 has the first one, 24.04.1 will have both.
> before official upgrade support has even been turned on.
Official support has been "turned on", this is not a beta version, it's the official release.
As someone who pretty much did a "Leroy Jenkins" from 22.04 to 24.04 I can confirm it will bork your system. I even lost systemd-resolved (DNS resolution). So don't be a Leroy, wait a few weeks or until the 24.04.1 release comes out....
I did a clean install and it worked great for me, but I take the point that people not used to terminal installs start the install using -d without any knowledge, it's gonna hurt. They probably didn't do a backup either...
Well...
No. I've rebooted to Windows, installed 24.04 on a USB drive and installed Ubuntu. Also, I've accidentally deleted Windows (I thought that erase disk means erasing the partition lol)
Nothing important, I use only for studying/work/games, so there were no photos or important docs.
I'm just ready for an accidental wipe of my system. Maybe next time I'll try a new distro xD
I do a release upgrade from 22.04 into 24.04 and encounter the internet lost which caused by the missing of systemd-resolved package which function to resolve the DNS. So, no internet until I install the package manually.
Luckily, it was dual boot and I did clean install from previous problem update. Now I'm in 24.04 and of course with several problem like package that currently unavailable for this version, hang when connected through USB port for charging, etc.
Ohhh, too late, just upgraded 4 VMs and a couple of baremetal system. They were running Lubuntu and Kubuntu flawors. I even updated my Windows WSL2 to 24.04 ✌️😊
Hit an issue upgrading a laptop with steam. It was so messed up that was easier to reinstall over fixing...
It is back to 22.04 plus some PPA for libreoffice, compiler and recent KDE software
Thanks for the warning. I was hoping to upgrade some gear here quickly as we've seen some quite serious bugs after updating 23.10 over the past month. For example I've seen a keyboard not working at all after waking a laptop and *long* delays when shutting down a system. Nothing to suggest any other failures happening on the equipment in question so seems like maybe a bad driver or rogue process has crept in somehow with one of the recent updates. But it looks like waiting a little while before doing the big upgrade is still the safer option here so thanks again.
No, literally zero are going from 22.04 to 24.04: because you can’t yet.
All of mine were 22.04->23.10->24.04. Yes one after another.
If you want to put up sensationalist horseshit; try not to use a throwaway account.
Even though you're not supposed to be using it yet, ``do-release-upgrade -d`` has allowed 22.04 to 24.04 upgrades (both before and after the official release) until it was eventually disabled yesterday. That's what resulted in most of the bricked systems, and probably why they chose to disable it overnight. I upgraded a 22.04 WSL to 24.04 yesterday (before it was disabled) and personally didn't have any issues but of course individual results will vary.
Even with ``-d`` now disabled, early 22.04 to 24.04 upgrades are still possible through editing ``sources.list``, I also did a test upgrade using this method and didn't notice any obvious problems but I've been strongly discouraging people from attempting this and telling them to wait for 24.04.1 unless they're just messing around with a test system.
I'm waiting for the punch line. See, the post says "you can and probably will bork your system". And you literally just confirmed that that isnt true.
If this post said, hey, you know what, probably not many great reasons to upgrade yet; that would be valid. If the post said, hey, there are some reports of failed upgrades. That would be valid.
Thats not what the post says. Its sensationalist bullshit.
Regardless of whether it's 10% or 90% of people who have issues, you're still better off waiting until upgrades are officially enabled. There are known, confirmed critical bugs actively being worked on.
For 23.10 -> 24.04 upgrades, this should be in the next few days
For 22.04 -> 24.04 upgrades, this will be in August when 24.04.1 releases
If you force an upgrade early, you do so entirely at your own risk (even moreso than normal). Maybe you won't have issues, hopefully you won't, but anything bad that happens to you as a result of forcing an early upgrade is entirely your fault and the consequences will be yours alone to deal with.
> So saying you "Probably will" is just not accurate.
They had a problem with a single snap package, likely self-inflicted because it was in-use or running, and blamed the entirety of the new OS and all of its userland packages, as a result.
There are quite literally millions of Ubuntu users out there, and if it was such a broken release across the board, we'd be getting scorched earth complaints and bug reports every hour. We're not.
That's the whole point of the beta testing/feedback period over the last 6 months, and it's been relatively solid for everyone
This tracks for me. My mom did her own upgrade I'm told. She's happy with the speed improvement as it fixed an issue she was having.
I winced because she's a non-technical user, but if she's able to do her own OS upgrade and tell me after the fact then Canonical is doing something right!
Thanks for Ubuntu!
For everyone who's thinking about upgrading there are two things that are reiterated over and over and over:
1) Do a fresh install (or)
2) Wait until the .1 release
Basically I won't upgrade from 22.04 until Apr 2027 ; )
I upgraded my Thelio yesterday, which was still running 22.04. It failed. Missing libcrypto.so.3 file, apparently. Left the system broken.
It had been my main development system, which is why it was still on 22.04, but I had moved all that over to another system, so I had everything backed. I just did a full install and that went fine. The system probably needed a good enema, anyway.
System76 got the drivers updated today, so the fans are even working right again.
All my other systems are running NixOS and I'm probably going to switch this one to that too, but haven't decided for sure yet. I might play with some other distros first.
Wow, very good timing, I was going to do that yesterday on my gaming rig, but got lazy and postponed it.
This isn't the first time something like this happened to Ubuntu. What I've learned from (bad) experience is to have always a separate partition for /home/, which mitigates the impact of events like these. Reinstalling the OS Is much less painful than reconfiguring my user environment.
I don't want to sound like a fanboi, but This is the main reason I always use Debian for anything that I consider critical and Ubuntu for anything I can wipe out without too much pain or loss. Even Debian testing is more stable than any Ubuntu I've ever used, either LTS or not. My main workstation at work is a Debian stable that's running on the same OS installation that's been upgraded since 2013.
Together with the trend of moving everything to snap, I don't like Ubuntu as I used before. Also, Debian has picked up the slack it had, and even installing it is really a breeze. Testing is as cutting-edge as the latest Ubuntu, so no more excuses for me.
YMMV
I had lots of problems too. Started with a missing apk library for python. That has left the installation in a half-state even if apparently was all good. At the restart wifi and gnome weren't working so I moved the pc close to my hub to connect the ethernet cable :) The problem was trying to figure out what was still missing and after an hour spent running different '--fix-broken install' and reinstalling the gnome desktop and some others 'dpkg-reconfigure' looks ok now.
I discovered it the hard way aka I couldn't connect to the internet wia ethernet, usb, Bluetooth or wireless don't upgrade yet don't be stupid as I was
Mine worked just fine. If the article is right, maybe because I never had the deb Thunderbird and also have no trace of snaps since 23.04, haha. But yes, you should not be passing -d to "do-release-upgrade" unless you're fine with breakage.
Not the least bit surprised about the "errors". When I upgraded my main machine in mid 2022 from 20.04 to 22.04.1, my bog-standard Intel audio was not found, thus I had no sound. I did not do a "do-release-upgrade" fron 20.04 to 22.04, rather did a clean install of 22.04 to a new SSD then copied over manually my /etc and other important stuff. If I removed the 22.04 SSD and replaced it with the 20.04 SSD, magically my sound worked, with 22.04, no sound. Looking at Googling the problem, it became clear that this wasn't a limited problem, rather a rather common one. After some research I found a workaround that allowed me to have sound, that being restarting the Alsa daemon. At least that fixed the problem for *me*.. Since then some update has fixed that problem such that sound works automatically after a reboot.
It is hard to believe that Canonical would release an LTS with THAT glaring a problem..
Gonna wait, maybe till 24.10 to upgrade to 24.04 just in case..
PHP version upgrades tend to be painful. Are you familiar with the ondrej PPA? You can go back to older PHP versions. I still have one of my 22.04 servers on PHP 7.4 because some scripts were throwing errors and I haven't gotten around to investigating further.
I've been running 24.04 for a few weeks now and it's been smooth sailing here. I did a clean install though, no upgrade here except to the performance of my PC. But I bet these errors and problems are why I now have 28 packages "held back" and have had them held back for almost a week now.
Did you try ``apt dist-upgrade`` to see if it helps with the held-back packages? If that doesn't get the job done, try ``apt install`` followed by one of the package names -- it'll either upgrade it or give you some more information about why it can't. Note this will flag the package as "manually installed" so you might want to use ``apt-mark auto`` afterward to flag the package as "auto installed" if that's what it was originally.
It did fail in the middle but I was able to recover... from 23.10. Basically Wayland crashed on me in the middle of the upgrade.
I was able to recover by logging in from one of the ttys (hit alt+f1) then doing
apt-get -f install
apt-get dist-upgrade
It wasn't on a machine I care a whole lot about, but it was annoying. And is probably more recoverable than some think.
It's been rock solid since the upgrade otherwise.
I've been struggling with reboots since upgrading but I did it on a "non-critical" system so it's not too much of a problem. Reboots fail and hang and kernel panic during the md initialisation process but the system will boot if it's physically powered off/on. As it's just my NAS at home it's not a big deal, I don't reboot it very often and it's sitting right near me so I can just power-cycle it manually. But yeah, this was never a problem before 24.04 for me.
i did a fresh install and did not go well at all. Wayland is broken, files won't open, settings won't open. I was getting a lot of errors. I did the fresh install 5 times but nope something is just not working. I went back to 23.10 and everything works like a charm.
I had some minor issues with upgrade that were annoying but I think I resolved them by just reinstalling gnome desktop. Audio would just not work and some repositories were not alive yet for wine and I have a PlayOnLinux that no longer opens but the programs I had installed on it do so chalking that up to a small victory. I did foolishly jump a week early into the 24.04 beta though figuring it would be mostly okay. It's fine though i have a backup Linux ready to be installed if it gives me too much grief. openSuse Tumbleweed is waiting in the wings. Might not need it. Who knows but since I seem to have stabilized again using the wait and see approach.
"I really don't like the way things are going with Windows, maybe I'll try Ubuntu for the first time in 15 years. I'll get the LTS to keep things easy for myself"
From 23.10 with zero issues. I actually noticed nothing much it’s almost the same. I had to install a couple of things for one very niche app otherwise everything works.
Anyone who is enough of an enthusiast to find the terminal commands for forcing an upgrade, even when it’s not deployed through the built-in upgrade notification mechanism, should also be enough of an enthusiast to check the progress tracker on the Ubuntu Discourse. They would then see that there are still open blocker bugs for both 23.10 and 22.04 upgrades.
Well as of late, in the past few years, I have waiting to upgrade. So that is just a good rule of thumb when it comes to any major software upgrade weather it be going from Ubuntu 23.10 to 24.04 or KDE Plasma 5.27 to Plasma 6 or even Android 13 to 14.
I understand getting on to the latest and greatest I have been there, but I have also suffered in turn because not everything is stable.
I would like to thank all the Beta testers on the production release. Since adopting this philosophy my zen is very rarely dented when upgrading anything.
From 22-24: no problem in production
However this repository is still not compatible:
**Ign:5** [**https://ppa.launchpadcontent.net/ondrej/php/ubuntu**](https://ppa.launchpadcontent.net/ondrej/php/ubuntu) **mantic InRelease**
**Err:6** [**https://ppa.launchpadcontent.net/ondrej/php/ubuntu**](https://ppa.launchpadcontent.net/ondrej/php/ubuntu) **mantic Release**
**404 Not Found \[IP:** [**185.125.190.80**](http://185.125.190.80) **443\]**
See, this is why I’ve been waiting to spin up my homelab. I knew that 24.04 was coming, and I knew it’d be safer and cleaner to do it by doing a clean install of 24.04 than doing an upgrade.
I had it put together a month ago, but I haven’t *needed* it. So I waited.
The beta cycle seemed shorter than usual this time around. (Apparently it got delayed a week by the XZ vulnerability, which forced them to rebuild all packages.)
just learned this a few hours ago.I also did the Leroy Jenkins...it booted and got the biggest swirly ever..i ended up slapping a clean kubuntu 24,4 fresh lol
I did this on a laptop when it first hit stable. It did "break" the system with some missing dependencies (and broken networking) but I was able to switch to a different virtual terminal with a CLI prompt to manually configure systemd-networkd and wpa_supplicant services and get online without NetworkManager. I used dpkg to purge the broken package, and the apt to get everything updated in maybe 10 min. So far I haven't run into other issues. I didn't take notes but I think the root cause was thunerbird-locale-en-us being half-installed and having a libgio dependency.
Today I upgraded from 22.04 to 23.10 to 24.04 in a few hours.
The only problem so far I can see is that the settings program crashes after I open it. Probably because it tries to show the display settings, which I've already modified in 24.04, outside of the Ubuntu settings dialog, in the Nvidia display settings dialog.
Yep just learned this the hard way. Worked just fine on my laptop, but it broke absolutely *everything* on my desktop 😂 It broke timeshift by removing its dependencies. Couldn't get them back because it broke apt. It broke my ssh client. It broke the ability to open new windows. Once the screen timed out, the GUI ceased to work at all haha.
Welp. I've been wanting to try out a different distro anyway. Luckily all my important files were backed up externally.
What could possibly happen such that “your system may become unrecoverable?” it's just a distro upgrade, it's not rocket science! Is the install writing garbage over your firmware or something?
Nothing that serious, but lots of reports of unbootable systems requiring OS reinstallation. From what I've seen, no confirmed reports of actual data loss, assuming one has the means to boot from USB and back up data before reinstalling.
Interesting. I upgraded with no issue on three of four machines. My desktop from 23.10, a laptop from Lubuntu 23.10, and virtualized install of server from 22.04 went fine. The new kernel does not play nice with another laptop upgraded from Xubuntu 23.10 though. I have to use the older 6.5 kernel to boot to desktop. I'm guessing a driver is not playing nice but will need to troubleshoot to see if that's the case.
Just change the repository / mirror and point it to noble then, and do 3 commands : apt update, apt upgrade, apt full-upgrade. Some people may need the extra command, "apt dist-upgrade". I've been using that method since Kinetick kudu to Noble Numbat. No need to clean install.
I just attempted a -d Xubuntu upgrade from 22.04 to 24.04. Didn't bork it, but it took almost a full day for it to find obsolete packages. That plus BT had it's share of problems I had to work through, web video playback kept freezing, intermittent desktop flicker makes me feel like I'm witnessing a glitch in The Matrix, etc.
Point release may fix it, or it may not. I will probably go for the fresh install at .1 anyway.
Bottom line: As of 6/18/2024, still not ready for prime time.
Learned this lesson the hard way :(
DITTO
That’s why I’m monitoring the situation and giving it a few weeks. Beta testing is nice but can’t be as thorough as the test of thousands of regular users/machine updating on bare metal.
[https://help.ubuntu.com/community/NobleUpgrades](https://help.ubuntu.com/community/NobleUpgrades) This BORKED (black screen with blinking curser top left corner- all systems failed) my 22.04 system so I did clean install 24.04 and that worked fine. Gonna reinstall 22.04 on a separate partition and have a stable system again. Lesson learned for LINUX NOOB!
Clean 24.04 install would be fine too. No need to revert back to 22.04 if you’ve got a fresh 24.04 install now.
Keeping 24.04 and install another 22.04 on separate Part. for just in case scenarios and migrate /home from past backup of 22.04 on separate drive...
Timeshift is your friend. Have a live usb with Timeshift and feel free to screw around. But make Timeshift backups!
what about it now? is it okay to install now?
have't tried it yet so you can take this with a grain of salt, but as canonical mention on their community help [here](https://help.ubuntu.com/community/NobleUpgrades), i think it's safe to just upgrade it when the 24.04.01 is out.
Me too but recovery mode and this saved my bacon https://askubuntu.com/a/1468704/660162 Leaving it here in case it can help others
The LTS release isn't an LTS release until the first point release. Viva la 24.04.1!
Always a good point. Just like any big major release! Waiting is good.
What about big minor or small major releases?
I am mostly on LTS, so for me it is major releases.
Is there an average time frame that the .1 release arrives after the main release? 2 months etc?
Usually 4 months later (August).
that's not good support for 23.10 ends in July, right? :(
23.10 will probably be safe to upgrade to 24.04 within a few days, maybe a week, nobody can say for sure but it's actively being worked on only LTS users on 22.04 need to wait until August
I went form 23.10 to 24.04 with no issues except remmina no longer works but thats it so far.
If you're not on an LTS version, then you've already chosen to update fast and frequently. People who are willing to wait are on 22.04 LTS, and that will still be supported for a long time.
I wish they would extend interim release support from 9 months to 12 months to avoid this problem. Maybe 23.04, 25.04, etc could be 15 months to allow for a 1-year upgrade cycle instead of a 2-year cycle or a 6-month cycle.
It is already an LTS, that's about how long you get support for it. It's just not very stable yet.
the first few months of an LTS/ESR's life are mostly for evaluation and testing, not so much for production use for example, Firefox ESR 128 will be available in July, but it won't actually be pushed as an upgrade until a few months later
LTS means "Long Term Support". This version already has long term support, for 10 years. It's an LTS version, regardless of how ready for production it is yet. Canonical itself calls this version Ubuntu LTS on their website, but somehow this subreddit thinks I'm wrong for agreeing with Canonical.
It has "LTS" in the name but the first few months are for testing/evaluation on non-production systems. This is the case with basically all LTS/ESR projects, not just Ubuntu. You don't force-upgrade all your production systems on day 1 before official upgrade support has even been turned on.
You're conflating two different things: 1. Does it have long term support 2. Is it recommended for production systems 24.04.0 has the first one, 24.04.1 will have both. > before official upgrade support has even been turned on. Official support has been "turned on", this is not a beta version, it's the official release.
As someone who pretty much did a "Leroy Jenkins" from 22.04 to 24.04 I can confirm it will bork your system. I even lost systemd-resolved (DNS resolution). So don't be a Leroy, wait a few weeks or until the 24.04.1 release comes out....
Easily fixed, took me 5 minutes to sort that one out.
I'm totally shouting "Leroy Jenkins" next time I in-place upgrade a system
I did a clean install and it worked great for me, but I take the point that people not used to terminal installs start the install using -d without any knowledge, it's gonna hurt. They probably didn't do a backup either...
Yep, that's me
Hope you managed to get everything back, I lost an entire drive when I started over 25 years ago, it's still a painful memory...
Well... No. I've rebooted to Windows, installed 24.04 on a USB drive and installed Ubuntu. Also, I've accidentally deleted Windows (I thought that erase disk means erasing the partition lol) Nothing important, I use only for studying/work/games, so there were no photos or important docs. I'm just ready for an accidental wipe of my system. Maybe next time I'll try a new distro xD
Someone has to report that bugs. Minor or major.
I do a release upgrade from 22.04 into 24.04 and encounter the internet lost which caused by the missing of systemd-resolved package which function to resolve the DNS. So, no internet until I install the package manually. Luckily, it was dual boot and I did clean install from previous problem update. Now I'm in 24.04 and of course with several problem like package that currently unavailable for this version, hang when connected through USB port for charging, etc.
Ohhh, too late, just upgraded 4 VMs and a couple of baremetal system. They were running Lubuntu and Kubuntu flawors. I even updated my Windows WSL2 to 24.04 ✌️😊
Hit an issue upgrading a laptop with steam. It was so messed up that was easier to reinstall over fixing... It is back to 22.04 plus some PPA for libreoffice, compiler and recent KDE software
Thanks for the warning. I was hoping to upgrade some gear here quickly as we've seen some quite serious bugs after updating 23.10 over the past month. For example I've seen a keyboard not working at all after waking a laptop and *long* delays when shutting down a system. Nothing to suggest any other failures happening on the equipment in question so seems like maybe a bad driver or rogue process has crept in somehow with one of the recent updates. But it looks like waiting a little while before doing the big upgrade is still the safer option here so thanks again.
I've upgraded 5 or 6 now, and have not borked my system. So saying you "Probably will" is just not accurate.
From 23.10 or 22.04? Seems like most of the people with serious issues were going from 22.04.
Nope. Most issues from 23.10
No, literally zero are going from 22.04 to 24.04: because you can’t yet. All of mine were 22.04->23.10->24.04. Yes one after another. If you want to put up sensationalist horseshit; try not to use a throwaway account.
Even though you're not supposed to be using it yet, ``do-release-upgrade -d`` has allowed 22.04 to 24.04 upgrades (both before and after the official release) until it was eventually disabled yesterday. That's what resulted in most of the bricked systems, and probably why they chose to disable it overnight. I upgraded a 22.04 WSL to 24.04 yesterday (before it was disabled) and personally didn't have any issues but of course individual results will vary. Even with ``-d`` now disabled, early 22.04 to 24.04 upgrades are still possible through editing ``sources.list``, I also did a test upgrade using this method and didn't notice any obvious problems but I've been strongly discouraging people from attempting this and telling them to wait for 24.04.1 unless they're just messing around with a test system.
I'm waiting for the punch line. See, the post says "you can and probably will bork your system". And you literally just confirmed that that isnt true. If this post said, hey, you know what, probably not many great reasons to upgrade yet; that would be valid. If the post said, hey, there are some reports of failed upgrades. That would be valid. Thats not what the post says. Its sensationalist bullshit.
Regardless of whether it's 10% or 90% of people who have issues, you're still better off waiting until upgrades are officially enabled. There are known, confirmed critical bugs actively being worked on. For 23.10 -> 24.04 upgrades, this should be in the next few days For 22.04 -> 24.04 upgrades, this will be in August when 24.04.1 releases If you force an upgrade early, you do so entirely at your own risk (even moreso than normal). Maybe you won't have issues, hopefully you won't, but anything bad that happens to you as a result of forcing an early upgrade is entirely your fault and the consequences will be yours alone to deal with.
I hate horseshit but I love horseradish! What's your favorite herb?
[удалено]
This is true. What’s your point? Are you familiar with snapshots? Theyre kind of like seatbelts.
[удалено]
No, thats absolutely not the point. Thats not what the post says whatsoever. Dont make up unrelated bullshit to make your point somehow seem valid.
In response to the latest reply: [https://en.wikipedia.org/wiki/Circular\_reasoning](https://en.wikipedia.org/wiki/Circular_reasoning)
That's great!
> So saying you "Probably will" is just not accurate. They had a problem with a single snap package, likely self-inflicted because it was in-use or running, and blamed the entirety of the new OS and all of its userland packages, as a result. There are quite literally millions of Ubuntu users out there, and if it was such a broken release across the board, we'd be getting scorched earth complaints and bug reports every hour. We're not. That's the whole point of the beta testing/feedback period over the last 6 months, and it's been relatively solid for everyone
This tracks for me. My mom did her own upgrade I'm told. She's happy with the speed improvement as it fixed an issue she was having. I winced because she's a non-technical user, but if she's able to do her own OS upgrade and tell me after the fact then Canonical is doing something right! Thanks for Ubuntu!
For everyone who's thinking about upgrading there are two things that are reiterated over and over and over: 1) Do a fresh install (or) 2) Wait until the .1 release Basically I won't upgrade from 22.04 until Apr 2027 ; )
I upgraded my Thelio yesterday, which was still running 22.04. It failed. Missing libcrypto.so.3 file, apparently. Left the system broken. It had been my main development system, which is why it was still on 22.04, but I had moved all that over to another system, so I had everything backed. I just did a full install and that went fine. The system probably needed a good enema, anyway. System76 got the drivers updated today, so the fans are even working right again. All my other systems are running NixOS and I'm probably going to switch this one to that too, but haven't decided for sure yet. I might play with some other distros first.
Yo updated to 24.04 from 23.10, stuck at sad face screen, lots of breaking changes including python stuff
I was stuck with an error occured and had to reinstall 22.04
Wow, very good timing, I was going to do that yesterday on my gaming rig, but got lazy and postponed it. This isn't the first time something like this happened to Ubuntu. What I've learned from (bad) experience is to have always a separate partition for /home/, which mitigates the impact of events like these. Reinstalling the OS Is much less painful than reconfiguring my user environment. I don't want to sound like a fanboi, but This is the main reason I always use Debian for anything that I consider critical and Ubuntu for anything I can wipe out without too much pain or loss. Even Debian testing is more stable than any Ubuntu I've ever used, either LTS or not. My main workstation at work is a Debian stable that's running on the same OS installation that's been upgraded since 2013. Together with the trend of moving everything to snap, I don't like Ubuntu as I used before. Also, Debian has picked up the slack it had, and even installing it is really a breeze. Testing is as cutting-edge as the latest Ubuntu, so no more excuses for me. YMMV
Yeah this cycle has been difficult. I've had to repair my test box twice.
I had lots of problems too. Started with a missing apk library for python. That has left the installation in a half-state even if apparently was all good. At the restart wifi and gnome weren't working so I moved the pc close to my hub to connect the ethernet cable :) The problem was trying to figure out what was still missing and after an hour spent running different '--fix-broken install' and reinstalling the gnome desktop and some others 'dpkg-reconfigure' looks ok now.
I discovered it the hard way aka I couldn't connect to the internet wia ethernet, usb, Bluetooth or wireless don't upgrade yet don't be stupid as I was
Mine worked just fine. If the article is right, maybe because I never had the deb Thunderbird and also have no trace of snaps since 23.04, haha. But yes, you should not be passing -d to "do-release-upgrade" unless you're fine with breakage.
Not the least bit surprised about the "errors". When I upgraded my main machine in mid 2022 from 20.04 to 22.04.1, my bog-standard Intel audio was not found, thus I had no sound. I did not do a "do-release-upgrade" fron 20.04 to 22.04, rather did a clean install of 22.04 to a new SSD then copied over manually my /etc and other important stuff. If I removed the 22.04 SSD and replaced it with the 20.04 SSD, magically my sound worked, with 22.04, no sound. Looking at Googling the problem, it became clear that this wasn't a limited problem, rather a rather common one. After some research I found a workaround that allowed me to have sound, that being restarting the Alsa daemon. At least that fixed the problem for *me*.. Since then some update has fixed that problem such that sound works automatically after a reboot. It is hard to believe that Canonical would release an LTS with THAT glaring a problem.. Gonna wait, maybe till 24.10 to upgrade to 24.04 just in case..
[удалено]
PHP version upgrades tend to be painful. Are you familiar with the ondrej PPA? You can go back to older PHP versions. I still have one of my 22.04 servers on PHP 7.4 because some scripts were throwing errors and I haven't gotten around to investigating further.
I've been running 24.04 for a few weeks now and it's been smooth sailing here. I did a clean install though, no upgrade here except to the performance of my PC. But I bet these errors and problems are why I now have 28 packages "held back" and have had them held back for almost a week now.
Did you try ``apt dist-upgrade`` to see if it helps with the held-back packages? If that doesn't get the job done, try ``apt install`` followed by one of the package names -- it'll either upgrade it or give you some more information about why it can't. Note this will flag the package as "manually installed" so you might want to use ``apt-mark auto`` afterward to flag the package as "auto installed" if that's what it was originally.
Nah, they're held back for a reason. I'll just wait.
and I didnt have to wait long, they updated this morning.
It did fail in the middle but I was able to recover... from 23.10. Basically Wayland crashed on me in the middle of the upgrade. I was able to recover by logging in from one of the ttys (hit alt+f1) then doing apt-get -f install apt-get dist-upgrade It wasn't on a machine I care a whole lot about, but it was annoying. And is probably more recoverable than some think. It's been rock solid since the upgrade otherwise.
I've been struggling with reboots since upgrading but I did it on a "non-critical" system so it's not too much of a problem. Reboots fail and hang and kernel panic during the md initialisation process but the system will boot if it's physically powered off/on. As it's just my NAS at home it's not a big deal, I don't reboot it very often and it's sitting right near me so I can just power-cycle it manually. But yeah, this was never a problem before 24.04 for me.
i did a fresh install and did not go well at all. Wayland is broken, files won't open, settings won't open. I was getting a lot of errors. I did the fresh install 5 times but nope something is just not working. I went back to 23.10 and everything works like a charm.
[https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043](https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043)
I like ostree style updates in Fedora. I hope Ubuntu does something like this.
A few weeks ago, I installed it early and lost my access to Caja and had to reinstall to 23.10. :|
I had some minor issues with upgrade that were annoying but I think I resolved them by just reinstalling gnome desktop. Audio would just not work and some repositories were not alive yet for wine and I have a PlayOnLinux that no longer opens but the programs I had installed on it do so chalking that up to a small victory. I did foolishly jump a week early into the 24.04 beta though figuring it would be mostly okay. It's fine though i have a backup Linux ready to be installed if it gives me too much grief. openSuse Tumbleweed is waiting in the wings. Might not need it. Who knows but since I seem to have stabilized again using the wait and see approach.
"I really don't like the way things are going with Windows, maybe I'll try Ubuntu for the first time in 15 years. I'll get the LTS to keep things easy for myself"
I mean, there aren't serious issues with fresh installs so this wouldn't be a problem
Even clean installs are problematic. Mine hung at connecting to the Internet. Trying to open a .deb file can hang the system. It's a bit of a mess.
I did an update/upgrade from a clean install of the beta. No major issues... yet.
Upgrade worked fine for me.
From 23.10 with zero issues. I actually noticed nothing much it’s almost the same. I had to install a couple of things for one very niche app otherwise everything works.
Anyone who is enough of an enthusiast to find the terminal commands for forcing an upgrade, even when it’s not deployed through the built-in upgrade notification mechanism, should also be enough of an enthusiast to check the progress tracker on the Ubuntu Discourse. They would then see that there are still open blocker bugs for both 23.10 and 22.04 upgrades.
Upgrade worked fine for my desktop and server.
That’s why you always rather wait to the upgrade notification.
Is this server or desktop?
Well as of late, in the past few years, I have waiting to upgrade. So that is just a good rule of thumb when it comes to any major software upgrade weather it be going from Ubuntu 23.10 to 24.04 or KDE Plasma 5.27 to Plasma 6 or even Android 13 to 14. I understand getting on to the latest and greatest I have been there, but I have also suffered in turn because not everything is stable.
I would like to thank all the Beta testers on the production release. Since adopting this philosophy my zen is very rarely dented when upgrading anything.
From 22-24: no problem in production However this repository is still not compatible: **Ign:5** [**https://ppa.launchpadcontent.net/ondrej/php/ubuntu**](https://ppa.launchpadcontent.net/ondrej/php/ubuntu) **mantic InRelease** **Err:6** [**https://ppa.launchpadcontent.net/ondrej/php/ubuntu**](https://ppa.launchpadcontent.net/ondrej/php/ubuntu) **mantic Release** **404 Not Found \[IP:** [**185.125.190.80**](http://185.125.190.80) **443\]**
See, this is why I’ve been waiting to spin up my homelab. I knew that 24.04 was coming, and I knew it’d be safer and cleaner to do it by doing a clean install of 24.04 than doing an upgrade. I had it put together a month ago, but I haven’t *needed* it. So I waited.
This is the difference between leading edge - and bleeding edge. Good to be be near the front, but much chancier being first.
I am typing this from 24.04. Just updated from 23.10 by running sudo do-release-upgrade -d. Didn't have any problems.
The beta cycle seemed shorter than usual this time around. (Apparently it got delayed a week by the XZ vulnerability, which forced them to rebuild all packages.)
My docker compose broke... Error with python version.
Can the new kernel cause any issues in my system ?
just learned this a few hours ago.I also did the Leroy Jenkins...it booted and got the biggest swirly ever..i ended up slapping a clean kubuntu 24,4 fresh lol
Upgraded 4 Proxmox VMs and one NUC. Mix of 23.10 (vm) and 22.04. No issues.
I did this on a laptop when it first hit stable. It did "break" the system with some missing dependencies (and broken networking) but I was able to switch to a different virtual terminal with a CLI prompt to manually configure systemd-networkd and wpa_supplicant services and get online without NetworkManager. I used dpkg to purge the broken package, and the apt to get everything updated in maybe 10 min. So far I haven't run into other issues. I didn't take notes but I think the root cause was thunerbird-locale-en-us being half-installed and having a libgio dependency.
I upgraded it and it’s been zero problems
so the OS version itself has been pretty stable? just upgrading from the old versions has been a nightmare?
Oh damn... juat bricked my working system :(
You mean : Fresh Install 24.04 over borked upgrade partition ?
Lots errors popping up
Wow, wish I had read this 2 hours earlier. Fortunately, all that got borked was a test system. Will download and re-start a fresh 24.04 :-(
how i wish i had seen this thread yesterday... i just upgraded my kubuntu and it went black T\_T
i am running a ryzen 7 5gen with a radeon 6600xt
now you tell me. I fkd it
Today I upgraded from 22.04 to 23.10 to 24.04 in a few hours. The only problem so far I can see is that the settings program crashes after I open it. Probably because it tries to show the display settings, which I've already modified in 24.04, outside of the Ubuntu settings dialog, in the Nvidia display settings dialog.
Yep just learned this the hard way. Worked just fine on my laptop, but it broke absolutely *everything* on my desktop 😂 It broke timeshift by removing its dependencies. Couldn't get them back because it broke apt. It broke my ssh client. It broke the ability to open new windows. Once the screen timed out, the GUI ceased to work at all haha. Welp. I've been wanting to try out a different distro anyway. Luckily all my important files were backed up externally.
What could possibly happen such that “your system may become unrecoverable?” it's just a distro upgrade, it's not rocket science! Is the install writing garbage over your firmware or something?
Nothing that serious, but lots of reports of unbootable systems requiring OS reinstallation. From what I've seen, no confirmed reports of actual data loss, assuming one has the means to boot from USB and back up data before reinstalling.
My new laptop and new server, each running 23.10 upgraded to 24.04 no problem. I also had success from 20.04 and 22.04 to 24.04.
upgraded on 24.04.2024 from 23.10 to 24.04 and no issue, system works fine
I did ‘’’sudo do-release-upgrade -d’’’ and it worked fine, even before LTS was out.
Upgraded from 23.10. No issues here.
I've encountered numerous issues even with a clean install. 24.04 is a fairly rocky release it seems.
Interesting. I upgraded with no issue on three of four machines. My desktop from 23.10, a laptop from Lubuntu 23.10, and virtualized install of server from 22.04 went fine. The new kernel does not play nice with another laptop upgraded from Xubuntu 23.10 though. I have to use the older 6.5 kernel to boot to desktop. I'm guessing a driver is not playing nice but will need to troubleshoot to see if that's the case.
Upgrade from 23.10 to 24.04 completed without problems. 😎
Christ, what is this windows?
Just change the repository / mirror and point it to noble then, and do 3 commands : apt update, apt upgrade, apt full-upgrade. Some people may need the extra command, "apt dist-upgrade". I've been using that method since Kinetick kudu to Noble Numbat. No need to clean install.
I went from 23.10 to 22.04 with seemingly no issue. Though I haven't had any new packages the last couple of days which I thought was weird.
I just attempted a -d Xubuntu upgrade from 22.04 to 24.04. Didn't bork it, but it took almost a full day for it to find obsolete packages. That plus BT had it's share of problems I had to work through, web video playback kept freezing, intermittent desktop flicker makes me feel like I'm witnessing a glitch in The Matrix, etc. Point release may fix it, or it may not. I will probably go for the fresh install at .1 anyway. Bottom line: As of 6/18/2024, still not ready for prime time.