[Touch-packages] [Bug 1616314] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[Hayato Hirata]

Public bug reported:

I do not have further information.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Fri Aug 19 18:13:45 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-09-10 (349 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Build i386 LIVE Binary 
20140428-16:49
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2016-08-19 (4 days ago)

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I do not have further information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Fri Aug 19 18:13:45 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-09-10 (349 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Build i386 LIVE Binary 
20140428-16:49
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-19 (4 days ago)

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

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

[Touch-packages] [Bug 1595485] Re: packages to remove from yakkety

[Martin Pitt]

I removed "python-pysam python3-pysam python-pysam-tests" from yakkety
and y-proposed on i386.

** Changed in: python-pysam (Ubuntu)
   Status: New => Fix Released

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

Title:
  packages to remove from yakkety

Status in flightgear package in Ubuntu:
  Invalid
Status in fpc package in Ubuntu:
  Incomplete
Status in fslview package in Ubuntu:
  Fix Released
Status in gnome-video-arcade package in Ubuntu:
  Fix Released
Status in insighttoolkit package in Ubuntu:
  Fix Released
Status in libpng package in Ubuntu:
  Fix Released
Status in mame package in Ubuntu:
  Fix Released
Status in pepperflashplugin-nonfree package in Ubuntu:
  Fix Released
Status in ppc64-diag package in Ubuntu:
  Fix Released
Status in python-pysam package in Ubuntu:
  Fix Released
Status in runit package in Ubuntu:
  New
Status in samtools package in Ubuntu:
  Fix Released
Status in simgear package in Ubuntu:
  Invalid
Status in singular package in Ubuntu:
  New
Status in stacks package in Ubuntu:
  Fix Released
Status in vcmi package in Ubuntu:
  Fix Released
Status in vmtk package in Ubuntu:
  Fix Released
Status in vtk package in Ubuntu:
  Fix Released
Status in fpc package in Debian:
  Fix Released

Bug description:
  (NOTE: all of them are gone from Debian)
  1) libpng.
  Superseded by libpng16

  no reverse dependencies I can see
  2) insighttoolkit
  Superseded by insighttoolkit4
  it doesn't build on powerpc, so we have to remove binaries here
  (sorry, but Debian maintains only amd64 and i386, and we can't maintain all 
the others including powerpc)

  just removing vmtk/powerpc should allow its removal too

  3) vtk
  Superseded by vtk6

  needs vmtk migration
  and fslview removal or demote to proposed.
  Debian broke it, because it is already broken, and it has little fix in time 
probability
  (probably we will remove in Debian soon)

  4) samtools
  old binaries left on armhf: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on powerpc: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on s390x: libbam-dev, samtools (from 0.1.19-1ubuntu1)

  removed in Debian too

  5) pepperflashplugin-nonfree [i386]
  please remove on i386 (removed in Debian too)
  upstream is not supporting it, so it can't be downloaded/installed on i386 
anymore

  6) singular [armhf]
  removed in Debian too

  7) fpc [powerpc]
  powerpc sadness with glib 2.23
  https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1562480

  8) mame [ppc64el]
  sandness on that arch, removed in Debian

  9) flightgear [armhf]
  I don't care about simgear/armhf, because it is unlikely for such a game to 
run on thar architecture.

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

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

[Touch-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore

[Aravind Gopal]

Printer driver is of epson.  iscan, scanlite, simple scan is not
scaning. Simple scan opens only though sudo and konsole. screenshot
attached. iscan and scanlite shows error message.

** Attachment added: "Screenshot_20160824_110020.png"
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1536353/+attachment/4726767/+files/Screenshot_20160824_110020.png

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

Title:
  [Regression] Epson's printer driver packages cannot be installed as
  lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore

[Aravind Gopal]

printer driver changed to epson. reinstalled epson scan driver again,
Simple scan can be opened through console, but cannot scan. Log file
attached. ?field.comment=printer driver changed to epson. reinstalled
epson scan driver again, Simple scan can be opened through console, but
cannot scan. new Log file attached.

** Attachment added: "log"
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1536353/+attachment/4726766/+files/log

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

Title:
  [Regression] Epson's printer driver packages cannot be installed as
  lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1612767] Re: Drop appmenu-qt5 from default installations

[Timo Jyrinki]

Ok I've the same problem:

https://launchpadlibrarian.net/280573314/buildlog_ubuntu-yakkety-amd64
.qtbase-opensource-src_5.6.1+dfsg-3ubuntu3~1_BUILDING.txt.gz

It seems it's something new in the last two weeks in yakkety, and not
related to Qt changes. Maybe glibc 2.24 related?

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

Title:
  Drop appmenu-qt5 from default installations

Status in indicator-appmenu package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Currently we are using appmenu-qt5 as our platform theme on desktop,
  however it has many disadvantages, which make me want to get rid of
  it:

  1) Its design is a hack: instead of the using normal QPA API for
  getting the menu, it retrieves the menu bar using QWidget::findChild,
  and then casts the pointer to QMenu*. The normal methods (which are
  getting called by Qt) remain empty stubs.

  2) It is preventing applications from using GTK+ theme integration,
  such as dialogs (I reported this as bug 1378935, but there is no easy
  way to fix that).

  3) It is not working with Qt Quick applications (because it expects a
  QtWidgets window; see also bug 1323853). The standard implementation
  will work with i.e. Qt Quick Controls 2 using apps (implemented in
  https://codereview.qt-project.org/142733).

  4) It breaks other environments such as Plasma when installed: see bug
  1434516.

  5) Finally, it is mostly unmaintained: most patches since 2014 are
  authored by me, however I see no point continuing to develop that
  code.

  Recently, Shawn Rutledge and I have written a native implementation of
  what appmenu-qt5 provides (global menu and system tray), which is part
  of Qt. That code uses the normal API, is well maintained, and works
  better than appmenu-qt5 (or at least not worse).

  So I propose to drop appmenu-qt5 from default Ubuntu installations,
  and maybe later from archive too.

  Unfortunately we use Qt 5.6, and some of the needed patches are only
  in Qt 5.7, so I would like to backport them to our packaging:

  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 
5.6.2 / 5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 
5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 
5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 
5.7.0)

  Timo: if you have no objections, I will commit those patches to the
  packaging Git.

  After we do that, I will remove the appmenu-qt5 recommendation from
  indicator-appmenu (that is the only package referring to it).

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

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

[Touch-packages] [Bug 1616258] Re: Ubuntu 16.04 server PXE installs correctly but loads to a blank screen instead of login

[jeffrey leung]

** Package changed: xorg (Ubuntu) => grub-installer (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/1616258

Title:
  Ubuntu 16.04 server PXE installs correctly but loads to a blank screen
  instead of login

Status in grub-installer package in Ubuntu:
  New

Bug description:
  When trying to do a PXE install for Ubuntu 16.04 and 16.04.1 server
  version, after OS install is complete and the machine reboots the OS
  loads into a blank screen instead of a login prompt. The screen stays
  blank and does not respond to key or mouse input. If I try Alt +
  F1-F6, I am able to open a terminal and see a login prompt.

  We do have a workaround for this. I was looking up similar symptoms on
  the forums and found issues with NVIDIA drivers and found this
  fix:http://askubuntu.com/questions/383636/12-04-3-can-start-only-
  after-press-resume-in-rescue-mode-every-boot-proble/391608#391608

  I edited the /etc/default/grub file and edited the
  GRUB_CMDLINE_LINUX_DEFAULT and added the "nomodeset" to the end at
  first and ran update-grub which did not work. I removed the
  "nomodeset" as well as the "quiet splash" and updated the grub. After
  disabling the boot splash screen and reboot, the OS boots up fine and
  is working as expected.

  We also found another workaround by adding lines to disable the boot splash 
screen in the preseed:
  # No boot splash screen.
  d-i debian-installer/quiet boolean false
  d-i debian-installer/splash boolean false

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1616258/+subscriptions

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

[Touch-packages] [Bug 1570156] Re: Themes.PaletteValues has no import version in docs

[Zoltan Balogh]

** Changed in: canonical-developer-experience
   Status: In Progress => Fix Released

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

Title:
  Themes.PaletteValues has no import version in docs

Status in Client Developer Experience:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  UITK r1984

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.5/Ubuntu.Components.Themes.PaletteValues/

  on the page, the version of the package is not specified, and this
  seems a common issue for a lot of other APIs. We need to review all of
  the API documents on the developer website. With the version number, a
  developer has to guess.

   import Ubuntu.Components.Themes .

  Best regards,
  XiaoGuo

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1570156/+subscriptions

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

[Touch-packages] [Bug 1585557] Re: ListItems, Popups, Pickers, Styles modules documentation pages suggest importing UC 1.0 instead of 1.3

[Zoltan Balogh]

** Changed in: canonical-developer-experience
   Status: In Progress => Fix Released

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

Title:
  ListItems, Popups, Pickers, Styles  modules documentation pages
  suggest importing UC 1.0 instead of 1.3

Status in Client Developer Experience:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.5/Ubuntu.Components.ListItems.Base/

  All the QML modules (ListItems, Pickers, Popups, Styles) imports in
  documentation pages have never been updated since 1.0...

  The ListItems module is deprecated so this bug has low priority, but
  it's still worth fixing as the documentation is live and the
  components are still available for developers to use

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1585557/+subscriptions

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

[Touch-packages] [Bug 1585591] Re: UITK documentation uses \inqmlmodule NAME VERSION, but \inqmlmodule only takes NAME

[Zoltan Balogh]

** Changed in: canonical-developer-experience
   Status: Fix Committed => Fix Released

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

Title:
  UITK documentation uses \inqmlmodule NAME VERSION, but \inqmlmodule
  only takes NAME

Status in Client Developer Experience:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  As of r1984, the whole documentation is full of

  \inqmlmodule Ubuntu.Components 1.3 or similar

  The \inqmlmodule only takes the name of the module, not the version.

  We can safely remove the version from all the 200+ occurrences
  available in the toolkit.

  This makes the documentation code even less confusing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1585591/+subscriptions

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

[Touch-packages] [Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

[Martin Pitt]

Thanks for reporting this! Indeed this is a silly rule construction,
*brown paperbag*. I fixed this for the next Debian/Yakkety upload in
https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=b42e1f8af2 and backported it to Xenial in
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-xenial=d244c9acd .

** Changed in: systemd (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Changed in: systemd (Ubuntu Xenial)
   Status: Triaged => In Progress

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  Fix Committed
Status in debian-installer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Committed
Status in busybox source package in Xenial:
  Won't Fix
Status in debian-installer source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  In Progress
Status in busybox source package in Yakkety:
  Fix Committed
Status in debian-installer source package in Yakkety:
  Triaged
Status in systemd source package in Yakkety:
  Fix Committed

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.

  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:

  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'

  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink 
/etc/udev/rules.d/80-net-setup-link.rules': No such
  file or directory'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with 
exit code 2.
  PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' 
/lib/udev/rules.d/73-usb-net-by-mac.rules:6
  passed device to netlink monitor 0x1003d01f730
  "

  Then it keeps hanged in this stage. We re-tested it by changing the
  file 73-usb-net-by-mac.rules in initrd, replacing "
  /etc/udev/rules.d/80-net-setup-link.rules" to  "/lib/udev/rules.d/80
  -net-setup-link.rules", since the former does not exist whereas the
  latter does. Same issue were observed!

  Notice that if we boot the installer with command-line "net.ifnames=0"
  or "net.ifnames=1", the problem does not reproduces anymore.

  We want to ask Canonical's help in investigating this issue.
  Thanks,

  Guilherme

  
  SRU INFORMATION for systemd
  ===

  Test case:
   * Check what happens for uevents on devices which are not USB network 
interfaces:
 udevadm test /sys/devices/virtual/mem/null
 udevadm test /sys/class/net/lo

   With the current version these will run

PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  /lib/udev/rules.d/73-usb-net-by-mac.rules:6

   which is pointless. With the proposed version these should be gone.

   * Ensure that the rule still works as intended by connecting an USB
  network device that has a permanent MAC address (e. g. Android
  tethering uses a temporary MAC): You should get a MAC-based name like
  "enx12345678" for it. Now disconnect it again, disable ifnames with

  

[Touch-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore

[Aravind Gopal]

Gluten print + cups install automatically when MFD printer is connected
for the first time. Changed to epson driver.. Now 'simple scan' not
loading, no error message , iscan and scanlite gives the same error
message. restarted the system, printer but no use. Error persists.

** Attachment added: "Screenshot_20160824_095523.png"
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1536353/+attachment/4726747/+files/Screenshot_20160824_095523.png

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

Title:
  [Regression] Epson's printer driver packages cannot be installed as
  lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1616262] Re: Unable to update initramfs with small boot partition

[Ubuntu Foundations Team Bug Bot]

The attachment "Patch to use /tmp to store temp initramfs image when
updating." seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  Unable to update initramfs with small boot partition

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I have a small 100MB boot paritition and an initramfs that is 37MB.
  Once you add in all the usual clutter in /boot there is 25MB or so of
  free space left. I have a single kernel installed, there are no older
  versions floating about.

  When I run the update-initramfs script, it fails with :

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-21-generic with 1.

  Looking at the default update-initramfs script, it appears to try and
  create the new initramfs image on the boot partition, then rename it
  to the current one in use. It fails at the cpio step as there is
  insufficient room for both initramfs images in the partition.

  I have tweaked the script to allow it to create the initramfs image in
  /tmp and then move it to the desired location (as opposed to creating
  it / renaming it in the same location), however while it works for me
  (tm) I'm unsure if this breaks any other behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1 [modified: usr/sbin/update-initramfs]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Aug 24 10:36:33 2016
  InstallationDate: Installed on 2016-08-23 (0 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1616262/+subscriptions

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

[Touch-packages] [Bug 1573587] Re: jerky mouse when accessing unity-control-center

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

Title:
  jerky mouse when accessing unity-control-center

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Fresh installation of Ubuntu 16.04 amd64 with usb roccat kone xtd
  When I access unity-control-center or things like about computer or smplayer 
- mouse moving is jerky for a while and then return to smooth, normal work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Apr 22 14:35:34 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8fecb235-f1d2-417c-b346-823e97a843c0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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 Apr 22 13:15:43 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1583102] Re: Could not execute 'apt-key' to verify signature (is gnupg installed?)

[Falcon Taylor-Carter]

I'm having the same issue. Hopefully someone else has a recommendation.

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

Title:
  Could not execute 'apt-key' to verify signature (is gnupg installed?)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04 I'm getting this error for all my apt
  sources.

  This seems different to both
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1524196 (since I
  don't get the "Couldn't create tempfiles for splitting up
  /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-
  updates_InRelease" errors) and
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1577926 (since apt-
  key run by itself fails too).

  Downgrading to apt=1.0.10.2ubuntu2 fixed the problem so it seems to be
  related to recent changes in apt.

  Thanks!

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

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

[Touch-packages] [Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

[Martin Pitt]

** Description changed:

  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).
  
  We're experiencing a strange issue in which the installer freezes before
  menus are showed. The system hangs in the point specified below, right
  after the i40e driver initialization:
  
  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***
  
  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the issue
  reproduction (heisenbug).
  
  We were successful though in getting logs by booting the kernel with the
  command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.
  
  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:
  
- 
  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  
  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink 
/etc/udev/rules.d/80-net-setup-link.rules': No such
  file or directory'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with 
exit code 2.
  PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' 
/lib/udev/rules.d/73-usb-net-by-mac.rules:6
  passed device to netlink monitor 0x1003d01f730
  "
  
- 
- Then it keeps hanged in this stage. We re-tested it by changing the file 
73-usb-net-by-mac.rules in initrd, replacing " 
/etc/udev/rules.d/80-net-setup-link.rules" to  
"/lib/udev/rules.d/80-net-setup-link.rules", since the former does not exist 
whereas the latter does. Same issue were observed!
+ Then it keeps hanged in this stage. We re-tested it by changing the file
+ 73-usb-net-by-mac.rules in initrd, replacing " /etc/udev/rules.d/80-net-
+ setup-link.rules" to  "/lib/udev/rules.d/80-net-setup-link.rules", since
+ the former does not exist whereas the latter does. Same issue were
+ observed!
  
  Notice that if we boot the installer with command-line "net.ifnames=0"
  or "net.ifnames=1", the problem does not reproduces anymore.
  
  We want to ask Canonical's help in investigating this issue.
  Thanks,
  
- 
  Guilherme
  
- == Comment: #8 - Guilherme Guaglianoni Piccoli  -
- 2016-08-19 10:09:51 ==
  
+ SRU INFORMATION for systemd
+ ===
  
- == Comment: #9 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:10:31 ==
+ Test case:
+  * Check what happens for uevents on devices which are not USB network 
interfaces:
+udevadm test /sys/devices/virtual/mem/null
+udevadm test /sys/class/net/lo
  
+  With the current version these will run
  
- == Comment: #10 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:11:49 ==
+   PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
+ /lib/udev/rules.d/73-usb-net-by-mac.rules:6
+ 
+  which is pointless. With the proposed version these should be gone.
+ 
+  * Ensure that the rule still works as intended by connecting an USB
+ network device that has a permanent MAC address (e. g. Android tethering
+ uses a temporary MAC): You should get a MAC-based name like
+ "enx12345678" for it. Now disconnect it again, disable ifnames with
+ 
+ sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
+ 
+ and reconnect the device. You should now get a kernel name like "usb0"
+ for it.
+ 
+ * Regression potential: Errors in the rule could break persistent naming
+ - or its disabling - of USB network interfaces. Running the above test
+ carefully is important to ensure this keeps working. This has little to
+ no actual effect on anything else on the system (aside from a
+ performance impact and spamming logs), so overall the regression
+ potential is low.

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

[Touch-packages] [Bug 1615164] Re: wifi connection manager gone, vpn connections gone after suspend , until reboot

[Tyler]

I have been having trouble with this as well.  It happens occasionally
for me...usually after a long period of inactivity.  Restarting the
network manager will bring everything back to life:

service network-manager restart

I haven't tried reinstalling the network manager yet.

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

Title:
  wifi connection manager gone, vpn connections gone after suspend
  ,until reboot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend mode, network-manager starts having
  problems with the wifi.  the area wifi networks disappear after coming
  out of suspend.  Also after coming out of suspend 2 or 3 times the vpn
  connections disappear and only return after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  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: Unity
  Date: Fri Aug 19 19:41:46 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-24 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlo1  proto static  metric 600 
   169.254.0.0/16 dev tun0  scope link  metric 1000 
   192.168.1.0/24 dev wlo1  proto kernel  scope link  src 192.168.1.122  metric 
600 
   192.168.20.0/24 via 192.168.20.1 dev tun0 
   192.168.20.1 dev tun0  proto kernel  scope link  src 192.168.20.9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   tun0 tun   connected/org/freedesktop/NetworkManager/Devices/1  
tun0 641bc6b5-71c8-418f-98ef-3e1b4dbe8cab  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlo1 wifi  connected/org/freedesktop/NetworkManager/Devices/0  
IAMSECOND 1  185f61fb-9917-4576-83a0-1f2cfb77de31  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----   
  
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/3  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1615164] Re: wifi connection manager gone, vpn connections gone after suspend , until reboot

[Launchpad Bug Tracker]

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

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

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

Title:
  wifi connection manager gone, vpn connections gone after suspend
  ,until reboot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend mode, network-manager starts having
  problems with the wifi.  the area wifi networks disappear after coming
  out of suspend.  Also after coming out of suspend 2 or 3 times the vpn
  connections disappear and only return after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  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: Unity
  Date: Fri Aug 19 19:41:46 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-24 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlo1  proto static  metric 600 
   169.254.0.0/16 dev tun0  scope link  metric 1000 
   192.168.1.0/24 dev wlo1  proto kernel  scope link  src 192.168.1.122  metric 
600 
   192.168.20.0/24 via 192.168.20.1 dev tun0 
   192.168.20.1 dev tun0  proto kernel  scope link  src 192.168.20.9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   tun0 tun   connected/org/freedesktop/NetworkManager/Devices/1  
tun0 641bc6b5-71c8-418f-98ef-3e1b4dbe8cab  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlo1 wifi  connected/org/freedesktop/NetworkManager/Devices/0  
IAMSECOND 1  185f61fb-9917-4576-83a0-1f2cfb77de31  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----   
  
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/3  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1522675] Re: /root/.synaptic/ not created due to locking status

[feroz]

Yet, anyone find out any workaround for this?

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

Title:
  /root/.synaptic/ not created due to locking status

Status in apt package in Ubuntu:
  Invalid
Status in synaptic package in Ubuntu:
  Confirmed
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583102] Re: Could not execute 'apt-key' to verify signature (is gnupg installed?)

[deivid]

@sgrimm Thanks for posting that. Unfortunately, I just had a look and my
tmp folder permissions are fine.

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

Title:
  Could not execute 'apt-key' to verify signature (is gnupg installed?)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04 I'm getting this error for all my apt
  sources.

  This seems different to both
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1524196 (since I
  don't get the "Couldn't create tempfiles for splitting up
  /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-
  updates_InRelease" errors) and
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1577926 (since apt-
  key run by itself fails too).

  Downgrading to apt=1.0.10.2ubuntu2 fixed the problem so it seems to be
  related to recent changes in apt.

  Thanks!

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

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

[Touch-packages] [Bug 1615156] Re: sudo crashed with signal 5 in kill()

[Emily Ratliff]

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

** This bug has been marked a duplicate of bug 1580597
   /usr/bin/sudo:11:kill:main

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

Title:
  sudo crashed with signal 5 in kill()

Status in sudo package in Ubuntu:
  New

Bug description:
  I select Shutdown from the dropdown menu.
  Desktop goes black then system error message appears.
  After the error reporting, it sits there, nothing happening.
  I select Shutdown from the dropdown menu. Nothing happens
  I press the the power button - that is a quick press, not a long one.
  The Ubuntu row of dots appear and it then seems to shut down normally.
  No apparent problems on re-booting.

  There was a terminal window open but it was sitting at the command
  prompt with nothing running.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 23:47:02 2016
  ExecutablePath: /usr/bin/sudo
  InstallationDate: Installed on 2014-09-17 (702 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/sudo -H -S -p GNOME_SUDO_PASS -u root -- nautilus
  Signal: 5
  SourcePackage: sudo
  StacktraceTop:
   kill () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   __libc_start_main (main=0x5575cc03fa20, argc=9, argv=0x7ffd41508e28, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd41508e18) at ../csu/libc-start.c:291
   ?? ()
  Title: sudo crashed with signal 5 in kill()
  UpgradeStatus: Upgraded to xenial on 2016-08-18 (1 days ago)
  UserGroups:

  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1616262] Re: Unable to update initramfs with small boot partition

[David Griffith]

** Description changed:

- I have a 100MB boot paritition and an initramfs that is 37MB. Once you
- add in all the usual clutter in /boot there is 25MB or so of free space
- left.
+ I have a small 100MB boot paritition and an initramfs that is 37MB. Once
+ you add in all the usual clutter in /boot there is 25MB or so of free
+ space left. I have a single kernel installed, there are no older
+ versions floating about.
  
  When I run the update-initramfs script, it fails with :
  
  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-21-generic with 1.
  
  Looking at the default update-initramfs script, it appears to try and
  create the new initramfs image on the boot partition, then rename it to
  the current one in use. It fails at the cpio step as there is
  insufficient room for both initramfs images in the partition.
  
  I have tweaked the script to allow it to create the initramfs image in
  /tmp and then move it to the desired location (as opposed to creating it
  / renaming it in the same location), however while it works for me (tm)
  I'm unsure if this breaks any other behaviour.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1 [modified: usr/sbin/update-initramfs]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Aug 24 10:36:33 2016
  InstallationDate: Installed on 2016-08-23 (0 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_AU.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_AU.UTF-8
+  SHELL=/bin/bash
  SourcePackage: initramfs-tools
  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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1616262

Title:
  Unable to update initramfs with small boot partition

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I have a small 100MB boot paritition and an initramfs that is 37MB.
  Once you add in all the usual clutter in /boot there is 25MB or so of
  free space left. I have a single kernel installed, there are no older
  versions floating about.

  When I run the update-initramfs script, it fails with :

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-21-generic with 1.

  Looking at the default update-initramfs script, it appears to try and
  create the new initramfs image on the boot partition, then rename it
  to the current one in use. It fails at the cpio step as there is
  insufficient room for both initramfs images in the partition.

  I have tweaked the script to allow it to create the initramfs image in
  /tmp and then move it to the desired location (as opposed to creating
  it / renaming it in the same location), however while it works for me
  (tm) I'm unsure if this breaks any other behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1 [modified: usr/sbin/update-initramfs]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Aug 24 10:36:33 2016
  InstallationDate: Installed on 2016-08-23 (0 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1616262/+subscriptions

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

[Touch-packages] [Bug 1616266] [NEW] AdaptivePageLayout gives "TypeError: Type error" and cannot create new component

[Larry Price]

Public bug reported:

Ubuntu Yakkety Yak (development branch)
qml-module-ubuntu-components 1.3.2060+16.10.20160814

I was using AdaptivePageLayout to build an app and everything was
working fine before the big yakkety updates recently. In running the
same code, I now see this in the terminal:

Gtk-Message: Failed to load module "overlay-scrollbar"
QQmlComponent: Cannot create new component instance before completing the 
previous

file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:945:
 TypeError: Type error

And my AdaptivePageLayout no longer loads properly using the
primaryPageSource property. Maybe something in the new Qt is causing
this issue? Seems my system is also having trouble with the overlay-
scrollbar, but I'm not sure whether that's related.

To reproduce this, I created a new project in the Ubuntu SDK IDE with
the template "QtQuick App with QML UI (qmake)" and edited Main.qml to
use an AdaptivePageLayout by giving the Page object an id of
"primaryPage" and adding the following lines before the definition of
primaryPage*:

AdaptivePageLayout {
primaryPage: primaryPage
}

* full file here: https://paste.ubuntu.com/23083699/

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  AdaptivePageLayout gives "TypeError: Type error" and cannot create new
  component

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

Bug description:
  Ubuntu Yakkety Yak (development branch)
  qml-module-ubuntu-components 1.3.2060+16.10.20160814

  I was using AdaptivePageLayout to build an app and everything was
  working fine before the big yakkety updates recently. In running the
  same code, I now see this in the terminal:

  Gtk-Message: Failed to load module "overlay-scrollbar"
  QQmlComponent: Cannot create new component instance before completing the 
previous
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:945:
 TypeError: Type error

  And my AdaptivePageLayout no longer loads properly using the
  primaryPageSource property. Maybe something in the new Qt is causing
  this issue? Seems my system is also having trouble with the overlay-
  scrollbar, but I'm not sure whether that's related.

  To reproduce this, I created a new project in the Ubuntu SDK IDE with
  the template "QtQuick App with QML UI (qmake)" and edited Main.qml to
  use an AdaptivePageLayout by giving the Page object an id of
  "primaryPage" and adding the following lines before the definition of
  primaryPage*:

  AdaptivePageLayout {
  primaryPage: primaryPage
  }

  * full file here: https://paste.ubuntu.com/23083699/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1616266/+subscriptions

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

[Touch-packages] [Bug 1616262] Re: Unable to update initramfs with small boot partition

[David Griffith]

Patch to use /tmp when creating initramfs

** Attachment added: "Patch to use /tmp to store temp initramfs image when 
updating."
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1616262/+attachment/4726690/+files/initramfs_patch

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

Title:
  Unable to update initramfs with small boot partition

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I have a small 100MB boot paritition and an initramfs that is 37MB.
  Once you add in all the usual clutter in /boot there is 25MB or so of
  free space left. I have a single kernel installed, there are no older
  versions floating about.

  When I run the update-initramfs script, it fails with :

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-21-generic with 1.

  Looking at the default update-initramfs script, it appears to try and
  create the new initramfs image on the boot partition, then rename it
  to the current one in use. It fails at the cpio step as there is
  insufficient room for both initramfs images in the partition.

  I have tweaked the script to allow it to create the initramfs image in
  /tmp and then move it to the desired location (as opposed to creating
  it / renaming it in the same location), however while it works for me
  (tm) I'm unsure if this breaks any other behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1 [modified: usr/sbin/update-initramfs]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Aug 24 10:36:33 2016
  InstallationDate: Installed on 2016-08-23 (0 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1616262/+subscriptions

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

[Touch-packages] [Bug 1616262] Re: Unable to update initramfs with small boot partition

[David Griffith]

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

Title:
  Unable to update initramfs with small boot partition

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I have a small 100MB boot paritition and an initramfs that is 37MB.
  Once you add in all the usual clutter in /boot there is 25MB or so of
  free space left. I have a single kernel installed, there are no older
  versions floating about.

  When I run the update-initramfs script, it fails with :

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-21-generic with 1.

  Looking at the default update-initramfs script, it appears to try and
  create the new initramfs image on the boot partition, then rename it
  to the current one in use. It fails at the cpio step as there is
  insufficient room for both initramfs images in the partition.

  I have tweaked the script to allow it to create the initramfs image in
  /tmp and then move it to the desired location (as opposed to creating
  it / renaming it in the same location), however while it works for me
  (tm) I'm unsure if this breaks any other behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1 [modified: usr/sbin/update-initramfs]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Aug 24 10:36:33 2016
  InstallationDate: Installed on 2016-08-23 (0 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1616262/+subscriptions

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

[Touch-packages] [Bug 1616262] [NEW] Unable to update initramfs with small boot partition

[David Griffith]

Public bug reported:

I have a small 100MB boot paritition and an initramfs that is 37MB. Once
you add in all the usual clutter in /boot there is 25MB or so of free
space left. I have a single kernel installed, there are no older
versions floating about.

When I run the update-initramfs script, it fails with :

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.4.0-21-generic with 1.

Looking at the default update-initramfs script, it appears to try and
create the new initramfs image on the boot partition, then rename it to
the current one in use. It fails at the cpio step as there is
insufficient room for both initramfs images in the partition.

I have tweaked the script to allow it to create the initramfs image in
/tmp and then move it to the desired location (as opposed to creating it
/ renaming it in the same location), however while it works for me (tm)
I'm unsure if this breaks any other behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.1 [modified: usr/sbin/update-initramfs]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: MATE
Date: Wed Aug 24 10:36:33 2016
InstallationDate: Installed on 2016-08-23 (0 days ago)
InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug sarah

** Patch added: "Patch to use /tmp to store temp initramfs image when updating."
   
https://bugs.launchpad.net/bugs/1616262/+attachment/4726675/+files/initramfs_patch

** Patch removed: "Patch to use /tmp to store temp initramfs image when 
updating."
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1616262/+attachment/4726675/+files/initramfs_patch

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

Title:
  Unable to update initramfs with small boot partition

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I have a small 100MB boot paritition and an initramfs that is 37MB.
  Once you add in all the usual clutter in /boot there is 25MB or so of
  free space left. I have a single kernel installed, there are no older
  versions floating about.

  When I run the update-initramfs script, it fails with :

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-21-generic with 1.

  Looking at the default update-initramfs script, it appears to try and
  create the new initramfs image on the boot partition, then rename it
  to the current one in use. It fails at the cpio step as there is
  insufficient room for both initramfs images in the partition.

  I have tweaked the script to allow it to create the initramfs image in
  /tmp and then move it to the desired location (as opposed to creating
  it / renaming it in the same location), however while it works for me
  (tm) I'm unsure if this breaks any other behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1 [modified: usr/sbin/update-initramfs]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Aug 24 10:36:33 2016
  InstallationDate: Installed on 2016-08-23 (0 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1616262/+subscriptions

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

[Touch-packages] [Bug 1612240] Re: [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot

[Steve Langasek]

Hi Łukasz,

When you say the next stable release of zeromq3 is "planned in the
nearest future", when exactly is that?

Since there is also a plan to get unity8 into main properly for 16.10,
this would seem to imply pulling zeromq3 into main.  So we would want to
make sure we can provide security support.  Would we want to include the
final release of zeromq3 4.2 in 16.10 under this FFe?

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

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

Title:
  [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot

Status in zeromq3 package in Ubuntu:
  Incomplete
Status in zmqpp package in Ubuntu:
  In Progress

Bug description:
  Please update zmqpp to version 4.1.2 with the following patch that I proposed 
upstream (it got merged into their "develop" branch):
  https://github.com/zeromq/zmqpp/pull/167/files

  (alternatively, use master + my patch or develop branch of zmqpp).

  This will require the current git snapshot of the zmq library (which
  will be version 4.2 when it's released) -
  https://github.com/zeromq/libzmq

  All the above is needed to support the new USE_FD socket option, which
  will probably be critical for scopes as snaps.

  == Feature Freeze Exception details ==

  These packages are required by the ongoing work of the unity scopes
  for snappy. Due to unrelated to zeromq issues (unity-scopes-api unit-
  test issues on arm64, possibly due to recent toolchain changes) we did
  not make it in time before Feature Freeze. The packages have been
  prepared and tested in:

  https://launchpad.net/~ci-train-ppa-
  
service/+archive/ubuntu/landing-005/+packages?field.name_filter=_filter=published_filter=yakkety

  There is no ABI breakage in zeromq3 so no reverse-depends rebuilds are
  required. The zmqpp package does break ABI so a so bump and rebuild of
  rev-deps was needed, but the currently only consumer of the zmqpp
  packages is unity-scopes-api. The new release of zeromq3 is based on a
  git snapshot as a new stable release of this project is planned in the
  nearest future, so a bit too late for the current plans. Some reverse-
  depends of zeromq3 have been tested to work fine with the new package
  as is.

  We kindly request a FFe for this very particular case.

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

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

[Touch-packages] [Bug 1583102] Re: Could not execute 'apt-key' to verify signature (is gnupg installed?)

[Steven Grimm]

I ran into this today and the problem turned out to be /tmp:

# ls -ld /tmp
drwxrwxr-x 11 ubuntu ubuntu 4096 Aug 24 00:23 /tmp

This fixed it:

# chown root:root /tmp
# chmod 1777 /tmp

I don't know how /tmp got in that state on my server (it's a fairly
fresh install of 16.04) but perhaps that's the underlying problem for
other people too.

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

Title:
  Could not execute 'apt-key' to verify signature (is gnupg installed?)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04 I'm getting this error for all my apt
  sources.

  This seems different to both
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1524196 (since I
  don't get the "Couldn't create tempfiles for splitting up
  /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-
  updates_InRelease" errors) and
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1577926 (since apt-
  key run by itself fails too).

  Downgrading to apt=1.0.10.2ubuntu2 fixed the problem so it seems to be
  related to recent changes in apt.

  Thanks!

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

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

[Touch-packages] [Bug 349469] lovely

[Muhammad Najmi Fauzi]

Greetings,

Have you seen something as lovely as that stuff? I swear you haven't,
just take a look  here 

My Best, najmiii

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Ambasa:
  New
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Confirmed
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1616258] [NEW] Ubuntu 16.04 server PXE installs correctly but loads to a blank screen instead of login

[jeffrey leung]

Public bug reported:

When trying to do a PXE install for Ubuntu 16.04 and 16.04.1 server
version, after OS install is complete and the machine reboots the OS
loads into a blank screen instead of a login prompt. The screen stays
blank and does not respond to key or mouse input. If I try Alt + F1-F6,
I am able to open a terminal and see a login prompt.

We do have a workaround for this. I was looking up similar symptoms on
the forums and found issues with NVIDIA drivers and found this
fix:http://askubuntu.com/questions/383636/12-04-3-can-start-only-after-
press-resume-in-rescue-mode-every-boot-proble/391608#391608

I edited the /etc/default/grub file and edited the
GRUB_CMDLINE_LINUX_DEFAULT and added the "nomodeset" to the end at first
and ran update-grub which did not work. I removed the "nomodeset" as
well as the "quiet splash" and updated the grub. After disabling the
boot splash screen and reboot, the OS boots up fine and is working as
expected.

We also found another workaround by adding lines to disable the boot splash 
screen in the preseed:
# No boot splash screen.
d-i debian-installer/quiet boolean false
d-i debian-installer/splash boolean false

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

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

Title:
  Ubuntu 16.04 server PXE installs correctly but loads to a blank screen
  instead of login

Status in xorg package in Ubuntu:
  New

Bug description:
  When trying to do a PXE install for Ubuntu 16.04 and 16.04.1 server
  version, after OS install is complete and the machine reboots the OS
  loads into a blank screen instead of a login prompt. The screen stays
  blank and does not respond to key or mouse input. If I try Alt +
  F1-F6, I am able to open a terminal and see a login prompt.

  We do have a workaround for this. I was looking up similar symptoms on
  the forums and found issues with NVIDIA drivers and found this
  fix:http://askubuntu.com/questions/383636/12-04-3-can-start-only-
  after-press-resume-in-rescue-mode-every-boot-proble/391608#391608

  I edited the /etc/default/grub file and edited the
  GRUB_CMDLINE_LINUX_DEFAULT and added the "nomodeset" to the end at
  first and ran update-grub which did not work. I removed the
  "nomodeset" as well as the "quiet splash" and updated the grub. After
  disabling the boot splash screen and reboot, the OS boots up fine and
  is working as expected.

  We also found another workaround by adding lines to disable the boot splash 
screen in the preseed:
  # No boot splash screen.
  d-i debian-installer/quiet boolean false
  d-i debian-installer/splash boolean false

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

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

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

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1605950, so 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.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

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

Status in gconf package in Ubuntu:
  New

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

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 19 21:09:53 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu2
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-08-19 (0 days ago)

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

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

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

[Seth Arnold]

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

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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

Status in gconf package in Ubuntu:
  New

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

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 19 21:09:53 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu2
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-08-19 (0 days ago)

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

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

[Touch-packages] [Bug 1452849] Re: initctl cannot find Upstart

[CosmoJG]

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

This is still an issue in 16.04.1 as of August 23rd, 2016.

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

Title:
  initctl cannot find Upstart

Status in upstart :
  New
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  Please see Apport's automatically generated files (attached)

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 15.04
  Package: upstart 1.13.2-0ubuntu13
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  7 19:03:35 2015
  DuplicateSignature: /sbin/upstart:indicator-session-unknown-user-error
  ExecutablePath: /sbin/upstart
  InstallationDate: Installed on 2011-12-08 (1246 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: /sbin/upstart --user
  SourcePackage: upstart
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (13 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 
'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not 
exist
  UserGroups: adm admin avahi avahi-autoipd cdrom dialout dip fax floppy fuse 
lp lpadmin mythtv plugdev sambashare tape users video whoopsie www-data
  icon_file: (null)
  is_current_user: false
  is_logged_in: false
  real_name: (null)
  uid: 0
  upstart.upstart-event-bridge.log: upstart-event-bridge: Could not connect to 
system Upstart: Failed to connect to socket /com/ubuntu/upstart/local/bridge: 
Connection refused
  user_name: (null)

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

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

[Touch-packages] [Bug 1615936] Re: hi, thank you very much, my hp 14 notebook keeps freezing

[Emily Ratliff]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  hi, thank you very much, my hp 14 notebook keeps freezing

Status in xorg package in Ubuntu:
  New

Bug description:
  every time more since i upgraded it, crashes and freezes (i mean it
  stops functioning at all) with tihe screen freezed and i would totally
  thank dor you to help me! thanks from forehand! :) hans

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  .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: Tue Aug 23 03:01:31 2016
  DistUpgraded: 2016-08-07 03:15:49,483 DEBUG failed to SystemUnLock() (E:No 
bloqueado)
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:220f]
  InstallationDate: Installed on 2016-02-20 (184 days ago)
  InstallationMedia: Ubuntu 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 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 14 Notebook PC
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=618c3a61-74fd-46f6-99f6-18d7b5fb734c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (15 days ago)
  dmi.bios.date: 05/26/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.39
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 220F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.54
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.39:bd05/26/2015:svnHewlett-Packard:pnHP14NotebookPC:pvr097710405F0610180:rvnHewlett-Packard:rn220F:rvr57.54:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 14 Notebook PC
  dmi.product.version: 097710405F0610180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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: Tue Aug 23 02:31:20 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1126 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1612835] Re: Please don't depend on jasper

[Jeremy Bicha]

** Description changed:

  Jasper is being removed from Debian. It would be great if this could be
  done in Ubuntu too before 16.10 is released.
  
  https://release.debian.org/transitions/html/jasper-rm.html
  
  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * dcraw (fixed in -proposed, autosynced from Debian but ftbfs, see bug 
1611001 )
- * imagemagick   (for libjasper-dev) (filed separately as bug 
1612822 )
  * kodi  (for libjasper-dev) (in sync with Debian, so 
we'll just sync their fix)
- * qtimageformats-opensource-src  (for libjasper-dev) (fixed in -proposed, 
autosynced from Debian)
  
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)
  
  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.

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

Title:
  Please don't depend on jasper

Status in digikam package in Ubuntu:
  New
Status in jasper package in Ubuntu:
  New
Status in kde4libs package in Ubuntu:
  New
Status in kimageformats package in Ubuntu:
  New
Status in kopete package in Ubuntu:
  New

Bug description:
  Jasper is being removed from Debian. It would be great if this could
  be done in Ubuntu too before 16.10 is released.

  https://release.debian.org/transitions/html/jasper-rm.html

  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * dcraw (fixed in -proposed, autosynced from Debian but ftbfs, see bug 
1611001 )
  * kodi  (for libjasper-dev) (in sync with Debian, so 
we'll just sync their fix)

  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)

  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.

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

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

[Touch-packages] [Bug 1616228] Re: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in packag

[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 account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1616228

Title:
  package account-plugin-google (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/accounts/providers/google.provider', which is also in
  package kaccounts-providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New
Status in kaccounts-providers package in Ubuntu:
  New

Bug description:
  I am not sure the issue but I keep crashing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 23 13:14:09 2016
  DuplicateSignature:
   package:account-plugin-google:(not installed)
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-08-23 (0 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1616228/+subscriptions

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

[Touch-packages] [Bug 1615340] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  ?

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

Bug description:
  ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Aug 21 00:39:13 2016
  DistUpgraded: 2016-08-20 21:34:16,635 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80e6]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80e6]
  InstallationDate: Installed on 2016-08-18 (3 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=1ae0756e-cef6-4606-b55a-1c07402caf98 ro vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago)
  dmi.bios.date: 03/04/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80E6
  dmi.board.vendor: HP
  dmi.board.version: 87.60
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd03/04/2016:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80E6:rvr87.60:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Aug 20 23:11:36 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4253 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

[Emily Ratliff]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Public Security to Public

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  New

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run 
  /etc/kernel/postinst.d/
  during each boot (e.g. by using cron).

  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  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.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

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

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

[Touch-packages] [Bug 1616228] Re: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in packag

[Emily Ratliff]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Also affects: kaccounts-providers (Ubuntu)
   Importance: Undecided
   Status: New

** Information type changed from Private Security to Public

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

Title:
  package account-plugin-google (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/accounts/providers/google.provider', which is also in
  package kaccounts-providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New
Status in kaccounts-providers package in Ubuntu:
  New

Bug description:
  I am not sure the issue but I keep crashing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 23 13:14:09 2016
  DuplicateSignature:
   package:account-plugin-google:(not installed)
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-08-23 (0 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1616228/+subscriptions

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

[Touch-packages] [Bug 1612708] Re: Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

[mohican]

My bug appears to be bug #1449112
There's a patch for it. If you try the patch (only for Ubuntu 16.04) you may 
find out whether your bug is the same as mine.

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

Title:
  Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.1 LTS

  colord:
Installiert:   1.2.12-1ubuntu1
Installationskandidat: 1.2.12-1ubuntu1
Versionstabelle:
   *** 1.2.12-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Under Ubuntu 14.04 LTS I have created NAS access by using 'gvfs-mount
  smb://nasdo/public'. It is linked to '/run/user/1000/gvfs/ als smb-
  share:server=nasdo,share=public' and I have created a Symbolic Link to
  this point with 'ln -s /run/user/1000/gvfs/smb-
  share\:server\=nasdo\,share\=public ~/nasdo_public'. Using this link
  folders, and files on the NAS have been accessable with r/w from
  Ubuntu 14.04 LTS. This is, what I expect from 16.04, too.

  Since I have upgraded to ubuntu 16.04 LTS a few days ago, all the
  links seem to be the same, but opening a file does not work. It comes
  to an input/output error. I can use the links to folders to navigate,
  but there is no chance to open e.g. an LibreOffice Calc Sheet, nor do
  I have access to mail folder via Thunderbird.

  Using gvfs-mount creates a shared folder in Nautilus called public.
  Using this way to access the NAS, and open the Calc file works with
  ubuntu 16.04 LTS fine.

  Locking to the syslog while trying to open a file creates the following 
entries:
  Aug 12 16:47:19 UDO systemd[1]: Started Hostname Service.
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (process:8645): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (process:8663): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:48 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:55:01 UDO dbus[2427]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
  Aug 12 16:55:01 UDO systemd[1]: Starting Hostname Service...
  Aug 12 16:55:01 UDO dbus[2427]: [system] Successfully activated service 
'org.freedesktop.hostname1'
  Aug 12 16:55:01 UDO systemd[1]: Started Hostname Service.

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

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

[Touch-packages] [Bug 1615340] Re: ?

[Emily Ratliff]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

** Information type changed from Private Security to Public

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

Title:
  ?

Status in linux package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Aug 21 00:39:13 2016
  DistUpgraded: 2016-08-20 21:34:16,635 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80e6]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80e6]
  InstallationDate: Installed on 2016-08-18 (3 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=1ae0756e-cef6-4606-b55a-1c07402caf98 ro vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago)
  dmi.bios.date: 03/04/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80E6
  dmi.board.vendor: HP
  dmi.board.version: 87.60
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd03/04/2016:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80E6:rvr87.60:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Aug 20 23:11:36 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4253 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2.3

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

-- 
Mailing list: https://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 1616196] Re: unable to stop avahi-daemon (dbus always restarts it)

[Simon Déziel]

Hi Trent,

On 2016-08-23 05:17 PM, Trent Lloyd wrote:
> The d-bus activation thing is a quirk of systemd, it actually tells you
> when you run stop.  You need to use disable (as well as stop) to both
> stop it and prevent re-activation.

Disabling and stopping the socket and the service works for the manual
case, thanks.

> root@ubuntu:~# systemctl stop avahi-daemon
> Warning: Stopping avahi-daemon.service, but it can still be activated by:
>   avahi-daemon.socket
> 
> You're right about the ifupdown script, though.

Unfortunately for me because I'm trying to remotely disable avahi-daemon
for clients connecting to a corporate VPN where "domain.local" is used
as the DNS zone.

I haven't found any valid workaround for the ifupdown script so I now
have to instruct every clients to do the disable/stop steps themselves.
This in turn has some undesired ramifications as avahi remains inactive
even when they are off of the VPN.

> The good news on the one hand is that upstream hopefully soon nss-mdns
will be improved to no longer need this trick.

I just noticed that you are an avahi developer so maybe it's my lucky
day :)

I don't know why but avahi doesn't seem to limit itself to resolving
single DNS label under ".local"? Currently, it will blackhole queries
for "server.domain.local". This makes it close to impossible to use a
DNS zone under ".local". While I know that using ".local" isn't ideal,
it was the recommended way in the past [1] and it's how many networks
are setup.

The RFC [2] mentions that ".local" is for single labels and OS X also
implementation this rule [3]. Do you think it would be possible for
avahi to also implement this behavior?

Best regards,
Simon


1: https://en.wikipedia.org/wiki/.local#Microsoft_recommendations
2: https://tools.ietf.org/html/rfc6762#section-3
3: https://support.apple.com/en-us/HT201275

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

Title:
  unable to stop avahi-daemon (dbus always restarts it)

Status in avahi package in Ubuntu:
  New

Bug description:
  When avahi-daemon is stopped, dbus always revives it.

  Steps to reproduce:

  1. sudo systemctl stop avahi-daemon.socket
  2. sudo systemctl stop avahi-daemon.service
  3. ps aux| grep avahi # should return nothing

  Currently, dbus revives it right away as shown in syslog:

  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Got SIGTERM, quitting.
  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Leaving mDNS multicast group on 
interface ens3.IPv6 with address 2001:470:b1c3:7946::a4.
  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Leaving mDNS multicast group on 
interface ens3.IPv4 with address 172.24.26.52.
  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: avahi-daemon 0.6.32-rc exiting.
  Aug 23 15:17:22 simon-vm dbus[1647]: [system] Activating via systemd: service 
name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
  Aug 23 15:17:22 simon-vm systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
  Aug 23 15:17:22 simon-vm systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
  Aug 23 15:17:22 simon-vm systemd[1]: Listening on Avahi mDNS/DNS-SD Stack 
Activation Socket.
  Aug 23 15:17:22 simon-vm systemd[1]: Starting Avahi mDNS/DNS-SD Stack...

  
  This automatic revival defeats the purpose of the up script [*] to deactivate 
avahi when .local is a regular DNS zone (not mDNS). This also goes against the 
principle of least surprise.

  *: /etc/network/if-{down,up}.d/avahi-daemon

  Additional information:

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

  # apt-cache policy avahi-daemon dbus systemd
  avahi-daemon:
Installed: 0.6.32~rc+dfsg-1ubuntu2
Candidate: 0.6.32~rc+dfsg-1ubuntu2
Version table:
   *** 0.6.32~rc+dfsg-1ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  dbus:
Installed: 1.10.6-1ubuntu3
Candidate: 1.10.6-1ubuntu3
Version table:
   *** 1.10.6-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  systemd:
Installed: 229-4ubuntu7
Candidate: 229-4ubuntu7
Version table:
   *** 229-4ubuntu7 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 [modified: 
usr/lib/avahi/avahi-daemon-check-dns.sh]
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 23 15:09:40 2016
  InstallationDate: Installed on 2016-08-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 

[Touch-packages] [Bug 1445755] Re: Provide a way to hide images from a particular location

[Michi Henning]

This happens if someone inserts a flash card or copies a collection from
some other music library, such as iTunes. For songs that don't have
embedded artwork, various music players store the artwork in a file
inside an album's folder. iTunes uses AlbumArtSmall.jpg and Folder.jpg.
Other players use cover.ext, album.ext, album art.ext, .folder.ext, or
folder.ext (where ext could be png, jpg, or jpeg).

It seems that gallery app shows these files as if they were photos taken
with the camera app.

For a test case, drop an image called AlbumArtSmall.jpg or cover.jpg
into a music album folder somewhere. I believe you'll find that image in
the gallery app then.

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

Title:
  Provide a way to hide images from a particular location

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

Bug description:
  I've put about 30GB of music in my SD card. Some of the music files
  don't have embedded cover art and their folders contain those cover
  art images.

  When I then opened the Gallery app, I noticed I now have thousands of
  "pictures" imported from the cover art images showing up in my Events
  and Pictures tabs, cluttering the real pictures I've taken with the
  camera.

  Is there a way to tell either mediascanner or the Gallery app to
  ignore a path and not import/show the images there? E.g. similar to
  Android, where you can put a .nomedia file in a folder and its images
  won't show up in the picture viewer.

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

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

[Touch-packages] [Bug 1445755] Re: Provide a way to hide images from a particular location

[Bill Filler]

I'm having a hard time reproducing this and don't know what I'm doing
wrong. I copy a bunch of music from my desktop to ~/Music of phone. I
see the album art in the Music app but don't see the album art in the
gallery-app. Repeat the same steps but copy music from desktop to sd
card then insert the sd in phone. Same thing - I correctly see album art
in Music player and My Music scope but not in gallery. Doing find for
AlbumArtSmall.jpg and Folder.jpg yields nothing. What am I doing wrong?

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

Title:
  Provide a way to hide images from a particular location

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

Bug description:
  I've put about 30GB of music in my SD card. Some of the music files
  don't have embedded cover art and their folders contain those cover
  art images.

  When I then opened the Gallery app, I noticed I now have thousands of
  "pictures" imported from the cover art images showing up in my Events
  and Pictures tabs, cluttering the real pictures I've taken with the
  camera.

  Is there a way to tell either mediascanner or the Gallery app to
  ignore a path and not import/show the images there? E.g. similar to
  Android, where you can put a .nomedia file in a folder and its images
  won't show up in the picture viewer.

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

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

[Touch-packages] [Bug 1598010] Re: cellular data switch disabled until SIM selected in settings

[Launchpad Bug Tracker]

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

---
indicator-network (0.8.0+16.10.20160817.2-0ubuntu1) yakkety; urgency=medium

  [ Antti Kaijanmäki ]
  * Use a timer to set the sim for mobile data if only one sim exists.
(LP: #1598010)

  [ Pete Woods ]
  * Re-enable tests on all architectures (LP: #1612619)

 -- Pete Woods   Wed, 17 Aug 2016 11:50:15
+

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

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

Title:
  cellular data switch disabled until SIM selected in settings

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  New
Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  
  Cellular data switch is disabled on nexus 4. 

  rc_proposed: r476
  Ubuntu Image Part: 20160701

  Mobile data cannot be activated on this device (possibly others) as
  the cellular data switch in settings and in the indicator are
  disabled.

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

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

[Touch-packages] [Bug 1612619] Re: [MIR] indicator-network

[Launchpad Bug Tracker]

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

---
indicator-network (0.8.0+16.10.20160817.2-0ubuntu1) yakkety; urgency=medium

  [ Antti Kaijanmäki ]
  * Use a timer to set the sim for mobile data if only one sim exists.
(LP: #1598010)

  [ Pete Woods ]
  * Re-enable tests on all architectures (LP: #1612619)

 -- Pete Woods   Wed, 17 Aug 2016 11:50:15
+

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

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

Title:
  [MIR] indicator-network

Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has both unit tests and integration tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libqofono (needs bug)
   * network-manager-openvpn (bug #1574576)
   * urfkill (needs bug)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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

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

[Adam Dingle]

I believe this bug occurs in any location whose default language is non-
English, even if you select English as your language.  I saw it while
trying to install Yakkety in Spain, even though I selected English for
the language and keyboard.  As a workaround, I ran the installer again
and chose New York rather than Madrid when asked for my time zone.  Then
it worked fine.

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

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

Status in apt package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Fix Committed

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

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

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

  Steps to reproduce:

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

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

  Expected result: No crashes during installation

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

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

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

[Touch-packages] [Bug 1616196] Re: unable to stop avahi-daemon (dbus always restarts it)

[Trent Lloyd]

The d-bus activation thing is a quirk of systemd, it actually tells you
when you run stop.  You need to use disable (as well as stop) to both
stop it and prevent re-activation.

root@ubuntu:~# systemctl stop avahi-daemon
Warning: Stopping avahi-daemon.service, but it can still be activated by:
  avahi-daemon.socket

You're right about the ifupdown script, though.


The good news on the one hand is that upstream hopefully soon nss-mdns will be 
improved to no longer need this trick.

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

Title:
  unable to stop avahi-daemon (dbus always restarts it)

Status in avahi package in Ubuntu:
  New

Bug description:
  When avahi-daemon is stopped, dbus always revives it.

  Steps to reproduce:

  1. sudo systemctl stop avahi-daemon.socket
  2. sudo systemctl stop avahi-daemon.service
  3. ps aux| grep avahi # should return nothing

  Currently, dbus revives it right away as shown in syslog:

  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Got SIGTERM, quitting.
  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Leaving mDNS multicast group on 
interface ens3.IPv6 with address 2001:470:b1c3:7946::a4.
  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Leaving mDNS multicast group on 
interface ens3.IPv4 with address 172.24.26.52.
  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: avahi-daemon 0.6.32-rc exiting.
  Aug 23 15:17:22 simon-vm dbus[1647]: [system] Activating via systemd: service 
name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
  Aug 23 15:17:22 simon-vm systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
  Aug 23 15:17:22 simon-vm systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
  Aug 23 15:17:22 simon-vm systemd[1]: Listening on Avahi mDNS/DNS-SD Stack 
Activation Socket.
  Aug 23 15:17:22 simon-vm systemd[1]: Starting Avahi mDNS/DNS-SD Stack...

  
  This automatic revival defeats the purpose of the up script [*] to deactivate 
avahi when .local is a regular DNS zone (not mDNS). This also goes against the 
principle of least surprise.

  *: /etc/network/if-{down,up}.d/avahi-daemon

  Additional information:

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

  # apt-cache policy avahi-daemon dbus systemd
  avahi-daemon:
Installed: 0.6.32~rc+dfsg-1ubuntu2
Candidate: 0.6.32~rc+dfsg-1ubuntu2
Version table:
   *** 0.6.32~rc+dfsg-1ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  dbus:
Installed: 1.10.6-1ubuntu3
Candidate: 1.10.6-1ubuntu3
Version table:
   *** 1.10.6-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  systemd:
Installed: 229-4ubuntu7
Candidate: 229-4ubuntu7
Version table:
   *** 229-4ubuntu7 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 [modified: 
usr/lib/avahi/avahi-daemon-check-dns.sh]
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 23 15:09:40 2016
  InstallationDate: Installed on 2016-08-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160819)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[moma]

Re-hi,
I may agree with @sudodus,

I cannot remember to have changed language or keyboard during the
installation.
I kept all in default: Language = 'en'

My initial bug was #1612570.


On Tue, Aug 23, 2016 at 9:14 PM, sudodus <1611...@bugs.launchpad.net>
wrote:

> I don't think bug #1616183 is a duplicate of this bug, because it
> affects the default language too, US English, which I found a few
> minutes ago while isotesting Lubuntu desktop i386 beta1.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1612570).
> https://bugs.launchpad.net/bugs/1611010
>
> Title:
>   yakkety desktop - non-english installation crashes with
>   /plugininstall.py: ValueError: invalid literal for int() with base 10:
>   ''
>
> Status in apt package in Ubuntu:
>   Fix Committed
> Status in ubiquity package in Ubuntu:
>   Fix Committed
>
> Bug description:
>   Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
>   /daily-live/current/
>
>   HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd
>
>   Preconditions: W10+Xenial xerus installed, internet connection, 3rd
>   party sw and updates selected
>
>   Steps to reproduce:
>
>   1º Click something else on Installation type screen>select /dev/sdaX
> where Xenial is installed, use it to mount / and leave some space to create
> the /home partition(ext4)
>   2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
>   3º Installation starts
>
>   Current result: After a little time installing it crashes and a window
>   shows up to let the user know that some info is being gathered to send
>   it to developers, and finally firefox opens on the bug report web on
>   ubiquity package
>
>   Expected result: No crashes during installation
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: ubiquity 16.10.5
>   ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
>   Uname: Linux 4.4.0-33-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu5
>   Architecture: amd64
>   CasperVersion: 1.376
>   Date: Mon Aug  8 15:50:56 2016
>   InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
> initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
>   LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
>   ProcEnviron:
>LANGUAGE=es_ES.UTF-8
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=es_ES.UTF-8
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1611010/+subscriptions
>


-- 
Sent from my PC, laptop or phone with Ubuntu-Linux.

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

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

Status in apt package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Fix Committed

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

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

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

  Steps to reproduce:

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

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

  Expected result: No crashes during installation

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

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

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

[Touch-packages] [Bug 1616082] Re: libpython2.7-minimal package missing required imports

[John Mellor]

Root cause found - using an old version of a2x from Ubuntu 10 instead of
the Ubuntu 16 version.

NFF.

** Changed in: python2.7 (Ubuntu)
 Assignee: (unassigned) => John Mellor (john-mellor)

** Changed in: python2.7 (Ubuntu)
   Status: New => Invalid

** Tags removed: regression-release

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

Title:
  libpython2.7-minimal package missing required imports

Status in python2.7 package in Ubuntu:
  Invalid

Bug description:
  libpython2.7-minimal is missing essential imports.  The _collections.py is 
missing.  This library exists in Trusty and previous, but is present in Xenial 
only in the Python3 libraries.
  See following confirming stack trace:

  00:03:49.816 /opt/bin/a2x --doctype manpage --format manpage ve.txt
  00:03:49.853 Traceback (most recent call last):
  00:03:49.853   File "/opt/bin/a2x", line 16, in 
  00:03:49.853 import shutil
  00:03:49.853   File "/usr/lib/python2.7/shutil.py", line 12, in 
  00:03:49.853 import collections
  00:03:49.853   File "/usr/lib/python2.7/collections.py", line 20, in 
  00:03:49.853 from _collections import deque, defaultdict
  00:03:49.853 ImportError: No module named _collections

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1616082/+subscriptions

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

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

[sudodus]

I don't think bug #1616183 is a duplicate of this bug, because it
affects the default language too, US English, which I found a few
minutes ago while isotesting Lubuntu desktop i386 beta1.

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

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

Status in apt package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Fix Committed

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

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

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

  Steps to reproduce:

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

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

  Expected result: No crashes during installation

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

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

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

[Touch-packages] [Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

[Steve Langasek]

I've thought about this some more, and while the /bin/readlink
/usr/bin/readlink in busybox is a bug, fixing this is definitely not
going to fix the problem in the installer.  In the installer,
/etc/udev/rules.d/80-net-setup-link.rules will never exist since this is
an admin override; so the readlink command - if it existed - would still
return false.  I'm reasonably sure the lack of /bin/readlink is not
causing the udev rule to behave differently; so it's sufficient to fix
this particular issue for 16.10 and later and not SRU it.

What is *more* of an issue is that the structure of /lib/udev/rules.d/73
-usb-net-by-mac.rules causes a separate call out to readlink for every
single udev event, because the readlink check happens *before* checking
the ACTION/SUBSYSTEM/SUBSYSTEMS attributes of the event, unless
net.ifnames=0 is set.

So regardless of whether this is the root cause of the install failure,
this udev rule is causing hundreds of thousands of extra calls out to
/bin/readlink on boot, which should definitely be fixed by reordering
these checks.

Martin, can you please look into fixing this for xenial+yakkety?

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

** Also affects: debian-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Also affects: debian-installer (Ubuntu Yakkety)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: Confirmed

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

** Also affects: systemd (Ubuntu Yakkety)
   Importance: Undecided
 Assignee: Martin Pitt (pitti)
   Status: Triaged

** Changed in: busybox (Ubuntu Xenial)
   Status: New => Won't Fix

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

** Changed in: debian-installer (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: debian-installer (Ubuntu Yakkety)
   Status: Confirmed => Triaged

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

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  Fix Committed
Status in debian-installer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in busybox source package in Xenial:
  Won't Fix
Status in debian-installer source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Triaged
Status in busybox source package in Yakkety:
  Fix Committed
Status in debian-installer source package in Yakkety:
  Triaged
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.

  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:

  
  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'

  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  

[Touch-packages] [Bug 1579837] Re: Issue after wizard with policykit

[Launchpad Bug Tracker]

This bug was fixed in the package policykit-unity8 -
0.1+16.10.20160822.1-0ubuntu1

---
policykit-unity8 (0.1+16.10.20160822.1-0ubuntu1) yakkety; urgency=medium

  [ Rodney Dawes ]
  * Add missing bzr-builddeb config for non-native version for CI train.

  [ Ted Gould ]
  * Replacing that U8 isn't responding with a recoverable error instead
of crashing (LP: #1579837)
  * Setup Agent so that it is the fallback agent (LP: #1579837)
  * Setting the password echo mode on passwords (LP: #1580236)

 -- Ted Gould   Mon, 22 Aug 2016 19:45:35 +

** Changed in: policykit-unity8 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Issue after wizard with policykit

Status in Canonical System Image:
  In Progress
Status in accountsservice package in Ubuntu:
  Fix Released
Status in policykit-unity8 package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Bootstrap flash a fresh image to a device
  2. Run through the wizard selecting pin for authentication
  3. Tap on the get started button
  4. Phone freezes for a while
  5. At some point it unfreezes and you see the dash
  6. Reboot and get password login instead of pin login

  EXPECTED:
  I expect no freeze (possibly due to apport) and pin dialogue on reboot

  ACTUAL:
  I get a long freeze and on reboot instead of getting the pin dialogue to 
unlock the phone I get the password dialogue and full osk.

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

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

[Touch-packages] [Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

[Steve Langasek]

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

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  New
Status in debian-installer package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.

  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:

  
  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'

  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink 
/etc/udev/rules.d/80-net-setup-link.rules': No such
  file or directory'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with 
exit code 2.
  PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' 
/lib/udev/rules.d/73-usb-net-by-mac.rules:6
  passed device to netlink monitor 0x1003d01f730
  "

  
  Then it keeps hanged in this stage. We re-tested it by changing the file 
73-usb-net-by-mac.rules in initrd, replacing " 
/etc/udev/rules.d/80-net-setup-link.rules" to  
"/lib/udev/rules.d/80-net-setup-link.rules", since the former does not exist 
whereas the latter does. Same issue were observed!

  Notice that if we boot the installer with command-line "net.ifnames=0"
  or "net.ifnames=1", the problem does not reproduces anymore.

  We want to ask Canonical's help in investigating this issue.
  Thanks,

  
  Guilherme

  == Comment: #8 - Guilherme Guaglianoni Piccoli  -
  2016-08-19 10:09:51 ==

  
  == Comment: #9 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:10:31 ==

  
  == Comment: #10 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:11:49 ==

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

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

[Touch-packages] [Bug 1612619] Re: [MIR] indicator-network

[Michael Terry]

So the changelog entry says "re-enable tests on all architectures", but
the diff actually skips the tests on "arm64 s390x powerpc".  Why are
those tests broken?  The MP says "slow build servers" -- can we increase
a timeout or something?

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

Title:
  [MIR] indicator-network

Status in indicator-network package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has both unit tests and integration tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libqofono (needs bug)
   * network-manager-openvpn (bug #1574576)
   * urfkill (needs bug)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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

[Touch-packages] [Bug 1613267] Re: [MIR] maliit-framework

[Michael Terry]

Thanks for the poke, I forgot to update this.

** Changed in: maliit-framework (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  [MIR] maliit-framework

Status in maliit-framework package in Ubuntu:
  Fix Committed

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8 and ubuntu-keyboard

  [Security]
   * No known security issues at this time. Additional patches have been added 
to provide enhanced security when running in a Mir based environment by only 
allowing focused applications to access the on-screen keyboard.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Only missing dependencies are gles variants of libqt5gui5-gles and 
libqt5quick5-gles (the non-gles variants are already in main and are the first 
choice for these dependencies)

  [Standards compliance]
   * This package uses qmake. This package doesn't provide a UI itself, this is 
handled via additional plugin packages (such as ubuntu-keyboard), which contain 
translations.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1613267/+subscriptions

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

[Touch-packages] [Bug 1613471] Re: [MIR] telepathy-ofono

[Michael Terry]

Using architectures as a proxy for products (Desktop vs Touch) is not
great.  As we move to a convergent achitecture, we want Touch to work on
all architectures.

Is there a bug or roadmap for fixing the pulseaudio situation?

There could even be a short term hack, before your create a new module.
Where you only do routing if $XDG_SESSION_DESKTOP == ubuntu-touch or
something.

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

Title:
  [MIR] telepathy-ofono

Status in telepathy-ofono package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by nuntium and telephony-service.

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   * This package depends on ofono, ofono-qt, libphonenumber7 and 
telepathy-qt5. (none of them are currently in main)

  [Standards compliance]
   * This package uses cmake and requires no translation.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1613471/+subscriptions

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

[Touch-packages] [Bug 1598593] Re: No video acceleration for Radeon Xpress 200M (r300)

[indigocat]

Packages are plain, vanilla Ubuntu.

Here are 2 videos: the first is using the Vivid xorg stack, YouTube
fullscreen on Chromium. The second video is the same, under the Xenial
stack.

Vivid: https://youtu.be/Ykhp2L_pf7Y
Xenial: https://youtu.be/p7FvXTzlIa0

The regression is patent, and it was already there in Wily.

It would be nice to know if someone going to read what I'm typing here,
or if I can just quit reporting bugs and use that spare time in going
for a walk or having a beer with friends.

In case anyone closes this thread, go here:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1610591

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

Title:
  No video acceleration for Radeon Xpress 200M (r300)

Status in xorg package in Ubuntu:
  Invalid

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

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

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

  Here's Xorg.0.log: (with /etc/X11/xorg.conf; removing it did not solve
  the problem)

  39.964] 
  X.Org X Server 1.17.2
  Release Date: 2015-06-16
  [39.964] X Protocol Version 11, Revision 0
  [39.964] Build Operating System: Linux 3.19.0-43-generic i686 Ubuntu
  [39.964] Current Operating System: Linux EasyNote 4.2.0-41-lowlatency 
#48~14.04.1-Ubuntu SMP PREEMPT Fri Jun 24 18:29:28 UTC 2016 i686
  [39.964] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.2.0-41-lowlatency 
root=UUID=1ab2e24a-a209-4061-8dae-a11a19a5059f ro quiet splash
  [39.964] Build Date: 15 January 2016  10:17:41PM
  [39.964] xorg-server 2:1.17.2-1ubuntu9.1~trusty1 (For technical support 
please see http://www.ubuntu.com/support) 
  [39.964] Current version of pixman: 0.30.2
  [39.964]Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
  [39.964] Markers: (--) probed, (**) from config file, (==) default 
setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [39.964] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul  1 09:57:38 
2016
  [39.964] (==) Using config file: "/etc/X11/xorg.conf"
  [39.964] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [39.965] (==) ServerLayout "X.org Configured"
  [39.965] (**) |-->Screen "Screen0" (0)
  [39.965] (**) |   |-->Monitor "Monitor0"
  [39.965] (**) |   |-->Device "Card0"
  [39.965] (**) |-->Input Device "Mouse0"
  [39.965] (**) |-->Input Device "Keyboard0"
  [39.965] (**) Option "AIGLX" "on"
  [39.965] (==) Automatically adding devices
  [39.965] (==) Automatically enabling devices
  [39.965] (==) Automatically adding GPU devices
  [39.965] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [39.965]Entry deleted from font path.
  [39.965] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
  [39.965]Entry deleted from font path.
  [39.965] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
  [39.966]Entry deleted from font path.
  [39.966] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
  [39.966]Entry deleted from font path.
  [39.966] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
  [39.966]Entry deleted from font path.
  [39.966] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [39.966]Entry deleted from font path.
  [39.966] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
  [39.966]Entry deleted from font path.
  [39.966] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
  [39.966]Entry deleted from font path.
  [39.966] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
  [39.966]Entry deleted from font path.
  [39.966] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
  [39.966]Entry deleted from font path.
  [39.966] (**) FontPath set to:
  /usr/share/fonts/X11/misc,
  /usr/share/fonts/X11/Type1,
  built-ins,
  /usr/share/fonts/X11/misc,
  /usr/share/fonts/X11/Type1,
  built-ins
  [39.966] (**) ModulePath set to 

[Touch-packages] [Bug 1616196] [NEW] unable to stop avahi-daemon (dbus always restarts it)

[Simon Déziel]

Public bug reported:

When avahi-daemon is stopped, dbus always revives it.

Steps to reproduce:

1. sudo systemctl stop avahi-daemon.socket
2. sudo systemctl stop avahi-daemon.service
3. ps aux| grep avahi # should return nothing

Currently, dbus revives it right away as shown in syslog:

Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Got SIGTERM, quitting.
Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Leaving mDNS multicast group on 
interface ens3.IPv6 with address 2001:470:b1c3:7946::a4.
Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Leaving mDNS multicast group on 
interface ens3.IPv4 with address 172.24.26.52.
Aug 23 15:17:22 simon-vm avahi-daemon[4036]: avahi-daemon 0.6.32-rc exiting.
Aug 23 15:17:22 simon-vm dbus[1647]: [system] Activating via systemd: service 
name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Aug 23 15:17:22 simon-vm systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Aug 23 15:17:22 simon-vm systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Aug 23 15:17:22 simon-vm systemd[1]: Listening on Avahi mDNS/DNS-SD Stack 
Activation Socket.
Aug 23 15:17:22 simon-vm systemd[1]: Starting Avahi mDNS/DNS-SD Stack...


This automatic revival defeats the purpose of the up script [*] to deactivate 
avahi when .local is a regular DNS zone (not mDNS). This also goes against the 
principle of least surprise.

*: /etc/network/if-{down,up}.d/avahi-daemon

Additional information:

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

# apt-cache policy avahi-daemon dbus systemd
avahi-daemon:
  Installed: 0.6.32~rc+dfsg-1ubuntu2
  Candidate: 0.6.32~rc+dfsg-1ubuntu2
  Version table:
 *** 0.6.32~rc+dfsg-1ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
dbus:
  Installed: 1.10.6-1ubuntu3
  Candidate: 1.10.6-1ubuntu3
  Version table:
 *** 1.10.6-1ubuntu3 500
500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
systemd:
  Installed: 229-4ubuntu7
  Candidate: 229-4ubuntu7
  Version table:
 *** 229-4ubuntu7 500
500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu4 500
500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 [modified: 
usr/lib/avahi/avahi-daemon-check-dns.sh]
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Aug 23 15:09:40 2016
InstallationDate: Installed on 2016-08-22 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160819)
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: avahi
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  unable to stop avahi-daemon (dbus always restarts it)

Status in avahi package in Ubuntu:
  New

Bug description:
  When avahi-daemon is stopped, dbus always revives it.

  Steps to reproduce:

  1. sudo systemctl stop avahi-daemon.socket
  2. sudo systemctl stop avahi-daemon.service
  3. ps aux| grep avahi # should return nothing

  Currently, dbus revives it right away as shown in syslog:

  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Got SIGTERM, quitting.
  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Leaving mDNS multicast group on 
interface ens3.IPv6 with address 2001:470:b1c3:7946::a4.
  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: Leaving mDNS multicast group on 
interface ens3.IPv4 with address 172.24.26.52.
  Aug 23 15:17:22 simon-vm avahi-daemon[4036]: avahi-daemon 0.6.32-rc exiting.
  Aug 23 15:17:22 simon-vm dbus[1647]: [system] Activating via systemd: service 
name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
  Aug 23 15:17:22 simon-vm systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
  Aug 23 15:17:22 simon-vm systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
  Aug 23 15:17:22 simon-vm systemd[1]: Listening on Avahi mDNS/DNS-SD Stack 
Activation Socket.
  Aug 23 15:17:22 simon-vm systemd[1]: Starting Avahi mDNS/DNS-SD Stack...

  
  This automatic revival defeats the purpose of the up script [*] to deactivate 
avahi when .local is a regular DNS zone (not mDNS). This also goes against the 
principle of least surprise.

  *: /etc/network/if-{down,up}.d/avahi-daemon

  Additional information:

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

  # apt-cache policy avahi-daemon dbus systemd
  avahi-daemon:
Installed: 0.6.32~rc+dfsg-1ubuntu2
Candidate: 

[Touch-packages] [Bug 1492180] Re: iwconfig reports wrong bitrate (6 Mb/s)

[GPratique]

Same here, "iwconfig" is always reporting the same fixed bitrate value
regardless of the real one reported by "iw dev wl3ps0 link".

Linux Mint 18 Sarah Cinnamon 64b (fresh install)
Kernel 4.4.0-34-generic x86_64 on Dell Latitude E6520 with Intel Centrino 
Advanced-N 6205 [Taylor Peak]

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

Title:
  iwconfig reports wrong bitrate (6 Mb/s)

Status in One Hundred Papercuts:
  Confirmed
Status in wireless-tools package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to Wily. iwconfig now says the Bitrate is 6 Mb/s when 'iw dev
  wlan0 link' seems to report the correct bitrate.

  Firmware iwlwifi-7260-13.ucode

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: wireless-tools 30~pre9-8ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Sep  4 12:43:52 2015
  Dependencies:
   gcc-5-base 5.2.1-15ubuntu5
   libc6 2.21-0ubuntu4
   libgcc1 1:5.2.1-15ubuntu5
   libiw30 30~pre9-8ubuntu1
   multiarch-support 2.21-0ubuntu4
  InstallationDate: Installed on 2011-11-11 (1393 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: wireless-tools
  UpgradeStatus: Upgraded to wily on 2015-09-04 (0 days ago)

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

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

[Touch-packages] [Bug 1613469] Re: [MIR] ofono-qt

[Michael Terry]

ofono-phonesim wouldn't work for tests?

Do we have a roadmap to switching to libqofono?

As a general rule, we don't like to officially support already-abandoned
code with an existing replacement if we can help it.  It would be nice
to know that we do have a plan.

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

Title:
  [MIR] ofono-qt

Status in ofono-qt package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by telepathy-ofono

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests, but not executed during build because they 
require ofono to be running.

  [Dependencies]
   * This package depends only on qt5 which is already in main.

  [Standards compliance]
   * This package uses qmake and requires no translation.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ofono-qt/+bug/1613469/+subscriptions

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

[Touch-packages] [Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

[Steve Langasek]

Examining the initrd shows that readlink is provided as
/usr/bin/readlink -> /bin/busybox, not as /bin/readlink where systemd
expects it (and where it's shipped on an installed system).  This is a
bug in debian-installer's construction of that image - though gee it
would be nice if systemd didn't require hard-coded paths to everything.

There's no guarantee that fixing the bug that's causing this error
message will fix the underlying problem preventing your boot, but it
will at least fix the message spam.

** Package changed: systemd (Ubuntu) => debian-installer (Ubuntu)

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

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  New
Status in debian-installer package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.

  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:

  
  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'

  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink 
/etc/udev/rules.d/80-net-setup-link.rules': No such
  file or directory'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with 
exit code 2.
  PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' 
/lib/udev/rules.d/73-usb-net-by-mac.rules:6
  passed device to netlink monitor 0x1003d01f730
  "

  
  Then it keeps hanged in this stage. We re-tested it by changing the file 
73-usb-net-by-mac.rules in initrd, replacing " 
/etc/udev/rules.d/80-net-setup-link.rules" to  
"/lib/udev/rules.d/80-net-setup-link.rules", since the former does not exist 
whereas the latter does. Same issue were observed!

  Notice that if we boot the installer with command-line "net.ifnames=0"
  or "net.ifnames=1", the problem does not reproduces anymore.

  We want to ask Canonical's help in investigating this issue.
  Thanks,

  
  Guilherme

  == Comment: #8 - Guilherme Guaglianoni Piccoli  -
  2016-08-19 10:09:51 ==

  
  == Comment: #9 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:10:31 ==

  
  == Comment: #10 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:11:49 ==

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

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

[Touch-packages] [Bug 1616186] [NEW] Installing INtel graphics driver

[Jinyang Liu]

Public bug reported:

I want to install an Intel graphics driver for my intel 520.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Aug 23 21:07:24 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: oem-audio-hda-daily-lts-xenial, 0.201608180746~ubuntu16.04.1, 
4.4.0-34-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GconfCompiz:
 /apps/compiz-1/general:
   /apps/compiz-1/general/screen0:
/apps/compiz-1/general/screen0/options:
 active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake Integrated Graphics [17aa:382b]
InstallationDate: Installed on 2016-08-05 (18 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 5986:0671 Acer, Inc 
 Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80LM
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic 
root=UUID=43728dff-c0d7-4dfe-a5af-6e5d25228973 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/24/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: D7CN25WW(V2.03)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo B51-80
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo B51-80
dmi.modalias: 
dmi:bvnLENOVO:bvrD7CN25WW(V2.03):bd11/24/2015:svnLENOVO:pn80LM:pvrLenovoB51-80:rvnLENOVO:rnLenovoB51-80:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrLenovoB51-80:
dmi.product.name: 80LM
dmi.product.version: Lenovo B51-80
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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: Tue Aug 23 21:04:08 2016
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5572 
 vendor CMN
xserver.version: 2:1.18.3-1ubuntu2.3

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

Title:
  Installing INtel graphics driver

Status in xorg package in Ubuntu:
  New

Bug description:
  I want to install an Intel graphics driver for my intel 520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug 23 21:07:24 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: 

[Touch-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

[TenLeftFingers]

I'm responding to Sebastien's comment on usecases here:
https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1574020/comments/35

The question is about the default setting for this and I would encourage
connections the user has established in the session to be available and
auto-connected from the greeter so that remote shares can be mounted at
login for apps that need them, for example.

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

Title:
  Can't use networkmanager from lightdm

Status in NetworkManager:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

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

[Touch-packages] [Bug 1616180] [NEW] Any application that prompts for a password appears grayed out

[Daniel Senderowicz]

Public bug reported:

I upgraded from 14.04.5 to 16.04.1 on three different 32b machines. All
of them have the same issue and it happens in several applications. For
example if I attempt to update and/or upgrade the software, at one point
the GUI prompts for the password. However it is grayed out and I can't
enter the password. I found a way to enable that box by "rocking" to a
different user and coming back to my username and then the password
entry box will not be grayed out anymore.

I don't know what is the specific piece of software that presents GUIs
for different applications.

So in a few words I expect to be able to enter a password but the box is
grayed out.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: software-properties-gtk 0.96.20.4
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: GNOME-Flashback:Unity
Date: Tue Aug 23 11:40:41 2016
InstallationDate: Installed on 2015-05-17 (463 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to xenial on 2016-08-23 (0 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 xenial

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

Title:
  Any application that prompts for a password appears grayed out

Status in software-properties package in Ubuntu:
  New

Bug description:
  I upgraded from 14.04.5 to 16.04.1 on three different 32b machines.
  All of them have the same issue and it happens in several
  applications. For example if I attempt to update and/or upgrade the
  software, at one point the GUI prompts for the password. However it is
  grayed out and I can't enter the password. I found a way to enable
  that box by "rocking" to a different user and coming back to my
  username and then the password entry box will not be grayed out
  anymore.

  I don't know what is the specific piece of software that presents GUIs
  for different applications.

  So in a few words I expect to be able to enter a password but the box
  is grayed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-gtk 0.96.20.4
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Aug 23 11:40:41 2016
  InstallationDate: Installed on 2015-05-17 (463 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to xenial on 2016-08-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1616180/+subscriptions

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

[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

[Tomasz Przybysz]

Ubuntu 16.04, Nouveau NVidia driver, Razer Blade (2014) with an external
monitor attached via DisplayLink. Cursor is blinking on the primary,
built-in LCD.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1614070] Re: Unity8 doesn't rotate on new images whether via flash or ota

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 - 8.14+16.10.20160819-0ubuntu1

---
unity8 (8.14+16.10.20160819-0ubuntu1) yakkety; urgency=medium

  [ Lukáš Tinkl ]
  * Reset topmostIsFullscreen to correctly rotate the shell when
dismissing SIM PIN screen (LP: #1614070)

 -- Michał Sawicz   Fri, 19 Aug 2016
14:16:54 +

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

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

Title:
  Unity8 doesn't rotate on new images whether via flash or ota

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

Bug description:
  STEPS:
  1. Have a SIM-locked device
  2. Install the latest rc-proposed image (403 on arale)
  3. Once in the system rotate the device

  EXPECTED:
  Shell rotates and refreshes

  ACTUAL:
  Nothing happens

  http://paste.ubuntu.com/23064285/

  Above is the paste from 401 the image before the latest untiy8 landed
  you will note that the shell activates a rotate and the resolution
  changes, below it is the resolute of OTAing to 403 you'll note the
  sensor is still triggered but the shell no longer rotates.

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

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

[Touch-packages] [Bug 1613471] Re: [MIR] telepathy-ofono

[Tiago Salem Herrmann]

- I believe telepathy-ofono-ril-mc-plugin is disabled on most archs
because it depends on libhybris-utils, and that is not available on all
architectures.

- telepathy-ofono uses libpulse to change the system audio routes when
there is an incoming call and other call events. That affects the entire
system, so by the time we created the package (3 years ago) that was the
only way to make sure it wasn't going to break audio of desktops. This
audio management should be done outside of telepathy-ofono. We had a
discussion some time ago and decided to create a pulse module to take
care of that, but it is still not done.

- Those crashes are mostly related to pulse audio. I believe some of
them are actually fixed by now.

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

Title:
  [MIR] telepathy-ofono

Status in telepathy-ofono package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by nuntium and telephony-service.

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   * This package depends on ofono, ofono-qt, libphonenumber7 and 
telepathy-qt5. (none of them are currently in main)

  [Standards compliance]
   * This package uses cmake and requires no translation.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1613471/+subscriptions

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

[Touch-packages] [Bug 1579135] Re: AppArmor profile reloading causes an intermittent kernel BUG

[John Johansen]

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

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

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

** Also affects: apparmor (Ubuntu Yakkety)
   Importance: Critical
 Assignee: John Johansen (jjohansen)
   Status: Incomplete

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

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

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

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

Title:
  AppArmor profile reloading causes an intermittent kernel BUG

Status in apparmor package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Incomplete
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  First, a bit of background: I've built a go binary of the upstream
  snappy integration tests, and built them into a snap so that we can
  easily keep them up to date, and call them from other test suites.

  I'm running through the tests in qemu on a current 16 image (built
  yesteray), and hitting this most of the time with the homeInterface
  Suite tests in particular. The networkInterfaceSuite tests also seem
  to produce a similar problem:

  sudo snap connect home-consumer:home ubuntu-core:home
  [/] Connect home-consumer:home to ubuntu-core:home
  home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable
  sudo snap disconnect home-consumer:home ubuntu-core:home
  [  519.416354] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [  519.417327] IP: [] profile_cmp+0x2f/0x180
  [  519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 
  [  519.418574] Oops:  [#1] SMP 
  [  519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm 
snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport 
evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 
nls_iso8859_1 usb_storage ahci libahci squashfs
  [  519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 
  4.4.0-21-generic #37-Ubuntu
  [  519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [  519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 
88001b58c000
  [  519.425385] RIP: 0010:[]  [] 
profile_cmp+0x2f/0x180
  [  519.426242] RSP: 0018:88001b58fcb0  EFLAGS: 00010086
  [  519.426791] RAX:  RBX: 88001b1b1400 RCX: 
0006
  [  519.427628] RDX:  RSI:  RDI: 
0009
  [  519.428405] RBP: 88001b58fcc0 R08: 000a R09: 
0274
  [  519.429127] R10: 88001f236890 R11: 0274 R12: 

  [  519.429956] R13: 000b R14:  R15: 
88001abff950
  [  519.430957] FS:  7f0c1609b740() GS:88001fc0() 
knlGS:
  [  519.432256] CS:  0010 DS:  ES:  CR0: 80050033
  [  519.433030] CR2: 0038 CR3: 1b14b000 CR4: 
06f0
  [  519.433868] Stack:
  [  519.434204]  000c 88001abff9b0 88001b58fd08 
8138a0c3
  [  519.435355]  00011f2b9450 880c 88001abff950 
88001b1b1760
  [  519.436480]  88001f236848 88001abff900 88001f236840 
88001b58fd98
  [  519.437609] Call Trace:
  [  519.438007]  [] aa_vec_unique+0x163/0x240
  [  519.438709]  [] __aa_labelset_update_subtree+0x687/0x820
  [  519.439537]  [] aa_replace_profiles+0x59b/0xb70
  [  519.440268]  [] ? __kmalloc+0x22e/0x250
  [  519.440944]  [] policy_update+0x9f/0x1f0
  [  519.441617]  [] profile_replace+0x13/0x20
  [  519.442299]  [] __vfs_write+0x18/0x40
  [  519.443032]  [] vfs_write+0xa9/0x1a0
  [  519.443721]  [] ? do_sys_open+0x1bf/0x2a0
  [  519.16]  [] SyS_write+0x55/0xc0
  [  519.445042]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [  519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 
8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 
7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 
  [  519.451336] RIP  [] profile_cmp+0x2f/0x180
  [  519.452088]  RSP 
  [  519.452570] CR2: 0038
  [  519.453032] ---[ end trace 65ff12ee2e7c26af ]---

  The details of this test can be found at:
  
https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer

  Will follow up with more details

To manage notifications about this bug go to:

[Touch-packages] [Bug 1613469] Re: [MIR] ofono-qt

[Tiago Salem Herrmann]

Tests are not executed because they rely on ofonod running with some
modem enabled, which is not doable on test environments.

Yes, it was abandoned upstream because ofono-qt was mostly replaced by 
libqofono.
This is the main reason why it has no bugs open.

There was some discussion to move telepathy-ofono to use libqofono
(currently telepathy-ofono is the only package linking against it), but
it would require a lot of effort and would risk introducing new bugs to
the telephony stack, which is not an option at the moment.

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

Title:
  [MIR] ofono-qt

Status in ofono-qt package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by telepathy-ofono

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests, but not executed during build because they 
require ofono to be running.

  [Dependencies]
   * This package depends only on qt5 which is already in main.

  [Standards compliance]
   * This package uses qmake and requires no translation.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ofono-qt/+bug/1613469/+subscriptions

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

[Touch-packages] [Bug 1278790] Re: [Messaging] Show number of characters used and number of messages to send

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+16.10.20160819-0ubuntu1

---
messaging-app (0.1+16.10.20160819-0ubuntu1) yakkety; urgency=medium

  [ Devid Antonio Filoni ]
  * Preserve empty lines and leading spaces. (LP: #1366592)

  [ Pat McGowan ]
  * This adds support for showing the current character count and number
of messages to be sent via SMS. It includes a new label on top of
the text area showing number of characters / 160 (number of
messages). It is shown once the message is over 1 line in length,
per other systems. (LP: #1278790)

  [ Tiago Salem Herrmann ]
  * Share text only if there is no url in the content-hub transfer. (LP:
#1613338)

 -- Tiago Salem Herrmann   Fri, 19 Aug
2016 15:15:35 +

** Changed in: messaging-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [Messaging] Show number of characters used and number of messages to
  send

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Triaged
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  As many carriers charge per text message sent, it'd be nice to show
  how many characters were used for the message, so the sender knows how
  many sent text messages this boils down to.

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

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

[Touch-packages] [Bug 1366592] Re: empty lines and leading spaces are not shown in messages

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+16.10.20160819-0ubuntu1

---
messaging-app (0.1+16.10.20160819-0ubuntu1) yakkety; urgency=medium

  [ Devid Antonio Filoni ]
  * Preserve empty lines and leading spaces. (LP: #1366592)

  [ Pat McGowan ]
  * This adds support for showing the current character count and number
of messages to be sent via SMS. It includes a new label on top of
the text area showing number of characters / 160 (number of
messages). It is shown once the message is over 1 line in length,
per other systems. (LP: #1278790)

  [ Tiago Salem Herrmann ]
  * Share text only if there is no url in the content-hub transfer. (LP:
#1613338)

 -- Tiago Salem Herrmann   Fri, 19 Aug
2016 15:15:35 +

** Changed in: messaging-app (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  empty lines and leading spaces are not shown in messages

Status in Band-aids for Ubuntu Phone:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  It seems that newlines in messages are sent and received, but they are
  not shown in the messaging-app (I would expect that they would be
  shown). However, the newline is shown in the notification bubble (see
  attached screenshot) and in the Notification center.

  OS: Ubuntu 14.10 (r203)

  Version of the app:
  $ apt-cache policy messaging-app
  messaging-app:
Installed: 0.1+14.10.20140813.2-0ubuntu1
Candidate: 0.1+14.10.20140828.3-0ubuntu1
Version table:
   0.1+14.10.20140828.3-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ utopic/universe armhf 
Packages
   *** 0.1+14.10.20140813.2-0ubuntu1 0
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/band-aids-uphone/+bug/1366592/+subscriptions

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

[Touch-packages] [Bug 1613338] Re: Share Link not working

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+16.10.20160819-0ubuntu1

---
messaging-app (0.1+16.10.20160819-0ubuntu1) yakkety; urgency=medium

  [ Devid Antonio Filoni ]
  * Preserve empty lines and leading spaces. (LP: #1366592)

  [ Pat McGowan ]
  * This adds support for showing the current character count and number
of messages to be sent via SMS. It includes a new label on top of
the text area showing number of characters / 160 (number of
messages). It is shown once the message is over 1 line in length,
per other systems. (LP: #1278790)

  [ Tiago Salem Herrmann ]
  * Share text only if there is no url in the content-hub transfer. (LP:
#1613338)

 -- Tiago Salem Herrmann   Fri, 19 Aug
2016 15:15:35 +

** Changed in: messaging-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Share Link not working

Status in Canonical System Image:
  Fix Committed
Status in messaging-app package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  on latest rc-proposed I can no longer share a link with messaging-app.
  Instead of the link being shared I get the page title only. Should
  display the page title and the url

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

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

[Touch-packages] [Bug 1615222] Re: [REGRESSION] Unable to use czech diacritics from czech keyboard for two stroke combinations

[Karl Koerner]

I spoke with a colleague at work, who also recently upgraded to 16.04
and regularly uses a Czech keyboard.  He did not encounter this problem.
I see now in the keyboards menu in the toolbar (top right) >  Text Entry
Settings,  that there are now 6 options for a Czech keyboard.  The
original one I was using was the first one "Czech".  I tried the
different input sources and found that Czech (UCW layout, accented
letter only), provides the correct key combinations. Ť ď ó for example,
but this is not the classic qwertz keyboard, which should also provide Ť
ď ó not (now switched to "Czech" ) ˇT ˇd ´o.

Checking the other Czech input sources with a simple editor like GVIM,
none of them seem to work with ˇ or ´.  Dvorak keyboards I've never
used.

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

Title:
  [REGRESSION] Unable to use czech diacritics from czech keyboard for
  two stroke combinations

Status in ibus package in Ubuntu:
  New

Bug description:
  Upgrade REGRESSION

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

  GENERAL DESCRIPTION

  I just upgraded from 15.10 to 16.04 this morning.  Everything seemed
  fine until I opened some translating work in libreoffice.  Trying to
  type the letter combination n with a háček  ˇ + n = ň, for example the
  word "Mňau", I found that whenever I hit the key with the háček symbol
  ˇ the háček automatically appears. In the traditional czech keyboard
  the first stroke of the ˇ should not produce anything until the second
  keystroke e.g. 'n', which will then produce the correct combination ň.
  The most common combinations are available through what would be the
  number keys in an english keyboard, however combinations with some
  consonants and with capital letters require two strokes.

  I also checked this in GVIM and the behaviour is the same.  The first stroke 
on the háček ˇ or the čárka ´ (same key but not shifted) immediately produces 
the character without waiting for the second stroke. I can work around this 
using spellcheck and replacing and then copying the correct combination where 
it might be needed.  However, this has long been working in earlier Ubuntu 
installations even across upgrades from 14.10 to 15.04 and from 15.04 to 15.10. 

 
  WHAT WAS EXPECTED

  Using the háček or čárka key on the czech keyboard [´|ˇ] the system
  would wait for a second keystroke to produce the correct diacritic and
  letter combination, as in the past.

  WHAT HAPPENED INSTEAD

  As soon as the  háček or čárka key was pressed, the diacritic appeared
  before the second keystroke.  The correct combination cannot be made.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160801.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-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
  CurrentDesktop: Unity
  Date: Sat Aug 20 13:10:06 2016
  DistUpgraded: 2016-08-20 11:19:30,354 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:2249]
  InstallationDate: Installed on 2015-03-20 (518 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP ProBook 470 G2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-08-20 (0 days ago)
  dmi.bios.date: 11/27/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M73 Ver. 01.00
  dmi.board.name: 2249
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 59.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM73Ver.01.00:bd11/27/2014:svnHewlett-Packard:pnHPProBook470G2:pvrA3008DD10B03:rvnHewlett-Packard:rn2249:rvrKBCVersion59.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 470 G2
  dmi.product.version: A3008DD10B03
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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: 

[Touch-packages] [Bug 1615409] Re: network problem after update ubutu14 to ubuntu16

[Baerbel]

** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  network problem after update ubutu14 to ubuntu16

Status in network-manager package in Ubuntu:
  New

Bug description:
  After updateing ubuntu 14 to ubuntu 16 there are two problems.

   firefox 48.0: When I starts www-farnell.de (electronics distributor) I can 
not use their search engine. You will find tcp reports at: 
http://www.ikebana-studio-kessenbrock.de/ubuntu16/ 
  After time out I receives the message: 
  Request Timeout The server timed out while waiting for the browser's request.

  Reference #2.5caf3554.1471165829.0

  I clearde the cach and cookies, but the problem is stable.

   FTP  via bareFTP It is not possible to upload big files (pictures) to the 
server.
  You will find the tcp report also at 
http://www.ikebana-studio-kessenbrock.de/ubuntu16/ 

  I changed back to ubuntu 14 and both features are working fine.

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

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

[Touch-packages] [Bug 1615409] [NEW] network problem after update ubutu14 to ubuntu16

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After updateing ubuntu 14 to ubuntu 16 there are two problems.

 firefox 48.0: When I starts www-farnell.de (electronics distributor) I can not 
use their search engine. You will find tcp reports at: 
http://www.ikebana-studio-kessenbrock.de/ubuntu16/ 
After time out I receives the message: 
Request Timeout The server timed out while waiting for the browser's request.

Reference #2.5caf3554.1471165829.0

I clearde the cach and cookies, but the problem is stable.

 FTP  via bareFTP It is not possible to upload big files (pictures) to the 
server.
You will find the tcp report also at 
http://www.ikebana-studio-kessenbrock.de/ubuntu16/ 

I changed back to ubuntu 14 and both features are working fine.

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


** Tags: bot-comment
-- 
network problem after update ubutu14 to ubuntu16
https://bugs.launchpad.net/bugs/1615409
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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

[Touch-packages] [Bug 1616148] [NEW] package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 101

[Fernando Santamaria]

Public bug reported:

No way to install the package python-gi 3.20.0-0ubuntu1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-gi 3.20.0-0ubuntu1
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: Tue Aug 23 16:53:08 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 101
InstallationDate: Installed on 2016-04-02 (143 days ago)
InstallationMedia: Lubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: pygobject
Title: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 101
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package python-gi 3.20.0-0ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 101

Status in pygobject package in Ubuntu:
  New

Bug description:
  No way to install the package python-gi 3.20.0-0ubuntu1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-gi 3.20.0-0ubuntu1
  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: Tue Aug 23 16:53:08 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 101
  InstallationDate: Installed on 2016-04-02 (143 days ago)
  InstallationMedia: Lubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: pygobject
  Title: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 101
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Brad Figg]

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

apport-collect 1616107

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

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

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

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

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
  Aug 23 

[Touch-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 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.8-rc3

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

** Tags added: kernel-da-key needs-bisect xenial

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 

[Touch-packages] [Bug 1616145] [NEW] package libqtcore4 (not installed) failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias

[JOSÉ CASANOVA]

Public bug reported:

Error during install Skype on Xubuntu 16.04.1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqtcore4 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Aug 23 12:55:07 2016
ErrorMessage: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', 
que es distinto de otras instancias del paquetes libqtcore4:i386
InstallationDate: Installed on 2016-08-07 (16 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: qt4-x11
Title: package libqtcore4 (not installed) failed to install/upgrade: intentando 
sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras 
instancias del paquetes libqtcore4:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package libqtcore4 (not installed) failed to install/upgrade:
  intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que
  es distinto de otras instancias del paquetes libqtcore4:i386

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  Error during install Skype on Xubuntu 16.04.1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 23 12:55:07 2016
  ErrorMessage: intentando sobreescribir el compartido 
`/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes 
libqtcore4:i386
  InstallationDate: Installed on 2016-08-07 (16 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 (not installed) failed to install/upgrade: 
intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es 
distinto de otras instancias del paquetes libqtcore4:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1616145/+subscriptions

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

[Touch-packages] [Bug 1615964] Re: Mouse pointer is invisible after suspend

[Paul White]

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

Almost certainly a duplicate of a bug that was reported many months ago
- bug 1568604.

Marking as a duplicate. If you're not seeing what almost 500 others have
reported as seeing then please let us know.

** This bug has been marked a duplicate of bug 1568604
   Mouse cursor lost when unlocking with Intel graphics

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

Title:
  Mouse pointer is invisible after suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu-Studio 16.04. After each suspending the mouse
  pointer is invisible, makeng me to do `Ctrl+Alt+F1` and `Ctrl+Alt+F7`
  to make it visible again. I have also searched
  (http://askubuntu.com/questions/808879/mouse-pointer-gets-invisible-
  after-standby) and it seems to be a bug.

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

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

[Touch-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

[AW]

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

** Also affects: bridge-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058984]  [] ? 
security_file_alloc+0x33/0x50
  Aug 23 15:09:46 base1 kernel: [  618.059095]  [] 
sock_ioctl+0x215/0x290
  Aug 23 15:09:46 base1 kernel: [  618.059121]  [] 
do_vfs_ioctl+0x29f/0x490
  Aug 23 15:09:46 base1 kernel: [  618.059223]  [] ? 
__do_page_fault+0x1b4/0x400
  Aug 23 15:09:46 base1 kernel: [  618.059264]  [] ? 
fd_install+0x25/0x30
 

[Touch-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore

[Douglas Santos]

Aravind, are you using Gutenprint + CUPS ? Didn't you try the official
Epson drivers? Your printer uses  the same driver I use here "201207w"
for the printer and the "iscan 1.0.1" for the scanner.

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

Title:
  [Regression] Epson's printer driver packages cannot be installed as
  lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1616138] [NEW] i386 E: Build failure (dpkg-buildpackage died)

[iLogin]

Public bug reported:

Failed to build heimdal 1.7~git20160703+dfsg-1 armhf i386 powerpc
https://launchpadlibrarian.net/276694805/buildlog_ubuntu-yakkety-i386.heimdal_1.7~git20160703+dfsg-1_BUILDING.txt.gz

as a result a problem to install wine

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

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

Title:
  i386 E: Build failure (dpkg-buildpackage died)

Status in heimdal package in Ubuntu:
  New

Bug description:
  Failed to build heimdal 1.7~git20160703+dfsg-1 armhf i386 powerpc
  
https://launchpadlibrarian.net/276694805/buildlog_ubuntu-yakkety-i386.heimdal_1.7~git20160703+dfsg-1_BUILDING.txt.gz

  as a result a problem to install wine

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

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

[Touch-packages] [Bug 1608986] Re: [amd64 0.166-2] FAIL run-backtrace-native-biarch.sh (exit status: 1)

[Launchpad Bug Tracker]

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

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

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

Title:
  [amd64 0.166-2] FAIL run-backtrace-native-biarch.sh (exit status: 1)

Status in elfutils package in Ubuntu:
  Confirmed

Bug description:
  libelf1 0.166-2 build has failed

  https://launchpadlibrarian.net/276347491/buildlog_ubuntu-yakkety-
  amd64.elfutils_0.166-2_BUILDING.txt.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: elfutils (not installed)
  ProcVersionSignature: Ubuntu 4.6.0-9.11-generic 4.6.4
  Uname: Linux 4.6.0-9-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Aug  2 16:38:24 2016
  SourcePackage: elfutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1611565] Re: Rsyslog facility based selectors not working for Dovecot

[Bmatthewshea]

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

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

Title:
  Rsyslog facility based selectors not working for Dovecot

Status in Dovecot:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  Post system upgrade from 14.04.4 to 16.04.1, Rsyslog facility/priority
  based selectors are no longer working for Dovecot 2.2.22. For
  instance, "imap-login" events do not appear in the logfiles, while
  "lmtp" events, which in our case are captured using property-based
  filters, do.

  /etc/rsyslog.d/23-dovecot.conf
  local5.*-/var/log/dovecot.log
  local5.warn;local5.err;local5.crit  -/var/log/dovecot.err
  :msg,contains,"lmtp"-/var/log/dovecot.log
  :msg,contains,"sieve"   -/var/log/dovecot.log

  & stop

  
  /etc/dovecot/conf.d/10-logging.conf:
  log_path = syslog
  syslog_facility = local5
  auth_verbose = yes

  
  The configuration has not been changed since it was last working, i.e. before 
the upgrade. Changing log_path directive in Dovecot from "syslog" to a valid 
file path is a working workaround:

  /etc/dovecot/conf.d/10-logging.conf:
  log_path = /var/log/dovecot.log

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

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

[Touch-packages] [Bug 1278790] Re: [Messaging] Show number of characters used and number of messages to send

[Pat McGowan]

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

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

Title:
  [Messaging] Show number of characters used and number of messages to
  send

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Triaged
Status in messaging-app package in Ubuntu:
  In Progress

Bug description:
  As many carriers charge per text message sent, it'd be nice to show
  how many characters were used for the message, so the sender knows how
  many sent text messages this boils down to.

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

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

[Touch-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore

[Till Kamppeter]

Aravind, and anyone who has followed the instructions of comment #101.
Please chack the "log" file from strace again whether you generally find
lines with file paths with "epson" or "EPSON" in it. They do not need to
contain "/opt/".

Run also ldd on these file paths.

** Summary changed:

- [Regression] epson-inkjet-printer-201106w package cannot be installed as lsb 
package is not available anymore
+ [Regression] Epson's printer driver packages cannot be installed as lsb 
package is not available anymore

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

Title:
  [Regression] Epson's printer driver packages cannot be installed as
  lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1366592] Re: empty lines and leading spaces are not shown in messages

[Pat McGowan]

** Changed in: band-aids-uphone
   Status: In Progress => Fix Committed

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

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

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

Title:
  empty lines and leading spaces are not shown in messages

Status in Band-aids for Ubuntu Phone:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  It seems that newlines in messages are sent and received, but they are
  not shown in the messaging-app (I would expect that they would be
  shown). However, the newline is shown in the notification bubble (see
  attached screenshot) and in the Notification center.

  OS: Ubuntu 14.10 (r203)

  Version of the app:
  $ apt-cache policy messaging-app
  messaging-app:
Installed: 0.1+14.10.20140813.2-0ubuntu1
Candidate: 0.1+14.10.20140828.3-0ubuntu1
Version table:
   0.1+14.10.20140828.3-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ utopic/universe armhf 
Packages
   *** 0.1+14.10.20140813.2-0ubuntu1 0
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/band-aids-uphone/+bug/1366592/+subscriptions

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

[Touch-packages] [Bug 1613338] Re: Share Link not working

[Pat McGowan]

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

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

Title:
  Share Link not working

Status in Canonical System Image:
  Fix Committed
Status in messaging-app package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  on latest rc-proposed I can no longer share a link with messaging-app.
  Instead of the link being shared I get the page title only. Should
  display the page title and the url

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

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

[Touch-packages] [Bug 1595485] Re: packages to remove from yakkety

[LocutusOfBorg]

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

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

Title:
  packages to remove from yakkety

Status in flightgear package in Ubuntu:
  Invalid
Status in fpc package in Ubuntu:
  Incomplete
Status in fslview package in Ubuntu:
  Fix Released
Status in gnome-video-arcade package in Ubuntu:
  Fix Released
Status in insighttoolkit package in Ubuntu:
  Fix Released
Status in libpng package in Ubuntu:
  Fix Released
Status in mame package in Ubuntu:
  Fix Released
Status in pepperflashplugin-nonfree package in Ubuntu:
  Fix Released
Status in ppc64-diag package in Ubuntu:
  Fix Released
Status in python-pysam package in Ubuntu:
  New
Status in runit package in Ubuntu:
  New
Status in samtools package in Ubuntu:
  Fix Released
Status in simgear package in Ubuntu:
  Invalid
Status in singular package in Ubuntu:
  New
Status in stacks package in Ubuntu:
  Fix Released
Status in vcmi package in Ubuntu:
  Fix Released
Status in vmtk package in Ubuntu:
  Fix Released
Status in vtk package in Ubuntu:
  Fix Released
Status in fpc package in Debian:
  Fix Released

Bug description:
  (NOTE: all of them are gone from Debian)
  1) libpng.
  Superseded by libpng16

  no reverse dependencies I can see
  2) insighttoolkit
  Superseded by insighttoolkit4
  it doesn't build on powerpc, so we have to remove binaries here
  (sorry, but Debian maintains only amd64 and i386, and we can't maintain all 
the others including powerpc)

  just removing vmtk/powerpc should allow its removal too

  3) vtk
  Superseded by vtk6

  needs vmtk migration
  and fslview removal or demote to proposed.
  Debian broke it, because it is already broken, and it has little fix in time 
probability
  (probably we will remove in Debian soon)

  4) samtools
  old binaries left on armhf: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on powerpc: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on s390x: libbam-dev, samtools (from 0.1.19-1ubuntu1)

  removed in Debian too

  5) pepperflashplugin-nonfree [i386]
  please remove on i386 (removed in Debian too)
  upstream is not supporting it, so it can't be downloaded/installed on i386 
anymore

  6) singular [armhf]
  removed in Debian too

  7) fpc [powerpc]
  powerpc sadness with glib 2.23
  https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1562480

  8) mame [ppc64el]
  sandness on that arch, removed in Debian

  9) flightgear [armhf]
  I don't care about simgear/armhf, because it is unlikely for such a game to 
run on thar architecture.

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

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

[Touch-packages] [Bug 1595485] Re: packages to remove from yakkety

[LocutusOfBorg]

lets wait for a bootstrap instead

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

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

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

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

Title:
  packages to remove from yakkety

Status in flightgear package in Ubuntu:
  Invalid
Status in fpc package in Ubuntu:
  Incomplete
Status in fslview package in Ubuntu:
  Fix Released
Status in gnome-video-arcade package in Ubuntu:
  Fix Released
Status in insighttoolkit package in Ubuntu:
  Fix Released
Status in libpng package in Ubuntu:
  Fix Released
Status in mame package in Ubuntu:
  Fix Released
Status in pepperflashplugin-nonfree package in Ubuntu:
  Fix Released
Status in ppc64-diag package in Ubuntu:
  Fix Released
Status in python-pysam package in Ubuntu:
  New
Status in runit package in Ubuntu:
  New
Status in samtools package in Ubuntu:
  Fix Released
Status in simgear package in Ubuntu:
  Invalid
Status in singular package in Ubuntu:
  New
Status in stacks package in Ubuntu:
  Fix Released
Status in vmtk package in Ubuntu:
  Fix Released
Status in vtk package in Ubuntu:
  Fix Released
Status in fpc package in Debian:
  Fix Released

Bug description:
  (NOTE: all of them are gone from Debian)
  1) libpng.
  Superseded by libpng16

  no reverse dependencies I can see
  2) insighttoolkit
  Superseded by insighttoolkit4
  it doesn't build on powerpc, so we have to remove binaries here
  (sorry, but Debian maintains only amd64 and i386, and we can't maintain all 
the others including powerpc)

  just removing vmtk/powerpc should allow its removal too

  3) vtk
  Superseded by vtk6

  needs vmtk migration
  and fslview removal or demote to proposed.
  Debian broke it, because it is already broken, and it has little fix in time 
probability
  (probably we will remove in Debian soon)

  4) samtools
  old binaries left on armhf: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on powerpc: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on s390x: libbam-dev, samtools (from 0.1.19-1ubuntu1)

  removed in Debian too

  5) pepperflashplugin-nonfree [i386]
  please remove on i386 (removed in Debian too)
  upstream is not supporting it, so it can't be downloaded/installed on i386 
anymore

  6) singular [armhf]
  removed in Debian too

  7) fpc [powerpc]
  powerpc sadness with glib 2.23
  https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1562480

  8) mame [ppc64el]
  sandness on that arch, removed in Debian

  9) flightgear [armhf]
  I don't care about simgear/armhf, because it is unlikely for such a game to 
run on thar architecture.

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

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

[Touch-packages] [Bug 1615964] Re: Mouse pointer is invisible after suspend

[Mario Limonciello]

** Package changed: fwupd (Ubuntu) => xorg (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/1615964

Title:
  Mouse pointer is invisible after suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu-Studio 16.04. After each suspending the mouse
  pointer is invisible, makeng me to do `Ctrl+Alt+F1` and `Ctrl+Alt+F7`
  to make it visible again. I have also searched
  (http://askubuntu.com/questions/808879/mouse-pointer-gets-invisible-
  after-standby) and it seems to be a bug.

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

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

[Touch-packages] [Bug 1595485] Re: packages to remove from yakkety

[LocutusOfBorg]

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820170
python-pysam (i386) removal request in Debian

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

Title:
  packages to remove from yakkety

Status in flightgear package in Ubuntu:
  Invalid
Status in fpc package in Ubuntu:
  Incomplete
Status in fslview package in Ubuntu:
  Fix Released
Status in gnome-video-arcade package in Ubuntu:
  Fix Released
Status in insighttoolkit package in Ubuntu:
  Fix Released
Status in libpng package in Ubuntu:
  Fix Released
Status in mame package in Ubuntu:
  Fix Released
Status in pepperflashplugin-nonfree package in Ubuntu:
  Fix Released
Status in ppc64-diag package in Ubuntu:
  Fix Released
Status in python-pysam package in Ubuntu:
  New
Status in runit package in Ubuntu:
  New
Status in samtools package in Ubuntu:
  Fix Released
Status in simgear package in Ubuntu:
  Invalid
Status in singular package in Ubuntu:
  New
Status in stacks package in Ubuntu:
  Fix Released
Status in vmtk package in Ubuntu:
  Fix Released
Status in vtk package in Ubuntu:
  Fix Released
Status in fpc package in Debian:
  Fix Released

Bug description:
  (NOTE: all of them are gone from Debian)
  1) libpng.
  Superseded by libpng16

  no reverse dependencies I can see
  2) insighttoolkit
  Superseded by insighttoolkit4
  it doesn't build on powerpc, so we have to remove binaries here
  (sorry, but Debian maintains only amd64 and i386, and we can't maintain all 
the others including powerpc)

  just removing vmtk/powerpc should allow its removal too

  3) vtk
  Superseded by vtk6

  needs vmtk migration
  and fslview removal or demote to proposed.
  Debian broke it, because it is already broken, and it has little fix in time 
probability
  (probably we will remove in Debian soon)

  4) samtools
  old binaries left on armhf: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on powerpc: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on s390x: libbam-dev, samtools (from 0.1.19-1ubuntu1)

  removed in Debian too

  5) pepperflashplugin-nonfree [i386]
  please remove on i386 (removed in Debian too)
  upstream is not supporting it, so it can't be downloaded/installed on i386 
anymore

  6) singular [armhf]
  removed in Debian too

  7) fpc [powerpc]
  powerpc sadness with glib 2.23
  https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1562480

  8) mame [ppc64el]
  sandness on that arch, removed in Debian

  9) flightgear [armhf]
  I don't care about simgear/armhf, because it is unlikely for such a game to 
run on thar architecture.

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

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

[Touch-packages] [Bug 1615474] Re: Wifi networking no longer possible, network indicator broken

[Alejandro J. Cura]

Hi Matthew, sorry to hear about this breakage, and that USB is not
working for you.

Can you please let us know if the process "indicator-network" process is
still running? Please paste the output of this: ps -ax | grep indicator-
network

Also, please paste any indicator-network logs you may find in
~/.cache/upstart

If you need wifi to get those things out of the phone, you may try using
the command line, as explained in http://askubuntu.com/questions/138472
/how-do-i-connect-to-a-wpa-wifi-network-using-the-command-line

That might help you also upgrade to a newer OTA, to see if things get
fixed, or to backup your data in case you want to try doing a full
device reset.

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

Title:
  Wifi networking no longer possible, network indicator broken

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  New

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Aravind Gopal]

Scan utilities not working..

** Attachment added: "Screenshot_20160823_210046.png"
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1536353/+attachment/4726447/+files/Screenshot_20160823_210046.png

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1613267] Re: [MIR] maliit-framework

[Bill Filler]

** Changed in: maliit-framework (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  [MIR] maliit-framework

Status in maliit-framework package in Ubuntu:
  Confirmed

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8 and ubuntu-keyboard

  [Security]
   * No known security issues at this time. Additional patches have been added 
to provide enhanced security when running in a Mir based environment by only 
allowing focused applications to access the on-screen keyboard.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Only missing dependencies are gles variants of libqt5gui5-gles and 
libqt5quick5-gles (the non-gles variants are already in main and are the first 
choice for these dependencies)

  [Standards compliance]
   * This package uses qmake. This package doesn't provide a UI itself, this is 
handled via additional plugin packages (such as ubuntu-keyboard), which contain 
translations.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1613267/+subscriptions

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

[Touch-packages] [Bug 1502484] Re: Picture shown != picture taken. Breaks flash light pictures.

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Picture shown != picture taken. Breaks flash light pictures.

Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  MEIZU MX4 running official release 15.04(r4)

  Main problem:
  When you take a picture in the camera app, the app makes a shutter sound and 
freezes the display for a second. Then you see this picture slide to the right 
(presumably "into the gallery"). This would be a really nice piece of well done 
user feedback -- if it wasn't lying to the user. The picture you will find in 
the gallery is NOT the one you have seen sliding to the right. Instead, the 
picture actually taken is produced some milliseconds later!
  You can easily show this by taking a picture of a running stop watch. I first 
noticed it when taking pictures of a jumping person: The "feedback picture" 
always showed a person in the air. It was very disappointing finding my gallery 
full of persons already back on the ground, when I looked at it later.

  Follow up problem:
  The flash light is obviously synchronized to the preview picture, not the 
picture really taken. This completely breaks flash light pictures.

  Steps to reproduce:
  1. Open camera app
  2. Set flash to on or auto
  3. Enter a dark room
  4. Take a picture
  5. Observe that the "feedback picture" that slides to the right shows a 
properly lit photograph.
  6. Go to the gallery and observe that the picture actually taken shows 
complete darkness.

  I.e.: Flashlight pictures are broken. You cannot take flashlight pictures 
with the Ubuntu phone in the current state of the app.
  This seems to me like a rather severe problem?

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

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

[Touch-packages] [Bug 1595485] Re: packages to remove from yakkety

[LocutusOfBorg]

vcmi has a -dbg package removed with migration to auto dbg

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

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

Title:
  packages to remove from yakkety

Status in flightgear package in Ubuntu:
  Invalid
Status in fpc package in Ubuntu:
  Incomplete
Status in fslview package in Ubuntu:
  Fix Released
Status in gnome-video-arcade package in Ubuntu:
  Fix Released
Status in insighttoolkit package in Ubuntu:
  Fix Released
Status in libpng package in Ubuntu:
  Fix Released
Status in mame package in Ubuntu:
  Fix Released
Status in pepperflashplugin-nonfree package in Ubuntu:
  Fix Released
Status in ppc64-diag package in Ubuntu:
  Fix Released
Status in python-pysam package in Ubuntu:
  New
Status in runit package in Ubuntu:
  New
Status in samtools package in Ubuntu:
  Fix Released
Status in simgear package in Ubuntu:
  Invalid
Status in singular package in Ubuntu:
  New
Status in stacks package in Ubuntu:
  Fix Released
Status in vcmi package in Ubuntu:
  New
Status in vmtk package in Ubuntu:
  Fix Released
Status in vtk package in Ubuntu:
  Fix Released
Status in fpc package in Debian:
  Fix Released

Bug description:
  (NOTE: all of them are gone from Debian)
  1) libpng.
  Superseded by libpng16

  no reverse dependencies I can see
  2) insighttoolkit
  Superseded by insighttoolkit4
  it doesn't build on powerpc, so we have to remove binaries here
  (sorry, but Debian maintains only amd64 and i386, and we can't maintain all 
the others including powerpc)

  just removing vmtk/powerpc should allow its removal too

  3) vtk
  Superseded by vtk6

  needs vmtk migration
  and fslview removal or demote to proposed.
  Debian broke it, because it is already broken, and it has little fix in time 
probability
  (probably we will remove in Debian soon)

  4) samtools
  old binaries left on armhf: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on powerpc: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on s390x: libbam-dev, samtools (from 0.1.19-1ubuntu1)

  removed in Debian too

  5) pepperflashplugin-nonfree [i386]
  please remove on i386 (removed in Debian too)
  upstream is not supporting it, so it can't be downloaded/installed on i386 
anymore

  6) singular [armhf]
  removed in Debian too

  7) fpc [powerpc]
  powerpc sadness with glib 2.23
  https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1562480

  8) mame [ppc64el]
  sandness on that arch, removed in Debian

  9) flightgear [armhf]
  I don't care about simgear/armhf, because it is unlikely for such a game to 
run on thar architecture.

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

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

[Touch-packages] [Bug 1592447] Re: camera startup time regression

[Florian Boucault]

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

** Changed in: camera-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  camera startup time regression

Status in Canonical System Image:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  Please see 
  http://reqorts.qa.ubuntu.com/reports/qa/performance/dashboard/index.html

  the camera time recently jumped in startup time, but this did not seem
  to be something caused by a common component when comparing to other
  apps.

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

-- 
Mailing list: https://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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Steve Langasek]

On Tue, Aug 23, 2016 at 03:26:24PM -, Aravind Gopal wrote:
> In the log file I did n't find any file/path with 'epson' under "/opt/"
> directory or sub directory.

Then you don't have the printer driver installed that requires the lsb
package, and this is not a bug in the LSB package.  You should file a new
bug report for your issue.


** Summary changed:

- [regression] Printer drivers install is broken as lsb package is not 
available anymore
+ [Regression] epson-inkjet-printer-201106w package cannot be installed as lsb 
package is not available anymore

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

Title:
  [Regression] epson-inkjet-printer-201106w package cannot be installed
  as lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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