** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: python-apt (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: python-apt (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for pointing that out. I was actually not quite sure. But it
sounded similar. The logs were almost the same. But in my case the
notebook actually doesn't get to sleep mode at all, although according
to the log it should be.
Thanks for the hint.
--
You received this bug notification
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
[Impact]
This is a major rewrite of ubuntu-advantage-client. This version introduces
an updated command line interface (UA Client) to simplify some interaction with
Ubuntu Advantage support offerings, and interacts with a new service backend
built specifically for
A 4.15 test kernel is available for validation with the backported
patches: https://kernel.ubuntu.com/~mhcerri/azure/lp1838796.1/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838796
Title:
TPM
2019-10-23 08:42:00,836 DEBUG url_downloadable:
http://archive.ubuntu.com/ubuntu/dists/eoan/Release
2019-10-23 08:42:00,836 DEBUG s='http' n='archive.ubuntu.com'
p='/ubuntu/dists/eoan/Release' q='' f=''
2019-10-23 08:42:10,963 DEBUG error from httplib: 'HTTP Error 503: Service
Unavailable'
Public bug reported:
On restart it sometimes happens that I get a message to the effect that my
graphics are operating in some kind of limited mode. An Xorg error is
mentioned. On OK I get a few options such as 'try starting in default mode' and
other options involving various possible tests,
Public bug reported:
problem occurred becauuse symlink /initrd.imgpointed to old disco
initrd, resolved by forcibly recreating it, for now...?
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: initramfs-tools 0.133ubuntu10
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849544
Title:
package initramfs-tools 0.133ubuntu10 failed to install/upgrade:
installed initramfs-tools
I guess https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/605
fixes this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694373
Title:
Gnome Shell app list scrolls too quickly with mouse
Regarding the kernel part of this LP ticket I plan to set it to Won't Fix - if
nobody objects.
And that's because we usually do not add performance improvements to stable
kernels, but have the hardware enablement (HWE) kernel instead.
I checked disco's git tree and "vfio-pci: Allow mapping MSIX
Just deleted global-messages-db.sqlite and now it looks like it works
fine. I hopê I didn't loose anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849542
Title:
Thunderbird empty after
Public bug reported:
If you want to install cron from a file you run crontab [filename].
Unfortunately the filename is truncated to 100 characters in the source
code set from #define MAX_FNAME 100
The MAX_FNAME should actually be set to PATH_MAX which is 4096
ProblemType: Bug
DistroRelease:
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/374620
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849322
Title:
Bogus serial string in subiquity
** Also affects: skimage (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/1849374
Title:
packages built for python3.8 with disabled tests, for a
This is going to be fixed on xenial once we fix #1828596 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/1655280
Title:
ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
Public bug reported:
HELP
Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched
Thunderbird and the interface is empty. No emails, no folders, no
calendar, I can't even open the "account settings" window.
This is a complete disaster. I need thunderbird for my work.
If I launch TB
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
My affected system is an ASUS Zenbook UX305FA with Secure Boot turned off.
Thanks for all the hints, especially comment #10. My workaround was easy:
1. In grub menu, choose an entry and edit it (key press: e).
2. Add rmmod tpm in a line before the first insmod.
3. Boot with the modified entry
Public bug reported:
Disk checked all right using the bootmenu option.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
** Description changed:
[Impact]
This is a major rewrite of ubuntu-advantage-client. This version introduces
an updated command line interface (UA Client) to simplify some interaction with
Ubuntu Advantage support offerings, and interacts with a new service backend
built specifically for
no need to rebase anything, just cherry-pick the patch on top of 5.3..
I've applied it on top of the eoan kernel and built it:
https://aaltoset.kapsi.fi/lp1826125
please test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
ubuntu shows pci bus error severity=corrected when shutting down
takes time for login page to pop up
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-31-generic
Ok, I'll fix this in the next batch of policy updates for snapd.
** Changed in: snapd (Ubuntu)
Importance: Undecided => Low
** Changed in: snapd (Ubuntu)
Status: New => Triaged
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Launchpad has imported 10 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=203877.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
[Impact]
This is a major rewrite of ubuntu-advantage-client. This version introduces
an updated command line interface (UA Client) to simplify some interaction with
Ubuntu Advantage support offerings, and interacts with a new service backend
built specifically for
Public bug reported:
Trying to install 19.10 on s390x LPAR using subiquity hangs on the
step/screen that comes AFTER "Configure Ubuntu Archive mirror" -
probably the partition screen.
I got the message:
"
Probing for devices to install to failed
Unfortunately probing for devices to install to
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
This is a known issue that always happens when the archive opens for a
new development series. It will be addressed shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849435
Title:
could not
** Description changed:
[Impact]
This is a major rewrite of ubuntu-advantage-client. This version introduces
an updated command line interface (UA Client) to simplify some interaction with
Ubuntu Advantage support offerings, and interacts with a new service backend
built specifically for
Yes, it is mounted:
ubuntu@bionicvm:~$ mount | grep Private
/home/ubuntu/.Private on /home/ubuntu/Private type ecryptfs
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=11d8701311f9dc77,ecryptfs_sig=4ca5cd476d88b7cd,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
--
You received
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Summary changed:
- trusty/linux-aws: -proposed tracker
+ trusty/linux-aws: 4.4.0-1057.61 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: New => Invalid
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Invalid
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Invalid
** Description changed:
This bug
Public bug reported:
Testing failed on:
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/snapd/20191010_150200_d4eee@/log.gz
These are the last messages from the log:
+ export SPREAD_CORE_CHANNEL=stable
+
Public bug reported:
Attempting to extract ISO to FAT32 partition for UEFI install which used
to work.
But get error that FAT32 does not support links.
Found these links:
fred@Bionic-Z170N:/media/fred/Ubuntu 20.04 LTS amd64$ find . -type l -ls
2761 0 lr-xr-xr-x 1 fred fred
Regardless, it's simply a hypothesis on my part that the fact that I
have configured Chinese input methods in the past may be the cause of
this problem. The Chinese keyboard setting is not active when this
problem manifests.
** Changed in: ibus (Ubuntu)
Status: Incomplete => New
--
You
Uploads pending in Eoan and Focal.
Bugs targeted per Eickmeyer's request.
** Changed in: carla (Ubuntu)
Status: New => 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/1849168
You can remove that property thus:
sudo zfs inherit org.zsys:bootfs-datasets
rpool/USERDATA/_
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849179
Title:
canmount property switches to noauto in
> There is a ~/.cache/ibus/compose folder with a suspicious cache file.
> Can you please rename that folder, relogin, and check if the issue is
> still present.
What is suspicious about the file?
I moved the directory aside, started ibus-daemon up again, and the
problem persists. The
** Summary changed:
- why does booting any livefs squashfs cause the kernel to complain about being
unable to read metadata
+ why does booting any livefs squashfs cause the kernel to complain about being
unable to read metadata‽
** Tags added: rls-ff-incoming
--
You received this bug
On a 19.04 system, I don't see the /boot/grub/x86_64-efi/tmp.mod file--
so added during the upgrade.
Speculation:
So, the problem might be related to signed versus unsigned kernels. The
earlier kernel was probably signed. The new kernels from the upgrade are
probably not
So the failure mode I ran into was running the upgrade to 19.10 after
upgrading all disco packages but before rebooting.
In that case it seems like the upgrader needs to refuse to run if the
system needs to be restarted?
--
You received this bug notification because you are a member of Ubuntu
Ok, that is a read on /home/ubuntu/.Private/. Is the encrypted home
mounted at the time of the denial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848919
Title:
[snap] Permission denied on
** Also affects: carla (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: carla (Ubuntu Eoan)
Status: New => Fix Committed
** Changed in: carla (Ubuntu)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849532
Title:
package gpsd 3.17-7 failed to install/upgrade: installed gpsd package
post-installation script
** Summary changed:
- why does booting any livefs squashfs has kernel complaining about unable to
read metadata something rather
+ why does booting any livefs squashfs cause the kernel to complain about being
unable to read metadata
--
You received this bug notification because you are a
And need casper in focal to migrate to support the "bebroken" keyword
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824407
Title:
why does booting any livefs squashfs cause the kernel to complain
I see there's one caveat, the autoinstall_all_kernels variable in
/etc/dkms/framework.conf can be set to build for all installed kernels,
not just the current and newest. But the default is to build only for
current and newest.
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
**
Modules should only be built at install time for the current and newest
kernels. So as long as you are up to date _and_ booted into a kernel
with the fix you should be able to upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kate (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kate in Ubuntu.
https://bugs.launchpad.net/bugs/1849455
This bug even renders Kate's --pid option dysfunctional, so there
seems to be no end-user workaround for this problem. Since the KDE devs
in the linked bug report above declined to do a "re-spin" and did indeed
"ship Kate like this", I'd be hugely grateful if the (K)Ubuntu devs
backported the
Public bug reported:
upgrade from 19.04 failed with these messsages (see log)
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: distcc 3.3.2-7
ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture:
Public bug reported:
Testing failed on:
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxd/20191010_151713_6f6f4@/log.gz
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza
(kleber-souza)
** Changed in: kernel-sru-workflow/prepare-package-lrm
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849531
Title:
package distcc 3.3.2-7 failed to install/upgrade: dependency problems
- leaving triggers
Public bug reported:
Description:Ubuntu 19.10
Release:19.10
gpsd:
Installé : 3.17-7
Candidat : 3.17-7
Table de version :
*** 3.17-7 500
500 http://fr.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
100 /var/lib/dpkg/status
Issue while upgrading from
Today on GitHub a ppc64el webhook was turned on for the systemd project. The
fuzzers (built with ASan) crashed there as soon as they started with something
like
```
757/758 fuzz-varlink:oss-fuzz-14708:address FAIL 0.02 s (exit status 1)
--- command ---
/usr/bin/env
python3-apt was already installed but I still have the same problem
corrado@corrado-p7-ff-1021:~$ apt policy python3-apt
python3-apt:
Installed: 1.9.0ubuntu1
Candidate: 1.9.0ubuntu1
Version table:
*** 1.9.0ubuntu1 500
500 http://it.archive.ubuntu.com/ubuntu focal/main amd64
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Incomplete => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => In Progress
** Description changed:
This bug will contain status and test results related to a kernel source
(or
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
Thank you, sorry for the noise. Will fix here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849342
Title:
Disco libvirt FTBS for the next SRU
To manage notifications about this bug go to:
Thanks for the clarification, that makes sense to me now. It doesn't
look like the patch handles CPU hotplugging though; a cpumask filled
with *only* offline CPUs can be passed as a parameter, or all of the
CPUs in the cpumask can be offlined after the setup is finished. This
isn't a problem with
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
This change was made by a bot.
** Changed in: linux (Ubuntu)
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/1849517
Title:
latest kernel problem 5.3
To manage
Public bug reported:
bmp-tag, when libsox-fmt-mp3 isn't installed, silently (wrongly) reports
and tags mp3s as 146bpm.
The fix is to install libsox-fmt-mp3, and unless the root bug is fixed
upstream, a sensible fix would be to have the package depend on that
library.
I found the fix here:
Oh, I'm on Disco, Ubuntu 19.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849527
Title:
Should depend on libsox-fmt-mp3
To manage notifications about this bug go to:
** Changed in: virtualbox (Ubuntu Bionic)
Status: New => In Progress
** Also affects: virtualbox-ext-pack (Ubuntu)
Importance: Undecided
Status: New
** Changed in: virtualbox (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: virtualbox-ext-pack (Ubuntu)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl
(connork)
** Summary changed:
- xenial/linux-azure-edge:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
Fixed with https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?id=aca99f48134f58c912d6a573ca1233ac601754ed.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of
the python3-apt binary should be installed...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849435
Title:
could not find a distribution template for Ubuntu/focal
To manage notifications about
Confirmed, and adding the mpris slot fixes the issue.
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Changed in: chromium-browser (Ubuntu)
Status: New =>
Klaus, that might be a separate issue. In my case the laptop really goes
into sleep (led blinks, screen off, fan off, no noticeable heat
production).
I found a related report on the kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=203877
** Bug watch added: Linux Kernel Bug Tracker
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
Hello Shih-Yuan, or anyone else affected,
Accepted nvidia-graphics-drivers-430 into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-430/430.50-0ubuntu0.18.04.2 in a few hours, and
then in the -proposed repository.
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
zsys is handling this (adduser will try to execute it and creates a
dataset, and if it can't, it fallbacks to traditional directory
creation.
zsys isn't installed by default on 19.10 but should be on 20.04 LTS, so
I encourage you to install and test it! Thanks :)
I'll have to mark the bug as
Public bug reported:
Seems to me that packaging virt-manager as a snap would allow for
delivering the most current version across supported Ubuntu releases.
Could we get virt-manager packaged as a snap?
Note that qemu (with virgil enabled) is already available as a snap.
See
Public bug reported:
Installed ubuntu 19.10 onto a zfs bpool/rpool.
Installed zsys.
Did a "zpool import" of my existing zfs pools.
Rebooted.
The previously imported zpools are not imported at boot!
I am currently using this hacky workaround:
Public bug reported:
Seems to me that packaging aqemu as a snap would allow for delivering
aqemu more easily across supported Ubuntu releases. Could we get aqemu
packaged as a snap?
Note that qemu (with virgil enabled) is already available as a snap.
See https://snapcraft.io/qemu-virgil
**
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.3)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
makedumpfile/1:1.6.5-1ubuntu1~18.04.3 (ppc64el)
Please visit the excuses page listed below and
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.3)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
makedumpfile/1:1.6.5-1ubuntu1~18.04.3 (ppc64el)
Please visit the excuses page listed below and
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.3)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
makedumpfile/1:1.6.5-1ubuntu1~18.04.3 (ppc64el)
Please visit the excuses page listed below and
Hello Alberto, or anyone else affected,
Accepted nvidia-graphics-drivers-430 into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-430/430.50-0ubuntu0.18.04.2 in a few hours, and
then in the -proposed repository.
Please
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.3)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
makedumpfile/1:1.6.5-1ubuntu1~18.04.3 (ppc64el)
Please visit the excuses page listed below and
I was fully updated in disco before I upgraded to 19.10.
I think the problem is that it's not good enough for the tip disco
kernel to be updated. One old kernel version is saved even after
autoremove, and if the user doesn't run autoremove then I think any
number of old kernels could be saved,
Public bug reported:
when i upgraded my system from 19.04 to 19.10 with latest kernel
5.3.0-19-generic everything works fine except when the system goes to sleep and
on wakeup the brighness goes to maximum even fresh install of ubuntu 19.10 has
the same problem .
The disco kernel was updated for this, but it looks like you were
running an older kernel which did not receive the update. If you reboot
into the newest kernel for disco you should not encounter this issue
when upgrading.
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
Full deinstallation of snapd didn't go through, error as described. A
restart and `sudo apt -f install` didn't show further issues.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: snapd (not installed)
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849517
Title:
latest kernel problem 5.3
To manage notifications about this bug go to:
I now have this exact same issue with KUbuntu 19.10.
Device Manager worked fine in KUbuntu 19.04 but then I upgraded to 19.10
(do-release-upgrade) and now get exactly the same hang of the kubuntu-
driver-manager
The command "ubuntu-drivers" seems to report info ok
but installing reports an issue
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
201 - 300 of 668 matches
Mail list logo
