[Touch-packages] [Bug 1843490] Re: lxc.cgroup.devices.allow prevents unprivileged container from starting

2019-09-22 Thread linas
So is there a workaround? In my case, I'm trying to access an OpenCL gpu
from a userland container. I was assuming that the below might be
enough.

lxc.mount.entry = /dev/dri/card1 dev/dri/card1 none bind,optional,create=file
lxc.mount.entry = /dev/dri/renderD128 dev/dri/renderD128 none 
bind,optional,create=file

lxc.cgroup.devices.allow = c 226:* rwm

The mounts work (although owned by nobody:nobody instead of root:video)
and the devices cgroup stanza in the config file generates the container
boot error, as described above. The mounts are not enough to get opencl
access in the container: running "clinfo" (the opencl diagnostic) in the
container doesn't find the devices (I presume because of ... well,
something to do with /dev/dri but don't really know)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1843490

Title:
  lxc.cgroup.devices.allow prevents unprivileged container from starting

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Adding lxc.cgroup.devices.allow directives to an unprivileged
  container config prevent the container from starting. These lxc-start
  errors look relevant:

  
  lxc-start testbox 20190910192712.171 WARN cgfsng - 
cgroups/cgfsng.c:get_hierarchy:204 - There is no useable devices controller
  lxc-start testbox 20190910192712.171 ERRORcgfsng - 
cgroups/cgfsng.c:cg_legacy_set_data:2191 - Failed to setup limits for the 
"devices" controller. The controller seems to be unused by "cgfsng" cgroup 
driver or not enabled on the cgroup hierarchy
  lxc-start testbox 20190910192712.171 WARN cgfsng - 
cgroups/cgfsng.c:__cg_legacy_setup_limits:2228 - Failed to set "devices.allow" 
to "c 10:57 rwm"

  
  It seems to me that I used lxc.cgroup.devices.allow directives without 
trouble a few years ago. I wonder which system upgrades broke it.

  
  To reproduce:

  (Note: subuid, subgid, and lxc-usernet are already configured for this
  user.)

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.04
  Release:  19.04
  Codename: disco

  $ dpkg-query --show libpam-cgfs lxc1
  libpam-cgfs   3.0.3-0ubuntu1
  lxc1  3.0.3-0ubuntu1

  $ lxc-create -t download -n testbox -- -d ubuntu -r bionic -a amd64
  The cached copy has expired, re-downloading...
  Setting up the GPG keyring
  Downloading the image index
  Downloading the rootfs
  Downloading the metadata
  The image cache is now ready
  Unpacking the rootfs

  ---
  You just created an Ubuntu bionic amd64 (20190910_07:42) container.

  To enable SSH, run: apt install openssh-server
  No default root or user password are set by LXC.

  $ echo "lxc.cgroup.devices.allow = c 10:57 rwm" >> lxc/testbox/config

  $ lxc-start -n testbox -o debug.out -l trace
  lxc-start: testbox: lxccontainer.c: wait_on_daemonized_start: 842 Received 
container state "ABORTING" instead of "RUNNING"
  lxc-start: testbox: tools/lxc_start.c: main: 330 The container failed to start
  lxc-start: testbox: tools/lxc_start.c: main: 333 To get more details, run the 
container in foreground mode
  lxc-start: testbox: tools/lxc_start.c: main: 336 Additional information can 
be obtained by setting the --logfile and --logpriority options

  $ cat debug.out
  lxc-start testbox 20190910192712.380 INFO confile - 
confile.c:set_config_idmaps:1555 - Read uid map: type u nsid 0 hostid 10 
range 65536
  lxc-start testbox 20190910192712.380 INFO confile - 
confile.c:set_config_idmaps:1555 - Read uid map: type g nsid 0 hostid 10 
range 65536
  lxc-start testbox 20190910192712.382 TRACEcommands - 
commands.c:lxc_cmd:300 - Connection refused - Command "get_init_pid" failed to 
connect command socket
  lxc-start testbox 20190910192712.383 TRACEcommands - 
commands.c:lxc_cmd:300 - Connection refused - Command "get_state" failed to 
connect command socket
  lxc-start testbox 20190910192712.383 TRACEstart - 
start.c:lxc_init_handler:748 - Created anonymous pair {4,5} of unix sockets
  lxc-start testbox 20190910192712.383 TRACEcommands - 
commands.c:lxc_cmd_init:1248 - Creating abstract unix socket 
"/home/ubuntu/lxc/testbox/command"
  lxc-start testbox 20190910192712.383 TRACEstart - 
start.c:lxc_init_handler:760 - Unix domain socket 6 for command server is ready
  lxc-start testbox 20190910192712.388 INFO lxccontainer - 
lxccontainer.c:do_lxcapi_start:961 - Set process title to [lxc monitor] 
/home/ubuntu/lxc testbox
  lxc-start testbox 20190910192712.392 TRACEstart - start.c:lxc_start:2052 
- Doing lxc_start
  lxc-start testbox 20190910192712.393 INFO lsm - lsm/lsm.c:lsm_init:50 - 
LSM security driver AppArmor
  lxc-start testbox 20190910192712.393 TRACEstart - start.c:lxc_init:777 - 
Initialized LSM
  lxc-start testbox 20190910192712.395 TRACEseccomp - 
seccomp.c:get_new_ctx:458 - Added arch 2 to main seccomp context
  lxc-start

[Touch-packages] [Bug 1408092] Re: sysconfig.get_path('purelib') points to site-packages directory

2018-05-23 Thread linas
my downstream package suffers from this: https://github.com/opencog
/link-grammar/issues/530

** Bug watch added: github.com/opencog/link-grammar/issues #530
   https://github.com/opencog/link-grammar/issues/530

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1408092

Title:
  sysconfig.get_path('purelib') points to site-packages directory

Status in python3-defaults package in Ubuntu:
  Confirmed
Status in python3.5 package in Ubuntu:
  Confirmed

Bug description:
  purelib and platlib paths in Python 3 sysconfig module point to site-
  packages directory:

  $ python3 -m sysconfig

  Platform: "linux-x86_64"
  Python version: "3.4"
  Current installation scheme: "posix_prefix"

  Paths: 
data = "/usr"
include = "/usr/include/python3.4m"
platinclude = "/usr/include/python3.4m"
platlib = "/usr/lib/python3.4/site-packages"
platstdlib = "/usr/lib/python3.4"
purelib = "/usr/lib/python3.4/site-packages"
scripts = "/usr/bin"
stdlib = "/usr/lib/python3.4"
  ...

  whereas Python 2 points to dist-packages:

  Platform: "linux-x86_64"
  Python version: "2.7"
  Current installation scheme: "posix_local"

  Paths: 
data = "/usr/local"
include = "/usr/local/include/python2.7"
platinclude = "/usr/local/include/python2.7"
platlib = "/usr/local/lib/python2.7/dist-packages"
platstdlib = "/usr/lib/python2.7"
purelib = "/usr/local/lib/python2.7/dist-packages"
scripts = "/usr/local/bin"
stdlib = "/usr/lib/python2.7"
  ...

  One severe consequence of this is that automake is installing Python
  modules to a location which is not in sys.path, namely site-packages
  directory.

  When one uses automake to create a Makefile that installs a Python
  module to the system, it is installed into /usr/local/lib/python3.4
  /site-packages since automake/aclocal uses sysconfig to determine
  where the package will be installed.

  From /usr/share/aclocal-1.14/python.m4 file:

AC_CACHE_CHECK([for $am_display_PYTHON script directory],
  [am_cv_python_pythondir],
  [if test "x$prefix" = xNONE
   then
 am_py_prefix=$ac_default_prefix
   else
 am_py_prefix=$prefix
   fi
   am_cv_python_pythondir=`$PYTHON -c "
  $am_python_setup_sysconfig
  if can_use_sysconfig:
  sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'})
  <---
  else:
  from distutils import sysconfig
  ...

  Here, it can be seen that automake uses purelib path defined by the
  sysconfig module of Python. However, since this path is not included
  in sys.path, and thus the installed package cannot be used:

  $ python3 -c "import sys; print(sys.path)"
  ['', '/usr/lib/python3.4', '/usr/lib/python3.4/plat-x86_64-linux-gnu', 
'/usr/lib/python3.4/lib-dynload', '/usr/local/lib/python3.4/dist-packages', 
'/usr/lib/python3/dist-packages']

  
  Ubuntu version:14.10

  $ apt-cache policy python3-minimal 
  python3-minimal:
Installed: 3.4.2-1
Candidate: 3.4.2-1
Version table:
   *** 3.4.2-1 0
  500 http://mirror.23media.de/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1659590] Re: containers won't start after lxc and apparmor upgrades in trusty

2017-02-04 Thread linas
fwiw: me too - I'm hitting a related bug; same timeframe I assume
similar reasons. Debugging now.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1659590

Title:
  containers won't start after lxc and apparmor upgrades in trusty

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  On January 19 lxc and apparmor were upgraded on our VPN servers:

  2017-01-19 06:30:36 upgrade libdbus-1-3:amd64 1.6.18-0ubuntu4.4 
1.6.18-0ubuntu4.5
  2017-01-19 06:30:37 upgrade python3-lxc:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2
  2017-01-19 06:30:38 upgrade libapparmor1:amd64 2.8.95~2430-0ubuntu5.3 
2.10.95-0ubuntu2.5~14.04.1
  2017-01-19 06:30:38 upgrade libapparmor-perl:amd64 2.8.95~2430-0ubuntu5.3 
2.10.95-0ubuntu2.5~14.04.1
  2017-01-19 06:30:38 upgrade apparmor:amd64 2.8.95~2430-0ubuntu5.3 
2.10.95-0ubuntu2.5~14.04.1
  2017-01-19 06:30:39 upgrade lxc-templates:amd64 1.0.8-0ubuntu0.4 
1.0.9-0ubuntu2
  2017-01-19 06:30:40 upgrade liblxc1:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2
  2017-01-19 06:30:40 upgrade lxc:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2
  2017-01-19 06:30:41 upgrade libseccomp2:amd64 2.1.0+dfsg-1 
2.1.1-1ubuntu1~trusty3
  2017-01-19 06:30:42 upgrade dbus:amd64 1.6.18-0ubuntu4.4 1.6.18-0ubuntu4.5

  The day after, the servers were rebooted and the application
  containers running the OpenVPN instances failed to start:

  + lxc-execute -n network-vpn -f /server/network.vpn/lxc/lxc.conf -- 
/server/network.vpn/lxc/lxc-start.sh
  lxc-execute: utils.c: safe_mount: 1391 No such file or directory - Failed to 
mount proc onto /proc
  lxc-execute: conf.c: tmp_proc_mount: 4132 No such file or directory - failed 
to mount /proc in the container.
  lxc-execute: lsm/apparmor.c: apparmor_process_label_get: 80 No such file or 
directory - opening /proc/1/attr/current
  lxc-execute: lsm/apparmor.c: apparmor_process_label_set: 191 No such file or 
directory - failed to change apparmor profile to lxc-container-default
  lxc-execute: sync.c: __sync_wait: 57 An error occurred in another process 
(expected sequence number 5)
  lxc-execute: start.c: __lxc_start: 1149 failed to spawn 'network-vpn'
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to 
cgmanager_remove_sync failed: invalid request
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing 
hugetlb:lxc/network-vpn
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to 
cgmanager_remove_sync failed: invalid request
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing 
perf_event:lxc/network-vpn
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to 
cgmanager_remove_sync failed: invalid request
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing 
blkio:lxc/network-vpn
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to 
cgmanager_remove_sync failed: invalid request
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing 
freezer:lxc/network-vpn
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to 
cgmanager_remove_sync failed: invalid request
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing 
devices:lxc/network-vpn
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to 
cgmanager_remove_sync failed: invalid request
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing 
memory:lxc/network-vpn
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to 
cgmanager_remove_sync failed: invalid request
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing 
name=systemd:lxc/network-vpn
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to 
cgmanager_remove_sync failed: invalid request
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing 
cpuacct:lxc/network-vpn
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to 
cgmanager_remove_sync failed: invalid request
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing 
cpu:lxc/network-vpn
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to 
cgmanager_remove_sync failed: invalid request
  lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing 
cpuset:lxc/network-vpn

  We had to downgrade lxc, apparmor and related packages to the latest
  version from trusty-security instead of trusty-updates to get the VPN
  up and running again.

  Details:

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  Codename: trusty

  3.13.0-107-generic #154-Ubuntu SMP Tue Dec 20 09:57:27 UTC 2016 x86_64
  x86_64 x86_64 GNU/Linux

  Any clue about what's going on?

  Thanks,
  Alex

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1659590/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.

[Touch-packages] [Bug 1167014] Re: MIssing cmake files

2016-09-07 Thread linas
Recommend closing this bug...  Here's why.

TL;DR: libopencv-dev provides /usr/share/OpenCV/OpenCVConfig.cmake etc

I experienced a bizarre bug, though:

On xenial (16.04), having a CMakeLists.txt with a find_package(OpenCV
REQUIRED) gave me an error:

CMake Error at CMakeLists.txt:9 (find_package):
  By not providing "FindOpenCV.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "OpenCV", but
  CMake did not find one.

This error leads to a fruitless hunt for FindOpenCV.cmake which leads to
this bug report.  However, the above error should never have happened,
because xenial libopencv-dev does provide the needed files in
/usr/share/OpenCV/  The error went away, for me, after running  cmake
--trace and after that, the error goes away, and becomes
unreproducible(!) (despite being highly reproducible for hours...)  I'm
befuddled. However

TL;DR: libopencv-dev provides /usr/share/OpenCV/OpenCVConfig.cmake etc.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to opencv in Ubuntu.
https://bugs.launchpad.net/bugs/1167014

Title:
  MIssing cmake files

Status in opencv package in Ubuntu:
  Confirmed

Bug description:
  This two files are part of libopencv-core-dev package in 12.04:
  /usr/share/OpenCV/OpenCVConfig.cmake
  /usr/share/OpenCV/OpenCVConfig-version.cmake

  But they disappeared in 12.10 and 13.04.
  This is causing problems when compiling projects using cmake and opencv.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1167014/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1167014] Re: MIssing cmake files

2016-09-07 Thread linas
... except that /usr/share/OpenCV/ already contains the required files!
So, in principle, find_package(OpenCV REQUIRED) should just plain work.
So why doesn't it? ??

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to opencv in Ubuntu.
https://bugs.launchpad.net/bugs/1167014

Title:
  MIssing cmake files

Status in opencv package in Ubuntu:
  Confirmed

Bug description:
  This two files are part of libopencv-core-dev package in 12.04:
  /usr/share/OpenCV/OpenCVConfig.cmake
  /usr/share/OpenCV/OpenCVConfig-version.cmake

  But they disappeared in 12.10 and 13.04.
  This is causing problems when compiling projects using cmake and opencv.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1167014/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1167014] Re: MIssing cmake files

2016-09-07 Thread linas
... except that I am unable to find any version of FindOpenCV.cmake that
actually works with the OpenCV that is provided in trusty or xenial
(14.04 or 16.04) -- one of many problems is that the way that the opencv
version numbers are specified is not compatible with how version numbers
used to be specified(!)  After fixing this, additional bugs appear.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to opencv in Ubuntu.
https://bugs.launchpad.net/bugs/1167014

Title:
  MIssing cmake files

Status in opencv package in Ubuntu:
  Confirmed

Bug description:
  This two files are part of libopencv-core-dev package in 12.04:
  /usr/share/OpenCV/OpenCVConfig.cmake
  /usr/share/OpenCV/OpenCVConfig-version.cmake

  But they disappeared in 12.10 and 13.04.
  This is causing problems when compiling projects using cmake and opencv.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1167014/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1167014] Re: MIssing cmake files

2016-09-06 Thread linas
It appears that one can be downloaded from here:
http://code.opencv.org/attachments/196/FindOpenCV.cmake

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to opencv in Ubuntu.
https://bugs.launchpad.net/bugs/1167014

Title:
  MIssing cmake files

Status in opencv package in Ubuntu:
  Confirmed

Bug description:
  This two files are part of libopencv-core-dev package in 12.04:
  /usr/share/OpenCV/OpenCVConfig.cmake
  /usr/share/OpenCV/OpenCVConfig-version.cmake

  But they disappeared in 12.10 and 13.04.
  This is causing problems when compiling projects using cmake and opencv.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1167014/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1289094] Re: Could not find module FindOpenCV.cmake when compiling

2016-09-06 Thread linas
*** This bug is a duplicate of bug 1167014 ***
https://bugs.launchpad.net/bugs/1167014

** This bug has been marked a duplicate of bug 1167014
   MIssing cmake files

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to opencv in Ubuntu.
https://bugs.launchpad.net/bugs/1289094

Title:
  Could not find module FindOpenCV.cmake when compiling

Status in opencv package in Ubuntu:
  New

Bug description:
  Quoted from here: http://stackoverflow.com/questions/8711109/could-
  not-find-module-findopencv-cmake-error-in-configuration-
  process/22239942

  I had installed opencv from ubuntu 12.10 repository (libopencv-)* and
  had this problem:

  I wrote a CMakeLists.txt for a project in C++ (using ROS), which uses OpenCV 
libraries. When I try to create the project using cmake, I get the next 
configuration problem:
  "
  CMake Error at CMakeLists.txt:15 (find_package):
Could not find module FindOpenCV.cmake or a configuration file for package
OpenCV.

Adjust CMAKE_MODULE_PATH to find FindOpenCV.cmake or set OpenCV_DIR to the
directory containing a CMake configuration file for OpenCV.  The file will
have one of the following names:

  OpenCVConfig.cmake
  opencv-config.cmake
  "

  Couldn't solve it with export OpenCV_DIR=/usr/share/OpenCV/ (since my
  OpenCVConfig.cmake whas there). It was solved when I also changed some
  lines on the OpenCVConfig.cmake file:

  # ==
  # Include directories to add to the user project:
  # ==

  # Provide the include directories to the caller

  #SET(OpenCV_INCLUDE_DIRS
  "${OpenCV_INSTALL_PATH}/include/opencv;${OpenCV_INSTALL_PATH}/include")

  SET(OpenCV_INCLUDE_DIRS "/usr/include/opencv;/usr/include/opencv2")
  INCLUDE_DIRECTORIES(${OpenCV_INCLUDE_DIRS})

  # ==
  # Link directories to add to the user project:
  # ==

  # Provide the libs directory anyway, it may be needed in some cases.

  #SET(OpenCV_LIB_DIR "${OpenCV_INSTALL_PATH}/lib")

  SET(OpenCV_LIB_DIR "/usr/lib")

  LINK_DIRECTORIES(${OpenCV_LIB_DIR})

  And that worked on my Ubuntu 12.10. Remember to add the
  target_link_libraries(yourprojectname ${OpenCV_LIBS}) in your
  CMakeLists.txt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1289094/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1167014] Re: MIssing cmake files

2016-09-06 Thread linas
Hitting this in xenial, too.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to opencv in Ubuntu.
https://bugs.launchpad.net/bugs/1167014

Title:
  MIssing cmake files

Status in opencv package in Ubuntu:
  Confirmed

Bug description:
  This two files are part of libopencv-core-dev package in 12.04:
  /usr/share/OpenCV/OpenCVConfig.cmake
  /usr/share/OpenCV/OpenCVConfig-version.cmake

  But they disappeared in 12.10 and 13.04.
  This is causing problems when compiling projects using cmake and opencv.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1167014/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1406401] Re: Nouveau TTM Failed to find memory space for buffer

2015-02-23 Thread linas
Hi Christopher,

I spent 2 or 3 16-hour days trying to bisect this bug every-which way.
I eventually punted, and just bought a newer graphics card -- they're
cheap -- a few hundred $$ and that "fixed" the problem.

Summary: the old card works great under ubuntu 12.04 but has issues, as
described above, under 14.04

My debug efforts centered on doing a git-bisect of the kernel git
sources.  Somewhere early in the kernel-3.0 series, the card works fine.
Somwhere a bit before linux 3.13, the card either would not run X11 at
all (and hose the tty as well) or x11 would come up for a few hours, and
then hit the TTM messages.

I reported the git bisects  (two of them, one for each bug) to the
nouveau folks, but did not get impression that they were able to do
anything about it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1406401

Title:
  Nouveau TTM Failed to find memory space for buffer

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've been wrestling with a 3D graphics driver problem for the last few
  months, Perhaps its time to report it.

  This appears to be some sort of bad interaction between Xorg and the
  nouveau kernel drivers.  Similar bugs have been seen by others, on
  other OS'es and spcifically on other graphics cards (e.g. Radeon).
  Seem to be few/no reports for nouveau.

  Symptoms: X11 background fails to repaint. Eventually X11 becomes
  unresponsive. Sometimes restarting X is enough to defer the problem,
  sometimes a reboot is required. Usually takes a week or so for the
  problem to recurr.  dmesg and /var/log/syslog fill up with vast
  numbers of this:

  
  Dec 29 14:30:17 fanny kernel: [258314.187016] [TTM] Failed to find memory 
space for buffer 0x
  880808666c00 eviction
  Dec 29 14:30:17 fanny kernel: [258314.187022] [TTM] No space for 
880808666c00 (884 pages,
   3536K, 3M)
  Dec 29 14:30:17 fanny kernel: [258314.187024] [TTM]   placement[0]=0x00070002 
(1)
  Dec 29 14:30:17 fanny kernel: [258314.187026] [TTM] has_type: 1
  Dec 29 14:30:17 fanny kernel: [258314.187027] [TTM] use_type: 1
  Dec 29 14:30:17 fanny kernel: [258314.187028] [TTM] flags: 0x000A
  Dec 29 14:30:17 fanny kernel: [258314.187030] [TTM] gpu_offset: 0x
  Dec 29 14:30:17 fanny kernel: [258314.187031] [TTM] size: 131072
  Dec 29 14:30:17 fanny kernel: [258314.187032] [TTM] available_caching: 
0x0007
  Dec 29 14:30:17 fanny kernel: [258314.187034] [TTM] default_caching: 
0x0001
  Dec 29 14:30:17 fanny kernel: [258314.187037] nouveau E[Xorg[2474]] fail 
ttm_validate
  Dec 29 14:30:17 fanny kernel: [258314.187039] nouveau E[Xorg[2474]] validate 
vram_list
  Dec 29 14:30:17 fanny kernel: [258314.187042] nouveau E[Xorg[2474]] validate: 
-12

  TTM appears to be a kernel module that performs memory management of
  the memory on the graphics card.  presuably X11 and/or Mesa is failing
  to release unused memory.

  My setup is unusual: I am using TWO graphics cards, not one:

  01:03.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] 
(rev a1)
  02:00.0 VGA compatible controller: NVIDIA Corporation G72 [GeForce 7300 LE] 
(rev a1)

  It appears only the second one is affected, as that is where the
  visual symptoms show up.

  Setup has three! monitors.  Xrandr is NOT running, since Xrandr
  appears to be unable to deal with the monitor setup (two of the
  monitors are rotated, the third is not; this seems to drive xrandr
  crazy, so it does not come up).  I mention this only because I'm
  wondering if the graphics card RAM me=nagement is done differrently if
  xrandr is present.

  Kernel is the stock kernel:
  Linux version 3.13.0-40-generic (buildd@comet) (gcc version 4.8.2 (Ubuntu 
4.8.2-19ubuntu1) ) #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014

  System has 32GB RAM.   Here is some more random info:
  From the boot dmesg:
  [   29.506436] nouveau  [  DEVICE][:02:00.0] BOOT0  : 0x046100a3
  [   29.506471] nouveau  [  DEVICE][:02:00.0] Chipset: G72 (NV46)
  [   29.506503] nouveau  [  DEVICE][:02:00.0] Family : NV40
  [   29.507685] nouveau  [   VBIOS][:02:00.0] checking PRAMIN for image...
  [   29.602531] nouveau  [   VBIOS][:02:00.0] ... appears to be valid
  [   29.602559] nouveau  [   VBIOS][:02:00.0] using image from PRAMIN
  [   29.602696] nouveau  [   VBIOS][:02:00.0] BIT signature found
  [   29.602721] nouveau  [   VBIOS][:02:00.0] version 05.72.22.49.09
  [   29.602941] nouveau :02:00.0: irq 79 for MSI/MSI-X
  [   29.602950] nouveau  [ PMC][:02:00.0] MSI interrupts enabled
  [   29.603001] nouveau  [ PFB][:02:00.0] RAM type: DDR2
  [   29.603024] nouveau  [ PFB][:02:00.0] RAM size: 128 MiB
  [   29.603047] nouveau  [ PFB][:02:00.0]ZCOMP: 0 tags
  [   29.643916] nouveau  [  PTHERM][:02:00.0] FAN control: none / external

[Touch-packages] [Bug 1421760] [NEW] /usr/bin/env hangs when a variable is set

2015-02-13 Thread linas
Public bug reported:

/usr/bin/env hangs when a variable is set. To reproduce this,  create a
file with the following contents:

 #!/usr/bin/env A=B python

; !#
(display "wtf")
(newline)

lets say the file was "wtf.sh". Then chmod ugo+x wtf.sh  and then
execute it:  ./wtf.sh   This will hang and spin and burn cpu time.
Removing the A=B  will cause the script to run just fine (and spew
errors, because the conents is not valid python, but that's OK.  Instead
of python, you could say guile. Its valuid guile. Or you could say bash.
whatever, it does not matter)

According to gdb, it is stuck in an infinite loop in the dynamic linker-
loader, where /usr/bin/env is calling itself over and over.

I can't quite tell if this is a bug in env, or in ld.so or in thelinux
kernel.  FWIW #!/usr/bin/env  python  42  also gives unexpeted results:
it searches for the interpreter "python 42" instead of searching for
"python" and passing it the argument "42".  Also the following does not
work:   #!/usr/bin/env  -i python -- it spews an error about the -i
flag.

This is on both trusty and precise

Attaching gdb to the hung pid gives the following:

gdb -p 27957
(gdb) bt
#0  0x7fa5286c92d0 in _start () from /lib64/ld-linux-x86-64.so.2
#1  0x0003 in ?? ()
#2  0x7fff36b5ac89 in ?? ()
#3  0x7fff36b5ac96 in ?? ()
#4  0x7fff36b5aca0 in ?? ()
#5  0x in ?? ()
(gdb) c
Continuing.
process 27957 is executing new program: /usr/bin/env
process 27957 is executing new program: /usr/bin/env
process 27957 is executing new program: /usr/bin/env
...
ctrl-C
^C__GI__dl_debug_state () at dl-debug.c:74
74  dl-debug.c: No such file or directory.
Quit
(gdb) bt
#0  __GI__dl_debug_state () at dl-debug.c:74
#1  0x7f7292b3396a in dl_main (phdr=, phdr@entry=0x400040, 
phnum=, phnum@entry=9, 
user_entry=user_entry@entry=0x7fff11adf818, auxv=)
at rtld.c:2305
#2  0x7f7292b47565 in _dl_sysdep_start (
start_argptr=start_argptr@entry=0x7fff11adf900, 
dl_main=dl_main@entry=0x7f7292b31910 ) at ../elf/dl-sysdep.c:249
#3  0x7f7292b34cf8 in _dl_start_final (arg=0x7fff11adf900) at rtld.c:332
#4  _dl_start (arg=0x7fff11adf900) at rtld.c:558
#5  0x7f7292b312d8 in _start () from /lib64/ld-linux-x86-64.so.2
#6  0x0003 in ?? ()
#7  0x7fff11ae0c89 in ?? ()
#8  0x7fff11ae0c96 in ?? ()
#9  0x7fff11ae0ca0 in ?? ()
#10 0x in ?? ()
(gdb) c
Continuing.
process 27957 is executing new program: /usr/bin/env
process 27957 is executing new program: /usr/bin/env
process 27957 is executing new program: /usr/bin/env
process 27957 is executing new program: /usr/bin/env
process 27957 is executing new program: /usr/bin/env
^C__GI__dl_debug_state () at dl-debug.c:74
74  dl-debug.c: No such file or directory.
Quit
(gdb) Quit
(gdb) Quit
(gdb) bt
#0  __GI__dl_debug_state () at dl-debug.c:74
#1  0x7f990150396a in dl_main (phdr=, phdr@entry=0x400040, 
phnum=, phnum@entry=9, 
user_entry=user_entry@entry=0x7fff61a966a8, auxv=)
at rtld.c:2305
#2  0x7f9901517565 in _dl_sysdep_start (
start_argptr=start_argptr@entry=0x7fff61a96790, 
dl_main=dl_main@entry=0x7f9901501910 ) at ../elf/dl-sysdep.c:249
#3  0x7f9901504cf8 in _dl_start_final (arg=0x7fff61a96790) at rtld.c:332
#4  _dl_start (arg=0x7fff61a96790) at rtld.c:558
#5  0x7f99015012d8 in _start () from /lib64/ld-linux-x86-64.so.2
#6  0x0003 in ?? ()
#7  0x7fff61a97c89 in ?? ()
#8  0x7fff61a97c96 in ?? ()
#9  0x7fff61a97ca0 in ?? ()
#10 0x in ?? ()

** Affects: coreutils (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1421760

Title:
  /usr/bin/env hangs when a variable is set

Status in coreutils package in Ubuntu:
  New

Bug description:
  /usr/bin/env hangs when a variable is set. To reproduce this,  create
  a file with the following contents:

   #!/usr/bin/env A=B python

  ; !#
  (display "wtf")
  (newline)

  lets say the file was "wtf.sh". Then chmod ugo+x wtf.sh  and then
  execute it:  ./wtf.sh   This will hang and spin and burn cpu time.
  Removing the A=B  will cause the script to run just fine (and spew
  errors, because the conents is not valid python, but that's OK.
  Instead of python, you could say guile. Its valuid guile. Or you could
  say bash. whatever, it does not matter)

  According to gdb, it is stuck in an infinite loop in the dynamic
  linker-loader, where /usr/bin/env is calling itself over and over.

  I can't quite tell if this is a bug in env, or in ld.so or in thelinux
  kernel.  FWIW #!/usr/bin/env  python  42  also gives unexpeted
  results: it searches for the interpreter "python 42" instead of
  searching for "python" and passing it the argument "42".  Also the
  following does not work:   #!/usr/bin/env  -i python -- it spews an
  err

[Touch-packages] [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

2014-12-05 Thread linas
I woke up this morning, and I get this error message.  What happened?

-- it was working last night.
-- ssh-add -l says everything is there.
-- above means that ssh-agent is running
-- contents of /tmp and /tmp/keyring-XXX look OK
-- SSH_AUTH_SOCK=0 ssh wherever works

System: ubuntu 14.04
Uptime: about a month

Why is something that worked fine for a month suddenly stop working in
the morning?

-- 
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/201786

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

Status in Seahorse:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Triaged
Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  on hardy (preserved home folder from feisty) i get the following when
  i try to ssh

  Agent admitted failure to sign using the key.
  Permission denied (publickey).

  or with verbose on

  sam@titania:~$ ssh -v oberon
  OpenSSH_4.7p1 Debian-4ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
  debug1: Reading configuration data /home/sam/.ssh/config
  debug1: Applying options for oberon
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: Applying options for *
  debug1: Connecting to ## [##] port ##.
  debug1: Connection established.
  debug1: identity file /home/sam/.ssh/identity type -1
  debug1: identity file /home/sam/.ssh/id_rsa type 1
  debug1: identity file /home/sam/.ssh/id_dsa type -1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_4.6p1 
Debian-5ubuntu0.1
  debug1: match: OpenSSH_4.6p1 Debian-5ubuntu0.1 pat OpenSSH*
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-4ubuntu1
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: server->client aes128-cbc hmac-md5 none
  debug1: kex: client->server aes128-cbc hmac-md5 none
  debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
  debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
  debug1: using hostkeyalias: oberon
  debug1: Host 'oberon' is known and matches the RSA host key.
  debug1: Found key in /home/sam/.ssh/known_hosts:1
  debug1: ssh_rsa_verify: signature correct
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_SERVICE_REQUEST sent
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey
  debug1: Next authentication method: publickey
  debug1: Offering public key: /home/sam/.ssh/id_rsa
  debug1: Server accepts key: pkalg ssh-rsa blen 277
  Agent admitted failure to sign using the key.
  debug1: Trying private key: /home/sam/.ssh/identity
  debug1: Trying private key: /home/sam/.ssh/id_dsa
  debug1: No more authentication methods to try.
  Permission denied (publickey).

  I tried generating a new key. this worked for a few logons, but then i
  get back to this error.

  I think it is to do with the local key agent. i found that
   SSH_AUTH_SOCK=0 ssh oberon
  works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1375921] Re: libedit should be updated to wchar_t capable version from debian 3.1-20140620-2

2014-11-16 Thread linas
Basically, this means that there's no utf8 support, which means that
almost any non-Eglish language  fails.

Appearently, this was/is a package build bug; the support was always
there in the sources, and was just not being built for the package.

typical symptoms:
nm /usr/lib/x86_64-linux-gnu/libedit.a |grep el_wgets reveals nothing, 

likewise a grep for  history_w history_winit el_wset history_wend and so
on, all of which are in the header file /usr/include/editline/readline.h

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libedit in Ubuntu.
https://bugs.launchpad.net/bugs/1375921

Title:
  libedit should be updated to wchar_t capable version from debian
  3.1-20140620-2

Status in “libedit” package in Ubuntu:
  Confirmed

Bug description:
  Current libedit claims to have wchar_t support in its changelog but
  doesn't, as per this bug on the debian bug tracker:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756736

  The debian package has been fixed and the package minor version
  updated, it'd be really nice to get this into ubuntu as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1375921/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1222791] Re: 1002:94c3 (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed

2014-08-30 Thread linas
Please also see https://bugs.launchpad.net/ubuntu/+source/linux-lts-
raring/+bug/1097178

These Xorg errors seem to be a side-effect of X hanging in
uninteruptible sleep, in the kernel: i.e. a nouveau kernel module issue.
At least for me. See the bug I just quoted for details.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1222791

Title:
  1002:94c3 (EE) [mi] EQ overflowing. Additional events will be
  discarded until existing events are processed

Status in “xorg” package in Ubuntu:
  Expired

Bug description:
  Random screen freezes (see also 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1184451).
  Sometimes system is hanging and it looks like swapping is active (but swap is 
disabled completely), no response to either mouse/keyboard. Switching to 
terminals (Ctrl+Alt+F1-F6) and Alt+SysRq is still working. In Xorh.0.log there 
are next messages:

  [258008.925] [mi] EQ overflowing.  Additional events will be discarded until 
existing events are processed.
  [258009.690] [mi] These backtraces from mieqEnqueue may point to a culprit 
higher up the stack.
  [258009.690] [mi] mieq is *NOT* the cause.  It is a victim.
  [258009.690] [mi] Increasing EQ size to 512 to prevent dropped events.
  [258009.691] [mi] EQ processing has resumed after 67 dropped events.
  [258009.691] [mi] This may be caused my a misbehaving driver monopolizing the 
server's resources.

  I use radeon driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,compiztoolbox,move,gnomecompat,snap,imgpng,regex,animation,grid,mousepoll,place,obs,resize,expo,wall,workarounds,session,fade,ezoom,scale]
  CompositorRunning: None
  Date: Mon Sep  9 16:00:46 2013
  DistUpgraded: 2013-05-24 14:43:41,354 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI RV610 [Radeon HD 2400 PRO] [1002:94c3] 
(prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited Device [174b:e370]
  InstallationDate: Installed on 2011-01-28 (954 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic 
root=UUID=172134af-724c-40b6-a610-6c2214bca596 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to raring on 2013-05-24 (108 days ago)
  dmi.bios.date: 11/08/2005
  dmi.bios.vendor: Award BIOS for Intel
  dmi.bios.version: GC11010N.86A.0303.2005.1108.2057
  dmi.board.name: D101GGC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD35788-304
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardBIOSforIntel:bvrGC11010N.86A.0303.2005.1108.2057:bd11/08/2005:svn:pn:pvr:rvnIntelCorporation:rnD101GGC:rvrAAD35788-304:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
  version.libdrm2: libdrm2 2.4.43-0ubuntu1.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 3:1.12.4+git20121105-makson1~ppa2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
2:2.7.3+git20120928~quantal2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
2:6.14.6+git20120928~quantal1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
3:2.20.8+git20120928~quantal2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Sep  6 15:23:51 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 3:1.12.4+git20121105-makson1~ppa2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1222791/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp