Arnold's questions

I love the old Motif desktops and stumbled upon an Iris desktop from MaxxInteractive. I installed it on my Ubuntu 21.04 system according to their instructions. The install and update scripts gave the impression that everything installed correctly.

The instructions also requested you to restart the computer. After that one would be able to choose the new desktop from the session menu. I don 't know what a session menu is. After looking around it seems to be a menu option on the login screen showing the desktops you have. I cannot find that option (upper right I got options for disabled, network, volume control and logging options).

In this blog I found how to run the desktop from the command line:

sudo service dbus restart
sudo service x11-common restart
. /opt/MaXX/etc/system.runtime
. /opt/MaXX/etc/skel/Xsession.dt

The services cannot be restarted, they are protected, even from root. I thought that it might not matter as I had restarted the computer already. When I entered the next two commands I did get a MaxxInteractive desktop. But nothing works, no reaction on mouse clicks.

Anybody any idea how to run my shiny new desktop?

I recently upgraded to Ubuntu (Gnome) 20.10 and ever since I have lots of messages like

SSSD failed to start system security daemon
dependency failed for PAM security socker
... and some more dependency related info...

during boot. As a beginner to Ubuntu I am not well able to judge how serious this problem is. But I don't want red flagged lines during my boot and that makes that I want to eliminate this problem. In journalctl -b I found some messages pertaining to to SSSD (see below). Especially the first message (in red) is worrysome: it appears that SSSD is not running.

• why is this caused by upgrading to 20.10?
• what can I do? I don't have an sssd.conf file in /etc/sssd but I am not sure why it has been removed or why it isn't present

As the journalctl file is about 8000 lines I only post the lines that signal the start of the sssd problems. If more info is needed please tell me.

Nov 05 20:44:30 loosken sssd[1031]: SSSD couldn't load the configuration database [2]: No such file or directory.
Nov 05 20:44:30 loosken systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION
Nov 05 20:44:30 loosken systemd[1]: sssd.service: Failed with result 'exit-code'.
Nov 05 20:44:30 loosken systemd[1]: Failed to start System Security Services Daemon.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD PAM Service responder private socket.
Nov 05 20:44:30 loosken snapd[1030]: AppArmor status: apparmor is enabled and all features are available
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD PAM Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: sssd-pam-priv.socket: Job sssd-pam-priv.socket/start failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD NSS Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD SSH Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-ssh.socket: Job sssd-ssh.socket/start failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD Sudo Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-sudo.socket: Job sssd-sudo.socket/start failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD AutoFS Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-autofs.socket: Job sssd-autofs.socket/start failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD PAC Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-pac.socket: Job sssd-pac.socket/start failed with result 'dependency'.
Nov 05 20:44:30 loosken dbus-daemon[995]: [system] AppArmor D-Bus mediation is enabled

I try to install Ubuntu 18.04 alongside windows 10 (Windows home N, version 10.0.18362 Build 18362). The system is UEFI based and the partition I want to install it on is 150GB, GPT based. I did format an USB drive with Rufus, UEFI, GPT-based and ubuntu 18.04. Whatever I do, I always get the Grub prompt while the information uptill now suggests I boot into the life environment. I tried to install from DVD, no luck either.

Quick restart is disabled. Is there a way to boot from USB into Ubuntu? If not, what should I do when in the Grub prompt?

I am doing deep learning computations and after a lot of computations the input freezes. This means that there is no reaction on mouse and keyboard while the system merrily computes along. However, when I do alt-prtscr-REISUB the system reboots. Does anyone what is going wrong and how I can prevent this?

The CPU is an AMD 1950X and during the computations all 32 threads are utilized for about 45%. The temperature rises to 76 Celsius. 2 Nvidia 1080Ti's are used for the computations. Both utilized for 75% on average.

Using ubuntu 18.04 with Mate, anaconda spyder, tensorflow 1.9/keras 2.2.2 or tensorflow 1.12/keras 2.2.4 (both combinations result in the same behavior) and Nvidia drivers version 415.

I am trying to install version 396 of the Nvidia drivers on Ubuntu 18.04 using this link. I got a message about unmet dependencies (see below). Actually when using ubuntu-drivers devices the recommended version is 415. I tried that but got same results. The excellent post mentioned in the link does not mention this problem. Does somebody know the cause of this problem (why doesn't apt install these dependencies) and how I can solve this?

I have a dual 1080Ti setup with driver version 390. For Cuda 9.2 I need at least version 396.

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:
 nvidia-driver-396 : Depends: libnvidia-gl-396 (= 396.54-0ubuntu0~gpu18.04.1) but it is not going to be installed
                     Depends: nvidia-dkms-396 (= 396.54-0ubuntu0~gpu18.04.1) but it is not going to be installed
                     Depends: libnvidia-compute-396 (= 396.54-0ubuntu0~gpu18.04.1) but it is not going to be installed
                     Depends: nvidia-compute-utils-396 (= 396.54-0ubuntu0~gpu18.04.1) but it is not going to be installed
                     Depends: libnvidia-decode-396 (= 396.54-0ubuntu0~gpu18.04.1) but it is not going to be installed
                     Depends: libnvidia-encode-396 (= 396.54-0ubuntu0~gpu18.04.1) but it is not going to be installed
                     Depends: nvidia-utils-396 (= 396.54-0ubuntu0~gpu18.04.1) but it is not going to be installed
                     Depends: libnvidia-ifr1-396 (= 396.54-0ubuntu0~gpu18.04.1) but it is not going to be installed
                     Recommends: libnvidia-compute-396:i386 (= 396.54-0ubuntu0~gpu18.04.1)
                     Recommends: libnvidia-decode-396:i386 (= 396.54-0ubuntu0~gpu18.04.1)
                     Recommends: libnvidia-encode-396:i386 (= 396.54-0ubuntu0~gpu18.04.1)
                     Recommends: libnvidia-ifr1-396:i386 (= 396.54-0ubuntu0~gpu18.04.1)
                     Recommends: libnvidia-gl-396:i386 (= 396.54-0ubuntu0~gpu18.04.1)
E: Unable to correct problems, you have held broken packages.

I develop a windows application and am curious whether it works via Wine. The application runs fine with Wine but I get no sound. In fact, I'm not sure whether my ubuntu installation has MIDI capabilities. The sound output settings shows "LFE on Separate Mono Output" one with "no amplifier" and another with "amplifier". They both function. I am using Ubuntu 12.04 as a client on virtualbox that runs on windows 7.

Thanks for any suggestion!

EDIT: virtual box hosted by windows 7, ubuntu running as a client in virtualbox.