Unfortunate but understandable. uBlue delivers images in a different way as opposed to silverblue. Great project though and one I will recommend to anybody
Does that work even for the OCI images that ublue uses¿? Also can we configure this further. I don't want to accidentally update my image when on a metered connection.
Lemmy version 0.19 has not been released yet and will not be at least for 3 weeks so voyager is currently compatible. Most of the clients out there are incompatible with 0.19 for now. Harsh to blame only voyager.
The other issues are genuine bugs though and it would be nice if they are fixed but voyager is an open source project so if people feel strongly about these issues, maybe they can contribute some code to fix the issues.
My point is that voyager was there when we needed it the most during the early phase of lemmy expansion when the PWA was called wefwef and we should be here when the dev is busy with other things.
If you can please donate to the kde organisation. That funding will prove invaluable for future development of plasma
Edit : I am not a contributor to plasma. Just an open source enthusiast who thinks that we should give back to the amazing people who create this software either by contributing to the projects or through monetary means. The degree of contribution is not important, the spirit behind it is
Well for Bluetooth to start you have to run systemctl start bluetooth and then systemctl enable bluetooth to start the Bluetooth service at every boot. For some reason the systemd Bluetooth service is not enabled by default in debian.
I unfortunately have no idea of how to resolve your USB issue.
Also coming from one noob to another - don't reinstall or restart to fix issues. Always make a good faith effort to search online for ways to fix your issues. Not only will this approach be more effective in solving the issue, you will also end up learning some new things.
The dev has replied on github that he will release an update for the API changes. It would be sad if the community totally abandoned voyager just because the update frequency has decreased
Hmm must be some bug in mesa or the way it interacts with vlc . I use VA-API with mesa for my decoding purposes on a system(laptop) with Vega iGPU and RDNA1 dGPU and I don't see high energy usage. In fact I get much better battery life with vaapi hardware decoding.
I am assuming you have the monitor connected directly to the 7800xt. Which is why it is the default GPU.
Is the decoding being done when watching the video¿? amdgpu_top shows if the application(vlc in this case) is using the decoding hardware(column named DEC).
Also using the iGPU for video decoding should be more efficient because the massive number of cores in dGPU aren't needed while decoding yet are kept active because the dGPU is active
I am guessing you are talking about the reduction in dimensions. But how can we say that the reduction in dimensions is nothing without considering the effects of the same
And thank you for the PR and your general contributions to the open source community. It is because of amazing people like you that idiots like me are able to daily drive linux
That's what apple are considering offering. That doesn't mean Liberty would bin F1TV.
The point is if they give apple exclusive rights, they will legally not have the ability to provide the F1TV service.
Also the entire thread is a discussion on apple thinking about making an offer for exclusive rights. Obviously any discussion would consider the possible exclusivity. Of course F1 may choose not give apple the rights but i thought that is implied.
Gsync works with x11 if I remember correctly