[Touch-packages] [Bug 1633319] [NEW] memory leak in indicator-datetime

2016-10-13 Thread Jonathan Brier
Public bug reported:

After upgrading from 16.04 to 16.10 on the System76 Serval WS indicator-
datetime-service is consuming all the system memory from 3.7GB up to 32
GB in 30 seconds. The system kills the indicator-datetime-service
process and indicator-datetime-service restarts and memory consumption
repeats until killed again. All swap memory is consumed in this pattern.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 14 00:12:00 2016
EcryptfsInUse: Yes
SourcePackage: indicator-datetime
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1556459] Re: [Lenovo ThinkPad W530] Regression: cannot set up 3 display configuration any more (Optimus)

2016-10-13 Thread Bernhard Zürn
Since a few wweks I am using the Nouveau (OpenSource) NVIDIA driver on
16.04. without those problems. Seems to be only soultion right now.

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

Title:
  [Lenovo ThinkPad W530] Regression: cannot set up 3 display
  configuration any more (Optimus)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I cannot set up the third monitor any more (it was working beginning
  of March 2016 with Ubuntu 16.04).

  The configuration with NVIDIA Optimus starts with builtin display (of
  Thinkpad W530) and one of (3K) monitors, the second monitor is
  detected, but not used.

  The unity configuration tool shows me two message boxes:

  "The selected configuration for displays could not be applied
  could not set the configuration for CRTC 64"

  and

  "Failed to apply configuration: %s

  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: 
could not set the configuration for CRTC 64
  "

  The first one I have seen at boot time on login screen (with 3
  displays) previously, the second one is new.

  The third monitor works if Optimus gets disabled in  BIOS and the
  machine runs with Nvidia only

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  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: Sat Mar 12 18:44:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.16, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  InstallationDate: Installed on 2016-02-25 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  MachineType: LENOVO 2447MU0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=c01ceec8-4b0c-447f-af8f-3e9c4ae90e15 ro rootflags=subvol=@ quiet 
splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2447MU0
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2447MU0
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar 12 18:30:45 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.1-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1556459/+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 1553885] Re: VPN split DNS gets broken after suspend/resume

2016-10-13 Thread Bug Watch Updater
** Changed in: network-manager
   Status: Confirmed => Incomplete

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

Title:
  VPN split DNS gets broken after suspend/resume

Status in NetworkManager:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  I've got a company's VPN server I connect to. When I connect to it I
  get several DNS entries for split DNS configuration and this works
  fine.

  After suspend/resume cycle I reconnect to VPN and see those split DNS
  entries added along with entries for VPN's DNS servers that do not
  have domain attached to it (i.e. not split). Disconnecting and
  reconnecting to VPN doesn't solve the problem: those non split entries
  gets stuck until I restart NetworkManager.

  I'll attach the patch that addresses the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1553885/+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 1524053] Re: Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session than a line.

2016-10-13 Thread ChesterCloud
I have the same problem, Unity session on ubuntu 16.04. If you can,
please fix it , it's really annoying that one of your favourite app
doesn't work on fresh system as it did in previous.

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

Title:
  Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu
  Session than a line.

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  I've tried both Ubuntu Minimal+XFCE & Xubuntu 16.04
  This gravely affect of XFCE, Openbox session on Ubuntu 16.04.
  However this doesn't happen on Xubuntu 16.04 Session at all it shows 
dependencies list normally
  But on XFCE, Openbox session it only shows a line.

  We need more tester to  confirm other session as well such as:
  Unity, Ubuntu, KDE, Kubuntu, lxde, lxde, Lubuntu, Edubuntu, Mythbuntu,
  To confirm if it's only affect on non-Ubuntu flavor Sessions.
  or are they affect to all Sessions Except Xubuntu Session?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1524053/+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 1633291] Re: package click-apparmor 0.3.17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package click-apparmor 0.3.17 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  This occurred as part of an upgrade to 16.10.

  It was part of a number of failed upgrades:

  Errors were encountered while processing:
   click
   click-apparmor
   url-dispatcher:amd64
   ubuntu-app-launch
   ubuntu-system-settings
   url-dispatcher-tools
   ubuntu-app-launch-tools
   libunity-scopes1.0:amd64
   ubuntu-system-settings-online-accounts
   unity8
   account-plugin-ubuntuone
   unity-plugin-scopes:amd64
   unity-greeter-session-broadcast
   unity8-desktop-session
   ubuntu-push-client
   unity-scope-click
   account-plugin-facebook
   pay-service
   unity8-common
   unity8-private:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: click-apparmor 0.3.17
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   ubuntu-release-upgrader-gtk:amd64: Install
   ubuntu-release-upgrader-core:amd64: Install
   python3-distupgrade:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Oct 13 20:54:48 2016
  DuplicateSignature:
   package:click-apparmor:0.3.17
   Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package click (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-10 (186 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.3.17 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1633291/+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 1633291] [NEW] package click-apparmor 0.3.17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-13 Thread Rob Moore
Public bug reported:

This occurred as part of an upgrade to 16.10.

It was part of a number of failed upgrades:

Errors were encountered while processing:
 click
 click-apparmor
 url-dispatcher:amd64
 ubuntu-app-launch
 ubuntu-system-settings
 url-dispatcher-tools
 ubuntu-app-launch-tools
 libunity-scopes1.0:amd64
 ubuntu-system-settings-online-accounts
 unity8
 account-plugin-ubuntuone
 unity-plugin-scopes:amd64
 unity-greeter-session-broadcast
 unity8-desktop-session
 ubuntu-push-client
 unity-scope-click
 account-plugin-facebook
 pay-service
 unity8-common
 unity8-private:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: click-apparmor 0.3.17
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
 ubuntu-release-upgrader-gtk:amd64: Install
 ubuntu-release-upgrader-core:amd64: Install
 python3-distupgrade:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Oct 13 20:54:48 2016
DuplicateSignature:
 package:click-apparmor:0.3.17
 Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ...
 Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.
 dpkg: error processing package click (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-04-10 (186 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: click-apparmor
Title: package click-apparmor 0.3.17 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package click-apparmor 0.3.17 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  This occurred as part of an upgrade to 16.10.

  It was part of a number of failed upgrades:

  Errors were encountered while processing:
   click
   click-apparmor
   url-dispatcher:amd64
   ubuntu-app-launch
   ubuntu-system-settings
   url-dispatcher-tools
   ubuntu-app-launch-tools
   libunity-scopes1.0:amd64
   ubuntu-system-settings-online-accounts
   unity8
   account-plugin-ubuntuone
   unity-plugin-scopes:amd64
   unity-greeter-session-broadcast
   unity8-desktop-session
   ubuntu-push-client
   unity-scope-click
   account-plugin-facebook
   pay-service
   unity8-common
   unity8-private:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: click-apparmor 0.3.17
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   ubuntu-release-upgrader-gtk:amd64: Install
   ubuntu-release-upgrader-core:amd64: Install
   python3-distupgrade:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Oct 13 20:54:48 2016
  DuplicateSignature:
   package:click-apparmor:0.3.17
   Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package click (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-10 (186 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.3.17 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1633291/+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 1631171] Re: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity-scopes-api (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  appears upon logging in

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  5 19:25:54 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-07-01 (96 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-04 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1631171/+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 1310186] Re: mediascanner prevents unmounting usb device

2016-10-13 Thread Michi Henning
It's difficult to see how to fix this. External devices are scanned
because people quite often use USB sticks or external drives with their
music collections.

I'm not sure whether it is even possible for mediascanner to find out
that some other arbitrary process has asked for a filesystem to be
unmounted. If so, the daemon could back off. If not, I don't know what
else it could/should do.

For what it's worth, placing a file called .nomedia into a directory
prevents scanning of that directory (and all its subdirectories).

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

Title:
  mediascanner prevents unmounting usb device

Status in mediascanner2 package in Ubuntu:
  Confirmed

Bug description:
  Trying to unmount a block device I just mounted, I get the following
  error (sorry for not resetting the locale. It says "Device is busy"):

  :~$ sudo umount /media/tkluck/tjk-backup 
  umount2: Apparaat of hulpbron is bezig
  umount: /media/tkluck/tjk-backup: apparaat is bezig
  (Welke processen het apparaat gebruiken kan mogelijk
   gevonden worden met behulp van lsof(8) of fuser(1).)
  umount2: Apparaat of hulpbron is bezig

  I get the same error in a dialog window when trying to unmount from
  the file manager.

  Using lsof shows that the media-scanner daemon is the culprit:

  tkluck@ultrabook-tjk:~$ lsof /media/tkluck/tjk-backup 
  COMMANDPID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
  mediascan 2898 tkluck   16r   DIR  252,3   2498562 
/media/tkluck/tjk-backup
  mediascan 2898 tkluck   17r   DIR  252,3 4096 50855937 
  mediascan 2898 tkluck   18r   DIR  252,3 4096 39080372 
  mediascan 2898 tkluck   19r   DIR  252,312288 39080513 
  mediascan 2898 tkluck   20r   DIR  252,320480 39080525 
  mediascan 2898 tkluck   21r   DIR  252,3 4096 46792990 
  mediascan 2898 tkluck   22r   DIR  252,3 4096 46792991 
  mediascan 2898 tkluck   23r   DIR  252,316384 46793749 
  mediascan 2898 tkluck   24r   DIR  252,3 4096 47317994 
  mediascan 2898 tkluck   25r   DIR  252,3 4096 47317997 
  mediascan 2898 tkluck   26r   DIR  252,3 4096 47317999 

  Sending it

  sudo kill -9 2898

  solved this for me.

  This is on Ubuntu GNOME 14.04. I uninstalled the mediascanner2.0 to
  solve this "once and for all" (which has no other impact since I do
  not use Unity).

  My guess is that the scan usually finishes quickly after mounting. But
  because this particular drive contains a big filetree, it doesn't,
  resulting in the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1310186/+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 1631474] Please test proposed package

2016-10-13 Thread Steve Langasek
Hello scotte, or anyone else affected,

Accepted initramfs-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.122ubuntu8.5 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in z-series:
  Fix Committed

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
     - The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken
     -
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  This bug is a regression of changes made under bug 1628306.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1633274] [NEW] Systemd-networkd crashes with core dump

2016-10-13 Thread Halvor Lyche Strandvoll
Public bug reported:

Systemd-networkd crashes with core dump, this happends in Yakkety and
Xenial.

The latest patch that was commited to Xenial-updates and Yakkety is the one 
that broke this.
Everything works just fine with Xenial without latest update or Yakkety Beta 2.

The log entries i see is:
Oct 14 02:37:42 Router01 systemd-networkd[3402]: Assertion 't' failed at 
../src/network/networkd-netdev-tunnel.c:210, function 
netdev_vti_fill_message_key(). Aborting.
Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Main process 
exited, code=dumped, status=6/ABRT
Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered 
failed state.
Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with 
result 'core-dump'.
Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Service has no 
hold-off time, scheduling restart.
Oct 14 02:37:42 Router01 systemd[1]: Stopped Network Service.
Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Start request 
repeated too quickly.
Oct 14 02:37:42 Router01 systemd[1]: Failed to start Network Service.
Oct 14 02:37:42 Router01 systemd[1]: Dependency failed for Wait for Network to 
be Configured.
Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd-wait-online.service: Job 
systemd-networkd-wait-online.service/start failed with result 'dependency'.
Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered 
failed state.
Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with 
result 'start-limit-hit'.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9git1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Fri Oct 14 02:39:05 2016
InstallationDate: Installed on 2016-10-13 (0 days ago)
InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
MachineType: Dell Inc. OptiPlex 755
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic 
root=/dev/mapper/hostname--vg-root ro
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A22
dmi.board.name: 0PU052
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.

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

Title:
  Systemd-networkd crashes with core dump

Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd-networkd crashes with core dump, this happends in Yakkety and
  Xenial.

  The latest patch that was commited to Xenial-updates and Yakkety is the one 
that broke this.
  Everything works just fine with Xenial without latest update or Yakkety Beta 
2.

  The log entries i see is:
  Oct 14 02:37:42 Router01 systemd-networkd[3402]: Assertion 't' failed at 
../src/network/networkd-netdev-tunnel.c:210, function 
netdev_vti_fill_message_key(). Aborting.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Main process 
exited, code=dumped, status=6/ABRT
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered 
failed state.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with 
result 'core-dump'.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Service has no 
hold-off time, scheduling restart.
  Oct 14 02:37:42 Router01 systemd[1]: Stopped Network Service.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Start request 
repeated too quickly.
  Oct 14 02:37:42 Router01 systemd[1]: Failed to start Network Service.
  Oct 14 02:37:42 Router01 systemd[1]: Dependency failed for Wait for Network 
to be Configured.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd-wait-online.service: 
Job systemd-networkd-wait-online.service/start failed with result 'dependency'.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered 
failed state.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with 
result 'start-limit-hit'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 14 02:39:05 2016
  InstallationDate: Installed on 2016-10-13 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 

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

2016-10-13 Thread Luke Yelavich
Ok, the profile selection stuff is a separate bug, but it seems things
are resolved with people's bluetooth audio devices not even connecting.

Thanks everybody, I'll now work on getting a stable update ready for
Xenial and yakkety.

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

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

Status in pulseaudio package in Ubuntu:
  In Progress

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

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

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

  Device info:

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

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

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

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


[Touch-packages] [Bug 1633219] Re: Upgrade to yakkety fails due to non-us locale

2016-10-13 Thread Ubuntu Foundations Team Bug Bot
** Tags added: xenial2yakkety

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

Title:
  Upgrade to yakkety fails due to non-us locale

Status in python-apt package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Upgrade to yakkety failed during updates installation. The do-release-
  upgrade window froze and there was a stacktrace in the terminal:

  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != self.percent or status_str != self.status:
  ValueError: could not convert string to float: '0,'
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 497, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 450, in write
  block = f.read(1048576)
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != self.percent or status_str != self.status:
  ValueError: could not convert string to float: '0,'

  
  It seems, that it's because release-upgrader incorrectly works with locale: 
Russian locale uses "," as a floating point separator, rather than ".", so it 
generates the "0," somewhere and cannot parse it afterwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.04.17
  

[Touch-packages] [Bug 1631504] Re: loadkeys segfaults with certain arguments in 16.10

2016-10-13 Thread Mathew Hodson
** Changed in: kbd (Ubuntu)
   Importance: Undecided => High

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

Title:
  loadkeys segfaults with certain arguments in 16.10

Status in kbd package in Ubuntu:
  New

Bug description:
  This can be reproduced as follows:

  1) Switch to VT 1 (ctrl+alt+f1)
  2) run: loadkeys garbage
  3) loadkeys will segfault

  The problem appears to be with the implicit declaration of xmalloc in 
loadkeys.c. It is resolved if
  #include "xmalloc.h" is added to the top of that file (and in fact all the 
other source files in kbd that reference xmalloc include that file).

  Interestingly xmalloc is resolved without include but the returned
  pointer seems to get truncated. It doesn't do this if the source is
  built with gcc 5.4 in 16.04 so maybe it has something to do with gcc
  6.2 in 16.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: kbd 2.0.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  7 15:27:58 2016
  InstallationDate: Installed on 2016-10-06 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161006)
  SourcePackage: kbd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2016-10-13 Thread pcjason
Hi Luke,
I did a clean install of Ubuntu GNOME 16.04.1 just a few days ago.  With the 
Ubuntu-provided Pulseaudio packages, my Plantronics BackBeat Go 2 (PLT_BBTGO2) 
bluetooth headphones would connect and then disconnect.  I have now added your 
PPA and confirmed that the headphones connect and stay connected.  Oddly 
enough, the headphone profile was set to "Analog" by default.  Upon clicking 
the dropdown to select the profile, "Analog" was not an option, and it 
immediately auto-selected HSP/HFP.  I then changed it to A2DP and I was able to 
hear nice, high quality audio through my headphones! :)

Unfortunately, after turning the headphones off/on, the headphones
immediately reconnected and defaulted to the A2DP profile, but there was
no sound.  I then changed the profile to HSP/HSF and heard low quality
audio.  Changing back to A2DP resulted in silence.  I toggled between
the two profiles a few times and the issue persisted.

I then powered off/on once again, and this time I was able to properly
select the A2DP profile and hear perfect audio!

So, the connection issue seems to be fixed (for me, atleast)!  There
seems to be something that is a little bit strange with the audio
profile selection, although there may be some user error involved here.
I'll try and repeat my power cycling tests a few more times and see if
the issue is a software problem or a user problem.

Thanks for looking into this!

-Jason

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

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

Status in pulseaudio package in Ubuntu:
  In Progress

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

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

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

  Device info:

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

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

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

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


[Touch-packages] [Bug 1633264] [NEW] My intel 7260 wifi device gone after upgrading to 4.4.0-43 kernel

2016-10-13 Thread Serge Kopalkin
Public bug reported:

Hello, after upgrading ubuntu 16.04 from 4.4.0-42 to 4.4.0-34 kernel my wifi 
stopped working altogether. I have Intel wireless 7260 wifi card. If I boot the 
computer with -42 kernel everything is ok, with -43 kernel wifi stopped 
working, only lo interface available in ifconfig, lshw -C network says network 
unclaimed.
I'm not sure where to look for meaningful logs related to the issue.
Help pls!

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  My intel 7260 wifi device gone after upgrading to 4.4.0-43 kernel

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello, after upgrading ubuntu 16.04 from 4.4.0-42 to 4.4.0-34 kernel my wifi 
stopped working altogether. I have Intel wireless 7260 wifi card. If I boot the 
computer with -42 kernel everything is ok, with -43 kernel wifi stopped 
working, only lo interface available in ifconfig, lshw -C network says network 
unclaimed.
  I'm not sure where to look for meaningful logs related to the issue.
  Help pls!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633264/+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 1632418] Re: Network Manager doesn't look for wifi after resume until restarted

2016-10-13 Thread lol24h
It happens on both home and office
Lenovo X230T
HP ProBook G640

The issue is not like mine. At my case 'systemctl restart network-
manager' does the job.

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

Title:
  Network Manager doesn't look for wifi after resume until restarted

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Once upon the time Network Manager doesn't scan to connect the
  networks until restarted

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.1
  Uname: Linux 4.8.0-040800rc8-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 11 08:12:47 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-20 (509 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.32.254 dev wlp3s0  proto static  metric 600 
   192.168.32.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.32.245  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (170 days ago)
  modified.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: [deleted]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-04-03T14:41:30.662323
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
~\_/~   a9c0eb9d-4df3-4769-95a6-b910d563d526  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   vpn0 tun   unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1632418/+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 1633219] Re: Upgrade to yakkety fails due to non-us locale

2016-10-13 Thread Vsevolod Velichko
Was it system-wide change (and reboot is done)? It may be needed if python-apt 
gets something from outside (e.g. by dbus).
I have no idea, I used update-manager to start the upgrade process and my env:
torkve@yaroot-46:/tmp [2016-10-14 02:01:18] 
0 ➜ locale
LANG=ru_RU.UTF-8
LANGUAGE=ru:en
LC_CTYPE="ru_RU.UTF-8"
LC_NUMERIC=ru_RU.UTF-8
LC_TIME=ru_RU.UTF-8
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY=ru_RU.UTF-8
LC_MESSAGES="ru_RU.UTF-8"
LC_PAPER=ru_RU.UTF-8
LC_NAME=ru_RU.UTF-8
LC_ADDRESS=ru_RU.UTF-8
LC_TELEPHONE=ru_RU.UTF-8
LC_MEASUREMENT=ru_RU.UTF-8
LC_IDENTIFICATION=ru_RU.UTF-8
LC_ALL=

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

Title:
  Upgrade to yakkety fails due to non-us locale

Status in python-apt package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Upgrade to yakkety failed during updates installation. The do-release-
  upgrade window froze and there was a stacktrace in the terminal:

  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != self.percent or status_str != self.status:
  ValueError: could not convert string to float: '0,'
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 497, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 450, in write
  block = f.read(1048576)
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File 

[Touch-packages] [Bug 1630014] Re: GPS is unable to find any position

2016-10-13 Thread Anupam
`ubuntu-location-serviced-cli --bus system --get --property
visible_space_vehicles` when "GPS only" or "GPS + Wi-Fi & cellular
network info" is active, gives:

Visible space vehicles:
Attempted to unregister path (path[0] = com path[1] = ubuntu) which isn't 
registered

I am indoor all the time and connected to Wi-Fi. Tried cold booting many
times, no change in output. Also tried deleting /var/lib/ubuntu-
location-service/config.ini file before rebooting, still no use.

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

Title:
  GPS is unable to find any position

Status in Canonical System Image:
  New
Status in location-service package in Ubuntu:
  New

Bug description:
  Even if you enable tracking position on Aquaris E 4.5, either with
  here drive or just with the GPS on, no position is tracked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630014/+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 1633153] Re: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: url-dispatcher (Ubuntu)
   Status: New => Confirmed

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

Title:
  package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in url-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  Crash during post-install tasks upgrading from 16.04 to 16.10 directly
  via Software Upgrader

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Oct 13 17:32:18 2016
  DuplicateSignature:
   package:url-dispatcher:amd64:0.1+16.10.20160816.1-0ubuntu1
   Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-11 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: url-dispatcher
  Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1633153/+subscriptions

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


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

2016-10-13 Thread Luke Yelavich
On Fri, Oct 14, 2016 at 09:00:04AM AEDT, Jeremy wrote:
> Luke and Joakim, thanks for your effort in this bug.
> 
> With Luke's latest PPA, things still don't work unless I use a terminal
> command I found on askubuntu

When you say things don't work, could you please be more specific? Does
pulseaudio still stop working/crash?

Luke

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

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

Status in pulseaudio package in Ubuntu:
  In Progress

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

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

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

  Device info:

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

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

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

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


[Touch-packages] [Bug 1633219] Re: Upgrade to yakkety fails due to non-us locale

2016-10-13 Thread Brian Murray
As one test I changed the Regional Format to "English (Denmark)" so that
numbers are 1.234.567,89 and then upgraded to yakkety using
DistUpgradeViewGtk3.  I did not encounter a crash.

bdmurray@clean-xenial-amd64:~$ env | grep LC_
LC_PAPER=en_DK.UTF-8
LC_ADDRESS=en_DK.UTF-8
LC_MONETARY=en_DK.UTF-8
LC_NUMERIC=en_DK.UTF-8
LC_TELEPHONE=en_DK.UTF-8
LC_IDENTIFICATION=en_DK.UTF-8
LC_MEASUREMENT=en_DK.UTF-8
LC_CTYPE=en_US.UTF-8
LC_TIME=en_DK.UTF-8
LC_NAME=en_DK.UTF-8

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

Title:
  Upgrade to yakkety fails due to non-us locale

Status in python-apt package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Upgrade to yakkety failed during updates installation. The do-release-
  upgrade window froze and there was a stacktrace in the terminal:

  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != self.percent or status_str != self.status:
  ValueError: could not convert string to float: '0,'
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 497, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 450, in write
  block = f.read(1048576)
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != 

[Touch-packages] [Bug 1632418] Re: Network Manager doesn't look for wifi after resume until restarted

2016-10-13 Thread Launchpad Bug Tracker
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/1632418

Title:
  Network Manager doesn't look for wifi after resume until restarted

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Once upon the time Network Manager doesn't scan to connect the
  networks until restarted

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.1
  Uname: Linux 4.8.0-040800rc8-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 11 08:12:47 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-20 (509 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.32.254 dev wlp3s0  proto static  metric 600 
   192.168.32.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.32.245  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (170 days ago)
  modified.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: [deleted]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-04-03T14:41:30.662323
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
~\_/~   a9c0eb9d-4df3-4769-95a6-b910d563d526  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   vpn0 tun   unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1632418/+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 1632418] Re: Network Manager doesn't look for wifi after resume until restarted

2016-10-13 Thread Aurimas
Can you confirm if those are the bugs that are like yours?

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

Title:
  Network Manager doesn't look for wifi after resume until restarted

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Once upon the time Network Manager doesn't scan to connect the
  networks until restarted

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.1
  Uname: Linux 4.8.0-040800rc8-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 11 08:12:47 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-20 (509 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.32.254 dev wlp3s0  proto static  metric 600 
   192.168.32.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.32.245  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (170 days ago)
  modified.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: [deleted]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-04-03T14:41:30.662323
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
~\_/~   a9c0eb9d-4df3-4769-95a6-b910d563d526  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   vpn0 tun   unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1632418/+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 1632418] Re: Network Manager doesn't look for wifi after resume until restarted

2016-10-13 Thread Aurimas
I think this is similar (or the same) issue as
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1632228
and https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1632228

What is your laptop?

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

Title:
  Network Manager doesn't look for wifi after resume until restarted

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Once upon the time Network Manager doesn't scan to connect the
  networks until restarted

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.1
  Uname: Linux 4.8.0-040800rc8-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 11 08:12:47 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-20 (509 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.32.254 dev wlp3s0  proto static  metric 600 
   192.168.32.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.32.245  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (170 days ago)
  modified.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: [deleted]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-04-03T14:41:30.662323
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
~\_/~   a9c0eb9d-4df3-4769-95a6-b910d563d526  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   vpn0 tun   unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1632418/+subscriptions

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


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

2016-10-13 Thread Luke Yelavich
On Thu, Oct 13, 2016 at 11:44:50PM AEDT, Joakim Koed wrote:
> Okay, so I can connect it just fine now, as A2DP still does not work.
> When selecting it under sound settings, it just reverts back to another
> audio source or not no sound coming out.
> 
> I think you need to look into the 03 patch as well maybe?

No, this is an issue with bluez. I've just checked myself with this fix
aplied to the yakkety package, and whilst it defaults to the wrong
profile by default, I can switch it to the A2DP profile, and the audio
quality does improve. In addition there were no changes to the
pulseaudio bluetooth module code between upstream version 8 in xenial
and version 9 in yakkety.

Luke

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

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

Status in pulseaudio package in Ubuntu:
  In Progress

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

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

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

  Device info:

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

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

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

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


[Touch-packages] [Bug 1592817] Re: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0, 0000'

2016-10-13 Thread Brian Murray
** Description changed:

- Gdebi chrahed while installing Google Chrome .deb-fil bur the error
+ Errors Bucket
+ -
+ https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53
+ 
+ Gdebi crashed while installing Google Chrome .deb-fil bur the error
  didn't appear until I logged out and back in again
  
- ProblemType: Crash
- DistroRelease: Ubuntu 16.10
+ ProblemType: CrashDistroRelease: Ubuntu 16.10
  Package: gdebi 0.9.5.7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 15 15:01:11 2016
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2016-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive 
/media/jimmy/Seagate\ Backup\ Plus\ 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb
  ProcEnviron:
-  PATH=(custom, no user)
-  LANG=da_DK.UTF-8
-  LANGUAGE=da
-  SHELL=/bin/bash
-  TERM=unknown
- PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate 
Backup Plus Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb']
- SourcePackage: gdebi
+  PATH=(custom, no user)
+  LANG=da_DK.UTF-8
+  LANGUAGE=da
+  SHELL=/bin/bash
+  TERM=unknown
+ PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate 
Backup Plus 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb']SourcePackage: 
gdebi
  Title: gdebi-gtk crashed with ValueError in update_interface(): could not 
convert string to float: '0,'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

** Description changed:

  Errors Bucket
  -
  https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53
+ and
+ https://errors.ubuntu.com/problem/c349b36522b1d43e2604357f75f0215fdafe1c7a
  
  Gdebi crashed while installing Google Chrome .deb-fil bur the error
  didn't appear until I logged out and back in again
  
  ProblemType: CrashDistroRelease: Ubuntu 16.10
  Package: gdebi 0.9.5.7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 15 15:01:11 2016
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2016-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive 
/media/jimmy/Seagate\ Backup\ Plus\ 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb
  ProcEnviron:
   PATH=(custom, no user)
   LANG=da_DK.UTF-8
   LANGUAGE=da
   SHELL=/bin/bash
   TERM=unknown
  PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate 
Backup Plus 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb']SourcePackage: 
gdebi
  Title: gdebi-gtk crashed with ValueError in update_interface(): could not 
convert string to float: '0,'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

Title:
  gdebi-gtk crashed with ValueError in update_interface(): could not
  convert string to float: '0,'

Status in gdebi package in Ubuntu:
  Confirmed
Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  Errors Bucket
  -
  https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53
  and
  https://errors.ubuntu.com/problem/c349b36522b1d43e2604357f75f0215fdafe1c7a

  Gdebi crashed while installing Google Chrome .deb-fil bur the error
  didn't appear until I logged out and back in again

  ProblemType: CrashDistroRelease: Ubuntu 16.10
  Package: gdebi 0.9.5.7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 15 15:01:11 2016
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2016-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive 
/media/jimmy/Seagate\ Backup\ Plus\ 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb
  ProcEnviron:
   PATH=(custom, no user)
   LANG=da_DK.UTF-8
   LANGUAGE=da
   SHELL=/bin/bash
   TERM=unknown
  PythonArgs: 

[Touch-packages] [Bug 1631631] Re: Trivial bug in man documentation: forgotten --strip-unneeded option in objcopy SYNOPSIS

2016-10-13 Thread Alberto Salvia Novella
** Changed in: binutils (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: hundredpapercuts
   Status: New => Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided => Medium

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

Title:
  Trivial bug in man documentation: forgotten --strip-unneeded option in
  objcopy SYNOPSIS

Status in One Hundred Papercuts:
  Confirmed
Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  In the man page of "objcopy" the "--strip-unneeded" option:
  - is described in OPTIONS section;
  - but is forgotten in SYNOPSIS section (don't confuse with 
"--strip-unneeded-symbol=" and "--strip-unneeded-symbols=", which aren't 
forgotten).

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  $ apt-cache policy binutils
  binutils:
Installed: 2.26.1-1ubuntu1~16.04.3
Candidate: 2.26.1-1ubuntu1~16.04.3
Version table:
   *** 2.26.1-1ubuntu1~16.04.3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.26-8ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I expected SYNOPSIS and OPTIONS sections of the man page of "objcopy"
  to be consistent.

  Option "--strip-unneeded" present in OPTIONS section, is absent in
  SYNOPSIS section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1631631/+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 1633219] Re: Upgrade to yakkety fails due to non-us locale

2016-10-13 Thread Vsevolod Velichko
May be you are right, I don't know where this "0," comes from.
But I'm not sure, may be it's ubuntu-release-upgrader and gdebi (since they are 
end-user binaries, rather than python-apt) who should set correct LC_NUMERIC.

** Also affects: python-apt (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Upgrade to yakkety fails due to non-us locale

Status in python-apt package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Upgrade to yakkety failed during updates installation. The do-release-
  upgrade window froze and there was a stacktrace in the terminal:

  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != self.percent or status_str != self.status:
  ValueError: could not convert string to float: '0,'
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 497, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 450, in write
  block = f.read(1048576)
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != self.percent or status_str != self.status:
  ValueError: could not convert string to float: '0,'

  
  It seems, that it's because release-upgrader incorrectly 

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

2016-10-13 Thread Jeremy
Luke and Joakim, thanks for your effort in this bug.

With Luke's latest PPA, things still don't work unless I use a terminal
command I found on askubuntu

pacmd set-card-profile `pacmd list-cards | grep bluez_card -B1 | grep
index | awk '{print $2}'` off; sleep 2 ; echo -e "disconnect
xx:xx:xx:xx:xx:xx\n quit"|bluetoothctl;sleep 5; echo -e "connect
xx:xx:xx:xx:xx:xx\n quit"|bluetoothctl; sleep 5; pacmd set-card-profile
`pacmd list-cards | grep bluez_card -B1 | grep index | awk '{print $2}'`
a2dp_sink

Where xx:xx:xx:xx:xx:xx is the MAC address of my headphones

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

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

Status in pulseaudio package in Ubuntu:
  In Progress

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

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

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

  Device info:

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

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

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

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


[Touch-packages] [Bug 1610111] Re: apache2 restart problems

2016-10-13 Thread Christian Boltz
abstractions/apache2-common was updated in trunk r2532 on 2014-06-12
(also included in 2.10 and 2.9), see bug 1322764.

I didn't check if r2532 covers everything reported in this bug.

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

Title:
  apache2 restart problems

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

Bug description:
  blahdeblah reported problems when deploying trusty apache2 with
  libapache2-mod-apparmor.

  The apache2 main processes are usually run in complain mode because
  there were problems restarting apache. At least a few rules were
  needed:

  To the main apache2 profile:
  signal peer=/usr/sbin/apache2//HANDLING_UNTRUSTED_INPUT,

  To the ^HANDLING_UNTRUSTED_INPUT hat:
  signal peer=/usr/sbin/apache2,

  To .. unknown hats (should be in all hats):
  #include (to receive profiles from unconfined)

  To abstractions/apache2-common:
  Change:
  @{PROC}/@{pid}/attr/currentw,
  to:
  @{PROC}/@{pid}/attr/currentrw,

  Also "flags=(complain)" was removed from ^DEFAULT_URI and
  ^HANDLING_UNTRUSTED_INPUT

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1610111/+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 1619216] Re: package gnupg 1.4.20-1ubuntu3 [modified: usr/bin/gpg usr/bin/gpgsplit usr/lib/gnupg/gpgkeys_curl usr/lib/gnupg/gpgkeys_finger usr/lib/gnupg/gpgkeys_hkp usr/lib/gnupg

2016-10-13 Thread Alberto Salvia Novella
** Changed in: gnupg (Ubuntu)
   Importance: Undecided => High

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

Title:
  package gnupg 1.4.20-1ubuntu3 [modified: usr/bin/gpg usr/bin/gpgsplit
  usr/lib/gnupg/gpgkeys_curl usr/lib/gnupg/gpgkeys_finger
  usr/lib/gnupg/gpgkeys_hkp usr/lib/gnupg/gpgkeys_ldap
  usr/share/man/man1/gpg.1.gz] failed to install/upgrade: package gnupg
  is not ready for configuration  cannot configure (current status
  'half-installed')

Status in gnupg package in Ubuntu:
  Confirmed

Bug description:
  error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnupg 1.4.20-1ubuntu3 [modified: usr/bin/gpg usr/bin/gpgsplit 
usr/lib/gnupg/gpgkeys_curl usr/lib/gnupg/gpgkeys_finger 
usr/lib/gnupg/gpgkeys_hkp usr/lib/gnupg/gpgkeys_ldap 
usr/share/man/man1/gpg.1.gz]
  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.1
  Architecture: amd64
  Date: Thu Sep  1 15:48:34 2016
  DpkgTerminalLog:
   dpkg: error processing package gnupg (--configure):
package gnupg is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package gnupg is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2016-08-28 (4 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: gnupg
  Title: package gnupg 1.4.20-1ubuntu3 [modified: usr/bin/gpg usr/bin/gpgsplit 
usr/lib/gnupg/gpgkeys_curl usr/lib/gnupg/gpgkeys_finger 
usr/lib/gnupg/gpgkeys_hkp usr/lib/gnupg/gpgkeys_ldap 
usr/share/man/man1/gpg.1.gz] failed to install/upgrade: package gnupg is not 
ready for configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1619216/+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 1606144] Re: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] No sound at all

2016-10-13 Thread Alberto Salvia Novella
** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works on laptop speakers, but there is no sound coming from the
  headphones jack. The laptop keeps playing from its own speakers
  instead of using the headphones I've plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.4.8-040408-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   stian  4028 F...m pulseaudio
   /dev/snd/controlC0:  stian  4028 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 25 10:03:23 2016
  InstallationDate: Installed on 2016-06-02 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   stian  4028 F...m pulseaudio
   /dev/snd/controlC0:  stian  4028 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] No sound 
at all
  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: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-07-25T10:01:11.561836

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606144/+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 1551731] Re: free command not working with -s flag

2016-10-13 Thread Alberto Salvia Novella
** Changed in: procps (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  free command not working with -s flag

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  when i enter this command :
  free -s 3
  or and numbers for seconds , it returns me :
  free: seconds argument `3' failed
  but i have only this bug in version 3.3.10 and in 3.3.9 it worls normally and 
refresh free in entered seconds

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  1 17:00:20 2016
  InstallationDate: Installed on 2016-01-24 (36 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160123)
  SourcePackage: procps
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1551731/+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 1610111] Re: apache2 restart problems

2016-10-13 Thread Christian Boltz
** Tags added: aa-policy

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

Title:
  apache2 restart problems

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

Bug description:
  blahdeblah reported problems when deploying trusty apache2 with
  libapache2-mod-apparmor.

  The apache2 main processes are usually run in complain mode because
  there were problems restarting apache. At least a few rules were
  needed:

  To the main apache2 profile:
  signal peer=/usr/sbin/apache2//HANDLING_UNTRUSTED_INPUT,

  To the ^HANDLING_UNTRUSTED_INPUT hat:
  signal peer=/usr/sbin/apache2,

  To .. unknown hats (should be in all hats):
  #include (to receive profiles from unconfined)

  To abstractions/apache2-common:
  Change:
  @{PROC}/@{pid}/attr/currentw,
  to:
  @{PROC}/@{pid}/attr/currentrw,

  Also "flags=(complain)" was removed from ^DEFAULT_URI and
  ^HANDLING_UNTRUSTED_INPUT

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1610111/+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 1631499] Re: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2016-10-13 Thread Alberto Salvia Novella
** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

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

Title:
  package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Installing new version of config file /etc/X11/Xsession.d/75dbus_dbus-launch 
...
  Setting up gcr (3.18.0-1ubuntu1) ...
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however:
Package libffi6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however:
Package libffi6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however:
Package libffi6:i386 is not configured yet.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Oct  7 15:22:06 2016
  DuplicateSignature: 
package:libglib2.0-0:i386:2.48.1-1~ubuntu16.04.1:dependency problems - leaving 
triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2014-09-03 (765 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: glib2.0
  Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-10-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1631499/+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 1629707] Re: package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2016-10-13 Thread Alberto Salvia Novella
** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Bug notification automatic after login

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-38-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: 92HD81B1X5 Analog [92HD81B1X5 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: 92HD81B1X5 Analog [92HD81B1X5 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guy1709 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xf050 irq 16'
 Mixer name : 'IDT 92HD81B1X5'
 Components : 'HDA:111d7605,103c1443,00100402'
 Controls  : 23
 Simple ctrls  : 11
  Date: Sun Oct  2 22:32:39 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=a101ccab-5f9a-4f81-bee3-73cda7f5ad0a
  InstallationDate: Installed on 2016-10-02 (0 days ago)
  InstallationMedia: budgie-remix 16.04.1 "Budgie-remix" -  amd64 (20160723)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=85b456d6-d514-4880-8f66-8fc03bf4ea4e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1443
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 67.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd02/25/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn1443:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 058B11242B1020100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1629707/+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 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

2016-10-13 Thread Alberto Salvia Novella
** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1630946/+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 1556459] Re: [Lenovo ThinkPad W530] Regression: cannot set up 3 display configuration any more (Optimus)

2016-10-13 Thread ligi
Just updated from 16.04 to 16.10 in the silent hope it fixes this
problem - unfortunately it got worse:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1633227

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

Title:
  [Lenovo ThinkPad W530] Regression: cannot set up 3 display
  configuration any more (Optimus)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I cannot set up the third monitor any more (it was working beginning
  of March 2016 with Ubuntu 16.04).

  The configuration with NVIDIA Optimus starts with builtin display (of
  Thinkpad W530) and one of (3K) monitors, the second monitor is
  detected, but not used.

  The unity configuration tool shows me two message boxes:

  "The selected configuration for displays could not be applied
  could not set the configuration for CRTC 64"

  and

  "Failed to apply configuration: %s

  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: 
could not set the configuration for CRTC 64
  "

  The first one I have seen at boot time on login screen (with 3
  displays) previously, the second one is new.

  The third monitor works if Optimus gets disabled in  BIOS and the
  machine runs with Nvidia only

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  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: Sat Mar 12 18:44:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.16, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  InstallationDate: Installed on 2016-02-25 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  MachineType: LENOVO 2447MU0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=c01ceec8-4b0c-447f-af8f-3e9c4ae90e15 ro rootflags=subvol=@ quiet 
splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2447MU0
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2447MU0
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar 12 18:30:45 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.1-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1556459/+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 1544791] Re: Is append mode useful?

2016-10-13 Thread Christian Boltz
** 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/1544791

Title:
  Is append mode useful?

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

Bug description:
  I think the 'a' append mode may not be useful.

  Including 'a' in a profile is insufficient for writing to the file, at
  least on 3.13.0-77-generic.

  Here's a sample profile:

  #include 

  /home/sarnold/demos/append flags=(complain) {
#include 

/home/sarnold/demos/append mr,
/home/sarnold/demos/testing a,

  }

  And I'll attach a sample program shortly.

  When using O_APPEND | O_WRONLY:

  If the file exists, denied_mask="w"
  If the file doesn't exist, open() fails, no AA involvement

  When using O_APPEND | O_WRONLY | O_CREAT:

  No change when the file does or doesn't exist: denied_mask="c",
  denied_mask="w"

  (When using enforce mode instead of complain mode, only
  denied_mask="c" gets logged; the open(2) fails and the write(2) is
  never called.)

  $ rm testing
  rm: cannot remove ‘testing’: No such file or directory
  $ ./append append wronly ; ls -l testing
  open: No such file or directory
  ls: cannot access testing: No such file or directory
  $ ./append append wronly creat ; ls -l testing
  open: Permission denied
  ls: cannot access testing: No such file or directory
  $ ./append append rdwr  ; ls -l testing
  open: No such file or directory
  ls: cannot access testing: No such file or directory
  $ ./append append rdwr creat ; ls -l testing
  open: Permission denied
  ls: cannot access testing: No such file or directory

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apparmor 2.8.95~2430-0ubuntu5.3
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 11 15:55:45 2016
  InstallationDate: Installed on 2012-10-18 (1211 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  KernLog:
   
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic 
root=UUID=7b8c2e1b-d2e6-47d9-9030-c078e9701a1d ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (670 days ago)
  
modified.conffile..etc.apparmor.d.abstractions.ubuntu.browsers.d.text.editors: 
[modified]
  mtime.conffile..etc.apparmor.d.abstractions.ubuntu.browsers.d.text.editors: 
2013-03-26T13:10:49

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1544791/+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 1622378] Re: package libqtcore4 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of packag

2016-10-13 Thread Alberto Salvia Novella
** Changed in: qt4-x11 (Ubuntu)
   Importance: Undecided => High

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

** Changed in: hundredpapercuts
   Status: New => Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided => High

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

Title:
  package libqtcore4 (not installed) failed to install/upgrade: trying
  to overwrite shared '/etc/xdg/Trolltech.conf', which is different from
  other instances of package libqtcore4:amd64

Status in One Hundred Papercuts:
  Confirmed
Status in qt4-x11 package in Ubuntu:
  Confirmed

Bug description:
  THis came up after I tried to install UNetbootin. I don't really know
  what's going on

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Sep 11 13:42:23 2016
  DuplicateSignature:
   package:libqtcore4:(not installed)
   Unpacking libqtcore4:amd64 (4:4.8.7+dfsg-5ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-5ubuntu2_amd64.deb (--unpack):
trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different 
from other instances of package libqtcore4:amd64
  ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:amd64
  InstallationDate: Installed on 2014-08-31 (742 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 (not installed) failed to install/upgrade: trying 
to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other 
instances of package libqtcore4:amd64
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (36 days ago)

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

2016-10-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

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:
  error after updating from 16.04.1 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Oct 11 22:08:46 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-25 (78 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(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-10-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1632415/+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 1633227] [NEW] After update to 16.10 second screen background is not cleared

2016-10-13 Thread ligi
Public bug reported:

I just updated from 16.04 to 16.10 and now the window background is not
cleared anymore - so when you drag windows they leave resedue which
looks like the screenshot I attached

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

** Attachment added: "ubuntu_16.10_2.png"
   
https://bugs.launchpad.net/bugs/1633227/+attachment/4760624/+files/ubuntu_16.10_2.png

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

Title:
  After update to 16.10 second screen background is not cleared

Status in xorg package in Ubuntu:
  New

Bug description:
  I just updated from 16.04 to 16.10 and now the window background is
  not cleared anymore - so when you drag windows they leave resedue
  which looks like the screenshot I attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1633227/+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 1633224] Re: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 5

2016-10-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to
  install/upgrade: il sottoprocesso nuovo script pre-removal ha
  restituito lo stato di errore 5

Status in android-tools package in Ubuntu:
  New

Bug description:
  Error launched while upgrading to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Oct 13 22:33:22 2016
  ErrorMessage: il sottoprocesso nuovo script pre-removal ha restituito lo 
stato di errore 5
  InstallationDate: Installed on 2014-04-19 (908 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: android-tools
  Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to 
install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo 
stato di errore 5
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1633224/+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 1617341] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-13 Thread Alberto Salvia Novella
** Changed in: ntp (Ubuntu)
   Importance: Undecided => High

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  The update did not install. Maybe because the net got disconnected in
  between ???

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   ntp: Install
   ntpdate: Install
   ntp: Configure
   ntpdate: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Aug 26 19:39:18 2016
  DpkgHistoryLog:
   Start-Date: 2016-08-26  19:36:04
   Commandline: aptdaemon role='role-commit-packages' sender=':1.65'
   Upgrade: ntp:amd64 (1:4.2.8p4+dfsg-3ubuntu5, 1:4.2.8p4+dfsg-3ubuntu5.1), 
ntpdate:amd64 (1:4.2.8p4+dfsg-3ubuntu5, 1:4.2.8p4+dfsg-3ubuntu5.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-03-28 (151 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=790d64f7-9847-4d8c-bbaa-3c87b8aaac16 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1617341/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

2016-10-13 Thread Mathieu Trudel-Lapierre
Seems to me like we're at the point where considering a straight revert
of the SRU would be in order (and I'm certainly considering it for the
short term), in order to move forward again at a later time when this is
more solid -- not that the end goal is still going to be happening
(though maybe not in 16.04), that is to gradually remove klibc from the
initramfs. That *will* require changes, such as we see here. If you
never fail, it's because you're not innovating...

The changes here were motivated by providing IPv6 support for MaaS
deployments in v6-only and mixed networks.

>From my understanding of things, we've now fixed (in 0.122ubuntu8.4) the
issues with ip=dhcp and some other ip= forms being parsed incorrectly.

There are still two outstanding issues:
 - boot speed (I suspect there is only a limited amount of things we can do 
about this, given the use of dhclient).
 - "portfast behavior", which is how we handle delays in getting a response 
from a DHCP server. There was definitely a regression there, for which I have a 
fix in my ppa at ppa:cyphermox/maas.

Are there any other outstanding issues? If so, what kernel command-line
are you using, and please include the exact messages on screen (or in
logs) so we can know what we're dealing with.

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in z-series:
  Fix Committed

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
     - The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken
     -
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  This bug is a regression of changes made under bug 1628306.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1633224] [NEW] package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 5

2016-10-13 Thread Paolo Roth
Public bug reported:

Error launched while upgrading to 16.10

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Thu Oct 13 22:33:22 2016
ErrorMessage: il sottoprocesso nuovo script pre-removal ha restituito lo stato 
di errore 5
InstallationDate: Installed on 2014-04-19 (908 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: android-tools
Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to 
install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo 
stato di errore 5
UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)

** Affects: android-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package yakkety

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

Title:
  package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to
  install/upgrade: il sottoprocesso nuovo script pre-removal ha
  restituito lo stato di errore 5

Status in android-tools package in Ubuntu:
  New

Bug description:
  Error launched while upgrading to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Oct 13 22:33:22 2016
  ErrorMessage: il sottoprocesso nuovo script pre-removal ha restituito lo 
stato di errore 5
  InstallationDate: Installed on 2014-04-19 (908 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: android-tools
  Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to 
install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo 
stato di errore 5
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1633224/+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 1606000] Re: package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6

2016-10-13 Thread Alberto Salvia Novella
** Changed in: apt (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 6

Status in apt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  bug error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 24 09:52:56 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 6
  InstallationDate: Installed on 2015-09-20 (308 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: apt
  Title: package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 6
  UpgradeStatus: Upgraded to xenial on 2016-07-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1606000/+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 1594105] Re: package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

2016-10-13 Thread Alberto Salvia Novella
** Changed in: qt4-x11 (Ubuntu)
   Importance: Undecided => High

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

Title:
  package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in qt4-x11 package in Ubuntu:
  Confirmed

Bug description:
  I was installing the Skype

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun 19 08:56:22 2016
  DuplicateSignature:
   package:libqt4-sql:i386:4:4.8.7+dfsg-5ubuntu2
   Processing triggers for libc-bin (2.23-0ubuntu3) ...
   dpkg: error processing package libqt4-sql:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-06-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 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/qt4-x11/+bug/1594105/+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 1597280] Re: [SVS1512Z9EB, Realtek ALC275, Black Headphone Out, Left] volume slider problem

2016-10-13 Thread Alberto Salvia Novella
** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [SVS1512Z9EB, Realtek ALC275, Black Headphone Out, Left] volume slider
  problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Very low sound level. Alsamixer and pavucontrol did not help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hoofoo 1877 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jun 29 13:37:49 2016
  InstallationDate: Installed on 2016-06-18 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Volume slider, or mixer problems
  Title: [SVS1512Z9EB, Realtek ALC275, Black Headphone Out, Left] volume slider 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0081C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0081C8:bd09/18/2012:svnSonyCorporation:pnSVS1512Z9EB:pvrC60B4TX4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1512Z9EB
  dmi.product.version: C60B4TX4
  dmi.sys.vendor: Sony Corporation
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-06-29T12:57:00.907312

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597280/+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 1606051] Re: dhclient fails to get address after latest patches

2016-10-13 Thread Alberto Salvia Novella
** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => High

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

Title:
  dhclient fails to get address after latest patches

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  From ASkUbuntu entry http://askubuntu.com/questions/801136/recent-
  patches-broke-dhclient/802390

  Running 16.04.01 LTS recently upgraded from 15.10. System is a home firewall 
with enp1s0 as LAN interface statically assigned and enp2s0 is WAN interface 
using DHCP, connected to modem.
  Ran apt-get upgrade and on reboot enp2s0 had no address. running ifdown 
enp2s0 and then ifup enp2s0 gave me

  root@sam:~# ifup enp2s0
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/enp2s0/d0:50:99:21:80:f8
  Sending on   LPF/enp2s0/d0:50:99:21:80:f8
  Sending on   Socket/fallback
  DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 3 (xid=0xd998571a)
  send_packet: Network is down
  dhclient.c:2098: Failed to send 300 byte long packet over enp2s0 interface.
  receive_packet failed on enp2s0: Network is down
  DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 5 (xid=0xd998571a)
  send_packet: Network is down
  Running ifconfig enp2s0 up and dhclient enp2s0 gave similar results, but 
eventually /var/log/syslog showed a dhclient ipv4 lease being obtained - but 
the enp2s0 had only an IPv6 address, which appears to have come from 
avahi-daemon.

  I then manually configured the enp2s0 interface with ifconfig enp2s0
  xxx.xxx.xxx.xxx netmask 255.255.248.0 and put in a default route based
  on the lease info in dhclient.leases and I'm back online. But if I
  reboot or try to get dhclient to work, I continue to get the network
  is down errors.

  apparmor is disabled, so that's not it. iptables is set to allow all
  DHCP traffic (67/udp and 68/udp) and all RELATED,ESTABLISHED traffic
  from enp2s0.

  enp2s0 and enp2s0 are the same hardware.

  root@sam:~# lshw -class network
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:01:00.0
 logical name: enp1s0
 version: 01
 serial: 04:8d:38:5d:20:17
 size: 100Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi pciexpress bus_master cap_list rom ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full ip=yyy.yyy.yyy.yyy latency=0 link=yes 
multicast=yes port=MII speed=100Mbit/s
 resources: irq:38 ioport:e000(size=256) memory:ffa0-ffa00fff 
memory:ffa2-ffa3
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: enp2s0
 version: 11
 serial: d0:50:99:21:80:f8
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 
ip=xxx.xxx.xxx.xxx latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
 resources: irq:40 ioport:d000(size=256) memory:ff90-ff900fff 
memory:d080-d0803fff
  Ideas? remember, this happened right after patching.

  networking network-manager dhclient

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12.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.1
  Architecture: amd64
  Date: Sun Jul 24 15:33:19 2016
  InstallationDate: Installed on 2016-03-01 (145 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to xenial on 2016-06-22 (32 days ago)
  mtime.conffile..etc.dhcp.debug: 2016-06-28T18:13:33.371977

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1606051/+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 1633217] Re: package avahi-daemon 0.6.32-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package avahi-daemon 0.6.32-1ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  After upgrading to 16.10 unity seems to crash completely I have no
  window border and no menu bar and no launcher.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Oct 13 22:40:10 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-06-22 (844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32-1ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.avahi.avahi-daemon.conf: 2016-10-13T22:52:08.066609

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1633217/+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 1633217] [NEW] package avahi-daemon 0.6.32-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-13 Thread Johannes Christenson
Public bug reported:

After upgrading to 16.10 unity seems to crash completely I have no
window border and no menu bar and no launcher.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: avahi-daemon 0.6.32-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Thu Oct 13 22:40:10 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2014-06-22 (844 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: avahi
Title: package avahi-daemon 0.6.32-1ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.avahi.avahi-daemon.conf: 2016-10-13T22:52:08.066609

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


** Tags: amd64 apport-package yakkety

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

Title:
  package avahi-daemon 0.6.32-1ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  After upgrading to 16.10 unity seems to crash completely I have no
  window border and no menu bar and no launcher.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Oct 13 22:40:10 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-06-22 (844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32-1ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.avahi.avahi-daemon.conf: 2016-10-13T22:52:08.066609

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1633217/+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 1385947] Re: specifying -O to parser causes the parser to not consider cache files

2016-10-13 Thread Christian Boltz
** Tags added: aa-parser

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

Title:
  specifying -O to parser causes the parser to not consider cache files

Status in AppArmor:
  Confirmed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu RTM:
  Fix Released

Bug description:
  If the cache files are up to date and I specify:
  /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor 
-- profile1 profile2 ...

  then the cache files in /var/cache/apparmor are used (good).

  However, if the cache files are up to date and I specify:
  /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor 
-O no-expr-simplify -- profile1 profile2 ...

  then the cache files in /var/cache/apparmor are all regenerated (not
  good).  This needs to be fixed in order to use '-O no-expr-simplify'
  to fix bug #1383858.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1385947/+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 1626411] Re: package ifupdown 0.8.10ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-13 Thread Alberto Salvia Novella
** Changed in: ifupdown (Ubuntu)
   Importance: Undecided => High

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

Title:
  package ifupdown 0.8.10ubuntu1.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  In upgrade after download package this package is going to failed
  during installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 02:05:28 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-03-17 (188 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ifupdown
  Title: package ifupdown 0.8.10ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1626411/+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 1598759] Re: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved

2016-10-13 Thread Christian Boltz
** Tags added: aa-policy

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

Title:
  AppArmor nameservice abstraction doesn't allow communication with
  systemd-resolved

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Fix Committed
Status in ntp package in Ubuntu:
  Invalid
Status in apparmor source package in Yakkety:
  Fix Committed
Status in ntp source package in Yakkety:
  Invalid

Bug description:
  [ Impact ]

  Processes confined by AppArmor profiles making use of the nameservice
  AppArmor abstraction are unable to access the systemd-resolved network
  name resolution service. The nsswitch.conf file shipped in Yakkety
  puts the nss-resolve plugin to use which talks to systemd-resolved
  over D-Bus. The D-Bus communication is blocked for the confined
  processes described above and those processes will fallback to the
  traditional means of name resolution.

  [ Test Case ]

  * Use ntpd to test:
$ sudo apt-get install -y ntp
...
$ sudo systemctl stop ntp

# in another terminal, watch for AppArmor denials
$ dmesg -w

# in the original terminal, start ntp
$ sudo systemctl start ntp

# You'll see a number of denials on the system_bus_socket file:
audit: type=1400 audit(1476240762.854:35): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=3867 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=126 ouid=0

   * Use tcpdump to test:

 # Capture traffic on whichever network interface you're currently using
 $ sudo tcpdump -i eth0

 # Look in /var/log/syslog for denials on the system_bus_socket file:
 audit: type=1400 audit(1476240896.021:40): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/tcpdump" 
name="/run/dbus/system_bus_socket" pid=4106 comm="tcpdump" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0

  In both situations, ntpd and tcpdump will seemingly work as expected
  due to the name resolution fallback configured in nsswitch.conf.
  However, neither confined process will be using systemd-resolved for
  name resolution.

  [ Regression Potential ]

  This fix will allow ntp, tcpdump, cupsd, dhclient, and other confined-
  by-default programs to start using systemd-resolved. There is some
  potential for regression since those applications have not been
  previously using systemd-resolved.

  [ Original bug description ]

  On this plain install of Xenial apparmor complains about ntpd:

  [   19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0

  Adding the following line to /etc/apparmor.d/usr.sbin.ntpd fixes the
  problem:

  #include 

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1598759/+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 1380702] Re: No keyboards shortcuts in QT apps

2016-10-13 Thread Nitin Gupta
Using Ubuntu 16.04 and no keyboard shortcuts visible is Visual Studio
Code which is I think based on Chrome. Though shortcuts are not visible
alongside menu text, they do trigger correct action when invoked. Still,
having them visible alongside menu text would be useful.

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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 1310186] Re: mediascanner prevents unmounting usb device

2016-10-13 Thread Alberto Salvia Novella
** Changed in: mediascanner2 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: mediascanner2 (Ubuntu)
   Importance: Medium => High

** Changed in: mediascanner2 (Ubuntu)
   Importance: High => Critical

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

Title:
  mediascanner prevents unmounting usb device

Status in mediascanner2 package in Ubuntu:
  Confirmed

Bug description:
  Trying to unmount a block device I just mounted, I get the following
  error (sorry for not resetting the locale. It says "Device is busy"):

  :~$ sudo umount /media/tkluck/tjk-backup 
  umount2: Apparaat of hulpbron is bezig
  umount: /media/tkluck/tjk-backup: apparaat is bezig
  (Welke processen het apparaat gebruiken kan mogelijk
   gevonden worden met behulp van lsof(8) of fuser(1).)
  umount2: Apparaat of hulpbron is bezig

  I get the same error in a dialog window when trying to unmount from
  the file manager.

  Using lsof shows that the media-scanner daemon is the culprit:

  tkluck@ultrabook-tjk:~$ lsof /media/tkluck/tjk-backup 
  COMMANDPID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
  mediascan 2898 tkluck   16r   DIR  252,3   2498562 
/media/tkluck/tjk-backup
  mediascan 2898 tkluck   17r   DIR  252,3 4096 50855937 
  mediascan 2898 tkluck   18r   DIR  252,3 4096 39080372 
  mediascan 2898 tkluck   19r   DIR  252,312288 39080513 
  mediascan 2898 tkluck   20r   DIR  252,320480 39080525 
  mediascan 2898 tkluck   21r   DIR  252,3 4096 46792990 
  mediascan 2898 tkluck   22r   DIR  252,3 4096 46792991 
  mediascan 2898 tkluck   23r   DIR  252,316384 46793749 
  mediascan 2898 tkluck   24r   DIR  252,3 4096 47317994 
  mediascan 2898 tkluck   25r   DIR  252,3 4096 47317997 
  mediascan 2898 tkluck   26r   DIR  252,3 4096 47317999 

  Sending it

  sudo kill -9 2898

  solved this for me.

  This is on Ubuntu GNOME 14.04. I uninstalled the mediascanner2.0 to
  solve this "once and for all" (which has no other impact since I do
  not use Unity).

  My guess is that the scan usually finishes quickly after mounting. But
  because this particular drive contains a big filetree, it doesn't,
  resulting in the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1310186/+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 1576524] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-13 Thread Alberto Salvia Novella
** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  It might have to do with installing nvidia-364 from the graphics diver
  PPA.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 22:59:47 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-28 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1576524/+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 1622223] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

2016-10-13 Thread Alberto Salvia Novella
** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

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

Title:
  package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Attempted system upgrade - many dialogue boxes appear with this error;
  attempted apt-get -f install but still get errors

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 225-1ubuntu9.1
  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.1
  Architecture: amd64
  Date: Sat Sep 10 12:16:04 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2013-04-27 (1231 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-09-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/163/+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 1631504] Re: loadkeys segfaults with certain arguments in 16.10

2016-10-13 Thread Ubuntu Foundations Team Bug Bot
The attachment "loadkeys_fix_implicit_xmalloc.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

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

** Tags added: patch

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

Title:
  loadkeys segfaults with certain arguments in 16.10

Status in kbd package in Ubuntu:
  New

Bug description:
  This can be reproduced as follows:

  1) Switch to VT 1 (ctrl+alt+f1)
  2) run: loadkeys garbage
  3) loadkeys will segfault

  The problem appears to be with the implicit declaration of xmalloc in 
loadkeys.c. It is resolved if
  #include "xmalloc.h" is added to the top of that file (and in fact all the 
other source files in kbd that reference xmalloc include that file).

  Interestingly xmalloc is resolved without include but the returned
  pointer seems to get truncated. It doesn't do this if the source is
  built with gcc 5.4 in 16.04 so maybe it has something to do with gcc
  6.2 in 16.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: kbd 2.0.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  7 15:27:58 2016
  InstallationDate: Installed on 2016-10-06 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161006)
  SourcePackage: kbd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1631504/+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 1598759] Re: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved

2016-10-13 Thread Tyler Hicks
We've decided not to merge this patch in the upstream AppArmor project
at this time because most distros don't have the ability to perform
fine-grained mediation of D-Bus communications and this change would
grant full system bus access to network-facing daemons in those distros.

** Changed in: apparmor
   Status: In Progress => Triaged

** Changed in: apparmor
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  AppArmor nameservice abstraction doesn't allow communication with
  systemd-resolved

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Fix Committed
Status in ntp package in Ubuntu:
  Invalid
Status in apparmor source package in Yakkety:
  Fix Committed
Status in ntp source package in Yakkety:
  Invalid

Bug description:
  [ Impact ]

  Processes confined by AppArmor profiles making use of the nameservice
  AppArmor abstraction are unable to access the systemd-resolved network
  name resolution service. The nsswitch.conf file shipped in Yakkety
  puts the nss-resolve plugin to use which talks to systemd-resolved
  over D-Bus. The D-Bus communication is blocked for the confined
  processes described above and those processes will fallback to the
  traditional means of name resolution.

  [ Test Case ]

  * Use ntpd to test:
$ sudo apt-get install -y ntp
...
$ sudo systemctl stop ntp

# in another terminal, watch for AppArmor denials
$ dmesg -w

# in the original terminal, start ntp
$ sudo systemctl start ntp

# You'll see a number of denials on the system_bus_socket file:
audit: type=1400 audit(1476240762.854:35): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=3867 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=126 ouid=0

   * Use tcpdump to test:

 # Capture traffic on whichever network interface you're currently using
 $ sudo tcpdump -i eth0

 # Look in /var/log/syslog for denials on the system_bus_socket file:
 audit: type=1400 audit(1476240896.021:40): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/tcpdump" 
name="/run/dbus/system_bus_socket" pid=4106 comm="tcpdump" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0

  In both situations, ntpd and tcpdump will seemingly work as expected
  due to the name resolution fallback configured in nsswitch.conf.
  However, neither confined process will be using systemd-resolved for
  name resolution.

  [ Regression Potential ]

  This fix will allow ntp, tcpdump, cupsd, dhclient, and other confined-
  by-default programs to start using systemd-resolved. There is some
  potential for regression since those applications have not been
  previously using systemd-resolved.

  [ Original bug description ]

  On this plain install of Xenial apparmor complains about ntpd:

  [   19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0

  Adding the following line to /etc/apparmor.d/usr.sbin.ntpd fixes the
  problem:

  #include 

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1598759/+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 1598759] Re: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved

2016-10-13 Thread Tyler Hicks
This change looks to be working as expected. I've done the manual
verification in the bug description and I've also went through the
desktop/server related portions of
https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor.

** 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/1598759

Title:
  AppArmor nameservice abstraction doesn't allow communication with
  systemd-resolved

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Fix Committed
Status in ntp package in Ubuntu:
  Invalid
Status in apparmor source package in Yakkety:
  Fix Committed
Status in ntp source package in Yakkety:
  Invalid

Bug description:
  [ Impact ]

  Processes confined by AppArmor profiles making use of the nameservice
  AppArmor abstraction are unable to access the systemd-resolved network
  name resolution service. The nsswitch.conf file shipped in Yakkety
  puts the nss-resolve plugin to use which talks to systemd-resolved
  over D-Bus. The D-Bus communication is blocked for the confined
  processes described above and those processes will fallback to the
  traditional means of name resolution.

  [ Test Case ]

  * Use ntpd to test:
$ sudo apt-get install -y ntp
...
$ sudo systemctl stop ntp

# in another terminal, watch for AppArmor denials
$ dmesg -w

# in the original terminal, start ntp
$ sudo systemctl start ntp

# You'll see a number of denials on the system_bus_socket file:
audit: type=1400 audit(1476240762.854:35): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=3867 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=126 ouid=0

   * Use tcpdump to test:

 # Capture traffic on whichever network interface you're currently using
 $ sudo tcpdump -i eth0

 # Look in /var/log/syslog for denials on the system_bus_socket file:
 audit: type=1400 audit(1476240896.021:40): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/tcpdump" 
name="/run/dbus/system_bus_socket" pid=4106 comm="tcpdump" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0

  In both situations, ntpd and tcpdump will seemingly work as expected
  due to the name resolution fallback configured in nsswitch.conf.
  However, neither confined process will be using systemd-resolved for
  name resolution.

  [ Regression Potential ]

  This fix will allow ntp, tcpdump, cupsd, dhclient, and other confined-
  by-default programs to start using systemd-resolved. There is some
  potential for regression since those applications have not been
  previously using systemd-resolved.

  [ Original bug description ]

  On this plain install of Xenial apparmor complains about ntpd:

  [   19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0

  Adding the following line to /etc/apparmor.d/usr.sbin.ntpd fixes the
  problem:

  #include 

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1598759/+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 1575438] Re: usr.sbin.nscd needs r/w access to nslcd socket

2016-10-13 Thread Seth Arnold
I think you're right that adding the nslcd socket to the
abstractions/nameservice probably makes sense; I didn't see anything in
the nslcd manpages that suggested nscd was the only way to use the
module.

Thanks

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

Title:
  usr.sbin.nscd needs r/w access to nslcd socket

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

Bug description:
  I am usinc nscd with nslcd (LDAP lookup daemon) for NSS services via
  LDAP.

  It is typical to configure nslcd to connect to the actual LDAP server,
  and then set up /etc/ldap.conf (which is what NSS/nscd uses for "ldap"
  type lookups in /etc/nsswitch.conf) with a server URI of
  ldapi:///var/run/nslcd/socket . This way, only nslcd needs to talk
  with the LDAP server, rather than every application that wants to do
  getpwent() et al.

  Unfortunately, the usr.sbin.nscd profile in apparmor-profiles
  2.10.95-0ubuntu2 (Xenial) makes no mention of the nslcd socket, which
  results in NSS LDAP lookups not working when the profile is enforced
  in this configuration.

  This is the new line that is needed:

  /{,var/}run/nslcd/socket rw,

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1575438/+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 1575455] Re: New AppArmor profile: usr.sbin.nslcd

2016-10-13 Thread Christian Boltz
** Tags added: aa-policy

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

Title:
  New AppArmor profile: usr.sbin.nslcd

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

Bug description:
  nslcd is a good program to be covered by an AppArmor profile, as it
  communicates with an LDAP server and services queries from arbitrary
  local applications.

  This new profile used the existing usr.sbin.nscd profile as a starting
  point.

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

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


[Touch-packages] [Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

2016-10-13 Thread Scott Moser
It seems that the issue here is networking.service does:
  /sbin/ifdown -a --read-environment
but it should do:
  ifdown -a --exclude=lo

As is seen in the equivalent upstart job (/etc/init/networking.conf).

$ m="ifdown -a --read-environment";
$ sed -i "s,$m, --exclude=lo," /lib/systemd/system/networking.service
$ systemctl daemon-reload
$ sudo poweroff

Demonstration below.

## http://paste.ubuntu.com/23319833/
## ipv6 networking is broken by
##ip link set down dev lo
##
## This seems to be the root cause of bug 1629972 (http://pad.lv/1629972)
## where system networking (networking.service) is brought down on
## shutdown and causes hang.
##
## Note, that it is the link that is the issue, there is actually
## no problem seen in 'ping6' by either:
##ip addr del 127.0.0.1/8 dev lo
##ip addr del ::1/128 dev lo

$ for n in y1 y2; do lxc delete --force $n; lxc launch ubuntu-daily:yakkety $n; 
done
error: not found
Creating y1
Starting y1
error: not found
Creating y2
Starting y2

$ for n in y1 y2; do lxc exec $n -- dhclient -6 -1 -v eth0; done

$ lxc list y[12]
+--+-+--+++---+
| NAME |  STATE  | IPV4 |  IPV6 
 |TYPE| SNAPSHOTS |
+--+-+--+++---+
| y1   | RUNNING | 10.75.205.102 (eth0) | 
fd42:eee5:7c43:3d62:c7fd:6ccc:6181:8d48 (eth0) | PERSISTENT | 0 |
+--+-+--+++---+
| y2   | RUNNING | 10.75.205.5 (eth0)   | 
fd42:eee5:7c43:3d62:f285:69dd:7210:c0a5 (eth0) | PERSISTENT | 0 |
+--+-+--+++---+

$ for n in y1 y2; do
   lxc exec $n -- ip route add fd42:eee5:7c43:3d62::0/64 dev eth0

$ lxc exec y1 --  ping6 fd42:eee5:7c43:3d62:f285:69dd:7210:c0a5
PING 
fd42:eee5:7c43:3d62:f285:69dd:7210:c0a5(fd42:eee5:7c43:3d62:f285:69dd:7210:c0a5)
 56 data bytes
64 bytes from fd42:eee5:7c43:3d62:f285:69dd:7210:c0a5: icmp_seq=1 ttl=64 
time=0.133 ms
64 bytes from fd42:eee5:7c43:3d62:f285:69dd:7210:c0a5: icmp_seq=2 ttl=64 
time=0.061 ms
64 bytes from fd42:eee5:7c43:3d62:f285:69dd:7210:c0a5: icmp_seq=3 ttl=64 
time=0.069 ms
...



$ lxc exec y1 -- ip link set down dev lo


immediately ping6 starts dropping packets in window1.


** Changed in: ifupdown (Ubuntu)
 Assignee: (unassigned) => Scott Moser (smoser)

** Changed in: ifupdown (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

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

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

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Xenial:
  Confirmed

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

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

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

  [Impact]

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

  [Test Case]

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

  [Regression potential]

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

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

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


[Touch-packages] [Bug 1632620] Re: No audio from webbrowser-app in 16.10 U8 or U7 session

2016-10-13 Thread Launchpad Bug Tracker
** Branch linked: lp:~osomon/webbrowser-app/fix-1632620-sound-yakkety

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

Title:
  No audio from webbrowser-app in 16.10 U8 or U7 session

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Load the browser on 16.10 in either a U8 or U7 session.
  Browse to YouTube
  Play a video
  Notice there is no sound.  Nor does the browser show in the sound menu/panel.

  I've attached the application-legacy-webbrowser-app-.log file which
  shows problems with "unknown pcm devices"

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1632620/+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 1575438] Re: usr.sbin.nscd needs r/w access to nslcd socket

2016-10-13 Thread Christian Boltz
** Tags added: aa-policy

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

Title:
  usr.sbin.nscd needs r/w access to nslcd socket

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

Bug description:
  I am usinc nscd with nslcd (LDAP lookup daemon) for NSS services via
  LDAP.

  It is typical to configure nslcd to connect to the actual LDAP server,
  and then set up /etc/ldap.conf (which is what NSS/nscd uses for "ldap"
  type lookups in /etc/nsswitch.conf) with a server URI of
  ldapi:///var/run/nslcd/socket . This way, only nslcd needs to talk
  with the LDAP server, rather than every application that wants to do
  getpwent() et al.

  Unfortunately, the usr.sbin.nscd profile in apparmor-profiles
  2.10.95-0ubuntu2 (Xenial) makes no mention of the nslcd socket, which
  results in NSS LDAP lookups not working when the profile is enforced
  in this configuration.

  This is the new line that is needed:

  /{,var/}run/nslcd/socket rw,

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1575438/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

2016-10-13 Thread Jarno Suni
For people to whom the previously mentioned troubleshooting alternatives do not 
work, or who just need more advanced kernel purging this could be an option:
https://www.bountysource.com/issues/38300038-feature-request-the-command-should-work-like-this

-- 
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/Lubuntu/Documentation/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 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created; remove rsyslog from default installs

2016-10-13 Thread Sean Ford
I understand it is not desirable to have duplicate logging, but there is
a corner case where logging that is done during systemd shutdown is lost
because rsyslog is killed. This makes shutdown look broken due to it
being non-deterministic exactly when rsyslog is killed.

Currently, the easiest way to get accurate logging is creating
/var/log/journal.

## Sometimes shutdown logs are brief:

Oct 13 18:51:07 HOST systemd[1]: Stopped target Cloud-init target.
Oct 13 18:51:07 HOST systemd[1]: Starting Unattended Upgrades Shutdown...
Oct 13 18:51:07 HOST systemd[1]: Stopping Session 1 of user ubuntu.
Oct 13 18:51:07 HOST systemd[1]: Stopped target Graphical Interface.
Oct 13 18:51:07 HOST systemd[1]: Stopping Accounts Service...
Oct 13 18:51:07 HOST rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" 
x-pid="759" x-info="http://www.rsyslog.com;] exiting on signal 15.

## Sometimes more detailed

Oct 13 18:57:33 HOST systemd[1]: Stopping Session 1 of user ubuntu.
Oct 13 18:57:33 HOST systemd[1]: Stopping User Manager for UID 1000...
Oct 13 18:57:33 HOST systemd[1]: Stopped target Timers.
Oct 13 18:57:33 HOST systemd[1]: Stopped Daily apt activities.
Oct 13 18:57:33 HOST systemd[1277]: Reached target Shutdown.
Oct 13 18:57:33 HOST systemd[1277]: Stopped target Default.
Oct 13 18:57:33 HOST systemd[1277]: Stopped target Basic System.
Oct 13 18:57:33 HOST systemd[1277]: Stopped target Timers.
Oct 13 18:57:33 HOST systemd[1277]: Stopped target Sockets.
Oct 13 18:57:33 HOST systemd[1277]: Starting Exit the Session...
Oct 13 18:57:33 HOST systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Oct 13 18:57:33 HOST systemd[1277]: Stopped target Paths.
Oct 13 18:57:33 HOST systemd[1]: Stopped target Graphical Interface.
Oct 13 18:57:33 HOST systemd[1]: Stopped Timer to automatically refresh 
installed snaps.
Oct 13 18:57:33 HOST systemd[1]: Stopping ACPI event daemon...
Oct 13 18:57:33 HOST systemd[1]: Starting Unattended Upgrades Shutdown...
Oct 13 18:57:33 HOST systemd[1]: Stopping Accounts Service...
Oct 13 18:57:33 HOST systemd[1]: Closed Load/Save RF Kill Switch Status 
/dev/rfkill Watch.
Oct 13 18:57:33 HOST systemd[1]: Stopping Virtual machine log manager...
Oct 13 18:57:33 HOST systemd[1]: Stopped target Cloud-init target.
Oct 13 18:57:33 HOST systemd[1277]: Received SIGRTMIN+24 from PID 1592 (kill).
Oct 13 18:57:33 HOST systemd[1]: Stopped Execute cloud user/final scripts.
Oct 13 18:57:33 HOST systemd[1]: Stopped Apply the settings specified in 
cloud-config.
Oct 13 18:57:33 HOST systemd[1]: Stopped target Cloud-config availability.
Oct 13 18:57:33 HOST rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" 
x-pid="737" x-info="http://www.rsyslog.com;] exiting on signal 15.

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created; remove rsyslog from default installs

Status in systemd package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't. 
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+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 1631241] Re: Name resolution stops working after resume from suspend

2016-10-13 Thread Launchpad Bug Tracker
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/1631241

Title:
  Name resolution stops working after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1631241/+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 1633186] Re: Unity 8 crashes every 5 seconds

2016-10-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Unity 8 crashes every 5 seconds

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I got some Bugsplat screens come up but they didn't bring up a
  Launchpad window so I'm gonna report it here too.

  I tried the Unity 8 session in Ubuntu 16.10 and when I log in I can't
  move the mouse (maybe this should be filed as a separate bug?), once I
  hit the keyboard (I used Alt+Tab) I am able to move the mouse but the
  screen goes black after five seconds and then comes back up after
  around 2.5 seconds with the scopes and indicator tray visibly
  reloading. After five seconds, the screen goes black again, comes up
  after 2.5 seconds, goes black after five seconds... seemingly forever.

  I noticed that my fingerprint scanner (this is a Lenovo ThinkPad X201)
  had its light on so it was wanting to receive a fingerprint. Trying to
  scan my fingerprint didn't make a difference to the situation. I use
  fprint from this PPA
  (https://launchpad.net/~fingerprint/+archive/ubuntu/fprint) to get the
  scanner to work, I don't think the official repository version of
  fprint supports my fingerprint reader. I will remove the package and
  see if this changes the situation and will edit/comment once I've done
  that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  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: Thu Oct 13 19:36:47 2016
  InstallationDate: Installed on 2016-06-18 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1633186/+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 1632620] Re: No audio from webbrowser-app in 16.10 U8 or U7 session

2016-10-13 Thread Olivier Tilloy
** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  No audio from webbrowser-app in 16.10 U8 or U7 session

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Load the browser on 16.10 in either a U8 or U7 session.
  Browse to YouTube
  Play a video
  Notice there is no sound.  Nor does the browser show in the sound menu/panel.

  I've attached the application-legacy-webbrowser-app-.log file which
  shows problems with "unknown pcm devices"

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1632620/+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 1632620] Re: No audio from webbrowser-app in 16.10 U8 or U7 session

2016-10-13 Thread Olivier Tilloy
** Also affects: apparmor-easyprof-ubuntu (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/1632620

Title:
  No audio from webbrowser-app in 16.10 U8 or U7 session

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Load the browser on 16.10 in either a U8 or U7 session.
  Browse to YouTube
  Play a video
  Notice there is no sound.  Nor does the browser show in the sound menu/panel.

  I've attached the application-legacy-webbrowser-app-.log file which
  shows problems with "unknown pcm devices"

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1632620/+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 1633186] [NEW] Unity 8 crashes every 5 seconds

2016-10-13 Thread Ads20000
Public bug reported:

I got some Bugsplat screens come up but they didn't bring up a Launchpad
window so I'm gonna report it here too.

I tried the Unity 8 session in Ubuntu 16.10 and when I log in I can't
move the mouse (maybe this should be filed as a separate bug?), once I
hit the keyboard (I used Alt+Tab) I am able to move the mouse but the
screen goes black after five seconds and then comes back up after around
2.5 seconds with the scopes and indicator tray visibly reloading. After
five seconds, the screen goes black again, comes up after 2.5 seconds,
goes black after five seconds... seemingly forever.

I noticed that my fingerprint scanner (this is a Lenovo ThinkPad X201)
had its light on so it was wanting to receive a fingerprint. Trying to
scan my fingerprint didn't make a difference to the situation. I use
fprint from this PPA
(https://launchpad.net/~fingerprint/+archive/ubuntu/fprint) to get the
scanner to work, I don't think the official repository version of fprint
supports my fingerprint reader. I will remove the package and see if
this changes the situation and will edit/comment once I've done that.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: unity8 8.14+16.10.20160922-0ubuntu2
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: Thu Oct 13 19:36:47 2016
InstallationDate: Installed on 2016-06-18 (116 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: unity8
UpgradeStatus: Upgraded to yakkety on 2016-10-11 (2 days ago)

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

Title:
  Unity 8 crashes every 5 seconds

Status in unity8 package in Ubuntu:
  New

Bug description:
  I got some Bugsplat screens come up but they didn't bring up a
  Launchpad window so I'm gonna report it here too.

  I tried the Unity 8 session in Ubuntu 16.10 and when I log in I can't
  move the mouse (maybe this should be filed as a separate bug?), once I
  hit the keyboard (I used Alt+Tab) I am able to move the mouse but the
  screen goes black after five seconds and then comes back up after
  around 2.5 seconds with the scopes and indicator tray visibly
  reloading. After five seconds, the screen goes black again, comes up
  after 2.5 seconds, goes black after five seconds... seemingly forever.

  I noticed that my fingerprint scanner (this is a Lenovo ThinkPad X201)
  had its light on so it was wanting to receive a fingerprint. Trying to
  scan my fingerprint didn't make a difference to the situation. I use
  fprint from this PPA
  (https://launchpad.net/~fingerprint/+archive/ubuntu/fprint) to get the
  scanner to work, I don't think the official repository version of
  fprint supports my fingerprint reader. I will remove the package and
  see if this changes the situation and will edit/comment once I've done
  that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  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: Thu Oct 13 19:36:47 2016
  InstallationDate: Installed on 2016-06-18 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1633186/+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 1625606] Re: List of available GPS app

2016-10-13 Thread Mite
Sami problemi for M10 tablet

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

Title:
  List of available GPS app

Status in bluez package in Ubuntu:
  New

Bug description:
  Aquarius E5
  OTA-13:
  Removed apps will not deleted on list of available GPS apps.

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

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


[Touch-packages] [Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

2016-10-13 Thread Paul Graydon
I ran into this with iSCSI root.  Installing cloud-init resulted in
problems rebooting.

If I install the ifupdown patch (without cloud-init installed), that
triggers the bug for me.

Spinning up a clean instance, installing cloud-init, letting it run (so
the conditions that cause the bug are triggered), then installing the
ifupdown package also fails to fix the reboot problems.  I've confirmed
this persists after the next boot as well.

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

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

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Xenial:
  Confirmed

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

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

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

  [Impact]

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

  [Test Case]

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

  [Regression potential]

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

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

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


[Touch-packages] [Bug 1631504] Re: loadkeys segfaults with certain arguments in 16.10

2016-10-13 Thread Jason Conti
Noticed that the code causing the crash is only in the Ubuntu package,
specifically debian/patches/loadkeys_ckbcomp.diff, so I refreshed the
patch with the include and made a debdiff.

** Patch added: "loadkeys_fix_implicit_xmalloc.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1631504/+attachment/4760528/+files/loadkeys_fix_implicit_xmalloc.debdiff

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

Title:
  loadkeys segfaults with certain arguments in 16.10

Status in kbd package in Ubuntu:
  New

Bug description:
  This can be reproduced as follows:

  1) Switch to VT 1 (ctrl+alt+f1)
  2) run: loadkeys garbage
  3) loadkeys will segfault

  The problem appears to be with the implicit declaration of xmalloc in 
loadkeys.c. It is resolved if
  #include "xmalloc.h" is added to the top of that file (and in fact all the 
other source files in kbd that reference xmalloc include that file).

  Interestingly xmalloc is resolved without include but the returned
  pointer seems to get truncated. It doesn't do this if the source is
  built with gcc 5.4 in 16.04 so maybe it has something to do with gcc
  6.2 in 16.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: kbd 2.0.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  7 15:27:58 2016
  InstallationDate: Installed on 2016-10-06 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161006)
  SourcePackage: kbd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1631504/+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 1632985] Re: package linux-image-4.4.0-42-generic 4.4.0-42.62 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2016-10-13 Thread Ren
On the first line of this report I meant:
"After a standard update : apt-get update and apt-get dist-upgrade"
Sorry!

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

Title:
  package linux-image-4.4.0-42-generic 4.4.0-42.62 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After a standard update : apt-get install and apt-get distupgrade
  on ubuntu 16.04.1
  The bug report signaled me this issue.

  rdy@rds:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  rdy@rds:~$ 

  rdy@rds:~$ apt-cache policy initramfs-tools
  initramfs-tools:
Installé : 0.122ubuntu8.1
Candidat : 0.122ubuntu8.3
   Table de version :
   0.122ubuntu8.3 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
   *** 0.122ubuntu8.1 100
  100 /var/lib/dpkg/status
   0.122ubuntu8 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  rdy@rds:~$ 

  Expected: the binary initrd should be installed correctly during the
  upgrade.

  Happened: the bug report signaled this error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  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.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rdy2544 F pulseaudio
   /dev/snd/pcmC0D3p:   rdy2544 F...m pulseaudio
   /dev/snd/controlC0:  rdy2544 F pulseaudio
  Date: Thu Oct 13 00:11:30 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=886f9bce-230b-490e-abcf-d04909f6e554
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 305V4A/305V5A/3415VA
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=c8c96891-7107-4ace-96a3-0d76ba7e3d4b ro bootkbd=fr
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-42-generic 4.4.0-42.62 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 09PW.ME13.20121101.SKK
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 305V4A/305V4A
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 09PW
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr09PW.ME13.20121101.SKK:bd11/01/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn305V4A/305V5A/3415VA:pvr09PW:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305V4A/305V4A:rvr09PW:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 305V4A/305V5A/3415VA
  dmi.product.version: 09PW
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1632985/+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 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out

2016-10-13 Thread Christopher
Desc:
 Wifi connection being sporadically lost during period of inactivity. Resume is 
no problem, however.  

 Initial error message: Oct 11 09:21:01 Ariadnex NetworkManager[727]:   
[1476170461.1053]  supiface[0x2327590,wlan0]: connection disconnected 
(reason -4) 
 
 Posted commands not working. Network manager showing connection active, even 
when not.
  
 Present workaround: ping localhost -i 9 -s 28 (60 seconds doesn't work)

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

Title:
  Connect to Hidden Wi-Fi Network, "Connect" grayed out

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  1. Create a static, connection to hidden Wi-Fi connection using 
nm-connection-editor

  2. click nm-applet icon
  click "Connect to Hidden Wi-Fi Network"
  click pre-existing connection
  "Connect" is grayed out

  Work around is using terminal.
  nmcli c up id 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Feb  6 15:58:22 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-06 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.0.55  
metric 600
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH
   Wired connection 1  7c22db8e-2026-413b-86cd-0c796f177dd5  
802-3-ethernet   1454790964  Sat 06 Feb 2016 02:36:04 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/1  no  
--  -- -- 
   jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
802-11-wireless  1454795858  Sat 06 Feb 2016 03:57:38 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes 
wlp2s0  activated  /org/freedesktop/NetworkManager/ActiveConnection/4
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1542733/+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 1632620] Re: No audio from webbrowser-app in 16.10 U8 or U7 session

2016-10-13 Thread Olivier Tilloy
The above rule comes from the audio and microphone policy groups:

  
https://bazaar.launchpad.net/~ubuntu-security/apparmor-easyprof-ubuntu/trunk/view/head:/data/policygroups/ubuntu/1.0/audio#L10
  
https://bazaar.launchpad.net/~ubuntu-security/apparmor-easyprof-ubuntu/trunk/view/head:/data/policygroups/ubuntu/1.0/microphone#L8

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

Title:
  No audio from webbrowser-app in 16.10 U8 or U7 session

Status in Oxide:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Load the browser on 16.10 in either a U8 or U7 session.
  Browse to YouTube
  Play a video
  Notice there is no sound.  Nor does the browser show in the sound menu/panel.

  I've attached the application-legacy-webbrowser-app-.log file which
  shows problems with "unknown pcm devices"

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1632620/+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 1632620] Re: No audio from webbrowser-app in 16.10 U8 or U7 session

2016-10-13 Thread Olivier Tilloy
The following rule in the browser’s apparmor profile is what causes the
audio manager to fail to initialize:

deny /{run,dev}/shm/pulse-shm* w,  # deny unless we have to have
it

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

Title:
  No audio from webbrowser-app in 16.10 U8 or U7 session

Status in Oxide:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Load the browser on 16.10 in either a U8 or U7 session.
  Browse to YouTube
  Play a video
  Notice there is no sound.  Nor does the browser show in the sound menu/panel.

  I've attached the application-legacy-webbrowser-app-.log file which
  shows problems with "unknown pcm devices"

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1632620/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-10-13 Thread Anupam
@Marek that's bug #1612367

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in qtmultimedia-opensource-src package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1632275] Re: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

2016-10-13 Thread Pete Woods
** Changed in: indicator-network (Ubuntu)
   Status: Triaged => In Progress

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => High

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

Title:
  indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Live session on i386 has an issue immediately which reports that
  network-manager indicator crashed

  On the installed version it is impossible to connect to the net via
  wifi

  Will check on amd64 but as far as I can tell it is fine there.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: indicator-network 0.8.0+16.10.20160930.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  CasperVersion: 1.379
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Oct 11 10:17:39 2016
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ExecutableTimestamp: 1475255305
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha i386 (20161008)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ProcCwd: /home/ubuntu
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb779ceba :   mov0x4(%eax),%ebx
   PC (0xb779ceba) ok
   source "0x4(%eax)" (0x03eb) not located in a known VMA region (needed 
readable region)!
   destination "%ebx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-network
  Stacktrace:
   #0  do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 , 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
   n = 
   list = 
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 , 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
   ?? ()
  Title: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.indicator-network.log: indicator-network stop/pre-start, process 5765

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1632275/+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 1632382] Re: indicator-network-secret-agent running automatically on unity7

2016-10-13 Thread Pete Woods
** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  indicator-network-secret-agent running automatically on unity7

Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  see the summary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1632382/+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 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-10-13 Thread scotte
Thanks Eric, we will remove our local workaround.

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in sysvinit source package in Xenial:
  Won't Fix
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the upsteam zfs
  test script suite.

   * This is a upstream commit merge in 0.7.0.

   * A ubuntu package has been tested (including the upstream commit) by
  a user of the community facing this bug, and confirmed it addresses
  the problem (see comment #7).

  [Other Info]

  * The "reading" is redirected to /proc/self/mounts. 
  The writing to /etc/mtab. Some distros still need that. The current hope is 
to replace the writing (and maybe reading) with libmount, in a second phase.

  
   * Upstream commit : 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

   * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=839071

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1607920/+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 1578810] Re: Insensitive (disabled) toolbar icons in GTK3 are not dimmed

2016-10-13 Thread Martin Wimpress
** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => In Progress

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

Title:
  Insensitive (disabled) toolbar icons in GTK3 are not dimmed

Status in remmina:
  New
Status in Ubuntu theme:
  New
Status in Wireshark:
  New
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  Since Ubuntu 16.04, the disabled buttons in Eclipse toolbars look like they 
are still enabled. See attached screenshots.
  This is very easy to reproduce:
  1. Download a recent Eclipse 
(https://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops4/R-4.5.2-201602121500/eclipse-SDK-4.5.2-linux-gtk-x86_64.tar.gz)
  2. Extract and execute the "eclipse" executable
  3. In the toolbar, several icons look enabled even though they are not. For 
example the Save icon (Floppy).

To manage notifications about this bug go to:
https://bugs.launchpad.net/remmina/+bug/1578810/+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 1632272] Re: need writable-path for snappy

2016-10-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: lxc-android-config (Ubuntu)
   Status: New => Confirmed

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

Title:
  need writable-path for snappy

Status in Canonical System Image:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  Confirmed

Bug description:
  Snappy writes to /etc/systemd/system, /snap and /var/lib/snapd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632272/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-10-13 Thread Marek Greško
Not sure whether it is same bug, but today there was no ringing on
incoming call. Just only seen incoming call on a display. BQ E4.5 with
OTA13.

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in qtmultimedia-opensource-src package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-10-13 Thread Eric Desrochers
Hi scotte,

The fix is now released as shown in comment#25 & #26

Eric

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in sysvinit source package in Xenial:
  Won't Fix
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the upsteam zfs
  test script suite.

   * This is a upstream commit merge in 0.7.0.

   * A ubuntu package has been tested (including the upstream commit) by
  a user of the community facing this bug, and confirmed it addresses
  the problem (see comment #7).

  [Other Info]

  * The "reading" is redirected to /proc/self/mounts. 
  The writing to /etc/mtab. Some distros still need that. The current hope is 
to replace the writing (and maybe reading) with libmount, in a second phase.

  
   * Upstream commit : 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

   * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=839071

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

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


[Touch-packages] [Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

2016-10-13 Thread Andres Rodriguez
** Changed in: maas
Milestone: 2.1.0 => 2.1.1

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

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

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Xenial:
  Confirmed

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

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

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

  [Impact]

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

  [Test Case]

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

  [Regression potential]

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

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

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


[Touch-packages] [Bug 1632620] Re: No audio from webbrowser-app in 16.10 U8 or U7 session

2016-10-13 Thread Olivier Tilloy
 oSoMoN, ah, so AudioManagerPulse fails to initialize, and then 
it tries to create AudioManagerAlsa before the unique_ptr instance holding 
AudioManagerPulse goes out of scope
 that makes sense
 that means chromium's fallback is buggy though, as 
AudioManager::Get() will always return nullptr if the pulseaudio path fails
 But, the root cause is confinement related

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

Title:
  No audio from webbrowser-app in 16.10 U8 or U7 session

Status in Oxide:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Load the browser on 16.10 in either a U8 or U7 session.
  Browse to YouTube
  Play a video
  Notice there is no sound.  Nor does the browser show in the sound menu/panel.

  I've attached the application-legacy-webbrowser-app-.log file which
  shows problems with "unknown pcm devices"

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1632620/+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 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-10-13 Thread Launchpad Bug Tracker
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu14

---
zfs-linux (0.6.5.6-0ubuntu14) xenial; urgency=medium

  * Fix zfs services to fail on first boot due to zfs services starting up
before /etc/mtab has a chance to be symlinked to /proc/mounts. (LP: 
#1607920)
(upstream commit 792517389fad5c495a2738b61c2e9c65dedaaa9a)

  * Symlink utilities in /usr/sbin to remove suffix as per policy 10.4 Scripts  
(LP: #1628279)
Users can rely on the new names, but relying on the old names won't break 
before
release upgrade.

 -- Eric Desrochers   Tue, 04 Oct 2016
15:07:52 +0200

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in sysvinit source package in Xenial:
  Won't Fix
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the upsteam zfs
  test script suite.

   * This is a upstream commit merge in 0.7.0.

   * A ubuntu package has been tested (including the upstream commit) by
  a user of the community facing this bug, and confirmed it addresses
  the problem (see comment #7).

  [Other Info]

  * The "reading" is redirected to /proc/self/mounts. 
  The writing to /etc/mtab. Some distros still need that. The current hope is 
to replace the writing (and maybe reading) with libmount, in a second phase.

  
   * Upstream commit : 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

   * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=839071

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1607920/+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 1607920] Update Released

2016-10-13 Thread Brian Murray
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in sysvinit source package in Xenial:
  Won't Fix
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the upsteam zfs
  test script suite.

   * This is a upstream commit merge in 0.7.0.

   * A ubuntu package has been tested (including the upstream commit) by
  a user of the community facing this bug, and confirmed it addresses
  the problem (see comment #7).

  [Other Info]

  * The "reading" is redirected to /proc/self/mounts. 
  The writing to /etc/mtab. Some distros still need that. The current hope is 
to replace the writing (and maybe reading) with libmount, in a second phase.

  
   * Upstream commit : 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

   * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=839071

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1607920/+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 1623003] Re: udev-generated /dev/disk/by-path names broken for virtio disks

2016-10-13 Thread Dimitri John Ledkov
Hi,
this bug report is marked invalid in Ubuntu, and severity-high has no affect.

Please report this issue upstream at https://github.com/systemd/systemd
as it affects all Linux on z distributions (or will when they upgrade to
the relevant systemd version)..

Do you have a url to a github issue you have opened?

Regards,

Dimitri.

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

Title:
  udev-generated /dev/disk/by-path names broken for virtio disks

Status in systemd:
  Unknown
Status in Ubuntu on IBM z Systems:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The udev-generated /dev/disk/by-path names for virtio disks are broken on z 
Systems as they have the format virtio-pci-h.h.[-partn], where h.h. is 
the CCW devno of the virtio device representing the whole disk. Historically, 
the standard CCW naming was applied, which was ccw-h.h.[-partn]
   
  ---uname output---
  Linux ubuntu 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = 2964-703 running KVM for IBM z Systems 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Install Ubuntu LTS 16.04.1 on KVM for IBM z Systems 1.1.1
  2. Issue ls -l /dev/disk/by-path
   
  Userspace tool common name: udev 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: udev

  Userspace tool obtained from project website:  na

  There are basically two problems with this:
  1. The naming is technically incorrect, since the virtio devices on z are no 
PCI devices but CCW devices
  2. Then naming based on virtio- is backwards incompatible. This may seem not 
to be an issue for Xenial but customers may be confused if they have been 
running Linux on KVM for IBM z before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1623003/+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 1633098] Re: override of APT_LISTCHANGES_FRONTEND can/should be removed

2016-10-13 Thread Brian Murray
** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  override of APT_LISTCHANGES_FRONTEND can/should be removed

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  unattended-upgrades overrides the setting of APT_LISTCHANGES_FRONTEND.
  per the comments, this was done at a time when apt-listchanges would
  "always send a mail if there is a mail address set in the config
  regardless of the frontend used."  this is no longer the case and this
  (now unnecessary) local override of APT_LISTCHANGES_FRONTEND can cause
  confusion when apt-listchanges appears to ignore its configured
  settings.

  What I expected to happen:

  i expected apt-listchanges to conform to its configuration.  setting
  the "none" frontend in /etc/apt/listchanges.conf should ensure it
  "Does nothing" as per the manpage.

  What happened instead:

  unattended-upgrades does not respect the frontend setting, essentially
  now replicating the bad behavior this snippet was originally meant to
  workaround (i.e., mail is currently sent when email_address is set but
  frontend=none).  with the attached patch the frontend specified in
  listchanges.conf is no longer unnecessarily overridden.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  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.1
  Architecture: amd64
  Date: Thu Oct 13 07:07:44 2016
  JournalErrors:
   -- Logs begin at Tue 2016-10-11 08:02:03 PDT, end at Thu 2016-10-13 07:06:49 
PDT. --
   Oct 11 08:13:30 hostname systemd-tmpfiles[10524]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
   Oct 12 08:13:50 hostname systemd-tmpfiles[25099]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  PackageArchitecture: all
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1633098/+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 1631288] Re: XV video screen always on top

2016-10-13 Thread Timo Aaltonen
feel free to uninstall xserver-xorg-video-intel

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

Title:
  XV video screen always on top

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  When playing a video with vlc, gstreamer(xvimagesink), the video stays on top 
of every X window.
  In VLC this bug can be bypassed disabling overlay video. 
  In Gstreamer using ximagsink is ok too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  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: Fri Oct  7 09:45:31 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Toshiba America Info Systems Skylake Integrated Graphics 
[1179:001d]
 Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:001d]
  InstallationDate: Installed on 2016-10-03 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: TOSHIBA TECRA Z50-C
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=f4f5014d-ef0f-49c7-9842-c164aa8b4bbc ro plymouth:debug splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.70
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA Z50-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.70:bd04/15/2016:svnTOSHIBA:pnTECRAZ50-C:pvrPT577E-01100GCE:rvnTOSHIBA:rnTECRAZ50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA Z50-C
  dmi.product.version: PT577E-01100GCE
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Oct  6 17:44:07 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1237 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288/+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 1628306] Re: network booting fails for iscsi root if no ip is set

2016-10-13 Thread scotte
Sorry for not linking the bug here initially, that's my fault and I
apologize...

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

Title:
  network booting fails for iscsi root if no ip is set

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

Bug description:
  [Impact]
  Remote-root installs (eg. / over iscsi and similar) where the configuration 
is simple, and no extra parameters are included on the kernel command-line (as 
opposed to MaaS specifying everything).

  [Test case]
  1) do an installation with /boot on a local disk and / and swap over a remote 
LUN (iSCSI is simple to do).
  2) Update to initramfs-tools with isc-dhcp support.

  [Regression potential]
  This is in itself a fix for a regression found in initramfs-tools 
(0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a 
remote root filesystem would constitue a regression.

  [Regressions]
   bug 1631474: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp 
boot option 

  --

  I did a new install with /boot on /dev/sda, and everything else (/ and
  swap) on an iSCSI LUN.

  Booting this with initramfs-tools using ipconfig works without issues.

  Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or
  0.122ubuntu8.2 on xenial) fails because no interface is specified.

  This appears to be because ipconfig interprets "" as meaning to try
  every interface until one works (or all fail), whereas calling
  dhclient without an interface name simply returns a failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1628306/+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 1633098] Re: override of APT_LISTCHANGES_FRONTEND can/should be removed

2016-10-13 Thread Ubuntu Foundations Team Bug Bot
The attachment "remove the APT_LISTCHANGES_FRONTEND override" seems to
be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  override of APT_LISTCHANGES_FRONTEND can/should be removed

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  unattended-upgrades overrides the setting of APT_LISTCHANGES_FRONTEND.
  per the comments, this was done at a time when apt-listchanges would
  "always send a mail if there is a mail address set in the config
  regardless of the frontend used."  this is no longer the case and this
  (now unnecessary) local override of APT_LISTCHANGES_FRONTEND can cause
  confusion when apt-listchanges appears to ignore its configured
  settings.

  What I expected to happen:

  i expected apt-listchanges to conform to its configuration.  setting
  the "none" frontend in /etc/apt/listchanges.conf should ensure it
  "Does nothing" as per the manpage.

  What happened instead:

  unattended-upgrades does not respect the frontend setting, essentially
  now replicating the bad behavior this snippet was originally meant to
  workaround (i.e., mail is currently sent when email_address is set but
  frontend=none).  with the attached patch the frontend specified in
  listchanges.conf is no longer unnecessarily overridden.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  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.1
  Architecture: amd64
  Date: Thu Oct 13 07:07:44 2016
  JournalErrors:
   -- Logs begin at Tue 2016-10-11 08:02:03 PDT, end at Thu 2016-10-13 07:06:49 
PDT. --
   Oct 11 08:13:30 hostname systemd-tmpfiles[10524]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
   Oct 12 08:13:50 hostname systemd-tmpfiles[25099]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  PackageArchitecture: all
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1633098/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

2016-10-13 Thread LaMont Jones
0.122ubuntu8.4 still fails to get an IP when the switchport is not
'portfast' (and the switch therefore passes no traffic for 60 seconds
after link-up.)

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in z-series:
  Fix Committed

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
     - The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken
     -
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  This bug is a regression of changes made under bug 1628306.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

2016-10-13 Thread scotte
smoser - I think you make a really good point. A regression in an LTS
distribution that results in a working configuration to no longer work
is fairly serious - as is introducing behavioral changes in an LTS.
While I'm generally in favor of fix-forward, it's not always the right
approach. I acknowledge changes are hard, and there's not always a clear
or right answer, especially given the vast diversity in exactly what
people do with their systems and how they configure them. This is a
larger discussion around change management, and my opinions here are a
bit off-topic as it relates specifically to this bug, so...

I retested with xenial-proposed and the system rebooted fine for me.

initramfs-tools:
  Installed: 0.122ubuntu8.4
  Candidate: 0.122ubuntu8.4
  Version table:
 *** 0.122ubuntu8.4 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages

ii  initramfs-tools  0.122ubuntu8.4  all
  generic modular initramfs generator (automation)
ii  initramfs-tools-bin  0.122ubuntu8.4  amd64  
  binaries used by initramfs-tools
ii  initramfs-tools-core 0.122ubuntu8.4  all
  generic modular initramfs generator (core tools)

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in z-series:
  Fix Committed

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
     - The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken
     -
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  This bug is a regression of changes made under bug 1628306.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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


  1   2   3   >