date:20161110

** Branch linked: lp:~mardy/account-plugins/nextcloud-1639175

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

Title:
  Please add an "account-plugin-nextcloud" package

Status in webapps-sprint:
  Confirmed
Status in account-plugins package in Ubuntu:
  Confirmed

Bug description:
  Please add an account-plugin-nextcloud package.

  For now, this could essentially be a copy of the ownCloud provider
  code with different branding.  Having both providers side-by-side has
  a few benefits:

  1. we can pick which one to install to get desired branding

  2. if the two projects diverge API wise, we can support each
  independently rather than targeting a common subset.

  The obvious downside though is that we'll have some duplication while
  they are ABI compatible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1639175/+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 1638565] Re: HP Envy 34c resolution maxes out at 1920x1200

2016-11-10 Thread Luis Arias

And now on 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux:

/sys/class/drm/card0-eDP-1/modes:3200x1800
/sys/class/drm/card0-HDMI-A-1/modes:1920x1200
/sys/class/drm/card0-HDMI-A-1/modes:1920x1080
/sys/class/drm/card0-HDMI-A-1/modes:1920x1080
/sys/class/drm/card0-HDMI-A-1/modes:1920x1080
/sys/class/drm/card0-HDMI-A-1/modes:1920x1080i
/sys/class/drm/card0-HDMI-A-1/modes:1920x1080i
/sys/class/drm/card0-HDMI-A-1/modes:1920x1080
/sys/class/drm/card0-HDMI-A-1/modes:1920x1080i
/sys/class/drm/card0-HDMI-A-1/modes:1920x1080
/sys/class/drm/card0-HDMI-A-1/modes:1920x1080
/sys/class/drm/card0-HDMI-A-1/modes:1600x1200
/sys/class/drm/card0-HDMI-A-1/modes:1680x1050
/sys/class/drm/card0-HDMI-A-1/modes:1600x900
/sys/class/drm/card0-HDMI-A-1/modes:1280x1024
/sys/class/drm/card0-HDMI-A-1/modes:1440x900
/sys/class/drm/card0-HDMI-A-1/modes:1280x720
/sys/class/drm/card0-HDMI-A-1/modes:1280x720
/sys/class/drm/card0-HDMI-A-1/modes:1280x720
/sys/class/drm/card0-HDMI-A-1/modes:1024x768
/sys/class/drm/card0-HDMI-A-1/modes:800x600
/sys/class/drm/card0-HDMI-A-1/modes:720x576
/sys/class/drm/card0-HDMI-A-1/modes:720x576i
/sys/class/drm/card0-HDMI-A-1/modes:720x480
/sys/class/drm/card0-HDMI-A-1/modes:720x480
/sys/class/drm/card0-HDMI-A-1/modes:720x480i
/sys/class/drm/card0-HDMI-A-1/modes:720x480i
/sys/class/drm/card0-HDMI-A-1/modes:640x480
/sys/class/drm/card0-HDMI-A-1/modes:640x480

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

Title:
  HP Envy 34c resolution maxes out at 1920x1200

Status in xorg package in Ubuntu:
  New

Bug description:
  Using get-edid, the best resolution is "Mode 0" below, but this
  doesn't show up in the Display systems settings panel.

  This is read-edid version 3.0.2. Prepare for some fun.
  Attempting to use i2c interface
  No EDID on bus 0
  No EDID on bus 1
  No EDID on bus 2
  No EDID on bus 3
  No EDID on bus 5
  No EDID on bus 7
  No EDID on bus 8
  No EDID on bus 9
  No EDID on bus 10
  2 potential busses found: 4 6
  Will scan through until the first EDID is found.
  Pass a bus number as an option to this program to go only for that one.
  256-byte EDID successfully retrieved from i2c bus 4
  Looks like i2c was successful. Have a good day.
  Checksum Correct

  Section "Monitor"
Identifier "HP ENVY 34c"
ModelName "HP ENVY 34c"
VendorName "HWP"
# Monitor Manufactured week 22 of 2015
# EDID version 1.3
# Digital Display
DisplaySize 800 330
Gamma 2.20
Option "DPMS" "true"
Horizsync 27-90
VertRefresh 24-60
# Maximum pixel clock is 250MHz
#Not giving standard mode: 1920x1080, 60Hz
#Not giving standard mode: 1600x900, 60Hz
#Not giving standard mode: 1280x720, 60Hz
#Not giving standard mode: 1920x1200, 60Hz
#Not giving standard mode: 1680x1050, 60Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1600x1200, 60Hz
#Not giving standard mode: 1280x1024, 60Hz

#Extension block found. Parsing...
Modeline"Mode 17" 241.50 2560 2608 2640 2720 1440 1443 1448 
1481 +hsync -vsync 
Modeline"Mode 0" 196.25 3440 3600 3952 4464 1440 1443 1453 1468 
+hsync -vsync 
Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 3" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 
+hsync +vsync
Modeline"Mode 4" 74.250 1280 1390 1420 1650 720 725 730 750 
+hsync +vsync
Modeline"Mode 5" 74.250 1280 1720 1760 1980 720 725 730 750 
+hsync +vsync
Modeline"Mode 6" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 9" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 10" 25.200 640 656 752 800 480 490 492 525 -hsync 
-vsync
Modeline"Mode 11" 74.250 1920 2008 2052 2200 1080 1082 1087 
1125 +hsync +vsync interlace
Modeline"Mode 12" 74.250 1920 2448 2492 2640 1080 1082 1089 
1125 +hsync +vsync interlace
Modeline"Mode 13" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 14" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 15" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 16" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 18" 198.00 2560 2808 2852 3000 1080 1084 1089 
1

[Touch-packages] [Bug 1610206] Re: "Web authentication for Google" WebView appears on login

This bug was fixed in the package signon-ui -
0.17+17.04.20161109-0ubuntu1

---
signon-ui (0.17+17.04.20161109-0ubuntu1) zesty; urgency=medium

  * debian/control:
- Remove dependency on libgstreamer-plugins-base0.10-dev
  * Unify QML and QWidget code paths (LP: #1610206)

 -- Alberto Mardegan   Wed, 09 Nov 2016
14:07:25 +

** Changed in: signon-ui (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  "Web authentication for Google" WebView appears on login

Status in webapps-sprint:
  Fix Released
Status in signon-ui package in Ubuntu:
  Fix Released

Bug description:
  Starting today, when I log in a "Web authentication for Google" web
  view (screenshot attached).

  It's probably because I have to re-authenticate to Google - but the
  web view doesn't tell me what it's asking for, and it is a bit strange
  to just see a dialog on login.

  mardy thinks that it's somehow failing to show the usual notification,
  and falling back to the path which shows the dialog.

  In the attached syslog, pid 7936 is my dbus-daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: signon-ui 0.17+16.04.20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  5 12:14:25 2016
  InstallationDate: Installed on 2012-10-07 (1397 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: signon-ui
  UpgradeStatus: Upgraded to yakkety on 2013-05-07 (1186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1610206/+subscriptions

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

2016-11-10 Thread Dave H

Hi Michi,

OK thanks for checking and I agree with your explanation as you can see
similar problems with other scopes. I guess the Today scope looks worse
(and more annoying) as its the main scope you see each time the phone is
active, others are not always checked or used. Also the scopes with
multiple feeds are more effected. This problem wouldn’t be so bad if
they cleared them selves once a good  wifi signal returns, but as it is
now you sometimes have to restart the phone. If this could be resolved I
think it would make Ubuntu Touch look more stable for normal every day
use, so should be given a high priority for OTA-14 / 15.

Note, have attached this mornings Today scope crash. In this case the
wifi has been active with good signal all night. Looking at the settings
in my 4G EE home broadband router, the DHCP lease time is set to 86400s
(1 day) so the IP number could have changed overnight, note sure if this
could also be related to general wifi issues.

Thanks for your continued support and hard work,

Best regards

Dave H

** Attachment added: "Today scope - morning result - after refresh still no 
good."
   
https://bugs.launchpad.net/today-scope/+bug/1637841/+attachment/4775237/+files/screenshot20161110_083755884.png

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

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

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

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

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

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1610206] Re: "Web authentication for Google" WebView appears on login

2016-11-10 Thread Alberto Mardegan

** Changed in: webapps-sprint
   Status: In Progress => Fix Released

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

Title:
  "Web authentication for Google" WebView appears on login

Status in webapps-sprint:
  Fix Released
Status in signon-ui package in Ubuntu:
  Fix Released

Bug description:
  Starting today, when I log in a "Web authentication for Google" web
  view (screenshot attached).

  It's probably because I have to re-authenticate to Google - but the
  web view doesn't tell me what it's asking for, and it is a bit strange
  to just see a dialog on login.

  mardy thinks that it's somehow failing to show the usual notification,
  and falling back to the path which shows the dialog.

  In the attached syslog, pid 7936 is my dbus-daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: signon-ui 0.17+16.04.20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  5 12:14:25 2016
  InstallationDate: Installed on 2012-10-07 (1397 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: signon-ui
  UpgradeStatus: Upgraded to yakkety on 2013-05-07 (1186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1610206/+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 1640734] [NEW] package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other

2016-11-10 Thread Max

Public bug reported:

Wanted to install scanner

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libperl5.22 5.22.2-3
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Thu Nov 10 10:56:59 2016
DuplicateSignature:
 package:libperl5.22:5.22.2-3
 Unpacking libperl5.22:i386 (5.22.2-3) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-Il1Esk/23-libperl5.22_5.22.2-3_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', 
which is different from other instances of package libperl5.22:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
InstallationDate: Installed on 2016-07-29 (103 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: perl
Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (25 days ago)

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


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

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

Title:
  package libperl5.22 5.22.2-3 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Wanted to install scanner

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libperl5.22 5.22.2-3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Nov 10 10:56:59 2016
  DuplicateSignature:
   package:libperl5.22:5.22.2-3
   Unpacking libperl5.22:i386 (5.22.2-3) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Il1Esk/23-libperl5.22_5.22.2-3_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-07-29 (103 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: perl
  Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1640734/+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 1640736] [NEW] dell dock system is freezing while docking

2016-11-10 Thread mukesh kumar gupta

Public bug reported:

I Can't find any solution to solve this headache. :(

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.21
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: Thu Nov 10 15:30:36 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: virtualbox, 4.3.36, 4.2.0-42-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Device [1028:06dc]
InstallationDate: Installed on 2016-11-09 (1 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Dell Inc. Latitude E7470
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-42-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.3
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7470
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Nov 10 15:28:33 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1168 
 vendor LGD
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

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

Title:
  dell dock system is freezing while docking

Status in xorg package in Ubuntu:
  New

Bug description:
  I Can't find any solution to solve this headache. :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  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: Thu Nov 10 15:30:36 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.36, 4.2.0-42-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Device [1028:06dc]
  InstallationDate: Installed on 2016-11-09 (1 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-42-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.3
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:

[Touch-packages] [Bug 1639000] Re: New upstream release 0.4.13

2016-11-10 Thread Iain Lane

Now this is done, I'll look at sponsoring libproxy to unstable and then
hopefully syncing it - I think if the mozjs thing goes to Universe then
it should be ok, but I'll check to be sure.

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

Title:
  New upstream release 0.4.13

Status in libproxy package in Ubuntu:
  Fix Released

Bug description:
  New in Version 0.4.13
  ==
  * Allow linking webkit pacrunner against javascriptcore-4.0
(webkit2).
  * Allow to disable building of the KDE module (-DWITH_KDE=ON/OFF).
  * Fix compilation errors with CLang on MacOSX.
  * bindings: perl: Add an option to explicitly link against libperl.so
Some distributions want to do it, other prefer not to, the library
is anyway in context of perl.
  * config_kde: Add a basic cache and invalidation: performance improvement
for the KDE module.

  New in version 0.4.12
  ==
  * Move development to github.com/libproxy/libproxy
  * Fix fd leak in get_pac (Bug #185)
  * Detect running MATE session (Bug #186, Part1).
  * Fix linking of perl bindings to pthread (Bug #182)
  * Correctly detect spidermonky (mozjs185) (Bug #188)
  * Stop pxgsettings from segfaulting on exit (Bug #192)
  * Fix test #10 (Bug #189)
  * Fix build on Mac OS X (Bug #183)
  * Add a generic KDE Config module (fix crashes of Qt5 based
  apps) (issue#4)

  We should get this in zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1639000/+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 1639977] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file

Hello errors.ubuntu.com, or anyone else affected,

Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.90ubuntu0.2 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 on 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!

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-
  upgrade@1468:main:write_stamp_file

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Yakkety:
  Fix Committed

Bug description:
  Test Case
  -
  1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 
and Unattended-Upgrade is 1
  2) sudo apt-get update
  3) sudo rm -fr /var/lib/apt/periodic
  4) sudo /usr/bin/unattended-upgrade
  5) observe the following Traceback

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1468, in 
  main(options)
    File "/usr/bin/unattended-upgrade", line 1419, in main
  write_stamp_file()
    File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file
  with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"):
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/lib/apt/periodic/unattended-upgrades-stamp'

  With the version of the package from -proposed you'll receive no such
  Traceback.

  Regression Potential
  
  This patch just ends up creating a directory if it does not exist.  Potential 
regressions would be a result of the patch being typo'ed e.g. typo'ing 
os.path.exits instead of os.path.exists and the code failing when a statedir 
does exist.  So read the patch carefully!

  Original description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.90ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1639977/+subscriptions

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

[Touch-packages] [Bug 1633828] Re: Mounting /boot/efi fails always after updating to 16.10

2016-11-10 Thread Prasanna Kumar

I am able to mount efi partition manually.

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

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

Status in util-linux package in Ubuntu:
  Incomplete

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1633828/+subscriptions

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

[Touch-packages] [Bug 1590321] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:get_dpkg_log_content

Hello errors.ubuntu.com, or anyone else affected,

Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.90ubuntu0.2 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 on 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!

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-
  upgrade@1468:main:get_dpkg_log_content

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Yakkety:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  Fix Released

Bug description:
  Test Case
  -
  1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 
and Unattended-Upgrade is 1
  2) sudo apt-get update
  3) sudo /usr/bin/unattended-upgrades (to update the system)
  4) sudo /usr/bin/unattended-upgrades (a second time for some reason)
  5) sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  6) sudo /usr/bin/unattended-upgrades

  Observe the following crash:

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1468, in 
  main(options)
    File "/usr/bin/unattended-upgrade", line 1406, in main
  log_content = get_dpkg_log_content(logfile_dpkg, install_start_time)
    File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content
  with io.open(logfile_dpkg, encoding='utf-8') as fp:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'

  With the version of the package from -proposed you won't receive the
  crash in step 6 and /var/log/unattended-upgrades/unattended-upgrades-
  dpkg.log will exist.

  Regression Potential
  
  This patch just ends up creating a file if it does not exist. Potential 
regressions would be a result of the patch being typo'ed e.g. typo'ing 
os.path.exits instead of os.path.exists and the code failing when a logfile 
does exist. So read the patch carefully!

  
  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with version 0.90, 
the problem page at 
https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a 
contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1590321/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

Hello errors.ubuntu.com, or anyone else affected,

Accepted ido into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ido/13.10.0+16.04.20161028-0ubuntu1
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 on 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!

** Changed in: ido (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

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

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 518890] Re: NM | Edit Connections | Wired | Edit | IPv6 Settings | Method | "Shared to other computers" is greyed out

2016-11-10 Thread Bug Watch Updater

** Changed in: network-manager
   Status: Confirmed => Fix Released

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

Title:
  NM | Edit Connections | Wired | Edit | IPv6 Settings | Method |
  "Shared to other computers" is greyed out

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: network-manager

  Ipv4 shares are offered, if switching to ipv6 the choice is grayed

  ProblemType: Bug
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Mon Feb  8 17:11:46 2010
  DistroRelease: Ubuntu 10.04
  EcryptfsInUse: Yes
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  IpRoute:
   192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.102  
metric 2 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   default via 192.168.2.1 dev wlan0  proto static
  Keyfiles: Error: [Errno 2] No such file or directory
  Package: network-manager 0.8~rc2-0ubuntu1
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
  SourcePackage: network-manager
  Uname: Linux 2.6.32-12-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/518890/+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 1639853] Re: Unity8 crash while locking/unlocking with HDMI plugged

2016-11-10 Thread Victor gonzalez

With today's image(79) I wasn't able to make it crash,but got the black
screen once when plugging/unplugging hdmi with the device locked.
Unfortunately, the device can't boot completely after this. The splash
screen appears and then it turns black, is not even displaying the
ubuntu boot image. I'll try again later

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

Title:
  Unity8 crash while locking/unlocking with HDMI plugged

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Environment:

  current build number: 76
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-11-07 08:03:44
  version version: 76
  version ubuntu: 20161105
  version device: 20161014.0
  version custom: 20161105

  Steps to reproduce:

  1º Connect hdmi 
  2º Lock/unlock device several times

  Current result: locking/unlocking device causes greeter to misbehave
  and finally the ubuntu boot logo appears. Attached some logs and crash
  files, hope it helps

  Expected result: unity8 should not crash

  Add info: time stamp 16:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639853/+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 1640776] [NEW] Mouse cursor changes to the "window resize" mode when it should not

2016-11-10 Thread Albert Astals Cid

Public bug reported:

when it should not = when there's a launcher quicklist open

How to reproduce: 
 * Put a window close enough to the launcher
 * open the launcher
 * Right click on a launcher icon
 * Move the window so that it's both above the launcher quicklist and in a 
window border
 * See how the mouse cursor changes to "resizing mode"

Actually i guess it should not even matter if you're over the quicklist
or not, i guess that simply the cursor should never change to resizing
mode when there's a quicklist open?

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

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

Title:
  Mouse cursor changes to the "window resize" mode when it should not

Status in unity8 package in Ubuntu:
  New

Bug description:
  when it should not = when there's a launcher quicklist open

  How to reproduce: 
   * Put a window close enough to the launcher
   * open the launcher
   * Right click on a launcher icon
   * Move the window so that it's both above the launcher quicklist and in a 
window border
   * See how the mouse cursor changes to "resizing mode"

  Actually i guess it should not even matter if you're over the
  quicklist or not, i guess that simply the cursor should never change
  to resizing mode when there's a quicklist open?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1640776/+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 1640777] [NEW] problem with regular expression

2016-11-10 Thread Glauber

Public bug reported:

I have a personal application that verify a xml file using a xsd file and I 
found a bug in the regular expression check in libxml2 version 2.9.3, but this 
bug was fixed in version 2.9.4 in the following commit 
https://git.gnome.org/browse/libxml2/commit/?id=34b350048d1ee97c4f42dd6729a77b3f36753b3a
 and I would like do update the repository to this new version.
I'm sending attached an example in C that shows the error, to compile just: gcc 
-I/usr/include/libxml2 main.c -lxml2
thank you!

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

** Attachment added: "this is a example of the error"
   https://bugs.launchpad.net/bugs/1640777/+attachment/4775298/+files/main.c

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

Title:
  problem with regular expression

Status in libxml2 package in Ubuntu:
  New

Bug description:
  I have a personal application that verify a xml file using a xsd file and I 
found a bug in the regular expression check in libxml2 version 2.9.3, but this 
bug was fixed in version 2.9.4 in the following commit 
https://git.gnome.org/browse/libxml2/commit/?id=34b350048d1ee97c4f42dd6729a77b3f36753b3a
 and I would like do update the repository to this new version.
  I'm sending attached an example in C that shows the error, to compile just: 
gcc -I/usr/include/libxml2 main.c -lxml2
  thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1640777/+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 1636905] Re: Sound card not recognized on Dell Vostro 5568

I have now done some further research on this. First, I tried to reset
Windows 10 once again. After finished the reset and having rebooted
Windows 10 once more after that. The sound started to work in Windows 10
again. But I also discover something new: If I plugged in the headphones
in Windows 10, the sound stopped working in Windows 10 also. If I
clicked on the sound icon in the Windows taskbar, Windows would try to
fix the sound problem, and asked me to reboot to implement the proposed
fix. Then sound started to work again after rebooting ( but only from
the speakers ). If I plugged in the headphones, it would work well until
I unplugged them. After that the sound stopped working again.

Also note: In Windows 10, there was no popup dialog when I plugged in my
headphones the first time (In Ubuntu I get the annoying popup dialog
asking what device I plugged in). So this might be an indication that
the popup dialog is really not necessary in Ubuntu?

Anyway, the next thing I did: After having ensured the sound was working
from Windows ( after Windows had fixed the sound problem, and I had
rebooted windows to implement the fix ) was to boot into Ubuntu. Now the
sound worked from Ubuntu 16.04 also ( as expected, since I had not
plugged in any headphones yet). I now tested that the speakers produced
sound in Ubuntu and then opened the terminal window and ran the
commands:

$ ls /proc/asound/
card0  cards  devices  hwdep  modules  oss  PCH  pcm  seq  timers  version

$ ls /proc/asound/card0
codec#0  codec#2  eld#2.0  eld#2.1  eld#2.2  id  pcm0c  pcm0p  pcm3p  pcm7p  
pcm8p

$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

$ lspci -v | grep Audio
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)


