Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No emblems after new MIME type registered #256

Closed
ghost opened this issue Mar 16, 2019 · 3 comments
Closed

No emblems after new MIME type registered #256

ghost opened this issue Mar 16, 2019 · 3 comments

Comments

@ghost
Copy link

ghost commented Mar 16, 2019

Dear all,

I am using linux Mint 19.1 Cinnamon with nautilus, but I noticed this issue on Ubuntu Gnome 3 as well. I have RabbitVCS installed and everything works well.

However, I had to register a new MIME type by following the instructions:
https://developer.gnome.org/integration-guide/stable/mime.html.en

The mime type is now successfully registered but RabbitVCS won't apply emblems on files of the new type. De-registering the new mime type by deleting the corresponding .xml file and re-updating mime database makes the emblems reappear.

I also tried to change icon theme without success.

@monnerat
Copy link

monnerat commented Jun 9, 2019

I made some testing and I can reproduce. However, it seems Nautilus itself refuses to set the emblem (I don't know under which precise condition). I think nothing can be done in RabbitVCS to overcome this problem.
This does not occur with Caja that has a RabbitVCS client very similar to Nautilus one.

@ghost
Copy link
Author

ghost commented Jun 9, 2019

Hello, I actually solved the problem. Instead of manually adding the mime types I began to use this tool https://forums.linuxmint.com/download/file.php?id=49217 that a very friendly guy on the linux Mint forums packaged for all of us. When registering new mimes with that script the emblems appear regularly.

@monnerat
Copy link

monnerat commented Jun 9, 2019

I actually solved the problem ...

Thank you for your reply. As a conclusion, we can surely assume the problem is outside RabbitVCS and this issue is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant