Hello everybody! here's the problem: In my EndeavourOS laptop I had a /swapfile, but couldn't take snapshots with snapper because of it (if I understood correctly). So, I created a 16Gb swap partition using GParted from a live USB. Then, I edited /etc/fstab to remove the line about the swapfile and to add the newly created swap partition:

 undefined

    
UUID=506d48e6-1cc0-4136-ba55-6f2f187bcdb1   swap           swap    defaults   0 0
# /swapfile                                   none           swap    sw         0 0

  

I took the UUID from

 sh

    
$ sudo blkid  
/dev/nvme0n1p3: LABEL="swap" UUID="506d48e6-1cc0-4136-ba55-6f2f187bcdb1" TYPE="swap" PARTLABEL="SWAP" PARTUUID="b4543e4e-4623-4317-99aa-086b0e62836e"
...

  

if I run sudo swapon -a it gets enabled correctly and it all works fine. The problem however is that when I reboot the machine, it gets stuck in the systemd screen saying "a job is running for /dev/disk/etc..." forever, and the only way I have to log in is to boot from a live

SOLVED: BananaTrifleViolin's post contains the solution.

Flatseal won't start by itself anymore, which is a known issue. I got it running by running

 undefined

    
GSK_RENDERER=gl com.github.tchx84.Flatseal

  

and inspired by a response in the above linked issue, I wanted to add GSK_RENDERER=gl as a variable in Flatseal so I could open it without having to manually run this in the terminal.

However, I seem to have screwed that up, and written GSK_RENDERER=ng instead, because the application still won't run, and now I get the following output anytime I try to open it by the method above:

 undefined

    
(com.github.tchx84.Flatseal:2): Gsk-WARNING **: 22:09:54.997: Unrecognized renderer "ng". Try GSK_RENDERER=help
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:782: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:814: FINISHME: support more multi-planar formats with DRM modifiers
  

I finally took the time to move my gaming rig to Bazzite because I don't boot it that often, and because I don't want to spend half the little time I have for gaming doing updates and maintenance.

Most of my games are on an ext4-formatted secondary drive. Note: They worked perfectly on Manjaro and Nobara, the previous distros I used on this machine.

They are recognized by Steam, I can install and uninstall games just fine, it's just that... they don't launch. At all. Native or Proton. Like if I was on an exFAT partition. The "Launching" button switches back to "Play" almost instantly. If I move a game to my main home partition, it launches fine.

Has anyone encountered this issue before?

Where/how could I get detailed logs to try and pinpoint the issue?

Thanks!

Edit: Solved! The issue was with fstab configuration, always specify exec AFTER users, despite the doc telling you that order doesn't matter ;)

Wrong fstab entry :

