Lubuntu 22.04 LTS LiveCD consistent crash since Aug 2023
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lubuntu-meta (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Reproducing the issue is very simple.
1. Boot a LiveUSB drive with Lubuntu 22.04.3 LTS Jammy Jellyfish
2. Once it starts, do "cat /etc/apt/
deb cdrom:[Lubuntu 22.04.3 LTS _Jammy Jellyfish_ - Release amd64 (20230807)]/ jammy main multiverse restricted universe
deb http://
deb http://
deb http://
3. sudo apt update
This shows some errors among other successful updates :
Err:3 http://
404 Not Found [IP: 185.125.190.39 80]
Err:18 http://
404 Not Found [IP: 185.125.190.39 80]
Err:50 http://
404 Not Found [IP: 185.125.190.39 80]
Err:12 http://
404 Not Found [IP: 91.189.91.81 80]
Fetched 73.1 MB in 12s (6,337 kB/s)
E: Failed to fetch http://
E: Failed to fetch http://
E: Failed to fetch http://
E: Failed to fetch http://
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
4. sudo apt install pychess
The GIU will crash and shows messages like :
integrity: Problem loading X.509 certificate -65
[FAILED] Failed to setup automunt Arbitrary Executable File Formats File System Automount Point.
[FAILED] Failed to start User Manager for UID 999
[FAILED] Failed to start Regular background program processing daemon
systemd-
[FAILED] Failed to start Snap Daemon
[FAILED] Failed to start Bluetooth service
[FAILED] Failed to start Avahi mDNS service
This issue started only in the past month or so - earlier the same steps were working just fine.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 2037770
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.
Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. Your issue appears to be network related, thus a support issue.
I suspect a Support site would be more appropriate, eg. https:/ /answers. launchpad. net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http:// loco.ubuntu. com/ or asking at https:/ /askubuntu. com or https:/ /ubuntuforums. org, or for more support options please look at https:/ /discourse. ubuntu. com/t/community -support/ 709