I really like fish because it has excellent contextual autocomplete based on the folder you’re in. I haven’t used any other shell that was as good at it.
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).
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.
It didn’t help but it definitely got me moving in the right direction. I remembered that I recently (yesterday) enabled the testing and kde-unstable repos in my system so I could install Plasma 6.1 to check it out. Prior to this change I had CM working properly but was having issues getting CSP to work. Well, I figured out a workaround to getting CSP to work (after this change) by just copying over my install directory from windows on top of the install in Linux. However since I had already updated to Plasma 6.1 it came with the new issue of the drop down menus.
I was using Wayland. Just swapped over to X11 and it’s working as intended. So something with Plasma 6.1 on Wayland is causing the issue.
So mostly a bunch of messing around with my system is probably what is causing the issue and for whatever reason disabling the testing and unstable repos isn’t allowing me to revert back to the previous version of Plasma. Not really sure why but that’s a totally different issue.
I really appreciate the time you took to give me such an in depth response.
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.
That only helps people who know what Adobe Lightroom is for.
In short, Darktable is a tool to generate images out of camera raw image formats. (Edit: You can think of Raw image formats as “kind of” source code for images, which requires to be interpreted as a traditional pixel based image format to be displayed.) The workflow is much different from a traditional image editor. I didn’t watch this video tutorial series here, but it looks good enough for linking: www.youtube.com/watch?v=NMcA6MIhg0Q&list=PLqa…
I dislike the paradigm that there are “techy people/programmers” and “tech illiterates/non programmers”. Anyone can develop the skills to properly use unix interfaces given proper training; and I know that’s true because the whole world used to run (mostly) unix on the desktop before corporate took over. Unix doesn’t need to be windowsified/macosified to get people to move over; people need to unlearn the interfaces corporate has brainwashed them with for generations. There are so many more interesting user interfaces than just what Windows and MacOS provide; graphical or otherwise.
OpenBSD’s default public domain kornshell fork on OpenBSD, oksh (portable OpenBSD ksh clone) on Linux/MacOS/Other Unix. It has far fewer extensions than something like Bash (which I consider a positive) while being much faster (tested with hyperfine), and the extensions it does have are all useful (arrays, coprocesses, select, .* not expanding to . or .., pattern blocks, suspending of the whole shell).
I didn’t at first, but after the response from @mranderson17 I ended up doing just that. Which seems to have resolved that issue.
Prior to enabling testing/unstable repos for access to Plasma 6.1, CM was working fine on Wayland. However after the update it seems to have broken it but changing to X11 fixes the issue. So it’s likely a combination of me messing with my system and something with Plasma 6.1.
Note I didn’t claim anything about technical security. It’s more of an ethical issue. Even if it’s FOSS (which, as seen in the other subthread, its merely pretending to be), it’s helping russian government.
If you want to consider security — security starts with trust. And GRU/FSB will infiltrate and use any segment of supply chain it has in its reach, being less constrained with any laws than NSA. Are you sure that malicious code will be caught in time like with xz?
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.