Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#66056 - [flameshot] not working on with the latest qt-base package.

Attached to Project: Community Packages
Opened by s3YpwQJEnRGoAURc (s3YpwQJEnRGoAURc) - Wednesday, 01 April 2020, 09:07 GMT
Last edited by Jiachen Yang (farseerfc) - Thursday, 02 April 2020, 01:18 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jiachen Yang (farseerfc)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The flameshot package is not working for me with the latest qt-base package. Nothing happens when I start the application, no error/debug messages in cli.

I tried to install the AUR version of the application: https://aur.archlinux.org/packages/flameshot-git/ that works.
I believe the issue is that the official package is build with an older version of qt. I think a rebuild should resolve this issue.

Additional info:
* package version(s)

flameshot --version
Flameshot v0.6.0
Compiled with Qt 5.12.1

pacman -Q | grep qt5-base
qt5-base 5.14.1-4

Steps to reproduce:

$ flameshot gui
nothing happens.

That should bring up the gui.

Thank you!
This task depends upon

Closed by  Jiachen Yang (farseerfc)
Thursday, 02 April 2020, 01:18 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in 0.6.0-4 as reported
Comment by Jiachen Yang (farseerfc) - Wednesday, 01 April 2020, 16:33 GMT
Sorry, I cannot reproduce this problem on my PCs, tested both qt5-base 5.14.1-4 and qt5-base 5.14.2-1 .

I did backport an unrelated PR, and as a side effect, rebuild the flameshot against the latest qt5.

Can you please test the version flameshot 0.6.0-4 whether that fixed your problem?
Comment by s3YpwQJEnRGoAURc (s3YpwQJEnRGoAURc) - Wednesday, 01 April 2020, 17:56 GMT
That fixed the issue thanks for the quick response!

Loading...