Hello everyone! This is a problem I've been having for about a month now, and the forums I've tried thus far have been fruitless, so I thought I'd say what's been happening here.
Before December, any packages I had installed on my Kubuntu LTS 22.04.3 laptop as normal system packages (be they through the Ubuntu repos, PPAs, or downloaded deb files) were all listed individually in Discover. Trying to update any and all of them required me to input my password after hitting "update selected" in Discover.
Starting in December, however, all packages installed this way, regardless of origin, have been getting lumped together into one big update option, labeled "System Upgrade." This would include core libraries and programming languages, to things like Spotify and Google Chrome. That is, somewhere, Discover started viewing all of these as the same.
​
Say I had google-chrome-stable, libc-bin, and​ firefox​ all needing updates. Under System upgrade, it would say "3 packages to upgrade." Alone, this is innocuous, but the problem is that updating these packages through Discover does not prompt me for my password. That is, somehow Discover is bypassing sudo (or has been opened with sudo already active), whereas before it would always prompt me, and nala/apt still requires me to do so. Finally, after updating this "System upgrade" (which sometimes is literally just Firefox), I am prompted to restart my system, and I am unable to download any more updates until then. That is, if I have flatpaks that I now need to update, but I installed that "System upgrade" update, I am not shown those updates until I've restarted.
This is incredibly strange behavior that I've never seen happen before. What might I be able to do to figure out the cause? And perhaps return my Discover to its original working order?
And yes, the command line does work, but I'd prefer not to receive any replies saying "just use apt?". That would be ignoring the problem, rather than fixing it. I still have a faulty software manager on my system at the end of the day, and I do not want that to be the case!
Thank you in advance for any responses!!! 😄
Edit: Because I forgot to mention this: nala shows that the python3-update-manager and update-manager-core packages are being held back; this has been the case for at least 3 weeks, potentially since this whole thing started.
Before December, any packages I had installed on my Kubuntu LTS 22.04.3 laptop as normal system packages (be they through the Ubuntu repos, PPAs, or downloaded deb files) were all listed individually in Discover. Trying to update any and all of them required me to input my password after hitting "update selected" in Discover.
Starting in December, however, all packages installed this way, regardless of origin, have been getting lumped together into one big update option, labeled "System Upgrade." This would include core libraries and programming languages, to things like Spotify and Google Chrome. That is, somewhere, Discover started viewing all of these as the same.
Say I had google-chrome-stable, libc-bin, and​ firefox​ all needing updates. Under System upgrade, it would say "3 packages to upgrade." Alone, this is innocuous, but the problem is that updating these packages through Discover does not prompt me for my password. That is, somehow Discover is bypassing sudo (or has been opened with sudo already active), whereas before it would always prompt me, and nala/apt still requires me to do so. Finally, after updating this "System upgrade" (which sometimes is literally just Firefox), I am prompted to restart my system, and I am unable to download any more updates until then. That is, if I have flatpaks that I now need to update, but I installed that "System upgrade" update, I am not shown those updates until I've restarted.
This is incredibly strange behavior that I've never seen happen before. What might I be able to do to figure out the cause? And perhaps return my Discover to its original working order?
And yes, the command line does work, but I'd prefer not to receive any replies saying "just use apt?". That would be ignoring the problem, rather than fixing it. I still have a faulty software manager on my system at the end of the day, and I do not want that to be the case!
Thank you in advance for any responses!!! 😄
Edit: Because I forgot to mention this: nala shows that the python3-update-manager and update-manager-core packages are being held back; this has been the case for at least 3 weeks, potentially since this whole thing started.
Comment