Using SU-GUI version 5.0.0.9 on Windows 10 (Danish), I can download and install versions, but at the end of the installation I am met with this error message: "This installation package could not be opened. Please control that the package exists and you have access to it, or contact the program retailer to control that this is a valid Windows installation package." (My translation from the Danish error message). Despite the error message, the parallel LO installation was actually successful! I can create a shortcut and run the LO installation without problems. However, it took me quite a while to figure out that the program was not just broken, so it would be worthwhile to fix the issue. I have used SU-GUI for a few years, and it was not like that in the beginning, but I cannot give a version number where it started. Perhaps 1 or 2 years back.
I use Si-Gui in Windows 7 and no problem. is this some Win 10 issue with signature? Or permission issue?
The error message does not say anything about lack of permissions, and I am not asked for administrator access. (Glad about that - apart from testing, SI-GUI can also be used to circumvent the need for administrator rights for installation at e.g. a work computer.) One thought struck me: At least at my home computer, my user account contains a space that is also part of the home directory. I tried creating a testing account with standard (non-administrator) rights with no space in the name, and SI-GUI does run on that without showing the error message. So perhaps the error is a consequence of a space in the directory name. Would handling of spaces in directory names be something likely to be be fixed? (It is still not running fully smoothly - apparently, the program has to be restarted before a second download can be initiated - but that would be a separate issue, I think.)
One thought struck me: At least at my home computer, my user account contains a space that is also part of the home directory. I tried creating a testing account with standard (non-administrator) rights with no space in the name, and SI-GUI does run on that without showing the error message. So perhaps the error is a consequence of a space in the directory name. http://www.contactforcustomerservice.com
Hi Florian Bugzilla has this SI-GUI part so I add you here to look at this bug about space in folder name.
Will look into it in the next days :)
Created attachment 174783 [details] Installation path with space Hi, Cannot reproduce the problem. I can also download more than one main installation at a time
Lars, please try to precise the problem or this bug can be closed.
Well, the bug is still present on my installation: SU-GUI version 5.0.0.9 (still the most recent version) on Window 10 (Danish). I do the following: 1. Start SU-GUI. 2. Choose and download some LO version (I choose the 64-bit version). 3. After download, install it by clicking "Start installation". 4. Wait for installation to finish. On one user account, named "Lars normalbruger", I get an error message on the screen, see the original report. However, despite the error message, install was successful: I can click "Install shortcut", and the shortcut opens the installed version. On another user account, named "Lars_test", I do not get an error message. Everything else appears to be the same. Both accounts are normal users, without administrator rights. As noted in comment 2: The space in "Lars normalbruger" also gives a space in the name of the home directory. It was a guess, but only a guess, that this relates to the difference in behaviour.
Hi Lars, is this issue still reproducible for you ?
(In reply to Xisco Faulí from comment #9) > Hi Lars, > is this issue still reproducible for you ? Yes, it is still reproducible for me. I see it every time I use SU-GUI on my standard account.
[Automated Action] NeedInfo-To-Unconfirmed
This appears similar to the problem I've just reported on the localised help download - select both installation file and the localised help, and the error message you get at the end of the install sequence is the same - but the failure is attributable to the help installation .. the program installs correctly, and the problem only presents itself if you try to use help.