I don’t have any idea about your hardware issues. They’re likely unrelated if the game has already been played without issue.
For the steam diagnosing, start with running steam from your terminal, by running steam. You may get lucky and the error is clearly identified in the console.
If that fails, backup $HOME/.local/share/Steam/steamapps/compatdata/221100 - the 221100 is the app ID of of DayZ on the steam store. After backing it up, delete the original 221100 directory and re-launch the game. This doesn’t delete the game, but rather deletes the Proton prefix for the game.
If the game launches, copy any save files (if any) you may have in the backed-up 221100 directory over to the new one.
The above worked for me when I had similar issues when playing Batman: Arkham Asylum.
To be thorough, have you tried any other games to rule out your hardware being an issue?
The logs say error on Vulkan, make sure your GPU is running with the correct drivers. If it’s a Vulkan thing old native games that use OpenGL should work, I think Team Fortress 2 is OpenGL but I’m not entirely sure.
I’m sorry I just don’t know how to check any of that. These are the GPU drivers I’m using (I think) The game worked just fine for several weeks with these drivers.
You can install vulkan-tools (ubuntu package name - not sure if it’s the same for your distro) and running vkcube. It’s a simple vulkan app that will display a rotating cube using vulkan. It will also spit out the GPU that it’s running on.
If it reports your nvidia card and the cube looks good then your drivers may be fine and the issue is with Steam and/or this application specifically. If not then there’s an issue with your drivers.
Occasionally when I’ve had a kernel update or something the nvidia drivers have gotten borked. Removing, re-installing, and rebooting has helped. Something like this:
Oh damn, you’re using the snap version of Steam, this is unfortunately outside of my area of experience :(
Some key error messages I see are:
<span style="color:#323232;">/home/pokko/snap/steam/common/.local/share/Steam/ubuntu12_64/steamwebhelper.sh: line 53: /proc/sys/kernel/unprivileged_userns_clone: Permission denied
</span><span style="color:#323232;">/home/pokko/snap/steam/common/.local/share/Steam/ubuntu12_64/steamwebhelper.sh: line 60: /proc/sys/user/max_user_namespaces: Permission denied
</span>
and
<span style="color:#323232;">flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13vkEnumeratePhysicalDevices failed, unable to init and enumerate GPUs with Vulkan.
</span><span style="color:#323232;">BInit - Unable to initialize Vulkan!
</span>
You’ve got permission errors and a GPU driver issue somewhere, likely related to the permission errors. The flock errors stand out to me also, as they are fonts. Maybe required fonts for the game to run?
I’m not trying to steal hollyberry’s job here but here is my understanding of snaps (and why they aren’t good).
Snaps were created by Canonical (The company behind Ubuntu) to fix the issue of inconsistent dependencies. The problem with the format is that the market is proprietary and they just aren’t very good. Also they perform somewhat worse than Appimages and Flatpak.
Personally I reccomend you look into Flatpak, as it’s a better sandboxing format than snap is.
Also the reason you ended up with the SNAP version of steam is because Ubuntu prioritizes the snap version over the native version when using
Yeah I installed Steam using the Ubuntu app store. Now I’m trying to uninstall it but it’s been going on for an hour and doesn’t seem to be progressing anywhere.
I’m sorry you’re having such a bad experience. It should be as simple as uninstalling in the Ubuntu store, and then reinstalling either using apt or flatpak. Is the uninstall not working?
I need no try again. The uninstall failed the first time. It got stuck at 80% or so. I’ve had so much issues with Linux from the start that I’m getting suspicious about wether it’s a hardware issue.
The uninstalling issue almost certainly isn’t hardware related, Ubuntu’s app store is just a pile of hot garbage. Stuff like that happens all the time, or at least that was my experience years ago when I used Ubuntu, one of the (many) reasons I no longer recommend Ubuntu to new users.
As for the Steam issues, it’s probably a mix of software and hardware issues. It seems there are some permissions issues (likely caused by snap), but it also seems like there are GPU driver issues. What GPU do you have? If you have an Nvidia card, have you installed their drivers? There is also a very real possibility that your card is so old that DayZ is no longer compatible with it (which may be the case given that it wasn’t working in Windows, but to be fair Windows 7 is incredibly out of date and doesn’t receive updates so it could have also been a software/driver issue there).
My GPU is just a few years old GeForce GTX 1660 SUPER and I just updated the drivers from 535 to 545 but no difference. However I’ve gotten a prompt saying that Steam needs nvidia-driver-libs:i386 so I’m not sure if I should install that instead or in addition to the ones I already have.
I still haven’t been able to uninstall steam snap(?) either. I’d like to try the non-snap version using terminal but I don’t know how to proceed. I’m sorry I’m such a novice with Linux. I’m feeling like my replies are really unhelpful.
EDIT: No luck trying to install the other drivers. All I got is this:
If you were to open the Software & Updates app and go to Additional Drivers, does the driver package you tested say it comes from Nvidia and it is “(proprietary, tested)”? If so, then your drivers should be fine. nvidia-driver-libs:i386 is 32-bit, so I don’t know why you would need that installed unless DayZ is only compatible with 32-bit drivers for some reason. I have Steam installed on my Fedora install, and I don’t have any 32-bit Nvidia drivers installed but everything works perfectly. That’s a separate issue altogether, and I don’t recommend running 32-bit drivers unless your system is 32-bit. Can you copy the “System Details” window in the About tab of the Settings app? It should have Hardware and Software information like the CPU, GPU, windowing system, etc. There are a few things that could cause issues that I might be able to glean from that.
I’m on Fedora, but since it’s running Gnome it should theoretically look the same. You access the system details here:
And assuming that works, to install the native version of Steam (which should be what’s installed anyway, but Canonical is pushing their proprietary snap BS that has never worked well), this should apparently work (I don’t have an Ubuntu install to test on though):
If it prompts you for anything, you can just confirm by typing “y”. I’d recommend you check that it isn’t installing the snap version, but I don’t know how to guide you to do that, really. I haven’t used a distro with the Aptitude package manager in over 5 years.
Of course, it probably isn’t helpful, but I’d recommend avoiding vanilla Ubuntu if you aren’t already too deeply invested. Linux Mint seems to be a common recommendation for new users and it’s based off Ubuntu, but in all honesty I’d probably recommend Nobara (gaming focused and more user friendly version of Fedora). That way you don’t get snaps shoved down your throat by Canonical, which break things constantly. Up to you if you want to install another OS though; in theory you shouldn’t need to, and there should be a way to resolve these issues with your current install.
Yeah the unistallation gets stuck with terminal aswell. It managed to break steam so it no longer opens but wont remove it either. Guess I’ll just try and install it again via terminal nevertheless.
That should skip the data backup when removing. I’ve seen reports of other users that this backup process sometimes takes 10-20 minutes with the default remove command, even with small programs. Blame Canonical for that one.
I wonder if this command would clear out the remaining files from the snap install that appears to have been left behind? Since the game is now working I’m afraid to tweak anything more so that I don’t mess it up again
No, it wouldn’t since the steam snap isn’t installed anymore. But you can clear out the left over snapshot of it manually. Just use sudo snap saved, find the entry that says steam, and sudo snap forget
If there is no steam entry listed, then there’s nothing else you have to do.
The drivers I had before were proprietary and tested but the ones I updated to now (545) are just proprietary. Earlier I got this message so that’s why I’m trying to install the 32 bit drivers too though it worked just fine before without them.
By the way, if you still have issues after the native Steam install and it gives you the same 32-bit driver warning, you should be able to resolve it with the following:
That is of course assuming that the error message you pasted in another thread gave the correct package name, which is not a guarantee. It should have automatically been installed as a dependency to Steam if it was installed through apt though, so I don’t feel like that will necessarily be a solution.
Yeah I actually saw that on an article while googling about it. I ran the code but haven’t managed to test it yet. Trying again with the different steam version in a moment. I think I saw something about i386 scroll by while it was installing.
I spun up an Ubuntu VM, and while it won’t have Nvidia drivers listed (since it doesn’t have GPU passthrough), this should be similar to what you should have seen when installing:
Pretty much all those are i386 packages (32-bit), so you shouldn’t need to enable the architecture in your version of Ubuntu, it should automatically happen (I didn’t need to use sudo dpkg --add-architecture i386). Of course I did this on Ubuntu 22.04 because it’s a VM I already had, but it should be very similar to 23.10
that would be really weird. snap install firefox or clicking “Install” in Ubuntu Software installs the snap, apt install firefox installs from the apt repositories
You will get tons of distro recommendations, so here is one more: OpenSUSE, then use the YAST GUI GTK application select Yast Printer it has a GUI tool for all kinds of printer setup options and will show recommended drivers based on printer type, it then installs them via that GUI. Not to be confused with the regular printer settings app you see in most distros.
How long ago? Everyone has an opinion and preference, but SUSE and RHEL are the only two certifed distros for corporate/ enterprise use of Teamcenter PLM and NX CAD…so it cannot be as “badly” built as you feel it is because it has to perform everyday with the least amount of issues.
I honestly believe Red Hat has a policy that everything should pull in Gnome. I have had headless RHEL installs and half the CLI tools require Gnome Keyring (even if they don't deal with secrets or store any). Back in RHEL 7, Kate the KDE based Text Editor pulled in a bunch of GTK dependencies somehow.
Certification is really someone paid to go through a process and so its designed so they pass.
Think about the people you know who are Agile/Cloud/whatever certified and how all it means is they have learnt the basic examples.
Its no different when a business gets certified.
The only reason people care is because they can point to the cert if it all goes wrong
I wrote a long reply but looks like posting it glitched. I’ll try shortening. I should have noted that the Certification on SUSE and RHEL, is also a certification compatibility matrix. distro ver to software ver, and Siemens needs stable Windows, SUSE, RHEL releases to code to. Trying to install/running on other distros fails in many areas (even with an experiences guru trying fixes). They have a symbiotic relationahip with those curated distros to ensure it doesnt give downtime to a large enterprise. It is not just a piece of paper saying yes we tested the software install here is your signoff. Personally I did get it running on OpenSUSE for obvious reasons.
Limiting support of software to specific software configurations makes sense.
Its stuff like Debian might be using Python 3.8 Ubuntu Python 3.9, OpenSuse Python 3.9, etc.. Your application might use a Python 3.9 requiring library and act odd on 3.8 but fine on 3.7, etc.. so only supporting X distributions let you make the test/QA process sane.
This is also why Docker/Flatpack exist since you can define all of this.
However the normal mix is RHEL/Suse/Ubuntu because those target businesses and your target market will most likely be running one.
Yeah it is a Known Known and those 3 distros have tried and true reliability. The term certified is what they call it “Certified to run on X” and “Compatibility CertifIcation” it was in response to OP asking if linux is used in corporate world. It is, and for larger operations it is the 3 you mention. Personally I think Ubuntu hasn’t made it into the Corporate Desktop apps like SUSE/REL because you install it and have a hairy hippo or faceted cougar head as the backdrop, just doesn’t sit well with CEO stuffed shirt types when looking for a professional software.
Case in point. You think quoting an argument and sneering is a counterargument. Obviously, because you don’t know the first thing about labor theory of value.
Someone asked if you think capitalists or engineers did the engineering, and you revealed you don’t understand the question.
You are once again building a flawed model of the dynamic at play here in an attempt to ease the discomfort you feel from encountering something that doesn’t make sense to you (why did I choose to join this community?). I’m not even attempting to build any counterarguments because the responses I’ve gotten don’t even attempt to understand what I’ve said in the beginning. To be utterly frank I just lack respect for people who think of themselves as any flavour of anarchist while still dreaming of a system as thoroughly rigid as the artificially created Internet. You pretend to hate the system while desperately trying to invent excuses for continuing to make yourself at home within it.
No dude, you demonstrably said ‘I’m going to repeat your argument so you can think about it.’ Projecting some emotional state onto me is not gonna change how you fucked this up.
This is mockery. I am calling you ignorant.
I am trying to highlight how you joined an explicitly leftist server, whilst remaining aggressively unaware of… genuinely the first things people learn about leftism. So when you try smugly posturing your way out of a pointed question, you’re just revealing you know less than nothing.
To be utterly frank I just lack respect for people who think of themselves as any flavour of anarchist while still dreaming of a system as thoroughly rigid as the artificially created Internet.
Anarchists being naked hippies, of course, not organized laborers. The internet was mostly designed and operated by academics. It runs on half a century of “does this sound right?” collaborative standards. Whatever browser you’re reading this in has its origins in anti-monopolist diehards building better software out of spite.
None of which is even addressing the initial failure. Capital didn’t design your computer. Intel’s founders definitely did, but only because they were workers dissatisfied under Fairchild, who were in turn workers dissatisfied under Shockley. The early history of silicon valley is halfway to semiconductor co-ops.
Well you solved that conundrum rightly. Now let’s go linch those dirty Apple and John Deere engineers. Since they’ve designed those machines, they must be the only responsible parties for designing them with their extreme anti-consumer and anti-repair policies. They must get commissions on every licensed repair or something, it’s definitely got nothing to do with capitalists putting restrictions on the design team in order to increase profits, nope…
You’re completely off on what I’m getting at. The idea of “Capitalist” hardware, as though the Capitalist did the labor, is wrong. Engineers are paid for their labor power, they don’t typically get royalties or anything of the sort, just like any other laborer.
Someone saying that FOSS software relies on Capitalist hardware is putting the Capitalist over the Engineer, as though the Capitalist created the hardware, and not the labor of the miners, assemblers, designers, engineers, and so forth, regardless of who owns the Capital the labor is done by the Workers. FOSS is agnostic to whoever owned the Means of Proruction of the hardware using or producing it.
Amazing how every single part of your comment is so wrong.
It’s actually a really good analogy,
Not an analogy, an example. Those two are different things.
because it can only run on
No, it can run on many things, including open source collaborative hardware that exists.
fully-capitalist hardware.
What the hell even is that? Fun fact: until very recently most of the computer hardware was made in communist China. I know, scary. And now that a lot of effort is being made to get that production out of there, those efforts are being sponsored by public money to an incredible degree. Billions of dollars of taxes (you know, community resources) are being poured into that because big corporations are the biggest lovers of government handouts.
Me - Yes. I use Debian 12. No intention any time to go back because of how much I love using Debian. May fire up a VM of Arch so I can run some specific AUR packages I am curious to try out, but we’ll see. I am cautious to go on another distor hopping bender between Debian and Arch as they are my 2 favorite distros and I am easily led to do that.
Work - No and that is fine me. I have no control over that and I’m still productive with Windows/Microsoft products.
Family - I am the tech support person of the household. I prefer for people to use what they are comfortable with because that’s less on me to maintain.
it always fascinates me when somebody tells about something they do and ppl first of any other reaction spits out how they should do instead. Not interesting at all and often annoying if it isn’t at least preceded by a “I find it interesting you did choose this approach, mind to share thenwhy and more details?” :D
I know you don’t game but a dedicated GPU will be a godsend for video editing. Depending on the budget I would get a used gaming laptop like an Omen or a legion 5
Edit: worst case wait a year for parts and laptops to be really cheap haha.
The downside of a dedicated GPU is that your battery life is going to be bad. Intel Iris graphics have come a long way and are likely fine for this kind of thing.
A dedicated GPU will mean reduced battery life. If you are only going to edit video at your desk, I would suggest getting a laptop with a thunderbolt 3 or USB 4 port and an external GPU. Make sure the port provides 4 PCIe lanes, not all of them do.
I don’t really love any that I’ve tried so far, but I dislike Audacious the least. FLAC, Musepack, and ReplayGain support are requirements for my library.
The last one I loved was foobar2000 on Windows, which supplanted Winamp. Linux UIs mostly feel a bit clunky by comparison. When the window has focus I like to have spacebar for pause/play, arrows up/down for primary gain, and arrows left/right for seek.
I also gravitated towards Audacious, but I foobar2000 was 10/10. Might consider running it through Wine, since Audacious is not quite there unfortunately
As a general best practice, you should never directly login as root on any server, and those servers should be configured to not allow remote connections as the root user. You should always log in as a non-root user and only run commands as root using sudo or similar features offered by your desktop environment. You should be wary of even having an interactive root shell open; usually I would only do so on a VM console, when first setting up a system or debugging it.
By doing this, you not only guard against other people compromising your system, but also against accidentally running commands as root that could damage your system. It’s always best to only run things with the minimum permissions they need, and then only grant them additional permissions on an as-needed basis.
you should never directly login as root on any server, and those servers should be configured to not allow remote connections as the root user. You should always log in as a non-root user and only run commands as root using sudo or similar features
That is commonly recommended but I have yet to see a good solution for sudo authentication in this case that works as well as public key only SSH logins with a passphrase encrypted key and ssh-agent on the client-side. With sudo you constantly have to use passwords anyway which is pretty much unworkable if you work on dozens of servers.
Of course I can store dozens of passwords but if every task that requires a single command to be run automatically on e.g. “every server with pending updates” requires entering each of those passwords that is unworkable.
Then enlighten me, what is the easy way to do tasks that do require some amount of manual oversight? Tasks that can be completely automated are easy of course but with our relatively heterogeneous servers automation a la “do it on this one test system and if it works there run it completely automatically on the 100 identical production systems” is not available to us.
Not my circus, not my monkeys. You’re doing things the hard way and now it’s somehow my responsibility to fix your mess? I’m SUPER glad I don’t work with you.
None of us can tell you the right approach for your specific system and use-case. People are simply pointing out that what you stated you’re doing is insecure and not recommended
And nobody in any of these threads has ever pointed out why it is considered to be insecure. The most probable origin for that idea I have come upon so far is that it is a left-over from pre-SSH days when people thought using the root password with su at something other than the start of their connection would make it harder to sniff. Literally nobody lists even one good reason why sudo should be more secure than direct root login with SSH public keys and password login disabled for full root access (as in not limited to just one or two commands).
It’s not about someone sniffing your passwords, it’s about reducing your attack surface. If you use su then the entire session has root privileges and any piece of software you run could do system level damage if it has a bug. Using sudo limits the privilege escalation to just one command.
You seem to be looking at the issue in black and white. Any reduction in root access is beneficial. Using sudo with password cache lasting an hour is still preferable to signing in as root. As many people have said, it’s about minimizing attack surface
Running fewer commands as root is more significant risk reduction than having an extra user. I won’t be replying further since I’m simply repeating what others have already said. If you sincerely don’t understand, I suggest doing additional research on your own.
You people don’t seem to grasp that I am already not running any commands on the server as root that do not require root. This is all about administrative tasks.
The vast majority of commands when debugging actual issues on the system or performing administrative tasks do require root. Out of the others some give you incomplete results when called as a regular user and 90% of the rest shouldn’t be run on the server in the first place if you can avoid it but directly on your client computer (e.g. looking up documentation).
FreeIPA and your password is the same on every machine: yours. (Make it good)
Service accounts should have either no sudo password or use something like Ansible with vault and keep every one of them scrambled and rotate regularly (which you can do with Ansible itself)
Yes, even if you have 2 VMs and a docker container, this is worth it.
FreeIPA and your password is the same on every machine: yours.
Any network based system like that sucks when you need to fix a system that has some severe issue (network, DNS, disk,…) which is exactly when root access is the most important.
It is. That is the whole point. Why would I make extra unprivileged accounts that can run any command I need to run as root at any time without a password on the system just to avoid it. That just increases the attack surface via any other vector by giving an attacker accounts to choose from to break into.
I am asking why it is considered to be more secure for the use case where you aren’t limiting access to a few commands because it is access meant for all kinds of admin tasks, not just one specific one (as in access for the people who need to fix unexpected problems among other things).
Realistically, there is only a trivial pure security difference between logging in directly to root vs sudo set up to allow unrestricted NOPASS access to specific users: the attacker might not know the correct username when trying to brute force. That doesn't matter in the slightest unless you have password auth enabled with trivial passwords.
But there is a difference in the ability to audit what happened after the fact if you have any kind of service storing system logs remotely or in a tamper-proof way. If there's more than one admin user on a service, that is very very important. Knowing where the compromise happened is absolutely essential to make things safe.
If there's only ever going to be one administrative user (personal machine), logging in directly as root for manual administrative tasks is fine: you already know who the user is. If there's any chance there might be more administrative users later (small but growing business), you should consider doing it right from the start.
I was aware of the login UID for auditd logging as a difference but as you say, that is only really helpful if the logs are shipped somewhere else or tampering with them is otherwise prevented for admin users. It is not quite the same but the auth.log entries sshd produces on login also contain the key fingerprint used to login these days so on a more limited scale you can at least tell who logged in when from those (or whose key but that is no different than whose account for the sudo approach).
you should consider doing it right from the start.
Do you have any advice on how to use the sudo approach without having a huge slow down in every automated process that requires ssh user@host calls for manual password entry? I am aware of Ansible but I am honestly very sceptical of Python tools since they tend to break easily and often from my past experiences and I would like to avoid using additional ones for critical tasks. Plus Ansible in particular seemed to be very late with their Python 3 transition, as I recall I uninstalled it when it was one of the last tools left that did not work with Python 3.
Well, my recommendations for anything semi-automated would be Ansible and Fabric/Invoke. Fabric is also a Python tool (though it's only used on the controlling side, unlike Ansible), so if that's a no-go, I'm afraid I don't have much to offer.
I don’t get it anyway, if you login remotely, why don’t you just open firefox locally but on the remote servers? This makes not much sense.
But If you absolutely have to. … At least be careful with your surf-targets. A search-engine and wiki would most likely be fine. Some pron-, stream- or warez-sites? Nah. Surely not.
I own all the pinephones and as much as I’ll go to bat and speak well if them… The tab support is super early. Lots of stuff doesnt work (wifi for one). That’s not to say that won’t change with time as the pinephone pro did
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.