the qobuz webapp is hi-res too, I just use it in Firefox and my dac reports the same bit/sample rate that qobuz does. AFAIK there’s no compression there though I haven’t extensively verified that, only that the end result is 24bit/192kHz if that’s what qobuz says is playing.
EDIT: Also, qobuz is nice because there’s very few things you can click on in the web interface which cause the music to stop playing. I really appreciate that feature… looking at you bandcamp…
Ah, I should have been more clear. The CRITERIA section of the sway documentation states that class matches support regex, so instead of using a * as you did in your example you’d use a regex any .*. So I think (untested of course) that for_window [class="steam_app_.*"] allow_tearing yes should work.
The comment in the code for allow_tearing notes that it must be enabled on the output as well. Here is the relevant output documentation. There are several other notes/recommendations there as well you should probably pay attention to.
Are your games all wine/proton games? For me in sway they all have the same class followed by some uid thing:
] > swaymsg -t get_tree
[...]
#92: output "DP-5"
#70: workspace "21"
#126: con "Automobilista 2" (xwayland, pid: 171976, instance: "steam_app_1066890", class: "steam_app_1066890", X11 window: 0x5400001)
Or gamescope:
] > swaymsg -t get_tree
[...]
#92: output "DP-5"
#70: workspace "21"
#124: con "Assetto Corsa" (xdg_shell, pid: 170694, app_id: "gamescope")
EDIT: Also allow_tearing was added to master 3 weeks ago, so this is definitely not in the current release. FYI to anyone who might try it.
Or add EA anti-cheat 6 months after release like they did for EA WRC.
Yeah, it changes without skipping a beat for me in pipewire, even in things like zoom/teams.
I use a little oneliner with tofi (rofi/wofi would also work) to select the current output and avoid pavucontrol. It’s mapped to a sway binding but would probably work in any wm/de:
pactl set-default-sink $(pactl list short sinks |awk '{print $2}' |tofi $tofi_args)
I’m using pipewire so the functionality of pactl is actually provided through pipewire-pulse I think
Interesting, it is working for me in wayland and the drop down menus are fine but I’m using sway which is a totally different wayland implementation than what KDE is doing. I’m glad you found a workaround.
Unfortunately I don’t know what is causing the exact issue you are having, however here are a few things I found when doing this myself that are “gotchas” (not immediately obvious).
This is the reason your fonts are all Times New Roman. Go to that key using protontricks regedit and delete all the font replacements.
Anything you put in $HOME/.steam/root/steamapps/common/assettocorsa stays there, even if you uninstall the game. If you want to “start over” you have to uninstall the game and then delete the whole assettocorsa directory there, and the wine prefix in $HOME/.steam/root/steamapps/compatdata/244210
AC and content manager work without .net changes in the latest GE but you do need corefonts which you can install with protontricks. If you want to be extra sure you have the right .net you can install dotnet472 but I don’t believe this is necessary anymore as it will be installed automatically or is already installed. You may get a wine .net error the first time you launch the game but it’s only the first time.
If you choose to use CSP you have to unzip the archive you get from either Patreon or acstuff.ru and manually copy the dwrite.dll file into $HOME/.steam/root/steamapps/common/assettocorsa on EVERY upgrade. The zip installer built into CM doesn’t do this correctly on Linux. It will cause rain not to work if you choose to use the Patreon version if you don’t do this manual step.
I think you should start over and make sure the assettocorsa directory is clean before re-installing the game. It could be missing fonts, but it’s hard to say. You can back it up somewhere if you have data in there you need.
Does Bazzite use a gamescope session on wayland by default? Gamescope has a bug which prevents the wayland client from drawing the steam overlay. I suppose it’s unlikely to be the same issue but I happen to be dealing with it on my system (not Bazzite) so I immediately made the connection.
What version of kde? I haven’t tried it, or read about it beyond the changelog, however the latest beta release says that it supports RDP to connect to plasma desktops which is quite an interesting development if it works the way it sounds like it does:
Remote Desktop system integration to allow RDP clients to connect to Plasma desktops, plus a new page in System Settings for configuring this
For the “from anywhere” component you could use a vpn, but if you’re looking for a simple solution with zero configuration than nomachine or rustdesk seem more appropriate. Just thought the RDP support was worth sharing.
So, I’m not sure if the process has changed in the last decade or so but in a long-ago computer forensics class step 0, before all else, was to never operate data recovery on the original disk. Create a block level image of the entire device, then work on that.
My go to steps for recovery have been the following in the years since:
ddrescue -d /dev/sdX <path_to_image>.imgtestdisk <path_to_image>.imgIf the disk has a complicated partition layout, or more effort is required to find the correct partition you can also mount parts of the disk.
create an image of the entire disk (not a partition) using ddrescue
ddrescue -d /dev/sdX <path_to_image>.img
Mount the image as a loopback device with the appropriate offset
losetup --offset <some_offset_like_8192> --show -v -r -f -P <path_to_image>.img
this will mount individual partitions:
loop58 7:58 0 465.8G 1 loop
├─loop58p1 259:7 0 1.5G 1 part
├─loop58p2 259:8 0 450.6G 1 part
└─loop58p3 259:9 0 13.7G 1 part
Then operate testdisk on whatever partition you want.
All that said there are a lot of variables here and things don’t always work perfectly. I hope you do find a way to recover them.
Nextcloud AIO is not the only way to run Nextcloud in docker. For example you can use the Nextcloud docker repository and docker-compose for which there are many examples. I’ve been running Nextcloud this way for many years now without any un-recoverable issues, and no issues at all that weren’t caused by me. Upgrading is also very easy since you simply increment the version in docker-compose.yml and restart the service.
That said the NixOS suggestion from @StrawberryPigtails@lemmy.sdf.org looks really neat and I may try that out soon my self since I’ve never played with NixOS before and it seems like a good excuse to do so.
Sway for a little over a year now (on an AMD gpu). I switched for mixed refresh rate support and VRR. VRR requires a workaround in sway but works better in others, like hyprland, however I like sway’s tiling better so I stuck with it. Also the absence of tearing in anything, ever, is worth it to me. I have two vertical displays and it was really hit or miss on X11. Sometimes GPU acceleration would just decide not to work in browsers and I’d have to restart them because smooth scrolling would turn into a stop-motion film. That’s never happened since switching to sway.
EDIT: I used i3 before
I use sway and run zoom in my browser (because zoom is shady and I don’t trust them). Screen sharing works fine in the browser. The application never worked very well to being with anyway for me, even on X11.
I also use https://git.dec05eba.com/gpu-screen-recorder/about/ for individual output screen recording such as gaming which works amazingly well. You can not select a section of a single output though, only the whole output. That’s a deal breaker for some, and a non-issue for others, just depends on what you need.
But can it sneekily destroy the cables under my desk? And does it sometimes just stop and look at you to think “I could destroy you… if only I was a little bit bigger”.
Is it on a tty in embedded mode? If so does switching ttys using CTRL+ALT+F{1…10} work? Usually the display manager is on F1 or F7. If it’s not in embedded mode, does Left Alt + Enter work?
EDIT: Re-read and realized I didn’t understand completely. You’re starting it with your display manager. I’m not sure how you would kill it in that case.
I think this one https://github.com/nextcloud/desktop/issues/5369 is probably the more relevant, and also open, issue. However even in that issue people claim you can choose not to. The argument is only that it suggests restarting explorer and also rebooting and that this is annoying. So you never get a prompt, it just dies?
I agree though that the amount of time where it was force rebooting is pretty bad, and it looks like the rollout of the patch was mishandled. I also should probably admit that I’ve never touched the windows client, my environment is entirely Linux and Android. The Linux client even with file manager integration doesn’t require restarts of anything.
I mentioned the client in there (4th paragraph), but mine was more of a general rant on the overall low effort that seems to have been put in to figuring out what the actual problem was. And that it is relatively common among people in the self hosting community to assume that Nextcloud is a lot simpler than it is. It’s a huge cloud suite consisting of many applications, clients, plugins, proxies, caching, database, etc. You need to have a pretty good understanding of how it all works, and how to investigate a problem, and ideally you should be testing before upgrades. Large organizations often even test endpoint applications like the desktop client and push out only tested versions to users via policy or some kind of endpoint management.
I can’t really draw many conclusions from the very little information provided in this post, but I suspect OPs windows machine is not in an entirely stable state, which is what is causing some of these update issues.
And, I put some of the blame for Nextcloud under-representing it’s complexity on Nextcloud’s marketing and AIO. You absolutely can install it without understanding anything, and that’s a little dangerous in my opinion because it is actually quite complex and you will probably end up breaking it at some point and need to dig in to fix 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.
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.