!!!!WARNING ALL FREEBSD DESKTOP USERS!!!! : Insane pkg's new version upgrade of installed apps

[Charlie Brown]

Wow, I just did a regular pkg update && upgrade, pkg told me only on package was going to be deleted and in fact half the system's app were deinstalled during the process so now I have to go trough the list of all deleted and installed package relating to that update.

Lots of stuff were being deinstalled and not reinstalled

a complete mess from the package manager, thanks pkg, great job!

For example had to reinstall firefox.

Freecad, dolphin, kdevloppe, konqueror, kcalc and lots of other package are not in the system rigth now.

Be careful out there pkg --version
2.3.1 might fail you. you cant trust it.

I should have waited, I knew it. When you see a major minor update like this, take your time and press n not y, come back two months later and then press y. or you'll be the guinea big.

 

[Useradd]

I tried to warn people:

pkg upgrade broke my installation (again). This time pkg: 2.2.2 -> 2.3.1 on my 14.3 test installation (something about Linux support). I dare not try it on my main 14.3 installation. This is why I am more nervous about upgrading FreeBSD than other operation systems as I stated earlier in this thread. I am using UFS so no roll back.

Affected applications include libreoffice.

 

[Charlie Brown]

I tried to warn people:

There should be a banner warning on the top of the forum for shitty update like that. like !!!!WARNING ALL FREEBSD DESKTOP USERS!!!! If you care about your stable working installation, do not upgrade to PKG version ...

 

[astyle]

Another one for the books - I just do a fresh installation of a bare-bones system, and then compile ports from that point on. Precisely because of this.

 

[freezmi]

the opencascade package was not version bumped at least since 2025-07-10T06:08:35+0000, but after the big upgrade today

# revdep-rebuild.sh # see https://gist.github.com/rodan/4c33509c3e25655d6665400b87d84be7
the following binaries have failed the dynamic linker test:
* /usr/local/bin/DRAWEXE
ld-elf.so.1: /usr/local/ffmpeg4/lib/libavcodec.so.58: version LIBAVCODEC_58 required by /usr/local/lib/libTKService.so.7.9 not defined
/usr/local/bin/DRAWEXE was installed by package opencascade-7.9.1_1

forcefully re-installing opencascade (with the same apparent version) fixed it.

and the new keepassxc version has the yubikey feature disabled due to an apparent incompatibility, so had to reinstall the old package from /var/cache/pkg

 

[Starcat]

Another one for the books - I just do a fresh installation of a bare-bones system, and then compile ports from that point on. Precisely because of this.

I did a fresh install, having had a nicely running 14.1 install prior to this. With 14.3, I immediately encountered lots of gotchas with a basic pkg install. It seems like a hot mess, especially for a minor release.

 

[Andrey Lanin]

Hmm.. I did an update yesterday (two workstations). Everything went fine.

[lanin@freebsd3 ~]$ pkg info pkg
pkg-2.3.1
Name           : pkg
Version        : 2.3.1
Installed on   : Wed Oct  8 09:10:00 2025 MSK
Origin         : ports-mgmt/pkg
Architecture   : FreeBSD:14:amd64
Prefix         : /usr/local
Categories     : ports-mgmt
Licenses       : BSD2CLAUSE
Maintainer     : pkg@FreeBSD.org
WWW            : https://github.com/freebsd/pkg
Comment        : Package manager
Options        :
        DOCS           : on
Shared Libs required:
        libarchive.so.7
        libc.so.7
        libcrypto.so.30
        libelf.so.2
        libjail.so.1
        libm.so.5
        libssl.so.30
        libthr.so.3
        libutil.so.9
        libz.so.6
Shared Libs provided:
        libpkg.so.4
Annotations    :
        FreeBSD_version: 1403000
        build_timestamp: 2025-10-02T01:04:09+0000
        built_by       : poudriere-git-3.4.3-4-ga545ef33
        port_checkout_unclean: no
        port_git_hash  : e3fa556c9
        ports_top_checkout_unclean: no
        ports_top_git_hash: e3fa556c9
        repo_type      : binary
        repository     : FreeBSD
