Originally posted by Kivarnis
View Post
Announcement
Collapse
No announcement yet.
Canonical Developer Tries Running GOG Games On 64-Bit-Only Ubuntu 19.10 Setup
Collapse
X
-
- Likes 2
-
Last edited by horizonbrave; 21 June 2019, 07:37 PM.
Comment
-
If the hardware will run 32-bit code, and won't stop doing so anytime soon, I'm not sure it makes much sense to stop supporting it in software for a distro. We can just install dosbox and run 16 bit code, so doing something along those lines for 32 bit is a better option than just choosing to not do multilib. You could do no-multilib in Gentoo pretty much the day the first Opteron launched, and I bet if you asked people today, they either have a dual-boot with multilib or just a multilib system for desktop use (servers, which is what ubuntu is focusing on, can do without multilib). It's never been easier to run a 64-bit only system, but the need to run 32 bit software hasn't completely gone away, and never will. Flatpak and containers have their own issues, so I would much prefer any 32 bit libs to be ported or merged into a few packages or something.
Comment
-
Assuming Canonical doesn't revert course or scale back their decision to offer at least the most popular 32-bit packages to remain, it could be pain in the short term particularly for gamers.
Also, I can imagine Linux Mint focussing more on their Debian-based flavours in the future..
- Likes 1
Comment
-
- Likes 7
Comment
-
Basically I can understand to drop 32 bit ISO images as long as a 32 bit EFI loader is included in the 64 bit one. But dropping 32 bit packages completely is ridiculous. Ubuntu lib packages are Debian based and tested there already. Also even if you could use a 32 bit user land via 3rd party lib package (like from Steam) usually you want to use mesa or even Nvidia binary drivers in the same version (little differences might work with mesa but not for Nvidia). If they remove most 32 bit apps but keep at least the commonly used 32 bit libs I would say this is okay, but otherwise Ubuntu 19.10 will be the end of the hype.Last edited by Kano; 22 June 2019, 12:03 AM.
- Likes 1
Comment
-
Originally posted by Britoid View PostA solution is to install Flatpak.
GameHub is a games manager/downloader/library written in Vala. It supports Steam, GOG and Humble Bundle as game sources. I have partially got it to work, but I have some issues: Network is weird, ...
Originally posted by barthalion (Bartłomiej Piotrowski from Flathub)To expand on what TingPing said, Steam at least provides some common runtime that publishers/developers can base on, and even if that in mind, it doesn't really work. Just go through issues reported on Flathub's Steam repository – many games are broken because of dependence on external libraries or applications that are not correctly shipped. GameHub doesn't provide even that and it's impractical to add every missing dependency to Flatpak application itself.
GOG clearly states on their website that only Ubuntu is supported and even the release differs between particular games. Humble Bundle is even more trigger happy and I had even less luck with few games I bought there. Not to mention that some are 32-bit only, making it even harder to make everything work. All this results in bad user experience, especially for players with no technical Linux background and I can't see Gamehub being any different.
(On a side note, we are also considering removing Steam.)
It should be possible to create a flatpak package for a game manager that supports GOG, and include Steam Runtime in it. I believe that it would help running most Unity-based games and maybe even some others, but definitely not all of them.
For example, the Epic Games documentation states that UE4 compiled for Ubuntu may be incompatible with UE4 compiled for CentOS (and vice versa). That's why game developers love Steam when it comes to publishing games on Linux. All they have to do is just to build game against Steam Runtime, and then it will work on (almost) every Linux distribution. It isn't the case when it comes to GOG. They state that Ubuntu is the only supported distro, so many developers cares only about this one. There is no enforcement to use Steam Runtime here, nor developers try to do this on their own. That's why running GOG games under Steam Runtime will not always be successful.
BTW: There is a reason why this list is so huge: https://web.archive.org/web/20180607...portselsewhere
Anyway, it will be a half-working solution. Probably much better than running an another Linux distribution in VM or using hangover, but still a partially-working workaround, rather than a complete solution.
And when it comes to Humble Bundle DRM-Free games, the situation would be even worse. Honestly, it will be a disaster.
- Likes 4
Comment
-
Originally posted by vegabook View PostThe consequences will be: even more market share for Ubuntu. Because they're not scared to lead, and indeed, as you might not have realised, with this move they're getting more press coverage than any other distribution could possibly hope for.
Originally posted by vegabook View PostI guarantee you the vast majority of people are looking at this and going "a) I been 64 bit for at least 5 years if not 10, b) you mean to tell me there's still 32 bit shite around? Get rid of it already. Well done Ubuntu!"
Insane? Of course! But no more insane than what you are suggesting here.
Microsoft tried to sell Windows RT without Win32 support and they failed. That's why they put a lot of effort into providing support for transparent x86 emulation in Windows 10 on ARM. They know that without it they have absolutely no chance in this market.
Oh, and one more thing. If you think that 32-bit support is just about some legacy software, you are wrong.
Originally posted by WINEWhen Windows began targeting 64-bit architectures, Microsoft decided to include a compatibility layer to support their massive universe of 32-bit applications. This kind of subcomponent, nicknamed WoW64 (for Windows on Windows 64-bit), is also implemented in Wine to solve the exact same problem.
64-bit Wine built without 32-bit support will not be able to run ANY 32-bit applications, which most Windows binaries are. Even many 64-bit programs still include 32-bit components!Originally posted by dmitry (Dmitry Timoshkov from baikal.ru)Many 64-bit applications still use either a 32-bit installer or some 32-bit components. In comparison 64-bit Windows will support 32-bit (probably) forever.Originally posted by vincent (Vincent Povirk from CodeWeavers)Make that almost all applications. It's very unusual for a program to have a 64-bit installer, because it won't be able to control what happens when a user runs the installer on 32-bit Windows.
In practice, the only cases where 64-bit only wine will be useful are when 64-bit applications are packaged some other way (such as a .zip, Steam Play, or packaging specifically for Wine) or for running Wine builtins like msidb.Originally posted by vincent (Vincent Povirk from CodeWeavers)Nor do I see much point in packaging a 64-bit-only Wine on our end. It's such a niche case for 64-bit-only Wine to be useful at all.
- Likes 3
Comment
Comment