[kde] [Bug 437003] New: xsel "crashes" when run from custom shortcut, but not terminal

[bugzilla_noreply at kde.org]

https://bugs.kde.org/show_bug.cgi?id=437003

            Bug ID: 437003
           Summary: xsel "crashes" when run from custom shortcut, but not
                    terminal
           Product: kde
           Version: unspecified
          Platform: Kubuntu Packages
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: kdebugs at caseyconnor.org
  Target Milestone: ---

SUMMARY

If I run the demo script below in a terminal, it works as expected. If I run it
triggered by a custom shortcut (configured via settings -> Shortcuts -> Custom
Shortcut) it stops after the xsel command and generates no further output.

STEPS TO REPRODUCE

Make this script in /tmp/ and chmod ug+x :

#!/bin/bash
rm /tmp/got_here /tmp/xsel.txt > /dev/null 2>&1
xsel -b > /tmp/xsel.txt 2>&1
touch /tmp/got_here

OBSERVED RESULT

If run from a terminal, /tmp/xsel.txt and /tmp/got_here both appear as
expected.

If you associate a hotkey to this script via System Settings -> Shortcuts ->
Custom Shortcuts -> Edit -> New -> Global Shortcut -> Command/URL (e.g. Action
= "/tmp/myscript") and use the hotkey, you will see that /tmp/xsel.txt appears,
but /tmp/got_here does not appear.

This implies to me that something is crashing, as there is no error output in
xsel.txt?

EXPECTED RESULT

In both cases, /tmp/xsel.txt and /tmp/got_here should appear.

If I substitute xclip in place of xsel, it works as expected: both files
appear.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 21.04 (also happened in 20.10)
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2

I don't see anything obviously awry in journalctl, there is no error in the
stdout or stderr in /tmp/xsel.txt, so this seems to fail "silently" which is
disturbing, and hence I file this bug report.

-- 
You are receiving this mail because:
You are the assignee for the bug.