Flat size      : 47.2MiB
Description    :
Package management tool
[lanin@freebsd3 ~]$ neofetch
```                        `       lanin@freebsd3
  ` `.....---.......--.```   -/    --------------
  +o   .--`         /y:`      +.   OS: FreeBSD 14.3-RELEASE-p4 amd64
   yo`:.            :o      `+-    Uptime: 28 mins
    y/               -/`   -o/     Packages: 979 (pkg)
   .-                  ::/sy+:.    Shell: bash 5.3.3
   /                     `--  /    Resolution: 3840x2160
  `:                          :`   Theme: Adwaita [GTK3]
  `:                          :`   Icons: Adwaita [GTK3]
   /                          /    Terminal: mc
   .-                        -.    CPU: Intel Xeon Gold 5120 (56) @ 2.200GHz
    --                      -.     GPU: TU106 [GeForce GTX 1650]
     `:`                  `:`      Memory: 26031MiB / 195157MiB
       .--             `--.
          .---.....----.                                 
                                                         


[lanin@freebsd3 ~]$
[lanin@freebsd3 ~]$ freebsd-version -kru
14.3-RELEASE-p3
14.3-RELEASE-p3
14.3-RELEASE-p4

 

[Useradd]

After reinstalling the missing desktop applications I tried pkg upgrade again. The changes to be made look more normal this time, but it won't proceed for reasons I don't understand:

Spoiler: pkg upgrade

~ $ uname -r
14.3-RELEASE-p3
~ $ sudo pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating FreeBSD-kmods repository catalogue...
FreeBSD-kmods repository is up to date.
All repositories are up to date.
Checking for upgrades (148 candidates): 100%
Processing candidates (148 candidates): 100%
Checking integrity... done (1 conflicting)
- nvidia-kmod-580.82.07.1403000 [FreeBSD] conflicts with nvidia-driver-570.169.1402000 [installed] on /boot/modules/nvidia.ko
Checking integrity... done (0 conflicting)
The following 96 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
linux-rl9-elfutils-libelf: 0.192_1 [FreeBSD]
linux-rl9-elfutils-libs: 0.192_1 [FreeBSD]
linux-rl9-libjxl: 0.7.2 [FreeBSD]
linux-rl9-libxml2: 2.9.13_8 [FreeBSD]
linux-rl9-python39: 3.9.21_2 [FreeBSD]
linux-rl9-systemd-libs: 252_10 [FreeBSD]
nvidia-kmod: 580.82.07.1403000 [FreeBSD]

