-
Notifications
You must be signed in to change notification settings - Fork 804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nextcloud windows client 2.5.3 and 2.6.0 when start as in remote desktop session will CANNOT start #1448
Comments
There is a new release 2.6.0, just published on Friday: Downloads for all platforms: Could you give it a try and get back here with the results? ;-) |
Thank you every much.I tested.But , still the same. Thanks a lot . |
Same here. Follow discussion |
Subscribe for 2.6.0 when using Remote Desktop, than error occurs. When using e.g. Teamviewer, Client starts normally. |
Same error on fresh-ish windows 10 install (1809, 1909) using remote desktop. Nextcloud client version 2.6.2. Now I think about it this probably is not a new problem? Or at least something else also had similar problem before and the solution is to disable the app's gpu acceleration. But I don't remember how to do that. Apparently it's common problem on systems running certain radeon driver? Renaming certain dll file seems to fix it. |
Filename is: atig6pxx.dll It's located in Windows directory. |
Same issue: |
Same here. Client works when started from local session, then you can even connect via RDP and it's ok. Startet from an RDP it crashes. |
Same here. Exact the same as Volker-K described. |
Same issue for me. I work from home and need RDP connection over VPN to my work computer. From time to time I need to reboot it. When I login over RDP the Nextcloud client will not start with that exact name. If I reboot and login from behind computer the client will start. Any solution for this? |
On Windows 10: If running this app over a remote desktop and you have an AMD/ATI card, simply disable the real graphics card in Device Manager and restart the application (not the computer). https://github.com/alacritty/alacritty/issues/1976 |
That's one way. It worked. |
Thanks. I think it is a problem of QT , several other application with QT in remote desktop session report the same message and cannot load , for example OpenSCAD. @Volker-K |
@ericohao It's a problem of QT caused by a misspelled dll-name insinde the registry. So lots of Nividia drivers for AMD/ATI systems will cause this error. QT tries something that should normally work and obviously does with other graphics cards. |
Here seems to be the relevant QT bug: https://bugreports.qt.io/browse/QTBUG-50371?focusedCommentId=329417&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel |
I found a workaround by placing opengl32.dll from the MESA windows builds (https://github.com/pal1000/mesa-dist-win/releases/) in the Nextcloud installation directory. |
Expected behaviour
Normal Start
Actual behaviour
with a MessageBox say :"Error: LoadLibrary failed with error 87:The parameter is incorrect."
Steps to reproduce
1.Normal Success Install nextcloud windows client 2.5.3(2.5.2).
2.Restart the computer without login.
3.On another computer remote desktop connect the computer and login,and click to start nextcloud windows client.
Client configuration
Client version:2.5.3
Operating system:
Windows 10
OS language:
English
Qt version used by client package (Linux only, see also Settings dialog):
Client package (From Nextcloud or distro) (Linux only):
Installation path of client:
C:\Program Files (x86)\Nextcloud
Server configuration
Nextcloud version:
Storage backend (external storage):
Logs
Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.
Client logfile: Output of
nextcloud --logwindow
ornextcloud --logfile log.txt
(On Windows using
cmd.exe
, you might need to firstcd
into the Nextcloud directory)(See also https://docs.nextcloud.com/desktop/2.3/troubleshooting.html#log-files)
Web server error log:
Server logfile: nextcloud log (data/nextcloud.log):
The text was updated successfully, but these errors were encountered: