I got
VMX (outside TXT) disabled by bios Ubuntu20.10 :clean,... files,...blocks
when I boot into Ubuntu 20.04.
It's little annoying
What this message means and how can I remove it?
There seem be be several options to install CUDA on Ubuntu 20.10: It is pre-bundled with 20.10, there are various installers at the official NVIDIA page, etc.
Question: What is a recommended way to install CUDA 11.X on Ubuntu 20.10, and how do I verify the installation?
Don't know why, but they decided to add sssd (System Security Services Daemon) to the standard Ubuntu 20.10 upgrade and fresh install. It fails to start, and generates lots of error messages. It's not configured at install time, as it's missing the required /etc/sssd/sssd.conf file.
SSSD is a system daemon. Its primary function is to provide access to local or remote identity and authentication resources through a common framework that can provide caching and offline support to the system. It provides several interfaces, including NSS and PAM modules or a D-Bus interface.
You can see the failure with:
systemctl status sssd
When starting Thunderbird in Ubuntu 20.10 an error message is displayed
XML Parsing Error: undefined entity
Location: chrome://messenger/content/messenger.xhtml
Line Number 905, Column 3:
<key id="openLightningKey"
--^
and nothing more happens. However Thunderbird can be started in "safe mode" with the command line command
thunderbird -safe-mode
I have a number of language packs installed, German, English (CA), English (GB), French and Swedish.
How can I make Thunderbird start OK from the apllications menu?
I have been using Viber for Desktop (the official .deb
package downloaded from https://download.cdn.viber.com/cdn/desktop/Linux/viber.deb ) for at least 4 normal Ubuntu versions (18.10 through 20.04) with no problem. A few days ago I upgraded from Ubuntu 20.04 to 20.10 and now the /opt/viber/Viber
executable crashes on startup with the following message on terminal:
Segmentation fault (core dumped)
System log has the following:
Oct 27 19:04:42 xxx kernel: [ 3782.065767] Viber[25573]: segfault at 0 ip 00007ff5e4804bc5 sp 00007fff2e7dc3b0 error 4 in iHD_drv_video.so[7ff5e46eb000+348000]
Oct 27 19:04:42 xxx kernel: [ 3782.065771] Code: 01 48 83 f8 42 75 e6 31 db 66 41 89 9f 58 0c 00 00 49 8b 5f 28 8b 83 f0 1d 00 00 85 c0 0f 84 ba 01 00 00 48 8b b3 e8 1d 00 00 <81> 3e 00 00 01 00 48 89 75 c8 0f 85 a3 01 00 00 44 8d 70 f0 4d 63
A crash dump on system's /var/crash
directory is also generated.
I have reinstalled the latest version from Viber's website.
I have deleted the ~/.ViberPC
and ~/.cache/Viber Media S.à r.l
directories from the home directory, but the problem stays the same.
Any other user having the same problem?
I contacted viber.com. First, they answered by proposing a complete removal and re-install. However, this was something that I have already done. After informing them so, they requested the crash dump, which I sent to them.
Currently Viber for Ubuntu is in version 13.3.1 and has not been updated since July 2020. So, we are stuck to this version until an update is released.
For the time being, the temporary workaround is to retry starting Viber
after crash, until it does not crash. It seems that the crash is pretty random, with a chance of 10% of the times Viber
starting without a crash. So, I wrote the following Bash function and added it to the end of my ~/.bash_aliases
file:
function vib
{
while ! /usr/bin/pgrep -i Viber ; do
nohup /opt/viber/Viber >/tmp/vib.out 2>/tmp/vib.err &
sleep 3
done
}
To start Viber, I simply type vib
into a terminal and wait until it starts.
This problem seems to have been solved in Viber version 16.1.0.37: