** Patch added: "debdiff with a port of the fix in PR#8803 for bionic"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5245782/+files/systemd_237-3ubuntu10.15.1.debdiff
** Summary changed:
- Please backport "fix race between daemon-reload and other commands #8803" t
** Description changed:
On Ubuntu Core we recently hit the a race in daemon-reload and systemctl
twice. This race is fixed in systemd upstream: "fix race between daemon-
reload and other commands #8803".
To reproduce its enough to run:
for i in $(seq 50); do
- systemctl daemon-re
** Also affects: libva via
https://github.com/intel/intel-vaapi-driver/issues/419
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bug
For a fresh install of Ubuntu 18.04 I found that libnss-resolve needed to be
installed to fix various systemd-resolvd errors (with a setup like you
describe, gateway does DHCP for a local net and DNS).
Your case may be different because you seem to have a null domain. My ISP sets
up a line like
For the affected, a workaround is available:
Download and manually install resolveconf from the previous version-1.79ubuntu10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bug
The ubuntu package doesn't include needed patch, i.e
0004-Check-the-interface-from-libva-first.patch
Apply that and it'll work fine..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net
I've faced the same issue, but in a recently installed Ubuntu Desktop 18.04 on
a Asus K46CB.
I tried @pujan fix but it didn't work.
Several minutes later I've tried to type: ~$ cat /etc/resolv.conf following
tips from here (Brazilian forum):
https://www.vivaolinux.com.br/topico/Iniciantes-no
Can confirm. Specifically breaks DNS resolution in Firefox when I'm
logged into an OpenConnect VPN. I can resolve hosts that are in public
DNS, but I'm uncertain if this is because of caching. Internal DNS over
the VPN no longer resolves. Downgrading to the previous version of
resolvconf restor
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: resolvconf (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launc
So I switched to Linux Kernel 5 since RC-5 and I was switching to the
latest version ever since a new one is released. It seems that the 5
branch has fixed the issue for good. I am on 5.0.1 and have no issue
with output. *fingers crossed*
However I do have an issue with the input. Cannot recognize
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 14.04 LTS.
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by checking in Software Center
apt-cache policy libselinux1
libselinux1:
Installed: 2.7
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libselinux in Ubuntu.
https://bugs.launchpad.net/bugs/1819817
Title:
package libselinux1:amd64 2.7-2build2 failed to install/upgrade: пак
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1742714
Title:
MIR: mesa-vulkan-drivers FFE: install by default
Stat
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.
The Suru icon theme is from the 'ubuntu-themes' source package.
** Package changed: yaru-theme (Ubuntu) => ubuntu-themes (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-themes (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs
The bug is still present in i965-va-driver 2.3.0-0ubuntu1 on disco.
** Changed in: intel-vaapi-driver (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: libva (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
** Changed in: pulseaudio (Ubuntu Disco)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1817338
Title:
HDMI sound output not selectable in
You have been subscribed to a public bug:
Google for "download icon" and you'll see that an arrow down to a
horizontal line is generally accepted as the icon for "download". See:
https://www.google.be/search?q=download+icon
In Suru icon theme, this icon however is the "save" icon. This has
alread
Yoshinori: Mesa i965 team is seeking a way to reproduce this bug, so we
can analyze and fix it.
How often does this occur in your product? If it is reproducible, then
perhaps we can use an apitrace to investigate the root cause.
--
You received this bug notification because you are a member of
I saw this once.
[Environment]
CPU: SkyLake(core i5 6500TE)
Distribution: debian(customised)
Kernel: 4.14.98
Mesa: 18.3.3
libdrm: 2.4.89
Message from stdout of drawing module was
i965: Failed to submit batchbuffer: Bad address
and back-trace were following
:
:
#5 0x7f4496240b
(In reply to Yoshinori Gento from comment #18)
> I saw this once.
This occurred in our product.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1794033
Title:
i965: Failed to
There is also a problem in dhclient where it forks off the daemon and
exits before writing the pidfile which needs a separate fix.
** Changed in: isc-dhcp (Ubuntu Disco)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
thats actually really useful information. the Arch link in particular.
think i am happy to have my family members able to change volume etc,
but not sure how to set up a systemd service.
think i will just log everyone out when the bug happens, at least
starting a new session gets the sound workin
** Changed in: initramfs-tools (Ubuntu Disco)
Status: New => Invalid
** Changed in: isc-dhcp (Ubuntu Disco)
Status: New => Invalid
** Changed in: cloud-initramfs-tools (Ubuntu Disco)
Status: New => Invalid
** Changed in: busybox (Ubuntu Disco)
Status: New => Fix Commi
On Tue, 12 Mar 2019 at 19:35, Seth Arnold <1797...@bugs.launchpad.net> wrote:
>
> On Tue, Mar 12, 2019 at 04:05:45PM -, Dimitri John Ledkov wrote:
> > defaults. And all of them however have committed to drop support for
> > those in 2020. My expectation is to follow suit, and set default
> > se
debdiff for libqmi 1.22.0 in Bionic. The upstream source tarball is the
same as for Disco.
** Patch added: "libqmi_1.18.0-3ubuntu1_1.22.0-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/1819615/+attachment/5245702/+files/libqmi_1.18.0-3ubuntu1_1.22.0-0ubuntu1.debdiff
-
I have made Bionic packages for ModemManager 1.10 and the needed
libraries now. I have attached the debdiffs and the upstream tarballs
are the same as of the Disco packages.
Ken, could you upload these packages for me.
Alex, if we need to go through the SRU process (is this needed for
hardware en
debdiff for libmbim 1.18.0 in Bionic. The upstream source tarball is the
same as for Disco.
** Patch added: "libmbim_1.14.2-2.1ubuntu1_1.18.0-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/1819615/+attachment/5245700/+files/libmbim_1.14.2-2.1ubuntu1_1.18.0-0ubuntu1.deb
debdiff for modemmanager 1.10 in Bionic. The upstream source tarball is
the same as for Disco.
** Patch added: "modemmanager_1.6.8-2ubuntu1_1.10.0-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/1819615/+attachment/5245699/+files/modemmanager_1.6.8-2ubuntu1_1.10.0-0ubun
On Tue, Mar 12, 2019 at 04:05:45PM -, Dimitri John Ledkov wrote:
> defaults. And all of them however have committed to drop support for
> those in 2020. My expectation is to follow suit, and set default
> security level to 2, and require TLS1.2 shortly after 19.10 release.
Can you expand upon
@lain:
https://bugs.freedesktop.org/show_bug.cgi?id=109535
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1818516
Title:
FFe: Mesa 19.0.x for disco
Status in mesa package i
https://github.com/systemd/systemd/issues/8686 seems related.
** Bug watch added: github.com/systemd/systemd/issues #8686
https://github.com/systemd/systemd/issues/8686
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syste
** Changed in: libmbim (Ubuntu Bionic)
Status: New => In Progress
** Changed in: libqmi (Ubuntu Bionic)
Status: New => In Progress
** Changed in: modemmanager (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Added tasks for libmbim and libqmi as their current versions are needed
by ModemManeger 1.10.
** Also affects: libmbim (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libmbim (Ubuntu)
Importance: Undecided => High
** Also affects: libqmi (Ubuntu)
Importance: Undecided
Public bug reported:
After isc-dhcp update from 4.3.5 to 4.4.1, dhclient-script uses
valid_lft option when adding an IPv4 address.
When used on the initrd generated by initramfs-tools, this will fail
because busybox ip does not support this option.
This affects the use of cloud-initramfs-dyn-net
There were no relevant changes between .1 and .2 thus marking this bug
as verified on Xenial again.
** 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
There were no relevant changes between .1 and .2 thus marking this bug
as verified on Xenial again.
** 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
There were no relevant changes between .1 and .2 thus marking this bug
as verified on Xenial again.
** 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
T
There were no relevant changes between .1 and .2 thus marking this bug
as verified on Xenial again.
** 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
Tested with unattended-upgrades/1.1ubuntu1.18.04.7~16.04.2:
Python-apt is not rebuilt in the test:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/u/unattended-
upgrades/20190228_150449_11313@/log.gz
** Tags removed: ver
The error is still not appearing on 16.04:
https://errors.ubuntu.com/?release=Ubuntu%2016.04&package=unattended-
upgrades&period=year&version=1.1ubuntu1.18.04.7~16.04.2
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
Y
Verified with unattended-upgrades/1.1ubuntu1.18.04.7~16.04.2 on Xenial:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/u/unattended-
upgrades/20190228_150449_11313@/log.gz :
Running ./test_remove_unused.py with python3
In
The upstream announcement is now available here:
https://discuss.linuxcontainers.org/t/lxc-2-0-11-has-been-released/4238
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1816642
Uploaded to the SRU queue for Ubuntu 16.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1816642
Title:
SRU of LXC 2.0.11
Status in lxc package in Ubuntu:
Fix Release
Added to Trello: https://trello.com/c/XNVW4Tpp/275-bug1817338-hdmi-
sound-output-not-selectable-in-1904-but-works-in-1810
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/18
** Also affects: pulseaudio (Ubuntu Disco)
Importance: Undecided
Status: Invalid
** Also affects: gnome-control-center (Ubuntu Disco)
Importance: High
Assignee: Robert Ancell (robert-ancell)
Status: Confirmed
--
You received this bug notification because you are a member
Opening pavucontrol after changing the setting in gnome-control-center
switches it half of the time, so there seems to be a problem in
pulseaudio with listening to changes and applying them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
FWIW, the same seems to apply to me, but not just HDMI.
I have:
* Digital output on external DAC
* Analog output on external DAC
* HDMI
* Speakers
I can change as I want to, the active output device does not change.
I think it's the same for recording devices, seeing as pacmd stat lists
the sam
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1819728
Title:
Please backport "fix race between daemon-reload and other commands
#8803" to 16.04 (fo
On Mon, 11 Mar 2019 at 21:20, Steve Langasek
wrote:
>
> Acceptance of openssl currently blocked on coverage of the (distro
> patch) OPENSSL_TLS_SECURITY_LEVEL change as part of the SRU template.
>
In Debian (but never ubuntu) they have bumped the default security
level from 1, to 2.
In Ubuntu, w
@laney:
https://bugs.freedesktop.org/show_bug.cgi?id=109535
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1818516
Title:
FFe: Mesa 19.0.x for disco
Status in mesa package
@Iain:
https://bugs.freedesktop.org/show_bug.cgi?id=109535
** Bug watch added: freedesktop.org Bugzilla #109535
https://bugs.freedesktop.org/show_bug.cgi?id=109535
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in U
Public bug reported:
On Ubuntu Core we recently hit the a race in daemon-reload and systemctl
twice. This race is fixed in systemd upstream: "fix race between daemon-
reload and other commands #8803".
To reproduce its enough to run:
for i in $(seq 50); do
systemctl daemon-reload &
systemctl
This change is already in the systemd in cosmic+
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1819728
Title:
Please backport "fix race between daemon-reload and other co
Hi sir I'm not sure about any of that, but if you click the drop down
button in the top right then click the button between the
wrench/screwdriver and the lock button and that middle button is the one
that stops the obnoxious screen rotation.
On Tue, Mar 12, 2019 at 9:56 AM Antonello
wrote:
> Pr
I'm untargetting the specific releases so that this doesn't show up in
our weekly reports. I would like to see some more debugging and to
better understand why it's just this one machine. It doesn't yet sound
like this is a release critical bug.
** No longer affects: Ubuntu Cosmic
** No longer
** Changed in: systemd (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1818282
Title:
systemd-networkd - RoutingP
** No longer affects: libnotify (Ubuntu Xenial)
** No longer affects: libnotify (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnotify in Ubuntu.
https://bugs.launchpad.net/bugs/1802483
Title:
Notificati
there's an older bug for src:vulkan-loader, let's use that
https://bugs.launchpad.net/ubuntu/+source/vulkan-loader/+bug/1742711
** Summary changed:
- Move mesa-vulkan-drivers from Univers to Main and install by default in
Ubuntu 18.04
+ MIR: mesa-vulkan-drivers FFE: install by default
** Change
Sponsored for Disco, considering that after a discussion with joalif,
she committed to file a debian bug and submit the patchset to debian as
well for stay consistent in the chain Upstream -> Debian -> Ubuntu.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch
xserver-xorg will Recommend mesa-vulkan-drivers
** Package changed: mesa (Ubuntu) => xorg (Ubuntu)
** Changed in: xorg (Ubuntu)
Status: Confirmed => Triaged
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because
Problem in Elitebook 840 g2 solved by removing/purging iio sensor
package after the first installation (Debian) updated to the testing
version . The problem affected screen and touchpad/mouse. It seems to me
that it is a unnecessary package for laptop with no position sensors is
it not?
--
You re
Thanks for filing this bug in Ubuntu.
You have some odd error messages in your logs:
Processing triggers for ufw (0.35-0ubuntu2) ...
Setting up openssh-client (1:7.2p2-4ubuntu2.8) ...
Setting up openssh-sftp-server (1:7.2p2-4ubuntu2.8) ...
Setting up openssh-server (1:7.2p2-4ubuntu2.8) ...
Unsafe
This bug was fixed in the package intel-vaapi-driver - 2.3.0-0ubuntu1
---
intel-vaapi-driver (2.3.0-0ubuntu1) disco; urgency=medium
* Merge with Debian, remaining changes:
- use upstream tarball with shader support
-- Timo Aaltonen Tue, 12 Mar 2019 14:15:20 +0200
** Changed
Public bug reported:
No apport report written because the error message indicates its a followup
error from a previous failure.
No apport report written because MaxReports is
reached already
dpkg: error processing package google-chrome-stable (--configure):
dep
This is resolved for me. Ubuntu 18.04 running stock gnome shell session.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1010421
Title:
Text antialiasing is green.
** Tags added: id-5c868875e54e05183ffb1732
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1818953
Title:
mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by
*** This bug is a duplicate of bug 1683383 ***
https://bugs.launchpad.net/bugs/1683383
Yes, I confirm the bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1720364
Title
actually, bionic was already tested earlier, and the tested fix is a
one-line change to mesa which is still the same on 18.2.8 so marking
bionic verified.. and also cosmic since it's the exact same version
there, and cosmic kernel was also tested to be buggy
--
You received this bug notification
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic
verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to me
Thanks, that solved it. Not sure why I had both at all, never fiddled on
this low level stuff. Must be a left-over from some Ubuntu upgrade in
the past that was now triggered by this patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
Marco, the kernel should be released next week.
I built a kernel against bionic/master-next branch, along with all
-proposed packages, the state state is now "not charging" [1] just like
Windows.
If would also be great if other users can verify this bug.
--
You received this bug notification be
> man systemd-resolved has the following line:
If this update had any effect on you, then you're not using systemd-
resolved; you're using resolvconf. If you don't want that, then
uninstall resolvconf, and your dns resolution will revert to using
systemd-resolved.
--
You received this bug notif
That worked.
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1819589
Title:
Ubuntu CI is broke
Public bug reported:
The package resolveconf version 1.79ubuntu10.18.04.1 is broken.
Installing the package breaks DNS resolution.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: resolvconf 1.79ubuntu10.18.04.1
Uname: Linux 4.15.0-46-generic x86_64
Architecture: amd64
** Affects: resolvcon
I've tested this on gen4 & gen9 Intel and AMD Bonaire
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic
verification-done-cosmic
--
You received this bug notification because you are a member of
Alkis, please test 18.2.8 for bionic and if possible, cosmic
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https:/
Public bug reported:
To have Bionic, the current LTS, working with as wide of a range of
modems as possible we need to have it upgraded to the current 1.10
versions. Also the underlying libraries need to get upgraded
appropriately.
** Affects: modemmanager (Ubuntu)
Importance: High
This does not only affect Y700. This affects all Lenovo laptops with
subwoofers, y50, y700, y720 etc.
Also, Linux supports drivers for hardware that is a lot older, this hardware is
only about 2 years old (y720).
--
You received this bug notification because you are a member of Ubuntu
Touch se
Forget about this, guys. Lenovo has already stopped selling Y700 for
years.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1553685
Title:
Lenovo Y700-17ISK subwoofer d
I just got this update on Ubuntu 18.10 and it broke resolving of
localhost subdomains. localhost can be resolved to 127.0.0.1, but any
*.localhost can not.
man systemd-resolved has the following line:
The hostnames "localhost" and "localhost.localdomain" (as well as any
hostname ending in
".
Should be fixed with https://salsa.debian.org/systemd-
team/systemd/commit/bd89a706b18796074d50bcf2a0cbd29de56ac542 . I'll
close this once the retried PRs go green.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Status: Ne
** Changed in: dbus (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1807709
Title:
dbus always crashes at session start (on waylan
I really want this solved too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1553685
Title:
Lenovo Y700-17ISK subwoofer doesn't work
Status in alsa-driver package in
Public bug reported:
Since
https://salsa.debian.org/systemd-team/systemd/commit/8d810fda9a640a932d6e7b32afd958fe75e36f5b
was merged Ubuntu CI has been failing with
```
Investigating (0) udev:amd64 < 237-3ubuntu10.13 -> 241-608-gfd541a5f08-0 @ii
pumU Ib >
Broken udev:amd64 Depends on dpkg:amd64
86 matches
Mail list logo
