These packages are not available in other distros and you can get them for free for up to 5 machines. Previously you weren’t able to get them at all without paying for corp support.
My understanding (and I’m happy to be corrected) is that feature and security updates will continue to be provided for Ubuntu.
Ubuntu Pro’s update badgering seems to allow for updates to be provided for packages that aren’t part of the base distro makeup - like packages that are held in non-Canonical repos.
For home users, Ubuntu Pro is free… for now.
I don’t think it’s anything horrendously bad, but the way it’s been rolled out is pretty fuckin’ far from good too.
This is correct. There’s no need for Ubuntu Pro to get the updates you used to get prior to Ubuntu Pro’s introduction. Ubuntu Pro gives additional updates that were not available before and the community does not provide. It’s free for up to 5 machines so you should register and enable it. There’s no downside for now.
If you typed your password wrong too many times you may have been locked out for a certain amount of time (normally 30 mins after 3 wrong attempts). In this situation sudo will not display a different error it will still say the password is wrong. You can clear the failed attempts using the command “faillock --reset”. Hopefully that solves it if not check your caps lock, and keyboard layout.
Are you sure you are inputting the right password? For instance, are you sure your keyboard layout is correct? If the keyboard layout is different, you may think you type one thing but type another.
It is also possible that you have simply misspelled the password during setup. A reinstall is the only way to fix that I think.
Unless I’m missing something, the sudo password should be the user’s password, so unless they’ve never logged out as their user, they should’ve already used the password to login. I wonder if they’re trying to use the root/su password instead of their own user’s
I don’t run Ubuntu, but was surprised I’d not heard of this.
This is canonical trying to make money for security updates, and stopping companies just running it for free, instead of using a licence (my own take). They are following a model by IBM, apparently.
That’s not at all what’s happening. Canonical have not put anything that was previously available without an account, behind this service. As others have noted, they’re making something that was previously paid-only, free for up to 5 machines.
AskUbuntu.com by far. Many years ago it replaced ubuntuforums.org for support queries. As others have pointed out, the current discussion place is discourse.ubuntu.com. But for support questions AskUbuntu.com is the best place and the best format because it’s easy to find the questions and the answers from within and via search engines without having to sift through tons of discussion responses. Anything that’s already answered becomes easy to find for the next person having this problem. Sometimes when I find the solution to a problem I had that wasn’t obvious, I add a question and answer it myself for others to find. Of course you can ask here as well. ☺️
I am certain I am inputting the same password that I am using for authentication during login. Certain in the sense that I have triple checked that I am typing the correct keys on my laptop keyboard, and the password only contains lower case letters.
In terms of keyboard layout, I have confirmed I am using US. Is there a different password specific for sudo that I am missing here? I’ve never set the password for root, since this requires the use of sudo and I’ve never been able to access sudo.
You can boot into recovery mode from the boot menu, which will give you root access without any password. From there you can reset your user password with passwd.
Or, if recovery mode does ask for a password...you can edit Linux’s commandline arguments in the bootloader to add init=/bin/sh and then it will boot to a root shell without a password. the rootfs will be mounted read-only, so, before using passwd you need to first run mount -oremount,rw / to remount it read-write. then run passwd (to set root’s password) or passwd user (to set user’s), and then run sync to ensure the changes are flushed to disk, and then sync twice more for superstitious/historical reasons, and then turn the computer off and back on. (the reboot command will not work here.)
Could try a new hdmi cable or if possible another hdmi slot on the card as well as the display if it has one. I would start with switching over teh next slot on the GPU, then switching over to the next slot on the display, then a new cable
ubuntu
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.