Can this be backported to Lunar. I tested hplip 3.22.10+dfsg0-2 on
Lunar, and it fixes the issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2012178
Title:
toolbox.py crashed with
The updated gstreamer-vaapi 1.20.1-1ubuntu1 is uninstallable from jammy-updates
due to a unmet dependency:
The following packages have unmet dependencies:
gstreamer1.0-vaapi : Depends: libgstreamer-plugins-bad1.0-0 (>= 1.20.3) but
1.20.1-1ubuntu2 is to be installed.
The package is dependent on
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
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 Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833479
Title:
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
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
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
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
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
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:
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
jackd2 released version 1.9.13 which includes this fix.
--
You received this bug notification because you are a member of Desktop
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 to jackd
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 Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833479
Title:
** 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
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 Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
** 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
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 Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
*** 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
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 Desktop
Packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1788448
Title:
*** 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
Is this going to get pulled into Artful? It's been in Debian since Dec
5, 2016. It made it into Debian 9.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxvmc in Ubuntu.
https://bugs.launchpad.net/bugs/1691532
Title:
CVE-2016-7953
Any reason libx11 wasn't bumped for zesty this? 1.6.4 has some security
fixes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1671799
Title:
FFe: xserver 1.19.3
Status in
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
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
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
That's a problem with the wine dependencies. It shouldn't be an explicit
dependency on ocl-icd-libopencl1. For other 32-bit packages that depend
on libopencl-1.1-1, picking either ocl-icd-libopencl1 or nvidia-
libopencl-1.1-1 should work. This needs to be Multi-Arch aware.
--
You received this
In order to truly fix this, nvidia-libopencl1-VER, libcuda1-VER and
nvidia-opencl-icd-VER will need to be made Multi-Arch aware. Right
now, the amd64 package includes the 32-bit libraries. Since wine is
32-bit, it'll try to pull in nvidia-libopencl1-VER:i386 which
conflicts with
KDE PowerDevil now checks for Upstart if the systemd version check
fails. The version API implementation is no longer needed. The call to
the sleep scripts still needs to happen.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in
I've just started seeing this again after upgrading to trusty. This time
sending SIGUSR1 does not work. The mount.nfs process appears hung on
boot. Killing this process, and then sending SIGUSR1 to mountall results
in the partition mounting.
--
You received this bug notification because you are
So the reason I decided to check for kernel version instead of
CONFIG_UIDGID_STRICT_TYPE_CHECKS was for possible future proofing. If
the kernel in the future fragments with yet another config option for
kuid_t, they would likely implement another __kuid_val function for
that, and the patch would
The buildfix_kernel_3.12.patch breaks building on vanilla 3.12 kernels.
The module builds fine without it on 3.12.6
In file included from
/var/lib/dkms/nvidia-331-updates-uvm/331.20/build/nvidia_uvm_common.h:49:0,
from
So it looks like the buildfix_kernel_3.12.patch is missing a check for
CONFIG_UIDGID_STRICT_TYPE_CHECKS. The change to kuid_t only happens if
that config flag is enabled.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Patch added: Fix building with CONFIG_UIDGID_STRICT_TYPE_CHECKS enabled
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1252664/+attachment/3943946/+files/buildfix_CONFIG_UIDGID_STRICT_TYPE_CHECKS.patch
--
You received this bug notification because you
I dug through git, and kuid_t/kgid_t were introduced in kernel 3.5. The
proper thing to do is to call __kuid_val(uid) to convert to uid_t on
these kernels. The bug isn't a problem introduced with kernel 3.12. It
is a problem with all kernels compiled with
CONFIG_UIDGID_STRICT_TYPE_CHECKS. This
I've split them off into their own PPA: https://launchpad.net/~joe-
yasi/+archive/appmenu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/126
Title:
appmenu-gtk support dropped,
I guess it depends on how user programs are currently using the systemd
version API to check things. KDE PowerDevil strips everything before the
space and just compares against the number, so in principle, the shim
could use the prefix string to say something. I don't know how others
use the API.
I saw that there was some discussion of this on the Ubuntu developer list back
in July:
http://comments.gmane.org/gmane.linux.ubuntu.devel/37604
Was a decision ever made about what to do about this on KDE? Could the
patch be added back into GTK and the appmenu-gtk package be readded for
13.10
Are there still plans to add the version API to systemd-shim?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1196752
Title:
Suspend only works once when using upower with logind --
Which deprecated API? upower suspend? The version API is needed for KDE
to correctly use the systemd logind suspend system instead of upower.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
I have a hack of a patch which implements reading the systemd version
string in systemd-shim. It just calls systemd-udevd --version and
reports that.
** Patch added: Implements version API in systemd-shim
I think this might actually be libdbusmenu-qt's bug. If the children-
display menu is not immutable in the libdbusmenu-gtk version, then it
shouldn't be in libdbusmenu-qt either.
** Also affects: libdbusmenu-qt
Importance: Undecided
Status: New
--
You received this bug notification
I figured out what is going on. The children-display property is
immutable in libdbusmenu-qt. This, when the firefox patch tries to
change that property to submenu for menus with children, it doesn't
work. The patch will have to be updated to set the children-display
property to submenu on
Is anyone looking at this bug?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/779344
Title:
Issue running in KDE - menus only appears after losing and regaining
focus
Status in
.xsession-errors contains:
void DBusMenuImporterPrivate::updateActionProperty(QAction*, const QString,
const QVariant): Unhandled property update children-display
after clicking on the missing menu items on the first try. It seems like there
is a lazy fetch out of order.
** Changed in:
This only affects an Ubuntu specific patch to Firefox which is not
upstreamed yet.
** Project changed: firefox = firefox (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/779344
Public bug reported:
GTK apps don't properly export menus on KDE since the appmenu-gtk
support was removed. unity-gtk-module does not work outside of unity.
Can the appmenu-gtk patch be added back in until unity-gtk-module works
in other environments?
** Affects: unity-gtk-module
Public bug reported:
On saucy with upower 0.9.20-1ubuntu2, suspending via UPower (or the KDE suspend
menu) only works once:
dbus-send --print-reply --system --dest=org.freedesktop.UPower
/org/freedesktop/UPower org.freedesktop.UPower.Suspend
and resuming works the first time. However, calling
47 matches
Mail list logo
