Skip to content
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

Client 2.5.0 installs on 32 bit Windows, but only 64 bit binaries are installed #840

Closed
e-alfred opened this issue Nov 15, 2018 · 71 comments
Closed

Comments

@e-alfred
Copy link

@e-alfred e-alfred commented Nov 15, 2018

Expected behaviour

Nextcloud Client 2.5 should install on 32 bit Windows installations and install the right binaries.

Actual behaviour

Nextcloud Client 2.5 installs, but only 64 bit binaries are installed on Windows, resulting in a non-woring installation.

Steps to reproduce

  1. Install the 2.5 client
  2. Try to start it

Client configuration

Client version: 2.5

Operating system: Windows 7 32-bit

OS language: German

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:\Programs/Nextcloud

@e-alfred e-alfred changed the title Client 2.5.0 installs on 32 bit, but only 64 bit binaries are installed Client 2.5.0 installs on 32 bit Windows, but only 64 bit binaries are installed Nov 15, 2018
@coyotenq
Copy link

@coyotenq coyotenq commented Nov 20, 2018

Confirmed in here. Same issue too (Windows 7 32 bits Spanish)
The installer works fine, but drops a 64 bit executable, so, error occurs.
Tested, even, with latest daily build.

@csana
Copy link

@csana csana commented Nov 29, 2018

I can confirm this issue, I tried on Windows 10 32bits Hungarian. The installer works, but the installed executable is 64bit.

@therfman
Copy link

@therfman therfman commented Dec 1, 2018

Confirmed on Windows 10 32-bit English, Is the previous version installer available to restore functionality until this bug is fixed? Not being able to access NextCloud on this machine after a reinstall is problematic.

@obitbef
Copy link

@obitbef obitbef commented Dec 3, 2018

@avrosen
Copy link

@avrosen avrosen commented Dec 3, 2018

Same issue here. After installing the latest official client on Win10 32bit application can't be started with the following windows error message "This App Can’t Run On Your PC".
Happy to provide further insight if this can help to fix the issue.

@JK74
Copy link

@JK74 JK74 commented Dec 12, 2018

same here for W8.1pro N Dutch install. even with the 2.5.1 or the daily build from dec.11

@tigernero79
Copy link

@tigernero79 tigernero79 commented Dec 21, 2018

Are you new to install 2.5.1 on 32-bit windows systems?

to date I have to use version 2.3.3.1 for windows 10 to 32 bit

@donvipre
Copy link

@donvipre donvipre commented Dec 27, 2018

2.5.1 on 32-bit Windows systems still does not work. Tested it today. "This software is not suitable for your computer"

@EmadFathy
Copy link

@EmadFathy EmadFathy commented Dec 29, 2018

I confirm this issue in 2.5.0 and 2.5.1, Please fix it, We need the 32bit version.

@KarelWintersky
Copy link

@KarelWintersky KarelWintersky commented Dec 30, 2018

Same issue. (language: RU)

@jasgot
Copy link

@jasgot jasgot commented Jan 1, 2019

@jasgot
Copy link

@jasgot jasgot commented Jan 1, 2019

Went back to 2.3.3.1 (found it in my folders) to restore functionality.

@anduz
Copy link

@anduz anduz commented Jan 4, 2019

I'm having the same issue.
Will there be a fix or is 32bit OS unsupported in current releases?

@meisterleise
Copy link

@meisterleise meisterleise commented Jan 6, 2019

I would like to know too if this is gonna to be fixed or if 32 bit will be unsupported from now on.
Thanks a lot!

@krombel
Copy link

@krombel krombel commented Jan 7, 2019

I and most other users which see this issue recognize the lack of x32 bit support in the latest release.

I would suggest to simply upvote this issue (react on issue description with 👍) as I did. Repeated messages, that you are affected might help as rememberer, but upvotes on the first message help to triage the most important issues (and therefore when planning the next development steps).

So upvote. And then reconsider writing a comment. In most cases upvoting is enough.
Thanks

@SunDancerGE
Copy link

@SunDancerGE SunDancerGE commented Jan 9, 2019

Same here.

@KarelWintersky
Copy link

@KarelWintersky KarelWintersky commented Jan 9, 2019

triage don't needed. Needed FIX.

@slydder101
Copy link

