https://bugs.kde.org/show_bug.cgi?id=426989
Bug ID: 426989
Summary: Dolphin crashes when launched via Steam
Product: dolphin
Version: 19.12.3
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: maqo31...@posteo.de
CC: kfm-de...@kde.org
Target Milestone: ---
SUMMARY
When I open a new Dolphin instance via Steam to browse local game files, this
instance does become unresponsive and needs to be terminated when I choose to
right click to open the right click menu or press F4 to open an attached
terminal. This behavior is limited to instances launched via Steam. If I have
already a running Dolphin instance and Steam only opens a new tab in this
instance, this bug does not occur. If I open a Dolphin instance via the desktop
GUI and navigate there by hand, this bug does also not occur. I can not say
that this bug only appears in conjunction with Steam but I've only noticed it
there (yet).
component: "general" because I don't know how to decide
STEPS TO REPRODUCE
1. open Steam library
2. right click on any game in collection -> properties
3. "Local files" tab -> Browse local files (this will open Dolphin)
4a. try to open right click menu or
4b. try to open terminal (F4)
OBSERVED RESULT
"dolphin" is not responding, process needs to be terminated
EXPECTED RESULT
dolphin does not crash just because
SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: Kubuntu 20.04
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
ADDITIONAL INFORMATION
Kernel Version: 5.4.0-48-generic
OS Type: 64-bit
Processors: 12x AMD Ryzen 5 3600 6-Core Processor
Memory: 31.4 GiB of RAM
I cannot install "kdelibs5-dbg" (E: Unable to locate package kdelibs5-dbg)
otherwise I would have tried to attach a proper crash dump (following
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29).
The official documentation seems to be out-of-date
--
You are receiving this mail because:
You are watching all bug changes.
