OK, so going to try to run sudo apt upgrade in terminal mode to install the Security Only Updates(then do it using softwre updater selecting ‘continue’ not ‘partial upgrade’ if that command fails to run in terminal), and even if nautilus does or does not get corrupted, I do want to use exec=nautilus --new-window %U in usr/share/applications to get GSK_RENDERER=cairo nautilus put in the nautilus icon - how is this done? just run it in a terminal or do I need to edit something somewhere in the usr/share/applications directory?
btw - great new title…
finally, I have Lubuntu installed on an old DELL laptop and do not care for it
I’ve been on Ubuntu since 18.04lts
Find the Exec line (should be line 6)and put a comment symbol # (i.e.ignore) at the beginning (so that it can easily be re-instated by removing the #)
Then , add the line in my example
OK - held my breath and ran in terminal the upgrade command (w/software updater settings set to ‘Security Updates Only’), and it ran (took awhile - went out and did early voting for TN primary) - rebooted to 6.8.0-136 kernel, my hibernate button is still there, and most importantly nautilus is not corrupted… THEN, followed your instructions to edit that desktop file - nautilus still not corrupted and came up via terminal command w/o the usual errors:
~/Desktop$ nautilus
** Message: 16:07:45.524: Connecting to org.freedesktop.Tracker3.Miner.Files
VERY happy camper - I am going to immediately image (G4L lzop) this current partition (sda5) before I do anything else so I can return to it if needed… but I suspect there will be no more corrupted nautilus now that that Gsk-Message: 16:19:22.335: Failed to realize renderer of type ‘GskNglRenderer’ for surface ‘GdkWaylandToplevel’: OpenGL ES 3.0 is not supported by this renderer. no longer haunts nautilus or is there to potentially corrupt it!
I seem to finally be back at a ‘normal’ ubuntu 24.04.3lts - will stick to security updates only for update/upgrade and let it be done by software updater that I pray is no longer going to suddenly corrupt nautilus
Once again you have been indispensable, and your diligence is to be commended.
Well, was able to run sudo apt upgrade in terminal (under software updater’s updates setting ‘security updates only’) and it installed a lot w/o corrupting nautilus or removing my hibernate button…
BUT, when I go to run software updater itself, even after upgrading via terminal, I still get:
…and being told NOT to run ‘partial upgrade’, and just click ‘continue’, it just pops up with “The software on this computer is up to date” - why does it still try to get me to run partial upgrade when I run software updater? Should I try changing the setting to ‘security and recommended updates’ and run the terminal upgrade again? It may or may not be what corrupts nautilus…
I ran sudo apt update under the ‘security and recommended updates’ setting and got:
~/Desktop$ sudo apt update
[sudo] password for batgirl:
Hit:1 http://archive.ubuntu.com/ubuntu noble InRelease
Hit:2 http://security.ubuntu.com/ubuntu noble-security InRelease
Hit:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu noble InRelease
Hit:4 http://archive.ubuntu.com/ubuntu noble-updates InRelease
Hit:5 https://ppa.launchpadcontent.net/unit193/inxi/ubuntu noble InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
144 packages can be upgraded. Run 'apt list --upgradable' to see them.
I ran sudo apt update under the ‘security updates only’ setting, and then sudo apt upgrade and got:
~/Desktop$ sudo apt update
[sudo] password for batgirl:
Hit:1 http://security.ubuntu.com/ubuntu noble-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu noble InRelease
Hit:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu noble InRelease
Hit:4 https://ppa.launchpadcontent.net/unit193/inxi/ubuntu noble InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
15 packages can be upgraded. Run 'apt list --upgradable' to see them.
batgirl@batgirl-E-475M:~/Desktop$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libreoffice-style-breeze lp-solve
Use 'sudo apt autoremove' to remove them.
Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
openjdk-11-jre openjdk-11-jre-headless qt5-qmake-bin
libmagickcore-6.q16-7t64 qtbase5-dev-tools ofono libqt5xml5t64
qt5-gtk-platformtheme imagemagick libqt5sql5t64 libmagickcore-6.q16-7-extra
libqt5qml5 libqt5test5t64 libwinpr2-2t64 libcjson1 libavdevice60 ffmpeg
libqt5quick5 libopenexr-3-1-30 libpostproc57 python3-wheel libqt5gui5t64
libmbedcrypto7t64 libavcodec60 libavcodec60 libqt5printsupport5t64
qtbase5-dev libqt5concurrent5t64 libavutil58 libavutil58 libqt5widgets5t64
imagemagick-6.q16 libswscale7 libfreerdp-server2-2t64 python3-pip
libfreerdp-client2-2t64 libqt5dbus5t64 libqt5network5t64 libqt5opengl5-dev
libqt5opengl5t64 libswresample4 libswresample4 imagemagick-6-common
libqt5sql5-sqlite libqt5qmlmodels5 qt5-qmake libavformat60 libfreerdp2-2t64
libqt5core5t64 libavfilter9 libmagickwand-6.q16-7t64
Learn more about Ubuntu Pro at https://ubuntu.com/pro
The following packages have been kept back:
gir1.2-polkit-1.0 libegl-mesa0 libgbm1 libgbm1:i386 libgl1-mesa-dri
libgl1-mesa-dri:i386 libglx-mesa0 libglx-mesa0:i386 libpolkit-agent-1-0
libpolkit-gobject-1-0 mesa-libgallium mesa-libgallium:i386 pkexec
policykit-1 polkitd
0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
I assumed there’s still 15 security updates only packages available, but is not installing them for some reason - what am I doing wrong?
Thanks! I will be patient with this in terminal manually updating with ‘apt upgrade’…
BTW - will this ‘Partial Upgrade’ from running the Software Updater also go away and return to the normal list of updates to install? (which is why I’m currently having to do the terminal version for update/upgrade)
If I select ‘Continue’ in lieu of ‘Partial Upgrade’, it just pops up saying system is up to date. I was advised not to run the partial upgrade ~ I have in the past and sometimes it runs w/o corrupting nautilus, but last time I did it corrupted it (nautilus and any ‘files’ type window for ‘save as’/’download to’/’open’/etc. will just blink on/off/on/off, freeze, not responding popup, lockup requiring cold boot, etc.).
not sure what you’re instructing - did the one you did above and got above output
did apt policy on one of the 15 not getting installed, and the first one came up with this:
~/Desktop$ apt policy gir1.2-polkit-1.0/noble-security 124-2ubuntu1.24.04.3 amd64 [upgradable from: 124-2ubuntu1.24.04.2]
N: Unable to locate package gir1.2-polkit-1.0/noble-security
N: Unable to locate package 124-2ubuntu1.24.04.3
N: Couldn't find any package by glob '124-2ubuntu1.24.04.3'
N: Unable to locate package amd64
N: Unable to locate package [upgradable
N: Unable to locate package from:
N: Unable to locate package 124-2ubuntu1.24.04.2
Ian - you’re so sweet to jump in here to help with the end of a very long problem that starts with nautilus corruption from updates, to this hopefully end run - btw: handle here is Jaimie…
I use 6.8.0-85 in between new kernel “try-outs” (most current kernel on mine is 6.8.0-135) and 6.8.0-79 is another very stable fall back I locked… 6.8.0-84 I’ll delete soon like I finally did 6.8.0-53 ~ all very stable (compared to all kernels in-between, at least on my system setup…) but time to let it go, too
Looks like two groups of kept-backs: A group of Mesa packages, and a group of Policykit packages.
All the clues and diagnostic data in this topic are pointing to choices you made in the past to manage your packages manually…and then making mistakes doing so. The Nautilus problem, and other unexpected behaviors, are consequences of those human choices. You, the human, have introduced a logical inconsistency into your package system (a.k.a “created a Frankensystem”). Since the inconsistency cannot be solved by logic, apt cannot fix it for you.
At this point, there are a couple approaches for you to resolve the logical inconsistency that has broken your updates. You get to decide the next step.
If the user remembers what changes they made (“Oh, I tried XYZ last year when I had a Mesa issue”), it’s usually not too difficult to remove those packages and replace them with packages from the Ubuntu repositories. The removal clears the version number collision(s) that prevent upgrades.
It fixes the actual underlying problem…but it’s risky. Removing polkit risks breaking your system quite awfully. A full data backup is essential, because there’s a very good chance you will wind up reinstalling Ubuntu. This option is most popular with learners and tinkerers who want to avoid the problem next time.
The other option is to skip the attempt to fix, and simply back up your data, reinstall Ubuntu, and the restore your data on the new system. This option is most popular with folks who just want a reliable, working system rapidly again.
OR - do this Partial Upgrade, and if it corrupts nautilus (and/or trashes my hibernate button), then restore my G4L lzop image done a few days ago, re-fix the OpenGL ES 3.0 bug per tea-for-one, and ignore these terminal run apt upgrade ‘holdup updates’ (ie stop using update/upgrade via terminal) and settling for the few minimal updates that come thru using ‘Continue’ on the Software Updater ‘partial upgrade’ attempts ~
… gotta remember, I’m fine with just shutting down Software Updater completely again - just hoped the discourse crowd might have a better solution
There’s still Fedora 43 and Win10 (and WinXP) that I use more than Ubuntu - Ubuntu is used for a few workhorse things from time to time… but mostly play games on it
Locked?
OK - so, having to resort to doing the ‘Partial Upgrade’, and it did indeed corrupt Nautilus AND took away my hibernate button - seems the fix for the OpenGL ES 3.0 bug per tea-for-one didn’t make any difference. Re-installing my G4L lzop image I did a few weeks ago before all this discourse experiments ran its course, and will no update/upgrade anymore…
