Dolphin auto-quits when checking file properties

Support KDE Plasma
1

Dear Gurus,

TL;DR version:
How to prevent Dolphin from auto-quitting and relaunching, when checking file properties?

Long version:
After the update on 2024.11.30, my Dolphin has been behaving unexpectedly.
When checking file properties, either through right-click menu OR Alt+Return, Dolphin would quit and relaunch, then only it would popup the file properties windows.
This happens only on the 1st time file properties command is executed on a Dolphin windows. The 2nd time, there is no such behaviour.

Normally, Dolphin would just popup the file properties windows without going through the “quit and relaunch” process.

Is there a way to fix this “quit and relaunch” behavior?

Thanks.

2

The problem might have something to do with Graphical interface might not start due to missing libpixbufloader-svg.so noted in the 2024-11-30 update announcement. It apparently caused an issue with Firefox as well, recently.

TL;DR, this was suggested as a quick fix;

sudo gdk-pixbuf-query-loaders --update-cache

In any case, it should do no harm.

3

Tried.
It didn’t work.

I’m frustrated that:
every time KDE bumps up a version, they are bound to break something.

4

Its something local to your system, as there arent any other reports about it.
For my part … I cant recall the last time dolphin crashed. It certainly does not now opening properties.

Tried with a different user account?

If it does not happen there then its an issue in your HOME, such as the dolphin configuration, ex, ~/.config/dolphinrc.

5

Hi,
I have the same thing: when i check properties of a directory, dolphin closes and reopens instantaneously. It occurs only once; when i check another directory, it’s ok.

6

I just tried checking a directory’s properties and the same thing happened - Dolphin disappeared for a split second and then reappeared with the properties window displayed.

I don’t think Dolphin is actually closing, as all of my open tabs were retained. I think the window manager might be “hiding” Dolphin for a moment.

Running Dolphin from a terminal, the following error message was displayed. However, it did not display each time the issue occurred, so it may be unrelated to the issue:

qt.qpa.wayland: Creating a popup with a parent, QWidgetWindow(0x653b201d25c0, name=“Dolphin#1Window”) which does not match the current topmost grabbing popup, QWidgetWindow(0x653b207afa70, name=“DolphinContextMenuClassWindow”) With some shell surface protocols, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly. Please fix the transient parent of the popup.

A look in my system log showed only the following kwin_wayland warning occurring 3 times in a row when the issue with the directory properties occurred:

kwin_core: Cannot grant a token to KWin::ClientConnection(0x605ffeb12f10)

Interestingly, the next time I tried opening the directory properties from the same Dolphin session, it did not disappear for a moment, and the above warning was only displayed twice.

I don’t think Dolphin is actually crashing. When I ran it from a terminal, there was no indication that Dolphin had closed or crashed. It seems to possibly be an issue with kwin redrawing Dolphin when the directory properties window is opened.

2 Likes
7

Just tested with X11 and Wayland - cannot replicate.

 $ dolphin -v
dolphin 24.08.3

General Plasma and kernel info

Operating System: Manjaro Linux 
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.12.4-1-MANJARO (64-bit)
Graphics Platform: Wayland
8

Just tested here and indeed the Dolphin window disappears briefly. First time I’ve noticed that happen.

Same specs as listed by @linux-aarhus (except kernel is 6.12.1-4 in my case).

9

:thinking:

If it is not version related - the only other component with a possible impact is GPU.

The tested system of mine is running AMD graphics.

10

My info:

Dolphin Version 24.08.3
Operating System: Manjaro Linux
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.12.1-4-MANJARO (64-bit)
Graphics Platform: X11

Yup, same here.

I think so too - all my tabs within same Dolphin windows still retained after auto re-launched.

I have multiple Dolphin windows opened - but only the windows which I run the File Properties command will auto-quit and re-launch.
So I dun think the app crashed.

If this info helps in identifying the cause, I’m using:

Graphics Processor: AMD Radeon Graphics

A little details on how the incident behaves:

  1. The auto-quit will happen, no matter how many Dolphin window is opened. It can happen even in a freshly rebooted PC, with only 1 Dolphin window launched.
  2. It only happen once per window. On the same window, it will not happen the 2nd time. But for every window, this will happen once.
  3. If I have multiple Dolphin windows opened, let’s say Dolphin windows A, B, C, D (the order in Task Manager) - when B auto-quits and relaunches, the order of the Dolphin windows will re-arrange - now becoming A, C, D, B.
1 Like
11

Since your environment is fairly identical to mine and I cannot reproduce it - the only explanation left, is a local issue.

Test if you can replicate using a secondary user.

12

Not AMD for me, it’s Intel.

13

I just did a search for “dolphin properties” on KDE’s Bug List. Several bugs have already been logged:

Comment #4 in the last of those bug reports says removal of the kdenetwork-filesharing package fixes the issue.

I uninstalled kdenetwork-filesharing (it is Dolphin’s Samba Filesharing Plugin, and not a required dependency). After restarting Dolphin, the issue no longer occurs.

3 Likes
14

This plugin is essential for Samba to work?
If so, I have no luck but to wait for an official fix…

15

Nope, it uses samba.
The package provides the ‘Sharing’ tab present in the properties dialog.

1 Like