Then, opened System Settings->Sound, and confirmed that there was no "Dummy 
output" in the Output tab. Instead, it now showed "Speakers: Built-in Audio" 
instead.

I then plugged in the headphones, and got the popup dialog "Unknown
audio device" and I chose headphones and confirmed that sound was
working from the headphones. Then I checked System Settings->Sound again
and confirmed that a new item "Headphones: Built-in Audio" was shown in
the Output tab.

I then unplugged and replugged the headphones five times, every time it
worked fine (except for the irritating popup window appearing each time
I plugged in the headphones).

(The next thing to try now is to reboot Ubuntu once more. I will
continue this comment after having rebooted)

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

Title:
  Sound card not recognized on  Dell Vostro 5568

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just reinstalled a fresh Ubuntu 16.10 on my Dell Vostro 5568 laptop.

  The audio controller on the laptop is a Realtek ALC3246 with Waves
  MaxxAudio Pro. The external interface connector is a microphone
  in/stereo headphones/external speakers connector.

  When I select "System Settings->Sound" the output device in the dialog
  window shows as "Dummy Output" and when I press the "Test Sound"
  button no sound is heard from either front left or front right speaker
  ( I have ensured sound is not muted ).

  Note: Before reinstalling, I asked a question on askubuntu,com:

  http://askubuntu.com/q/841759/156688

  So reinstallation of Ubuntu 16.10 did not help on my sound problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+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 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

This bug was fixed in the package qtmultimedia-opensource-src -
5.6.1-2ubuntu3~1

---
qtmultimedia-opensource-src (5.6.1-2ubuntu3~1) zesty; urgency=medium

  [ Devid Antonio Filoni ]
  * Add opusenc support needed by Telegram app (LP: #1630399)

 -- Alfonso Sanchez-Beato (email Canonical)   Fri, 04 Nov 2016 12:42:19 +0100

** Changed in: qtmultimedia-opensource-src (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

Status in Canonical System Image:
  In Progress
Status in gst-plugins-bad0.10 package in Ubuntu:
  In Progress
Status in qtmultimedia-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Hi, as described in QTBUG-50567 [1], qtmultimedia doesn't support opus
  audio codec so for example we cannot record Telegram voice messages (
  bug #1460464 and bug #1375179 ).

  I patched qtmultimedia adding the support for audio/x-opus codec
  through opusdec encoder in qtmultimedia, then I found qtmultimedia
  5.4.1 (shipped with Ubuntu Phone vivid) is built against gstreamer0.10
  and, as gstreamer0.10-plugins-bad packages is not installed by
  default, opusdec encoder is not available.

  I'm working on this bug, I created it to track the progress, in order
  to add opus support I have to:

  1 - create a new gstreamer0.10-opus package containing only the
  opusdec plugin: I don't know whether I have to create a new source
  package containing opusdec sources or only a new .deb package
  (generated from gst-plugins-bad0.10 sources). I'm working on the
  latter as gst-plugins-bad0.10 package requires work in any ways.

  2 - properly patch qtmultimedia source, I'm attaching a 
working-but-needs-cleanup patch. I think some opus declarations in the attached 
patch can be avoided, but I haven't had time to work on it so I'm attaching the 
patch I tested (requires gstreamer0.10-plugins-bad).
  I don't know if qtmultimedia xenial/yakkety versions requires the patch too, 
I haven't checked them yet.

  [1] https://bugreports.qt.io/browse/QTBUG-50567

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630399/+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 1640326] Re: FTBFS on zesty

2016-11-10 Thread Michi Henning

Almost certainly not related. The test that triggers this is far away
from the core dump. Still worth following up on though.

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/taglib/+bug/1640326/+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 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

2016-11-10 Thread Mauricio Faria de Oliveira

Hi @paelzer,

> I meant a Debian bug against base-passwd to begin with not a libvirt bug.
> I think the Mail you have written is a good start, yet IMHO a related bug
> can't hurt t track and make them more aware.

Ah, ok.  Yes, you're right.  That is BTS #843881 [1].

> Yes it is primarily @cjwatson in both cases, but he is great and
> usually pretty responsive - so no "help" needed on that.

Absolutely. I know Colin's work and interacted w/ him a few times; that
"help" is not what I meant. :)

That was just in case you were also / could be involved in some part of
the process before libvirt; I guess I should have asked 'Can you'
instead of 'Could you'; but either way, I understand that's still vague.

So, alright; i'll keep watching the Debian bug, and ping him if that
takes a bit longer.

Thank you.

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

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

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in base-passwd package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

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

  Sorry about the inconvenience.

  <...>

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1637601/+subscriptions

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

[Touch-packages] [Bug 1628790] Re: Changing the user settings to autologin on Lubuntu 16.04 causes LightDM to get stuck in a login loop

2016-11-10 Thread cadet willy

i think it's a bug with graphic driver nvidia/ati..., i had this problem after 
a security update of this driver. 
i removed this driver, reboot my pc and i could login. 
after that i installed my graphic driver again

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

Title:
  Changing the user settings to autologin on Lubuntu 16.04 causes
  LightDM to get stuck in a login loop

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  After setting my account to login automatically through the user and
  groups setting in Lubuntu. After the computer reboots it gets stuck in
  a loop on the login screen. Logging in will just send you back to the
  same screen.

  The only way I could fix the issue was to press CRTL + ALT + F1, logging in 
through the CLI and typing:
  "sudo mv .Xauthority .Xauthority.bak"
  and then once I was back to the login screen I was able to login and turn the 
setting off. 

  I did check to see weather that was what caused it, by restarting the
  computer without turning off the auto-login. However the same issue
  happened and only turning off auto-login would stop the login loop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1628790/+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 1636905] Re: Sound card not recognized on Dell Vostro 5568

Ok I rebooted Ubuntu with headphones plugged in. I went to System
Settings->Sound and confirmed that everything looked fine. However, when
I tried to play sound from youtube in Google Chrome there was no sound.
I rechecked that the sound was not muted, and that 'aplay -l' showed
correct output. I then unplugged the headphones, and sound started to
work ( from the speakers ). Then I replugged the headphones, and I got
the popup dialog, and then sound started to work from the headphones
also. Everything looking fine so far. I then tried to unplug and replug
the headphones a few times. Working fine. I will now try to reboot
Ubuntu with headphones unplugged.

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

Title:
  Sound card not recognized on  Dell Vostro 5568

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just reinstalled a fresh Ubuntu 16.10 on my Dell Vostro 5568 laptop.

  The audio controller on the laptop is a Realtek ALC3246 with Waves
  MaxxAudio Pro. The external interface connector is a microphone
  in/stereo headphones/external speakers connector.

  When I select "System Settings->Sound" the output device in the dialog
  window shows as "Dummy Output" and when I press the "Test Sound"
  button no sound is heard from either front left or front right speaker
  ( I have ensured sound is not muted ).

  Note: Before reinstalling, I asked a question on askubuntu,com:

  http://askubuntu.com/q/841759/156688

  So reinstallation of Ubuntu 16.10 did not help on my sound problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+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 1639208] Re: The app store button is hardcoded to the Click Store scope

2016-11-10 Thread Marcus Tomlinson

** Changed in: unity8 (Ubuntu)
 Assignee: Marcus Tomlinson (marcustomlinson) => (unassigned)

** Branch unlinked: lp:~marcustomlinson/unity8/new-store

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

