Check out our Monthly Survey Page to see what our users are running.
Latest Comments by F.Ultra
Check out the new demo for Casebook 1899 - The Leipzig Murders
31 May 2022 at 11:53 am UTC

Looks a bit like The Slaughter: Act One, I hope the dev will make Act Two some day now (6 years in the making).

An interview with Ken VanDine, Ubuntu desktop lead at Canonical
25 May 2022 at 12:23 am UTC Likes: 2

Quoting: Eike
Quoting: ShabbyX
Quoting: Lycurgus87And learn to use your system, because probably (about 99%) you are the problem, not your machine, nor the software.

Oh no no no, never say that. Take any device (a computer, a door, a hose, whatever), and if most users have trouble using it, that's definitely a design flaw of the device.

Here, see this:

At work we've got, on a single walk through a single floor, doors that
* are just opened manually,
* must be opened manually, but only after you show your entrance card to some device,
* open automatically after you show your entrance card to some device, and must not be moved by the handle they've got, because otherwise, most probably, world explodes.

Please, if you constructed a door so stupidly that it must not be moved by its handle, AT LEAST DON'T GIVE IT A FU**ING HANDLE!

Probably designed by the same geniuses that designs the self scanning check out stations that have a touch screen and then either a IR reader for a card (drivers license in this case) or VISA/Mastercard touchless reader and if you accidentally scan your card before touching the screen it locks with a "you must touch the screen to begin before you scan your card". Ok so why is the damn scanner even active before I touch the screen if this is so important and secondly why is it so important?

Not to mention how completely AI-less they are, here I am using a machine that requires me to have a visa card (which the banks over here only hands out if you are 18+) and have the shop member card (which again they only hand out if you are 18+) and I have bought stuff for say €200 but I no I also have bought a few energy drinks (which the store on it's own have decided to have a 15 age limit on) so now it have to blink red until some underpaid clerk 15 minutes later can come to my aid and logon, click "age verified" so I can continue.

Because the modus operandi of some pre-teen wanting to buy an energy drink (which is not illegal. again the age limit is set by the store) is to steal some one else visa card, their store membership card and then also spend €200 on other stuff...

An interview with Ken VanDine, Ubuntu desktop lead at Canonical
25 May 2022 at 12:10 am UTC

Quoting: mirvTo be fair, I've had continued problems with PulseAudio that were entirely resolved by purging it from the system and relying on ALSA more directly, or using apulse as PA proxy. These were not ALSA driver problems, these were "no sound, no possibility to get sound, pulse was seemingly doing whatever the hell it wanted regardless of configuration or attempts to restart the service". My favourite was ignoring the mono sink and outputting to speakers that didn't exist.
While your problems very much could be related to pulse (I do not want to convey the idea here that it's the most bug free software out there [somewhat due to the complex nature of the problem it is trying to solve which pipewire have demonstrated since some people for whom pulse worked perfectly well pipewire doesn't at all]) even problems like this could be due to errors on ALSA; the whole architecture in pulse depends upon the rewind functionality of ALSA, something that no other software uses and it turned out that a lot of drivers therefore also had massive problems with it (aka completely untested feature in the drivers). Granted one can blame pulse for using that feature when it was so badly supported.

Quoting: mirvAnd true enough that internal QA cannot hope to cover all the myriad configurations and setups out there, there was still a level of rolling out that could have been handled better. A response to buggy software by saying what is akin to "deal with it" will never sit well with me.
If that indeed was the answer then yes that is both a horrible and idiotic answer. Just like you I would be without customers if I had that attitude (basically also why we gain customers from competitors, but I digress).

Quoting: mirvI am, however, rather concerned about the code complexity and just how susceptible it is to security flaws, especially given the level of control over the rest of the system.
And I would argue that the old way with lines upon lines of bash scripts was a way more complex and error prone world. But yes there will always be a tradeoff between functionality and more chance of security problems due to more lines of and more complex interactions of code. And there are no objective truth here, myself I subjectively like the features more than I'm afraid over the added complexity, others are free to do a different tradeoff analysis and that is of course fine.

Quoting: mirvSure, security flaws are elsewhere too, but I'm one who suscribes to the old unix philosophy of keeping everything as simple as possible, do one thing and that one thing right, and systemd does away with that. I'm also against the kind of spread of scope - there's software that now relies on systemd (init) that ideally shouldn't have to know about the init system at all.