@slydder101 slydder101 commented Jan 13, 2019

Same issue for me as well! Hope that the problem will be fixed soon...

@CAXAline
Copy link

@CAXAline CAXAline commented Jan 24, 2019

I confirm. Same problem. I can not run on Windows 7 32-bit

@jospoortvliet
Copy link
Member

@jospoortvliet jospoortvliet commented Jan 25, 2019

an ownCloud employee posted some advertising for their client. While it might work, I want to point out that using the ownCloud client is untested (and thus risky) and it lacks functionality. We will look into building a 32 bit version of our client!

@nextcloud nextcloud deleted a comment from guruz Jan 25, 2019
@meisterleise
Copy link

@meisterleise meisterleise commented Jan 25, 2019

an ownCloud employee posted some advertising for their client. While it might work, I want to point out that using the ownCloud client is untested (and thus risky) and it lacks functionality. We will look into building a 32 bit version of our client!

Well, I'm not an owncloud employee. I just switched from owncloud to nextcloud and now I must conclude that there is a very big issue with the client app and have to tell my clients that they can't use the nextcloud client app.

I use the owncloud client app for the nextcloud in a complex structur of 3 Clouds and it works with no harm. In fact it has less interruptions in transfer then the nextcloud client.

Will my post now also be censored?

@donvipre
Copy link

@donvipre donvipre commented Jan 27, 2019

@meisterleise: you can simply use an older version for now. And please click on upvote in the first post :)
thank you very much.

@meisterleise
Copy link

@meisterleise meisterleise commented Jan 27, 2019

@meisterleise: you can simply use an older version for now. And please click on upvote in the first post :)
thank you very much.

I've done that already.
Older Version: I don't need the older version. I'm using a mac. But all the users of my cloud download the new version and wonder why it don't work. The best would be, Nextcloud would no longer offer the current version for download! Or they would indicate in bold letters that the version is for 64 bit only (although -wouldn't help- most users don't know about that).

@guruz

This comment has been minimized.

@camilasan
Copy link
Member

@camilasan camilasan commented Jan 27, 2019

I didn't post an ADVERTISTING for the ownCloud client, I tried to help the people on this public GitHub. That's what Open Source is about, people helping each other.

Yes, right 🦄 @guruz
I am glad you have time for this. Good for you! Open source contributor of the year! 🏆 👏

Just like @owncloud has time to count git commits: https://dragotin.wordpress.com/2018/12/23/eighty-percent-owncloud/. That is great!

@jospoortvliet
Copy link
Member

@jospoortvliet jospoortvliet commented Jan 27, 2019

@guruz that wasn't "helping", telling people "try the ownCloud client" on every bug in our repo isn't helpful in any way. So please just stick to the oC repo and don't comment here at all anymore. I have blocked you now and hidden all comments as I haven't seen a single constructive comment from you in our repo in, well, EVER.

@meisterleise
Copy link

@meisterleise meisterleise commented Jan 27, 2019

@jospoortvliet
Okay, I think you're right. He was a troll.
Nevertheless – perhaps you could stop making the actual version available for download, because people download a version that don't work and they dont know why.

@Happyfeet01
Copy link

@Happyfeet01 Happyfeet01 commented May 4, 2019

@misch7
Copy link
Member

@misch7 misch7 commented May 4, 2019

Hey all,

I built the Desktop Client for 32-bit Windows a few hours ago:
https://schuster.ms/nextcloud-win32/

Tested on Windows 10 (1709), more testing on older systems would be appreciated! ;-)

Thanks and have fun!

@Happyfeet01
Copy link

@Happyfeet01 Happyfeet01 commented May 4, 2019

Oh thanks. That is fast :-)

@e-alfred
Copy link
Author

@e-alfred e-alfred commented May 4, 2019

@misch7 Awesome work! Can you publish some build instructions? This would be very helpful.

It is sad to see this issue being the top voted of all in this repository and no reaction from the devs.

@starox
Copy link

@starox starox commented May 4, 2019

@misch7 Thank you very much for your work.
I installed it on windows 10 build 1803 flawlessly (minus warning for non signed app from windows).
I haven't test it extensively for the moment, it works as usual.

Thank you again

@misch7
Copy link
Member

@misch7 misch7 commented May 5, 2019