Title:
  The app store button is hardcoded to the Click Store scope

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Clicking the app store icon in the Manage Dash view should activate
  whichever store is default on the system. E.g. Click Store scope on V,
  Snappy Store scope on X, and the Snappy Store app on Y+.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1639208/+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 483803] Re: Spelling error in rdisc.c error message

2016-11-10 Thread Bug Watch Updater

** Changed in: iputils (Debian)
   Status: New => Fix Released

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

Title:
  Spelling error in rdisc.c error message

Status in iputils package in Ubuntu:
  Confirmed
Status in iputils package in Debian:
  Fix Released

Bug description:
  Spelling error appears in error message displayed to the user.
  diff below is difference between original file and my own fixed version.

  
  diff rdisc.c rdisc.fc
  390c390
  < (void) fprintf(stderr, "Extra paramaters\n");
  ---
  > (void) fprintf(stderr, "Extra parameters\n");

  
  Version information
  apt-cache policy iputils-ping
  iputils-ping:
Installed: 3:20071127-1
Candidate: 3:20071127-1
Version table:
   *** 3:20071127-1 0
  500 http://archive.ubuntu.com intrepid/main Packages
  100 /var/lib/dpkg/status

  Ubuntu 8.10

  ProblemType: Bug
  Architecture: i386
  Dependencies:
   libgcc1 1:4.3.2-1ubuntu12
   gcc-4.3-base 4.3.2-1ubuntu12
   findutils 4.4.0-2ubuntu3
   libc6 2.8~20080505-0ubuntu7
  DistroRelease: Ubuntu 8.10
  Package: iputils-ping 3:20071127-1
  ProcEnviron:
   
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: iputils
  Uname: Linux 2.6.27-7-generic i686

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

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

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

2016-11-10 Thread Felipe Lemos

I think you are right, thank you.

On Thu, 10 Nov 2016, 05:54 draco, <1574...@bugs.launchpad.net> wrote:

> Hi Felipe
> Have a look to Bug #1577197, I have this problem on switching profile, may
> it be the same case.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
> Status in pulseaudio source package in Xenial:
>   Fix Committed
> Status in pulseaudio source package in Yakkety:
>   Fix Committed
>
> Bug description:
>   Impact:
>
>   A patch we carry for Ubuntu touch introduced a change that originally
>   was required to make sure PulseAudio did not crash. This patch was
>   ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
>   hardware that was to hand at the time worked so was assumed to be ok.
>   However, the opposite is now happening, i.e PulseAudio is crashing
>   with a subset of Bluetooth hardware.
>
>   Regression potential:
>
>   Very low to none. As can be read in this report, much debugging and
>   testing has been done to find the problem, and the eventual fix.
>   Moreover the change is the removal of a patch hunk that removed a line
>   of code originally present in PulseAudio.
>
>   Test case:
>
>   NOTE that this test case applies to bluetooth hardware that is
>   identified as not working in this bug report.
>
>   1. Install, or upgrade to Xenial or yakkety.
>   2. Pair your bluetooth device in the bluetooth settings in the relevant
> settings application for your desktop environment.
>   3. Once paired, you will notice that sound stops working, as pulseaudio
> has thrown an assertion error.
>   4. You do not have to remove your audio device from the paired device
> list, but it may be easier to do so for the next part of the testing.
>   5. Update to the version of PulseAudio in xenial-proposed which is
> 1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
>   6. Re-pair your device. Audio should continue to work, and you should be
> able to switch to your bluetooth device and use it.
>
>
>   Original bug report:
>
>   When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
>   pulseaudio crashes, this does *NOT* happen with a Jambox which leads
>   me to believe it's an intermittent problem with some hardware. This
>   did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).
>
>   Ubuntu Release:
>
>   Description:  Ubuntu 16.04 LTS
>   Release:  16.04
>
>   Pulseaudio Version:
>
>   pulseaudio:
> Installed: 1:8.0-0ubuntu3
> Candidate: 1:8.0-0ubuntu3
> Version table:
>*** 1:8.0-0ubuntu3 500
>   500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
> Packages
>   100 /var/lib/dpkg/status
>
>   Device info:
>
>   [bluetooth]# info 44:5E:F3:B4:07:29
>   Device 44:5E:F3:B4:07:29
>Name: BlueBuds X
>Alias: BlueBuds X
>Class: 0x240404
>Icon: audio-card
>Paired: yes
>Trusted: yes
>Blocked: no
>Connected: no
>LegacyPairing: no
>UUID: Headset   (1108--1000-8000-00805f9b34fb)
>UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
>UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
>UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
>UUID: Handsfree (111e--1000-8000-00805f9b34fb)
>UUID: Unknown   (80ff--1000-8000-00805f9b34fb)
>
>   I have also attached a debug dump of Pulseaudio when attempting to
>   connect to the headphones.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions
>

-- 
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
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Yakkety:
  Fix Committed

Bug description:
  Impact:

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

  Regression potential:

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

[Touch-packages] [Bug 1639337] Re: Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-xorg-evdev

2016-11-10 Thread Aidan Walton

Thanks vasdi, can you perhaps, confirm if this problem does not present
when you run 16.04.1 LTS. I'm trying to work out what changed between
the two releases.

Thanks

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

Title:
  Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-
  xorg-evdev

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Please refer to bug filed with freedesktop.org:

  https://bugs.freedesktop.org/show_bug.cgi?id=98575

  I modified a driver for the Bosto Tablet 22HD and others, this has
  been working without problems across the last several releases and
  continues to work with 16.04.1 LTS.

  When I upgraded to 16.10, pressure readings are lost from all
  applications, X & Y data still visible.

  evtest shows correct EV_ data for ABS_X ABS_Y and ABS_PRESSURE, but
  when xinput is used.

  xinput --list --long 

  The Valuator for pressure is listed, but no changes occur as the tool
  is used. The parameters of the Valuator can still be modified using
  xinput tweaking tools, but no pressure reported.

  All X apps requiring pressure data fail.

  I made a fresh install of 16.10, loaded the driver  same issue.

  I run 16.04.1 LTS, everything fine.
  I have others users of my driver code also using 16.04.1 without issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639337/+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 1640784] [NEW] package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

2016-11-10 Thread michalis

Public bug reported:

