Fixed that for two more patches for IceLake, but the resulting tree
fails to enter deeper state than PC3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848978
Title:
CML: perf enabling for core
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
/var/log/cups/error log repeatedly contains things like:
Session setup failed: NT_STATUS_LOGON_FAILURE
SMB connection failed!
and
Unable to connect to CIFS host: NT_STATUS_IO_TIMEOUT. Will retry in 60
seconds...
Unable to connect to CIFS host after (tried 3 times)
--
You received this bug
@UCA-Team
I'm also subscribing the UCA Team as I personally only know about [1] which
allows you to use named CPU models.
I expect there already is some general pattern established to handle e.g. the
older MDS which if you look at "Configuration as a Hypervisor" at [2] also
needs such
** Tags added: oem-priority originate-from-1851774 sutton
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853246
Title:
[SRU][B/OEM-B/OEM-OSP1/D] Enable new touchpads which are not in
current
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
** 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:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-8.0 (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/1853082
Title:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
Public bug reported:
SRU justification:
[Impact]
New touchpads are ignored by hid driver because of IDs are missed in the
whitelist.
[Fix]
Only 2 Elan touchpad IDs are allowed to be loaded in hid driver.
Change to the blacklist of elan touchpads supported by elan_i2c, so others can
be
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1853246
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
SRU Justification
=== Impact ===
Some issues found while Mellanox verifying linux-bluefield. These are the
patches they sent to address those issues.
=== Risk of Regression ===
Should be reasonably low since:
* Patches are clean cherry-picks from upstream.
* Verified on
I found no changes since the CRD nor a discussion on the ML of qemu or libvirt.
There are the backported fixes that add taa-no and pschange-mc-no to qemu - but
nothing touches hle/rtm yet.
The general answer of of the virt stack avoiding type proliferation are
versioned CPU models.
=>
Public bug reported:
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.42.2/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.42.2 (note that the debian
changelog is
ubuntu@lp1849733-b:~$ dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.33 amd64system and service manager
ubuntu@lp1849733-b:~$ dig +noanswer +noedns toomany.ddstreet.org
;; Truncated, retrying in TCP mode.
; <<>> DiG 9.11.3-1ubuntu1.10-Ubuntu <<>> +noanswer +noedns
When I however add in the init file it gets sourced and shows up in
chrome://version but does not work as prefers-color-scheme is still
light. If I supply it at the command line it correctly works but shows
up twice on chrome://version. Should I report this in a seperate bug or
in the chromium bug
ubuntu@lp1849733-b:~$ dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.31 amd64system and service manager
ubuntu@lp1849733-b:~$ telnet toomany100.ddstreet.org
telnet: could not resolve toomany100.ddstreet.org/telnet: Temporary failure in
name resolution
ubuntu@lp1849733-b:~$
Good, that means this issue should be fixed in the 20.04 release of
Ubuntu, as it will utilize the updated package currently in Debian. Feel
free to try requesting a sync for the 19.10 release, but the source has
significantly changed since the version currently in Ubuntu, so I
suspect it'll be
Public bug reported:
After upgrade from disco to eoan, notwithstanding the fact that
/etc/cups/printers.conf has stayed the same, I cannot print anymore to an smb
connected printer provided by my Institution.
The connection uses authentication and username, password are present in the
smb url
ubuntu@lp1832672-b:~$ dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.31 amd64system and service manager
ubuntu@lp1832672-b:~$ grep bar /etc/hosts
127.0.2.1 foo # bar
ubuntu@lp1832672-b:~$ systemd-resolve -4 bar
bar: 127.0.2.1
-- Information acquired via protocol DNS in 1.9ms.
--
Hi Dave,
IIRC Openstack either tries to determine the least common denominator (in cpu
features) or whatever you pass to hi, in your case that was:
[libvirt]
cpu_mode = custom
cpu_model = Skylake-Server-IBRS
And your guest definition won't change after the initial definition.
Even if you would
Should I build this from source? Or is there a .deb package that I can
install with dpkg?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853075
Title:
19.10 Boots into a black screen
To manage
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Po-Hsu Lin (cypressyew)
Status: In Progress
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
**
** 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 --
** 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/1851347
Title:
libmbim-proxy using 100% CPU on a Dell Edge Gateway
Yes it will, I am working on it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850651
Title:
Authentication constantly re-requested for Google
To manage notifications about this bug go to:
https://lists.ubuntu.com/archives/kernel-team/2019-November/105575.html
** Description changed:
- Would it be possible to enable rockchip support in Ubuntu 18.04 kernel
- for arch aarch64(arm64)?
+ == SRU Justification ==
+ We already have this ROCKCHIP support enabled for armhf (bug 1566283),
+
** 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:
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:
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:
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 --
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
--
You received this bug notification because you
** 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:
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:
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 --
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
--
You received this bug notification because you
Ran into the same scanner issue today with a Brother MFC-6490CW under
Ubuntu 18.04 (factory installed by Dell and fully updated before
attempting printer/scanner install). Found pdc's post on askubuntu.com (
https://askubuntu.com/a/1054065/314730 ) first, which linked to
staedtler-przyborski's
I know this is fixed in Thunderbird 69.0.1 and 68.2. can this be put into
the repository for Ubuntu 16.04 LTS?
Jeremy
On Tue, Nov 19, 2019, 10:41 PM Olivier Tilloy
wrote:
> ** Changed in: thunderbird (Ubuntu Xenial)
>Status: In Progress => Fix Committed
>
> ** Changed in: thunderbird
** 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
**
** 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
**
** Changed in: thunderbird (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: thunderbird (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux
Status: Confirmed => Unknown
** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #433
https://gitlab.freedesktop.org/drm/amd/issues/433
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux
Status: Confirmed => Unknown
** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #293
https://gitlab.freedesktop.org/drm/amd/issues/293
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
Still present with kernel-4.0.5-200.fc21.x86_64:
[drm:radeon_get_legacy_connector_info_from_bios [radeon]] *ERROR*
Unknown connector type: 8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157681
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
Probably a bios bug. What physical connectors are actually on the
board?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157681
Title:
Some drm/radeon *ERROR* messages unnecessarily alarm the user
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc8/
Under v5.4-rc8, run
# echo "file drivers/pci/* +p" > /sys/kernel/debug/dynamic_debug/control
And attach dmesg when this issue happens again.
--
You received this bug notification because you are a
Daniel, can you please attach output of `grep . /sys/class/dmi/id/*`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799235
Title:
kworker process starts at 85% of cpu and stays there
To manage
** Changed in: lmms (Debian)
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/1757751
Title:
Please port your package away from Qt 4
To manage notifications about
commit 86c6739eda7d2a03f2db30cbee67a5fb81afa8ba
Author: Steffen Klassert
Date: Wed Nov 6 08:13:49 2019 +0100
xfrm: Fix memleak on xfrm state destroy
We leak the page that we use to create skb page fragments
when destroying the xfrm_state. Fix this by dropping a
page
** 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:
The error message when executing `sudo apt -y upgrade`:
- postgresql-common : Depends: postgresql-client-common (= 190) but
+ postgresql-common : Depends: postgresql-client-common (= 190) but
190ubuntu0.1 is installed
+ `sudo apt --fix-broken install` did
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc8/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853075
Title:
19.10 Boots into a black screen
To manage
** Summary changed:
- trusty/linux-azure: -proposed tracker
+ trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical
** 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 will contain status and test results related to a kernel source
(or snap) as stated in the
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820967
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743595
[Expired for thunar (Ubuntu) because there has been no activity for 60
days.]
** Changed in: thunar (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844841
[Expired for gnome-user-docs (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gnome-user-docs (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for tzdata (Ubuntu) because there has been no activity for 60
days.]
** Changed in: tzdata (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830495
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems to be a problem from the chip series itself since in 16.04.03
it also does not get detected. Or the internal mic is flawed, I still
need to test in windows 10 to be sure if it is a alsa driver problem to
this chip or a hardware problem
--
You received this bug notification because you
Public bug reported:
The error message when executing `sudo apt -y upgrade`:
postgresql-common : Depends: postgresql-client-common (= 190) but
190ubuntu0.1 is installed
`sudo apt --fix-broken install` did not solve the problem. My Postgres is
completely down.
** Affects:
** Description changed:
+ [Impact]
+ With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT
+ is set to Y, then it will make the legacy intel soc driver fail, and
+ moreover the current sof driver can't support broadwell well, as a
+ result, many broadwell computers with I2S
Public bug reported:
I am using two monitors, they both are displaying the same image. In
settings, only one monitor is recognized (technically they have the same
name, though). I have tried to go into arandr to see what I could do but
only one monitor is recognized there.
ProblemType: Bug
All three distros are fixed, thanks!
What about Eoan? Does it need this fix, too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833660
Title:
/lib/udev/rules.d/99-gce.rules tries to apply
indeed, the headphone mic is working perfectly, so it`s not detecting
the internal, i am still to test the internal mic in others SOs to
attest that is an alsa-driver bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I should have mentioned that I have a fix for this too just running it
by mvo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852773
Title:
test failures on focal due to missing build-depends on
** Attachment added: "testlog-disco.log"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+attachment/5306548/+files/testlog-disco.log
** Tags removed: removal-candidate verification-needed verification-needed-disco
** Tags added: verification-done-disco
--
** 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:
*-display
description: VGA compatible controller
product: HD Graphics 620
vendor: Intel Corporation
physical id: 2
bus info: pci@:00:02.0
version: 02
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm
** Attachment added: "modinfo-i915.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5306547/+files/modinfo-i915.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I should have mentioned that I have a fix for this just running it by
mvo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852772
Title:
test_updates_interval fails on focal
To manage notifications
** Changed in: gce-compute-image-packages (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Tags removed: verification-needed-bionic verification-needed-xenial
** Tags added: verification-done-bionic verification-done-xenial
** Attachment added: "testlog-xenial.log"
Sorry about messing with the status. I should have RTFM twice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833660
Title:
/lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1853219
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Description
Add intel_thermal_pch driver support Comet Lake -H
Target Release: 20.04
Target Kernel: 5.5
** Affects: intel
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: focal
Target machins is Ubuntu 16.04:
Linux scadauser-NP3020M3 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri
Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
This problem also affected me after a new qt installation ( I only
copied the lib, plugins, qml into target machine's /usr/local/qt5.7 ).
Public bug reported:
I'm trying to use Evolution to access a 6000-vcard collection on a slow
CardDAV server.
Evolution (actually the backend 'evolution-addressbook-factory') fails
to read the contents of an address book stored on this slow CardDAV
server.
The message is "Socket I/O timed out"
Sorry Brian, I managed to miss the original notification. I'll check all
3 distros right now on the GCE.
** Changed in: gce-compute-image-packages (Ubuntu Bionic)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "testlog-bionic.log"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+attachment/5306541/+files/testlog-bionic.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Using AMCGPU driver with same results by v86d under Kubuntu 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/1504886
Title:
v86d is taking 100% of 1 CPU
To manage notifications about this bug
That didn't help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853075
Title:
19.10 Boots into a black screen
To manage notifications about this bug go to:
Public bug reported:
No further information
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
** 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:
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:
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 --
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
--
You received this bug notification because you
I tried to create audio.conf, but it doesn't work for me.
Ubuntu 18.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/192502
Title:
bluetooth audio skips, cuts out
To manage notifications about
This bug has been fixed on Ubuntu 14.04 ESM,
linux kernel package version 3.13.0-175.226.
Marking the LP bug as Fix Released / Trusty.
** Changed in: linux (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => gerald.yang (gerald-yang-tw)
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification
The attachment "0001-dmidecode-Only-scan-dev-mem-for-entry-point-
on-x86.patch" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message
** Changed in: glib
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/1852844
Title:
Nautilus/Files UI requires sudo access to unmount a disk that can be
unmounted
** Tags removed: verification-needed-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/1850572
Title:
AMD Prairie Falcon platform failed to boot up
To
** 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 --
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
--
You received this bug notification because you
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
This package failure looks like it was caused by bad ISO download,
corrupted install media, or device failure. eg. look in the logs and
you'll see messages like these :-
Nov 19 21:42:49 ubuntu kernel: [
Launchpad has imported 6 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=99181.
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
1 - 100 of 456 matches
Mail list logo
