Freezing issues after upgrade to 19.04

I recently upgraded from Ubuntu 16.04 to 18.04 -> 18.10 and 19.04 since I had problems with Ubuntu crashing/hard freezing, especially with lock screen or after sleeping.

The lock screen hard crashes are gone, but I have plenty of other issues instead.

In particular, every time I drag to open the “lock” screen it gets stuck and seems frozen, half way for 30-60 seconds before finally getting into Ubuntu (see image)

enter image description here

Also, whenever I create a new text file and save it for the first time, the GUI freezes completely for 30-60 seconds as well, before going back to normal. The same thing happens when saving a screen shot from the screenshot app, so it seems there is some problem with disk access? However, when saving to an existing file, there is no delay.

Any ideas what could cause these issues or how I can try to debug it?

Basic system info from the “About” tab:

Ubuntu 19.04 Memory: 15.4 GiB Intel Core i7 8550U CPU @ 1.80 GHz x 8 Graphics Intel UHD Graphics 620 (Kabylake GT2) Gnome 3.32.1 Os type 64-bit Disk 512,1 GB 

DEBIAN 10 UPDATING ISSUES

I have just done a clean installation of debian buster, and I’m having trouble with apt update (I’m posting this question to this community since ubuntu it’s just a distribution of debian, so i guessed somebody could help).

UPDATES PROBLEM

I run sudo apt update and I get this

    Ign:1 cdrom://[Debian GNU/Linux 10.1.0 _Buster_ - Official amd64 NETINST 20190908-01:07] buster InRelease Err:2 cdrom://[Debian GNU/Linux 10.1.0 _Buster_ - Official amd64 NETINST 20190908-01:07] buster Release   Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs Hit:3 http://deb.debian.org/debian buster InRelease               Ign:4 http://deb.debian.org/debian buster/updates InRelease       Hit:5 http://deb.debian.org/debian buster-updates InRelease Err:6 http://deb.debian.org/debian buster/updates Release   404  Not Found [IP: 151.101.132.204 80] Reading package lists... Done E: The repository 'cdrom://[Debian GNU/Linux 10.1.0 _Buster_ - Official amd64 NETINST 20190908-01:07] buster Release' does not have 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://deb.debian.org/debian buster/updates Release' does not have 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. W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list:4 W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list:4 W: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list:4 W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list:4 W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list:4 W: Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list:4 W: Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list:4 W: Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list:4 

Here you have the content of my sources.list

    #   deb cdrom:[Debian GNU/Linux 10.1.0 _Buster_ - Official amd64 NETINST 20190908-01:07]/ buster main deb cdrom:[Debian GNU/Linux 10.1.0 _Buster_ - Official amd64 NETINST 20190908-01:07]/ buster main  deb http://deb.debian.org/debian/ buster main deb-src http://deb.debian.org/debian/ buster main  deb http://deb.debian.org/debian/ buster/updates main deb-src http://deb.debian.org/debian/ buster/updates main  # buster-updates, previously known as 'volatile' deb http://deb.debian.org/debian/ buster-updates main deb-src http://deb.debian.org/debian/ buster-updates main  # This system was installed using small removable media # (e.g. netinst, live or single CD). The matching "deb cdrom" # entries were disabled at the end of the installation process. # For information about how to configure apt package sources, # see the sources.list(5) manual. 

I really can’t understand what’s the problem here, if these are the default sources that came with my clean installation inside the file, I changed nothing.

Web parts are having theme issues?

The company I work for has a SharePoint Online communication page. We have different departments sites such as HR, Marketing, IT, Business Development, etc.

We have this blue theme background set for all our sites:

enter image description here

Let’s say our HR site, we have a few web parts (Library) and when we click on it our current theme is applied.

enter image description here

However, we have this issue in some of our other sites like IT and Business Development that when you click on some web part we have a blue background:

enter image description here This is Our Business Development page when I click on the Business Development News web part I got the blue background issue below:

enter image description here

enter image description here

Any ideas, why the current theme is not being applied properly to some web parts. We had checked the composed look settings of each site and everything is configured the same way as the HR page. We have some custom CSS that we created for each site. We checked the HR site master pages, the custom CSS link is being called in, the same way in our IT and Business Development sites.

Any suggestions would be greatly appreciated. Thank you!

Cuda memory issues using large Pytorch model and Tensorflow model together

The Pytorch network is Tencent DSFD:https://github.com/TencentYoutuResearch/FaceDetection-DSFD

and the Tensorflow network is WideResNet: https://github.com/yu4u/age-gender-estimation

I’m using the former for face detection (very robust to all poses) and the latter for gender detection. They both get instantiated in the same driver script. I am on Ubuntu 18.04 with Pytorch GPU and Tensorflow GPU installed as Conda packages in a conda env. I read on a blog by Puget Systems that this is all I need to do with regards to Cuda and Cudnn installation and in fact it does seem that the GPU is used and thus results in Cuda Runtime memory errors.

My proposed solution is to detect faces first, save the bounding boxes and crops of faces as .npz files and then run the gender detection separately.

It was working fine with a much smaller gender detection model (Hassner and Levi’s) but the accuracy was too low.

Would installing Cuda and Cudnn on the Ubuntu 18.04 server itself make a difference? Ie. Do I have a better chance of running this script with both models? The GPU is a GTX 1080 with 8 GB memory.

sudo apt-get update issues in Ubuntu 18.04

sudo apt-get update isn’t working for me in Ubuntu 18.04 LTS

Err:1 http://in.archive.ubuntu.com/ubuntu bionic InRelease   Could not resolve 'proxyhost' Err:2 http://in.archive.ubuntu.com/ubuntu bionic-updates InRelease   Could not resolve 'proxyhost' Err:3 http://in.archive.ubuntu.com/ubuntu bionic-backports InRelease   Could not resolve 'proxyhost' Err:4 http://in.archive.ubuntu.com/ubuntu bionic-security InRelease   Could not resolve 'proxyhost' Reading package lists... Done W: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/bionic/InRelease  Could not resolve 'proxyhost' W: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease  Could not resolve 'proxyhost' W: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease  Could not resolve 'proxyhost' W: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/bionic-security/InRelease  Could not resolve 'proxyhost' W: Some index files failed to download. They have been ignored, or old ones used instead.