fresh install

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Nov 10 14:57:54 2016
DuplicateSignature:
 package:unattended-upgrades:0.90ubuntu0.1
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package unattended-upgrades (--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-11-10 (0 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  fresh install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 10 14:57:54 2016
  DuplicateSignature:
   package:unattended-upgrades:0.90ubuntu0.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package unattended-upgrades (--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-11-10 (0 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.1 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/unattended-upgrades/+bug/1640784/+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 1639175] Re: Please add an "account-plugin-nextcloud" package

** Branch linked: lp:~ci-train-bot/account-plugins/account-plugins-
ubuntu-zesty-2131

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

Title:
  Please add an "account-plugin-nextcloud" package

Status in webapps-sprint:
  Confirmed
Status in account-plugins package in Ubuntu:
  Confirmed

Bug description:
  Please add an account-plugin-nextcloud package.

  For now, this could essentially be a copy of the ownCloud provider
  code with different branding.  Having both providers side-by-side has
  a few benefits:

  1. we can pick which one to install to get desired branding

  2. if the two projects diverge API wise, we can support each
  independently rather than targeting a common subset.

  The obvious downside though is that we'll have some duplication while
  they are ABI compatible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1639175/+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 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

2016-11-10 Thread Jean-Baptiste Lallement

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

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

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

Status in Canonical System Image:
  Fix Committed
Status in gst-plugins-bad0.10 package in Ubuntu:
  In Progress
Status in qtmultimedia-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Hi, as described in QTBUG-50567 [1], qtmultimedia doesn't support opus
  audio codec so for example we cannot record Telegram voice messages (
  bug #1460464 and bug #1375179 ).

  I patched qtmultimedia adding the support for audio/x-opus codec
  through opusdec encoder in qtmultimedia, then I found qtmultimedia
  5.4.1 (shipped with Ubuntu Phone vivid) is built against gstreamer0.10
  and, as gstreamer0.10-plugins-bad packages is not installed by
  default, opusdec encoder is not available.

  I'm working on this bug, I created it to track the progress, in order
  to add opus support I have to:

  1 - create a new gstreamer0.10-opus package containing only the
  opusdec plugin: I don't know whether I have to create a new source
  package containing opusdec sources or only a new .deb package
  (generated from gst-plugins-bad0.10 sources). I'm working on the
  latter as gst-plugins-bad0.10 package requires work in any ways.

  2 - properly patch qtmultimedia source, I'm attaching a 
working-but-needs-cleanup patch. I think some opus declarations in the attached 
patch can be avoided, but I haven't had time to work on it so I'm attaching the 
patch I tested (requires gstreamer0.10-plugins-bad).
  I don't know if qtmultimedia xenial/yakkety versions requires the patch too, 
I haven't checked them yet.

  [1] https://bugreports.qt.io/browse/QTBUG-50567

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630399/+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 1640776] Re: Mouse cursor changes to the "window resize" mode when it should not

I wonder if we should have a shell component that eats the events...
it's not the first time (and probably not the last) we're hitting that
;P

** Description changed:

- when it should not = when there's a launcher quicklist open
+ when it should not = when the window is under a launcher quicklist
  
- How to reproduce: 
-  * Put a window close enough to the launcher
-  * open the launcher
-  * Right click on a launcher icon
-  * Move the window so that it's both above the launcher quicklist and in a 
window border
-  * See how the mouse cursor changes to "resizing mode"
+ How to reproduce:
+  * Put a window close enough to the launcher
+  * open the launcher
+  * Right click on a launcher icon
+  * Move the window so that it's both above the launcher quicklist and in a 
window border
+  * See how the mouse cursor changes to "resizing mode"
  
  Actually i guess it should not even matter if you're over the quicklist
  or not, i guess that simply the cursor should never change to resizing
  mode when there's a quicklist open?

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

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

Title:
  Mouse cursor changes to the "window resize" mode when it should not

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  when it should not = when the window is under a launcher quicklist

  How to reproduce:
   * Put a window close enough to the launcher
   * open the launcher
   * Right click on a launcher icon
   * Move the window so that it's both above the launcher quicklist and in a 
window border
   * See how the mouse cursor changes to "resizing mode"

  Actually i guess it should not even matter if you're over the
  quicklist or not, i guess that simply the cursor should never change
  to resizing mode when there's a quicklist open?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1640776/+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 1476041] Re: iptables-save duplicates libvirt and ufw rules on iptables-restore with iptables-persistent

2016-11-10 Thread MikeR

Happens on 14.04 Ubuntu. As far as I know I have neither installed or defined 
ufw or libvirt.
However after every reboot I have to list:
sudo iptables -L INPUT --line-numbers,  and delete duplicate fail2ban-* entries.

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

Title:
  iptables-save duplicates libvirt and ufw rules on iptables-restore
  with iptables-persistent

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  libvirt and ufw have their own .rule files that they'll load on boot.

  If you want to use iptables-persistent to restore rules you set using
  iptables, there will be duplicate entries once libvirt and ufw also
  load their rules on boot.

  Chain OUTPUT (policy ACCEPT 1780 packets, 323K bytes)
   pkts bytes target prot opt in out source   
destination 
  0 0 ACCEPT udp  --  *  virbr0  0.0.0.0/00.0.0.0/0 
   udp dpt:68
  0 0 ACCEPT udp  --  *  virbr0  0.0.0.0/00.0.0.0/0 
   udp dpt:68

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: iptables 1.4.21-2ubuntu2
  Uname: Linux 4.1.1-040101-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Sun Jul 19 15:04:53 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-06-18 (31 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1476041/+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 1634261] Re: wrong aspect ratio for video playback

2016-11-10 Thread Jim Hodapp

I can confirm that the aspect ratio is incorrect, both for the inline
video scope playback and in mediaplayer-app. It seems to be stretch
vertically.

** Also affects: qtvideo-node (Ubuntu)
   Importance: Undecided
   Status: New

** Project changed: mediaplayer-app => media-hub

** Project changed: media-hub => media-hub (Ubuntu)

** Changed in: media-hub (Ubuntu)
   Status: New => Triaged

** Changed in: qtvideo-node (Ubuntu)
   Status: New => Triaged

** Changed in: media-hub (Ubuntu)
   Importance: Undecided => Medium

** Changed in: qtvideo-node (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- wrong aspect ratio for video playback
+ Wrong aspect ratio for video playback

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

Title:
  Wrong aspect ratio for video playback

Status in media-hub package in Ubuntu:
  Triaged
Status in qtvideo-node package in Ubuntu:
  Triaged

Bug description:
  On my BQ M10, some MP4 videos have a wrong aspect ratio when played.

  While the preview picture is displayed correctly, the playback of
  video has wrong aspect ratio.

  The MP4-video is 16:9 with 720x576 pixels and seems to be played back
  without pixel aspect ratio correction. This is annoying.

  The video file itself seems to be OK as it is played back correctly
  with vlc, mplayer and totem on my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1634261/+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 1634261] Re: Wrong aspect ratio for video playback

2016-11-10 Thread Jim Hodapp

Btw, I confirmed this on turbo running image #r219.

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

Title:
  Wrong aspect ratio for video playback

Status in media-hub package in Ubuntu:
  Triaged
Status in qtvideo-node package in Ubuntu:
  Triaged

Bug description:
  On my BQ M10, some MP4 videos have a wrong aspect ratio when played.

  While the preview picture is displayed correctly, the playback of
  video has wrong aspect ratio.

  The MP4-video is 16:9 with 720x576 pixels and seems to be played back
  without pixel aspect ratio correction. This is annoying.

  The video file itself seems to be OK as it is played back correctly
  with vlc, mplayer and totem on my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1634261/+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()

** Branch linked: lp:~ci-train-bot/indicator-network/indicator-network-
ubuntu-zesty-2185

-- 
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 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

** Description changed:

  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.
  
  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the other
  binary packages do not change and there are no code changes that affect
  processes other than the "deputy pid 1" service manager). So for plain
  upgrades the regression potential is very low. However, there is a
  medium potential for breakage when actually installing the new systemd
  package, as it might interfere with upstart jobs or other running
  processes, cause boot/shutdown hangs, etc.
  
  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.
  
   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.
  
   3. Ensure that "sudo journalctl" works and that "sudo systemctl status
  systemd-journald" is running and has a few lines of log at the end
  (unlike what you get when you run systemctl as user).
  
   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af haveged"
  should only have *one* process and "systemctl status haveged" should not
  be running (it should not exist, or not be enabled and be inactive).
  
     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.
  
   5. Ensure that the standard targets are active, as that is where third-
  party/snap services hook into:
  
  systemctl status sysinit.target multi-user.target default.target
  
   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and ensure
  you can install a snap, and its services start after installing the snap
  and after rebooting.
  
   7. Run "sudo apt-get install --reinstall systemd" to ensure that
  upgrades to newer systemd trusty versions work. The running systemd
  should *not* be restarted as that would disrupt snapd and its services
  (verify that the pid in "initctl status systemd" is the same before and
  after the upgrade).
  
-  8. Run "sudo apt install -y colord && sudo apt purge -y colord". This
+  8. Run "sudo apt install -y colord && sudo apt purge -y colord". This
  should succeed.
  
   9. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
  dependency issues, etc.

** Description changed:

  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.
  
  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the other
  binary packages do not change and there are no code changes that affect
  processes other than the "deputy pid 1" service manager). So for plain
  upgrades the regression potential is very low. However, there is a
  medium potential for breakage when actually installing the new systemd
  package, as it might interfere with upstart jobs or other running
  processes, cause boot/shutdown hangs, etc.
+ 
+ For init-system-helpers, the regression potential is near-zero: We
+ never had (and never will) systemd as pid 1 in trusty, so deb-systemd-
+ invoke was previously never called. It does get called now if you
+ install Ubuntu packages that ship a systemd unit, so we need to make
+ that a no-op to retain the current behaviour.
  
  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.
  
   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.
  
   3. Ensure that "sudo journalctl" works and that "sudo systemctl status
  systemd-journald" is running and has a few lines of log at the end
  (unlike

[Touch-packages] [Bug 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

I discussed the current status with Thomas today, and he says that i-s-h
and systemd are good to go. I uploaded those to the trusty-proposed SRU
review queue.

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

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in init-system-helpers package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in init-system-helpers source package in Trusty:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  For init-system-helpers, the regression potential is near-zero: We
  never had (and never will) systemd as pid 1 in trusty, so deb-systemd-
  invoke was previously never called. It does get called now if you
  install Ubuntu packages that ship a systemd unit, so we need to make
  that a no-op to retain the current behaviour.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af
  haveged" should only have *one* process and "systemctl status haveged"
  should not be running (it should not exist, or not be enabled and be
  inactive). [This part also needs the updated init-system-helpers].

     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.

   5. Ensure that the standard targets are active, as that is where
  third-party/snap services hook into:

  systemctl status sysinit.target multi-user.target default.target

   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and
  ensure you can install a snap, and its services start after installing
  the snap and after rebooting.

   7. Run "sudo apt-get install --reinstall systemd" to ensure that
  upgrades to newer systemd trusty versions work. The running systemd
  should *not* be restarted as that would disrupt snapd and its services
  (verify that the pid in "initctl status systemd" is the same before
  and after the upgrade).

   8. Run "sudo apt install -y colord && sudo apt purge -y colord". This
  should succeed.

   9. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
  dependency issues, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1616422/+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 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

2016-11-10 Thread Timo Jyrinki

Also fixed in vivid's gst0.10, and added gstreamer0.10-opus to vivid
seed.

** Changed in: gst-plugins-bad0.10 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

Status in Canonical System Image:
  Fix Committed
Status in gst-plugins-bad0.10 package in Ubuntu:
  Fix Released
Status in qtmultimedia-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Hi, as described in QTBUG-50567 [1], qtmultimedia doesn't support opus
  audio codec so for example we cannot record Telegram voice messages (
  bug #1460464 and bug #1375179 ).

  I patched qtmultimedia adding the support for audio/x-opus codec
  through opusdec encoder in qtmultimedia, then I found qtmultimedia
  5.4.1 (shipped with Ubuntu Phone vivid) is built against gstreamer0.10
  and, as gstreamer0.10-plugins-bad packages is not installed by
  default, opusdec encoder is not available.

  I'm working on this bug, I created it to track the progress, in order
  to add opus support I have to:

  1 - create a new gstreamer0.10-opus package containing only the
  opusdec plugin: I don't know whether I have to create a new source
  package containing opusdec sources or only a new .deb package
  (generated from gst-plugins-bad0.10 sources). I'm working on the
  latter as gst-plugins-bad0.10 package requires work in any ways.

  2 - properly patch qtmultimedia source, I'm attaching a 
working-but-needs-cleanup patch. I think some opus declarations in the attached 
patch can be avoided, but I haven't had time to work on it so I'm attaching the 
patch I tested (requires gstreamer0.10-plugins-bad).
  I don't know if qtmultimedia xenial/yakkety versions requires the patch too, 
I haven't checked them yet.

  [1] https://bugreports.qt.io/browse/QTBUG-50567

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630399/+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 1598584] Re: wifi slows to a crawl when bluetooth is enabled

2016-11-10 Thread Jean-Baptiste Lallement

no improvement on frieza with latest rc-proposed (ubuntu-touch/rc-
proposed/bq-aquaris-pd.en 228) and boot.img from comment 15. It even
seems to be worse. Sometimes I cannot connect to the network at all with
BT on and no activity on BT.

** Changed in: canonical-devices-system-image
 Assignee: Jean-Baptiste Lallement (jibel) => Alfonso Sanchez-Beato 
(alfonsosanchezbeato)

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

Title:
  wifi slows to a crawl when bluetooth is enabled

Status in arale:
  New
Status in Canonical System Image:
  In Progress
Status in frieza:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  I am having serious wifi performance issues on my Aquaris M10 (running
  rc-proposed r133). When measuring the wifi speed, I get download
  speeds of less than 1/20 compared to my Pro 5 at the same distance
  from the wifi router. This seems to be consistent through reboots. I
  had similar wifi performance also before recently upgrading to rc-
  proposed, which I thought would have fixed the issue.

  I am in the same place testing 3 different ubuntu devices and these are the 
readings of the wifi download speed:
  Laptop: 4 MB/s
  Pro 5: 3.5 MB/s
  Aquaris M10: 0.16 MB/s

  However, upload speed is about the same on all three devices.

  Turning bluetooth off gets Aquaris M10 wifi speed back to sort of
  normal, 2.5-3.4 MB/s. Bluetooth on, again 0.1-0.2 MB/s. Seems the two
  wireless technologies interfere with each other on the M10, while the
  Pro 5 doesn't have that problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/arale/+bug/1598584/+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 1638695] Re: Python 2.7.12 performance regression

2016-11-10 Thread Major Hayden

Thanks for confirming that, Matthias. Testing with GCC 4.8 seemed to
yield (mostly) better results. I put the data into a Google Sheet:

https://goo.gl/9gW82j

Out of the 10 pyperformance tests:

* 3 tests were actually faster with python compiled w/gcc-4.8
* 4 tests were slightly slower (but within 5%)
* 3 tests were ~ 20-25% slower

Overall, these numbers look quite a bit better.

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

Title:
Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
Confirmed

Bug description:
I work on the OpenStack-Ansible project and we've noticed that testing
jobs on 16.04 take quite a bit longer to complete than on 14.04. They
complete within an hour on 14.04 but they normally take 90 minutes or
more on 16.04. We use the same version of Ansible with both versions
of Ubuntu.

After more digging, I tested python performance (using the
'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There
is a significant performance difference between each version of
python. That is detailed in a spreadsheet[0].

I began using perf to dig into the differences when running the python
performance module and when using Ansible playbooks. CPU migrations
(as measured by perf) are doubled in Ubuntu 16.04 when running the
same python workloads.

I tried changing some of the kerne.sched sysctl configurables but they
had very little effect on the results.

I compiled python 2.7.12 from source on 14.04 and found the
performance to be unchanged there. I'm not entirely sure where the
problem might be now.

We also have a bug open in OpenStack-Ansible[1] that provides
additional detail. Thanks in advance for any help you can provide!

[0]
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
[1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+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 1640823] [NEW] [trusty] limited to 8 loop devices

Public bug reported:

trusty has a very old util-linux which does not yet know about /dev
/loop-control to create arbitrarily many loop devices. This feature was
introduced in Linux 3.1 already (i. e. before precise even). This is a
showstopper for backporting snappy as that needs a lot of loop mounts.

Support for loop-control got introduced in
http://git.kernel.org/cgit/utils/util-linux/util-
linux.git/commit/?id=0b14bf7a

SRU TEST CASE:
$ for i in `seq 20`; do echo $i; sudo losetup --find --show /etc/issue; done

With current trusty's util-linux this will only work for 8 loop devices
and then start failing:

8
/dev/loop7
9
losetup: could not find any free loop device
[...]

With the proposed version, they should all work.

REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux
support has exited for a long time without known/major issues, so this
should be fairly safe. Also, the patch falls back to the previous
"iterate over loop0 to loop7" behaviour if loop-control is not
available.

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: util-linux (Ubuntu Trusty)
 Importance: Undecided
 Status: Triaged

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

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

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

** Description changed:

  trusty has a very old util-linux which does not yet know about /dev
  /loop-control to create arbitrarily many loop devices. This feature was
  introduced in Linux 3.1 already (i. e. before precise even). This is a
  showstopper for backporting snappy as that needs a lot of loop mounts.
  
  Support for loop-control got introduced in
  http://git.kernel.org/cgit/utils/util-linux/util-
  linux.git/commit/?id=0b14bf7a
  
  SRU TEST CASE:
  $ for i in `seq 20`; do echo $i; sudo losetup --find --show /etc/issue; done
  
  With current trusty's util-linux this will only work for 8 loop devices
  and then start failing:
  
  8
  /dev/loop7
  9
  losetup: could not find any free loop device
  [...]
  
  With the proposed version, they should all work.
  
  REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux
  support has exited for a long time without known/major issues, so this
- should be fairly safe.
+ should be fairly safe. Also, the patch falls back to the previous
+ "iterate over loop0 to loop7" behaviour if loop-control is not
+ available.

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

Title:
  [trusty] limited to 8 loop devices

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Triaged

Bug description:
  trusty has a very old util-linux which does not yet know about /dev
  /loop-control to create arbitrarily many loop devices. This feature
  was introduced in Linux 3.1 already (i. e. before precise even). This
  is a showstopper for backporting snappy as that needs a lot of loop
  mounts.

  Support for loop-control got introduced in
  http://git.kernel.org/cgit/utils/util-linux/util-
  linux.git/commit/?id=0b14bf7a

  SRU TEST CASE:
  $ for i in `seq 20`; do echo $i; sudo losetup --find --show /etc/issue; done

  With current trusty's util-linux this will only work for 8 loop
  devices and then start failing:

  8
  /dev/loop7
  9
  losetup: could not find any free loop device
  [...]

  With the proposed version, they should all work.

  REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-
  linux support has exited for a long time without known/major issues,
  so this should be fairly safe. Also, the patch falls back to the
  previous "iterate over loop0 to loop7" behaviour if loop-control is
  not available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1640823/+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 1640823] Re: [trusty] limited to 8 loop devices

** Description changed:

  trusty has a very old util-linux which does not yet know about /dev
  /loop-control to create arbitrarily many loop devices. This feature was
  introduced in Linux 3.1 already (i. e. before precise even). This is a
  showstopper for backporting snappy as that needs a lot of loop mounts.
  
  Support for loop-control got introduced in
  http://git.kernel.org/cgit/utils/util-linux/util-
  linux.git/commit/?id=0b14bf7a
  
  SRU TEST CASE:
- $ for i in `seq 20`; do echo $i; sudo losetup --find --show /etc/issue; done
+ First, use up all default 8 loop devices:
+ $ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done
  
- With current trusty's util-linux this will only work for 8 loop devices
- and then start failing:
+ Now try to use a 9th:
+ $ sudo mount -o loop /etc/issue /mnt
  
- 8
- /dev/loop7
- 9
- losetup: could not find any free loop device
- [...]
- 
- With the proposed version, they should all work.
+ With current trusty's util-linux this will fail with "could not find any
+ free loop device". With the proposed version, this should "only" fail
+ with "you must specify the filesystem type" (or try it on an actual file
+ system image).
  
  REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux
  support has exited for a long time without known/major issues, so this
  should be fairly safe. Also, the patch falls back to the previous
  "iterate over loop0 to loop7" behaviour if loop-control is not
  available.

** Summary changed:

- [trusty] limited to 8 loop devices
+ [trusty] mount -o loop is limited to 8 loop devices

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

Title:
  [trusty] mount -o loop is limited to 8 loop devices

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Triaged

Bug description:
  trusty has a very old util-linux which does not yet know about /dev
  /loop-control to create arbitrarily many loop devices. This feature
  was introduced in Linux 3.1 already (i. e. before precise even). This
  is a showstopper for backporting snappy as that needs a lot of loop
  mounts.

  Support for loop-control got introduced in
  http://git.kernel.org/cgit/utils/util-linux/util-
  linux.git/commit/?id=0b14bf7a

  SRU TEST CASE:
  First, use up all default 8 loop devices:
  $ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done

  Now try to use a 9th:
  $ sudo mount -o loop /etc/issue /mnt

  With current trusty's util-linux this will fail with "could not find
  any free loop device". With the proposed version, this should "only"
  fail with "you must specify the filesystem type" (or try it on an
  actual file system image).

  REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-
  linux support has exited for a long time without known/major issues,
  so this should be fairly safe. Also, the patch falls back to the
  previous "iterate over loop0 to loop7" behaviour if loop-control is
  not available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1640823/+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 1636905] Re: Sound card not recognized on Dell Vostro 5568

Sorry, the attached screen shot for the previous comment was not
correct, here is the correct one.

** Attachment added: "audio3.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+attachment/4775374/+files/audio3.png

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

Title:
  Sound card not recognized on  Dell Vostro 5568

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just reinstalled a fresh Ubuntu 16.10 on my Dell Vostro 5568 laptop.

  The audio controller on the laptop is a Realtek ALC3246 with Waves
  MaxxAudio Pro. The external interface connector is a microphone
  in/stereo headphones/external speakers connector.

  When I select "System Settings->Sound" the output device in the dialog
  window shows as "Dummy Output" and when I press the "Test Sound"
  button no sound is heard from either front left or front right speaker
  ( I have ensured sound is not muted ).

  Note: Before reinstalling, I asked a question on askubuntu,com:

  http://askubuntu.com/q/841759/156688

  So reinstallation of Ubuntu 16.10 did not help on my sound problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+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 1636905] Re: Sound card not recognized on Dell Vostro 5568

Rebooting with headphones unplugged worked fine for a while; then I
suspended my laptop for an hour. When I came back and the laptop was
reactivated (by opening the lid) sound was not working. Now I went to
System Settings->Sound again, and to my surprise some new items had been
added to the Output Tab ( see attached file ). It now showed three
additional devices: "HDMI/DisplayPort: Built-in Audio",
"HDMI/DisplayPort 2: Built-in Audio", and "HDMI/DisplayPort 3: Built-in
Audio". But none of these devices worked any better than the original
"Headphones: Built-in Audio". If I now uplugged the headphones, there
was no sound from the speakers either. And if I tried to replug the
headphones, I did not get the popup window about unknown audio device,
and still no sound. (aplay -l still shows correct output). I will now
try to reboot again and see what happens. I expect I will now have come
back to my original problem where sound is permanently disabled, and the
sound card is not recognized at all.

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

Title:
  Sound card not recognized on  Dell Vostro 5568

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just reinstalled a fresh Ubuntu 16.10 on my Dell Vostro 5568 laptop.

  The audio controller on the laptop is a Realtek ALC3246 with Waves
  MaxxAudio Pro. The external interface connector is a microphone
  in/stereo headphones/external speakers connector.

  When I select "System Settings->Sound" the output device in the dialog
  window shows as "Dummy Output" and when I press the "Test Sound"
  button no sound is heard from either front left or front right speaker
  ( I have ensured sound is not muted ).

  Note: Before reinstalling, I asked a question on askubuntu,com:

  http://askubuntu.com/q/841759/156688

  So reinstallation of Ubuntu 16.10 did not help on my sound problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+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 1636905] Re: Sound card not recognized on Dell Vostro 5568

Ok then, I have rebooted Ubuntu again, and yes, as I expected I have now
returned to the origianl situation:

When I select "System Settings->Sound" the output device in the dialog
window shows as "Dummy Output" and when I press the "Test Sound" button
no sound is heard from either front left or front right speaker. Running
aplay -l gives:

$ aplay -l
aplay: device_list:268: no soundcards found...

Any advice on what to do next?

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

Title:
  Sound card not recognized on  Dell Vostro 5568

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just reinstalled a fresh Ubuntu 16.10 on my Dell Vostro 5568 laptop.

  The audio controller on the laptop is a Realtek ALC3246 with Waves
  MaxxAudio Pro. The external interface connector is a microphone
  in/stereo headphones/external speakers connector.

  When I select "System Settings->Sound" the output device in the dialog
  window shows as "Dummy Output" and when I press the "Test Sound"
  button no sound is heard from either front left or front right speaker
  ( I have ensured sound is not muted ).

  Note: Before reinstalling, I asked a question on askubuntu,com:

  http://askubuntu.com/q/841759/156688

  So reinstallation of Ubuntu 16.10 did not help on my sound problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+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 1640836] [NEW] running xdiagnose

2016-11-10 Thread andreas ott

Public bug reported:

not much to say i was running sudo sudo xdiagnose on a macbook pro

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
 GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
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: Thu Nov 10 16:28:59 2016
DistUpgraded: 2016-10-13 21:58:43,832 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: yakkety
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] [10de:0fe9] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Apple Inc. GK107M [GeForce GT 750M Mac Edition] [106b:0130]
InstallationDate: Installed on 2014-11-26 (715 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Apple Inc. MacBookPro11,3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=c2b561fa-803d-4674-82d9-1a1c65331365 ro libata.force=noncq quiet 
splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2016-10-13 (27 days ago)
dmi.bios.date: 08/29/2014
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP112.88Z.0138.B11.1408291503
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-2BD1B31983FE1663
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,3
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-2BD1B31983FE1663
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B11.1408291503:bd08/29/2014:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
dmi.product.name: MacBookPro11,3
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Thu Nov 10 10:46:25 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-1ubuntu6

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety

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

Title:
  running xdiagnose

Status in xorg package in Ubuntu:
  New

Bug description:
  not much to say i was running sudo sudo xdiagnose on a macbook pro

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  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: Thu Nov 10 16:28:59 2016
  DistUpgraded: 2016-10-13 21:58:43,832 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] [10de:0fe9] (rev a1) 
(prog-if 00 [VGA controller])

[Touch-packages] [Bug 1632275] Re: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

This bug was fixed in the package indicator-network -
0.8.0+17.04.20161109-0ubuntu1

---
indicator-network (0.8.0+17.04.20161109-0ubuntu1) zesty; urgency=medium

  * Try again to make the tests more reliable (LP: #1632275)

 -- Pete Woods   Wed, 09 Nov 2016 10:04:06
+

** Changed in: indicator-network (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  Fix Released

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 1634748] Re: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf',

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

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

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

Title:
  package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/accounts.google.com.conf', which is also in package
  kaccounts-providers 4:16.04.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  Confirmed

Bug description:
  This does this after GUI is logged into...

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: account-plugin-google 0.13+16.10.20160831-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
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 17 22:13:47 2016
  DuplicateSignature:
   package:account-plugin-google:0.13+16.10.20160831-0ubuntu1
   Unpacking account-plugin-google (0.13+16.10.20160929.1-0ubuntu1) over 
(0.13+16.10.20160831-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-FwnFQX/033-account-plugin-google_0.13+16.10.20160929.1-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: account-plugins
  Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1634748/+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 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

** Description changed:

  trusty has a very old util-linux which does not yet know about /dev
  /loop-control to create arbitrarily many loop devices. This feature was
  introduced in Linux 3.1 already (i. e. before precise even). This is a
  showstopper for backporting snappy as that needs a lot of loop mounts.
  
  Support for loop-control got introduced in
  http://git.kernel.org/cgit/utils/util-linux/util-
  linux.git/commit/?id=0b14bf7a
  
- SRU TEST CASE:
+ SRU TEST CASE: (FIXME: this does not actually get fixed with the above commit)
  First, use up all default 8 loop devices:
  $ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done
  
  Now try to use a 9th:
  $ sudo mount -o loop /etc/issue /mnt
  
  With current trusty's util-linux this will fail with "could not find any
  free loop device". With the proposed version, this should "only" fail
  with "you must specify the filesystem type" (or try it on an actual file
  system image).
  
  REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux
  support has exited for a long time without known/major issues, so this
  should be fairly safe. Also, the patch falls back to the previous
  "iterate over loop0 to loop7" behaviour if loop-control is not
  available.

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

Title:
  [trusty] mount -o loop is limited to 8 loop devices

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Triaged

Bug description:
  trusty has a very old util-linux which does not yet know about /dev
  /loop-control to create arbitrarily many loop devices. This feature
  was introduced in Linux 3.1 already (i. e. before precise even). This
  is a showstopper for backporting snappy as that needs a lot of loop
  mounts.

  Support for loop-control got introduced in
  http://git.kernel.org/cgit/utils/util-linux/util-
  linux.git/commit/?id=0b14bf7a

  SRU TEST CASE: (FIXME: this does not actually get fixed with the above commit)
  First, use up all default 8 loop devices:
  $ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done

  Now try to use a 9th:
  $ sudo mount -o loop /etc/issue /mnt

  With current trusty's util-linux this will fail with "could not find
  any free loop device". With the proposed version, this should "only"
  fail with "you must specify the filesystem type" (or try it on an
  actual file system image).

  REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-
  linux support has exited for a long time without known/major issues,
  so this should be fairly safe. Also, the patch falls back to the
  previous "iterate over loop0 to loop7" behaviour if loop-control is
  not available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1640823/+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 1639337] Re: Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-xorg-evdev

2016-11-10 Thread Mike H

Note, this bug does not only apply to USB digitizers but to built-in
digitizers in some 2-in-1's as well (I am experiencing exactly the same
behavior on a fresh install of 16.10 but instead with the pen on my
lenovo miix 700 tablet, 100% vanilla drivers from the ubuntu install).

The pressure events show up just fine when watching from evtest, but
xinput never seems to get ABS_PRESSURE updates. xinput sees the device
axis just never gets update, which pins the pressure at zero. This is
not a bug at the driver level, It's almost definitely some kind of
regression in xorg/xinput/touch code..

Since the pressure is stuck at zero, this bug doesn't just stop pressure
sensing, it's a total creative showstopper - makes it impossible to draw
in any of the various art programs because pressure=0 --> nothing gets
drawn in most programs, Krita segfaults, etc. etc.

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

Title:
  Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-
  xorg-evdev

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Please refer to bug filed with freedesktop.org:

  https://bugs.freedesktop.org/show_bug.cgi?id=98575

  I modified a driver for the Bosto Tablet 22HD and others, this has
  been working without problems across the last several releases and
  continues to work with 16.04.1 LTS.

  When I upgraded to 16.10, pressure readings are lost from all
  applications, X & Y data still visible.

  evtest shows correct EV_ data for ABS_X ABS_Y and ABS_PRESSURE, but
  when xinput is used.

  xinput --list --long 

  The Valuator for pressure is listed, but no changes occur as the tool
  is used. The parameters of the Valuator can still be modified using
  xinput tweaking tools, but no pressure reported.

  All X apps requiring pressure data fail.

  I made a fresh install of 16.10, loaded the driver  same issue.

  I run 16.04.1 LTS, everything fine.
  I have others users of my driver code also using 16.04.1 without issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639337/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

** Merge proposal linked:
   https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/310547

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  In Progress
Status in cloud-init source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  
  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
└─basic.target @11.403s
  └─sockets.target @11.401s
└─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
└─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
└─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
└─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
└─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
└─system.slice @783ms
  └─-.slice @721ms

  
  cloud-init would need networkd to run at or before 'networking.service' so it 
can raise networking to then find and use network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list 
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init /usr/share/snappy/dpkg.list 
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1636912/+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 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up

** Merge proposal linked:
   https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/310547

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

Title:
  resolve service in nsswitch.conf adds 25 seconds to failed lookups
  before systemd-resolved is up

Status in cloud-init:
  Fix Committed
Status in D-Bus:
  Unknown
Status in cloud-init package in Ubuntu:
  Fix Released
Status in dbus package in Ubuntu:
  Won't Fix
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact] 
  In cases where cloud-init used dns during early boot and system was
  configured in nsswitch.conf to use systemd-resolvd, the system would
  timeout on dns attempts making system boot terribly slow.

  [Test Case]
  Boot a system on GCE.
  check for WARN in /var/log/messages
  check that time to boot is reasonable (<30 seconds).  In failure case the
  times would be minutes.

  [Regression Potential]
  Changing order in boot can be dangerous.  There is real chance for 
  regression here, but it should be fairly small as xenial does not include
  systemd-resolved usage.  This was first noticed on yakkety where it did.

  [Other Info]
  It seems useful to SRU this in the event that systemd-resolvd is used
  on 16.04 or the case where user upgrades components (admittedly small use
  case).

  === End SRU Template ===


  
  During boot, cloud-init does DNS resolution checks to if particular metadata 
services are available (in order to determine which cloud it is running on).  
These checks happen before systemd-resolved is up[0] and if they resolve 
unsuccessfully they take 25 seconds to complete.

  This has substantial impact on boot time in all contexts, because
  cloud-init attempts to resolve three known-invalid addresses ("does-
  not-exist.example.com.", "example.invalid." and a random string) to
  enable it to detect when it's running in an environment where a DNS
  server will always return some sort of redirect.  As such, we're
  talking a minimum impact of 75 seconds in all environments.  This
  increases when cloud-init is configured to check for multiple
  environments.

  This means that yakkety is consistently taking 2-3 minutes to boot on
  EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
  seconds thereafter in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1629797/+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 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

2016-11-10 Thread Steve Langasek

Hello Martin, or anyone else affected,

Accepted init-system-helpers into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/init-
system-helpers/1.14ubuntu1 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 on 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!

** Changed in: init-system-helpers (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in init-system-helpers package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in init-system-helpers source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  In Progress

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  For init-system-helpers, the regression potential is near-zero: We
  never had (and never will) systemd as pid 1 in trusty, so deb-systemd-
  invoke was previously never called. It does get called now if you
  install Ubuntu packages that ship a systemd unit, so we need to make
  that a no-op to retain the current behaviour.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af
  haveged" should only have *one* process and "systemctl status haveged"
  should not be running (it should not exist, or not be enabled and be
  inactive). [This part also needs the updated init-system-helpers].

     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.

   5. Ensure that the standard targets are active, as that is where
  third-party/snap services hook into:

  systemctl status sysinit.target multi-user.target default.target

   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and
  ensure you can install a snap, and its services start after installing
  the snap and after rebooting.

   7. Run "sudo apt-get install --reinstall systemd" to ensure that
  upgrades to newer systemd trusty versions work. The running systemd
  should *not* be restarted as that would disrupt snapd and its services
  (verify that the pid in "initctl status systemd" is the same before
  and after the upgrade).

   8. Run "sudo apt install -y colord && sudo apt purge -y colord". This
  should succeed.

   9. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
  dependency issues, etc.

To manage notifications about this bug

[Touch-packages] [Bug 1640849] [NEW] Enhanced coloring of differences

2016-11-10 Thread Sworddragon

Public bug reported:

I'm using Ubuntu 17.04 dev with diffutils 1:3.5-1 and currently only the
lines are colored for added/removed ones. Maybe the differences in the
lines which characters are added/removed can be colored too (for example
with a higher opacity) to make them easier to see.

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

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

Title:
  Enhanced coloring of differences

Status in diffutils package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 17.04 dev with diffutils 1:3.5-1 and currently only
  the lines are colored for added/removed ones. Maybe the differences in
  the lines which characters are added/removed can be colored too (for
  example with a higher opacity) to make them easier to see.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/diffutils/+bug/1640849/+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 1486128] Re: Coloring of differences

2016-11-10 Thread Sworddragon

** Changed in: diffutils (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Coloring of differences

Status in diffutils package in Ubuntu:
  Fix Released
Status in diffutils package in Debian:
  Fix Released

Bug description:
  I'm using Ubuntu 15.10 dev with diffutils 1:3.3-1 and maybe diff can
  color added/removed lines green/red for example like git-gui does.
  Maybe this could also get enhanced to do this for the differences in
  the lines which characters are added/removed (for example with a
  higher opacity).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/diffutils/+bug/1486128/+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 508522] Re: Mic is not available with A2DP Bluetooth profile

2016-11-10 Thread Raphael Carrier

Its a limitation of the bluetooth protocol.

Windows and macos implement both A2DP and HFP and switch on the fly when
microphone usage is requested by an app. HFP uses a low quality GSM
codec so the sound quality will degrade when switching to that profile.

It is possible to have multiple bluetooth profiles active on one device
but A2DP and HFP are mutually exclusive due to bandwidth limitations.

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

Title:
  Mic is not available with A2DP Bluetooth profile

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+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 1595963] Re: vt1-6 getting stuck or blank

2016-11-10 Thread Phillip Susi

If you can reproduce it, let us know and we'll try to get a better
handle on it.  Had you already logged in on that terminal before, or was
it supposed to still be sitting at the login prompt?


** No longer affects: systemd (Ubuntu)

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

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

Title:
  vt1-6 getting stuck or blank

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  It's happening from time to time that my vt1-6 are getting stuck
  (showing tty1 and no input) or blank (just black) completely.

  Restarting system-getty.slice or console-getty.slice doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 24 10:00:54 2016
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 12-9Q33
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: systemd 229-4ubuntu6
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed 
root=ZFS=/root ro root=ZFS=username-laptop/root quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1595963/+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 1637712] Re: Pixelated icon in notification bubble

** Changed in: canonical-devices-system-image
Milestone: 14 => backlog

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

Title:
  Pixelated icon in notification bubble

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  bq M10 rc-proposed r220 and bq e4.5 OTA13

  Icon visible in the notification bubble looks pixelated. Screenshot
  attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1637712/+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 1622423] Re: My activity child link disappears after logged in fitbit account

** Changed in: canonical-devices-system-image
Milestone: 14 => backlog

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

Title:
  My activity child link disappears after logged in fitbit account

Status in Canonical System Image:
  In Progress
Status in Today Scope:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  $ system-image-cli -i
  current build number: 15
  device name: turbo
  channel: ubuntu-touch/rc/meizu-pd.en
  last update: 2016-09-05 03:19:44
  version version: 15
  version ubuntu: 20160903
  version tag: OTA-13-rc
  version device: 20160824-d33b825
  version custom: 20160831-992-8-12

  The child arrow link of My Activity session disappears once logged in
  fitbit account in Today scope, so unable to open My Activity child
  scope from Today scope

  Steps to reproduce:
  1. Open Today scope and navigate to My Activity session, 
  2. Existing a child link, tap it will open My Activity scope
  2. Tap 'Add your fitbit account' and login with Google account
  3. Once logged in, back to Today scope and refresh, check if the child link 
still exist.

  Actual results:
  Once logged in fitbit account, some items of fitbit displayed in session, but 
the child scope link has gone, unable to open My Activity scope from Today scope
  If open My Activity scope from manage page by swiping up, blank scope page 
shown

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1622423/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-11-10 Thread ghuisman

@Peter S (peter-sevemark):

First of all I agree on your comment #114: We need to test suggested
scenarios so we can converge to a solution or approach to tackle the
issue.

So I have installed WICD (conform issue #109) and removed the default network 
manager.
summary of my issue: in most cases no wifi connection after suspend and no 
possibility to make a new connection. I am using a Lenovo X220 with Ubuntu 
16.04.

WICD gives me the opportunity to enable the WIFI connection after
suspend. however I have to do it manually by starting the WICD
application. The setting to make a connection automatically does not
work.

I will test the robustness of WICD in relation to my issue further
Do you have a solution for the fact that WICD does not connect automatically?

Thanks
Geert

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

Title:
  cannot view wifi networks after re-enabling wifi

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

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1508905] Re: Graphics disorder, a large "claw" ('>') appearing

** Changed in: canonical-devices-system-image
Milestone: 14 => backlog

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

Title:
  Graphics disorder, a large "claw" ('>') appearing

Status in Canonical System Image:
  In Progress
Status in Today Scope:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Hi,

  Currently I have this bug. It was already present in the OTA-6.
  Usually a reboot fix the problem, but after a while it come back
  again.

  It only appears ate the bottom of the scope! If I swipe back to the
  top the "claw" fade out.

  I've attached a screenshot.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508905/+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 1607427] Re: super key not showing scopes home

** Changed in: canonical-devices-system-image
Milestone: 14 => backlog

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

Title:
  super key not showing scopes home

Status in Canonical System Image:
  In Progress
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Hey,

  if I press super key, the scopes home does not appear. In OTA-11 it
  worked as it should, but in OTA-12 it doesn't work.

  I use M10 FHD tablet with OTA-12 and external keyboard Logitech k810.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607427/+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 1378814] Re: greeter does not properly update infographic after unlock

** Changed in: canonical-devices-system-image
Milestone: 14 => backlog

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

Title:
  greeter does not properly update infographic after unlock

Status in Band-aids for Ubuntu Phone:
  In Progress
Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  This bug has been here since forever, but really needs to get cleaned
  up for rtm.

  Steps to reproduce:
  - send 2 text messages
  - lock your phone
  - unlock your phone
  - confirm infographic says "2 text messages sent today"
  - lock your phone for the night and go to sleep
  - unlock your phone the next day

  Expected results:
  - infographic should be cleared, or show relevant information for today

  Actual results:
  - infographic still says "2 text messages sent today"

  When the phone is unlocked the greeter should update the infographic
  text

To manage notifications about this bug go to:
https://bugs.launchpad.net/band-aids-uphone/+bug/1378814/+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 1640868] [NEW] network-interface-security upstart job is not container aware

2016-11-10 Thread Tyler Hicks

Public bug reported:

The network-interface-security upstart job unconditionally loads the
usr.sbin.dhclient AppArmor profile even if the job is running in a
LXC/LXD container that cannot load AppArmor policy.

I don't see any negative side effects from this behavior, so I don't
think this is a high priority bug. If this were to be fixed, the upstart
job would need to check to see if it is running inside of a container
and, if so, if the container is capable of loading its own AppArmor
security policy. See
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-4ubuntu5 for an
example of what this would look like.

** Affects: ifupdown (Ubuntu)
 Importance: Low
 Status: Triaged

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

Title:
  network-interface-security upstart job is not container aware

Status in ifupdown package in Ubuntu:
  Triaged

Bug description:
  The network-interface-security upstart job unconditionally loads the
  usr.sbin.dhclient AppArmor profile even if the job is running in a
  LXC/LXD container that cannot load AppArmor policy.

  I don't see any negative side effects from this behavior, so I don't
  think this is a high priority bug. If this were to be fixed, the
  upstart job would need to check to see if it is running inside of a
  container and, if so, if the container is capable of loading its own
  AppArmor security policy. See
  https://launchpad.net/ubuntu/+source/apparmor/2.10.95-4ubuntu5 for an
  example of what this would look like.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1640868/+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 1640868] Re: network-interface-security upstart job is not container aware

2016-11-10 Thread Tyler Hicks

** Description changed:

  The network-interface-security upstart job unconditionally loads the
  usr.sbin.dhclient AppArmor profile even if the job is running in a
  LXC/LXD container that cannot load AppArmor policy.
  
  I don't see any negative side effects from this behavior, so I don't
  think this is a high priority bug. If this were to be fixed, the upstart
  job would need to check to see if it is running inside of a container
  and, if so, if the container is capable of loading its own AppArmor
  security policy. See
  https://launchpad.net/ubuntu/+source/apparmor/2.10.95-4ubuntu5 for an
  example of what this would look like.
+ 
+ This behavior can be seen with a 16.04 host, running lxd from either the
+ archive or as a snap, and launching a 14.04 container. aa-status inside
+ of the container will show:
+ 
+ $ lxd.lxc exec t aa-status
+ apparmor module is loaded.
+ 3 profiles are loaded.
+ 3 profiles are in enforce mode.
+/sbin/dhclient
+/usr/lib/NetworkManager/nm-dhcp-client.action
+/usr/lib/connman/scripts/dhclient-script
+ 0 profiles are in complain mode.
+ 1 processes have profiles defined.
+ 1 processes are in enforce mode.
+/sbin/dhclient (810) 
+ 0 processes are in complain mode.
+ 0 processes are unconfined but have a profile defined.
+ 
+ IMPORTANT: It is likely that upstart in 14.04 will receive a future SRU
+ which will result in AppArmor policy to be loaded during the boot
+ process when inside of a LXD container. That will make this bug more
+ difficult to verify. Once that change lands, you'll likely have to
+ modify /lib/init/aa-profile-load, inside of the container, to not load
+ policy at boot in order to definitively see this bug.

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

Title:
  network-interface-security upstart job is not container aware

Status in ifupdown package in Ubuntu:
  Triaged

Bug description:
  The network-interface-security upstart job unconditionally loads the
  usr.sbin.dhclient AppArmor profile even if the job is running in a
  LXC/LXD container that cannot load AppArmor policy.

  I don't see any negative side effects from this behavior, so I don't
  think this is a high priority bug. If this were to be fixed, the
  upstart job would need to check to see if it is running inside of a
  container and, if so, if the container is capable of loading its own
  AppArmor security policy. See
  https://launchpad.net/ubuntu/+source/apparmor/2.10.95-4ubuntu5 for an
  example of what this would look like.

  This behavior can be seen with a 16.04 host, running lxd from either
  the archive or as a snap, and launching a 14.04 container. aa-status
  inside of the container will show:

  $ lxd.lxc exec t aa-status
  apparmor module is loaded.
  3 profiles are loaded.
  3 profiles are in enforce mode.
 /sbin/dhclient
 /usr/lib/NetworkManager/nm-dhcp-client.action
 /usr/lib/connman/scripts/dhclient-script
  0 profiles are in complain mode.
  1 processes have profiles defined.
  1 processes are in enforce mode.
 /sbin/dhclient (810) 
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  IMPORTANT: It is likely that upstart in 14.04 will receive a future
  SRU which will result in AppArmor policy to be loaded during the boot
  process when inside of a LXD container. That will make this bug more
  difficult to verify. Once that change lands, you'll likely have to
  modify /lib/init/aa-profile-load, inside of the container, to not load
  policy at boot in order to definitively see this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1640868/+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 508522] Re: Mic is not available with A2DP Bluetooth profile

2016-11-10 Thread Pali

Good news! My (reworked) patches from comment #31 were finally accepted
into pulseaudio git. Autoswitch support for media.role=phone
applications will be in pulseaudio 10.0. And autoswitch support based on
heuristic will be in version after 10.0 (but disabled by default).

media.role=phone patches for pulseaudio 10.0:
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=bde2ff8794a9363b1f7f2c683b160268ce371770
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=e32a462cc4201d9c3c7305d0f806d16a09f08875

heuristic patch (after 10.0):
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=b245fb41e17a4c74a2226f9202788aa883a340e9

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

Title:
  Mic is not available with A2DP Bluetooth profile

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

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

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

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2016-11-10 Thread archenroot

Some interesting update.

The card worked for last 5 months without issue on Windows 10, and
worked under Gentoo(I installed gentoo 1 week ago) until I started
plugin-in the headphones. It worked like this about 5x times and then
the sound stopped working at all. The device was visible, but unusable
under Linux and Windows. I tried to disable Audio in BIOS and rebooted,
but no luck (few times).

Then today I was updating my drivers under Windows again and also
flashed the BIOS with latest one (strange was that the version installed
was same as new proposed, but number of features was different). Anyway
I pickup the install, flashed the BIOS and voila the sound card is
online and working :-)

I didn't do screenshots, but if this will happen again, I will try to do
some more data capture.

So in general I got to situation reported by some other users which were
asking Dell to replace audio card at all in the past (I was saying my
wife that I will do the same this morning), but finally BIOS flash
helped.

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+subscriptions

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

[Touch-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock

2016-11-10 Thread Iain Lane

** Also affects: gtk+2.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gtk+2.0 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: gtk+2.0 (Ubuntu Xenial)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

** Changed in: gtk+2.0 (Ubuntu Yakkety)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

** Changed in: gtk+2.0 (Ubuntu)
 Assignee: Martin Wimpress (flexiondotorg) => Iain Lane (laney)

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

Title:
  Gimp crashes with text tool & caps lock

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Committed
Status in gtk+2.0 source package in Xenial:
  New
Status in gtk+2.0 source package in Yakkety:
  New

Bug description:
  [Impact]

  Gimp crashes with a segfault when I use caps lock while renaming a
  layer. It is possible Caps lock causes crashes in other events also.

  [Test Case]

  Steps to reproduce:

  1. Open a new blank gimp document
  2. select the text tool
  3. type a couple of words of text (gimp will create a text layer above the 
background layer)
  4. with the text tool still selected, click on the background layer (just to 
move away from the text layer)
  5. now double click on the text layer to rename the layer (layer name gets 
highlighted)
  6. press the caps lock key
  7. click on the background layer again (without renaming or doing anything to 
the text layer)
  Now repeat steps 5 and 6.
  Gimp crashes.

  [Regression Potential]

  None expected. The patch used has been taken from upstream
  development.

  
https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad

  Packages for Xenial and Yakkety have been built in a PPA and
  regression tested.

  [ Other Info ]

  I can force this to happen every time I launch Gimp. Rebooting makes
  no difference. It seems to be the second time I press caps lock that
  forces the crash. I tried launching Gimp with caps lock on vs caps
  lock off, but I don't believe it made any difference. I can force a
  crash every time following the above sequence.

  I deleted my gimp preferences folder then rebooted for good measure.
  Gimp created a fresh preferences folder, but it hasn't solved the
  problem. I was originally in single window mode, but the new
  preferences folder put me back to multi window, but it crashes either
  way.

  I ran dmesg | tail after the crash and got the following line:

  gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0
  error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000]

  I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver
  (available from the Additional Drivers tab). In that same tab, I also
  have enabled Processor microcode firmware for Intel CPUs. Terminal
  tells me Gimp version is 2.8.16-1ubuntu1

  I'm not very experienced with bug reporting and not sure what other
  information I need to supply. Gimp was absolutely rock solid on this
  machine with 15.10, so it may be a Xubuntu issue.

  Hope someone can take a look at this. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1576424/+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 1576424] Re: Gimp crashes with text tool & caps lock

2016-11-10 Thread Iain Lane

** Changed in: gtk+2.0 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Gimp crashes with text tool & caps lock

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Committed
Status in gtk+2.0 source package in Xenial:
  New
Status in gtk+2.0 source package in Yakkety:
  New

Bug description:
  [Impact]

  Gimp crashes with a segfault when I use caps lock while renaming a
  layer. It is possible Caps lock causes crashes in other events also.

  [Test Case]

  Steps to reproduce:

  1. Open a new blank gimp document
  2. select the text tool
  3. type a couple of words of text (gimp will create a text layer above the 
background layer)
  4. with the text tool still selected, click on the background layer (just to 
move away from the text layer)
  5. now double click on the text layer to rename the layer (layer name gets 
highlighted)
  6. press the caps lock key
  7. click on the background layer again (without renaming or doing anything to 
the text layer)
  Now repeat steps 5 and 6.
  Gimp crashes.

  [Regression Potential]

  None expected. The patch used has been taken from upstream
  development.

  
https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad

  Packages for Xenial and Yakkety have been built in a PPA and
  regression tested.

  [ Other Info ]

  I can force this to happen every time I launch Gimp. Rebooting makes
  no difference. It seems to be the second time I press caps lock that
  forces the crash. I tried launching Gimp with caps lock on vs caps
  lock off, but I don't believe it made any difference. I can force a
  crash every time following the above sequence.

  I deleted my gimp preferences folder then rebooted for good measure.
  Gimp created a fresh preferences folder, but it hasn't solved the
  problem. I was originally in single window mode, but the new
  preferences folder put me back to multi window, but it crashes either
  way.

  I ran dmesg | tail after the crash and got the following line:

  gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0
  error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000]

  I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver
  (available from the Additional Drivers tab). In that same tab, I also
  have enabled Processor microcode firmware for Intel CPUs. Terminal
  tells me Gimp version is 2.8.16-1ubuntu1

  I'm not very experienced with bug reporting and not sure what other
  information I need to supply. Gimp was absolutely rock solid on this
  machine with 15.10, so it may be a Xubuntu issue.

  Hope someone can take a look at this. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1576424/+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 1576424] Re: Gimp crashes with text tool & caps lock

** Branch linked: lp:~ubuntu-desktop/gtk/ubuntu

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

Title:
  Gimp crashes with text tool & caps lock

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Committed
Status in gtk+2.0 source package in Xenial:
  New
Status in gtk+2.0 source package in Yakkety:
  New

Bug description:
  [Impact]

  Gimp crashes with a segfault when I use caps lock while renaming a
  layer. It is possible Caps lock causes crashes in other events also.

  [Test Case]

  Steps to reproduce:

  1. Open a new blank gimp document
  2. select the text tool
  3. type a couple of words of text (gimp will create a text layer above the 
background layer)
  4. with the text tool still selected, click on the background layer (just to 
move away from the text layer)
  5. now double click on the text layer to rename the layer (layer name gets 
highlighted)
  6. press the caps lock key
  7. click on the background layer again (without renaming or doing anything to 
the text layer)
  Now repeat steps 5 and 6.
  Gimp crashes.

  [Regression Potential]

  None expected. The patch used has been taken from upstream
  development.

  
https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad

  Packages for Xenial and Yakkety have been built in a PPA and
  regression tested.

  [ Other Info ]

  I can force this to happen every time I launch Gimp. Rebooting makes
  no difference. It seems to be the second time I press caps lock that
  forces the crash. I tried launching Gimp with caps lock on vs caps
  lock off, but I don't believe it made any difference. I can force a
  crash every time following the above sequence.

  I deleted my gimp preferences folder then rebooted for good measure.
  Gimp created a fresh preferences folder, but it hasn't solved the
  problem. I was originally in single window mode, but the new
  preferences folder put me back to multi window, but it crashes either
  way.

  I ran dmesg | tail after the crash and got the following line:

  gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0
  error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000]

  I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver
  (available from the Additional Drivers tab). In that same tab, I also
  have enabled Processor microcode firmware for Intel CPUs. Terminal
  tells me Gimp version is 2.8.16-1ubuntu1

  I'm not very experienced with bug reporting and not sure what other
  information I need to supply. Gimp was absolutely rock solid on this
  machine with 15.10, so it may be a Xubuntu issue.

  Hope someone can take a look at this. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1576424/+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 1640888] [NEW] package libnss3-1d:amd64 2:3.23-0ubuntu0.14.04.1 failed to install/upgrade: package libnss3-1d:amd64 is already installed and configured

2016-11-10 Thread Robert Zbašnik

Public bug reported:

m,

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libnss3-1d:amd64 2:3.23-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39
Uname: Linux 3.13.0-101-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
AptdaemonVersion: 1.1.1-1ubuntu5.2
Architecture: amd64
Date: Thu Nov 10 19:04:50 2016
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
DuplicateSignature: package:libnss3-1d:amd64:2:3.23-0ubuntu0.14.04.1:package 
libnss3-1d:amd64 is already installed and configured
ErrorMessage: package libnss3-1d:amd64 is already installed and configured
InstallationDate: Installed on 2016-11-10 (0 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.15
SourcePackage: nss
Title: package libnss3-1d:amd64 2:3.23-0ubuntu0.14.04.1 failed to 
install/upgrade: package libnss3-1d:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package libnss3-1d:amd64 2:3.23-0ubuntu0.14.04.1 failed to
  install/upgrade: package libnss3-1d:amd64 is already installed and
  configured

Status in nss package in Ubuntu:
  New

Bug description:
  m,

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libnss3-1d:amd64 2:3.23-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-101-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Thu Nov 10 19:04:50 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DuplicateSignature: package:libnss3-1d:amd64:2:3.23-0ubuntu0.14.04.1:package 
libnss3-1d:amd64 is already installed and configured
  ErrorMessage: package libnss3-1d:amd64 is already installed and configured
  InstallationDate: Installed on 2016-11-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: nss
  Title: package libnss3-1d:amd64 2:3.23-0ubuntu0.14.04.1 failed to 
install/upgrade: package libnss3-1d:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1640888/+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 1531184] Re: dnsmasq doesn't start on boot because its interface isn't up yet

2016-11-10 Thread Sarraceno

I have openvswitch-switch, which did required from me to apply some
changes to systemd service file that seems not to be aware of virtual
devices up.

So, bottom line, /etc/network/interface files are taking action in a way
that smashes the rush to boot up, so dnsmasq also become a victim, and
for me the solution above was not compatible.

So I had to add to dnsmasq.service the follow lines:

 Requires=sys-subsystem-net-devices-.device
 After=sys-subsystem-net-devices-.device
 Wants=sys-subsystem-net-devices-.device


Got the above info from

 systemctl --full | grep subsystem

Best regards!

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

Title:
  dnsmasq doesn't start on boot because its interface isn't up yet

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

Bug description:
  My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0
  is managed manually in /etc/network/interfaces.

  During boot, dnsmasq is started before br-vz0 is created and this
  causes dnsmasq to exit:

  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up
  Jan  5 08:56:17 simon-laptop NetworkManager[937]:   NetworkManager 
(version 1.0.4) is starting...
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]: 
interface-parser: parsing file /etc/network/interfaces
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   found bridge ports 
none for br-vz0
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   adding bridge port 
none to eni_ifaces
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   management mode: 
unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq 2.75-1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan  5 09:53:30 2016
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+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 1637258] Re: Side stage hides after rotating

2016-11-10 Thread Michal Predotka

Thanks for the quick fix! I've installed silo #2177 with this and other
bug fixes. I have one question regarding this issue though. When using
silo #2177, I noticed the app is visible in the side stage after
rotation only if that app is focused. But if an app is in the side stage
and the main app is focused, after rotating to portrait and back to
landscape, the side stage is hidden. I'm not sure if that's by design or
not?

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

Title:
  Side stage hides after rotating

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  bq M10 rc-proposed r219

  Steps to reproduce:
  1. Open an app
  2. Put it in the side stage
  3. Rotate the tablet to portrait
  At this point you should see the app which was in the side stage on the whole 
screen
  4. Rotate the tablet back to landscape

  Expected result:
  The app is visible in the side stage

  What happens instead:
  The side stage is closed but the app still has focus as its name is visible 
in the top bar (screenshot attached)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1637258/+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 1630324] Re: Broadcom wifi dies in 60s cycles with 4.8 kernel

2016-11-10 Thread hoxnox

I've got the same issue with my Dell XPS-15 (9550). The chip is
BCM43602.

I've flashed my router (Archer C7 v2) with dd-wrt (ftp://ftp.dd-
wrt.com/betas/2016/11-01-2016-r30826/tplink_archer-c7-v2/), configured
5Gz network as follows:

Wireless Mode: AP
Wireless Network Mode: AC/N-Mixed
Channel Width: Full (20 MHz)
Wireless Channel: 40-5200 MHz

And the problem is almost gone. The connection is fast and stable, but I
still getting error about ISO code.

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

Title:
  Broadcom wifi dies in 60s cycles with 4.8 kernel

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9350 with a Broadcom wifi adapter. Wifi connects
  fine, but dies for around 5-10s (the signal dies completely, tools
  like wavemon show "no interface data") in regular cycles of about 60s.
  dmesg logs the same brcmfmac errors every minute or so: "brcmfmac:
  brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)".

  network-manager's icon doesn't change however (remains as if the
  adapter was connected).

  This issue started to affect me when using kernel 4.8 on Ubuntu 16.04.
  I previously used kernel 4.7 and did not experience this bug.

  I booted the 16.10 daily build and experienced exactly the same
  errors.

  $ lspci | grep BCM4350
  3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless 
Network Adapter (rev 08)

  $ dmesg | grep brcm
  [5.864558] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 
22 2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176
  [5.898803] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  [   74.991987] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  [  142.503220] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  ...

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  Uname: Linux 4.8.0-040800-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct  4 14:15:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-26 (131 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.0.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev wlp58s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.0.29  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
Guava Guest 1  68ae8dc2-ab23-42ef-9e41-ac8e9d91385a  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --  
   ----
  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/1630324/+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 1640924] [NEW] MFC8600 Brother Prints OK first PDF job, second job prints garbage

2016-11-10 Thread Bryce Nesbitt

Public bug reported:

It's been like this for years. Some initialization problem between
driver and printer.

If I print certain types of documents the printer is fine.
If I print a pdf, it's fine.
If I print a second pdf, reams of paper spit out of the machine each with a few 
random characters on them.

Resetting CUPS or power cycling the printer fixes the issue for one printout.
Resetting CPUS ("sudo /etc/init.d/cups restart") fixes the issue for one 
printout.

I use the "Brother MFC-8600 Foomatic/hl7x0 (recommended)" driver.  Changing 
driver
does not... at least not for sure... fix the problem.

--

Or maybe it is an end job problem, as the printer often reports a state of
"Idle - Sending data to printer."
Hours after the last printout.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.7
ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
Uname: Linux 3.13.0-100-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CupsErrorLog:
 E [09/Nov/2016:09:07:28 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
 E [10/Nov/2016:09:18:42 -0800] [Job 2767] Unable to send data to printer.
 E [10/Nov/2016:09:23:43 -0800] [Job 2767] Stopping unresponsive job.
 E [10/Nov/2016:09:26:06 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
CurrentDesktop: Unity
Date: Thu Nov 10 11:37:50 2016
Lpstat:
 device for Brother-MFC-8600: 
ipps://Bryces-Mac-mini.local:631/printers/Brother_MFC_8600
 device for MFC-8600: usb://Brother/MFC-8600
 device for MFCJ985DW: dnssd://Brother%20MFC-J985DW._ipp._tcp.local/
MachineType: Supermicro X8SAX
Papersize: letter
PpdFiles:
 MFCJ985DW: Brother MFC-J985DW CUPS
 MFC-8600: Brother MFC-8600 Foomatic/hl7x0 (recommended)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic 
root=UUID=8a67d411-9750-46e4-8a53-b2059e5a4eeb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/17/10
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: X8SAX
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd09/17/10:svnSupermicro:pnX8SAX:pvr1234567890:rvnSupermicro:rnX8SAX:rvr2.0:cvnSupermicro:ct3:cvr1234567890:
dmi.product.name: X8SAX
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
mtime.conffile..etc.cups.cupsd.conf: 2015-01-21T15:19:58.577664

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


** Tags: amd64 apport-bug trusty

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

Title:
  MFC8600 Brother Prints OK first PDF job, second job prints garbage

Status in cups package in Ubuntu:
  New

Bug description:
  It's been like this for years. Some initialization problem between
  driver and printer.

  If I print certain types of documents the printer is fine.
  If I print a pdf, it's fine.
  If I print a second pdf, reams of paper spit out of the machine each with a 
few random characters on them.

  Resetting CUPS or power cycling the printer fixes the issue for one printout.
  Resetting CPUS ("sudo /etc/init.d/cups restart") fixes the issue for one 
printout.

  I use the "Brother MFC-8600 Foomatic/hl7x0 (recommended)" driver.  Changing 
driver
  does not... at least not for sure... fix the problem.

  --

  Or maybe it is an end job problem, as the printer often reports a state of
  "Idle - Sending data to printer."
  Hours after the last printout.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-100-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CupsErrorLog:
   E [09/Nov/2016:09:07:28 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
   E [10/Nov/2016:09:18:42 -0800] [Job 2767] Unable to send data to printer.
   E [10/Nov/2016:09:23:43 -0800] [Job 2767] Stopping unresponsive job.
   E [10/Nov/2016:09:26:06 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
  CurrentDesktop: Unity
  Date: Thu Nov 10 11:37:50 2016
  Lpstat:
   device for Brother-MFC-8600: 
ipps://Bryces-Mac-mini.local:631/printers/Brother_MFC_8600
   device for MFC-8600: usb://Brother/MFC-8600
   device for MFCJ985DW: dnssd://Brother%20MFC-J985DW._ipp._tcp.local/
  MachineType: Supermicro X8SAX
  Papersize: letter
  PpdFiles:
   MFCJ985DW: Brother MFC-J985DW CUPS
   MFC-8

[Touch-packages] [Bug 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

2016-11-10 Thread Steve Langasek

Hello Martin, or anyone else affected,

Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.20 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 on 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!

** Changed in: systemd (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in init-system-helpers package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in init-system-helpers source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  For init-system-helpers, the regression potential is near-zero: We
  never had (and never will) systemd as pid 1 in trusty, so deb-systemd-
  invoke was previously never called. It does get called now if you
  install Ubuntu packages that ship a systemd unit, so we need to make
  that a no-op to retain the current behaviour.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af
  haveged" should only have *one* process and "systemctl status haveged"
  should not be running (it should not exist, or not be enabled and be
  inactive). [This part also needs the updated init-system-helpers].

     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.

   5. Ensure that the standard targets are active, as that is where
  third-party/snap services hook into:

  systemctl status sysinit.target multi-user.target default.target

   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and
  ensure you can install a snap, and its services start after installing
  the snap and after rebooting.

   7. Run "sudo apt-get install --reinstall systemd" to ensure that
  upgrades to newer systemd trusty versions work. The running systemd
  should *not* be restarted as that would disrupt snapd and its services
  (verify that the pid in "initctl status systemd" is the same before
  and after the upgrade).

   8. Run "sudo apt install -y colord && sudo apt purge -y colord". This
  should succeed.

   9. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
  dependency issues, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/161

[Touch-packages] [Bug 1640888] Re: package libnss3-1d:amd64 2:3.23-0ubuntu0.14.04.1 failed to install/upgrade: package libnss3-1d:amd64 is already installed and configured

2016-11-10 Thread dino99

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

** This bug has been marked a duplicate of bug 1635280
   [ BUG 541595 IS BACK ] package is already installed and configured

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

Title:
  package libnss3-1d:amd64 2:3.23-0ubuntu0.14.04.1 failed to
  install/upgrade: package libnss3-1d:amd64 is already installed and
  configured

Status in nss package in Ubuntu:
  New

Bug description:
  m,

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libnss3-1d:amd64 2:3.23-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-101-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Thu Nov 10 19:04:50 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DuplicateSignature: package:libnss3-1d:amd64:2:3.23-0ubuntu0.14.04.1:package 
libnss3-1d:amd64 is already installed and configured
  ErrorMessage: package libnss3-1d:amd64 is already installed and configured
  InstallationDate: Installed on 2016-11-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: nss
  Title: package libnss3-1d:amd64 2:3.23-0ubuntu0.14.04.1 failed to 
install/upgrade: package libnss3-1d:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1640888/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1629510] Re: pulseaudio crashed with SIGABRT in pa_cvolume_set()

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

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

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_cvolume_set()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I was trying to connect my Bluetooth headset

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   e-evil 2651 F...m pulseaudio
   /dev/snd/controlC1:  e-evil 2651 F pulseaudio
   /dev/snd/controlC0:  e-evil 2651 F pulseaudio
  Date: Sat Oct  1 06:33:25 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-05-17 (136 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160517)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_cvolume_set () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-9.0.so
   ?? () from /usr/lib/pulse-9.0/modules/module-bluez5-device.so
   pa_hook_fire () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-9.0.so
   ?? () from /usr/lib/pulse-9.0/modules/libbluez5-util.so
   pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
  Title: pulseaudio crashed with SIGABRT in pa_cvolume_set()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A75-V EVO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd05/27/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A75-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1629510/+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 1443052] Re: User accounts login history showing incorrect history - patch

This bug was fixed in the package accountsservice - 0.6.35-0ubuntu7.3

---
accountsservice (0.6.35-0ubuntu7.3) trusty; urgency=medium

  * debian/patches/wtmp-fix-logout.patch:
 - Backport 0.6.43 commit to fix logout records when a user
   shuts down or restarts their computer (LP: #1443052)

 -- Nikita Yerenkov-Scott   Mon, 31 Oct 2016
20:12:38 +

** Changed in: accountsservice (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.
  [bdmurray] - What could go wrong? What should a user testing this look for?

  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1443052] Update Released

2016-11-10 Thread Brian Murray

The verification of the Stable Release Update for accountsservice 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 accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1443052

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.
  [bdmurray] - What could go wrong? What should a user testing this look for?

  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1443052] Re: User accounts login history showing incorrect history - patch

This bug was fixed in the package accountsservice - 0.6.40-2ubuntu11.3

---
accountsservice (0.6.40-2ubuntu11.3) xenial; urgency=medium

  * debian/patches/wtmp-fix-logout.patch:
- Backport 0.6.43 commit to fix logout records when a user
  shuts down or restarts their computer (LP: #1443052)

 -- Nikita Yerenkov-Scott   Tue, 25 Oct 2016
16:15:26 +0100

** Changed in: accountsservice (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 accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1443052

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.
  [bdmurray] - What could go wrong? What should a user testing this look for?

  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

2016-11-10 Thread System76

This affects the entire System76 product line, including:

Lemur 6, Lemur 7, Gazelle 10, Gazelle 11, Kudu 2, Kudu 3, Serval 10,
Bonobo 10, Bonobo 11, Meerkat 2, Sable 6, Ratel 5, and other desktop
hardware with additional wifi cards added.

To reproduce:

- Install Ubuntu in OEM mode
- Prepare for shipping to end user
- Power off system
- Power on system.
- Go through user setup
- Either join or don't join a Wifi during user setup, does not change outcome
- Log into user account
- Try to join a WiFi network

No wifi networks will be shown.

This affects Ubuntu 16.04.1 and 16.10, including the following kernels:

4.8.0-26-generic
4.8.0-22-generic
4.4.0-35-generic
4.4.0-47-generic

Looking at log messages, there may be a race condition present that a
fresh boot does not have.  On first boot:

[8.824974] iwlwifi :03:00.0 wlp3s0: renamed from wlan0
[9.133313] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[9.206671] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[9.324861] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready


On reboot:

[3.515363] iwlwifi :03:00.0 wlp3s0: renamed from wlan0
[4.386126] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[4.610799] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[4.712271] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[7.614299] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link becomes ready


It appears that the system gives up/times out trying to make the device ready 
when being booted the first time, but the process happens much faster on later 
reboots.

This is solved by either rebooting, or restarting network-manager, as
indicated above.

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

2016-11-10 Thread System76

Our systems contain an Intel 8260, 7260, or 3165 Wifi card, and this bug
affects all 3 cards.

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

2016-11-10 Thread olfa hedde

** Branch unlinked: lp:~mardy/gnome-control-center-
signon/username-1565772

** Branch unlinked: lp:~mardy/account-plugins/usernames-1565772

** Branch unlinked: lp:~ci-train-bot/account-plugins/account-plugins-
ubuntu-xenial-landing-062

** Branch unlinked: lp:~ci-train-bot/gnome-control-center-signon/gnome-
control-center-signon-ubuntu-xenial-landing-062

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Fix Committed
Status in gnome-control-center-signon source package in Xenial:
  Fix Committed
Status in account-plugins source package in Yakkety:
  Fix Released
Status in gnome-control-center-signon source package in Yakkety:
  Fix Released

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+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 1640890] [NEW] Samsung-C460-Series does not print

You have been subscribed to a public bug:

Gives error message paper jam in tray 1although therre is actually no
paper when i remove the tray.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity 7.4.0+16.04.20160906-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-45.66-lowlatency 4.4.21
Uname: Linux 4.4.0-45-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Nov 10 19:07:51 2016
InstallationDate: Installed on 2015-08-26 (442 days ago)
InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial
-- 
Samsung-C460-Series does not print
https://bugs.launchpad.net/bugs/1640890
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups in Ubuntu.

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

[Touch-packages] [Bug 1640890] Re: Samsung-C460-Series does not print

2016-11-10 Thread Paul White

** Package changed: unity (Ubuntu) => cups (Ubuntu)

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

Title:
  Samsung-C460-Series does not print

Status in cups package in Ubuntu:
  New

Bug description:
  Gives error message paper jam in tray 1although therre is actually no
  paper when i remove the tray.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-lowlatency 4.4.21
  Uname: Linux 4.4.0-45-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov 10 19:07:51 2016
  InstallationDate: Installed on 2015-08-26 (442 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1640890/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

UseHostname: is currently broken anyway
(https://github.com/systemd/systemd/issues/4646), so letting networkd
start earlier than dbus.service does not actually regress anything for
now. This will be different once #4646 gets fixed, as then this will
break functionality.

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

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  In Progress
Status in cloud-init source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  
  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
└─basic.target @11.403s
  └─sockets.target @11.401s
└─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
└─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
└─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
└─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
└─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
└─system.slice @783ms
  └─-.slice @721ms

  
  cloud-init would need networkd to run at or before 'networking.service' so it 
can raise networking to then find and use network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list 
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init /usr/share/snappy/dpkg.list 
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances

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

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

[Touch-packages] [Bug 1639472] Re: Alarm should provide GAction for toggling them

2016-11-10 Thread Charles Kerr

Marco, could you explain more what you're asking for here? A way to
toggle on/off whether alarms will go off?

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

Title:
  Alarm should provide GAction for toggling them

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Indicator-datetime should provide a GAaction for toggling the
  activation of alarms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1639472/+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 1611466] Re: Calendar crashes on ESC typing.

2016-11-10 Thread Charles Kerr

I'm marking this bug as closed due to your last comment on no longer
being able to reproduce it, either through an update or some other
reason. If the problem reappears for you in the future, please submit a
backtrace using the method linked to by seb128 in the comment above.
Thank you again for taking the time to report this bug and helping to
make Ubuntu better. Please submit any future bugs you may find.

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Calendar crashes on ESC typing.

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  When you click on date, it opens the calendar, if you type the ESC
  button on keyboard, the graphical interface crashes and in a few
  seconds it restart. During this few seconds or a minute, all the
  system stay frozen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1611466/+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 1639472] Re: Alarm should provide GAction for toggling them

2016-11-10 Thread Treviño

Charles, yes.

Basically new desing requires toggalble alarms using a switch from the
indicator. So we'd need the backend to do provide an action in order to
do that.

Devid volunteered to help, but if this is a too big change I can handle
that too.

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

Title:
  Alarm should provide GAction for toggling them

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Indicator-datetime should provide a GAaction for toggling the
  activation of alarms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1639472/+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 1640966] [NEW] package linux-image-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2016-11-10 Thread Harald Riedel

*** This bug is a security vulnerability ***

Private security bug reported:

1. Rebooting Ubunto
2. Klick on Software Updater
3. Informaiton  about Updates of more then 200 MB 
4. o.k.
5. Problemreport (I remembrer in intramfs-tools, but maybe later other 
packages, after some reboots)


6. Reboot
2. Klick on Software Update
3. Information about Update ca. 130 MB
4. o.k.
5. Problem Report

and so on.

Now it is shown that I have all Updates.

But, may that is wrong and the Bug is there.

Pleas send me a feedback.

Kind regards

Harald

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-47-generic 4.4.0-47.68
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  harald 1692 F pulseaudio
 /dev/snd/controlC0:  harald 1692 F pulseaudio
Date: Thu Nov 10 23:46:31 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=c9bfefc2-2076-4868-9edc-bd080f7a0a74
InstallationDate: Installed on 2016-05-08 (186 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
MachineType: LENOVO 20CM004UGE
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=762d0ab6-989f-4adb-ab57-38517101538b 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-4.4.0-47-generic 4.4.0-47.68 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/26/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N10ET42W (1.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CM004UGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET42W(1.21):bd02/26/2016:svnLENOVO:pn20CM004UGE:pvrThinkPadX250:rvnLENOVO:rn20CM004UGE:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20CM004UGE
dmi.product.version: ThinkPad X250
dmi.sys.vendor: LENOVO

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


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

** Information type changed from Public to Private Security

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

Title:
  package linux-image-4.4.0-47-generic 4.4.0-47.68 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:
  1. Rebooting Ubunto
  2. Klick on Software Updater
  3. Informaiton  about Updates of more then 200 MB 
  4. o.k.
  5. Problemreport (I remembrer in intramfs-tools, but maybe later other 
packages, after some reboots)

  
  6. Reboot
  2. Klick on Software Update
  3. Information about Update ca. 130 MB
  4. o.k.
  5. Problem Report

  and so on.

  Now it is shown that I have all Updates.

  But, may that is wrong and the Bug is there.

  Pleas send me a feedback.

  Kind regards

  Harald

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  harald 1692 F pulseaudio
   /dev/snd/controlC0:  harald 1692 F pulseaudio
  Date: Thu Nov 10 23:46:31 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=c9bfefc2-2076-4868-9edc-bd080f7a0a74
  InstallationDate: Installed on 2016-05-08 (186 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20CM004UGE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=762d0ab6-989f-4adb-ab57-38517101538b 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-4.4.0-47-generic 4.4.0-47.68 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upg

[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-11-10 Thread Michael Terry

** Also affects: address-book-service (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1629009] Re: Does not work inside a snap due to hardcoded paths

** Branch linked: lp:~mterry/address-book-service/snap-root

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1640970] [NEW] 16.10: VPN Connections -> Configure VPN grayed out

2016-11-10 Thread Adam Jacobs

Public bug reported:

After upgrading from 16.04 to 16.10, in the nm applet menu, VPN
Connections -> Configure VPN is grayed out.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Nov 10 16:04:49 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-04-04 (951 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
IpRoute:
 default via 172.28.77.1 dev wlan0  proto static  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 172.28.77.0/24 dev wlan0  proto kernel  scope link  src 172.28.77.23  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2016-11-07 (3 days ago)
modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-07T11:36:55.286063
nmcli-dev:
 DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
 wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/0  
BlueCedar-GUEST  f7b79954-9427-47eb-adba-875b5b152f37  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 eth0ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/1  --  
 ----   
  
 lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  --  
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  16.10: VPN Connections -> Configure VPN grayed out

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading from 16.04 to 16.10, in the nm applet menu, VPN
  Connections -> Configure VPN is grayed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 10 16:04:49 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-04 (951 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  IpRoute:
   default via 172.28.77.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.28.77.0/24 dev wlan0  proto kernel  scope link  src 172.28.77.23  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-11-07 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-07T11:36:55.286063
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/0  
BlueCedar-GUEST  f7b79954-9427-47eb-adba-875b5b152f37  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths