

Finding sites that prohibit rvs kinda depends on the website you’re reserving your site with. You’re basically looking for tent only with vehicle access.
You can try going to an outdoor store and chatting with the employees for suggestions


Finding sites that prohibit rvs kinda depends on the website you’re reserving your site with. You’re basically looking for tent only with vehicle access.
You can try going to an outdoor store and chatting with the employees for suggestions
It gets worse…


I’m pretty clueless at that point. Never seen something like it. Apologies for not actually being able to help out. Hopefully it will be resolved soon, though.
Right? It’s super strange. On a normal system I would try reinstalling GRUB and maybe manually generating the initramfs, maybe compile a new kernel, but idk if I can do that here.
This is probably not the advice you’d like to hear, but I wonder if rebasing to uBlue’s Kinoite would make any difference. Regardless, wish you the best!
That’s actually really interesting, maybe getting away from the fedora ecosystem would help. I do think uBlue is downstream. But it wouldn’t hurt


Perhaps I had to be more clear and explicit, boot twice So yeah it’s not showing anything from the “first” broken deployment. Just to be empirical,
date > time.txt && rebootjournalctl -b -1 and the last entry was 2 seconds after the date output in step one.It is not even getting to systemd.
I tried uninstalling the packages, and rebasing to silverblue. Nothing changed. I think I’m going to just put a pin in it and hope that the next update fixes something haha
speaking of pins
If you’re afraid of losing your working deployment, ensure to evoke the
sudo ostree admin pin 1command to pin it.
This is so important and the first thing I did. I got screwed a few years ago when I first tried silverblue. Everyone talks about how you can just rollback, no one ever mentions that you can lose your last working deployment hahah thanks though


No Nvidia, just intel integrated graphics. Its a dell ispiron 7500.
My system isn’t pristine but it’s not that bad, and I don’t see how any of the packages would cause this problem. I can upgrade fine, there’s no conflicts. I could see it messing up if I tried to layer a different bootloader but it’s nothing like that. Here’s my layered packages anyway
LayeredPackages: alacritty bat btop distrobox fish flatpak-builder kpeoplevcard light lsd mako neovim parallel python3-neovim shellcheck swaybg swayfx swayidle swaylock syncthing
tailscale tmux virt-manager waybar wlogout wlsunset wofi
journalctl shows nothing. That’s what I meant by no logs, I should have been clearer. It’s not even getting that far. It’s like it’s stuck in grub, but only when I try the new kernel.
The only deviation from the vanilla kargs have been for troubleshooting this and I did it in the grub editor so they aren’t persistent. I tried removing rhgb changed quiet to verbose and debug and loglevel=7 just to see if anything would happen. It still just hangs


I left it for an hour and it did nothing :(


I added earlyprintk verbose loglevel=7 to the kernel params in grub and all it says is:
Booting a command list
Still hangs


Nope, escape does nothing. Tried different tty, does nothing. It’s not even showing the fedora symbol under the Dell icon. I am about to try and just let it sit for 15-30 minutes and see if it does anything.


Damn I had no idea, you made my day
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


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.
Underrated meme


Reminds me of this Steve Huges joke


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


If you’re making backups of things you care about and not running sudo rm -rf the command isn’t really dangerous.
But +1 for having it in /tmp
I have a bash function I call tempd that is basically cd $(mktemp -d) I use it so much for stuff I dont really care to keep.


That’s really weird. I set up a test system and I couldnt reproduce. The only thing I noticed errors flooding dmesg about elogind already running when I enabled it following the docs. I guess sddm is already starting it?
I dont see how that would cause your issue though. I would probably just reinstall lol


If you CTRL-ALT-F3 and login to a non graphical session does everything work as intended?


Did anybody think that they did?
I always assumed they were just easier to set up
It looks like it’s partially related to an issue the integration between the desktop app and browser extension.
This issue at least explains needing <browser_stuff>/NativeMessagingHosts
https://github.com/bitwarden/clients/issues/18996
Idk about the other stuff though