Hi there, as far as I can tell, pinning docker to 20.x leads to build
failures for riscv64 artifacts, as the 20.x docker.io is not available
for that arch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
1. Description: Ubuntu 24.10
Release:24.10
2. xwayland:
Installed: 2:24.1.2-1ubuntu0.1
Candidate: 2:24.1.2-1ubuntu0.2
Version table:
2:24.1.2-1ubuntu0.2 500 (phased 0%)
500 http://us.archive.ubuntu.com/ubuntu oracular-updates/main amd64
Packages
*
This bug still exists in Oracular mid-January 2025.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064624
Title:
Warning: W:Unable to read /var/lib/ubuntu-advantage/apt-
esm/etc/apt/apt.conf.d/ -
Hi. I indeed followed the test plan, using livecd-rootfs version
2.765.54.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done-jammy
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi, I've verified the changes by building a riscv64 image from -proposed
and verified that the image builds successfully. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086455
Title:
manifes
Oh, nevermind, the changes are still in -proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086455
Title:
manifest not generated for ubuntu-cpc uefi hook in riscv64 when no
subarch present
T
@lool I think the changes have actually landed in -updates. Please
correct me if I'm wrong but I believe this bug can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086455
Title:
manifest
** Changed in: cloud-images
Status: In Progress => 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/2072929
Title:
Ubuntu cloud image partition numbering
To manage notifications ab
** Changed in: cloud-images
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/2080223
Title:
Ensure WSL instances do not rely on the Windows launcher by using the
ne
> Does the solution to this bug include making the SBOMs public @
https://cloud-images.ubuntu.com/ ?
Not exactly. The plan is for SBOMs to be available at the org level for
a variety of artifacts as part of the 25.04 cycle. So SBOMs for cloud
images would be gotten from the same place that e.g. SB
** Description changed:
[ Impact ]
- * Lack of manifest causes downstream builds to break during the
+ * Lack of manifest causes downstream builds to break during the
manifest copy commands in the qcow binary hook. This is causing jammy
riscv64 builds to fail.
- * proposed fix [1] i
Public bug reported:
[ Impact ]
* Lack of manifest causes downstream builds to break during the
manifest copy commands in the qcow binary hook. This is causing jammy
riscv64 builds to fail.
* proposed fix [1] is to check that $SUBARCH is nonzero in the if
branch that returns early.
[ Test Pla
I've confirmed on focal, jammy, noble, and oracular that enabling
-proposed and updating distro-info-data causes `distro-info` commands to
output correct info:
--devel and --latest: shows plucky
--fullname: shows Ubuntu 25.04 "Plucky Puffin"
--stable: shows oracular
--lts: shows noble
--series=plu
Public bug reported:
[ Impact ]
Several tools rely on the `distro-info` package to tell them which releases are
available.
This package just contains data, with no format changes.
[ Regression Potential ]
Minimal, as long as we are only adding new entries (we do this every
release).
[ Test Ca
Public bug reported:
Version 46.3.
In settings, there is a spaces per tab option. Changing this does not
affect the amount of spaces per tab within the file even after restart.
** Affects: gnome-text-editor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notif
Crash file since I could only attach 1 file to the last comment
** Attachment added: "crash.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063341/+attachment/5814898/+files/crash.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
the journal, notably line 63562 has the segfault:
Sep 09 12:53:53 cody-Precision-3660 kernel: gnome-shell[266460]: segfault at 0
ip 7354d2835241 sp 7ffdbb70c0d0 error 4 in
libwayland-server.so.0.20.0[7354d2833000+8000] likely on CPU 8 (core 16, socket
0)
I don't know the terms enou
I've tested this by running an oracular build on s390x with your ppa
package thrown in. The build succeeded, so it looks like the ppa package
is what we want.
Relevant portions from the build log:
```
After this operation, 747 MB of additional disk space will be used.
Get:1 http://ftpmaster.inter
> (But btw. why have you attached your Intel ProcCpuinfoMinimal.txt
here?)
I used ubuntu-bug to file the bug, and it collected that automatically.
It's irrelevant, I've removed it.
** Attachment removed: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/207236
Public bug reported:
This issue has already been identified and fixed in the (upstream?)
github repository:
https://github.com/ibm-s390-linux/s390-tools/commit/63ff07ba38dda99e2661a097d05266555c727a2e
The issue fixed by the revert linked above is causing Cloudware Oracular
download image builds t
After doing some deeper reading I've come across this bug via the
DisplayLink GitHub Repo.
As a developer, I recognize that this isn't really the responsiblity of
the Canonical Ltd. to hunt down issues that don't relate back to the
Core OS - to an extent - so it's not really THEIR fault that an
un
I have been encountering this issue for the past month on my newly
installed (1-2 months old) version of Ubuntu 20.04.2 LTS.
I finally got frustrated enough to dig in and find a solution and
arrived here from a stackexchange comment.
FYI is all - OP's solution seems to have fixed the issue for me
do not know how much more detailed i can really be. theres a host of
ACPI issues. the BIOS/EFI will not boot into menu. system tools do not
boot either. i need a break. been working on trying to pinpoint the
specific issue for over a week now (it only says installed 4 days ago
because the support f
** Package changed: ubuntu-release-upgrader (Ubuntu) => lubuntu-meta
(Ubuntu)
** Changed in: lubuntu-meta (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/193185
Public bug reported:
switched distributions after a series of problems with Ubuntu packages
continually breaking. Switched to Solus-Plasma. Didn't care for the ballo.file
filing system creating enormous file sizes nor the very limited capabilities of
eopkg pkg manager. So tried installing Lubun
This system is unfortunately walled off from the Internet. I am unable
to run apport collect from it. I have attached the apport collection to
the original submission.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a mem
Public bug reported:
Description:Ubuntu 20.04.2 LTS
Release:20.04
Kernel: 5.4.0-72-generic
Problem Description:
When rebooting the system, a bus fatal error is generated by the system
hardware pointing to the BCM57XX network card. Upon reboot the error is
cleared.
Dell notes this i
So I did look at those options, but disabling them did not provide the
experience I was looking for, and required me to do as much or more
manual switching of audio devices.
To be clear, I don't want to disable the functionality that these
options provide. I am happy with the audio switching to ho
Public bug reported:
Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for
development work. I run it on a Lenovo X1 Carbon 8th Generation
connected to dual monitors via a Lenovo dock. Both monitors are capable
of outputting sound via HDMI.
I use bluetooth headphones frequently w
Public bug reported:
"System problem detected" pops up at seemingly random times. Has been
appearing since approximately linux-headers-5.8.0-39 was installed
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-headers-5.8.0-45-generic 5.8.0-45.51~20.04.1
ProcVersionSignature: Ubuntu
Public bug reported:
Ubuntu "bootable" buildd vm images, if imported into lxd and booted in a
VM container, cannot produce an interactive bash session via, e.g. `lxd
exec bash`.
This appears to be a problem of the buildd image lacking grub settings
to produce console output on ttyS0. Lack of con
I've proposed an MP that lays down a systemd conf file in cloud images
that implements the workaround described in this bug's top comment. This
represents a temporary workaround for cloud images, and can be reverted
if/when it's no longer needed.
--
You received this bug notification because you
This bug is also affecting Hirsute cloud images. The workaround
mentioned in the comments does seem to alleviate the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910815
Title:
race on boot
** Description changed:
[Impact]
- * There are currently no manifests being produced for buildd tarballs
- in bionic and focal.
+ * There are currently no manifests being produced for buildd tarballs
+ in bionic, focal, and groovy.
- * Manifests _are_ being produced for the buildd tarba
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/397440
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/397441
--
You received this bug notification because you are a memb
Public bug reported:
[Impact]
* There are currently no manifests being produced for buildd tarballs
in bionic and focal.
* Manifests _are_ being produced for the buildd tarballs in Hirsute and
Xenial (the latter as part of recent longer-term work to produce
bootable buildd images in Xenial)
I've built xenial buildd using livecd-rootfs version 2.408.65 and
verified the lxd and rootfs tarballs are sized and structured as
expected, and that the .img boots in multipass. This confirms
verification done for xenial.
--
You received this bug notification because you are a member of Ubuntu
B
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863024
Title:
SRU: bootable b
*** This bug is a duplicate of bug 1912216 ***
https://bugs.launchpad.net/bugs/1912216
Public bug reported:
Continuously missing package virtualbox-dkms
6.1.10-dfsg-1~ubuntu1.20.04.1 failed to install/upgrade: installed
virtualbox-dkms package post-installation script subprocess returned
erro
The xenial changes for 2.408.61 are currently failing verification for
me. Depending on the value of the --image-format argument passed to the
livefs build, the build results in either a .img that boots (--image-
format ext4) or lxd/rootfs tarballs that work (--image-format none), but
not both in t
I've built the ubuntu-base/buildd project and verified that the
resulting .img boots in multipass.
Using the lxd tarball to do a build is still pending.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
All parts of case k) verified by repeating the steps described above
against -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888575
Title:
Split motd-news config into a new package
To man
Ok, I wasn't building from -proposed, I'll try again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888575
Title:
Split motd-news config into a new package
To manage notifications about this bug g
My initial guess at why this has failed is that the ubuntu-server
package appears to still depend on grub-legacy-ec2 [1].
[1] https://packages.ubuntu.com/xenial/ubuntu-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Also as to verification of k.i), I've verified that the "deployed"
server seed [1] matches the seed configuration in VCS linked in the last
comment.
[1] https://people.canonical.com/~ubuntu-
archive/seeds/ubuntu.xenial/server
--
You received this bug notification because you are a member of Ubun
My attempts to verify test case k) seem to indicate there is still a
problem somewhere.
I've verified
i) that grub-legacy-ec2 is no longer in the server seed [1]
iv) that the livecd.ubuntu-cpc.manifest contains grub-legacy-ec2 and
ubuntu-server.
However,
ii) the rootfs manifest has not retaine
Public bug reported:
Tried to upgrade to ubuntu 20 and received this error.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-440 440.100-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubunt
** Description changed:
[Impact]
The motd-news script is largely useless for desktop users, as they rarely
login via a text console. It makes more sense for server users.
We can use package dependencies to have the motd-news script enabled on
servers, but disabled on desktops, and still
Recently installed Arch Linux and I am no longer encountering this issue
at all.
Kernel version: 5.8.8
SystemD version: 246.4
BIOS version: 1.12.1
libinput version: 1.16.1-1
xf86-input-libinput version: 0.30.0-1
Not sure if there are any other relevant packages.
--
You received this bug notifi
Fair enough, but it literally says right above the check box.
Use proposed updates if you're willing to report bugs on any problems
that occur.
So something is wrong at least in terms of when you do move it into the
main repo.
But you also might want to remove that text if you don't want people
Public bug reported:
Hello just updated like I do most days on 20.10 and I got this
dependency issue. It looks like this package was just recently renamed
within the last few days maybe?
codyf86@Test-iT-Server:~$ sudo apt-get full-upgrade
Reading package lists... Done
Building dependency tree
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891061
Title:
SRU: Bootable buildd images boot vu
I've verified that this is fixed for Focal by:
* Building the livecd-rootfs 2.664.5 source package in a private ppa
* Building the focal buildd image with the cpc-buildd livefs, with the above
private-ppa as an extra archive
* Booting the resulting disk-linux-virtual.img in Multipass with libvirt
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/387163
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/387162
** Merge proposal linked:
https://code.launchpad.net/~cod
Public bug reported:
[Impact]
* Bootable buildd images are currently built from the -release pocket only,
leaving them vulnerable to issues fixed by -updates and/or -security.
* MP: #387164 [1] should be backported to ensure updated packages are used
when building the bootable buildd ima
Just commenting to say I have the same problem with Dell XPS 15 2-in-1
9575, BIOS version 1.12.1. The problem was indeed fixed with
blacklisting intel_vbtn. Using Fedora 32.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Confirmed on Multipass using the 20200702 focal release image. Also
captured a sample selection of virsh console output during the infinite
boot loop: https://paste.ubuntu.com/p/dqqgqryXNV/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Changed in: cloud-images
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885571
Title:
Can't set boot kernel in GRUB on focal image
To manage notifications about t
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/387162
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/387163
** Merge proposal linked:
https://code.launchpad.net/~cod
** Description changed:
- Placeholder: will update with SRU template
+ Pull in upstream [1] changes to bump this package version to the latest
+ release version (0.3.3) as required by upstream awscli [2].
+
+ [Impact]
+
+ * This bug is intended to work in tandem with bugs for awscli [3] and
+ p
Public bug reported:
Placeholder: will update with SRU template
** Affects: python-s3transfer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
Public bug reported:
Encountered while upgrading the Ubuntu APP from the Windows 10 store
from 18.04 TO 20.04 using sudo do-release-upgrade -d
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libc6:amd64 2.31-0ubuntu9
ProcVersionSignature: Microsoft 4.4.0-18362.476-Microsoft 4.4.35
Uname
** Description changed:
[Impact]
* the python-botocore package is out of date, and out of sync with
python3-botocore in debian [1], for all pockets except groovy-proposed.
* The various outdated versions in, e.g. xenial and bionic, leave out
lots of useful botocore functionality
Public bug reported:
i'm a noob. all i know is that ubuntu crashes during install
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.14
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Archit
** Description changed:
+ [Original Bug Description]
+
awscli is not kept up to date, and so new AWS features are not
available.
The AWS pip installation method is unaudited and unsigned, and is not a
production ready solution to the out-of-date problem.
The awscli package needs t
** Description changed:
[Impact]
- * the python-botocore package is out of date, and out of sync with
+ * the python-botocore package is out of date, and out of sync with
python3-botocore in debian [1], for all pockets except groovy-proposed.
- * The various outdated versions in, e.g
This bug affects all suites to some extent, excluding groovy-proposed,
and the package version is more outdated for the older supported
releases, e.g. xenial and bionic.
The versions in the archive for xenial and bionic, 1.11 and 1.14,
respectively, lack functionality applicable to newer AWS featu
** Also affects: focal (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: focal (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867673
Title:
awscli not kept up to d
Public bug reported:
[Impact]
* the python-botocore package is out of date, and out of sync with
python3-botocore in debian [1], for all pockets except groovy-proposed.
* The various outdated versions in, e.g. xenial and bionic, leave out
lots of useful botocore functionality.
* SRUing the
I probably also should have elaborated that this succeeded over multiple
consecutive reboots.
** Changed in: plymouth (Ubuntu Focal)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Hi, this appears to be fixed.
I re-enabled "quite splash" in my grub config, ran update-grub, and
rebooted. I got a black splash screen with white "Ubuntu" branding, and
a prompt to enter my FDE key. Boot went just fine.
Thanks!
--
You received this bug notification because you are a member of
Public bug reported:
I was installing Ubuntu 18.04.4. During the grub2 part of the
installation it failed with an error "grub installation failed grub-efi-
amd64-signed package failed to install into /target/." This installation
was on a 1 TB partition that previously had Antergos Linux installed.
Public bug reported:
On exactly every other reboot, a purple splash screen with the words
"Ubuntu 20.04" and four dots presents itself immediately on boot, and
prevents boot from progressing any further.
This splash screen occurs before the grub menu, and also before the
splash screen presented f
** Description changed:
We want to backport bootable enabling bootable buildd images to eoan,
bionic, and xenial.
- This is a placeholder description: will fill in SRU template soon.
[Impact]
* We don't have bootable buildd images, and we need them for Multipass.
[Test Case]
** Description changed:
We want to backport bootable enabling bootable buildd images to eoan,
bionic, and xenial.
This is a placeholder description: will fill in SRU template soon.
[Impact]
- * We don't have bootable buildd images, and we need them for Multipass.
+ * We don't ha
** Description changed:
We want to backport bootable enabling bootable buildd images to eoan,
bionic, and xenial.
This is a placeholder description: will fill in SRU template soon.
+
+ [Impact]
+
+ * We don't have bootable buildd images, and we need them for Multipass.
+
+ [Test Case]
Public bug reported:
We want to backport bootable enabling bootable buildd images to eoan,
bionic, and xenial.
This is a placeholder description: will fill in SRU template soon.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notifica
Public bug reported:
Ubuntu release: 20.04 Focal Fossa
Package version: gnome-shell 3.34.3-1ubuntu1, firefox 72.0.2+build1-0ubuntu1
Expected Behavior: new Terminal window would be foregrounded/focused on
creation via ctrl-alt-t when another terminal window not already focused
Actual Behavior: if
Public bug reported:
After completing release upgrade from Eoan to Focal as a devel release
without errors, subsequent updates via Software Updater show a window
that prompts the user for a Partial Upgrade, stating "Not all updates
can be installed.
The user can then either select Partial Upgrade
I want to call attention to this recent merge into master here:
https://github.com/ubuntu/yaru/pull/1578
This allows both light and dark shell themes to be selectable in gnome-
tweaks. I am not sure if this can be put into the 19.10 release.
--
You received this bug notification because you are
Thanks Rocko for the workaround in #11! Worked great!
I had the same light shell menus on a fresh install of the release
version of 19.10. I slightly modified your workaround and provided it in
an answer here: https://askubuntu.com/a/1182202/874660
--
You received this bug notification because y
This exact same issue has happened to me as well. I attempted to run a
livecd of Ubuntu 19.04 on a HP g72 notebook PC and came across this
exact error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/174
** Changed in: base-files (Ubuntu Xenial)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836236
Title:
9.4ubuntu4.9: Broken package because of missing "#"
** Changed in: base-files (Ubuntu Xenial)
Status: Fix Committed => New
** Changed in: base-files (Ubuntu Xenial)
Assignee: (unassigned) => shane cody perry (theinsanelunatic5934)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: base-files (Ubuntu Xenial)
Status: In Progress => Fix Released
** Changed in: base-files (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836
Public bug reported:
Iscsid restart fails when killed with a SIGTERM.
Conditions:
Iscsid restart policy set to "Always" via a .conf file in
/etc/systemd/system/iscsid.service.d/, with the contents:
[Service]
Restart=always
Steps to Reproduce:
1. Confirm iscsid is running, e.g.
$ ps aux | grep i
I am experiencing this same issue on Fedora 29 after installing the
Krita snap. It is using core18 also.
krita:
execl failed: No such file or directory
child exited with status 1
snap2.37.2-1.fc29
snapd 2.37.2-1.fc29
series 16
fedora 29
kernel 4.20.8-200.fc29.x86_64
core18 18
I am happy that we were able to get this resolved for you. I'm going to
go ahead and convert this report to a question, because this is more of
a support request than a bug in the release-upgrader. From here we can
mark the issue as "Solved" so that others with similar issues are able
to easily fin
Tony, if you look at the log files that got submitted with the bug
report, they can be found in the file named VarLogDistupgradeAptlog.txt.
Towards the bottom of the log file, all of the lines that started with
"broken" indicated packages that needed to be removed.
--
You received this bug notifi
Hi Tony, thank you for taking the time to submit this bug.
The log indicates several broken packages still on your system that appear to
be interfering with the upgrade. Try running 'sudo apt-get remove libblas3
libpython2.7-stdlib libopenblas-base python-scipy' and then attempting the
upgrade
Not sure if this is a bug or expected behavior for Nautilus now.
Can confirm that the middle-mouse button does open a file with a single click.
Both the left or middle mouse buttons can drag and drop a file by moving the
file, not copying the file. No option appears to select which method to use.
Verification done for Bionic and Xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805497
Title:
Snaps not i
** Tags removed: verification-failed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805497
Title:
Snaps not included in image manifests
To manage noti
Please note that for now this bug only applies to cloud images.
** Description changed:
[Impact]
- * Snaps are not included in manifests for those releases where snaps
- are pre-seeded (Xenial & Bionic)
+ * Snaps are not included in manifests for cloud images for those
+ releases where sna
Hi there. It looks like the fix for this bug for Cosmic is already in
cosmic-proposed: https://code.launchpad.net/~codyshepherd/livecd-rootfs
/uefi-manifests-cosmic/+merge/357833. Just waiting to be uploaded!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: livecd-rootfs (Ubuntu)
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/1805190
Title:
Image manifests for bionic and later are incorrect
To manage no
The package and version I tested: livecd-rootfs/xenial-proposed, version
2.408.41 xenial.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have also built and mounted a base (non-minimal) image from xenial-
proposed and confirmed no apparent regressions for the base image as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801134
T
** Description changed:
DNS was broken in Xenial minimal images under some circumstances due to
a 0-byte /etc/resolv.conf file.
[Test Case]
- Build Xenial Minimal Image
+ Build Xenial Minimal Image (along with private hook that actually installs
+ the resolvconf package).
Check /etc/res
I built a minimal image using the -proposed package and tested it by
running it on kvm. There do not appear to be any regressions (the image
boots fine and appears normal). A non-minimal build is in the works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1 - 100 of 2236 matches
Mail list logo
