Colin, thanks for sponsoring and additional testing!
Is this ZFS regression test suite available to other people?
It sounds great for future work with ZFS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Kernel deb testing completes, no regressions found. Ready for Updates.
Results here: https://trello.com/c/46BHK5zc/128-disco-linux-
image-500-25-generic-500-2526
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Fix Released
--
You received this bug
OK. recent update is this, i re-installed 18.04 and when i first booted
after installation desktop wallpaper was corrupted again. then i changed
desktop wallpaper and there was no corruption. i installed mesa drivers,
some codecs and rebooted again. then same thing happened that desktop
wallpaper
[BIONIC VERIFICATION DONE]
It has been brought to my attention the following by an impacted user:
"
Thanks for getting a fix prepared so quickly.
I appreciate that you have to follow your SRU process; I'm happy to use
the resource-agent package in the proposed repo in the meantime.
Our testing
You say "But I'm getting tired of this after years of doing it.". Does
this mean that you are suffering this bug already with older versions of
Ubuntu?
Yes, that is correct. It is happening for 2 years now, if I'm not
mistaken.
--
You received this bug notification because you are a member of
screen flickering and login screen corruption problem with docking
station and external monitor still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839353
Title:
Login screen and desktop
/var/log/syslog seems to contain debug information of network-manager, although
I was not successful:
With this command:
sudo /usr/lib/NetworkManager/debug-helper.py --nm debug
I followed these instructions:
https://wiki.ubuntu.com/DebuggingNetworkManager#Getting_NetworkManager_debug_logs
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #824
https://gitlab.gnome.org/GNOME/nautilus/issues/824
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/issues/824
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Hello,
sorry for the late reply. It hasn't done it again until today.
I went on lunch, I come back, my system is unresponsive. ThinkPad light
on no screen no ability to go to a tty. (ctl f2)
We ssh to the laptop and it shows as offline. And I know the IP is 100%
correct.
I have made a
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1030
https://gitlab.gnome.org/GNOME/nautilus/issues/1030
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/issues/1030
Importance: Unknown
Status: Unknown
** Changed in: nautilus (Ubuntu)
It has been fixed upstream now
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #788
https://gitlab.gnome.org/GNOME/nautilus/issues/788
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/issues/788
Importance: Unknown
Status: Unknown
** Changed in:
Thank you for your bug report, could you provide some details?
- what Ubuntu/nautilus version are you using?
- what sort of performance improvement are you speaking about (and how slow is
it by default for you/with what content)
- could you maybe also report it upstream on
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => 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/1784665
Title:
bcache: bch_allocator_thread(): hung task timeout
To
This bug was fixed upstream in version 22.18 [1], and in xenial we
already have version 22.21. So this bug is already fixed in the
supported releases.
[1] https://sourceforge.net/p/psmisc/code/ci/master/tree/ChangeLog
** Changed in: psmisc (Ubuntu)
Status: Confirmed => Fix Released
--
** Changed in: ubuntu-z-systems
Status: In Progress => 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/1836860
Title:
[18.04 FEAT] Enhanced CPU-MF hardware counters - kernel part
Reviewing the package in your PPA I do have a few comments that should
be addressed.
1) It looks like the standards version has been downgraded. If being modified
at all it should be bumped up to match standards version in Eoan. This should
also be mentioned in debian/changelog
2) VCS-Git and
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => 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 bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable
Public bug reported:
Each time you travel to new location, e.g.
Home --> Documents
you can improve performance if you open new window
and go to recent files (file history) and close
it (I use Ctrl W shortcut).
Performance change is left while you
stay in the location if you travel
to a new
This has been released:
https://launchpad.net/ubuntu/+source/ibus-avro/1.1-0ubuntu1
Thanks Mattia and Ćukasz for your constructive advice in the process!
** Changed in: ubuntu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Please have a look at
https://wiki.ubuntu.com/DebuggingNetworkManager
and supply us with debug logs of NetworkManager and wpasupplicant,
You say "But I'm getting tired of this after years of doing it.". Does
this mean that you are suffering this bug already with older versions of
Ubuntu?
**
Sorry, I don't have per-package upload rights to dptfxtract, you need to
ask a MOTU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838590
Title:
Update thermald to 1.9 release
To manage
dptfxtract 1.4.2-0ubuntu1 uploaded to
https://launchpad.net/~anthonywong/+archive/ubuntu/for-review/+packages for
review.
Colin, could you help sponsor this upload?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
dptfxtract 1.4.2-0ubuntu1 uploaded to my PPA for review.
Colin, could you help sponsor this upload?
** Changed in: dptfxtract (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934069
for Ubuntu are ppc64el and s390x
** Affects: sigil (Ubuntu)
Importance: Undecided
Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
Status: New
** Description changed:
Public bug reported:
grub installation failed
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CasperVersion:
** Changed in: linux-aws (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux-aws (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member
and now we have broken bionic cosmic and disco...
** Also affects: imagemagick (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: imagemagick (Ubuntu Eoan)
Importance: Critical
Assignee: Marc Deslauriers (mdeslaur)
Status: Confirmed
** Also affects:
Thanks Mauricio, I've sponsored this package, and sent the kernel
related changes to the kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-August/102938.html
I also sanity checked the code with the ubuntu kernel team ZFS
regression tests and they all pass successfully.
** Description changed:
This is constant struggle for me, it seems that in the initial days
after installation of Ubuntu 19.10 this problem of Wifi stopping to work
after wake up does not happen. I'm sure, I reinstalled Ubuntu many
times, the issue still persist.
-
- Breaking of Wifi
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
** Tags removed: wily
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577654
Title:
PCI/internal sound card not detected E7470
To manage notifications about this bug go to:
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
** Also affects: linux-aws (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Tags added: sru-20190722 ubuntu-stress-smoke-test
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
This is constant struggle for me, it seems that in the initial days
after installation of Ubuntu 19.10 this problem of Wifi stopping to work
after wake up does not happen. I'm sure, I reinstalled Ubuntu many
times, the issue still persist.
Breaking of Wifi after computer
** Tags added: sru-20190722 ubuntu-qrt-apparmor
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834192
Title:
apparmor mult_mount regression test fails in eoan
To manage
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
*** This bug is a duplicate of bug 1794053 ***
https://bugs.launchpad.net/bugs/1794053
I fixed this in 1.7.0, but forgot about this bug and tracked it in bug
1794053, so marking this as a duplicate.
** Changed in: apt (Ubuntu)
Status: Triaged => Fix Released
** This bug has been
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
** Tags removed: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533343
Title:
No sound from internal speakers after boot with connected headphones
To manage notifications about this bug go
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
I was incorrect, it's actually a racy read on /proc/bus/pci/:00/00.0
that's causing a hang:
sudo cat /proc/bus/pci/\:00/00.0
..takes a few seconds.. with stress-ng we have a multi-threaded
open/read/close on this file with random read sizes, this seems to cause
the machine to hang and
** Also affects: ubuntu-kernel-tests
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/1834192
Title:
apparmor mult_mount regression test fails in eoan
To
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
** Tags removed: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523100
Title:
Alsa not detecting internal microphone [ALC255] (Realtek)
To manage notifications about this bug go to:
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
** 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 --
One obvious downside of the Debian approach is the size occupied by the
extension when installed unpacked. With all available language packs,
/usr/share/lightning occupies 24MB, versus 4.8MB for the corresponding
zipped xpi.
--
You received this bug notification because you are a member of
** 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
looks like crmsh has a similar issue, I'm fixing it!
G.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837091
Title:
sbd autopkgtest regresion
To manage notifications about this bug go to:
** Description changed:
[Impact]
APT releases the locks in the same order it acquires them, rather than
reverse order. Given that we have no waiting for locks, this is not _super_
problematic, but it might be wrong: You'd get a lock failure on dpkg's lock,
rather than lock-frontend.
btusb.enable_autosuspend=0 is a magic! Yay!!!
Later I will try to permanent set it.
P.S. Still wondering why Kernel (or linux-firmware?) upgrade bring this
issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
201 - 300 of 365 matches
Mail list logo