`UUID=blah-blah-blah /my/mount/point ext4 def

I've been trying to find it for a week now but I don't seem to have any luck so far. I had seen a video about it a couple years back from a brittish YouTuber who mainly reviews DEs, although his name slipped my mind.

It is a very minimalist UI with not much customisation apart from dock size, transparency and positioning, it is niche and not an extension or customisation of another DE, and I believe it may still be in beta, although I'm unsure.

Also I apologise for the image quality, it was the only one I could find. If anyone can identify it I would really appreciate it, although I understand if you are unable, thanks.

EDIT: Also I checked if it was Orion OS or other OS names in the text but none of them matched.

Playing modded Witcher 3 through proton. After dying and loading the last save (and perodically while playing) gpu clocks drop such that the framerate is barely above 60 (and very stuttery). Tried enabling framegen, same thing but it drops to 70 ish. It sometimes goes back to normal if I alt tab out and back, but that gets annoying when playing with a controller (especially if it happens in the middle of combat).

I can see the gpu clock dropping and going back up in system monitor. This doesn't happen with any other game. Any advice?

The device with I2P is behind a NAT router without UPnP. The device has a firewall but has opened the UDP and TCP port for internet facing communication. The ports from the router are forward to the device's ports. Are there any ports missing?

Edit: I finally figured it out. The port forwarding was only for TCP. It would be good to have logs or some kind of status window stating why it thinks it's firewalled though.

Anti Commercial-AI license

Edit: The issue appears to have been some intermittent problem and it was solved (perhaps by chance) a few minutes after contacting support.

I woke up this morning to find out that the images are not accessible through the site.

This seems to be an issue on the side of the object storage provider, as the "bucket" is not accessible through the provider's web portal. I have reached out to them to hopefully sort this out ASAP.

SOLVED

Edit: Solved using workaround of creating a systemd service that disables GPP0 wakeup: https://forums.linuxmint.com/viewtopic.php?t=364220&start=20

Hey everyone!

The suspend feature has never worked on my system, so I always turned it off in the settings. But now, with the electricity prices going up in my country (we have the most expensive electricity in Europe, lol), I figured it’s a good time to tackle this.

When the system tries to go into sleep mode, it just wakes up right away, and the monitors don’t show anything (no signal). I’ve got a backlit keyboard and an RGB mouse, but they don’t light up during this, and the caps lock key doesn’t respond when I press it.

I’m on kernel 6.12.7 and I updated the BIOS a few days ago, but the problem is still there.

My hardware:

• CPU: Ryzen 5 5600
• MOBO: GIGABYTE B550 GAMING X V2 (rev. 1.3)
• GPU: RX 6700 XT
• PSU: SilentiumPC Supremo M2 (600W I guess?)
• CASE: be quiet! Pure Base DX500

If anyone has any ideas on ho

Original Post:

I recently had a Proxmox node I was using as a NAS fail catastrophically. Not surprising as it was repurposed 12 year old desktop. I was able to salvage my data drive, but the boot drive was toast. Looks like the sata controller went out and fried the SSD I was using as the boot drive. This system was running TurnKey FileServer as a LXC with the media storage on a subvol on a ZFS storage pool.

My new system is based on OpenMediaVault and I'm am happy with it, but I'm hitting my head against a brick wall trying to get it to mount the ZFS drive from the old system. I tried installing ZFS using the instructions here as OMV is based on Debian but haven't had any luck so far.

Solved:

1. Download and install OMV Extras
2. OMV's web admin panel, go to System -> Plugins and install the Kernel Plugin
3. Go to System -> Kernel and click the blue icon that says Proxmox (looks like a box with a down arrow as of Jan

[Thanks morgunkorn for replying to show where it is: on our Profile pages, 4 lines beneath our usernames.]

How can I find a list of the Lemmy posts I've saved in my browser?

Saving posts are done by clicking on the star icon. Once saved the icon becomes orange.

Can't find them on my Profile page, or via the Search page, and searches seem to only answer it for apps.

For a long time, when using my computer (Arch linux), I would sometimes run into this problem. When trying to open an application in a new window, I'll be met by:

 undefined

    
Invalid MIT-MAGIC-COOKIE-1 key
cannot open display: :0


  

I've tried a lot of "solutions" without luck, but I've finally found a way to consistently reproduce the error. It happens everytime I connect to a new wifi.

I found this 9 year old post about the same problem, but it does not include a real solution or the cause of the problem.

I'll try asking it here, to see if anybody knows why it happens and how to solve it, and perhaps to help others with the same problem find the cause of this error. It is such a relief for me, knowing that it is caused by changing wifi.

In advance, thanks for the help/feedback :)

Hi, I’ve got an issue with 2FA. I got logged out on my desktop PC and when I try to log back in, the 2FA code that I have doesn’t work. I’m still logged in on my phone but I’m no sure how to proceed from here?

SOLVED: My desktop machine was looking for a NTP server that was no longer responding. Changed to a working NTP server and all is well. I had drifted 66 seconds back since 9 Sept 2024.

I've been trying to code python on my deck and I can't for the life of me figure out how to activate the virtual environment. I keep using "source .venv/bin/activate" and it does nothing. No errors, no feedback, doesn't hang, doesn't use the environment, nothing.

I've tried installing Kitty to see if it was an issue with Konsole but the exact same thing happens. It works fine in Visual Studio Code but I do t want to have to open that every time I try and run a command.

Anyone know why this could be or what I could do to fix it?

Edit to add: This is my first real attempt at Linux idk what I'm doing in a very broad way. Only other time I tried was nearly 15 years ago dual booting Windows/Ubuntu but that lasted like a week because Windows kept blowing up the config and I needed some Windows only programs for school

Solved edit: I don't exactly know what was up. If I made the venv with the terminal, it would work in the terminal but not work with VSCode's terminal. If I made it in VSCo

Hey all, had some weirdness with the native discord app on Arch today. Was trying to screen share and discord just noped, went hunting for logs but no dice. I tried a few different programs with screen share, but it just seems to completely nuke disord. Any ideas? Anyone else have the same issue? Any clue where I might find crash logs?

Edit: installed Vesktop, problem went away, thanks everyone for the input.

The posts I can't comment:
https://lemmy.world/post/23853105
https://lemmy.world/post/18437211

Greetings. I'm using PiVPN right now. Works great for me, connecting via Wireguard clients and able to use both WAN and LAN. There is one client that I would like to allow to connect to my VPN and be able to use the WAN only, and this is where I'm running into some trouble finding a solution. I took a few swings at the problem by trying to narrow down the Allowed IPs in the wg config file but that not only didn't work but in hindsight it seems like an ineffective way to attack the problem to begin with.

Is there a way to set this up, either via something in the client config file or something else on the hosting side? I don't want to disallow all Wireguard clients from accessing the LAN+WAN. It's just one particular client that I want to allow access to only the WAN.

Thanks!

It has a very specific use and context

I’ve been using LaTeX to prepare legal documents in PDF format with a tree of PDF bookmarks like this:

• list of facts
  -- exhibit A
  -- exhibit B
  -- exhibit C
  -- exhibit D
• law
  -- national
  -- international

So if you click “exhibit C” in the sidebar of the PDF viewer, it jumps to that document which has “exhibit C” in the corner of the doc in a bubble, along with commentary like “redactions in Bob’s version but not Alice’s”. I have no idea to what extent courts and lawyers appreciate or oppose metadata like this.

Some recipients want to see a verbatim version of the document without my markups. I am tempted to use the \usepackage{attachfile} … \attachfile{exhibit_c.pdf} which puts a thumbtack on the page whereby someone can click it and extract the original version without markups. The problem is that this embeds another redundant copy of the document in the PDF so every document presented will have two copies and ultimately double the size of the PDF.

when I run on my treadmill, it has suddenly started feeling like it briefly stops the belt whenever I land my stride. I've tried greasing the board underneath the belt with silicone grease according to the manual, but that didn't help. Any advice on how to fix this? Could it be the belt that needs tightening?

[SOLUTION] It was just belt tension, it had become too slack. A quick tightening fixed the issue completely.