Created attachment 184740 [details] Bug report System update returns an error: <html>Package download failed:<br/><br/>E: http://archive.ubuntu.com/ubuntu noble-security/main amd64 linux-firmware amd64 20240318.git3b128b60-0ubuntu2.17 is not (yet) available (500 Internal Server Error [IP: 2620:2d:4000:1::102 80]) </html>
*** Bug 509155 has been marked as a duplicate of this bug. ***
(In reply to Prodyut Mukherjee from comment #0) > Created attachment 184740 [details] > Bug report > > System update returns an error: > > <html>Package download failed:<br/><br/>E: http://archive.ubuntu.com/ubuntu > noble-security/main amd64 linux-firmware amd64 > 20240318.git3b128b60-0ubuntu2.17 is not (yet) available (500 Internal > Server Error [IP: 2620:2d:4000:1::102 80]) > </html> I'm getting the same problem.
*** Bug 509168 has been marked as a duplicate of this bug. ***
it's an upstream debian archive issue that will resolve soon when the file sync is completed properly https://askubuntu.com/questions/1555531/install-linux-firmware-update-failed
*** Bug 509196 has been marked as a duplicate of this bug. ***
*** Bug 509200 has been marked as a duplicate of this bug. ***
*** Bug 509206 has been marked as a duplicate of this bug. ***
*** Bug 509208 has been marked as a duplicate of this bug. ***
*** Bug 509219 has been marked as a duplicate of this bug. ***
(In reply to Carlos De Maine from comment #4) > it's an upstream debian archive issue that will resolve soon when the file > sync is completed properly > https://askubuntu.com/questions/1555531/install-linux-firmware-update-failed Apologies to all it's an upstream Ubuntu issue. This does happen, no distribution is a immune from mistakes/failures/problems
*** Bug 509228 has been marked as a duplicate of this bug. ***
This does happen, and yes no distribution is immune from mistakes/failures/problems, but extremely few (if any) distributions would dishonestly rename an issue from "The Never Ending Bug" (which is the truth) to a half-truth that the "System update is not happening" and then proceeding to close out the issue (again) as "Resolved", when my system still will not update and absolutely no solution has been offered to adequately explain it and fix it. Do I need to open yet another issue for the same exact thing again? How many duplicate "resolved" issues would that make then? Six or seven? It is one thing to have mistakes/failures/problems, but it quite another to never go back and fix your mistakes/failures/problems, so this is minus 50 points for KDE Neon as a distribution, because if they would act like that with a simple issue like this, what other issues could KDE Neon have had that we would never know about or think were fixed because it was listed as "Resolved", when in reality it was never actually resolved? My experience with Plasma (and KFind) led me to believe that KDE was reputable and trustworthy and competent, and that is why I wanted to go to KDE Neon, but now I have no reason ever to want to have anything to do with KDE Neon or maybe even Plasma. I think now I should go the opposite direction and patronize Linux Mint or some other distro based on Mate or something like that instead. If you can fix this issue in one day (like I think can be done) and truthfully tell me what was wrong, I might forgive this gaff, but this is the fifth time that the same exact issue has been brought up and immediately "resolved", yet it still isn't working. So I doubt that would happen, although I can hope you are different and this really is a "one time mistake". I would love to be proven wrong, because I would love to be proven wrong, so feel free to prove me wrong. On 9/7/25 00:46, Carlos De Maine wrote: > https://bugs.kde.org/show_bug.cgi?id=509152 > > --- Comment #10 from Carlos De Maine <carlosd.kde@gmail.com> --- > (In reply to Carlos De Maine from comment #4) >> it's an upstream debian archive issue that will resolve soon when the file >> sync is completed properly >> https://askubuntu.com/questions/1555531/install-linux-firmware-update-failed > Apologies to all it's an upstream Ubuntu issue. This does happen, no > distribution is a immune from mistakes/failures/problems >
I must agree and diaagree here. Yes, errors can happen, even at Ubuntu, but it's abit strange that no Ubuntu sysadmin fixed something like this in over 2 days, as it affects their own LTS version... Some log, some alert should have happenend ther and someone should have fixed it, but as someone on askubuntu.com said: Just wait for the everything to besynced again, will not take more then one or two weeks (!!!) then it should work again... And no,it has nothing to do with KDE or neon as a ditro, after all the problem is one at Ubuntu (which is mainly GTK bases as I remember). The only problem here is to call it resolved, (which it is not), it is correct, that it is upstream, but it definitely is not resolved!
Please read https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean to understand the meaning of RESOLVED.
*** Bug 509243 has been marked as a duplicate of this bug. ***
So I guess if it was actually working you would redefine it as being unresolved? On 9/7/25 12:37, Antonio Rojas wrote: > https://bugs.kde.org/show_bug.cgi?id=509152 > > --- Comment #14 from Antonio Rojas <arojas@archlinux.org> --- > Please read > https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean > to understand the meaning of RESOLVED. >
marked as verified to please the pedants even thought the guidelines state - RESOLVED UPSTREAM means the issue is not caused by any KDE software, but rather in some upstream software that KDE software depends on, such as Qt or another software library--even if the issue has not yet been fixed in that upstream software, or if the version of it that fixes the bug is not yet released or available in your distro.
marking as resolved upstream as the package now downloads as expected carlos@carlos-slimbook-unstable:~/Projects/neon_qt6/qt6-wasm$ sudo apt install --reinstall linux-firmware Reading package lists... Done Building dependency tree... Done Reading state information... Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 537 MB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://security.ubuntu.com/ubuntu noble-security/main amd64 linux-firmware amd64 20240318.git3b128b60-0ubuntu2.17 [537 MB] Fetched 537 MB in 37s (14.6 MB/s)