date:20161130

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
   X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Expired

Bug description:
  not all the time, but at some suspend/resume operations fonts disapear from 
gnome terminal, nm-applet and soffice which then show spaces and underscore 
placeholders instead of characters.
  google chrome, thunderbird, firefox, virtualbox are not affected.
  As it happens not at each suspend resume I find it hard to diagnose what is 
going wrong.
  next time I will launch more apps to see wich ones are affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   /dev/sdb1: clean, 505825/14589952 files, 3844900/58349824 blocks
   [[0;1;31mFAILED[0m] Failed to start Automatically refresh installed snaps.
   See 'systemctl status snapd.refresh.service' for details.
   [[0;32m  OK  [0m] Started Detect the available GPUs and deal with any 
system changes.
Starting Light Display Manager...
  CompizPlugins:
   (gconftool-2:18460): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
   Failed to connect to socket /tmp/dbus-NG2bGyKMRZ: Connection refused
   Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: None
  CurrentDesktop: i3
  Date: Wed Sep 21 23:41:50 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:6504]
  InstallationDate: Installed on 2016-07-27 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook W65_67SZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ef4d32b1-8cd0-4f61-9e8e-a0a191b86e14 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05SB.02
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05SB.02:bd08/26/2015:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Sep 21 23:08:03 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5941 
   vendor CMN
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626288/+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 1629365] Re: In response of Bug #1551982

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  In response of Bug #1551982

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Mr Scott Stensland, Thanks for your interest in this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Sep 30 10:14:01 2016
  DistUpgraded: 2016-04-30 05:14:03,198 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [1043:844d]
  InstallationDate: Installed on 2016-01-25 (249 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=ba786508-17d0-4fdf-bcd2-125ae6c7fb76 ro splash quiet plymouth:debug=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (153 days ago)
  dmi.bios.date: 10/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX3 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd10/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Sep 30 10:09:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 891 
   vendor SAM
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629365/+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 1646341] [NEW] Placing calls with priximity sensor

2016-11-30 Thread Tuomas Pylkkö

Public bug reported:

This might be something easy to implement, butthat would help users
much. Change the app so that when user is browsing through contacts and
selects one, if then at that moment proximity sensor realizes that user
has put phone against head, place call. Currently user needs to select
contact with button which throws the contact info into dialer and then
again press another button to place the call. Thats two more touchscreen
button clicks than on, say, Android.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: dialer-app 0.1+15.04.20160825.2-0ubuntu1
Uname: Linux 3.10.35+ armv7l
ApportVersion: 2.17.2-0ubuntu1.3touch1
Architecture: armhf
CurrentDesktop: Unity
Date: Wed Nov 30 22:12:53 2016
InstallationDate: Installed on 2016-09-13 (78 days ago)
InstallationMedia: Ubuntu 15.04 - armhf (20160913-023544)
SourcePackage: dialer-app
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug armhf vivid

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

Title:
  Placing calls with priximity sensor

Status in dialer-app package in Ubuntu:
  New

Bug description:
  This might be something easy to implement, butthat would help users
  much. Change the app so that when user is browsing through contacts
  and selects one, if then at that moment proximity sensor realizes that
  user has put phone against head, place call. Currently user needs to
  select contact with button which throws the contact info into dialer
  and then again press another button to place the call. Thats two more
  touchscreen button clicks than on, say, Android.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dialer-app 0.1+15.04.20160825.2-0ubuntu1
  Uname: Linux 3.10.35+ armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Wed Nov 30 22:12:53 2016
  InstallationDate: Installed on 2016-09-13 (78 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160913-023544)
  SourcePackage: dialer-app
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1646341/+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 1644062] Re: googletest 1.8.0-2 (on zesty) breaks existing builds [add_library cannot create target "gmock" ...]

This bug was fixed in the package content-hub -
0.2+17.04.20161128-0ubuntu1

---
content-hub (0.2+17.04.20161128-0ubuntu1) zesty; urgency=medium

  * Fix build failure on zesty due to googletest 1.8. Also refactored
tests/acceptance-tests/CMakeLists.txt to make adding tests less
cumbersome. (LP: #1644062)

 -- Ken VanDine   Mon, 28 Nov 2016 17:39:58
+

** Changed in: content-hub (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
  cannot create target "gmock" ...]

Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Fix Committed
Status in cmake-extras package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu:
  Fix Released
Status in googletest package in Ubuntu:
  Won't Fix
Status in mir package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  In Progress

Bug description:
  After upgrading to 1.8.0-2 (from 1.7.0-4), our previously-working
  builds break:

  CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock" because another target with the
 same name already exists.  The existing target is a static library created
 in source directory "/usr/src/googletest/googlemock".  See documentation
 for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:84 (cxx_library)


   CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock_main" because another target with
 the same name already exists.  The existing target is a static library
 created in source directory "/usr/src/googletest/googlemock".  See
 documentation for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:89 (cxx_library)


   CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
 install TARGETS given target "gmock" which does not exist in this
 directory.

  The CMakeLists.txt in our project that triggers this error does this:

  set(old_cxx_flags ${CMAKE_CXX_FLAGS})
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -Wno-old-style-cast 
-Wno-missing-field-initializers")
  find_package(GMock)
  set(CMAKE_CXX_FLAGS ${old_cxx_flags})

  This used to work fine, but no breaks on zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644062/+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 1641243] Re: Provide full AppArmor confinement for snaps on 14.04

2016-11-30 Thread Tyler Hicks

** Description changed:

  = apparmor SRU =
  [Rationale]
  For backporting snapd to 14.04 LTS, we need to provide proper AppArmor 
confinement for snaps when running under the 16.04 hardware enablement kernel. 
The apparmor userspace package in 14.04 is missing support key mediation 
features such as UNIX domain socket rules, AppArmor policy namespaces, and 
AppArmor profile stacking. UNIX domain socket mediation is needed by nearly all 
snaps. AppArmor policy namespaces and profile stacking are needed by the lxd 
snap.
  
  Unfortunately, it was not feasible to backport the individual features
  to the 14.04 apparmor package as they're quite complex and have a large
  number of dependency patches. Additionally, the AppArmor policy
  abstractions from Ubuntu 16.04 are needed to provide proper snap
  confinement. Because of these two reasons, the decision to bring 16.04's
  apparmor package to 14.04 was (very carefully) made.
  
  [Test Case]
  
    https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
  
  This update will go through the Test Plan as well as manual testing to
  verify that snap confinement on 14.04 does work. Manual tests include
  installing snapd in 14.04 and running simple snaps such as pwgen-tyhicks
  and hello-world, as well as a much more complex snap such as lxd.
  
  The following regression tests from lp:qa-regression-testing (these
  packages ship an AppArmor profile) can be used to verify that their
  respective packages do not regress:
  
   test-apache2-mpm-event.py
   test-apache2-mpm-itk.py
   test-apache2-mpm-perchild.py
   test-apache2-mpm-prefork.py
   test-apache2-mpm-worker.py
   test-bind9.py
   test-clamav.py
   test-cups.py
   test-dhcp.py
   test-mysql.py
   test-ntp.py
   test-openldap.py
   test-rsyslog.py
   test-squid.py
   test-strongswan.py
   test-tcpdump.py
  
  I have a branch of lp:qa-regression-testing (unmerged, currently at
  https://code.launchpad.net/~tyhicks/+git/qa-regression-testing/+ref
  /apparmor-trusty-sru) that pulls in the parser and regression tests from
  the apparmor 2.8.95~2430-0ubuntu5.3 package currently shipping in
  Trusty, in addition to the tests in the 2.10.95 based package.
  
  Additionally, manually testing evince, which is confined by an AppArmor
  profile, should be done. The manual test should check basic
  functionality as well as for proper confinement (`ps auxZ` output).
  
  [Regression Potential]
  High. We must be extremely careful to not regress existing, confined 
applications in Ubuntu 14.04. We are lucky that the upstream AppArmor project 
has extensive regression tests and that the Ubuntu Security team adds even more 
testing via the AppArmor Test Plan.
  
  Care was taken to minimally change how the AppArmor policies are loaded
  during the boot process. I also verified that the abstractions shipped
  in apparmor and the profiles shipped in apparmor-profiles are the same
  across this SRU update.
  
  = dbus SRU =
  [Rationale]
  For backporting snapd to 14.04 LTS, we need to provide proper D-Bus mediation 
for snaps when running under the 16.04 hardware enablement kernel. The dbus 
package in 14.04 is missing support for blocking unrequested reply messages. 
This functionality was added to the D-Bus AppArmor mediation patches after 
14.04 was released but before the patches were merged upstream in dbus. The 
idea is to prevent a malicious snap from attacking another snap, over D-Bus, 
with unrequested reply messages and also to prevent two connections from 
subverting the snap confinement by communicating via unrequested reply messages.
  
  [Test Case]
  
  The upstream AppArmor userspace project has thorough tests for D-Bus
  mediation, including unrequested replies. Its
  tests/regression/apparmor/dbus_*.sh tests should be ran before and after
  updating to the dbus SRU. Before updating, the dbus_unrequested_reply.sh
  should fail and should pass after updating.
  
+ To run the dbus_*.sh tests:
+ 
+ $ sudo apt-get install -y bzr libdbus-1-dev
+ $ bzr branch lp:apparmor # apt-get source apparmor to test the current 
apparmor
+ $ cd apparmor/tests/regression/apparmor/
+ $ make USE_SYSTEM=1 \
+   dbus_{eavesdrop,message,service,unrequested_reply} uservars.inc
+ $ for t in dbus_{eavesdrop,message,service,unrequested_reply}.sh; \
+   do sudo VERBOSE=1 bash $t || break; done
+ 
+ The exit code should be 0 and all output lines should start with "ok:".
+ 
  In addition, the test-dbus.py tests from lp:qa-regression-testing should
  be ran to verify basic D-Bus functionality.
  
  This update will go through the Test Plan as well as manual testing to
  verify that snap confinement on 14.04 does work. Manual tests include
  installing snapd in 14.04 and running simple snaps such as pwgen-tyhicks
  and hello-world, as well as a much more complex snap such as lxd.
  
  [Regression Potential]
  Low. There's no use for unrequested D-Bus reply messages and silently 
dropping them for AppArmor confined applications

[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-11-30 Thread Michi Henning

I've added Pawel because of the "Invalid departments database" error.

I'm looking at the other errors. I suspect what's happening is that some
of the local socket path names are wrong.

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  New

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645798/+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 1641243] Re: Provide full AppArmor confinement for snaps on 14.04

2016-11-30 Thread Tyler Hicks

Moving the apparmor task back to "incomplete" while I gather info for
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628285/comments/10.

** Description changed:

+ = apparmor SRU =
  [Rationale]
  For backporting snapd to 14.04 LTS, we need to provide proper AppArmor 
confinement for snaps when running under the 16.04 hardware enablement kernel. 
The apparmor userspace package in 14.04 is missing support key mediation 
features such as UNIX domain socket rules, AppArmor policy namespaces, and 
AppArmor profile stacking. UNIX domain socket mediation is needed by nearly all 
snaps. AppArmor policy namespaces and profile stacking are needed by the lxd 
snap.
  
  Unfortunately, it was not feasible to backport the individual features
  to the 14.04 apparmor package as they're quite complex and have a large
  number of dependency patches. Additionally, the AppArmor policy
  abstractions from Ubuntu 16.04 are needed to provide proper snap
  confinement. Because of these two reasons, the decision to bring 16.04's
  apparmor package to 14.04 was (very carefully) made.
  
  [Test Case]
  
    https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
  
  This update will go through the Test Plan as well as manual testing to
  verify that snap confinement on 14.04 does work. Manual tests include
  installing snapd in 14.04 and running simple snaps such as pwgen-tyhicks
  and hello-world, as well as a much more complex snap such as lxd.
  
  The following regression tests from lp:qa-regression-testing (these
  packages ship an AppArmor profile) can be used to verify that their
  respective packages do not regress:
  
   test-apache2-mpm-event.py
   test-apache2-mpm-itk.py
   test-apache2-mpm-perchild.py
   test-apache2-mpm-prefork.py
   test-apache2-mpm-worker.py
   test-bind9.py
   test-clamav.py
   test-cups.py
   test-dhcp.py
   test-mysql.py
   test-ntp.py
   test-openldap.py
   test-rsyslog.py
   test-squid.py
   test-strongswan.py
   test-tcpdump.py
  
  I have a branch of lp:qa-regression-testing (unmerged, currently at
  https://code.launchpad.net/~tyhicks/+git/qa-regression-testing/+ref
  /apparmor-trusty-sru) that pulls in the parser and regression tests from
  the apparmor 2.8.95~2430-0ubuntu5.3 package currently shipping in
  Trusty, in addition to the tests in the 2.10.95 based package.
  
  Additionally, manually testing evince, which is confined by an AppArmor
  profile, should be done. The manual test should check basic
  functionality as well as for proper confinement (`ps auxZ` output).
  
  [Regression Potential]
  High. We must be extremely careful to not regress existing, confined 
applications in Ubuntu 14.04. We are lucky that the upstream AppArmor project 
has extensive regression tests and that the Ubuntu Security team adds even more 
testing via the AppArmor Test Plan.
  
  Care was taken to minimally change how the AppArmor policies are loaded
  during the boot process. I also verified that the abstractions shipped
  in apparmor and the profiles shipped in apparmor-profiles are the same
  across this SRU update.
+ 
+ = dbus SRU =
+ [Rationale]
+ For backporting snapd to 14.04 LTS, we need to provide proper D-Bus mediation 
for snaps when running under the 16.04 hardware enablement kernel. The dbus 
package in 14.04 is missing support for blocking unrequested reply messages. 
This functionality was added to the D-Bus AppArmor mediation patches after 
14.04 was released but before the patches were merged upstream in dbus. The 
idea is to prevent a malicious snap from attacking another snap, over D-Bus, 
with unrequested reply messages and also to prevent two connections from 
subverting the snap confinement by communicating via unrequested reply messages.
+ 
+ [Test Case]
+ 
+ The upstream AppArmor userspace project has thorough tests for D-Bus
+ mediation, including unrequested replies. Its
+ tests/regression/apparmor/dbus_*.sh tests should be ran before and after
+ updating to the dbus SRU. Before updating, the dbus_unrequested_reply.sh
+ should fail and should pass after updating.
+ 
+ In addition, the test-dbus.py tests from lp:qa-regression-testing should
+ be ran to verify basic D-Bus functionality.
+ 
+ This update will go through the Test Plan as well as manual testing to
+ verify that snap confinement on 14.04 does work. Manual tests include
+ installing snapd in 14.04 and running simple snaps such as pwgen-tyhicks
+ and hello-world, as well as a much more complex snap such as lxd.
+ 
+ [Regression Potential]
+ Low. There's no use for unrequested D-Bus reply messages and silently 
dropping them for AppArmor confined applications should have no unintended side 
effects. The unrequested reply protections have been present in releases after 
14.04 and have not caused any issues.

** Changed in: apparmor (Ubuntu Trusty)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed

[Touch-packages] [Bug 1591354] Re: [tests] given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset fails

2016-11-30 Thread Daniel van Vugt

Now in bug 1646302

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

Title:
  [tests]
  
given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
  fails

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  18:48:48 13: [ RUN ] 
NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
  ...
  18:48:51 13: [2016-06-10 18:48:50.931481] mirserver: Logical position +0+0
  18:48:52 13: 
/��BUILDDIR��/mir-0.23.0+xenial1328bzr3533/tests/acceptance-tests/test_nested_mir.cpp:1135:
 Failure
  18:48:52 13: Value of: condition.raised()
  18:48:52 13: Actual: false
  18:48:52 13: Expected: true
  18:48:52 13: 
/��BUILDDIR��/mir-0.23.0+xenial1328bzr3533/tests/acceptance-tests/test_nested_mir.cpp:1129:
 Failure
  18:48:52 13: Actual function call count doesn't match 
EXPECT_CALL(*the_mock_display_configuration_report(), 
new_configuration(mt::DisplayConfigMatches(expected_config)))...
  18:48:52 13: Expected: to be called once
  18:48:52 13: Actual: never called - unsatisfied and active
  18:48:52 13: [2016-06-10 18:48:52.115583] mirserver: Stopping
  18:48:52 13: [2016-06-10 18:48:52.280421] mirserver: Stopping
  18:48:52 13: [ FAILED ] 
NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
 (3916 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial/1297/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1591354/+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 1591354] Re: [tests] given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset fails

2016-11-30 Thread Daniel van Vugt

This one was Fix Released some months ago so it's more appropriate to
make a new bug...

** Changed in: mir
   Status: Confirmed => Fix Released

** Changed in: mir (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [tests]
  
given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
  fails

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  18:48:48 13: [ RUN ] 
NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
  ...
  18:48:51 13: [2016-06-10 18:48:50.931481] mirserver: Logical position +0+0
  18:48:52 13: 
/��BUILDDIR��/mir-0.23.0+xenial1328bzr3533/tests/acceptance-tests/test_nested_mir.cpp:1135:
 Failure
  18:48:52 13: Value of: condition.raised()
  18:48:52 13: Actual: false
  18:48:52 13: Expected: true
  18:48:52 13: 
/��BUILDDIR��/mir-0.23.0+xenial1328bzr3533/tests/acceptance-tests/test_nested_mir.cpp:1129:
 Failure
  18:48:52 13: Actual function call count doesn't match 
EXPECT_CALL(*the_mock_display_configuration_report(), 
new_configuration(mt::DisplayConfigMatches(expected_config)))...
  18:48:52 13: Expected: to be called once
  18:48:52 13: Actual: never called - unsatisfied and active
  18:48:52 13: [2016-06-10 18:48:52.115583] mirserver: Stopping
  18:48:52 13: [2016-06-10 18:48:52.280421] mirserver: Stopping
  18:48:52 13: [ FAILED ] 
NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
 (3916 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial/1297/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1591354/+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 1627697] Re: gnome-terminal crashes on resize

2016-11-30 Thread Daniel van Vugt

Yeah seems to work on zesty. Although only as a regular user (not sudo)
and with a mountain of GTK warnings.

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: Confirmed => Fix Released

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

Title:
  gnome-terminal crashes on resize

Status in MirAL:
  Fix Released
Status in Ubuntu:
  Fix Released

Bug description:
  Yakkety, Mir-0.24, lp:miral

  Run gnome-terminal on a touchscreen laptop and resizing by three-
  finger pinch...

  $ miral-run gnome-terminal
  $ 
  (gnome-terminal-server:4817): Gtk-WARNING **: GtkSettings Cursor Theme: 
Unsupported GDK backend
  ...
  (gnome-terminal-server:4817): Gdk-WARNING **: unknown property 
gtk-fontconfig-timestamp

  (gnome-terminal-server:4817): Gdk-WARNING **: Ignoring unknown Mir
  event 11

  (gnome-terminal-server:4817): Gtk-WARNING **: Allocating size to GtkBox 
0x55eb906c6900 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  *** Error in `/usr/lib/gnome-terminal/gnome-terminal-server': double free or 
corruption (out): 0x7f2e70258010 ***

  (Can't reproduce with Mir-0.1, but that may be because resize was too
  broken.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/miral/+bug/1627697/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-11-30 Thread Anthony Ledford

Terminal output:

lpstat -v
device for Brother-HL-2270DW-series: 
dnssd://Brother%20HL-2270DW%20series._pdl-datastream._tcp.local/

lpstat -o outputs nothing, there are no jobs in queue

cupsd.conf attached.


** Attachment added: "location /etc/cups"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+attachment/4785505/+files/cupsd.conf

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1645501] Re: corefiles not created in armhf chroot on arm64 porter

2016-11-30 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  corefiles not created in armhf chroot on arm64 porter

Status in gdb package in Ubuntu:
  Triaged

Bug description:
  I'm filing this about gdb per Steve's suggestion, although this could
  be an issue somewhere else.

  I recently discovered that the apport-test-crash
  (https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment
  /test-crashes) crash files produced for armhf are crash files without
  CoreDumps.  This happened sometime between 20160531 and 20161025.
  I've recreated this on the porter-arm64 box with the following minimal
  test case (generate-sigsegv-crash.py is from apport-test-crashes):

  schroot -c yakkety-armhf
  python generate-sigsegv-crash.py cat

  Running this on both armhf and arm64 we can see the following
  different output.

  armhf chroot on porter-armhf:

47 Program received signal SIGSEGV, Segmentation fault.
48 0xb6f599e4 in read () at ../sysdeps/unix/syscall-template.S:84
49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core

  armhf chroot on porter-arm64:

47 Program received signal SIGSEGV, Segmentation fault.
48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
50 (gdb) Unable to fetch the floating point registers.: Invalid argument.

  Notice how there is no core file save on porter-arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1645501/+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 1507469] Re: Evince's Apparmour profile prevents opening docs from other apps under Wayland

2016-11-30 Thread Steve Beattie

** Changed in: apparmor
Milestone: None => 2.11

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

Title:
  Evince's Apparmour profile prevents opening docs from other apps under
  Wayland

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Evince fails to run when launched from another app (Nautilus, Ephy,
  etc) and running under Wayland. For example, nothing appears to happen
  when double-clicking on a PDF file in Nautilus. Evince is launched,
  but its Apparmour profile is preventing access to a Wayland socket,
  hence it immediately exits.

  The following is typical of the reported error:

  > Oct 19 15:06:40 payens kernel: audit: type=1400
  audit(1445227600.333:26): apparmor="DENIED" operation="connect"
  profile="/usr/bin/evince" name="/run/user/1000/wayland-0" pid=12956
  comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000
  ouid=1000

  Adding the following lines to it's local Apparmour config and
  reloading Apparmour fixes the problem:

  >  owner /run/user/*/wayland-* rw,
  >  owner /run/user/*/weston-shared-* rw,

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: evince 3.16.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 19 17:49:19 2015
  InstallationDate: Installed on 2015-07-22 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: evince
  UpgradeStatus: Upgraded to wily on 2015-08-27 (52 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1507469/+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 1643467] Re: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

2016-11-30 Thread Woody

How is this not fixed yet? It appears to affect all 14.04 users of
firefox. Thats a lot of people.

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

Title:
  Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Confirmed

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1643467/+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

Re: [Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-11-30 Thread Luke Yelavich

Florian, please get a log from PulseAudio as I described earlier in this
bug report.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1645501] Re: corefiles not created in armhf chroot on arm64 porter

Kees provided me the following debdiffs for testing on zesty and yakkety
armhf chroots.

** Patch added: "gdb_7.12-0ubuntu3.debdiff"

https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1645501/+attachment/4785470/+files/gdb_7.12-0ubuntu3.debdiff

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

Title:
corefiles not created in armhf chroot on arm64 porter

Status in gdb package in Ubuntu:
Triaged

Bug description:
I'm filing this about gdb per Steve's suggestion, although this could
be an issue somewhere else.

I recently discovered that the apport-test-crash
(https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment
/test-crashes) crash files produced for armhf are crash files without
CoreDumps. This happened sometime between 20160531 and 20161025.
I've recreated this on the porter-arm64 box with the following minimal
test case (generate-sigsegv-crash.py is from apport-test-crashes):

schroot -c yakkety-armhf
python generate-sigsegv-crash.py cat

Running this on both armhf and arm64 we can see the following
different output.

armhf chroot on porter-armhf:

47 Program received signal SIGSEGV, Segmentation fault.
48 0xb6f599e4 in read () at ../sysdeps/unix/syscall-template.S:84
49 84 ../sysdeps/unix/syscall-template.S: No such file or directory.
50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core

armhf chroot on porter-arm64:

47 Program received signal SIGSEGV, Segmentation fault.
48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
49 84 ../sysdeps/unix/syscall-template.S: No such file or directory.
50 (gdb) Unable to fetch the floating point registers.: Invalid argument.

Notice how there is no core file save on porter-arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1645501/+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 1645501] Re: corefiles not created in armhf chroot on arm64 porter

** Patch added: "gdb_7.11.90.20161005-0ubuntu1.1.debdiff"

https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1645501/+attachment/4785471/+files/gdb_7.11.90.20161005-0ubuntu1.1.debdiff

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

Title:
corefiles not created in armhf chroot on arm64 porter

Status in gdb package in Ubuntu:
Triaged

Bug description:
I'm filing this about gdb per Steve's suggestion, although this could
be an issue somewhere else.

schroot -c yakkety-armhf
python generate-sigsegv-crash.py cat

Running this on both armhf and arm64 we can see the following
different output.

armhf chroot on porter-armhf:

armhf chroot on porter-arm64:

Notice how there is no core file save on porter-arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1645501/+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 1645501] Re: corefiles not created in armhf chroot on arm64 porter

I couldn't build the zesty debdiff on the arm64 porter box due to not
being able to install the dependencies to build it.  I did get the
yakkety one to build and then extracted the package contents and used
gdb from there.  I was then able to create core files with this new gdb.

GNU gdb (Ubuntu 7.11.90.20161005-0ubuntu1.1) 7.11.90.20161005-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from cat...(no debugging symbols found)...done.
(gdb) Starting program: /bin/cat
Cannot parse expression `.L954 4@r4'.
warning: Probes-based dynamic linker interface failed.
Reverting to original interface.


Program received signal SIGSEGV, Segmentation fault.
0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) Saved corefile /tmp/tmp8x5x1scn/my.core

I went so far as to run the generate-crashes script and it created core
files for multiple applications.

** Changed in: gdb (Ubuntu)
   Importance: Undecided => High

** Changed in: gdb (Ubuntu)
   Status: New => Triaged

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

Title:
  corefiles not created in armhf chroot on arm64 porter

Status in gdb package in Ubuntu:
  Triaged

Bug description:
  I'm filing this about gdb per Steve's suggestion, although this could
  be an issue somewhere else.

  I recently discovered that the apport-test-crash
  (https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment
  /test-crashes) crash files produced for armhf are crash files without
  CoreDumps.  This happened sometime between 20160531 and 20161025.
  I've recreated this on the porter-arm64 box with the following minimal
  test case (generate-sigsegv-crash.py is from apport-test-crashes):

  schroot -c yakkety-armhf
  python generate-sigsegv-crash.py cat

  Running this on both armhf and arm64 we can see the following
  different output.

  armhf chroot on porter-armhf:

47 Program received signal SIGSEGV, Segmentation fault.
48 0xb6f599e4 in read () at ../sysdeps/unix/syscall-template.S:84
49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core

  armhf chroot on porter-arm64:

47 Program received signal SIGSEGV, Segmentation fault.
48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
50 (gdb) Unable to fetch the floating point registers.: Invalid argument.

  Notice how there is no core file save on porter-arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1645501/+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

Re: [Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-11-30 Thread Pierluigi70

Ok Thanks so much
I try to do it

Il 30/nov/2016 19:01, "Robie Basak" <1642...@bugs.launchpad.net> ha
scritto:

> I think this might be caused by an interesting interaction between
> systemd, debhelper and the CUPS scheduler.
>
> I can reproduce a very similar error with the following. I think (though
> am not sure) that this is related to the root cause. On a fresh Xenial
> system:
>
> sudo apt-get update && sudo apt-get -y install cups
> sudo -i
> systemctl stop cups.service
> sleep 4
> touch /var/cache/cups/org.cups.cupsd
> sleep 4
> sudo rm /var/cache/cups/org.cups.cupsd
> sleep 4
> systemctl stop cups.service
>
> (the sleeps are to avoid any unknown, additional and unintentional race
> conditions)
>
> This results in an exit status of 1 and the message "Job for
> cups.service canceled." which matches the error that reporters have been
> seeing.
>
> In other words, if cups.service is started via cups.path, that cause is
> removed, and then we request a manual stop of cups.service, then systemd
> refuses to stop the service the first time (a retry always succeeds for
> me).
>
> In cups-daemon.prerm, debhelper has added "deb-systemd-invoke stop
> cups.path" followed by "invoke-rc.d cups stop || exit $?". I believe the
> second invocation is ultimately equivalent to "systemctl stop
> cups.service" and fails the same way as in my example, causing the prerm
> to exit 1, causing the dpkg failure reported.
>
> I'm not sure of the intended logic for /lib/systemd/system/cups.path
> here. AFAICT, it exists because when using CUPS with launchd, the CUPS
> daemon leaves the file in place as long as it doesn't want to be
> terminated, and removes it when it wants to be terminated before it
> exits anyway. Is this because launchd kills daemons itself unless the
> keepalive file exists?
>
> With systemd, I can't find any documentation that suggests that systemd
> ever intends to automatically kill a socket activated daemon. AFAICT,
> it's entirely up to the daemon when it chooses to exit. So there appears
> to be no need for cupsd to maintain /var/cache/cups/org.cups.cupsd when
> running under systemd.
>
> As configured right now, systemd will also start cupsd if
> /var/cache/cups/org.cups.cupsd is created while cupsd is not running. I
> can't find anything that might use this function. So either this is an
> accidental side-effect that is not needed, or I have missed some other
> path that does need this.
>
> systemd talks about CUPS in a blog post that is relevant:
> http://0pointer.de/blog/projects/socket-activation2.html. Note that this
> only sets up a path unit for /var/spool/cups, not any kind of keepalive
> file for cupsd.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1644526).
> https://bugs.launchpad.net/bugs/1642966
>
> Title:
>   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
>   pre-removal script returned error exit status 1
>
> Status in cups package in Ubuntu:
>   Confirmed
>
> Bug description:
>   This is in xenial-proposed, please block release to -updates
>   accordingly :)
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: cups-daemon 2.1.3-4
>   ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
>   Uname: Linux 4.4.0-46-generic x86_64
>   NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   CupsErrorLog:
>
>   Date: Fri Nov 18 11:13:15 2016
>   ErrorMessage: subprocess new pre-removal script returned error exit
> status 1
>   InstallationDate: Installed on 2016-05-02 (200 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%
> 208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-
> 1f08-abcd-d89d67d63461
>   MachineType: Dell Inc. XPS 15 9550
>   Papersize: a4
>   PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups
> 3.16.3
>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed
> root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash
> vt.handoff=7
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed
> root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash
> vt.handoff=7
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.1
>apt  1.2.15
>   SourcePackage: cups
>   Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
> new pre-removal script returned error exit status 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/07/2016
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 01.02.00
>   dmi.board.name: 0N7TVV
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:
> pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
>

[Touch-packages] [Bug 1507469] Re: Evince's Apparmour profile prevents opening docs from other apps under Wayland

** Branch linked: lp:apparmor

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

Title:
  Evince's Apparmour profile prevents opening docs from other apps under
  Wayland

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Evince fails to run when launched from another app (Nautilus, Ephy,
  etc) and running under Wayland. For example, nothing appears to happen
  when double-clicking on a PDF file in Nautilus. Evince is launched,
  but its Apparmour profile is preventing access to a Wayland socket,
  hence it immediately exits.

  The following is typical of the reported error:

  > Oct 19 15:06:40 payens kernel: audit: type=1400
  audit(1445227600.333:26): apparmor="DENIED" operation="connect"
  profile="/usr/bin/evince" name="/run/user/1000/wayland-0" pid=12956
  comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000
  ouid=1000

  Adding the following lines to it's local Apparmour config and
  reloading Apparmour fixes the problem:

  >  owner /run/user/*/wayland-* rw,
  >  owner /run/user/*/weston-shared-* rw,

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: evince 3.16.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 19 17:49:19 2015
  InstallationDate: Installed on 2015-07-22 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: evince
  UpgradeStatus: Upgraded to wily on 2015-08-27 (52 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1507469/+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 1507469] Re: Evince's Apparmour profile prevents opening docs from other apps under Wayland

2016-11-30 Thread Seth Arnold

Thanks Simon,

Committed revision 3590.

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

Title:
  Evince's Apparmour profile prevents opening docs from other apps under
  Wayland

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Evince fails to run when launched from another app (Nautilus, Ephy,
  etc) and running under Wayland. For example, nothing appears to happen
  when double-clicking on a PDF file in Nautilus. Evince is launched,
  but its Apparmour profile is preventing access to a Wayland socket,
  hence it immediately exits.

  The following is typical of the reported error:

  > Oct 19 15:06:40 payens kernel: audit: type=1400
  audit(1445227600.333:26): apparmor="DENIED" operation="connect"
  profile="/usr/bin/evince" name="/run/user/1000/wayland-0" pid=12956
  comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000
  ouid=1000

  Adding the following lines to it's local Apparmour config and
  reloading Apparmour fixes the problem:

  >  owner /run/user/*/wayland-* rw,
  >  owner /run/user/*/weston-shared-* rw,

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: evince 3.16.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 19 17:49:19 2015
  InstallationDate: Installed on 2015-07-22 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: evince
  UpgradeStatus: Upgraded to wily on 2015-08-27 (52 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1507469/+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 1643467] Re: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

2016-11-30 Thread Not Martin Wimpress

Allowing "obsolete" codecs to run is an absolutely terrible idea. For
those of you on 14.04, I'd recommend updating libav-tools by PPA
following this answer: http://askubuntu.com/a/851192 That's your best
bet so far.

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

Title:
  Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Confirmed

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1643467/+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 1643467] Re: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

