Is there an official resource where is available a complete list of all the Ubuntu releases but including the respective version of systemd applied for each one? I found this systemd/NEWS page where appears each systemd version but I want to know for each Ubuntu release what was the systemd version applied.
For Ubuntu Desktop 22.04 was installed Brave web browser according with the official instructions indicated at Release Channel Installation - Debian, Ubuntu, Mint. Therefore as follows:
sudo apt install curl
sudo curl -fsSLo /usr/share/keyrings/brave-browser-archive-keyring.gpg https://brave-browser-apt-release.s3.brave.com/brave-browser-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main"|sudo tee /etc/apt/sources.list.d/brave-browser-release.list
sudo apt update
sudo apt install brave-browser
The process was successful but in that process and for each execution of the apt update command appears:
sudo apt update
...
Hit:3 https://brave-browser-apt-release.s3.brave.com stable InRelease
...
Fetched 3,590 B in 3s (1,411 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com stable InRelease' doesn't support architecture 'i386'
Observe the latest line (split in many lines for presentational purposes):
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository
'https://brave-browser-apt-release.s3.brave.com stable InRelease' doesn't support
architecture 'i386'
I know it is a Note due the N: part, but being curious: How to remove the doesn't support architecture 'i386' message?
Just being curious about the following situation
When the adduser command is executed as follows:
sudo adduser optimusprime
Adding user `optimusprime' ...
Adding new group `optimusprime' (1015) ...
Adding new user `optimusprime' (1013) with group `optimusprime' ...
Creating home directory `/home/optimusprime' ...
Copying files from `/etc/skel' ...
New password:
Retype new password:
passwd: password updated successfully
Changing the user information for optimusprime
Enter the new value, or press ENTER for the default
Full Name []:
Room Number []:
Work Phone []:
Home Phone []:
Other []:
Is the information correct? [Y/n]
Observe there are 5 optional fields available to write data. If they are left empty as default when the cat /etc/passwd command is executed, the record for that user appears as follows:
optimusprime:x:1013:1015:,,,:/home/optimusprime:/bin/bash
Observe the ,,, GECOS part. It represents 4 fields as A,B,C,D and not 5 as A,B,C,D,E. Why this difference or mismatch between them? To be honest I expected
optimusprime:x:1013:1015:,,,,:/home/optimusprime:/bin/bash
Which represents the 5 fields available through the adduser command too.
And if is used the usermod command as follows:
sudo usermod -c "A,B,C,D,E" optimusprime
The user appears as:
optimusprime:x:1013:1015:A,B,C,D,E:/home/optimusprime:/bin/bash
I know is possible even add more fields through the usermod command as follows:
sudo usermod -c "A,B,C,D,E,F" optimusprime
sudo usermod -c "A,B,C,D,E,F,G" optimusprime
Therefore these commands executions are reflected as follows respectively
optimusprime:x:1013:1015:A,B,C,D,E,F:/home/optimusprime:/bin/bash
optimusprime:x:1013:1015:A,B,C,D,E,F,G:/home/optimusprime:/bin/bash
At a first glance is not clear if GECOS as minimum is based on 4 or 5 fields.
After to did do an upgrade through VirtualBox for Ubuntu Desktop 20.04 to 22.04 - focal to jammy - at the /etc/apt/sources.list.d directory exists the mysql.list file.
According with a research was indicated to open that file and change from local to jammy. Therefore I have now
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out entries below, but any other modifications may be lost.
# Use command 'dpkg-reconfigure mysql-apt-config' as root for modifications.
deb http://repo.mysql.com/apt/ubuntu/ jammy mysql-apt-config
deb http://repo.mysql.com/apt/ubuntu/ jammy mysql-8.0
deb http://repo.mysql.com/apt/ubuntu/ jammy mysql-tools
#deb http://repo.mysql.com/apt/ubuntu/ jammy mysql-tools-preview
deb-src http://repo.mysql.com/apt/ubuntu/ jammy mysql-8.0
manueljordan@mac2013-vb143:/etc/apt/sources.list.d$
Now when is executed the sudo apt update command happens the following:
sudo apt update
Get:1 http://repo.mysql.com/apt/ubuntu jammy InRelease [20.2 kB]
Hit:2 https://download.docker.com/linux/ubuntu focal InRelease
Hit:3 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:5 http://pe.archive.ubuntu.com/ubuntu jammy InRelease
Hit:6 http://pe.archive.ubuntu.com/ubuntu jammy-updates InRelease
Err:1 http://repo.mysql.com/apt/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B7B3B788A8D3785C
Hit:7 http://pe.archive.ubuntu.com/ubuntu jammy-backports InRelease
Fetched 20.2 kB in 2s (11.7 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
16 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mysql.com/apt/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B7B3B788A8D3785C
W: Failed to fetch http://repo.mysql.com/apt/ubuntu/dists/jammy/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B7B3B788A8D3785C
W: Some index files failed to download. They have been ignored, or old ones used instead.
As you can see there are many errors
How to fix apt update after to upgrade the mysql.list file?
Through VirtualBox was installed long time ago Ubuntu Desktop 20.04 (focal) and was upgraded successfully to 22.04 jammy
Now, the reason of this post, when the sudo apt update command is executed appears:
sudo apt update
Hit:1 http://repo.mysql.com/apt/ubuntu focal InRelease
Hit:2 https://download.docker.com/linux/ubuntu focal InRelease
Hit:3 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:5 http://pe.archive.ubuntu.com/ubuntu jammy InRelease
Hit:6 http://pe.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:7 http://pe.archive.ubuntu.com/ubuntu jammy-backports InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
11 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: http://repo.mysql.com/apt/ubuntu/dists/focal/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Observe the two first lines, they contain the focal term, and the others lines contain the jammy term.
How to upgrade the repositories locations from focal to jammy?
The goal is update correctly MySQL and Docker.
For Ubuntu Desktop 22.04, with the ctrl + alt + t shortcut is opened the default terminal available.
Now Terminator was installed and with the same shorcut now Terminator is opened instead. I did do a research in Preferences for each one and does not exist a shortcut to define how to open each one. Only their respective internal shortcuts.
Through:
Terminator and works.But ctrl + alt + t remains for Terminator yet.
Through
Launch terminal option defined with ctrl + alt + t but is not possible edit to indicate use TerminalHow to Fix this?
For documentation purposes, about the apt-key command in many places I found these two variations:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys PUBKEY
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv PUBKEY
Observe the difference about the latest option --recv-keys and --recv. About the Ubuntu's official man at jammy apt-key(8) does mention only about:
adv (deprecated)
Pass advanced options to gpg. With adv **--recv-key** you can e.g. download key from
keyservers directly into the trusted set of keys. Note that there are no checks
performed, so it is easy to completely undermine the apt-secure(8) infrastructure if
used without care.
And now from above see other option --recv-key (different as --recv-keys - it ends with s)
And at jammy gpg(1) does mention only about:
--recv-keys keyIDs
Import the keys with the given keyIDs from a keyserver.
Observation in the mentioned man appears the --recv-key term as content for other options but it does not exist as an option definition itself. ( consider to use the ctrl + f keys to search using the --recv as search term, it because there is a line with the --recv-key term split in 2 lines.)
Question
--recv-key, --recv-keys and --recv options?If exists these 3 options, therefore each one has a specific purpose.
About the dpkg command, a few tutorials do mention of the --unpack option. According with
jammy (1) dpkg.1 it indicates
--unpack package-file...
Unpack the package, but don't configure it. If --recursive or -R option is specified,
package-file must refer to a directory instead.
Well just how testing, from the MySQL APT Repository page it is possible to get the mysql-apt-config_0.8.24-1_all.deb file. So in the Downloads directory I executed the command:
sudo dpkg --unpack mysql-apt-config_0.8.24-1_all.deb
It works with the following message
(Reading database ... 238377 files and directories currently installed.)
Preparing to unpack mysql-apt-config_0.8.24-1_all.deb ...
Unpacking mysql-apt-config (0.8.24-1) over (0.8.24-1) ...
Even when MySQL is installed.
Question
.deb file?A simple execution of the ls command only shows the current .deb file. I expected a kind of extraction. I am assuming a kind of default directory or other something else was used.
If with the -c option, it is possible to see the directories of the .deb file I am assuming that the --unpack option unpacks the .deb file - if my assumption is incorrect about the latter, please correct me.
Through VirtualBox for many Virtual Machines for Ubuntu Server - for each one an upgrade was done from 20.04 to 22.04. The apt update and apt upgrade commands work fine. But just few days ago I did realize that if I execute the following command to all the Virtual Machines:
VBoxClient --version
arises the following error message
VBoxClient: error while loading shared libraries: libXt.so.6: cannot open shared object file: No such file or directory
was reinstalled VirtualBox Guest Additions and the situation remains.
Question
Extra Question
UPDATE
In the post:
is indicated as solution execute the command
sudo apt install libxt6:i386
It shows
E: Unable to locate package libxt6:i386
Thus was executed
sudo apt install libxt6
And was installed.
But sadly even if the VM is restarted, the error remains
In many hosts through VirtualBox 6.1.38, for many Virtual Machines: Ubuntu Desktop/Servers was accomplished an upgrade from 20.04 to 22.04. The process was successful.
Now for all the Desktop environments (not sure if happens for servers) when Ubuntu is loading appears this message:
RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!
This message only has appeared for this 22.04 version - therefore never for previous releases such as 18.04 to 20.04
My concern is:
How to fix this situation?
Note I can work in peace through all these Virtual Machines.
If the following sequence of commands is executed:
sudo apt update
sudo du -sh /var/cache/apt
it shows 92M - of course for this current point of time. It could be other value.
If the following sequence of commands is executed:
sudo apt autoclean
sudo du -sh /var/cache/apt
it still shows 92M
Finally, if the following sequence of commands is executed:
sudo apt clean
sudo du -sh /var/cache/apt
it shows 28K - so is clear that sudo apt clean cleans the /var/cache/apt directory
Note for either sudo apt autoclean or sudo apt clean there is no output/result, but according with some tutorials the target directory used for cleaning purposes is /var/cache/apt, but ...
Question:
sudo apt autoclean is executed?
Through VirtualBox, even in different machines, I have 2 Ubuntu Server 20.04 instances running with the following info:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal
Both have MySQL installed with the same instructions that I used since months ago. Suddenly just for one of them when I do sudo apt update appears the following:
Get:2 http://repo.mysql.com/apt/ubuntu focal InRelease [12.9 kB]
Hit:3 http://pe.archive.ubuntu.com/ubuntu focal InRelease
Ign:4 https://packages.erlang-solutions.com/ubuntu focal InRelease
Hit:5 https://packages.erlang-solutions.com/ubuntu focal Release
Get:6 http://pe.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Err:2 http://repo.mysql.com/apt/ubuntu focal InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 467B942D3A79BD29
Get:9 http://pe.archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Get:10 http://pe.archive.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Hit:7 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu focal InRelease
Fetched 349 kB in 3s (133 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mysql.com/apt/ubuntu focal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 467B942D3A79BD29
W: Failed to fetch http://repo.mysql.com/apt/ubuntu/dists/focal/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 467B942D3A79BD29
W: Some index files failed to download. They have been ignored, or old ones used instead.
Questions
I have some Ubuntu Server 20.04 installations, but just for one of them happens the following:
sudo apt update
... password
Hit:1 http://repo.mysql.com/apt/ubuntu groovy InRelease
Ign:2 http://pe.archive.ubuntu.com/ubuntu groovy InRelease
Ign:3 http://pe.archive.ubuntu.com/ubuntu groovy-updates InRelease
Hit:4 http://apt.postgresql.org/pub/repos/apt groovy-pgdg InRelease
Ign:5 http://pe.archive.ubuntu.com/ubuntu groovy-backports InRelease
Ign:6 http://pe.archive.ubuntu.com/ubuntu groovy-security InRelease
Err:7 http://pe.archive.ubuntu.com/ubuntu groovy Release
404 Not Found [IP: 200.236.31.4 80]
Err:8 http://pe.archive.ubuntu.com/ubuntu groovy-updates Release
404 Not Found [IP: 200.236.31.4 80]
Err:9 http://pe.archive.ubuntu.com/ubuntu groovy-backports Release
404 Not Found [IP: 200.236.31.4 80]
Err:10 http://pe.archive.ubuntu.com/ubuntu groovy-security Release
404 Not Found [IP: 200.236.31.4 80]
Reading package lists... Done
E: The repository 'http://pe.archive.ubuntu.com/ubuntu groovy Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://pe.archive.ubuntu.com/ubuntu groovy-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://pe.archive.ubuntu.com/ubuntu groovy-backports Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://pe.archive.ubuntu.com/ubuntu groovy-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
What happened this? and how to solve?
I understand about the difference between Interactive login and Interactive non-login
According with this excellent post: Zsh/Bash startup files loading order (.bashrc, .zshrc etc.) we have the following table
+----------------+-----------+-----------+------+
| |Interactive|Interactive|Script|
| |login |non-login | |
+----------------+-----------+-----------+------+
|/etc/profile | A | | |
+----------------+-----------+-----------+------+
|/etc/bash.bashrc| | A | |
+----------------+-----------+-----------+------+
|~/.bashrc | | B | |
+----------------+-----------+-----------+------+
|~/.bash_profile | B1 | | |
+----------------+-----------+-----------+------+
|~/.bash_login | B2 | | |
+----------------+-----------+-----------+------+
|~/.profile | B3 | | |
+----------------+-----------+-----------+------+
|BASH_ENV | | | A |
+----------------+-----------+-----------+------+
| | | | |
+----------------+-----------+-----------+------+
| | | | |
+----------------+-----------+-----------+------+
|~/.bash_logout | C | | |
+----------------+-----------+-----------+------+
The first link refers to this other excellent post: Cleaning up bash customizations where has available an excellent explanation about Interactive login and Interactive non-login as follows:
An interactive login shell is a shell that you are typing into, that is the first such shell you execute on the machine. Typically you will have had to log in immediately before the shell starts. For example, when you SSH to a remote system and type commands to that system, you are typing into an interactive login shell.
An interactive non-login shell is a new shell started once you have already logged in; one which doesn’t require that you log in again. For example, if you open a new terminal window in your graphical user interface and get a shell prompt, that’s an interactive non-login shell. Another example of an interactive non-login shell would be a sub-shell started from inside a text editor; for example, typing :sh in vi.
About the former, it practically applies mandatorily in Ubuntu Server environment - where to work with each tty is need it do a login, so according with the table ~/.profile is used (I confirmed does not exist neither the ~/.bash_profile nor ~/.bash_login files). It applies for su - otheruser (it asks for his/her password) and therefore his/her own ~/.profile file is executed too. Until here I am fine.
About the latter - reason of this post - Ubuntu Desktop environment, it applies when a new window/terminal is opened with just one tab by default, so according with the table should be executed the /etc/bash.bashrc and ~/.bashrc files and not the .profile file
But why if is executed in that terminal:
echo $JAVA_HOME (defined on .profile)echo $M2_HOME (defined on .profile)echo $GRADLE_HOME (defined on .profile)which javawhich mvnwhich gradleall the commands work normally?
Same behavior for any new tab (Ctrl + Shift + T) within the same Window and even for a new Terminal Window with again its unique default tab
I read the following post:
And I don't have the settings mentioned about (the second is adapted for Ubuntu Desktop 18:04):
.bashrc files does not refer or sourcing the .profile fileEdit --> Preferences --> Unamed -> Command tab --> Run command as login shell (it is unchecked)
For sharing data files and directories among users within the same machine, the /srv directory was recommended here:
I am assuming this is still valid or recommendded — correct me if that changed.
But what should be the directory for shared development-related software like Java, Maven, Gradle? They will all be installed by unpacking .tar.gz archives. A central location for programs would be preferred over repeated installations by each user in their respective home directory.
As an example, in order to work with CI like Jenkins I would have installed many JDK versions: 11, 15 and 17, and similarly for Gradle and Maven. These are used to test a project with different environments. The mentioned software packets are installed simply by unpacking the .tar.gz files and updating the .profile file with the respective settings for them. And yes, I use these repositories as well to install servers, such as MySQL, RabbitMQ etc ...
For Ubuntu Desktop 18:04 for update I use:
But suddenly for the latter now arises:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem
So executing that command I got:
sudo dpkg --configure -a
dpkg: dependency problems prevent configuration of linux-generic-hwe-18.04:
linux-generic-hwe-18.04 depends on linux-headers-generic-hwe-18.04 (= 5.4.0.80.90~18.04.72); however:
Version of linux-headers-generic-hwe-18.04 on system is 5.4.0.77.86~18.04.69.
dpkg: error processing package linux-generic-hwe-18.04 (--configure):
dependency problems - leaving unconfigured
Setting up linux-modules-5.4.0-80-generic (5.4.0-80.90~18.04.1) ...
Setting up linux-image-5.4.0-80-generic (5.4.0-80.90~18.04.1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.4.0-77-generic
I: /initrd.img.old is now a symlink to boot/initrd.img-5.4.0-77-generic
I: /vmlinuz is now a symlink to boot/vmlinuz-5.4.0-80-generic
I: /initrd.img is now a symlink to boot/initrd.img-5.4.0-80-generic
Setting up linux-modules-extra-5.4.0-80-generic (5.4.0-80.90~18.04.1) ...
Setting up linux-image-generic-hwe-18.04 (5.4.0.80.90~18.04.72) ...
Processing triggers for linux-image-5.4.0-80-generic (5.4.0-80.90~18.04.1) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-80-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-80-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-80-generic
Found initrd image: /boot/initrd.img-5.4.0-80-generic
Found linux image: /boot/vmlinuz-5.4.0-77-generic
Found initrd image: /boot/initrd.img-5.4.0-77-generic
Found linux image: /boot/vmlinuz-5.4.0-73-generic
Found initrd image: /boot/initrd.img-5.4.0-73-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
Errors were encountered while processing:
linux-generic-hwe-18.04
So executing
The second now fails with:
sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
linux-generic-hwe-18.04 : Depends: linux-headers-generic-hwe-18.04 (= 5.4.0.80.90~18.04.72) but 5.4.0.77.86~18.04.69 is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
so
sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-headers-5.4.0-73-generic linux-hwe-5.4-headers-5.4.0-73 linux-image-5.4.0-73-generic linux-modules-5.4.0-73-generic
linux-modules-extra-5.4.0-73-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
linux-headers-5.4.0-80-generic linux-headers-generic-hwe-18.04 linux-hwe-5.4-headers-5.4.0-80
The following NEW packages will be installed:
linux-headers-5.4.0-80-generic
The following packages will be upgraded:
linux-headers-generic-hwe-18.04 linux-hwe-5.4-headers-5.4.0-80
2 upgraded, 1 newly installed, 0 to remove and 11 not upgraded.
2 not fully installed or removed.
Need to get 0 B/12.3 MB of archives.
After this operation, 85.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 210068 files and directories currently installed.)
Preparing to unpack .../linux-hwe-5.4-headers-5.4.0-80_5.4.0-80.90~18.04.1_all.deb ...
Unpacking linux-hwe-5.4-headers-5.4.0-80 (5.4.0-80.90~18.04.1) over (5.4.0-80.90~18.04.1) ...
So
All work fine
Question
I work with Ubuntu Desktop 18.04
Furthermore I have Windows 10 and MacOS working with multi desktops. I know how create a new one and how move through them
An important observation is that for each laptop is that each one has a secondary monitor. I am able to open any application (editor, window explorer or finder, terminal console, an IDE - etc) and move it to the secondary monitor. Therefore some applications are in the primary monitor and others in the secondary monitor.
The point here is, for each Desktop, I am able to have in the primary and secondary monitors any application. If I pass through these Desktops each Desktop respects and keeps isolated the same set of applications opened and distributed through the primary and secondary monitors from the beginning. Again it for each Desktop.
After to did do a research to accomplish the same goal in Ubuntu, I did realize that multi desktop is referred how workspace. Well, I am able to move through them with Ctrl + Alt [up|down].
Problem: all the content (app) opened in the secondary monitor is shared through all the workspace, therefore the apps are not isolated through each workspace.
In Settings -> Devices -> Displays there is no a special settings to have the same behavior like the two other OS
How to fix this?
I am reading some tutorials about Linux configurations:
root. Well I did realize that in many places are used sudo su and sudo -i, even when both accomplish the the same goal, I have the doubt about:
I am doing this question because for some reason exists these two approaches
I have:
About VirtualBox having
Sharedclipboard and Drag n Drop configured with bidirectionalExtension Pack 6.1.4 r136177 installedAnd the Guest Ubuntu having:
Guest Additions installedThe Shared Clipboard feature does not work how is expected.
Ctrl + C + Ctrl + V between Host/Guest and vice versa, right?Confirm that they are the correct combination.
Because I tried with
Shift + Ctrl[left|right] + c - Shift + Ctrl[left|right] + v Ctrl[left|right] + Shift + c - Ctrl[left|right] + Shift + v and does not work
What is missing?
I read these links:
Both do mention to install virtualbox-guest-x11
Assumption: of course, assuming it should enable in peace the shared clipboard feature.
Through the sudo apt search virtualbox command I got a list and I can see these two coincidences
virtualbox-guest-x11/bionic-updates 5.2.34-dfsg-0~ubuntu18.04.1 amd64
x86 virtualization solution - X11 guest utilities
virtualbox-guest-x11-hwe/bionic-updates 5.2.34-dfsg-0~ubuntu18.04.1 amd64
x86 virtualization solution - X11 guest utilities
Working with the former, I tried but arises:
sudo apt install virtualbox-guest-x11
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
virtualbox-guest-x11 : Depends: xorg-video-abi-23
Depends: xserver-xorg-core (>= 2:1.18.99.901)
E: Unable to correct problems, you have held broken packages.
I am not a Linux/Ubuntu expert, my concern is avoid to create conflicts with VirtualBox - Guest Additions and virtualbox-guest-x11 mostly because their versions are not the same.
So I should go and install anyway that dependencies?
I am working with Ubuntu 18.04 and MySQL Server - 8.0.18
Suddenly today MySQL can't start anymore
With the sudo service mysql status command appears:
sudo service mysql status
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2019-11-02 17:05:23 -05; 1min 44s ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 1659 ExecStart=/usr/sbin/mysqld (code=exited, status=2)
Process: 1620 ExecStartPre=/usr/share/mysql-8.0/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
Main PID: 1659 (code=exited, status=2)
Status: "Server startup in progress"
Nov 02 17:05:22 asus2016-vb01 systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 02 17:05:22 asus2016-vb01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 02 17:05:22 asus2016-vb01 systemd[1]: Failed to start MySQL Community Server.
Nov 02 17:05:23 asus2016-vb01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Nov 02 17:05:23 asus2016-vb01 systemd[1]: mysql.service: Scheduled restart job, restart counter is at 9.
Nov 02 17:05:23 asus2016-vb01 systemd[1]: Stopped MySQL Community Server.
Nov 02 17:05:23 asus2016-vb01 systemd[1]: mysql.service: Start request repeated too quickly.
Nov 02 17:05:23 asus2016-vb01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 02 17:05:23 asus2016-vb01 systemd[1]: Failed to start MySQL Community Server.
With the sudo service mysql restart command appears:
sudo service mysql restart
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.
Following and executing the two suggested commands:
systemctl status mysql.servicejournalctl -xeTherefore: sudo systemctl status mysql.service
sudo systemctl status mysql.service
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2019-11-02 17:08:21 -05; 38s ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 2633 ExecStart=/usr/sbin/mysqld (code=exited, status=2)
Process: 2594 ExecStartPre=/usr/share/mysql-8.0/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
Main PID: 2633 (code=exited, status=2)
Status: "Server startup in progress"
Nov 02 17:08:20 asus2016-vb01 systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 02 17:08:20 asus2016-vb01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 02 17:08:20 asus2016-vb01 systemd[1]: Failed to start MySQL Community Server.
Nov 02 17:08:21 asus2016-vb01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Nov 02 17:08:21 asus2016-vb01 systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
Nov 02 17:08:21 asus2016-vb01 systemd[1]: Stopped MySQL Community Server.
Nov 02 17:08:21 asus2016-vb01 systemd[1]: mysql.service: Start request repeated too quickly.
Nov 02 17:08:21 asus2016-vb01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 02 17:08:21 asus2016-vb01 systemd[1]: Failed to start MySQL Community Server.
And with journalctl -xe
-- Unit mysql.service has begun starting up.
Nov 02 17:08:20 asus2016-vb01 audit[2632]: AVC apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/sbin/mysqld" pid=2632 comm="apparmor_p
Nov 02 17:08:20 asus2016-vb01 audit[2633]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/etc/ssl/openssl.cnf" pid=2633 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=122
Nov 02 17:08:20 asus2016-vb01 audit[2633]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/2633/task/2634/mem" pid=2633 comm="mysqld" requested_mask="r" denied_mask="r" fsuid
Nov 02 17:08:20 asus2016-vb01 systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 02 17:08:20 asus2016-vb01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 02 17:08:20 asus2016-vb01 systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit mysql.service has failed.
--
-- The result is RESULT.
Nov 02 17:08:21 asus2016-vb01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Nov 02 17:08:21 asus2016-vb01 systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
I followed the solution about this post:
I used the innodb_force_recovery = 10 (ten), it playing, because with 1 and 2 did not work
Therefore with the sudo systemctl start mysql command is possible start the server.
I can see all the data and users saved in peace.
Now through the sudo systemctl status mysql command I get
sudo systemctl status mysql
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2019-11-02 17:26:48 -05; 11s ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 2769 ExecStartPre=/usr/share/mysql-8.0/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
Main PID: 2808 (mysqld)
Status: "Server is operational"
Tasks: 19 (limit: 4617)
CGroup: /system.slice/mysql.service
└─2808 /usr/sbin/mysqld
Nov 02 17:26:47 asus2016-vb01 systemd[1]: Starting MySQL Community Server...
Nov 02 17:26:48 asus2016-vb01 systemd[1]: Started MySQL Community Server.
Until this point would has no sense this post, but if I do either Alpha or Beta steps:
Alpha (steps):
sudo systemctl stop mysql
remove innodb_force_recovery = 10
sudo systemctl start mysql
Beta (steps):
restart the PC,
(I can confirm `MySQL` was started),
remove innodb_force_recovery = 10
restart the PC
the same problem happens again.
Therefore now is mandatory keep the innodb_force_recovery = 10, otherwise it returns to the same problem
Warning:
According with:
The correct range is from 1 to 6, I am assuming 10 is "interpreted" how the maximum value (6)
Is there a way to configure something and remove innodb_force_recovery? It to return to the normal or old configuration where all worked fine (without innodb_force_recovery)
Note the final content of /var/log/mysql/error.log is
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2019-11-02T23:24:37.346875Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.18) starting as process 1668
2019-11-02T23:24:37.804662Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
2019-11-02T23:24:37.804783Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3563:err == DB_SUCCESS thread 139850038036224
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
23:24:37 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x555c74a041c0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f315fd6bce0 thread_stack 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x555c72ab2edd]
/usr/sbin/mysqld(handle_fatal_signal+0x303) [0x555c71b5bc63]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7f317319a890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7) [0x7f31712d3e97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141) [0x7f31712d5801]
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x2ec) [0x555c72d6015c]
/usr/sbin/mysqld(+0x2074038) [0x555c72c1d038]
/usr/sbin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0x660) [0x555c72c26e40]
/usr/sbin/mysqld(srv_start(bool, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)+0x1741) [0x555c72d0e701]
/usr/sbin/mysqld(+0x1fe3f25) [0x555c72b8cf25]
/usr/sbin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0x9f) [0x555c72868f5f]
/usr/sbin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x5b4) [0x555c72a7d8f4]
/usr/sbin/mysqld(+0x1076dc5) [0x555c71c1fdc5]
/usr/sbin/mysqld(+0x24182b9) [0x555c72fc12b9]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7f317318f6db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f31713b688f]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
I am working with VirtualBox - Ubuntu is a guest. It had been working for more of 3 months, now suddenly this situation appeared.
More Info:
One
As requested desertangels
sudo /usr/sbin/mysqld
2019-11-03T00:07:06.466871Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.18) starting as process 2307
2019-11-03T00:07:06.470277Z 0 [ERROR] [MY-010123] [Server] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
2019-11-03T00:07:06.472544Z 0 [ERROR] [MY-010119] [Server] Aborting
2019-11-03T00:07:06.475967Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.18) MySQL Community Server - GPL.
Two
Executing cat /etc/mysql/mysql.conf.d/mysqld.cnf
[mysqld]
port = 3307
bind-address = 0.0.0.0
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
datadir = /var/lib/mysql
log-error = /var/log/mysql/error.log
Three
BTW: just in case, with mysql -u root -p appears:
mysql -u root -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Of course, the server is not running