create a new, empty profile in waterfox or librefox, and test again.

I habitually use a clean install whenever I move OS - so much so that I’ve been buying new storage drives for the sake thereof. I actually have one ready to go for Trixie, once I finish a current project.

clipboard…

This just sounds bothersome. A clipboard should really be machine-wide, that’s the purpose of it. Although I can understand the reticence there, what with password managers. I would argue that, to achieve that sort of security, there should be a separate, “secure” clipboard that only enrolled applications can access - and enrollment should be left up to the user, not the application developer.

RDP

How do you approach RDP? Do you have multiple monitors at all? Is your approach scriptable? The reason I ask is because I can easily access my machines like so:

exec xfreerdp3 /u:<user> /p:<pass> /v:<address> +f +clipboard /drive:/home/<user>>,Z: /drive:/,Y: -grab-keyboard /monitors:0,1 /multimon

This can be added to a script that also checks the state of the target machine, and boots it via my IPMI console if necessary, waiting until the machine is ready to login. And, as you’ll note, I can specify which monitors I would like to provide for the connection. grab-keyboard allows me to set a keyboard shortcut that minimises the remote session, and you’ll note the mapped drives also. This is pretty much the lowest level of functionality I’m after. If that can be replicated on Wayland, that’s at least one hurdle down.

On the contrary, they provided a piece of information that I’m very interested in. They’re hardly shilling.

You don’t need something huge. Remove the DVD drive and the old mechanical drive from a USFF machine, stick a pair of 4TB drives in it, and put a basic debian image on it. Configure SMB with a shared folder or two, and voila: you now have a comfortable NAS for maybe £20 plus drives. Add in a sata pcie card if you can find a decent low-profile one, and that’s an extra four or even six drives. It won’t give you the cream of top performance, but it will be perfectly serviceable for a homelab.

Can we get that udev rule? Or at least a rough idea how to put it together? I had to put a windows box up just to get this phone talking to a pc

I get the feeling that it would be more feasible to build a separate kernel at this point. Its a lot of work, but adding another option to the comparatively small array of kernel options that we have might actually be a good idea -and in doing so, it word demonstrate r4l’s willingness to maintain the project long-term. There’s no need for this pissy behaviour, and there’s no need to take the drama to social media.

I have an SFF PC currently running Mint, with Bello and steam as well as xemu and a few other goodies. The flexibility is great, if something is a bit borked I can usually just play it in VLC, and the compute allows me to run pretty much any emulator besides Xenia or that PS3 one. Once I plug a GPU into it, those should be fine too. Not bad for a cheap i5 system.

Forewarning, wine appears to be a bit broken on Mint at the moment. I was recently experimenting with it in a VM, and I could not seem to get it installed properly - even after adding the winehq repo. Debian, by contrast, just works. I still use winamp for my music library, and play a few games that are windows based.

Holy shit this looks practically perfect. Thanks!