https://bugs.kde.org/show_bug.cgi?id=502217
--- Comment #3 from Julian Pollak <bugs.kde.org.distress...@passmail.net> --- So I tried to create a coredump for kscreen by pressing the keybind. This gets me these lines with journalctl -b 0 | grep kscreen: Mar 31 21:39:29 ppocket-msi dbus-broker-launch[861]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'. Mar 31 21:39:38 ppocket-msi dbus-broker-launch[1061]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'. Apr 01 00:11:47 ppocket-msi systemd[983]: app-org.kde.kscreen@62afff6826db4c5fb8099df9cd5559ed.service: Main process exited, code=exited, status=1/FAILURE Apr 01 00:11:47 ppocket-msi systemd[983]: app-org.kde.kscreen@62afff6826db4c5fb8099df9cd5559ed.service: Failed with result 'exit-code'. 21:39 is when the machine booted, 00:11 is when I pressed the keybind. But this doesn't result in any coredumps I can see with coredumpctl. I am a software developer but I am not at all familiar with D-BUS. I tried attaching to kscreen_osd_service. But that doesn't show me anything at all. I tried running org.kde.kscreen with gdb-attached plasmawindowed as described in the docs. But that one isn't the problem, it works fine. Is there a way to invoke the OSD with a command instead of D-BUS? -- You are receiving this mail because: You are watching all bug changes.
