[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
I have a similar problem. For me the Ubuntu 20.04 installer would consistently crash at 90% (regardless of which hard drive I installed it to). When I followed the instructions to report the bug, it led me here. I was able to circumvent the problem by choosing "minimal installation" and NOT "download updates while installing". That made the installation succeed. It might be caused by bad hardware on my system. I don't know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in apt source package in Bionic: Invalid Status in glibc source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Invalid Status in apt source package in Focal: Confirmed Status in glibc source package in Focal: Invalid Status in ubiquity source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
Same problem for me on Raspi 4 (bridged networking) I have found a quick and dirty workaround: In crontab: @reboot root netplan apply -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [regression potential] Not SRU - N/A [scope] This is not reproducable on Eoan or Bionic; this is needed only for Focal. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 979 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 4.1M CGroup: /system.slice/systemd-networkd.service └─979 /lib/systemd/systemd-networkd Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for link '5' we don't know about, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring. systemctl restart systemd-networkd resolved the issue and a systemctl status systemd-network producessystemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 1650 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 1.6M CGroup: /system.slice/systemd-networkd.service └─1650
[Touch-packages] [Bug 1766643] [NEW] package perl-modules-5.22 5.22.1-9ubuntu0.3 failed to install/upgrade: defektes Tar-Dateisystem - Paketarchiv ist defekt
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: perl-modules-5.22 5.22.1-9ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Sat Apr 21 06:50:39 2018 DpkgTerminalLog: Vorbereitung zum Entpacken von .../perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb ... Entpacken von perl-modules-5.22 (5.22.1-9ubuntu0.3) über (5.22.1-9ubuntu0.2) ... dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb (--unpack): defektes Tar-Dateisystem - Paketarchiv ist defekt ErrorMessage: defektes Tar-Dateisystem - Paketarchiv ist defekt InstallationDate: Installed on 2016-09-26 (575 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: perl Title: package perl-modules-5.22 5.22.1-9ubuntu0.3 failed to install/upgrade: defektes Tar-Dateisystem - Paketarchiv ist defekt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1766643 Title: package perl-modules-5.22 5.22.1-9ubuntu0.3 failed to install/upgrade: defektes Tar-Dateisystem - Paketarchiv ist defekt Status in perl package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: perl-modules-5.22 5.22.1-9ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Sat Apr 21 06:50:39 2018 DpkgTerminalLog: Vorbereitung zum Entpacken von .../perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb ... Entpacken von perl-modules-5.22 (5.22.1-9ubuntu0.3) über (5.22.1-9ubuntu0.2) ... dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb (--unpack): defektes Tar-Dateisystem - Paketarchiv ist defekt ErrorMessage: defektes Tar-Dateisystem - Paketarchiv ist defekt InstallationDate: Installed on 2016-09-26 (575 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: perl Title: package perl-modules-5.22 5.22.1-9ubuntu0.3 failed to install/upgrade: defektes Tar-Dateisystem - Paketarchiv ist defekt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1766643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1517983] Re: Attempt to unlock mutex that was not locked, Or: Do not release the GDK lock if it hasn't been acquired yet
I apologize. I am running elementary and was sure that glib 2.42 was coming from trusty, which of course it doesn't. ** Changed in: gtk+2.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1517983 Title: Attempt to unlock mutex that was not locked, Or: Do not release the GDK lock if it hasn't been acquired yet Status in gtk+2.0 package in Ubuntu: Invalid Bug description: In trusty, gtk+2.0 is currently on version 2.24.23-0ubuntu. The commit specified here[1] fixes a bug where using libgtk+2.0 in an unidiomatic manner leads to a SIGABRT when starting the app. I know that unidiomatic behaviour is not supported per-se, but there are a whole bunch of "legacy" apps that are hard to update. Examples include IntelliJ IDEA, OpenXenManager, and numerous others. Is there a chance of getting libgtk+2 updated to a version that in includes [1], or getting that commit backported to trusty? The fix seems to have landed in upstream[2] and utopic[3], but not in trusty. Thanks, Claus Strasburger [1]: https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=fbf38d16bcc26630f0f721d266509f5bc292f606 [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758619 [3]: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1376530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1517983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1517983] [NEW] Attempt to unlock mutex that was not locked, Or: Do not release the GDK lock if it hasn't been acquired yet
Public bug reported: In trusty, gtk+2.0 is currently on version 2.24.23-0ubuntu. The commit specified here[1] fixes a bug where using libgtk+2.0 in an unidiomatic manner leads to a SIGABRT when starting the app. I know that unidiomatic behaviour is not supported per-se, but there are a whole bunch of "legacy" apps that are hard to update. Examples include IntelliJ IDEA, OpenXenManager, and numerous others. Is there a chance of getting libgtk+2 updated to a version that in includes [1], or getting that commit backported to trusty? The fix seems to have landed in upstream[2] and utopic[3], but not in trusty. Thanks, Claus Strasburger [1]: https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=fbf38d16bcc26630f0f721d266509f5bc292f606 [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758619 [3]: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1376530 ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1517983 Title: Attempt to unlock mutex that was not locked, Or: Do not release the GDK lock if it hasn't been acquired yet Status in gtk+2.0 package in Ubuntu: New Bug description: In trusty, gtk+2.0 is currently on version 2.24.23-0ubuntu. The commit specified here[1] fixes a bug where using libgtk+2.0 in an unidiomatic manner leads to a SIGABRT when starting the app. I know that unidiomatic behaviour is not supported per-se, but there are a whole bunch of "legacy" apps that are hard to update. Examples include IntelliJ IDEA, OpenXenManager, and numerous others. Is there a chance of getting libgtk+2 updated to a version that in includes [1], or getting that commit backported to trusty? The fix seems to have landed in upstream[2] and utopic[3], but not in trusty. Thanks, Claus Strasburger [1]: https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=fbf38d16bcc26630f0f721d266509f5bc292f606 [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758619 [3]: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1376530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1517983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373598] Re: apt-get update fails, hash sum mismatches (trusty)
As this seems to affect mostly users of the de. mirror I subscribed the owner of that mirror to this bug (hope this is the right way to go about it). Changing to the German NetCologne mirror fixed this issue for me for now. It was an ongoing problem with several Trusty servers for several month. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1373598 Title: apt-get update fails, hash sum mismatches (trusty) Status in apt package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: 1. Release: Description: Ubuntu 14.04.1 LTS Release: 14.04 2. not a package. The whole distro is broken. 3. I always expect apt-get update to work, at least with Ubuntu's own repositories. 4. apt-get update failed, and later apt-get dist upgrade It started with this when doing a normal apt-get update W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/source/Sources Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/universe/binary-i386/Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. When doing a dist-upgrade, I then got this: E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package linux-image-extra-3.13.0-36-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however: Package linux-image-extra-3.13.0-36-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ... Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic /boot/vmlinuz-3.13.0-36-generic Setting up linux-headers-generic (3.13.0.36.43) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 3.13.0.36.43); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured And later this at the end: Processing triggers for libc-bin (2.19-0ubuntu6.3) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.5 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Sep 24 21:57:55 2014 InstallationDate: Installed on 2013-05-09 (503 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-05-04 (142 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1373598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