Does those softwares really rely on the systemd as init or are they relying on some D-BUS interface provided by various applications in the systemd project? In any case this is of course due to the project providing functionality and services that other software writes find useful, I get that it sucks for people not wanting to run systemd or not wanting to write software providing similar functionality using the same D-BUS namespace but at the same time should be forbid developers from providing great features?

Quoting: mirvI've also personally suffered systems that refused to boot because systemd wasn't recovering properly. Root cause was not systemd, but it was clobbered far too easily and locked up everything else. On non-init, I've had problems with logging, I don't even know what was going on with timesync and ended disabling the entire damn thing until a full OS reinstall was done, and a bunch of other problems that probably bias me against the whole project.
I can see how such a situation can be frustrating enough to be mad at the entire project, I've had similar experience with various pieces of software (hello macOS) that made me hope that they would freeze in hel. The irony of it all though is that if something, systemd brought excellent logging to Linux with the journal (I'm not a friend with how it handles tab-completion though) so unfortunate that we don't have a time machine so we could get back to your machine with the systemd-timesyncd so figure out what it was, perhaps sitting behind the machine the both of us would have showed you exactly why I like systemd and how I see the journal as a life save. Or the result would have been the same, who knows when it comes to software :)

In any case I asked for your reasons and I thank you for providing them. I fully understand that you don't want to make this into a debate and I see no reason for it to be that either. As I said I was simply interested in your experience since you sounds like a sane person (you don't want to know how many insane anti-systemd people I have talked to on Slashdot or Phoronix over the years) and I'm glad that I was right :).

An interview with Ken VanDine, Ubuntu desktop lead at Canonical
24 May 2022 at 1:54 pm UTC Likes: 1

Quoting: mirv
Quoting: Eike
Quoting: scaineb) I wondered if it was just Poettering-hate.

That was my impression as well.

And while I can't say much about this person, in general I'm of the opinion that social competence does matter, not only technical one, as open source should be about working together.

Actually I think this was the core of the problem. PulseAudio was not ready for primetime, but it was forced upon everyone, and it had (has) some major issues - which is why pipewire is taking over.
Systemd has some design decisions that I personally find design flaws, and was something similar - pushed on people, and then grown to encompass more functionality than emacs. I think by now it's probably stable enough to be acceptable (I still won't allow it on my rig), but you're absolutely correct - had there been more social competence, more engagement with the community, perhaps the drama would have been less or avoided.

I still recall a talk, I forget by who, where a question was asked about the instability of systemd at the time, and the response was "oh but it's software and that happens". That kind of response was indicitive of a software engineer who obviously doesn't care about professional development and probably hadn't heard of test suites and CI setups. It did not inspire confidence in any project they were involved in.

Yes pulse was pushed out by Ubuntu before every single ALSA driver (the main problems lied with the ALSA drivers and not with pulse itself) worked great with it, but then if one want's to hold off a new piece of software until it's perfect then you have to hold it off indefinitely. As someone that works in the software industry (kinda), the real QA only comes once you have released the version in the wild, until then you can do all sorts of crazy tests and still the first customer will find 1000 ways to crash it. Just look at how often MS have to go back on their updates to Windows 10/11 because it breaks things for end users and don't say that MS doesn't spend millions on QA.

systemd was pushed on users by distro maintainers since they saw the extreme benefits it had for them over sysv. I would very much like if you could find that interview though because AFAIK instability have never been a case for systemd, it working as a replacement for init have been rock solid since day one.

comparing it with emacs is reaching to be honest, it's not systemd the init replacement that have grown functionality, it's systemd the project (that consists of several binaries) but it's easy to conflate the two due to them using the same name and the systematic denial to see them as separate things by the anti-systemd people.

Would be interesting to hear what you think are design flaws in systemd, not to start some flame war but to hear what your thoughts are. I'm not a systemd dev so have no stake in the design choices.

An interview with Ken VanDine, Ubuntu desktop lead at Canonical
23 May 2022 at 6:02 pm UTC Likes: 5

Quoting: scaine
Quoting: SoltrummanAs a Ubuntu user since 06.06 snaps are probably the biggest misstep up there with MIR and we all know how well that NiH-project turned out.

I've covered before how ridiculous calling things "NIH" is. It's literally how Linux evolves and becomes better. Weird that Canonical gets hate for that, but no-one bats an eyelid when Redhat decide to replace the entire sound system, or indeed, the entire fucking init system.

While I basically agree with your post as such this last part does not compute at all. Just like Canonical, Red Hat got a lot of irrational hate for pulse and systemd to the point that it now have become a conspiracy theory of it's own where evil Red Hat in cahoots with eviler IBM are working behind the scenes for total world domination of Linux systems by replacing sysvinit with systemd...

