Can't open Dolphin in super user mode because of missing packages

Hello,
I recently “upgraded” from Leap 15.6 to Tumbleweed but had to reinstall everything because I apparently messed up the upgrade process and borked my system.

After reinstalling everything from a fresh USB I was going through the process of reinstalling the various packages and programs I need but I found a curious issue: Dolphin doesn’t want to open in super user mode, it asks for the password but then it doesn’t open at all.

After trying to access it through the console it gives me this error:

costanzo@localhost:~> sudo dolphin
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, xcb, wayland-egl, wayland.

Aborted

How much should I be concerned? Did I mess up the install somehow? The only thing I did was to import the user configuration from the previous install.
I guess that a solution could be to install one of the available plugins but I’m making this post mainly to ask if this is a symptom of a greater problem or if it is “expected behaviour” from Tumbleweed.

Many thanks.

I am not using Tumbleweed, but I can imagine that people want to know:

  • which Tumbleweed snapshot was on the USB you installed from?
  • if you did a zypper dup after installation to be sure your are up-to-date?

BTW, it is normal to get that could not connect to display when you start it the way you do.
I suggest you use kdesu dolphin instead.

1 Like

Don’t remember which version I installed but I did it last week and it was a fresh download, I did a zypper dup a couple days after and right now I’m on version 20240905.

Using kdesu dolphin opens the application correctly.

So we are now at the point where starting it from konsole with kdesu dolphin opens correct and clicking on the “File Manager in superuser mode” item of the main menu does not?

1 Like

@KekkusMaximus:

First, welcome to the openSUSE Forums.


In general, when using openSUSE, the first thing to do when something unexpected happens is →

# zypper verify

and, then →

# rpm --verify --all


Trust the RPM dependencies – they are there for a very good reason …

Yes, the situation is as you described (have to be verbose or else it wouldn’t let me answer)

Thank you,

Here is the output of those commands:

costanzo@localhost:~> sudo zypper verify
[sudo] password for root: 
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Dependencies of all installed packages are satisfied.
costanzo@localhost:~> sudo rpm --verify --all
.M.......  g /var/log/alternatives.log
.M.......  g /run/netns
.M.......  g /etc/xml/catalog-d.xml
....L....  d /usr/share/man/man1/ctags.1.gz
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
.M.......  g /var/lib/power-profiles-daemon
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
......G.P    /usr/bin/newgidmap
......G.P    /usr/bin/newuidmap
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
....L....  d /usr/share/man/man1/ftp.1.gz
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
.M.......  g /var/lib/wtmpdb
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
.M.......  g /var/adm/update-messages/mariadb-11.4.2-2.1-something
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
.M.......  g /run/ostree
WARNING: `chkstat` has been renamed to `permctl`.
.M.......  g /run/mcelog
S.5....T.  c /etc/speech-dispatcher/speechd.conf
.......T.  c /etc/chrony.d/pool.conf
.M.......  g /var/lib/chrony/drift
.M.......    /var/lib/bluetooth
.M.......  g /run/avahi-daemon
.M.......  g /etc/aliases.lmdb
S.5....T.  c /etc/postfix/main.cf
S.5....T.  c /etc/postfix/master.cf
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
S.5....T.  c /etc/fonts/conf.d/10-rendering-options.conf
S.5....T.  c /etc/fonts/conf.d/58-family-prefer-local.conf
.M.......  g /usr/share/fonts/misc/encodings.dir
.M.......  g /usr/share/fonts/misc/fonts.scale
.......T.  c /etc/pki/nssdb/pkcs11.txt
......G..    /etc/cups/ssl
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
WARNING: `chkstat` has been renamed to `permctl`.
.M.......  g /var/cache/PackageKit
.M.......  g /usr/share/fonts/Type1/encodings.dir
.M.......  g /usr/share/fonts/cyrillic/encodings.dir
.M.......  g /usr/share/fonts/cyrillic/fonts.scale
.M.......  g /usr/share/fonts/truetype/encodings.dir
.M.......  g /usr/share/fonts/100dpi/encodings.dir
.M.......  g /usr/share/fonts/100dpi/fonts.scale
.M.......  g /usr/share/fonts/75dpi/encodings.dir
.M.......  g /usr/share/fonts/75dpi/fonts.scale
.M.......  g /var/lib/flatpak
S.5....T.  c /etc/default/grub
.M.......  g /var/lib/plymouth/boot-duration
.M.......  g /var/log/boot.log
.M.......  g /run/media
WARNING: `chkstat` has been renamed to `permctl`.
........P    /usr/libexec/ksysguard/ksgrd_network_helper
WARNING: `chkstat` has been renamed to `permctl`.
missing     /usr/lib64/libreoffice/program/intro-highres.png
missing     /usr/lib64/libreoffice/program/shell/logo.svg
missing     /usr/lib64/libreoffice/program/shell/logo_inverted.svg
WARNING: `chkstat` has been renamed to `permctl`.
.M.......  g /etc/zypp/services.d/openSUSE.service
.M.......  g /etc/zypp/services.d/openSUSE.service
S.5....T.  c /usr/lib/dracut/dracut.conf.d/60-nvidia-default.conf
S.5....T.  c /usr/lib/modprobe.d/50-nvidia-default.conf
.......T.    /usr/lib64/xorg/modules/drivers/nvidia_drv.so
..5....T.    /var/lib/nordvpn/data/countries.dat
S.5....T.    /var/lib/nordvpn/data/insights.dat
S.5....T.    /var/lib/nordvpn/data/servers.dat

