[Resolved] Zoner Photostudio fails to refresh display

[txemamint]

Hello,
I have a VirtualBox 4.3 on a Linux mint 19 host with a Windows 7 Home edition 64 bits guest, and Zoner Photo Studio 15 running on Windows.
I have encountered a problem, Zoner does not refresh the display after some actions. For example, when i delete a picture, the thumbnail does not disappear from the display, and when i rename a picture, his name under the thumbnail does not change. But if i go to a different directory in the navigator and then i return to the original directory, the new display show the changes correctly. So i deduce that Zoner fails to refresh the display after some actions, but not when the whole browser is refreshed.
Zoner Photo Studio 15 works correctly on a Windows 7 machine.
I desinstalled Zoner and installed again but it continues the same.
Has anybody found this problem? Any suggestion will be appreciated.

Best regards;

[socratis]

I have a VirtualBox 4.3

That's a really old version, even the latest 4.3.40 was released on 2016-08-22!!!

I suggest you update to the latest 6.0.4 (or 5.2.26 from the 5.x series) before we can have a meaningful conversation. You might be looking at something that may have been addressed already. There's no point in dealing with that old of a VirtualBox.

Get and install the official version from the Linux Downloads section of VirtualBox (not your distro, it's not supported). You can even add VirtualBox as a repository, so you could use your traditional install/upgrade/uninstall tools.

[txemamint]

Hello Socratis,
I tried to install the official version by adding the virtualbox repository to /etc/apt/sources.list.
Mint 19 is based in Bionic release of Ubuntu.
deb https://download.virtualbox.org/virtualbox/debian Bionic contrib
From the command: apt-get update, i get the next error:
Err:63 https://download.virtualbox.org/virtualbox/debian Bionic Release
404 Not Found [IP: 2.17.152.141 443]
E: Repository «https://download.virtualbox.org/virtualbox/debian Bionic Release» has not a publication file.
¿Is there a problem with Bionic release?

Regards;

[mpack]

Please provide a VM log file. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

[txemamint]

Uppps, i realized that my actual Virtualbox version is 5.2.18_Ubuntu r123745, not the version i put in the first post, i am sorry.
Here is attached the log. As it exceeds the max. size, it is divided in two files: Fist part is in W7_HOME-2019-03-26-22-18-28_1.log, the rest of the log is in W7_HOME-2019-03-26-22-18-28_2.log.
Regards;

[ModEdit; Two partial logs removed. See next post for the proper attachment]

[mpack]

You were given instructions that would avoid the need to split the log. Any particular reason for ignoring that part?

[socratis]

I tried to install the official version by adding the virtualbox repository to /etc/apt/sources.list.

i realized that my actual Virtualbox version is 5.2.18_Ubuntu r123745

As a first pass, why don't you simply download VirtualBox manually? Do that, let's solve your current problem, then we can figure out why your repository setup doesn't work. Plus you need to do that because you have the Ubuntu fork...

Get the 6.0.4 Bionic version from: http://download.virtualbox.org/virtualb ... _amd64.deb
and the Extension Pack from: http://download.virtualbox.org/virtualb ... ox-extpack

On other news, please follow mpack's instructions, ZIP the log, edit your message and delete the two partial logs and upload the ZIPPED single log.

[txemamint]

No, i didn't notice the word "zip" in your message.
I send the log again in a single file.

[socratis]

You must have been preparing your ZIPPED log the same time that I was posting, and you missed my warning about the Ubuntu fork of VirtualBox that you have:

VirtualBox VM 5.2.18_Ubuntu r123745 linux.amd64 (Dec 27 2018 00:41:57) release log

You can either ask in their forums/channels for help, or completely remove/uninstall/delete/purge their version and install the official version. I gave you the direct links for your Bionic in my previous post.

[txemamint]

I downloaded and installed manually Virtualbox Versión 6.0.4 r128413 (Qt5.9.5) and also the Extension pack 6.0.4r128413, but the same problem goes on.

[socratis]

1. Post an updated VBox.log ZIPPED now that you have the proper version, so we can see the messages.
2. Are we talking about an application not refreshing? While working with local data? Remote data? Describe the situation please so that we can try and replicate it...

[txemamint]

Ok, Socratis.
Here is attached the log file from the new version.
I will send a detailed description of the wrong behavior of the application as soon as possible.

[socratis]

Barring the fact that you got a log after installing and re-installing the GAs (we just need a simple run, not your whole past week's activity log), I cannot see anything really standing out.

I asked you if the files that you were accessing were in a shared folder, you didn't answer. I do see the following however in the log:

00:00:01.464522 SharedFolders host service: Adding host mapping
00:00:01.464533     Host path '/mnt/foto', map name 'FOTO', writable, automount=true, automntpnt=, create_symlinks=false, missing=false

And I have a really high level of certainty when I'm going to say that I smell that this is the problem; the photos you're trying to analyze are in a shared folder, that's mounted to your host, perhaps an ext. HD. Is that correct?

If that's the case, yes, do expect it not to work as if the shared folder was a local folder.

[txemamint]

I asked you if the files that you were accessing were in a shared folder, you didn't answer.

I can not see where you asked that.
Anyway, the answer is "yes", the pictures i manage with the application are in a shared folder linked to a different partition of the same disk.
This works great with photoshop.
Do you think it will go better with a "Raw disk" instead of the shared folder?

[mpack]

Do you think it will go better with a "Raw disk" instead of the shared folder?

Absolutely not. Raw disk is a last resort server option, not an alternative to shared folders. Raw disk would mean unmounting that volume from the host and doesn't apply to folders at all.

The actual alternative to GA shared folders is a proper network share. I.e. designate a folder as shared on the host (obviously, sharing a whole drive is incredibly risky). Then make sure VM and host are on a common network: the easiest way is bridge to the host network (ideally Ethernet). Failing that use the "Host Only" network mode for that connection. If you need Internet then keep NAT as the first network, as a second virtual NIC for host-only.