Bug 472015

Summary: Opening Filelight from Dolphin folder info is not working
Product: [Applications] dolphin Reporter: Henning <boredsquirrel>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: akselmo, kfm-devel
Priority: NOR    
Version First Reported In: 23.04.1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Henning 2023-07-06 20:32:16 UTC
I right click on a folder and see its info. I try to analyze it with Filelight.

It doesnt matter if the folder is through symlinks or not, its the same effect.

qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x55657095e660) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x556570f1da60) According to the xdg-shell protocol, 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 because xdg-shell mandate that child popups close before parents
kf.kio.widgets: Could not find mount point for QUrl("file:///home/user/some/directory")
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
QString::arg: 2 argument(s) missing in org.kde.filelight
F: Not sharing "/usr/share/icons" with sandbox: Path "/usr" is reserved by Flatpak
Error: Invalid fd passed

This is the output I get. Filelight is not opening. Launching it normally and opening that folder works.

Specified App:
dolphin-23.04.2-1.fc38.x86_64
filelight-23.04.2-1.fc38.x86_64

--- Software ---
OS: Fedora Linux 38.20230705.0 (Kinoite)
KDE Plasma: 5.27.6
KDE Frameworks: 5.107.0
Qt: 5.15.10
Kernel: 6.3.8-200.fc38.x86_64
Compositor: wayland

--- Hardware ---
CPU: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx
RAM: 13.5 GB
GPU: AMD Radeon Vega 8 Graphics
Video memory: 2048MB
Comment 1 Akseli Lahtinen 2024-11-26 14:59:33 UTC

*** This bug has been marked as a duplicate of bug 496557 ***