4/6/2023 0 Comments Kde image viewer![]() The same thing happens with Kate, Google Chrome / Chromium, and some other applications under the latest KDE / KIO. That's why I no longer believe this is an issue with XnViewMP. (Having minor problems using XnViewMP only with the latest KDE versions) Which distribution and/or version of KDE are you using? This issue does not happen on Cinnamon desktop (only KDE for some reason.) This issue also happens when opening an image file from an external USB drive. The only reason I believed this was related to network shares was because it was obvious that I cannot disconnect the share. This issue always happens if I open up an image with XnViewMP with my file browser (under KDE), and it doesn't matter if I am using a network shared folder. This issue does not happen if I first open up XnViewMP and then load an image either by click-and-drag or File > Open The file.so process gracefully disappears. This issue does not happen if I open up an image using the file paramter with other image viewers (eg, GwenView, GPicView, Ristretto). For every time I open up an image with XnViewMP (from my file browser), it adds another process of file.so that will not release the file, until I kill the file.so process. However, the process file.so is still using the image file. Once I close XnViewMP, all such xnview processes disappear. Xnview wrote: ↑ Thu 11:25 amAnd XnView is not in process list?Ĭorrect. Click-and-drag image into XnViewMP window.Scenario 5, using XnViewMP, without invoking a file parameter ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |