Kexi no longer opens after kde neon upgrade

After upgrading my KDE Neon system, Kexi no longer opens. Something about not being able to find breeze-icons:
Here’s the error message:
“Tried to find in /usr/bin/data/icons/breeze, /home/waynevid/.local/share/icons/breeze, /home/waynevid/.local/share/flatpak/exports/share/icons/breeze, /var/lib/flatpak/exports/share/icons/breeze, /usr/local/share/icons/breeze, /usr/share/icons/breeze, /var/lib/snapd/desktop/icons/breeze, /home/waynevid/.local/bin/data/icons/breeze, /usr/local/sbin/data/icons/breeze, /usr/local/bin/data/icons/breeze, /usr/sbin/data/icons/breeze, /usr/bin/data/icons/breeze, /sbin/data/icons/breeze, /bin/data/icons/breeze, /usr/games/data/icons/breeze, /usr/local/games/data/icons/breeze, and /snap/bin/data/icons/breeze.”
Any help would be appreciated.

The paths with bin/data are very suspicious - I’ve never heard about this kind of path before.

Breeze icons are installed in /usr/share/icons/breeze, or sometimes - when you install in your local home folder, something like ~/.local/share/icons/breeze (which we can see listed somewhere in that list, though it is very obvious that you don’t have Breeze icons installed in your home folder).

I have not used Kexi in a long while, but I tried to install it in my current Neon and I can reproduce the problem, but specifically the error message starts with:

Could not open icon resource file ‘breeze-icons.rcc’.

Which I think is the most pertinent part. The breeze-icons.rcc was supposed to come from the package breeze-icon-theme-rcc, but that package has apparently not been ported to KF6, and does not at the moment provide that file. The description for the package says “Empty transitional package”.

A transitional package is a dummy package that matches a name that older software expects but the content that it was supposed to provide had been moved to another package that the transitional package will force to be installed instead. breeze-icon-theme-rcc installs kf6-breeze-icon-theme as its “replacement”, but that package does not contain the breeze-icons.rcc file. I’m not sure what that file was supposed to do - but it is no longer available in Plasma 6.

The conclusion is that Kexi cannot be made to work in a Plasma 6 environment, at the moment, and it should be ported to Plasma 6. Looking at the Kexi git repository - there doesn’t seem to be a lot of work going into that application: aside from bots committing translation updates, the last person to do anything was @carl with some minor commits that look like fixing compilation issues. I don’t think anyone is planning to fixed Kexi for Plasma 6 anytime soon, sorry :frowning:

Thanks for your help. Guess I’ll have to go back to Plasma 5.

For what it’s worth, I tried KEXI on Plasma 5 about a year ago to test an icon theme I was developing. It shipped with its own icons (taken from Breeze) and did not follow the active icon theme. Krita does the same thing, annoyingly enough. I didn’t check where KEXI installed its icons, hut something like /bin/data/ certainly sounds plausible.

Another option, other than giving up on Plasma 6 entirely, is to use Distrobox to run a Kubuntu 22.04 box (that has Plasma 5.27) and run Kexi from that - so everything is Plasma 6 and Kexi runs from what it thinks is Plasma 5.27. I tested it and it runs well (also, no /bin/data paths anywhere in there - I think its just a bug in the Kexi build system somewhere). Here’s how to do it:

  1. Install distrobox if you don’t have it already.
  2. In your terminal, run distrobox create --name kubuntu-jammy --image ubuntu:22.04 (or give it some other name).
  3. Open the application launcher (main menu) and search for “kubuntu-jammy” - you should see a launcher for “Terminal entering Kubuntu-jammy”, run that. It will open a terminal and will do some setup that’ll take about a minute.
  4. In the new terminal run sudo apt update then sudo apt install kexi. After that is done you can close the terminal.
  5. Right click your application launcher icon in the panel and choose “Edit applications”.
    image
  6. In the KDE Menu Editor that opens select the category where you want to put in Kexi - for example “Office”, right click it and select “New Item”. In the dialog box that opens, give that new item a name - possibly “Kexi”.
  7. The right side of the editor, put in: For “Program”: distrobox; for “Command-Line Arguments”: enter kubuntu-jammy -- kexi-3.2 (or whatever other name you used in “create” for the second parameter). You can also set an icon that will make sense to you, and click the “Save” button:

Now you can open the application launcher and run Kexi and it should appears in all its Plasma 5 glory, and you don’t have to give up on the great new stuff in Plasma 6 :smile:

Hi guss77,

Tried to follow your instructions but couldn’t get past step #2. Couldn’t find “Terminal entering Kubuntu-jammy” in the application launcher. Any clues?

Waynevid

Distrobox is supposed to populate the application launcher with links to the distroboxes. It may be misconfigured configured for your system, the cache takes time to update or any number of reasons.

You can just use a regular terminal to enter the distrbox, for example by running distrobox enter kubuntu-jammy.

This is what I get when I enter distrobox enter kubuntu-jammy in the terminal:

permission denied while trying to connect to the Docker daemon socket at … (won’t allow me to include links in this reply)

Thanks anyway.
Waynevid

Distrobox requires either docker or podman to run. By default, if you had neither installed and you try to install Distrobox, it should install podman because it is easier to use - docker requires some non-trivial setup to work, which is what you’d hit your head against here.

I’m not sure why you have docker installed if it isn’t setup properly to be used, and that may also explain why creating the distrobox didn’t put the launcher for it in the menu. I recommend you remove any existing distroboxes you have created by listing them - distrobox ls - then removing each by name - distrobox rm kubuntu-jammy - then install podman and remove docker:

sudo apt install podman && sudo apt purge docker.io

After that try to start the process again from the distrobox create stage.

Thanks, guss77.
It worked. I’m back on Kexi again.
I really appreciate your help.

Waynevid

BTW, how does one handle updates(kubuntu, kexi, etc.) on distrobox?

You’d need to run the updates manually from time to time - either on the command line or install Discover or Synaptic in the distrobox and run them to do the updates.

But generally, I wouldn’t worry about it too much - its a small container that you use to run one single program, that doesn’t even connect to the internet. The security considerations here are negligible.

How does one install fonts in distrobox?

Waynevid

The distrobox mounts your home directory, so any user configuration - like user installed fonts - can be seen by applications inside the distrobox.

To install fonts into your user fonts, find the font files and double click them, then in the dialog that opens choose “Personal”.