@wide0s: what is the exact version of podman you were testing in the
comment above? Please provide the output of:
type -p podman
dpkg -s podman
podman --version
podman system info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@mdeslaur the issue is not addressed with a simple debdiff, several
packages need to be updated in the right order. I've done all this work
in debian testing, and all those packages could be synced over.
I'm asking for help with coordinating these uploads.
--
You received this bug notification
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1227
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-27191
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-27649
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a security vulnerability ***
Public security bug reported:
Ubuntu 20.04 ships currently with podman 3.4.4. Current upstream is at
version 3.4.7 and ships with a number of security updates:
3.4.7
* This release addresses CVE-2022-1227, where running podman top on a container
Ubuntu Jammy ships with podman 3.4
** Changed in: libpod (Ubuntu)
Status: New => Fix Released
** Changed in: libpod (Ubuntu)
Assignee: (unassigned) => Reinhard Tartler (siretart)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I've created test packages in my ppa at
https://launchpad.net/~siretart/+archive/ubuntu/podman/+packages
** Description changed:
+ [Impact]
+
+ Buildah, a specialized tool for building container images and an
+ alternative to docker, fails to fulfill it's primary use-case: building
+ container
)
Status: New => In Progress
** Changed in: golang-github-containers-buildah (Ubuntu Impish)
Assignee: (unassigned) => Reinhard Tartler (siretart)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
are you sure that the autopkgtests ever worked? As far as I can tell
from https://ci.debian.net/packages/c/consul/unstable/amd64/ it seems to
have been broken for quite a while (if they ever worked, that is)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: Debian Bug tracker #997133
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997133
** Also affects: consul (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997133
Importance: Unknown
Status: Unknown
--
You received this bug notification because
This might actually be intended behavior. I noticed that 21.10
introduced a new package that contains the missing kernel modules in
`linux-modules-extra-raspi`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
libpod uploaded to impish-proposed
** Changed in: libpod (Ubuntu Impish)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943049
Title:
Docker
golang-github-opencontainers-specs uploaded to impish-proposed
** Changed in: golang-github-opencontainers-specs (Ubuntu Impish)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
golang-github-containers-common uploaded to impish-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943049
Title:
Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm
-f
** Also affects: golang-github-opencontainers-specs (Ubuntu)
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/1943049
Title:
Docker ubuntu:impish: Problem
It's actually more complicated. Seems that
https://github.com/containers/common/pull/573 is necessary, but not
sufficient to fix this issue. I'm backporting additional commits that
made it into the containers/common 0.40.1 release (all of which update
seccomp.json), which I believe are all
Importance: Undecided => High
** Changed in: golang-github-containers-common (Ubuntu Impish)
Status: New => Confirmed
** Changed in: golang-github-containers-common (Ubuntu Impish)
Assignee: (unassigned) => Reinhard Tartler (siretart)
--
You received this bug notification becau
Hi, I've been doing the uploads for podman to debian and ubuntu for a
while now.
I'm struggling with reproducing this bug with podman on impish. On a
freshly "multipass launch'ed" impsish vm, I tried:
ubuntu@primary:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Please also check the configuration in your home directory.
Also, you always have the option of just installing both crun and run.
Lastly, can you try podman on hirsute or impish? Vagrant should make this
really easy.
On Sun, Jun 13, 2021, 17:25 Alex Rodriguez <1925...@bugs.launchpad.net>
just installed a fresh 'impish' installation with 'multipass', installed
via 'apt install podman', and a quick 'podman run --rm -it fedora'
worked right away.
** Changed in: libpod (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
and
needs syncing with the rest of the ubuntu archive.
** Changed in: libpod (Ubuntu)
Status: New => Invalid
** Changed in: libpod (Ubuntu)
Assignee: (unassigned) => Reinhard Tartler (siretart)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
'
** Changed in: libpod (Ubuntu)
Status: New => Incomplete
** Changed in: libpod (Ubuntu)
Assignee: (unassigned) => Reinhard Tartler (siretart)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
ibpod (Ubuntu)
Assignee: (unassigned) => Reinhard Tartler (siretart)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925765
Title:
[21.04 regression] networking broken in containers
To manage notification
** Summary changed:
- Podman/libpod crash
+ Error: default OCI runtime "runc" not found: invalid argument
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905443
Title:
Error: default OCI runtime
=> Triaged
** Changed in: libpod (Ubuntu)
Importance: Undecided => Medium
** Changed in: libpod (Ubuntu)
Assignee: (unassigned) => Reinhard Tartler (siretart)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
package available in ubuntu 20.10 and later
** Changed in: libpod (Ubuntu)
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/1851960
Title:
[needs-packaging] missing
Didier, what's the best way to contact them? Can you subscribe people
that would be able to advise / give guidance how to best resolve the
FTBFS bugs mentioned above?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this is also affecting many other package builds, such as
https://launchpad.net/ubuntu/+source/golang-github-containers-
storage/1.20.2-3/+build/19612159
Didier, Roche, how do you feel about adding those dependencies to the
ubuntu package?
** Changed in: docker.io (Ubuntu)
Status:
As another datapoint, the docker.io package serves as a build dependency
to many container-related packages in the archive. Dropping the package
would in the short-term mean breaking all packages that use this code
(nomad, buildah, podman, to name a few). In the long term, it might
cause increased
** Changed in: fs2ram (Ubuntu)
Status: Invalid => New
** Changed in: software-center (Ubuntu)
Status: Invalid => New
** Changed in: vdradmin (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Nathan, could you please elaborate why you marked this bug as invalid?
What makes you think this was fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1341307
Title:
fs2ram places /var/cache on
Unfortunately, apport-collect didn't collect the crash file. Please
check if there is an corresponding crash file for this segfault in
/var/crash and report it using "ubuntu-bug /var/crash/". We
can then mark the new bug as duplicate of this one as necessary.
Alternatively, you could use
** Changed in: synaptic (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336527
Title:
add --version argument
To manage notifications about this bug go
Unfortunately, this is not enough. Please use apport-collect
(http://manpages.ubuntu.com/manpages/bionic/en/man1/ubuntu-bug.1.html)
to attach the missing information.
The backtrace indicates that the crash comes from avcodec_open2(), which
is found in the ffmpeg package. However, your trace did
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
** Bug watch added: Red Hat Bugzilla #1147282
https://bugzilla.redhat.com/show_bug.cgi?id=1147282
** Also affects: qemu (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1147282
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
to assist wherever I can, but I
> reported chiefly because I cannot debug or investigate of my own.
>
> Regarding the cheese issue, the exact same issue arises when just using
> uvcvideo, so it is definitely something passed on from the driver.
>
> 2018-04-12 15:52 GMT+02:00 Reinhard
Looking at the stacktrace, this is coming from /usr/bin/cheese. Even
with bad input from the driver (which seems like a valid issue to
investigate and improve) - an error message is preferable to a SIGFPE as
seen in the initial report.
** Also affects: linux via
A fixed version is now in the archive
** Package changed: aspectc++ (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: Confirmed => Fix Released
** Changed in: ubuntu
Assignee: (unassigned) => Reinhard Tartler (siretart)
--
You received this bug notification because you are
A fixed version is now in the archive
** Package changed: aspectc++ (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, the warning is printed whenever you use a copy of the 'ffmpeg'
binary with a copy of libavcodec (or any other library provided by the
ffmpeg source package) that has been built with a different
configuration. Which is the whole point of the 'libavcodec-extra*'
packages: Enable additional
This is a bug in the clipgrab package, which was probably installed from
https://launchpad.net/~clipgrab-team/+archive/ubuntu/ppa. I have
subscribed the clipgrab team to notify them about this bug.
Dear clibgrab packaging team:
The clipgrab package really isn't supposed to ship the file
This backtrace is pretty much the same as
https://bugzilla.redhat.com/show_bug.cgi?id=1015831 - redhat/fedora has
released a fix to accomodate that /var/run is now a tmpfs. Does the fix
also apply to Ubuntu?
** Bug watch added: Red Hat Bugzilla #1015831
Rolf, please show the partition table of the trusty system that you
tested.
On Thu, May 26, 2016, 23:45 Rolf Leggewie <736...@bugs.launchpad.net>
wrote:
> I do not experience this in trusty. Is this still an issue?
>
> ** Changed in: grub2 (Ubuntu)
>Status: Triaged => Incomplete
>
> --
>
I've uploaded a package that reverts the string to the version in xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454306
Title:
apt-btrfs-snapshot supported reports "Sorry, your system lacks
This issue is already fixed in the latest development version of Ubuntu
yakkety.
The fix has also been uploaded to xenial, the most recent Ubuntu release,
and is currently waiting for the archive admins to approve.
On Mon, May 9, 2016, 11:11 S. W. wrote:
> he guys
>
>
>
I've uploaded version 3.5.1ubuntu0.1 to xenial-proposed.
Ubuntu-SRU, please review and approve. Thanks
** Changed in: apt-btrfs-snapshot (Ubuntu Xenial)
Status: New => In Progress
** Changed in: apt-btrfs-snapshot (Ubuntu Xenial)
Importance: Undecided => High
--
You received this
** Description changed:
+ [Impact]
+ apt-btrfs-snapshot is unable to detect the btrfs binary, rendering the
package completely useless. The symptom is that the package claims the system
was not supported despite having root on btrfs
+
+ [Test Case]
+ root@halde:~# apt-btrfs-snapshot supported
>From reading those links, I take it that this issue can be fixed by
changing the keepassx.desktop file. That file is taken verbatim from
upstream:
https://github.com/keepassx/keepassx/blob/master/share/linux/keepassx.desktop
Maybe you can propose a change?
On Sun, May 1, 2016 at 10:35 AM
Can you please clarify what meta data is needed? I'm not familiar with
Gnome Software requirements.
A patch (in form of a debdiff) would be most appreciated.
On Tue, Apr 26, 2016 at 4:30 PM AsciiWolf <1575...@bugs.launchpad.net>
wrote:
> Public bug reported:
>
> The KeePassX package cannot be
Status: Confirmed
** Also affects: apt-btrfs-snapshot (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: apt-btrfs-snapshot (Ubuntu Yakkety)
Assignee: (unassigned) => Reinhard Tartler (siretart)
** Changed in: apt-btrfs-snapshot (Ubuntu Xenial)
Assignee: (unassig
What needs to be changed in the keepassx package?
On Mon, Apr 25, 2016, 10:11 Matthias Klumpp
wrote:
> FTR, Keepass needs a short summary:
> http://appstream.ubuntu.com/xenial/universe/issues/keepass2.html
> http://appstream.ubuntu.com/xenial/universe/issues/keepassx.html
Thank you for this clarification.
I'm not sure how to enable the aufs backend. Reading in the docker
documentation at
https://docs.docker.com/engine/userguide/storagedriver/selectadriver/, I
understand with lxc running on btrfs, there is no other option than
using the btrfs option.
--
You
Public bug reported:
System uses / on btrfs.
System: Xenial
Testcase:
apt install lxd
lxc launch -e ubuntu:x x
lxc exec apt update
lxc exec apt install docker.io
lxc exec docker -ti run debian:latest uptime
lxc exec bash
root@x:~# docker rm $(docker ps -a -q)
Failed to remove container
Hi Michael,
I've locally built your branch lp:~mvo/apt-btrfs-snapshot/trunk and am
happy to confirm that it fixes this bug. Too bad it didn't make it into
xenial, because without it the package is rather useless.
Can you please upload it to yakety so that we can start the SRU process?
Thanks,
I can also confirm that this bug is present in the Final xenial release
** Changed in: apt-btrfs-snapshot (Ubuntu)
Importance: Undecided => High
** Changed in: apt-btrfs-snapshot (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member
Does this patch also apply to wily, and thus needs to be uploaded there
as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447099
Title:
/sbin/upstart:indicator-session-unknown-user-error
To
I've just synced the debian package from strech to Xenial
** Changed in: keepassx (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: keepassx (Ubuntu)
Assignee: (unassigned) => Reinhard Tartler (siretart)
--
You received this bug notification because you are a
A new upstream version of keepassx has entered Xenial now. This version
rewrites basically the whole UI code, which makes this particular crash
very unlikely. If you can, please give the new version a try and let us
know how it works for you.
** Changed in: keepassx (Ubuntu)
Status:
A new upstream version of keepassx has entered Xenial now. This version
rewrites basically the whole UI code, which makes this particular crash
very unlikely. If you can, please give the new version a try and let us
know how it works for you.
** Changed in: keepassx (Ubuntu)
Status:
Is this reproducible? It sounds like something that can be resolved
following http://askubuntu.com/questions/422696/package-is-in-a-very-
bad-inconsistent-state
** Changed in: libav (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
transcode needs to be ported to use the new avcodec_encode_video2 API, the
old API has been deprecated long ago and is no longer available now.
On Wed, Jul 22, 2015, 3:30 PM Luca Olivetti olivl...@gmail.com wrote:
Public bug reported:
When I try to rip a dvd with k3b (selecting mpeg4 as the
I've just uploaded gnucash_2.6.6-2ubuntu1_source.changes to wily
** Changed in: gnucash (Ubuntu)
Status: New = Fix Released
** Changed in: gnucash (Ubuntu)
Assignee: (unassigned) = Reinhard Tartler (siretart)
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ Following the bug comments below, it seems that problem is specific to
+ systems that have the package ibus, but not the package ibus-gtk,
+ installed. Kubuntu installations seem to be typically affected.
+
+ Workaround: sudo apt-get ibus-gtk.
+
+ Original Description:
** Bug watch added: Debian Bug tracker #778999
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778999
** Also affects: gnucash (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778999
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Ubuntu vivid now ships with gnucash version 1:2.6.4-3, which contains
this changelog entry:
gnucash (1:2.6.4-1) unstable; urgency=medium
* Imported Upstream version 2.6.4
+ Fixes formula parsing error with scheduled mortgage transactions.
(Closes: #748594)
+ No longer crashes on
I've just recompiled and installed debian package version 1:2.6.4-3, and
can confirm that the bug has *NOT* been fixed:
gnucash
Traceback (most recent call last):
File /usr/share/gnucash/python/init.py, line 3, in module
from gnucash import *
ImportError: No module named gnucash
Found
With this patch, how does the user select whether to encode with 8bit or
10bit depth?
On Jan 10, 2015 10:20 AM, djcj d...@gmx.de wrote:
I figured that linking the x262 and x26410b plugins dynamically does
work. x26410b requires an rpath though, otherwise it would use the
regular 8bit x264
On Sat, Jan 10, 2015 at 12:53 PM, djcj d...@gmx.de wrote:
With this patch libx26410b_plugin.so is linked against
/usr/lib/${DEB_HOST_MULTIARCH}/x264-10bit/libx264.so.140 and loading it via
rpath. libx264_plugin.so loads the regular x264 library.
It seems the x264 bit depth can be set in the
Ubuntu already does provide a 10bit libx264 library in
/usr/lib/x86_64-linux-gnu/x264-10bit/libx264.so.142
Check yourself at: http://packages.ubuntu.com/trusty/amd64/libx264-142/filelist
The problem is that you can't have both the 8bit and the 10bit
libx264.so loaded into the same process
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366348
Title:
vlc crashed with SIGABRT in qt_message_output()
To manage notifications about this
We need a full backtrace of this crash, cf. to
https://wiki.ubuntu.com/Backtrace how to provide that.
Also, does this crash also occur with other players, such as avplay or
vlc?
** Changed in: libav (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377464
Title:
update-desktop-file-unity-webapps-twitter.py crashed with
AttributeError in
Nope, that line does not seem to exist on my system:
grep dbus-vfs-daemon /etc/apparmor.d/abstractions/gnome
zsh: exit 1 grep dbus-vfs-daemon /etc/apparmor.d/abstractions/gnome
dpkg -S /etc/apparmor.d/abstractions/gnome
apparmor: /etc/apparmor.d/abstractions/gnome
dpkg -l apparmor
From the buildlog of the 14.04 build:
Warning: AV_PIX_FMT_FLAG_RGB is missing from libavutil, update for swscale
support
Warning: libavformat is not supported without swscale support
Warning: ffms is not supported without swscale support
This problem seems to be fixed in utopic!
** Also
Public bug reported:
standard upgrade with apt-get
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: gdb 7.8-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
Date: Fri Oct 3
Public bug reported:
I've recently upgraded to Ubuntu utopic.
When trying to access a pdf file on a dav:// share, I get a permission
denied error.
While getting peer-to-peer dbus connection: Verbindung ist gescheitert: Keine
Berechtigung
In dmesg, I see this
[ 1394.331262] audit: type=1400
As a workaround, disabling apparmor allows me to open files directly
from dav:// shares: sudo aa-complain /usr/bin/evince
Alternatively, I could copy the file to /tmp, and open it from there,
even with apparmor active
--
You received this bug notification because you are a member of Ubuntu
Works for me on Ubuntu 14.10 - most likely also in previous releases of
ubuntu:
avplay http://samples.mplayerhq.hu/V-codecs/CRAM/dance.avi
** Changed in: libav (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1369273
Title:
gnucash crashed with ImportError in /usr/share/gnucash/python/init.py:
No module
looks very similar to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=737202
** Package changed: devscripts (Ubuntu) = emacs-goodies-el (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
cat /tmp/elc_sjtjLr.log
(master↑1|✔) :0
emacs24 -q -batch -l path.el -f batch-byte-compile devscripts.el
pbuilder-log-view-mode.el pbuilder-mode.el
Loading 00debian-vars...
the fix proposed in the related branch unbroke the upgrade for me
** Changed in: emacs-goodies-el (Ubuntu)
Importance: Undecided = High
** Also affects: emacs-goodies-el (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737202
Importance: Unknown
Status: Unknown
--
whatever support for libindicator3 was introduced in 1.10-0ubuntu1, it
doesn't seem to work on Ubuntu utopic
** Changed in: workrave (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
cf.
https://launchpad.net/~cjwatson/+archive/ubuntu/devirt/+build/6323454
[ 41%] Building CXX object src/CMakeFiles/spark.dir/scripting/abc_codesynt.cpp.o
cd /build/buildd/lightspark-0.7.2/obj-x86_64-linux-gnu/src
/usr/bin/x86_64-linux-gnu-g++ -DAUDIO_BACKEND=\pulse sdl\
On Mon, Sep 1, 2014 at 9:55 AM, Reinhard Tartler siret...@gmail.com wrote:
On Sat, Aug 30, 2014 at 1:00 PM, Scott Kitterman ubu...@kitterman.com wrote:
On Saturday, August 30, 2014 12:46:19 Reinhard Tartler wrote:
On Sat, Aug 30, 2014 at 12:36 PM, Scott Kitterman ubu...@kitterman.com
wrote
On Sat, Aug 30, 2014 at 1:00 PM, Scott Kitterman ubu...@kitterman.com wrote:
On Saturday, August 30, 2014 12:46:19 Reinhard Tartler wrote:
On Sat, Aug 30, 2014 at 12:36 PM, Scott Kitterman ubu...@kitterman.com
wrote:
On Saturday, August 30, 2014 11:35:13 Reinhard Tartler wrote:
On Thu, Aug
On Thu, Aug 21, 2014 at 9:30 PM, Reinhard Tartler siret...@gmail.com wrote:
On Thu, Aug 21, 2014 at 3:12 PM, Adam Conrad adcon...@ubuntu.com wrote:
As of nowish, Feature Freeze is in effect for utopic (14.10), leading
up to the release in October.
Don't fret if you have One Last Feature
On Sat, Aug 30, 2014 at 12:36 PM, Scott Kitterman ubu...@kitterman.com wrote:
On Saturday, August 30, 2014 11:35:13 Reinhard Tartler wrote:
On Thu, Aug 21, 2014 at 9:30 PM, Reinhard Tartler siret...@gmail.com
wrote:
On Thu, Aug 21, 2014 at 3:12 PM, Adam Conrad adcon...@ubuntu.com wrote
AFAIUI, all packages that fail to build libav11 related have been fixed
in Debian. all other package fail to build from source because of
reasons unrelated to libav11
** Bug watch added: Debian Bug tracker #757917
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757917
** Also affects: libav
Public bug reported:
This ticket is to track the Libav11 transition in Utopic.
See the discussion on the Mailing list on
https://lists.ubuntu.com/archives/ubuntu-devel/2014-August/038435.html
The transition is being staged in
https://launchpad.net/~motumedia/+archive/ubuntu/libav11/+packages.
AFAIUI, there is nothing to do for the libdvdread package
** Changed in: libdvdread (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912320
Title:
DVD CSS
comment from IRC:
04:12 j-b LP #975959 is a totem bug
** Package changed: libdvdread (Ubuntu) = totem (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975959
Title:
when inserting dvd Open
*** This bug is a duplicate of bug 1179913 ***
https://bugs.launchpad.net/bugs/1179913
** This bug has been marked a duplicate of bug 1179913
Zero check failed in ifo_read.c:904 for pgc-subp_control[i] = 0x0001
--
You received this bug notification because you are a member of Ubuntu
At least for precise, libav-extra also needs to be updated to 0.8.15
** Also affects: libav-extra (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libav-extra (Ubuntu Trusty)
Status: New = Invalid
** Changed in: libav-extra (Ubuntu Precise)
Importance: Undecided =
I can confirm the observations of comment #20. On this basis, I'm
raising the importance because this seems to me like a major usability
issue.
** Changed in: nautilus (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Package built fine:
https://launchpad.net/~siretart/+archive/ubuntu/ppa?field.series_filter=trusty
** Changed in: libav (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
utopic already works with libav 10, nothing left to do here
** Changed in: libav (Ubuntu Utopic)
Status: Fix Committed = 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/1341216
Public bug reported:
Trusty should get version 9.16:
version 9.16:
- vp3: Copy all 3 frames for thread updates (CVE-2011-3934)
- mpegts: Do not try to write a PMT larger than SECTION_SIZE (CVE-2014-2263)
- mpegts: Define the section length with a constant
- error_concealment: avoid using the
a fixed package should appear in ppa:siretart shortly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354755
Title:
Libav security fixes Aug 2014
To manage notifications about this bug go to:
Utopic already has the latest upstream release including all fixes so
far in utopic-proposed. I'm not sure why the transition is stuck at this
point, though.
** Changed in: libav (Ubuntu Utopic)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a
1 - 100 of 4020 matches
Mail list logo