Bug? Konqueror filemanagement - Mimetype ".conf" shows as "C++ header"
All, On leap 15.4 going to edit nginx.conf, konqueror shows it as a "C++ header" file. (obviously wrong). Selecting "Properties" from context menu, then clicking the little wrench icon to bring up "General" and "Embedding" tabs, the "Filename Patters" show "*.hh", "*.hpp" and "*.H", all correct (all though the *.H is a bit wonky) Nowhere is "*.conf" shown, but conqueror still thinks my ".conf" file is a C++ header. In kcontrol -> KDE Components -> File Associations, this corresponds to text -> x-c++hdr. In the past, there was a type for ".conf". Can someone confirm what they see for a ".conf" file. Just touch or redirect something into a conf and you can look, e.g. $ echo "# hello" > foo.conf and then look at what konqueror thinks the type of file foo.conf is. Thanks. -- David C. Rankin, J.D.,P.E.
On 9/28/23 02:59, David C. Rankin wrote:
All,
On leap 15.4 going to edit nginx.conf, konqueror shows it as a "C++ header" file. (obviously wrong). Selecting "Properties" from context menu, then clicking the little wrench icon to bring up "General" and "Embedding" tabs, the "Filename Patters" show "*.hh", "*.hpp" and "*.H", all correct (all though the *.H is a bit wonky)
Nowhere is "*.conf" shown, but conqueror still thinks my ".conf" file is a C++ header. In kcontrol -> KDE Components -> File Associations, this corresponds to text -> x-c++hdr.
In the past, there was a type for ".conf". Can someone confirm what they see for a ".conf" file. Just touch or redirect something into a conf and you can look, e.g.
$ echo "# hello" > foo.conf
and then look at what konqueror thinks the type of file foo.conf is. Thanks.
There is something fishy with the mime-types. Just rebooted after the nvidia driver update and now ".conf" is back to showing as "plain text" - which it should. There is probably an outside of bounds or use-after-free leading to some UP in the desktop somewhere. If I had the computing horsepower it would be to to run the desktop under some type memory/error check (similar to running the whole thing in valgrind) or a continual strace to see if anything turns up. So I doubt anyone will be able to confirm this behavior exactly. The error likely affects the desktop in random ways -- in this case corrupting the file-association memory. -- David C. Rankin, J.D.,P.E.
participants (1)
-
David C. Rankin