date:20170306

** Summary changed:

- Mir server crashes when given an invalid keymap
+ Unity8/Mir server crashes when given an invalid keymap

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

Title:
  Unity8/Mir server crashes when given an invalid keymap

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/4b8d65fc943d9604a00af4439b24bf85ddc6d1a7

  I foolishly tested unity8's keymap switching with the keymap "zh" (I
  should have used "cn").

  But I noticed that libmirclient crashed when I switched to "zh".
  While this isn't a supported use case, we shouldn't crash.

  Here's a non-debugful stack trace:

  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb614562e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
  #2  0xb6146332 in abort () from /lib/arm-linux-gnueabihf/libc.so.6
  #3  0xb6283120 in __gnu_cxx::__verbose_terminate_handler() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6281950 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #5  0xb62819a6 in std::terminate() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6281bc6 in __cxa_throw ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #7  0xb3d726ec in ?? () from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #8  0xb3d857f2 in 
mir::events::make_event(mir::IntWrapper const&, long long, std::string const&, std::string const&, std::string 
const&, std::string const&) ()
     from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #9  0xb3e3e5e2 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #10 0xb3e24d1e in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #11 0xb3e2aeb0 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #12 0xb3e26870 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #13 0xaa6476ce in qtmir::MirSurface::setKeymap(QString const&, QString const&)

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

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

[Touch-packages] [Bug 1660367] Re: App drawer doesn't dismiss on clicking the launcher unity8 zesty

Same for the BFB. I expect it to close the app drawer but it doesn't.

** Summary changed:

- app drawer doesn't dismiss on selecting active (or inactive) app from 
launcher unity8 zesty
+ App drawer doesn't dismiss on clicking the launcher unity8 zesty

** Summary changed:

- App drawer doesn't dismiss on clicking the launcher unity8 zesty
+ App drawer doesn't dismiss upon clicking the launcher in Unity8 zesty

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

Title:
  App drawer doesn't dismiss upon clicking the launcher in Unity8 zesty

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

Bug description:
  unsure if this is by design, but it doesn't "feel correct"

  on unity8(deb) zesty, installed the chrome-test snap
  launched chrome test along with terminal, hid chrome behind terminal
  moused over to reveal app drawer, selected chrome, which gained focus - but 
app drawer was still covering

  was able to repeat with unity-system-settings icon on launcher, u-s-s
  launched but drawer remained open.

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

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

[Touch-packages] [Bug 1670390] Re: Desktop applications don't get properly resized when launched in staged mode

** Changed in: canonical-devices-system-image
Milestone: None => u8c-1

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

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

Title:
  Desktop applications don't get properly resized when launched in
  staged mode

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

Bug description:
  Steps to reproduce the issue:

  1 - Put unity8 in staged mode
  2 - Launch a desktop application like kate or qtcreator

  Expected outcome:
  The launched application takes up the entire stage area

  Actual outcome:
  The launched application starts with some windowed size it wanted to have, 
not filling the entire stage area. As if launched in desktop mode.

  Comments:
  Leaving staged mode and going back into it again gets the application to 
resize correctly and fill the entire stage area.

  Going from desktop to staged mode while the desktop application is
  already running also works fine.

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

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

[Touch-packages] [Bug 1668825] Re: Sync pango1.0 1.40.4-1 (main) from Debian unstable (main)

2017-03-06 Thread Jeremy Bicha

** Changed in: pango1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync pango1.0 1.40.4-1 (main) from Debian unstable (main)

Status in pango1.0 package in Ubuntu:
  Fix Released

Bug description:
  Please sync pango1.0 1.40.4-1 (main) from Debian unstable (main)

  It's a new minimal bugfix release:
  https://git.gnome.org/browse/pango/tree/NEWS
  https://git.gnome.org/browse/pango/log

  Changelog entries since current zesty version 1.40.3-3:

  pango1.0 (1.40.4-1) unstable; urgency=medium

* New upstream release.
* Drop debian/patches/disable-layout-test.patch, no longer needed.
* Force update of pango-view.1.in to ensure it doesn't contain a dummy text.
  This requires a Build-Depends on help2man. (Closes: #774431)

   -- Michael Biebl   Tue, 28 Feb 2017 19:59:30 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1668825/+subscriptions

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

[Touch-packages] [Bug 1528735] Re: Suspend fails every second time on some laptops in UEFI mode

2017-03-06 Thread carloslp

It seems some hardware needs the OS to store/restore the NVS state when
entering/exiting S3 (suspend to ram).

On bug https://bugzilla.kernel.org/show_bug.cgi?id=189431 a quirk was
added to the Linux Kernel to do this for the Lenovo G50-45. If you have
a similar issue on hardware other than this Lenovo laptop please say
that on the previous linked kernel bug.

** Bug watch added: Linux Kernel Bug Tracker #189431
   http://bugzilla.kernel.org/show_bug.cgi?id=189431

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

Title:
  Suspend fails every second time on some laptops in UEFI mode

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
  Install detected UEFI, and installed in UEFI mode. (I have attempted
  to change to legacy boot, and got it to a state where it was booting
  without /sys/firmware/efi/ being present, but behaviour persisted.)

  Suspending the laptop, whether by closing the lid, choosing the
  suspend option from the menu, or directly typing "sudo pm-suspend"
  works perfectly well... once.

  The second attempt to suspend, whether immediately or hours later,
  suspends the laptop (I can see the screen turn off, and hear the disk
  and fans stop, but a moment later the screen shows bright yellow
  console text declaring "Warning!!! Boot script table modified!!!
  Please contact your vendor.", and then it hard reboots.

  This appears to be a weird interaction between suspend and UEFI
  protection, but others have reported that they have had working
  suspend when installed alone (and presumably in legacy from the
  start), but this behaviour appeared when reinstalled as dual-boot
  (when presumably UEFI would have had to be on).
  (http://askubuntu.com/questions/675683/suspend-does-not-work-more-
  than-once-after-reboot-ubuntu-15-04-dual-boot/712232 and earlier
  http://askubuntu.com/questions/651481/boot-script-table-modified-
  please-contact-vendor, from different people.)

  Beyond the investigations I have done, I know next to nothing about
  UEFI, or how Suspend might be interacting with it. Much less why it
  appears to work perfectly exactly once.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 23 13:27:11 2015
  InstallationDate: Installed on 2015-12-19 (3 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1528735/+subscriptions

-- 
Mailing list: https://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 1670567] [NEW] package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-03-06 Thread Ryan Tandy

Hello,

The log says that slapd failed to start, but not why.

Please could you check /var/log/syslog for messages emitted by slapd and 
paste them here.

Alternatively, start slapd in debug mode (-d):

/usr/sbin/slapd -h 'ldap:/// ldapi:///' -F /etc/ldap/slapd.d -u openldap
-g openldap -d1

and paste its output.

Thank you!

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

Title:
  package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openldap package in Ubuntu:
  New

Bug description:
  while installing ldap packages this issue is observed.

  sudo apt install slapd ldap-utils

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: slapd 2.4.31-1+nmu2ubuntu8.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Tue Mar  7 09:46:20 2017
  DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.3:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-18 (79 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: openldap
  Title: package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1670567] Re: package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openldap package in Ubuntu:
  New

Bug description:
  while installing ldap packages this issue is observed.

  sudo apt install slapd ldap-utils

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: slapd 2.4.31-1+nmu2ubuntu8.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Tue Mar  7 09:46:20 2017
  DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.3:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-18 (79 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: openldap
  Title: package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1161546] Re: Disabled accounts data appears in timeline

[Expired for Friends because there has been no activity for 60 days.]

** Changed in: friends
   Status: Incomplete => Expired

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

Title:
  Disabled accounts data appears in timeline

Status in Friends:
  Expired
Status in Gwibber:
  Invalid
Status in friends-app package in Ubuntu:
  Incomplete

Bug description:
  If you toggle off an online account, it doesn't remove posts from
  timeline

  To repeat:

  Add an online account, eg facebook
  Start gwibber
  --Timeline fills up with facebook posts
  Close gwibber
  Toggle account off in online accounts (both setting 'gwibber' to off, or 
turning off the entire account)
  gwibber still contains the previous data from the account

  EDIT: It appears that if I completely remove the account from online
  accounts the data is removed from gwibber.. Is this intended? If I
  disable an account I simply get no new data from the data source, and
  I must remove the account completely to remove the data? (If so, what
  about the other account integration points I may want to keep?)

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

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

[Touch-packages] [Bug 1670567] [NEW] package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-03-06 Thread Saikat Saha

Public bug reported:

while installing ldap packages this issue is observed.

sudo apt install slapd ldap-utils

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: slapd 2.4.31-1+nmu2ubuntu8.3
ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Tue Mar  7 09:46:20 2017
DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.3:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-12-18 (79 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: openldap
Title: package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openldap package in Ubuntu:
  New

Bug description:
  while installing ldap packages this issue is observed.

  sudo apt install slapd ldap-utils

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: slapd 2.4.31-1+nmu2ubuntu8.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Tue Mar  7 09:46:20 2017
  DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.3:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-18 (79 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: openldap
  Title: package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661836] Re: supertux 2 can't start with SDL_VIDEODRIVER=mir [Couldn't initialize SDL: Failed to connect to the mir server]

Sounds like this is just an (un)lucky case for bug 1605478. Sometimes it won't 
crash if you're either:
   (a) lucky enough to have a memory state that doesn't segfault; or
   (b) running an X server somewhere else on the system.

In that case I would expect the Mir connection to fail with some error
message. But it could still be bug 1605478 that's the root cause.

Let's get a fix for bug 1605478 released first then see if this one
persists.

** Changed in: canonical-devices-system-image
   Status: New => Incomplete

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

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

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

Title:
  supertux 2 can't start with SDL_VIDEODRIVER=mir [Couldn't initialize
  SDL: Failed to connect to the mir server]

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Invalid
Status in libsdl2 package in Ubuntu:
  Incomplete
Status in supertux package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  17.04 / unity8 session

  from what i understand this is an SDL2 app and should work on unity8,
  it did before

  $ journalctl --user-unit 
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service
  -- Logs begin at Sat 2017-02-04 14:24:38 EET, end at Sat 2017-02-04 14:55:01 
EET. --
  Feb 04 14:53:00 pixel-desktop systemd[3969]: Starting 
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service...
  Feb 04 14:53:01 pixel-desktop supertux2[8395]: [2017-02-04 14:53:01.377093] 
 MirConnectionAPI: Caught exception at client library boundary (in 
mir_connection_release): /build/mir-1Sl_GZ/mir-0.26.0
  Feb 04 14:53:01 pixel-desktop supertux2[8395]: Dynamic exception type: 
boost::exception_detail::clone_impl
  Feb 04 14:53:01 pixel-desktop supertux2[8395]: std::exception::what: Failed 
to send message to server: Broken pipe
  Feb 04 14:53:01 pixel-desktop supertux2[8395]: [boost::errinfo_errno_*] = 32, 
"Broken pipe"
  Feb 04 14:53:01 pixel-desktop supertux2[8395]: [FATAL] 
/build/supertux-LmXSob/supertux-0.5.1/src/supertux/main.cpp:510 Unexpected 
exception: Couldn't initialize SDL: Failed to connect to the mir server:
  Feb 04 14:53:01 pixel-desktop systemd[3969]: 
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service: Main 
process exited, code=exited, status=1/FAILURE
  Feb 04 14:53:01 pixel-desktop systemd[3969]: Failed to start 
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service.
  Feb 04 14:53:01 pixel-desktop systemd[3969]: 
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service: Unit 
entered failed state.
  Feb 04 14:53:01 pixel-desktop systemd[3969]: 
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service: Failed 
with result 'exit-code'.

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

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

[Touch-packages] [Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported

2017-03-06 Thread Chris Glass

More investigation is needed. The path *does* fix the problem, but in a
way that feels like it is a side effect.

Sorry, I should have commented on this bug before.

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

Title:
  dpkg-reconfigure unattended-upgrades results in update-rc.d warning
  that start and stop actions are no longer supported

Status in One Hundred Papercuts:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to script a change to the automatic updating of servers,
  and tried the following:

  echo "debconf unattended-upgrades/enable_auto_updates boolean false" | 
debconf-set-selections -
  dpkg-reconfigure -fnoninteractive unattended-upgrades

  The result, however, is a warning message:

  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

  At this point, the change I tried to make seems to be lost. To show
  this in an expanded sequence:

  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: true
  root@brennan:/home/ubuntu# echo "debconf 
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections 
-
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: false
  root@brennan:/home/ubuntu# dpkg-reconfigure -fnoninteractive 
unattended-upgrades
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/enable_auto_updates: true
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";

  If I omit the "-fnoninteractive" option to dpkg-reconfigure, I still
  get the warning message, but the change IS accepted and takes effect.
  Of course, this isn't useful in a script that should be run non-
  interactively. I've tried the equivalent commands to reconfigure other
  packages, and they work without error message, so I believe the
  problem is with unattended-upgrades, not with debconf/dpkg-
  reconfigure.

  This problem affects Ubuntu 16.04.1 (and probably 16.04 GA, but I've
  not tested it). It works as expected with Ubuntu 14.04. (That version,
  of course, defeaults to "false" for the unattended-
  upgrades/enable_auto_updates value. I've tested both with the default
  "false" value and after changing it to "true," with successful runs
  both times.)

  Version information, as requested:

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

  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90
Version table:
   *** 0.90 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy debconf
  debconf:
Installed: 1.5.58ubuntu1
Candidate: 1.5.58ubuntu1
Version table:
   *** 1.5.58ubuntu1 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1670390] Re: Desktop applications don't get properly resized when launched in staged mode

This sounds like bug 1655804. It may require the same kind of fix: The
toolkit needs to register its Mir event callback in the spec prior to
window creation to support Unity8 behaviour.

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

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

** Tags added: unity8-desktop

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

Title:
  Desktop applications don't get properly resized when launched in
  staged mode

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

Bug description:
  Steps to reproduce the issue:

  1 - Put unity8 in staged mode
  2 - Launch a desktop application like kate or qtcreator

  Expected outcome:
  The launched application takes up the entire stage area

  Actual outcome:
  The launched application starts with some windowed size it wanted to have, 
not filling the entire stage area. As if launched in desktop mode.

  Comments:
  Leaving staged mode and going back into it again gets the application to 
resize correctly and fill the entire stage area.

  Going from desktop to staged mode while the desktop application is
  already running also works fine.

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

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

[Touch-packages] [Bug 1670290] modified.conffile..etc.systemd.system.conf.txt

apport information

** Attachment added: "modified.conffile..etc.systemd.system.conf.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832665/+files/modified.conffile..etc.systemd.system.conf.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

[Touch-packages] [Bug 1670290] Re: Ubuntu can't suspend anymore after very recent update

apport-collect kept throwing exceptions and errors, took me about 5
times to get it right.

anyways it showed me a message that "I've modified systemd" & it said it
would include it in the report. But note that I didn't do anything to
systemd. Not "me", maybe something I installed.

Is the information sufficient? Anything else I need to provide? thx
Brian

how do we mention people here? XD

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Touch-packages] [Bug 1669819] Re: [unity8] Strange behavior when maximizing snapped windows

** Summary changed:

- [unity8] strange behavior  when maximizing snaped windows
+ [unity8] Strange behavior when maximizing snapped windows

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

Title:
  [unity8] Strange behavior when maximizing snapped windows

Status in Canonical System Image:
  Triaged
Status in Ubuntu UX:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 17.04 Unity8

  open random app (terminal app), snap it randomly on the screen (right
  buttom corner) by draging the app by the title bar (see screenshot1).
  now click on maximize window, the window almost leaves the screen
  (screenshot2).

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

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

[Touch-packages] [Bug 1669988] Re: [Xmir] full screen doesn't work

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

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


** This bug has been marked a duplicate of bug 1618712
   Xmir: Fullscreen apps never go full screen

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

Title:
  [Xmir] full screen doesn't work

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity8
  [Xmir] full screen doesn't work

  launch supertux2 on Xmir, go to Settings/Full screen. doesn't seem to
  work

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

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

[Touch-packages] [Bug 1668429] Re: X apps (LibreOffice, Thunderbird) fail to launch with failure to open display (no Xmir is running)

If we could get a fix for bug 1577641 then this would be easy to solve
(in the most efficient way): Just start an 'Xmir -rootless ...' at
login.

That way you don't need custom launcher magic for every X app to start
an X server.

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

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

Title:
  X apps (LibreOffice, Thunderbird) fail to launch with failure to open
  display (no Xmir is running)

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in libertine package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Feb 27 iso build of zesty, clean u8 exploration

  repro:
  1) open app drawer, find the thunderbird app
  2) click on icon to launch
  3) window closes immediately

  not a very useful journal log
  http://pastebin.ubuntu.com/24080860/

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

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

