Bug 439519 - When "*jpe" is a file association, saving a JPEG in apps uses ".jpe" as the extension
Summary: When "*jpe" is a file association, saving a JPEG in apps uses ".jpe" as the e...
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_filetypes (show other bugs)
Version: unspecified
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
: 433176 446887 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-07-05 15:03 UTC by Lapineige
Modified: 2024-10-15 11:28 UTC (History)
12 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Save Menu (29.29 KB, image/png)
2021-07-05 19:19 UTC, S-Paliwal
Details
screenshot 3 (14.81 KB, image/png)
2021-07-05 19:29 UTC, Lapineige
Details
screenshot 2 (30.09 KB, image/png)
2021-07-05 19:30 UTC, Lapineige
Details
screenshot 1, when extension autocompletion is activated (11.87 KB, image/png)
2021-07-05 19:30 UTC, Lapineige
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lapineige 2021-07-05 15:03:58 UTC
SUMMARY


STEPS TO REPRODUCE
1. Try to save a file in jpeg format

OBSERVED RESULT
- 2 error pop-ups : "Saving XXX.jpe failed : image format not supported"
- also the setting to automatically add the extension shows ".jpe" instead of ".jpeg". Disabling this settings does not fix the issue.

EXPECTED RESULT
- image is saved correctly

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 21.04
(available in About System)
KDE Plasma Version: 5.22.2
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 S-Paliwal 2021-07-05 19:19:57 UTC
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.
Comment 2 Lapineige 2021-07-05 19:29:55 UTC
Created attachment 139879 [details]
screenshot 3
Comment 3 Lapineige 2021-07-05 19:30:13 UTC
Created attachment 139880 [details]
screenshot 2
Comment 4 Lapineige 2021-07-05 19:30:41 UTC
Created attachment 139881 [details]
screenshot 1, when extension autocompletion is activated
Comment 5 Nate Graham 2021-08-02 14:52:03 UTC
I think this may actually be a translation issue. Moving to i18n.
Comment 6 Lapineige 2021-08-02 15:48:11 UTC
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.
Comment 7 Jazeix Johnny 2021-08-02 17:06:41 UTC
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)"
Comment 8 Lapineige 2021-08-02 17:30:13 UTC
>  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.
Comment 9 Jazeix Johnny 2021-08-02 18:35:49 UTC
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 :)
Comment 10 Lapineige 2021-08-02 18:40:37 UTC
> 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.
Comment 11 Nate Graham 2021-08-02 19:21:58 UTC
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?
Comment 12 Lapineige 2021-08-02 19:49:37 UTC
>  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
Comment 13 Lapineige 2021-08-15 20:59:46 UTC
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 :/
Comment 14 Ian Goddard 2021-09-08 21:05:28 UTC
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.
Comment 15 Ian Goddard 2021-09-08 21:27:08 UTC
(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.
Comment 16 Nate Graham 2021-12-14 18:58:53 UTC
*** Bug 446887 has been marked as a duplicate of this bug. ***
Comment 17 Ian Goddard 2021-12-21 14:32:25 UTC
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
Comment 18 Lapineige 2021-12-21 15:52:26 UTC
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 ^^
Comment 19 Greg Lepore 2022-02-01 12:20:49 UTC
*** Bug 433176 has been marked as a duplicate of this bug. ***
Comment 20 Robert Grasböck 2022-05-05 12:42:29 UTC
(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 !?!?
Comment 21 Nate Graham 2022-05-05 21:16:19 UTC
Oh wow, fascinating. Can reproduce. This does seem to be a deficiency in our mimetype association system.
Comment 22 byebyebugaylon 2024-06-25 15:42:01 UTC
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.