But it still proves your point, many times, if not close to frickin always, when some one does something new or different in Linux it will always bring out the Knights of NIH on forums.

I'm a huge defender of DEB over any of these new forms of distribution package formats due to the inherent problem of embedded libraries, overhead, security issues and so on. That said, snap is probably the better one of them due to the sand-boxing (which have unfortunate side effects for desktop users that are used to be able to compromise their entire system from within Firefox) and Firefox is also most likely the perfect candidate (and so is Steam and games) for such a distribution format since Firefox embeds so many special versions of otherwise shared libraries anyway that there are basically no benefits of using a DEB (with my concerns) unless of course on would have managed to unbundle those libs for Firefox but as I have written before it would probably be easier to solve world hunger and peace (not to mention much better benefit for humanity).

Quoting: RandomizedKirbyTree47
Quote"Anyone can create an alternate store that supports snaps. The API is completely open as is snapd.
Can you have multiple Snap stores configured on the same system? If so, great. If not, this seems like a bad-faith argument.

You can have multiple APT repositories on the same system together: if you want one deb package that isn't in the main repository, you can add another repository without losing access to the stuff in the main repository. Likewise, you can have multiple Flatpak remotes available on the same system.

Last time I checked, I couldn't figure out a way to do this with Snap. So while someone could theoretically make another snap store, no one could use it unless they completely gave up the ability to use Canonical's store. That's a <i>massive</i> barrier to entry for any potential new store, and it also means there's no way to add a store just for a few apps that Canonical doesn't like. Unless I am mistaken and it actually is possible, in which case I would be grateful if someone corrected me.

It sort of feels like if Meta said "WhatsApp isn't a closed ecosystem! The Signal Protocol is open source, so anyone can make another messaging service similar to WhatsApp." While it is possible to make another messaging app with the signal protocol (including Signal itself), the lack of federation means new messaging apps can't communicate with the 2 billion+ people on WhatsApp.

For now, this isn't a serious issue, because Snap can coexist with all the other package formats. It will only become an issue if Snap ends up becoming the dominant means of distributing apps on Linux.

What he means is that it's possible for anyone to write their own competing snap utility that supports their own store, or to create their own fork of snap that supports both Canonicals store and 3d party stores. There are no requirement that a 3d party snap store use the /usr/bin/snap binary.

Canonical seek Software Engineers for the 'Ubuntu Gaming Experience' team
20 May 2022 at 6:14 pm UTC

Quoting: ElamanOpiskelija
Quoting: scaineSeparately, I work in Finance, and you'll never, ever, get salaries even mentioned until the second round of interviews, unless the position is (extremely) senior. It doesn't even come up in first-round interviews.

Happy GOL cake day, person on the internet!

A bit off-topic, but I believe salaries should always be mentioned as soon as possible. Lots of time and effort would be saved.

It would, however for all the jobs that I've ever applied the salary has always been a negotiation.

Wolfire versus Valve antitrust lawsuit to continue
11 May 2022 at 7:15 pm UTC Likes: 1

