I have been using 20.04 on a RPi4/4GB since its release and am very pleased with the performance.
Today, I upgraded to 20.10 and all works well, except for a couple of issues:
After every boot, a "System program problem detected" window opens. It has no "details" tab, so there is no hint of what is the problem. I have checked the /var/log/syslog file, but there doesn't appear to be anything obvious. How can I found out what is the problem?
Chromium takes about 90 seconds to open to my home page (for 20.04 was 2-3 seconds). I have tried removing and reinstalling, but that does not resolve the issue. Once my home page opens, chromium responds normally.
The following entries from /var/log/syslog relate to the problem. As you can see from the timestamps, the whole process takes 1 minute 28 seconds and includes many "DENIED" messages.
You are no doubt correct. But I use this system as my main work computer, and a fresh install carries a significant setup overhead. It's true that the majority of the setup information can be used directly from /home/XXX/.config, but I would still have to install programs and carry out various setups which are in the root.
I too experienced several problems after upgrade and was forced to do a clean install. The clean install works great without any of the problems with an upgrade.
I also have this problem but I did not investigate because I was running 20.10 from alpha stage and have done lot of fiddling. Planning to do clean install to see if it is issue with my setup or with 20.10 release.
I guess that is (new) normal Chromium is a snap package now instead of .deb and as of today snaps do take a while to launch compared to traditional packages (although in my case it is about 20s not 90s).
I guess that is (new) normal Chromium is a snap package now instead of .deb and as of today snaps do take a while to launch compared to traditional packages (although in my case it is about 20s not 90s).
No, that's not the problem. It was also a snap package for 20.04, but then chromium startup took 2-3 seconds.
By the way, this long delay only happens the first time after startup. If I close chromium and then reopen, it reopens immediately.
You are right. I checked chromium, it is slow only first time but starts in couple of seconds thereafter. I also do not have same apparmor DENIED msgs.
I'm getting this same 'crash' problem with Ayatana too. Is there a fix to sort this out at all?
Plus the clock is missing (although I can add a clock back using the Clock panel item)...
(Bluetooth icon was missing but managed to add this back reticking the AppIndicator item in Bluetooth plugin setup)
I've tried a clean install, without setting up my whole system, and that seems to work OK.
Anyway, as I use this as my main computer, I've decided to stay with 20.04 LTS, and not waste time getting the system to work rather than just using it.
If you look at the other recent crash thread JonG, I think I figured this problem out... it was from having the indicator-datetime package still installed as well as the new ayatana-indicator-datetime. I guess it is a bug that the old one is not removed during the upgrade process.
From the Ayatana Indicators github:
"When using the -datetime Ayatana Indicator, make sure that the -datetime Ubuntu Indicator (package name: indicator-datetime) is not installed."
Same problem for me on a clean install of 20.10 (sha=06e26aa197eb8e7fc....). In fact, several crashes and the report dialog either does not come up or does not respond. Here is my 1st 3 hour history in /var/crash:
-rw------- 1 root whoopsie 38809 Nov 2 14:58 samba-common.0.crash
-rw-r----- 1 ubuntu whoopsie 2482161 Nov 2 15:01 _usr_lib_aarch64-linux-gnu_brisk-menu_brisk-menu.1000.crash
-rw-r----- 1 ubuntu whoopsie 71061 Nov 2 17:40 _usr_bin_update-manager.1000.crash
-rw-r----- 1 ubuntu whoopsie 89755 Nov 2 17:42 _usr_bin_software-properties-gtk.1000.crash
Possibly related to that, all software installs and update stopped working with:
dpkg: unrecoverable fatal error, aborting:
files list file for package 'avahi-autoipd' is missing final newline
So things are apparently in a dead state. Not able to apt install anything or apt upgrade.
For "non-savant user" adoption of your work, please Linux/ubuntu/mate developers consider working on fundamental ways to mask/tolerate errors that are not relevant, keep real ones from corrupting the system, and/or ways to revert major functions to working state if corruption does occur.
Chromium is a snap package now instead of .deb and as of today snaps do take a while to launch compared to traditional packages (although in my case it is about 20s not 90s).