Run xfce4-screenshooter -fdc 1. Paste e.g. into a GitHub comment. Expected behaviour: it pastes a fullscreen image, as it does with xfce4-screenshooter -fd 1, select copy. Actual behaviour: it doesn't paste anything. ```bash [jray@jr-dl ~]$ inxi -Fxz System: Host: jr-dl Kernel: 4.19.13-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: N/A Distro: Manjaro Linux Machine: Type: Laptop System: Dell product: Latitude E6410 v: 0001 serial: <filter> Mobo: Dell model: 0HNGW4 serial: <filter> UEFI: Dell v: A16 date: 12/05/2013 Battery: ID-1: BAT0 charge: 39.6 Wh condition: 39.6/48.8 Wh (81%) model: Samsung SDI DELL PT43699 status: Full CPU: Topology: Dual Core model: Intel Core i5 M 560 bits: 64 type: MT MCP arch: Nehalem rev: 5 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21290 Speed: 1335 MHz min/max: 1199/2667 MHz Core speeds (MHz): 1: 1487 2: 1405 3: 1339 4: 1409 Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Dell Latitude E6410 driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: intel unloaded: modesetting resolution: 1440x900~60Hz, 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 18.3.1 direct render: Yes Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Dell Latitude E6410 driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.19.13-1-MANJARO Network: Device-1: Intel 82577LM Gigabit Network vendor: Dell Latitude E6410 driver: e1000e v: 3.2.6-k port: 7040 bus ID: 00:19.0 IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: Broadcom and subsidiaries BCM43224 802.11a/b/g/n vendor: Dell Wireless 1520 Half-size Mini PCIe Card driver: wl v: kernel port: 7000 bus ID: 02:00.0 IF: wlp2s0 state: down mac: <filter> Drives: Local Storage: total: 1.20 TiB used: 142.38 GiB (11.6%) ID-1: /dev/sda vendor: Seagate model: ST9320423AS size: 298.09 GiB ID-2: /dev/sdb type: USB vendor: Seagate model: Expansion size: 931.51 GiB Partition: ID-1: / size: 284.06 GiB used: 10.83 GiB (3.8%) fs: ext4 dev: /dev/sda2 ID-2: /home size: 622.48 GiB used: 91.96 GiB (14.8%) fs: ext4 dev: /dev/sdb1 ID-3: swap-1 size: 8.18 GiB used: 587.5 MiB (7.0%) fs: swap dev: /dev/sda3 Sensors: System Temperatures: cpu: 52.0 C mobo: N/A sodimm: 48.0 C Fan Speeds (RPM): cpu: 4311 Info: Processes: 192 Uptime: 7h 33m Memory: 3.72 GiB used: 2.16 GiB (58.1%) Init: systemd Compilers: gcc: 8.2.1 Shell: bash v: 4.4.23 inxi: 3.0.28 ``` I have two screens.
Works for me, probably it is the same problem as reported in Bug #13342. Try "xfce4-screenshooter -wdc 1" instead, if you can paste the screenshot, then it should be indeed that issue with xfsettingsd.
Yes, I'd already tried that, it works.
Ok, if you could try /usr/lib/gnome-settings-daemon/gsd-clipboard instead of xfsettingsd, we would be sure if this is a screenshooter bug or not. For more details, see Bug #13537.
OK I read #13537, but I'm not exactly sure what to do: ```bash [jray@jr-dl media]$ /usr/lib/gnome-settings-daemon/gsd-clipboard bash: /usr/lib/gnome-settings-daemon/gsd-clipboard: No such file or directory [jray@jr-dl media]$ yay gsd-clipboard No packages match search ``` Kernel: 4.20.1-1-MANJARO x86_64
You need first to install gnome-settings-daemon, which provides gsd-clipboard. Then run: pkill xfsettingsd /usr/lib/gsd-clipboard # yeah, the path has changed Now you may repeat the steps to reproduce the bug. After that you can finish and uninstall gsd-clipboard and run xfsettingsd again.
I have the same issue with the latest git (2019-04-21). My command is: ./src/xfce4-screenshooter --clipboard --fullscreen --delay=0 Or ./src/xfce4-screenshooter -c -f Althought I'm not sure this is an xfce4-screenshooter bug. It may be a clipboard bug.
Sorry, cannot check it with gnome-settings-daemon, Slackware is not too friendly to GNOME, and I'd have to install too many dependencies.
I just pushed the fix for Bug #13537, can you guys confirm if xfce4-settings from git master works for you?
Can you try with xfce4-settings 4.14.1?
I'm closing because it's very likely to fixed by that version of xfce4-settings, reopen if not.
I'll test it when xfce 4.14 lands into Slackware-current