(Solved) Problems with Ubuntu version updates

Software
1

After successful update from system to Ubuntu 22.04.1 LTS I failed with update to a stable V6 kicad version. I tried

sudo add-apt-repository --yes ppa:kicad/kicad-6.0-releases
sudo apt update
sudo apt install --install-recommends kicad

what reports many errors:

dpkg: Fehler beim Bearbeiten des Paketes openmpi-bin (–configure):
»installiertes openmpi-bin-Skript des Paketes post-installation«-Unterprozess
gab den Fehlerwert 2 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von mpi-default-bin:
mpi-default-bin hängt ab von openmpi-bin; aber:
Paket openmpi-bin ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten des Paketes mpi-default-bin (–configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von libcoarrays-openmpi-dev
:amd64:
libcoarrays-openmpi-dev:amd64 hängt ab von openmpi-bin; aber:
Paket openmpi-bin ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes libcoarrays-openmpi-dev:amd64 (–config
ure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von libopenmpi-dev:amd64:
libopenmpi-dev:amd64 hängt ab von openmpi-bin (>= 3.0.0-1); aber:
Paket openmpi-bin ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes libopenmpi-dev:amd64 (–configure):
Abhängigkeitsprobleme - verbleibt unkonfigurEs wurde kein Apport-Bericht verfas
st, da die Fehlermeldung darauf hindeutet, dass dies lediglich ein Folgefehler e
ines vorherigen Problems ist.
Es wurde kein Apport-Bericht verfasst, da die Fehle
rmeldung darauf hindeutet, dass dies lediglich ein Folgefehler eines vorherigen
Problems ist.
Es wurde kein Apport-Bericht verfasst, da das Limit MaxReports bere
its erreicht ist.

dpkg: Abhängigkeitsprobleme verhindern Konfiguration von libboost-mpi-python1.74
.0:
libboost-mpi-python1.74.0 hängt ab von mpi-default-bin; aber:
Paket mpi-default-bin ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes libboost-mpi-python1.74.0 (–configure)
:
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von libboost-mpi-python1.74
-dev:
libboost-mpi-python1.74-dev hängt ab von libboost-mpi-python1.74.0 (= 1.74.0-14
ubuntu3); aber:
Paket libboost-mpi-python1.74.0 ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes libboost-mpi-python1.74-dev (–configur
e):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von libboost-mpi-python-dev
:
libboost-mpi-python-dev hängt ab von libboost-mpi-python1.74-dev; aber:
Paket libboost-mpi-python1.74-dev ist noch nicht konfiguriert.

dpkg: FehlerEs wurde kein Apport-Bericht verfasst, da das Limit MaxReports berei
ts erreicht ist.
beim Bearbeiten des Paketes libboost-mpi-python-dev (–configur
e):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von libboost-all-dev:
libboost-all-dev hängt ab von libboost-mpi-python-dev; aber:
Paket libboost-mpi-python-dev ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes libboost-all-dev (–configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von mpi-default-dev:
mpi-default-dev hängt ab von libopenmpi-dev; aber:
Paket libopenmpi-dev:amd64 ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes mpi-default-dev (–configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von libboost-mpi1.74-dev:
libboost-mpi1.74-dev hängt ab von mpi-default-dev; aber:
Paket mpi-default-dev ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes libboost-mpi1.74-dev (–configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von libboost-mpi-dev:
libboost-mpi-dev hängt ab von libboost-mpi1.74-dev; aber:
Paket libboost-mpi1.74-dev ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes libboost-mpi-dev (–configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert

Fehler traten auf beim Bearbeiten von:
openmpi-bin
mpi-default-bin
libcoarrays-openmpi-dev:amd64
libopenmpi-dev:amd64
libboost-mpi-python1.74.0
libboost-mpi-python1.74-dev
libboost-mpi-python-dev
libboost-all-dev
mpi-default-dev
libboost-mpi1.74-dev
libboost-mpi-dev
E: Sub-process /usr/bin/dpkg returned an error code (1)

There still seems to live parts of the old V5.99 Version for what I was not able to uninstall and I do not know what the root of all this errors is. My knowledge on Linux is not enough to know what to do in this situation and sorry for the German system setup

2

I hesitate to get involved because I don’t run Ubuntu and don’t know the dependencies between the packages. It looks messy. It doesn’t help that the error messages are in German. Could you not help us out by switching to English when you want to capture the errors?

I don’t think kicad depends at all on MPI. The only package in the list of failures that might be needed is libboost, but even then it’s a dev package, needed only for compiling, not running an app.

I propose something drastic: Delete all the packages on the error list at the end and see if it complains. Hopefully you don’t use any MPI applications. If the deletion succeeds, then proceed to install kicad.

I suspect the MPI errors have nothing to do with kicad but are residual errors caused by upgrading your Ubuntu release and would have been triggered by installing anything.

3

At least, switching of language worked. Any hints about how to solve are welcome:

sudo apt autoremove

Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
11 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up openmpi-bin (4.1.2-2ubuntu1) …
update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc
dpkg: error processing package openmpi-bin (–configure):
installed openmpi-bin package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of mpi-default-bin:
mpi-default-bin depends on openmpi-bin; however:
Package openmpi-bin is not configured yet.

dpkg: error processing package mpi-default-bin (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libcoarrays-openmpi-dev:amd64:
libcoarrays-openmpi-dev:amd64 depends on openmpi-bin; however:
Package openmpi-bin is not configured yet.

dpkg: error processing package libcoarrays-openmpi-dev:amd64 (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libopenmpi-dev:amd64:
libopenmpi-dev:amd64 depends on openmpi-bin (>= 3.0.0-1); however:
Package openmpi-bin is not configured yet.

dpkg: error processing package libopenmpi-dev:amd64 (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup erro
r from a previous failure.
No apport report written because the error message ind
icates its a followup error from a previous failure.
No apport report written bec
ause MaxReports is reached already
No apport report written because MaxReports is
reached already
dpkg: dependency problems prevent configuration of libboost-mpi-
python1.74.0:
libboost-mpi-python1.74.0 depends on mpi-default-bin; however:
Package mpi-default-bin is not configured yet.

dpkg: error processing package libboost-mpi-python1.74.0 (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libboost-mpi-python1.74-dev:
libboost-mpi-python1.74-dev depends on libboost-mpi-python1.74.0 (= 1.74.0-14ub
untu3); however:
Package libboost-mpi-python1.74.0 is not configured yet.

dpkg: error processing package libboost-mpi-python1.74-dev (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libboost-mpi-python-dev:
libboost-mpi-python-dev depends on libboost-mpi-python1.74-dev; however:
Package libboost-mpi-python1.74-dev is not configured yet.

dpkg: error processing package libboost-mpi-python-dev (–configure):
dependency prNo apport report written because MaxReports is reached already
No a
pport report written because MaxReports is reached already
oblems - leaving uncon
figured
dpkg: dependency problems prevent configuration of libboost-all-dev:
libboost-all-dev depends on libboost-mpi-python-dev; however:
Package libboost-mpi-python-dev is not configured yet.

dpkg: error processing package libboost-all-dev (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mpi-default-dev:
mpi-default-dev depends on libopenmpi-dev; however:
Package libopenmpi-dev:amd64 is not configured yet.

dpkg: error processing package mpi-default-dev (–configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
No apport report w
ritten because MaxReports is reached already
dpkg: dependency problems prevent co
nfiguration of libboost-mpi1.74-dev:
libboost-mpi1.74-dev depends on mpi-default-dev; however:
Package mpi-default-dev is not configured yet.

dpkg: error processing package libboost-mpi1.74-dev (–configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency p
roblems prevent configuration of libboost-mpi-dev:
libboost-mpi-dev depends on libboost-mpi1.74-dev; however:
Package libboost-mpi1.74-dev is not configured yet.

dpkg: error processing package libboost-mpi-dev (–configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
Errors were encoun
tered while processing:
openmpi-bin
mpi-default-bin
libcoarrays-openmpi-dev:amd64
libopenmpi-dev:amd64
libboost-mpi-python1.74.0
libboost-mpi-python1.74-dev
libboost-mpi-python-dev
libboost-all-dev
mpi-default-dev
libboost-mpi1.74-dev
libboost-mpi-dev
E: Sub-process /usr/bin/dpkg returned an error code (1)
jv@JamesWebb:~$

4

Do a real remove of all the offending packages, not autoremove. Autoremove only removes stray packages that are not needed by anything.

5

problem always seems recursive:

sudo apt purge openmpi-bin

Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages were automatically installed and are no longer required:
libboost-atomic-dev libboost-atomic1.74-dev libboost-atomic1.74.0
libboost-chrono-dev libboost-chrono1.74-dev libboost-chrono1.74.0
libboost-container-dev libboost-container1.74-dev libboost-container1.74.0
libboost-context-dev libboost-context1.74-dev libboost-context1.74.0
libboost-coroutine-dev libboost-coroutine1.74-dev libboost-coroutine1.74.0
libboost-date-time-dev libboost-date-time1.74-dev libboost-date-time1.74.0
libboost-dev libboost-exception-dev libboost-exception1.74-dev
libboost-fiber-dev libboost-fiber1.74-dev libboost-fiber1.74.0
libboost-filesystem-dev libboost-filesystem1.74-dev libboost-graph-dev
libboost-graph-parallel-dev libboost-graph-parallel1.74-dev
libboost-graph-parallel1.74.0 libboost-graph1.74-dev libboost-graph1.74.0
libboost-iostreams-dev libboost-iostreams1.74-dev libboost-locale-dev
libboost-locale1.74-dev libboost-log-dev libboost-log1.74-dev
libboost-log1.74.0 libboost-math-dev libboost-math1.74-dev
libboost-math1.74.0 libboost-mpi1.74.0 libboost-nowide-dev
libboost-nowide1.74-dev libboost-nowide1.74.0 libboost-numpy-dev
libboost-numpy1.74-dev libboost-numpy1.74.0 libboost-program-options-dev
libboost-program-options1.74-dev libboost-program-options1.74.0
libboost-python-dev libboost-python1.74-dev libboost-python1.74.0
libboost-random-dev libboost-random1.74-dev libboost-random1.74.0
libboost-regex-dev libboost-regex1.74-dev libboost-serialization-dev
libboost-serialization1.74-dev libboost-serialization1.74.0
libboost-stacktrace-dev libboost-stacktrace1.74-dev
libboost-stacktrace1.74.0 libboost-system-dev libboost-system1.74-dev
libboost-system1.74.0 libboost-test-dev libboost-test1.74-dev
libboost-test1.74.0 libboost-thread-dev libboost-thread1.74-dev
libboost-timer-dev libboost-timer1.74-dev libboost-timer1.74.0
libboost-tools-dev libboost-type-erasure-dev libboost-type-erasure1.74-dev
libboost-type-erasure1.74.0 libboost-wave-dev libboost-wave1.74-dev
libboost-wave1.74.0 libboost1.74-dev libboost1.74-tools-dev libcaf-openmpi-3
libevent-core-2.1-7 libevent-dev libevent-extra-2.1-7 libevent-openssl-2.1-7
libevent-pthreads-2.1-7 libfabric1 libhwloc-dev libhwloc-plugins libhwloc15
libibverbs-dev libnl-3-dev libnl-route-3-dev libnuma-dev libopenmpi3
libpmix-dev libpmix2 libpsm-infinipath1 libpsm2-2 libucx0 openmpi-common
Use ‘sudo apt autoremove’ to remove them.
The following packages will be REMOVED:
openmpi-bin*
0 upgraded, 0 newly installed, 1 to remove and 15 not upgraded.
1 not fully installed or removed.
After this operation, 567 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database … 438530 files and directories currently installed.)
Removing openmpi-bin (4.1.2-2ubuntu1) …
update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link s
ame as main link /usr/bin/mpicc
dpkg: error processing package openmpi-bin (–remove):
installed openmpi-bin package pre-removal script subprocess returned error exit
status 2
dpkg: too many errors, stopping
Errors were encountered while processing:
openmpi-bin
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
jv@JamesWebb:~$

6

Try this tip to force removal: apt - Removing broken packages in Ubuntu - Stack Overflow

7

Failed with following the Stack Overflow instructions but anything diffrent happend there without understanding:

sudo apt install --install-recommends kicad

Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
kicad is already the newest version (6.0.10-0-202212181939+86aedd382b~118~ubuntu22.04.1).
0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.

Try invoking from commandline, only V5.99 project manager starts
Schema or PCB reports IO_ERROR Failed to laod kiface library.
Seems to be a problem with parts of old versions remaining anywhere ?

8

List the packages matching *kicad* with: dpkg -l ‘*kicad*’

Perhaps it will find the 5.99 version and you can remove that explicitly.

9

jv@JamesWebb:~$ dpkg -l kicad |more

everything with “nightly” seems suspicious ?

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
++±========================-==================================================-============-============================================
un kicad (no description available)
un kicad-common (no description available)
un kicad-demo (no description available)
ii kicad-demos 6.0.10-0-202212181939+86aedd382b~118~ubuntu20.04.1 all Common files used by kicad
ii kicad-doc-en 6.0.10-0-202212181943+1944~33~ubuntu22.04.1 all Kicad help files (English)
ii kicad-footprints 6.0.10-0-202212181946+24671f775~11~ubuntu22.04.1 all Kicad footprints (modules)
ii kicad-libraries 6.0.10-0-202212182040+9~ubuntu22.04.1 all KiCad meta-package for deps to all libraries
un kicad-library (no description available)
un kicad-library-all (no description available)
un kicad-library-footprints (no description available)
un kicad-library-packages3d (no description available)
un kicad-library-symbols (no description available)
un kicad-library-templates (no description available)
rc kicad-nightly 202205171718+5edc03e85b~148~ubuntu20.04.1 amd64 Electronic schematic and PCB design software
un kicad-nightly-demos (no description available)
un kicad-nightly-doc-en (no description available)
ii kicad-nightly-footprints 202212192116+3ac90c7ed~14~ubuntu20.04.1 all Kicad footprints (modules)
ii kicad-nightly-libraries 1:202202221504+12~ubuntu20.04.1 all KiCad meta-package for deps to all libraries
un kicad-nightly-locale-bg (no description available)
un kicad-nightly-locale-ca (no description available)
un kicad-nightly-locale-cs (no description available)
un kicad-nightly-locale-de (no description available)
un kicad-nightly-locale-el (no description available)
un kicad-nightly-locale-es (no description available)
un kicad-nightly-locale-fi (no description available)
un kicad-nightly-locale-fr (no description available)
un kicad-nightly-locale-hu (no description available)
un kicad-nightly-locale-id (no description available)
un kicad-nightly-locale-it (no description available)
un kicad-nightly-locale-ja (no description available)
un kicad-nightly-locale-ko (no description available)
un kicad-nightly-locale-lt (no description available)
un kicad-nightly-locale-nl (no description available)
un kicad-nightly-locale-pl (no description available)
un kicad-nightly-locale-pt (no description available)
un kicad-nightly-locale-ru (no description available)
un kicad-nightly-locale-sk (no description available)
un kicad-nightly-locale-sl (no description available)
un kicad-nightly-locale-sv (no description available)
un kicad-nightly-locale-zh (no description available)
ii kicad-nightly-packages3d 202212181918+7aeaa02a~13~ubuntu20.04.1 all Kicad packages3d (3d models for footprints)
ii kicad-nightly-symbols 202212192216+85beb52c~10~ubuntu20.04.1 all Kicad symbols (schematic)
ii kicad-nightly-templates 202205181717+ae2b46f~11~ubuntu20.04.1 all Kicad templates
ii kicad-packages3d 6.0.10-0-202212181947+417c4ea8~9~ubuntu22.04.1 all Kicad packages3d (3d models for footprints)
ii kicad-symbols 6.0.10-0-202212181945+3ec40517~7~ubuntu22.04.1 all Kicad symbols (schematic)
ii kicad-templates 6.0.10-0-202212181944+ae2b46f~9~ubuntu22.04.1 all Kicad templates
ii libngspice-kicad 0.1-38~202211100132+14f42f805~ubuntu20.04.1 amd64 Library (shared) for ngspice. Used by kicad
un ngspice-kicad (no description available)
jv@JamesWebb:~$

10

Everything from ubuntu20.04 that is actually installed (not u in first column) should be removed. After removing them, reinstall kicad-6.0.10 with --install-recommends as the latest versions of the libraries may not have been installed.

Also have you commented out the 20.04 repos somewhere under /etc/apt? It should be part of the upgrade instructions.

11

I did not rename anything from /etc/apt - what to do there ?

Using “apt remove” was able to delete everything without u in first column except kicad-nightly. Therefore I used “apt purge” and everything disapeared. Invoking kicad from commandline, Version “5.99 dirty” still starts with the project manager from everywhere

dpkg -l kicad |more
dpkg-query: no packages found matching kicad

12

I don’t know how Ubuntu organises /etc/apt these days, but the repo lines are in files under that directory, either at the first or second level. Check that any lines in any file referring to 20.04 (or the codename focal) is not present, or commented out. If present that line would have been put there by the install of 20.04.

Looks like you still have a copy of kicad somewhere. Do “which kicad” to see where the executable is, and then take the pathname and feed it to dpkg like this: “dpkg -S <output of ‘which kicad’>” That will tell you which package contains it. If no package contains it but the executable exists, then it was installed outside of the package manager.

13

which kicad
/usr/local/bin/kicad
jv@JamesWebb:~$ sudo apt remove /usr/local/bin/kicad
Reading package lists… Done
E: Unsupported file /usr/local/bin/kicad given on commandline

what went wrong ?

14

You can only remove packages with dpkg, not files. Somehow you installed kicad by other means, perhaps a tarball. /usr/local is not a standard location for packages to use. You have to track down all the kicad stuff you installed that bypassed the package manager and remove it.

15

rm /usr/local/bin/kicad
rm: remove write-protected regular file ‘/usr/local/bin/kicad’? y
rm: cannot remove ‘/usr/local/bin/kicad’: Permission denied
jv@JamesWebb:~$ sudo rm /usr/local/bin/kicad
jv@JamesWebb:~$ kicad
bash: /usr/local/bin/kicad: No such file or directory
jv@JamesWebb:~$ sudo rm /usr/local/bin/eeschema
jv@JamesWebb:~$ sudo rm /usr/local/bin/bitmap2component
jv@JamesWebb:~$ sudo rm /usr/local/bin/dxf2idf
jv@JamesWebb:~$ sudo rm /usr/local/bin/_cvpcb.kiface
jv@JamesWebb:~$ sudo rm /usr/local/bin/_eeschema.kiface
jv@JamesWebb:~$ sudo rm /usr/local/bin/gerbview
jv@JamesWebb:~$ sudo rm /usr/local/bin/_gerbview.kiface
jv@JamesWebb:~$ sudo rm /usr/local/bin/idf2vrml
jv@JamesWebb:~$ sudo rm /usr/local/bin/idfcyl
jv@JamesWebb:~$ sudo rm /usr/local/bin/idfrect
jv@JamesWebb:~$ sudo rm /usr/local/bin/kicad2step
jv@JamesWebb:~$ sudo rm /usr/local/bin/_pcb_calculator.kiface
jv@JamesWebb:~$ sudo rm /usr/local/bin/pcb_calculator
jv@JamesWebb:~$ sudo rm /usr/local/bin/pcbnew
jv@JamesWebb:~$ sudo rm /usr/local/bin/pl_editor
jv@JamesWebb:~$ sudo rm /usr/local/bin/kicad-ogltest
jv@JamesWebb:~$ sudo rm /usr/local/bin/_pcbnew.kiface
jv@JamesWebb:~$ sudo rm /usr/local/bin/_pl_editor.kiface
jv@JamesWebb:~$

16

Installation seems to run fine now, but where is it ?

jv@JamesWebb:~$ sudo add-apt-repository --yes ppa:kicad/kicad-6.0-releases
PPA publishes dbgsym, you may need to include ‘main/debug’ component
Repository: ‘deb Index of /kicad/kicad-6.0-releases/ubuntu jammy main’
Description:
Official KiCad 6.0 releases
More info: PPA for KiCad: 6.0 releases : “KiCad” team
Adding repository.
Found existing deb entry in /etc/apt/sources.list.d/kicad-ubuntu-kicad-6_0-releases-jammy.list
Adding deb entry to /etc/apt/sources.list.d/kicad-ubuntu-kicad-6_0-releases-jammy.list
Found existing deb-src entry in /etc/apt/sources.list.d/kicad-ubuntu-kicad-6_0-releases-jammy.list
Adding disabled deb-src entry to /etc/apt/sources.list.d/kicad-ubuntu-kicad-6_0-releases-jammy.list
Adding key to /etc/apt/trusted.gpg.d/kicad-ubuntu-kicad-6_0-releases.gpg with fingerprint FDA854F61C4D0D9572BB95E5245D5502FAD7A805
Hit:1 Index of /ubuntu jammy InRelease
Get:2 Index of /ubuntu jammy-updates InRelease [114 kB]
Hit:3 Index of /kicad/kicad-6.0-releases/ubuntu jammy InRelease
Get:4 Index of /ubuntu jammy-security InRelease [110 kB]
Get:5 Index of /ubuntu jammy-backports InRelease [99,8 kB]
Get:6 Index of /ubuntu jammy-updates/main amd64 DEP-11 Metadata [94,9 kB]
Get:7 Index of /ubuntu jammy-updates/universe amd64 DEP-11 Metadata [258 kB]
Get:8 Index of /ubuntu jammy-updates/multiverse amd64 DEP-11 Metadata [940 B]
Get:9 Index of /ubuntu jammy-backports/universe amd64 DEP-11 Metadata [11,7 kB]
Get:10 Index of /ubuntu jammy-security/main amd64 DEP-11 Metadata [20,1 kB]
Get:11 Index of /ubuntu jammy-security/universe amd64 DEP-11 Metadata [13,3 kB]
Hit:12 Index of /kicad/kicad-6.0-releases/ubuntu focal InRelease
Fetched 723 kB in 1s (567 kB/s)
Reading package lists… Done
jv@JamesWebb:~$ sudo apt update
Hit:1 Index of /kicad/kicad-6.0-releases/ubuntu focal InRelease
Hit:2 Index of /ubuntu jammy InRelease
Hit:3 Index of /ubuntu jammy-updates InRelease
Hit:4 Index of /kicad/kicad-6.0-releases/ubuntu jammy InRelease
Hit:5 Index of /ubuntu jammy-backports InRelease
Hit:6 Index of /ubuntu jammy-security InRelease
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
14 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
jv@JamesWebb:~$ sudo apt install --install-recommends kicad
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
kicad is already the newest version (6.0.10-0-202212181939+86aedd382b~118~ubuntu22.04.1).
0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.
jv@JamesWebb:~$
jv@JamesWebb:~$ kicad
bash: /usr/local/bin/kicad: No such file or directory
jv@JamesWebb:~$ which kicad
/usr/bin/kicad
jv@JamesWebb:~$

17

The bash shell keeps a cache of recent executable paths. You can get it to forget a cached path with

hash -d kicad

or logout and login again.

Just in case you did manage to start kicad 6.0 at least once before, you should remove the contents under ~/.config/kicad/6.0 so that it will setup afresh, otherwise it may not find the standard libraries.

Also this:

indicates you still have a reference to focal in /etc/apt, as mentioned. It could cause problems later so you should comment out that reference.

18

After flushing the path, its now /usr/bin/kicad (before /usr/local/bin/kicad) and the project manager welcomes to V6.0. I am able to open project pcb and sbk. PCB cannot show pads for the moment and probably there is no library access as I ignored your hints to “focal InRelease”.

Therefore I have no idea on what to do for “comment out that reference”.
My /etc/apt/ looks like this:

jv@JamesWebb:~$ cd /etc
jv@JamesWebb:/etc$ cd apt
jv@JamesWebb:/etc/apt$ ls
apt.conf.d preferences.d sources.list.distUpgrade trusted.gpg~
auth.conf.d sources.list sources.list.save trusted.gpg.d
keyrings sources.list.d trusted.gpg
jv@JamesWebb:/etc/apt$

19

Libraries for 6.0 should have been installed with the official instructions. If you had private libraries you’ll need to add them again.

This shouldn’t affect the library situation. Look for references to focal in any file under /etc/apt including the second level. They are text files so you can grep for focal. Then comment out those lines.

It’s past bedtime here so good luck. And practice better hygiene with software installs, stick to packages as far as possible as side installs can disrupt.

20

jv@JamesWebb:/etc/apt$ grep focal .
grep: apt.conf.d: Is a directory
grep: auth.conf.d: Is a directory
grep: preferences.d: Is a directory
grep: sources.list.d: Is a directory
sources.list.distUpgrade:deb Index of /ubuntu focal main restricted
sources.list.distUpgrade:deb Index of /ubuntu focal-updates main restricted
sources.list.distUpgrade:deb Index of /ubuntu focal universe
sources.list.distUpgrade:deb Index of /ubuntu focal-updates universe
sources.list.distUpgrade:deb Index of /ubuntu focal multiverse
sources.list.distUpgrade:deb Index of /ubuntu focal-updates multiverse
sources.list.distUpgrade:deb Index of /ubuntu focal-backports main restricted universe multiverse
sources.list.distUpgrade:deb Index of /ubuntu focal-security main restricted
sources.list.distUpgrade:deb Index of /ubuntu focal-security universe
sources.list.distUpgrade:deb Index of /ubuntu focal-security multiverse
grep: trusted.gpg.d: Is a directory

All non comments in sources.list.distUpgrade are focal reference.
Therefore I can delete the complete file ?
There are some more in ect/apt/soruces.list.d/
jv@JamesWebb:/etc/apt/sources.list.d$ grep focal .
freecad-maintainers-ubuntu-occt-releases-bionic.list:# deb Index of /freecad-maintainers/occt-releases/ubuntu focal main # Bei Aktualisierung zu focal deaktiviert
freecad-maintainers-ubuntu-occt-releases-bionic.list.distUpgrade:# deb Index of /freecad-maintainers/occt-releases/ubuntu focal main # Bei Aktualisierung zu focal deaktiviert
freecad-maintainers-ubuntu-occt-releases-bionic.list.save:# deb Index of /freecad-maintainers/occt-releases/ubuntu focal main # Bei Aktualisierung zu focal deaktiviert
gezakovacs-ubuntu-ppa-focal.list:# deb-src Index of /gezakovacs/ppa/ubuntu focal main
gezakovacs-ubuntu-ppa-focal.list.distUpgrade:deb Index of /gezakovacs/ppa/ubuntu focal main
gezakovacs-ubuntu-ppa-focal.list.distUpgrade:# deb-src Index of /gezakovacs/ppa/ubuntu focal main
gezakovacs-ubuntu-ppa-focal.list.save:# deb-src Index of /gezakovacs/ppa/ubuntu focal main
js-reynaud-ubuntu-kicad-dev-nightly-bionic.list:# deb-src Index of /js-reynaud/kicad-dev-nightly/ubuntu focal main # Bei Aktualisierung zu focal deaktiviert
js-reynaud-ubuntu-kicad-dev-nightly-bionic.list.distUpgrade:# deb-src Index of /js-reynaud/kicad-dev-nightly/ubuntu focal main # Bei Aktualisierung zu focal deaktiviert
js-reynaud-ubuntu-kicad-dev-nightly-bionic.list.save:# deb-src Index of /js-reynaud/kicad-dev-nightly/ubuntu focal main # Bei Aktualisierung zu focal deaktiviert
js-reynaud-ubuntu-ngspice-bionic.list:# deb Index of /js-reynaud/ngspice/ubuntu focal main # Bei Aktualisierung zu focal deaktiviert
js-reynaud-ubuntu-ngspice-bionic.list.distUpgrade:# deb Index of /js-reynaud/ngspice/ubuntu focal main # Bei Aktualisierung zu focal deaktiviert
js-reynaud-ubuntu-ngspice-bionic.list.save:# deb Index of /js-reynaud/ngspice/ubuntu focal main # Bei Aktualisierung zu focal deaktiviert
kicad-ubuntu-kicad-5_1-releases-focal.list:# deb-src Index of /kicad/kicad-5.1-releases/ubuntu focal main
kicad-ubuntu-kicad-5_1-releases-focal.list.distUpgrade:deb Index of /kicad/kicad-5.1-releases/ubuntu focal main
kicad-ubuntu-kicad-5_1-releases-focal.list.distUpgrade:# deb-src Index of /kicad/kicad-5.1-releases/ubuntu focal main
kicad-ubuntu-kicad-5_1-releases-focal.list.save:# deb-src Index of /kicad/kicad-5.1-releases/ubuntu focal main
kicad-ubuntu-kicad-6_0-releases-focal.list:deb-src Index of /kicad/kicad-6.0-releases/ubuntu focal main
kicad-ubuntu-kicad-6_0-releases-focal.list.distUpgrade:deb Index of /kicad/kicad-6.0-releases/ubuntu focal main
kicad-ubuntu-kicad-6_0-releases-focal.list.distUpgrade:# deb-src Index of /kicad/kicad-6.0-releases/ubuntu focal main
kicad-ubuntu-kicad-6_0-releases-focal.list.save:# deb-src Index of /kicad/kicad-6.0-releases/ubuntu focal main
kicad-ubuntu-kicad-dev-nightly-focal.list:# deb-src Index of /kicad/kicad-dev-nightly/ubuntu focal main
kicad-ubuntu-kicad-dev-nightly-focal.list.distUpgrade:deb Index of /kicad/kicad-dev-nightly/ubuntu focal main
kicad-ubuntu-kicad-dev-nightly-focal.list.distUpgrade:# deb-src Index of /kicad/kicad-dev-nightly/ubuntu focal main
kicad-ubuntu-kicad-dev-nightly-focal.list.save:# deb-src Index of /kicad/kicad-dev-nightly/ubuntu focal main
teamviewer.list:# deb https://linux.teamviewer.com/deb stable main # Bei Aktualisierung zu focal deaktiviert
teamviewer.list.distUpgrade:# deb https://linux.teamviewer.com/deb stable main # Bei Aktualisierung zu focal deaktiviert
teamviewer.list.save:# deb https://linux.teamviewer.com/deb stable main # Bei Aktualisierung zu focal deaktiviert
jv@JamesWebb:/etc/apt/sources.list.d$