Image files not associated with the image viewer by default

[john256]

Well, I am not sure if this counts as a bug, but I think that it will perhaps be taken more seriously if posted in this section rather than among the "Suggestions"

So, as the title says, it appears that currently all the image files are by default associated with the corresponding editing application and not with the image viewer (Viewnior). Opening an image file with the viewer is much more natural when a user would like to scan through a folder full of images, than opening every file in GIMP (*.jpg, *.png, and the other currently associated) or Inkscape (*.svg). I know that this can be easily changed through the file context menu, but I think that Salix OS will benefit from such small brush-ups towards its perfection

[mimosa]

This has always annoyed me, especially because GIMP takes quite a while to open before you can close it again, if you forget about this. Because I don't look at that many pictures, I usually do forget. And as john 256 says, of course you can change it, but I don't think it's a good default. I am an example of the tendency to just live with the default even though I know it must be easy to change globally forever.

In fact I see that I finally have now, which reminds me of a related point. When you ask to open a file with an app other than the default, having right-clicked on it, you choose from a list. The option to change the default permanently is ticked. I think it would be better if it were unticked, so that making the change would be a conscious decision.

This stuff is fatal for inexperienced users, and annoying to everyone else for what are fundamentally the same reasons: the interface is being bossy.

[gapan]

I am absolutely certain that after a fresh installation, with a new user profile, all image files open with viewnior, not gimp. If you have them opening with gimp, it's probably because you used an existing user profile when installing salix and that is a problem with that existing profile, not salix default settings.

[john256]

I am absolutely certain that after a fresh installation, with a new user profile, all image files open with viewnior, not gimp. If you have them opening with gimp, it's probably because you used an existing user profile when installing salix and that is a problem with that existing profile, not salix default settings.

No, gapan, it's a pristine installation; all partitions were formatted, so there are no previous configuration files remaining.

mimosa, had you an existing profile that interfered somehow?

I observed the same problem on a fresh install of the previous version (I think it was 13.1.2, not the live CD) months ago on a different PC, but as I just started to use Salix OS I thought I have to report this minor issue.

[Akuna]

I am absolutely certain that after a fresh installation, with a new user profile, all image files open with viewnior, not gimp. If you have them opening with gimp, it's probably because you used an existing user profile when installing salix and that is a problem with that existing profile, not salix default settings.

No, gapan, it's a pristine installation; all partitions were formatted, so there are no previous configuration files remaining.

Yes. Same here and same for all machines that I installed for friends and family. Another problem at one point was pdf files opening with gimp instead of evince. But this might not be the case anymore, I'll have to verify on a new install again.

[gapan]

Well, I just did a fresh installation and it works fine! I'm wondering if something else is interfering with the default settings. One thought: if you have this problem, what is your default locale?

[Akuna]

French here

[john256]

Default locale here is en_us.utf8. PDFs open correctly in Evince.

[mimosa]

Mine's British English. I remember the problem with pdfs too. My installations generally start pristine, because I still haven't quite got the hang of getting user mimosa in a new install to use existing mimosa's /home, even though that's the whole point of keeping it on a separate partition.

EDIT Ratpoison doesn't seem to have any equivalent behaviour, though I dare say you could configure it to.

[pwatk]

My installations generally start pristine, because I still haven't quite got the hang of getting user mimosa in a new install to use existing mimosa's /home, even though that's the whole point of keeping it on a separate partition.

I just move my home directory to something like /home/pwatk.bak, install Salix, then move over what I want to keep afterwards and delete the rest.