Quoting: eldaking
Quoting: CatKiller
Quoting: TermyI'm just confused that the judge didn't ask for any sort of evidence (which wolfire wouldn't be able to provide of course) - guess he wants to keep enough work for the court going? ^^
Quite the opposite. This is a motion to dismiss, which is to get cases sorted out quickly (and cheaply for the parties). In a ruling on dismissal, the judge assumes that everything the plaintiff says is true, and then sees if there's a reasonable likelihood that they could win: if not, the case gets thrown out. Which is how it got thrown out before. That time, the judge let Wolfire amend their complaint and try again, which is how we're at this point where the case has mostly been thrown out.

Seeing if what the plaintiff has said is actually true comes later.

So it was pretty much a case so stupid that even if Wolfire could prove absolutely everything they would lose, so the court wasn't even bothering, and now it is a case of "if they can get proof then maybe, so I guess we have to do it".

Basically yes, now they will soon enter discovery which is the phase where either party will ask the court to force the other party to hand over private information.

Wolfire versus Valve antitrust lawsuit to continue
11 May 2022 at 2:44 pm UTC Likes: 1

Quoting: Mountain Man
Quoting: mirvIt isn't about selling steam keys cheaper elsewhere, it's about selling a (non-steam) game elsewhere cheaper has threats to delist the game on steam. It seems the judge has ruled that this is a plausible scenario, and is thus allowing the case to proceed.

The judge is not saying it's happening or not. Just that it's possible, and so a trial can proceed to determine the matter.

Wolfire was supposedly told that Valve will "delist any games available for sale at a lower price elsewhere, whether or not using Steam keys", which is demonstrably false.

What I want to know is if Wolfire changed their allegations or if this is just a change in reporting. In their initial complaint they claimed that they had heard this from a 3d party that they would be delisted from Steam of they added their game to a Humble Bundle with discounts. But now it's being reported as Valve telling this directly to Wolfire.

Embracer Group to acquire Eidos, Crystal Dynamics and Square Enix Montréal
2 May 2022 at 9:08 pm UTC Likes: 10

I think you people are a bit to negative here. Fully understandable with the experience from EA and other big firms but Embracer Group, at least so far, looks to be genuinely interested in producing games and having the studios run independently.

In their Annual Reports each studio is presented individually with a list of what games they currently sell and what they are working on for the future, zero mentioning of "consolidation goals" or "business optimization". I also note that they buy studios by way of share issues so each studio becomes shareholders of Embrace Group.

They are also no big venture capital owners of the company, 61.12% of the votes are owned by 3 people Lars Wingefors from Nordic Games (that became THQ Nordic that become Embracer) and Matthew Karch and Andrey Iones that founded Saber Interactive.

QuoteIn my belief, a key factor to our success is that entre-
preneurs who become part of Embracer maintain their
creative and operative freedom while they can go faster
and boost their growth by being docked into our growing
eco-system and available resources. We are steadily
seeing more cooperation between the independent oper-
ating groups – for the simple reason that it makes sense
for everyone. We hope that access to the Embracer eco
system will be an even more decisive reason when gam-
ing entrepreneurs chose to become part of the Embracer
family in the future.
Lars Wingefors
Co-founder & CEO

Canonical going 'all in' on gaming for Ubuntu, new Steam Snap package in testing
1 May 2022 at 11:55 pm UTC

Quoting: slaapliedje
Quoting: F.Ultra
Quoting: slaapliedje
Quoting: user1
Quoting: scaineThat's a great turnaround from a few years ago, when the threatened removal of 32-bit libraries would have crippled the O/S from a gaming perspective.

A better gaming experience in what is still an incredibly popular "entry" distro is superb news.

You know what I think? Making a SNAP Steam is exactly the first step towards removal of the last few remaining 32 bit libraries in Ubuntu (the original plan was to remove ALL 32 bit libraries, but because of backlash, the final decision was to keep a few 32 bit libraries used by popular software). I mean think about it, Steam and Wine are the 2 most popular pieces of software that still require 32 bit dependencies. By making a SNAP Steam, Canonical will then be able to proceed removing those remaining 32 bit libraries (and also removing .deb Steam in the process). Regarding Wine, I heard it's also available as a Snap.

I'm surprised nobody here is asking himself the question what is even the benefit of having a SNAP Steam, when .deb Steam is working perfectly?
So to me it seems that in the case of creating a SNAP Steam, Canonical is just masquerading itself as "caring about gamers", but under the hood it's just part of the plan to remove the final remaining 32 bit libraries and push their SNAP garbage.

I'm so tired of Canonical's bull**** and so glad I've switched to Fedora after a few years of mainly using Ubuntu based distros.
I stopped using Ubuntu before it was cool to do so.

Ha, they stopped being relevant to me when the changed their 'let's be Debian, with the latest Gnome and 6 month release cycles to match Gnome's purpose they had at the beginning.

I am positive their push for ditching 32bit support was because they figured if Apple could do it, why can't they? There is no technical reason for Ubuntu to do so, unlike for Apple as they knew they were moving toward ARM... pretty sad to see the amount of native mac games that won't run after Mojave.

Someone mentioned Arch ditching 32bit support? Pretty sure they have always had the separate multi architecture repo, similar to Debian needing to add it in.

There are actual programs that simply can't be ported to 64bit (or it would take some significant effort" so dropping it is the equivalent of trashing all that past work. Part of why there are software preservation groups these days.

Of course there are technical reasons for ditching 32-bit support (I'm a maintainer for the software my company distributes and I decided to ditch 32-bit support due to technical reasons). It takes time and resources to build an entire arch of your distribution, on top of which you have to provide actual support, for an arch where you have very few users. That Canonical reversed their decision when there was a backlash indicates to me that they simply didn't understand the need for 32-bit libs to support games, they obviously only thought that it was about running Ubuntu on 32-bit hardware.
Those aren't technical reasons. Those are resource reasons.

True, got me there, does it matter though? The point I was trying to make is that they had reasons which was not "let's screw gamers and Steam".