2016-11-30 Thread R.Zimmermann

For me, Firefox (50.0 on Ubuntu 14.04) not only shows the warning, but also 
seems to prevent embedded .gif/.gifv animations from playing, at least on 
Reddit and Twitter.
Example: Almost every video on https://www.reddit.com/r/gifs/
After clicking the Play button, the video will "load forever" or show a still 
image.

It worked in previous FF versions, or works when setting
media.libavcodec.allow-obsolete=true (which I don't want to do
permanently).

It also works *sometimes* if the URL is pointing directly to the GIF
file.

Would appreciate if the fix for 14.04 could get a higher priority.

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

Title:
  Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Confirmed

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1643467/+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 1645798] Re: No snaps appear in scope on Core 16

2016-11-30 Thread Michael Terry

The scoperunner does NOT crash if I run it under gdbserver.  But I do
see some errors in that case:

(process:4583): ubuntu-app-launch-DEBUG: Initialized Click DB
[2016-11-30 21:43:45.633] ERROR: clickscope: ObjectAdapter: error unmarshaling 
request header (id: , adapter: clickscope-c, op: ): ZmqReceiver::receive(): 
socket was closed
...
various snaps being found
...
[2016-11-30 21:43:45.690] ERROR: clickscope: ReplyImpl::error(): 
ThreadPool::submit(): cannot accept task for destroyed pool
[2016-11-30 21:43:45.693] ERROR: clickscope: ReplyImpl::error(): exception from 
finished(): ThreadPool::submit(): cannot accept task for destroyed pool
2016-11-30 21:43:45,707 - DEBUG - destroying search

