Bug 1753673 - Strange screen when you capture your screen with flameshot
Summary: Strange screen when you capture your screen with flameshot
Keywords:
Status: CLOSED DUPLICATE of bug 1643327
Alias: None
Product: Fedora
Classification: Fedora
Component: flameshot
Version: 31
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Vitaly
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-19 14:57 UTC by Héctor Louzao
Modified: 2019-09-21 16:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-21 16:43:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
screen (1.57 MB, image/png)
2019-09-19 14:57 UTC, Héctor Louzao 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github lupoDharkael flameshot issues 446 0 None None None 2019-09-20 13:26:44 UTC

Description Héctor Louzao 2019-09-19 14:57:32 UTC 
Created attachment 1616773 [details]
screen

Description of problem:

I've update from fedora 30 to 31 via DNF, no problem in 30

I've found two problem...

1.- Strange screen when you capture screen with flameshot
2.- doesn't show in TopIcons+

Version-Release number of selected component (if applicable):

flameshot-0.6.0-4.fc31.x86_64

How reproducible:

Always

Steps to Reproduce:

1. add to start application in gnome-tweaks
1. doesn't show in topicon+
2. Open a terminal and start with sudo flameshot
3. 

Actual results:

strange screnn

Expected results:

Capture the screen without problem

Additional info:
Comment 1 Vitaly 2019-09-20 13:26:44 UTC 
> Strange screen when you capture screen with flameshot

Known Wayland issue. Flameshot 0.6.0 currently does not support native Wayland Screenshot API. Upstream know about this issue: https://github.com/lupoDharkael/flameshot/issues/446

> doesn't show in TopIcons+

Replace this extension to AppIndicator.
Comment 2 Vitaly 2019-09-21 16:43:12 UTC 

*** This bug has been marked as a duplicate of bug 1643327 ***
Note You need to log in before you can comment on or make changes to this bug.