Quoting: MohandevirThe bug that quickly comes to my mind, that I personnally witnessed, since switching to Kubuntu, is always happening after an update... Suddenly I can't turn off or reboot the computer. Everytime I get an error message that... I don't remember the name... just crashed. I have to ALT+F4 + CTRL-ALT-DEL to reboot.

If it's the thing I've seen, it's specifically after Nvidia updates. The version mismatch causes the shutdown widget to crash when you try to use it. You can still do sudo shutdown -h now though.

View this comment - View article - View full comments

Quoting: slaapliedjeAlso... why have System menu, and Settings menu, then have System Settings? Should be called Preferences or something...

It's in the specification [External Link]. "Preferences" could be OK for the settings of the system, but that might be confused with preferences for the menu.

View this comment - View article - View full comments

Quoting: AnanaceWait, for that comparison image, are Nvidia saying that a lower resolution image upscaled with DLSS gives a better resulting 4k quality than a native 4k render?

That's what they've said before, and what people have found. For example. [External Link]

View this comment - View article - View full comments

Quoting: win8linuxI've seen the last half of that sentence in particular happen with all kinds of software over the years and there are pretty good chances that it will happen again sometime after this comment.

"I know about computers; of course I should use Arch rather than this 'beginner' distro. 'Remove essential packages'? Do as I say!"

View this comment - View article - View full comments

Quoting: slaapliedjeA good example of this is the clock settings. In Gnome, you can change it in the settings -> Date & Time. It lists 'Automatic Date & Time', or you can manually change it. And Time Zone. And 24 hour or AM/PM.

Then it is smart enough to do the reast based on location.

KDE on the other hand (which it looks like it is better, is still terrible)...
Settings -> Regional Settings -> Date & Time Or Time Zone (they are on separate tabs).

Right-click on the clock widget -> Adjust Date and Time.

View this comment - View article - View full comments

Quoting: omer666I've been using so many desktops over the years I lost count a while ago, but after all these years I finally know what I want: something I don't have to configure for hours. So I prefer GNOME because it fits my needs perfectly and it is very intuitive. I can quickly focus on what I'm working on.

There is functionality that I require from my computer - like being able to set the volume control interval to something other than 6%, or making applications look how I want - that can't be achieved on Gnome no matter how much tweaking I do. Whereas from any distro's KDE defaults I can turn it into what I want with maybe a couple of minutes clicking in the built-in settings application.

View this comment - View article - View full comments

Quoting: Eike"we may sometimes" sounds way less than I expected, to be honest.

Valve wants developers to be stoked about developing for Linux. The softly, softly, "we'll take care of everything," approach that they started with, if they keep doing it too long, will lead developers to expect that Valve will actually take care of everything. Which isn't good enough.

Valve (and us customers) need developers to be actively testing their games on Linux themselves (which is what Valve recommend in their developer documents) and flagging up updates that might have issues. At the same time, they can't launch their new platform with no games tested, and they can't afford to have inaccurate information in their store about the level of functionality. So they have to be the final arbiter (we've already seen too many games saying that they support Linux, but don't actually support Linux), and they have to do testing off their own bat, but they need to use as much carrot, stick, and critical mass as they can to get developer buy-in.

"Build it and they will come" did work to some extent with the Steam Machines, but not nearly enough. So this time they need to steer developers into the behaviour that they want. Hence firm statements of intent but vague specific targets, plenty of extra visibility for games that are playing nice and not specifically saying that games that don't play nice won't get reduced visibility.

View this comment - View article - View full comments

Quoting: rustybroomhandleAhhhh, the "Compatibility Review Process" section was not like that when I last looked at those docs. And this does go against what it sounded like initially, where they hinted at testing the entire library.

One thing that I thought was sensible, given the amount of data that Valve have available about their customers and sales, is that they're feeding the "customers like you love this game" data for customers who've reserved a Deck into their heuristics to decide what to test; the games that people are likely to want to play on the Deck get some priority.

View this comment - View article - View full comments

Quoting: rustybroomhandleI don't think their communication reflects this clearly.

There are three different ways a game can be added to the queue to be reviewed:

• You can manually request a review for an upcoming or a back-catalog title by using the "Steam Deck Compatibility Review" link in the Technical Tools sections of your app landing page. (Note: not all partners have access to the review request tool yet. We're increasing the number of partners with access over time.)


• When a back-catalog title meets certain automated heuristics, it will automatically be added to the review queue with no need for you to submit a manual request. You'll receive a notification when this happens.


• When Valve identifies a game as important to Steam Deck customers, we may sometimes add games to the review queue with no need for you to submit a manual request. You'll receive a notification when this happens.

Steam Deck Compatibility Review Process [External Link]

View this comment - View article - View full comments

Quoting: rustybroomhandleOh! Something that jumped out at me during the talks was about the verification process. Originally when they announced Deck Verified, it sounded like they were proactively testing all games, but something said in the Q&A made it sound like developers have to manually submit games for review. If this is the case, I predict the likes of Ubisoft won't even bother.

Valve are doing it themselves, without requests, as they see fit - because a game is popular or whatever other criteria they want to use - and retesting whenever they feel like it - because of bug reports or whatever. In addition, developers can specifically request that Valve test or retest their games should they want the additional visibility that comes from having the green check mark.

View this comment - View article - View full comments