Installed packages to be UPGRADED:
alsa-lib: 1.2.13 -> 1.2.14 [FreeBSD]
apache24: 2.4.65 -> 2.4.65_1 [FreeBSD]
bash: 5.2.37 -> 5.3.3_1 [FreeBSD]
curl: 8.14.1 -> 8.16.0 [FreeBSD]
dbus: 1.16.2_3,1 -> 1.16.2_4,1 [FreeBSD]
egl-wayland: 1.1.19 -> 1.1.20 [FreeBSD]
expat: 2.7.1 -> 2.7.3 [FreeBSD]
gdk-pixbuf2: 2.42.12_2 -> 2.44.1 [FreeBSD]
glib: 2.84.1_2,2 -> 2.84.1_3,2 [FreeBSD]
hwdata: 0.396,1 -> 0.399,1 [FreeBSD]
jpeg-turbo: 3.1.1 -> 3.1.2 [FreeBSD]
libdisplay-info: 0.2.0 -> 0.3.0 [FreeBSD]
libinotify: 20240724_1 -> 20240724_3 [FreeBSD]
libinput: 1.27.1 -> 1.28.1 [FreeBSD]
libnghttp2: 1.66.0 -> 1.67.0 [FreeBSD]
libnotify: 0.8.6 -> 0.8.7 [FreeBSD]
librsvg2-rust: 2.60.0_3 -> 2.60.0_5 [FreeBSD]
libwnck3: 43.2 -> 43.3 [FreeBSD]
libxfce4menu: 4.20.1 -> 4.20.2 [FreeBSD]
libxfce4windowing: 4.20.3_1 -> 4.20.4_2 [FreeBSD]
linux_base-rl9: 9.6 -> 9.6_1 [FreeBSD]
mariadb114-client: 11.4.7_1 -> 11.4.8_1 [FreeBSD]
mariadb114-server: 11.4.7_1 -> 11.4.8_1 [FreeBSD]
mesa-dri: 24.1.7_6 -> 24.1.7_9 [FreeBSD]
mod_php84: 8.4.10 -> 8.4.13 [FreeBSD]
networkmgr: 6.4_2 -> 6.7_1 [FreeBSD]
ninja: 1.11.1,4 -> 1.13.1,4 [FreeBSD]
nss: 3.115.1 -> 3.117 [FreeBSD]
nvidia-driver: 570.169.1402000 -> 580.82.07_1 [FreeBSD]
openjdk17: 17.0.15+6.1_1 -> 17.0.16+8.1_4 [FreeBSD]
openjdk8: 8.452.09.1_1 -> 8.462.08.1 [FreeBSD]
orc: 0.4.41 -> 0.4.41_1 [FreeBSD]
pcre2: 10.45_1 -> 10.46 [FreeBSD]
perl5: 5.40.3_2 -> 5.42.0_1 [FreeBSD]
php84: 8.4.10 -> 8.4.13 [FreeBSD]
php84-ctype: 8.4.10 -> 8.4.13 [FreeBSD]
php84-dom: 8.4.10 -> 8.4.13 [FreeBSD]
php84-fileinfo: 8.4.10 -> 8.4.13 [FreeBSD]
php84-filter: 8.4.10 -> 8.4.13 [FreeBSD]
php84-iconv: 8.4.10 -> 8.4.13 [FreeBSD]
php84-intl: 8.4.10 -> 8.4.13 [FreeBSD]
php84-mbstring: 8.4.10 -> 8.4.13 [FreeBSD]
php84-mysqli: 8.4.10 -> 8.4.13 [FreeBSD]
php84-readline: 8.4.10 -> 8.4.13 [FreeBSD]
php84-session: 8.4.10 -> 8.4.13 [FreeBSD]
php84-sockets: 8.4.10 -> 8.4.13 [FreeBSD]
php84-xml: 8.4.10 -> 8.4.13 [FreeBSD]
php84-xmlreader: 8.4.10 -> 8.4.13 [FreeBSD]
php84-zlib: 8.4.10 -> 8.4.13 [FreeBSD]
pinentry: 1.3.1_2 -> 1.3.2 [FreeBSD]
pinentry-curses: 1.3.1 -> 1.3.2 [FreeBSD]
png: 1.6.49 -> 1.6.50 [FreeBSD]
pulseaudio: 17.0_3 -> 17.0_4 [FreeBSD]
py311-anyio: 4.9.0 -> 4.10.0 [FreeBSD]
py311-certifi: 2025.6.15 -> 2025.8.3 [FreeBSD]
py311-cryptography: 44.0.3_1,1 -> 44.0.3_3,1 [FreeBSD]
py311-dnspython: 2.7.0,1 -> 2.8.0,1 [FreeBSD]
py311-markdown: 3.8.2 -> 3.9 [FreeBSD]
py311-trio: 0.30.0 -> 0.31.0 [FreeBSD]
py311-truststore: 0.10.1 -> 0.10.4 [FreeBSD]
py311-typing-extensions: 4.14.0 -> 4.15.0 [FreeBSD]
python311: 3.11.13 -> 3.11.13_1 [FreeBSD]
qt6-base: 6.9.2 -> 6.9.3 [FreeBSD]
qt6-svg: 6.9.2 -> 6.9.3 [FreeBSD]
rsync: 3.4.1_2 -> 3.4.1_3 [FreeBSD]
samba416: 4.16.11_8 -> 4.16.11_10 [FreeBSD]
spirv-llvm-translator-llvm19: 19.1.8 -> 19.1.12 [FreeBSD]
spirv-tools: 2025.2.r1 -> 2025.4 [FreeBSD]
thunar: 4.20.3 -> 4.20.5 [FreeBSD]
unixODBC: 2.3.12_1 -> 2.3.12_2 [FreeBSD]
upower: 1.90.7 -> 1.90.10 [FreeBSD]
vte3: 0.80.3 -> 0.80.4 [FreeBSD]
vulkan-loader: 1.4.319 -> 1.4.327 [FreeBSD]
wayland: 1.23.1_1 -> 1.24.0_2 [FreeBSD]
wayland-protocols: 1.44 -> 1.45 [FreeBSD]
webp: 1.5.0 -> 1.6.0 [FreeBSD]
xfce4-panel: 4.20.4 -> 4.20.5 [FreeBSD]
xfce4-screensaver: 4.18.4_1 -> 4.20.1 [FreeBSD]
xfce4-session: 4.20.2_1 -> 4.20.3 [FreeBSD]
xfce4-settings: 4.20.1 -> 4.20.2 [FreeBSD]
xorg-server: 21.1.18,1 -> 21.1.18_1,1 [FreeBSD]

