Konqueror unable to recognize folder ( vhosts.d ) as a folder ( inode/directory )

Hi …

Konqueror falsely recognizes that a folder ( /etc/apache2/vhosts.d) is of type text/x-dsrc instead of correctly recognizing it as inode/directory - hence you cannot right click and open in a tab as a folder
Dolphin also recognizes that folder as type text/x-dsrc but at least it can open that folder in a tab.

So any ideas on how to get Konqueror to recognize that folders with a *.d ( like conf.d , ssl.crt etc ) are actually folders ?


First prove what /etc/apache2/vhosts.d is:

ls -ld /etc/apache2/vhosts.d

Hehehehe … vhosts.d is used to setup virtual hosts in opensuse … Its been there for years and years …

Anyway …

ls -ld /etc/apache2/vhosts.d

drwxr-xr-x 2 root root 4096 May 22 23:19 /etc/apache2/vhosts.d

Also …

ls -ld /etc/apache2/*.d

drwxr-xr-x 2 root root 4096 May 13 22:59 /etc/apache2/conf.d
drwxr-xr-x 2 root root 4096 Aug 17 2018 /etc/apache2/sysconfig.d
drwxr-xr-x 2 root root 4096 May 22 23:19 /etc/apache2/vhosts.d

Another note - This has never happened with any version of opensuse before 42.3 …

I am fully aware of that, but when some GUI application says it isn’t a directory, the first thing I would do is check it directly without any interference of a GUI. Only after that confirms that it is what it should be, I would do the next steps in finding out what is wrong with that silly GUI application.

And BTW,

There is an important, but not easy to find feature on the forums.

Please in the future use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.

First, I do not see this on LEAP 15.0 (I specialy started Konqueror for this and managed to find out how to use it as file manager, I normaly use Dolphin for that).

As this happens in both applications, my guess is that it is a central KDE thing. And as for KDE the connection between file name patterns (like having a suffix .d) is configured in System Settings > Applications > File associations (rough translation back from Dutch), I went there and searched for x-dsrc. To my surprise there is such an MIME type there, it is described: D-source code (whatever that may be). And it is connected to the file patterns *.d and *.di.

So far so good. But I am with you when you say that this only should count when it is about a normal file, and not about a directory. I have no explanation for that.

Noted. Thanks.

Can i remove that mime type ? I have never worked on ony D Source Code …
Any idea where that central location is to remove this x-dsrc mime type ? So that it would not interfere with konqueror or dolphin ?
I am running opensuse 42.3 with xfce.

I do not know about xfce, you should try to find the equivalent of what I have describes about KDE.

But then, I am not sure that will help. The application should first decide if it is a directory or not. Once it thinks it is a normal file, it will go for x-dsrc, but then we are already past the problem point.

Hi …I found the text/x-dsrc mimetype at /home/userm/.local/share/mime/packages and /home/userm/.local/share/mime/text.

Its an xml file " x-dsrc.xml " with contents as below …

<?xml version="1.0" encoding="utf-8"?>
<mime-type xmlns="http://www.freedesktop.org/standards/shared-mime-info" type="text/x-dsrc">
  <!--Created automatically by update-mime-database. DO NOT EDIT!-->

I just renamed the file to x-dsrc_xml and restarted konqueror.
There is a change … Konqueror now sees that vhosts.d folder as D Source Code … hehehehehehehe

Note - earlier it reported it as folder / text-x-dsrc ( instead of the expected folder/inode-directory)

Any other ideas on what else i can do ?

Well, it increases the mystics I assume. :wink:

Again, I am not an XFCE user, but as it seems to be a desktop , thus user configuration/environment thing, you could create a fresh user and see if it happens there also. This is more of a basic trial when somebody reposts things that other users can not reproduce.

Thanks for trying. Much appreciated.

Sorry, some misunderstanding here?

I am not trying anything. My suggestion was that you create a new user in your system and then check if the same problem persists in that new users session.

I mean thanks for trying to help. I am closing the matter - indicated by [CLOSED] in the title.
Once again thank you for spending some time on this.

You are welcome.

Well, it seems you have a solution? Or are you giving up?

Other people, finding your thread because they may have the same will be interested.