I think I need to hand this off to someone that understands scopes
better.  Michi, is this something you would know about?

** Also affects: unity-api (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-api (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  New

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645798/+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 1646256] [NEW] Update sudo for proper support of netgroups

2016-11-30 Thread KC

Public bug reported:

sudo v1.8.16 has a bug that prevents it from working properly with
netgroups.

The main affected usage case that I'm aware of is when using FreeIPA to
define host groups, and then using those host groups within sudo rules.

It would appear that a release >=1.8.17 resolves the issue.

https://bugzilla.redhat.com/show_bug.cgi?id=1348672
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_Management_Guide/sudo.html#abt-sudo2

Package: sudo 1.8.16-0ubuntu1.2
Distribution: Ubuntu 16.04 and later

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

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

Title:
  Update sudo for proper support of netgroups

Status in sudo package in Ubuntu:
  New

Bug description:
  sudo v1.8.16 has a bug that prevents it from working properly with
  netgroups.

  The main affected usage case that I'm aware of is when using FreeIPA
  to define host groups, and then using those host groups within sudo
  rules.

  It would appear that a release >=1.8.17 resolves the issue.

  https://bugzilla.redhat.com/show_bug.cgi?id=1348672
  
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_Management_Guide/sudo.html#abt-sudo2

  Package: sudo 1.8.16-0ubuntu1.2
  Distribution: Ubuntu 16.04 and later

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1646256/+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 1646253] [NEW] I am getting frequent DRM hangs while playing Cities: Skylines from Steam

2016-11-30 Thread Clint Byrum

Public bug reported:

It happens during normal gameplay. Have tried reducing settings. Seems
like a legitimate driver bug. The program crashes, but X does not.

[16868.151225] [drm] stuck on render ring
[16868.155458] [drm] GPU HANG: ecode 8:0:0x84dffefc, in Cities.x64 [21076], 
reason: Ring hung, action: reset
[16868.155472] [ cut here ]
[16868.155503] WARNING: CPU: 1 PID: 13959 at 
/build/linux-j9zxaP/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
[16868.155505] WARN_ON(__i915_wait_request(mmio_flip->req, 
mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips))
[16868.155506] Modules linked in:
[16868.155508]  tcp_diag inet_diag hid_microsoft hid_generic snd_usb_audio 
usbhid hid snd_usbmidi_lib usb_serial_simple usbserial ctr ccm pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 ipt_REJECT nf_reject_ipv4 
xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables rfcomm 
aufs bnep arc4 iwlmvm uvcvideo mac80211 videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 intel_rapl videobuf2_core x86_pkg_temp_thermal v4l2_common 
intel_powerclamp cdc_mbim snd_hda_codec_hdmi coretemp cdc_wdm 
snd_hda_codec_realtek snd_hda_codec_generic cdc_ncm videodev joydev iwlwifi
[16868.155545]  input_leds cdc_acm btusb usbnet serio_raw media btrtl 
snd_hda_intel mii btbcm rtsx_pci_ms thinkpad_acpi snd_hda_codec btintel 
memstick snd_hda_core cfg80211 bluetooth snd_hwdep snd_seq_midi 
snd_seq_midi_event intel_pch_thermal nvram snd_rawmidi lpc_ich snd_pcm mei_me 
mei shpchp snd_seq snd_seq_device snd_timer snd soundcore kvm_intel mac_hid kvm 
irqbypass parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher 
af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect 
sysimgblt rtsx_pci fb_sys_fops ahci psmouse ptp drm libahci pps_core wmi fjes 
video
[16868.155589] CPU: 1 PID: 13959 Comm: kworker/1:0 Tainted: GW  OE   
4.4.0-51-generic #72-Ubuntu
[16868.155591] Hardware name: LENOVO 20CLS5N900/20CLS5N900, BIOS N10ET36W (1.15 
) 06/19/2015
[16868.155617] Workqueue: events intel_mmio_flip_work_func [i915]
[16868.155619]  0286 dd043c13 880382bbbd20 
813f5fc3
[16868.155622]  880382bbbd68 c03a7ab8 880382bbbd58 
810812b2
[16868.155624]  8802970af040 88042dc56500 88042dc5ae00 
0040
[16868.155626] Call Trace:
[16868.155632]  [] dump_stack+0x63/0x90
[16868.155637]  [] warn_slowpath_common+0x82/0xc0
[16868.155639]  [] warn_slowpath_fmt+0x5c/0x80
[16868.155643]  [] ? __switch_to+0x437/0x5c0
[16868.155667]  [] intel_mmio_flip_work_func+0x38e/0x3d0 
[i915]
[16868.155672]  [] process_one_work+0x165/0x480
[16868.155674]  [] worker_thread+0x4b/0x4c0
[16868.155677]  [] ? process_one_work+0x480/0x480
[16868.155679]  [] kthread+0xd8/0xf0
[16868.155681]  [] ? kthread_create_on_node+0x1e0/0x1e0
[16868.155685]  [] ret_from_fork+0x3f/0x70
[16868.155687]  [] ? kthread_create_on_node+0x1e0/0x1e0
[16868.155689] ---[ end trace 1339c06922e659f4 ]---
[16868.157772] drm/i915: Resetting chip after gpu hang
[16874.163802] [drm] stuck on render ring
[16874.168161] [drm] GPU HANG: ecode 8:0:0x86dd, in Cities.x64 [21076], 
reason: Ring hung, action: reset
[16874.168182] [ cut here ]
[16874.168215] WARNING: CPU: 1 PID: 13959 at 
/build/linux-j9zxaP/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
[16874.168216] WARN_ON(__i915_wait_request(mmio_flip->req, 
mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips))
[16874.168217] Modules linked in:
[16874.168221]  tcp_diag inet_diag hid_microsoft hid_generic snd_usb_audio 
usbhid hid snd_usbmidi_lib usb_serial_simple usbserial ctr ccm pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 ipt_REJECT nf_reject_ipv4 
xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables rfcomm 
aufs bnep arc4 iwlmvm uvcvideo mac80211 videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 intel_rapl videobuf2_core x86_pkg_temp_thermal v4l2_common 
intel_powerclamp cdc_mbim snd_hda_codec_hdmi coretemp cdc_wdm 
snd_hda_codec_realtek snd_hda_codec_generic cdc_ncm videodev joydev iwlwifi
[16874.168250]  input_leds cdc_acm btusb usbnet serio_raw media btrtl 
snd_hda_intel mii btbcm rtsx_pci_ms thinkpad_acpi

[Touch-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

2016-11-30 Thread Pat McGowan

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  In Progress
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  In Progress
Status in unity-gtk-module source package in Xenial:
  In Progress

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1644355] Re: udev netdev naming does not work with mellanox switches

2016-11-30 Thread Luke Williams

The naming currently is ethXX where XX is a sequential number that does not 
correlate with the port on the front panel. For example, eth0 will sometimes 
correlate with port 30, and on the next reboot it will be port 6.
After the patch is installed, the devices are named enp3s0pXX where XX 
correlates with the panel names, for example enp3s0p1 correlates to port 1.

I am not aware of any other devices that make use of phys_port_name
patterns.

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

Title:
  udev netdev naming does not work with mellanox switches

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Yakkety:
  Incomplete

Bug description:
  The current packaged systemd for Yakkety does not have the Mellanox
  netdev udev naming set for systemd patch installed
  (https://github.com/systemd/systemd/commit/4887b656c22). The current
  version for zesty does. I installed the ppa for this on to my Yakkety
  switch and rebooted and the devices are properly named.

  SRU TEST CASE:
* (To be filled out by Luke)

  REGRESSION POTENTIAL:
  This changes the network device names for an unknown set of devices (those 
which have a "phys_port_name" sysfs attribute), which can lead to 
unbootable/inaccessible existing systems. @Luke: Is this only being used by 
Mellanox drivers in yakkety's kernels? Which other drivers expose this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1644355/+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 1644355] Re: udev netdev naming does not work with mellanox switches

2016-11-30 Thread Luke Williams

The naming currently is ethXX where XX is a sequential number that does not 
correlate with the port on the front panel. For example, eth0 will sometimes 
correlate with port 30, and on the next reboot it will be port 6.
After the patch is installed, the devices are named enp3s0pXX where XX 
correlates with the panel names, for example enp3s0p1 correlates to port 1.

I am not aware of any other devices that make use of phys_port_name
patterns.

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

Title:
  udev netdev naming does not work with mellanox switches

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Yakkety:
  Incomplete

Bug description:
  The current packaged systemd for Yakkety does not have the Mellanox
  netdev udev naming set for systemd patch installed
  (https://github.com/systemd/systemd/commit/4887b656c22). The current
  version for zesty does. I installed the ppa for this on to my Yakkety
  switch and rebooted and the devices are properly named.

  SRU TEST CASE:
* (To be filled out by Luke)

  REGRESSION POTENTIAL:
  This changes the network device names for an unknown set of devices (those 
which have a "phys_port_name" sysfs attribute), which can lead to 
unbootable/inaccessible existing systems. @Luke: Is this only being used by 
Mellanox drivers in yakkety's kernels? Which other drivers expose this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1644355/+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 1646245] [NEW] /etc/init.d/ondemand keeps /etc/init.d/cpufrequtils from working

2016-11-30 Thread Len Ovens

Public bug reported:

dpkg -S /etc/init.d/ondemand says initscripts. /etc/init.d/cpufrequtils
already sets the cpu governor and has the option that a user can set
system governor in /etc/default/. ondemand over rides this and even
worse does it 60 seconds late so that the user can not even set the
governor from rc.local. There is no sense in waiting 60 seconds as the
cpu governor is already at ondemand or powersave before the system gets
around to running ondemand. ondemand needs to just be removed so that
cpufrequtils can do it's job properly. Or at least ondemand needs to
read some file in /etc/defaults that tells it what the system default
should be rather forcing the user to edit system files to get around
ondemand's crazy activity which then breaks package updates.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: initscripts 2.88dsf-59.3ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-47.68-lowlatency 4.4.24
Uname: Linux 4.4.0-47-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 30 12:35:55 2016
InstallationDate: Installed on 2016-04-22 (222 days ago)
InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
SourcePackage: sysvinit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  /etc/init.d/ondemand keeps /etc/init.d/cpufrequtils from working

Status in sysvinit package in Ubuntu:
  New

Bug description:
  dpkg -S /etc/init.d/ondemand says initscripts.
  /etc/init.d/cpufrequtils already sets the cpu governor and has the
  option that a user can set system governor in /etc/default/. ondemand
  over rides this and even worse does it 60 seconds late so that the
  user can not even set the governor from rc.local. There is no sense in
  waiting 60 seconds as the cpu governor is already at ondemand or
  powersave before the system gets around to running ondemand. ondemand
  needs to just be removed so that cpufrequtils can do it's job
  properly. Or at least ondemand needs to read some file in
  /etc/defaults that tells it what the system default should be rather
  forcing the user to edit system files to get around ondemand's crazy
  activity which then breaks package updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initscripts 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-47.68-lowlatency 4.4.24
  Uname: Linux 4.4.0-47-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 30 12:35:55 2016
  InstallationDate: Installed on 2016-04-22 (222 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: sysvinit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1646245/+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 1594266] Re: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: hicolor-icon-theme (Ubuntu)
   Status: New => Confirmed

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

Title:
  package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  lors de la mise à jour d'Ubuntu vers la version 16.04 j'ai eu de nombreux 
messages d'erreurs dont je ne sais que faire. je ne suis pas developpeur et vos 
mises a jour intempestives m'ont mis dans l'embarras pour rester poli.
  que faire ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun 19 18:58:38 2016
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-01-04 (532 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-06-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1594266/+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 1591354] Re: [tests] given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset fails

2016-11-30 Thread Cemil Azizoglu

Reopening since it's still happening :
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/3009/consoleFull

** Changed in: mir
   Status: Fix Released => Confirmed

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

Title:
  [tests]
  
given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
  fails

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  18:48:48 13: [ RUN ] 
NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
  ...
  18:48:51 13: [2016-06-10 18:48:50.931481] mirserver: Logical position +0+0
  18:48:52 13: 
/��BUILDDIR��/mir-0.23.0+xenial1328bzr3533/tests/acceptance-tests/test_nested_mir.cpp:1135:
 Failure
  18:48:52 13: Value of: condition.raised()
  18:48:52 13: Actual: false
  18:48:52 13: Expected: true
  18:48:52 13: 
/��BUILDDIR��/mir-0.23.0+xenial1328bzr3533/tests/acceptance-tests/test_nested_mir.cpp:1129:
 Failure
  18:48:52 13: Actual function call count doesn't match 
EXPECT_CALL(*the_mock_display_configuration_report(), 
new_configuration(mt::DisplayConfigMatches(expected_config)))...
  18:48:52 13: Expected: to be called once
  18:48:52 13: Actual: never called - unsatisfied and active
  18:48:52 13: [2016-06-10 18:48:52.115583] mirserver: Stopping
  18:48:52 13: [2016-06-10 18:48:52.280421] mirserver: Stopping
  18:48:52 13: [ FAILED ] 
NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
 (3916 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial/1297/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1591354/+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 1646233] [NEW] file command incorrectly identifies a gzipped file as being a Minix filesystem

2016-11-30 Thread Rarylson Freitas

Public bug reported:

In Ubuntu 14.04, the command `file` (1:5.14-2ubuntu3.3) incorrectly
identifies a gzipped file as being a Minix filesystem.

Example:

```
$ file gzip-minix.eml 
gzip-minix.eml: Minix filesystem, V3, 43470 zones
$ file -v
file-5.14
magic file from /etc/magic:/usr/share/misc/magic
```

The workaround I'm using is passing the `-k` (keep going) param to file.

```
$ file -k gzip-minix.eml 
gzip-minix.eml: Minix filesystem, V3, 43470 zones\012- gzip compressed data, 
from Unix
```

In Ubuntu 16.04, however, the file is correctly identified.

```
$ file gzip-minix.eml 
gzip-minix.eml: gzip compressed data, from Unix
$ file -v
file-5.25
magic file from /etc/magic:/usr/share/misc/magic
```

This bug has a description very similar to those reported in these URLs:

- https://bugzilla.redhat.com/show_bug.cgi?id=873997
- https://bugzilla.redhat.com/show_bug.cgi?id=758429

However, despite the very similar description, I didn't find any problem
with the JPEG files attached in these bug reports.

Note: The error is occurring in about 1 gzipped file for each 6 or
10 files I have in my data filesystem. Because some of these files
contain sensitive information, I'm attaching only one of them (an
innocent example).

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

** Attachment added: "gzip-minix.eml"
   
https://bugs.launchpad.net/bugs/1646233/+attachment/4785419/+files/gzip-minix.eml

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

Title:
  file command incorrectly identifies a gzipped file as being a Minix
  filesystem

Status in file package in Ubuntu:
  New

Bug description:
  In Ubuntu 14.04, the command `file` (1:5.14-2ubuntu3.3) incorrectly
  identifies a gzipped file as being a Minix filesystem.

  Example:

  ```
  $ file gzip-minix.eml 
  gzip-minix.eml: Minix filesystem, V3, 43470 zones
  $ file -v
  file-5.14
  magic file from /etc/magic:/usr/share/misc/magic
  ```

  The workaround I'm using is passing the `-k` (keep going) param to
  file.

  ```
  $ file -k gzip-minix.eml 
  gzip-minix.eml: Minix filesystem, V3, 43470 zones\012- gzip compressed data, 
from Unix
  ```

  In Ubuntu 16.04, however, the file is correctly identified.

  ```
  $ file gzip-minix.eml 
  gzip-minix.eml: gzip compressed data, from Unix
  $ file -v
  file-5.25
  magic file from /etc/magic:/usr/share/misc/magic
  ```

  This bug has a description very similar to those reported in these
  URLs:

  - https://bugzilla.redhat.com/show_bug.cgi?id=873997
  - https://bugzilla.redhat.com/show_bug.cgi?id=758429

  However, despite the very similar description, I didn't find any
  problem with the JPEG files attached in these bug reports.

  Note: The error is occurring in about 1 gzipped file for each 6 or
  10 files I have in my data filesystem. Because some of these files
  contain sensitive information, I'm attaching only one of them (an
  innocent example).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1646233/+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 1606418] Re: PointerConfinement.test_we_update_our_confined_region_on_a_resize

2016-11-30 Thread Cemil Azizoglu

Another instance : 
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/3008/consoleFull

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

Title:
  PointerConfinement.test_we_update_our_confined_region_on_a_resize

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Randomly fails 1/100 times.
  
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/1612/console

  Looking into it, most likely a race with surface resize...

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1606418/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-11-30 Thread Till Kamppeter

Can everyone suffering this problem please attach his
/etc/cups/cupsd.conf file? Please also post the output of the commands:

lpstat -v
lpstat -o

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"

2016-11-30 Thread Bug Watch Updater

** Changed in: cyrus-sasl2
   Status: Unknown => New

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

Title:
  Annoying log message "DIGEST-MD5 common mech free"

Status in Cyrus-sasl2:
  New
Status in cyrus-sasl2 package in Ubuntu:
  Confirmed
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  I recently updated the libsasl2-modules to 
2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric.
  That triggered the bug also described in Debian here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932

  The annoying message is logged in auth.log. In my case, it is associated with 
svnserve:
  svnserve: DIGEST-MD5 common mech free

  I'm not exactly sure what action triggers the message, but I can
  investigate more if required.

  $ lsb_release -rd
  Description:Ubuntu oneiric (development branch)
  Release:11.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"

2016-11-30 Thread hackel

FYI: From https://bugs.archlinux.org/task/44945:

Comment by Jan de Groot (JGC) - Thursday, 04 June 2015, 08:01 GMT
These messages are logged at debug level, you can change syslog config to 
filter out debug messages.

I will not remove this from Cyrus SASL, as debug logging is the only way
to debug issues with SASL when not running interactive, for example when
running a mailserver.


** Bug watch added: Debian Bug tracker #805310
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805310

** Also affects: cyrus-sasl2 via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805310
   Importance: Unknown
   Status: Unknown

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

Title:
  Annoying log message "DIGEST-MD5 common mech free"

Status in Cyrus-sasl2:
  Unknown
Status in cyrus-sasl2 package in Ubuntu:
  Confirmed
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  I recently updated the libsasl2-modules to 
2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric.
  That triggered the bug also described in Debian here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932

  The annoying message is logged in auth.log. In my case, it is associated with 
svnserve:
  svnserve: DIGEST-MD5 common mech free

  I'm not exactly sure what action triggers the message, but I can
  investigate more if required.

  $ lsb_release -rd
  Description:Ubuntu oneiric (development branch)
  Release:11.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1591490] Re: Please backport apt 1.0.9.2ubuntu2 from utopic (to fix do-release-upgrade)

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apt (Ubuntu)
   Status: New => Confirmed

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

Title:
  Please backport apt 1.0.9.2ubuntu2 from utopic (to fix do-release-
  upgrade)

Status in trusty-backports:
  New
Status in apt package in Ubuntu:
  Confirmed

Bug description:
  For me (and apparently many others), upgrading Ubuntu Trusty LTS to
  Ubuntu Xenial LTS fails because do-release-upgrade bails out because
  of apt error messages like this:

  
  Unknown Multi-Arch type 'no' for package 'kwin'
  Unknown Multi-Arch type 'no' for package 'kwin-dev'
  Unknown Multi-Arch type 'no' for package 'kwin-wayland'
  Unknown Multi-Arch type 'no' for package 'kwin-x11'
  Unknown Multi-Arch type 'no' for package 'libkf5sysguard-dev'

  Unknown Multi-Arch type 'no' for package 'compiz-core'
  Unknown Multi-Arch type 'no' for package 'compiz-gnome'
  Unknown Multi-Arch type 'no' for package 'libxapian-dev'

  
  It is caused by Debian bug #759099 [1] fixed in apt 1.0.7. Therefore I'm 
requesting a backport of "apt" to trusty.

  In the title I've suggested 1.0.9 from utopic - a more recent version
  might be fine too but when I tried to build the wily version on my
  local machine it couldn't because the g++ requirement had moved on too
  far.

  
  [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759099

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1591490/+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

Re: [Touch-packages] [Bug 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

2016-11-30 Thread Olnei Araujo

Thank you! I will not do it.



Olnei A Araujo
Comunidade ubuntu-br
http://wiki.ubuntu-br/InstalacaoUbuntu
http://ubuntu.com
31-987-120-747
twitter:@olneiaa
linux user # 484050
ubuntu user # 26374-2007


2016-11-30 13:00 GMT-02:00 Julian Andres Klode :

> Not sure about the ubiquity task, though, I unmerged the other bug
> reports (which actually are 2 distinct ones), but did not mark it as
> fixed again.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1615273).
> https://bugs.launchpad.net/bugs/1611010
>
> Title:
>   yakkety desktop - non-english installation crashes with
>   /plugininstall.py: ValueError: invalid literal for int() with base 10:
>   ''
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1611010/+subscriptions
>

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

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  In Progress
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  [Impact]
  Breaks installation in some non-English locales.

  [Test case]
  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  [Regression potential]
  Very low, we're running this in 1.3 since a long time. The fix depends on 
another one that restricts the Date parser to accept only UTC time zones in 
Release files, though (we do not understand the other ones anyway), and thus 
might reject some repositories it silently accepted in a wrong way previously 
(we have not seen anyone report a regression yet since uploading that in June).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1611010/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-11-30 Thread Till Kamppeter

Robie, thanks for the investigations. I have looked into what the file
/var/cache/cups/org.cups.cupsd (CUPS calls it "keepalive" file) is good
for and what CUPS does with it. The file is created by the CUPS daemon
cupsd when it needs to keep running, having active jobs, being in the
course of a reload, having the web interface active or sharing printers,
otherwise the file is removed. CUPS updates presence/no presence on
start-up and shutdown of the daemon and it does exactly the same in both
cases, so it can remain present after shutdown, depending on CUPS'
configuration. CUPS never reads this file (or checks its presence),
meaning that it is purely for advising external processes.

So for me it looks like that there is a certain system service manager
(what one usually runs as PID 1 under Linux) which checks for the
presence of keepalive files and decides based on this which daemons to
kill and which to keep running.

I do not know everything about systemd. Does systemd care about
keepalive files?

The CUPS upstream *.path makes cupsd being triggered by creating the
file, but only if the file is not there already. What is this good for?

Does this *.path also take down cupsd if one removes the keepalive file
or is systemd supposed to do so? For me cupsd does not get stopped by
that.

And why does shutdown of CUPS fail after removing the keepalive file
(with "Job for cups.service canceled.")? As CUPS does not care about it,
systemd seems to depend on it. And what in the prerm script of the CUPS
Debian package deletes the keepalive file?

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"

2016-11-30 Thread hackel

FYI: The solution Debian implemented was quite trivial.  Simply create the file 
/etc/logcheck/ignore.d.server/libsasl2-modules:
\w{3} [ :0-9]{11} [._[:alnum:]-]+ [._[:alnum:]-]+: DIGEST-MD5 common mech free

It doesn't actually fix the problem, it just ignores the pointless log
messages.

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

Title:
  Annoying log message "DIGEST-MD5 common mech free"

Status in Cyrus-sasl2:
  Unknown
Status in cyrus-sasl2 package in Ubuntu:
  Confirmed
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  I recently updated the libsasl2-modules to 
2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric.
  That triggered the bug also described in Debian here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932

  The annoying message is logged in auth.log. In my case, it is associated with 
svnserve:
  svnserve: DIGEST-MD5 common mech free

  I'm not exactly sure what action triggers the message, but I can
  investigate more if required.

  $ lsb_release -rd
  Description:Ubuntu oneiric (development branch)
  Release:11.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"

2016-11-30 Thread hackel

Confirmed, this is incredibly annoying.  In my case, it's coming from
PHP.  I've got 44k of such messages in my auth.log file that covers just
the last 3.5 days, and 16k of those were actually "repeated x times"
messages!  All coming from php or php7.0 (both pointing to the same
php7.0-cli binary).  I believe this is because I use php-mongodb
extensively, which uses libsasl2-2.

libsasl2-modules 2.1.25.dfsg1-17build1 on Ubuntu 14.04.

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

Title:
  Annoying log message "DIGEST-MD5 common mech free"

Status in cyrus-sasl2 package in Ubuntu:
  Confirmed
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  I recently updated the libsasl2-modules to 
2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric.
  That triggered the bug also described in Debian here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932

  The annoying message is logged in auth.log. In my case, it is associated with 
svnserve:
  svnserve: DIGEST-MD5 common mech free

  I'm not exactly sure what action triggers the message, but I can
  investigate more if required.

  $ lsb_release -rd
  Description:Ubuntu oneiric (development branch)
  Release:11.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/827151/+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 1507469] Re: Evince's Apparmour profile prevents opening docs from other apps under Wayland

2016-11-30 Thread Simon McVittie

There is now an , which is #include'd by
. It includes weston-shared, but not the Wayland
socket itself.

I suspect a better rule for that would be:

owner /run/user/*/wayland-[0-9]* rw,

so that the numbered sockets that are conventionally used are matched
more precisely.

The complete set of possible fd-passed shared-memory backing files is
more like:

owner /run/user/*/{mesa,mutter,sdl,weston,xwayland}-shared-* rw,

because the Wayland code to create an anonymous backing file for shared
memory has been copied and pasted all over the place, with some
instances changing the name.

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

Title:
  Evince's Apparmour profile prevents opening docs from other apps under
  Wayland

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Evince fails to run when launched from another app (Nautilus, Ephy,
  etc) and running under Wayland. For example, nothing appears to happen
  when double-clicking on a PDF file in Nautilus. Evince is launched,
  but its Apparmour profile is preventing access to a Wayland socket,
  hence it immediately exits.

  The following is typical of the reported error:

  > Oct 19 15:06:40 payens kernel: audit: type=1400
  audit(1445227600.333:26): apparmor="DENIED" operation="connect"
  profile="/usr/bin/evince" name="/run/user/1000/wayland-0" pid=12956
  comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000
  ouid=1000

  Adding the following lines to it's local Apparmour config and
  reloading Apparmour fixes the problem:

  >  owner /run/user/*/wayland-* rw,
  >  owner /run/user/*/weston-shared-* rw,

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: evince 3.16.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 19 17:49:19 2015
  InstallationDate: Installed on 2015-07-22 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: evince
  UpgradeStatus: Upgraded to wily on 2015-08-27 (52 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1507469/+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 1633828] Re: Mounting /boot/efi fails always after updating to 16.10

2016-11-30 Thread Prasanna Kumar

I copied the values from /etc/fstab while mounting. The command I used
to mount is "sudo mount UUID=86E4-0AA9 /boot/efi".

Attached my /etc/fstab file. I have commented the line that mounts
/boot/efi.

** Attachment added: "fstab"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1633828/+attachment/4785394/+files/fstab

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

Title:
  Mounting /boot/efi fails always after updating to 16.10

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  System does not boot properly as mounting /boot/efi fails. Commented
  out /boot/efi entry in /etc/fstab to boot system normally. This
  started happening after update to 16.10. Everything was working fine
  in 15.10, 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: mount 2.28.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 16 15:23:19 2016
  InstallationDate: Installed on 2015-11-20 (330 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1633828/+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 1619600] Re: [SRU] New stable release 1.8.3

2016-11-30 Thread Marc Deslauriers

gst-plugins-good1.0 needs to be updated to incorporate the security
fixes from (1.8.2-1ubuntu0.3). Marking as verification-failed until
then.

** Tags removed: verification-needed
** Tags added: verification-failed

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Fix Committed
Status in gstreamer1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Yakkety:
  Invalid

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1633828] Re: Mounting /boot/efi fails always after updating to 16.10

Can you show the exact command that you used to mount it, and the line
from /etc/fstab?

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

Title:
  Mounting /boot/efi fails always after updating to 16.10

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  System does not boot properly as mounting /boot/efi fails. Commented
  out /boot/efi entry in /etc/fstab to boot system normally. This
  started happening after update to 16.10. Everything was working fine
  in 15.10, 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: mount 2.28.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 16 15:23:19 2016
  InstallationDate: Installed on 2015-11-20 (330 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1633828/+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 1646080] Re: Mir-backed InputDeviceModel’s count property is not updated timely

