As you might have heard by now, Canonical has made the decision to drop 32bit support from Ubuntu 19.10 onwards.
Writing on the mailing list, as well as this post on Ubuntu's Community Hub, Canonical gave a reminder that the decision isn't coming without warning. It was proposed last year and it was followed up with another post detailing a final decision to be made in the middle of 2019. So here we are, the decision seems to have been made.
The problem isn't hardware, as likely around 99% of people nowadays have a 64bit capable computer. Going by our own statistics, from what 2,254 users told us only 4 are using a 32bit Linux distribution. The issue then, is mainly software and libraries needed to actually run 32bit applications. This is where it sounds like there's going to be plenty of teething issues, with a number of people not too happy about the decision.
Steam, for example, is one such application along with plenty of 32bit games that will likely never get updated, although Canonical did say they're "in discussions" with Valve about it. There's also GOG, Humble Store and itch.io which all provide a number of direct-download 32bit games, which do not supply the required 32bit libraries to run. It doesn't sound like they have been given any thought (at least they haven't been mentioned).
Another of the major problems being Wine, with a discussion now happening on their mailing list. The discussion doesn't seem to be too positive, with developer Henri Verbeet even saying "I think not building packages for Ubuntu 19.10 would be the only practical option.", although Andrew Eikum's idea of using the Steam Runtime could be an interesting way around it.
What are your thoughts?
Perhaps because it's new and shiny (to me), but I recently left Debian and tried Suse tumbleweed (their rolling distro). I find it much easier to set up (great installer) and it feels much more polished. It has simple instructions to activate Nvidia drivers and is more up to date (bleeding edge) than Debian testing. The package manager is different and takes some getting used to, but it seems well thought out.
If your looking for something on the user friendly side, it might be worth a look.
While I had been aware of plans to stop the 32bit variants of the distribution, I never would have imagined that they'd also remove 32bit support from the 64bit distro at this point in time.
Not sure what I'll do now. Back to Debian? A colleague suggested Manjaro, but after a quick search it appears as if there aren't any ready-made wine-devel packages. Don't really want to be limited to wine-stable or compile anything but 64bit wine myself.
Or I'll just sit it out and hope that somebody provides a PPA for the essential 32bit stuff. Will not upgrade before 20.04.1 LTS is out anyway.
That said, as a developer (and even as a user), I do not understand how in this day and age we're held back by legacy 32bit stuff. It's understandable that support is desirable when looking at games from 15 years ago, but why aren't things like Steam or GOG Galaxy or modern software install packages 64bit these days? The one bit that wasn't 64bit on my Linux system (before I ditched Windows as gaming OS in 2015) were the shoddy Canon printer drivers, and even then it irked me that I had to have a host of 32bit libs installed on top of the regular 64bit stuff. Maybe it's about time for some of the developers out there to move with the times! :-).
Quoting: denyasisFor those looking to jump off Ubuntu, Debian testing is nice. I used it for the past 10 years.Maybe it's because I've been using it for so damned long, but Debian to me is VERY easy to set up. The only things out of the box I do really is this;
Perhaps because it's new and shiny (to me), but I recently left Debian and tried Suse tumbleweed (their rolling distro). I find it much easier to set up (great installer) and it feels much more polished. It has simple instructions to activate Nvidia drivers and is more up to date (bleeding edge) than Debian testing. The package manager is different and takes some getting used to, but it seems well thought out.
If your looking for something on the user friendly side, it might be worth a look.
1) add user to sudo (not really needed, but some may like it this way.)
2) install nvidia drivers 'sudo apt install nvidia-driver'
3) enable i386 packages 'sudo dpkg --add-architecture i386' (something apparently Ubuntu is going to kill)
4) 'sudo apt install plymouth-themes'
5) 'sudo plymouth-set-default-theme futureprototype' (assuming you're running buster/testing)
6) edit /etc/default/grub to add 'splash' next to 'quiet'
7) 'sudo update-grub2'
8) reboot.
Only thing Debian could use work on for the install, is probably the partitioning. Though they are the one distribution who I think just letting it choose actually works well (every other distro I've tried does something ridiculous and gives like 100GB to root, and still uses the 'double the ram for swap' idea that went away as soon as we went over 1gb of ram..
Yes, there will be a few bumps along the way, but the longer people wait to move forward with this, the harder it will get.
Better sooner than later, then. It is inevitable, anyway.
Last edited by TheSHEEEP on 21 June 2019 at 4:04 pm UTC
Last edited by Scoopta on 21 June 2019 at 4:37 pm UTC
Last edited by Shmerl on 21 June 2019 at 4:48 pm UTC
The problem might get resolved in the background while we, the users, won't notice.
Playing devil's advocate a bit here, but, since 32 bit is no longer being pushed, Isn't it just a matter of time before it would be dropped or that future versions of libraries would have incapabilities with our beloved older games and programs?
It seems to me at some point in the future there would have to be an extra overhead, akin to a WINE or dosbox or something, that preserves that working state for older titles.
I just don't think any of us thought that time would be now
Last edited by denyasis on 21 June 2019 at 5:24 pm UTC
Quoting: denyasisIsn't it a bit of an inevitability, though?
Playing devil's advocate a bit here, but, since 32 bit is no longer being pushed, Isn't it just a matter of time before it would be dropped or that future versions of libraries would have incapabilities with our beloved older games and programs?
It seems to me at some point in the future there would have to be an extra overhead, akin to a WINE or dosbox or something, that preserves that working state for older titles.
I just don't think any of us thought that time would be now
So far, it doesn't need to be now, and there will be too much overhead, to be acceptable. Too many games were made in 32-bit still in the not distant past.
In the further future - yes, likely there will be ways to run 32-bit in some kind of emulated mode or thunking? But that should come with acceptable performance to work out for gaming. And it should be tested before dropping support for what's working today.
Last edited by Shmerl on 21 June 2019 at 5:32 pm UTC
Quoting: denyasisIsn't it a bit of an inevitability, though?
Playing devil's advocate a bit here, but, since 32 bit is no longer being pushed, Isn't it just a matter of time before it would be dropped or that future versions of libraries would have incapabilities with our beloved older games and programs?
There are two things to note here. One, by the time something is given up completely, there usually something in place to still run you old things. Dosbox for instance (or dosemu before that). Right now the only thing available is to actually have the 32-bit libs (or a VM, but that's too problematic).
Second problem is Wine specifically. Microsoft was very late in moving over to 64 bit. Windows software even later. So while most things native Linux have moved on, the same cannot be said for Windows. Which is a problem for those using Wine.
I agree that it is inevitable, it's just way too early.
See more from me