- 4 Posts
- 8 Comments
Hi, I can answer about the PS3 controller issue. I thought about making a public announcement about this, but I forgot. I’ll work on that now and then link to it here, but to sum up the situation: Support for insecure legacy devices is now disabled due to CVE-2023-45866, and that includes the PS3 controller. You can re-enable support, but that will make your PC vulnerable when Bluetooth is in discoverable mode — that’s when you’re pairing a device; in GNOME that’s when you just have the Bluetooth settings open; easy to have on by accident.
I’ll explain how to re-enable support in the PSA post. It’s a one-liner, but I won’t put it here because I think people should be well-informed of the risks before considering it.
Edit: PSA posted at https://lemmy.world/post/11498269
jntesteves@lemmy.worldto
Linux@lemmy.ml•[SOLVED] How to customize dead keys under Wayland / Electron apps?
4·2 years agoYou should be able to type
çthe way I described for all apps, so you could just remove your custom layout. I highly recommend theEnglish (intl., with AltGr dead keys)layout, it’s perfect for coding and writing in English. It’s a bit more work to write in Portuguese, though, so it took me a while to get used to it, but it’s worth it if coding is what you’re doing most of the time. In this layout, you must hold AltGr to get the dead keys, otherwise it’s a normal English layout.You can also use two layouts — one for English/coding, one for Portuguese — and the keyboard shortcut Super+Space to switch between them. I always have two layouts setup like this, but I never switch anymore because I just learned to love the
English (intl., with AltGr dead keys)layout — and I don’t write much Portuguese nowadays.
jntesteves@lemmy.worldto
Linux@lemmy.ml•[SOLVED] How to customize dead keys under Wayland / Electron apps?
5·2 years agoI’m using GNOME Wayland on Fedora 39 and I don’t have the problem you describe. I just go to settings and select my keyboard layouts:
- English (US, intl., with dead keys)
- English (intl., with AltGr dead keys)
And everything just works. I specially like the second one because it doesn’t interfere with keybindings in games, which can be a problem in GNOME Wayland.
Oh, I think I get the issue you’re having, you can’t find the Çç character on the Linux layout 😅 I always have to explain this to people migrating from Windows, it’s
AltGr+,(right Alt key plus Comma). I like this shortcut better than the Windows layout, but I understand some people might not like it. Unfortunately, I can’t answer your question, as I too don’t know how to customize the keyboard layout. I just got used to the Linux layout.
SELinux in Podman works pretty much the same way it works on Docker, so if you are having problems with Podman, you should also be having problems with Docker, so I don’t see how that’s impeding your migration. You need to be more specific about the issues you’re having to get a good answer.
The post by Chris Smart you linked on your comment below is a good start, but everything there also applies to Docker, so if you still didn’t know those basics, you shouldn’t be able to use Docker on Fedora either.
About your question of how to set it up, use-case is an important consideration, there is no generic answer that covers all use-cases. I’ve even found out that for some use-cases (like ad-hoc containers), disabling SELinux within the container (with
--security-opt=label=disable) seems to be the most secure option. That’s what I’ve done in contr (see this commit message). I’ve been meaning to blog about that, but never did because I’m in the process of migrating my blog but too lazy to finish it.I’ve put a lot of links about SELinux in containers in this issue.
jntesteves@lemmy.worldto
Linux@lemmy.ml•*Finally* found a decently priced laptop using AMD's 780m iGPU | Lenovo UK Laptop configurator
1·2 years agoHere’s the update, I’ve got the USB-C/HDMI adapter today. Connected it to the port that connects directly to the dGPU and even during boot Plymouth was already outputting video to the TV. I also tested hot-plugging and it just works as expected.
Now for the problems, I ran benchmarks and the performance was as expected, but frame delivery didn’t look as good as when using the HDMI port on this device. It doesn’t show on the performance metrics, but looking at the screen, the frametimes looked off, stuttering. I’m still figuring out where the issue might be to report it to upstream. EDIT: For people reading this in the future, I’ve found the issue to be in GNOME’s compositor, Mutter: https://gitlab.gnome.org/GNOME/mutter/-/issues/3070#note_1865351
jntesteves@lemmy.worldto
Linux@lemmy.ml•*Finally* found a decently priced laptop using AMD's 780m iGPU | Lenovo UK Laptop configurator
1·2 years agoI hear you, I have a Legion laptop with a GTX 1060 mobile and I keep the dGPU as primary all the time because I just can’t be bothered by NVIDIA optimus anymore. That’s the reason I decided to upgrade to AMD, even though the performance of the 1060 was still appropriate for me and I wouldn’t have upgraded yet otherwise.
I don’t have any issues with the Strix G15 on Fedora Silverblue. Talking to other owners of the same model and also other Asus AMD laptops on Reddit, I didn’t hear any complaints about that.
The G15 has the HDMI port connected to the iGPU, and the USB-C (DisplayPort Alt Mode) connected directly to the dGPU. I’ve only used HDMI to connect to a TV, I haven’t tested the USB-C output because I don’t have a monitor with DisplayPort. So I can’t really answer your question.
Tell you what, I’ve just ordered a USB-C to HDMI adapter, as soon as it arrives I’ll test the output that’s connected directly to the dGPU and update you on that. I’d bet on it being plug-and-play, but we’ll see. 😉
jntesteves@lemmy.worldto
Linux@lemmy.ml•*Finally* found a decently priced laptop using AMD's 780m iGPU | Lenovo UK Laptop configurator
5·2 years agoYou shouldn’t generalize your bad experience with NVIDIA’s proprietary driver to Mesa. Graphics device switching just works on Mesa, hence laptops with an AMD dGPU are great on Linux.
Typing this from a 2021 Asus ROG Strix G15 Advantage Edition


rpm-ostree currently does not support DKMS, and it’s unlikely that’ll be implemented anytime soon, if ever. It does support akmods, though, which is the preferred way to build Kernel modules on Fedora. You could ask if the packager can build that way to support the Fedora Atomic editions.
If you need these Kernel modules now, I think your only option would be to build manually from source, but that has the downside of requiring a manual step every time the Kernel is updated.
Edit: there are a few issue reports already: https://github.com/pop-os/system76-dkms/issues/58 https://github.com/pop-os/system76-acpi-dkms/issues/16