Quoting: chancho_zombiethere might be a time were removing 32bits would be a good decision, now it's not that time. There is still 5% of pc users that use windows xp, how many of those machines are 32bits?? 5% is a lot more than all the Linux userbase.

Thing is, almost everyone was thinking like you. But what they intended was not dropping support for 32 bit machines, but to drop ability to run 32bit software an 64bit system. Like 95% of Linux games, for example

View this comment - View article - View full comments

Quoting: F.Ultra

Quoting: eldaking

Quoting: F.UltraNo I didn't say that others did such stuff all the time. What I said was that in the real world companies announce their plans, then they await comments from users and partners to see how said plans will be received after which the plans are either amended or put into production.

The problem here is that the Linux fanbase decided to see the announcement of plans as a foregone conclusion and then run around screaming.

When they "announced" this years ago, did they set a date? Was it fully decided and plotted out? How much did they broadcast their intentions so that people could prepare their transition?

Or was their announcement now still just a "plan" to be discussed, despite the fact the changes takes effect in a few months?

Everyone was surprised by this because information was not communicated clearly enough and in advance enough. Yeah, we are probably overstating the impact... but this a panic Canonical created.

Here is the initial announcement from last year: https://lists.ubuntu.com/archives/ubuntu-devel/2018-May/040310.html [External Link] so it was just one year ago and not years as I first claimed (shame on me there).

edit: further research shows that they also made an announcement back in 2016: https://lists.ubuntu.com/archives/ubuntu-devel/2016-June/039420.html [External Link]

Basically, they said in 2016: "What do you think is appropriate?"
In 2018 as i understand they talk about dropping i386 images- not whole legacy 32 bit support, at least in your linked post
In 2019 we get: BANG!, you have 4 months to prepare your software/game/library for 64-bit only Ubuntu. You need 32 bit? Stay on older system until it runs out of support.
There was never a plan to migrate software. There was discussion about dropping, but until recently we had no timelines or guides how to prepare. That's not fair.

View this comment - View article - View full comments

Quoting: Nevertheless

Quoting: Gryxx

Quoting: Nevertheless

Quoting: x_wing

Quoting: Luke_NukemI just purged all *386 libs from my install, including Steam. Then installed Steam via flatpak...

No. Issues. At. All.

But this doesn't solve HumbleBumble or GOG. Though I do seem to recall and automated GOG->flatpak creator?

And what about proton games? Do they work without problems?

I have no problems at all.

So, how you can install games to non-system drive? As i recall, flatpak Steam is isolated from the rest of OS. You cannot go out of flatpak's file system.

EDIT: Without changing location of Steam, of course. For example leave Steam (and some games) on SSD and keep rest of them on two separate HDD drives.

You can do it with a flatpak override like described here:
https://askubuntu.com/questions/1086529/how-to-give-a-flatpak-app-access-to-a-directory [External Link]

or you can mount partitions into the [edit: Steam flatpak] packages folder.

But as i said earlier in replay- you can't compare it to "native" solution. These are like 5 clicks or so, not mounting disks manually or changing flatpak permissions.

View this comment - View article - View full comments

Quoting: poiuz

Quoting: GryxxSo, how you can install games to non-system drive? As i recall, flatpak Steam is isolated from the rest of OS. You cannot go out of flatpak's file system.

You can configure the sandbox (I don't think there is a GUI, yet): Flatpak Sandbox Permissions [External Link]

You can put your Flatpaks anywhere you want, too: Flatpak installation [External Link]

"Nice" "upgrade" from "Create stem library on XXX"

View this comment - View article - View full comments

Quoting: Nevertheless

Quoting: x_wing

Quoting: Luke_NukemI just purged all *386 libs from my install, including Steam. Then installed Steam via flatpak...

No. Issues. At. All.

But this doesn't solve HumbleBumble or GOG. Though I do seem to recall and automated GOG->flatpak creator?

And what about proton games? Do they work without problems?

I have no problems at all.

So, how you can install games to non-system drive? As i recall, flatpak Steam is isolated from the rest of OS. You cannot go out of flatpak's file system.

EDIT: Without changing location of Steam, of course. For example leave Steam (and some games) on SSD and keep rest of them on two separate HDD drives.

View this comment - View article - View full comments

instead they've oddly decided to split them in two

Good, they are not going to make second Facebook out of it. That app is amazing at wasting resources.

View this comment - View article - View full comments

Quoting: Guest

Quoting: WernerDay ~2237 Windows free :D^_^

but Welcome :)

It's nice here ^_^

How are you dealing with left control being non assignable?

EDIT: I mean in Overwatch

View this comment - View article - View full comments

I may just buy it at launch then. If they won't drop Linux support in the meantime, of course.

View this comment - View article - View full comments

Personally, I really like this game. Even without multiplayer vechicles and Steam Worksop are enought to keep me busy. I just wish that i can use machines in creative- without it making and testing vechicels is so much harder

View this comment - View article - View full comments

Someone can confirm that it is still locked by EAC to *buntu family? I'm particularly interested in OpenSUSE.

Spoiler, click me

3G internet sucks

View this comment - View article - View full comments