Public bug reported:
libsdl1.2 always enables backingstore when it is present in the X
server. For modern X servers, backingstore is implemented by redirecting
through the composite extension. This causes tearing on SDL applications
such as xbmc because the redirected rendering is not guaranteed
** Description changed:
libsdl1.2 always enables backingstore when it is present in the X
server. For modern X servers, backingstore is implemented by redirecting
through the composite extension. This causes tearing on SDL applications
such as xbmc because the redirected rendering is not
It should be noted that upstream is not planning on making another SDL
1.2 release. They are building a compatibility API for SDL 2.0 instead.
We should apply this patch until that compatibility API is ready.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I can verify that the bug still occurs with libsdl1.2debian
1.2.15-8ubuntu1 and is fixed by libsdl1.2debian 1.2.15-8ubuntu1.1.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libsdl1.2 in Ubuntu.
https://bugs.launchpad.net/bugs/1280665
This has stopped working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217610
Title:
NFS mounts don't mount on boot
To manage notifications about this bug go to:
It's something with mountall. It was upgraded from 2.49 to 2.50 and 2.51
before the last reboot. I reverted to 2.50 and the problem still
occured. I reverted to 2.49 and the NFS mounts come up on boot. I'll
take a look at what changed in the mountall package between 2.49 and
2.50.
--
You
Hmm, so if I revert this change to the init script:
. /etc/default/rcS || true
[ -f /forcefsck ] force_fsck=--force-fsck
[ $FSCKFIX = yes ] fsck_fix=--fsck-fix
+# Doesn't work so well if mountall is responsible for mounting /proc, heh.
+if [ -e /proc/cmdline ]; then
+
/proc/cmdline is:
BOOT_IMAGE=/boot/vmlinuz-3.11.1-customatom
root=UUID=708b3ba8-c42a-4adf-a195-c0fb8d8f8dd3 ro
So, none of those options are passed to the kernel. Mountall is
starting, and everything but the NFS mounts are mounting fine. When NFS
fails to mount without those lines, mountall is
Public bug reported:
NFS partitions fail to mount on boot, and mountall freezes without mounting
them. If I revert this change to the init script:
. /etc/default/rcS || true
[ -f /forcefsck ] force_fsck=--force-fsck
[ $FSCKFIX = yes ] fsck_fix=--fsck-fix
+ # Doesn't work so
Here is the mountall.log requested in bug #1217610
** Attachment added: mountall.log with --verbose passed.
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1226766/+attachment/3825793/+files/mountall.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Filed as: #1226766
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217610
Title:
NFS mounts don't mount on boot
To manage notifications about this bug go to:
Okay, sending SIGUSR1 after booting does bring up the NFS mounts.
The network configuration is just gigabit ethernet on eth0 configured
via DHCP through NetworkManager as a system connection.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
sudo status network-interface INTERFACE=eth0
network-interface (eth0) start/running
Yes. It shows as running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1226766
Title:
Mountall fails to mount
It's not just DNS. I changed the /etc/fstab entry to the IP address instead of
the hostname, and it still fails to mount with: mount.nfs: mount system call
failed
mountall: mount /mnt/readyshare [811] terminated with status 32
mountall: Disconnected from Plymouth
It must be racing the network
Public bug reported:
The published deb files for plasma-nm 0.9.3.0-0ubuntu3 are all nearly
empty. They contain just the debian changelog and the copyright file.
Something was missed when the transition package got added.
** Affects: plasma-nm (Ubuntu)
Importance: Undecided
Status:
The Firefox problem is due to this bug: https://bugs.launchpad.net
/globalmenu-extension/+bug/779344
I doubt anyone is looking at it because GTK+ apps don't work with KDE on
saucy by default anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@avlas: Careful with my PPA, there's also experimental graphics drivers
and stuff in there. I should probably split this out into another PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/126
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/126
Title:
appmenu-gtk support dropped, but
Here's an updated patch for the version that is currently in raring with
support for Qt5.
** Patch added: Use the X11 apptime instead of system time for an event.
https://bugs.launchpad.net/libdbusmenu-qt/+bug/1035755/+attachment/3621848/+files/fix-x-apptime.patch
--
You received this bug
Changing the timestamp to CurrentTime from X instead of the system
current time fixes the problem for me. I don't know if this is the
correct solution for Qt, but it's working for me.
** Patch added: change from system time to X11 CurrentTime
I've revised the patch to use the QX11Info::appTime() method for
querying the X time. This is probably better than the using the X
define.
** Patch added: use-qx11info-apptime.diff
https://bugs.launchpad.net/libdbusmenu-qt/+bug/1035755/+attachment/3484322/+files/use-qx11info-apptime.diff
**
The firmware shipped in the current version of the linux-firmware
package is incorrect. I have version 1.97 installed on Ubuntu 12.10.
The /lib/firmware/v4l-cx23885-enc.fw is identical to /lib/firmware/v4l-
cx23885-avcore-01.fw . However, when the cx23885 driver tries to load
the firmware, there
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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
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
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
Public bug reported:
kubuntu-settings-desktop version 14.04ubuntu6 fails to install due to
syntax errors in kubuntu-settings-desktop.postinst and kubuntu-settings-
desktop.postinst. The warn() functions in these scripts are missing a
semicolon:
warn() { echo W: $1 }
should be
warn() { echo W: $1
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
Public bug reported:
On boot with nfs shares specified in /etc/fstab, mountall hangs and the
nfs shares never get mounted. mount -a after boot properly mounts the
shares. The log on tty7 contains the line: mountall: Disconnected from
Plymouth
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package:
*** This bug is a duplicate of bug 1217110 ***
https://bugs.launchpad.net/bugs/1217110
Public bug reported:
Recently, pinentry-qt4 segfaults when I use gpg to decrypt a file:
gpg -d file.gpg
gpg: problem with the agent - disabling agent use
Enter passphrase:
This shows up in dmesg:
[
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
This happens with ibus-qt4 installed. If I remove ibus-qt4, it no longer
crashes.
** Also affects: ibus
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Are there still plans to add the version API to systemd-shim?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1196752
Title:
Suspend only works once when using upower with logind -- s-shim needs
to
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1196752
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 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.
You can turn it off by setting ui.use_unity_menubar = false in
about:config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1035755
Title:
[firefox] Extension causes context/drop down menus to
I've been using this fix for months with no problems. Are you running
into this bug: https://bugs.launchpad.net/libdbusmenu-qt/+bug/779344 ?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to libdbusmenu-qt in Ubuntu.
I did propose a merge. See https://code.launchpad.net/~joe-yasi
/libdbusmenu-qt/fix-x-timestamp/+merge/174573 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1035755
Title:
[firefox] Extension
Interesting. The D-BUS timeout for the org.freedesktop.UPower.Suspend is
new with the latest update to systemd-logind. I did not get a D-BUS
timeout before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So Powerdevil in KDE is supposed to call systemd-logind now instead of UPower
if it finds it. However, it is checking for the systemd version with a call to
org.freedesktop.systemd1.Manager.VErsion and not geting a valid response. For
some reason, that method doesn't exist on my system.
gdbus
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
I updated the patch to be a little cleaner for detecting Qt 5.0 and 5.1
as well as X11. It will default back to the system time in the no X11
case now.
** Patch added: Makes libdbusmenu-qt send the correct X11 event time instead
of the system time.
It's because the patch still hasn't been applied to the official
libdbusmenu-qt package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1035755
Title:
[firefox] Extension causes context/drop down
Is anyone looking at this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779344
Title:
Issue running in KDE - menus only appears after losing and regaining
focus
To manage notifications
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779344
Title:
Issue
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
Yes, systemd-shim is installed. The problem is UPower is not getting the
resume signal from logind, so suspend gets blocked the 2nd time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1196752
Title:
.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:
** Changed in: linux-firmware (Ubuntu)
Assignee: Chase Douglas (chasedouglas) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/569615
Title:
error in cx23885 firmware
To manage
Here is the working firmware file that is missing from the linux-
firmware package.
** Tags added: quantal
** Attachment added: v4l-cx23885-enc.fw
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/569615/+attachment/3470051/+files/v4l-cx23885-enc.fw
--
You received this bug
Public bug reported:
libsdl1.2 always enables backingstore when it is present in the X
server. For modern X servers, backingstore is implemented by redirecting
through the composite extension. This causes tearing on SDL applications
such as xbmc because the redirected rendering is not guaranteed
** Description changed:
libsdl1.2 always enables backingstore when it is present in the X
server. For modern X servers, backingstore is implemented by redirecting
through the composite extension. This causes tearing on SDL applications
such as xbmc because the redirected rendering is not
Public bug reported:
The change to startkde introduced in kde-workspace 4:4.11.8-0ubuntu4
breaks KDE startup. The correct change for the qdbus line is: qdbus=env
QT_SELECT=qt4 qdbus.
** Affects: kde-workspace (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
I can verify that the bug still occurs with libsdl1.2debian
1.2.15-8ubuntu1 and is fixed by libsdl1.2debian 1.2.15-8ubuntu1.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280665
Title:
libsdl1.2
It should be noted that upstream is not planning on making another SDL
1.2 release. They are building a compatibility API for SDL 2.0 instead.
We should apply this patch until that compatibility API is ready.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
Public bug reported:
The nvidia-opencl-dev package depends on nvidia-libopencl1-331 | nvidia-
libopencl1-331-updates. This dependency is too strict as nvidia-
libopencl1-334 and nvidia-libopencl1-337 will also satisfy it. There
should be a virtual dependency (libopencl1)
** Affects:
Public bug reported:
When building kernels with make-kpkg 13.014, it creates a broken symlink for
the architecture headers:
/usr/src/linux-headers-${KERNEL_VERSION}/include/asm/asm-x86 - asm-x86
This symlink is breaking the nvidia driver compile. Removing it fixes
their build.
** Affects:
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
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
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
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
*** 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
Bugs, which is subscribed to
This bug is a duplicate of #1496163.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492774
Title:
update-initramfs doesn't copy symlinked firmware files
To manage notifications about this bug go
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492774
Title:
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
Bugs, which is subscribed to Ubuntu.
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
** Bug watch added: code.mythtv.org/trac/ #12898
http://code.mythtv.org/trac/ticket/12898
** Changed in: mythtv
Importance: Undecided => Unknown
** Changed in: mythtv
Status: New => Unknown
** Changed in: mythtv
Remote watch: None => code.mythtv.org/trac/ #12898
--
You received
This patch fixes the build with newer ffmpeg.
** Patch added: "Fix build with newer ffmpeg PIXFMT names"
https://bugs.launchpad.net/ubuntu/+source/transcode/+bug/1631796/+attachment/4779421/+files/pixfmt_av.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This gentoo patch is probably cleaner than my patch which leaves a bunch of
warnings in place:
https://gitweb.gentoo.org/repo/gentoo.git/tree/media-video/transcode/files/transcode-1.1.7-ffmpeg29.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
** Also affects: mythtv
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/1631796
Title:
Yakkety version of transcode needed (removal causes unmet
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671799
Title:
FFe: xserver 1.19.3
To manage notifications about this
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
That info is from:
zpool status -v
I've worked around this suspend issue by writing a script to take the
NVMe L2ARC cache offline during suspend, and bring it back online on
resume.
The issue with bcache on suspend that I had for a similar situation is
because a read can trigger a write to the
I am also seeing this issue with zfs and l2arc cache on an NVMe and
4.10.14 on zesty. I've seen it in the past with btrfs, and a bcache
cache on NVMe as well, but not with the bcache cache on a SATA SSD. I
will move my zfs l2arc cache to a SATA SSD to see if that fixes suspend.
This is probably an
I've attached my workaround script. To use:
change the ZFSPOOLNAME variable in the script to the name of the zfspool with
an NVMe L2ARC.
change the NVMEL2ARCPART to the name of the cache partition.
sudo cp zpool-offline-cache.sh /lib/systemd/system-sleep/
sudo chmod +x
** Summary changed:
- zfs-auto-snapshot 1.2.2-1 is broken
+ zfs-auto-snapshot 1.2.2-1 does not make snapshots
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719724
Title:
zfs-auto-snapshot 1.2.2-1
Is this update going to make artful?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719724
Title:
zfs-auto-snapshot 1.2.2-1 is broken
To manage notifications about this bug go to:
Public bug reported:
zfs-auto-snapshot 1.2.2-1 has broken exec logic in cron which causes it
to not work at all. Upstream has released 1.2.4 which fixes the broken
cron syntax issues. Debian has released it as 1.2.4-1. There are no
reverse dependencies on zfs-auto-snapshot.
** Affects:
I believe this update should have a FeatureFreeze exception. The current
version in artful is non-functional due to the broken cron scripts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719724
Public bug reported:
There was an ABI change with the bump to version 20170815-1 of
libhdhomerun (the types of some exported function arguments were
changed). libhdhomerun 20170815-2 has been released at debian which
bumps libhdhomerun3 to libhdhomerun4 to reflect the ABI change. Can
Ubuntu pull
The Debian bugs for the issues with 1.2.2 are here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850776
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874182
1.2.3 and 1.2.4 were bug fix releases that fix this cron issue. With
1.2.2, the hourly, weekly and monthly snapshots do not happen.
** Tags added: artful
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719724
Title:
zfs-auto-snapshot 1.2.2-1 is broken
To manage notifications about this
I agree this should be a FreezeException due to the ABI breakage with
20170815-1.
libhdhomerun changed some type definitions for exported functions between
20161117 and 20170815. See:
https://github.com/Silicondust/libhdhomerun/commit/94edccd040a5a8021d28c37ca51677d8a8d9d07c
The kodi-pvr-hdhomerun and hdhomerun-config-gui packages are dependent
on libhdhomerun3, and haven't been rebuilt since the libhdhomerun
upgrade from 20161117-2 to 20170815-1. These packages are built against
the old ABI.
--
You received this bug notification because you are a member of Ubuntu
** Also affects: kodi-pvr-hdhomerun (Ubuntu)
Importance: Undecided
Status: New
** Also affects: hdhomerun-config-gui (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691532
Title:
CVE-2016-7953 in libxvmc 1.0.9
*** 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
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
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1788448
Title:
Most of the changes between 1.2.2 and 1.2.4 are related to fixing this bug.
"make --quiet really quiet" and it's merge are the only things not related.
All of the cron cleanups are for fixing this issue:
https://github.com/zfsonlinux/zfs-auto-snapshot/commits/upstream/1.2.4
I've been running
Public bug reported:
Since the binary packages have different versions from the source
package for the gcc-defaults package, but generate the deb revision
based on the source package, some binary packages did not upgrade when
upgrading from bionic to cosmic.
In my case, these two packages were
I think this needs to get pushed to cosmic as well. Cosmic has 12.2.4
which created a bit of a mess on upgrade from bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796645
Title:
[SRU] ceph
It looks like oath-toolkit 2.6.1-1.2ubuntu0.18.10.1 was pushed to
cosmic-updates resolving bug 1783706. Will this be resolved soon?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800526
Title:
1 - 100 of 134 matches
Mail list logo
