Is there a workaround for this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2059872
Title:
Unable to listen on port 22 if multiple Port= present in sshd
configuration
See kodi issue with stack traces:
https://github.com/xbmc/xbmc/issues/16258
** Also affects: jackd2 (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https:
*** This bug is a security vulnerability ***
Public security bug reported:
After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes
in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-
plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is
enabled by d
I'm marking this a security bug, since all double close bugs can
potentially be security bugs in multithreaded programs depending on the
close interleaving.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
htt
** Patch added:
"Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch"
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+attachment/5271631/+files/Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch
** Information type changed from Publi
** Description changed:
After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes
in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-
- plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is
+ plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA ja
jackd2 released version 1.9.13 which includes this fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833479
Title:
libjack-jackd2-0 double close on a failure to connect
I just requested one and received: CVE-2019-13351
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-13351
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/18334
Can this package get updated to 1.9.13, or at least patched in time for
20.04? The security exploitability of this bug may be low, but the impact
on affected users is high. It causes hard to debug, random crashes of other
programs (e g. Kodi) that are scanning ALSA devices when the jack daemon
isn'
I'm marking this as also affects alsa-plugins since that is shipping a
jack plugin by default, and this bug is triggered when jack isn't even
running. Programs that scan for ALSA devices pick up that jack plugin
and trigger the double close.
** Also affects: alsa-plugins (Ubuntu)
Importance: Un
*** This bug is a security vulnerability ***
Public security bug reported:
There are 3 security issues reported in libx11 that are fixed upstream
in libx11 1.6.6.
Bugs announced:
https://lists.x.org/archives/xorg-announce/2018-August/002915.html
Release announcement of libx11 1.6.6 with commits
It looks like libx11-1.6.6 was pulled into cosmic. So this is fixed
there. This still needs a backport to earlier releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1788
*** This bug is a duplicate of bug 1496163 ***
https://bugs.launchpad.net/bugs/1496163
** This bug has been marked a duplicate of bug 1496163
i915 firmware is not copied to initrd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
This bug is a duplicate of #1496163.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1492774
Title:
update-initramfs doesn't copy symlinked firmware files
Status i
Public bug reported:
In /usr/share/initramfs-tools/hook-functions, the firmware is copied to the
initramfs using:
cp -a "$firmware" "$target_dir"
For symlinked firmware such as /lib/firmware/i915/skl_dmc_ver1.bin for
Intel Skylake, this results in a copy of the symlink instead of the
firmware fi
I want to add that this isn't in the Debian version of the package. The
change to remove the call to copy_exec is what broke this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchp
I've just upgraded to zesty, and this problem is still present. Since
systemd-resolved is sticking a 127.0.0.53 nameserver in resolv.conf, the
problem is worse. To work around it, I have to replace resolv.conf with
the old dnsmasq 127.0.1.1 address instead to prevent DNS lookups from
going through
Is this going to make it for focal? This bug causes kodi to crash when
turning my TV screen off.
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/183
I currently have the package patched in my PPA to resolve the bug. It is
a difficult to debug problem that has been sending users upstream to
kodi with bug reports and confusing stack traces. This will get more
exposure when focal is released due to the LTS status.
--
You received this bug notifi
This is supposed to be fixed in Mesa 20.1 git by c81aa15d,
gallium/auxiliary/vl: fix bob compute shaders for deint yuv.
See:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/c81aa15d646215eac38c8e0b6dc1a10b35bc13c3
This could be backported to Mesa 20 if someone wants to try it.
--
You received
Public bug reported:
2.04-1ubuntu12.2 broke boot on my machine. It doesn't work with kernels
that don't have CONFIG_EFI_STUB=y configured. This really needs to fall
back to the old mode if EFI handover is not supported by the kernel.
Also, after using a kernel with CONFIG_EFI_STUB=y it still fail
I filed this against grub2 originally. Somehow ubuntu-bug changed that
to xorg. I added grub2 back. It's not letting me remove xorg.
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: xorg (Ubuntu)
--
You received this bug notification because you
Oibaf is using the development release of Mesa. It's not released yet.
Mesa 20.1 isn't scheduled for release until May.
You need them to backport the fix to the 20.0.x branch. Here is the
upstream issue: https://gitlab.freedesktop.org/mesa/mesa/issues/2523
You can ask there for a backport to 20.0
No one is asking you to send them a fix. Since you are experiencing the
issue on a stable release, you should let Mesa know that the issue
exists in stable releases, and ask them to provide the fix for the
stable 20.0.x branch.
--
You received this bug notification because you are a member of Ubu
I upgraded to Utopic and this problem got worse on that machine. I've
attached the new mountall.log.
The fstab line for the mount is now:
rt-ac66u:/tmp/mnt/yasimedia /mnt/readyshare nfs
_netdev,hard,intr,exec,nodev,nosuid,async,nobootwait 0 0
It looks like it's not detecting the m
I've been suffering the same issue. Plasma crashes every time my 4K
monitor sleeps or is turned off in Kubuntu 15.10. I had to pull in Qt
5.5 and this patch to make my desktop usable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Public bug reported:
After upgrading to Ubuntu 16.10 from 16.04, DNS resolution of hosts on
my local network fails.
The hosts line in /etc/nsswitch.conf is:
hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return]
dns mdns4
If I change it to:
hosts: files mdns4_m
Public bug reported:
libx11 suffers from 32-bit sequence wraparound for programs that make a
large number of calls to the server. (See: https://lists.x.org/archives
/xorg-devel/2013-October/038370.html )
The Freedesktop bug is here:
https://bugs.freedesktop.org/show_bug.cgi?id=71338
This was fix
Public bug reported:
After upgrading to upstart 1.12.1-0ubuntu4.1, logging in via lightdm
freezes on xsession start. The choice of xsession doesn't matter. It
will not load KDE or TWM. It freezes after pressing login without trying
to start the xsession.
startx from the commandline launches the x
It's still working for me here. I just tried Pidgin to make sure the
menu is exported. You'll need appmenu-gtk from the PPA and the version
of GTK2 in the PPA. appmenu-gtk requires a patched version of GTK2. This
will not work for GTK3 apps as I have not forward ported the patch for
GTK3 from rarin
30 matches
Mail list logo
