hello, could someone help get that patch get merged ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886831
Title:
whitelist 64-bit time syscalls
To manage notifications about this bug go to:
https
is there a git repository for ubuntu's docker.io package where I could
submit the update ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886831
Title:
whitelist 64-bit time syscalls
To manage noti
I just rebuilt docker-doc_19.03.6-0ubuntu1~18.04.1_all.deb (in bionic) with
this patch:
apt-get source docker.io && cd docker.io-19.03.6/ && curl -L
https://github.com/docker/docker-ce/commit/3c5d28f12ba6f3839ae77837633372993a073f57.patch
| patch -p1 && dpkg-source --commit && debuild -us -uc
I
this is a feature request for the docker version in bionic/focal to pick up a
commit from v19.03.9
to allow these syscalls (or update these packages to 19.03.9)
the libseccomp SRU was a necessary condition to allow such a backport
(in other words the syscalls were blocked at the libseccomp level,
** Summary changed:
- whitelist 64-bit time_t syscalls
+ whitelist 64-bit time syscalls
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886831
Title:
whitelist 64-bit time syscalls
To manage notifi
I ran more tests, and the first version to work is 19.03.9, I wonder if
an update would be possible:
bionic: 19.03.6 => 19.03.9
focal: 19.03.8 => 19.03.9
groovy: 19.03.11 ok
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
993a073f57
here is a testcase that ends up calling utimensat_time64 via docker:
cd /tmp && git clone https://github.com/xantares/test-seccomp-time64.git &&
docker build test-seccomp-time64
this affects bionic, but also focal as the same version 19.03 is used
--
You rece
/files
these changes need to be applied to the docker.io file
"components/engine/profiles/seccomp/default.json"
(moby sources are included in docker.io sources)
here is a testcase that ends up calling utimensat_time64 via docker:
cd /tmp && git clone https://github
the docker.io file
"components/engine/profiles/seccomp/default.json"
(moby sources are included in docker.io sources)
here is a testcase that ends up calling utimensat_time64 via docker:
cd /tmp && git clone https://github.com/xantares/test-seccomp-time64.git &&
docker
Focal may be affected after all then
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868720
Title:
backport time64 syscalls whitelist
To manage notifications about this bug go to:
https://bugs.launc
turns ou we may also need this fix in docker:
https://github.com/moby/moby/pull/40739
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868720
Title:
backport time64 syscalls whitelist
To manage notif
of course, you do:
cd /tmp && git clone https://github.com/xantares/test-seccomp-time64.git
&& docker build test-seccomp-time64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Patch added: "backport time64 syscalls from 2.4.2 into 2.4.1"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+attachment/5340882/+files/libseccomp241-time64.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Public bug reported:
A number of new *time64 syscalls are introduced in newer kernel series
(>=5.1.x):
403: clock_gettime64
404: clock_settime64
405: clock_adjtime64
406: clock_getres_time64
407: clock_nanosleep_time64
408: timer_gettime64
409: timer_settime64
410: timerfd_gettime64
411: timerfd_
Public bug reported:
hello,
could it be updated to 1.6.1 ?
https://github.com/jeromerobert/hmat-oss/releases/tag/1.6.1
** Affects: hmat-oss (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Public bug reported:
can we sync to 3.7.0-3 in debian sid that has the fix to include
arpack.hpp for ubuntu 20.04 ?
it is possible to backport it for 18.04 ?
** Affects: arpack (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
can we sync to 3.7.0-3 in debian s
Public bug reported:
nlopt got some updates, currently it is at 2.6.1
see https://github.com/stevengj/nlopt/releases
it would be cool to have some newer release of nlopt for the LTS
thanks for maintaining
** Affects: nlopt (Ubuntu)
Importance: Undecided
Status: New
--
You receive
Has this been released ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755250
Title:
backport statx syscall whitelist fix
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
Ok for me too, I just installed libseccomp2_2.3.1-2.1ubuntu4.1_amd64.deb
and it works:
Step 16/18 : RUN gcc test-statx.c -o test-statx
---> Running in 501935bb923d
Removing intermediate container 501935bb923d
---> a47f15cd6fc8
Step 17/18 : RUN touch test-file
---> Running in 1038f76ad915
Removi
Public bug reported:
The libcminpack-dev subpackage misses the CMinpackConfig.cmake file:
$ cat debian/libcminpack-dev.install
usr/include/cminpack-1/*.h
usr/lib/*/libcminpack.so
usr/lib/*/pkgconfig/cminpack.pc
We can see it is part of the package:
/usr/bin/cmake -P cmake_install.cmake
-- Insta
hello,
how long does it take usually for ubuntu to review the changes ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755250
Title:
backport statx syscall whitelist fix
To manage notifications ab
here is a patch against libseccomp 2.3.1 in bionic (on top of the debian risc
port patch)
I manually applied changes from libseccomp 2.3.3 that reference the
statx syscalls
for the risc part i used the diff from
https://github.com/seccomp/libseccomp/blob/2a70ad4f3e8ab80e88f0662a760f4ef1d9219205/
Unfortunately that's not recent enough: the bug has just been fixed a
few days ago and will need some backporting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755250
Title:
backport statx syscall
Public bug reported:
Hello maintainer,
The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall
which is needed to build qt >=5.10 applications:
https://github.com/docker/for-linux/issues/208#issuecomment-372400859
Could this fix be backported in the ubuntu package ?
https://
*** This bug is a duplicate of bug 1424013 ***
https://bugs.launchpad.net/bugs/1424013
if you downgraded compiz and experienced the same issues, how can you tell it's
from the compiz package ?
I uninstalled nvidia (304) drivers (lsmod shows nouveau), downgraded compiz &
unity, and I'm still
*** This bug is a duplicate of bug 1424013 ***
https://bugs.launchpad.net/bugs/1424013
Hi,
How did you disable X11 sync in compiz, preferably in command line ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
26 matches
Mail list logo