Installed packages to be REINSTALLED:
gtk3-3.24.50 [FreeBSD] (options changed)
hunspell-1.7.2_1 [FreeBSD] (direct dependency changed: perl5)
llvm19-19.1.7_1 [FreeBSD] (direct dependency changed: perl5)
mousepad-0.6.5_1 [FreeBSD] (direct dependency changed: perl5)
mythes-1.2.4_7 [FreeBSD] (direct dependency changed: perl5)
poppler-glib-25.04.0_2 [FreeBSD] (direct dependency changed: glib)
xfce4-notifyd-0.9.7 [FreeBSD] (required shared library changed)
zenity-3.44.5 [FreeBSD] (direct dependency changed: perl5)

Number of packages to be installed: 7
Number of packages to be upgraded: 81
Number of packages to be reinstalled: 8

The process will require 119 MiB more space.

Proceed with this action? [y/N]: y
[1/165] Upgrading linux_base-rl9 from 9.6 to 9.6_1...
Cannot install package: kernel missing 64-bit Linux support
pkg: PRE-INSTALL script failed
~ $

 

[vmisev]

Personally, I had no troubles with latest pkg upgrades, but I was posting about similar issue few times before and about my way to mitigate this potential problem, please see

Few years back, AFAIR ~v12, pkg upgrade removed LibreOffice, and I deleted older downloaded pkg from the cache before that upgrade, so I was left without it. Luckily, having LibreOffice is not critical for me, but I had to wait for it to reappear in the repo. Since, I'm always upgrading with pkg upg -n | grep Number first, and if there is nothing scheduled to be removed, I go with pkg upg -y, but if there is something that pkg upgrade wants to remove and I need it, I'll put lock on those packages first and only then go with pkg upg.

and a few posts bellow quoted post.

14.3-RELEASE-p4; pkg 2.3.1; all looks okay from my POV; \
FreeBSD.conf set to url: ".../$(ABI)/latest"; \
same for kmods

 

[Maturin]

I just updated two 14.3-RELEASE machines the last two days ordinarily with freebsd-update to
14.3-RELEASE-p3
14.3-RELEASE-p3
14.3-RELEASE-p4
after I first upgraded pkg: 2.2.2 -> 2.3.1
and everything went fine - as always.
Not even remotely the slightest issue.
Most "boring" update. That's exactly how I wants it.

Maybe you guys run some STABLE, CURRENT, or some inconsistent packages and ports mix up?

you'll be the guinea big.

What's that suppose to mean?

Run RELEASE for heaven's sake! I don't know which version you run. You didn't say. But many run CURRENT or STABLE just for always have the very newest versions. As long as you're not testing or developing I simply don't get why. And I wonder why people then wonder.
Of course you're getting no reliable functioning machine, when you run some not-yet-released development state which are meant for development, or testing purposes, but explicitly not for production (-> FAQs 2.3)
If you don't want any blood spilled don't run on the bleeding edge. If you chose for yourself a development version which is clearly not released, nobody makes you "the guinea pig" but you.

Besides that, some packages need to be built on the servers first, which takes some time.
Especially when you deal with such large packages like KDE, LibreOffice, et al, wait at least two days after a FreeBSD update is released. Give the servers a chance to get the packages up to date, too.
Your machine will neither be hacked, nor catch on fire, when you don't run the very latest version released immediatly, but wait for a couple of days.
I even overslept some upgrades months over EOL, and my computers still run not hacked (AFAIK.)
Relax! There are machines out there running over ten years old versions, still not burnt.

 

[vmisev]

Maybe you guys run some STABLE, CURRENT, or some inconsistent packages and ports mix up?

What's that suppose to mean?

Run RELEASE for heaven's sake! I don't know which version you run. You didn't say. But many run CURRENT or STABLE just for always have the very newest versions. As long as you're not testing or developing I simply don't get why. And I wonder why people then wonder.

Well, I like running at least one -STABLE because I'm always testing (only, not officially). TBH I'm not a dev, but I like to be among firsts to have new goodies in the base, like awk, bc, etc.

Yeah, this wasn't a very helpful post, sorry

 

[Useradd]

Run RELEASE for heaven's sake! I don't know which version you run. You didn't say.

I guess you didn't look at the spoiler in my last post.

or some inconsistent packages and ports mix up?

I didn't build any packages from ports. Glad it worked alright for you though. Maybe that will help someone figure out what's wrong.

Give the servers a chance to get the packages up to date, too.

I have done, but still have the same problem with the kernel missing 64-bit linux support. I know nothing about linux support but maybe one of the packages wants it now.

 

[vmisev]

I have done, but still have the same problem with the kernel missing 64-bit linux support. I know nothing about linux support but maybe one of the packages wants it now.

sudo sh -c 'sysrc kld_list+=" linux64";shutdown -r now'

 

