I started playing Dying Light for the first time recently. Compared to the Windows version, it looks like Techland completely abandoned the Linux native version of the game. Is this update fixing the Linux native version to be on par with Windows?
jrgd
I can only guess the previous BIOS wasn't enabling every virtualization extension necessary for some applications for some reason then, given that GNOME Boxes did work. Glad you've found a solution.
The explicit denial I saw is multi-genre, multi-artist in ID3 v2.4 I won't be parsed.
EDIT: The source.
Rockbox will only pick up one of a tag (RIP Vorbis) and will only parse up to 500 bytes on higher end players, 240 bytes on other players of the grouped tag (RIP ID3 v2.4).
I did accidentally type the relevant command incorrectly, forgetting that sudo swaps the user before subcommands like whoami will resolve. So that command attempted to add the kvm group to 'root' rather to your user. I have fixed the command in the relevant comment for anyone else reading this thread. You can try sudo adduser "<username>" kvm
, manually substituting for your username. As normal, restart after adding the group to your user. Additionally, I have added a warning to the solution in the original comment of why you may not want to keep this solution enabled forever as well as a way to disable it later if desired.
Rockbox unfortunately is built with "dinosaurs" in mind. As a side effect, the project does not intend to properly handle modern ID3, Vorbis tags.
I could use an older Android phone, but would have to find a suitable device to de-Google and load a custom music player app onto (such as Vinyl). Neither my Pixel XL nor Pixel 5a that I own currently are suitable targets (neither have microSD support, my Pixel XL has a damaged headphone jack and needs to be repaired). If you have any recommendations for something used that has a headphone jack, microSD slot, and can bootloader unlock via adb, let me know.
Based on using a local installation without elevated permissions (outside of /usr/(local)), I can only guess of two things happening:
The first is GNOME Boxes asks for elevated permissions when running or otherwise uses Polkit to gain those permissions. Your user by default likely isn't granted access to /dev/kvm and running userland software without additional permissions will inherently not allow KVM access.
To allow this sanely, you can add your user to the KVM group to allow userland KVM access. It can be done via sudo adduser "<username>" kvm
and then restarting your computer. To note, this is something that can allow any application to access virtualization without special permissions. If you don't want this change to remain forever, the command sudo usermod -r -G kvm "<username>"
followed by a restart can revert this change.
Alternatively, installing Android Studio via the Flathub Flatpak may handle permissions without needing to modify user groups in this case.
The second (unlikely, but possible) problem is the AppArmor profile blocking KVM access for userland. I don't have particularly any experience with creating modified profiles for AppArmor, if this is the cause. I could only offer terrible advice for AppArmor (disabling AppArmor or switching to warn-only, both things I do not recommend doing). Again, it might be worth trying to install Android Studio via flatpak to see if things work better if this is the cause.
I am testing this currently to ensure correctness, but if you're using Android Studio via Flatpak, you may need to enable kvm permissions for the application to have hardware-accelerated VMs. This can be done using Flatseal. The relevant permission (device=kvm) is under the Device section labeled as Virtualization.
Additionally, if problems are occurring outside of Flatpak, you might need to enable certain hardware virtualization technologies from your computer's BIOS (AMD-V, VT-x, VT-d, Intel VT, Virtualization, or some other similar term depending on CPU and motherboard).
EDIT: Doing testing, it seems the default permissions provided for Android Studio's Flathub Flatpak includes device=all. No permissions edits are necessary by default. If there are problems with the /dev/kvm device not being reachable, it is almost certainly due to the necessary extensions not being enabled in the BIOS, or your CPU doesn't support virtualization. Pop! OS 22.04 has the necessary components in software for KVM to function pre-installed, so nothing should be wrong on the OS side.
Superior over what exactly? Most workstation/desktop distros have a graphical software manager and handle drivers in a similar manner.
From my experience with a modern Thinkpad (A485); nothing if not outright inferior. The trackpoints on them are pretty terrible compared to classic IBM-era thinkpads (10-20hz polling rate, abysmal velocity curve). The physical durability of the machine might be above-average for business laptops, but the chance of the hardware failing in some major way within warranty seems to be quite high (among other replacement parts, I had 4-5 mainboard replacements done under warranty). The cooling solution on the Thinkpad I used to use was also a fair bit inadequate, and would lead to severe thermal throttling of the mid-range APU. Honestly between the reliability and torturous process to even buy a new Thinkpad from Lenovo, I just wouldn't bother.
On my mobile Lemmy client (Eternity), I already keep a multicommunity group for finding tech support posts in case I have something to offer in response. As it stands with [email protected], there aren't too many posts that are pure conjecture or information and thus doesn't really clog my feed. If this community grows to have more of these kinds of posts showing up, it may be worth having a split. As it stands currently though, I feel it would mostly serve to significantly lessen what gets posted to this community.
A majority of the Linux-native titles I have played work well. It's only a handful of titles that have blatant neglect or malice from the developers, publishers that don't work fully. Dying Light looks to fall under neglect as it doesn't seem to have been updated (except for the inclusion of DLCs) beyond the 2015 build of the game, and seems to be stuck in a console-ready graphics preset.