Thanks for your feedback! :-)

@e-alfred Yepp, that's really sad and I'm still confused why there is no vital response to that.

I'll post a reference to my build instructions as soon as I have them ready. ;-)

@starox Thx! (Even though I considered code signing to make my release more trustworthy the expense was currently unreasonable for that yet, since I have no certificate at hand.)

By the way I stumbled across the SSL issue just a minute ago:
#622

Another reason not to use the old 2.3 client was the outdated OpenSSL version in it. I compiled the 32-bit version with the more secure OpenSSL v1.0.2r (and libcrypto 1.1.1b).

@KarelWintersky
Copy link

@KarelWintersky KarelWintersky commented May 5, 2019

Anybody knows:

is client version 2.5.2 (32bit) compatible with Nextcloud Server version 14.0.10 ?

@misch7
Copy link
Member

@misch7 misch7 commented May 5, 2019

@KarelWintersky I used Nextcloud Server 15.0.5 for testing my 32-bit build.

General rule of thumb: If it works with the 2.5.2 stable 64-bit build, it should also work with the 32-bit build.
If you try to connect the client to an unsupported server it should show a message warning you about the issue. This happened to me for example when I migrated from ownCloud to Nextcloud, still using the Desktop Sync Clients of ownCloud with the new Nextcloud Server. I got the message but everything was working. It depends on the specific (in)compatibilties of the corresponding client vs. server versions.

So I would suggest to give it a try, perhaps select some test folders only for sync and get back to us with the result! fingers crossed :-)

@avrosen
Copy link

@avrosen avrosen commented May 6, 2019

Just installed on Win10 32bit ver 1809. Saw a whole bunch of suspected virus warnings by my scanner but beside that it works fine so far with Nextcloud 15.0.7.

Big thx @misch7 for your extra work.

@e-alfred
Copy link
Author

@e-alfred e-alfred commented May 8, 2019

@misch7 @camilasan Maybe you can integrate your build instructions/set up into the official client so the official client can support both 32- and 64-bit? The installer of the official client still has the problem of not checking if it is executed on a 32-bit system and simply installing the wrong binaries without any check.

@misch7
Copy link
Member

@misch7 misch7 commented May 8, 2019

@e-alfred Seems we share the same idea! ;-)
That's right and the installer also has the problem to not contain any 32-bit binaries so you'll never end up with a 32-bit version of the client with version 2.5 so far.

@camilasan Is this still the place?:
https://github.com/nextcloud/client-building
If so, I could try to migrate my 32-bit stuff into it and adapt the NSIS script to check for the right installation environment.
Sadly I just found this repo after nearly having a working client. Could have saved me some time.^^
For my built I heavily modified the NSIS script from the client repo because it was outdated. So half of the work is already done.

There are more questions: The instructions there (and the current x64 release of the client) include Debug DLL's like Qt5CoreD.dll which further requires the debug versions of the VC runtime's DLL's.

Are they intended to end up in the release package?

For testing the 32-bit client I left them intentionally out of the Nextcloud folder and everything went fine. So I decided to not include them in my release and I further built zlib myself and picked all DLL's by hand to eleminate the need for the VC 12.x runtime libs.

Till I have feedback and know more I'm continuing with the work on my build instructions so everybody can reproduce a 32-bit build.

@camilasan
Copy link
Member

@camilasan camilasan commented May 8, 2019

@camilasan Is this still the place?:
https://github.com/nextcloud/client-building

Yes.

If so, I could try to migrate my 32-bit stuff into it and adapt the NSIS script to check for the right installation environment.

That would be amazing 🎉

Sadly I just found this repo after nearly having a working client. Could have saved me some time.^^
For my built I heavily modified the NSIS script from the client repo because it was outdated. So half of the work is already done.

There are more questions: The instructions there (and the current x64 release of the client) include Debug DLL's like Qt5CoreD.dll which further requires the debug versions of the VC runtime's DLL's.

Are they intended to end up in the release package?

They should be removed.

For testing the 32-bit client I left them intentionally out of the Nextcloud folder and everything went fine. So I decided to not include them in my release and I further built zlib myself and picked all DLL's by hand to eleminate the need for the VC 12.x runtime libs.

Ok.

