Dolphin file manager is freezing when right-clicking or viewing the context menu

The Problem:

Any attempt to view the content menu causes the file manager to freeze completely for 5 minutes. This problem started happening after the latest Manjaro update.

What Have I tried So Far?

  • I tried to reset Dolphin completely and return it back to default.
  • I tried to delete all cache files and settings files of Dolphin and even reinstall it from scratch.
  • I tried to disable and delete all plugins that can be installed on top of Dolphin.

System Info:

  • Operating System: Manjaro Linux
  • KDE Plasma Version: 5.24.2
  • KDE Frameworks Version: 5.91.0
  • Qt Version: 5.15.2
  • Kernel Version: 5.16.11-2-MANJARO (64-bit)
  • Graphics Platform: X11
  • Processors: 4 × AMD Ryzen 3 2200G with Radeon Vega Graphics
  • Memory: 15.5 GiB of RAM
  • Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2

Thanks in advance for your help!

Update: I just found that right-clicking on any file on the desktop of KDE also generates the same issue. For example, even after waiting for 3 minutes, I can’t view the properties of any file even after waiting for the context menu to open.

have dolphin open and ready

then open terminal and use command;

journalctl -f

and then proceed to do all things, that reproduce the errors you mentioned, and paste the dump in terminal window here.

Thank you for your reply.

Recording the journal did not produce any new entries after right-clicking and waiting. However, upon issuing the command, I did notice a few error messages in the terminal. I will write the output below:

[kenshiwara@tornado ~]$ journalctl -f
Mar 05 15:23:35 tornado dolphin[11159]: libpng warning: iCCP: known incorrect sRGB profile
Mar 05 15:23:35 tornado kioslave5[11186]: Qt: Session management error: networkIdsList argument is NULL
Mar 05 15:23:41 tornado plasmashell[1424]: kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found
Mar 05 15:23:41 tornado systemd[1278]: Started Konsole - Terminal.
Mar 05 15:23:41 tornado kwin_x11[1346]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 17961, resource id: 14680186, major code: 3 (GetWindowAttributes), minor code: 0
Mar 05 15:23:41 tornado kwin_x11[1346]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 17962, resource id: 14680186, major code: 14 (GetGeometry), minor code: 0
Mar 05 15:23:49 tornado kwin_x11[1346]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 18980, resource id: 73400343, major code: 18 (ChangeProperty), minor code: 0
Mar 05 15:23:49 tornado kwin_x11[1346]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 18984, resource id: 31457453, major code: 18 (ChangeProperty), minor code: 0
Mar 05 15:23:52 tornado kioslave5[11248]: Qt: Session management error: networkIdsList argument is NULL
Mar 05 15:23:54 tornado systemd[1278]: Started Konsole - Terminal.

Update: I have tried the method again but this time, I tried to replicate the issue using the settings panel since it is also freezing when trying to view the custom keyboard shortcuts. The output is as follows:

Mar 05 15:31:29 tornado systemd[1278]: Started System Settings - System Settings.
Mar 05 15:31:30 tornado kwin_x11[1346]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31130, resource id: 14680236, major code:
3 (GetWindowAttributes), minor code: 0         
Mar 05 15:31:30 tornado kwin_x11[1346]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 31131, resource id: 14680236, major cod
e: 14 (GetGeometry), minor code: 0              
Mar 05 15:31:30 tornado systemsettings[11537]: QQmlEngine::setContextForObject(): Object already has a QQmlContext                                
Mar 05 15:31:30 tornado systemsettings[11537]: file:///usr/share/kpackage/kcms/kcm_landingpage/contents/ui/main.qml:130:9: QML FormLayout (parent
or ancestor of QQuickLayoutAttached): Binding loop detected for property "preferredHeight"                                                     
Mar 05 15:31:30 tornado systemsettings[11537]: file:///usr/share/kpackage/kcms/kcm_landingpage/contents/ui/main.qml:20:9: QML FormLayout (parent
or ancestor of QQuickLayoutAttached): Binding loop detected for property "preferredHeight"                                                      
Mar 05 15:31:30 tornado kwin_x11[1346]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31247, resource id: 73400329, major code:
18 (ChangeProperty), minor code: 0             
Mar 05 15:31:59 tornado systemsettings[11537]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
Mar 05 15:31:59 tornado systemsettings[11537]: file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/OverlaySheet.qml:219:38: QML FocusScope: Bindi
ng loop detected for property "contentItemMaximumWidth"                                                                                           
Mar 05 15:31:59 tornado systemsettings[11537]: file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/OverlaySheet.qml:219:38: QML FocusScope: Bindi
ng loop detected for property "contentItemMaximumWidth"                                                                                           
Mar 05 15:31:59 tornado systemsettings[11537]: qml: The item SubCategoryPage_QMLTYPE_109(0x5610b72fe490) is already in the PageRow
Mar 05 15:32:02 tornado systemsettings[11537]: qml: The item SubCategoryPage_QMLTYPE_109(0x5610b72fe490) is already in the PageRow
Mar 05 15:32:53 tornado systemsettings[11537]: Unable to start server org.kde.khotkeys (kded module) [ "org.freedesktop.DBus.Error.NoReply" ]: "D
id not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply,
the reply timeout expired, or the network connection was broken."

Your help will be much appreciated!

I had the exact same problem yesterday and somehow fixed it.

What I did was to remove every kde config files i had from my home directory

and I cleared kcookiejar because i had an error of kded trying to access kcookiejar:

kcookiejar5 --remove-all
(took ~50 sec to execute)

Not quite sure which one did it but I think clearing kcookiejar fixed it for me

After a reboot everything seemed to work fine