Created attachment 92244 [details] Encrypted file detected as plain text file Just to clarify, I am running Plasma 5 using the plasma5-session package provided in openSUSE. When I check File Association in System Settings, *.asc files appear to be rightly associated with gpg type files. However, in Dolphin, downloaded *.asc files are opened as text files, as the type is detected as "plain text document". I have attached the file in question.
I found a workaround. I removed *.asc from the plain text file pattern in File Associations. Restarting Dolphin after that showed the message correctly as a gpg encrypted file.
Thanks for the bug report! MIME types are determined using the KFileItem class from KIO, so I'll reassign there. In KDE Frameworks 5, the internal mime type handling is dropped in favor of a class that is provided by Qt, so it could be that the problem will be fixed in KF5-based applications.
Both kdelibs4 and KF5 use shared-mime-info, which is where this problem came from. application/pgp-encrypted, application/pgp-keys, application/pgp-signature and text/plain are all associated with *.asc So file contents ("magic") is used to disambiguate, and clearly there's some missing magic to match your file. You could look into improving that - and in any case, report a bug for shared-mime-info on http://bugs.freedesktop.org. I just don't know if it makes sense to have *.asc associated with text/plain or if it should be just for encrypted files.
(In reply to David Faure from comment #3) > Both kdelibs4 and KF5 use shared-mime-info, which is where this problem came > from. > > application/pgp-encrypted, application/pgp-keys, application/pgp-signature > and text/plain are all associated with *.asc > > So file contents ("magic") is used to disambiguate, and clearly there's some > missing magic to match your file. > You could look into improving that - and in any case, report a bug for > shared-mime-info on http://bugs.freedesktop.org. > > > I just don't know if it makes sense to have *.asc associated with text/plain > or if it should be just for encrypted files. Then this would make sense as to why I am unable to open the encrypted message directly in KMail, which was why I downloaded the file to be opened separately in the first place. I thought it was a user setting so I was asking questions about it on the KDE Forum instead. https://forum.kde.org/viewtopic.php?f=215&t=126105 Do you think they are related, or should I file a separate bug report?
https://bugs.freedesktop.org/show_bug.cgi?id=70539 talks about the magic for *.asc files. Clearly it's the intent to associate it with both openpgp and plain text, so the issue is the file contents. You should post a sample non-working file in a new bugs.freedesktop.org bug report. As to kmail, I doubt it relies on kmimetype for this, the content-type is in the mail, so this looks like a different issue.
Thanks. I have added *.asc back to the file type association and the problem has reappeared. I have filed a new bug report on the issue here: https://bugs.freedesktop.org/show_bug.cgi?id=90459 My mistake for adding the report to the issue you pointed to. I will file a new bug report for KMail then for the other issue. Thanks for the help.
I was wrong, the bug is in my QMimeDatabase code. Reopening.
Qt fix written, now awaiting review at https://codereview.qt-project.org/180842
The Qt fix went in.