[Useradd]

That fixed it! I did sudo sysrc kld_list+=linux64 and rebooted before I saw your updated command. I just had to remove the quotes because I already had nvidia-modeset in the list.

Thank you very much! Now I can go and update my main 14.3-RELEASE installation (I tried it on my test installation first).

 

[Yampress]

my last update removed the libreoffice pl-libreoffice and py311-lxml5 packages
(FBSD 14.3)

 

[meaw229a]

I did the Q4 package update today and so far only one minor problem.
VLC complains about missing codec(s) when I want to play a mp4 video ?
Everything else is just fine.
I'm running FreeBSD as a Desktop with KDE6

 

[Maturin]

Yeah, this wasn't a very helpful post, sorry

I guess you didn't look at the spoiler in my last post.

No.
But we have it here everytime some patch, or minor update occurs:
"!!!!!!!!NOTHING WORKS ANYMORE!!!!!EVERYTHING IS BROKEN!!!!!DON'T DO THE UPDATE!!!!IT KILLS EVERYTHING!!!!!!!!!"

While in 99% of all cases one of the following points turned out to be the reason:
- the update was done before the package repository was finished building
- not running RELEASE
- mix up ports and packages

I'm getting tired of this.
Maybe it's better I leave this forums. (sorry, sometimes I overreact.)

 

[drhowarddrfine]

fwiw, no upgrade issues here either.

 

[mer]

If one runs ZFS, it's kind of trivial to create a new BE, mount it, then do pkg upgrade into it:
bectl create pkgs-Q4
bectl mount pkgs-Q4 /mnt
mount -t devfs devfs /mnt/dev # pkg needs devfs mounted
pkg-static -c /mnt upgrade -f
umount /mnt/dev

That way you can see exactly what will happen, you don't break your working BE, if it looks good, you can activate it and reboot into it.

 

[fjdlr]

Personally, I had no troubles with latest pkg upgrades, but I was posting about similar issue few times before and about my way to mitigate this potential problem, please see

and a few posts bellow quoted post.

14.3-RELEASE-p4; pkg 2.3.1; all looks okay from my POV; \
FreeBSD.conf set to url: ".../$(ABI)/latest"; \
same for kmods

Yes
My alias csh
update pkg upg -n

Or if it's too late
zfs clone [dataset]@[name_snapshot] new BE

 

[scottro]

Also no issues here, save for some expected nvidia ones. By expected I mean when any nvidia package I have is upgraded, I often have to do a port upgrade on nvidia-drm-kmod which pulls in any other nvidia stuff that is needed.

 

[T-Aoki]

For anyone using quarterly repo (default for *-Release), avoid upgrading in early January, April, July and October.

In these timing, new quarterly (*Q1, *Q2, *Q3 and *Q4) branch is created and all pkgs are build with new quarterly (now 2025Q4) and until the build finishes, some of pkgs should be absent and cause deletion on upgrading.

Significant examples are www/chromium, editors/libreoffice, www/ungoogled-chromium, www/iridium and devel/electron*, which all of them are huge.

 

[T-Aoki]

Also no issues here, save for some expected nvidia ones. By expected I mean when any nvidia package I have is upgraded, I often have to do a port upgrade on nvidia-drm-kmod which pulls in any other nvidia stuff that is needed.

It would become better once kmod builder starts properly building them.

The changes for it (split out kmod parts from x11/nvidia-driver* into x11/nvidia-kmod*) is already committed but not being built, and now bapt@ is looking into the reason why.

Fortunately, 14.2-Release is EoL'ed at the end of September and all pkgs on main pkg repo (FreeBSD[-ports]) are built against 14.3 for 14.*.

 

[CShell]

I should have waited, I knew it. When you see a major minor update like this, take your time and press n not y, come back two months later and then press y. or you'll be the guinea big.

Yeah I saw that -- and then I literally looked around for my ZFS book to make sure I had the right ZFS snapshot point installed before I tried that. And in the mean time I did indeed type "n" in pkg !

I am really glad that FreeBSD has a solid ZFS file system that I can go back "in time" to restore what "was". I am starting to feel like a Time Lord.

 

[CShell]

did a fresh install, having had a nicely running 14.1 install prior to this. With 14.3, I immediately encountered lots of gotchas with a basic pkg install. It seems like a hot mess, especially for a minor release.

Yes! This same thing happened to me too and I ended up doing a completely fresh install of 14.3. And even after I did the fresh install of 14.3 it still did not work and I had to manually compile a few packages to get a working GUI and other things.