Till I have feedback and know more I'm continuing with the work on my build instructions so everybody can reproduce a 32-bit build.

Thanks so much ❤️

@misch7
Copy link
Member

@misch7 misch7 commented May 8, 2019

If so, I could try to migrate my 32-bit stuff into it and adapt the NSIS script to check for the right installation environment.

That would be amazing 🎉

Great, count me in! 🚀

Thanks :) ❤️

@ychaouche
Copy link

@ychaouche ychaouche commented May 9, 2019

Would be nice to have the build instructions to reproduce here. Thanks and nice work you !

@misch7
Copy link
Member

@misch7 misch7 commented Jun 4, 2019

As promised after a vast amount of work and perhaps a little over-escalation 😹 :

https://github.com/misch7/nextcloud-client-building

A new build system and instructions. Happy building! :-)

@misch7
Copy link
Member

@misch7 misch7 commented Jun 9, 2019

If you like to try out ready-built client installers with 32- and 64-bit support, here‘s where my daily test builds get uploaded to:
https://nextcloud-builds.schuster.ms/desktop/daily/Windows/
2.5.3 builds on Win 10 VM, stable-2.5.2 on Win 7 VM, signed with a test key. 😉
Have fun! 😊

@camilasan : Get in touch with me if I can be of any help to support you integrating the new build scripts into your bulid environment. Tried to modify everything in way to help you save time building, so you can focus on client programming. 😼

@polytan02
Copy link

@polytan02 polytan02 commented Jul 8, 2019

So is the issue now sorted with the official client ?
Can we actually install the official build on win32 computers please ? @michaelstingl ?

@polytan02
Copy link

@polytan02 polytan02 commented Jul 8, 2019

@misch7 Thanks for your great support, but how do we know which one of your builds is a stable release please ?

@polytan02
Copy link

@polytan02 polytan02 commented Jul 8, 2019

@e-alfred Hi, please could you change title of this issue by "Client 2.5.x doesn't install on 32 bits windows platforms as client building tools are broken" ?

Maybe this thread doesn't get attention because it says 2.5.0 and not 2.5.x (currently they are on 2.5.3)

@pagaille
Copy link

@pagaille pagaille commented Jul 9, 2019

I built the Desktop Client for 32-bit Windows a few hours ago:
https://schuster.ms/nextcloud-win32/

Hi @misch7, are you aware that your nextcloud client triggers Avast's antivirus ?

Nextcloud is doing a bad job here by making users rely on outdated or unsecure (nothing personnal @misch7) source of software.

@misch7
Copy link
Member

@misch7 misch7 commented Jul 9, 2019

@polytan02 The initial 32-bit-only build on my website (https://schuster.ms/nextcloud-win32/) is the stable one and the only build using a custom update URL so the client won't get replaced by a 64-bit-only version from the official sources. The second link contains combined installer builds with unmodified sources and update URL's and also signed with a testing key not valid on other systems. Anyways daily builds should never be considered stable.

@pagaille I'm aware that certain scanners will complain since my build is similar to the official one and may trigger some fake alerts. It neither outdated (more recent OpenSSL & Qt versions!) nor insecure (well that's up to your trust). It's just not officially signed and ideally you would an official version, published and signed by Nextcloud.
Good news is, they are already integrating my build scripts so there will be an official 64- and 32-bit combined release in the (hopefully) near future.
Of course I already considered trust and signing as an issue prior publishing my first build. But I decided to share it so everybody could benefit from my work. The rest is up to you. ;-)

@krab
Copy link

@krab krab commented Jul 21, 2019

Nextcloud-2.5.2-setup.exe from official website its 32 bit executable but contains 64 bit nextcloud binaries, 64 bit Qt and x64 visual studio redistribute package. So its clearly made for 64bit only windows.

Installer shouldn't run on 32 bit systems either, they just have to add Error box and close installer. Or better build for 32/64 bit separately and put 2 installers on website.

@Happyfeet01
Copy link

@Happyfeet01 Happyfeet01 commented Jul 21, 2019

Use the installer from @misch7

@camilasan
Copy link
Member

@camilasan camilasan commented Aug 7, 2019

Hi All, the daily builds and the last release (2.5.3) are now using @misch7 scripts, which means the installer works on 64 bit and 32 bits. So I am closing this ticket...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet