Russ

Just ran into this exact problem this morning which was incredibly frustrating. Performed a routine system update, and I’m pretty sure I had a kernel panic (all input was non responsive, couldn’t even switch to a tty) in the middle of pacman’s upgrade phase.

While I was able to chroot into my install and reinstall the kernel, half of my system’s packages were left in an inconsistent state so I still couldn’t properly boot - and so I just nuked my root subvolume and reinstalled Arch (I suspect I could’ve somehow got the packages reinstalled if I wrangled for a while with pacman but it was just easier to reinstall at this point).

Atomic distros like Bazzite are designed to prevent that exact situation I ran into, unfortunately I just haven’t had enough time or energy to try to make my own custom image that has what I need in it (got kind of close with NixOS but that had its own issues), otherwise I’d probably be running that.

I’m not sure if this is a Pixel feature or if its available across all of Android, but there is an option when you connect over USB to connect your phone as a webcam - but that is of course tethered instead of being wireless.

No problem! It looks like there’s an AUR package for it - though exercise caution since it is still in beta. That being said, 555 has been in beta for a bit now, so I expect it’ll probably be promoted to an official release imminently.

Definitely would give Wayland another try once the newer Nvidia driver is installed later on (either via the beta or the official release). I don’t use an Nvidia card anymore (this bug is precisely what caused me to switch, ironically - it has been around for a while and got worse for me when 535 came around) but I’ve heard from a lot of folks that it resolves the flickering issue.

Either way, I’m glad to hear that you’re glitch free now - and on a side note, it appears its your cake day so happy cake day!

I’m pretty sure the explicit sync fix requires the 555 beta version of the Nvidia driver to be installed, as there’s a driver component that’s required.

What distro are you on? If it has a decent way to install the 555 beta that would probably be a good route to go with - but otherwise, no, switching to X11 shouldn’t require reverting any settings at all. I used to switch between the two sessions all the time, right before you enter your password on the login screen (you have to be completely logged out, not just at the screen lock) click the menu at the bottom right and it should have a “Plasma (X11)” option.

I haven’t tried it myself, but I believe the OC is referring to the webcam USB mode that Pixels (idk if this is an Android feature or a “Pixel” feature) have. To enable it, connect over USB then you’ll have a notification along the lines of “Charging this device over USB”.

If you click that notification it’ll let you enable Webcam over USB mode, which I assume just causes the phone to act as any other webcam device would.

Things are also constantly improving over time as well, so its very possible that OP’s setup was somewhat problematic a while ago but have since been resolved.

Which would also make sense if the hardware itself was super new at the time, and didn’t have proper kernel modules for it when it was originally released perhaps.

I’ve been using EndeavourOS for a few years now, which is effectively a “good sane defaults” Arch out of the box. I’ve attempted to use numerous distros in between (including plain Arch) but there’s always something I feel is missing or just isn’t right (for me).

This looks like a fantastic update! Huge thanks to everyone involved!

Same with my Stadia controller - funnily enough, Windows is the one that required me to purchase some third party software to be able to use it wired or wireless…

Definitely keep us in the loop!

They have their own hosting plans, but you can also self host it.

Were you using X11 before, by chance? IIRC Fedora 40 dropped X11, and only ships with Wayland by default. The fact that all of your apps are using the same screen sharing interface sounds like they’re using the screen share portal due to running under a Wayland session, which Discord doesn’t currently support currently.

For a while there was a workaround using a tool called XWaylandVideoBridge but even that stopped working for me.

I’ve heard that Vesktop supports screensharing under Wayland (and supposedly with sound support too), and it is available on Flathub - might be worth a try.

Oh that is perfect, thank you! Funnily enough, pasting into VNC sessions is exactly what I needed something like this for as well - you’ve taken a lot of future pain out of my workday!

I’d love to find an alternative to xdotool’s auto type feature (or ClickPaste from Windows).

There is wtype but unfortunately it doesn’t work in KDE nor GNOME because neither of them support the right protocol. I’ve run into the “<DE> hasn’t implemented $PROTOCOL” a few times in the past and it’s certainly a bit annoying.

Aside from when that comes up, I don’t really have any complaints. A tool we used for work was never going to be fully functional on Wayland because of its dependence on Xinerama (I think) but thankfully we’ve moved away from it.

Thank you for the update! I just gave it another go and don’t seem to have any audio, and it still seems quite jittery - I’ll have to play around with it some more and see what I can get working on it :)

AFAIK the inbox analogy that the previous user wrote applies on an instance level, so in your example the LW admin would still see it (assuming it was against a LW user or something in one of their communities, I believe).

The “mark report as resolved” option doesn’t federate to other instances, if that makes sense. It’ll mark it as resolved for that whole instance (so a community mod won’t see the report anymore once an admin from that instance marks it as resolved and vice versa), but not other instances.

At least, that’s as far as I understand it, don’t quote me on that 😅

For myself, I’m fine with using ChatGPT and other LLMs (I’ve been experimenting with trying to run them locally, so that I can gain some insight on them a bit better) to “fill in the gaps”, or as a sort of interactable Wikipedia - but I try to avoid asking LLMs something that I have zero knowledge of, because it then makes it a bit more difficult to verify the results it produces.

It should, yep! It’ll be in the Display Configuration if Plasma is properly detecting an HDR display.

Since Plasma 6. Not sure about HDR wallpapers (never even heard of an “HDR Wallpaper”, so I’ve not looked into support for it), it should work with fullscreen videos though, and Steam games work if you run it through a nested gamescope session with a special HDR Vulkan layer installed.

Interesting, I’ll give it another go and try out your recommendations - thank you!!