2016-11-30 Thread Lorn Potter

upstream MR https://codereview.qt-project.org/#/c/178521/

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

Title:
  Mir-backed InputDeviceModel’s count property is not updated timely

Status in qtsystems-opensource-src package in Ubuntu:
  In Progress

Bug description:
  I’m trying to use InputDeviceModel from QML with the following
  example:

  import QtQuick 2.4
  import QtSystemInfo 5.5
  Item {
InputDeviceModel {
  id: idm
  filter: InputInfo.Mouse
  onCountChanged: console.log("mice model count:", devices, count)
  onAdded: console.log("added mouse:", inputDevice, count)
  onRemoved: console.log("removed mouse:", deviceId, count)
}
readonly property bool hasMouse: idm.count > 0
onHasMouseChanged: console.log("has mouse:", hasMouse)
  }

  When I launch the example with qmlscene on my arale with no mouse
  connected, I’m not seeing any output (expected).

  Then I connect a bluetooth keyboard/mouse combo, and I’m seeing the following:
mice model count: 1 0
added mouse: QInputDevice(0x17f6298) 1
(note how 'hasMouse', which supposedly was initially false, hasn’t been 
updated)

  Then I disconnect the combo, and I’m seeing the following:
mice model count: 0 1
has mouse: true
removed mouse: 15 0

  Then I connect it again, and I’m seeing the following:
mice model count: 1 0
has mouse: false
added mouse: QInputDevice(0x18ee508) 1

  It appears the countChanged property is emitted before a device is
  added to/removed from the model, and thus the row count hasn’t
  actually been updated yet. So any property binding that relies on
  'count' will have an incorrect value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+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 1646080] Re: Mir-backed InputDeviceModel’s count property is not updated timely

2016-11-30 Thread Olivier Tilloy

Thanks!

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

Title:
  Mir-backed InputDeviceModel’s count property is not updated timely

Status in qtsystems-opensource-src package in Ubuntu:
  In Progress

Bug description:
  I’m trying to use InputDeviceModel from QML with the following
  example:

  import QtQuick 2.4
  import QtSystemInfo 5.5
  Item {
InputDeviceModel {
  id: idm
  filter: InputInfo.Mouse
  onCountChanged: console.log("mice model count:", devices, count)
  onAdded: console.log("added mouse:", inputDevice, count)
  onRemoved: console.log("removed mouse:", deviceId, count)
}
readonly property bool hasMouse: idm.count > 0
onHasMouseChanged: console.log("has mouse:", hasMouse)
  }

  When I launch the example with qmlscene on my arale with no mouse
  connected, I’m not seeing any output (expected).

  Then I connect a bluetooth keyboard/mouse combo, and I’m seeing the following:
mice model count: 1 0
added mouse: QInputDevice(0x17f6298) 1
(note how 'hasMouse', which supposedly was initially false, hasn’t been 
updated)

  Then I disconnect the combo, and I’m seeing the following:
mice model count: 0 1
has mouse: true
removed mouse: 15 0

  Then I connect it again, and I’m seeing the following:
mice model count: 1 0
has mouse: false
added mouse: QInputDevice(0x18ee508) 1

  It appears the countChanged property is emitted before a device is
  added to/removed from the model, and thus the row count hasn’t
  actually been updated yet. So any property binding that relies on
  'count' will have an incorrect value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+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 1640554] Re: package util-linux 2.28.2-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

You have a third party service installed named "smfpd" that is broken
and will need to be removed.


** Changed in: util-linux (Ubuntu)
   Status: New => Invalid

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

Title:
  package util-linux 2.28.2-1ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  upgrade from 16.4 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.28.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  9 12:11:58 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-06 (94 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: util-linux
  Title: package util-linux 2.28.2-1ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-11-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1640554/+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 1646140] Re: Radeon Xpress 200M - performance regression in video playback with Wily stack (Vivid is last working stack)

2016-11-30 Thread indigocat

*** This bug is a duplicate of bug 1610591 ***
https://bugs.launchpad.net/bugs/1610591

Because you had said it could be related to Mesa, so I asked again
referring to the Mesa package.

Close it if you want.
I guess I'll never ask for help anymore.

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

Title:
  Radeon Xpress 200M - performance regression in video playback with
  Wily stack (Vivid is last working stack)

Status in mesa package in Ubuntu:
  New

Bug description:
  After updating the Ubuntu HWE stack in 14.04 to Wily (kernel 4.2 and
  xserver-xorg-video-radeon-lts-wily), system boots up fine, but screen
  is laggy; although DRI3 is now enabled (according to Xorg.0.log), 2D
  acceleration seems to be gone.

  System is an older Pentium laptop (Packard Bell EasyNote) with a
  Radeon Xpress 200M chip (r300 driver). Video acceleration was working
  with DRI2 under the Vivid stack (kernel 3.19-64-lowlatency + xserver-
  xorg-video-radeon-lts-vivid).

  I'm using a 14.04 LTS-based distro, ElementaryOS, with vanilla Ubuntu HWE 
stacks.
  (Testing with Oibaf's PPA or Xorg-edgers repo did not solve the problem 
either, so I purged the PPAs and reverted to official Ubuntu sources)

  We already bisected and tested Xorg versions with the package
  maintainers, and could not determine a consistent culprit, so the
  suggestion is that perhaps a newer Mesa version after Vivid is
  impairing video acceleration in 2D content display. Which Mesa package
  could be showing a regression, I do not know how to assess, so I'm
  eager for your input.

  Here is the original report, with logs and bisect results:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598593

  Tell me what else you need, I'll get it for you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1646140/+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 1598300] Re: CUPS web interface stops responding after a while

2016-11-30 Thread dominix

To give more information on this issue. We are heavily using cups lpd daemon 
(via inetd) because the machine is used to convert from some old systems, old 
fashioned printer that do not exists no more, and cups is able to convert this 
in whatever we want (pcl, pdf, postscript) via its powerfull drivers plugins 
system. 
So cups.lpd might be involved in this issue, because we dont have this issue on 
system that do not run cups.lpd

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1646080] Re: Mir-backed InputDeviceModel’s count property is not updated timely

2016-11-30 Thread Lorn Potter

@osomon looks good. I will apply upstream.

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

Title:
  Mir-backed InputDeviceModel’s count property is not updated timely

Status in qtsystems-opensource-src package in Ubuntu:
  In Progress

Bug description:
  I’m trying to use InputDeviceModel from QML with the following
  example:

  import QtQuick 2.4
  import QtSystemInfo 5.5
  Item {
InputDeviceModel {
  id: idm
  filter: InputInfo.Mouse
  onCountChanged: console.log("mice model count:", devices, count)
  onAdded: console.log("added mouse:", inputDevice, count)
  onRemoved: console.log("removed mouse:", deviceId, count)
}
readonly property bool hasMouse: idm.count > 0
onHasMouseChanged: console.log("has mouse:", hasMouse)
  }

  When I launch the example with qmlscene on my arale with no mouse
  connected, I’m not seeing any output (expected).

  Then I connect a bluetooth keyboard/mouse combo, and I’m seeing the following:
mice model count: 1 0
added mouse: QInputDevice(0x17f6298) 1
(note how 'hasMouse', which supposedly was initially false, hasn’t been 
updated)

  Then I disconnect the combo, and I’m seeing the following:
mice model count: 0 1
has mouse: true
removed mouse: 15 0

  Then I connect it again, and I’m seeing the following:
mice model count: 1 0
has mouse: false
added mouse: QInputDevice(0x18ee508) 1

  It appears the countChanged property is emitted before a device is
  added to/removed from the model, and thus the row count hasn’t
  actually been updated yet. So any property binding that relies on
  'count' will have an incorrect value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+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 1646140] Re: Radeon Xpress 200M - performance regression in video playback with Wily stack (Vivid is last working stack)

2016-11-30 Thread Timo Aaltonen

*** This bug is a duplicate of bug 1610591 ***
https://bugs.launchpad.net/bugs/1610591

** This bug has been marked a duplicate of bug 1610591
   Video acceleration regression for Radeon Xpress 200M (r300) in 
xorg-lts-xenial & xorg-lts-wily

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

Title:
  Radeon Xpress 200M - performance regression in video playback with
  Wily stack (Vivid is last working stack)

Status in mesa package in Ubuntu:
  New

Bug description:
  After updating the Ubuntu HWE stack in 14.04 to Wily (kernel 4.2 and
  xserver-xorg-video-radeon-lts-wily), system boots up fine, but screen
  is laggy; although DRI3 is now enabled (according to Xorg.0.log), 2D
  acceleration seems to be gone.

  System is an older Pentium laptop (Packard Bell EasyNote) with a
  Radeon Xpress 200M chip (r300 driver). Video acceleration was working
  with DRI2 under the Vivid stack (kernel 3.19-64-lowlatency + xserver-
  xorg-video-radeon-lts-vivid).

  I'm using a 14.04 LTS-based distro, ElementaryOS, with vanilla Ubuntu HWE 
stacks.
  (Testing with Oibaf's PPA or Xorg-edgers repo did not solve the problem 
either, so I purged the PPAs and reverted to official Ubuntu sources)

  We already bisected and tested Xorg versions with the package
  maintainers, and could not determine a consistent culprit, so the
  suggestion is that perhaps a newer Mesa version after Vivid is
  impairing video acceleration in 2D content display. Which Mesa package
  could be showing a regression, I do not know how to assess, so I'm
  eager for your input.

  Here is the original report, with logs and bisect results:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598593

  Tell me what else you need, I'll get it for you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1646140/+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 1644595] Re: krb5-1.13.2+dfsg-5 source contains source subject to the aladdin license

2016-11-30 Thread Bug Watch Updater

** Changed in: kerberos
   Status: Unknown => Fix Committed

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

Title:
  krb5-1.13.2+dfsg-5 source contains source subject to the aladdin
  license

Status in Kerberos:
  Fix Committed
Status in krb5 package in Ubuntu:
  Confirmed

Bug description:
  The krb5-1.13.2+dfsg-5 package source contains a file autolock.hxx  in
  the directory
  
