[Touch-packages] [Bug 1585886] Re: WiFi indicator icon disappears in Ubuntu 16.04

2016-08-04 Thread Robert Orzanna
So, it has to do something with the Ethernet connection in your case?

Weird, I can't test it, unfortunately, as I don't use any Ethernet.

~Robert

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

Title:
  WiFi indicator icon disappears in Ubuntu 16.04

Status in indicator-applet package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  Dear all,

  Can someone confirm an occasionally missing WiFi indicator tray icon?

  Sometimes it happens that the icon is not displayed although the WiFi
  connection is working.

  Please see also the attached screenshot.

  Warmly,

  ~Robert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1585886/+subscriptions

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


[Touch-packages] [Bug 1610066] [NEW] gst-plugins-bad1.0 ftbfs on yakkety

2016-08-04 Thread Jeremy Bicha
Public bug reported:

gst-plugins-bad1.0 fails to build from source on i386 and armhf because
of a problem with the android hybris support. This build was a no-change
rebuild for the libwebp transition.

https://launchpad.net/ubuntu/+source/gst-plugins-bad1.0/1.8.2-1ubuntu3

configure: *** checking feature: Android Media Hybris ***
configure: *** for plug-ins: androidmediahybris ***
checking hybris/media/media_codec_layer.h usability... no
checking hybris/media/media_codec_layer.h presence... yes
configure: WARNING: hybris/media/media_codec_layer.h: present but cannot be 
compiled
configure: WARNING: hybris/media/media_codec_layer.h: check for missing 
prerequisite headers?
configure: WARNING: hybris/media/media_codec_layer.h: see the Autoconf 
documentation
configure: WARNING: hybris/media/media_codec_layer.h: section "Present But 
Cannot Be Compiled"
configure: WARNING: hybris/media/media_codec_layer.h: proceeding with the 
compiler's result
configure: WARNING: ## 
 ##
configure: WARNING: ## Report this to 
http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer ##
configure: WARNING: ## 
 ##
checking for hybris/media/media_codec_layer.h... no
configure: *** These plugins will not be built: androidmediahybris

The previous successful build used libhybris
0.1.0+git20151016+6d424c9-0ubuntu14 and platform-api
3.0.1+16.10.20160613-0ubuntu1

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: High
 Status: New

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


** Tags: ftbfs

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

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

Title:
  gst-plugins-bad1.0 ftbfs on yakkety

Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in libhybris package in Ubuntu:
  New

Bug description:
  gst-plugins-bad1.0 fails to build from source on i386 and armhf
  because of a problem with the android hybris support. This build was a
  no-change rebuild for the libwebp transition.

  https://launchpad.net/ubuntu/+source/gst-plugins-bad1.0/1.8.2-1ubuntu3

  configure: *** checking feature: Android Media Hybris ***
  configure: *** for plug-ins: androidmediahybris ***
  checking hybris/media/media_codec_layer.h usability... no
  checking hybris/media/media_codec_layer.h presence... yes
  configure: WARNING: hybris/media/media_codec_layer.h: present but cannot be 
compiled
  configure: WARNING: hybris/media/media_codec_layer.h: check for missing 
prerequisite headers?
  configure: WARNING: hybris/media/media_codec_layer.h: see the Autoconf 
documentation
  configure: WARNING: hybris/media/media_codec_layer.h: section "Present 
But Cannot Be Compiled"
  configure: WARNING: hybris/media/media_codec_layer.h: proceeding with the 
compiler's result
  configure: WARNING: ## 
 ##
  configure: WARNING: ## Report this to 
http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer ##
  configure: WARNING: ## 
 ##
  checking for hybris/media/media_codec_layer.h... no
  configure: *** These plugins will not be built: androidmediahybris

  The previous successful build used libhybris
  0.1.0+git20151016+6d424c9-0ubuntu14 and platform-api
  3.0.1+16.10.20160613-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1610066/+subscriptions

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


[Touch-packages] [Bug 1610065] [NEW] display problems

2016-08-04 Thread Dharmendra Mishra
Public bug reported:

from my settings -> displays output shows could not get screen information
but when opened from top title bar system settings shows setting details.
i am using acer p166hql monitor. motherboard is express g33 chipset

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Aug  5 10:27:03 2016
DistUpgraded: 2016-08-02 12:13:30,790 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 
(rev 10) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation 82G33/G31 Express Integrated Graphics 
Controller [1849:29c2]
InstallationDate: Installed on 2016-05-29 (67 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=247ca8e0-230b-4661-8e58-f7c781c801fa ro plymouth:debug drm.debug=0xe 
init=/sbin/upstart
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-08-02 (2 days ago)
dmi.bios.date: 07/08/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: G31M-S.
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG31M-S.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Aug  5 09:15:56 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech Dell Wireless Mouse WM123 MOUSE, id 8
 inputLogitech Dell Wireless Mouse WM123 KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 630 
 vendor ACR
xserver.version: 2:1.18.3-1ubuntu2.2

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


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

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

Title:
  display problems

Status in xorg package in Ubuntu:
  New

Bug description:
  from my settings -> displays output shows could not get screen information
  but when opened from top title bar system settings shows setting details.
  i am using acer p166hql monitor. motherboard is express g33 chipset

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Aug  5 10:27:03 2016
  DistUpgraded: 2016-08-02 12:13:30,790 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 

[Touch-packages] [Bug 1609044] Re: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

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

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

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

Title:
  package click 0.4.43+16.04.20160203-0ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  Confirmed

Bug description:
  Upgrade from 14.4 to 16.4.1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: click 0.4.43+16.04.20160203-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug  2 14:06:29 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2014-09-04 (698 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: click
  Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (0 days ago)

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

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


[Touch-packages] [Bug 1610059] [NEW] no icons on desktop

2016-08-04 Thread 袁桦斌
Public bug reported:

cannot see anything

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic i686
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
BootLog:
 Scanning for Btrfs filesystems
 /dev/sda3: clean, 344593/4587520 files, 2456090/18326016 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Aug  5 12:34:46 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, i686: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, i686: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-34-generic, i686: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02d8]
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02d8]
InstallationDate: Installed on 2016-08-02 (2 days ago)
InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
MachineType: Dell Inc. Vostro 1220
ProcEnviron:
 LANGUAGE=zh_CN:
 PATH=(custom, no user)
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=110f42be-2342-422d-94b6-fa37bed8b495 ro locale=zh_CN quiet splash 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0X482M
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/15/2009:svnDellInc.:pnVostro1220:pvr:rvnDellInc.:rn0X482M:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Vostro 1220
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Aug  5 11:14:38 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   14100 
 vendor AUO
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: apport-bug i386 ubuntu xenial

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

Title:
  no icons on desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  cannot see anything

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic i686
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog:
   Scanning for Btrfs filesystems
   /dev/sda3: clean, 344593/4587520 files, 2456090/18326016 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Aug  5 12:34:46 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, i686: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, i686: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-34-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02d8]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02d8]
  InstallationDate: Installed on 2016-08-02 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: Dell Inc. Vostro 1220
  ProcEnviron:
   LANGUAGE=zh_CN:
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=110f42be-2342-422d-94b6-fa37bed8b495 ro locale=zh_CN 

[Touch-packages] [Bug 1609215] Re: Merge grilo-plugins 0.3.2-1 (main) from Debian unstable (main)

2016-08-04 Thread Jeremy Bicha
** Changed in: rhythmbox (Ubuntu)
   Status: New => Fix Committed

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

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

Title:
  Merge grilo-plugins 0.3.2-1 (main) from Debian unstable (main)

Status in grilo-plugins package in Ubuntu:
  Fix Committed
Status in rhythmbox package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Fix Committed

Bug description:
  Please merge grilo-plugins 0.3.2-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta:
* No-change rebuild against libgrilo-0.3-0
* d/p/0003-Revert-apple-trailers-Remove-stand-alone-C-apple-tra.patch: 
revert standalone
  C plugin, will look at moving lua-factory into -base next cycle (LP: 
1570157)
* debian/rules: don't install lua apple-trailers for now.
* d/p/0003-Revert-apple-trailers-Remove-stand-alone-C-apple-tra.patch: 
revert standalone
  C plugin, will look at moving lua-factory into -base next cycle (LP: 
1570157)
* debian/rules: don't install lua apple-trailers for now.
* New upstream release
* debian/control: Bump build-deps on libglib2.0-dev (>= 2.44), 
libgoa-1.0-dev (>= 3.17.91)
  and liblua5.3-dev. Drop build-dep on librest-dev.
* Update .install files for removed/renamed plugins
* debian/patches:
  - Drop git patches included in new version
  - video_sanitise_string-crash.patch, Dropped, affected function has been
removed
  - Cherry-pick git patches to fix build failures