[Touch-packages] [Bug 1670290] SystemdFailedUnits.txt

apport information

** Attachment added: "SystemdFailedUnits.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832663/+files/SystemdFailedUnits.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage

[Touch-packages] [Bug 1670290] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832660/+files/ProcEnviron.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications

[Touch-packages] [Bug 1670290] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832662/+files/ProcModules.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications

[Touch-packages] [Bug 1670290] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1670290/+attachment/4832664/+files/UdevDb.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications about this

[Touch-packages] [Bug 1670290] modified.conffile..etc.systemd.system.conf.txt

apport information

** Attachment added: "modified.conffile..etc.systemd.system.conf.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832654/+files/modified.conffile..etc.systemd.system.conf.txt

** Description changed:

  Earlier today after update Ubuntu can't suspend.
  
  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.
  
  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.
  
  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.5
+ Architecture: amd64
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-09-29 (158 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
+  Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: HP HP ENVY x360 Convertible
+ Package: systemd 229-4ubuntu16
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
+ ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
+ SystemdDelta:
+  [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
+  [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
+  [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
+  
+  3 overridden configuration files found.
+ Tags:  xenial
+ Uname: Linux 4.4.0-64-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 12/07/2015
+ dmi.bios.vendor: Insyde
+ dmi.bios.version: F.19
+ dmi.board.asset.tag: Type2 - Board Asset Tag
+ dmi.board.name: 80D0
+ dmi.board.vendor: HP
+ dmi.board.version: 84.29
+ 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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
+ dmi.product.name: HP ENVY x360 Convertible
+ dmi.product.version: Type1ProductConfigId
+ dmi.sys.vendor: HP
+ mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

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

Title:
  Ubuntu can't suspend anymore after very recent update

[Touch-packages] [Bug 1670290] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832659/+files/ProcCpuinfo.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications

[Touch-packages] [Bug 1670290] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1670290/+attachment/4832658/+files/Lspci.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications about this bug

[Touch-packages] [Bug 1670290] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832649/+files/ProcEnviron.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications

[Touch-packages] [Bug 1670290] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832655/+files/CurrentDmesg.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications

[Touch-packages] [Bug 1670290] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832657/+files/JournalErrors.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage

[Touch-packages] [Bug 1670290] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832656/+files/Dependencies.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications

[Touch-packages] [Bug 1670290] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832646/+files/JournalErrors.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage

[Touch-packages] [Bug 1670290] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832645/+files/Dependencies.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications

[Touch-packages] [Bug 1670290] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1670290/+attachment/4832647/+files/Lspci.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications about this bug

[Touch-packages] [Bug 1670290] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832648/+files/ProcCpuinfo.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications

[Touch-packages] [Bug 1670290] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832651/+files/ProcModules.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications

[Touch-packages] [Bug 1670290] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1670290/+attachment/4832653/+files/UdevDb.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications about this

[Touch-packages] [Bug 1670290] SystemdFailedUnits.txt

apport information

** Attachment added: "SystemdFailedUnits.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832652/+files/SystemdFailedUnits.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage

[Touch-packages] [Bug 1670290] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832650/+files/ProcInterrupts.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage

[Touch-packages] [Bug 1670290] Re: Ubuntu can't suspend anymore after very recent update

apport information

** Tags added: apport-collected xenial

** Description changed:

  Earlier today after update Ubuntu can't suspend.
  
  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.
  
  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.
  
  Laptop is Hp Envy x360
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.5
+ Architecture: amd64
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-09-29 (158 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
+  Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: HP HP ENVY x360 Convertible
+ Package: systemd 229-4ubuntu16
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
+ ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
+ SystemdDelta:
+  [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
+  [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
+  [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
+  
+  3 overridden configuration files found.
+ Tags:  xenial
+ Uname: Linux 4.4.0-64-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 12/07/2015
+ dmi.bios.vendor: Insyde
+ dmi.bios.version: F.19
+ dmi.board.asset.tag: Type2 - Board Asset Tag
+ dmi.board.name: 80D0
+ dmi.board.vendor: HP
+ dmi.board.version: 84.29
+ 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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
+ dmi.product.name: HP ENVY x360 Convertible
+ dmi.product.version: Type1ProductConfigId
+ dmi.sys.vendor: HP
+ mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1670290/+attachment/4832644/+files/CurrentDmesg.txt

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29

[Touch-packages] [Bug 1577641] Re: Unity8 creates a blank black window for windowless apps

I don't think a utilities socket is a useful solution.

Mir apps need to discover their socket automatically. libmirclient does
not know or care about the difference between an app and a utility.
There is only one default Mir socket it can find automatically, and only
one Mir socket for Unity8.

Secondly, the utility idea only solves it for utilities like mirout and
media-hub. We also have the same problem with actual apps where 'Xmir
-rootless' is running for some time before the app exists. It should not
be given a window until the X app creates one. Fixing this bug may also
be a prerequisite for bug 1668429 if we need 'Xmir -rootless' running in
advance.

I understand the original motivation for the splash screen, but we need
to move out of it. Apps should launch faster so it's a non-issue. Or at
least desktop mode should not show splash screens since slow launching
is really more of a mobile problem.

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

Title:
  Unity8 creates a blank black window for windowless apps

Status in Canonical System Image:
  Won't Fix
Status in Mir:
  Invalid
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  Unity8 creates a blank black window for windowless apps.

  Windowless apps are closer thank you think:   Xmir -rootless
  is one such example while no X apps have started yet.

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

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

[Touch-packages] [Bug 1656727] Re: Unity8 crashes and restarts when clicking on a menu [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

Sorry, both statements are true.

Aisleriot may well be fixed but the underlying Mir server crash remains.
I logged that more recently as bug 1668466 that should stay open.

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

Title:
  Unity8 crashes and restarts when clicking on a menu [terminate called
  after throwing an instance of 'std::out_of_range' what():  map::at]

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Invalid
Status in MirAL:
  Invalid
Status in QtMir:
  Fix Released
Status in miral package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Unity8 crashes and restarts when clicking on a menu:

  terminate called after throwing an instance of 'std::out_of_range'
    what():  map::at

  Test case:
    1. Launch AisleRiot
    2. Click on a menu

  Expected: Menu opens
  Observed: Unity8 crashes and restarts every time

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170110.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  Date: Mon Jan 16 10:29:08 2017
  InstallationDate: Installed on 2016-11-03 (74 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2017-03-06 Thread Sledgez

Still doesn't work

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1670545] [NEW] package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-03-06 Thread Phil Sutter

Public bug reported:

failure during auto update from 14.04 to 16.04.2

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initscripts 2.88dsf-59.3ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
Date: Mon Mar  6 07:30:28 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-08-04 (580 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: sysvinit
Title: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-03-06 (0 days ago)
modified.conffile..etc.init.d.rc.local: [deleted]

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

Title:
  package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  New

Bug description:
  failure during auto update from 14.04 to 16.04.2

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initscripts 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Mon Mar  6 07:30:28 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-08-04 (580 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-03-06 (0 days ago)
  modified.conffile..etc.init.d.rc.local: [deleted]

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

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

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

2017-03-06 Thread Carl Mueller

Suspend fixes problem for me. Dell Precision 5520.

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

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

Status in alsa-driver package in Ubuntu:
Confirmed

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1612917] Re: Parts of words are hidden in Thunderbird

2017-03-06 Thread Vej

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

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

** No longer affects: thunderbird (Ubuntu)

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=88584
   Importance: Unknown
   Status: Unknown

** This bug has been marked a duplicate of bug 1515539
   letters stop being displayed

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

Title:
  Parts of words are hidden in Thunderbird

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  Some parts of words are hidden in Thunderbird on KDE desktop, after
  kwin crash. See Screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: thunderbird 1:45.2.0+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  smihael1537 F pulseaudio
  BuildID: 20160704153737
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sat Aug 13 09:52:19 2016
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Deutsch (DE) Language Pack - langpack...@thunderbird.mozilla.org
   Slovenski jezik Language Pack - langpack...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-04-27 (107 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev enx9cebe809b3e9  proto static  metric 100 
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.1.0/24 dev enx9cebe809b3e9  proto kernel  scope link  src 
192.168.1.14  metric 100 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.13  
metric 600
  MostRecentCrashID: bp-7ee352e8-a9ee-45ce-8043-26eed2160718
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=45.2.0/20160704153737 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-7ee352e8-a9ee-45ce-8043-26eed2160718
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1612917/+subscriptions

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

[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules

2017-03-06 Thread Brian Murray

** Tags added: rls-z-incoming

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

Title:
  udevadm trigger subsystem-match=net doesn't always run rules

Status in systemd package in Ubuntu:
  New

Bug description:
  1. root@ubuntu:~# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04

  2. root@ubuntu:~# apt-cache policy udev
  udev:
    Installed: 232-18ubuntu1
    Candidate: 232-18ubuntu1
    Version table:
   *** 232-18ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  3. udevadm trigger --verbose --subsystem-match=net --action=add will run and 
read .link files from /run/systemd/network/10-netplan-interface1.link
  and apply MTU settings

  4. during system boot running (3) does not set the MTU; running (3)
  after boot has completed MTU is set correctly.

  Here'a log during boot where cloud-init generates a netplan config,
  invokes `netplan generate` which writes the networkd config out 
  and then udevadm trigger (3).  Upon logging in interface1 has an MTU of 1500. 
 Re-running udevadm trigger now runs the rules/link files and updates the MTU.

  Note that, if you run udevadm test /sys/class/net/interface1; this also will
  apply the MTU (test probably shouldn't change the interface, I'll file a
  bug for that as well).

  # journalctl -o short-precise --no-pager -b | grep WARK
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 
'generate']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', 
'--no-block', 'systemd-udev-trigger.service']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', 
'--verbose', '--subsystem-match=net', '--action=add']:

  root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link
  [Match]
  MACAddress=52:54:00:12:34:02

  [Link]
  Name=interface1
  WakeOnLan=off
  MTUBytes=1492

  root@ubuntu:~# ifconfig interface1
  interface1: flags=4163  mtu 1500
  inet 10.0.2.100  netmask 255.255.255.0  broadcast 10.0.2.255
  inet6 fe80::5054:ff:fe12:3402  prefixlen 64  scopeid 0x20
  inet6 fec0::5054:ff:fe12:3402  prefixlen 64  scopeid 0x40
  ether 52:54:00:12:34:02  txqueuelen 1000  (Ethernet)
  RX packets 16  bytes 5053 (5.0 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 35  bytes 3287 (3.2 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ubuntu:~# udevadm trigger --verbose --subsystem-match=net --action=add
  /sys/devices/pci:00/:00:04.0/virtio1/net/interface1
  /sys/devices/pci:00/:00:05.0/virtio2/net/interface2
    ys/devices/pci:00/:00:06.0/virtio3/net/interface0
  /sys/devices/virtual/net/lo

  root@ubuntu:~# ifconfig interface1
  interface1: flags=4163  mtu 1492
  inet 10.0.2.100  netmask 255.255.255.0  broadcast 10.0.2.255
  inet6 fe80::5054:ff:fe12:3402  prefixlen 64  scopeid 0x20
  inet6 fec0::5054:ff:fe12:3402  prefixlen 64  scopeid 0x40
  ether 52:54:00:12:34:02  txqueuelen 1000  (Ethernet)
  RX packets 16  bytes 5053 (5.0 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 37  bytes 3504 (3.5 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: udev 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Thu Mar  2 19:22:14 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=8bbb84fe-91e8-4a9a-bd91-f6af4793727e ro console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.1-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-zesty
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-zesty:cvnQEMU:ct1:cvrpc-i440fx-zesty:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-zesty
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:

[Touch-packages] [Bug 1670290] Re: Ubuntu can't suspend anymore after very recent update

2017-03-06 Thread Brian Murray

It'd be helpful to know what release of Ubuntu you are running along
with things like the version of systemd.  Please run apport-collect
1670290 in a terminal so that information can be added automatically.

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

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360

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

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

[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist

2017-03-06 Thread Jon Grimm

>From upstream:

https://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=b08b5ff128874f94a1bc9dd8e178fa0e57c11c61

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

Title:
  The tc man page references tc-index man page but tc-index man page
  does not exist

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  New
Status in iproute2 source package in Yakkety:
  New

Bug description:
  The tc man page references tc-index man page but tc-index man page
  does not exist.

  The tc-index man page is incorrectly named tcindex.

  This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2

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

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

[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist

2017-03-06 Thread Jon Grimm

Low hanging fruit, I can probably get to this week; but feel free to
poke me if anyone else wants it.

** Changed in: iproute2 (Ubuntu Xenial)
 Assignee: (unassigned) => Jon Grimm (jgrimm)

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

Title:
  The tc man page references tc-index man page but tc-index man page
  does not exist

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  New
Status in iproute2 source package in Yakkety:
  New

Bug description:
  The tc man page references tc-index man page but tc-index man page
  does not exist.

  The tc-index man page is incorrectly named tcindex.

  This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2

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

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

[Touch-packages] [Bug 1670507] [NEW] why is hud-service using so much memory?

2017-03-06 Thread Seth Arnold

Public bug reported:

When inspecting why my computer was sluggish I found hud-service using a
lot of memory:


  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
 3142 sarnold   20   0 1208.1m 515.9m   9.9m S   0.0  3.3   1:44.69 hud-service


Why are menus I never use taking over five hundred megabytes of my memory and 
so much CPU time?

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: hud 14.10+16.04.20160415-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar  6 14:43:07 2017
InstallationDate: Installed on 2012-10-18 (1600 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
SourcePackage: hud
UpgradeStatus: Upgraded to xenial on 2016-04-30 (310 days ago)
upstart.hud.log: [31mvoid 
DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)[0m: "No such 
interface 'com.canonical.dbusmenu' on object at path 
/org/ayatana/bamf/window/44040199"

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


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

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

Title:
  why is hud-service using so much memory?

Status in hud package in Ubuntu:
  New

Bug description:
  When inspecting why my computer was sluggish I found hud-service using
  a lot of memory:

  
PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
   3142 sarnold   20   0 1208.1m 515.9m   9.9m S   0.0  3.3   1:44.69 
hud-service

  
  Why are menus I never use taking over five hundred megabytes of my memory and 
so much CPU time?

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  6 14:43:07 2017
  InstallationDate: Installed on 2012-10-18 (1600 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: hud
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (310 days ago)
  upstart.hud.log: [31mvoid 
DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)[0m: "No such 
interface 'com.canonical.dbusmenu' on object at path 
/org/ayatana/bamf/window/44040199"

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

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

[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist

2017-03-06 Thread Nish Aravamudan

@hjd I'm not sure where you verified that this is still a problem in
17.04. The web page seems to be a regularly-generated thing and I don't
believe it's reliable to use during a development release.

In an actual 17.04 environment, `man tc` refers to `man tc-tcindex`,
which does exist. Presumably an upstream fix needs to be backported to
16.04 and 16.10.

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

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

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

** Tags removed: zesty
** Tags added: bitesize

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

Title:
  The tc man page references tc-index man page but tc-index man page
  does not exist

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  New
Status in iproute2 source package in Yakkety:
  New

Bug description:
  The tc man page references tc-index man page but tc-index man page
  does not exist.

  The tc-index man page is incorrectly named tcindex.

  This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2

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

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

[Touch-packages] [Bug 1670383] Re: OSK doesn't work in unity8-greeter

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  OSK doesn't work in unity8-greeter

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  With silo https://bileto.ubuntu.com/#/ticket/2481 we get a better OSK
  experience on desktops.

  Unfortunately with unity8-greeter maliit isn't started in the
  lightdm/greeter session, nor can I see the keyboard switch or button
  in the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8-greeter 8.15+17.04.20170303.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar  6 15:53:31 2017
  InstallationDate: Installed on 2016-05-06 (303 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (104 days ago)

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

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

[Touch-packages] [Bug 1667928] Re: app drawer, Select All Paste menu (wrong z ordering) it is above the mouse pointer

2017-03-06 Thread Lukáš Tinkl

** Branch linked: lp:~lukas-kde/unity8/reparent-cursor

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

Title:
  app drawer, Select All  Paste menu (wrong z ordering) it is above the
  mouse pointer

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

Bug description:
  ubuntu 17.04 unit8
  app drawer, Select All  Paste menu (wrong z ordering) it is above the mouse 
pointer

  open the app drawer, right click in the Search, move the mouse pointer
  to the opened menu

  see attached screenshot

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

-- 
Mailing list: https://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 1668724] Re: fails to mount cgroupfs inside containers running on 16.04

2017-03-06 Thread Serge Hallyn

Thanks for looking. I'll push that tonight.

  Original Message  
From: Cam Cope
Sent: Monday, March 6, 2017 3:50 PM
To: serge.hal...@gmail.com
Reply To: Bug 1668724
Subject: [Bug 1668724] Re: fails to mount cgroupfs inside containers running on 
16.04

LGTM

-- 
You received this bug notification because you are subscribed to cgroup-
lite in Ubuntu.
Matching subscriptions: cgroup-lite
https://bugs.launchpad.net/bugs/1668724

Title:
fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
Fix Released
Status in cgroup-lite source package in Precise:
New
Status in cgroup-lite source package in Trusty:
New
Status in cgroup-lite source package in Xenial:
New
Status in cgroup-lite source package in Yakkety:
New

Bug description:
I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
and have noticed that the cgroups-mount script for mounting the
cgroups inside the containers has stopped working. This is because
systemd now comounts multiple controllers on a single hierarchy, which
prevents mounting them individually inside the container.

=== SRU Justification 
Impact: nested containers fail to start
Reproduce: create a root owned container; install lxc and cgroup-lite; create a 
container, and try to start it. Starting will fail if cgroup-lite is running in 
the first level container without this patch.
Regression potential: should be low, it's possible that the regexp is simply 
wrong for some cases.
===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+subscriptions

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

Title:
  fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in cgroup-lite source package in Precise:
  New
Status in cgroup-lite source package in Trusty:
  New
Status in cgroup-lite source package in Xenial:
  New
Status in cgroup-lite source package in Yakkety:
  New

Bug description:
  I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
  and have noticed that the cgroups-mount script for mounting the
  cgroups inside the containers has stopped working. This is because
  systemd now comounts multiple controllers on a single hierarchy, which
  prevents mounting them individually inside the container.

  ===  SRU Justification 
  Impact: nested containers fail to start
  Reproduce:  create a root owned container;  install lxc and cgroup-lite;  
create a container, and try to start it.  Starting will fail if cgroup-lite is 
running in the first level container without this patch.
  Regression potential:  should be low, it's possible that the regexp is simply 
wrong for some cases.
  ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+subscriptions

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

[Touch-packages] [Bug 1669643] Re: Wifi WPA2-PSK 4-Way Handshake Faliure

2017-03-06 Thread Adrian Vovk

Seriously I really need help with this issue I cannot use my home WiFi
without a slow Bluetooth tether. It's been days and nobody has noticed
anything. Somebody please help?

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

Title:
  Wifi WPA2-PSK 4-Way Handshake Faliure

Status in network-manager package in Ubuntu:
  New

Bug description:
  After I upgraded to Ubuntu 17.04 yesterday, I started having this
  problem. My device will only connect to unsecured (public) WiFi
  networks. I tried booting into an older series kernel (4.8.0) and the
  issue persisted.

  I ran `sudo systemctl status network-manager` and got this:

  device (wlx501ac505fcbc): supplicant interface state: associating -> 4-way 
handshake
  sup-iface[0x55eb41e5bc20,wlx501ac505fcbc]: connection disconnected (reason 15)
  device (wlx501ac505fcbc): supplicant interface state: 4-way handshake -> 
disconnected
  device (wlx501ac505fcbc): Activation: (wifi) disconnected during association, 
asking for new key
  device (wlx501ac505fcbc): state change: config -> need-auth (reason 
'supplicant-disconnect') [50 60 8]
  device (wlx501ac505fcbc): supplicant interface state: disconnected -> inactive

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  2 20:55:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-04 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  IpRoute:
   default via 192.168.42.129 dev enp0s20u2 proto static metric 100 
   169.254.0.0/16 dev enp0s20u2 scope link metric 1000 
   192.168.42.0/24 dev enp0s20u2 proto kernel scope link src 192.168.42.246 
metric 100
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  ProcEnviron:
   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  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   enp0s20u2  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/4  Wired connection 1  
474aac38-e4d8-4102-b2eb-c5cc6bdb17aa  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   AC:37:43:7C:B4:57  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   wlx501ac505fcbcwifi  disconnected  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1437229] Re: There should be an option in the language settings to switch off Auto corrections (without going to the System Settings)

2017-03-06 Thread Michael Rowland Hunter

** Summary changed:

- There should be an option in the language settings to switch of Auto 
corrections (without going to the System Settings)
+ There should be an option in the language settings to switch off Auto 
corrections (without going to the System Settings)

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

Title:
  There should be an option in the language settings to switch off Auto
  corrections (without going to the System Settings)

Status in ubuntu-keyboard:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  The autocorretion ist very helfull if you write things properly in a
  language but if you want to use a dialect or abbreveations like "Can u
  go 2 the superM?" (There are better examples in Austrian dialects) it
  would be better to have the auto correction switched off.

  The way through the System Settings is a very long one to achieve the
  wished behaviour.

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

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

[Touch-packages] [Bug 1670494] [NEW] 'wpa_supplicant -D nl80211 -W' hangs with some Intel cards

2017-03-06 Thread Paul Donohue

Public bug reported:

init_wpa_supplicant() in /etc/wpa_supplicant/functions.sh runs
wpa_supplicant with the -W option, which causes it to wait for wpa_cli
to attach.  init_wpa_supplicant() then attaches wpa_cli to
wpa_supplicant.

When the nl80211 driver is used with some Intel cards, wpa_supplicant
automatically defines a second p2p_dev_${WPA_IFACE} interface.  If
multiple interfaces are defined in wpa_supplicant, then wpa_supplicant
will wait for multiple wpa_cli instances to attach.  Since
init_wpa_supplicant() only attaches a single wpa_cli process, this
causes wpa_supplicant to hang, which ultimately leads to a timeout and
causes interface configuration to fail.

This has been fixed upstream: 
http://lists.infradead.org/pipermail/hostap/2015-December/034410.html
And also in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833402

However, the updated wpa_supplicant has not made it to Ubuntu (not even
Zesty), and the "-m ''" workaround mentioned in the mailing list thread
associated with the upstream fix does not work with the version of
wpa_supplicant that comes with Ubuntu.

Could the P2P patches that were merged into Debian be merged into
Ubuntu?

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

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

Title:
  'wpa_supplicant -D nl80211 -W' hangs with some Intel cards

Status in wpa package in Ubuntu:
  New

Bug description:
  init_wpa_supplicant() in /etc/wpa_supplicant/functions.sh runs
  wpa_supplicant with the -W option, which causes it to wait for wpa_cli
  to attach.  init_wpa_supplicant() then attaches wpa_cli to
  wpa_supplicant.

  When the nl80211 driver is used with some Intel cards, wpa_supplicant
  automatically defines a second p2p_dev_${WPA_IFACE} interface.  If
  multiple interfaces are defined in wpa_supplicant, then wpa_supplicant
  will wait for multiple wpa_cli instances to attach.  Since
  init_wpa_supplicant() only attaches a single wpa_cli process, this
  causes wpa_supplicant to hang, which ultimately leads to a timeout and
  causes interface configuration to fail.

  This has been fixed upstream: 
http://lists.infradead.org/pipermail/hostap/2015-December/034410.html
  And also in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833402

  However, the updated wpa_supplicant has not made it to Ubuntu (not
  even Zesty), and the "-m ''" workaround mentioned in the mailing list
  thread associated with the upstream fix does not work with the version
  of wpa_supplicant that comes with Ubuntu.

  Could the P2P patches that were merged into Debian be merged into
  Ubuntu?

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

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

[Touch-packages] [Bug 1642078] Re: Black screen at startup on Carrizo

2017-03-06 Thread Evren Yurtesen

Are you sure the black screens are your only problem?

I have problems with keyboard missing keypresses, touchpad doing strange
stuff, hard drive performance, random crashes and caps-lock blinks, wifi
required driver from github and manual setting of antenna. I ran
sysbench and disk was performing at about 1.3mb/s speed only! There was
at least 1 other person who wrote to my bug report that he was having
the same problems.

With 4.8 hwe kernel, it does not even boot anymore. Looking at all the
bug reports, the problems seem to be only getting worse and worse with
updates. It is almost like linux is trying to irradicate AMD machines...

Here is my bug report for the hard drive performance, are you able to replicate 
it?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830

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

Title:
  Black screen at startup on Carrizo

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Problem description:
  The laptop starts up fine but the screen is black; even though the screen is 
black I can hear the drum sound prompting me to log in. After rebooting laptop 
all is well with the screen and I have a fully functional system. Sometimes, 
though, I have to restart twice.

  After some search I found people reporting the same issue:
  https://ubuntuforums.org/showthread.php?t=2337274

  or similar issues:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1577074?comments=all

  Additional information:

  1) Ubuntu release:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) Package version:
  xorg:
Instalados: 1:7.7+13ubuntu3
Candidato:  1:7.7+13ubuntu3
Tabla de versión:
   *** 1:7.7+13ubuntu3 500
  500 http://co.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Computer information:
  Processor: AMD A10-8700 Radeon R6
  Graphic card: Gallium 0.4 on AMD Carrizo (DRM 3.1.0, LLVM 3.8.0)

  Kind regards,
  Victor

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-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: Tue Nov 15 17:56:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Carrizo [103c:8246]
  InstallationDate: Installed on 2016-11-10 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.03
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8246
  dmi.board.vendor: HP
  dmi.board.version: 98.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.03:bd05/03/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn8246:rvr98.11:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  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.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Nov 15 17:21:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2
  xserver.video_driver: amdgpu

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

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

[Touch-packages] [Bug 1665359] Re: apport-gtk crashed with SIGABRT in g_assertion_message()

2017-03-06 Thread David Kastrup

** Information type changed from Private to Public

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

Title:
  apport-gtk crashed with SIGABRT in g_assertion_message()

Status in apport package in Ubuntu:
  New

Bug description:
  No further information available.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-lowlatency 4.9.5
  Uname: Linux 4.9.0-15-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Feb 16 14:46:52 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2011-10-14 (1952 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Signal: 6
  SourcePackage: apport
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to zesty on 2017-01-05 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1591137] Re: sudo ignores shortname aliases in sudoers file

2017-03-06 Thread Martin Fox

We are experiencing the same symptoms with sudo (v1.8.16) as have been 
previously reported in this bug.
 
On an Ubuntu 16.04 system short hostnames don't work in the sudoers file when 
the 'fqdn' option is true (as it is by default). The documentation indicates 
that the short form should still work with the fqdn option set.
 
Steps to reproduce:
 
On a system called 'ubuntu1604.example.com', put the following into sudoers:
 
%john ubuntu1604=(root) NOPASSWD: /bin/true
%john ubuntu1604.example.com=(root) NOPASSWD: /bin/false
 
Expected outcome:
 
sudo -l shows user 'john' is allowed to run:
 
(root) /bin/true
(root) /bin/false
 
Actual outcome:
 
sudo -l shows user 'john' is allowed to run:
 
(root) /bin/false
 
sudo -l -U john -h ubuntu1604 shows user 'john' is allowed to run:
 
(root) /bin/false
 
sudo -l -U test -h ubuntu1604.example.com shows user 'john' is allowed to run:
 
(root) /bin/true
(root) /bin/false


--
Sudo version 1.8.16
Configure options: --prefix=/usr -v --with-all-insults --with-pam --with-fqdn 
--with-logging=syslog --with-logfac=authpriv --with-env-editor 
--with-editor=/usr/bin/editor --with-exampledir=/usr/share/doc/sudo/examples 
--with-timeout=15 --with-password-timeout=0 --with-passprompt=[sudo] password 
for %p:  --without-lecture --with-tty-tickets --disable-root-mailer 
--enable-admin-flag --with-sendmail=/usr/sbin/sendmail 
--with-rundir=/var/run/sudo --mandir=/usr/share/man --libexecdir=/usr/lib/sudo 
--with-sssd --with-sssd-lib=/usr/lib/x86_64-linux-gnu --with-selinux 
--with-linux-audit
Sudoers policy plugin version 1.8.16

-

root@bs-ubuntu1604:~# uname -a
Linux bs-ubuntu1604 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

-

root@bs-ubuntu1604:~# cat /etc/hosts
127.0.0.1   localhost
127.0.1.1   bs-ubuntu1604.ethz.ch   bs-ubuntu1604

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
root@bs-ubuntu1604:~# hostname
bs-ubuntu1604

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

Title:
  sudo ignores shortname aliases in sudoers file

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Our sudoers file contains host aliases which all work fine on versions
  of Ubuntu < 16.04.

  On 16.04, it has become necessary to include the FQDN of the machine
  in order for sudo permissions to be granted. I have reproduced this
  problem on two cleanly-installed servers.

  
  i.e.

  This entry in /etc/sudoers does not work for members of sudo group:-

  %sudo   ourserver

  This entry in /etc/sudoers does work for members of sudo group:-

  %sudo   ourserver.our.domain

  
  Extra information which may be of interest:

  'hostname' returns the shortname on both Ub1604 and Ub1404
  installations

  
  /etc/hosts lists machines by fqdn and then shortname on both platforms, i.e.

  ip.ad.dr.esourserver.our.domain   ourserver

  
  /etc/resolv.conf is set to search our.domain, same on both platforms

  
  sudo package version is 1.8.16-0ubuntu1.1

  
  Bw
  John

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

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

[Touch-packages] [Bug 1668951] Re: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  Systempackage is corrupt

  1. 

  2. 

  3. Update

  4- 

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Wed Mar  1 12:00:25 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2013-09-01 (1276 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.1)
  Lpstat: device for MFC7360N: usb://Brother/MFC-7360N?serial=E69717J1N892883
  MachineType: Dell Inc. Inspiron One 2320
  Papersize: a4
  PpdFiles: MFC7360N: Brother MFC-7225N BR-Script3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f58ec9cd-7c26-49be-9698-46cb6bcfae59 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f58ec9cd-7c26-49be-9698-46cb6bcfae59 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-01-17 (43 days ago)
  dmi.bios.date: 09/17/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0JC4YH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: PRFirestone_P7PG1_A01.SDR
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd09/17/2012:svnDellInc.:pnInspironOne2320:pvr00:rvnDellInc.:rn0JC4YH:rvrA00:cvnDellInc.:ct13:cvrPRFirestone_P7PG1_A01.SDR:
  dmi.product.name: Inspiron One 2320
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-08-23T09:12:01.222658

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

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

[Touch-packages] [Bug 1670057] Re: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  cant do system/app upgrades

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: sudo 1.8.16-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Sat Mar  4 17:22:53 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-12-31 (63 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/50_prey_switcher: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1668741] Re: libcurl4-gnutls-dev:i386 and libcurl4-gnutls-dev:amd64 conflict on shared file '/usr/include/curl/curlbuild.h'

** Tags removed: need-duplicate-check

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

Title:
  libcurl4-gnutls-dev:i386 and libcurl4-gnutls-dev:amd64 conflict on
  shared file '/usr/include/curl/curlbuild.h'

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  libcurl4-gnutls-dev:i386 and libcurl4-gnutls-dev:amd64 can't be
  installed together because they both contain a file
  '/usr/include/curl/curlbuild.h' but it's different.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcurl4-gnutls-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   libcurl4-gnutls-dev: Install
   libcurl4-gnutls-dev: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Feb 28 20:54:17 2017
  DpkgTerminalLog:
   Preparing to unpack .../libcurl4-gnutls-dev_7.47.0-1ubuntu2.2_amd64.deb ...
   Unpacking libcurl4-gnutls-dev:amd64 (7.47.0-1ubuntu2.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcurl4-gnutls-dev_7.47.0-1ubuntu2.2_amd64.deb 
(--unpack):
trying to overwrite shared '/usr/include/curl/curlbuild.h', which is 
different from other instances of package libcurl4-gnutls-dev:amd64
  DuplicateSignature:
   package:libcurl4-gnutls-dev:(not installed)
   Unpacking libcurl4-gnutls-dev:amd64 (7.47.0-1ubuntu2.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcurl4-gnutls-dev_7.47.0-1ubuntu2.2_amd64.deb 
(--unpack):
trying to overwrite shared '/usr/include/curl/curlbuild.h', which is 
different from other instances of package libcurl4-gnutls-dev:amd64
  ErrorMessage: trying to overwrite shared '/usr/include/curl/curlbuild.h', 
which is different from other instances of package libcurl4-gnutls-dev:amd64
  InstallationDate: Installed on 2016-08-25 (187 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: curl
  Title: package libcurl4-gnutls-dev (not installed) failed to install/upgrade: 
trying to overwrite shared '/usr/include/curl/curlbuild.h', which is different 
from other instances of package libcurl4-gnutls-dev:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1669901] Re: unity8 dash crash - bad url

** Tags removed: need-duplicate-check

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

Title:
  unity8 dash crash - bad url

Status in unity8 package in Ubuntu:
  New

Bug description:
  unity8 dash crash - bad url

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170221-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  BadURL: 
appid://ubuntu-calculator-app/ubuntu-calculator-app/current-user-version
  CurrentDesktop: Unity:Unity8
  Date: Fri Mar  3 20:36:14 2017
  DuplicateSignature: /usr/bin/unity8-dash:url-dispatcher-bad-url
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2016-12-12 (81 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: unity8-dash --desktop_file_hint=unity8-dash.desktop
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1670131] Re: package ca-certificates 20160104ubuntu0.14.04.1 failed to install/upgrade: eindeloze triggerlus; afgebroken

** Tags removed: need-duplicate-check

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

Title:
  package ca-certificates 20160104ubuntu0.14.04.1 failed to
  install/upgrade: eindeloze triggerlus; afgebroken

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  during do-release-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Sun Mar  5 15:25:33 2017
  DuplicateSignature: package:ca-certificates:20160104ubuntu0.14.04.1:eindeloze 
triggerlus; afgebroken
  ErrorMessage: eindeloze triggerlus; afgebroken
  InstallationDate: Installed on 2016-11-02 (122 days ago)
  InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu0.14.04.1 failed to 
install/upgrade: eindeloze triggerlus; afgebroken
  UpgradeStatus: Upgraded to xenial on 2017-03-05 (0 days ago)

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

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

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

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

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 #1632415, 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 1632415
   package gconf2 3.2.6-3ubuntu7 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/1669632

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

Status in gconf package in Ubuntu:
  New

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

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Mar  2 20:56:22 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-04-10 (326 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-03-03 (0 days ago)

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

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

[Touch-packages] [Bug 1669250] Re: package apport 2.20.3-0ubuntu8 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package apport 2.20.3-0ubuntu8 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  anzhuangshibai

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: apport 2.20.3-0ubuntu8
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportLog:
   ERROR: apport (pid 4749) Thu Mar  2 11:10:01 2017: called for pid 4737, 
signal 11, core limit 0
   ERROR: apport (pid 4749) Thu Mar  2 11:10:01 2017: executable was modified 
after program start, ignoring
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashReports: 600:0:122:253095:2017-03-02 11:40:29.509586811 +0800:2017-03-02 
11:40:30.509586811 +0800:/var/crash/apport.0.crash
  Date: Thu Mar  2 11:40:29 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-03-01 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: apport
  Title: package apport 2.20.3-0ubuntu8 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1670383] Re: OSK doesn't work in unity8-greeter

2017-03-06 Thread Michael Terry

Quick update -- I've got some fixes to our greeter launch script that
let maliit-server run.  But OSK still isn't coming up.  Looking further.

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

Title:
  OSK doesn't work in unity8-greeter

Status in unity8 package in Ubuntu:
  New

Bug description:
  With silo https://bileto.ubuntu.com/#/ticket/2481 we get a better OSK
  experience on desktops.

  Unfortunately with unity8-greeter maliit isn't started in the
  lightdm/greeter session, nor can I see the keyboard switch or button
  in the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8-greeter 8.15+17.04.20170303.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar  6 15:53:31 2017
  InstallationDate: Installed on 2016-05-06 (303 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (104 days ago)

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

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

[Touch-packages] [Bug 1666059] Re: Main virtualbox window resizes itself 4 or 4 times - then no start

2017-03-06 Thread LocutusOfBorg

not sure if mesa has something to do here, because we are using ld to
override the ld.so.conf.d EGL and GL configuration files

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

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Main virtualbox window resizes itself 4 or 4 times - then no start

Status in mesa package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Install virtualbox from repo's.

  Install Xubuntu or Ubuntu

  Install virtulabox-guest-utils

  Reboot - virtual installation starts.

  Install virtualbox-guest-x11

  Reboot

  Virtual installation starts, see disk clean notice, window then
  resizes itself a few times - then cursor flashing but no login screen
  appears

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: virtualbox-guest-x11 5.1.14-dfsg-2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 19 20:34:16 2017
  InstallationDate: Installed on 2017-02-19 (0 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1666059] Re: Main virtualbox window resizes itself 4 or 4 times - then no start

2017-03-06 Thread LocutusOfBorg

putting xorg developers in the loop

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

Title:
  Main virtualbox window resizes itself 4 or 4 times - then no start

Status in mesa package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Install virtualbox from repo's.

  Install Xubuntu or Ubuntu

  Install virtulabox-guest-utils

  Reboot - virtual installation starts.

  Install virtualbox-guest-x11

  Reboot

  Virtual installation starts, see disk clean notice, window then
  resizes itself a few times - then cursor flashing but no login screen
  appears

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: virtualbox-guest-x11 5.1.14-dfsg-2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 19 20:34:16 2017
  InstallationDate: Installed on 2017-02-19 (0 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1648921] Re: Sandbox the tracker extractor

2017-03-06 Thread Jeremy Bicha

** Changed in: tracker (Ubuntu Yakkety)
   Status: Fix Committed => Won't Fix

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

Title:
  Sandbox the tracker extractor

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Xenial:
  Won't Fix
Status in tracker source package in Yakkety:
  Won't Fix

Bug description:
  * SECURITY UPDATE: extractor now runs in a sandbox confined by libseccomp
  - extractor's filesystem and network access is limited to being read and
    local only (LP: #1648921)
  - No CVE number

  The tracker developers have recently confined their extractor to
  attempt to make tracker more resilient to attacks, especially
  involving flaws in gstreamer parsers.

  There is no CVE number assigned to this issue.

  https://lwn.net/Articles/708196/
  
https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html

  The gstreamer security fixes are being handled separately. See bug
  1619600

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

2017-03-06 Thread Ryan Harper

For yakkety resolvconf update;  I've updated the SRU test-case to
include a more general netplan config for bringing up ethernet devices;
the previous version only worked on lxd (or instances with devices named
eth0).

With the above change; it looks like yakkety/zesty (due to running
systemd-resolved instead of resolvconf service) need an update to the
systemd-resolved service the instance is configured to use networkd
insteadof ifupdown to ensure that systemd-resolved runs *before*
network-online.target.

# diff -u systemd-resolved.service.orig systemd-resolv
--- systemd-resolved.service.orig   2017-03-06 19:37:44.206692449 +
+++ systemd-resolved.service2017-03-06 19:33:09.467080158 +
@@ -12,6 +12,7 @@
 
Documentation=http://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
 
Documentation=http://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
 After=systemd-networkd.service network.target
+Before=network-online.target
 
 # On kdbus systems we pull in the busname explicitly, because it
 # carries policy that allows the daemon to acquire its name.

This makes things more complicated for this SRU;  yakkety/zesty will
need an updated systemd; the resolvconf portion of this SRU (for
yakkety) is still OK but it's not sufficient to achieve the goal of
ensuring DNS is functional *before* we reach 'network-online.target'.

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in resolvconf source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in resolvconf source package in Yakkety:
  Fix Committed
Status in resolvconf package in Debian:
  Fix Committed

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  Test Case:
    lxc launch ubuntu-daily:xenial x1
    lxc exec x1 /bin/bash

    # make sure you're on systemd-229-4ubuntu17
    apt update && apt install -y systemd

    # enable networkd and netplan
    apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
  version: 2
  ethernets:
  all-en:
  match:
  name: "en*"
  dhcp4: true
  all-eth:
  match:
  name: "eth*"
  dhcp4: true
  EOF
    sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

    netplan generate

    # make sure cloud-init.service uses networkd
    sed -i.orig -e '/After=networking.service/a 
After=systemd-networkd-wait-online.service' 
/lib/systemd/system/cloud-init.service

    reboot

    # check that the order of execution with:
    journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

    # the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15

[Touch-packages] [Bug 1670442] Re: Improve splash screen behaviour

Sure, but it will resize to the right size once it knows it (even before
the application draws).

We could also give the ability to configure the preferred splash screen
size.

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

Title:
  Improve splash screen behaviour

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Related to bug #1577641, we may want to improve the way the splash
  screen logic is implemented.

  The shell-managed splash screens serve as a way to provide immediate
  feedback for an application being launched, so that the user doesn't
  need to find out whether they failed to launch the app or the app's
  just slow to launch (or maybe even crashed on startup).

  My proposal is that:
  - we delay showing the splash screen for a very short interval (50ms to start 
with?)
  - *if* the splash screen is shown, it has to be shown for at least a certain 
time (500ms?) to avoid "flicker" between the splash screen and the app surface
  - if possible, let the user know that the app crashed/exited with an error 
and give the user an option to restart or close (long-term maybe also report 
the issue?)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170303.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar  6 18:33:05 2017
  InstallationDate: Installed on 2016-05-06 (303 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (104 days ago)

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

2017-03-06 Thread Ryan Harper

** Description changed:

  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.
  
  This was discussed in https://launchpad.net/bugs/1636912 however it was
  not a regression since there aren't any users of networkd + DNS early in
  boot at this time, it was requested that we move this DNS issue to a
  separate bug.
  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.
  
  Regression potential: Low. networkd is not widely being used outside of
  netplan/snappy in xenial.
  
  Test Case:
    lxc launch ubuntu-daily:xenial x1
    lxc exec x1 /bin/bash
  
    # make sure you're on systemd-229-4ubuntu17
    apt update && apt install -y systemd
  
    # enable networkd and netplan
    apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
-   version: 2
-   ethernets:
- eth0:
-   dhcp4: true
+ version: 2
+ ethernets:
+ all-en:
+ match:
+ name: "en*"
+ dhcp4: true
+ all-eth:
+ match:
+ name: "eth*"
+ dhcp4: true
  EOF
    sed -i.orig -e 's/^source/# source/' /etc/network/interfaces
  
    netplan generate
  
    # make sure cloud-init.service uses networkd
    sed -i.orig -e '/After=networking.service/a 
After=systemd-networkd-wait-online.service' 
/lib/systemd/system/cloud-init.service
  
    reboot
  
    # check that the order of execution with:
    journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service
  
    # the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.
  
  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:
  
  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.
  
  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in resolvconf source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in resolvconf source package in Yakkety:
  Fix Committed
Status in resolvconf package in Debian:
  Fix Committed

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to

[Touch-packages] [Bug 1555904] Re: opal-prd not installed by default on ppc64el systems

2017-03-06 Thread Adam Conrad

** Package changed: ubuntu-meta (Ubuntu) => skiboot (Ubuntu)

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

Title:
  opal-prd not installed by default on ppc64el systems

Status in skiboot package in Ubuntu:
  New

Bug description:
  Just tried an install with current 16.04 network media, using standard
  server package selections, and it looks like opal-prd isn't installed
  by default:

   [jk@fstn ~]$ dpkg -l opal-prd
   dpkg-query: no packages found matching opal-prd

  This is required for RAS-type functions on OpenPOWER machines; and has
  a similar role to something like acpid, on x86.

  I'm not sure whether filing this against the skiboot package is best,
  or whether this should be moved to something installer-related. Happy
  to shift if necessary.

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

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

[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found

** Branch linked: lp:~osomon/apparmor/newer-nvidia-abstraction-trunk

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

Title:
  webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
  EGL configs found

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Invalid
Status in apparmor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  When trying to start webbrowser-app a unresponsive window appears and
  after a few moments it crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  8 22:56:35 2016
  InstallationDate: Installed on 2016-04-28 (41 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1670442] Re: Improve splash screen behaviour

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

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

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

Title:
  Improve splash screen behaviour

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Related to bug #1577641, we may want to improve the way the splash
  screen logic is implemented.

  The shell-managed splash screens serve as a way to provide immediate
  feedback for an application being launched, so that the user doesn't
  need to find out whether they failed to launch the app or the app's
  just slow to launch (or maybe even crashed on startup).

  My proposal is that:
  - we delay showing the splash screen for a very short interval (50ms to start 
with?)
  - *if* the splash screen is shown, it has to be shown for at least a certain 
time (500ms?) to avoid "flicker" between the splash screen and the app surface
  - if possible, let the user know that the app crashed/exited with an error 
and give the user an option to restart or close (long-term maybe also report 
the issue?)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170303.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar  6 18:33:05 2017
  InstallationDate: Installed on 2016-05-06 (303 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (104 days ago)

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

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

[Touch-packages] [Bug 1670442] Re: Improve splash screen behaviour

2017-03-06 Thread Daniel d'Andrada

The biggest problem with splash screens is on desktop: the first time an
application is launched Unity8 has no idea of its window constraints
(minimum, maximum and preferred sizes) so that it can choose an adequate
size for the splash screen.

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

Title:
  Improve splash screen behaviour

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Related to bug #1577641, we may want to improve the way the splash
  screen logic is implemented.

  The shell-managed splash screens serve as a way to provide immediate
  feedback for an application being launched, so that the user doesn't
  need to find out whether they failed to launch the app or the app's
  just slow to launch (or maybe even crashed on startup).

  My proposal is that:
  - we delay showing the splash screen for a very short interval (50ms to start 
with?)
  - *if* the splash screen is shown, it has to be shown for at least a certain 
time (500ms?) to avoid "flicker" between the splash screen and the app surface
  - if possible, let the user know that the app crashed/exited with an error 
and give the user an option to restart or close (long-term maybe also report 
the issue?)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170303.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar  6 18:33:05 2017
  InstallationDate: Installed on 2016-05-06 (303 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (104 days ago)

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

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

[Touch-packages] [Bug 1532855] Re: add-apt-repository exits with 0 even when adding key failed

This bug was fixed in the package software-properties - 0.96.24.11

---
software-properties (0.96.24.11) zesty; urgency=medium

  [Scott Moser]
  * debian/tests/run-tests: use gpg rather than gpg1, and show errors
(LP: #1670399)
  * debian/tests/control: add gnupg to list of dependencies.

  [Iain Lane]
  * softwareproperties/shortcuts.py: Make add_key() return True. Since r988,
the return value of add_key() is now used to raise an exception.
ShortcutHandler.add_key() always succeeds, so should return True. This
(LP: #1670399)

 -- Scott Moser   Mon, 06 Mar 2017 12:22:03 -0500

** Changed in: software-properties (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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1532855

Title:
  add-apt-repository exits with 0 even when adding key failed

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Confirmed
Status in software-properties source package in Yakkety:
  Confirmed

Bug description:
  add-apt-repository exits happily even if it failed adding the key:

  $ sudo env LANGUAGE=en add-apt-repository ppa:launchpad/buildd-staging -k 
hkp://bad-server/
   Buildd staging packages for Launchpad. New packages are staged here for 
testing on the staging PPA buildds.
   More info: https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging
  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keyring `/tmp/tmp3246v7n8/secring.gpg' created
  gpg: keyring `/tmp/tmp3246v7n8/pubring.gpg' created
  gpg: requesting key 0A5174AF from hkp server bad-server
  ?: bad-server: Host not found
  gpgkeys: HTTP fetch error 7: couldn't connect: Success
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  gpg: keyserver communications error: keyserver unreachable
  gpg: keyserver communications error: public key not found
  gpg: keyserver receive failed: public key not found

  $ echo $?
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.17
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 11 17:17:56 2016
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1532855/+subscriptions

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

[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found

** Branch linked: lp:~osomon/apparmor/newer-nvidia-abstraction

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

Title:
  webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
  EGL configs found

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Invalid
Status in apparmor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  When trying to start webbrowser-app a unresponsive window appears and
  after a few moments it crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  8 22:56:35 2016
  InstallationDate: Installed on 2016-04-28 (41 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1670385] Re: Add knowledge of openstack releases Pike and Queens

This bug was fixed in the package software-properties - 0.96.24.11

---
software-properties (0.96.24.11) zesty; urgency=medium

  [Scott Moser]
  * debian/tests/run-tests: use gpg rather than gpg1, and show errors
(LP: #1670399)
  * debian/tests/control: add gnupg to list of dependencies.

  [Iain Lane]
  * softwareproperties/shortcuts.py: Make add_key() return True. Since r988,
the return value of add_key() is now used to raise an exception.
ShortcutHandler.add_key() always succeeds, so should return True. This
(LP: #1670399)

 -- Scott Moser   Mon, 06 Mar 2017 12:22:03 -0500

** Changed in: software-properties (Ubuntu Zesty)
   Status: Confirmed => Fix Released

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

Title:
  Add knowledge of openstack releases Pike and Queens

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Confirmed
Status in software-properties source package in Yakkety:
  Confirmed
Status in software-properties source package in Zesty:
  Fix Released

Bug description:
  === Begin SRU Information ===
  [Impact]
  Software-properties knows about openstack releases so that the user can do
$ add-apt-repository cloud-archive/ocata

  The next 2 openstack releases are known already, so we might as well add
  them to software-properties.

  [Test case]
  sudo add-apt-repository cloud-archive:queens
  sudo add-apt-repository cloud-archive:queens-proposed
  sudo add-apt-repository cloud-archive:pike
  sudo add-apt-repository cloud-archive:pike-proposed

  There are no repositories on the other side of those commands at the
  moment, so an 'apt-get update' will not succeed, but when they are populated
  it will.

  [Regression Potential]
  As mentioned above, the repositories are not yet populated.
  So, the failure case is a bit different than it was before when
  add-apt-repositiry would just fail.  However, it could not have been expected
  to succeed in either case.

  [Other Info]
  This was originally requested by xnox in bug 1645827.
  But the SRU and upload to zesty went through, so I made another bug
  for this.
  === End SRU Information ===

  O

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1670385/+subscriptions

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

[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found

** Branch linked: lp:~osomon/webbrowser-app/apparmor-profile-ibus-nvidia

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

Title:
  webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
  EGL configs found

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Invalid
Status in apparmor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  When trying to start webbrowser-app a unresponsive window appears and
  after a few moments it crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  8 22:56:35 2016
  InstallationDate: Installed on 2016-04-28 (41 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1658239] Re: base abstraction missing glibc /proc/$pid/ things

2017-03-06 Thread Robie Basak

There are some reports of this affecting Xenial users with mysql-5.7.
See bug 1610765. I'm not sure how to reproduce though.

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

Title:
  base abstraction missing glibc /proc/$pid/ things

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.10 series:
  Fix Committed
Status in AppArmor 2.11 series:
  Fix Committed
Status in AppArmor 2.9 series:
  Fix Committed
Status in AppArmor master series:
  Fix Committed
Status in apparmor package in Ubuntu:
  New

Bug description:
  There are yet more glibc-needed files missing from the base
  abstraction:

  --- base2017-01-20 15:37:50.0 -0800
  +++ /etc/apparmor.d/abstractions/base   2016-12-06 14:13:58.0 -0800
  @@ -92,7 +92,7 @@
 /sys/devices/system/cpu/online r,

 # glibc's *printf protections read the maps file
  -  @{PROC}/@{pid}/mapsr,
  +  @{PROC}/@{pid}/{maps,auxv,status}r,

 # libgcrypt reads some flags from /proc
 @{PROC}/sys/crypto/*   r,

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

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

[Touch-packages] [Bug 1668347] Re: Unable to set bridge_portpriority with networkd

2017-03-06 Thread Dimitri John Ledkov

Upstream pull request:
https://github.com/systemd/systemd/pull/5545

Sample packages with patch applied for zesty:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2541

How to use:
Similar to bridge port cost, one can set [Bridge] Priority= setting in the 
.network file for a given ether device, e.g.:

/etc/systemd/network/10-ens3.network
[Match]
Name=ens3

[Bridge]
Priority=33

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

Title:
  Unable to set bridge_portpriority with networkd

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  1. root@ubuntu:/run/systemd/network# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04

  2. root@ubuntu:/run/systemd/network# apt-cache policy systemd
  systemd:
Installed: 232-18ubuntu1
Candidate: 232-18ubuntu1
Version table:
   *** 232-18ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  3. Using a networkd config like this:

  # cat 10-netplan-eth1.network 
  [Match]
  MACAddress=52:54:00:12:34:02
  Name=eth1

  [Network]
  Bridge=br0
  LinkLocalAddressing=no
  IPv6AcceptRA=no

  [Bridge]
  Cost=50
  Priority=28

  %  cat /sys/class/net/br0/brif/eth1/priority 
  28

  
  4. %  cat /sys/class/net/br0/brif/eth1/priority 
  32

  
  When using ifupdown and /etc/network/interfaces to configure a bridge
  users are able to specify a bridge port priority:

  auto br0
  iface br0 inet static
address 192.168.1.1
bridge_ports eth1 eth2
bridge_portprio eth1 28
bridge_portprio eth2 14

  Which results in the bridge hook scripts running:

  brctl setportprio br0 eth1 28

  which is visible via:

  /sys/class/net/br0/brif/eth2/priority

  Note, networkd does not mention PortPriority under netdev Bridge section,
  however, PathCost is mentioned.  It appears networkd is missing an 
implementation.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Mon Feb 27 17:11:32 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=900c1e3f-f682-4455-949c-ebdbf60ac6f5 ro console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.1-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-zesty
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-zesty:cvnQEMU:ct1:cvrpc-i440fx-zesty:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-zesty
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1531184] Re: dnsmasq doesn't start on boot because its interface isn't up yet

2017-03-06 Thread Robie Basak

> Rather surprised I need to add this report, and that this Bug report isn't a 
> higher Importance and not resolved in 3 months.
Surely loads of users will have this issue?

dnsmasq (as opposed to dnsmasq-base) is not in main in Ubuntu, so relies
entirely on community support. It is not installed by default on Ubuntu,
and is an "unusual end-user configuration" as far as I can tell. And a
workaround appears available and is trivial.

If somebody wants to drive getting a fix landed, please do.

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1654406] Re: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.

2017-03-06 Thread chris pollock

Why is there no importance placed on this bug nor has it been assigned
to anyone?

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

Title:
  Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable
  to create file '/run/user/1000/dconf/user': Permission denied.  dconf
  will not work properly.

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  chris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  chris@localhost:~$ apt-cache policy tracker-extract
  tracker-extract:
Installed: 1.8.2-0ubuntu1~xenial3
Candidate: 1.8.2-0ubuntu1~xenial3
Version table:
   *** 1.8.2-0ubuntu1~xenial3 500
  500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu 
xenial/main amd64 Packages

  Jan  5 15:10:42 localhost tracker-extract.desktop[3459]: (tracker-
  extract:3459): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  Jan  5 15:12:25 localhost tracker-extract.desktop[3459]: message
  repeated 2 times: [ (tracker-extract:3459): dconf-CRITICAL **: unable
  to create file '/run/user/1000/dconf/user': Permission denied.  dconf
  will not work properly.]

  Jan  5 15:14:27 localhost tracker-extract.desktop[3459]: (tracker-
  extract:3459): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  and so on every two minutes +- a few seconds.

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

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

[Touch-packages] [Bug 1465777] Re: No ddeb for current Trusty updates.

2017-03-06 Thread Robie Basak

This also affects php-json and some other packages in Trusty. I'm duping
bug reports here for the general "there are missing ddebs on Trusty"
issue. I note that affected users can rebuild the packages with
debugging locally and then reproduce issues locally with the locally
built packages as needed.

** Also affects: php-json (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: php-json (Ubuntu)
   Status: New => Won't Fix

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

Title:
  A subset of ddebs built during the Trusty cycle are missing

Status in freetype package in Ubuntu:
  Won't Fix
Status in php-json package in Ubuntu:
  Won't Fix

Bug description:
  The page at https://launchpad.net/ubuntu/+source/freetype currently
  says that Trusty updates has FreeType 2.5.2-1ubuntu2.4, but the debug
  symbols for this are not present at
  
http://ddebs.ubuntu.com/pool/main/f/freetype/libfreetype6-dbgsym_2.5.2-1ubuntu2.4_amd64.ddeb
  . I can see that they were built at
  https://launchpadlibrarian.net/198626832/buildlog_ubuntu-trusty-
  amd64.freetype_2.5.2-1ubuntu2.4_BUILDING.txt.gz and I believe it used
  to be available, but is now missing. Is it possible to restore these
  missing ddebs? Since the freetype package does not have a -dbg
  package, using these ddebs (along with installing the source package
  at /build/bbuild/) is the only good way to step into FreeType code
  while debugging.

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

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

[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

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

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

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

Title:
  ifup -a does not start dependants last, causes deadlocks with
  vlans/bonding

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  This is a problem I've been struggling with since moving to 16.04.1
  from 14.04 (fresh install)

  I don't believe this problem affected 14.04. I have used an almost
  identical interfaces file on 14.04 without problem.

  On 16.04.1, however, 9/10 boots would hang during network
  configuration and leave the network incorrectly configured.

  When calling "ifup -a" all candidate interfaces appear to be started
  in parallel leading to collisions with locks. This causes hanging
  (until timeout) during booting and the network interfaces left
  incorrectly configured

  Imagine this /etc/network/interfaces

  auto eno1 bond0 bond0.1

  iface eno1 inet manual
  bond-master bond0

  iface bond0 inet manual
  bond-slaves eno1
  bond-mode   4
  bond-lacp-rate  1
  bond-miimon 100
  bond-updelay200
  bond-downdelay  200

  iface bond0.5 inet dhcp
  vlan-raw-device bond0

  
  eno1 -> bond0 -> bond0.5 -> dhcp

  When calling "ifup -a" at boot time all three interfaces are started
  at the same time.

  bond0 and bond0.5 both attempt to share the same lock file:

/run/network/ifstate.bond0

  If bond0 wins the race, the system will start correctly (1/10):

* bond0 starts and creates the bond0 device and the ifenslave.bond0 file to 
indicate the bond is ready
* eno1 polls for the ifenslave.bond0 file, when it appears it attaches eno1 
to bond0
* bond0 finishes and releases the lock
* bond0.5 now acquires the lock.
* bond0.5 starts dhclient, which can talk to the network and configure the 
interface

  
  If, however, bond0.2 wins the lock race, the system will hang at boot (5 
mins) and fail to set up the network.

* bond0.5 is awarded the ifstate.bond0 lockfile
* bond0.5 starts dhclient waiting to hear from the network
* bond0 is blocked, so bond0 is not created nor is the bond0.ifenslave file 
* eno1 polls but never finds the ifenslave.bond0 file so never attaches to 
bond0
* bond0.5's dhclient is trying to talk to a disconnected network and never 
receives an answer

! bond0.5 is stuck running dhclient
! bond0 is stuck waiting for bond0.5 to finish
! eno1 is stuck waiting for bond0 to create the ifenslave.bond0 file

  
  I believe ifup should start interfaces (that share lock files) in dependant 
order. The most basic interface must be awarded the lock over its dependants. 
In this case:

1 eno1
2 bond0
3 bond0.5

  but never:

1 eno1
2 bond0.5
3 bond0

  
  As a work arouund, in /etc/network/interfaces

  -auto   eno1 bond0 bond0.1
  +auto   eno1 bond0
  +allow-bond bond0.1

  And also in /lib/systemd/system/networking.service

   ExecStart=/sbin/ifup -a --read-environment
  +ExecStart=/sbin/ifup -a --allow=bond --read-environment
   ExecStop=/sbin/ifdown -a --read-environment

  Then run:

systemctl dameon-reload

  This causes all "auto" interfaces to start then, when they've
  completed, all allow-bond interfaces to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.1 [modified: 
lib/systemd/system/networking.service]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 26 06:32:57 2016
  InstallationDate: Installed on 2016-10-24 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.networking.conf: [modified]
  mtime.conffile..etc.init.networking.conf: 2016-10-26T04:52:05.750927

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

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

[Touch-packages] [Bug 1669133] Re: Drop unnecessary rename of dlm -> dlm-controld (binary package)

2017-03-06 Thread Nish Aravamudan

** Tags added: bitesize

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

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

** Changed in: ocfs2-tools (Ubuntu)
   Status: New => Triaged

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

Title:
  Drop unnecessary rename of dlm -> dlm-controld (binary package)

Status in dlm package in Ubuntu:
  Triaged
Status in lvm2 package in Ubuntu:
  Triaged
Status in ocfs2-tools package in Ubuntu:
  Triaged

Bug description:
  dlm -> dlm-controld transition (will need to be kept through 18.04 for LTS 
upgraders)
- Add transitional dummy binary package to rename back
- Drop delta in lvm2 and ocfs2-tools

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

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

[Touch-packages] [Bug 1669819] Re: [unity8] strange behavior when maximizing snaped windows

2017-03-06 Thread Lukáš Tinkl

** Branch linked: lp:~lukas-kde/unity8/fix-restore-position

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

Title:
  [unity8] strange behavior  when maximizing snaped windows

Status in Canonical System Image:
  Triaged
Status in Ubuntu UX:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 17.04 Unity8

  open random app (terminal app), snap it randomly on the screen (right
  buttom corner) by draging the app by the title bar (see screenshot1).
  now click on maximize window, the window almost leaves the screen
  (screenshot2).

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

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

[Touch-packages] [Bug 1670442] [NEW] Improve splash screen behaviour

Public bug reported:

Related to bug #1577641, we may want to improve the way the splash
screen logic is implemented.

The shell-managed splash screens serve as a way to provide immediate
feedback for an application being launched, so that the user doesn't
need to find out whether they failed to launch the app or the app's just
slow to launch (or maybe even crashed on startup).

My proposal is that:
- we delay showing the splash screen for a very short interval (50ms to start 
with?)
- *if* the splash screen is shown, it has to be shown for at least a certain 
time (500ms?) to avoid "flicker" between the splash screen and the app surface
- if possible, let the user know that the app crashed/exited with an error and 
give the user an option to restart or close (long-term maybe also report the 
issue?)

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity8 8.15+17.04.20170303.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon Mar  6 18:33:05 2017
InstallationDate: Installed on 2016-05-06 (303 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: unity8
UpgradeStatus: Upgraded to zesty on 2016-11-22 (104 days ago)

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

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


** Tags: amd64 apport-bug third-party-packages zesty

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

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

Title:
  Improve splash screen behaviour

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Related to bug #1577641, we may want to improve the way the splash
  screen logic is implemented.

  The shell-managed splash screens serve as a way to provide immediate
  feedback for an application being launched, so that the user doesn't
  need to find out whether they failed to launch the app or the app's
  just slow to launch (or maybe even crashed on startup).

  My proposal is that:
  - we delay showing the splash screen for a very short interval (50ms to start 
with?)
  - *if* the splash screen is shown, it has to be shown for at least a certain 
time (500ms?) to avoid "flicker" between the splash screen and the app surface
  - if possible, let the user know that the app crashed/exited with an error 
and give the user an option to restart or close (long-term maybe also report 
the issue?)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170303.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar  6 18:33:05 2017
  InstallationDate: Installed on 2016-05-06 (303 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (104 days ago)

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

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

[Touch-packages] [Bug 1577641] Re: Unity8 creates a blank black window for windowless apps

I'm going to say Won't Fix again. On the default socket we only expect
apps - apps that will have surfaces. For those apps unity8 is showing a
splash screen.

Any clients that are not apps can connect on a trusted socket - and we
may decide to open a "utilities" socket, but we wouldn't accept any
surfaces there.

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: canonical-devices-system-image
   Status: Confirmed => Won't Fix

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

Title:
  Unity8 creates a blank black window for windowless apps

Status in Canonical System Image:
  Won't Fix
Status in Mir:
  Invalid
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  Unity8 creates a blank black window for windowless apps.

  Windowless apps are closer thank you think:   Xmir -rootless
  is one such example while no X apps have started yet.

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

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

[Touch-packages] [Bug 1668347] Re: Unable to set bridge_portpriority with networkd

2017-03-06 Thread Dimitri John Ledkov

** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1668347

Title:
  Unable to set bridge_portpriority with networkd

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  1. root@ubuntu:/run/systemd/network# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04

  2. root@ubuntu:/run/systemd/network# apt-cache policy systemd
  systemd:
Installed: 232-18ubuntu1
Candidate: 232-18ubuntu1
Version table:
   *** 232-18ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  3. Using a networkd config like this:

  # cat 10-netplan-eth1.network 
  [Match]
  MACAddress=52:54:00:12:34:02
  Name=eth1

  [Network]
  Bridge=br0
  LinkLocalAddressing=no
  IPv6AcceptRA=no

  [Bridge]
  Cost=50
  Priority=28

  %  cat /sys/class/net/br0/brif/eth1/priority 
  28

  
  4. %  cat /sys/class/net/br0/brif/eth1/priority 
  32

  
  When using ifupdown and /etc/network/interfaces to configure a bridge
  users are able to specify a bridge port priority:

  auto br0
  iface br0 inet static
address 192.168.1.1
bridge_ports eth1 eth2
bridge_portprio eth1 28
bridge_portprio eth2 14

  Which results in the bridge hook scripts running:

  brctl setportprio br0 eth1 28

  which is visible via:

  /sys/class/net/br0/brif/eth2/priority

  Note, networkd does not mention PortPriority under netdev Bridge section,
  however, PathCost is mentioned.  It appears networkd is missing an 
implementation.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Mon Feb 27 17:11:32 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=900c1e3f-f682-4455-949c-ebdbf60ac6f5 ro console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.1-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-zesty
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-zesty:cvnQEMU:ct1:cvrpc-i440fx-zesty:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-zesty
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1669819] Re: [unity8] strange behavior when maximizing snaped windows

2017-03-06 Thread Lukáš Tinkl

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

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

Title:
  [unity8] strange behavior  when maximizing snaped windows

Status in Canonical System Image:
  Triaged
Status in Ubuntu UX:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 17.04 Unity8

  open random app (terminal app), snap it randomly on the screen (right
  buttom corner) by draging the app by the title bar (see screenshot1).
  now click on maximize window, the window almost leaves the screen
  (screenshot2).

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

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

[Touch-packages] [Bug 1644237] Re: unity8 fails to start as guest user

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  unity8 fails to start as guest user

Status in Canonical System Image:
  Triaged
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

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

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

[Touch-packages] [Bug 1670399] Re: dep8 tests are failing in zesty

2017-03-06 Thread Scott Moser

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

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

Title:
  dep8 tests are failing in zesty

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  software-properties tests are failing in autopkgtests.
   http://autopkgtest.ubuntu.com/packages/s/software-properties/zesty/amd64

  The first failure is just lack of 'gpg1' in the build environment.

  then after that, we still get some failures in my environment at least
  (running in lxc container).

  $ sudo xvfb-run -e my.log sh -ec "python3 setup.py test"

  http://paste.ubuntu.com/24125361/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1670399/+subscriptions

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

[Touch-packages] [Bug 1670432] [NEW] Xorg freeze

2017-03-06 Thread tclovis

Public bug reported:

Freezes the computer in the log in and also when entering the screen
saver.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-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
Date: Mon Mar  6 14:13:14 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.1.14, 4.10.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Since before I upgraded
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:7222]
InstallationDate: Installed on 2015-07-06 (608 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-9-generic 
root=UUID=5898c70a-eebd-44a1-b634-56c69c8a4914 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.75-1
version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.4-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1
xserver.bootTime: Mon Mar  6 13:21:05 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu9
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu zesty

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Freezes the computer in the log in and also when entering the screen
  saver.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-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
  Date: Mon Mar  6 14:13:14 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.1.14, 4.10.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:7222]
  InstallationDate: Installed on 2015-07-06 (608 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType:

[Touch-packages] [Bug 1633046] Re: Pressing play/pause hotkey hangs U8 session

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

As far I can tell this is a duplicate of bug #1525285, please undupe if
you know otherwise.

** This bug has been marked a duplicate of bug 1525285
   inspecting clutter plugin hangs outside X11

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

Title:
  Pressing play/pause hotkey hangs U8 session

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

Bug description:
  Log in to a U8 session in 16.10.
  Press the play/pause hotkey.
  Note that the session is now hung.

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

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

[Touch-packages] [Bug 1553328] Re: Mir/Unity8 crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Stephen M. Webb (bregma)

** Changed in: canonical-devices-system-image
Milestone: None => u8c-1

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

Title:
  Mir/Unity8 crashes/freezes on nouveau (nv50) in pushbuf_kref()
  especially with multiple monitors, webbrowser-app or system settings

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in Nouveau Xorg driver:
  Unknown
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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

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

** Changed in: canonical-devices-system-image
Milestone: None => u8c-1

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

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

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

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

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

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

[Touch-packages] [Bug 1584894] Re: unity-system-compositor (or any Mir server) crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter and QEMU