apt dist-upgrade "crashes" two times

[Fritz Hudnut]

Running a standard "apt dist-upgrade" in U-MATE 20.10 via GUI console & part way through suddenly the screen flashes black and a brief TTY-like dmesg data shows "[Failed] and a bunch of data before going black again . . . . Seems like the GUI was crashed . . . . After a minute the mouse cursor came back and then the log-in window.

I logged in and saw the "error" applet up on the toolbar . . . saying "possibly unmet dependencies" . . . launched the console again and it said, "dpkg was interrupted, run 'sudo dpkg --configure -a'" . . . so I ran that, and a few errors on "libreoffice" showed up . . . it was running through the items again . . . and then the same crash of the GUI happened again . . . ???

Haven't seen anything quite like this in some 13 years of messing with linux . . . GUI crashes while running an apt update?????

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubuntu-release-upgrader-core 1:20.10.9
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu44
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: MATE
Date: Fri Aug 21 08:24:21 2020
InstallationDate: Installed on 2020-01-20 (214 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.update-manager.release-upgrades: 2020-03-18T12:04:25.397274

[Fritz Hudnut (este-el-paz)]

opened synaptic and it says:

"E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
E: _cache->open() failed, please report."

[Fritz Hudnut (este-el-paz)]

This time "dpkg --configure" made it through w/o crashing . . . but reported:

"Errors were encountered while processing:
 libreoffice-math
 libreoffice-gtk3
 libreoffice-writer
 libreoffice-draw
 libreoffice-gnome
 bcmwl-kernel-source
 libreoffice-base-core
 python3-uno
 libreoffice-calc"

[Fritz Hudnut (este-el-paz)]

Ran "configure" and then "fix broken install" . . . the ran thru apt dist-upgrade and it appeared "OK" . . . then I ran autoremove and autoclean and again ran apt dist-upgrade . . . it showed "52 packages" to upgrade . . . half way through again the GUI crashed into blackness.

This time took a full minute before mouse came back . . . and back into GUI . . . .

[Fritz Hudnut (este-el-paz)]

Problems continuing with my U-MATE install of 20.10 . . . very long boot times, and in the TTY there is a large "FAILED to start processes" . . . . This morning it took maybe 3 minutes to get to a log in window, but the "log in" window was upper left corner . . . it was like in the TTY where it was asking for user name, rather than already "knowing" and just wanting the password. I entered the password . . . then realizing that it wasn't going to accept my password as the user name . . . I hit the power button . . . the TTY with the large "FAILED" line after line showed up . . . before shutting down . . . .

A thread on the U-MATE forum has been started w/o much in the way of insight . . . .

https://ubuntu-mate.community/t/apt-dist-upgrade-crashes-gui-two-times/22561/9

[Fritz Hudnut (este-el-paz)]

[edit: After I posted this earlier data, I ran apt and it brought back 126 packages to upgrade and some to autoremove . . . . Also I tried to get into a TTY and it was filled with the "Failed" lines, I tried each of them--all showing the same data. I ran the upgrades and then autoremove showed at the end:

    BlockquoteProcessing triggers for desktop-file-utils (0.24-1ubuntu4) ...
    Processing triggers for mime-support (3.64ubuntu1) ...
    Processing triggers for hicolor-icon-theme (0.17-2) ...
    Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
    Processing triggers for libglib2.0-0:amd64 (2.64.4-1) ...
    /usr/share/glib-2.0/schemas/org.ayatana.indicator.datetime.gschema.xml:4:1 Erro
    r on line 4 char 1: already specified. This entire file h
    as been ignored.
    Processing triggers for libc-bin (2.31-2ubuntu1) ...
    Processing triggers for man-db (2.9.3-2) ...
    Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu2) ...
    Rebuilding /usr/share/applications/bamf-2.index...

About to restart to see if anything changes . . . .

[Fritz Hudnut (este-el-paz)]

Just to update . . . running the update/upgrade after I posted before did seem to clear the TTY up, the "Failed" endlessly streaming seems to be gone . . . and I could log in to the TTY.

Boot up seems a little faster, but when the log in window loads the "error" "clang" sound sounds . . . but there is no error "splotch" signaling a crash report . . . . and it still seems to be asking for the user name & password even though there is only one user.

[Launchpad Janitor (janitor)]

[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]