I haven't seen any other occurrence of this error with latest release
and there is not enough informations in the logs to understand what
happened. I'll set it to incomplete.
@roberto could you please report a separate bug?
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Incomplete
*** This bug is a duplicate of bug 1874524 ***
https://bugs.launchpad.net/bugs/1874524
** This bug is no longer a duplicate of bug 1875084
zfs installation fails with : Failed to add #4 partition: Numerical result
out of range
** This bug has been marked a duplicate of bug 1874524
ZFS
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Triaged
** Summary changed:
- ZFS installation fails with; Failed to add #4 partition: Numerical result out
of range
+ ZFS installation fails with; Failed to add #4 partition: Numerical result out
of range - 2TB+ disk on MBR
--
*** This bug is a duplicate of bug 1874524 ***
https://bugs.launchpad.net/bugs/1874524
** This bug has been marked a duplicate of bug 1874524
ZFS installation fails with; Failed to add #4 partition: Numerical result
out of range
--
You received this bug notification because you are a
Public bug reported:
Focal daily 20200507 (started earlier)
Kernel is 5.4.0-30.34
Kernel crashes on boot in Qemu with:
[4.019922] RIP: 0010:ovl_open_realfile+0x4a/0x150 [overlay]
[4.022101] Code: 44 8b 6f 40 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0
49 8b 7e 28 41 81 cd 00 00 04 04
Public bug reported:
Preseed directory is missing from groovy images (checked on 20200507)
but the boot command line is still referring to it.
$ wget -O - -q
http://cdimage.ubuntu.com/daily-live/pending/groovy-desktop-amd64.list|grep -w
preseed
$
^ nothing. It should return the seeds
I'm closing this report. I added a card to
https://github.com/orgs/ubuntu/projects/1 for discussion and address
this issue.
** Changed in: zsys (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: ubiquity (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943844
Title:
No welcoming message if install chosen in gfxboot and no network
To
Thanks for your report.
It seems that installation failed because some partitions were already
mounted
May 4 14:11:11 ubuntu ubiquity: This disk is currently in use - repartitioning
is probably a bad idea.
May 4 14:11:11 ubuntu ubiquity: Umount all file systems, and swapoff all swap
@didrocks, that was my first assumption too but this worries me:
May 01 10:53:13 mcp systemd[1]: boot.mount: Directory /boot to mount over is
not empty, mounting anyway.
May 01 10:53:13 mcp systemd[1]: Mounting /boot...
May 01 10:53:13 mcp systemd[1]: Mounting /home/alan...
May 01 10:53:13 mcp
Could you please add the journal from the date when this happened?
You can export the journal with journalctl.
journalctl --list-boots will give you the list of boot number and timestamps
journalctl -b ID will print the content of the journal for a given boot.
Extract to a file the journal for
Thanks for your report, from the logs, bpool counldn't be imported and
is missing.
** Changed in: zsys (Ubuntu)
Status: New => Confirmed
** Changed in: zsys (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks for your report. It's something we discussed yesterday with
Didier and we have to revisit the way we handle bpool ( would a bigger
pool be enough for example or would it just push the wall further).
Could you please run
apport-collect 1876334
It'll collect useful information to help us
For the snap, this is because data_dir in distro_info is hardcoded to
/usr/share/distro_info/ whichi corresponds to the version included in
core18 not the version that ships with the snap itself.
Version 20200427 (1754) of core18 contains the right data file with
information about groovy.
Could you confirm that you booted in BIOS mode when the error occurred?
Can you try the installation again in UEFI and tell is you reproduce the issue?
** Changed in: ubiquity (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Thanks for the logs
The error happens in grub-mkconfig. So much earlier than any zfs
specific grub script.
One of the main issue on your system that could lead to this error is
the corrupted rpool.
NAME STATE READ WRITE CKSUM
rpoolDEGRADED 0 0 0
@Donald, could you please file a separate report since it's a different
issue.
You can report it from the live session on the system you're
experiencing this issue with:
ubuntu-bug ubiquity
It'll collect useful information to help us understand the problem.
Thanks.
--
You received this bug
** Changed in: zsys (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874304
Title:
grub-probe fails with failed to get canonical path of rpool with ZFS
My guess is that the machine has been booted in Legacy mode, in this
mode disks up to 2TB are supported but on your setup sda is 8TB hence
the numerical result out of range. To be confirmed.
** Changed in: ubiquity (Ubuntu)
Importance: Medium => High
--
You received this bug notification
Thanks for your report.
Apparently sda has an AHDI partition which could lead to a shift in the
calculation of the partition indexes we use for ZFS.
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Triaged
--
You
** Changed in: ubiquity (Ubuntu)
Status: New => Triaged
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875045
Title:
Could you also run the following command:
$ apport-collect 1874304
It'll attach logs that'll help us troubleshoot this issue.
Thanks.
** Package changed: grub2 (Ubuntu) => zsys (Ubuntu)
** Changed in: zsys (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
In order to understand which call fails, could you edit the file
/usr/sbin/grub-mkconfig and add a 'set -x' just under the 'set -e' as
follow:
#! /bin/sh
set -e
set -x
# Generate grub.cfg by inspecting /boot contents.
[...]
Then run update-grub
** Tags added: zfs
** Summary changed:
- Crashed on a clean install after selecting timezone
+ zfs installation fails with : Failed to add #4 partition: Numerical result
out of range
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
** Changed in: ubiquity (Ubuntu)
*** This bug is a duplicate of bug 1875084 ***
https://bugs.launchpad.net/bugs/1875084
** This bug has been marked a duplicate of bug 1875084
Crashed on a clean install after selecting timezone
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1069133 ***
https://bugs.launchpad.net/bugs/1069133
** This bug has been marked a duplicate of bug 1069133
Get upgrade error 12.04 - 12.10 "Could not determine upgrade" - xorg from ppa
--
You received this bug notification because you are a member of
** Tags added: zfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875045
Title:
Ubiquity 20.04 interferes with existing ZFS pools, making them
"disappear"
To manage notifications about this bug
*** This bug is a duplicate of bug 1874945 ***
https://bugs.launchpad.net/bugs/1874945
** This bug has been marked a duplicate of bug 1874945
text input is not available at all when I am initializing an install of
ubuntu
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1874945 ***
https://bugs.launchpad.net/bugs/1874945
** This bug has been marked a duplicate of bug 1874945
text input is not available at all when I am initializing an install of
ubuntu
--
You received this bug notification because you are a member of
** Summary changed:
- python crash during "do-release-upgrade -d"
+ do-release-upgrade crashes with UnicodeDecodeError in DistUpgradeViewText.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874702
Thanks for your report.
images has been renamed to legacy-images and documentation needs fixing.
** Changed in: installation-guide (Ubuntu)
Importance: Undecided => High
** Changed in: installation-guide (Ubuntu)
Status: New => Triaged
--
You received this bug notification because
I cannot reproduce it here but it could be due to a mismatch of the
locale between the session (uk_UA.UTF8) and the upgrader (en_US.UTF8)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874702
Title:
** Description changed:
- If you have been redirected to this page, it means that your
- installation of Ubuntu or a flavour failed.
+
+ If you have been redirected to this page, it means that your installation of
Ubuntu or a flavour failed.
If you search in the log file /var/log/syslog,
Public bug reported:
The filesystem integrity is now checked on boot of the installation
medium. The user has the possibility to skip it or it may fail in which
case a message is displayed briefly during the boot.
Ubiquity should show this information on the first page of the installer to the
** Description changed:
The original bug report was submitted to https://discourse.ubuntu.com/t
/error-upgrading-to-development-version-of-20-04/15522. Moving it here.
+ Crash from main.log:
+ Traceback (most recent call last):
+ File "/tmp/ubuntu-release-upgrader-clogvkrp/focal", line
*** This bug is a duplicate of bug 1871268 ***
https://bugs.launchpad.net/bugs/1871268
** This bug has been marked a duplicate of bug 1871268
Installation fails with Could not configure 'libc6:i386'. , E:Could not
perform immediate configuration on 'libgcc-s1:i386'
--
You received this
*** This bug is a duplicate of bug 1871268 ***
https://bugs.launchpad.net/bugs/1871268
** This bug has been marked a duplicate of bug 1871268
Installation fails with Could not configure 'libc6:i386'. , E:Could not
perform immediate configuration on 'libgcc-s1:i386'
--
You received this
** Description changed:
If you have been redirected to this page, it means that your
installation of Ubuntu or a flavour failed.
- If you look in the log file /var/log/syslog, you'll see messages like
- the above:
+ If you search in the log file /var/log/syslog, you'll see messages like
+
Public bug reported:
If you have been redirected to this page, it means that your
installation of Ubuntu or a flavour failed.
If you look in the log file /var/log/syslog, you'll see messages like
the above:
Apr 24 00:01:40 ubuntu kernel: [ 329.409695] SQUASHFS error: zlib
decompression
Thanks for your report.
Integrity check of the installation medium failed. Please try with
another usb stick.
Do not hesitate to file any bug you may find.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874550
Title:
Apr 24 04:33:47 ubuntu ubiquity: Setting up shim-signed
(1.40.3+15+1533136590.3beb971-0ubuntu1) ...
Apr 24 04:33:48 ubuntu grub-installer: info: Installing grub on '/dev/sda'
Apr 24 04:33:48 ubuntu grub-installer: info: grub-install does not support
--no-floppy
Apr 24 04:33:48 ubuntu
*** This bug is a duplicate of bug 1874571 ***
https://bugs.launchpad.net/bugs/1874571
** This bug has been marked a duplicate of bug 1874571
I/O error installing 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for your report.
According to 'CasperMD5CheckResult: fail' your installation media is
corrupted. Please try to recreate it or use another stick.
Do not hesitate to file any bug you may find.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
** Tags added: zfs
** Summary changed:
- Installation crashes
+ ZFS installation fails with Failed to add #4 partition: Numerical result out
of range
** Summary changed:
- ZFS installation fails with Failed to add #4 partition:
Thanks for your report.
You apparently skipped the integrity check and the installation media is
corrupted. Please try with another USB stick or recreate it.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1069133 ***
https://bugs.launchpad.net/bugs/1069133
** This bug has been marked a duplicate of bug 1069133
Get upgrade error 12.04 - 12.10 "Could not determine upgrade" - xorg from ppa
--
You received this bug notification because you are a member of
* Changed in: ubuntu-manual-tests
Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874302
Title:
ZFS installation never prompts for securit
** Also affects: thunar (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-manual-tests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836235
Title:
ubuntu-bug
Thanks for your report. With which software are you experiencing this
issue?
** Project changed: ubuntu-manual-tests => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860911
Title:
Restart
Thanks for you report.
It works fine on final build of Ubuntu Desktop 20.04LTS. Is it still an
issue for you?
** Project changed: ubuntu-manual-tests => ubiquity (Ubuntu)
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
** Changed in: ubiquity (Ubuntu)
Importance: Undecided
Thanks for your report. This is fixed in latest image.
** Project changed: ubuntu-manual-tests => casper (Ubuntu)
** Changed in: casper (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: calamares (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-manual-tests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871880
Title:
"EFI system
Public bug reported:
Test Case:
1. Fresh Bionic installation from 18.04.4 + all updates applied
2. Run: update-manager -d
3. Proceed with the upgrade.
Actual Result:
Everything goes well but the stage "Searching for obsolete software" takes a
very long time.
ProblemType: Bug
DistroRelease:
** Changed in: ubiquity (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786992
Title:
Existing bios mode Windows install left unbootable after installing in
Page rendered by Chrome.
** Attachment added: "rst_chrome.png"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1874068/+attachment/5357553/+files/rst_chrome.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On the RST page, clicking on the link help.ubuntu.com/rst does nothing
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.14
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl
Public bug reported:
help.ubuntu.com/rst is linked from the Ubuntu installer when it detects an
RST-enabled drive.
This page doesn't look like an Ubuntu page and it displays badly on a phone
(which is the recommended device on the installer page to flash the QR code)
** Affects: ubuntu-docs
Page rendered on a phone.
** Attachment added: "rst_phone.png"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1874068/+attachment/5357554/+files/rst_phone.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Test Case:
1. On a machine with 2 disk 1 spinning disk and 1 nvme disk, enable RST
2. Start ubiquity and proceed zith the installation to the partitioning step
Expected result
Despite RST being enabled, user should be able to install on the non-RST disk
Actual result
** Changed in: partman-efi (Ubuntu)
Status: New => Confirmed
** Changed in: partman-efi (Ubuntu)
Importance: Undecided => Low
** Changed in: partman-efi (Ubuntu)
Milestone: None => ubuntu-20.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Package changed: live-build (Ubuntu) => ubuntu-qa-website
** Changed in: ubuntu-qa-website
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874013
Title:
Check
it's been reported to errors.u.c
(https://errors.ubuntu.com/oops/7a122fe4-82ff-11ea-abcd-fa163e983629)
but it couldn't be retraced
** Also affects: libgtk3-perl (Ubuntu Focal)
Importance: Critical
Status: New
** Changed in: libgtk3-perl (Ubuntu Focal)
Status: New => Confirmed
** Changed in: ubiquity (Ubuntu Focal)
Milestone: ubuntu-20.04 => ubuntu-20.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860957
Title:
ZFS installation crash when ESP already exists
To
@apt-ghetto, an ESP is always created in BIOS in case the boot is
switched to UEFI. A typical use case on many systems, you boot an image
and perform the installation in BIOS mode, and reboot in UEFI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On ZFS setup, boot/grub/ uses the EFI system partition to store GRUB
configuration so, it's always readable by grub on boot. This partition
is of type vfat and this filesystem type doesn't support symbolic links.
The problem with lubuntu grub theme is that a file used for the theme is
a symbolic
** Summary changed:
- package lubuntu-grub-theme (not installed) failed to install/upgrade: error
creating symbolic link
'./boot/grub/themes/lubuntu-grub-theme/icons/ubuntu.png': Operation not
permitted
+ package lubuntu-grub-theme (not installed) failed to install/upgrade: error
creating
** Changed in: ubiquity (Ubuntu Focal)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860957
Title:
ZFS installation crash when ESP already exists
To manage
*** This bug is a duplicate of bug 1862553 ***
https://bugs.launchpad.net/bugs/1862553
** This bug has been marked a duplicate of bug 1862553
gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
--
You received this bug notification because you are a member of Ubuntu
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
** Description changed:
+ Test Case
+ 1. On a fresh installation of Ubuntu Desktop Focal run software-properties-gtk
+ 2. Go to the tab
** Changed in: ubiquity (Ubuntu)
Status: New => Triaged
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Tags added: zfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for your report.
According to the log, there is a general memory fault on your system
Apr 16 15:22:45 ubuntu kernel: [ 603.251691] Code: 8b 44 24 08 4c 8b 40 08 41
80 38 00 75 18 48 8b 05 fc a6 01 00 4c 8b 00 48 8d 05 84 21 01 00 4d 85 c0 4c
0f 44 c0 48 8b 45 68 <48> 8b 40 08 48 89 04
** Changed in: ubiquity (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856422
Title:
always call mokutil with --timeout -1 when enrolling dkms keys
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
** Changed in: ubiquity (Ubuntu)
Milestone: None => ubuntu-20.04
** Also affects: ubiquity (Ubuntu Focal)
Importance: High
Status: Confirmed
**
** Merge proposal linked:
https://code.launchpad.net/~mwhudson/ubiquity/+git/ubiquity/+merge/382150
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824195
Title:
Ubiquity offers network-required
Thanks for following up. I'm closing this bug then according to your
latest comment.
Don't hesitate to report any bug you may find.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for your report.
could you please explain what and how installation failed? There is
nothing in the logs that indicates a failure.
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1872077 ***
https://bugs.launchpad.net/bugs/1872077
** This bug has been marked a duplicate of bug 1872077
package grub-efi-amd64-signed 1.140+2.04-1ubuntu24 failed to install/upgrade
with mount: /var/lib/grub/esp: special device /, does not exist
--
*** This bug is a duplicate of bug 1872077 ***
https://bugs.launchpad.net/bugs/1872077
** This bug has been marked a duplicate of bug 1872077
package grub-efi-amd64-signed 1.140+2.04-1ubuntu24 failed to install/upgrade
with mount: /var/lib/grub/esp: special device /, does not exist
--
** Summary changed:
- package grub-efi-amd64-signed 1.140+2.04-1ubuntu24 failed to install/upgrade:
installed grub-efi-amd64-signed package post-installation script subprocess
returned error exit status 32
+ package grub-efi-amd64-signed 1.140+2.04-1ubuntu24 failed to install/upgrade
with
*** This bug is a duplicate of bug 1872077 ***
https://bugs.launchpad.net/bugs/1872077
** This bug has been marked a duplicate of bug 1872077
package grub-efi-amd64-signed 1.140+2.04-1ubuntu24 failed to install/upgrade
with mount: /var/lib/grub/esp: special device /, does not exist
--
*** This bug is a duplicate of bug 1871963 ***
https://bugs.launchpad.net/bugs/1871963
** This bug has been marked a duplicate of bug 1871963
dpkg fails to install grub-efi-amd64 signed and shim-signed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
*** This bug is a duplicate of bug 1871963 ***
https://bugs.launchpad.net/bugs/1871963
** This bug has been marked a duplicate of bug 1871963
dpkg fails to install grub-efi-amd64 signed and shim-signed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
*** This bug is a duplicate of bug 1871963 ***
https://bugs.launchpad.net/bugs/1871963
** This bug has been marked a duplicate of bug 1871963
dpkg fails to install grub-efi-amd64 signed and shim-signed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks for your report.
I believe this is fixed by
grub2-signed (1.140) focal; urgency=medium
* Fix postinst typpo.
** Changed in: grub-installer (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 1745345 ***
https://bugs.launchpad.net/bugs/1745345
/usr/lib/gdm3/gdm-x-session[3073]: Xorg:
../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion
`key->initialized' failed.
/usr/lib/gdm3/gdm-x-session[3073]: (EE)
*** This bug is a duplicate of bug 1745345 ***
https://bugs.launchpad.net/bugs/1745345
Public bug reported:
Broken image 20200406
Test Case:
1. Install Ubuntu Desktop in Qemu
2. Reboot and login
Actual result:
User login and is back to GDM.
There is an xorg crash in the journal
*** This bug is a duplicate of bug 1851955 ***
https://bugs.launchpad.net/bugs/1851955
** Summary changed:
- grab-efi-amd64-signed package failed to install
+ grab-efi-amd64-signed package failed to install: failed to register the EFI
boot entry: Invalid argument
--
You received this bug
** Summary changed:
- package grub-efi-amd64-signed 1.138+2.04-1ubuntu23 failed to install/upgrade:
installed grub-efi-amd64-signed package post-installation script subprocess
returned error exit status 1
+ package grub-efi-amd64-signed 1.138+2.04-1ubuntu23 failed to install/upgrade:
error:
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871202
Title:
dpkg-deb crashed with SIGSEGV
To manage notifications about this bug go to:
** Changed in: zsys (Ubuntu)
Status: New => Triaged
** Changed in: zsys (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870057
Title:
Ensure we
** Changed in: zsys (Ubuntu)
Status: New => Triaged
** Changed in: zsys (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870058
Title:
Collect
** Description changed:
- Before finishing installation the installer shows the error
+ 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
*** This bug is a duplicate of bug 1871268 ***
https://bugs.launchpad.net/bugs/1871268
** This bug has been marked a duplicate of bug 1871268
Installation fails with Could not configure 'libc6:i386'. , E:Could not
perform immediate configuration on 'libgcc-s1:i386'
--
You received this
Thanks for the logs.
The curly brace error should be fixed now. Now we must understand why it
doesn't find the kernels.
- Could you please save /etc/grub.d/10_linux_zfs somewhere outside of
/etc/grub.d/
- Replace /etc/grub.d/10_linux_zfs by the file in attachment. It adds set -x to
watch its
There is nothing to do on zsys's side. mount points are generated by the zfs
generator and mount order is set by systemd. apparmor must wait until all its
requirements are met to start which is what Jamie's fix does.
Closing zsys task.
** Changed in: zsys (Ubuntu Focal)
Importance: Critical
Apr 6 18:21:20 ubuntu ubiquity: Unpacking grub-common (2.04-1ubuntu23) over
(2.04-1ubuntu22) ...
Apr 6 18:21:20 ubuntu kernel: [ 649.865765] dpkg-deb[40276]: segfault at 9392
ip 7fd4b0b383c5 sp 7ffe78c98300 error 6 in
liblzma.so.5.2.4[7fd4b0b26000+17000]
Apr 6 18:21:20 ubuntu
** Summary changed:
- Clean Install first time
+ Installation fails with Could not configure 'libc6:i386'. , E:Could not
perform immediate configuration on 'libgcc-s1:i386'
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Importance:
This error is caused by a segfault of dpkg. This is the only occurrence
of this bug I found. Could you please run a memory test on your system
and try the installation again.
If it happens again, please check if there is a crash file in /var/crash/ and
upload it to launchpad with the command:
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Critical
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
401 - 500 of 32050 matches
Mail list logo
