I have been flopping back and forth between arch and windows the last few years depending on the weather as I like to game in the garage when it's really nice out. I have been using an app called Apollo. Which is a fork of Sunshine with SudoVDA implemented. SudoVDA is perfect for my use cases. It allows you to spin up a virtual screen of whatever hz/size you'd prefer even HDR. This allows me to remotely game while leaving my gaming PC effectively running "headless" until the virtual screen is closed(you close the connection) I haven't found a way to implement a similar thing on Linux. The main sticking point being the headless application of it. I had a solution at one point that "worked" but only for 1440p 120hz and I'd have had to download or create some monitor profile file thing to change it and it was over my head and did not work well for my usecase as I also like to remote into my PC while working to game on breaks or lulls in tickets which is 1920x60 so then I had to spin up another virtual screen and things got broke and I gave up and eent back to using Apollo on windows as it's just so damn easy to use lol. I'm not dedicated to using sunshine/moonlight as my connection software id just like to find something as seemless as Apollo/moonlight or Apollo/Artemis(Android) is. Anyone know of any solutions? I'm fine with distro swapping. I've used arch based, fedora based, and Debian based distros in the past.

Edit: this will all be local connection. Nothing on the actually internet.

Hi, i hope someone can help me with this one

I logged-in, changed the touchpad behaviour,. It works as expected. But when log-out, the settings didn't change in the greeter. Reboot doesnt change that.

:~$ cat/etc/lightdm/lightdm.conf | grep greeter-session

greeter-session=lightdm-greeter

Is that the right greeter? I heard it should be greeter-session=lightdm-gtk-greeter instead. Does LightDM default to a different setting?

What can i do to get the touchpad right in the greeter?

Thanks for your help!

I've been a Linux user for almost 30 years but never had to tinker with any software to solve a problem. Cue a Fedora upgrade to somewhere around 38. I've been using the multiseat feature for years. It's alway seemed very fragile. With this upgrade it was seriously broken. I managed to find a patch someone made that for some reason wasn't accepted into the gnome-shell package. I was able to grab the patch, rebuild the RPM package and install the update to my system and restore multiseat. It was actually pretty effortless. The hardest part by far was finding the fix. Now updating to Fedora 41 I had to do the same process again. Apparently the problem still exists. This time I had to create a new patch as the original one wouldn't apply anymore but that wasn't very hard. It was very satisfying to be able to fix that problem and it was only possible due to the OSS community.

https://gitlab.com/christosangel/audacity-nord-theme

• Copy ImageCache.png to $HOME/.audacity-data/Theme/

• Open audacity, Select Edit=>Preferences=>Theme:Custom

bazzite seems to be so crucial for widespread adoption, watching with great interest!

Text: Allows you to determine whether to limit CPUID maximum value. Set this to enabled for legacy operating systems such as Linux or Unix.

Found this in the BIOS of a Gigabyte Z97X-UD3H mobo.

I just installed Debian with the KDE desktop and I'm looking to see what kind of packages are available in the Discover store by default as they are not labeled i.e., Snaps/Flatpak. Should I install Flatpak? Thanks I don't to break anything

cross-posted from: https://lemmy.ca/post/45140185

I was able to literally 1 hour ago.

I changed my DNS from Next DNS to CIRA Canadian Shield (Protected) to test it out.

Then I was only able to connect to the internet through Mulvad VPN.

Then I changed back to Next DNS and I observe the same behaviour.

How do I determine what is causing the problem?

How do I solve it?

[solved]: gHub-GUI seems outdated. openRGP does what i need instead.

Hi, i'd like to use my Logitech G915 LEDs properly under KDE neon and since logitech only provides for Win or Mac, someone recommended gHUB-GUI. https://github.com/ysph/gHub-GUI

I tried the little installation instructions on https://github.com/ysph/gHub-GUI but something does not seem to work. This is not my first git app(?), but the first one i can't seem to use. I tried to ask ChatGPT but it...

spoiler

poured kerosene all over itself, jumped head first off the autobahn bridge, got ran over by a Lastkraftwagen, biting a cyanide pill. That

...didn't help.

Can anybody please point me in the right direction? I am fine with the CLI. I cloned the project, Installed those mentioned dependencies, but ~/gHub-GUI$ make all returns

gcc -g main.o mouselist.o -o ghub-gui -lusb-1.0. And i dont kow what that means.

