[Touch-packages] [Bug 1651938] Re: Owncloud Account doesn't work with Nextcloud 11

[Alberto Mardegan]

Hi Slash, thanks for reporting this bug. As I understand from your logs,
it's not even possible to create a nextcloud account; can you please
confirm this?

Anyway, this looks like a bug in the Nextcloud server implementation:
CSRF is not something that normally affects REST APIs, which are
stateless by definition. When registering the account, we are passing
username and password with every function call.

Please file a bug against Nextcloud, and write here the link to the
report, so that I can comment in case they ask for more information.

For the record, the API we are using when verifying whether the account is 
valid is /ocs/v1.php/person/check, which is documented here:
https://www.freedesktop.org/wiki/Specifications/open-collaboration-services/#index4h4

I think they forced the CSRF check on all API, including the public REST
APIs, by mistake.

** Changed in: account-plugins (Ubuntu)
   Status: New => Incomplete

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

Title:
  Owncloud Account doesn't work with Nextcloud 11

Status in account-plugins package in Ubuntu:
  Incomplete

Bug description:
  Dear,

  Since my nextcloud server update i cannot connect anymore to my calendar.
  My contacts with syncevolution no problem. 

  I think i found why, nextcloud reduce the CRSF vulnerability

  phablet@ubuntu-phablet:~$   export OAU_LOGGING_LEVEL=2
  phablet@ubuntu-phablet:~$   export OAU_DAEMON_TIMEOUT=
  phablet@ubuntu-phablet:~$   online-accounts-service
  service.cpp 42 requestAccess Got request: QMap(("application", 
QVariant(QString, "system-settings") ) ( "pid" ,  QVariant(uint, 26947) ) ( 
"provider" ,  QVariant(QString, "owncloud") ) ( "windowId" ,  QVariant(uint, 
26947) ) ) 
  App ID: "unconfined"
  request-manager.cpp 113 runQueue Head: OnlineAccountsUi::Request(0x1d829d8)
  mir-helper.cpp 151 session_event_callback Prompt Session state updated to 1
  Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
  ui-server.cpp 103 onDataReady QMap(("code", QVariant(QString, "process") ) ( 
"data" ,  QVariant(QVariantMap, QMap(("application", QVariant(QString, 
"system-settings") ) ( "pid" ,  QVariant(uint, 26947) ) ( "provider" ,  
QVariant(QString, "owncloud") ) ( "windowId" ,  QVariant(uint, 26947) ) ) ) ) ( 
"id" ,  QVariant(int, 0) ) ( "interface" ,  QVariant(QString, 
"com.ubuntu.OnlineAccountsUi") ) ( "profile" ,  QVariant(QString, "unconfined") 
) ) 
  qml: Page_QMLTYPE_24(0x1973a38)"ownCloud": In Ubuntu.Components 1.3, the use 
of Page.title, Page.flickable and Page.head is deprecated. Use Page.header and 
the PageHeader component instead.
  file:///home/phablet/.local/share/accounts/qml-plugins/owncloud/Main.qml: 
File not found
  virtual void OnlineAccountsPlugin::Plugin::registerTypes(const char*) 
Ubuntu.OnlineAccounts.Plugin
  request.cpp 115 setWindow Requesting window reparenting
  QWindow::fromWinId(): platform plugin does not support foreign windows.
  APP_ID isn't set, the handler ignored
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  qml: Trying host https://server as login:password
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  

[Touch-packages] [Bug 1652228] [NEW] package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt

[Roberto]

Public bug reported:

I already try to reinstall the package

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
Uname: Linux 3.13.0-106-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.14.1-0ubuntu3.23
AptOrdering: gir1.2-gst-plugins-base-1.0: Configure
Architecture: amd64
Date: Thu Dec 22 07:53:26 2016
DpkgTerminalLog:
 dpkg: error processing package gir1.2-gst-plugins-base-1.0 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
DuplicateSignature: package:gir1.2-gst-plugins-base-1.0:1.2.4-1~ubuntu2:package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2014-07-29 (878 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: gst-plugins-base1.0
Title: package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-base1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gst-plugins-base1.0 package in Ubuntu:
  New

Bug description:
  I already try to reinstall the package

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-106-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.14.1-0ubuntu3.23
  AptOrdering: gir1.2-gst-plugins-base-1.0: Configure
  Architecture: amd64
  Date: Thu Dec 22 07:53:26 2016
  DpkgTerminalLog:
   dpkg: error processing package gir1.2-gst-plugins-base-1.0 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature: 
package:gir1.2-gst-plugins-base-1.0:1.2.4-1~ubuntu2:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-07-29 (878 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: gst-plugins-base1.0
  Title: package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1652228/+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 1339749] Re: [enhancement] android hwc overlay could optimize movement of surfaces without buffer update

[Daniel van Vugt]

** Changed in: mir
   Importance: Medium => Low

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

** Changed in: mir
   Status: Confirmed => Triaged

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

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

Title:
  [enhancement] android hwc overlay could optimize movement of surfaces
  without buffer update

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Currently, we check in the hwc code that a buffer has changed from the
  previous commit to avoid submitting the same thing to the screen
  twice. This does not factor in changes to the the screen positioning.
  If it did, we could optimize a few more scenarios using 2d
  acceleration.

  This won't  cause rendering glitches, just a bit worse performance in
  some non-critical-path scenarios.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1339749/+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 1377872] Re: Double-buffered compositing performance is sometimes very poor (30 FPS) on intel

[Daniel van Vugt]

Hmm it seems this bug refuses to expire.

Can't be reproduced any more and only happens using a rendering approach
we have never used.

** No longer affects: mesa

** Changed in: mir
   Status: Incomplete => New

** Changed in: mir
   Status: New => Incomplete

** Changed in: mir
   Status: Incomplete => Invalid

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Double-buffered compositing performance is sometimes very poor (30
  FPS) on intel

Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  Double-buffered compositing performance is sometimes artificially poor
  on some intel systems. When this happens the frame rate seen is halved
  - about 30 FPS. However at the same time, Mir is observed to use very
  little render time and both the CPU and GPU are still mostly idle.
  It's just the Intel DRM logic sometimes takes two frames (~32ms) to
  complete a single page flip.

  Two known workarounds avoid the issue:
(a) Add glFinish() into the mesa DisplayBuffer code; or
(b) env INTEL_DEBUG=sync for the Mir server binary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1377872/+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 1651944] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1651944

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  Kernel panic when we call pipework to setup virtual network for docker
  containers

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I found a kernel panic issue when I was using pipework to config the
  network of a docker container on an x86 board with all-snap image. The
  issue is related to the auditing module of Linux kernel. So it should
  be an issue of pc-kernel-snap.

  I created a simple test snap to reproduce the issue and upload it to github.
  https://github.com/pliu6/docker-snap-test

  Software environment to reproduce the bug:
  #snap list
  Name Version Rev  Developer  Notes
  core 16.04.1 714  canonical  -
  docker   1.11.2-956   canonical  devmode
  dockertest   0.0.1   x12 devmode
  pc   16.04-0.8   9canonical  -
  pc-kernel4.4.0-53-2  51   canonical  -

  The log is below:
  [  504.783341] BUG: unable to handle kernel paging request at 
fff3 
  [  504.867186] IP: [] strlen+0x0/0x20 
  [  504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0  
  [  504.976588] Oops:  [#1] SMP  
  [  505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT 
nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack 
  iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c
  fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid 
i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables 
aut
  ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 
usb_storage ahci libahci 
  [  505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 
4.4.0-53-generic #74-Ubuntu 
  [  505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 
04/05/2014 
  [  505.787738] task: 880037637080 ti: 880061a7 task.ti: 
880061a7 
  [  505.877382] RIP: 0010:[]  [] 
strlen+0x0/0x20 
  [  505.966192] RSP: 0018:880061a73a20  EFLAGS: 00010246 
  [  506.029835] RAX: 880061a73b20 RBX: fff3 RCX: 
 
  [  506.115320] RDX: 014e RSI: fff3 RDI: 
fff3 
  [  506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 
880061a73a94 
  [  506.286283] R10: 000e R11: 88005c835131 R12: 
88007aff0480 
  [  506.371767] R13: 880037637080 R14: 81399fc0 R15: 
fff3 
  [  506.457251] FS:  7fa9f36aa740() GS:88007df0() 
knlGS: 
  [  506.554170] CS:  0010 DS:  ES:  CR0: 80050033 
  [  506.623014] CR2: fff3 CR3: 7853e000 CR4: 
06e0 
  [  506.708497] Stack: 
  [  506.732624]  81122a1a 88007aff0480 880061a73b00 
880061a73a60 
  [  506.822056]  8139a028 88007aff0480 880061a73b00 
880037637080 
  [  506.911490]  880061a73ad8 8136f088 812285c0 
880061a73af0 
  [  507.000926] Call Trace: 
  [  507.030263]  [] ? audit_log_untrustedstring+0x1a/0x30 
  [  507.109502]  [] audit_cb+0x68/0x3f0 
  [  507.170027]  [] common_lsm_audit+0x1b8/0x740 
  [  507.239910]  [] ? alloc_inode+0x50/0x90 
  [  507.304593]  [] ? prepend_path+0xc6/0x2a0 
  [  507.371358]  [] aa_audit+0x5f/0x170 
  [  507.431880]  [] audit_mount+0x152/0x160 
  [  507.496567]  [] match_mnt_path_str+0x1dd/0x490 
  [  507.568529]  [] ? dentry_path+0x18/0x70 
  [  507.633213]  [] match_mnt+0xda/0x150 
  [  507.694776]  [] aa_bind_mount+0x100/0x180 
  [  507.761540]  [] wrap_apparmor_sb_mount+0x1c0/0x270 
  [  507.837664]  [] security_sb_mount+0x57/0x80 
  [  507.906506]  [] do_mount+0xab/0xde0 
  [  507.967032]  [] ? __kmalloc_track_caller+0x1b4/0x250 
  [  508.045236]  [] ? hrtimer_try_to_cancel+0xd1/0x130 
  [  508.121361]  [] ? memdup_user+0x42/0x70 
  [  508.186042]  [] SyS_mount+0x9f/0x100 
  [  508.247607]  [] entry_SYSCALL_64_fastpath+0x16/0x71 
  [  508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f 
b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8
  0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 

[Touch-packages] [Bug 1610952] Re: upgrade error

[Launchpad Bug Tracker]

[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/1610952

Title:
  upgrade error

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Upgraded system from 14.04 LTS to 16.04 LTS using the online system updates 
that are regularly used by me as this is my workstation.
  Once finished only one of three monitors would show the desktop and login 
prompt.
  Once my password was entered a short dialogue box appeared and it showed I 
had an error.
  The screen within about 3 seconds after I typed my password was able to show 
the error which was ambiguous, then logged me out. I was stuck with a system 
that runs my workstation, and unable to login.
  I chose to use a DVD and run the set-up from a disk, I had done the online 
update option. Once I did this I was able to work. I did choose to save my 
previous OS, however now I basicly have a triple boot system, as I already had 
a dual boot, from Debian 8 , to Ubuntu that works fine, now I have a generic 
Ubuntu that is at the latest version, my set-up working upgraded system which 
works, and my other Debian system that works, Then I was able to go in and 
change my graphics card to use the non generic drive and login and set it to a 
Nvidia.  All works now.
  Current system 16.04 LTS
  Intel® Core™ i7-3770 CPU @ 3.40GHz × 8
  GeForce GTX 660/PCIe/SSE2
  64-bit

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:

  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: Mon Aug  8 07:54:26 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-34-generic, x86_64: installedError! Could not 
locate dkms.conf file.
   File:  does not exist.
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. GK106 [GeForce GTX 660] [3842:2662]
  InstallationDate: Installed on 2016-02-01 (188 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. XPS 8500
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/ubuntu--vg-root
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0NW73C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/19/2012:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0NW73C:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8500
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Aug  2 11:03:24 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post 

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

[Bug Watch Updater]

** Changed in: libvirt
   Status: Incomplete => Fix Released

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

  Please see comments for the problem description, and summary of
  originally bridged comments in the description.

  Sorry about the inconvenience.

  <...>

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1637601/+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 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers

[Seth Arnold]

I added linux back due to the uncanny resemblance to:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508737
and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586997

Thanks

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Kernel panic when we call pipework to setup virtual network for docker
  containers

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

Bug description:
  I found a kernel panic issue when I was using pipework to config the
  network of a docker container on an x86 board with all-snap image. The
  issue is related to the auditing module of Linux kernel. So it should
  be an issue of pc-kernel-snap.

  I created a simple test snap to reproduce the issue and upload it to github.
  https://github.com/pliu6/docker-snap-test

  Software environment to reproduce the bug:
  #snap list
  Name Version Rev  Developer  Notes
  core 16.04.1 714  canonical  -
  docker   1.11.2-956   canonical  devmode
  dockertest   0.0.1   x12 devmode
  pc   16.04-0.8   9canonical  -
  pc-kernel4.4.0-53-2  51   canonical  -

  The log is below:
  [  504.783341] BUG: unable to handle kernel paging request at 
fff3 
  [  504.867186] IP: [] strlen+0x0/0x20 
  [  504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0  
  [  504.976588] Oops:  [#1] SMP  
  [  505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT 
nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack 
  iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c
  fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid 
i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables 
aut
  ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 
usb_storage ahci libahci 
  [  505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 
4.4.0-53-generic #74-Ubuntu 
  [  505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 
04/05/2014 
  [  505.787738] task: 880037637080 ti: 880061a7 task.ti: 
880061a7 
  [  505.877382] RIP: 0010:[]  [] 
strlen+0x0/0x20 
  [  505.966192] RSP: 0018:880061a73a20  EFLAGS: 00010246 
  [  506.029835] RAX: 880061a73b20 RBX: fff3 RCX: 
 
  [  506.115320] RDX: 014e RSI: fff3 RDI: 
fff3 
  [  506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 
880061a73a94 
  [  506.286283] R10: 000e R11: 88005c835131 R12: 
88007aff0480 
  [  506.371767] R13: 880037637080 R14: 81399fc0 R15: 
fff3 
  [  506.457251] FS:  7fa9f36aa740() GS:88007df0() 
knlGS: 
  [  506.554170] CS:  0010 DS:  ES:  CR0: 80050033 
  [  506.623014] CR2: fff3 CR3: 7853e000 CR4: 
06e0 
  [  506.708497] Stack: 
  [  506.732624]  81122a1a 88007aff0480 880061a73b00 
880061a73a60 
  [  506.822056]  8139a028 88007aff0480 880061a73b00 
880037637080 
  [  506.911490]  880061a73ad8 8136f088 812285c0 
880061a73af0 
  [  507.000926] Call Trace: 
  [  507.030263]  [] ? audit_log_untrustedstring+0x1a/0x30 
  [  507.109502]  [] audit_cb+0x68/0x3f0 
  [  507.170027]  [] common_lsm_audit+0x1b8/0x740 
  [  507.239910]  [] ? alloc_inode+0x50/0x90 
  [  507.304593]  [] ? prepend_path+0xc6/0x2a0 
  [  507.371358]  [] aa_audit+0x5f/0x170 
  [  507.431880]  [] audit_mount+0x152/0x160 
  [  507.496567]  [] match_mnt_path_str+0x1dd/0x490 
  [  507.568529]  [] ? dentry_path+0x18/0x70 
  [  507.633213]  [] match_mnt+0xda/0x150 
  [  507.694776]  [] aa_bind_mount+0x100/0x180 
  [  507.761540]  [] wrap_apparmor_sb_mount+0x1c0/0x270 
  [  507.837664]  [] security_sb_mount+0x57/0x80 
  [  507.906506]  [] do_mount+0xab/0xde0 
  [  507.967032]  [] ? __kmalloc_track_caller+0x1b4/0x250 
  [  508.045236]  [] ? hrtimer_try_to_cancel+0xd1/0x130 
  [  508.121361]  [] ? memdup_user+0x42/0x70 
  [  508.186042]  [] SyS_mount+0x9f/0x100 
  [  508.247607]  [] entry_SYSCALL_64_fastpath+0x16/0x71 
  [  508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f 
b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8
  0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7  
  [  508.564156] RIP  [] strlen+0x0/0x20 
  [  508.624889]  RSP  
  [  508.96] CR2: fff3 
  [  508.706425] ---[ end trace 9a8196367a1a3630 ]---

To manage notifications about this bug go to:

[Touch-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers

[Peng]

Changed the target to be apparmor because the kernel panic is triggered
by apparmor.

** Package changed: linux (Ubuntu) => apparmor (Ubuntu)

** Also affects: apparmor
   Importance: Undecided
   Status: New

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

Title:
  Kernel panic when we call pipework to setup virtual network for docker
  containers

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

Bug description:
  I found a kernel panic issue when I was using pipework to config the
  network of a docker container on an x86 board with all-snap image. The
  issue is related to the auditing module of Linux kernel. So it should
  be an issue of pc-kernel-snap.

  I created a simple test snap to reproduce the issue and upload it to github.
  https://github.com/pliu6/docker-snap-test

  Software environment to reproduce the bug:
  #snap list
  Name Version Rev  Developer  Notes
  core 16.04.1 714  canonical  -
  docker   1.11.2-956   canonical  devmode
  dockertest   0.0.1   x12 devmode
  pc   16.04-0.8   9canonical  -
  pc-kernel4.4.0-53-2  51   canonical  -

  The log is below:
  [  504.783341] BUG: unable to handle kernel paging request at 
fff3 
  [  504.867186] IP: [] strlen+0x0/0x20 
  [  504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0  
  [  504.976588] Oops:  [#1] SMP  
  [  505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT 
nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack 
  iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c
  fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid 
i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables 
aut
  ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 
usb_storage ahci libahci 
  [  505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 
4.4.0-53-generic #74-Ubuntu 
  [  505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 
04/05/2014 
  [  505.787738] task: 880037637080 ti: 880061a7 task.ti: 
880061a7 
  [  505.877382] RIP: 0010:[]  [] 
strlen+0x0/0x20 
  [  505.966192] RSP: 0018:880061a73a20  EFLAGS: 00010246 
  [  506.029835] RAX: 880061a73b20 RBX: fff3 RCX: 
 
  [  506.115320] RDX: 014e RSI: fff3 RDI: 
fff3 
  [  506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 
880061a73a94 
  [  506.286283] R10: 000e R11: 88005c835131 R12: 
88007aff0480 
  [  506.371767] R13: 880037637080 R14: 81399fc0 R15: 
fff3 
  [  506.457251] FS:  7fa9f36aa740() GS:88007df0() 
knlGS: 
  [  506.554170] CS:  0010 DS:  ES:  CR0: 80050033 
  [  506.623014] CR2: fff3 CR3: 7853e000 CR4: 
06e0 
  [  506.708497] Stack: 
  [  506.732624]  81122a1a 88007aff0480 880061a73b00 
880061a73a60 
  [  506.822056]  8139a028 88007aff0480 880061a73b00 
880037637080 
  [  506.911490]  880061a73ad8 8136f088 812285c0 
880061a73af0 
  [  507.000926] Call Trace: 
  [  507.030263]  [] ? audit_log_untrustedstring+0x1a/0x30 
  [  507.109502]  [] audit_cb+0x68/0x3f0 
  [  507.170027]  [] common_lsm_audit+0x1b8/0x740 
  [  507.239910]  [] ? alloc_inode+0x50/0x90 
  [  507.304593]  [] ? prepend_path+0xc6/0x2a0 
  [  507.371358]  [] aa_audit+0x5f/0x170 
  [  507.431880]  [] audit_mount+0x152/0x160 
  [  507.496567]  [] match_mnt_path_str+0x1dd/0x490 
  [  507.568529]  [] ? dentry_path+0x18/0x70 
  [  507.633213]  [] match_mnt+0xda/0x150 
  [  507.694776]  [] aa_bind_mount+0x100/0x180 
  [  507.761540]  [] wrap_apparmor_sb_mount+0x1c0/0x270 
  [  507.837664]  [] security_sb_mount+0x57/0x80 
  [  507.906506]  [] do_mount+0xab/0xde0 
  [  507.967032]  [] ? __kmalloc_track_caller+0x1b4/0x250 
  [  508.045236]  [] ? hrtimer_try_to_cancel+0xd1/0x130 
  [  508.121361]  [] ? memdup_user+0x42/0x70 
  [  508.186042]  [] SyS_mount+0x9f/0x100 
  [  508.247607]  [] entry_SYSCALL_64_fastpath+0x16/0x71 
  [  508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f 
b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8
  0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7  
  [  508.564156] RIP  [] strlen+0x0/0x20 
  [  508.624889]  RSP  
  [  508.96] CR2: fff3 
  [  508.706425] ---[ end trace 9a8196367a1a3630 ]---

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

-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1651944] [NEW] Kernel panic when we call pipework to setup virtual network for docker containers

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I found a kernel panic issue when I was using pipework to config the
network of a docker container on an x86 board with all-snap image. The
issue is related to the auditing module of Linux kernel. So it should be
an issue of pc-kernel-snap.

I created a simple test snap to reproduce the issue and upload it to github.
https://github.com/pliu6/docker-snap-test

Software environment to reproduce the bug:
#snap list
Name Version Rev  Developer  Notes
core 16.04.1 714  canonical  -
docker   1.11.2-956   canonical  devmode
dockertest   0.0.1   x12 devmode
pc   16.04-0.8   9canonical  -
pc-kernel4.4.0-53-2  51   canonical  -

The log is below:
[  504.783341] BUG: unable to handle kernel paging request at fff3 
[  504.867186] IP: [] strlen+0x0/0x20 
[  504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0  
[  504.976588] Oops:  [#1] SMP  
[  505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT 
nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c
fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid 
i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables 
aut
ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage 
ahci libahci 
[  505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic 
#74-Ubuntu 
[  505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 
04/05/2014 
[  505.787738] task: 880037637080 ti: 880061a7 task.ti: 
880061a7 
[  505.877382] RIP: 0010:[]  [] 
strlen+0x0/0x20 
[  505.966192] RSP: 0018:880061a73a20  EFLAGS: 00010246 
[  506.029835] RAX: 880061a73b20 RBX: fff3 RCX: 
 
[  506.115320] RDX: 014e RSI: fff3 RDI: 
fff3 
[  506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 
880061a73a94 
[  506.286283] R10: 000e R11: 88005c835131 R12: 
88007aff0480 
[  506.371767] R13: 880037637080 R14: 81399fc0 R15: 
fff3 
[  506.457251] FS:  7fa9f36aa740() GS:88007df0() 
knlGS: 
[  506.554170] CS:  0010 DS:  ES:  CR0: 80050033 
[  506.623014] CR2: fff3 CR3: 7853e000 CR4: 
06e0 
[  506.708497] Stack: 
[  506.732624]  81122a1a 88007aff0480 880061a73b00 
880061a73a60 
[  506.822056]  8139a028 88007aff0480 880061a73b00 
880037637080 
[  506.911490]  880061a73ad8 8136f088 812285c0 
880061a73af0 
[  507.000926] Call Trace: 
[  507.030263]  [] ? audit_log_untrustedstring+0x1a/0x30 
[  507.109502]  [] audit_cb+0x68/0x3f0 
[  507.170027]  [] common_lsm_audit+0x1b8/0x740 
[  507.239910]  [] ? alloc_inode+0x50/0x90 
[  507.304593]  [] ? prepend_path+0xc6/0x2a0 
[  507.371358]  [] aa_audit+0x5f/0x170 
[  507.431880]  [] audit_mount+0x152/0x160 
[  507.496567]  [] match_mnt_path_str+0x1dd/0x490 
[  507.568529]  [] ? dentry_path+0x18/0x70 
[  507.633213]  [] match_mnt+0xda/0x150 
[  507.694776]  [] aa_bind_mount+0x100/0x180 
[  507.761540]  [] wrap_apparmor_sb_mount+0x1c0/0x270 
[  507.837664]  [] security_sb_mount+0x57/0x80 
[  507.906506]  [] do_mount+0xab/0xde0 
[  507.967032]  [] ? __kmalloc_track_caller+0x1b4/0x250 
[  508.045236]  [] ? hrtimer_try_to_cancel+0xd1/0x130 
[  508.121361]  [] ? memdup_user+0x42/0x70 
[  508.186042]  [] SyS_mount+0x9f/0x100 
[  508.247607]  [] entry_SYSCALL_64_fastpath+0x16/0x71 
[  508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f 
b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8
0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7  
[  508.564156] RIP  [] strlen+0x0/0x20 
[  508.624889]  RSP  
[  508.96] CR2: fff3 
[  508.706425] ---[ end trace 9a8196367a1a3630 ]---

** Affects: apparmor (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
Kernel panic when we call pipework to setup virtual network for docker 
containers
https://bugs.launchpad.net/bugs/1651944
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apparmor 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 1651617] Re: [regression] Unity8 is just a black screen on zesty

[Daniel van Vugt]

qtmir (0.5.1+17.04.20161216-0ubuntu2) zesty; urgency=medium

  * No-change rebuild against latest miral.

 -- Łukasz 'sil2100' Zemczak   Wed, 21 Dec
2016 10:07:36 +0100

** Package changed: unity8 (Ubuntu) => qtmir (Ubuntu)

** Changed in: qtmir (Ubuntu)
   Status: In Progress => Fix Released

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

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

Title:
  [regression] Unity8 is just a black screen on zesty

Status in Canonical System Image:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released

Bug description:
  [regression] Unity8 no longer visible (just a black screen) on zesty,
  although the process is running...

  Full unity8 log:

  [2016-12-21:09:20:26.624] qtmir.screens: ScreensModel::ScreensModel
  [2016-12-21 09:20:26.626872] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.25.0)
  [2016-12-21 09:20:26.626907] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.25.0)
  [2016-12-21 09:20:26.627018] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.25.0)
  [2016-12-21 09:20:26.627028] mirplatform: Found graphics driver: 
throw-on-creation (version 0.25.0)
  [2016-12-21:09:20:26.627] qtmir.mir: MirServer created
  [2016-12-21:09:20:26.627] qtmir.mir: Command line arguments passed to Qt: 
("unity8", "--mode=full-shell")
  [2016-12-21:09:20:26.628] QSocketNotifier: Can only be used with threads 
started with QThread
  [2016-12-21 09:20:26.629763] mirserver: Starting
  [2016-12-21 09:20:26.646283] mirserver: Using nested cursor
  [2016-12-21 09:20:26.646812] mirserver: Initial display configuration:
  [2016-12-21 09:20:26.646838] mirserver:   Output 36: VGA disconnected
  [2016-12-21 09:20:26.646843] mirserver:   Output 39: DisplayPort disconnected
  [2016-12-21 09:20:26.646846] mirserver:   Output 45: HDMI-A disconnected
  [2016-12-21 09:20:26.646850] mirserver:   Output 48: DisplayPort connected, 
used
  [2016-12-21 09:20:26.646856] mirserver:   Physical size 24.0" 520x320mm
  [2016-12-21 09:20:26.646860] mirserver:   Current mode 1920x1200 59.95Hz
  [2016-12-21 09:20:26.646863] mirserver:   Preferred mode 1920x1200 59.95Hz
  [2016-12-21 09:20:26.646866] mirserver:   Logical position +0+0
  [2016-12-21 09:20:26.646870] mirserver:   Output 52: HDMI-A disconnected
  [2016-12-21:09:20:26.646] qtmir.mir: 
PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x7fd54c1c09d0)
  [2016-12-21:09:20:26.646] qtmir.mir: SessionListener::SessionListener - this= 
SessionListener(0x7fd54c1c0660)
  [2016-12-21:09:20:26.647] qtmir.mir: 
MirWindowManagerImpl::MirWindowManagerImpl
  [2016-12-21 09:20:26.647386] mirserver: Mir version 0.25.0
  [2016-12-21:09:20:26.647] qtmir.screens: QtCompositor::start
  [2016-12-21:09:20:26.656] qtmir.screens: ScreensModel::update
  [2016-12-21:09:20:26.657] qtmir.sensor: Screen - nativeOrientation is: 
Qt::ScreenOrientation(LandscapeOrientation)
  [2016-12-21:09:20:26.657] qtmir.sensor: Screen - initial currentOrientation 
is: Qt::ScreenOrientation(LandscapeOrientation)
  [2016-12-21:09:20:26.659] qtmir.screens: Added Screen with id 48 and geometry 
QRect(0,0 1920x1200)
  [2016-12-21:09:20:26.659] qtmir.screens: Screen::setMirDisplayBuffer 
Screen(0x5608b9ff8fd0) 0x7fd54c140a30 0x7fd54c140b80
  [2016-12-21:09:20:26.659] qtmir.screens: 
===
  [2016-12-21:09:20:26.659] qtmir.screens: Screen(0x5608b9ff8fd0) - id: 48 
geometry: QRect(0,0 1920x1200) window: 0x0 type: "DisplayPort" scale: 1
  [2016-12-21:09:20:26.659] qtmir.screens: 
===
  [2016-12-21:09:20:26.725] qtmir.applications: 
UnityApplicationPlugin::registerTypes - this= 
UnityApplicationPlugin(0x7fd5340ee440) uri= Unity.Application
  [2016-12-21:09:20:26.758] QObject::connect: No such signal 
QDBusAbstractInterface::FlightModeChanged(bool) in 
/build/telephony-service-GdIWd2/telephony-service-0.1+17.04.20161129/libtelephonyservice/telepathyhelper.cpp:99
  [2016-12-21:09:20:27.365] file:///usr/share/unity8//OrientedShell.qml:253:5: 
Type Shell unavailable 
   Shell { 
   ^
  [2016-12-21:09:20:27.366] file:///usr/share/unity8//Shell.qml:267:9: Element 
is not creatable. 
   SurfaceManager { 
   ^
  [2016-12-21:09:20:27.366] qtmir.screens: Screen::setWindow - new geometry for 
shell surface ShellView(0x5608ba0ee230) QRect(0,0 1920x1200)
  [2016-12-21:09:20:27.366] qtmir.screens: ScreenWindow 0x5608ba118190 with 
window ID 1 backed by Screen(0x5608b9ff8fd0) with ID 48
  [2016-12-21:09:20:27.366] qtmir.screens: QWindow ShellView(0x5608ba0ee230) 
with geom QRect(0,0 1920x1200) is backed by a Screen(0x5608b9ff8fd0) with 
geometry QRect(0,0 1920x1200)
  [2016-12-21:09:20:27.367] qtmir.screens: 

[Touch-packages] [Bug 1652199] Re: pdftocairo pdf convert error

[park sang hoon]

** Description changed:

  Hi
  
  OS: ubuntu 16.04
+ comamnd : pdftcocairo -pdf samplefile.pdf output.pdf
  I have tested the attached pdf sample file to convert it to pdftocairo
  However, some charts and images seem to be broken.
  broken chart in 16p,46p in pdf sample file and broken image 71page
  
+ add test : evnince samplefile.pdf ... normally (not broken)
  
  In ubuntu 14.04 it is converted normally.
  
  Please help me ...

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

Title:
  pdftocairo pdf convert error

Status in poppler package in Ubuntu:
  New

Bug description:
  Hi

  OS: ubuntu 16.04
  comamnd : pdftcocairo -pdf samplefile.pdf output.pdf
  I have tested the attached pdf sample file to convert it to pdftocairo
  However, some charts and images seem to be broken.
  broken chart in 16p,46p in pdf sample file and broken image 71page

  add test : evnince samplefile.pdf ... normally (not broken)

  In ubuntu 14.04 it is converted normally.

  Please help me ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1652199/+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 1652199] Re: pdftocairo pdf convert error

[park sang hoon]

** Description changed:

  Hi
  
  OS: ubuntu 16.04
  I have tested the attached pdf sample file to convert it to pdftocairo
  However, some charts and images seem to be broken.
+ broken chart in 16p,46p in pdf sample file and broken image 71page
+ 
  
  In ubuntu 14.04 it is converted normally.
  
  Please help me ...

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

Title:
  pdftocairo pdf convert error

Status in poppler package in Ubuntu:
  New

Bug description:
  Hi

  OS: ubuntu 16.04
  I have tested the attached pdf sample file to convert it to pdftocairo
  However, some charts and images seem to be broken.
  broken chart in 16p,46p in pdf sample file and broken image 71page

  
  In ubuntu 14.04 it is converted normally.

  Please help me ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1652199/+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 1652199] [NEW] pdftocairo pdf convert error

[park sang hoon]

Public bug reported:

Hi

OS: ubuntu 16.04
I have tested the attached pdf sample file to convert it to pdftocairo
However, some charts and images seem to be broken.

In ubuntu 14.04 it is converted normally.

Please help me ...

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


** Tags: pdftocairo

** Attachment added: "pdf sample file"
   
https://bugs.launchpad.net/bugs/1652199/+attachment/4795556/+files/china_test1_source.pdf

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

Title:
  pdftocairo pdf convert error

Status in poppler package in Ubuntu:
  New

Bug description:
  Hi

  OS: ubuntu 16.04
  I have tested the attached pdf sample file to convert it to pdftocairo
  However, some charts and images seem to be broken.

  In ubuntu 14.04 it is converted normally.

  Please help me ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1652199/+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 861642] Re: upowerd uses 100% cpu till killed

[Max Barry]

Same as #8 with iPhone 6 and Ubuntu 16.10. CPU usage vanishes upon
tapping "Trust" on phone.

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

Title:
  upowerd uses 100% cpu till killed

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  top - 12:57:54 up  2:56,  3 users,  load average: 1.06, 1.12, 1.35
  Tasks: 219 total,   2 running, 216 sleeping,   0 stopped,   1 zombie
  Cpu0  : 70.2%us, 29.8%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu1  :  2.3%us,  1.3%sy,  0.0%ni, 96.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu2  :  1.0%us,  0.3%sy,  0.0%ni, 98.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu3  :  0.7%us,  1.6%sy,  0.0%ni, 97.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu4  :  0.0%us,  0.3%sy,  0.0%ni, 99.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu5  :  0.0%us,  0.3%sy,  0.0%ni, 98.3%id,  1.4%wa,  0.0%hi,  0.0%si,  0.0%st
  Mem:   5994176k total,  4198260k used,  1795916k free,63308k buffers
  Swap:  8193144k total,   355188k used,  7837956k free,   334316k cached

PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND  
  
   2268 root  20   0  148m 1572  680 R  100  0.0 111:08.37 upowerd

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: upower 0.9.9-4
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Sep 28 12:53:23 2011
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  ProcEnviron:
   
  SourcePackage: upower
  UpgradeStatus: Upgraded to natty on 2011-04-06 (175 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/861642/+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 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early

[Nico Orrù]

> ExecStop=/bin/sh -c "echo Stopping the system dbus-daemon is not
supported. Reboot the system instead.; exit 1"

This is nonsense and makes me wonder if I should switch back to Windows
instead.

Trolling intended.

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

Title:
  remote file systems hang on shutdown, D-BUS stops too early

Status in D-Bus:
  Won't Fix
Status in dbus package in Ubuntu:
  Fix Released

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1438612/+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 1652166] Re: Sync qtwebkit-opensource-src from Debian (enable webp)

[Jeremy Bicha]

The easiest way to stop something from autosyncing is to use an ubuntu#
version number! :)

We could just wait for the Qt 5.7 transition (in January I think): bug
1640290

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

Title:
  Sync qtwebkit-opensource-src from Debian (enable webp)

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

Bug description:
  The last merge from Debian has this changelog entry:

* Sync with Debian packaging, remaining changes:
  - Build without WebP (in universe)
  - Own .symbols file

  https://launchpad.net/ubuntu/+source/qtwebkit-opensource-src/5.6.1
  +dfsg-4ubuntu1~2

  But libwebp is in main and has been for a while. The only part that's
  in universe is the webp binary package which is not a dependency of
  anything (and honestly I don't know why it's not in main too, it's not
  mentioned on the MIR LP: #1186553 )

  https://people.canonical.com/~ubuntu-
  archive/madison.cgi?package=libwebp=on

  That leaves the only change as using an Ubuntu-specific symbols file.
  I don't know how Qt symbols work but maybe that's not needed anymore.

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

[Tyler Hicks]

I've completed my verification of the apparmor
2.10.95-0ubuntu2.5~14.04.1 SRU. Testing very went well and I did not
uncover any issues. I completed the entire Test Case as documented in
the bug description. The AppArmor test plan was completed on the 14.04
release and HWE kernels as well as all of the regression tests from QRT.
The manual testing of evince was also performed on the release and HWE
kernels. Additionally, I ran test-apparmor.py on the i386 release and
HWE kernels (all other tests were ran on amd64).

On the HWE kernel, I was able to test apparmor with the snapd in trusty-
proposed. The pwgen-tyhicks, hello-world, and lxd snaps all seemed to be
working correctly. I created a 16.04 LXD container and verified that
confinement was working as intended. I also verified that confinement
was working properly with hello-world.sh.

As for the 12.04 -> 14.04 upgrade testing, it also went very well. I
installed most major 12.04 packages containing an AppArmor profile, in
addition to what's present in a default desktop install, and performed
an upgrade:

$ sudo apt-get install slapd mysql-server clamav tcpdump ntp
...

$ sudo aa-status
...
26 profiles are in enforce mode.
   /sbin/dhclient
   /usr/bin/evince
   /usr/bin/evince-previewer
   /usr/bin/evince-previewer//launchpad_integration
   /usr/bin/evince-previewer//sanitized_helper
   /usr/bin/evince-thumbnailer
   /usr/bin/evince-thumbnailer//sanitized_helper
   /usr/bin/evince//launchpad_integration
   /usr/bin/evince//sanitized_helper
   /usr/bin/freshclam
   /usr/lib/NetworkManager/nm-dhcp-client.action
   /usr/lib/connman/scripts/dhclient-script
   /usr/lib/cups/backend/cups-pdf
   /usr/lib/lightdm/lightdm-guest-session
   /usr/lib/lightdm/lightdm-guest-session//chromium
   /usr/lib/telepathy/mission-control-5
   /usr/lib/telepathy/telepathy-*
   /usr/lib/telepathy/telepathy-*//pxgsettings
   /usr/lib/telepathy/telepathy-*//sanitized_helper
   /usr/lib/telepathy/telepathy-ofono
   /usr/sbin/cups-browsed
   /usr/sbin/cupsd
   /usr/sbin/mysqld
   /usr/sbin/ntpd
   /usr/sbin/slapd
   /usr/sbin/tcpdump
...

There were a couple denials logged but they didn't affect the upgrade:

$ grep DENIED /var/log/syslog
Dec 16 18:00:41 sec-precise-amd64 kernel: [ 8267.110822] type=1400 
audit(1481911241.875:29): apparmor="DENIED" operation="open" parent=6862 
profile="/usr/sbin/slapd" name="/etc/pkcs11/modules/" pid=6873 comm="slapd" 
requested_mask="r" denied_mask="r" fsuid=118 ouid=0
Dec 16 18:32:21 sec-precise-amd64 kernel: [ 1766.776830] type=1400 
audit(1481913141.561:35): apparmor="DENIED" operation="open" parent=1 
profile="/usr/sbin/mysqld" name="/proc/sys/vm/overcommit_memory" pid=29835 
comm="mysqld" requested_mask="r" denied_mask="r" fsuid=116 ouid=0

I then performed the same 12.04 -> 14.04 upgrade test except that I
didn't use the new apparmor from trusty-proposed and it turns out that I
see the same two AppArmor denials:

$ grep DENIED /var/log/syslog
Dec 16 21:03:18 sec-precise-amd64 kernel: [  739.903410] type=1400 
audit(1481922198.702:34): apparmor="DENIED" operation="open" parent=1 
profile="/usr/sbin/mysqld" name="/proc/sys/vm/overcommit_memory" pid=1679 
comm="mysqld" requested_mask="r" denied_mask="r" fsuid=116 ouid=0
Dec 16 21:03:18 sec-precise-amd64 kernel: [  740.079754] type=1400 
audit(1481922198.878:35): apparmor="DENIED" operation="open" parent=1747 
profile="/usr/sbin/slapd" name="/etc/pkcs11/modules/" pid=1760 comm="slapd" 
requested_mask="r" denied_mask="r" fsuid=118 ouid=0

In other words, the apparmor package from trusty-proposed does not
regress the 12.04 -> 14.04 upgrade process.

I feel like the apparmor 2.10.95-0ubuntu2.5~14.04.1 SRU has went through
very thorough testing and that it is good to go.

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

Title:
  Provide full AppArmor confinement for snaps on 14.04

Status in apparmor package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in apparmor source package in Trusty:
  Fix Committed
Status in dbus source package in Trusty:
  Fix Committed

Bug description:
  = 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 

[Touch-packages] [Bug 1641243] Re: Provide full AppArmor confinement for snaps on 14.04

[Tyler Hicks]

I've completed my verification of the dbus 1.6.18-0ubuntu4.5 SRU. The
documented Test Plan went as expected. It leverages extensive automated
tests that were written when the AppArmor D-Bus mediation patch set was
upstreamed into the D-Bus project. I am confident of the dbus SRU and
feel like it is ready to migrate from proposed.

I'm marking this bug as verification-done since both the apparmor and
dbus packages have been verified.

** 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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1641243

Title:
  Provide full AppArmor confinement for snaps on 14.04

Status in apparmor package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in apparmor source package in Trusty:
  Fix Committed
Status in dbus source package in Trusty:
  Fix Committed

Bug description:
  = 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 pushed changes to lp:qa-regression-testing which 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).

  Finally, we need to test that 12.04 -> 14.04 upgrades continue to
  work. Specifically, the apparmor packages in trusty-proposed and the
  12.04 kernel need to be tested together.

  [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 

[Touch-packages] [Bug 1450642] Re: seccomp missing many new syscalls

[Tyler Hicks]

I've completed my verification of the libseccomp 2.1.1-1ubuntu1~trusty1
SRU.

I followed the test plan and everything went as expected. I think this
SRU is good to go.

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

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

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

Title:
  seccomp missing many new syscalls

Status in Snappy:
  Fix Released
Status in Snappy 15.04 series:
  Fix Released
Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Trusty:
  Fix Committed
Status in libseccomp source package in Vivid:
  Fix Released
Status in libseccomp source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Several syscalls were discovered to be missing when using the launcher on 
snappy. These should be added so we may properly support seccomp filtering.

  [Test Case]
  seccomp itself has a comprehensive testsuite, and while it doesn't fail the 
build, regressions can be seen by looking at the build log. Eg:

  Regression Test Summary
  tests run: 6494
  tests skipped: 52
  tests passed: 6494
  tests failed: 0
  tests errored: 0

  Furthermore, on a snappy system, perform:
  # Note, for the 14.04 SRU, you'll have to install snapd from trusty-proposed
  $ sudo snappy install hello-world
  $ hello-world.env

  It should show the environment. On an arm system with 2.1.1-1 from the 
archive, this will fail due to a seccomp denial:
  audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 
pid=1491 comm="env" exe="/bin/bash" sig=31 arch=4028 syscall=983045 
compat=0 ip=0xb6fb0bd6 code=0x0

  (note, snappy images have a ppa fix for this, see notes below).

  To test the segfault fix, do:
  $ scmp_sys_resolver 1024
  Segmentation fault

  It should return:
  $ scmp_sys_resolver 1024
  UNKNOWN

  For the new 3.19 syscalls:
  $ scmp_sys_resolver getrandom
  -1

  it should return something like (actual number depends on arch, this is on 
armhf):
  $ scmp_sys_resolver getrandom
  384

  For the 14.04 SRU, test the following syscalls (expected results on
  amd64 are shown):

  $ scmp_sys_resolver getrandom
  318
  $ scmp_sys_resolver membarrier
  324
  $ scmp_sys_resolver userfaultfd
  323
  $ scmp_sys_resolver mlock2
  325

  
  autopkgtests for libseccomp have been added as part of this update to verify 
that the library recognizes all the syscalls from 3.19 and the private 
syscalls. These tests can be run like so (assuming you are in the unpacked 
source and the binaries are in ../binary):
  $ export REL=vivid
  $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source 
../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot 
autopkgtest-$REL-amd64 || echo "** AUTOPKGTESTS FAILED"

  Alternatively, if you don't have autopkgtest setup, you can do:
  $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev 
seccomp
  $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-filter
  ...
  PASS
  $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh 
./debian/tests/test-scmp_sys_resolver
  ...
  PASS

  Lastly, seccomp is used by lxc. lxc can be tested by using the test
  case as outlined in step 4 of
  https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only.

  [Regression Potential]
  If the above tests, regression potential is considered low. Unknown syscalls 
will continue to be handled as before.

  Description of changes:
  add finit_module:
  
https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15

  sync the syscall table entries - 3.16
  
https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75
  
https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4
  
https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd
  
https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb
  
https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718
  
https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a

  sync the syscall table entries - 3.17
  
https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9

  sync the syscall table entries - 3.19
  
https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3

  This should also be applied (fix a segfault for invalid syscall numbers):
  
https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3

  For the 14.04 SRU so that libseccomp can handle all of the syscalls in the 
4.4 based linux-lts-xenial kernel:
  - membarrier and userfaultfd syscalls:
    

[Touch-packages] [Bug 1163023] Re: GTK Compose Behaviour for "ć" Incorrect

[Adrianna Pińska]

I believe that this is a duplicate of Bug #919899.

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

Title:
  GTK Compose Behaviour for "ć" Incorrect

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  According to the GtkComposeTable:

  https://help.ubuntu.com/community/GtkComposeTable

  ćcapostrophe0107small C with acute

  This behaviour, and its capital version do not work. They instead
  produce "ç" and upper-case variant.

  Tested on 12.10 and 13.04 from March 27, 2013.

  Additionally: does not happen on Debian unstable with GNOME3. The
  compose sequence for this character works as expected in Ubuntu's
  xterm, which leads me to believe it is an Ubuntu-specific issue with
  Gtk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1163023/+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 919899] Re: There is no sequence for c-acute

[Adrianna Pińska]

Addendum for anyone else coming across this thread: for the workaround,
I have added `export GTK_IM_MODULE=xim` to `~/.xprofile`. Environment
values exported in `.bashrc` will not be applied to the graphical
environment, and therefore will not affect apps launched from the GUI.

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

Title:
  There is no  sequence for c-acute

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Starting with Ubuntu 11.10, the key sequence Compose+apostrophe+c
  produces the letter ç (c with cedilla) while the correct one should be
  ć (c with acute). My compose key is mapped to the right menu key.

  The problem is visible in FireFox, Thunderbird, and gedit. Strangely,
  however, Emacs does it correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/919899/+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 1450642] Re: seccomp missing many new syscalls

[Tyler Hicks]

** Description changed:

  [Impact]
  Several syscalls were discovered to be missing when using the launcher on 
snappy. These should be added so we may properly support seccomp filtering.
  
  [Test Case]
  seccomp itself has a comprehensive testsuite, and while it doesn't fail the 
build, regressions can be seen by looking at the build log. Eg:
  
  Regression Test Summary
  tests run: 6494
  tests skipped: 52
  tests passed: 6494
  tests failed: 0
  tests errored: 0
  
  Furthermore, on a snappy system, perform:
- # Note, for the 14.04 SRU, you'll have to enable trusty-proposed and install 
snapd from
- # the following PPA:
- # https://launchpad.net/~thomas-voss/+archive/ubuntu/trusty/+packages
+ # Note, for the 14.04 SRU, you'll have to install snapd from trusty-proposed
  $ sudo snappy install hello-world
  $ hello-world.env
  
  It should show the environment. On an arm system with 2.1.1-1 from the 
archive, this will fail due to a seccomp denial:
  audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 
pid=1491 comm="env" exe="/bin/bash" sig=31 arch=4028 syscall=983045 
compat=0 ip=0xb6fb0bd6 code=0x0
  
  (note, snappy images have a ppa fix for this, see notes below).
  
  To test the segfault fix, do:
  $ scmp_sys_resolver 1024
  Segmentation fault
  
  It should return:
  $ scmp_sys_resolver 1024
  UNKNOWN
  
  For the new 3.19 syscalls:
  $ scmp_sys_resolver getrandom
  -1
  
  it should return something like (actual number depends on arch, this is on 
armhf):
  $ scmp_sys_resolver getrandom
  384
+ 
+ For the 14.04 SRU, test the following syscalls (expected results on
+ amd64 are shown):
+ 
+ $ scmp_sys_resolver getrandom
+ 318
+ $ scmp_sys_resolver membarrier
+ 324
+ $ scmp_sys_resolver userfaultfd
+ 323
+ $ scmp_sys_resolver mlock2
+ 325
+ 
  
  autopkgtests for libseccomp have been added as part of this update to verify 
that the library recognizes all the syscalls from 3.19 and the private 
syscalls. These tests can be run like so (assuming you are in the unpacked 
source and the binaries are in ../binary):
  $ export REL=vivid
  $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source 
../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot 
autopkgtest-$REL-amd64 || echo "** AUTOPKGTESTS FAILED"
  
  Alternatively, if you don't have autopkgtest setup, you can do:
  $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev 
seccomp
  $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-filter
  ...
  PASS
  $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh 
./debian/tests/test-scmp_sys_resolver
  ...
  PASS
  
  Lastly, seccomp is used by lxc. lxc can be tested by using the test case
  as outlined in step 4 of
  https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only.
  
  [Regression Potential]
  If the above tests, regression potential is considered low. Unknown syscalls 
will continue to be handled as before.
  
  Description of changes:
  add finit_module:
  
https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15
  
  sync the syscall table entries - 3.16
  
https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75
  
https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4
  
https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd
  
https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb
  
https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718
  
https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a
  
  sync the syscall table entries - 3.17
  
https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9
  
  sync the syscall table entries - 3.19
  
https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3
  
  This should also be applied (fix a segfault for invalid syscall numbers):
  
https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3
  
  For the 14.04 SRU so that libseccomp can handle all of the syscalls in the 
4.4 based linux-lts-xenial kernel:
  - membarrier and userfaultfd syscalls:
-   
https://github.com/seccomp/libseccomp/commit/d2ca11b7cdddbba3782b1e306ceacf19e898faee
+   
https://github.com/seccomp/libseccomp/commit/d2ca11b7cdddbba3782b1e306ceacf19e898faee
  - x86 direct socket syscalls
-   
https://github.com/seccomp/libseccomp/commit/24114ca6703036f76be1920a7ba387d6835dd764
+   
https://github.com/seccomp/libseccomp/commit/24114ca6703036f76be1920a7ba387d6835dd764
  - mlock2 syscall
-   
https://github.com/seccomp/libseccomp/commit/173b96ba8d36a4b1954e99570e82f2f932fe056a
+   
https://github.com/seccomp/libseccomp/commit/173b96ba8d36a4b1954e99570e82f2f932fe056a
  
  In addition, add-missing-arm-private-syscalls.patch is add to add 5
  private ARM syscalls. These are absolutely 

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Dave Chiluk]

@Lukasz 
Looking good so far.  Appears resolved with 1.10.6-1ubuntu3.2.

Thanks,
Dave.

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

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

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Fix Committed
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  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.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug 

[Touch-packages] [Bug 1652166] Re: Sync qtwebkit-opensource-src from Debian (enable webp)

[Dmitry Shachnev]

Copied to https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/2324, to see if it builds successully on all our
architectures.

The symbols files are mostly identical, so they should not be a problem.

One thing that bothers me is that after I copy 5.6.1+dfsg-5 to Zesty,
the auto-syncer will sync the latest Debian upload
(5.7.1~20161021+dfsg-2) which will dep-wait, so there is a risk that my
sync won't be able to migrate.

Do you have any ideas how to deal with that?

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

Title:
  Sync qtwebkit-opensource-src from Debian (enable webp)

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

Bug description:
  The last merge from Debian has this changelog entry:

* Sync with Debian packaging, remaining changes:
  - Build without WebP (in universe)
  - Own .symbols file

  https://launchpad.net/ubuntu/+source/qtwebkit-opensource-src/5.6.1
  +dfsg-4ubuntu1~2

  But libwebp is in main and has been for a while. The only part that's
  in universe is the webp binary package which is not a dependency of
  anything (and honestly I don't know why it's not in main too, it's not
  mentioned on the MIR LP: #1186553 )

  https://people.canonical.com/~ubuntu-
  archive/madison.cgi?package=libwebp=on

  That leaves the only change as using an Ubuntu-specific symbols file.
  I don't know how Qt symbols work but maybe that's not needed anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1652166/+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 1651923] Re: 505 HTTP Version not supported - installing kxstudio packages

[Nico Orrù]

The redirect URL comes directly from the github server, by the way.

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

Title:
  505  HTTP Version not supported - installing kxstudio packages

Status in apt package in Ubuntu:
  New
Status in curl package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request=20161222T022041Z=300=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef=host_id=0=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+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 1651923] Re: 505 HTTP Version not supported - installing kxstudio packages

[Nico Orrù]

nico@nico-lenovo-ubuntu:~$ curl --version
curl 7.50.1 (x86_64-pc-linux-gnu) libcurl/7.50.1 GnuTLS/3.5.3 zlib/1.2.8 
libidn/1.33 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 
pop3s rtmp rtsp smb smbs smtp smtps telnet tftp 
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL 
libz TLS-SRP UnixSockets

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

Title:
  505  HTTP Version not supported - installing kxstudio packages

Status in apt package in Ubuntu:
  New
Status in curl package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request=20161222T022041Z=300=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef=host_id=0=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+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 1651923] Re: 505 HTTP Version not supported - installing kxstudio packages

[Nico Orrù]

ock
< Vary: Accept-Encoding
< X-Served-By: 9e87b28fb3a65e563c8d72545356c3e0
< X-GitHub-Request-Id: 4D62FBED:5067:CCBC7B0:585C4996
< 
* Ignoring the response-body
{ [622 bytes data]
100   6100   6100 0468  0 --:--:--  0:00:01 --:--:--   871
* Connection #1 to host github.com left intact
* Issue another request to this URL: 
'https://github-cloud.s3.amazonaws.com/releases/39372848/4074c29a-d734-11e5-8632-2259aafc2c91.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ%2F20161222%2Fus-east-1%2Fs3%2Faws4_request=20161222T214558Z=300=c42514a341b5775702cfa0e797d09d3ae3388257c936128fe26809f1ac04018f=host_id=0=attachment%3B%20filename%3Dardour4_4.7.0-1kxstudio1_i386.deb=application%2Foctet-stream'
*   Trying 54.231.81.80...
* Connected to github-cloud.s3.amazonaws.com (54.231.81.80) port 443 (#2)
* found 173 certificates in /etc/ssl/certs/ca-certificates.crt
* found 697 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
  0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0* 
SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
*server certificate verification OK
*server certificate status verification SKIPPED
*common name: *.s3.amazonaws.com (matched)
*server certificate expiration date OK
*server certificate activation date OK
*certificate public key: RSA
*certificate version: #3
*subject: C=US,ST=Washington,L=Seattle,O=Amazon.com 
Inc.,CN=*.s3.amazonaws.com
*start date: Fri, 29 Jul 2016 00:00:00 GMT
*expire date: Wed, 29 Nov 2017 12:00:00 GMT
*issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert Baltimore 
CA-2 G2
*compression: NULL
* ALPN, server did not agree to a protocol
> GET 
> /releases/39372848/4074c29a-d734-11e5-8632-2259aafc2c91.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ%2F20161222%2Fus-east-1%2Fs3%2Faws4_request=20161222T214558Z=300=c42514a341b5775702cfa0e797d09d3ae3388257c936128fe26809f1ac04018f=host_id=0=attachment%3B%20filename%3Dardour4_4.7.0-1kxstudio1_i386.deb=application%2Foctet-stream
>  HTTP/1.1
> Host: github-cloud.s3.amazonaws.com
> User-Agent: curl/7.50.1
> Accept: */*
> 
< HTTP/1.1 200 OK
< x-amz-id-2: 
jgftd3KO43W9MqQRkaXxZQj/9CHRvJcMQtqke6185CND77T3zmAov5yolBYJa70pmzfrvIaQsEk=
< x-amz-request-id: 763EFA47B3F85EAB
< Date: Thu, 22 Dec 2016 21:46:00 GMT
< Last-Modified: Fri, 19 Feb 2016 17:11:54 GMT
< ETag: "abb6b1bf10a5c1e30c367ed9c7517e7d"
< Content-Disposition: attachment; filename=ardour4_4.7.0-1kxstudio1_i386.deb
< Accept-Ranges: bytes
< Content-Type: application/octet-stream
< Content-Length: 60151504
< Server: AmazonS3
< 
{ [16360 bytes data]
100 57.3M  100 57.3M0 0  2212k  0  0:00:26  0:00:26 --:--:-- 2514k
* Connection #2 to host github-cloud.s3.amazonaws.com left intact
```

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

Title:
  505  HTTP Version not supported - installing kxstudio packages

Status in apt package in Ubuntu:
  New
Status in curl package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request=20161222T022041Z=300=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef=host_id=0=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

[Touch-packages] [Bug 919899] Re: There is no sequence for c-acute

[Adrianna Pińska]

This is *still* a problem for me, two years later, in a fresh install of
16.10. I get the correct compose sequence in Qt apps, but not in GTK
apps.  The workaround of setting GTK_IM_MODULE=xim still appears to
work.

Is any attempt being made to fix this? The upstream bug appears to have
been "resolved" as "not a bug". GTK apps are currently effectively
unusable for typing Polish out of the box (unless you change the
keyboard layout, which is not an acceptable solution for users of US-
layout keyboards who use multiple languages).

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

Title:
  There is no  sequence for c-acute

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Starting with Ubuntu 11.10, the key sequence Compose+apostrophe+c
  produces the letter ç (c with cedilla) while the correct one should be
  ć (c with acute). My compose key is mapped to the right menu key.

  The problem is visible in FireFox, Thunderbird, and gedit. Strangely,
  however, Emacs does it correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/919899/+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 12.04 and 14.04 LTS's version of libavcodec

[Norbert]

Ubuntu 12.04.5 LTS with all updates.
I removed PPA ppa:itachi-san/ffmpeg with ppa-purge.
In Firefox I have media.libavcodec.allow-obsolete = false.
Tried to find patch in proposed updates with no luck.


The bug is not fixed!
Please fix it!
Precise is an LTS version, is not it?


@louis romano (troubleshooter1961) 
Fixing bugs by commenting is not real bug fixing! 
"Talk is cheap. Show me the code." as Linus Torvalds said.

** Changed in: firefox (Ubuntu Precise)
 Assignee: louis romano (troubleshooter1961) => (unassigned)

-- 
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 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Fix Released
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

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/libav/+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 1652166] [NEW] Sync qtwebkit-opensource-src from Debian (enable webp)

[Jeremy Bicha]

Public bug reported:

The last merge from Debian has this changelog entry:

  * Sync with Debian packaging, remaining changes:
- Build without WebP (in universe)
- Own .symbols file

https://launchpad.net/ubuntu/+source/qtwebkit-opensource-src/5.6.1+dfsg-
4ubuntu1~2

But libwebp is in main and has been for a while. The only part that's in
universe is the webp binary package which is not a dependency of
anything (and honestly I don't know why it's not in main too, it's not
mentioned on the MIR LP: #1186553 )

https://people.canonical.com/~ubuntu-
archive/madison.cgi?package=libwebp=on

That leaves the only change as using an Ubuntu-specific symbols file. I
don't know how Qt symbols work but maybe that's not needed anymore.

** Affects: qtwebkit-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Sync qtwebkit-opensource-src from Debian (enable webp)

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

Bug description:
  The last merge from Debian has this changelog entry:

* Sync with Debian packaging, remaining changes:
  - Build without WebP (in universe)
  - Own .symbols file

  https://launchpad.net/ubuntu/+source/qtwebkit-opensource-src/5.6.1
  +dfsg-4ubuntu1~2

  But libwebp is in main and has been for a while. The only part that's
  in universe is the webp binary package which is not a dependency of
  anything (and honestly I don't know why it's not in main too, it's not
  mentioned on the MIR LP: #1186553 )

  https://people.canonical.com/~ubuntu-
  archive/madison.cgi?package=libwebp=on

  That leaves the only change as using an Ubuntu-specific symbols file.
  I don't know how Qt symbols work but maybe that's not needed anymore.

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

[louis romano]

Thanks for all info on this matter..problem seems to be fixed. not
getting warning.


Louis V.Romano Jr.



From: boun...@canonical.com  on behalf of Seth Arnold 
<1643...@bugs.launchpad.net>
Sent: Wednesday, December 21, 2016 6:00 PM
To: troubleshooter1...@hotmail.com
Subject: [Bug 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's 
version of libavcodec

William, as far as I know the next LTS is still intended to be 18.04.

Our current LTS releases are 12.04, 14.04, and 16.04.

If you wish to upgrade to 14.04 note that Apache2's authentication and
authorization changed drastically. If you wish to upgrade to 16.04 note
that php is now version 7, and many applications aren't yet updated for
php7. Be sure to check the release notes for details of larger changes:
https://wiki.ubuntu.com/Releases
Releases - Ubuntu Wiki
wiki.ubuntu.com
The content of these old releases can be accessed at the old Ubuntu releases 
directory. Management of releases. Support length. Regular releases are ...


Thanks

--
You received this bug notification because you are a bug assignee.
https://bugs.launchpad.net/bugs/1643467
Bug #1643467 "Firefox 50 blocks Ubuntu 14.04 LTS's version 
...
bugs.launchpad.net
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 ...


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

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Fix Released
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

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/libav/+bug/1643467/+subscriptions

-- 
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 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Fix Released
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

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/libav/+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 1652101] Re: Can't created nested AppArmor namespaces

[Tyler Hicks]

This is a feature bug that the security team is using for tracking.
Moving the bug status back to confirmed.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Can't created nested AppArmor namespaces

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor
  policy namespace and load a profile belonging to that AppArmor
  namespace. Once that's done, the user can confine a process with that
  namespaced AppArmor profile and enter into a user namespace. That
  process can then load additional AppArmor profiles inside of the
  AppArmor and user namespace. Here's an example:

  We need to set up the namespace, n1, and load the profile, p1.
  $ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root, 
capability,"
  $ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1
  $ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1

  Now we enter into confinement using the AppArmor namespace and profile and 
then enter into an unprivileged user namespace
  $ aa-exec -n n1 -p p1 -- unshare -Ur

  We can now load profiles as the privileged user inside of the unprivileged 
user namespace
  # echo "profile test {}" | apparmor_parser -qr

  The reason for this bug report is that we cannot create a nested
  AppArmor policy namespace inside of the unprivileged user namespace

  # mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1
  mkdir: cannot create directory 
‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission 
denied

  If that worked, we could adjust LXD to read
  /sys/kernel/security/apparmor/.ns_name to get the current AppArmor
  namespace, then create a new namespace under the current namespace,
  and leverage the nested namespace for its nested containers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1652101/+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 1638345] Re: avahi-daemon crashes multiple times an hour

[Jamie Eisenhart]

Same on my system (16.04, kernel 4.8.12)

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[Sabin Iacob]

so, in order to get sound I have to:

* start blueman applet (default applet connects to ... something on the 
headphones, because they say "device connected", but not to some audio thingy, 
or at least pulseaudio doesn't pick it up unless I use blueman and tell it to 
connect to the audio sink on the headphones)
* start headphones
* sometimes open sound settings and click on the headphones so the sink shows 
up - it's listed in sound settings, but doesn't show up in pacmd list-sinks
* run a2dp.py

awesome!

Does anyone have a way to automate this, or at least remotely stab a
pulseaudio developer?

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  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 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  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
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Dave H]

Hi Kyle and Michi,

Just to let you know, I still have the problem with the Today scope
refresh / messed up icons, on my MX4 with OTA-14 installed. I was
wondering if you had any time to look again at this problem.

Merry Christmas and happy new year to you all!

Best regards

Dave H

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+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 1652148] [NEW] I am not able to print on my new canon laser shot LBP2900B printer

[Yogendra Garodi]

Public bug reported:

i am able to find the printer on the system but it is not able to print...
in the status of printer it shows "idle:sending file to printer"
or "sending file to printer" or "Idle - Sending data to printer. "but the 
printer doesnt prints

output of lpusb commmand
Bus 001 Device 002: ID 8087:8001 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 8087:0a2a Intel Corp. 
Bus 002 Device 003: ID 04f2:b413 Chicony Electronics Co., Ltd 
Bus 002 Device 012: ID 04a9:2676 Canon, Inc. CAPT Device
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

printer :canon laser shot LBP2900B printer
 driver downloaded from : 
http://gdlp01.c-wss.com/gds/6/014596/04/Linux_CAPT_PrinterDriver_V270_uk_EN.tar.gz
 Tried x64 bit drivers

expected: printer to print

happened : no response from printer

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Dec 23 00:26:32 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-12-22 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lpstat: device for CanonLBP2900B: usb://Canon/LBP2900?serial=C1G97FQN
MachineType: FUJITSU LIFEBOOK A555
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/CanonLBP2900B.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/CanonLBP2900B.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=94e9467b-205b-43c4-b1ca-7f285806bdba ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2016
dmi.bios.vendor: FUJITSU // Insyde Software Corp.
dmi.bios.version: 1.21
dmi.board.name: FJNBB3E
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.21:bd05/31/2016:svnFUJITSU:pnLIFEBOOKA555:pvr:rvnFUJITSU:rnFJNBB3E:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A555
dmi.sys.vendor: FUJITSU

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


** Tags: amd64 apparmor apport-bug xenial

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

Title:
  I am not able to print on my new canon laser shot LBP2900B printer

Status in cups package in Ubuntu:
  New

Bug description:
  i am able to find the printer on the system but it is not able to print...
  in the status of printer it shows "idle:sending file to printer"
  or "sending file to printer" or "Idle - Sending data to printer. "but the 
printer doesnt prints

  output of lpusb commmand
  Bus 001 Device 002: ID 8087:8001 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 004: ID 8087:0a2a Intel Corp. 
  Bus 002 Device 003: ID 04f2:b413 Chicony Electronics Co., Ltd 
  Bus 002 Device 012: ID 04a9:2676 Canon, Inc. CAPT Device
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  printer :canon laser shot LBP2900B printer
   driver downloaded from : 
http://gdlp01.c-wss.com/gds/6/014596/04/Linux_CAPT_PrinterDriver_V270_uk_EN.tar.gz
   Tried x64 bit drivers

  expected: printer to print

  happened : no response from printer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec 23 00:26:32 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-12-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: device for CanonLBP2900B: usb://Canon/LBP2900?serial=C1G97FQN
  MachineType: FUJITSU LIFEBOOK A555
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/CanonLBP2900B.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/CanonLBP2900B.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=94e9467b-205b-43c4-b1ca-7f285806bdba ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2016
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.21
  dmi.board.name: FJNBB3E
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  

[Touch-packages] [Bug 1652131] Re: Putting Apparmor profile usr.lib.dovecot.auth into enforce mode blocks access to /var/spool/private/auth for Dovecot

[Nathaniel Homier]

Launchpad acting weird.  Won't select the right package which is
apparmor.

** Package changed: dpkg (Ubuntu) => apparmor (Ubuntu)

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

Title:
  Putting Apparmor profile usr.lib.dovecot.auth into enforce mode blocks
  access to /var/spool/private/auth for Dovecot

Status in apparmor package in Ubuntu:
  New

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  Installing Postfix and Dovecot and setting them up as explained at
  https://help.ubuntu.com/lts/serverguide/postfix.html

  Then setting all apparmor profiles including Postfix and Dovecot to
  enforce mode.

  Postfix fails to send a TLS protected email because Dovecot can't
  connect to /var/spool/postfix/auth/private because when Dovecot's
  apparmor profile is set to enforce mode, apparmor denies Dovecot
  access to /var/spool/postfix/auth/private.

  Syslog
  apparmor="DENIED" operation="connect" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/anvil-auth-penalty" pid=8251 comm="auth" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0

  apparmor="DENIED" operation="open" profile="/usr/lib/dovecot/auth"
  name="/run/dovecot/stats-user" pid=8251 comm="auth" requested_mask="w"
  denied_mask="w" fsuid=0 ouid=0

  apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
  disconnected path" error=-13 profile="/usr/lib/dovecot/log"
  name="run/systemd/journal/dev-log" pid=8093 comm="log"
  requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
  disconnected path" error=-13 profile="/usr/lib/dovecot/log"
  name="run/systemd/journal/dev-log" pid=8093 comm="log"
  requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  apparmor="DENIED" operation="file_perm"
  profile="/usr/lib/dovecot/auth" name="/var/spool/postfix/private/auth"
  pid=8251 comm="auth" requested_mask="w" denied_mask="w" fsuid=129
  ouid=130

  apparmor="DENIED" operation="file_perm"
  profile="/usr/lib/dovecot/auth" name="/var/spool/postfix/private/auth"
  pid=8251 comm="auth" requested_mask="w" denied_mask="w" fsuid=129
  ouid=130

  Dec 22 10:38:20 frontier postfix/master[1516]: warning: process
  /usr/lib/postfix/sbin/smtpd pid 8248 exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1652131/+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 1652131] [NEW] Putting Apparmor profile usr.lib.dovecot.auth into enforce mode blocks access to /var/spool/private/auth for Dovecot

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename:   yakkety

Installing Postfix and Dovecot and setting them up as explained at
https://help.ubuntu.com/lts/serverguide/postfix.html

Then setting all apparmor profiles including Postfix and Dovecot to
enforce mode.

Postfix fails to send a TLS protected email because Dovecot can't
connect to /var/spool/postfix/auth/private because when Dovecot's
apparmor profile is set to enforce mode, apparmor denies Dovecot access
to /var/spool/postfix/auth/private.

Syslog
apparmor="DENIED" operation="connect" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/anvil-auth-penalty" pid=8251 comm="auth" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0

apparmor="DENIED" operation="open" profile="/usr/lib/dovecot/auth"
name="/run/dovecot/stats-user" pid=8251 comm="auth" requested_mask="w"
denied_mask="w" fsuid=0 ouid=0

apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="/usr/lib/dovecot/log"
name="run/systemd/journal/dev-log" pid=8093 comm="log"
requested_mask="w" denied_mask="w" fsuid=0 ouid=0

apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="/usr/lib/dovecot/log"
name="run/systemd/journal/dev-log" pid=8093 comm="log"
requested_mask="w" denied_mask="w" fsuid=0 ouid=0

apparmor="DENIED" operation="file_perm" profile="/usr/lib/dovecot/auth"
name="/var/spool/postfix/private/auth" pid=8251 comm="auth"
requested_mask="w" denied_mask="w" fsuid=129 ouid=130

apparmor="DENIED" operation="file_perm" profile="/usr/lib/dovecot/auth"
name="/var/spool/postfix/private/auth" pid=8251 comm="auth"
requested_mask="w" denied_mask="w" fsuid=129 ouid=130

Dec 22 10:38:20 frontier postfix/master[1516]: warning: process
/usr/lib/postfix/sbin/smtpd pid 8248 exit status 1

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


** Tags: apparmor dovecot mta postfix
-- 
Putting Apparmor profile usr.lib.dovecot.auth into enforce mode blocks access 
to /var/spool/private/auth for Dovecot
https://bugs.launchpad.net/bugs/1652131
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apparmor 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 1587965] Re: [OTA11][m10] long swipe or home button doesn't "mazimize" dash

[Joan CiberSheep]

This bug is fixed in OTA14. \o/

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Released

** Changed in: ubuntu-ux
   Status: New => Fix Released

** Changed in: unity8 (Ubuntu)
   Status: New => Fix Released

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

Title:
  [OTA11][m10] long swipe or home button doesn't "mazimize" dash

Status in Canonical System Image:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  1) swipe from outside of the screen from the right to get the apps that are 
opened
  2) outside long swipe from the left, moves the most left app to move to the 
right but it doesn't "maximize" main scope.
  3) outside short swipe from the left shows dash but tapping on home button 
has no effect (before it was "maximizing" main scope)

  PS: All in all good work, OTA 11 feels really faster!

  The key point is that the M10 works differently from the phones, so
  something is different with the staged mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587965/+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

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: init-system-helpers (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: cups (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: cups (Ubuntu)
Milestone: None => ubuntu-16.12

** Also affects: cups (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: init-system-helpers (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: cups (Ubuntu Zesty)
   Importance: High
 Assignee: Dimitri John Ledkov (xnox)
   Status: Confirmed

** Also affects: systemd (Ubuntu Zesty)
   Importance: High
 Assignee: Dimitri John Ledkov (xnox)
   Status: Invalid

** Also affects: init-system-helpers (Ubuntu Zesty)
   Importance: High
   Status: Invalid

** Also affects: cups (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: init-system-helpers (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: init-system-helpers (Ubuntu)

** No longer affects: systemd (Ubuntu)

** No longer affects: init-system-helpers (Ubuntu Zesty)

** No longer affects: init-system-helpers (Ubuntu Yakkety)

** No longer affects: init-system-helpers (Ubuntu Xenial)

** No longer affects: systemd (Ubuntu Xenial)

** No longer affects: systemd (Ubuntu Yakkety)

** No longer affects: systemd (Ubuntu Zesty)

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

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

** Changed in: cups (Ubuntu Zesty)
   Status: Confirmed => Triaged

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

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

** Changed in: cups (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: cups (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.2

** Changed in: cups (Ubuntu Yakkety)
Milestone: None => yakkety-updates

** Changed in: cups (Ubuntu Yakkety)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

-- 
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:
  Triaged
Status in cups source package in Xenial:
  Triaged
Status in cups source package in Yakkety:
  Triaged
Status in cups source package in Zesty:
  Triaged

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

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  
  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: 

[Touch-packages] [Bug 1617512] Re: x-systemd.automount causes system to fail to boot

[Launchpad Bug Tracker]

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

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

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

Title:
  x-systemd.automount causes system to fail to boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I've changed /etc/fstab mount line from:
  UUID=78fc6e4d-9a37-406d-9bde-449fd8595373 /media/Data ext4 relatime 0 1
  to:
  UUID=78fc6e4d-9a37-406d-9bde-449fd8595373 /media/Data ext4 
noauto,x-systemd.automount,relatime 0 1

  Now system fails to boot, in logs I see:
  systemd[1]: Starting of media-Data.automount not supported.
  systemd[1]: Dependency failed for Local File Systems.
  systemd[1]: local-fs.target: Job local-fs.target/start failed with result 
'dependency'.
  systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
  systemd[1]: Started Emergency Shell.
  systemd[1]: Reached target Emergency Mode.

  While according to
  http://manpages.ubuntu.com/manpages/xenial/man5/systemd.mount.5.html
  it should work.

  I'm on Xenial as of today.

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

[Dimitri John Ledkov]

** Description changed:

  This is in xenial-proposed, please block release to -updates accordingly
  :)
+ 
+ [Impact]
+ * fail to upgrade
+ 
+ [testcase]
+ Root cause is believed to be reproducible with:
+ 
+ #!/bin/bash
+ systemctl stop cups.path cups.service
+ rm /var/cache/cups/org.cups.cupsd
+ systemctl start cups.path
+ touch /var/cache/cups/org.cups.cupsd
+ sleep 1
+ rm /var/cache/cups/org.cups.cupsd
+ sleep 1
+ systemctl stop cups.service
+ echo $?
+ 
  
  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
+  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.

-- 
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
Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

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

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  
  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: 

[Touch-packages] [Bug 1652101] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1652101

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  Can't created nested AppArmor namespaces

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor
  policy namespace and load a profile belonging to that AppArmor
  namespace. Once that's done, the user can confine a process with that
  namespaced AppArmor profile and enter into a user namespace. That
  process can then load additional AppArmor profiles inside of the
  AppArmor and user namespace. Here's an example:

  We need to set up the namespace, n1, and load the profile, p1.
  $ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root, 
capability,"
  $ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1
  $ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1

  Now we enter into confinement using the AppArmor namespace and profile and 
then enter into an unprivileged user namespace
  $ aa-exec -n n1 -p p1 -- unshare -Ur

  We can now load profiles as the privileged user inside of the unprivileged 
user namespace
  # echo "profile test {}" | apparmor_parser -qr

  The reason for this bug report is that we cannot create a nested
  AppArmor policy namespace inside of the unprivileged user namespace

  # mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1
  mkdir: cannot create directory 
‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission 
denied

  If that worked, we could adjust LXD to read
  /sys/kernel/security/apparmor/.ns_name to get the current AppArmor
  namespace, then create a new namespace under the current namespace,
  and leverage the nested namespace for its nested containers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1652101/+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 1652103] Re: ifupdown expecting upstart where systemd exists

[flickerfly]

Also, I've been able to repeat this on multiple 16.04 machines.

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

Title:
  ifupdown expecting upstart where systemd exists

Status in ifupdown package in Ubuntu:
  New

Bug description:
  I was doing an upgrade of a few utilities and noticed them output when
  ifupdown was upgrading.

  Setting up ifupdown (0.8.10ubuntu1.2) ...
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`screen-cleanup'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`screen-cleanup'
  Setting up initramfs-tools-bin (0.122ubuntu8.7) ...

  After the upgrade I ran `status ifpudown` and received one of the same
  complaints.

  $ sudo status ifupdown
  status: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused

  The same output occurs if I run this against networking.

  $ sudo status networking
  status: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Thu Dec 22 07:53:25 2016
  InstallationDate: Installed on 2012-12-29 (1454 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (139 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1652103/+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 1651923] Re: 505 HTTP Version not supported - installing kxstudio packages

[Nico Orrù]

om; frame-ancestors 'none'; frame-src 
render.githubusercontent.com; img-src 'self' data: assets-cdn.github.com 
identicons.github.com collector.githubapp.com github-cloud.s3.amazonaws.com 
*.githubusercontent.com; media-src 'none'; script-src assets-cdn.github.com; 
style-src 'unsafe-inline' assets-cdn.github.com
< Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
< Public-Key-Pins: max-age=5184000; 
pin-sha256="WoiWRyIOVNa9ihaBciRSC7XHjliYS9VwUGOIud4PB18="; 
pin-sha256="RRM1dGqnDFsCJXBTHky16vi1obOlCgFFn/yOhI/y+ho="; 
pin-sha256="k2v657xBsOVe1PQRwOsHsw3bsGT2VzIqz5K+59sNQws="; 
pin-sha256="K87oWBWM9UZfyddvDfoxL+8lpNyoUB2ptGtn0fv6G2Q="; 
pin-sha256="IQBnNBEiFuhj+8x6X8XLgh01V9Ic5/V3IRQLNFFc7v4="; 
pin-sha256="iie1VXtL7HzAMF+/PVPR9xzT80kQxdZeJ+zduCB3uj0="; 
pin-sha256="LvRiGEjRqfzurezaWuj8Wie2gyHMrW5Q06LspMnox7A="; includeSubDomains
< X-Content-Type-Options: nosniff
< X-Frame-Options: deny
< X-XSS-Protection: 1; mode=block
< Vary: Accept-Encoding
< X-Served-By: 7d2a2d05162492046d9960cdbc326796
< X-GitHub-Request-Id: 4D62FBED:5067:C82969A:585BFCB6
< 
* Connection #0 to host github.com left intact
You are being https://github-cloud.s3.amazonaws.com/releases/39372848/4074c29a-d734-11e5-8632-2259aafc2c91.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ%2F20161222%2Fus-east-1%2Fs3%2Faws4_requestX-Amz-Date=20161222T161758ZX-Amz-Expires=300X-Amz-Signature=9b01bd5373576686821a64246a49f2aa743bd61a8a263344903424b177c58a20X-Amz-SignedHeaders=hostactor_id=0response-content-disposition=attachment%3B%20filename%3Dardour4_4.7.0-1kxstudio1_i386.debresponse-content-type=application%2Foctet-stream;>redirected.

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

Title:
  505  HTTP Version not supported - installing kxstudio packages

Status in apt package in Ubuntu:
  New
Status in curl package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request=20161222T022041Z=300=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef=host_id=0=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+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 1652103] [NEW] ifupdown expecting upstart where systemd exists

[flickerfly]

Public bug reported:

I was doing an upgrade of a few utilities and noticed them output when
ifupdown was upgrading.

Setting up ifupdown (0.8.10ubuntu1.2) ...
initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`screen-cleanup'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`screen-cleanup'
Setting up initramfs-tools-bin (0.122ubuntu8.7) ...

After the upgrade I ran `status ifpudown` and received one of the same
complaints.

$ sudo status ifupdown
status: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused

The same output occurs if I run this against networking.

$ sudo status networking
status: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ifupdown 0.8.10ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Thu Dec 22 07:53:25 2016
InstallationDate: Installed on 2012-12-29 (1454 days ago)
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ifupdown
UpgradeStatus: Upgraded to xenial on 2016-08-04 (139 days ago)

** Affects: ifupdown (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 ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1652103

Title:
  ifupdown expecting upstart where systemd exists

Status in ifupdown package in Ubuntu:
  New

Bug description:
  I was doing an upgrade of a few utilities and noticed them output when
  ifupdown was upgrading.

  Setting up ifupdown (0.8.10ubuntu1.2) ...
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`screen-cleanup'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`screen-cleanup'
  Setting up initramfs-tools-bin (0.122ubuntu8.7) ...

  After the upgrade I ran `status ifpudown` and received one of the same
  complaints.

  $ sudo status ifupdown
  status: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused

  The same output occurs if I run this against networking.

  $ sudo status networking
  status: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Thu Dec 22 07:53:25 2016
  InstallationDate: Installed on 2012-12-29 (1454 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (139 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1652103/+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 1652101] [NEW] Can't created nested AppArmor namespaces

[Tyler Hicks]

Public bug reported:

A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor
policy namespace and load a profile belonging to that AppArmor
namespace. Once that's done, the user can confine a process with that
namespaced AppArmor profile and enter into a user namespace. That
process can then load additional AppArmor profiles inside of the
AppArmor and user namespace. Here's an example:

We need to set up the namespace, n1, and load the profile, p1.
$ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root, 
capability,"
$ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1
$ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1

Now we enter into confinement using the AppArmor namespace and profile and then 
enter into an unprivileged user namespace
$ aa-exec -n n1 -p p1 -- unshare -Ur

We can now load profiles as the privileged user inside of the unprivileged user 
namespace
# echo "profile test {}" | apparmor_parser -qr

The reason for this bug report is that we cannot create a nested
AppArmor policy namespace inside of the unprivileged user namespace

# mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1
mkdir: cannot create directory 
‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission 
denied

If that worked, we could adjust LXD to read
/sys/kernel/security/apparmor/.ns_name to get the current AppArmor
namespace, then create a new namespace under the current namespace, and
leverage the nested namespace for its nested containers.

** Affects: apparmor (Ubuntu)
 Importance: High
 Assignee: Ubuntu Security Team (ubuntu-security)
 Status: New

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Ubuntu Security Team (ubuntu-security)
 Status: New


** Tags: aa-kernel bot-stop-nagging

** Tags added: bot-stop-nagging

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

** Also affects: apparmor (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

** Tags added: aa-kernel

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

Title:
  Can't created nested AppArmor namespaces

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor
  policy namespace and load a profile belonging to that AppArmor
  namespace. Once that's done, the user can confine a process with that
  namespaced AppArmor profile and enter into a user namespace. That
  process can then load additional AppArmor profiles inside of the
  AppArmor and user namespace. Here's an example:

  We need to set up the namespace, n1, and load the profile, p1.
  $ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root, 
capability,"
  $ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1
  $ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1

  Now we enter into confinement using the AppArmor namespace and profile and 
then enter into an unprivileged user namespace
  $ aa-exec -n n1 -p p1 -- unshare -Ur

  We can now load profiles as the privileged user inside of the unprivileged 
user namespace
  # echo "profile test {}" | apparmor_parser -qr

  The reason for this bug report is that we cannot create a nested
  AppArmor policy namespace inside of the unprivileged user namespace

  # mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1
  mkdir: cannot create directory 
‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission 
denied

  If that worked, we could adjust LXD to read
  /sys/kernel/security/apparmor/.ns_name to get the current AppArmor
  namespace, then create a new namespace under the current namespace,
  and leverage the nested namespace for its nested containers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1652101/+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 1636503] Re: recovery mode gets borked after some time out

[mike]

still borked with systemd 229-4ubuntu13(xenial)

-_- guys, isn't this a serious bug?
You are left with unusable recovery mode

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

Title:
  recovery mode gets borked after some time out

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  (Linux mint 18 / Xenial)

  after booting in recovery mode from grub.
  If you just wait 30-60seconds, a new stream of messages appear and something 
gets messed up, you can't use recovery mode any more, you have to do a hard 
reboot.

  You don't need to do something in particular for this to happen,
  simply some time out occurs.

  ---

  more precisely, one of the messages say(copied manually):

  "[FAILED] Failed to start Console System on Startup logging.
  see 'systemctl status console-kit-log-system-start.service' for more details.

  It seams, it tries to launch a second recovery mode on top of the
  previous one after the error.

  

  I confirm, this is happening on both my PC linux mint 18 64bits,
  laptop linux mint 18 32bits and some one else from a forum on a
  ThinkPad X201 with Mint 18 KDE 64-bit.

  On my systems, both are fully up to date, 32 and 64 bit. Kernels don't
  seam to change anything.

  systemd version 229-4ubuntu11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636503/+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 1635783] Re: Regression with suspend 229-4ubuntu4/10 on 32bits old thinkpad t40

[mike]

that was fixed at some point.
works with systemd 229-4ubuntu13(xenial)

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

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

Title:
  Regression with suspend 229-4ubuntu4/10 on 32bits old thinkpad t40

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  (I"m actually on linux mint)

  In the live USB and default install, suspend worked correctly
  (hibernation didn't). At some point, it stopped working (and
  hibernation started working), it just get blocked on a black screen,
  the laptop is totally blocked, i have to press the power button.

  sudo pm-suspend still works correctly.
  systemctl suspend gives the above behavior.

  I"m actually on linux mint 18 MATE 32bits, everything upgraded and with 
original kernel.
  I think it stopped working after the systemd update, still with original 
kernel. I tried installing other kernels from the official repos and from 
kernel.ubuntu.com, but nothing changed (4.4.1 and 4.8).

  I think a regression hapened in systemd somewhere between 
229-4ubuntu4(xenial) and 229-4ubuntu10(xenial)
  I couldn't test between 4 and 10.

  I can send you logs, if you tell me exactly how and what.

  ---
  linux mint 18 32bit
  thinkpad t40 (2003)
  ATI Mobility Radeon 7500

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635783/+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 1652084] [NEW] package libgtk2.0-0 2.24.30-4ubuntu2 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz usr/share/doc/libgtk2.0-0/copyright] failed to install/upgrade: tryin

[cmd673]

Public bug reported:

Unable to perform any software updates.  "The package system is broken"
-- not very helpful.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libgtk2.0-0 2.24.30-4ubuntu2 [modified: 
usr/share/doc/libgtk2.0-0/changelog.Debian.gz 
usr/share/doc/libgtk2.0-0/copyright]
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
 libgtk2.0-0:i386: Install
 libgail18:i386: Install
 libgail-common:i386: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Nov 12 15:35:46 2016
DpkgHistoryLog:
 Start-Date: 2016-11-12  15:35:45
 Commandline: apt-get install -f
 Requested-By: dennison (1000)
 Install: libgail-common:i386 (2.24.30-4ubuntu2, automatic), libgail18:i386 
(2.24.30-4ubuntu2, automatic)
 Upgrade: libgtk2.0-0:i386 (2.24.25-3+deb8u1, 2.24.30-4ubuntu2)
DpkgTerminalLog:
 Preparing to unpack .../0-libgtk2.0-0_2.24.30-4ubuntu2_i386.deb ...
 Unpacking libgtk2.0-0:i386 (2.24.30-4ubuntu2) over (2.24.25-3+deb8u1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-TQWxBx/0-libgtk2.0-0_2.24.30-4ubuntu2_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', 
which is different from other instances of package libgtk2.0-0:i386
DuplicateSignature:
 package:libgtk2.0-0:2.24.30-4ubuntu2 [modified: 
usr/share/doc/libgtk2.0-0/changelog.Debian.gz 
usr/share/doc/libgtk2.0-0/copyright]
 Unpacking libgtk2.0-0:i386 (2.24.30-4ubuntu2) over (2.24.25-3+deb8u1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-TQWxBx/0-libgtk2.0-0_2.24.30-4ubuntu2_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', 
which is different from other instances of package libgtk2.0-0:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other 
instances of package libgtk2.0-0:i386
InstallationDate: Installed on 2015-02-24 (667 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: gtk+2.0
Title: package libgtk2.0-0 2.24.30-4ubuntu2 [modified: 
usr/share/doc/libgtk2.0-0/changelog.Debian.gz 
usr/share/doc/libgtk2.0-0/copyright] failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is 
different from other instances of package libgtk2.0-0:i386
UpgradeStatus: Upgraded to yakkety on 2016-10-25 (57 days ago)

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check package-conflict yakkety

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

Title:
  package libgtk2.0-0 2.24.30-4ubuntu2 [modified:
  usr/share/doc/libgtk2.0-0/changelog.Debian.gz
  usr/share/doc/libgtk2.0-0/copyright] failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz',
  which is different from other instances of package libgtk2.0-0:i386

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Unable to perform any software updates.  "The package system is
  broken" -- not very helpful.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libgtk2.0-0 2.24.30-4ubuntu2 [modified: 
usr/share/doc/libgtk2.0-0/changelog.Debian.gz 
usr/share/doc/libgtk2.0-0/copyright]
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   libgtk2.0-0:i386: Install
   libgail18:i386: Install
   libgail-common:i386: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Nov 12 15:35:46 2016
  DpkgHistoryLog:
   Start-Date: 2016-11-12  15:35:45
   Commandline: apt-get install -f
   Requested-By: dennison (1000)
   Install: libgail-common:i386 (2.24.30-4ubuntu2, automatic), libgail18:i386 
(2.24.30-4ubuntu2, automatic)
   Upgrade: libgtk2.0-0:i386 (2.24.25-3+deb8u1, 2.24.30-4ubuntu2)
  DpkgTerminalLog:
   Preparing to unpack .../0-libgtk2.0-0_2.24.30-4ubuntu2_i386.deb ...
   Unpacking libgtk2.0-0:i386 (2.24.30-4ubuntu2) over (2.24.25-3+deb8u1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-TQWxBx/0-libgtk2.0-0_2.24.30-4ubuntu2_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other 
instances of package libgtk2.0-0:i386
  DuplicateSignature:
   package:libgtk2.0-0:2.24.30-4ubuntu2 [modified: 
usr/share/doc/libgtk2.0-0/changelog.Debian.gz 
usr/share/doc/libgtk2.0-0/copyright]
   Unpacking libgtk2.0-0:i386 (2.24.30-4ubuntu2) over (2.24.25-3+deb8u1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-TQWxBx/0-libgtk2.0-0_2.24.30-4ubuntu2_i386.deb (--unpack):
trying to overwrite shared 

[Touch-packages] [Bug 1652080] [NEW] package ifupdown 0.8.10ubuntu1.2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Павел Заец]

Public bug reported:

Настраивается пакет ifupdown (0.8.10ubuntu1.2) …
insserv: warning: script 'S80panasoniclpd-init' missing LSB tags and overrides
insserv: warning: script 'panasoniclpd-init' missing LSB tags and overrides
insserv: There is a loop between service plymouth and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting panasoniclpd-init 

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Joachim Fagerholm]

This bug is a disgrace. It has been around for years and sabotages many
non-tech users life. If I was able to fix it I would try. Unfortunately
I am not that skilled, can only fix the symptoms not contribute to
fixing the problem itself. But I would think that someone on a higher
skill level could do a service to the community here, fairly easily?
apt-get autoremove and autoclean takes care of it on newer versions,
didn't on 10.04. But they are apparently never run automatically? And
/boot could really be more in tune with the size of the disk it is
created on by the installation. I have had this trouble on Ubuntu 10.04,
12.04 and now 14.04.

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1645117] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[David]

Hello,
the problem seems to come from python3 and dh-python packages wich request each 
other to be configured. a dpkg --force-configure-any --configure dh-python 
seems to solve the problem.

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  --

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  Date: Sun Nov 27 21:29:34 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-09-03 (85 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-11-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1645117/+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 1615474] Re: Network Indicator / Connectivity-API is not accessible

[AlexAD]

I have a the same issue on a BQ 4.5 running OTA-14 20161118. I
accidently left the hotspot on over night whilst it was charging, took
the phone to work and it when I tried to use it would not respond. I
went for a reset, when it came up the phone a drained a lot of the
battery, I could see a steady downward trend on the graph durring my
commute. The sub network icons are gone and now the music app crashes
instantly. My guess is that it is something to do with the hotspot.

Before this the phone had never been in developer mode and worked like a
charm. Is there a way to see the status of the hotspot via command line?

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

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Triaged
Status in indicator-network package in Ubuntu:
  Triaged

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

  -

  Per the comments the .config/connectivity-service/config.ini file
  seems to hold bad or outdated info and needs to be manually deleted
  and then recreated by the service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+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 1651923] Re: 505 HTTP Version not supported - installing kxstudio packages

[Julian Andres Klode]

Ah no, my Debian was just using a proxy in between. It fails there too.

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

Title:
  505  HTTP Version not supported - installing kxstudio packages

Status in apt package in Ubuntu:
  New
Status in curl package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request=20161222T022041Z=300=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef=host_id=0=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+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 1651923] Re: 505 HTTP Version not supported - installing kxstudio packages

[Julian Andres Klode]

Adding curl to the loop. It works fine on Debian, but fails in yakkety,
and there have been no changes in our https module.

Attaching a log: We send the server a HTTP/1.1 request and it responds
with one

** Attachment added: "HTTP log"
   
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1651923/+attachment/4795307/+files/log

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

Title:
  505  HTTP Version not supported - installing kxstudio packages

Status in apt package in Ubuntu:
  New
Status in curl package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request=20161222T022041Z=300=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef=host_id=0=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+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 1651923] Re: 505 HTTP Version not supported - installing kxstudio packages

[Julian Andres Klode]

I think the problem is that there is a space in the URI before
"filename=", and that is not encoded before it being sent out, causing
the server to think "filename=..." is the http version...

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

Title:
  505  HTTP Version not supported - installing kxstudio packages

Status in apt package in Ubuntu:
  New
Status in curl package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request=20161222T022041Z=300=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef=host_id=0=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+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 1651923] Re: 505 HTTP Version not supported - installing kxstudio packages

[Julian Andres Klode]

Right:

 /usr/lib/apt/apt-helper download-file 
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb 
test.deb
Err:1 
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  505  HTTP Version not supported


** Also affects: curl (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  505  HTTP Version not supported - installing kxstudio packages

Status in apt package in Ubuntu:
  New
Status in curl package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request=20161222T022041Z=300=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef=host_id=0=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+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 1637652] Re: stucked in a login loop

[Gary Caine]

Sorry I mis read the report.

I am getting the login loop with nvidea 304 not 340

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

Title:
  stucked in a login loop

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  after 16.10 upgrade I cannot login into the graphical interface

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Oct 28 23:40:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Point of View BV G86 [GeForce 8500 GT] [1acc:0857]
  InstallationDate: Installed on 2012-03-13 (1690 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. Z68XP-UD3P
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=401cb21e-ddab-46d5-a6dd-72a53a7f0ca3 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: Z68XP-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd02/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Oct 28 23:29:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Gaming Keyboard G610 KEYBOARD, id 8
   inputLogitech Gaming Keyboard G610 KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637652/+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 1637652] Re: stucked in a login loop

[Gary Caine]

I am also getting the login loop with nvidia-304.134

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

Title:
  stucked in a login loop

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  after 16.10 upgrade I cannot login into the graphical interface

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Oct 28 23:40:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Point of View BV G86 [GeForce 8500 GT] [1acc:0857]
  InstallationDate: Installed on 2012-03-13 (1690 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. Z68XP-UD3P
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=401cb21e-ddab-46d5-a6dd-72a53a7f0ca3 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: Z68XP-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd02/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Oct 28 23:29:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Gaming Keyboard G610 KEYBOARD, id 8
   inputLogitech Gaming Keyboard G610 KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637652/+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 1633877] Re: VPN - "Additional Search Domains" Settings are being Ignored

[Launchpad Bug Tracker]

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

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  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
  CurrentDesktop: Unity
  Date: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633877/+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 1640468] Re: package bluez 5.41-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Thomas Schwinge]

 looks very relevant, so
this would supposedly be a bug in systemd itself.

** Bug watch added: github.com/systemd/systemd/issues #3867
   https://github.com/systemd/systemd/issues/3867

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

Title:
  package bluez 5.41-0ubuntu3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Nov  9 07:18:21 js-frerot-lnx systemd[1]: bluetooth.service: Main process 
exited, code=exited, status=226/NAMESPACE
  Nov  9 07:18:21 js-frerot-lnx systemd[1]: bluetooth.service: Unit entered 
failed state.
  Nov  9 07:18:21 js-frerot-lnx systemd[1]: bluetooth.service: Failed with 
result 'exit-code'.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   bluez:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Nov  9 07:06:51 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-05-11 (547 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: btusb bluetooth
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: bluez
  Title: package bluez 5.41-0ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-25 (14 days ago)
  dmi.bios.date: 02/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0806
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E
  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.:bvr0806:bd02/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  hciconfig:
   
  rfkill:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1640468/+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 1640468] Re: package bluez 5.41-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Thomas Schwinge]

The systemd log line "bluetooth.service: Failed at step NAMESPACE
spawning /usr/lib/bluetooth/bluetoothd: Too many levels of symbolic
links" (which is also present in your "JournalErrors.txt" file) lead me
to systemd's "ProtectHome" configuration option, and indeed
"/lib/systemd/system/bluetooth.service" states "ProtectHome=true", which
supposedly doesn't play well with my "/home -> media/[...]/home"
symlink.  Changing that to the weaker "ProtectHome=read-only", the bluez
package configures successfully.

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

Title:
  package bluez 5.41-0ubuntu3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Nov  9 07:18:21 js-frerot-lnx systemd[1]: bluetooth.service: Main process 
exited, code=exited, status=226/NAMESPACE
  Nov  9 07:18:21 js-frerot-lnx systemd[1]: bluetooth.service: Unit entered 
failed state.
  Nov  9 07:18:21 js-frerot-lnx systemd[1]: bluetooth.service: Failed with 
result 'exit-code'.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   bluez:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Nov  9 07:06:51 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-05-11 (547 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: btusb bluetooth
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: bluez
  Title: package bluez 5.41-0ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-25 (14 days ago)
  dmi.bios.date: 02/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0806
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E
  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.:bvr0806:bd02/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  hciconfig:
   
  rfkill:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1640468/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[auspex]

You're kidding?  "no longer affects:network-manager"

It certainly did as recently as yesterday!

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 1640468] Re: package bluez 5.41-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package bluez 5.41-0ubuntu3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Nov  9 07:18:21 js-frerot-lnx systemd[1]: bluetooth.service: Main process 
exited, code=exited, status=226/NAMESPACE
  Nov  9 07:18:21 js-frerot-lnx systemd[1]: bluetooth.service: Unit entered 
failed state.
  Nov  9 07:18:21 js-frerot-lnx systemd[1]: bluetooth.service: Failed with 
result 'exit-code'.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   bluez:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Nov  9 07:06:51 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-05-11 (547 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: btusb bluetooth
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: bluez
  Title: package bluez 5.41-0ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-25 (14 days ago)
  dmi.bios.date: 02/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0806
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E
  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.:bvr0806:bd02/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  hciconfig:
   
  rfkill:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1640468/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Aron Xu]

** No longer affects: network-manager

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 1652036] [NEW] package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura

[Adelar Dias Junior]

Public bug reported:

Computador trava constantemente e aparece esse erro

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libdbus-1-3:amd64 1.10.6-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Thu Dec 22 10:15:29 2016
ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
InstallationDate: Installed on 2016-12-17 (4 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: dbus
Title: package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade:
  O pacote está num mau estado de inconsistência; deve  reinstala-lo
  antes de tentar configura-lo.

Status in dbus package in Ubuntu:
  New

Bug description:
  Computador trava constantemente e aparece esse erro

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libdbus-1-3:amd64 1.10.6-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Thu Dec 22 10:15:29 2016
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2016-12-17 (4 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: dbus
  Title: package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade: 
O pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1652036/+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 1650900] Re: UHD TV resolution changed unintendly to FHD

[jsc]

I had several installations on the same computer now (for other reasons) and 
ALWAYS the correct resolution was found (without changing anything with the 
cables). To my view it cannot be the cable.
Why is the resolution then never changed back to UHD even after restart/power 
on/off ?

Additional info: The TV is incorrectly identified as an Phillips 58" ...
but is in fact only a 49" unit.

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

Title:
  UHD TV resolution changed unintendly to FHD

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After "original Ubuntu 16.04 LTS" installation on my

  Intel® Pentium(R) CPU G4400 @ 3.30GHz × 2
  Intel® HD Graphics 510 (Skylake GT1)

  System with UHD TV (3840x216@30Hz)

  Philips 49PUT4900

  everything seemed fine. The resolution was totally ok with 3840x2160@30Hz. 
Without further installs (no known updates or so, beside the OpenSSH Server 
install) it falls back after a while to FHD (1920x1080) without option to 
switch back.
  It seems that the original installation recognizes all parameters as needed 
from the TV, but afterwards at some point it cannot.
  Several reboots of the system after the original installation it works still 
fine, but from one day to the other it is wrong.

  Additional information:

  1.) I use an adapter cable converting from DP to HDMI (I have no DP monitor 
available).
  2.) I already tried to start without a monitor connected and then connect
  3.) I already tried to disconnect and then connect again (after 15sec.)
  4.) Now I have upgraded everything with "apt-get upgrade"

  All without changing anything.

  Result from "lsb_release -rd"
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  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
  CurrentDesktop: Unity
  Date: Sun Dec 18 15:33:11 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:1902] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Technology Solutions Device [1734:121c]
  InstallationDate: Installed on 2016-12-10 (7 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
   Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU ESPRIMO P556/E85+
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=1905211f-7356-4656-beaf-3804725467d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2016
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.11 R1.14.0 for D3400-A1x
  dmi.board.name: D3400-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3400-A1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.11R1.14.0forD3400-A1x:bd06/09/2016:svnFUJITSU:pnESPRIMOP556/E85+:pvr:rvnFUJITSU:rnD3400-A1:rvrS26361-D3400-A1:cvnFUJITSU:ct3:cvr:
  dmi.product.name: ESPRIMO P556/E85+
  dmi.sys.vendor: FUJITSU
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Dec 18 15:12:00 2016

[Touch-packages] [Bug 1652032] [NEW] ambiguous config file

[Hadmut Danisch]

Public bug reported:

Hi,

I'm currently hunting some problems caused by some ambiguity in the
dnsmasq config.

There's a directory /etc/dnsmasq.d, where some packages put files with
except-interface=... clauses, telling other instances of dnsmasq to
"Keep your fingers from my interface". Good practice.

But then, conf-dir=/etc/dnsmasq.d clauses in /etc/dnsmasq.conf are
commented out, so actually the /etc/dnsmasq.d directory is not read by
default.

Some packages that use dnsmasq therefore give it a --conf-
dir=/etc/dnsmasq.d command line parameter to make it read all those
config snippets.

This causes two problems:

- Not all packages give their dnsmasq this additional parameter, and
therefore not all dnsmasq instances obey those config. E.g.
NetwerkManager uses it's own /etc/NetworkManager/dnsmasq.d, libvirt does
not read it either.


- Even those packages that use --conf-dir=/etc/dnsmasq.d do not all read the 
same, since there is an additional parameter telling which files to load or 
ignore, which is used differently by all the packages. 


So it is quite unclear how these things should work together cleanly.
Since the details are left to both the user's arbitrary configuration of
/etc/dnsmasq.conf and every single package maintainer how he would
prefer to use it, there's just a heap of confusion.

In my eyes the best way would be to just use

conf-dir=/etc/dnsmasq.d/,*.conf


in the /etc/dnsmasq.conf and have this as a default, and that's it. 


regards

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Dec 22 12:55:33 2016
InstallationDate: Installed on 2016-04-22 (243 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
PackageArchitecture: all
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (66 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  ambiguous config file

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,

  I'm currently hunting some problems caused by some ambiguity in the
  dnsmasq config.

  There's a directory /etc/dnsmasq.d, where some packages put files with
  except-interface=... clauses, telling other instances of dnsmasq to
  "Keep your fingers from my interface". Good practice.

  But then, conf-dir=/etc/dnsmasq.d clauses in /etc/dnsmasq.conf are
  commented out, so actually the /etc/dnsmasq.d directory is not read by
  default.

  Some packages that use dnsmasq therefore give it a --conf-
  dir=/etc/dnsmasq.d command line parameter to make it read all those
  config snippets.

  This causes two problems:

  - Not all packages give their dnsmasq this additional parameter, and
  therefore not all dnsmasq instances obey those config. E.g.
  NetwerkManager uses it's own /etc/NetworkManager/dnsmasq.d, libvirt
  does not read it either.

  
  - Even those packages that use --conf-dir=/etc/dnsmasq.d do not all read the 
same, since there is an additional parameter telling which files to load or 
ignore, which is used differently by all the packages. 


  So it is quite unclear how these things should work together cleanly.
  Since the details are left to both the user's arbitrary configuration
  of /etc/dnsmasq.conf and every single package maintainer how he would
  prefer to use it, there's just a heap of confusion.

  In my eyes the best way would be to just use

  conf-dir=/etc/dnsmasq.d/,*.conf

  
  in the /etc/dnsmasq.conf and have this as a default, and that's it. 


  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Dec 22 12:55:33 2016
  InstallationDate: Installed on 2016-04-22 (243 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1652032/+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 1643789] Re: Backport packages for 16.04.2 lts-hwe stack

[Timo Aaltonen]

** Description changed:

  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.
  
  [Test case]
  
  libdrm, mesa: run a desktop session, see that things still work
  
  [Regression potential]
  
  libdrm:
  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu
  
  mesa:
- slim
+ included here just to keep the necessary backport bits in the same bug, the 
actual update testing will be handled on bug #1641017. That said:
  - Intel validates new upstream releases on all their hw
  - AMD probably does the same, though it's unverified
- - was already tested by cert team on a handful of intel/amd machines
+ - this release was already tested by cert team on a handful of intel/amd 
machines

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

Title:
  Backport packages for 16.04.2 lts-hwe stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Won't Fix
Status in libdrm source package in Xenial:
  Incomplete
Status in mesa source package in Xenial:
  New

Bug description:
  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.

  [Test case]

  libdrm, mesa: run a desktop session, see that things still work

  [Regression potential]

  libdrm:
  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu

  mesa:
  included here just to keep the necessary backport bits in the same bug, the 
actual update testing will be handled on bug #1641017. That said:
  - Intel validates new upstream releases on all their hw
  - AMD probably does the same, though it's unverified
  - this release was already tested by cert team on a handful of intel/amd 
machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1643789/+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 1641017] Re: Mesa 12.0.5 - multiple important fixes, stable branch

[Timo Aaltonen]

Xenial added as a target, we will be providing unrenamed backports from
now on.

** Description changed:

  [Impact]
  Mesa 12.0.5 is now available as a point release in the stable branch. Mesa 
has MRE for these.
  
  The release contains multiple fixes amongst which:
  The nouveau vdpau driver performance has been restored. The wayland-egl
  module no longer crashes if the user calls eglDestroySurface and
  wl_egl_window_destroy in the "wrong" order. libEGL correctly advertises
  the EGL platforms available. Multiple fd leaks were addressed, which
  could prevent rmmod of devices such as the DisplayLink drivers. Radeonsi
  has gained noticeable performance by disabling ReZ. Interop between third
  party OpenCL implementations and mesa's libGL/libEGL is back online...
  and many more.
  
  Full changelog:
  https://lists.freedesktop.org/archives/mesa-dev/2016-November/135027.html
  
  I am particularly interested in the RadeonSI performance boost:
  https://lists.freedesktop.org/archives/mesa-dev/2016-October/131759.html
  In real-world tests the boost is about 20% (Yay!) :
  
http://www.phoronix.com/scan.php?page=news_item=Mesa-Post-ReZ-Change-Benchmarks
  
  [Test case]
- There's only a modest number of changes to the drivers, the performance boost 
for Radeon is result of one fix for the shaders.
+ Run the default desktop and maybe a game or two.
  
- This release will be tested by the certification team on a set of
- machines, they will post the results here when done.
+ This release has been tested on xenial by the certification team on a set of 
machines, covering:
+ Intel Haswell
+ Intel Broadwell
+ Intel Skylake
+ AMD Mobility Radeon HD 5430/5450/5470
+ 
+ and they all passed the tests.
+ 
+ Once this is in -proposed, the community will be asked to test it on a
+ wider range of devices.
  
  [Regression potential]
- The release consists of cherry-picks from master, specifically selected as 
bugfixes. Regression potential should be low.
+ yakkety: the release consists of cherry-picks from master, specifically 
selected as bugfixes. Regression potential should be low.
+ 
+ xenial: it's a bigger bump for xenial, but since yakkety already ships
+ with this series the risk should be low

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

Title:
  Mesa 12.0.5 - multiple important fixes, stable branch

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in mesa source package in Yakkety:
  Confirmed

Bug description:
  [Impact]
  Mesa 12.0.5 is now available as a point release in the stable branch. Mesa 
has MRE for these.

  The release contains multiple fixes amongst which:
  The nouveau vdpau driver performance has been restored. The wayland-egl
  module no longer crashes if the user calls eglDestroySurface and
  wl_egl_window_destroy in the "wrong" order. libEGL correctly advertises
  the EGL platforms available. Multiple fd leaks were addressed, which
  could prevent rmmod of devices such as the DisplayLink drivers. Radeonsi
  has gained noticeable performance by disabling ReZ. Interop between third
  party OpenCL implementations and mesa's libGL/libEGL is back online...
  and many more.

  Full changelog:
  https://lists.freedesktop.org/archives/mesa-dev/2016-November/135027.html

  I am particularly interested in the RadeonSI performance boost:
  https://lists.freedesktop.org/archives/mesa-dev/2016-October/131759.html
  In real-world tests the boost is about 20% (Yay!) :
  
http://www.phoronix.com/scan.php?page=news_item=Mesa-Post-ReZ-Change-Benchmarks

  [Test case]
  Run the default desktop and maybe a game or two.

  This release has been tested on xenial by the certification team on a set of 
machines, covering:
  Intel Haswell
  Intel Broadwell
  Intel Skylake
  AMD Mobility Radeon HD 5430/5450/5470

  and they all passed the tests.

  Once this is in -proposed, the community will be asked to test it on a
  wider range of devices.

  [Regression potential]
  yakkety: the release consists of cherry-picks from master, specifically 
selected as bugfixes. Regression potential should be low.

  xenial: it's a bigger bump for xenial, but since yakkety already ships
  with this series the risk should be low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1641017/+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 1641017] Re: Mesa 12.0.5 - multiple important fixes, stable branch

[Timo Aaltonen]

** Also affects: mesa (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Mesa 12.0.5 - multiple important fixes, stable branch

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in mesa source package in Yakkety:
  Confirmed

Bug description:
  [Impact]
  Mesa 12.0.5 is now available as a point release in the stable branch. Mesa 
has MRE for these.

  The release contains multiple fixes amongst which:
  The nouveau vdpau driver performance has been restored. The wayland-egl
  module no longer crashes if the user calls eglDestroySurface and
  wl_egl_window_destroy in the "wrong" order. libEGL correctly advertises
  the EGL platforms available. Multiple fd leaks were addressed, which
  could prevent rmmod of devices such as the DisplayLink drivers. Radeonsi
  has gained noticeable performance by disabling ReZ. Interop between third
  party OpenCL implementations and mesa's libGL/libEGL is back online...
  and many more.

  Full changelog:
  https://lists.freedesktop.org/archives/mesa-dev/2016-November/135027.html

  I am particularly interested in the RadeonSI performance boost:
  https://lists.freedesktop.org/archives/mesa-dev/2016-October/131759.html
  In real-world tests the boost is about 20% (Yay!) :
  
http://www.phoronix.com/scan.php?page=news_item=Mesa-Post-ReZ-Change-Benchmarks

  [Test case]
  Run the default desktop and maybe a game or two.

  This release has been tested on xenial by the certification team on a set of 
machines, covering:
  Intel Haswell
  Intel Broadwell
  Intel Skylake
  AMD Mobility Radeon HD 5430/5450/5470

  and they all passed the tests.

  Once this is in -proposed, the community will be asked to test it on a
  wider range of devices.

  [Regression potential]
  yakkety: the release consists of cherry-picks from master, specifically 
selected as bugfixes. Regression potential should be low.

  xenial: it's a bigger bump for xenial, but since yakkety already ships
  with this series the risk should be low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1641017/+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 1643789] Re: Backport packages for 16.04.2 lts-hwe stack

[Timo Aaltonen]

dropped libclc, yakkety shipped with the same version

** Changed in: libclc (Ubuntu Xenial)
   Status: Incomplete => Won't Fix

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mesa (Ubuntu)
   Status: New => Invalid

** Description changed:

  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.
  
  [Test case]
  
- libdrm: run a desktop session, see that things still work
- libclc: TBD
+ libdrm, mesa: run a desktop session, see that things still work
  
  [Regression potential]
  
  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu

** Description changed:

  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.
  
  [Test case]
  
  libdrm, mesa: run a desktop session, see that things still work
  
  [Regression potential]
  
+ libdrm:
  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu
+ 
+ mesa:
+ slim
+ - Intel validates new upstream releases on all their hw
+ - AMD probably does the same, though it's unverified
+ - was already tested by cert team on a handful of intel/amd machines

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

Title:
  Backport packages for 16.04.2 lts-hwe stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Won't Fix
Status in libdrm source package in Xenial:
  Incomplete
Status in mesa source package in Xenial:
  New

Bug description:
  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.

  [Test case]

  libdrm, mesa: run a desktop session, see that things still work

  [Regression potential]

  libdrm:
  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu

  mesa:
  slim
  - Intel validates new upstream releases on all their hw
  - AMD probably does the same, though it's unverified
  - was already tested by cert team on a handful of intel/amd machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1643789/+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 1652007] [NEW] webbrowser-app crashes on startup in Desktop Mode

[Bry Wilson]

Public bug reported:

Running Meizu Pro 5 rc-proposed Version 249. When I connect to a monitor
using the Microsoft Wireless Display Adapter (both Versions 1 and 2) and
the phone enters Desktop Mode, webbrowser-app starts to open and crashes
immediately.

application-legacy-webbrowser-app.log:

Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
could not open containers config file  
"/home/phablet/.local/share/libertine/ContainersConfig.json"
[1222/111616:WARNING:qt_screen.cc(125)] More than one virtual screen detected - 
this is not supported in Oxide

(process:6110): dconf-WARNING **: Unable to open
/custom/xdg/data/dconf/profile/custom: Permission denied

(process:6110): dconf-WARNING **: unable to open named profile (custom): using 
the null configuration.
OxideQQuickWebView: canGoForward is deprecated. Please use the API provided by 
OxideQQuickNavigationHistory instead
OxideQQuickWebView: canGoBack is deprecated. Please use the API provided by 
OxideQQuickNavigationHistory instead
Input device added: "Logitech Bluetooth Mouse M555b" "/dev/input/event8" 
QFlags(0x2)
Input device added: "Logitech K810" "/dev/input/event9" QFlags(0x1|0x10)
Input device added: "Headset" "/dev/input/event5" QFlags(0x1)
Input device added: "fts" "/dev/input/event7" QFlags(0x1|0x8)
Input device added: "pa122" "/dev/input/event0" QFlags()
Input device added: "isl29125" "/dev/input/event1" QFlags()
Input device added: "gpio-keys" "/dev/input/event6" QFlags(0x1|0x20)
Input device added: "unity8-simulated-mouse" "/dev/input/event10" QFlags(0x2)
Input device added: "STM VL6180 proximity sensor" "/dev/input/event2" QFlags()
Input device added: "fpc_irq_wakeup" "/dev/input/event3" QFlags(0x1)
Input device added: "fpc-keys" "/dev/input/event4" QFlags(0x1)
terminate called after throwing an instance of 'std::out_of_range'
  what():  map::at
[0100/00:ERROR:broker_posix.cc(41)] Invalid node channel message

I assume it's connected but webapps exhibit the same behaviour.

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

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

Title:
  webbrowser-app crashes on startup in Desktop Mode

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Running Meizu Pro 5 rc-proposed Version 249. When I connect to a
  monitor using the Microsoft Wireless Display Adapter (both Versions 1
  and 2) and the phone enters Desktop Mode, webbrowser-app starts to
  open and crashes immediately.

  application-legacy-webbrowser-app.log:

  Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
  could not open containers config file  
"/home/phablet/.local/share/libertine/ContainersConfig.json"
  [1222/111616:WARNING:qt_screen.cc(125)] More than one virtual screen detected 
- this is not supported in Oxide

  (process:6110): dconf-WARNING **: Unable to open
  /custom/xdg/data/dconf/profile/custom: Permission denied

  (process:6110): dconf-WARNING **: unable to open named profile (custom): 
using the null configuration.
  OxideQQuickWebView: canGoForward is deprecated. Please use the API provided 
by OxideQQuickNavigationHistory instead
  OxideQQuickWebView: canGoBack is deprecated. Please use the API provided by 
OxideQQuickNavigationHistory instead
  Input device added: "Logitech Bluetooth Mouse M555b" "/dev/input/event8" 
QFlags(0x2)
  Input device added: "Logitech K810" "/dev/input/event9" QFlags(0x1|0x10)
  Input device added: "Headset" "/dev/input/event5" QFlags(0x1)
  Input device added: "fts" "/dev/input/event7" QFlags(0x1|0x8)
  Input device added: "pa122" "/dev/input/event0" QFlags()
  Input device added: "isl29125" "/dev/input/event1" QFlags()
  Input device added: "gpio-keys" "/dev/input/event6" QFlags(0x1|0x20)
  Input device added: "unity8-simulated-mouse" "/dev/input/event10" QFlags(0x2)
  Input device added: "STM VL6180 proximity sensor" "/dev/input/event2" QFlags()
  Input device added: "fpc_irq_wakeup" "/dev/input/event3" QFlags(0x1)
  Input device added: "fpc-keys" "/dev/input/event4" QFlags(0x1)
  terminate called after throwing an instance of 'std::out_of_range'
what():  map::at
  [0100/00:ERROR:broker_posix.cc(41)] Invalid node channel message

  I assume it's connected but webapps exhibit the same behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1652007/+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 1651735] Re: $ mir_demo_server --help fails with an exception

[Alan Griffiths]

On further investigation I only see this on my desktop (not on VM or
laptop).

** Changed in: mir
   Status: Incomplete => Invalid

** Changed in: mir (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  $ mir_demo_server --help fails with an exception

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid

Bug description:
  $ mir_demo_server --help
  [2016-12-21 11:49:00.068655] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.25.0)
  [2016-12-21 11:49:00.069710] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.25.0)
  [2016-12-21 11:49:00.069935] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.25.0)
  [2016-12-21 11:49:00.069954] mirplatform: Found graphics driver: 
throw-on-creation (version 0.25.0)
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: character conversion failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651735/+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 1644244] Re: Extraneous files left in apt config directories

[V. K.]

** Summary changed:

- error
+ Extraneous files left in apt config directories

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

Title:
  Extraneous files left in apt config directories

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  N: Ignoring file '20auto-upgrades.ucf-dist' in directory 
'/etc/apt/apt.conf.d/' as it has an invalid filename extension
  N: Ignoring file 'getdeb.list.bck' in directory '/etc/apt/sources.list.d/' as 
it has an invalid filename extension
  E: The package secondlife needs to be reinstalled, but I can't find an 
archive for it.
  multiverse restricted main' #Added by software-properties
  kimbro-vargas@kimbro-vargas-HP-Pavilion-dv5-Notebook-PC:~$ sudo dpkg --audit
  The following packages are in a mess due to serious problems during
  installation.  They must be reinstalled for them (and any packages
  that depend on them) to function properly:
   secondlife   SecondLife client

  how do I fix it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644244/+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 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early

[Tim Passingham]

Adam, can you confirm what link you have in pre-down?  I created a link
in pre-down.d called pre-down pointing to nfs.sh in the higher
directory.  When I included this script (on ubuntu 16.04), in systog I
get messages like:

root: ** NetworkManager dispatch script nfs, IF=none
STATUS=hostname

(after trying to bring up my wifi device which is disabled)

And:

root: ** NetworkManager dispatch script nfs,
IF=enp2s0 STATUS=up

(on bring up my ethernet network)

But never a Status=pre-down

I am using autofs, but I'm not sure if that's the same as using 'systemd
automount fstab'

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

Title:
  remote file systems hang on shutdown, D-BUS stops too early

Status in D-Bus:
  Won't Fix
Status in dbus package in Ubuntu:
  Fix Released

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1438612/+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 1649077] Re: [regression] OSK appears blank and/or flickers in the lock screen

[Daniel van Vugt]

My mistake. I now can't see how Mir can cause this.

** Changed in: mir
   Status: New => Incomplete

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

Title:
  [regression] OSK appears blank and/or flickers in the lock screen

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in QtMir:
  Confirmed
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  After using OTA-14 a while, the OSK starts to exhibit a strange
  behaviour.

  1. It appears blank after a while in the lock screen. You can still
  press randomly which then makes the OSK to appear fully. When you
  press a character again it starts to flicker.

  2. OSK starts to flicker similar to bug #1590765 which was fixed in
  OTA-12. It seems to have resurfaced in OTA-14.

  Systems Info:
  OTA-14 Stable Channel
  Devices: E4.5, E5

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649077/+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