Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filename format defaults to BMP #3695

Open
dsoprea opened this issue Aug 23, 2024 · 9 comments
Open

Filename format defaults to BMP #3695

dsoprea opened this issue Aug 23, 2024 · 9 comments
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.

Comments

@dsoprea
Copy link

dsoprea commented Aug 23, 2024

Flameshot Version

flameshot-12.1.0-3

Installation Type

Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)

Operating System type and version

Manjaro, Mate

Description

As of a couple of months ago, the save dialog now defaults to BMP. All I'm doing is calling /usr/bin/flameshot gui. I've reinstalled it to no effect. It's driving me crazy. Any suggestions? It's installed via Pacman.

Steps to reproduce

No response

Screenshots or screen recordings

image

System Information

Manjaro, Mate, Xorg

@dsoprea dsoprea added the Unconfirmed Bug The bug is not confirmed by anyone else. label Aug 23, 2024
@mmahmoudian
Copy link
Member

Would you please provide your config file (~/.config/flameshot/flameshot.ini)

@mmahmoudian mmahmoudian added the Waiting For Info Addressing the issue or merging the PR is halted and we are waiting for more info to be provided. label Aug 23, 2024
@dsoprea
Copy link
Author

dsoprea commented Aug 23, 2024

$ cat ~/.config/flameshot/flameshot.ini
[General]
contrastOpacity=188
drawColor=#800080
filenamePattern=%Y%m%d-%I%M%S
savePath=/home/dustin/Pictures/2024/Screenshots
startupLaunch=true

@mmahmoudian
Copy link
Member

it is interesting that your config file does not contain the following. Just add it to the end of the [General] section and you will be good to go:

[General]
saveAsFileExtension=png

If you want to dive into the config (although you can do all this via the flameshot config, checkout this example file:

https://github.com/flameshot-org/flameshot/blob/master/flameshot.example.ini

As for this being a bug, I'm afraid it is not a bug to my understanding, simply because we have not released new stable version for quite a while now:

https://github.com/flameshot-org/flameshot/releases/latest

@mmahmoudian mmahmoudian removed the Waiting For Info Addressing the issue or merging the PR is halted and we are waiting for more info to be provided. label Aug 24, 2024
@dsoprea
Copy link
Author

dsoprea commented Aug 24, 2024

Well, it's "buggy behavior" in that I haven't done anything and suddenly this changed for me. It may not have been a coding change, but something agitated the configuration/operation.

That change isn't having the desired affected. I updated the config, exited Flameshot, confirmed it wasn't running, started it, took a screenshot, and we're still seeing a BMP as the default format.

This is my current config:

[General]
contrastOpacity=188
drawColor=#800080
filenamePattern=%Y%m%d-%I%M%S
savePath=/home/dustin/Pictures/2024/Screenshots
startupLaunch=true
saveAsFileExtension=png

@dsoprea
Copy link
Author

dsoprea commented Aug 24, 2024

I'd prefer it if we reopened this issue.

@mmahmoudian
Copy link
Member

@dsoprea

I'd prefer it if we reopened this issue.

Can you explain why? whatever change you have seen recently is definitely not because of Flameshot, simply because we have not released any stable version for about 2 years. So unless the issue was introduced 2 years ago, and after updating to 12.1.0, I don't think it is related to Flameshot directly. Something might have changed at your end perhaps, or MATE have changed some MIME types or something.

I'll gladly reopen the issue, I just would like to know the justification.

@dsoprea
Copy link
Author

dsoprea commented Aug 25, 2024

It's just a support request. You're the subject-matter expert. Are you just saying that there is nothing else to try? Your response made it sound like you're just saying "not my problem", though without giving me, or anyone else that might run into this, any other recourse but to just uninstall Flameshot and go somewhere else after years of usage.

@mmahmoudian
Copy link
Member

Sorry, I answered from my phone and didn't see you first comment of the day (somehow I didn't expect to get two separate answers back-to-back):

#3695 (comment)

Since you have tried it and that have not changed the outcome, I will reopen the issue, although one thing is certain, Flameshot 12.1.0 was released 2 years and 1 month ago. So whatever caused the change couple of months back definitely didn't stem from our code-base.

Would you please also test the AUR and see if the issue still persist there. It is maintained by us and it uses HEAD of the master branch.

@mmahmoudian mmahmoudian reopened this Aug 25, 2024
@dsoprea
Copy link
Author

dsoprea commented Aug 26, 2024

I appreciate it.

No difference using the -git repository. The config still has the same file-format modification from before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.
Projects
None yet
Development

No branches or pull requests

2 participants