Bug 439519

Created attachment 139878 [details]
Save Menu

Can you attach a screenshot for how it's appearing your PC? For me at least, the jpg option is appearing normally and the save to jpg option is working normally.

Created attachment 139879 [details]
screenshot 3

Created attachment 139880 [details]
screenshot 2

Created attachment 139881 [details]
screenshot 1, when extension autocompletion is activated

I think this may actually be a translation issue. Moving to i18n.

Ok. That's a very surprising one, even an auto-translation shouldn't change that ^^

If needed : I'm using French (France) language in my system.

Hi, if you run gwenview in command line, do you have some errors/warnings?

I don't see in any French translation file the translated sentence (except in ./messages/kio/kio5.po:3619 where the generic %s is used).

Note: doing: "export LC_ALL=fr_FR.UTF-8; locale && gwenview", I started the application in French and didn't have the issue, I managed to save a file in jpeg + it was written "Sélectionner automatiquement le nom et l'extension du fichier (.jpg)"

>  Hi, if you run gwenview in command line, do you have some errors/warnings?
No. Any debug command I should run ?

I noticed something new (I believe ?):
> also the setting to automatically add the extension shows ".jpe" instead of ".jpeg". Disabling this settings does not fix the issue.
If I disable that setting, and write .jpg (not .jpeg), it allows me to export "file.jpg" (not.jpe), but still, "image format not supported"

> Note: doing: "export LC_ALL=fr_FR.UTF-8; locale && gwenview", I started the application in French and didn't have the issue

I did that too. Same error as before.
I also did use:
> export LC_ALL=en_EN.UTF-8; locale && gwenview

No change.

Disclaimer, I'm not a gwenview developer, just a French translator.

On my side when I run gwenview from a terminal, I have some warnings like:
org.kde.kdegraphics.gwenview.lib: Unresolved mime type  "image/x-mng"
...

I was expecting some equivalent for you with jpg maybe...

I can reproduce the issue when I manually remove the /usr/lib/qt/plugins/imageformats/libqjpeg.so from Qt installation folder (but in this case, the JPEG option disappears from the combobox)...

@Nate, so not a i18n issue for me :)

> org.kde.kdegraphics.gwenview.lib: Unresolved mime type  "image/x-mng"

I have this error message, but that when opening gwenview. There is nothing during and after the whole saving to jpeg process.


> /usr/lib/qt/plugins/imageformats/

I don't have this directory.

Hmm, my mistake, sorry.

I cannot reproduce the issue at all. No idea how to debug. It's possible this was fixed a while ago. Lapineige, is there any chance you can update to a newer version of Gwenview?

Also, is Gwenview installed from Kubuntu's packages, or some other source?

>  is there any chance you can update to a newer version of Gwenview?

I'm already on Kubuntu Backports. Should I wait for the next upgrade ?
NB: that issue came with the last upgrade from backports (I believe), it was not present before.

> Also, is Gwenview installed from Kubuntu's packages, or some other source?

I don't know how to check, but it should come from Kubuntu Backports

Gwenview updated today (I believe), to 21.0.8.

The issue is still there (can't save a .jp(e)g file), but I no longer have the ".jpe" problem…

I really don't get where is that trouble coming from :/

It appears to be associated with a more general "Save as" problem affecting jpegs.  If something.jpg file is simply saved there is no problem.  If it's Save[d] as somethingelse.jpg or .jpeg or .jpe an unsupported format error is thrown.  Kolourpaint has exactly the same set of errors.

Could it be an error setting up the save dialog?  It looks like it's set up with the wrong suffix, .jpe, doesn't recognise the correct ones, .jpg and .jpeg and the .jpe it does recognise is not a valid suffix for the file type.

(In reply to Ian Goddard from comment #14)
> It appears to be associated with a more general "Save as" problem affecting
> jpegs.  If something.jpg file is simply saved there is no problem.  If it's
> Save[d] as somethingelse.jpg or .jpeg or .jpe an unsupported format error is
> thrown.  Kolourpaint has the same set of errors.
> 
> Could it be an error setting up the save dialog?  It looks like it's set up
> with the wrong suffix, .jpe, doesn't recognise the correct ones, .jpg and
> .jpeg and the .jpe it does recognise is not a valid suffix for the file type.

I should have added the version is 20.12.1-1 from Devuan Chimaera, i.e. same as Debian Bullseye.

*** Bug 446887 has been marked as a duplicate of this bug. ***

Workaroud:
System setting>Applications>File associations 
Look up the enter jpeg in the filename search box.
The Filename Patterns list to the right has *.jpe as the first pattern in the list.  Select this, click Remove, click Apply.
It seems to solve the problem, or at least, so far, so good

Excellent, it's working, thanks !!

It doesn't solve my issue opening some JPEG (namely those generated by Darktable, maybe some others) but I was only dreaming it could have that side effect ^^

*** Bug 433176 has been marked as a duplicate of this bug. ***

(In reply to Ian Goddard from comment #17)
> Workaroud:
> System setting>Applications>File associations 
> Look up the enter jpeg in the filename search box.
> The Filename Patterns list to the right has *.jpe as the first pattern in
> the list.  Select this, click Remove, click Apply.
> It seems to solve the problem, or at least, so far, so good

Thank you, that worked also for me!
I was searching a while to come to this fix.
Never, ever thought, that this problem has todo with file associations !?!?

Oh wow, fascinating. Can reproduce. This does seem to be a deficiency in our mimetype association system.

It looks like this bug affects Spectacle as well, at least as recently as Version 22.12.3.

(In reply to Ian Goddard from comment #17)
> Workaroud:
> System setting>Applications>File associations 
> Look up the enter jpeg in the filename search box.
> The Filename Patterns list to the right has *.jpe as the first pattern in
> the list.  Select this, click Remove, click Apply.
> It seems to solve the problem, or at least, so far, so good
This workaround also worked for me.