F39 release upgrade not installing new default apps


I upgraded to f39 yesterday. The upgrade itself went smoothly, but I noticed something as I started to go through some online videos explaining some new features in this release.

The upgrade itself did not install any of the new default apps, e.g. loupe (a substitution for Eye of GNOME), nor the new Camera app (which is supposed to replace Cheese, although I tried a fresh f39 image in a vm and it still used Cheese, so this point might be moot).

I also noticed that my terminal was missing the bash-color-promptpackage, which is supposed to be the new default in f39.

I just wanted to ask whether this is normal for a release upgrade, and I just need to always keep up-to-date on what new default packages are being introduced, manually replace them, and always check what my upgrade might have missed?

On my upgraded f39 system I see bash-color-prompt is installed.
But becuase I have control of my .bashrc and .bash_profile its not taking effect.

This line checks for the user setting the PS1 and does not override that choice.

$ more /etc/profile.d/bash-color-prompt.sh
# only set for color terminals and if PS1 unchanged
if [ "$PS1" = "[\u@\h \W]\\$ " -a "${TERM: -5}" = "color" -o -n "${prompt_color_force}" ]; then

I do not know about the other app choices.

Thank you for your response. It works on my system once I install the actual package, but it was just missing upon my initial upgrade so there was no /etc/profile.d/bash-color-prompt.sh

it just feels weird that one would need to look for missing packages after an upgrade. I just came upon it while watching the latest DJ Ware video and found the name of the package in this topic: Fedora 39 bash prompt now displays exit codes - #2 by chrisawi

Thank you for your time though, I appreciate it.

Say you removed some packages and installed others. What do you expect an upgrade to do? Most users would want the upgrade to respect and preserve their choices as much as possible.

Note that you can always (re)install complete groups if you want to get everything which is (now) in a group such as GNOME Desktop Environment or Basic Desktop.

Alternatively, separate system and user data and do a new install instead of an upgrade to get the shiny new default :slight_smile:

1 Like

No need to replace them. Just install new packages and try them first. “Gedit” (for example) is no more default but it has more features than it’s replacement “Text Editor”.

Also, from this response:

1 Like

As noted, the upgrade tries to respect the users already existing configs. It generally does not install apps or packages that are not already existing. A new clean install would install the defaults, but an upgrade mostly just upgrades the existing system as-is.

1 Like

Does sudo dnf group upgrade 'Fedora Workstation' do anything?

From what I can tell dnf system-upgrade has done something comparable since around F33. Did you use that or GNOME Software to upgrade?


This was exactly my first thought. Thank you.

I used GNOME Software. I tried the group update in a fedora vm at work and it worked. It installed the missing bash-color-prompt package, along with others so I really appreciate it. Once I get home, I will try it on my actual machine and mark the solution. Thank you.

edit 2:

This is the way. It installs all the missing packages. Thank you very much.

@alan-jelaska , @mjg @computersavvy

Thank you. Of course that makes sense. I guess I was more concerned about the missing package/packages.

I will keep that in mind.

Yes, I think this might be a good alternative moving forward. Thank you again.

That is not how macOS upgrades work. My settings are in ~/Library and are not changed on an upgrade. The apps like Pages are updated via the app store, not OS upgrades.

Thank you everyone. The immediate solution has been marked.

Just taking this opportunity to evangelize Silverblue and other rpm-ostree variants as an additional alternative. This “problem” of package drift is exactly one of the things rpm-ostree was designed to address. Great read here (specifically the Image Based Updates section):

1 Like

Hum, somebody else reported the same. I do wonder if GNOME Software doesn’t hit the path where we try to install new packages from installed groups on upgrade. I’ll have to take a look and see where exactly that code is and whether g-s should be hitting it.

See https://gitlab.gnome.org/GNOME/gnome-software/-/issues/2383#note_1919184 (again)

I never did file a bug against PackageKit. I’m still not totally clear how the DNF5 transition will affect GNOME Software:

I filed a PK issue. dnf: refresh group packages on system upgrade · Issue #708 · PackageKit/PackageKit · GitHub