XnView Software

When I click on an image within the xnview browser some of my images are now being displayed with my default image viewer app instead of xnview.

This did not use to be the case - I'm now using vs.1.9.3.

Unaffected image show 'mm f/s iso' in browser whereas affected images are greyed. Filenames and Format seem to be the same between affected and unaffected images. 'Convert to' is unavailable on affected images. Batch converting affected images to JPEG removes the problem.

I have versions of the affected files from a few days ago which are interpreted and displayed correctly by the vs 1.9.3 software.

The affected files fill the Info/Properties pane correctly but are not displayed by XnView but XnView uses imageViewer to display them.

Only the files' XMP data have been changed by XnView between the two different versions of the files and they have not been touched by any other SW.

The XnView preview, Histogram, EXIF, XMP, EXIF tool info panels works correctly on the affected files.

Changing a category on a single unaffected file does not result in it being affected (NB XnView writes out changed XMP data to the file).

When I recreate the database from the image file XMP data the problem does not persist.

mkc73 wrote: Sat Aug 23, 2025 2:55 pm When I click on an image within the xnview browser some of my images are now being displayed with my default image viewer app instead of xnview.

image files opens with XnView from Browser by default,
but you can change it to 'associated app' in Settings > File list > Custom filter

if its not the case try to reassociate image formats

Many thanks for you reply - could not find Settings/Integration/File associations from root/xnview on Ubuntu (only get Paths).

Default image viewer is imageViewer for all jpg images so not clear why some were displayable by xnview and some not.

But must be something along those lines being corrupted but note that seems to be something flaky with running xnview on my system since deleting database and refreshing database from XMP data fixed the problem.

I left it up in case it is a more generic problem with xnview.

do you have tried to 'update catalog from' on these files?

xnview wrote: Sun Aug 24, 2025 6:15 am do you have tried to 'update catalog from' on these files?

No - but presumably same effect as deleting and recovering catalgue.