krb5-1.13.2+dfsg-5\krb5_1.13.2+dfsg.orig\krb5-1.13.2+dfsg\src\ccapi\common\win\OldCC.
  Although not declared in any other licensing file for this package the
  file contains comments indicating its subject to the Aladdin license
  which has implications for any commercial distribution of the
  software, specifically:

  “2(a) Distribution of the Program or any work based on the Program by
  a commercial organization to any third party is prohibited if any
  payment is made in connection with such distribution, whether directly
  (as in payment for a copy fo the Program) or indirectly (as in payment
  for some service related to the Program, or payment for some product
  or service that includes a copy of the Program ‘without charge’ . . .”

  This file clearly is not needed or used for any Linux build as it
  appears specific to windows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kerberos/+bug/1644595/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

I've adjusted the description, including SRU template of this bug to
better fit what we found out and the solution that was applied.

** Description changed:

+ === Begin SRU Template ===
+ [Impact]
+ The systemd networking.service unit will bring down the loopback device (lo)
+ when it is stopped.  This behavior differs from the behavior in other
+ Ubuntu releases (upstart's networking.conf), where 'lo' is not taken down.
+ 
+ The problem that was seen was that iscsi root over ipv6 would hang on
+ shutdown.  
+ 
+ [Test Case]
+ Test is fairly simple and can be demonstrated in lxc container.
+ The key is really that the lo device should not have its link set down
+ after stopping networking.service.  So, below:
+   out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
+ 
+ should not show 'empty', but should have LOOPBACK,UP,LOWER in its
+ output.
+ 
+ $ release=yakkety; name=y1
+ $ lxc launch ubuntu-daily:$release $name
+ $ sleep 10
+ $ lxc exec $name /bin/bash
+ 
+ ## show only things that are up (note output has LOOPBACK,UP,LOWER_UP)
+ % ip link show dev lo
+ 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ 
+ % ip address show dev lo up
+ 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+valid_lft forever preferred_lft forever
+ 
+ ## Stop the service and show lo link is down (no 'UP' or 'LOWER_UP').
+ % systemctl stop networking.service
+ % ip link show dev lo
+ 1: lo:  mtu 65536 qdisc noqueue state DOWN mode DEFAULT group 
default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
+ empty
+ 
+ ## Now enable proposed, install update, reboot and show.
+ % rel=$(lsb_release -sc)
+ % echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
+ sudo tee /etc/apt/sources.list.d/proposed.list
+ % sudo apt update -qy && sudo apt install -qy ifupdown  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ % ip address show dev lo up
+ 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+valid_lft forever preferred_lft forever
+ % systemctl stop networking.service
+ % ip link show dev lo
+ 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
+ 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+valid_lft forever preferred_lft forever
+ 
+ 
+ [Regression Potential]
+ Should be pretty low.  zesty and  yakkety-proposed have this.
+ Taking down 'lo' is often cause of problems, and never the solution to
+ problems as far as I'm aware.
+ 
+ [Other Info]
+ 
+ === End SRU Template ===
+ 
  With the switch to systemd, all support for iscsi root (and other)
  filesystems disappeared, since shutdown yanks the rug out from under us.
  
  Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
  creates..), the DEV check should be expanded to include iscsi devices,
  and networking.service ExecStop should honor those checks.
  
  Related bugs:
-   * bug 1229458: grub2 needed changes
-   * bug 1621615: network not configured when ipv6 netbooted into cloud-init
-   * bug 1621507: ipv6 network boot does not work
- 
- [Impact]
- 
- With the changes from the above, the iscsi root (at least in the ipv6
- case) gets disconneceted prior to clean shutdown (ifdown downs the
- interface), resulting in a failure to enlist, commission, or deploy
- cleanly under MAAS. (and a failure to cleanly unmount the root
- filesystem when it is over iscsi.)
- 
- [Test Case]
- 
- Given a MAAS 2.0 installation, and the packages in the other bugs,
- attempt to enlist, commission, or deploy a host with xenial.
- 
- [Regression potential]
- 
- This restores the pre-xenial behavior of not shutting down the interface
- if there are network drives at the time that neworking is stopped
- (making it a no-op.)  The additional change is to detect "/dev/disk/by-
- path/*-iscsi-*" as a network disk, replacing the check for the existence
- of /etc/iscsi/iscsi.initramfs, which was only

[Touch-packages] [Bug 1646140] Re: Radeon Xpress 200M - performance regression in video playback with Wily stack (Vivid is last working stack)

2016-11-30 Thread Timo Aaltonen

why did you file this again, isn't 1610591 enough?

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

Title:
  Radeon Xpress 200M - performance regression in video playback with
  Wily stack (Vivid is last working stack)

Status in mesa package in Ubuntu:
  New

Bug description:
  After updating the Ubuntu HWE stack in 14.04 to Wily (kernel 4.2 and
  xserver-xorg-video-radeon-lts-wily), system boots up fine, but screen
  is laggy; although DRI3 is now enabled (according to Xorg.0.log), 2D
  acceleration seems to be gone.

  System is an older Pentium laptop (Packard Bell EasyNote) with a
  Radeon Xpress 200M chip (r300 driver). Video acceleration was working
  with DRI2 under the Vivid stack (kernel 3.19-64-lowlatency + xserver-
  xorg-video-radeon-lts-vivid).

  I'm using a 14.04 LTS-based distro, ElementaryOS, with vanilla Ubuntu HWE 
stacks.
  (Testing with Oibaf's PPA or Xorg-edgers repo did not solve the problem 
either, so I purged the PPAs and reverted to official Ubuntu sources)

  We already bisected and tested Xorg versions with the package
  maintainers, and could not determine a consistent culprit, so the
  suggestion is that perhaps a newer Mesa version after Vivid is
  impairing video acceleration in 2D content display. Which Mesa package
  could be showing a regression, I do not know how to assess, so I'm
  eager for your input.

  Here is the original report, with logs and bisect results:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598593

  Tell me what else you need, I'll get it for you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1646140/+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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-11-30 Thread Florian Stalzer

Martynas, Luke

Here it goes, without headphones paired it gives me this:
/var/log/syslog:Nov 30 18:53:11 fury-M90z pulseaudio[1082]: [pulseaudio] 
source.c: Default and alternate sample rates are the same.
/var/log/syslog:Nov 30 18:53:37 fury-M90z pulseaudio[1403]: [pulseaudio] 
source.c: Default and alternate sample rates are the same.
/var/log/syslog:Nov 30 18:53:37 fury-M90z pulseaudio[1419]: [pulseaudio] pid.c: 
Daemon already running.
/var/log/syslog.1:Nov 29 19:52:54 fury-M90z pulseaudio[1404]: [pulseaudio] 
source.c: Default and alternate sample rates are the same.
/var/log/syslog.1:Nov 29 19:54:26 fury-M90z pulseaudio[2328]: [pulseaudio] 
source.c: Default and alternate sample rates are the same.
/var/log/syslog.1:Nov 29 19:54:26 fury-M90z pulseaudio[2346]: [pulseaudio] 
pid.c: Daemon already running.

After I paired for a 1 second (and it crashes), it gives me this:

/var/log/syslog:Nov 30 18:53:11 fury-M90z pulseaudio[1082]: [pulseaudio] 
source.c: Default and alternate sample rates are the same.
/var/log/syslog:Nov 30 18:53:37 fury-M90z pulseaudio[1403]: [pulseaudio] 
source.c: Default and alternate sample rates are the same.
/var/log/syslog:Nov 30 18:53:37 fury-M90z pulseaudio[1419]: [pulseaudio] pid.c: 
Daemon already running.
/var/log/syslog.1:Nov 29 19:52:54 fury-M90z pulseaudio[1404]: [pulseaudio] 
source.c: Default and alternate sample rates are the same.
/var/log/syslog.1:Nov 29 19:54:26 fury-M90z pulseaudio[2328]: [pulseaudio] 
source.c: Default and alternate sample rates are the same.
/var/log/syslog.1:Nov 29 19:54:26 fury-M90z pulseaudio[2346]: [pulseaudio] 
pid.c: Daemon already running.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when

[Touch-packages] [Bug 1646080] Re: Mir-backed InputDeviceModel’s count property is not updated timely

2016-11-30 Thread Lorn Potter

** Changed in: qtsystems-opensource-src (Ubuntu)
   Importance: Undecided => High

** Changed in: qtsystems-opensource-src (Ubuntu)
   Status: New => In Progress

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

Title:
  Mir-backed InputDeviceModel’s count property is not updated timely

Status in qtsystems-opensource-src package in Ubuntu:
  In Progress

Bug description:
  I’m trying to use InputDeviceModel from QML with the following
  example:

  import QtQuick 2.4
  import QtSystemInfo 5.5
  Item {
InputDeviceModel {
  id: idm
  filter: InputInfo.Mouse
  onCountChanged: console.log("mice model count:", devices, count)
  onAdded: console.log("added mouse:", inputDevice, count)
  onRemoved: console.log("removed mouse:", deviceId, count)
}
readonly property bool hasMouse: idm.count > 0
onHasMouseChanged: console.log("has mouse:", hasMouse)
  }

  When I launch the example with qmlscene on my arale with no mouse
  connected, I’m not seeing any output (expected).

  Then I connect a bluetooth keyboard/mouse combo, and I’m seeing the following:
mice model count: 1 0
added mouse: QInputDevice(0x17f6298) 1
(note how 'hasMouse', which supposedly was initially false, hasn’t been 
updated)

  Then I disconnect the combo, and I’m seeing the following:
mice model count: 0 1
has mouse: true
removed mouse: 15 0

  Then I connect it again, and I’m seeing the following:
mice model count: 1 0
has mouse: false
added mouse: QInputDevice(0x18ee508) 1

  It appears the countChanged property is emitted before a device is
  added to/removed from the model, and thus the row count hasn’t
  actually been updated yet. So any property binding that relies on
  'count' will have an incorrect value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+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 1598300] Re: CUPS web interface stops responding after a while

2016-11-30 Thread Alessandro albanese

Hi!
I have same problem.
Ubuntu 16.04.1.
When login in localhost:631, to work with printer's, after some minutes, cups 
go down, and i see with sudo service cups status, he is inactive.
Problem occur only when logged on web interface, else no.

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1449555] Re: password request for cryptswap1 during boot when encrypted home directory selected

2016-11-30 Thread Samir M

*** This bug is a duplicate of bug 1453738 ***
https://bugs.launchpad.net/bugs/1453738

+1 to the list of folks who say this bug is still active. It's quite
annoying in 16.04 LTS, I get this message almost every time I use some
"sudo " command.

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

Title:
  password request for cryptswap1 during boot when encrypted home
  directory selected

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  On a system freshly installed (haven't tried the upgrade route) where
  the user selects to encrypt their home directory, they will get a
  password prompt during boot and at other times on the command-line
  requesting a password for cryptswap1.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: cryptsetup 2:1.6.1-1ubuntu7
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 28 09:02:12 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-28 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  crypttab: cryptswap1 UUID=c9d10691-df3f-49ae-a734-cdf2cbbaee8e /dev/urandom 
swap,offset=1024,cipher=aes-xts-plain64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449555/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

** Changed in: ifupdown (Ubuntu Xenial)
   Status: Confirmed => In Progress

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

Title:
  networking stop incorrectly disconnects from (network) root filesystem

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  In Progress
Status in ifupdown source package in Yakkety:
  Fix Committed
Status in ifupdown package in Debian:
  New

Bug description:
  With the switch to systemd, all support for iscsi root (and other)
  filesystems disappeared, since shutdown yanks the rug out from under
  us.

  Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
  creates..), the DEV check should be expanded to include iscsi devices,
  and networking.service ExecStop should honor those checks.

  Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1621507: ipv6 network boot does not work

  [Impact]

  With the changes from the above, the iscsi root (at least in the ipv6
  case) gets disconneceted prior to clean shutdown (ifdown downs the
  interface), resulting in a failure to enlist, commission, or deploy
  cleanly under MAAS. (and a failure to cleanly unmount the root
  filesystem when it is over iscsi.)

  [Test Case]

  Given a MAAS 2.0 installation, and the packages in the other bugs,
  attempt to enlist, commission, or deploy a host with xenial.

  [Regression potential]

  This restores the pre-xenial behavior of not shutting down the
  interface if there are network drives at the time that neworking is
  stopped (making it a no-op.)  The additional change is to detect
  "/dev/disk/by-path/*-iscsi-*" as a network disk, replacing the check
  for the existence of /etc/iscsi/iscsi.initramfs, which was only
  created by debian-installer (and maas until recently).

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1629972/+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 1592040] Re: Can't update repos due to signing problems

2016-11-30 Thread Christian Doczkal

I can confirm that removing /etc/apt/trusted.gpg* and then running "sudo
apt-key update" to regenerate the trust store from the one stored in the
package resolves the issue. I could even copy back the entries from
/etc/apt/trusted.gpg.d.

It still might be worthwhile to find out what caused the apparent
corruption of "/etc/apt/trusted.gpg".

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

Title:
  Can't update repos due to signing problems

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I can't update the repos through 'sudo apt-get update' due to these
  errors:

  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial InRelease: Errore 
sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial InRelease' is not 
signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-updates InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-updates InRelease' 
is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-backports InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-backports 
InRelease' is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-security InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-security 
InRelease' is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  The /etc/apt/sources.list contains only the official Ubuntu repo since
  it's untouched from a clean 16.04 install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1592040/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

I've verified that networking.service does not take down 'lo' interface
with the proposed version in yakkety (0.8.13ubuntu3).

Below, first  I show the problem in 0.8.13ubuntu2 and then install
the proposed version and show it fixed.

$ lxc  launch ubuntu-daily:yakkety y1
$ sleep 10
$ lxc exec y1 /bin/bash

% dpkg-query --show ifupdown
ifupdown 0.8.13ubuntu2

## show only things that are up (note output has LOOPBACK,UP,LOWER_UP)
% ip link show dev lo
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

% ip address show dev lo up
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever

## Stop the service and show lo link is down (no 'UP' or 'LOWER_UP').
% systemctl stop networking.service
% ip link show dev lo
1: lo:  mtu 65536 qdisc noqueue state DOWN mode DEFAULT group default 
qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
% out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
empty

## Now enable proposed, install update, reboot and show.
% rel=$(lsb_release -sc)
% echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
sudo tee /etc/apt/sources.list.d/proposed.list
% sudo apt update -qy && sudo apt install -qy ifupdown  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
% ip address show dev lo up
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
% systemctl stop networking.service
% ip link show dev lo
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
% out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever




** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  networking stop incorrectly disconnects from (network) root filesystem

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  Confirmed
Status in ifupdown source package in Yakkety:
  Fix Committed
Status in ifupdown package in Debian:
  New

Bug description:
  With the switch to systemd, all support for iscsi root (and other)
  filesystems disappeared, since shutdown yanks the rug out from under
  us.

  Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
  creates..), the DEV check should be expanded to include iscsi devices,
  and networking.service ExecStop should honor those checks.

  Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1621507: ipv6 network boot does not work

  [Impact]

  With the changes from the above, the iscsi root (at least in the ipv6
  case) gets disconneceted prior to clean shutdown (ifdown downs the
  interface), resulting in a failure to enlist, commission, or deploy
  cleanly under MAAS. (and a failure to cleanly unmount the root
  filesystem when it is over iscsi.)

  [Test Case]

  Given a MAAS 2.0 installation, and the packages in the other bugs,
  attempt to enlist, commission, or deploy a host with xenial.

  [Regression potential]

  This restores the pre-xenial behavior of not shutting down the
  interface if there are network drives at the time that neworking is
  stopped (making it a no-op.)  The additional change is to detect
  "/dev/disk/by-path/*-iscsi-*" as a network disk, replacing the check
  for the existence of /etc/iscsi/iscsi.initramfs, which was only
  created by debian-installer (and maas until recently).

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1629972/+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 1646170] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-11-30 Thread Till Kamppeter

*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966

** This bug has been marked a duplicate of bug 1642966
   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Nov 30 17:08:20 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-07-21 (132 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for HP-Photosmart-5520-series: 
usb://HP/Photosmart%205520%20series?serial=CN43Q726400602=1
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Papersize: a4
  PpdFiles: HP-Photosmart-5520-series: HP Photosmart 5520 Series, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic.efi.signed 
root=UUID=dd936384-ef9f-4dd3-a56b-9ea1ec36585b ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic.efi.signed 
root=UUID=dd936384-ef9f-4dd3-a56b-9ea1ec36585b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H110M-S2H DDR3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2HDDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1646170/+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 1646015] Re: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

** Package changed: ubuntu => audit (Ubuntu)

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

Title:
  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

Status in audit package in Ubuntu:
  New

Bug description:
  HI

  I have the docker image for ubuntu 16.04 and 16.10 .  In both I  was
  tried to install the auditd but getting the following  error.

  apt-get install auditdReading package lists... Done
  Building dependency tree... Done
  The following additional packages will be installed:
  libauparse0
  Suggested packages:
  audispd-plugins
  The following NEW packages will be installed:
  auditd libauparse0
  0 upgraded, 2 newly installed, 0 to remove and 21 not upgraded.
  Need to get 224 kB of archives.
  After this operation, 753 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://archive.ubuntu.com/ubuntu yakkety/main amd64 libauparse0 amd64 
1:2.6.6-1ubuntu1 [38.6 kB]
  Get:2 http://archive.ubuntu.com/ubuntu yakkety/main amd64 auditd amd64 
1:2.6.6-1ubuntu1 [186 kB]
  Fetched 224 kB in 0s (409 kB/s)
  debconf: delaying package configuration, since apt-utils is not installed
  Selecting previously unselected package libauparse0:amd64.
  (Reading database ... 6501 files and directories currently installed.)
  Preparing to unpack .../0-libauparse0_1%3a2.6.6-1ubuntu1_amd64.deb ...
  Unpacking libauparse0:amd64 (1:2.6.6-1ubuntu1) ...
  Selecting previously unselected package auditd.
  Preparing to unpack .../1-auditd_1%3a2.6.6-1ubuntu1_amd64.deb ...
  Unpacking auditd (1:2.6.6-1ubuntu1) ...
  Setting up libauparse0:amd64 (1:2.6.6-1ubuntu1) ...
  Setting up auditd (1:2.6.6-1ubuntu1) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Processing triggers for libc-bin (2.24-0ubuntu1) ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1646015/+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 1646183] [NEW] /usr/bin/content-hub-service:6:__gnu_cxx::__verbose_terminate_handler:cxxabiv1::terminate:std::terminate:cxxabiv1::cxa_throw:ubuntu::app_launch::Applicatio

2016-11-30 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
content-hub.  This problem was most recently seen with package version 
0.2+17.04.20161026-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/5698163e41c2d459cff5207646128d201ae4ea30 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

** Affects: content-hub (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid zesty

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

Title:
  /usr/bin/content-hub-
  
service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:ubuntu::app_launch::Application::create

Status in content-hub package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
content-hub.  This problem was most recently seen with package version 
0.2+17.04.20161026-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/5698163e41c2d459cff5207646128d201ae4ea30 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1646183/+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 1446537] Re: apport hook fails in add_info with TypeError: 'str' does not support the buffer interface

I utilized the version of the package from -proposed and did not receive
a crash.

 $ PYTHONPATH='' ubuntu-bug ubiquity 
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import GLib, Wnck, GdkX11, Gdk
dpkg-query: no packages found matching ubiquity

 $ apt-cache policy apport
apport:
  Installed: 2.20.1-0ubuntu2.2
  Candidate: 2.20.1-0ubuntu2.2
  Version table:
 *** 2.20.1-0ubuntu2.2 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main i386 Packages
100 /var/lib/dpkg/status
 2.20.1-0ubuntu2.1 500
500 http://192.168.10.7/ubuntu xenial-updates/main amd64 Packages
500 http://192.168.10.7/ubuntu xenial-updates/main i386 Packages
 2.20.1-0ubuntu2 500
500 http://192.168.10.7/ubuntu xenial/main amd64 Packages
500 http://192.168.10.7/ubuntu xenial/main i386 Packages


** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  apport hook fails in add_info with TypeError: 'str' does not support
  the buffer interface

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed

Bug description:
  Impact
  --
  Some apport package hooks are not able to check the contents of log files for 
errors, e.g. looking for hard disk errors in ubiquity install logs, so we may 
be getting crash reports that we don't want.

  
  Test Case
  -
  ⟫ ubuntu-bug ubiquity
  dpkg-query: aucun paquet ne correspond à ubiquity
  ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
    File "/usr/share/apport/package-hooks/source_ubiquity.py", line 61, in 
add_info
  if 'Buffer I/O error on device' in syslog:
  TypeError: 'str' does not support the buffer interface

  With the version of the package in the archive you'll see the above
  Traceback, with the version of proposed you will not.

  Regression Potential
  
  The change uses a try, except clause to do the decoding of the log file so 
there should be little chance of a regression.

  
  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 21 10:15:56 2015
  InstallationDate: Installed on 2013-09-03 (594 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 
(20130902)SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1446537/+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 1646178] [NEW] video problems

2016-11-30 Thread joe

Public bug reported:

Running 16.04, after update, new Nvidia driver (304.132) caused login
loop - resorted to nouveau driver and have arbitrary crashes and weird
boot issues. Have not been able to reinstall old Nvidia (304.131).  Have
been checking the forum and see similar problems, nothing seems to work.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Nov 30 11:19:56 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] 
[103c:2a58]
InstallationDate: Installed on 2013-01-01 (1428 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
Lsusb:
 Bus 001 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless 
keyboard/mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: HP-Pavilion GX614AA-ABA a6330f
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=1ede16fa-23c2-4f4d-8b28-b9318d2ff433 ro splash quiet
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.13
dmi.board.name: NARRA2
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 2.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.13:bd10/29/2007:svnHP-Pavilion:pnGX614AA-ABAa6330f:pvr:rvnASUSTekComputerINC.:rnNARRA2:rvr2.00:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: GX614AA-ABA a6330f
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Nov 30 10:40:59 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMLK wireless combo   KEYBOARD, id 8
 inputMLK wireless combo   KEYBOARD, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install ubuntu 
xenial

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

Title:
  video problems

Status in xorg package in Ubuntu:
  New

Bug description:
  Running 16.04, after update, new Nvidia driver (304.132) caused login
  loop - resorted to nouveau driver and have arbitrary crashes and weird
  boot issues. Have not been able to reinstall old Nvidia (304.131).
  Have been checking the forum and see similar problems, nothing seems
  to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 30 11:19:56 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])

[Touch-packages] [Bug 1646015] [NEW] update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

You have been subscribed to a public bug:

HI

I have the docker image for ubuntu 16.04 and 16.10 .  In both I  was
tried to install the auditd but getting the following  error.

apt-get install auditdReading package lists... Done
Building dependency tree... Done
The following additional packages will be installed:
libauparse0
Suggested packages:
audispd-plugins
The following NEW packages will be installed:
auditd libauparse0
0 upgraded, 2 newly installed, 0 to remove and 21 not upgraded.
Need to get 224 kB of archives.
After this operation, 753 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu yakkety/main amd64 libauparse0 amd64 
1:2.6.6-1ubuntu1 [38.6 kB]
Get:2 http://archive.ubuntu.com/ubuntu yakkety/main amd64 auditd amd64 
1:2.6.6-1ubuntu1 [186 kB]
Fetched 224 kB in 0s (409 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libauparse0:amd64.
(Reading database ... 6501 files and directories currently installed.)
Preparing to unpack .../0-libauparse0_1%3a2.6.6-1ubuntu1_amd64.deb ...
Unpacking libauparse0:amd64 (1:2.6.6-1ubuntu1) ...
Selecting previously unselected package auditd.
Preparing to unpack .../1-auditd_1%3a2.6.6-1ubuntu1_amd64.deb ...
Unpacking auditd (1:2.6.6-1ubuntu1) ...
Setting up libauparse0:amd64 (1:2.6.6-1ubuntu1) ...
Setting up auditd (1:2.6.6-1ubuntu1) ...
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Processing triggers for libc-bin (2.24-0ubuntu1) ...

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


** Tags: bot-comment
-- 
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
https://bugs.launchpad.net/bugs/1646015
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to audit in Ubuntu.

-- 
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 1644062] Re: googletest 1.8.0-2 (on zesty) breaks existing builds [add_library cannot create target "gmock" ...]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2180

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

Title:
  googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
  cannot create target "gmock" ...]

Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Fix Committed
Status in cmake-extras package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in googletest package in Ubuntu:
  Won't Fix
Status in mir package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  In Progress

Bug description:
  After upgrading to 1.8.0-2 (from 1.7.0-4), our previously-working
  builds break:

  CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock" because another target with the
 same name already exists.  The existing target is a static library created
 in source directory "/usr/src/googletest/googlemock".  See documentation
 for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:84 (cxx_library)


   CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock_main" because another target with
 the same name already exists.  The existing target is a static library
 created in source directory "/usr/src/googletest/googlemock".  See
 documentation for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:89 (cxx_library)


   CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
 install TARGETS given target "gmock" which does not exist in this
 directory.

  The CMakeLists.txt in our project that triggers this error does this:

  set(old_cxx_flags ${CMAKE_CXX_FLAGS})
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -Wno-old-style-cast 
-Wno-missing-field-initializers")
  find_package(GMock)
  set(CMAKE_CXX_FLAGS ${old_cxx_flags})

  This used to work fine, but no breaks on zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644062/+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 1646080] Re: Mir-backed InputDeviceModel’s count property is not updated timely

2016-11-30 Thread Ubuntu Foundations Team Bug Bot

The attachment "fix-1646080.patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Mir-backed InputDeviceModel’s count property is not updated timely

Status in qtsystems-opensource-src package in Ubuntu:
  New

Bug description:
  I’m trying to use InputDeviceModel from QML with the following
  example:

  import QtQuick 2.4
  import QtSystemInfo 5.5
  Item {
InputDeviceModel {
  id: idm
  filter: InputInfo.Mouse
  onCountChanged: console.log("mice model count:", devices, count)
  onAdded: console.log("added mouse:", inputDevice, count)
  onRemoved: console.log("removed mouse:", deviceId, count)
}
readonly property bool hasMouse: idm.count > 0
onHasMouseChanged: console.log("has mouse:", hasMouse)
  }

  When I launch the example with qmlscene on my arale with no mouse
  connected, I’m not seeing any output (expected).

  Then I connect a bluetooth keyboard/mouse combo, and I’m seeing the following:
mice model count: 1 0
added mouse: QInputDevice(0x17f6298) 1
(note how 'hasMouse', which supposedly was initially false, hasn’t been 
updated)

  Then I disconnect the combo, and I’m seeing the following:
mice model count: 0 1
has mouse: true
removed mouse: 15 0

  Then I connect it again, and I’m seeing the following:
mice model count: 1 0
has mouse: false
added mouse: QInputDevice(0x18ee508) 1

  It appears the countChanged property is emitted before a device is
  added to/removed from the model, and thus the row count hasn’t
  actually been updated yet. So any property binding that relies on
  'count' will have an incorrect value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+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 1646170] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-11-30 Thread Mario Passeri

Public bug reported:

package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog:
 
Date: Wed Nov 30 17:08:20 2016
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-07-21 (132 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lpstat: device for HP-Photosmart-5520-series: 
usb://HP/Photosmart%205520%20series?serial=CN43Q726400602=1
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
Papersize: a4
PpdFiles: HP-Photosmart-5520-series: HP Photosmart 5520 Series, hpcups 3.16.3
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic.efi.signed 
root=UUID=dd936384-ef9f-4dd3-a56b-9ea1ec36585b ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic.efi.signed 
root=UUID=dd936384-ef9f-4dd3-a56b-9ea1ec36585b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.2.15
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/23/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H110M-S2H DDR3-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2HDDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package need-duplicate-check third-party-packages yakkety

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Nov 30 17:08:20 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-07-21 (132 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for HP-Photosmart-5520-series: 
usb://HP/Photosmart%205520%20series?serial=CN43Q726400602=1
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Papersize: a4
  PpdFiles: HP-Photosmart-5520-series: HP Photosmart 5520 Series, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic.efi.signed 
root=UUID=dd936384-ef9f-4dd3-a56b-9ea1ec36585b ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic.efi.signed 
root=UUID=dd936384-ef9f-4dd3-a56b-9ea1ec36585b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H110M-S2H DDR3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2HDDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte

[Touch-packages] [Bug 1432935] Re: ntpd -x steps clock on leap second (upstream bug: 2745)

** Also affects: ntp (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  ntpd -x steps clock on leap second (upstream bug: 2745)

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Trusty:
  New

Bug description:
  in http://bugs.ntp.org/show_bug.cgi?id=2745
   | With older versions it was possible to use the -x option to avoid upsetting
   | applications running on the system when the clock is stepped due to a leap
   | second.
   | 
   | It seems in 4.2.6 was added support for inserting/deleting leap seconds on
   | systems without kernel discipline. However, the clock is now stepped even 
when
   | the -x option or tinker step is used to disable stepping.

  I'm not sure this bug could affect Ubuntu's ntp packages, but I
  believe that this information is IMPORTANT for some ubuntu users.

  Note: This bug is copied from
  https://rhn.redhat.com/errata/RHBA-2015-0690.html, thanks Red Hat.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1432935/+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 1646168] [NEW] hadoop crash on ubuntu 16.04

2016-11-30 Thread Jacek Sroka

Public bug reported:

I'm trying to run custom installed hadoop 2.7.3 on ubuntu 16.04. When I
run a map reduce job I'm being logged out (this does not happen always).
I've looked at
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1610499 and
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637026. I
confirmed that I have procps - 2:3.3.10-4ubuntu2.2 installed, yet the
bug still persists.

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


** Tags: regression-update

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

Title:
  hadoop crash on ubuntu 16.04

Status in procps package in Ubuntu:
  New

Bug description:
  I'm trying to run custom installed hadoop 2.7.3 on ubuntu 16.04. When
  I run a map reduce job I'm being logged out (this does not happen
  always). I've looked at
  https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1610499 and
  https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637026. I
  confirmed that I have procps - 2:3.3.10-4ubuntu2.2 installed, yet the
  bug still persists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1646168/+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 1610499] Re: hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process group

2016-11-30 Thread Jacek Sroka

*** This bug is a duplicate of bug 1637026 ***
https://bugs.launchpad.net/bugs/1637026

I still get this bug on 16.04 LTS after updating my system. I've looked
at https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637026 and
confirmed that I have procps - 2:3.3.10-4ubuntu2.2

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

Title:
  hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process
  group

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  when i run hadoop in ubuntu 16.04, ssh will exit, all process which
  belong to hadoop user will be killed ,through debug ,i found the
  /bin/kill in ubuntu16.04 has a bug , it has bug in killing process
  group   .

  Ubuntu version is:

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  (1)The way to repeat this bug
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .

  (2)Cause analysis
  The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,

  -1 mean it will kill all the process .

  (3)The bug in procps-3.3.10/skill.c ,I think the code "pid =
  (long)('0' - optopt) " is not right .

  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
    case '?':
  if (!isdigit(optopt)) {
  xwarnx(_("invalid argument %c"), optopt);
  kill_usage(stderr);
  } else {
  /* Special case for signal digit negative
   * PIDs */
  pid = (long)('0' - optopt);

  if (kill((pid_t)pid, signo) != 0)
   exitvalue = EXIT_FAILURE;
  exit(exitvalue);
  }
  loop=0;
  }

  (4) the cause
   sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal to 
kill this jvm process ,it is a normal behavior for hadoop to kill a task and 
then reexecute this task. but with this kill bug ,it kill all the process 
belong to a hadoop user .

  (5) The way to workaround
   I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way . I also think it is better to ask procps-3.3.10 maintainer to 
solve their bug,but i don't know how to contact them .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1610499/+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 1485752] Re: drop oneiric /run compatibility link

I've verified this using the steps described in the SRU template
$ dpkg-query --show overlayroot 
overlayroot 0.27ubuntu1.3


** Description changed:

  === Begin SRU Template ===
- [Impact] 
+ [Impact]
  overlayfs writes some log information to the tmpfs that was intended
  to be then viewable after the pivot_root to the real root.
  The path used was /dev/.initramfs.  Due to changes in initramfs-tools
  under this bug, that path was no longer supported.  And the logging
  was busted.
-   
+ 
  There was no functional problem with this except in the crypt use
  case as described in bug 1634310.
-   
+ 
  [Test Case]
  1.) Start an instance of a cloud image.
- 
+ 
  2.) Enable proposed and install overlayroot to show fix.
- $ rel=$(lsb_release -sc)
- $ echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
- $ sudo tee /etc/apt/sources.list.d/proposed.list
- $ sudo apt update -qy && sudo apt install -qy overlayroot http://archive.ubuntu.com/ubuntu $rel-proposed main" |
+ $ sudo tee /etc/apt/sources.list.d/proposed.list
+ $ sudo apt update -qy && sudo apt install -qy overlayroot http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/overlayroot/scripts/init-bottom/overlayroot
  [2] 
http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/revision/112
  
  === End SRU Template ===
  
- 
- Drop: Maintain compatibility with pre- /run configurations -- this was for 
compatibility with oneiric which is now long gone.
+ Drop: Maintain compatibility with pre- /run configurations -- this was
+ for compatibility with oneiric which is now long gone.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  drop oneiric /run compatibility link

Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  overlayfs writes some log information to the tmpfs that was intended
  to be then viewable after the pivot_root to the real root.
  The path used was /dev/.initramfs.  Due to changes in initramfs-tools
  under this bug, that path was no longer supported.  And the logging
  was busted.

  There was no functional problem with this except in the crypt use
  case as described in bug 1634310.

  [Test Case]
  1.) Start an instance of a cloud image.

  2.) Enable proposed and install overlayroot to show fix.
  $ rel=$(lsb_release -sc)
  $ echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
  $ sudo tee /etc/apt/sources.list.d/proposed.list
  $ sudo apt update -qy && sudo apt install -qy overlayroot http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/overlayroot/scripts/init-bottom/overlayroot
  [2] 
http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/revision/112

  === End SRU Template ===

  Drop: Maintain compatibility with pre- /run configurations -- this was
  for compatibility with oneiric which is now long gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1485752/+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 1598300] Re: CUPS web interface stops responding after a while

Another consideration is that the web interface is optional, whereas the
failure in bug 1642966 will happen for some proportion of users with a
default installation.

To be clear, I'm not saying that we shouldn't release this SRU; just
that some consideration and discussion is warranted to consider the
trade-off in both directions.

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1598300] Re: CUPS web interface stops responding after a while

> To the SRU team: Bug 1642966 cannot be caused by the fix for this bug.

I agree. But nevertheless, users may still get errors when upgrading,
and won't get errors if we don't release this SRU. So the failures would
still be a consequence of releasing this SRU, so I think we should care.

> Bug 1642966 is probably caused by some coincidence which had also
broken any other update of the cups package.

Agreed. I did some investigation, and I think it's a race. I added some
details in that bug.

So the question is: do we release this SRU in the knowledge that it will
cause failures for some users (quite a large number given the numbers
affected in bug 1642966), or do we defer until we can have a fix for
that bug too?

How important is it that this SRU lands sooner, rather than waiting and
bundling a fix for bug 1642966 at the same time?

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-11-30 Thread Jeff

Luke,

Just an FYI:  Your fix resolved an issue with using bluetooth speakers
to connect via A2DP.  I was finally able to validate the fix once it was
pushed to stable.  So, thank you and I apologize for not testing this
during the "proposed" testing!

It appears there may be multiple issues given what others are reporting.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1646080] Re: Mir-backed InputDeviceModel’s count property is not updated timely

2016-11-30 Thread Olivier Tilloy

Attaching a simple patch that fixes the issue for me. Please review!

** Patch added: "fix-1646080.patch"
   
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+attachment/4785330/+files/fix-1646080.patch

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

Title:
  Mir-backed InputDeviceModel’s count property is not updated timely

Status in qtsystems-opensource-src package in Ubuntu:
  New

Bug description:
  I’m trying to use InputDeviceModel from QML with the following
  example:

  import QtQuick 2.4
  import QtSystemInfo 5.5
  Item {
InputDeviceModel {
  id: idm
  filter: InputInfo.Mouse
  onCountChanged: console.log("mice model count:", devices, count)
  onAdded: console.log("added mouse:", inputDevice, count)
  onRemoved: console.log("removed mouse:", deviceId, count)
}
readonly property bool hasMouse: idm.count > 0
onHasMouseChanged: console.log("has mouse:", hasMouse)
  }

  When I launch the example with qmlscene on my arale with no mouse
  connected, I’m not seeing any output (expected).

  Then I connect a bluetooth keyboard/mouse combo, and I’m seeing the following:
mice model count: 1 0
added mouse: QInputDevice(0x17f6298) 1
(note how 'hasMouse', which supposedly was initially false, hasn’t been 
updated)

  Then I disconnect the combo, and I’m seeing the following:
mice model count: 0 1
has mouse: true
removed mouse: 15 0

  Then I connect it again, and I’m seeing the following:
mice model count: 1 0
has mouse: false
added mouse: QInputDevice(0x18ee508) 1

  It appears the countChanged property is emitted before a device is
  added to/removed from the model, and thus the row count hasn’t
  actually been updated yet. So any property binding that relies on
  'count' will have an incorrect value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+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

Re: [Touch-packages] [Bug 1644595] Re: krb5-1.13.2+dfsg-5 source contains source subject to the aladdin license

2016-11-30 Thread Sam Hartman

As a FYI, upstream has relicensed the file under their standard license
with permission from the author.
Coming to Debian soon.

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

Title:
  krb5-1.13.2+dfsg-5 source contains source subject to the aladdin
  license

Status in Kerberos:
  Unknown
Status in krb5 package in Ubuntu:
  Confirmed

Bug description:
  The krb5-1.13.2+dfsg-5 package source contains a file autolock.hxx  in
  the directory
  
krb5-1.13.2+dfsg-5\krb5_1.13.2+dfsg.orig\krb5-1.13.2+dfsg\src\ccapi\common\win\OldCC.
  Although not declared in any other licensing file for this package the
  file contains comments indicating its subject to the Aladdin license
  which has implications for any commercial distribution of the
  software, specifically:

  “2(a) Distribution of the Program or any work based on the Program by
  a commercial organization to any third party is prohibited if any
  payment is made in connection with such distribution, whether directly
  (as in payment for a copy fo the Program) or indirectly (as in payment
  for some service related to the Program, or payment for some product
  or service that includes a copy of the Program ‘without charge’ . . .”

  This file clearly is not needed or used for any Linux build as it
  appears specific to windows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kerberos/+bug/1644595/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

I can reproduce my original example on Xenial on a different machine,
and now I see that it is a race. Whether I drop the sleeps or not, it
sometimes gives me "Job for cups.service canceled." and sometimes:

Warning: Stopping cups.service, but it can still be activated by:
  cups.path

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

I'm getting some stranger behaviour on Zesty.

1) cups.path doesn't seem to be started until after reboot.
2) I can't reliably reproduce my example case. After the second stop, 
cups.service is claimed to have been stopped successfully, but a subsequent 
call to "systemctl status cups.service" shows it as still running.
3) I have seen the failure case from my example in my testing on Zesty, after 
fiddling with combinations of commands from my example, but I don't have steps 
to get there.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1646140] [NEW] Radeon Xpress 200M - performance regression in video playback with Wily stack (Vivid is last working stack)

2016-11-30 Thread indigocat

Public bug reported:

After updating the Ubuntu HWE stack in 14.04 to Wily (kernel 4.2 and
xserver-xorg-video-radeon-lts-wily), system boots up fine, but screen is
laggy; although DRI3 is now enabled (according to Xorg.0.log), 2D
acceleration seems to be gone.

System is an older Pentium laptop (Packard Bell EasyNote) with a Radeon
Xpress 200M chip (r300 driver). Video acceleration was working with DRI2
under the Vivid stack (kernel 3.19-64-lowlatency + xserver-xorg-video-
radeon-lts-vivid).

I'm using a 14.04 LTS-based distro, ElementaryOS, with vanilla Ubuntu HWE 
stacks.
(Testing with Oibaf's PPA or Xorg-edgers repo did not solve the problem either, 
so I purged the PPAs and reverted to official Ubuntu sources)

We already bisected and tested Xorg versions with the package
maintainers, and could not determine a consistent culprit, so the
suggestion is that perhaps a newer Mesa version after Vivid is impairing
video acceleration in 2D content display. Which Mesa package could be
showing a regression, I do not know how to assess, so I'm eager for your
input.

Here is the original report, with logs and bisect results:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598593

Tell me what else you need, I'll get it for you.

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


** Tags: acceleration dri mesa radeon

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

Title:
  Radeon Xpress 200M - performance regression in video playback with
  Wily stack (Vivid is last working stack)

Status in mesa package in Ubuntu:
  New

Bug description:
  After updating the Ubuntu HWE stack in 14.04 to Wily (kernel 4.2 and
  xserver-xorg-video-radeon-lts-wily), system boots up fine, but screen
  is laggy; although DRI3 is now enabled (according to Xorg.0.log), 2D
  acceleration seems to be gone.

  System is an older Pentium laptop (Packard Bell EasyNote) with a
  Radeon Xpress 200M chip (r300 driver). Video acceleration was working
  with DRI2 under the Vivid stack (kernel 3.19-64-lowlatency + xserver-
  xorg-video-radeon-lts-vivid).

  I'm using a 14.04 LTS-based distro, ElementaryOS, with vanilla Ubuntu HWE 
stacks.
  (Testing with Oibaf's PPA or Xorg-edgers repo did not solve the problem 
either, so I purged the PPAs and reverted to official Ubuntu sources)

  We already bisected and tested Xorg versions with the package
  maintainers, and could not determine a consistent culprit, so the
  suggestion is that perhaps a newer Mesa version after Vivid is
  impairing video acceleration in 2D content display. Which Mesa package
  could be showing a regression, I do not know how to assess, so I'm
  eager for your input.

  Here is the original report, with logs and bisect results:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598593

  Tell me what else you need, I'll get it for you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1646140/+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 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

2016-11-30 Thread Julian Andres Klode

Not sure about the ubiquity task, though, I unmerged the other bug
reports (which actually are 2 distinct ones), but did not mark it as
fixed again.

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

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  In Progress
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  [Impact]
  Breaks installation in some non-English locales.

  [Test case]
  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  [Regression potential]
  Very low, we're running this in 1.3 since a long time. The fix depends on 
another one that restricts the Date parser to accept only UTC time zones in 
Release files, though (we do not understand the other ones anyway), and thus 
might reject some repositories it silently accepted in a wrong way previously 
(we have not seen anyone report a regression yet since uploading that in June).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1611010/+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 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

2016-11-30 Thread Julian Andres Klode

These are different bugs.Or rather, we definitely fixed the

if float(percent) != self.percent or status_str != self.status:
Aug 8 13:49:44 ubuntu /plugininstall.py: ValueError: could not convert string 
to float: '0,'

thing here. And to keep our sanity (especially WRT to the SRU fixing
that), we do need this bug closed, otherwise everything becomes a mess.

** Changed in: apt (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  In Progress
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  [Impact]
  Breaks installation in some non-English locales.

  [Test case]
  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  [Regression potential]
  Very low, we're running this in 1.3 since a long time. The fix depends on 
another one that restricts the Date parser to accept only UTC time zones in 
Release files, though (we do not understand the other ones anyway), and thus 
might reject some repositories it silently accepted in a wrong way previously 
(we have not seen anyone report a regression yet since uploading that in June).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1611010/+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 1627697] Re: gnome-terminal crashes on resize

2016-11-30 Thread Alan Griffiths

gtk seems to be fixed on 17.04

** Changed in: miral
   Status: Fix Committed => Fix Released

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

Title:
  gnome-terminal crashes on resize

Status in MirAL:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Yakkety, Mir-0.24, lp:miral

  Run gnome-terminal on a touchscreen laptop and resizing by three-
  finger pinch...

  $ miral-run gnome-terminal
  $ 
  (gnome-terminal-server:4817): Gtk-WARNING **: GtkSettings Cursor Theme: 
Unsupported GDK backend
  ...
  (gnome-terminal-server:4817): Gdk-WARNING **: unknown property 
gtk-fontconfig-timestamp

  (gnome-terminal-server:4817): Gdk-WARNING **: Ignoring unknown Mir
  event 11

  (gnome-terminal-server:4817): Gtk-WARNING **: Allocating size to GtkBox 
0x55eb906c6900 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  *** Error in `/usr/lib/gnome-terminal/gnome-terminal-server': double free or 
corruption (out): 0x7f2e70258010 ***

  (Can't reproduce with Mir-0.1, but that may be because resize was too
  broken.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/miral/+bug/1627697/+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 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2016-11-30 Thread Deon Blaauw

Having the same issue. As a workaround, I have also found that the
headphones are detected after suspending the laptop. I have a Dell XPS
15 running Ubuntu 16.04.

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

I think this might be caused by an interesting interaction between
systemd, debhelper and the CUPS scheduler.

I can reproduce a very similar error with the following. I think (though
am not sure) that this is related to the root cause. On a fresh Xenial
system:

sudo apt-get update && sudo apt-get -y install cups
sudo -i
systemctl stop cups.service
sleep 4
touch /var/cache/cups/org.cups.cupsd
sleep 4
sudo rm /var/cache/cups/org.cups.cupsd
sleep 4
systemctl stop cups.service

(the sleeps are to avoid any unknown, additional and unintentional race
conditions)

This results in an exit status of 1 and the message "Job for
cups.service canceled." which matches the error that reporters have been
seeing.

In other words, if cups.service is started via cups.path, that cause is
removed, and then we request a manual stop of cups.service, then systemd
refuses to stop the service the first time (a retry always succeeds for
me).

In cups-daemon.prerm, debhelper has added "deb-systemd-invoke stop
cups.path" followed by "invoke-rc.d cups stop || exit $?". I believe the
second invocation is ultimately equivalent to "systemctl stop
cups.service" and fails the same way as in my example, causing the prerm
to exit 1, causing the dpkg failure reported.

I'm not sure of the intended logic for /lib/systemd/system/cups.path
here. AFAICT, it exists because when using CUPS with launchd, the CUPS
daemon leaves the file in place as long as it doesn't want to be
terminated, and removes it when it wants to be terminated before it
exits anyway. Is this because launchd kills daemons itself unless the
keepalive file exists?

With systemd, I can't find any documentation that suggests that systemd
ever intends to automatically kill a socket activated daemon. AFAICT,
it's entirely up to the daemon when it chooses to exit. So there appears
to be no need for cupsd to maintain /var/cache/cups/org.cups.cupsd when
running under systemd.

As configured right now, systemd will also start cupsd if
/var/cache/cups/org.cups.cupsd is created while cupsd is not running. I
can't find anything that might use this function. So either this is an
accidental side-effect that is not needed, or I have missed some other
path that does need this.

systemd talks about CUPS in a blog post that is relevant:
http://0pointer.de/blog/projects/socket-activation2.html. Note that this
only sets up a path unit for /var/spool/cups, not any kind of keepalive
file for cupsd.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1613949] Re: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial

2016-11-30 Thread zacktu

My workaround was to rename ~/.vimrc effectively removing it. Now I can
use vi with no error messages.

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

Title:
  vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu
  16.04.1 Xenial

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  I have a fresh install of Ubuntu v16.04.1, then I did an `apt-get
  upgrade` and it only had a few seemingly-minor packages to upgrade
  (don't remember the list, sorry).

  Apparently all the core vim packages have been upgraded to
  2:7.4.1689-3ubuntu1.1 but vim-gtk3 (and all the other gvim-providing
  packages I tested) are still held back to 2:7.4.1689-3ubuntu1 so there
  is a version mis-match.

  Now I get the following error:

  [[[ BEGIN PASTE ]]]

  root@machine:/# apt-get install vim-gtk3
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   vim-gtk3 : Depends: vim-common (= 2:7.4.1689-3ubuntu1) but 
2:7.4.1689-3ubuntu1.1 is to be installed
  Depends: vim-runtime (= 2:7.4.1689-3ubuntu1) but 
2:7.4.1689-3ubuntu1.1 is to be installed
  E: Unable to correct problems, you have held broken packages.

  [[[ END PASTE ]]]

  
  However I can still get gvim working if I force the installation of the 
vim-gtk3 package using dpkg.  Of course this is not a good solution, because it 
leaves my system in a state of seemingly-broken packages!

  
  [[[ BEGIN PASTE ]]]

  root@machine:/# dpkg -i --force-depends ./vim-gtk3_7.4.1689-3ubuntu1_amd64.deb
  Selecting previously unselected package vim-gtk3.
  (Reading database ... 251539 files and directories currently installed.)
  Preparing to unpack .../vim-gtk3_7.4.1689-3ubuntu1_amd64.deb ...
  Unpacking vim-gtk3 (2:7.4.1689-3ubuntu1) ...
  dpkg: vim-gtk3: dependency problems, but configuring anyway as you requested:
   vim-gtk3 depends on vim-common (= 2:7.4.1689-3ubuntu1); however:
Version of vim-common on system is 2:7.4.1689-3ubuntu1.1.
   vim-gtk3 depends on vim-runtime (= 2:7.4.1689-3ubuntu1); however:
Version of vim-runtime on system is 2:7.4.1689-3ubuntu1.1.

  Setting up vim-gtk3 (2:7.4.1689-3ubuntu1) ...
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vim (vim) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vimdiff 
(vimdiff) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rvim (rvim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rview 
(rview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vi (vi) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/view (view) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/ex (ex) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/editor 
(editor) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvim (gvim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gview 
(gview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgview 
(rgview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgvim 
(rgvim) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/evim (evim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/eview 
(eview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvimdiff 
(gvimdiff) in auto mode

  [[[ END PASTE ]]]

  
  And yes, I can confirm that gvim actually works using this method.  We just 
need to upgrade the package versioning so that we don't have a problem with the 
apt-get packaging dependency system.

  Thanks for all your hard work.  Ubuntu is #1!!!  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1613949/+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 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

And bug #1637756.

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

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Triaged
Status in ubiquity package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  In Progress
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  [Impact]
  Breaks installation in some non-English locales.

  [Test case]
  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  [Regression potential]
  Very low, we're running this in 1.3 since a long time. The fix depends on 
another one that restricts the Date parser to accept only UTC time zones in 
Release files, though (we do not understand the other ones anyway), and thus 
might reject some repositories it silently accepted in a wrong way previously 
(we have not seen anyone report a regression yet since uploading that in June).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1611010/+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 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

It looks like this has regressed on 17.10, see bug #1638142.


** Changed in: ubiquity (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: apt (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Triaged
Status in ubiquity package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  In Progress
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  [Impact]
  Breaks installation in some non-English locales.

  [Test case]
  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  [Regression potential]
  Very low, we're running this in 1.3 since a long time. The fix depends on 
another one that restricts the Date parser to accept only UTC time zones in 
Release files, though (we do not understand the other ones anyway), and thus 
might reject some repositories it silently accepted in a wrong way previously 
(we have not seen anyone report a regression yet since uploading that in June).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1611010/+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 1432935] Re: ntpd -x steps clock on leap second (upstream bug: 2745)

2016-11-30 Thread ChristianEhrhardt

I've backported the fix (actually adapted the backport that existed).
But given that this is a very rare case and we are targeting an SRU eventually 
I'd want somebody else to test and confirm the fix.

To ease to do so I've made a ppa available at:
https://launchpad.net/~paelzer/+archive/ubuntu/bug-1432935-leap-x

Please report if this fixes the issue for you so that we can go on
processing that as an SRU.

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

Title:
  ntpd -x steps clock on leap second (upstream bug: 2745)

Status in ntp package in Ubuntu:
  Fix Released

Bug description:
  in http://bugs.ntp.org/show_bug.cgi?id=2745
   | With older versions it was possible to use the -x option to avoid upsetting
   | applications running on the system when the clock is stepped due to a leap
   | second.
   | 
   | It seems in 4.2.6 was added support for inserting/deleting leap seconds on
   | systems without kernel discipline. However, the clock is now stepped even 
when
   | the -x option or tinker step is used to disable stepping.

  I'm not sure this bug could affect Ubuntu's ntp packages, but I
  believe that this information is IMPORTANT for some ubuntu users.

  Note: This bug is copied from
  https://rhn.redhat.com/errata/RHBA-2015-0690.html, thanks Red Hat.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1432935/+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 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers