Latest Comments by dziadulewicz
Hearts of Iron IV: Arms Against Tyranny to focus on Scandinavia and Finland
7 Jun 2023 at 3:24 pm UTC Likes: 1
7 Jun 2023 at 3:24 pm UTC Likes: 1
Finland fought against impossible odds for all of Nordic countries really..
Canonical planning an immutable desktop version of Ubuntu
5 Jun 2023 at 5:13 pm UTC Likes: 1
5 Jun 2023 at 5:13 pm UTC Likes: 1
Quoting: dpanterCanoniclowns.Hmm would You say that to their face in person? Meeting Canonical devs and for example Shuttleworth? It is Ubuntu to thank for fair bit for so much in the world of Linux
Fedora Onyx voted in as a new official Fedora Linux immutable variant
26 May 2023 at 10:58 am UTC Likes: 1
26 May 2023 at 10:58 am UTC Likes: 1
Inspired by this tried Fedora 38. The videos still don't play on Twitch and other video platforms... Even though the codecs were checked to install. Then i tried to go to rpmfusion website as adviced to click those two links https://rpmfusion.org/Configuration [External Link]:
Graphical Setup via Firefox web browser
1. First enable access to the free repository. For users of gpk (gnome package kit) or kpackagekit in Fedora that is easy and basically only one step: just click on one of the following files, depending on what distribution you use and then follow the default options that Firefox and Package Kit offer by clicking Enter a few times (¹):
RPM Fusion free for Fedora 36
RPM Fusion free for Fedora 37
this > RPM Fusion free for Fedora 38
RPM Fusion free for Fedora Rawhide
RPM Fusion free for RHEL 9 or compatible like CentOS
RPM Fusion free for RHEL 8 or compatible like CentOS
RPM Fusion free for RHEL 7 or compatible like CentOS
2. Once that succeeds, you can enable access to the nonfree repositories by clicking on one of the following files, depending on what distribution you use and then follow the default options that Firefox and Package Kit offer by clicking Enter a few times(¹):
RPM Fusion nonfree for Fedora 36
RPM Fusion nonfree for Fedora 37
and this > RPM Fusion nonfree for Fedora 38
RPM Fusion nonfree for Fedora Rawhide
RPM Fusion nonfree for RHEL 9 or compatible like CentOS
RPM Fusion nonfree for RHEL 8 or compatible like CentOS
RPM Fusion nonfree for RHEL 7 or compatible like CentOS
And it made no difference. Youtube plays videos though that's it. I don't know what is Fedora team doing but obviously something is done wrong. Of course at least the videos should play. What other tweaking is the user supposed to do to get the damn videos play? :shock:
Graphical Setup via Firefox web browser
1. First enable access to the free repository. For users of gpk (gnome package kit) or kpackagekit in Fedora that is easy and basically only one step: just click on one of the following files, depending on what distribution you use and then follow the default options that Firefox and Package Kit offer by clicking Enter a few times (¹):
RPM Fusion free for Fedora 36
RPM Fusion free for Fedora 37
this > RPM Fusion free for Fedora 38
RPM Fusion free for Fedora Rawhide
RPM Fusion free for RHEL 9 or compatible like CentOS
RPM Fusion free for RHEL 8 or compatible like CentOS
RPM Fusion free for RHEL 7 or compatible like CentOS
2. Once that succeeds, you can enable access to the nonfree repositories by clicking on one of the following files, depending on what distribution you use and then follow the default options that Firefox and Package Kit offer by clicking Enter a few times(¹):
RPM Fusion nonfree for Fedora 36
RPM Fusion nonfree for Fedora 37
and this > RPM Fusion nonfree for Fedora 38
RPM Fusion nonfree for Fedora Rawhide
RPM Fusion nonfree for RHEL 9 or compatible like CentOS
RPM Fusion nonfree for RHEL 8 or compatible like CentOS
RPM Fusion nonfree for RHEL 7 or compatible like CentOS
And it made no difference. Youtube plays videos though that's it. I don't know what is Fedora team doing but obviously something is done wrong. Of course at least the videos should play. What other tweaking is the user supposed to do to get the damn videos play? :shock:
Microsoft experiments with a handheld Windows 11 mode for Steam Deck
13 Apr 2023 at 2:01 pm UTC Likes: 2
13 Apr 2023 at 2:01 pm UTC Likes: 2
Steam OS is optimized for all things on Steam Deck. Install a "crippled down" version of Win 11: there are no guarantees for anything. Working touchpads, networking etc. Never mind any official support from Microsoft IF someone is to start to process on installing and using Win 11 on Steam Deck.
Looks like Microsoft are out of ideas on stopping freedom and Linux.
Looks like Microsoft are out of ideas on stopping freedom and Linux.
Sci-fi submarine sim Barotrauma floats out of Early Access
17 Mar 2023 at 7:21 pm UTC
17 Mar 2023 at 7:21 pm UTC
Bit expensive but wishlisted!
Canonical want help testing their Steam snap package for Ubuntu
17 Mar 2023 at 7:18 pm UTC Likes: 5
17 Mar 2023 at 7:18 pm UTC Likes: 5
I have started to like Snaps more and more. They work really well now! They also fixed this bug now: https://bugs.launchpad.net/snapd/+bug/1980271 [External Link]
Ubuntu flavours to drop Flatpak by default and stick to Snaps
23 Feb 2023 at 6:46 pm UTC Likes: 6
23 Feb 2023 at 6:46 pm UTC Likes: 6
Please read this response from a developer to understand this decision better. It makes perfect sense and no need to raise pitchforks yet again: https://discourse.ubuntu.com/t/ubuntu-flavor-packaging-defaults/34061/9 [External Link]
"As a developer, it might help to see a bit of the standpoint I have on this issue, as I actually agree with the decision to not include Flatpak by default. I may simply be reiterating what @kewisch has already said, but I don’t have to talk in “official language” so it might be a bit easier to swallow.
It may be easily overlooked, but one of the core features of Ubuntu is that package versions change very, very rarely. If at all possible, bug fixes are taken from the (openly viewable) source code of an application, carefully tweaked to make them compatible with an older version of the software, patched in, tested, and only then deployed. There are a few packages where this is impractical (Firefox for instance), and there are some closed-source packages in the Restricted repo that we can’t backport patches into since we don’t have the code. But for the most part, if you install an app into Ubuntu, that’s the app you get, and that will be the app you continue to use for the rest of that release’s lifespan.
This is a powerful feature since it makes Ubuntu unlikely to randomly break your important data as often as that other OS that you hear get a lot of grief from Linux geeks, but it also requires that Canonical and the Ubuntu community have near-total control over the software repository.
That’s only possible if Canonical actually has the necessary control.
Canonical does have total and complete control over the Ubuntu archive that apt uses. And Canonical has total and complete control over the Snap repository. If something goes wrong and Canonical must step it, they can.
But Canonical has zero control over the Flatpak repositories. They do not host a Flatpak repo of their own (Snap does the near-equivalent job), nor do they control Flathub or any of the other Flatpak repos (at least as far as I know). This means that if something goes awry with a Flatpak, the user is pretty much left to figure it out for themselves.
What’s worse, most of the Ubuntu flavors (and Ubuntu itself) provide free technical support via forums and IRC channels. Most of our users are using software from the Ubuntu repos or Snap Store and we are equipped to help them. We know what to expect from the software our users run and can give targeted and efficient advice on how to resolve issues. Some of us can even kick things into shape in the archives if there’s a legitimate problem with our packages, or we know who to talk to.
With Flatpaks, the situation is much more dismal from a technical support perspective. We have little-to-no clue what quirks the software vendor(s) will have introduced since we don’t work closely with them. We have no way to reach in and fix legitimate bugs aside from filing bug reports and hoping that they will be answered. We’re going to end up with frustrated support staff and even more frustrated users. And all because they didn’t know that if they clicked a particular button in their flavor’s app store, they would be downloading unsupported software.
Yuck. No thanks.
Ubuntu provides plenty enough software for most people in the apt archives and in the Snap Store. In the rare instances that someone needs a Flatpak, they have to go out of their way to enable Flatpak support, which gives them a clue that what they’re doing might not end well. If they enable Flatpak, install an app, it fails, and then they come ask for help, they’ll at least expect it when we say “sorry, we don’t support Flatpaks, that’s why they require extra steps to enable”. They’re exactly like PPAs from an Ubuntu support perspective. And I’m sure we can agree that providing official support for arbitrary PPAs is a bad idea.
That, in a nutshell, is why Canonical and the Ubuntu flavors have gone ahead and agreed to not include Flatpak on the default ISOs, at least as I understand it. As a regular supporter in the IRC channels and many of the Ubuntu-related forums, I heartily agree with this decision.
(For the record, I don’t hate Flatpaks, just like I don’t hate PPAs. In fact I have Flatpak enabled on my personal system and have nn app installed from Flathub that I use. I just don’t expect that the official Ubuntu support venues are going to help me if that app goes berzerk.)"
"As a developer, it might help to see a bit of the standpoint I have on this issue, as I actually agree with the decision to not include Flatpak by default. I may simply be reiterating what @kewisch has already said, but I don’t have to talk in “official language” so it might be a bit easier to swallow.
It may be easily overlooked, but one of the core features of Ubuntu is that package versions change very, very rarely. If at all possible, bug fixes are taken from the (openly viewable) source code of an application, carefully tweaked to make them compatible with an older version of the software, patched in, tested, and only then deployed. There are a few packages where this is impractical (Firefox for instance), and there are some closed-source packages in the Restricted repo that we can’t backport patches into since we don’t have the code. But for the most part, if you install an app into Ubuntu, that’s the app you get, and that will be the app you continue to use for the rest of that release’s lifespan.
This is a powerful feature since it makes Ubuntu unlikely to randomly break your important data as often as that other OS that you hear get a lot of grief from Linux geeks, but it also requires that Canonical and the Ubuntu community have near-total control over the software repository.
That’s only possible if Canonical actually has the necessary control.
Canonical does have total and complete control over the Ubuntu archive that apt uses. And Canonical has total and complete control over the Snap repository. If something goes wrong and Canonical must step it, they can.
But Canonical has zero control over the Flatpak repositories. They do not host a Flatpak repo of their own (Snap does the near-equivalent job), nor do they control Flathub or any of the other Flatpak repos (at least as far as I know). This means that if something goes awry with a Flatpak, the user is pretty much left to figure it out for themselves.
What’s worse, most of the Ubuntu flavors (and Ubuntu itself) provide free technical support via forums and IRC channels. Most of our users are using software from the Ubuntu repos or Snap Store and we are equipped to help them. We know what to expect from the software our users run and can give targeted and efficient advice on how to resolve issues. Some of us can even kick things into shape in the archives if there’s a legitimate problem with our packages, or we know who to talk to.
With Flatpaks, the situation is much more dismal from a technical support perspective. We have little-to-no clue what quirks the software vendor(s) will have introduced since we don’t work closely with them. We have no way to reach in and fix legitimate bugs aside from filing bug reports and hoping that they will be answered. We’re going to end up with frustrated support staff and even more frustrated users. And all because they didn’t know that if they clicked a particular button in their flavor’s app store, they would be downloading unsupported software.
Yuck. No thanks.
Ubuntu provides plenty enough software for most people in the apt archives and in the Snap Store. In the rare instances that someone needs a Flatpak, they have to go out of their way to enable Flatpak support, which gives them a clue that what they’re doing might not end well. If they enable Flatpak, install an app, it fails, and then they come ask for help, they’ll at least expect it when we say “sorry, we don’t support Flatpaks, that’s why they require extra steps to enable”. They’re exactly like PPAs from an Ubuntu support perspective. And I’m sure we can agree that providing official support for arbitrary PPAs is a bad idea.
That, in a nutshell, is why Canonical and the Ubuntu flavors have gone ahead and agreed to not include Flatpak on the default ISOs, at least as I understand it. As a regular supporter in the IRC channels and many of the Ubuntu-related forums, I heartily agree with this decision.
(For the record, I don’t hate Flatpaks, just like I don’t hate PPAs. In fact I have Flatpak enabled on my personal system and have nn app installed from Flathub that I use. I just don’t expect that the official Ubuntu support venues are going to help me if that app goes berzerk.)"
Wine 8.2 rolls out along with a new Proton Experimental update
17 Feb 2023 at 9:17 pm UTC
17 Feb 2023 at 9:17 pm UTC
Nowadays i don't know should i install this normal Wine, or should i use Lutris? But, when i tried Lutris: there is no "normal Wine" available to choose from at all but all kinds of customised or "unofficial" Wines.
There is no flatpak or a snap for Wine either (if there was, users could run Wine happily in a sandbox without any fear?)
There is no flatpak or a snap for Wine either (if there was, users could run Wine happily in a sandbox without any fear?)
The Force Engine for Star Wars Dark Forces improves Steam Deck & Linux support
17 Feb 2023 at 8:46 pm UTC
The output:
17 Feb 2023 at 8:46 pm UTC
Quoting: KlaasOr take a look at the second comment https://www.gamingonlinux.com/2023/02/star-wars-dark-forces-source-port-the-force-engine-adds-linux-support/I can't get it to install either.
The output:
git clone https://github.com/luciusDXL/TheForceEngine.git
Cloning into 'TheForceEngine'...
remote: Enumerating objects: 19062, done.
remote: Counting objects: 100% (661/661), done.
remote: Compressing objects: 100% (390/390), done.
remote: Total 19062 (delta 397), reused 484 (delta 264), pack-reused 18401
Receiving objects: 100% (19062/19062), 48.32 MiB | 1.04 MiB/s, done.
Resolving deltas: 100% (14354/14354), done.
cd TheForceEngine
~/TheForceEngine $ mkdir build
~/TheForceEngine $ cd build
~/TheForceEngine/build $ cmake ..
-- The C compiler identification is Clang 14.0.6
-- The CXX compiler identification is Clang 14.0.6
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: /usr/bin/clang
-- Check for working C compiler: /usr/bin/clang - broken
CMake Error at /usr/share/cmake-3.24/Modules/CMakeTestCCompiler.cmake:69 (message):
The C compiler
"/usr/bin/clang"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: /home/user/TheForceEngine/build/CMakeFiles/CMakeTmp
Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_772f0/fast && /usr/bin/gmake -f CMakeFiles/cmTC_772f0.dir/build.make CMakeFiles/cmTC_772f0.dir/build
gmake[1]: Entering directory '/home/user/TheForceEngine/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_772f0.dir/testCCompiler.c.o
/usr/bin/clang -MD -MT CMakeFiles/cmTC_772f0.dir/testCCompiler.c.o -MF CMakeFiles/cmTC_772f0.dir/testCCompiler.c.o.d -o CMakeFiles/cmTC_772f0.dir/testCCompiler.c.o -c /home/user/TheForceEngine/build/CMakeFiles/CMakeTmp/testCCompiler.c
Linking C executable cmTC_772f0
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_772f0.dir/link.txt --verbose=1
/usr/bin/clang CMakeFiles/cmTC_772f0.dir/testCCompiler.c.o -o cmTC_772f0
ld.lld: error: cannot open crtbeginS.o: No such file or directory
ld.lld: error: unable to find library -lgcc
ld.lld: error: unable to find library -lgcc
ld.lld: error: cannot open crtendS.o: No such file or directory
clang-14: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[1]: *** [CMakeFiles/cmTC_772f0.dir/build.make:100: cmTC_772f0] Error 1
gmake[1]: Leaving directory '/home/user/TheForceEngine/build/CMakeFiles/CMakeTmp'
gmake: *** [Makefile:127: cmTC_772f0/fast] Error 2
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:11 (project)
-- Configuring incomplete, errors occurred!
See also "/home/user/TheForceEngine/build/CMakeFiles/CMakeOutput.log".
See also "/home/user/TheForceEngine/build/CMakeFiles/CMakeError.log".
10 years ago Steam released for Linux
15 Feb 2023 at 2:16 pm UTC
15 Feb 2023 at 2:16 pm UTC
I suppose one cant really get that achievement though. I didn't get that dialog though ive been from the start.
- Nexus Mods retire their in-development cross-platform app to focus back on Vortex
- Windows compatibility layer Wine 11 arrives bringing masses of improvements to Linux
- GOG plan to look a bit closer at Linux through 2026
- European Commission gathering feedback on the importance of open source
- Hytale has arrived in Early Access with Linux support
- > See more over 30 days here
- Venting about open source security.
- LoudTechie - Weekend Players' Club 2026-01-16
- Mustache Gamer - Welcome back to the GamingOnLinux Forum
- simplyseven - A New Game Screenshots Thread
- JohnLambrechts - Will you buy the new Steam Machine?
- mr-victory - See more posts
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck