[Bug 1926672] Re: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition
** Attachment added: "apport.ubiquity.mzexll29.apport" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+attachment/5499132/+files/apport.ubiquity.mzexll29.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926672 Title: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926672] Re: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition
apport-cli is crashing on hirsute, so I cannot send you the debug log, but I have tried my setting (with existing swap and efi partitions) again, and am still getting the same error. I also took some screenshots and saved the debug log, in case you need it. Just in case, "apport-cli -u 1926672" and "apport-collect 1926672" are crashing with the following error: Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 597, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 719, in run_argv return self.run_update_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 637, in run_update_report self.crashdb.update(self.options.update_report, self.report, File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 419, in update bug.lp_save() File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 775, in lp_save response, content = self._root._browser.patch( File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 494, in patch return self._request( File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 438, in _request raise error lazr.restfulclient.errors.PreconditionFailed: HTTP Error 412: Precondition Failed Response headers: --- content-length: 0 content-security-policy: frame-ancestors 'self'; content-type: text/plain date: Fri, 21 May 2021 00:52:01 GMT server: zope.server.http (HTTP) status: 412 strict-transport-security: max-age=15552000 vary: Accept x-content-type-options: nosniff x-content-type-warning: guessed from content x-frame-options: SAMEORIGIN x-launchpad-revision: efc28e2b5d587feb8d4730501a578b7c3feee810 x-lazr-notifications: [] x-powered-by: Zope (www.zope.org), Python (www.python.org) x-xss-protection: 1; mode=block --- Response body: --- b'' --- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926672 Title: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926672] Re: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition
** Tags added: ubiquity-21.04.19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926672 Title: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926672] Re: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition
Okay, having a closer look at the uploaded logs I just noticed the timestamp in syslog (20 December without year), so those logs are really old (probably from 2018) and misleading. Maybe apport uploaded logs from an older crash? In any case, the bug is still there. I will try again with 20.04 and 20.10, collect the logs and upload them here. Sorry for the confusion! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926672 Title: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926672] UbiquitySyslog.txt
apport information ** Attachment added: "UbiquitySyslog.txt" https://bugs.launchpad.net/bugs/1926672/+attachment/5494134/+files/UbiquitySyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926672 Title: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926672] UbiquityDm.txt
apport information ** Attachment added: "UbiquityDm.txt" https://bugs.launchpad.net/bugs/1926672/+attachment/5494133/+files/UbiquityDm.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926672 Title: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926672] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1926672/+attachment/5494132/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926672 Title: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926672] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1926672/+attachment/5494131/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926672 Title: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926672] OemConfigLog.txt
apport information ** Attachment added: "OemConfigLog.txt" https://bugs.launchpad.net/bugs/1926672/+attachment/5494130/+files/OemConfigLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926672 Title: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926672] Re: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition
apport information
** Tags added: apport-collected hirsute oem-config wayland-session
** Description changed:
In focal 20.04.02 the ubiquity-gtk installer (20.04.15.11/focal-updates)
always crashes after the partition step.
Although this seems to be an old bug, I could not find a relevant bug
report so far.
I am having this issue when installing Ubuntu 20.04 to removable media
from an existing Ubuntu 20.04 system. I could reproduce the issue on a
PC in UEFI mode and on another one in BIOS mode. Before reporting this
bug, I tested the installer on both Live USB media and internal disks.
How to reproduce?
1. The install medium needs to be writable (i.e. no CD/DVD) and contain a
mounted EFI partition (e.g. /dev/sda1), while the target presumably needs to be
a removable medium or a secondary disk.
2. sudo --preserve-env=DBUS_SESSION_BUS_ADDRESS,XDG_RUNTIME_DIR sh -c
'ubiquity gtk_ui'
3. In the ubiquity installer create a GPT partition on the target medium
(e.g. /dev/sdb) containing an EFI partition (e.g. /dev/sdb1) and a root
partition (e.g. /dev/sdb2), and set the Grub target ("boot disk") accordingly.
4. The installer will ask for confirmation, stating that the partition table
of both disks will change and that the two newly created partitions will be
formatted. In case of an existing swap partition on the primary disk, this
partition will also be formatted (which I consider another bug).
5. After the crash, you can notice that
a. the new system has been partially installed, as /target (e.g.
/dev/sdb2) is mounted and contains 329 MB
b. the EFI partition of the install medium or primary disk (e.g.
/dev/sda1) has been unmounted from /boot/efi and remounted to /target/boot/efi
c. the target EFI partition (e.g. /dev/sdb1) has been created and
formatted, but is unmounted and empty.
$ cat /target/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sdb2 during installation
UUID=76ecfd0f-dae5-4801-9db0-7d8bc8d20b8f / ext4
errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=A815-6B37 /boot/efi vfatumask=0077 0 1
# swap was on /dev/sda6 during installation
UUID=c2e0cb67-23de-4ab3-be19-4123e6229ade noneswapsw
0 0
$ sudo du -shx /target/* | sort -h
4,0K/target/home
4,0K/target/lib64
4,0K/target/media
4,0K/target/mnt
4,0K/target/opt
4,0K/target/proc
4,0K/target/srv
4,0K/target/sys
4,0K/target/tmp
4,0K/target/writable
12K /target/dev
12K /target/root
16K /target/lost+found
16K /target/meta
84K /target/snap
96K /target/run
3,8M/target/etc
4,1M/target/boot
9,7M/target/sbin
9,8M/target/var
14M /target/bin
48M /target/lib
240M/target/usr
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.11
ProcVersionSignature: Ubuntu 5.8.0-51.57~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr 30 00:34:13 2021
InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz root=UUID=E6BD-0CD8
file=/cdrom/preseed/ubuntu.seed maybe-ubiquity debian-installer/language=de
keyboard-configuration/layoutcode=de
iso-scan/filename=/ubuntu-18.10-desktop-amd64.iso boot=casper persistent
noprompt quiet splash --
InstallationDate: Installed on 2018-12-11 (870 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
SourcePackage: ubiquity
UpgradeStatus: Upgraded to focal on 2020-10-26 (185 days ago)
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu65
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.04
+ InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic
root=UUID=d58bb821-fce1-4730-802d-4afdcf512495 ro quiet splash vt.handoff=7
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: ubiquity 21.04.19
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
+ Tags: hirsute wayland-session oem-config
+ Uname: Linux 5.11.0-16-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1926672/+attachment/5494129/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926672
[Bug 1926672] Re: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition
It just says that the initial install of my system was done with 18.10. Distro release is Ubuntu 20.04. This is my desktop system, as I wanted to confirm that the error does not only happen when installing from a removable media to another removable media, but also when installing from disk to removable media. I know that ubiquity is not intended to run from a normal desktop system, but as I said this was only for testing after having experienced the issue on several installs. Additionally, I have just tested this with Ubuntu hirsute 21.04 (stable live iso), and I am experiencing the same issue (with ubiquity 21.04.19). I have also tested whether there is a difference if I boot into the installer directly from Grub, but it is just the same as booting into live mode first and then manually starting ubiquity. This seems somehow dangerous, as it may break a current EFI installation. The crash directory inside install-logs-2021-05-02.0 is empty, so I cannot send you a stacktrace. I took some bad fotos of the error (in German), in case this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926672 Title: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926672] [NEW] ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition
Public bug reported:
In focal 20.04.02 the ubiquity-gtk installer (20.04.15.11/focal-updates)
always crashes after the partition step.
Although this seems to be an old bug, I could not find a relevant bug
report so far.
I am having this issue when installing Ubuntu 20.04 to removable media
from an existing Ubuntu 20.04 system. I could reproduce the issue on a
PC in UEFI mode and on another one in BIOS mode. Before reporting this
bug, I tested the installer on both Live USB media and internal disks.
How to reproduce?
1. The install medium needs to be writable (i.e. no CD/DVD) and contain a
mounted EFI partition (e.g. /dev/sda1), while the target presumably needs to be
a removable medium or a secondary disk.
2. sudo --preserve-env=DBUS_SESSION_BUS_ADDRESS,XDG_RUNTIME_DIR sh -c 'ubiquity
gtk_ui'
3. In the ubiquity installer create a GPT partition on the target medium (e.g.
/dev/sdb) containing an EFI partition (e.g. /dev/sdb1) and a root partition
(e.g. /dev/sdb2), and set the Grub target ("boot disk") accordingly.
4. The installer will ask for confirmation, stating that the partition table of
both disks will change and that the two newly created partitions will be
formatted. In case of an existing swap partition on the primary disk, this
partition will also be formatted (which I consider another bug).
5. After the crash, you can notice that
a. the new system has been partially installed, as /target (e.g. /dev/sdb2)
is mounted and contains 329 MB
b. the EFI partition of the install medium or primary disk (e.g. /dev/sda1)
has been unmounted from /boot/efi and remounted to /target/boot/efi
c. the target EFI partition (e.g. /dev/sdb1) has been created and formatted,
but is unmounted and empty.
$ cat /target/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sdb2 during installation
UUID=76ecfd0f-dae5-4801-9db0-7d8bc8d20b8f / ext4
errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=A815-6B37 /boot/efi vfatumask=0077 0 1
# swap was on /dev/sda6 during installation
UUID=c2e0cb67-23de-4ab3-be19-4123e6229ade noneswapsw
0 0
$ sudo du -shx /target/* | sort -h
4,0K/target/home
4,0K/target/lib64
4,0K/target/media
4,0K/target/mnt
4,0K/target/opt
4,0K/target/proc
4,0K/target/srv
4,0K/target/sys
4,0K/target/tmp
4,0K/target/writable
12K /target/dev
12K /target/root
16K /target/lost+found
16K /target/meta
84K /target/snap
96K /target/run
3,8M/target/etc
4,1M/target/boot
9,7M/target/sbin
9,8M/target/var
14M /target/bin
48M /target/lib
240M/target/usr
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.11
ProcVersionSignature: Ubuntu 5.8.0-51.57~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr 30 00:34:13 2021
InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz root=UUID=E6BD-0CD8
file=/cdrom/preseed/ubuntu.seed maybe-ubiquity debian-installer/language=de
keyboard-configuration/layoutcode=de
iso-scan/filename=/ubuntu-18.10-desktop-amd64.iso boot=casper persistent
noprompt quiet splash --
InstallationDate: Installed on 2018-12-11 (870 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: ubiquity
UpgradeStatus: Upgraded to focal on 2020-10-26 (185 days ago)
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal ubiquity-18.10.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926672
Title:
ubiquity-gtk installer crashes in focal 20.04.02 after partitioning
due to existing EFI partition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926462] [NEW] Typo 'libreoffice-oopslash' in /usr/lib/libreoffice/program/oosplash
Public bug reported: Affected package: libreoffice-common (1:6.4.7-0ubuntu0.20.04.1, focal- updates) While investigating the reason for lot of aa messages flooding my kernel logs, I noticed a (supposed) typo in the file /usr/lib/libreoffice/program/oosplash at line 17. I guess 'libreoffice- oopslash' should be 'libreoffice-oopslash'. It seems that the issue has already been reported one and a half years ago: https://listarchives.libreoffice.org/global/users/2019/msg00812.html Fix: Edit /usr/lib/libreoffice/program/oosplash, systemctl reload-or- restart apparmor.service, aa-remove-unknown to remove libreoffice- oopslash aka :-O/ PS: My initial "issue" that is filling up my /var/log/kern.log persists, but this might be a misconfiguration on my side. :-) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.4.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-51.57~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 16:49:54 2021 InstallationDate: Installed on 2018-12-11 (869 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-10-26 (184 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926462 Title: Typo 'libreoffice-oopslash' in /usr/lib/libreoffice/program/oosplash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1926462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883345] Re: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
This is a bug in sicherboot. Unfortunately, it still exists with version 0.1.5 on Ubuntu "hirsute" 21.04. Creating a symlink seems to work fine, so this might be added to the sicherboot postinst. ln -s /proc/cmdline /etc/kernel/cmdline (uname -r: 5.11.0-16-generic) ** Changed in: sicherboot (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883345 Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sicherboot/+bug/1883345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922307] [NEW] package libaacs0 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libaacs0/changelog.Debian.gz« zu überschreiben, welches verschieden von and
Public bug reported: How to reproduce? First, we install libaacs0 for amd64. sudo apt install libaacs0:amd64 Now we realize that we need libaacs0 for wine, so we install libaacs0 for i386 which should remove the first package. sudo apt install libaacs0:i386 The installation fails as /usr/share/doc/libaacs0/changelog.Debian.gz from libaacs0:amd64 has not yet been deleted when libaacs0:i386 tries to write this file. Manually removing libaacs0:amd64 before installing libaacs0:i386 works as expected. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libaacs0 (not installed) ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 2 02:36:23 2021 ErrorMessage: Versuch, gemeinsam benutztes »/usr/share/doc/libaacs0/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libaacs0:i386 ist InstallationDate: Installed on 2018-12-11 (843 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: libaacs Title: package libaacs0 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libaacs0/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libaacs0:i386 ist UpgradeStatus: Upgraded to focal on 2020-10-26 (157 days ago) ** Affects: libaacs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922307 Title: package libaacs0 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libaacs0/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libaacs0:i386 ist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libaacs/+bug/1922307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