Thanks!

The final issue of Linux Format, the UK's best selling monthly Linux magazine, has gone on sale. The first issue launched in May 2000.

Hi everyone,

Recently i discovered Aneko on Android, I want to find something similar on linux. Oneko seem to be fun but I am using wayland(Hyprland). Is there anything similar on wayland linux? Is this even possible with current state of wayland protocal?

Hello everyone,

I wanted to ask if anyone has a preferred software for the purpose of creative writing.

Libre Office Writer is great of course, but just as software like LogSeq or Obsidian exist for the note taking process, I was wondering if there is anything that is specifically geared toward the creative writing process.

I know that there are federated blog platforms which focus on this in their presentation, but was curious about applications specifically.

FOSS is definitely preferable.

Thanks!

when I say trim I don't mean to time trim a file, like getting rid of the last 2 minutes of the mkv file, but to picture trim every frame of the mkv file to get rid of black margins to both left and right of the actual image.

Files were originally recorded on 4:3 aspect ratio (some are movies from the 1950's) but the encoder somehow created / copied huge black margins to both left and right of the actual image. I want to get rid of these.

Some of my files are 30 minutes long but others 2 hours.

if ffmpeg is the application I need, could anyone knowledgeable enough write the actual command?

can it be done for several files automatically?

NOTE

For some reason, Lemmy isn't allowing me to upload more than 11 images. I will try to add the missing images after posting. It will take a while.

Edit: It isn't allowing me to add more images. If anyone is interested, I will upload the images elsewhere.

Introduction

Setting up a secure coding environment for the Rust programming language on secureblue isn't hard to do, but it's difficult to figure out on your own. That is why I am making a guide explaining how to do it yourself.

For this tutorial, I will be using the silverblue-main-hardened:latest image of secureblue. For this tutorial, I am also assuming you have enabled Flatpak permission lockdown by running ujust flatpak-permissions-lockdown.

Install a code editor

You can install whichever code editor you want, but for this tutorial I will be using VSCodium which is an open source binary of Microsoft's Visual Studio Code without telemetry.

Command-line instructions

Open the terminal.

VScodium can be installed using the following command:

flatpak install com.vscodium.codium

Sources: 1, 2

You will be prompted to proceed with changes to the user installation. After reviewing the changes, you can press enter. VSCodium will be downloaded and installed for the current user.

You may close the terminal now.

User-interface instructions

1. Open GNOME Software.

2. Type VSCodium. This should begin typing in a search bar, and VSCodium should show up as a search result.

3. Select VSCodium (the blue one). VSCodium - Insiders (the orange one) is the nightly release of VSCodium, and is not recommended for daily use.

4. Click the blue Install button on the top right. VSCodium will be downloaded and installed for the current user.

You may close GNOME Software now.

Install the Rust SDK

Rust provides multiple ways of installing. On secureblue, things are more locked down, especially with VSCodium being installed as a Flatpak. Rather than layering Rust as a system package and giving VSCodium invasive permissions to make it work, there is a much more elegant way to install Rust that isn't mentioned in their install instructions.

Flathub provides an SDK Extension for Rust that can be used for Flatpak code editors, such as VSCodium. This can only be installed from the command line. Trying to install it from GNOME Software will install an outdated version of the Rust SDK.

Open the terminal.

First, we need to find the branch of org.freedesktop.Sdk. This will allow us to install the correct version of the Rust SDK.

The branch of org.freedesktop.Sdk can be found using the following command:

flatpak info org.freedesktop.Sdk

Make a note of the version number next to the Branch: section. In my case, it is 24.08.

The Rust SDK can be installed using the following command:

flatpak install org.freedesktop.Sdk.Extension.rust-stable

You will be prompted to select which ref you would like to install. Find the version that matches the branch of org.freedesktop.Sdk. Type the number corresponding with the version (in my case, 5), and press enter.

You will be prompted to proceed with changes to the user installation. After reviewing the changes, you can press enter. The Rust SDK will be downloaded and installed for the current user.

You may close the terminal now.

Grant Flatpak permissions

Assuming you enabled Flatpak permission lockdown, VSCodium won't have permission to access everything it needs to work properly. We need to grant these permissions manually.

We will need to create a directory to act as your project directory. VSCodium will have access to every file in this directory, so it is best to only use it for VSCodium. I am deciding to create a folder in my home directory named VSCodium to store all of my VSCodium projects.

VSCodium will need the following permissions to work:

• The Network permission, in order to efficiently install extensions and update them automatically.
• Access to a dedicated project directory, in order to create workspaces.
• Permission to access the Rust SDK, in order to support the Rust language.
• Optional access to Development syscalls, in order to use debugging extensions.

Command-line instructions

Open the terminal.

VScodium can be granted the Network permission using the following command:

flatpak override -u --share=network com.vscodium.codium

The -u flag is an alias for --user, which will change the permission only for the current user.

[INSERT IMAGE HERE]

A project directory can be created using the following command:

mkdir VSCodium

[INSERT IMAGE HERE]

VSCodium can be granted access to the project directory using the following command:

flatpak override -u --filesystem=~/VSCodium com.vscodium.codium

[INSERT IMAGE HERE]

VScodium can be granted access to the Rust SDK using the following command:

flatpak override -u --env=FLATPAK_ENABLE_SDK_EXT=rust-stable com.vscodium.codium

[INSERT IMAGE HERE]

You may close the terminal now.

User-interface instructions

1. Open Flatseal. This should be installed by default, but if you decided not to install it during the post-install of secureblue, it can be installed from GNOME Software.

2. Type VSCodium. This should begin typing in a search bar on the left, and VSCodium should show up as a search result.

[INSERT IMAGE HERE]

3. Select VSCodium.

[INSERT IMAGE HERE]

4. To grant VSCodium the Network permission, enable the switch next to the Network permission. It should turn blue, indicating that the permission has been granted.

[INSERT IMAGE HERE]

5. Open Files

[INSERT IMAGE HERE]

6. Right click, and click on the option labeled New Folder... (This can also be done using Shift+Ctrl+N)

[INSERT IMAGE HERE]

7. Enter VSCodium in the text field labeled Folder Name.

[INSERT IMAGE HERE]

8. Click Create to create the folder. This will create a project directory for VSCodium to use.

[INSERT IMAGE HERE]

9. In Flatseal, scroll down to the Filesystem section.

[INSERT IMAGE HERE]

10. Click on the folder with a plus icon under the Other files section. An empty text field should appear.

[INSERT IMAGE HERE]

11. Click on the empty text field.

[INSERT IMAGE HERE]

12. Enter the following into the text field:

~/VSCodium

[INSERT IMAGE HERE]

13. To grant VSCodium access to the Rust SDK, scroll down to the Environment section.

[INSERT IMAGE HERE]

14. Click the plus icon on the top right. An empty text field should appear.

[INSERT IMAGE HERE]

15. Click on the empty text field.

[INSERT IMAGE HERE]

16. Enter the following into the text field:

FLATPAK_ENABLE_SDK_EXT=rust-stable

[INSERT IMAGE HERE]

You may close Flatseal now.

Open VSCodium

Now that VSCodium has the necessary permissions to function, we can finally run it.

Command-line instructions

Open the terminal.

VScodium can berun using the following command:

flatpak run com.vscodium.codium

[INSERT IMAGE HERE]

User-interface instructions

1. Press the Super key to view the dock.

2. Click on the Show Apps button (nine dots) on the bottom right to show a list of installed apps.

3. Click on the VSCodium icon to open it.

Install the rust-analyzer extension

Upon first launching VSCodium, you will be presented with a README.md file.

[INSERT IMAGE HERE]

This file has information about using VSCodium as a Flatpak. Since we have already granted it the necessary permissions, this file can be ignored.

We now need to install the rust-analyzer extension. This extension will give us a comfortable Rust development environment in VSCodium.

Keyboard instructions

Launch the VSCodium Quick Open by using Ctrl+P.

[INSERT IMAGE HERE]

Enter the following command:

ext install rust-lang.rust-analyzer

Sources: 1

[INSERT IMAGE HERE]

Press enter to install the rust-analyzer extension.

[INSERT IMAGE HERE]

You will be prompted to trust the publisher and install the extension. After reviewing the prompt, you can press enter to select the Trust Publisher & Install button on the bottom right.

[INSERT IMAGE HERE]

You may be prompted to trust the authors of the files in this workspace. After reviewing the prompt, you can select the Install button. The rust-analyzer extension will be downloaded and installed for the current profile.

Mouse instructions

1. Click on the Extensions menu on the left. (This can also be opened by using Ctrl+Shift+X)

[INSERT IMAGE HERE]

2. Enter rust-analyzer into the search bar. This will search for the extension we need.

[INSERT IMAGE HERE]

3. Click on the extension labeled rust-analyzer.

[INSERT IMAGE HERE]

4. Click the Install button for the rust-analyzer extension.

[INSERT IMAGE HERE]

5. You will be prompted to trust the publisher and install the extension. After reviewing the prompt, you can click on the Trust Publisher & Install button on the bottom right.

[INSERT IMAGE HERE]

6. You may be prompted to trust the authors of the files in this workspace. After reviewing the prompt, you can click the Install button. The rust-analyzer extension will be downloaded and installed for the current profile.

[INSERT IMAGE HERE]

The rust-analyzer extension is now installed.

Create a new project

Now that we have the rust-analyzer extension installed, we can create a new Rust project.

The keyboard instructions are broken due to the Ctrl+K keybind being unfunctional, and the Ctrl+O keybind being binded to the wrong option. Because of that, only mouse instructions are available for this step.

1. Click on the File dropdown on the top left.

[INSERT IMAGE HERE]

2. Click on the option labeled Open Folder...

You will get a dialogue saying the following:

Oops! Something went wrong.
Unable to find "/app/share/ide-flatpak-wrapper". Please check the spelling and try again.

[INSERT IMAGE HERE]

This can be ignored. It is appearing because we never granted VSCodium access to a specific folder, and it has no effect.

3. Click on OK to dismiss it.

[INSERT IMAGE HERE]

4. Double click on the VSCodium folder to enter it.

[INSERT IMAGE HERE]

5. Right click, and click on the option labeled New Folder... (This can also be done using Shift+Ctrl+N). Alternatively, select the folder with a plus icon on the top right.

[INSERT IMAGE HERE]

6. Enter the name of your project in the text field labeled Folder Name. For this example, I will create a folder named example.

[INSERT IMAGE HERE]

9. Click Create to create the folder.

[INSERT IMAGE HERE]

10. Click Open in the bottom left to open the folder.

[INSERT IMAGE HERE]

11. You will be prompted to trust the authors of the files in this folder. After reviewing the prompt, you can select the Yes, I trust the authors button.

[INSERT IMAGE HERE]

12. Press Ctrl+` to open the terminal.

[INSERT IMAGE HERE]

13. The project can be initialized using the following command:

cargo init

[INSERT IMAGE HERE]

You have now created a Rust project, and you can get started coding in Rust.

Optional: Support for debugging

Right now, there are no debugging extensions installed. The two recommended debugging extensions are CodeLLDB and Native Debug. I prefer CodeLLDB because, as of writing this, Native Debug has not been updated in over a year. It is still in active development, but there has not been a release in over a year.

Keyboard instructions

Open VSCodium.

[INSERT IMAGE HERE]

Launch the VSCodium Quick Open by using Ctrl+P.

[INSERT IMAGE HERE]

Enter the following command:

ext install vadimcn.vscode-lldb

Sources: 1

[INSERT IMAGE HERE]

Press enter to install the CodeLLDB extension.

[INSERT IMAGE HERE]

You will be prompted to trust the publisher and install the extension. After reviewing the prompt, you can press enter to select the Trust Publisher & Install button on the bottom right. The CodeLLDB extension will be downloaded and installed for the current profile.

[INSERT IMAGE HERE]

You will see a prompt on the bottom right saying the following:

Completed installing extension. Please restart extensions to enable it.

Select Restart Extensions to restart the extensions.

[INSERT IMAGE HERE]

Mouse instructions

1. Click on the Extensions menu on the left. (This can also be opened by using Ctrl+Shift+X)

[INSERT IMAGE HERE]

2. Enter CodeLLDB into the search bar. This will search for the extension we need.

[INSERT IMAGE HERE]

3. Click on the extension labeled CodeLLDB.

[INSERT IMAGE HERE]

4. Click the Install button for the CodeLLDB extension.

[INSERT IMAGE HERE]

5. You will be prompted to trust the publisher and install the extension. After reviewing the prompt, you can click on the Trust Publisher & Install button on the bottom right. The CodeLLDB extension will be downloaded and installed for the current profile.

[INSERT IMAGE HERE]

You will see a prompt on the bottom right saying the following:

Completed installing extension. Please restart extensions to enable it.

Select Restart Extensions to restart the extensions.

[INSERT IMAGE HERE]

The CodeLLDB extension is now installed.

Grant VSCodium ptrace access

If you try to debug a program using a debugger extension, you will receive the following error:

VSCodium
Cannot launch '/var/home/anonymous/VSCodium/example/target/debug/example': ptrace failed: Operation not permitted

[INSERT IMAGE HERE]

The reason for this is because VSCodium does not have permission to access development syscalls.

Command-line instructions

Open the terminal.

VScodium can be granted the Development syscalls permission using the following command:

flatpak override -u --allow=devel com.vscodium.codium

[INSERT IMAGE HERE]

You may close the terminal now.

User-interface instructions

1. Open Flatseal.

2. Type VSCodium. This should begin typing in a search bar on the left, and VSCodium should show up as a search result.

[INSERT IMAGE HERE]

3. Select VSCodium.

[INSERT IMAGE HERE]

4. To grant VSCodium the Development syscalls permission, scroll down to the section labeled Allow.

[INSERT IMAGE HERE]

5. Enable the switch next to the Development syscalls (e.g. ptrace) permission. It should turn blue, indicating that the permission has been granted.

[INSERT IMAGE HERE]

You may close Flatseal now.

Enable anti-cheat support

Even though VSCodium has access to ptrace, the system still does not permit it. This is to defend against basic security concerns. secureblue provides a toggle to enable support for anti-cheat, which will allow VSCodium to access ptrace.

Open the terminal.

Anti-cheat support can be enabled using one of the following commands:

ujust toggle-anticheat-support

or

ujust toggle-ptrace-scope

Sources: 1

[INSERT IMAGE HERE]

You will be prompted for your administrator passphrase. After reviewing the prompt, enter your passphrase and click Authenticate. This will enable anti-cheat support.

[INSERT IMAGE HERE]

You will need to restart your device to complete the changes.

Command-line instructions

Open the terminal.

The device can be restarted using the following command:

reboot

User-interface instructions

1. Click on the status bar on the top right.

2. Click on the power button.

3. Click on the option labeled Restart....

4. You will get a prompt saying the following:

Restart
The system will restart automatically in 60 seconds

5. Click on the button labeled Restart to restart the system now.

Anti-cheat support is now enabled, and debugging extensions will work.

E: I AM NOT USING FEDORA. Please stop linking to guides for Fedora. They will not work. uBlue/Bazzite does not use dnf.

---

I got a free iMac. Installed Linux on an external drive. Bazzite, specifically. WiFi does not work. My research leads me to a problem with proprietary Broadcom drivers but no solutions. If you know how to get this working, your advice would be appreciated.

Also if there's another distro that works "out of the box" on Macs with GNOME I'd be open to installing that as well.

E: "System information" says it is a

Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1772.1)

I had backblaze, and it's really a bummer they don't support linux. The closest one I've found is Icedrive, but it costs a bit more. I don't mind paying a bit more though for a FOSS solution (technially not free but yeah). I probably only have 2 TB of actual important stuff but it would be nice to have more for future.

Hi all, Sony loves these data collection messages at the beginning of their games. They don’t even give you the option to opt-out. It is mandatory and is either “Full data” or “limited”. I don’t want to give them either. Is there a straight forward way to do this? Thanks in advance.

Hi, I've been thinking about switching from Win11 to Linux Mint due to Microsoft collecting lots of data. My current setup has been cobbled together over the past decade and consists of a C drive NvME, 1 old SATA SSD, and 2 HDDs. I have games installed across all of the non-C drives, some from steam some not.

Windows tells me each drive by letter. I installed Mint on a virtual machine to get a look, but it couldn't read any of my files. I don't want to wipe my C drive without knowing that at least the other drives will be readable if I make the switch.

How does Linux account multiple hard drives? I'm so used to how Windows does it that I'm worried about switching over and losing access to my other drives. Thanks!

I didn't intentionally pick Ubuntu, my pc went shit and I needed to install some os and the only one I had available in a usb was Ubuntu noble.

Laptop specs: I think a 7th gen inter i5, 8 GBs of ram and (the issue) a 125 GB M2.Sata SSD

I'm not really going to play games on it, it's one of those weird laptops that folds and can use a stylus.

So what would you suggest for something light in size and good with a stylus.