The fork was merged into rofi, See the Announcement at the top of the readme for the fork.

So this is not exactly what you want, but have you seen the rofi -show window feature? There’s no preview of the window, but it does display the title even if the window is not on the current workspace.

I have nothing really to add, but just want to say thanks for making watchfaces!

- fellow pebbler

Weird coincidence that the exact reason for this thread is addressed in https://github.com/nextcloud/android/releases/tag/rc-3.35.0-01. RC2 was just released yesterday.

I tried it but having some trouble binding my input devices. Seems to be a common issue so hopefully it will be resolved soon.

This. I had symptoms extremely similar to OPs and saw this in the kernel logs immediately before the system would reset:

[    0.705185] mce: [Hardware Error]: Machine check events logged
[    0.705187] mce: [Hardware Error]: CPU 17: Machine Check: 0 Bank 5: baa0000000090150
[    0.705190] fbcon: Taking over console
[    0.705191] mce: [Hardware Error]: TSC 0 MISC d012000200000000 SYND 4d000020 IPID 500b000000000
[    0.705195] mce: [Hardware Error]: PROCESSOR 2:a20f12 TIME 1678252812 SOCKET 0 APIC 3 microcode a20120a

It turned out to be a hardware issue with my CPU (AMD Ryzen 9 5950X). I got it replaced under warranty (twice actually, the first replacement had other issues) and everything is fine now. Definitely check what the kernel logs say.

You can look at the previous kernel log from before a reboot with journalctl -k -b -1 (as root)

You can do it just in the sketcher and get 90% of the way there with just sketcher constraints. You can also create a body with a subshape binder for each sketch line and use assembly and create an animation. You don’t even need 3d solids. I created a gif, we’ll see if it attaches properly to this reply…

I see you made a comment in https://github.com/ValveSoftware/gamescope/issues/1913 . Did you try vkcube like someone earlier in that issue? And the other workarounds like --expose-wayland?

Also what version of gamescope? And you don’t happen to be running steam as a flatpak do you?

EDIT: they JUST released a new version https://github.com/ValveSoftware/gamescope/compare/3.16.14...3.16.15 . So if you are having issues downgrading might be worth a try, but I haven’t been able to reproduce the issues you are having.

Also, I know it sounds weird for a linux machine, but update and restart just to rule anything weird out. I’ve had steam and steam related applications leave around weird state, processes, etc. before and restarting is an easy way to clear that all out and start fresh, eliminating variables.

I dunno why but this immediately made me think of Uplink https://en.wikipedia.org/wiki/Uplink_(video_game)

Quake3 and Overload (only sortof FPS) are the ones I play. Both have plenty of community servers and also community games. And both have linux native versions that run without wine. I’m by no means an expert in this area nor do I have a vast knowledge of what people play these days. Just sharing what I like.

universal-pidff is working on support for many wheels. I believe they are also working on upstreaming.

Thrustmaster hid-tmff2 is a module that supports some common belt drive wheels. (I had a t300 but upgraded, see below)

OpenFFBoard is fully supported without any extra drivers/modules in Linux. Even the configurator is just python+qt and works fine (This is the wheel I use).

Running the drivers in wine won’t work, or at least there is no benifit that I’ve seen. Oversteer provides some udev rules which improve logitech support, you should install that and reboot even if you don’t plan to use it. The udev rules initialize the wheel correctly, set permissions on the sysfs components, etc. AFAIK the Logitech Driving Force GT is fully supported by the in-tree logitec driver link. Can you post more details about the issues you are having, maybe with screenshots?

EDIT: I forgot that oversteer recommends using new-lg4ff for most logi wheels. So definitely give that a try as others said.

Lastly there’s sim community https://infosec.pub/c/diysimulators@discuss.tchncs.de (the creator of openffboard is the mod of that community) if you’re interested. It doesn’t see that much action but there’s a little here and there.

I’d suggest a decongestant, looks like you’ve got a lot of snot going on there =]

In all seriousness though, we all have to start somewhere. Just keep practicing, you’ll get the hang of it.

Ok, I’m prepared to be downvoted today so here goes.

Nextcloud is an enterprise cloud suite. The one you run in docker on your rpi (or whatever) is the same one that is run at a company, albeit with more high availability and redundancy, but the same application, proxies, caching, db, etc. Nothing is stopping you from running the stable channel and testing your upgrades, or even rolling out specific stable client versions to your devices.

Said companies often have teams (more than one person) to run it, stage upgrades, automated testing, automated backups, monitoring, etc. They go to work and do just that, maybe not every day but at least a couple times a week their focus is Nextcloud and only Nextcloud.

What many people in the self hosting community do is spin up docker, without ever having touched docker before, and try to run Nextcloud, forget that it exists, and then upgrade it a year later across multiple versions without maintaining the database. Then they obsess about how fast an app loads by refreshing it a whole bunch, and then complain on internet forums that it sucks. This, like many posts, doesn’t have a specific problem for us to help with, no logs or stack traces have been posted, and the subject of the complaint shows just how terrible your understanding of application security is.

So, while there is legitimate criticism of some of Nextcloud’s design choices, this isn’t it. And at the risk of sounding a little gatekeepy, if you post “nextcloud updates break everything” with no context you probably should spend some time gaining a better understanding of how internet facing services work and make an attempt to fix the problem (probably misconfiguration, and in this desktop client case probably a heap of un-updated local software installed alongside the client), which I’m sure people would find if they did the bare minimum of reading a few log files or any of the other things that come with being an application admin.