[Spectacle] [Bug 447140] Does not automatically copy in clipboard on wayland under certain circumstances

2021-12-27 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=447140

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||22.04
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 447140] Does not automatically copy in clipboard on wayland under certain circumstances

2021-12-18 Thread Méven Car
https://bugs.kde.org/show_bug.cgi?id=447140

--- Comment #3 from Méven Car  ---
(In reply to Nate Graham from comment #1)
> This was supposed to be fixed in Bug 421974 and it's currently working for
> me.

My bad this is properly fixed only for spectacle 22.06 with KF 5.89

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 447140] Does not automatically copy in clipboard on wayland under certain circumstances

2021-12-17 Thread d3coder
https://bugs.kde.org/show_bug.cgi?id=447140

--- Comment #2 from d3coder  ---
Do you see spectacle window appear after you make a screenshot? It shouldn't
appear after the screenshot.
Try to:
1. Run wayland
2. Make sure "copy to clipboard" is enabled in spectacle
3. Reboot or killall spectacle if you started it before or made a screenshot
4. Make a screenshot with a hotkey

What should happen:
1. Spectacle window should not appear
2. Screenshot must be in a clipboard

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 447140] Does not automatically copy in clipboard on wayland under certain circumstances

2021-12-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=447140

Nate Graham  changed:

   What|Removed |Added

Summary|Does not automatically copy |Does not automatically copy
   |in clipboard on wayland |in clipboard on wayland
   ||under certain circumstances
   Keywords||wayland
 CC||meve...@gmail.com,
   ||n...@kde.org

--- Comment #1 from Nate Graham  ---
This was supposed to be fixed in Bug 421974 and it's currently working for me.

-- 
You are receiving this mail because:
You are watching all bug changes.