Ich bin etwas verwirrt. Ich habe vor etwa zwei Wochen ohne Probleme ein Upgrade von 18.10 auf 19.04 durchgeführt. Heute erhielt ich eine Meldung, dass ein Upgrade auf 19.04 verfügbar sei und ob ich es installieren wolle. Ich stimmte zu und der Upgrade-Prozess begann. Ich erhielt dann zwei Fehlermeldungen: dass „install-info“ nicht installiert werden konnte, und dann, dass die Upgrades nicht installiert werden konnten und dass das System in einem möglicherweise unbrauchbaren Zustand war (siehe Screenshots).
Ich verwende das System jetzt und es scheint einwandfrei zu funktionieren. Wie kann ich sicherstellen, dass alles in Ordnung ist?
bearbeiten: dies ist die Ausgabe vonapt list systemd
`$ apt list systemd
Listing... Done
systemd/disco,now 240-6ubuntu5 amd64 [installed]
systemd/disco 240-6ubuntu5 i386`
I'm using a laptop with **Intel i5** chipset.
edit2: I learned that the chipset has nothing to do with the problem. Following the output for `sudo apt update` and `sudo apt upgrade` - I had to change all instances of http or https to *http because my user level is not high enough to paste that many links
`$ sudo apt update
Hit:1 *ttp://archive.ubuntu.com/ubuntu disco InRelease
Hit:2 *ttps://repo.skype.com/deb stable InRelease
Hit:3 *ttp://archive.ubuntu.com/ubuntu disco-updates InRelease
Hit:4 *ttp://security.ubuntu.com/ubuntu disco-security InRelease
Hit:5 *ttps://download.jitsi.org stable/ InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
10 packages can be upgraded. Run 'apt list --upgradable' to see them.
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
curl gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 libcurl3-gnutls
libcurl4 libjavascriptcoregtk-4.0-18 libwebkit2gtk-4.0-37
python3-distupgrade ubuntu-release-upgrader-core ubuntu-release-upgrader-gtk
10 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 17.0 MB of archives.
After this operation, 15.4 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 *ttp://archive.ubuntu.com/ubuntu disco-updates/main amd64 ubuntu-release-upgrader-gtk all 1:19.04.16.5 [9,364 B]
Get:2 *ttp://archive.ubuntu.com/ubuntu disco-updates/main amd64 ubuntu-release-upgrader-core all 1:19.04.16.5 [23.7 kB]
Get:3 *ttp://archive.ubuntu.com/ubuntu disco-updates/main amd64 python3-distupgrade all 1:19.04.16.5 [101 kB]
Get:4 *ttp://security.ubuntu.com/ubuntu disco-security/main amd64 libwebkit2gtk-4.0-37 amd64 2.24.2-0ubuntu0.19.04.1 [11.3 MB]
Get:5 *ttp://security.ubuntu.com/ubuntu disco-security/main amd64 libjavascriptcoregtk-4.0-18 amd64 2.24.2-0ubuntu0.19.04.1 [4,770 kB]
Get:6 *ttp://security.ubuntu.com/ubuntu disco-security/main amd64 gir1.2-webkit2-4.0 amd64 2.24.2-0ubuntu0.19.04.1 [68.4 kB]
Get:7 *ttp://security.ubuntu.com/ubuntu disco-security/main amd64 gir1.2-javascriptcoregtk-4.0 amd64 2.24.2-0ubuntu0.19.04.1 [21.8 kB]
Get:8 *ttp://security.ubuntu.com/ubuntu disco-security/main amd64 curl amd64 7.64.0-2ubuntu1.1 [166 kB]
Get:9 *ttp://security.ubuntu.com/ubuntu disco-security/main amd64 libcurl4 amd64 7.64.0-2ubuntu1.1 [233 kB]
Get:10 *ttp://security.ubuntu.com/ubuntu disco-security/main amd64 libcurl3-gnutls amd64 7.64.0-2ubuntu1.1 [230 kB]
Fetched 17.0 MB in 31s (546 kB/s)
(Reading database ... 271096 files and directories currently installed.)
Preparing to unpack .../0-libwebkit2gtk-4.0-37_2.24.2-0ubuntu0.19.04.1_amd64.deb ...
Unpacking libwebkit2gtk-4.0-37:amd64 (2.24.2-0ubuntu0.19.04.1) over (2.24.1-1) ...
Preparing to unpack .../1-libjavascriptcoregtk-4.0-18_2.24.2-0ubuntu0.19.04.1_amd64.deb ...
Unpacking libjavascriptcoregtk-4.0-18:amd64 (2.24.2-0ubuntu0.19.04.1) over (2.24.1-1) ...
Preparing to unpack .../2-gir1.2-webkit2-4.0_2.24.2-0ubuntu0.19.04.1_amd64.deb ...
Unpacking gir1.2-webkit2-4.0:amd64 (2.24.2-0ubuntu0.19.04.1) over (2.24.1-1) ...
Preparing to unpack .../3-gir1.2-javascriptcoregtk-4.0_2.24.2-0ubuntu0.19.04.1_amd64.deb ...
Unpacking gir1.2-javascriptcoregtk-4.0:amd64 (2.24.2-0ubuntu0.19.04.1) over (2.24.1-1) ...
Preparing to unpack .../4-ubuntu-release-upgrader-gtk_1%3a19.04.16.5_all.deb ...
Unpacking ubuntu-release-upgrader-gtk (1:19.04.16.5) over (1:19.04.16.4) ...
Preparing to unpack .../5-ubuntu-release-upgrader-core_1%3a19.04.16.5_all.deb ...
Unpacking ubuntu-release-upgrader-core (1:19.04.16.5) over (1:19.04.16.4) ...
Preparing to unpack .../6-python3-distupgrade_1%3a19.04.16.5_all.deb ...
Unpacking python3-distupgrade (1:19.04.16.5) over (1:19.04.16.4) ...
Preparing to unpack .../7-curl_7.64.0-2ubuntu1.1_amd64.deb ...
Unpacking curl (7.64.0-2ubuntu1.1) over (7.64.0-2ubuntu1) ...
Preparing to unpack .../8-libcurl4_7.64.0-2ubuntu1.1_amd64.deb ...
Unpacking libcurl4:amd64 (7.64.0-2ubuntu1.1) over (7.64.0-2ubuntu1) ...
Preparing to unpack .../9-libcurl3-gnutls_7.64.0-2ubuntu1.1_amd64.deb ...
Unpacking libcurl3-gnutls:amd64 (7.64.0-2ubuntu1.1) over (7.64.0-2ubuntu1) ...
Setting up jitsi-meet-prosody (1.0.3387-1) ...
The given hostname does not exist in the config
dpkg: error processing package jitsi-meet-prosody (--configure):
installed jitsi-meet-prosody package post-installation script subprocess returned error exit status 1
Setting up libjavascriptcoregtk-4.0-18:amd64 (2.24.2-0ubuntu0.19.04.1) ...
Setting up libcurl3-gnutls:amd64 (7.64.0-2ubuntu1.1) ...
Setting up gir1.2-javascriptcoregtk-4.0:amd64 (2.24.2-0ubuntu0.19.04.1) ...
Setting up python3-distupgrade (1:19.04.16.5) ...
Setting up ubuntu-release-upgrader-core (1:19.04.16.5) ...
Setting up libwebkit2gtk-4.0-37:amd64 (2.24.2-0ubuntu0.19.04.1) ...
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-meet-prosody (= 1.0.3387-1); however:
Package jitsi-meet-prosody is not configured yet.
dpkg: error processing package jitsi-meet (--configure):
dependency problems - leaving unconfigured
Setting up libcurl4:amd64 (7.64.0-2ubuntu1.1) ...
No apport report written because the error message indicates its a followup error from a previous failure.
Setting up curl (7.64.0-2ubuntu1.1) ...
Setting up gir1.2-webkit2-4.0:amd64 (2.24.2-0ubuntu0.19.04.1) ...
Setting up ubuntu-release-upgrader-gtk (1:19.04.16.5) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.29-0ubuntu2) ...
Errors were encountered while processing:
jitsi-meet-prosody
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ sudo apt update
Hit:1 *ttp://security.ubuntu.com/ubuntu disco-security InRelease
Hit:2 *ttps://repo.skype.com/deb stable InRelease
Hit:3 *ttp://archive.ubuntu.com/ubuntu disco InRelease
Hit:4 *ttp://archive.ubuntu.com/ubuntu disco-updates InRelease
Hit:5 *ttps://download.jitsi.org stable/ InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up jitsi-meet-prosody (1.0.3387-1) ...
The given hostname does not exist in the config
dpkg: error processing package jitsi-meet-prosody (--configure):
installed jitsi-meet-prosody package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-meet-prosody (= 1.0.3387-1); however:
Package jitsi-meet-prosody is not configured yet.
dpkg: error processing package jitsi-meet (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
jitsi-meet-prosody
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)`
Entschuldigen Sie die Formatierung, ich verwende Backticks, aber es scheint nicht zu funktionieren
Bearbeitung3:Okay, ich habe endlich herausgefunden, wie ich die Fehlermeldung zumindest loswerden kannSystemprogrammproblem erkanntjedes Mal, wenn ich neu gestartet habe. Ich dachte, das bedeutete, dass der Fehler jedes Mal wieder auftrat, aber ein kurzer Blick auf /var/crash/ machte mir klar, dass dies die vorherigen Fehler waren (tatsächlich von der Installation von Jitsi und dem Install-Info-Fehler).
ls -l /var/crash/
Anschließend habe ich die Absturzberichte wie sudo rm /var/crash/*hier vorgeschlagen gelöscht:https://itsfoss.com/wie-man-das-systemprogram-problem-erkannt-ubuntu-behebt/
Danke für all deine Hilfe!