somethingsomethingidk

joined 11 months ago

A lot of times you will see the format string for the fedora version in the .repo file. This means its probably looking for f41. Since fedora updates fast, third party repos are usually slow to move to the next version and this repo probably doesnt exist causing dnf to fail. You can try and change the format string to the last available version. It usually works without issue, and updates aren't disabled as long as the vendor updates that version

Start with 10 and subtract 2 for every step

[–] somethingsomethingidk@lemmy.world 16 points 2 weeks ago (1 children)

Companies have until January 1, 2026, to create memory safety roadmaps.

Not really the same as dropping entirely

So this isn't really an answer on how to migrate but this solution has worked well for me.

I define the toolboxes config with it, and if it gets destroyed, recreating it is as simple as creating a new one with the same name. You could upgrade or downgrade by just creating a new toolbox with the version you want.

I was going to say this too, but I've never cross compiled a cmake project so I wasn't sure how much overhead there would be

[–] somethingsomethingidk@lemmy.world 20 points 2 months ago* (last edited 2 months ago) (8 children)

You can compile on a big pi and copy the binary to your zeros. No need to compile on a zero lol

For me, setting up colored man pages is essential. I was hoping to see that in this article, because my methods aren't ideal.

I'm either holding most back a couple versions, using a personal version of gentoos man pager that relies on texinfo and breaks on fedora, or using vim which is not my favorite.

I found this. I didn't look at the code at all but the Readme mentions another project that might help.

https://github.com/ipatix/libvirt-usb-hotplug

I just did the same thing with llama and got the same thing

it still mounts and at first glance seems to be working

What makes you say that?

Show us the output of things like lsblk, mount and cat /etc/fstab to give us a fuller picture

I use privatebin. Has some good features but I dont think it has login

I like to put mine in /var/local/movies etc. to keep the root standard and uncluttered.

Of course it's just personal preference

 

Edit:

I turned off my wifi card, and now it launches immediately. Of course, what is a browser with no internet. But I guess there's something about the network I moved to thats causing the delay. I'll try a different network tomorrow and update for science

OG post: This applies to librewolf and firefox flatpaks. Just to preface, I've been using these flatpaks for years and never experienced anything like this.

This morning I did my business as normal with no issues. I usually open and close firefox alot and it takes maybe 10-30 seconds to start.

Then I shutdown for awhile. Came back and fired up firefox... nothing happened. The process is not using any cpu, it just sits. I kill the process and try again nothing changes. After 3-5 minutes, the window finally pops up.

My system installation of firefox works fine. So does the flatpaks for qutebrowser and tor browser. I ran flatpak repair and reinstalled them. Nothing has changed.

I didn't make any changes to my system. There were no significant updates. I have no idea why this started.

If anybody has any tips on troubleshooting this, I would appreciate it.

Btw I'm on fedora39, and I've tested this on sway, gnome, hyprland, and gnome on xorg.

view more: next ›