Did I bork something by importing the user configuration from Leap 15.6?

That is not impossible and something that came to my mind.
You probably either kept /home by it being a separate file system and re-using it, or by restoring everything from a backup. That is not a bad idea, but deep inside configuration ad or cache file something could pester you.

You could try to remove ~/.local/dolphin/ (of course of the users that has the problem).

Probably not the user configuration → your Desktop Environment should have migrated everything correctly from the Leap 15.6 version to the Tumbleweed version …


The “chkstat” issue « here on Leap 15.6 … » –

 > which -a chkstat
/usr/bin/chkstat
 > file /usr/bin/chkstat
/usr/bin/chkstat: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=314cbcf55800c702712bf44452ffd05832ce0eb1, for GNU/Linux 3.2.0, stripped
 > rpm --query --whatprovides /usr/bin/chkstat
permissions-20240826-150600.10.9.1.x86_64
 >

It seems that Tumbleweed has an RPM version which isn’t quite compatible with the “chkstat” versus “permctl” conflict – maybe a future upgrade will resolve this conflict.


System configuration

Please be aware that, after performing a major system upgrade – which is what the upgrade from Leap to Tumbleweed is – it is compulsory that →

# rpmconfigcheck

be executed.

  • If this isn’t performed as part of the upgrade workflow, the system configuration will be not compatible with the new system version.
    The affected system may appear to be executing, as in limping along, but, not quite as it should do … :imp:

The thing is that the configuration I have now is not technically an upgrade from Leap to Tumbleweed since when I tried to upgrade it didn’t work and so I had to do a clean install of Tumbleweed from a fresh USB like I said in the beginning. The only thing I ported over from the old install was the user configuration during the installation process.
Anyway, I did the rpmconfigcheck and the output is this:

costanzo@localhost:~> sudo rpmconfigcheck
[sudo] password for root: 
Searching for unresolved configuration files
costanzo@localhost:~> 

So I don’t think that’s the issue. Still don’t know why I have permctl instead of chkstat tho.

I already removed and reinstalled dolphin through konsole but it didn’t do anything to solve this issue.

Sorry, but that is not what I suggested. uninstalling an application does not remove anything from the user, only from the system. And installing does not create anything in the users environment (except that it indirect can create new entries in the main menu)

UWhen the user uses an application for the first time (and that is most eminent with a desktop environment, many files are then created (and later maintained when configurations changes are done by the user) in e.g. ~/.local, ~/.config, ~/.mozilla, etc. But, I repeat, these rae not removed when the application package(s) are uninstalled

Also, newer versions of an application, when executed for the first time by a user, can adapt the existing files to something the new version likes (that is something that will/can not be done going back to an older version of the application).

So removing and installing is something from the MS Windows school of living and will almost never change anything in Linux.

Ok, I deleted ~/.local/dolphin and ~/.config/dolphinrc but it didn’t change the unusual behaviour.

OK, you could have a look at how the menu entry is configured.

Go to the menu entry “File manager in superuser mode” and Right-Click on it. From the context menu choose “Edit Application …”. From the window that opens the contents click the Tab “Application”. Now the fields “Program” and “Arguments” are important. What are they.

Please take into account that I am still on Leap 15.5 with Plasma 5, thus things here can differ from what you see.

After right clicking on “File manager in superuser mode” it closes the menu but doesn’t do anything else. I see a dolphin icon appear in the task bar for a brief moment but it goes away almost instantly.

Looking at the systemd journal from Yast it doesn’t say anything relevant about it, the only recent log regarding kde is this:

dh=Display_Handle[i2c-4: fd=38], Replacing adjusted sleep multiplier 0.20 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS

But honestly it doesn’t seem to be relevant at all.

The Program section says dbus-launch.
The Arguments section says dolphin -qwindowtitle %c %u.

I had to go through the app launcher to see those settings. Trying to open from the app launcher doesn’t do anything like trying to do so from the context menu.

Anyway, I tried doing a fresh install again, this time without importing anything and making sure that the drive was completely wiped clean. I still have this issue.

Same as here on Leap 15.5.

I tried it (I never use it), but it works as expected: pop-up window for root password and then Dolphin.

Maybe someone on Leap 15.6 who uses it can jump in and tell us what there is on that system.

You mean you started with en fresh (empty) home directory of that user?

What happens, if you start
/usr/share/applications/org.kde.dolphinsu.desktop
?

If I start /usr/share/applications/org.kde.dolphinsu.desktop a prompt for the administrator password opens up but after filling in the password it doesn’t do anything.

Again, if I use the command kdesu dolphin from konsole it opens correctly

Yes, I completely wiped the drive and did a clean install so this issue appears also with a fresh home directory.