* debian/rules: Remove obsolete --disable-bliptv configure flag
* Disable bliptv plugin this service has been shutdown (LP: #1498562)
* Merge from Debian unstable.  Remaining changes:
  - Split package into -base and -extra
  - Build with --fail-missing so we install everything.
  - debian/patches/0001-guardianvideos-fix-URL-format-string.patch:
Cherry-pick. guardianvideos: fix URL format string The online service
complains loudly if passed 1.0 instead of 1, let's make sure values are
formatted as integers.
* 
debian/patches/0001-grl-bookmarks-Notify-about-a-removal-if-there-was-no.patch:
  Take patch from upstream bug to fix notification of deletions.

  Remaining delta:
* Merge with Debian unstable.  Remaining changes:
  - Split package into -base and -extra
  - Build with --fail-missing to ensure we install everything.
* Have grilo-plugins-0.3-base install the Lua plugins (LP: #1570157)

  Changelog entries since current yakkety version 0.2.17-0ubuntu3:

  grilo-plugins (0.3.2-1) unstable; urgency=medium

* New upstream release.
* debian/control:
  - Require libgrilo 0.3.1.
  - Add build dependencies for the new chromaprint plugin:
libgstreamer1.0-dev, gstreamer1.0-tools, gstreamer1.0-plugins-bad.
  - List new plugins in the package description: Chromaprint, Acoustid,
iTunes Podcast, TheGamesDB.net.
* Drop the patch that allows co-installation with grilo-plugins 0.2.
  This was a temporary fix for the transition and it is no longer
  necessary.
  - debian/patches/v0.2-coinstall.patch:
+ Remove.
  - debian/install:
+ Update installation path.
  - debian/rules:
+ Don't rename example-tmdb.c anymore.
  - debian/control:
+ Make this package break and replace grilo-plugins-0.2.
* debian/copyright:
  - Update copyright attributions.

   -- Alberto Garcia   Mon, 20 Jun 2016 12:30:01 +0300

  grilo-plugins (0.3.1-1) unstable; urgency=medium

* New upstream release.
* debian/patches/fix-double-free.patch,
  debian/patches/fix-lua-factory-leak.patch:
  - Remove these patches, they are included in this release.
* debian/patches/v0.2-coinstall.patch
  - Refresh.
* debian/copyright:
  - Update copyright years and add missing attributions.
* debian/control:
  - Update build dependency on libgom to 0.3.2.
  - Update Standards-Version to 3.9.8.

   -- Alberto Garcia   Sun, 24 Apr 2016 21:35:49 +0300

  grilo-plugins (0.3.0-1.1) unstable; urgency=medium

* Non-maintainer upload.
* Upload to unstable.

   -- Michael Biebl   Tue, 19 Apr 2016 15:34:37 +0200

  grilo-plugins (0.3.0-1) experimental; urgency=medium

* New upstream release.
  - Rename grilo-plugins-0.2 to grilo-plugins-0.3.
* debian/control:
  - Downgrade build dependency on debhelper to >= 9, we are not
overriding dh_strip anymore.
* debian/patches:
  - Refresh all patches.
* Allow co-installing with grilo-plugins-0.2 by renaming all files and
  directories that have the same name. This is a temporary change that
  can be reverted once the transition to grilo-plugins-0.3 is complete.
  - 

[Touch-packages] [Bug 1576864] Re: Unable to extend to second display

2016-08-04 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Unable to extend to second display

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Upgrading from UbuntuStudio 15.10 to 16.04, my 2nd display is a no
  more a 1st display extension and only a clone. xrand detects only one
  display.

  $ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050
  default connected 1400x1050+0+0 0mm x 0mm
 1400x1050 77.00* 
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644]
  $ dmesg | egrep 'drm|radeon'
  [1.293303] [drm] Initialized drm 1.1.0 20060810
  [1.328085] [drm] VGACON disable radeon kernel modesetting.
  [1.328109] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
  [   12.801460] [drm] VGACON disable radeon kernel modesetting.
  [   12.801484] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
  $ uname -r 
  4.4.0-21-lowlatency
  $ 

  Seems same than bug 1407505, but apport-bug failed, so I created a new
  bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Apr 29 23:19:49 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (252 days ago)
  InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (5 days ago)

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

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


[Touch-packages] [Bug 1598181] Re: No network showing from the dialer app even though phone calls are possible

2016-08-04 Thread Seth
Attaching Video File

** Attachment added: "Video File"
   
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1598181/+attachment/4714463/+files/NoNetwork.mp4

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

Title:
  No network showing from the dialer app even though phone calls are
  possible

Status in Canonical System Image:
  Confirmed
Status in dialer-app package in Ubuntu:
  Triaged
Status in indicator-network package in Ubuntu:
  New
Status in ofono package in Ubuntu:
  Confirmed

Bug description:
  I noticed that I am seeing "No network" being displayed in the upper
  right hand corner of the dialer app even though I am able to make
  phone calls. This is on turbo and using the smaller SIM slot (#2) with
  T-Mobile in the US.

  Build version info:

  current build number: 116
  device name: turbo
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2016-07-01 09:38:31
  version version: 116
  version ubuntu: 20160701
  version device: 20160617-82a5c0d
  version custom: 20160701

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598181/+subscriptions

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


[Touch-packages] [Bug 1598181] Re: No network showing from the dialer app even though phone calls are possible

2016-08-04 Thread Seth
I have created a video and log file to demonstrate some of the behavior.

Step 1: Notice "No Network" at dialer screen for "SIM 2 AT" "SIM 1 Cricket" 
shows connected
Step 2: Visually verify connections
Step 3: Select SIM 2 AT at the dialer screen
Step 4: Successfully dial the US Naval Observatory Time Announcer to verify 
connection to AT network
Step 5: Hang up
Step 6: Visually verify that "No Network" is still displayed for "SIM 2 AT"

This happens no matter which SIM card is in which slot. In this
instance, AT was not showing service. However, Cricket and T-Mobile
will exhibit the same behavior of "No Network" yet successfully make
phone calls.

** Attachment added: "Log File"
   
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1598181/+attachment/4714462/+files/application-legacy-dialer-app.log

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

Title:
  No network showing from the dialer app even though phone calls are
  possible

Status in Canonical System Image:
  Confirmed
Status in dialer-app package in Ubuntu:
  Triaged
Status in indicator-network package in Ubuntu:
  New
Status in ofono package in Ubuntu:
  Confirmed

Bug description:
  I noticed that I am seeing "No network" being displayed in the upper
  right hand corner of the dialer app even though I am able to make
  phone calls. This is on turbo and using the smaller SIM slot (#2) with
  T-Mobile in the US.

  Build version info:

  current build number: 116
  device name: turbo
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2016-07-01 09:38:31
  version version: 116
  version ubuntu: 20160701
  version device: 20160617-82a5c0d
  version custom: 20160701

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598181/+subscriptions

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


[Touch-packages] [Bug 1606489] Re: Right clicking on the webbrowser-app location bar, the popup is blurry (e.g. Select All, Paste)

2016-08-04 Thread Daniel van Vugt
The blurry problem persists in webbrowser-app under Unity7 too. It's an
app bug.

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

Title:
  Right clicking on the webbrowser-app location bar, the popup is blurry
  (e.g. Select All, Paste)

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Right clicking on the location bar, the popup is blurry (e.g. Select
  All, Paste). It looks like the pop-up is not pixel-aligned.

  The rest of the app, including right clicking on a web page is clear
  and has no such problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1606489/+subscriptions

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


[Touch-packages] [Bug 1308111] Re: Unity 8 Desktop Preview has no screensaver/automatic lockscreen

2016-08-04 Thread Daniel van Vugt
Suddenly this is fixed on yakkety.

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

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

** Changed in: unity8-desktop-session (Ubuntu)
   Status: Confirmed => Fix Released

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

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

Title:
  Unity 8 Desktop Preview has no screensaver/automatic lockscreen

Status in Canonical System Image:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Logging in to the Unity 8 Desktop Preview session the screen remains
  on 24x7.  No screensaver, screen blanking, or sleep ever appears to
  happen.  No lockscreen ever appears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1308111/+subscriptions

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


[Touch-packages] [Bug 1610052] [NEW] Horizontal two-finger scrolling direction is backwards (but only in Qt Mir apps)

2016-08-04 Thread Daniel van Vugt
Public bug reported:

Horizontal two-finger scrolling direction is backwards (but only in Qt
Mir apps)

Test case:
  1. Open webbrowser-app and resize it small so you have both horizontal and 
vertical scrollbars.
  2. Using a touchpad try scrolling up/down/left/right

Expected: Vertical and horizontal scrolling in the direction of the two-finger 
guesture.
Observed: Vertical scrolling is in the direction of the gesture, but horiztonal 
scrolling goes the other way ("Australian scrolling").

This bug only occurs in Unity8. Under Unity7 the webbrowser-app scrolls
in the correct direction (when "Natural scrolling" is turned off).

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

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


** Tags: unity8-desktop

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

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

** Description changed:

  Horizontal two-finger scrolling direction is backwards (but only in Qt
  Mir apps)
  
  Test case:
-   1. Open webbrowser-app and resize it small so you have both horizontal and 
vertical scrollbars.
-   2. Using a touchpad try scrolling up/down/left/right
+   1. Open webbrowser-app and resize it small so you have both horizontal and 
vertical scrollbars.
+   2. Using a touchpad try scrolling up/down/left/right
  
  Expected: Vertical and horizontal scrolling in the direction of the 
two-finger guesture.
  Observed: Vertical scrolling is in the direction of the gesture, but 
horiztonal scrolling goes the other way ("Australian scrolling").
  
  This bug only occurs in Unity8. Under Unity7 the webbrowser-app scrolls
- in the correct direction.
+ in the correct direction (when "Natural scrolling" is turned off).

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

Title:
  Horizontal two-finger scrolling direction is backwards (but only in Qt
  Mir apps)

Status in Canonical System Image:
  New
Status in qtmir package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New

Bug description:
  Horizontal two-finger scrolling direction is backwards (but only in Qt
  Mir apps)

  Test case:
    1. Open webbrowser-app and resize it small so you have both horizontal and 
vertical scrollbars.
    2. Using a touchpad try scrolling up/down/left/right

  Expected: Vertical and horizontal scrolling in the direction of the 
two-finger guesture.
  Observed: Vertical scrolling is in the direction of the gesture, but 
horiztonal scrolling goes the other way ("Australian scrolling").

  This bug only occurs in Unity8. Under Unity7 the webbrowser-app
  scrolls in the correct direction (when "Natural scrolling" is turned
  off).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1610052/+subscriptions

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


[Touch-packages] [Bug 1610005] Re: Remove gtk3's versioned dependency of on adwaita-icon-theme

2016-08-04 Thread Jeremy Bicha
** Also affects: lubuntu-artwork
   Importance: Undecided
   Status: New

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

Title:
  Remove gtk3's versioned dependency of on adwaita-icon-theme

Status in Lubuntu Artwork:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Impact
  ===
  libgtk-3-common depends on adwaita-icon-theme (>= ${gnome:Version}). For 
xenial, this is adwaita-icon-theme >= 3.18.

  This causes 2 problems. One is that we have to remember to upload a
  new version of adwaita-icon-theme before we upload a new version of
  GTK3. Otherwise, the new version of adwaita-icon-theme becomes
  unbuildable because adwaita-icon-theme depends on GTK3 to build but
  GTK3 is uninstallable because the dependency can't be satisfied yet.
  This can be worked around (it happened this week with 3.20 in yakkety)
  but it's not good.

  The other is that Lubuntu doesn't want to install adwaita-icon-theme
  but instead install lubuntu-icon-theme as a replacement by setting
  Provides: adwaita-icon-theme. According to Debian policy, that doesn't
  work if something has a versioned dependency on the provided package.

  https://www.debian.org/doc/debian-policy/ch-
  relationships.html#s-virtual

  The versioned dependency was removed in Debian svn: 
  
https://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gtk%2B3.0/debian/control.in?r1=49406=49410

  Test case
  =
  Since the xenial daily images use -proposed, check here whether 
adwaita-icon-theme is installed a day or two after the gtk update has been 
pushed to xenial-proposed:

  http://cdimage.ubuntu.com/lubuntu/xenial/daily-live/current/xenial-
  desktop-amd64.manifest

  Regression potential
  
  If in fact, lubuntu-icon-theme does not include some of the icons in 
adwaita-icon-theme, there will be missing icons in apps that try to use those 
icons.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-common 3.18.9-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  4 18:55:25 2016
  InstallationDate: Installed on 2016-07-31 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-artwork/+bug/1610005/+subscriptions

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


[Touch-packages] [Bug 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)

2016-08-04 Thread Daniel van Vugt
Further to comment #30, the "preferred" solution of SimpleDRM is making a 
comeback (but doesn't yet exist in anyone's kernel):
  https://lists.freedesktop.org/archives/dri-devel/2016-August/114861.html

It doesn't have to be the only option though. We can still do an
fbdev+osmesa driver in the meantime that will work with current kernels
instead of having to wait for some future kernel.

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

Title:
  [enhancement] Mir lacks a software rendering backend (and doesn't work
  in virtual machines)

Status in Canonical System Image:
  New
Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  As always, it's a critical requirement for Ubuntu to be able to render
  the same thing on any machine (metal or virtual), regardless of the
  availability of hardware acceleration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1118903/+subscriptions

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


[Touch-packages] [Bug 1539811] Re: Mir crashed with std::exception::what: Couldn't clear output eDP-1 (drmModeSetCrtc = -13)

2016-08-04 Thread Daniel van Vugt
Another report of the same crash came in today.

Perhaps we need a fix like that of bug 1579630.

** Summary changed:

- Mir crashed with std::exception::what: Couldn't clear output eDP-1 
(drmModeSetCrtc = -13)
+ Mir/unity-system-compositor crashed with std::exception::what: Couldn't clear 
output eDP-1 (drmModeSetCrtc = -13)

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

Title:
  Mir/unity-system-compositor crashed with std::exception::what:
  Couldn't clear output eDP-1 (drmModeSetCrtc = -13)

Status in Mir:
  Confirmed
Status in Unity System Compositor:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  This is a live USB environment (16.04, 2016-01-29 image). HP Envy x360
  hybrid notebook. Package installed: 1.0.12+15.10.20150609-0ubuntu1 .

  After installing the mir desktop session package and choosing
  "logout", the greeter correctly shows Unity8 as a login option. After
  entering "ubuntu" and a blank password, the screen goes to black (with
  backight), the fan runs for a few seconds of high activity, and no
  graphical session ever actually starts.  The other tty screens remain
  available, and lightdm is eventually able to restart (though only
  after some time, and it is unclear if the commands to restart it are
  actually helping).

  Some selected error messages from the time of session login:

  *From lightdm.log*:
  [+158.12s] DEBUG: Session pid=6899: Greeter requests session unity8-mir
  [+158.12s] CRITICAL: g_dbus_connection_call_sync_internal: assertion 
'object_path != NULL && g_variant_is_object_path (object_path)' failed

  *From unity-system-compositor.log*:
  dm_connection_start
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: write: Broken pipe
  ...
  Closing session GDK-Mir
  ERROR: 
/build/mir-UeyFew/mir-0.19.0+16.04.20160128/src/common/fatal/fatal.cpp(55): 
Throw in function void mir::fatal_error_except(const char*, ...)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Couldn't clear output eDP-1 (drmModeSetCrtc = -13)

  *From syslog*:
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: Failed to connect 
to Mir: Failed to connect to server socket: No such file or directory
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: Unable to init 
server: Could not connect: Connection refused
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: 
(notify-osd:7672): Gtk-WARNING **: cannot open display:
  Jan 29 22:40:42 ubuntu dbus[1325]: [system] Activating service 
name='com.canonical.SystemImage' (using servicehelper)
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: usage: 
system-image-dbus [-h] [--version] [-C DIRECTORY] [-v]
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: system-image-dbus: 
error:
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: Configuration 
directory not found: .load() requires a directory: /etc/system-image/config.d
  Jan 29 22:40:42 ubuntu dbus[1325]: [system] Activated service 
'com.canonical.SystemImage' failed: Launcher could not run (out of memory)

  The Unity8.log and Unity8-dash.log files are just repetitions of:
  QXcbConnection: Could not connect to display .

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

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


[Touch-packages] [Bug 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working

2016-08-04 Thread Daniel van Vugt
That's awesome news. Do we expect the benefit to be just bypassing GL,
or that as well as lower latency?

If you provide a prototype branch I can run it under high-speed camera
testing to measure...

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

Title:
  Nested servers prevent overlays or fullscreen bypass from working

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  New

Bug description:
  Nested servers prevent fullscreen bypass from working.

  This would explain why nesting fullscreen clients is measurably slower than 
non-nesting:
  Direct (bypass) 2600
  Direct (bypass off) 2400
  Nested (bypass) 2450
  Nested (bypass off) 2330

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

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


[Touch-packages] [Bug 1609974] Re: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()

2016-08-04 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1539811 ***
https://bugs.launchpad.net/bugs/1539811

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1539811, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1539811
   Mir crashed with std::exception::what: Couldn't clear output eDP-1 
(drmModeSetCrtc = -13)

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

Title:
  unity-system-compositor crashed with SIGABRT in
  mir::fatal_error_abort()

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  *

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-system-compositor 0.6.0+16.10.20160609-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-0ubuntu4
  Architecture: amd64
  Date: Thu Aug  4 22:39:44 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 2nd Generation Core Processor 
Family Integrated Graphics Controller [1179:0003]
  InstallationDate: Installed on 2016-07-25 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160725)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket 
--from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   mir::fatal_error_abort(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.6
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.9
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.9
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.9
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.9
  Title: unity-system-compositor crashed with SIGABRT in 
mir::fatal_error_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.70-1
  version.lightdm: lightdm 1.19.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1609974/+subscriptions

-- 
Mailing list: https://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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2016-08-04 Thread auspex
You can try having the script do "modprobe -r" and "modprobe" on your wifi
module. That should always work, but seemed like overkill in my case. In
any case, these are workarounds, not fixes.

On 4 Aug 2016 6:01 a.m., "Aleve Sicofante"  wrote:

> @auspex: Your script doesn't work here. I just created it and gave it
> execution permissions, rebooted and tried a sleep/resume cycle. No dice.
>
> I'm just amazed no one from Canonical is chiming in. This has been
> happening from the very moment I installed 16.04 on its release day and
> it happens in the two laptops I use (Lenovo T400 and Dell Studio 1537,
> both with Intel wireless cards). It's so obvious I didn't even try to
> file a bug understanding it would be naturally solved by 16.04.1 at the
> latest... I'm truly amazed in the worst sense.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1448555).
> https://bugs.launchpad.net/bugs/1585863
>
> Title:
>   WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
>   required to fix it.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions
>

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

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

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

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

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

  Expected result:
  The WiFi still functioned.

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

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

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

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


Re: [Touch-packages] [Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

2016-08-04 Thread Ryan Harper
On Thu, Aug 4, 2016 at 5:21 PM, Dan Streetman <
dan.streetman+launch...@canonical.com> wrote:

> > In the original bug where one is comparing ip output of MTU; is there
> something *not* working ?
>
> in that original bug, the user is trying to set up ipv6 tunneling:
>
> "This scenario is quiet common when using tunnels (e.g. Sixxs) to provide
> IPv6
> connectivity. My IPv6 MTU needs to be 20 bytes smaller than may IPv4 MTU
> because of the tunnel's overhead."
>
> > Or did we just observe that the bond interface isn't the same MTU? Can
> we confirm that without
> > the bond interface itself set to MTU 9202 that we don't see the correct
> jumbo frames over ipv6?
>
> this isn't bonding-specific, the example from bug 1609861 just happens
> to use bonding.  But an regular interface configured with a "inet6"
> section mtu of e.g. 9000 and no "inet" section (or an "inet" section but
> no mtu in it) will not correctly set the device mtu to 9000.
>

I understand this scenario; however, what I don't understand is why
if we're setting mtu 9002 on the underlying devices, why the mtu on the
"virtual" device (bond0)
matters vs. the mtu setting of the ipv6 link, especially since this is ipv6
only.

Do we see packets actually get fragmented at the bond ?


>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1609367
>
> Title:
>   ifupdown does not set ipv6-only large mtu
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/
> 1609367/+subscriptions
>

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

Title:
  ifupdown does not set ipv6-only large mtu

Status in ifupdown package in Ubuntu:
  Incomplete

Bug description:
  ifupdown changes a device's mtu differently, between "inet" section
  mtu and "inet6" section mtu.  For "inet", ifupdown changes the
  device's mtu, using 'ip link set DEV mtu NNN'.  However for "inet6",
  ifupdown changes the interface's IPv6 mtu, using 'sysctl -q -e -w
  net.ipv6.conf.DEV.mtu=NNN'.

  The problem is that a device's ipv6 mtu cannot be larger than the
  device mtu.  Normally this is not a problem; the main reason a device
  needs a separate ipv6 mtu is to support ipv6 tunneling inside ipv4
  (e.g. 6in4 or 6rd), so ifupdown would also have a ipv4 "inet" section
  that contained a larger mtu (or, the ipv6 section would have a lower-
  than-default mtu).

  But, in the case of an interface that is configured only for ipv6
  *and* large frames (e.g. 9000 mtu), there is only an "inet6" section
  in the ifupdown config, and so ifupdown fails to set the device's mtu,
  which causes its attempt to set the ipv6 mtu to fail.

  I believe the correct behavior is for ifupdown to check if there is
  any "inet" config section for the same device as the "inet6" section,
  and if there is not then it should change the device mtu as well as
  the ipv6 mtu.  Additionally, the "inet6" configuration must be done
  after the "inet" configuration for the same device, since the ipv6 mtu
  can't be higher than the device mtu.

  I don't see any easy way to add that logic to inet6.defn, however...

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

-- 
Mailing list: https://launchpad.net/~touch-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-08-04 Thread lauricat

Mikko:

I have installed the new network-manager-gnome 1.2.2 as suggested, as
well as [last week] the latest stable kernel - 4.6.3

So after a dozen suspend-resume cycles I can report so far so good!

But no willing to say fixed until I give it some more time, say a week
of normal use.

Yes - I have also noticed a reduction in start up time.
*

Further to this post I made, I have to retract that statement to say the
fault still occurs.

I have doing a fair bit of my own testing with this bug - whether this
assists or not with a fix not sure, but here are my obseravtions.

Lenevo x220, latest iwlwifi driver [18.168.6.1], Ubuntu 16.04.1 (clean
install), latest stable kernel 4.6.5, and latest Network manager
1.2.2-0ubuntu6.

I can report the following:

After Suspend then resume, fault still occurs. Also see nmcli below,
output of Nm icon is the 2 vertical arrows (not the wifi symbol) and NO
WIFI NETWORKS LISTED - but connected to wifi:

xxx@xxx-ThinkPad-X220:~$ nmcli dev
DEVICE TYPE STATE CONNECTION
wlp3s0 wifi connected L 1
enp0s25 ethernet unavailable --
lo loopback unmanaged --
xxx@xxx-ThinkPad-X220:~$


Also, Subsequent to installing 16.04.1, I tried a clean install of 16.10 
Yaketty Yak. Alpha 1

Only 5 days of testing, but many suspend-resume cycles over the course
of a normal work day.

I can report that the problem appeared to not appear with this config!

I had to then subsequently go back to 16.04.1, as the Alpha 1 build was too 
unstable for my usage.
HTH

Cheers...

-- 
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:
  Confirmed

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 1574347] Re: [SRU] Re-read the link type if the name changed

2016-08-04 Thread lauricat
More..

Subsequent to installing 16.04.1, I tried a clean install of 16.10
Yaketty Yak. Alpha 1

Only 5 days of testing, but many suspend-resume cycles over the course
of a normal work day.

I can report that the problem appeared to not appear with this config!

I had to then subsequently go back to 16.04.1, as the Alpha 1 build was
too unstable for my usage.

HTH

Cheers

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

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

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


[Touch-packages] [Bug 1540108] Re: Blue dots for text marking/placing a cursor are too small

2016-08-04 Thread GTriderXC
You see, thats the problem! They are too small in comparison with my
finger. If I put my finger on this tiny blue thing, my fingers covers
already after zooming 2-3 line of text. I can't see where is the
handler. Now as someone put it over the text, situation is even worse
what i reported in another bug: How can you place a handler over the
text if your finger comes always from bottom of the screen?

The correct solution is:

1. A handler big enough to "get" it with a finger as in my photo
2. We can't cover a whole handler! It has to be longer so that we can still see 
some part of it and what it does. This way we get precision. The text should be 
selected or cursor steered OVER a handler so that we don't cover everything as 
it takes place at the moment. Because of the handlers that are to small we 
cover our job with relatively to the screen (even by M10) size HUGE finger. And 
my finger are not the bigger ones that one can have.

I try to do what You wrote. It is impossible. See a photo taken on M10.
Now what about E4.5? I think my photo says everything. Now really try
the same on Android to see how it should work.

** Attachment added: "image20160805_024237465.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1540108/+attachment/4714409/+files/image20160805_024237465.jpg

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

Title:
  Blue dots for text marking/placing a cursor are too small

Status in Ubuntu UX:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I mean the blue dots that are visible in the photo. Ok my hands are not the 
smallest but I saw already bigger ones. I can not place the cursor in the text 
where I want to as well as mark/highlight the text to cut or copy. On Android 
these dots are big raindrops. I have no problem. In Ubuntu it simply doesn't 
work at all without a touchpen. These dots are too tiny.
  --
  I'm updating the bug with an additional information which is actually another 
problem which You can see in the photo in a comment #3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1540108/+subscriptions

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


[Touch-packages] [Bug 1610029] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

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

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

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

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  when upgrading from 14.04 LTS to 16.04 LTS this error came up during
  the upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Aug  3 23:57:59 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago)

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

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


[Touch-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed

2016-08-04 Thread lauricat
I have doing a fair bit of my own testing with this bug - whether this
assists or not with a fix not sure, but here are my obseravtions.

Lenevo x220, latest iwlwifi driver [18.168.6.1], Ubuntu 16.04.1 (clean
install), latest stable kernel 4.6.5, and latest Network manager
1.2.2-0ubuntu6.

I can report the following:

After Suspend then resume, fault still occurs. Also see nmcli below,
output of Nm icon is the 2 vertical arrows (not the wifi symbol) and NO
WIFI NETWORKS LISTED - but connected to wifi:

xxx@xxx-ThinkPad-X220:~$ nmcli dev
DEVICE   TYPE  STATECONNECTION 
wlp3s0   wifi  connectedL 1
enp0s25  ethernet  unavailable  -- 
lo   loopback  unmanaged-- 

HTH

Cheers...
xxx@xxx-ThinkPad-X220:~$

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

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

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


[Touch-packages] [Bug 1610029] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2016-08-04 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

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

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  when upgrading from 14.04 LTS to 16.04 LTS this error came up during
  the upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Aug  3 23:57:59 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago)

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

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


[Touch-packages] [Bug 1610029] [NEW] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2016-08-04 Thread Ronald Pettigrew
Public bug reported:

when upgrading from 14.04 LTS to 16.04 LTS this error came up during the
upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gconf2 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Aug  3 23:57:59 2016
ErrorMessage: dependency problems - leaving triggers unprocessed
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

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

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  when upgrading from 14.04 LTS to 16.04 LTS this error came up during
  the upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Aug  3 23:57:59 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago)

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

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


[Touch-packages] [Bug 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

2016-08-04 Thread Marek Dopiera
I might be doing something broken, but it still seems broken to me on
Ubuntu 16.04 on Raspberry PI despite having these fixes applied.

Package versions:
systemd: 229-4ubuntu7
udev: 229-4ubuntu7

Could you please take a look if I'm not doing something stupid (I
hopefully attached the relevant info):

$ ifconfig -a | head
enxb827eb739cc2 Link encap:Ethernet  HWaddr b8:27:eb:73:9c:c2  
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host


$ ls -l /etc/udev/rules.d/80-net-setup-link.rules | tee -a report.txt 
lrwxrwxrwx 1 root root 9 Aug  4  2016 /etc/udev/rules.d/80-net-setup-link.rules 
-> /dev/null


$ grep net.ifnames=0 /proc/cmdline | tee -a report.txt
8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa02082 bcm2709.serial=0xb2739cc2 
smsc95xx.macaddr=B8:27:EB:73:9C:C2 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  fsck.mode=force net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait


$ cat /lib/udev/rules.d/73-usb-net-by-mac.rules
# Use MAC based names for network interfaces which are directly or indirectly
# on USB and have an universally administered (stable) MAC address (second bit 
# is 0). 

IMPORT{cmdline}="net.ifnames", ENV{net.ifnames}=="0", GOTO="usb_net_by_mac_end"
PROGRAM="/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules", 
RESULT=="/dev/null", GOTO="usb_net_by_mac_end"

ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", NAME=="", \
ATTR{address}=="?[014589cd]:*", \
IMPORT{builtin}="net_id", NAME="$env{ID_NET_NAME_MAC}"

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

Title:
  systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or
  /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd package in Debian:
  Fix Released

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB
  devices.

  It appears the regression is here:
  * Set MAC based name for USB network interfaces only for universally
  administered (i. e. stable) MACs, not for locally administered (i. e.
  randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link
  (as link files don't currently support globs for MACAddress=) and replace
  with an udev rule in /lib/udev/rules.d/73-special-net-names.rules.
  (Closes: #812575, LP: #1574483)

  As Raspberry Pi's use eth0 via USB, this breaks running systems.

  Before:
  ii  systemd229-4ubuntu4 armhfsystem and service manager
  ii  udev   229-4ubuntu4 armhf/dev/ and hotplug management daem

  3: eth0:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  After:

  ii  systemd  229-4ubuntu6armhf   
system and service manager
  ii  udev 229-4ubuntu6armhf   
/dev/ and hotplug management daemon

  3: enxb827eb1639e9:  mtu 1500 qdisc 
pfifo_fast state UP mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  cat /proc/cmdline
  dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 
bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 
smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 
rootfstype=ext4 elevator=deadline rootwait

  With the default interfaces configuration, all networking is lost on
  reboot after upgrade.

  
  SRU TEST CASE
  =
   * Boot with "net.ifnames=0" on the kernel command line, and connect an USB 
ethernet device. It will still be called enxDEADBEEF with current xenial. With 
the -proposed version it will instead keep the kernel name, like "usb0" as 
intended.

   * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
  (the other documented way to disable ifnames) and do the above
  connect/name check test again.

To manage notifications about this bug go 

[Touch-packages] [Bug 1609110] Re: Do we still need the mesa or mesa-egl directories in /usr/lib/?

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

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

** Tags added: patch

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

Title:
  Do we still need the mesa or mesa-egl directories in /usr/lib/?

Status in mesa package in Ubuntu:
  New

Bug description:
  One of our mesa changes means we can't sync Wine packages (or wine-
  development stuck in proposed) from Debian.  See bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827770

  We purposely end up creating in /usr/lib/x86_64-linux-gnu
  mesa/ld.so.conf
  mesa/libGL.so -> libGL.so.1.2.0
  mesa/libGL.so.1 -> libGL.so.1.2.0
  mesa/libGL.so.1.2.0
  libGL.so -> mesa/libGL.so

  Debian on the other hand just creates:
  libGL.so.1 -> libGL.so.1.2.0
  libGL.so.1.2.0

  I haven't found a clear reason for the divergence.  I do see some
  comments about making it work with the alternates system. I'm not sure
  if that's current though.  Long term libglvnd should help there in a
  better way (IIUC).

  For reference Fedora does:
  /usr/lib64/libGL.so.1
  /usr/lib64/libGL.so.1.2.0

  Can we drop these Debian differences from mesa for Yakkety?

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

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


[Touch-packages] [Bug 1603416] Re: Unable to add time & date stamps to photos

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

** Changed in: camera-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Unable to add time & date stamps to photos

Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Currently there is no setting to allow the time and date stamp to be
  added to photos taken using the camera in Ubuntu Touch.

  This functionality into the camera app should be standard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1603416/+subscriptions

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


[Touch-packages] [Bug 1509379] Re: [wishlist] add camera effects

2016-08-04 Thread Anupam
** Also affects: camera-app (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [wishlist] add camera effects

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  New

Bug description:
  It would be amazing!

  Like:

  - panoramic mode (merge more photos to create a landscape)
  - black filtre
  - effects

  ..and so on..

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1509379/+subscriptions

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


[Touch-packages] [Bug 1605867] Re: Panorama Function

2016-08-04 Thread Anupam
*** This bug is a duplicate of bug 1509379 ***
https://bugs.launchpad.net/bugs/1509379

** This bug has been marked a duplicate of bug 1509379
   [wishlist] add camera effects

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

Title:
  Panorama Function

Status in camera-app package in Ubuntu:
  New

Bug description:
  It would be awesome to have a panorama function in the camera app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1605867/+subscriptions

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


[Touch-packages] [Bug 1610010] Re: [Scopes] ⨂ icon in search field is jagged

2016-08-04 Thread Anupam
** Summary changed:

- [Scopes] ⨂ icon in search field not smooth 
+ [Scopes] ⨂ icon in search field is jagged

** Description changed:

- ⨂ icon in the search field of a scope looks low-res.
+ ⨂ icon in the search field of a scope is not smooth.
  Device: E5, stable channel, OTA-12
  
  Screenshot:
  https://launchpadlibrarian.net/277165796/screenshot20160803_000859160.png

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

Title:
  [Scopes] ⨂ icon in search field is jagged

Status in Ubuntu UX:
  New
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  ⨂ icon in the search field of a scope is not smooth.
  Device: E5, stable channel, OTA-12

  Screenshot:
  https://launchpadlibrarian.net/277165796/screenshot20160803_000859160.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1610010/+subscriptions

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


[Touch-packages] [Bug 1610013] [NEW] /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

2016-08-04 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding qtdeclarative-opensource-src.  This problem was most recently
seen with version 5.4.1-1ubuntu11~overlay8, the problem page at
https://errors.ubuntu.com/problem/3ec61a10481c4d44ce2b3112c4ef4a13a6be9977
contains more details.

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


** Tags: vivid

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

Title:
  /usr/lib/arm-linux-
  
gnueabihf/qt5/bin/qmlscene:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding qtdeclarative-opensource-src.  This problem was most
  recently seen with version 5.4.1-1ubuntu11~overlay8, the problem page
  at
  https://errors.ubuntu.com/problem/3ec61a10481c4d44ce2b3112c4ef4a13a6be9977
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1610013/+subscriptions

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


[Touch-packages] [Bug 1610010] [NEW] [Scopes] ⨂ icon in search field not smooth

2016-08-04 Thread Anupam
Public bug reported:

⨂ icon in the search field of a scope looks low-res.
Device: E5, stable channel, OTA-12

Screenshot:
https://launchpadlibrarian.net/277165796/screenshot20160803_000859160.png

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

** Affects: unity-scopes-shell (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "screenshot20160803_000859160.png"
   
https://bugs.launchpad.net/bugs/1610010/+attachment/4714364/+files/screenshot20160803_000859160.png

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Description changed:

  ⨂ icon in the search field of a scope looks low-res.
  Device: E5, stable channel, OTA-12
+ 
+ Screenshot:
+ https://launchpadlibrarian.net/277165796/screenshot20160803_000859160.png

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

Title:
  [Scopes] ⨂ icon in search field not smooth

Status in Ubuntu UX:
  New
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  ⨂ icon in the search field of a scope looks low-res.
  Device: E5, stable channel, OTA-12

  Screenshot:
  https://launchpadlibrarian.net/277165796/screenshot20160803_000859160.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1610010/+subscriptions

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


[Touch-packages] [Bug 1608493] Re: No easy way to delete a scope

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

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

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

Title:
  No easy way to delete a scope

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

Bug description:
  Bring up the manage scopes view. Attempt to delete a scope.

  It seems there is no way to delete a scope from this view.

  The only way to delete a scope, appears to be to try and find it in
  the app store again (if it even exists there) and then uninstall it
  from the app description page. This is awkward and time consuming.

  There should be a delete option in the manage scopes view, perhaps the
  system standard slide to the right to reveal a delete button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1608493/+subscriptions

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


[Touch-packages] [Bug 1610005] Re: Remove gtk3's versioned dependency of on adwaita-icon-theme

2016-08-04 Thread Jeremy Bicha
** Description changed:

- .
+ Impact
+ ===
+ libgtk-3-common depends on adwaita-icon-theme (>= ${gnome:Version}). For 
xenial, this is adwaita-icon-theme >= 3.18.
+ 
+ This causes 2 problems. One is that we have to remember to upload a new
+ version of adwaita-icon-theme before we upload a new version of GTK3.
+ Otherwise, the new version of adwaita-icon-theme becomes unbuildable
+ because adwaita-icon-theme depends on GTK3 to build but GTK3 is
+ uninstallable because the dependency can't be satisfied yet. This can be
+ worked around (it happened this week with 3.20 in yakkety) but it's not
+ good.
+ 
+ The other is that Lubuntu doesn't want to install adwaita-icon-theme but
+ instead install lubuntu-icon-theme as a replacement by setting Provides:
+ adwaita-icon-theme. According to Debian policy, that doesn't work if
+ something has a versioned dependency on the provided package.
+ 
+ https://www.debian.org/doc/debian-policy/ch-relationships.html#s-virtual
+ 
+ Test case
+ =
+ Since the xenial daily images use -proposed, check here whether 
adwaita-icon-theme is installed a day or two after the gtk update has been 
pushed to xenial-proposed:
+ 
+ http://cdimage.ubuntu.com/lubuntu/xenial/daily-live/current/xenial-
+ desktop-amd64.manifest
+ 
+ 
+ Regression potential
+ 
+ If in fact, lubuntu-icon-theme does not include some of the icons in 
adwaita-icon-theme, there will be missing icons in apps that try to use those 
icons.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-common 3.18.9-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  4 18:55:25 2016
  InstallationDate: Installed on 2016-07-31 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Impact
  ===
  libgtk-3-common depends on adwaita-icon-theme (>= ${gnome:Version}). For 
xenial, this is adwaita-icon-theme >= 3.18.
  
  This causes 2 problems. One is that we have to remember to upload a new
  version of adwaita-icon-theme before we upload a new version of GTK3.
  Otherwise, the new version of adwaita-icon-theme becomes unbuildable
  because adwaita-icon-theme depends on GTK3 to build but GTK3 is
  uninstallable because the dependency can't be satisfied yet. This can be
  worked around (it happened this week with 3.20 in yakkety) but it's not
  good.
  
  The other is that Lubuntu doesn't want to install adwaita-icon-theme but
  instead install lubuntu-icon-theme as a replacement by setting Provides:
  adwaita-icon-theme. According to Debian policy, that doesn't work if
  something has a versioned dependency on the provided package.
  
  https://www.debian.org/doc/debian-policy/ch-relationships.html#s-virtual
  
+ The versioned dependency was removed in Debian svn: 
+ 
https://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gtk%2B3.0/debian/control.in?r1=49406=49410
+ 
  Test case
  =
  Since the xenial daily images use -proposed, check here whether 
adwaita-icon-theme is installed a day or two after the gtk update has been 
pushed to xenial-proposed:
  
  http://cdimage.ubuntu.com/lubuntu/xenial/daily-live/current/xenial-
  desktop-amd64.manifest
- 
  
  Regression potential
  
  If in fact, lubuntu-icon-theme does not include some of the icons in 
adwaita-icon-theme, there will be missing icons in apps that try to use those 
icons.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-common 3.18.9-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  4 18:55:25 2016
  InstallationDate: Installed on 2016-07-31 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Remove gtk3's versioned dependency of on adwaita-icon-theme

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Impact
  ===
  libgtk-3-common depends on 

[Touch-packages] [Bug 1610005] [NEW] Remove gtk3's versioned dependency of on adwaita-icon-theme

2016-08-04 Thread Jeremy Bicha
Public bug reported:

.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgtk-3-common 3.18.9-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Aug  4 18:55:25 2016
InstallationDate: Installed on 2016-07-31 (4 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Remove gtk3's versioned dependency of on adwaita-icon-theme

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-common 3.18.9-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  4 18:55:25 2016
  InstallationDate: Installed on 2016-07-31 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1610005/+subscriptions

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


[Touch-packages] [Bug 1610005] Re: Remove gtk3's versioned dependency of on adwaita-icon-theme

2016-08-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~jbicha/gtk/gtk-3-20-7

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

Title:
  Remove gtk3's versioned dependency of on adwaita-icon-theme

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-common 3.18.9-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  4 18:55:25 2016
  InstallationDate: Installed on 2016-07-31 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1610005/+subscriptions

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


[Touch-packages] [Bug 1609110] Re: Do we still need the mesa or mesa-egl directories in /usr/lib/?

2016-08-04 Thread Timo Aaltonen
the linux opengl abi requires that libGL.so is in /usr/lib(/)

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

Title:
  Do we still need the mesa or mesa-egl directories in /usr/lib/?

Status in mesa package in Ubuntu:
  New

Bug description:
  One of our mesa changes means we can't sync Wine packages (or wine-
  development stuck in proposed) from Debian.  See bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827770

  We purposely end up creating in /usr/lib/x86_64-linux-gnu
  mesa/ld.so.conf
  mesa/libGL.so -> libGL.so.1.2.0
  mesa/libGL.so.1 -> libGL.so.1.2.0
  mesa/libGL.so.1.2.0
  libGL.so -> mesa/libGL.so

  Debian on the other hand just creates:
  libGL.so.1 -> libGL.so.1.2.0
  libGL.so.1.2.0

  I haven't found a clear reason for the divergence.  I do see some
  comments about making it work with the alternates system. I'm not sure
  if that's current though.  Long term libglvnd should help there in a
  better way (IIUC).

  For reference Fedora does:
  /usr/lib64/libGL.so.1
  /usr/lib64/libGL.so.1.2.0

  Can we drop these Debian differences from mesa for Yakkety?

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

-- 
Mailing list: https://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 1609750] Status changed to Confirmed

2016-08-04 Thread Luke Yelavich
Have you tried a newer kernel? Yakkety is still on 4.4, but I think
mainline is up to 4.7.

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

Title:
  Audio not working on Acer Chromebook R11

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

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  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
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:12:03 2016
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux-image-4.4.0-33-generic 4.4.0-33.52
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-33-generic N/A
   linux-backports-modules-4.4.0-33-generic  N/A
   linux-firmware1.159
  Tags:  yakkety
  Uname: Linux 4.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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


[Touch-packages] [Bug 1610002] Re: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-08-04 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Sorry I have no idea. Ever since I upgraded to 16.04 LTS from 14.04
  LTS my netbook has been a disaster. Shutdown doesn't work and I am
  getting loads of 'Report error?' windows popping up :(

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Mon Aug  1 13:14:36 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-04-27 (464 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1610002/+subscriptions

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


[Touch-packages] [Bug 1610002] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-08-04 Thread Cameron Míceál Tyre
Public bug reported:

Sorry I have no idea. Ever since I upgraded to 16.04 LTS from 14.04 LTS
my netbook has been a disaster. Shutdown doesn't work and I am getting
loads of 'Report error?' windows popping up :(

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Mon Aug  1 13:14:36 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-04-27 (464 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: ca-certificates
Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2016-08-01 (3 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Sorry I have no idea. Ever since I upgraded to 16.04 LTS from 14.04
  LTS my netbook has been a disaster. Shutdown doesn't work and I am
  getting loads of 'Report error?' windows popping up :(

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Mon Aug  1 13:14:36 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-04-27 (464 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1610002/+subscriptions

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


[Touch-packages] [Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

2016-08-04 Thread Dan Streetman
> In the original bug where one is comparing ip output of MTU; is there
something *not* working ?

in that original bug, the user is trying to set up ipv6 tunneling:

"This scenario is quiet common when using tunnels (e.g. Sixxs) to provide IPv6
connectivity. My IPv6 MTU needs to be 20 bytes smaller than may IPv4 MTU
because of the tunnel's overhead."

> Or did we just observe that the bond interface isn't the same MTU? Can we 
> confirm that without
> the bond interface itself set to MTU 9202 that we don't see the correct jumbo 
> frames over ipv6?

this isn't bonding-specific, the example from bug 1609861 just happens
to use bonding.  But an regular interface configured with a "inet6"
section mtu of e.g. 9000 and no "inet" section (or an "inet" section but
no mtu in it) will not correctly set the device mtu to 9000.

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

Title:
  ifupdown does not set ipv6-only large mtu

Status in ifupdown package in Ubuntu:
  Incomplete

Bug description:
  ifupdown changes a device's mtu differently, between "inet" section
  mtu and "inet6" section mtu.  For "inet", ifupdown changes the
  device's mtu, using 'ip link set DEV mtu NNN'.  However for "inet6",
  ifupdown changes the interface's IPv6 mtu, using 'sysctl -q -e -w
  net.ipv6.conf.DEV.mtu=NNN'.

  The problem is that a device's ipv6 mtu cannot be larger than the
  device mtu.  Normally this is not a problem; the main reason a device
  needs a separate ipv6 mtu is to support ipv6 tunneling inside ipv4
  (e.g. 6in4 or 6rd), so ifupdown would also have a ipv4 "inet" section
  that contained a larger mtu (or, the ipv6 section would have a lower-
  than-default mtu).

  But, in the case of an interface that is configured only for ipv6
  *and* large frames (e.g. 9000 mtu), there is only an "inet6" section
  in the ifupdown config, and so ifupdown fails to set the device's mtu,
  which causes its attempt to set the ipv6 mtu to fail.

  I believe the correct behavior is for ifupdown to check if there is
  any "inet" config section for the same device as the "inet6" section,
  and if there is not then it should change the device mtu as well as
  the ipv6 mtu.  Additionally, the "inet6" configuration must be done
  after the "inet" configuration for the same device, since the ipv6 mtu
  can't be higher than the device mtu.

  I don't see any easy way to add that logic to inet6.defn, however...

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

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-08-04 Thread Seth Arnold
In what circumstances do dhcpv6 servers hand out an IPv6 address without
also reporting the prefix length the client should use? Something seems
wrong here. (Is it me? :)

Thanks

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Precise:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  In Progress

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

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


[Touch-packages] [Bug 1609110] Re: Do we still need the mesa or mesa-egl directories in /usr/lib/?

2016-08-04 Thread Bryan Quigley
What about just getting rid of the:
/usr/lib/x86_64-linux-gnu/libGL.so symlink?   It's provided by libgl1-mesa-dev. 
 I have the nvidia driver installed and it libGL.so (above) is still symlinked 
to mesa.

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

Title:
  Do we still need the mesa or mesa-egl directories in /usr/lib/?

Status in mesa package in Ubuntu:
  New

Bug description:
  One of our mesa changes means we can't sync Wine packages (or wine-
  development stuck in proposed) from Debian.  See bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827770

  We purposely end up creating in /usr/lib/x86_64-linux-gnu
  mesa/ld.so.conf
  mesa/libGL.so -> libGL.so.1.2.0
  mesa/libGL.so.1 -> libGL.so.1.2.0
  mesa/libGL.so.1.2.0
  libGL.so -> mesa/libGL.so

  Debian on the other hand just creates:
  libGL.so.1 -> libGL.so.1.2.0
  libGL.so.1.2.0

  I haven't found a clear reason for the divergence.  I do see some
  comments about making it work with the alternates system. I'm not sure
  if that's current though.  Long term libglvnd should help there in a
  better way (IIUC).

  For reference Fedora does:
  /usr/lib64/libGL.so.1
  /usr/lib64/libGL.so.1.2.0

  Can we drop these Debian differences from mesa for Yakkety?

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

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


[Touch-packages] [Bug 1609745] Re: Touch screen not working on Acer Chromebook R11

2016-08-04 Thread Timo Aaltonen
it is a kernel bug, closing for xorg

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

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

Title:
  Touch screen not working on Acer Chromebook R11

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Touch screen seems to be identified as far as I can see, but there's
  no working input. I've tried among else xinput test-xi2, reattach
  command but it seems simply non-functional for whatever reason.

  It works on the ChromeOS side.

  I'll add kernel to the bug report since it might be on that side.

  The machine is Acer Chromebook R11 (codename CYAN), Intel Braswell
  platform.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  BootLog: H-STATE: clean, 343470/1638400 files, 2175315/6546944 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:02:31 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Braswell Integrated Graphics Controller [8086:22b1] (rev 
21) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  version.compiz: compiz 1:0.9.13.0+16.10.20160726.4-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu4
  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.0-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 Aug  4 13:59:45 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu4
  xserver.video_driver: modeset
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-33-generic N/A
   linux-backports-modules-4.4.0-33-generic  N/A
   linux-firmware1.159
  Tags:  yakkety
  Uname: 

[Touch-packages] [Bug 1609875] Re: Lenovo ThinkPad T440s has display issues after docking

2016-08-04 Thread Timo Aaltonen
** Package changed: xorg (Ubuntu) => unity-settings-daemon (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/1609875

Title:
  Lenovo ThinkPad T440s has display issues after docking

Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  When undocking the Lenovo Thinkpad T440s from a dock with an external
  monitor, all the screens move to the laptop display.  When I redock
  the laptop, all the screens stay on the laptop display and the monitor
  configurations don't reset.  The laptop display is still marked as the
  main display and is on the wrong side of the other monitor from where
  it's physically located.  I have to either restart the machine to have
  the display settings return to the way they were, or reapply them by
  hand.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Aug  4 08:34:34 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:220c]
  InstallationDate: Installed on 2015-01-05 (576 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20AQ006HUS
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic 
root=UUID=8f3296b0-155a-4776-a162-283095042d6b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET78WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ006HUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ006HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ006HUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQ006HUS
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Aug  4 08:26:39 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1034 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1609875/+subscriptions

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


[Touch-packages] [Bug 1609110] Re: Do we still need the mesa or mesa-egl directories in /usr/lib/?

2016-08-04 Thread Timo Aaltonen
the alternates handling was supposed to be less brittle than diversions
(what debian does for fglrx/nvidia). Now that fglrx is no more there's
still nvidia, and it creates libGL.so symlinks as well.

libglvnd will hopefully make these obsolete at some point in the future,
but we're not there yet

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

Title:
  Do we still need the mesa or mesa-egl directories in /usr/lib/?

Status in mesa package in Ubuntu:
  New

Bug description:
  One of our mesa changes means we can't sync Wine packages (or wine-
  development stuck in proposed) from Debian.  See bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827770

  We purposely end up creating in /usr/lib/x86_64-linux-gnu
  mesa/ld.so.conf
  mesa/libGL.so -> libGL.so.1.2.0
  mesa/libGL.so.1 -> libGL.so.1.2.0
  mesa/libGL.so.1.2.0
  libGL.so -> mesa/libGL.so

  Debian on the other hand just creates:
  libGL.so.1 -> libGL.so.1.2.0
  libGL.so.1.2.0

  I haven't found a clear reason for the divergence.  I do see some
  comments about making it work with the alternates system. I'm not sure
  if that's current though.  Long term libglvnd should help there in a
  better way (IIUC).

  For reference Fedora does:
  /usr/lib64/libGL.so.1
  /usr/lib64/libGL.so.1.2.0

  Can we drop these Debian differences from mesa for Yakkety?

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

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


[Touch-packages] [Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

2016-08-04 Thread Dan Streetman
> and the tl;dr is that IPv6 supports per protocol, rather than
interface.

the ipv6 mtu is for situations where the host's ipv6 connection uses (at
some point down the line) ipv6 tunneling, for example 6in4 or 6rd.  The
ipv6 mtu is strictly a subset of the device mtu; it can never be more
than the device mtu.  For cases where the system has native ipv6
connectivity, typically the device mtu == ipv6 mtu, so the device mtu
should be set and the ipv6 mtu should not be changed.  Anytime the
device mtu is set, the ipv6 mtu is also changed to match it.

I think the ifupdown api is not actually in sync with what the ipv6 mtu
really means.  Part of this comes from the fact that ifupdown separates
conf into "inet" for ipv4 and "inet6" for ipv6, but mtu isn't actually a
networking layer setting; it's a link layer setting.

Within the inet/ipv4 and inet6/ipv6 constraints, one possibility is
instead of setting the ipv6 mtu for all cases of a "inet6" section,
ifupdown should restore the original behavior of setting the device mtu
for either a "inet" or "inet6" section mtu param, and an additional
"mtu6" param, valid only in the "inet6" section, should be added.  That
new param should be used to configure a lower ipv6 mtu for cases of ipv6
tunneling.  Something like:

iface eth1 inet manual
  mtu 1500

iface eth1 inet6 manual
  mtu 1500  # this is equivalent to the "inet" section mtu
  mtu6 1480

However, that's obviously an api change that may require other changes
to things that create ifupdown configuration.

Alternately, ifupdown could add logic to decide whether or not to change
the device mtu or the ipv6 mtu, e.g. pseudocode:

if (interface_does_not_have_inet_section)
  # the "inet6" mtu really meant device mtu, not ipv6 mtu
  device_mtu = inet6_section_mtu
else if (inet_section_has_mtu)
  device_mtu = inet_section_mtu
  ipv6_mtu = inet6_section_mtu
else
  # interface has inet config,
  # but mtu specified only in ipv6,
  # must infer meaning
  if (current_device_mtu < inet6_section_mtu)
# assume large device mtu desired
device_mtu = inet6_section_mtu
  else
# assume ipv6 tunneling
ipv6_mtu = inet6_section_mtu

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

Title:
  ifupdown does not set ipv6-only large mtu

Status in ifupdown package in Ubuntu:
  Incomplete

Bug description:
  ifupdown changes a device's mtu differently, between "inet" section
  mtu and "inet6" section mtu.  For "inet", ifupdown changes the
  device's mtu, using 'ip link set DEV mtu NNN'.  However for "inet6",
  ifupdown changes the interface's IPv6 mtu, using 'sysctl -q -e -w
  net.ipv6.conf.DEV.mtu=NNN'.

  The problem is that a device's ipv6 mtu cannot be larger than the
  device mtu.  Normally this is not a problem; the main reason a device
  needs a separate ipv6 mtu is to support ipv6 tunneling inside ipv4
  (e.g. 6in4 or 6rd), so ifupdown would also have a ipv4 "inet" section
  that contained a larger mtu (or, the ipv6 section would have a lower-
  than-default mtu).

  But, in the case of an interface that is configured only for ipv6
  *and* large frames (e.g. 9000 mtu), there is only an "inet6" section
  in the ifupdown config, and so ifupdown fails to set the device's mtu,
  which causes its attempt to set the ipv6 mtu to fail.

  I believe the correct behavior is for ifupdown to check if there is
  any "inet" config section for the same device as the "inet6" section,
  and if there is not then it should change the device mtu as well as
  the ipv6 mtu.  Additionally, the "inet6" configuration must be done
  after the "inet" configuration for the same device, since the ipv6 mtu
  can't be higher than the device mtu.

  I don't see any easy way to add that logic to inet6.defn, however...

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

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


[Touch-packages] [Bug 1609088] Re: map view is off-center

2016-08-04 Thread Mathew Hodson
** Tags added: patch

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

Title:
  map view is off-center

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  [Impact]
  Some widgets such as the map view in gnome-maps 3.18.3 are off-center. (The 
upstream bug was originally about polari 3.19, an IRC app from GNOME.)

  Screenshot attached.

  [Test Case]
  1. Install gnome-maps 3.18.3-0ubuntu1 (as of today, in xenial-proposed)
  2. Open the maps app. Is there a blank area on one side of the map view?
  3. Install the updated gtk-3 packages
  4. Open the maps app. The map view should fill the map view space.

  [Regression Potential]
  The minimal fix has been shipped with GTK since 3.19.10. (Therefore, this bug 
is already fixed in yakkety-proposed.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.18.9-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Aug  2 14:58:11 2016
  InstallationDate: Installed on 2016-07-31 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2016-08-04 Thread Etienne Van Bogaert
Jose Luis, that's the HDA driver for the same codecs, AFAIK these don't
port to the sst driver for socs.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1584393] Re: systemctl restart networking hangs reloading ssh.service

2016-08-04 Thread Mathew Hodson
** Changed in: openssh (Ubuntu Xenial)
   Importance: Undecided => Low

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

Title:
  systemctl restart networking hangs reloading ssh.service

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  Issues "systemctl restart networking" never exits. It hangs during a
  call to "systemctl reload ssh.service":

  ● networking.service - Raise network interfaces
 Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor 
preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
 Active: activating (start) since Sat 2016-05-21 21:41:58 UTC; 18s ago
   Docs: man:interfaces(5)
Process: 1288 ExecStop=/sbin/ifdown -a --read-environment (code=exited, 
status=0/SUCCESS)
Process: 1376 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] 
&& [ -n "$(ifquery --read-environment --list --exclude=lo)" ] &
   Main PID: 1383 (ifup)
  Tasks: 7 (limit: 512)
 Memory: 1.8M
CPU: 111ms
 CGroup: /system.slice/networking.service
 ├─1383 /sbin/ifup -a --read-environment
 ├─1479 /sbin/dhclient -1 -v -pf /run/dhclient.enp0s3.pid -lf 
/var/lib/dhcp/dhclient.enp0s3.leases -I -df /var/lib/dhcp/dhclient6
 ├─1480 /bin/sh -c /bin/run-parts --exit-on-error 
/etc/network/if-up.d
 ├─1481 /bin/run-parts --exit-on-error /etc/network/if-up.d
 ├─1504 /bin/sh /etc/network/if-up.d/openssh-server
 ├─1507 /bin/sh /usr/sbin/invoke-rc.d ssh reload
 └─1527 systemctl reload ssh.service

  Then issuing the same command from another terminal causes the first
  to exit successfully (the second also exists successfully).

  On the official vagrant image, I get this problem independently of
  whether the command is issued through and ssh session. I've gotten the
  same behavior on the official xenial AMIs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May 21 21:35:08 2016
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1609986] Re: package systemd 229-4ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-04 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package systemd 229-4ubuntu7 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  richo@richo-lappy:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  
  I just tried to upgrade to the latest xubuntu
  and systemd failed to upgrade or something

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu7
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu Aug  4 23:16:09 2016
  DuplicateSignature: package:systemd:229-4ubuntu7:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-12-30 (218 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b8 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-311
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-65-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro noprompt quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/docker.service → 
/etc/systemd/system/docker.service.d/docker.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-311
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.10:rvnAcer:rnAspireES1-311:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.name: Aspire ES1-311
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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


[Touch-packages] [Bug 1609986] [NEW] package systemd 229-4ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-04 Thread Richard Tjerngren
Public bug reported:

richo@richo-lappy:~$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04


I just tried to upgrade to the latest xubuntu
and systemd failed to upgrade or something

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu7
ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-65-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Thu Aug  4 23:16:09 2016
DuplicateSignature: package:systemd:229-4ubuntu7:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-12-30 (218 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:57b8 Realtek Semiconductor Corp. 
 Bus 001 Device 004: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire ES1-311
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-65-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro noprompt quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/docker.service → 
/etc/systemd/system/docker.service.d/docker.conf
 
 3 overridden configuration files found.
Title: package systemd 229-4ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago)
dmi.bios.date: 10/24/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Aspire ES1-311
dmi.board.vendor: Acer
dmi.board.version: V1.10
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.10
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.10:rvnAcer:rnAspireES1-311:rvrV1.10:cvnAcer:ct10:cvrV1.10:
dmi.product.name: Aspire ES1-311
dmi.product.version: V1.10
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package systemd 229-4ubuntu7 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  richo@richo-lappy:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  
  I just tried to upgrade to the latest xubuntu
  and systemd failed to upgrade or something

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu7
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu Aug  4 23:16:09 2016
  DuplicateSignature: package:systemd:229-4ubuntu7:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-12-30 (218 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b8 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-311
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-65-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro noprompt quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/docker.service → 
/etc/systemd/system/docker.service.d/docker.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script 

[Touch-packages] [Bug 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind

2016-08-04 Thread EdwardClay
How does one get 0.8.11 for ubuntu 16.04?  dpkg -l|grep ifupdown returns
0.8.10ubuntu1 and I still have this issue.

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

Title:
  inet6 dhcp doesn't wait for link-local address to leave tentative -
  dhclient fails to bind

Status in ifupdown package in Ubuntu:
  Triaged

Bug description:
  =
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  ifupdown:
Installed: 0.8.10ubuntu1
Candidate: 0.8.10ubuntu1
  =

  With an /etc/network/interfaces file containing:

  auto eno16780032
  iface eno16780032 inet dhcp
  iface eno16780032 inet6 dhcp

  On boot, ifup starts 'dhclient -6' before the link local address has
  completed Duplicate Address Discovery (the address is marked
  'tentative').  In turn, dhclient reports 'Can't bind to dhcp address:
  Cannot assign requested address', and fails almost immediately.

  It would seem that either wait-for-ll6.sh should wait for the link
  local address to come up AND stop being tentative, or the dhcp method
  for inet6 should call settle-dad.sh after wait-for-ll6?

  This is partly a race condition, so on slower devices the dad may
  complete by the time dhclient has got started, however I can regularly
  reproduce this on a virtual machine.

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

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


[Touch-packages] [Bug 1567744] Re: USB NICs get too long name for ifupdown aliases

2016-08-04 Thread David A. Desrosiers
Doesn't adding "net.ifnames=0 biosdevname=0" to your kernel boot line
fix this for you? It will stop udev from creating the longer-than-
desired names.

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

Title:
  USB NICs get too long name for ifupdown aliases

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I have a USB NIC that is connected to my denial system. I tried to
  create an alias, and after reboot, it wasn't created. When I manually
  try to bring it up I have the error.

  /e/n/i:

  auto enx000ec688b79f
  iface enx000ec688b79f inet static
  address 10.90.90.1
  netmask 255.255.255.0

  auto enx000ec688b79f:1
  iface enx000ec688b79f:1 inet static
  address 192.168.100.1
  netmask 255.255.255.0

  ubuntu@maas00:~$ sudo ifup enx000ec688b79f
  ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
  RTNETLINK answers: Numerical result out of range
  Failed to bring up enx000ec688b79f:1.

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

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


[Touch-packages] [Bug 1577310] Re: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** Changed in: python-defaults (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python-minimal 2.7.11-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in python-defaults package in Ubuntu:
  Confirmed

Bug description:
  python-minimal
  python-all
  python-all-dev
  pakage are failed to install while upgrade from 15.10 need to fixed the 
problem soon tried out sudo apt-get update --fix , sudo dpkg -- configure -a , 
sudo apt-get install -f couldnot able to resolve the issue Please suggest 
how to fixed it

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.11-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon May  2 12:33:17 2016
  DpkgHistoryLog:
   Start-Date: 2016-05-02  12:33:17
   Commandline: apt-get install -f
   Requested-By: ujjal (1000)
   Upgrade: python:amd64 (2.7.9-1, 2.7.11-1)
  DpkgTerminalLog:
   Setting up python-minimal (2.7.11-1) ...
   dpkg: error processing package python-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
  DuplicateSignature:
   Setting up python-minimal (2.7.11-1) ...
   dpkg: error processing package python-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-09-03 (241 days ago)
  InstallationMedia: Ubuntu-Kylin 15.04 "Vivid Vervet" - Release amd64 
(20150423)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-20 (11 days ago)

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

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


[Touch-packages] [Bug 1609110] Re: Do we still need the mesa or mesa-egl directories in /usr/lib/?

2016-08-04 Thread Bryan Quigley
@Timo
Does this make sense to you?  Thanks!

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

Title:
  Do we still need the mesa or mesa-egl directories in /usr/lib/?

Status in mesa package in Ubuntu:
  New

Bug description:
  One of our mesa changes means we can't sync Wine packages (or wine-
  development stuck in proposed) from Debian.  See bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827770

  We purposely end up creating in /usr/lib/x86_64-linux-gnu
  mesa/ld.so.conf
  mesa/libGL.so -> libGL.so.1.2.0
  mesa/libGL.so.1 -> libGL.so.1.2.0
  mesa/libGL.so.1.2.0
  libGL.so -> mesa/libGL.so

  Debian on the other hand just creates:
  libGL.so.1 -> libGL.so.1.2.0
  libGL.so.1.2.0

  I haven't found a clear reason for the divergence.  I do see some
  comments about making it work with the alternates system. I'm not sure
  if that's current though.  Long term libglvnd should help there in a
  better way (IIUC).

  For reference Fedora does:
  /usr/lib64/libGL.so.1
  /usr/lib64/libGL.so.1.2.0

  Can we drop these Debian differences from mesa for Yakkety?

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

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


[Touch-packages] [Bug 1609110] Re: Do we still need the mesa or mesa-egl directories in /usr/lib/?

2016-08-04 Thread Bryan Quigley
Alternatively dropping just the /usr/lib/x86_64-linux-gnu/libGL.so
symlink is consistent with what we currently do and makes the Wine build
work fine (see https://launchpad.net/~bryanquigley/+archive/ubuntu/wine-
sync-testing/+packages - arm failures are unrelated).

It's just the mesa dev package that makes the libGL.so symlink.

** Patch added: "Drop libGL.so symlink"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1609110/+attachment/4714293/+files/mesa_12.0.1-3ubuntu3.debdiff

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

Title:
  Do we still need the mesa or mesa-egl directories in /usr/lib/?

Status in mesa package in Ubuntu:
  New

Bug description:
  One of our mesa changes means we can't sync Wine packages (or wine-
  development stuck in proposed) from Debian.  See bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827770

  We purposely end up creating in /usr/lib/x86_64-linux-gnu
  mesa/ld.so.conf
  mesa/libGL.so -> libGL.so.1.2.0
  mesa/libGL.so.1 -> libGL.so.1.2.0
  mesa/libGL.so.1.2.0
  libGL.so -> mesa/libGL.so

  Debian on the other hand just creates:
  libGL.so.1 -> libGL.so.1.2.0
  libGL.so.1.2.0

  I haven't found a clear reason for the divergence.  I do see some
  comments about making it work with the alternates system. I'm not sure
  if that's current though.  Long term libglvnd should help there in a
  better way (IIUC).

  For reference Fedora does:
  /usr/lib64/libGL.so.1
  /usr/lib64/libGL.so.1.2.0

  Can we drop these Debian differences from mesa for Yakkety?

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

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


[Touch-packages] [Bug 1609110] Re: Do we still need the mesa or mesa-egl directories in /usr/lib/?

2016-08-04 Thread Bryan Quigley
I ran the wine build before mesa arm build had finished.  
This blocks both syncing wine (needs more work) and wine-development (has been 
syncing now stuck in proposed).

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

Title:
  Do we still need the mesa or mesa-egl directories in /usr/lib/?

Status in mesa package in Ubuntu:
  New

Bug description:
  One of our mesa changes means we can't sync Wine packages (or wine-
  development stuck in proposed) from Debian.  See bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827770

  We purposely end up creating in /usr/lib/x86_64-linux-gnu
  mesa/ld.so.conf
  mesa/libGL.so -> libGL.so.1.2.0
  mesa/libGL.so.1 -> libGL.so.1.2.0
  mesa/libGL.so.1.2.0
  libGL.so -> mesa/libGL.so

  Debian on the other hand just creates:
  libGL.so.1 -> libGL.so.1.2.0
  libGL.so.1.2.0

  I haven't found a clear reason for the divergence.  I do see some
  comments about making it work with the alternates system. I'm not sure
  if that's current though.  Long term libglvnd should help there in a
  better way (IIUC).

  For reference Fedora does:
  /usr/lib64/libGL.so.1
  /usr/lib64/libGL.so.1.2.0

  Can we drop these Debian differences from mesa for Yakkety?

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

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


[Touch-packages] [Bug 1589557] Re: [SRU]upstream stable point release 1.2.2

2016-08-04 Thread Brian Murray
** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  [SRU]upstream stable point release 1.2.2

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  New

Bug description:
  [Impact]

  Upstream releases 1.2.2 as a stable point release to the 1.2.x branch
  with a handy amount of bug fixes included. Most of the fixes are
  around the behavior when the status of link has changed.

  [Test case]

  After upgrading to 1.2.2, the user be able to use network-manager as
  usual, nothing that works with 1.2.0 should break with 1.2.2.
  errors.ubuntu.com should receive less reports than before.

  [Regression Potential]

  Code changes in this release are focusing on bug fixes, even there are
  some patches that aren't trivial they aren't likely to lead to
  significant regression.

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

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


[Touch-packages] [Bug 1337584] Re: Support sharing of Links

2016-08-04 Thread Joe Liau
On nexus 4 mako
Rc-proposed channel

I still cannot share linka from browser to text message. Only the title
of thr webpage shows up

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

Title:
  Support sharing of Links

Status in messaging-app:
  Fix Released
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  modify the share handler to support the content type Links such that
  links can be shared from the browser (or other apps). They should just
  be pasted into the text message, no MMS required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/messaging-app/+bug/1337584/+subscriptions

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


[Touch-packages] [Bug 1609215] Re: Merge grilo-plugins 0.3.2-1 (main) from Debian unstable (main)

2016-08-04 Thread Jeremy Bicha
ok, grilo-plugins is fixed, thanks!

https://launchpad.net/ubuntu/+source/grilo-plugins/0.3.2-1ubuntu2

** Changed in: grilo-plugins (Ubuntu)
   Status: New => Fix Committed

** Branch unlinked: lp:~jbicha/grilo/update-to-grilo-0.3

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

Title:
  Merge grilo-plugins 0.3.2-1 (main) from Debian unstable (main)

Status in grilo-plugins package in Ubuntu:
  Fix Committed
Status in rhythmbox package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Please merge grilo-plugins 0.3.2-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta:
* No-change rebuild against libgrilo-0.3-0
* d/p/0003-Revert-apple-trailers-Remove-stand-alone-C-apple-tra.patch: 
revert standalone
  C plugin, will look at moving lua-factory into -base next cycle (LP: 
1570157)
* debian/rules: don't install lua apple-trailers for now.
* d/p/0003-Revert-apple-trailers-Remove-stand-alone-C-apple-tra.patch: 
revert standalone
  C plugin, will look at moving lua-factory into -base next cycle (LP: 
1570157)
* debian/rules: don't install lua apple-trailers for now.
* New upstream release
* debian/control: Bump build-deps on libglib2.0-dev (>= 2.44), 
libgoa-1.0-dev (>= 3.17.91)
  and liblua5.3-dev. Drop build-dep on librest-dev.
* Update .install files for removed/renamed plugins
* debian/patches:
  - Drop git patches included in new version
  - video_sanitise_string-crash.patch, Dropped, affected function has been
removed
  - Cherry-pick git patches to fix build failures
* debian/rules: Remove obsolete --disable-bliptv configure flag
* Disable bliptv plugin this service has been shutdown (LP: #1498562)
* Merge from Debian unstable.  Remaining changes:
  - Split package into -base and -extra
  - Build with --fail-missing so we install everything.
  - debian/patches/0001-guardianvideos-fix-URL-format-string.patch:
Cherry-pick. guardianvideos: fix URL format string The online service
complains loudly if passed 1.0 instead of 1, let's make sure values are
formatted as integers.
* 
debian/patches/0001-grl-bookmarks-Notify-about-a-removal-if-there-was-no.patch:
  Take patch from upstream bug to fix notification of deletions.

  Remaining delta:
* Merge with Debian unstable.  Remaining changes:
  - Split package into -base and -extra
  - Build with --fail-missing to ensure we install everything.
* Have grilo-plugins-0.3-base install the Lua plugins (LP: #1570157)

  Changelog entries since current yakkety version 0.2.17-0ubuntu3:

  grilo-plugins (0.3.2-1) unstable; urgency=medium

* New upstream release.
* debian/control:
  - Require libgrilo 0.3.1.
  - Add build dependencies for the new chromaprint plugin:
libgstreamer1.0-dev, gstreamer1.0-tools, gstreamer1.0-plugins-bad.
  - List new plugins in the package description: Chromaprint, Acoustid,
iTunes Podcast, TheGamesDB.net.
* Drop the patch that allows co-installation with grilo-plugins 0.2.
  This was a temporary fix for the transition and it is no longer
  necessary.
  - debian/patches/v0.2-coinstall.patch:
+ Remove.
  - debian/install:
+ Update installation path.
  - debian/rules:
+ Don't rename example-tmdb.c anymore.
  - debian/control:
+ Make this package break and replace grilo-plugins-0.2.
* debian/copyright:
  - Update copyright attributions.

   -- Alberto Garcia   Mon, 20 Jun 2016 12:30:01 +0300

  grilo-plugins (0.3.1-1) unstable; urgency=medium

* New upstream release.
* debian/patches/fix-double-free.patch,
  debian/patches/fix-lua-factory-leak.patch:
  - Remove these patches, they are included in this release.
* debian/patches/v0.2-coinstall.patch
  - Refresh.
* debian/copyright:
  - Update copyright years and add missing attributions.
* debian/control:
  - Update build dependency on libgom to 0.3.2.
  - Update Standards-Version to 3.9.8.

   -- Alberto Garcia   Sun, 24 Apr 2016 21:35:49 +0300

  grilo-plugins (0.3.0-1.1) unstable; urgency=medium

* Non-maintainer upload.
* Upload to unstable.

   -- Michael Biebl   Tue, 19 Apr 2016 15:34:37 +0200

  grilo-plugins (0.3.0-1) experimental; urgency=medium

* New upstream release.
  - Rename grilo-plugins-0.2 to grilo-plugins-0.3.
* debian/control:
  - Downgrade build dependency on debhelper to >= 9, we are not
overriding dh_strip anymore.
* debian/patches:
  - Refresh all patches.
* Allow co-installing with grilo-plugins-0.2 by renaming all files and
  directories that have the same name. This is a temporary change that
  can be 

[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

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

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

** Tags added: patch

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Precise:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  In Progress

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

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


[Touch-packages] [Bug 388553] Re: Wi-Fi Protected Setup (WPS) not supported

2016-08-04 Thread Sven R. Kunze
Still not working on Ubuntu 16.04. :(

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

Title:
  Wi-Fi Protected Setup (WPS) not supported

Status in Ayatana Design:
  New
Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  As the title the Wi-Fi Protected Setup (WPS) is not supported by
  NetworkManager (but is supported by wpa_supplicant).

  The WPS WI-Fi standard is implementated in various newer access points
  and allow user to configure the access point in just a few of steps
  and do all configuring process very simple.

  Specifications: http://www.wi-fi.org/wifi-protected-setup/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/388553/+subscriptions

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


[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

2016-08-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/dbus-cpp/dbus-cpp-ubuntu-yakkety-
landing-028

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Released
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

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


[Touch-packages] [Bug 1526877] Re: Dbus errors in the console when closing the music-app

2016-08-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/dbus-cpp/dbus-cpp-ubuntu-yakkety-
landing-028

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

Title:
  Dbus errors in the console when closing the music-app

Status in Canonical System Image:
  Fix Released
Status in Ubuntu Music App:
  Invalid
Status in dbus-cpp package in Ubuntu:
  Confirmed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released

Bug description:
  Due to bug 1434584 being fixed when you swipe to close an application
  the following appears in the log, note the dbus errors, and that I am
  not able to reproduce this on the desktop.

  
  ** Application is now inactive
  Attempted to deliver an event to a non-existent window, ignoring.
  virtual bool QMediaPlaylist::setMediaObject(QMediaObject*)
  void QMediaPlaylistPrivate::syncControls(QMediaPlaylistControl*, 
QMediaPlaylistControl*)
  void AalMediaPlayerService::deletePlaylistControl()
  virtual AalMediaPlaylistProvider::~AalMediaPlaylistProvider()
  void AalMediaPlaylistProvider::disconnect_signals()
  virtual AalMediaPlaylistControl::~AalMediaPlaylistControl()
  void AalMediaPlayerService::deleteMediaPlayerControl()
  void AalMediaPlayerService::destroyPlayerSession()
  PlaybackStatusChanged signal arrived via the bus (Status: 
PlaybackStatus::ready)
  PlaybackStatusChanged signal arrived via the bus (Status: 
PlaybackStatus::stopped)
  OnTrackListReset signal arrived via the bus.
  Attempted to unregister path (path[0] = com path[1] = canonical) which isn't 
registered
  process 6617: arguments to dbus_connection_close() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2935.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_close() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2935.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  Sdk-Launcher> Stopping Application
  Sdk-Launcher> The Application exited, cleaning up
  Sdk-Launcher> Finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526877/+subscriptions

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


[Touch-packages] [Bug 1567744] Re: USB NICs get too long name for ifupdown aliases

2016-08-04 Thread Andreas Hasenack
I renamed the NIC in the MAAS node page to enx0 to workaround this
issue.

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

Title:
  USB NICs get too long name for ifupdown aliases

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I have a USB NIC that is connected to my denial system. I tried to
  create an alias, and after reboot, it wasn't created. When I manually
  try to bring it up I have the error.

  /e/n/i:

  auto enx000ec688b79f
  iface enx000ec688b79f inet static
  address 10.90.90.1
  netmask 255.255.255.0

  auto enx000ec688b79f:1
  iface enx000ec688b79f:1 inet static
  address 192.168.100.1
  netmask 255.255.255.0

  ubuntu@maas00:~$ sudo ifup enx000ec688b79f
  ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
  RTNETLINK answers: Numerical result out of range
  Failed to bring up enx000ec688b79f:1.

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

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


[Touch-packages] [Bug 1567744] Re: USB NICs get too long name for ifupdown aliases

2016-08-04 Thread Andreas Hasenack
@andres that's a cool feature, btw :)

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

Title:
  USB NICs get too long name for ifupdown aliases

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I have a USB NIC that is connected to my denial system. I tried to
  create an alias, and after reboot, it wasn't created. When I manually
  try to bring it up I have the error.

  /e/n/i:

  auto enx000ec688b79f
  iface enx000ec688b79f inet static
  address 10.90.90.1
  netmask 255.255.255.0

  auto enx000ec688b79f:1
  iface enx000ec688b79f:1 inet static
  address 192.168.100.1
  netmask 255.255.255.0

  ubuntu@maas00:~$ sudo ifup enx000ec688b79f
  ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
  RTNETLINK answers: Numerical result out of range
  Failed to bring up enx000ec688b79f:1.

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

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


[Touch-packages] [Bug 1587093] Re: "Reached target shutdown" message seen, but laptop won't turn off, just hangs and needs the laptop's button.

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

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

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

Title:
  "Reached target shutdown" message seen, but laptop won't turn off,
  just hangs and needs the laptop's button.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

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

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-08-04 Thread Dan Streetman
yakkety build also at ppa

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Precise:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  In Progress

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-08-04 Thread Dan Streetman
** Patch added: "lp1609898-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+attachment/4714232/+files/lp1609898-yakkety.debdiff

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Precise:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  In Progress

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

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


[Touch-packages] [Bug 1595177] Re: [SRU] Update apt/xenial to 1.2.14

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

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

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

Title:
  [SRU] Update apt/xenial to 1.2.14

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  (This is a template for now, so I can close the bug in the 1.2.14
  upload)

  [Impact]
  We intend to upload APT 1.2.14 to xenial under the new "micro upstream 
release" policy.

  Apart from fixing bug 1573547, it also updates translations fixes the
  following other bugs:

  [[1.2.13]]

  Segmentation fault fixes:
  * fail instead of segfault on unreadable config files (Closes: 824503)

  Fixes for 3rd party programs using libapt and C++ locale API:
  * prevent C++ locale number formatting in text APIs (Closes: #825396)

  Fix for hurd (not really affecting us here, but upstream):
  * apt-key: change to / before find to satisfy its CWD needs.
    Thanks to Samuel Thibault for 'finding' the culprit! (Closes: 826043)

  Leak fixes:
  * do not hang on piped input in PipedFileFdPrivate
  * don't leak an FD in lz4 (de)compression
  * don't leak FD in AutoProxyDetect command return parsing

  [[1.2.14]]
  Regression fix from 1.2.13:
    * do not error if auto-detect-proxy cmd has no output (Closes: 827713)
  Huge apt-ftparchive performance regression fix from 1.1:
    * Reinstate caching of file hashes in apt-ftparchive (Closes: #806924)
  Tiny bug fixes, about 2 lines each:
    * source: if download is skipped, don't try to unpack
    * ensure filesize of deb is included in the hashes list

  [Test case]
  The releases follow new upstream micro release rule and thus are assumed to 
be tested by our integration test suite. There are two exceptions which cannot 
be tested:

  * prevent C++ locale number formatting in text APIs
  * apt-key: change to / before find to satisfy its CWD needs

  The first has no affected code in the archive (but maybe 3rd party
  code), the second only affects hurd.

  [Regression Potential]
  Very low. The release has been tested by a thorough integration test suite on 
Travis CI, Debian autopkgtests, and has been in Debian unstable since 
2016-06-22.

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

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


[Touch-packages] [Bug 1609707] Re: lxc in Power8 System

2016-08-04 Thread Stéphane Graber
You will also need to upgrade to the 4.4 kernel (linux-generic-lts-
xenial) if you want containers to actually work as prior kernels for
power8 didn't properly support seccomp.

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

Title:
  lxc in Power8 System

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  fenris@bigsoftware:~$ uname -a
  Linux bigsoftware 3.19.0-28.31-openpower1-generic #openpower1 SMP Wed Sep 9 
10:34:29 AEST 2015 ppc64le ppc64le ppc64le GNU/Linux
  fenris@bigsoftware:~$ lxc
  No command 'lxc' found, did you mean:
   Command 'lc' from package 'mono-devel' (main)
   Command 'lpc' from package 'lprng' (universe)
   Command 'lpc' from package 'cups-bsd' (main)
   Command 'lpc' from package 'lpr' (universe)
  lxc: command not found
  fenris@bigsoftware:~$ dpkg -l | grep lxc
  ii  liblxc1   1.0.8-0ubuntu0.3
ppc64el  Linux Containers userspace tools (library)
  ii  lxc   1.0.8-0ubuntu0.3
ppc64el  Linux Containers userspace tools
  ii  lxc-templates 1.0.8-0ubuntu0.3
ppc64el  Linux Containers userspace tools (templates)
  ii  python3-lxc   1.0.8-0ubuntu0.3
ppc64el  Linux Containers userspace tools (Python 3.x bindings)

  fenris@bigsoftware:~$ cat /etc/issue
  Ubuntu 14.04.5 LTS \n \l

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

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


[Touch-packages] [Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

2016-08-04 Thread Ryan Harper
Can you explain which part fails?

"ifupdown fails to set the device's mtu, which causes its attempt to set
the ipv6 mtu to fail"

This is the change that drove the use of sysctl to set mtu:

https://anonscm.debian.org/git/collab-
maint/ifupdown.git/commit/?id=a1b2cfea935d91961dc2df3ac5cfe6668bcf

which comes from bug: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809714

and the tl;dr is that IPv6 supports per protocol, rather than interface.

It appears that we want the opposite here; so it's not quite clear how
to resolve this.

In the case that the user doesn't want the underlying interface MTU to
change, then the sysctl is needed to change the MTU *only* for IPv6.

In the original bug where one is comparing ip output of MTU; is there
something *not* working ?  Or did we just observe that the bond
interface isn't the same MTU?  Can we confirm that without the bond
interface itself set to MTU 9202 that we don't see the correct jumbo
frames over ipv6?



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

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

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

Title:
  ifupdown does not set ipv6-only large mtu

Status in ifupdown package in Ubuntu:
  Incomplete

Bug description:
  ifupdown changes a device's mtu differently, between "inet" section
  mtu and "inet6" section mtu.  For "inet", ifupdown changes the
  device's mtu, using 'ip link set DEV mtu NNN'.  However for "inet6",
  ifupdown changes the interface's IPv6 mtu, using 'sysctl -q -e -w
  net.ipv6.conf.DEV.mtu=NNN'.

  The problem is that a device's ipv6 mtu cannot be larger than the
  device mtu.  Normally this is not a problem; the main reason a device
  needs a separate ipv6 mtu is to support ipv6 tunneling inside ipv4
  (e.g. 6in4 or 6rd), so ifupdown would also have a ipv4 "inet" section
  that contained a larger mtu (or, the ipv6 section would have a lower-
  than-default mtu).

  But, in the case of an interface that is configured only for ipv6
  *and* large frames (e.g. 9000 mtu), there is only an "inet6" section
  in the ifupdown config, and so ifupdown fails to set the device's mtu,
  which causes its attempt to set the ipv6 mtu to fail.

  I believe the correct behavior is for ifupdown to check if there is
  any "inet" config section for the same device as the "inet6" section,
  and if there is not then it should change the device mtu as well as
  the ipv6 mtu.  Additionally, the "inet6" configuration must be done
  after the "inet" configuration for the same device, since the ipv6 mtu
  can't be higher than the device mtu.

  I don't see any easy way to add that logic to inet6.defn, however...

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

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-08-04 Thread Chris J Arges
** Also affects: isc-dhcp (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Dan Streetman (ddstreet)
   Status: In Progress

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Precise:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  In Progress

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

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


[Touch-packages] [Bug 1609919] Re: Need "pivot_root" and "change_profile" exceptions for the unconfined template

2016-08-04 Thread Tyler Hicks
A bare pivot_root rule would be acceptable to add to the unconfined
template. We probably wouldn't want to add a bare change_profile rule to
the template but could possibly add a set of rules that allow
change_profile to anything except for "unconfined".

Another option would be to create a new template that allows a bare
change_profile rule.

Christopher is currently investigating the option of shipping the
Libertine Manager UI as a deb, instead of a click, so we may not need to
adjust the template for these two sets of rules if that provides a
viable path forward.

** Summary changed:

- Need "pivot_root" and "change_profile" exceptions for the unconfined temple
+ Need "pivot_root" and "change_profile" exceptions for the unconfined template

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

Title:
  Need "pivot_root" and "change_profile" exceptions for the unconfined
  template

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New

Bug description:
  Per discussion on IRC, in order to support the Libertine Manager UI
  click package, we would need the "pivot_root" and "change_profile"
  exceptions added to the unconfined template in order for it to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1609919/+subscriptions

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


[Touch-packages] [Bug 1609919] [NEW] Need "pivot_root" and "change_profile" exceptions for the unconfined template

2016-08-04 Thread Christopher Townsend
Public bug reported:

Per discussion on IRC, in order to support the Libertine Manager UI
click package, we would need the "pivot_root" and "change_profile"
exceptions added to the unconfined template in order for it to work.

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

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

Title:
  Need "pivot_root" and "change_profile" exceptions for the unconfined
  template

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New

Bug description:
  Per discussion on IRC, in order to support the Libertine Manager UI
  click package, we would need the "pivot_root" and "change_profile"
  exceptions added to the unconfined template in order for it to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1609919/+subscriptions

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


[Touch-packages] [Bug 1600124] Re: Adjust KBL PCI-ID's

2016-08-04 Thread Seth Forshee
Verified that i915_bpo.ko in 4.4.0-34.53 reflects the PCI id changes
from the patches.

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

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

Title:
  Adjust KBL PCI-ID's

Status in libdrm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in libdrm source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in xserver-xorg-video-intel source package in Xenial:
  New

Bug description:
  Current list of KBL PCI-ID's is incomplete, there are a few that are
  should not be listed and few that are missing. To fix this, adjust the
  list in kernel/libdrm/mesa/ddx to match upstream.

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

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


[Touch-packages] [Bug 1523948] Re: L2TP VPN support

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

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

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

Title:
  L2TP VPN support

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  It should be possible to configure a L2TP VPN, not just OpenVPN.

  Related to bug #1495553.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523948/+subscriptions

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


[Touch-packages] [Bug 1285444] Re: Login Successful, Desktop Never Loads

2016-08-04 Thread Hiklo
Having a similar issue, but when i try to log in (bot with guest and
main user) i get thrown out and not frozen. The issue seem to be
something about openConnect

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

Title:
  Login Successful, Desktop Never Loads

Status in at-spi2-core package in Ubuntu:
  Triaged

Bug description:
  Here is what I encounter
  1. Boot computer, boot proceeds normally
  2. Reach standard Ubuntu login screen, nothing seems to be amiss
  3. Enter user name and password
  4. Login disappears, just see the pink "Ubuntu 14.04" background

  The desktop never loads, not even after ~30 minutes. The launcher
  never appears, and the Desktop background never changes to the user-
  configured background.

  Other features:
  * Cursor works fine, it can be moved around the screen
  * No error messages pop up
  * ALT+F1 etc. can be used to switch to different TTYs; all files on the 
system appear to be intact
  * Print screen button works (I will upload a screen shot when I get a chance 
to copy it onto a USB drive)
  * Hitting power button pops up a window prompting the user to decide whether 
to shut down
  * CTRL+ALT+DELETE prompts the user to log out
  * Desktop does not load on any user accounts, including the guest account

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions

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


[Touch-packages] [Bug 1594816] Re: GtkSwitch button background overflows the border

2016-08-04 Thread Dmitry Shachnev
I can include this in my Xenial ubuntu-themes upload, can you please add
the SRU paperwork?

** Also affects: ubuntu-themes (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  GtkSwitch button background overflows the border

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  New

Bug description:
  Where GtkSwitch is used, for example in the Screen Display section of
  Unity Control Center the background of the toggle buttons appears
  outside of the borders.

  See attached screenshot for an example.

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

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


[Touch-packages] [Bug 1442655] Re: typo in man xtables-multi man page

2016-08-04 Thread Hans Joachim Desserud
As mentioned by the bug watch updater, the patch has been applied in
Debian and is fixed in iptables version 1.6.0-3.

Though since Ubuntu has some additional patches for this package, it
will need to be merged in order for the fix to appear in Ubuntu.

** Tags removed: vivid wily
** Tags added: needs-debian-merge xenial yakkety

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

Title:
  typo in man xtables-multi man page

Status in One Hundred Papercuts:
  Confirmed
Status in iptables package in Ubuntu:
  Confirmed
Status in iptables package in Debian:
  Fix Released

Bug description:
  In the man page for "xtables-multi" there is a reference to
  "ip6tables-resotre".

  The correct reference would be "ip6tables-restore".

  Attached patch fixes it.

  Mark

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

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


[Touch-packages] [Bug 1584393] Re: systemctl restart networking hangs reloading ssh.service

2016-08-04 Thread Brian Murray
Hello Gustavo, or anyone else affected,

Accepted openssh into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:7.2p2-4ubuntu2 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: openssh (Ubuntu Xenial)
   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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1584393

Title:
  systemctl restart networking hangs reloading ssh.service

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  Issues "systemctl restart networking" never exits. It hangs during a
  call to "systemctl reload ssh.service":

  ● networking.service - Raise network interfaces
 Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor 
preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
 Active: activating (start) since Sat 2016-05-21 21:41:58 UTC; 18s ago
   Docs: man:interfaces(5)
Process: 1288 ExecStop=/sbin/ifdown -a --read-environment (code=exited, 
status=0/SUCCESS)
Process: 1376 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] 
&& [ -n "$(ifquery --read-environment --list --exclude=lo)" ] &
   Main PID: 1383 (ifup)
  Tasks: 7 (limit: 512)
 Memory: 1.8M
CPU: 111ms
 CGroup: /system.slice/networking.service
 ├─1383 /sbin/ifup -a --read-environment
 ├─1479 /sbin/dhclient -1 -v -pf /run/dhclient.enp0s3.pid -lf 
/var/lib/dhcp/dhclient.enp0s3.leases -I -df /var/lib/dhcp/dhclient6
 ├─1480 /bin/sh -c /bin/run-parts --exit-on-error 
/etc/network/if-up.d
 ├─1481 /bin/run-parts --exit-on-error /etc/network/if-up.d
 ├─1504 /bin/sh /etc/network/if-up.d/openssh-server
 ├─1507 /bin/sh /usr/sbin/invoke-rc.d ssh reload
 └─1527 systemctl reload ssh.service

  Then issuing the same command from another terminal causes the first
  to exit successfully (the second also exists successfully).

  On the official vagrant image, I get this problem independently of
  whether the command is issued through and ssh session. I've gotten the
  same behavior on the official xenial AMIs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May 21 21:35:08 2016
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-08-04 Thread Dan Streetman
Patched builds for precise, trusty, xenial at ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1609898

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-08-04 Thread Dan Streetman
** Patch added: "lp1609898-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+attachment/4714183/+files/lp1609898-xenial.debdiff

** Changed in: isc-dhcp (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => Medium

** Changed in: isc-dhcp (Ubuntu)
   Status: New => In Progress

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-08-04 Thread Dan Streetman
** Patch added: "lp1609898-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+attachment/4714182/+files/lp1609898-trusty.debdiff

** Patch removed: "lp1609898.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+attachment/4714179/+files/lp1609898.debdiff

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-08-04 Thread Dan Streetman
** Patch added: "lp1609898-precise.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+attachment/4714181/+files/lp1609898-precise.debdiff

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

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


[Touch-packages] [Bug 1593048] Re: ubuntu-themes should support GTK 3.20

2016-08-04 Thread Jeremy Bicha
** Changed in: mate-themes (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  ubuntu-themes should support GTK 3.20

Status in arc-theme package in Ubuntu:
  Fix Committed
Status in breeze-gtk package in Ubuntu:
  Fix Committed
Status in lubuntu-artwork package in Ubuntu:
  Fix Committed
Status in mate-themes package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-artwork package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Fix Committed

Bug description:
  This is a tracking bug. ubuntu-themes needs to be updated to support
  GTK+ 3.20 before GTK+ 3.20 can land in Ubuntu.

  Some initial work has been done at
  https://code.launchpad.net/~laney/ubuntu-themes/gtk320

  If you would like to help, please contact the Ubuntu Desktop Team.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arc-theme/+bug/1593048/+subscriptions

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-08-04 Thread Dan Streetman
** Patch added: "lp1609898.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+attachment/4714179/+files/lp1609898.debdiff

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

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


[Touch-packages] [Bug 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working

2016-08-04 Thread Kevin DuBois
Have a spike-prototype working of bypassing buffers. Still more work to
do with atomic multi-bufferstream updates, and sorting out the nested
platform, but goal is within reach...

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

Title:
  Nested servers prevent overlays or fullscreen bypass from working

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  New

Bug description:
  Nested servers prevent fullscreen bypass from working.

  This would explain why nesting fullscreen clients is measurably slower than 
non-nesting:
  Direct (bypass) 2600
  Direct (bypass off) 2400
  Nested (bypass) 2450
  Nested (bypass off) 2330

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

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


[Touch-packages] [Bug 1540108] Re: Blue dots for text marking/placing a cursor are too small

2016-08-04 Thread Christian Dywan
You seem to be hitting bug 1484825 judging by the text handlers ("blue
thing") being offset on your screenshot.

1. Touch one of the handlers with your finger.
2. Move it left or right to change the selection.
3. A menu should show up automatically.

1. Long-press a word to select it.
2. A menu should show up automatically.

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

Title:
  Blue dots for text marking/placing a cursor are too small

Status in Ubuntu UX:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I mean the blue dots that are visible in the photo. Ok my hands are not the 
smallest but I saw already bigger ones. I can not place the cursor in the text 
where I want to as well as mark/highlight the text to cut or copy. On Android 
these dots are big raindrops. I have no problem. In Ubuntu it simply doesn't 
work at all without a touchpen. These dots are too tiny.
  --
  I'm updating the bug with an additional information which is actually another 
problem which You can see in the photo in a comment #3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1540108/+subscriptions

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


[Touch-packages] [Bug 1342400] Re: avahi-daemon constantly reporting "Invalid response packet from host"

2016-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package avahi - 0.6.31-4ubuntu1.1

---
avahi (0.6.31-4ubuntu1.1) trusty; urgency=medium

  * debian/patches/lp-1342400-invalid-response-packet.patch:
- Stop printing "Invalid response packet" messages to system log, they can
  occur frequently filling the logs from some mDNS stacks.  Patch from
  upstream commit de7cde877e4daa5d9d4fb5b1a349299eaa94969d (LP: #1342400)

 -- Trent Lloyd   Fri, 10 Jun 2016 07:12:31
+

** Changed in: avahi (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 avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1342400

Title:
  avahi-daemon constantly reporting "Invalid response packet from host"

Status in avahi package in Ubuntu:
  Fix Released
Status in avahi source package in Precise:
  Fix Released
Status in avahi source package in Trusty:
  Fix Released
Status in avahi package in Debian:
  Fix Released

Bug description:
  After installing Ubuntu 14.04 (Release: 14.04) and looking for other
  information in /var/log/syslog, I see that syslog is being flooded by
  "Invalid response packet from host" messages from avahi-daemon.

  I searched around to see why this might be and ran across the following avahi 
mailing list post along with a patch to fix it:
  http://lists.freedesktop.org/archives/avahi/2012-July/002171.html

  >>>
  I would say you can safely ignore it, since any machine on your
  network running a recent OSX version will cause these messages.
  Here's a patch with what we change to avoid these messages flooding
  syslog.

  -Justin
  <<<

  The patch which fixes this is here:
  
http://lists.freedesktop.org/archives/avahi/attachments/20120719/1e71846e/attachment.obj

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

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


[Touch-packages] [Bug 1609215] Re: Merge grilo-plugins 0.3.2-1 (main) from Debian unstable (main)

2016-08-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~jbicha/grilo/update-to-grilo-0.3

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

Title:
  Merge grilo-plugins 0.3.2-1 (main) from Debian unstable (main)

Status in grilo-plugins package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Please merge grilo-plugins 0.3.2-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta:
* No-change rebuild against libgrilo-0.3-0
* d/p/0003-Revert-apple-trailers-Remove-stand-alone-C-apple-tra.patch: 
revert standalone
  C plugin, will look at moving lua-factory into -base next cycle (LP: 
1570157)
* debian/rules: don't install lua apple-trailers for now.
* d/p/0003-Revert-apple-trailers-Remove-stand-alone-C-apple-tra.patch: 
revert standalone
  C plugin, will look at moving lua-factory into -base next cycle (LP: 
1570157)
* debian/rules: don't install lua apple-trailers for now.
* New upstream release
* debian/control: Bump build-deps on libglib2.0-dev (>= 2.44), 
libgoa-1.0-dev (>= 3.17.91)
  and liblua5.3-dev. Drop build-dep on librest-dev.
* Update .install files for removed/renamed plugins
* debian/patches:
  - Drop git patches included in new version
  - video_sanitise_string-crash.patch, Dropped, affected function has been
removed
  - Cherry-pick git patches to fix build failures
* debian/rules: Remove obsolete --disable-bliptv configure flag
* Disable bliptv plugin this service has been shutdown (LP: #1498562)
* Merge from Debian unstable.  Remaining changes:
  - Split package into -base and -extra
  - Build with --fail-missing so we install everything.
  - debian/patches/0001-guardianvideos-fix-URL-format-string.patch:
Cherry-pick. guardianvideos: fix URL format string The online service
complains loudly if passed 1.0 instead of 1, let's make sure values are
formatted as integers.
* 
debian/patches/0001-grl-bookmarks-Notify-about-a-removal-if-there-was-no.patch:
  Take patch from upstream bug to fix notification of deletions.

  Remaining delta:
* Merge with Debian unstable.  Remaining changes:
  - Split package into -base and -extra
  - Build with --fail-missing to ensure we install everything.
* Have grilo-plugins-0.3-base install the Lua plugins (LP: #1570157)

  Changelog entries since current yakkety version 0.2.17-0ubuntu3:

  grilo-plugins (0.3.2-1) unstable; urgency=medium

* New upstream release.
* debian/control:
  - Require libgrilo 0.3.1.
  - Add build dependencies for the new chromaprint plugin:
libgstreamer1.0-dev, gstreamer1.0-tools, gstreamer1.0-plugins-bad.
  - List new plugins in the package description: Chromaprint, Acoustid,
iTunes Podcast, TheGamesDB.net.
* Drop the patch that allows co-installation with grilo-plugins 0.2.
  This was a temporary fix for the transition and it is no longer
  necessary.
  - debian/patches/v0.2-coinstall.patch:
+ Remove.
  - debian/install:
+ Update installation path.
  - debian/rules:
+ Don't rename example-tmdb.c anymore.
  - debian/control:
+ Make this package break and replace grilo-plugins-0.2.
* debian/copyright:
  - Update copyright attributions.

   -- Alberto Garcia   Mon, 20 Jun 2016 12:30:01 +0300

  grilo-plugins (0.3.1-1) unstable; urgency=medium

* New upstream release.
* debian/patches/fix-double-free.patch,
  debian/patches/fix-lua-factory-leak.patch:
  - Remove these patches, they are included in this release.
* debian/patches/v0.2-coinstall.patch
  - Refresh.
* debian/copyright:
  - Update copyright years and add missing attributions.
* debian/control:
  - Update build dependency on libgom to 0.3.2.
  - Update Standards-Version to 3.9.8.

   -- Alberto Garcia   Sun, 24 Apr 2016 21:35:49 +0300

  grilo-plugins (0.3.0-1.1) unstable; urgency=medium

* Non-maintainer upload.
* Upload to unstable.

   -- Michael Biebl   Tue, 19 Apr 2016 15:34:37 +0200

  grilo-plugins (0.3.0-1) experimental; urgency=medium

* New upstream release.
  - Rename grilo-plugins-0.2 to grilo-plugins-0.3.
* debian/control:
  - Downgrade build dependency on debhelper to >= 9, we are not
overriding dh_strip anymore.
* debian/patches:
  - Refresh all patches.
* Allow co-installing with grilo-plugins-0.2 by renaming all files and
  directories that have the same name. This is a temporary change that
  can be reverted once the transition to grilo-plugins-0.3 is complete.
  - debian/install:
+ Use /usr/share/grilo-plugins-0.3.
  - debian/rules:
+ Rename example-tmdb.c to 

[Touch-packages] [Bug 1607552] Re: Blue dots for highlighting a text/cursor control can not be placed over the cursor

2016-08-04 Thread Christian Dywan
*** This bug is a duplicate of bug 1484825 ***
https://bugs.launchpad.net/bugs/1484825

** This bug is no longer a duplicate of bug 1540108
   Blue dots for text marking/placing a cursor are too small
** This bug has been marked a duplicate of bug 1484825
   Text handle in the wrong position when the text field moves

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

Title:
  Blue dots for highlighting a text/cursor control can not be placed
  over the cursor

Status in Ubuntu UX:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Just because we cover everything with the finger and are unable to
  place the cursor where we want to. Correct is a BIG raindrop(Android)
  >under< the cursor so that we can put the finger on a blue control
  point and precisely put the cursor where we want to. On Ubuntu Touch:
  Mission impossible!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1607552/+subscriptions

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


[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

2016-08-04 Thread Todor Kouyoumdjiev
I have absolute the same behaviour as Dadio describe it, except that the
phone is bq 4.5 Aquaris. With Audi bluetooth system the phone is OK and
the car system doesn't recongnize it. On Mercedes car bluetooth system
the phone connects normally.

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions

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


[Touch-packages] [Bug 1609745] Re: Touch screen not working on Acer Chromebook R11

2016-08-04 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7

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

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

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

Title:
  Touch screen not working on Acer Chromebook R11

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

Bug description:
  Touch screen seems to be identified as far as I can see, but there's
  no working input. I've tried among else xinput test-xi2, reattach
  command but it seems simply non-functional for whatever reason.

  It works on the ChromeOS side.

  I'll add kernel to the bug report since it might be on that side.

  The machine is Acer Chromebook R11 (codename CYAN), Intel Braswell
  platform.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  BootLog: H-STATE: clean, 343470/1638400 files, 2175315/6546944 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:02:31 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Braswell Integrated Graphics Controller [8086:22b1] (rev 
21) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  version.compiz: compiz 1:0.9.13.0+16.10.20160726.4-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu4
  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.0-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 Aug  4 13:59:45 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu4
  xserver.video_driver: modeset
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek 

[Touch-packages] [Bug 1609898] [NEW] dhclient incorrectly assumes a /64 ipv6 prefix

2016-08-04 Thread Dan Streetman
Public bug reported:

[Impact]

clients who get an ipv6 address from a dhcpv6 server assume the address
has a /64 prefix, but that is not necessarily true, and if the subnet is
different than /64 those clients will not be able to reach other
addresses in that /64 prefix because the other systems are not on-link.
This /64 assumption of dhclient effectively breaks the client networking
for certain addresses.

[Test Case]

Set up a server with two interface nics, and one client connected to
each of those interfaces.  On the server, set up a ipv6 subnet on each
interface, with a larger prefix than /64, e.g.:

2001:db8:0:0:1::/96
2001:db8:0:0:2::/96

configure dhcpv6 on the server, to provide ipv6 addresses on each
interface.  Set the server as the default ipv6 route for the clients.

Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
clients will each get a ipv6 address with a /64 prefix, due to the bug
in dhclient.

Try to ping (or otherwise communicate) between the clients.  Since they
have /64 prefixes, they think they are on-link with each other, but they
are not, so they can't communicate.

After the dhclient bug is fixed, repeat the above setup, and the clients
will get /128 prefixes instead, and then will be able to communicate
with each other, because they will route the traffic to each other
through the server.

[Regression potential]

None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
are broken, this fixes that.

[Other info]

This is fixed in debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

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


[Touch-packages] [Bug 1604617] Re: dhclient does not send fqdn.fqdn for DHCPv6

2016-08-04 Thread EdwardClay
I'm also experiencing this issue in 16.04 LTS.

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

Title:
  dhclient does not send fqdn.fqdn for DHCPv6

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  ISC DHCP's dynamic DNS updates rely on the fqdn.fqdn option being sent
  in order to work for DHCPv6.  This used to be done in Ubuntu, as shown
  in bugs #991360 and #108862, and all my Windows hosts send it.
  However this was removed in Ubuntu due to a regression in IPv4
  functionality.

  As IPv6 is more widely deployed these days, this regression in IPv6 should be 
fixed.  This bug is
  current as of Ubuntu 16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1604617/+subscriptions

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


[Touch-packages] [Bug 1609891] Re: package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2

2016-08-04 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: subprocess
  new pre-installation script returned error exit status 2

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Upgrading from 14.04.3 to 16.04.1

  Noted during install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.98-6ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-65-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Aug  4 09:10:47 2016
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  InstallationDate: Installed on 2015-08-19 (351 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: lvm2
  Title: package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: subprocess 
new pre-installation script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago)

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

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


  1   2   3   >