Wayland is the fancy new standard that never seems to stably work for me on any of my machines :( Thanks for letting me revert to X in the login screen, GNOME.
The messages you’re getting sound like they’re from the bootloader, so I think secure boot is not causing the problem… Linux should print some stuff right away when it loads, maybe check the architecture of the kernel you’re trying to boot, even an error immediately after loading the kernel should print something unless the architecture is so different that it’s just feeding the CPU bad instructions… Not sure how the bootloader would get installed correctly in that situation though. Is this after installation? Does the system boot from a live USB or cdrom?
Example: there’s another user with sudo access, he has access to my home folder, encrypting the drive doesn’t solve anything. Or maybe you just are not the system administrator.
It’s not my usecase, but it’s definitely a reasonable situation.
Unless some sandboxing or other explicit security measure is in place, any software you run typically has access to your entire home directory, including .ssh/. If any one of those was compromised somehow, they’ve got access to your SSH keys.
Which model do you have? There’s a known issue affecting the sleep/hibernate for the chipset on the new AMD model on the, I believe AMD has already submitted patches to fix it in the next kernel release though.
I used to use Ubuntu before unity and switched to Debian 👑 in 2012. I still have to use Ubuntu for work and I just get on with it. It could be worse… I could have to use windows.
Anyway my main gripes with Ubuntu are snaps and how they keep swapping packages in apt to be installed as snaps .
I dont hate it, its a tool and in most cases I can use it and there is no problem if not there are other options.
I've been really happy with it; I've been using it for templating reports at work for months now. I've just started experimenting with using jinja to pretemplate my template lol.
I'll probably continue down that track to try and automate my workflow away so I can focus on less tedious things, but after you get used to the box encapsulation it becomes fairly easy to work with!
Controversial, but when it comes to hibernating the system, it actually is.
Unfortunately Windows suffers from the s0ix power consumption bugs that’ll drain your battery faster than Linux does, so neither is a very good experience. The current state of modern PC suspend behaviour is just rather terrible.
There is some stuff that I hate, but I tend to come back to it for my home server just because of livepatch, which is nice to minimize the amount of reboots necessary and having a patched kernel for all my LXCs makes then also automatically protected.
If you keep around a bootable rescue stick like System Rescue it has a boot menu entry that will boot the Linux installed on your machine. Once you do that you can run a command or two to reinstall the bootloader. You can search the net or whatever at leisure since it will work fully.
Alternatively, if your system Linux is borked harder, you can boot the rescue Linux and use more advanced methods, depending on what’s wrong. The rescue Linux also has a graphical environment with browser if you need it.
At the very least sometimes you can figure out what went wrong. It may not be much comfort if you lost your system but at least you learn what not to do in the future. Too many people just say “oh, it just broke” and leave it at that.
I think I know what the issue was… I modified the grub.cfg file and ran grub2-mkconfig and I think it was saying it detected a Linux install at my root partition, but didn’t seem to recognize my /boot or /boot/efi partitions and I couldn’t figure out how to edit that via the grub cli. If that wasn’t the case, then that’s okay. I’ll make sure to teach myself a bit more about the bootloader before trying to edit it again
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.