[dolphin] [Bug 472015] New: Opening Filelight on Folder info not working
Henning
bugzilla_noreply at kde.org
Thu Jul 6 21:32:16 BST 2023
https://bugs.kde.org/show_bug.cgi?id=472015
Bug ID: 472015
Summary: Opening Filelight on Folder info not working
Classification: Applications
Product: dolphin
Version: 23.04.1
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-null at kde.org
Reporter: amanita+KDEBUGS at mailbox.org
CC: kfm-devel at kde.org
Target Milestone: ---
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
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list