date:20170203

[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package openssh-server 1:7.3p1-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 255

Status in openssh package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 16.10
  Release:  16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: openssh-server 1:7.3p1-1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   ncurses-term:amd64: Install
   openssh-sftp-server:amd64: Install
   openssh-server:amd64: Install
   ssh-import-id:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Oct 18 10:39:14 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2016-10-14 (7 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: openssh
  Title: package openssh-server 1:7.3p1-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 255
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1637663] Re: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in ntp package in Ubuntu:
  Expired

Bug description:
  root@ntp-srv001:~# apt-get install ntp
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  ntp is already the newest version.
  0 upgraded, 0 newly installed, 0 to remove and 86 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2.14.04.10) ...
  dpkg: error processing package ntp (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ntp
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  root@ntp-srv001:~#

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Oct 28 15:24:45 2016
  DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu2.14.04.10:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-28 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: ntp
  Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 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/ntp/+bug/1637663/+subscriptions

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

[Touch-packages] [Bug 1641806] Re: double date listed on pull-down calendar

[Expired for indicator-datetime (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: indicator-datetime (Ubuntu)
   Status: Incomplete => Expired

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

Title:
 double date listed on pull-down calendar

Status in indicator-datetime package in Ubuntu:
  Expired

Bug description:
  The calendar on my Meizu Pro5 (not so) smart phone, running 15.04
OTA-13 has the 6th of November listed twice, Sunday and Monday, on the
pull-down calendar. Hence every day/date after that is wrong by one
day. This continues into the next year. The Calendar app that allows
events to be recorded is not affected and shows the correct day/dates.

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

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

[Touch-packages] [Bug 1645114] Re: Error splicing file

[Expired for util-linux (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Error splicing file

Status in util-linux package in Ubuntu:
  Expired

Bug description:
  I've a trouble in transfering a large file (4.8Gb) from my HD to an external 
HD in sharing with Win too.
  The external HD is NTFS formatted for compatibility with WIN

  If I move/copy the file from WIN10 environment, the process is completed 
correctly.
  If I move/copy the file from Ubuntu 16.04 LTS environment, I have the error:

  Error splicing file: File too large

  System configuration:

Intel® Core™ i7-3770K CPU @ 3.50GHz × 8 
RAM 32Gb
Graphics Quadro 600
OS type 64-bit

  External HD Packard Bell 1Tb Graffite model, NTFS format
  Many thanks for any help on the subject, Claudio

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

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

[Touch-packages] [Bug 1643717] Re: package tar 1.27.1-1ubuntu0.1 failed to install/upgrade

[Expired for tar (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package tar 1.27.1-1ubuntu0.1 failed to install/upgrade

Status in tar package in Ubuntu:
  Expired

Bug description:
  I'm new to bug reporting so please forgive me if I'm doing it wrong. I
  was trying to run apt-get updgrade and it crashed. There appears to be
  something wrong with tar, but I don't know what or how. My system is
  pretty hosed at the moment.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tar 1.27.1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-101-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Tue Nov 22 12:14:59 2016
  DuplicateSignature: package:tar:1.27.1-1ubuntu0.1:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-10-22 (761 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: tar
  Title: package tar 1.27.1-1ubuntu0.1 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to trusty on 2016-08-07 (106 days ago)

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

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

[Touch-packages] [Bug 1651474] Re: App Drawer does not refresh

2017-02-03 Thread Ted Gould

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

** This bug has been marked a duplicate of bug 1630997
   Provide a way to listen to registry changes

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

Title:
  App Drawer does not refresh

Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When adding or removing applications from the system (either via snap
  cli, apt, or snappy scope), the contents of the App Drawer do not
  refresh to reflect the current state of installed apps in the system.
  There is also no way to manually cause a refresh, and searching only
  works on the existing cached results.

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

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

[Touch-packages] [Bug 1659955] Re: Not possible to launch apps in xenial using unity8-session.ubuntu-app-launch command using the unity8 session snap

2017-02-03 Thread Ted Gould

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Not possible to launch apps in xenial using unity8-session.ubuntu-app-
  launch command using the unity8 session snap

Status in Canonical System Image:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  
  Steps:
  . I start unity8 session snap in my xenial 
  . It is possible start apps manually
  . When run the command unity8-session.ubuntu-app-launch-appids a list of apps 
are printed (I select webbrowser-app_webbrowser-app_8) (also tried with other 
too)
  . I run the command "unity8-session.ubuntu-app-launch 
webbrowser-app_webbrowser-app_8" and I get the following output 
http://paste.ubuntu.com/23877063/ (everything seems to be ok)
  . But in the screen the app is not displayed in the screen. 

  If I follow the same steps in zesty, the app is displayed in the
  screen.

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

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

[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

2017-02-03 Thread Bug Watch Updater

** Changed in: unattended-upgrades (Debian)
   Status: Unknown => New

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

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Yakkety:
  Confirmed
Status in unattended-upgrades package in Debian:
  New

Bug description:
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.

  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).

  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.

  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:

  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True

  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.

  Additional information:

  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2)
  unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  3)
  Fast reboot
  4)
  Very slow reboot (after a 10 minutes timeout)

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

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

[Touch-packages] [Bug 1661521] Re: [regression] Windowed clients of nested servers are all black

** Changed in: mir
 Assignee: Mir development team (mir-team) => (unassigned)

** Branch linked: lp:~kdub/mir/fix-1661521

** Changed in: mir
 Assignee: (unassigned) => Kevin DuBois (kdub)

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

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

Title:
  [regression] Windowed clients of nested servers are all black

Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  [regression] Windowed clients of nested servers are all black

  FAILING:
  lp:mir r4008
  lp:mir/0.26 r4005

  WORKING:
  Mir 0.26.0 zesty binaries (lp:mir/0.26 r3994)
  lp:mir/0.25 r3822

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

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

[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what

Fix committed to lp:mir/0.26 at revision 4007, scheduled for release in
Mir 0.26.1

** Changed in: mir/0.26
   Status: In Progress => Fix Committed

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

Title:
  [regression] Nested server segfaults or rapidly logs exceptions when a
  fullscreen client starts [in mir_presentation_chain_set_dropping_mode
  ... std::exception::what: Operation not permitted]

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Nested server segfaults when a fullscreen client starts

  Using Mir 0.26.0 (zesty release):

  The client dies:

  [2017-02-03 15:05:44.315444]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76):
 Throw in function void mir::client::PromiseStateBase::break_promise() [with 
T = std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::error_info_injector
  std::exception::what: broken_promise

  Because the server died:

  Segmentation fault (core dumped)
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x7fcceb7b4003 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #2  0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fccec0e3a7a in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #4  0x7fccec09fd2d in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #5  0x7fccec09f018 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #6  0x7fccec0e2c79 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #7  0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #8  0x7fcce95326ca in start_thread (arg=0x7fccde2b4700)
  at pthread_create.c:333
  #9  0x7fccec4710ff in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

  However in development builds the server does not die and just floods
  the log instead:

  [2017-02-03 16:52:44.382460]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.399142]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.415823]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.432504]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  *** WORKAROUND ***
  Start your nested server with --nested-passthrough=OFF
  Which works on the 0.26.0 release, but not on anything newer because you'll 
then hit the more recent regression bug 1661521.

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

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

[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what

** Changed in: mir
 Assignee: (unassigned) => Kevin DuBois (kdub)

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

Title:
  [regression] Nested server segfaults or rapidly logs exceptions when a
  fullscreen client starts [in mir_presentation_chain_set_dropping_mode
  ... std::exception::what: Operation not permitted]

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Nested server segfaults when a fullscreen client starts

  Using Mir 0.26.0 (zesty release):

  The client dies:

  [2017-02-03 15:05:44.315444]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76):
 Throw in function void mir::client::PromiseStateBase::break_promise() [with 
T = std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::error_info_injector
  std::exception::what: broken_promise

  Because the server died:

  Segmentation fault (core dumped)
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x7fcceb7b4003 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #2  0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fccec0e3a7a in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #4  0x7fccec09fd2d in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #5  0x7fccec09f018 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #6  0x7fccec0e2c79 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #7  0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #8  0x7fcce95326ca in start_thread (arg=0x7fccde2b4700)
  at pthread_create.c:333
  #9  0x7fccec4710ff in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

  However in development builds the server does not die and just floods
  the log instead:

  [2017-02-03 16:52:44.382460]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.399142]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.415823]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.432504]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  *** WORKAROUND ***
  Start your nested server with --nested-passthrough=OFF
  Which works on the 0.26.0 release, but not on anything newer because you'll 
then hit the more recent regression bug 1661521.

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

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

[Touch-packages] [Bug 1661521] Re: [regression] Windowed clients of nested servers are all black

Fix committed to lp:mir/0.26 at revision 4011, scheduled for release in
Mir 0.26.1

** Changed in: mir/0.26
   Status: Triaged => Fix Committed

** Changed in: mir/0.26
 Assignee: Mir development team (mir-team) => Kevin DuBois (kdub)

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

Title:
  [regression] Windowed clients of nested servers are all black

Status in Mir:
  Triaged
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  [regression] Windowed clients of nested servers are all black

  FAILING:
  lp:mir r4008
  lp:mir/0.26 r4005

  WORKING:
  Mir 0.26.0 zesty binaries (lp:mir/0.26 r3994)
  lp:mir/0.25 r3822

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

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

[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

2017-02-03 Thread Scott Leggett

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

** Also affects: unattended-upgrades (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809669
   Importance: Unknown
   Status: Unknown

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

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Yakkety:
  Confirmed
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.

  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).

  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.

  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:

  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True

  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.

  Additional information:

  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2)
  unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  3)
  Fast reboot
  4)
  Very slow reboot (after a 10 minutes timeout)

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

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

[Touch-packages] [Bug 1638902] Re: [2.27 Regression] gold internal error in fix_errata on aarch64-linux-gnu

2017-02-03 Thread Bug Watch Updater

** Changed in: binutils
   Status: Unknown => Confirmed

** Changed in: binutils
   Importance: Unknown => Medium

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

Title:
   [2.27 Regression] gold internal error in fix_errata on aarch64-linux-
  gnu

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  seen with binutils from the 2.27 branch:

  $ sh link.sh 
  ld.gold: internal error in fix_errata, at ../../gold/aarch64.cc:1960

  This works with the BFD linker, or when dropping the --fix-
  cortex-a53-843419 option.

  The test cases comes from the build of the gitit package on Ubuntu 16.10,
  see https://launchpad.net/ubuntu/+source/gitit/0.12.1.1+dfsg-2build7

  The package built successfully with binutils 2.26.1

  test case at
  http://people.canonical.com/~doko/tmp/tst.tar.xz

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

-- 
Mailing list: https://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 1660111] Re: PCI/internal sound card not detected

2017-02-03 Thread jeffrey morgan

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

thanks, I unmuted and it was fine


Jeffrey Morgan
jeffrey_morga...@aim.com



-Original Message-
From: Tyler Hicks 
To: jeffrey_morgan35 
Sent: Fri, Feb 3, 2017 5:01 pm
Subject: [Bug 1660111] Re: PCI/internal sound card not detected

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

** Information type changed from Private Security to Public

** This bug has been marked a duplicate of bug 1660109
   [, Realtek ALC880, Green Headphone Out, Front] No sound at all

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1660111

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  speaker icon on desktop is red with a red X at the side of it- sound
  was ok this was fixed once but has returned to red

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jeffrey2370 F...m pulseaudio
   /dev/snd/controlC0:  jeffrey2370 F pulseaudio
  CurrentDesktop: Unity
 Date: Sun Jan 29 08:17:05 2017
  InstallationDate: Installed on 2017-01-28 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
 PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2005
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EV91510A.86A.0444.2005.0429.2108
  dmi.board.name: D915GEV
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC63667-503
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEV91510A.86A.0444.2005.0429.2108:bd04/29/2005:svn:pn:pvr:rvnIntelCorporation:rnD915GEV:rvrAAC63667-503:cvn:ct2:cvr:

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

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  speaker icon on desktop is red with a red X at the side of it- sound
  was ok this was fixed once but has returned to red

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jeffrey2370 F...m pulseaudio
   /dev/snd/controlC0:  jeffrey2370 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jan 29 08:17:05 2017
  InstallationDate: Installed on 2017-01-28 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2005
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EV91510A.86A.0444.2005.0429.2108
  dmi.board.name: D915GEV
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC63667-503
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEV91510A.86A.0444.2005.0429.2108:bd04/29/2005:svn:pn:pvr:rvnIntelCorporation:rnD915GEV:rvrAAC63667-503:cvn:ct2:cvr:

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

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

[Touch-packages] [Bug 1660496] Re: Libva upstream project has moved to Github from Freedesktop.org

2017-02-03 Thread Bug Watch Updater

** Changed in: libva (Debian)
   Status: New => Fix Committed

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

Title:
  Libva upstream project has moved to Github from Freedesktop.org

Status in libva package in Ubuntu:
  New
Status in libva package in Debian:
  Fix Committed

Bug description:
  Package: libva
  Version: 1.7.3-2

  I'm a maintainer of upstream Libva.  I have moved our project from
  freedesktop.org to github.com.

  Wiki location has moved to: https://01.org/linuxmedia/vaapi

  Libva project has moved to https://github.com/01org/libva

  Use https://github.com/01org/libva/issues/new to file bugs on the
  libva github site

  Packages will need to be updated to pull source from the new github
  repos mentioned above.

  I have submitted this bug upstream to debian packagers of libva
  Bug#853270
  853...@bugs.debian.org

  Thanks,

  Sean

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

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

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

2017-02-03 Thread luca

any news?

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

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

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

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

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

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

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

[Touch-packages] [Bug 769314] Re: System bell completely silent because PulseAudio sample file undefined by default

2017-02-03 Thread Iiro Laiho

** Tags added: xenial

** Description changed:

  Binary package hint: unity
  
  This bug is about problems using the system bell in Unity or another
  Compiz-based environment.  For problems using the system bell in Ubuntu
  Classic/Metacity or another Metacity-based environment, please see bug
  #486154.
  
  The system bell (that beep when you backspace on an empty line on a
  terminal, i.e.) is badly broken using the Unity environment in the Natty
  beta 2.  By default, no sound is produced, and several misconfigurations
  make it difficult to produce sound either from the PC speaker or Pulse
  Audio's module-x11-bell.  Not knowing what the desired behavior is, I
  can't say exactly what needs to be fixed.  But the combination of the
  following issues makes the system quite obviously broken.
  
  1) pcskpr is blacklisted.
  The pcspkr module is necessary for the PC speaker to produce sound.  It is 
blacklisted, so regular users cannot turn the bell on.  It would be nice for 
this to be fixed, but the attitudes displayed in #77010 suggest that it won't 
be.  Nonetheless, I note it here because it interacts with some of the 
following.
  
- 2) The X bell volume is set to 0.
+ 2) The X bell volume is set to 0. (no more true in xenial)
  As reported by `xset q`, the bell volume is 0 when Unity is started.  Both 
the PC speaker and module-x11-bell respect this setting, so the volume must be 
turned up (with `xset b on` or `xset b 100`) for either to work.  Since both 
the PC speaker and module-x11-bell are disabled by default, this setting only 
serves to frustrate attempts to turn them on; it never prevents unwanted sound.
  
  3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11
  This is a system file, not a user file, so users cannot decide whether they 
want this module loaded or not.  They could write a script to unload the module 
at login (and hope the module number doesn't vary between boots), but it would 
be much cleaner to have the modules loaded from a user file, possibly with 
defaults if the user file doesn't exist.
  
  4) Sample bell.ogg is not loaded.
  When module-x11-bell is loaded, it is told to use the sample bell.ogg.  But 
no sample is loaded into Pulse Audio.  Thus, module-x11-bell traps system bell 
events (keeping them from going to the PC speaker) without producing any sound. 
 If module-x11-bell is loaded, the sample it calls on should be loaded as well. 
 (To fix this, run `pactl upload-sample 
/usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.)
  
  5) gnome-volume-control doesn't.
  The "Sound Effects" tab of gnome-volume-control offers to set the volume and 
sound for system bell events, but these have no effect.  This is because 
gnome-volume-control is trying to control system bells through metacity.  
Ideally, it should be rewritten to control module-x11-bell instead, but a 
temporary fix could be to simply disable this tab.
  
  6) System bell settings don't transfer to the Ubuntu Classic environment.
  Because that is using metacity, which has it's own set of problems.  See bug 
#486154.
  
  This has been from testing in a VM (virtualbox), but all of these
  behaviors have also been seen in Compiz in various previous versions of
  Ubuntu running on various hardware.
  
  I have reported this bug against several components, as it is really an 
integration issue.  The eventual fix may not involve your component, but please 
do not mark this bug as invalid until we have at least a roadmap for fixing it. 
 Otherwise, I fear responsibility will be passed from component to component 
without anything being fixed.  Rationales:
  Unity - As the overarching environment, Unity should be responsible for 
getting everything integrated.  Additionally, some of the problems relate to 
session startup settings.
  Pulse Audio - module-x11-bell is not loaded intelligently or correctly.
  Gnome Media - Own gnome-volume-control.
  
  Versions (but note the same behavior has been seen in many earlier versions):
  unity: 3.8.10-0ubuntu2
  pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3
  gnome-media: 2.32.0-0ubuntu7

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

Title:
  System bell completely silent because PulseAudio sample file undefined
  by default

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  This bug is about problems using the system bell in Unity or another
  Compiz-based environment.  For problems using the system bell in
  Ubuntu Classic/Metacity or another Metacity-based environment, please
  see bug #486154.

  The system bell (that beep when you backspace on an empty line on a
  terminal, i.e.) is badly broken using the Unity environment in the

[Touch-packages] [Bug 1661763] [NEW] screen turns off during standby, doesn't wake up on resume

2017-02-03 Thread Gábor Lipták

Public bug reported:

screen turns off during standby, doesn't wake up on resume

had to reboot to recover

Feb  2 22:51:59 ubuntu8 kernel: [318555.548546] [ cut here 
]
Feb  2 22:51:59 ubuntu8 kernel: [318555.548650] WARNING: CPU: 3 PID: 14496 at 
/build/linux-RZGRu0/linux-4.8.0/drivers/gpu/drm/i915/intel_display.c:14328 
skl_max_scale.part.120+0x75/0x80 [i915]
Feb  2 22:51:59 ubuntu8 kernel: [318555.548654] WARN_ON_ONCE(!crtc_clock || 
cdclk < crtc_clock)
Feb  2 22:51:59 ubuntu8 kernel: [318555.548657] Modules linked in: msr ccm 
rfcomm bnep hid_multitouch i2c_designware_platform i2c_designware_core hp_wmi 
sparse_keymap nls_iso8859_1 arc4 snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc 
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal coretemp 
snd_hda_codec_conexant snd_hda_codec_generic snd_soc_sst_dsp snd_hda_ext_core 
kvm_intel snd_soc_sst_match kvm iwlmvm snd_soc_core irqbypass crct10dif_pclmul 
snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec 
crc32_pclmul mac80211 snd_hda_core ghash_clmulni_intel snd_hwdep aesni_intel 
snd_pcm aes_x86_64 lrw snd_seq_midi glue_helper snd_seq_midi_event ablk_helper 
snd_rawmidi cryptd iwlwifi snd_seq snd_seq_device snd_timer input_leds cfg80211 
joydev serio_raw rtsx_pci_ms memstick snd soundcore uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 shpchp videobuf2_core videodev media mei_me 
idma64 mei virt_dma btusb btrtl intel_lpss_pci intel_pch_thermal 
processor_thermal_device in
 tel_soc_dts_iosf ucsi int3403_thermal hci_uart btbcm btqca btintel bluetooth 
intel_lpss_acpi intel_lpss hp_accel lis3lv02d input_polldev int3402_thermal 
int3406_thermal int340x_thermal_zone tpm_crb mac_hid int3400_thermal 
acpi_thermal_rel acpi_pad dptf_power hp_wireless parport_pc ppdev lp parport 
ip_tables x_tables autofs4 btrfs xor raid6_pq rtsx_pci_sdmmc i915 i2c_algo_bit 
drm_kms_helper syscopyarea psmouse sysfillrect nvme sysimgblt fb_sys_fops 
nvme_core drm ahci rtsx_pci libahci i2c_hid wmi hid video fjes
Feb  2 22:51:59 ubuntu8 kernel: [318555.548904] CPU: 3 PID: 14496 Comm: Xorg 
Not tainted 4.8.0-34-generic #36-Ubuntu
Feb  2 22:51:59 ubuntu8 kernel: [318555.548907] Hardware name: HP HP ENVY 
Notebook/81D1, BIOS F.28 10/05/2016
Feb  2 22:51:59 ubuntu8 kernel: [318555.548911]  0286 
8055b5e8 975531437930 8e430a22
Feb  2 22:51:59 ubuntu8 kernel: [318555.548924]  975531437980 
 975531437970 8e08319b
Feb  2 22:51:59 ubuntu8 kernel: [318555.548930]  37f88e1a9a80 
975412ad86c0 97555c5b3c00 9755660a6000
Feb  2 22:51:59 ubuntu8 kernel: [318555.548936] Call Trace:
Feb  2 22:51:59 ubuntu8 kernel: [318555.548948]  [] 
dump_stack+0x63/0x81
Feb  2 22:51:59 ubuntu8 kernel: [318555.548957]  [] 
__warn+0xcb/0xf0
Feb  2 22:51:59 ubuntu8 kernel: [318555.548965]  [] 
warn_slowpath_fmt+0x5f/0x80
Feb  2 22:51:59 ubuntu8 kernel: [318555.548998]  [] ? 
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549068]  [] 
skl_max_scale.part.120+0x75/0x80 [i915]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549131]  [] 
intel_check_primary_plane+0xc6/0xe0 [i915]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549151]  [] ? 
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549211]  [] 
intel_plane_atomic_check+0x132/0x1f0 [i915]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549230]  [] 
drm_atomic_helper_check_planes+0x84/0x200 [drm_kms_helper]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549292]  [] 
intel_atomic_check+0x155/0x760 [i915]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549339]  [] 
drm_atomic_check_only+0x187/0x610 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549377]  [] 
drm_atomic_commit+0x17/0x60 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549397]  [] 
drm_atomic_helper_disable_plane+0xac/0xf0 [drm_kms_helper]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549430]  [] 
__setplane_internal+0x17b/0x270 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549436]  [] ? 
unix_stream_read_generic+0x24f/0x920
Feb  2 22:51:59 ubuntu8 kernel: [318555.549467]  [] 
drm_mode_cursor_universal+0x139/0x240 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549498]  [] 
drm_mode_cursor_common+0x7e/0x180 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549530]  [] 
drm_mode_cursor_ioctl+0x50/0x70 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549555]  [] 
drm_ioctl+0x200/0x4f0 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549585]  [] ? 
drm_mode_setcrtc+0x580/0x580 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549592]  [] ? 
timerqueue_add+0x59/0xb0
Feb  2 22:51:59 ubuntu8 kernel: [318555.549599]  [] ? 
enqueue_hrtimer+0x3d/0x80
Feb  2 22:51:59 ubuntu8 kernel: [318555.549606]  [] ? 
hrtimer_start_range_ns+0x1c0/0x3d0
Feb  2 22:51:59 ubuntu8 kernel: [318555.549612]  [] 
do_vfs_ioctl+0xa3/0x610
Feb  2 22:51:59 ubuntu8 kernel: [318555.549617]  [] ? 
__sys_recvmsg+0x51/0x90
Feb  2 22:51:59 ubuntu8 kernel: [318555.549622]  [] 
S

[Touch-packages] [Bug 769314] Re: System bell completely silent because PulseAudio sample file undefined by default

2017-02-03 Thread Iiro Laiho

** Summary changed:

- System bell broken in Natty/Unity (despite heroic...)
+ System bell completely silent because PulseAudio sample file undefined by 
default

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

Title:
  System bell completely silent because PulseAudio sample file undefined
  by default

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  This bug is about problems using the system bell in Unity or another
  Compiz-based environment.  For problems using the system bell in
  Ubuntu Classic/Metacity or another Metacity-based environment, please
  see bug #486154.

  The system bell (that beep when you backspace on an empty line on a
  terminal, i.e.) is badly broken using the Unity environment in the
  Natty beta 2.  By default, no sound is produced, and several
  misconfigurations make it difficult to produce sound either from the
  PC speaker or Pulse Audio's module-x11-bell.  Not knowing what the
  desired behavior is, I can't say exactly what needs to be fixed.  But
  the combination of the following issues makes the system quite
  obviously broken.

  1) pcskpr is blacklisted.
  The pcspkr module is necessary for the PC speaker to produce sound.  It is 
blacklisted, so regular users cannot turn the bell on.  It would be nice for 
this to be fixed, but the attitudes displayed in #77010 suggest that it won't 
be.  Nonetheless, I note it here because it interacts with some of the 
following.

  2) The X bell volume is set to 0.
  As reported by `xset q`, the bell volume is 0 when Unity is started.  Both 
the PC speaker and module-x11-bell respect this setting, so the volume must be 
turned up (with `xset b on` or `xset b 100`) for either to work.  Since both 
the PC speaker and module-x11-bell are disabled by default, this setting only 
serves to frustrate attempts to turn them on; it never prevents unwanted sound.

  3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11
  This is a system file, not a user file, so users cannot decide whether they 
want this module loaded or not.  They could write a script to unload the module 
at login (and hope the module number doesn't vary between boots), but it would 
be much cleaner to have the modules loaded from a user file, possibly with 
defaults if the user file doesn't exist.

  4) Sample bell.ogg is not loaded.
  When module-x11-bell is loaded, it is told to use the sample bell.ogg.  But 
no sample is loaded into Pulse Audio.  Thus, module-x11-bell traps system bell 
events (keeping them from going to the PC speaker) without producing any sound. 
 If module-x11-bell is loaded, the sample it calls on should be loaded as well. 
 (To fix this, run `pactl upload-sample 
/usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.)

  5) gnome-volume-control doesn't.
  The "Sound Effects" tab of gnome-volume-control offers to set the volume and 
sound for system bell events, but these have no effect.  This is because 
gnome-volume-control is trying to control system bells through metacity.  
Ideally, it should be rewritten to control module-x11-bell instead, but a 
temporary fix could be to simply disable this tab.

  6) System bell settings don't transfer to the Ubuntu Classic environment.
  Because that is using metacity, which has it's own set of problems.  See bug 
#486154.

  This has been from testing in a VM (virtualbox), but all of these
  behaviors have also been seen in Compiz in various previous versions
  of Ubuntu running on various hardware.

  I have reported this bug against several components, as it is really an 
integration issue.  The eventual fix may not involve your component, but please 
do not mark this bug as invalid until we have at least a roadmap for fixing it. 
 Otherwise, I fear responsibility will be passed from component to component 
without anything being fixed.  Rationales:
  Unity - As the overarching environment, Unity should be responsible for 
getting everything integrated.  Additionally, some of the problems relate to 
session startup settings.
  Pulse Audio - module-x11-bell is not loaded intelligently or correctly.
  Gnome Media - Own gnome-volume-control.

  Versions (but note the same behavior has been seen in many earlier versions):
  unity: 3.8.10-0ubuntu2
  pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3
  gnome-media: 2.32.0-0ubuntu7

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

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

[Touch-packages] [Bug 1661757] [NEW] libc6 Depends line for xenial i386 package appears to be incorrect.

2017-02-03 Thread Rodney Lott

Public bug reported:

Upon inspecting the i386 and amd64 packages of libncurses5/xenial, there
appears to be an error in the libc6 dependency for the i386 case:

$ dpkg -I libncurses5_6.0+20160213-1ubuntu1_amd64.deb | grep Depends
 Depends: libtinfo5 (= 6.0+20160213-1ubuntu1), libc6 (>= 2.14)
$ dpkg -I libncurses5_6.0+20160213-1ubuntu1_i386.deb | grep Depends
 Depends: libtinfo5 (= 6.0+20160213-1ubuntu1), libc6 (>= 2.4)

As you can see, the amd64 version indicates a libc6 version of 2.14 or
greater, but the i386 version says 2.4 or greater. It would appear that
this is a typo, since it should match the amd64 case and that there is
no libc6 version in Ubuntu with that version number. Ubuntu Zesty has a
libc6 version of 2.24-7ubuntu2.

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

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

Title:
  libc6 Depends line for xenial i386 package appears to be incorrect.

Status in ncurses package in Ubuntu:
  New

Bug description:
  Upon inspecting the i386 and amd64 packages of libncurses5/xenial,
  there appears to be an error in the libc6 dependency for the i386
  case:

  $ dpkg -I libncurses5_6.0+20160213-1ubuntu1_amd64.deb | grep Depends
   Depends: libtinfo5 (= 6.0+20160213-1ubuntu1), libc6 (>= 2.14)
  $ dpkg -I libncurses5_6.0+20160213-1ubuntu1_i386.deb | grep Depends
   Depends: libtinfo5 (= 6.0+20160213-1ubuntu1), libc6 (>= 2.4)

  As you can see, the amd64 version indicates a libc6 version of 2.14 or
  greater, but the i386 version says 2.4 or greater. It would appear
  that this is a typo, since it should match the amd64 case and that
  there is no libc6 version in Ubuntu with that version number. Ubuntu
  Zesty has a libc6 version of 2.24-7ubuntu2.

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

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

[Touch-packages] [Bug 1661406] Re: apparmor failing to be purged on trusty

Thanks for the bug report! This only seems to affect the apparmor
package that was SRU'ed to trusty from xenial. Xenial doesn't look to be
affected.

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

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

** Also affects: apparmor (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  apparmor failing to be purged on trusty

Status in apparmor package in Ubuntu:
  Invalid
Status in apparmor source package in Trusty:
  Confirmed

Bug description:
  Version: 2.10.95-0ubuntu2.5~14.04.1

  When executing apt -y purge apparmor.

  The purge run but has errors as files do not exist and the rmdir fails
  to execute.

  rmdir: failed to remove '/var/lib/apparmor/profiles': No such file or
  directory

  Steps to reproduce:
  apt-get update
  apt-get -y install apparmor
  apt -y purge apparmor

  I will put workarounds in place for now in puppet but this is making
  puppet not like it..

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

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

[Touch-packages] [Bug 1661745] [NEW] ssh-keyscan does not exit with non-zero return code on error

2017-02-03 Thread Luke Browning

Public bug reported:

On xenial, ssh-keyscan returns zero indicating success, when the command
fails.

root@cp1:~# lsb_release -d
Description:Ubuntu 16.04.1 LTS

root@cp1:~# ssh-keyscan -H -t ssh-rsa bad-host
getaddrinfo bad-host: Name or service not known
root@cp1:~# echo $?
0

On trusty, the exit status is non-zero as expected.

root@integration-deployer:/home/ubuntu# lsb_release -d
Description:Ubuntu 14.04.5 LTS

root@integration-deployer:/home/ubuntu# ssh-keyscan -H -t ssh-rsa bad-host
getaddrinfo bad-host: Name or service not known
root@integration-deployer:/home/ubuntu# echo $?
255

This is a incompatibility between Ubuntu 14.04 and 16.04

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

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

Title:
  ssh-keyscan does not exit with non-zero return code on error

Status in openssh package in Ubuntu:
  New

Bug description:
  On xenial, ssh-keyscan returns zero indicating success, when the
  command fails.

  root@cp1:~# lsb_release -d
  Description:  Ubuntu 16.04.1 LTS

  root@cp1:~# ssh-keyscan -H -t ssh-rsa bad-host
  getaddrinfo bad-host: Name or service not known
  root@cp1:~# echo $?
  0

  On trusty, the exit status is non-zero as expected.

  root@integration-deployer:/home/ubuntu# lsb_release -d
  Description:  Ubuntu 14.04.5 LTS

  root@integration-deployer:/home/ubuntu# ssh-keyscan -H -t ssh-rsa bad-host
  getaddrinfo bad-host: Name or service not known
  root@integration-deployer:/home/ubuntu# echo $?
  255

  This is a incompatibility between Ubuntu 14.04 and 16.04

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

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

[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2017-02-03 Thread Ubuntu Foundations Team Bug Bot

The attachment "debdiff for pulseaudio: upload bell.ogg" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

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

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

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  This bug is about problems using the system bell in Unity or another
  Compiz-based environment.  For problems using the system bell in
  Ubuntu Classic/Metacity or another Metacity-based environment, please
  see bug #486154.

  The system bell (that beep when you backspace on an empty line on a
  terminal, i.e.) is badly broken using the Unity environment in the
  Natty beta 2.  By default, no sound is produced, and several
  misconfigurations make it difficult to produce sound either from the
  PC speaker or Pulse Audio's module-x11-bell.  Not knowing what the
  desired behavior is, I can't say exactly what needs to be fixed.  But
  the combination of the following issues makes the system quite
  obviously broken.

  1) pcskpr is blacklisted.
  The pcspkr module is necessary for the PC speaker to produce sound.  It is 
blacklisted, so regular users cannot turn the bell on.  It would be nice for 
this to be fixed, but the attitudes displayed in #77010 suggest that it won't 
be.  Nonetheless, I note it here because it interacts with some of the 
following.

  2) The X bell volume is set to 0.
  As reported by `xset q`, the bell volume is 0 when Unity is started.  Both 
the PC speaker and module-x11-bell respect this setting, so the volume must be 
turned up (with `xset b on` or `xset b 100`) for either to work.  Since both 
the PC speaker and module-x11-bell are disabled by default, this setting only 
serves to frustrate attempts to turn them on; it never prevents unwanted sound.

  3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11
  This is a system file, not a user file, so users cannot decide whether they 
want this module loaded or not.  They could write a script to unload the module 
at login (and hope the module number doesn't vary between boots), but it would 
be much cleaner to have the modules loaded from a user file, possibly with 
defaults if the user file doesn't exist.

  4) Sample bell.ogg is not loaded.
  When module-x11-bell is loaded, it is told to use the sample bell.ogg.  But 
no sample is loaded into Pulse Audio.  Thus, module-x11-bell traps system bell 
events (keeping them from going to the PC speaker) without producing any sound. 
 If module-x11-bell is loaded, the sample it calls on should be loaded as well. 
 (To fix this, run `pactl upload-sample 
/usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.)

  5) gnome-volume-control doesn't.
  The "Sound Effects" tab of gnome-volume-control offers to set the volume and 
sound for system bell events, but these have no effect.  This is because 
gnome-volume-control is trying to control system bells through metacity.  
Ideally, it should be rewritten to control module-x11-bell instead, but a 
temporary fix could be to simply disable this tab.

  6) System bell settings don't transfer to the Ubuntu Classic environment.
  Because that is using metacity, which has it's own set of problems.  See bug 
#486154.

  This has been from testing in a VM (virtualbox), but all of these
  behaviors have also been seen in Compiz in various previous versions
  of Ubuntu running on various hardware.

  I have reported this bug against several components, as it is really an 
integration issue.  The eventual fix may not involve your component, but please 
do not mark this bug as invalid until we have at least a roadmap for fixing it. 
 Otherwise, I fear responsibility will be passed from component to component 
without anything being fixed.  Rationales:
  Unity - As the overarching environment, Unity should be responsible for 
getting everything integrated.  Additionally, some of the problems relate to 
session startup settings.
  Pulse Audio - module-x11-bell is not loaded intelligently or correctly.
  Gnome Media - Own gnome-volume-control.

  Versions (but note the same behavior has been seen in many earlier versions):
  unity: 3.8.10-0ubuntu2
  pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3
  gnome-media: 2.32.0-0ubuntu7

To manage notifications about this bug go to:
https://bu

[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2435

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

Title:
  [regression] Nested server segfaults or rapidly logs exceptions when a
  fullscreen client starts [in mir_presentation_chain_set_dropping_mode
  ... std::exception::what: Operation not permitted]

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Nested server segfaults when a fullscreen client starts

  Using Mir 0.26.0 (zesty release):

  The client dies:

  [2017-02-03 15:05:44.315444]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76):
 Throw in function void mir::client::PromiseStateBase::break_promise() [with 
T = std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::error_info_injector
  std::exception::what: broken_promise

  Because the server died:

  Segmentation fault (core dumped)
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x7fcceb7b4003 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #2  0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fccec0e3a7a in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #4  0x7fccec09fd2d in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #5  0x7fccec09f018 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #6  0x7fccec0e2c79 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #7  0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #8  0x7fcce95326ca in start_thread (arg=0x7fccde2b4700)
  at pthread_create.c:333
  #9  0x7fccec4710ff in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

  However in development builds the server does not die and just floods
  the log instead:

  [2017-02-03 16:52:44.382460]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.399142]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.415823]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.432504]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  *** WORKAROUND ***
  Start your nested server with --nested-passthrough=OFF
  Which works on the 0.26.0 release, but not on anything newer because you'll 
then hit the more recent regression bug 1661521.

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

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

[Touch-packages] [Bug 1661521] Re: [regression] Windowed clients of nested servers are all black

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2435

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

Title:
  [regression] Windowed clients of nested servers are all black

Status in Mir:
  Triaged
Status in Mir 0.26 series:
  Triaged
Status in mir package in Ubuntu:
  Invalid

Bug description:
  [regression] Windowed clients of nested servers are all black

  FAILING:
  lp:mir r4008
  lp:mir/0.26 r4005

  WORKING:
  Mir 0.26.0 zesty binaries (lp:mir/0.26 r3994)
  lp:mir/0.25 r3822

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

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

[Touch-packages] [Bug 1661521] Re: [regression] Windowed clients of nested servers are all black

** Branch linked: lp:mir/0.26

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

Title:
  [regression] Windowed clients of nested servers are all black

Status in Mir:
  Triaged
Status in Mir 0.26 series:
  Triaged
Status in mir package in Ubuntu:
  Invalid

Bug description:
  [regression] Windowed clients of nested servers are all black

  FAILING:
  lp:mir r4008
  lp:mir/0.26 r4005

  WORKING:
  Mir 0.26.0 zesty binaries (lp:mir/0.26 r3994)
  lp:mir/0.25 r3822

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

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

[Touch-packages] [Bug 1661694] [NEW] Desktop

2017-02-03 Thread patrick grech

Public bug reported:

And I have a problem with desktop. It remains on Cinnamon. I have not
the session page with the 3 choices : Cinnamon, Mate, Ubuntu. The
installs on terminal are inoperant.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  370.28  Thu Sep  1 19:45:04 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Feb  3 18:13:55 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed
 nvidia-370, 370.28, 4.4.0-59-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics 
Controller [1043:178d]
   Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 930M] [1043:178d]
InstallationDate: Installed on 2016-12-09 (55 days ago)
InstallationMedia: cubuntu 16.04.1 217c Nvidia - Release amd64
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
 Bus 001 Device 005: ID 13d3:3408 IMC Networks 
 Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X550JF
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=UUID=49238169-3e22-4b43-a3a7-c49e1ca89ce8 ro plymouth:debug drm.debug=0xe 
nopat
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/31/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550JF.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550JF
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JF.208:bd10/31/2015:svnASUSTeKCOMPUTERINC.:pnX550JF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X550JF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Feb  3 17:22:39 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  Desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  And I have a problem with desktop. It remains on Cinnamon. I have not
  the session page with the 3 choices : Cinnamon, Mate, Ubuntu. The
  installs on terminal are inoperant.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  370.28  Thu Sep  1 19:45:04 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~1

[Touch-packages] [Bug 1661521] Re: [regression] Windowed clients of nested servers are all black

** Branch linked: lp:~kdub/mir/fix-1661521-0.26.1

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

Title:
  [regression] Windowed clients of nested servers are all black

Status in Mir:
  Triaged
Status in Mir 0.26 series:
  Triaged
Status in mir package in Ubuntu:
  Invalid

Bug description:
  [regression] Windowed clients of nested servers are all black

  FAILING:
  lp:mir r4008
  lp:mir/0.26 r4005

  WORKING:
  Mir 0.26.0 zesty binaries (lp:mir/0.26 r3994)
  lp:mir/0.25 r3822

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

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

[Touch-packages] [Bug 1661719] Re: package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: package libfaad2:amd64 is already installed and configured

2017-02-03 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade:
  package libfaad2:amd64 is already installed and configured

Status in faad2 package in Ubuntu:
  New

Bug description:
  IDK issue says to report.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libfaad2:amd64 2.8.0~cvs20150510-1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Feb  3 23:18:42 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu5
  DuplicateSignature:
   package:libfaad2:amd64:2.8.0~cvs20150510-1
   Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
   dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
package chromium-codecs-ffmpeg-extra is already installed and configured
  ErrorMessage: package libfaad2:amd64 is already installed and configured
  InstallationDate: Installed on 2017-02-02 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: faad2
  Title: package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: 
package libfaad2:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661521] Re: [regression] Windowed clients of nested servers are all black

pixel format was not communicated properly all the way back to the
client buffers. This resulted in the nested server's EGLClientBuffer
image import failing, only in the mesa platform.

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

Title:
  [regression] Windowed clients of nested servers are all black

Status in Mir:
  Triaged
Status in Mir 0.26 series:
  Triaged
Status in mir package in Ubuntu:
  Invalid

Bug description:
  [regression] Windowed clients of nested servers are all black

  FAILING:
  lp:mir r4008
  lp:mir/0.26 r4005

  WORKING:
  Mir 0.26.0 zesty binaries (lp:mir/0.26 r3994)
  lp:mir/0.25 r3822

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

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

[Touch-packages] [Bug 1661719] [NEW] package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: package libfaad2:amd64 is already installed and configured

2017-02-03 Thread Manu Srivastava

Public bug reported:

IDK issue says to report.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libfaad2:amd64 2.8.0~cvs20150510-1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Fri Feb  3 23:18:42 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu5
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu5
DuplicateSignature:
 package:libfaad2:amd64:2.8.0~cvs20150510-1
 Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
 dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
  package chromium-codecs-ffmpeg-extra is already installed and configured
ErrorMessage: package libfaad2:amd64 is already installed and configured
InstallationDate: Installed on 2017-02-02 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: faad2
Title: package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: 
package libfaad2:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade:
  package libfaad2:amd64 is already installed and configured

Status in faad2 package in Ubuntu:
  New

Bug description:
  IDK issue says to report.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libfaad2:amd64 2.8.0~cvs20150510-1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Feb  3 23:18:42 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu5
  DuplicateSignature:
   package:libfaad2:amd64:2.8.0~cvs20150510-1
   Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
   dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
package chromium-codecs-ffmpeg-extra is already installed and configured
  ErrorMessage: package libfaad2:amd64 is already installed and configured
  InstallationDate: Installed on 2017-02-02 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: faad2
  Title: package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: 
package libfaad2:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2017-02-03 Thread Peter Draksler

Seeing the same on a fresh (as of last week) Xubuntu 16.04 install
(4.4.0-62-generic) with all the latest updates;

Feb  3 14:07:17 vader systemd[1]: Started CUPS Scheduler.
Feb  3 14:07:17 vader colord[1453]: (colord:1453): Cd-WARNING **: failed to get 
session [pid 6191]: No such device or address
Feb  3 14:07:17 vader colord[1453]: (colord:1453): Cd-WARNING **: failed to get 
session [pid 6191]: No such device or address

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1661716] [NEW] Domain names not resolving on bootup

2017-02-03 Thread Tom Magee

Public bug reported:

I just installed Ubuntu 16.10 on my System76 Pangolin Performance
laptop. After bootup, connecting to the internet via a WiFi connection,
both Chromium and Firefox failed to resolve any domain names (cnn.com,
google.com, etc.) I entered into the browser. I at first thought that my
internet connection was not working, so I opened up a terminal and
entered "ping 8.8.8.8" and was surprised to see that the ping attempt
was successful. However, when I tried to ping a domain name
(google.com), I was not successful.

I then entered "sudo service systemd-resolved restart" and the problem
was resolved.

This is a recurring problem. Every time I start up my laptop I have to
restart systemd-resolved or else both the browser and command line are
unable to resolve domain names.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb  3 14:00:57 2017
InstallationDate: Installed on 2017-02-02 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: System76, Inc. Pangolin Performance
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic 
root=UUID=ed0fb709-9a93-4ef8-957b-58dcd639c8a6 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Pangolin Performance
dmi.board.vendor: System76, Inc.
dmi.board.version: panp8
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: panp8
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/12/2011:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp8:rvnSystem76,Inc.:rnPangolinPerformance:rvrpanp8:cvnSystem76,Inc.:ct9:cvrpanp8:
dmi.product.name: Pangolin Performance
dmi.product.version: panp8
dmi.sys.vendor: System76, Inc.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Domain names not resolving on bootup

Status in systemd package in Ubuntu:
  New

Bug description:
  I just installed Ubuntu 16.10 on my System76 Pangolin Performance
  laptop. After bootup, connecting to the internet via a WiFi
  connection, both Chromium and Firefox failed to resolve any domain
  names (cnn.com, google.com, etc.) I entered into the browser. I at
  first thought that my internet connection was not working, so I opened
  up a terminal and entered "ping 8.8.8.8" and was surprised to see that
  the ping attempt was successful. However, when I tried to ping a
  domain name (google.com), I was not successful.

  I then entered "sudo service systemd-resolved restart" and the problem
  was resolved.

  This is a recurring problem. Every time I start up my laptop I have to
  restart systemd-resolved or else both the browser and command line are
  unable to resolve domain names.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  3 14:00:57 2017
  InstallationDate: Installed on 2017-02-02 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: System76, Inc. Pangolin Performance
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic 
root=UUID=ed0fb709-9a93-4ef8-957b-58dcd639c8a6 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Pangolin Performance
  dmi.board.vendor: System76, Inc.
  dmi.board.version: panp8
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: panp8
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/12/2011:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp8:rvnSystem76,Inc.:rnPangolinPerformance:rvrpanp8:cvnSystem76,Inc.:ct9:cvrpanp8:
  dmi.product.name: Pangolin Performance
  dmi.product.version: panp8
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what

2017-02-03 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   Status: Triaged => Fix Committed

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

Title:
  [regression] Nested server segfaults or rapidly logs exceptions when a
  fullscreen client starts [in mir_presentation_chain_set_dropping_mode
  ... std::exception::what: Operation not permitted]

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Nested server segfaults when a fullscreen client starts

  Using Mir 0.26.0 (zesty release):

  The client dies:

  [2017-02-03 15:05:44.315444]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76):
 Throw in function void mir::client::PromiseStateBase::break_promise() [with 
T = std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::error_info_injector
  std::exception::what: broken_promise

  Because the server died:

  Segmentation fault (core dumped)
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x7fcceb7b4003 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #2  0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fccec0e3a7a in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #4  0x7fccec09fd2d in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #5  0x7fccec09f018 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #6  0x7fccec0e2c79 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #7  0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #8  0x7fcce95326ca in start_thread (arg=0x7fccde2b4700)
  at pthread_create.c:333
  #9  0x7fccec4710ff in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

  However in development builds the server does not die and just floods
  the log instead:

  [2017-02-03 16:52:44.382460]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.399142]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.415823]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.432504]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  *** WORKAROUND ***
  Start your nested server with --nested-passthrough=OFF
  Which works on the 0.26.0 release, but not on anything newer because you'll 
then hit the more recent regression bug 1661521.

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

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

[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2017-02-03 Thread Iiro Laiho

Present in 16.04.

Is the silence of the X11 bell intentional behavior? This is a really
weird case. I mean, the bug has been open for longer than half a decade
and triaged for a couple of years as well. The fix also is very simple
and there are proposed patches.

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

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  This bug is about problems using the system bell in Unity or another
  Compiz-based environment.  For problems using the system bell in
  Ubuntu Classic/Metacity or another Metacity-based environment, please
  see bug #486154.

  The system bell (that beep when you backspace on an empty line on a
  terminal, i.e.) is badly broken using the Unity environment in the
  Natty beta 2.  By default, no sound is produced, and several
  misconfigurations make it difficult to produce sound either from the
  PC speaker or Pulse Audio's module-x11-bell.  Not knowing what the
  desired behavior is, I can't say exactly what needs to be fixed.  But
  the combination of the following issues makes the system quite
  obviously broken.

  1) pcskpr is blacklisted.
  The pcspkr module is necessary for the PC speaker to produce sound.  It is 
blacklisted, so regular users cannot turn the bell on.  It would be nice for 
this to be fixed, but the attitudes displayed in #77010 suggest that it won't 
be.  Nonetheless, I note it here because it interacts with some of the 
following.

  2) The X bell volume is set to 0.
  As reported by `xset q`, the bell volume is 0 when Unity is started.  Both 
the PC speaker and module-x11-bell respect this setting, so the volume must be 
turned up (with `xset b on` or `xset b 100`) for either to work.  Since both 
the PC speaker and module-x11-bell are disabled by default, this setting only 
serves to frustrate attempts to turn them on; it never prevents unwanted sound.

  3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11
  This is a system file, not a user file, so users cannot decide whether they 
want this module loaded or not.  They could write a script to unload the module 
at login (and hope the module number doesn't vary between boots), but it would 
be much cleaner to have the modules loaded from a user file, possibly with 
defaults if the user file doesn't exist.

  4) Sample bell.ogg is not loaded.
  When module-x11-bell is loaded, it is told to use the sample bell.ogg.  But 
no sample is loaded into Pulse Audio.  Thus, module-x11-bell traps system bell 
events (keeping them from going to the PC speaker) without producing any sound. 
 If module-x11-bell is loaded, the sample it calls on should be loaded as well. 
 (To fix this, run `pactl upload-sample 
/usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.)

  5) gnome-volume-control doesn't.
  The "Sound Effects" tab of gnome-volume-control offers to set the volume and 
sound for system bell events, but these have no effect.  This is because 
gnome-volume-control is trying to control system bells through metacity.  
Ideally, it should be rewritten to control module-x11-bell instead, but a 
temporary fix could be to simply disable this tab.

  6) System bell settings don't transfer to the Ubuntu Classic environment.
  Because that is using metacity, which has it's own set of problems.  See bug 
#486154.

  This has been from testing in a VM (virtualbox), but all of these
  behaviors have also been seen in Compiz in various previous versions
  of Ubuntu running on various hardware.

  I have reported this bug against several components, as it is really an 
integration issue.  The eventual fix may not involve your component, but please 
do not mark this bug as invalid until we have at least a roadmap for fixing it. 
 Otherwise, I fear responsibility will be passed from component to component 
without anything being fixed.  Rationales:
  Unity - As the overarching environment, Unity should be responsible for 
getting everything integrated.  Additionally, some of the problems relate to 
session startup settings.
  Pulse Audio - module-x11-bell is not loaded intelligently or correctly.
  Gnome Media - Own gnome-volume-control.

  Versions (but note the same behavior has been seen in many earlier versions):
  unity: 3.8.10-0ubuntu2
  pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3
  gnome-media: 2.32.0-0ubuntu7

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

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

[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression

2017-02-03 Thread Louis Bouchard

Hello,

Just to clarify something that I have just realized using :

$ pyperformance run -p={some python} means that {some python} will be
used to run PYPERFORMANCE, not to run the benchmarks !!! So changing -p
to use different builds of python will not run proper comparaison of the
different builds.

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

Title:
Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
Confirmed

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

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

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

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

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

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

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

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

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

Re: [Touch-packages] [Bug 1661575] Re: printer

rehi
I forgot to ask you how do I proceed to cancel the bug report 1661575 which
appears each time I connect the pc. Kafka again!!!tks   cheers  jacques
 and sorry for the trouble

2017-02-03 12:43 GMT+01:00 Paul White <1661...@bugs.launchpad.net>:

> You might find https://wiki.ubuntu.com/DebuggingPrintingProblems
> helpful.
>
> ** Package changed: xorg (Ubuntu) => cups (Ubuntu)
>
> ** Summary changed:
>
> - printer
> + printer doesn't print anymore
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1661575
>
> Title:
>   printer doesn't print anymore
>
> Status in cups package in Ubuntu:
>   New
>
> Bug description:
>   printer doesn't print anymore
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
>   Uname: Linux 4.4.0-62-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.5
>   Architecture: amd64
>   CompizPlugins: No value set for `/apps/compiz-1/general/
> screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   Date: Fri Feb  3 12:02:19 2017
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD
> 4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
>  Subsystem: Samsung Electronics Co Ltd RV710/M92 [Mobility Radeon HD
> 4530/4570/545v] [144d:c07f]
>   InstallationDate: Installed on 2016-07-06 (212 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   MachineType: SAMSUNG ELECTRONICS CO., LTD. R540/R580/R780/SA41/E452/E852
>   ProcEnviron:
>LANGUAGE=fr_FR
>PATH=(custom, no user)
>LANG=fr_FR.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic
> root=UUID=4915e0c4-9b44-4791-91a6-f7ea13097772 ro quiet splash
> vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 09/27/2010
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 03KP.M008.20100927.LDG
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: R540/R580/R780/SA41/E452/E852
>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.board.version: 03KP
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.chassis.version: N/A
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr03KP.M008.20100927.LDG:
> bd09/27/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR540/R580/R780/SA41/E452/
> E852:pvr03KP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR540/R580/R780/SA41/E452/
> E852:rvr03KP:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
>   dmi.product.name: R540/R580/R780/SA41/E452/E852
>   dmi.product.version: 03KP
>   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>   xserver.bootTime: Fri Feb  3 11:54:03 2017
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.18.4-0ubuntu0.2
>   xserver.video_driver: radeon
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1661575/+subscriptions
>

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

Title:
  printer doesn't print anymore

Status in cups package in Ubuntu:
  New

Bug description:
  printer doesn't print anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Feb  3 12:02:19 2017
  DistUpgraded: Fre

[Touch-packages] [Bug 1661690] [NEW] Reload page shortcut not working in u8

Public bug reported:

the keyboard shortcuts for reloading a page are not working in unity8 (ctrl-r 
and f5)
they work fine in u7
most other shortcuts I've tried in u8 work

** Affects: webbrowser-app (Ubuntu)
 Importance: High
 Status: New

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

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

Title:
  Reload page shortcut not working in u8

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  the keyboard shortcuts for reloading a page are not working in unity8 (ctrl-r 
and f5)
  they work fine in u7
  most other shortcuts I've tried in u8 work

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

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

[Touch-packages] [Bug 1661691] [NEW] TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

2017-02-03 Thread Scott Moser

Public bug reported:

I quite often have the following work flow:

a.) lxc launch ubuntu-daily:zesty z1
b.) lxc exec z1 /bin/bash
c.) % vi foo.txt
d.) paste some thing from my X buffer (hit middle mouse button).

Somewhere between yakkety (2:7.4.1829-1ubuntu2.1) and zesty
(2:8.0.0095-1ubuntu2) this behavior changed.

Previously this all worked fine.

Now, in zesty, however an attempt to paste results in a vi error message:
 E353: Nothing in register "

to fix this, you can first disable the mouse 'a' [1]

 : set mouse-=a


I'm not sure what is enabling this, because /usr/share/vim/vimrc has the line
set mouse=a commented out.

--
[1] 
http://www.varesano.net/blog/fabio/disable%20vim%20automatic%20visual%20mode%20using%20mouse

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: vim-nox 2:8.0.0095-1ubuntu2
ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
Uname: Linux 4.9.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb  3 12:14:20 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (561 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
SourcePackage: vim
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

Status in vim package in Ubuntu:
  New

Bug description:
  I quite often have the following work flow:

  a.) lxc launch ubuntu-daily:zesty z1
  b.) lxc exec z1 /bin/bash
  c.) % vi foo.txt
  d.) paste some thing from my X buffer (hit middle mouse button).

  Somewhere between yakkety (2:7.4.1829-1ubuntu2.1) and zesty
  (2:8.0.0095-1ubuntu2) this behavior changed.

  Previously this all worked fine.

  Now, in zesty, however an attempt to paste results in a vi error message:
   E353: Nothing in register "

  to fix this, you can first disable the mouse 'a' [1]

   : set mouse-=a

  
  I'm not sure what is enabling this, because /usr/share/vim/vimrc has the line
  set mouse=a commented out.

  --
  [1] 
http://www.varesano.net/blog/fabio/disable%20vim%20automatic%20visual%20mode%20using%20mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: vim-nox 2:8.0.0095-1ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  3 12:14:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (561 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1661575] Re: printer

re hi
 I forgot to ask you how do I proceed to cancel the bug report 1661575
which appears each time I connect the pc . Kafka again!!!tks   cheers
jacques

2017-02-03 17:18 GMT+01:00 jacques gorisse :

> hi
> tks for your mail. I got after" sudo tail-f/var/log/syslolog" the answer
> "commande introuvable" which means command not found. I don't know what to
> do specially now when the printer not only doesn't print when I want to
> but print all the pc files automatically, when connected, without me asking
> for it!!! It is Kafka. I am considering either using the printer only for
> copyworks or turning back to windows with much regrets
> cheers & tks for your help  jacques
>
> 2017-02-03 12:43 GMT+01:00 Paul White <1661...@bugs.launchpad.net>:
>
>> You might find https://wiki.ubuntu.com/DebuggingPrintingProblems
>> helpful.
>>
>> ** Package changed: xorg (Ubuntu) => cups (Ubuntu)
>>
>> ** Summary changed:
>>
>> - printer
>> + printer doesn't print anymore
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1661575
>>
>> Title:
>>   printer doesn't print anymore
>>
>> Status in cups package in Ubuntu:
>>   New
>>
>> Bug description:
>>   printer doesn't print anymore
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 16.04
>>   Package: xorg 1:7.7+13ubuntu3
>>   ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
>>   Uname: Linux 4.4.0-62-generic x86_64
>>   .tmp.unity_support_test.0:
>>
>>   ApportVersion: 2.20.1-0ubuntu2.5
>>   Architecture: amd64
>>   CompizPlugins: No value set for `/apps/compiz-1/general/screen
>> 0/options/active_plugins'
>>   CompositorRunning: compiz
>>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>>   CompositorUnredirectFSW: true
>>   Date: Fri Feb  3 12:02:19 2017
>>   DistUpgraded: Fresh install
>>   DistroCodename: xenial
>>   DistroVariant: ubuntu
>>   GraphicsCard:
>>Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD
>> 4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
>>  Subsystem: Samsung Electronics Co Ltd RV710/M92 [Mobility Radeon HD
>> 4530/4570/545v] [144d:c07f]
>>   InstallationDate: Installed on 2016-07-06 (212 days ago)
>>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
>> (20160420.1)
>>   MachineType: SAMSUNG ELECTRONICS CO., LTD. R540/R580/R780/SA41/E452/E852
>>   ProcEnviron:
>>LANGUAGE=fr_FR
>>PATH=(custom, no user)
>>LANG=fr_FR.UTF-8
>>SHELL=/bin/bash
>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic
>> root=UUID=4915e0c4-9b44-4791-91a6-f7ea13097772 ro quiet splash
>> vt.handoff=7
>>   SourcePackage: xorg
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 09/27/2010
>>   dmi.bios.vendor: American Megatrends Inc.
>>   dmi.bios.version: 03KP.M008.20100927.LDG
>>   dmi.board.asset.tag: To be filled by O.E.M.
>>   dmi.board.name: R540/R580/R780/SA41/E452/E852
>>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>>   dmi.board.version: 03KP
>>   dmi.chassis.asset.tag: No Asset Tag
>>   dmi.chassis.type: 9
>>   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>>   dmi.chassis.version: N/A
>>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:
>> bvr03KP.M008.20100927.LDG:bd09/27/2010:svnSAMSUNGELECTRONICS
>> CO.,LTD.:pnR540/R580/R780/SA41/E452/E852:pvr03KP:rvnSAMS
>> UNGELECTRONICSCO.,LTD.:rnR540/R580/R780/SA41/E452/E852:
>> rvr03KP:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
>>   dmi.product.name: R540/R580/R780/SA41/E452/E852
>>   dmi.product.version: 03KP
>>   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
>>   version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>>   version.ia32-libs: ia32-libs N/A
>>   version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
>>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
>>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>>   version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
>>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
>>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
>> 1:1.0.12-1build2
>>   xserver.bootTime: Fri Feb  3 11:54:03 2017
>>   xserver.configfile: default
>>   xserver.errors:
>>
>>   xserver.logfile: /var/log/Xorg.0.log
>>   xserver.version: 2:1.18.4-0ubuntu0.2
>>   xserver.video_driver: radeon
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1661575/
>> +subscriptions
>>
>
>

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

Title:
  printer doesn't print anymore

Status

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

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

** Information type changed from Private Security to Public

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

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

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: ca-certificates 20161130
  Uname: Linux 4.9.6-040906-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  Date: Fri Jan 27 22:09:16 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-01-27 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4~beta4ubuntu1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20161130 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2017-02-03 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

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

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: ca-certificates 20161130
  Uname: Linux 4.9.6-040906-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  Date: Fri Jan 27 22:09:16 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-01-27 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4~beta4ubuntu1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20161130 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what

** Branch linked: lp:mir/0.26

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

Title:
  [regression] Nested server segfaults or rapidly logs exceptions when a
  fullscreen client starts [in mir_presentation_chain_set_dropping_mode
  ... std::exception::what: Operation not permitted]

Status in Mir:
  Triaged
Status in Mir 0.26 series:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Nested server segfaults when a fullscreen client starts

  Using Mir 0.26.0 (zesty release):

  The client dies:

  [2017-02-03 15:05:44.315444]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76):
 Throw in function void mir::client::PromiseStateBase::break_promise() [with 
T = std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::error_info_injector
  std::exception::what: broken_promise

  Because the server died:

  Segmentation fault (core dumped)
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x7fcceb7b4003 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #2  0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fccec0e3a7a in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #4  0x7fccec09fd2d in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #5  0x7fccec09f018 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #6  0x7fccec0e2c79 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #7  0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #8  0x7fcce95326ca in start_thread (arg=0x7fccde2b4700)
  at pthread_create.c:333
  #9  0x7fccec4710ff in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

  However in development builds the server does not die and just floods
  the log instead:

  [2017-02-03 16:52:44.382460]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.399142]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.415823]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.432504]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  *** WORKAROUND ***
  Start your nested server with --nested-passthrough=OFF
  Which works on the 0.26.0 release, but not on anything newer because you'll 
then hit the more recent regression bug 1661521.

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

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

[Touch-packages] [Bug 1660109] Re: [, Realtek ALC880, Green Headphone Out, Front] No sound at all

** Information type changed from Private Security to Public

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

Title:
  [, Realtek ALC880, Green Headphone Out, Front] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the on screen volume icon is red with a red cross

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jeffrey2370 F...m pulseaudio
   /dev/snd/controlC0:  jeffrey2370 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jan 29 08:05:14 2017
  InstallationDate: Installed on 2017-01-28 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jeffrey2370 F...m pulseaudio
   /dev/snd/controlC0:  jeffrey2370 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [, Realtek ALC880, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2005
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EV91510A.86A.0444.2005.0429.2108
  dmi.board.name: D915GEV
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC63667-503
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEV91510A.86A.0444.2005.0429.2108:bd04/29/2005:svn:pn:pvr:rvnIntelCorporation:rnD915GEV:rvrAAC63667-503:cvn:ct2:cvr:

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

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

[Touch-packages] [Bug 1660143] Re: Cannot download updates

Hi Gordon - Thanks for the bug report! I don't see anything related to
an inability to download updates. The only errors that I see in the
information attached to this bug report is that the nvidia driver cannot
be loaded but the nouveau driver is successfully loaded so I don't think
that should be giving you any problems.

Please provide some more information about what errors you're seeing
when you can't download updates. Thanks!

** Information type changed from Private Security to Public

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

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

Title:
  Cannot download updates

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  unable to down load updates

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Jan 29 14:52:08 2017
  DistUpgraded: 2016-08-09 15:14:27,074 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] 
[1043:83a4]
  InstallationDate: Installed on 2012-09-29 (1583 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=6eb98a42-bc12-42f1-992b-97782d05bb24 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-09 (173 days ago)
  dmi.bios.date: 01/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N68T-M-LE-V2
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-LE-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Jan 29 14:24:43 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-0ubuntu0.2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1660111] Re: PCI/internal sound card not detected

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

** Information type changed from Private Security to Public

** This bug has been marked a duplicate of bug 1660109
   [, Realtek ALC880, Green Headphone Out, Front] No sound at all

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  speaker icon on desktop is red with a red X at the side of it- sound
  was ok this was fixed once but has returned to red

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jeffrey2370 F...m pulseaudio
   /dev/snd/controlC0:  jeffrey2370 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jan 29 08:17:05 2017
  InstallationDate: Installed on 2017-01-28 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2005
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EV91510A.86A.0444.2005.0429.2108
  dmi.board.name: D915GEV
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC63667-503
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEV91510A.86A.0444.2005.0429.2108:bd04/29/2005:svn:pn:pvr:rvnIntelCorporation:rnD915GEV:rvrAAC63667-503:cvn:ct2:cvr:

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

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

[Touch-packages] [Bug 1660844] Re: SRU of LXC 2.0.7 (upstream bugfix release)

2017-02-03 Thread Brian Murray

Hello Stéphane, or anyone else affected,

Accepted lxc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.7-0ubuntu1~16.04.1 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: lxc (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  SRU of LXC 2.0.7 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed
Status in lxc source package in Yakkety:
  Fix Committed

Bug description:
  LXC upstream released LXC 2.0.7 as a bugfix release with following changelog:
   - attach: Close lsm label file descriptor
   - attach: Non-functional changes
   - attach: Simplify lsm_openat()
   - caps: Add lxc_cap_is_set()
   - conf: attach: Save errno across call to close
   - conf: Clearly report to either use drop or keep
   - conf: criu: Add make_anonymous_mount_file()
   - conf: Fix suggest_default_idmap()
   - configure: Add --enable-gnutls option
   - configure: Check for memfd_create()
   - configure: Check whether gettid() is declared
   - configure: Do not allow variable length arrays
   - configure: Remove -Werror=vla
   - configure: Use AC_HEADER_MAJOR to detect major()/minor()/makedev()
   - conf: Non-functional changes
   - conf: Remove thread-unsafe strsignal + improve log
   - init: Add cgroupfs-mount to Should-Start/Stop sysvinit LSB headers
   - log: Add lxc_unix_epoch_to_utc()
   - log: Annotate lxc_unix_epoch_to_utc()
   - log: Drop all timezone conversion functions
   - log: Make sure that date is correctly formatted
   - log: Use lxc_unix_epoch_to_utc()
   - log: Use N/A if getpid() != gettid() when threaded
   - log: Use thread-safe localtime_r()
   - lvm: Suppress warnings about leaked files
   - lxccontainer: Log failure to send sig to init pid
   - monitor: Add more logging
   - monitor: Close mainloop on exit if we opened it
   - monitor: Improve log + set log level to DEBUG
   - monitor: Log which pipe fd is currently used
   - monitor: Make lxc-monitord async signal safe
   - monitor: Non-functional changes
   - python3-lxc: Fix api_test.py on s390x
   - start: Check for CAP_SETGID before setgroups()
   - start: Fix execute and improve setgroups() calls
   - state: Use async signal safe fun in lxc_wait()
   - templates: lxc-debian: Don't try to get stuff from /usr/lib/systemd on the 
host
   - templates: lxc-debian: Fix getty service startup
   - templates: lxc-debian: Fix typo in calling dpkg with 
--print-foreign-architectures option
   - templates: lxc-debian: Handle ppc hostarch -> powerpc
   - templates: lxc-opensuse: Change openSUSE default release to Leap 42.2
   - templates: lxc-opensuse: Remove libgcc_s1
   - templates: lxc-opensuse: Remove poweroff.target -> sigpwr.target copy
   - templates: lxc-opensuse: Set to be unconfined by AppArmor
   - templates: lxc-opensuse: Update for Leap 42.2
   - tests; Don't cause test failures on cleanup errors
   - tests: Skip unpriv tests on broken overlay module
   - tools: Improve logging
   - tools: lxc-start: Remove c->is_defined(c) check
   - tools: lxc-start: Set configfile after load_config
   - tools: Only check for O_RDONLY
   - tree-wide: Random macro cleanups
   - tree-wide: Remove any variable length arrays
   - tree-wide: Sic semper assertis!
   - utils: Add macro __LXC_NUMSTRLEN
   - utils: Add uid, gid, group convenience wrappers

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 2.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Zesty and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the minor upstream bugfix release allowance

[Touch-packages] [Bug 1661675] Re: too hard to tell which window will be selected in alt-tab window switcher

** Changed in: ubuntu-ux
 Assignee: (unassigned) => Teresa Vasi (teresa.vasi)

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

Title:
  too hard to tell which window will be selected in alt-tab window
  switcher

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

Bug description:
  I find it really difficult to tell which window will be selected when
  alt-tabbing through my window list on Unity8. The highlighting of the
  selection is very subtle and there is not change to the window preview
  or the icon. I thought it would get easier after using unity8 a lot
  but it really hasn't.

  I think the following tweaks would make it much more clear which window is 
selected:
  1) The app icon at the bottom should get bigger or some effect applied to it 
when the app window is selected. My eyes tend to look there as it's less 
cluttered than the window preview list
  2) Make the border around the selected window preview thicker/darker to make 
it stand out more as currently the border highlighting is very subtle
  And/Or
  3) Make the actual window preview larger (or some other effect to make it 
move forward) for the selected window so that it's super clear which window is 
selected.

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

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

[Touch-packages] [Bug 1660844] Re: SRU of LXC 2.0.7 (upstream bugfix release)

2017-02-03 Thread Brian Murray

Hello Stéphane, or anyone else affected,

Accepted lxc into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.7-0ubuntu1~16.10.1 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: lxc (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  SRU of LXC 2.0.7 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed
Status in lxc source package in Yakkety:
  Fix Committed

Bug description:
  LXC upstream released LXC 2.0.7 as a bugfix release with following changelog:
   - attach: Close lsm label file descriptor
   - attach: Non-functional changes
   - attach: Simplify lsm_openat()
   - caps: Add lxc_cap_is_set()
   - conf: attach: Save errno across call to close
   - conf: Clearly report to either use drop or keep
   - conf: criu: Add make_anonymous_mount_file()
   - conf: Fix suggest_default_idmap()
   - configure: Add --enable-gnutls option
   - configure: Check for memfd_create()
   - configure: Check whether gettid() is declared
   - configure: Do not allow variable length arrays
   - configure: Remove -Werror=vla
   - configure: Use AC_HEADER_MAJOR to detect major()/minor()/makedev()
   - conf: Non-functional changes
   - conf: Remove thread-unsafe strsignal + improve log
   - init: Add cgroupfs-mount to Should-Start/Stop sysvinit LSB headers
   - log: Add lxc_unix_epoch_to_utc()
   - log: Annotate lxc_unix_epoch_to_utc()
   - log: Drop all timezone conversion functions
   - log: Make sure that date is correctly formatted
   - log: Use lxc_unix_epoch_to_utc()
   - log: Use N/A if getpid() != gettid() when threaded
   - log: Use thread-safe localtime_r()
   - lvm: Suppress warnings about leaked files
   - lxccontainer: Log failure to send sig to init pid
   - monitor: Add more logging
   - monitor: Close mainloop on exit if we opened it
   - monitor: Improve log + set log level to DEBUG
   - monitor: Log which pipe fd is currently used
   - monitor: Make lxc-monitord async signal safe
   - monitor: Non-functional changes
   - python3-lxc: Fix api_test.py on s390x
   - start: Check for CAP_SETGID before setgroups()
   - start: Fix execute and improve setgroups() calls
   - state: Use async signal safe fun in lxc_wait()
   - templates: lxc-debian: Don't try to get stuff from /usr/lib/systemd on the 
host
   - templates: lxc-debian: Fix getty service startup
   - templates: lxc-debian: Fix typo in calling dpkg with 
--print-foreign-architectures option
   - templates: lxc-debian: Handle ppc hostarch -> powerpc
   - templates: lxc-opensuse: Change openSUSE default release to Leap 42.2
   - templates: lxc-opensuse: Remove libgcc_s1
   - templates: lxc-opensuse: Remove poweroff.target -> sigpwr.target copy
   - templates: lxc-opensuse: Set to be unconfined by AppArmor
   - templates: lxc-opensuse: Update for Leap 42.2
   - tests; Don't cause test failures on cleanup errors
   - tests: Skip unpriv tests on broken overlay module
   - tools: Improve logging
   - tools: lxc-start: Remove c->is_defined(c) check
   - tools: lxc-start: Set configfile after load_config
   - tools: Only check for O_RDONLY
   - tree-wide: Random macro cleanups
   - tree-wide: Remove any variable length arrays
   - tree-wide: Sic semper assertis!
   - utils: Add macro __LXC_NUMSTRLEN
   - utils: Add uid, gid, group convenience wrappers

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 2.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Zesty and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the min

[Touch-packages] [Bug 1661675] [NEW] too hard to tell which window will be selected in alt-tab window switcher

Public bug reported:

I find it really difficult to tell which window will be selected when
alt-tabbing through my window list on Unity8. The highlighting of the
selection is very subtle and there is not change to the window preview
or the icon. I thought it would get easier after using unity8 a lot but
it really hasn't.

I think the following tweaks would make it much more clear which window is 
selected:
1) The app icon at the bottom should get bigger or some effect applied to it 
when the app window is selected. My eyes tend to look there as it's less 
cluttered than the window preview list
2) Make the border around the selected window preview thicker/darker to make it 
stand out more as currently the border highlighting is very subtle
And/Or
3) Make the actual window preview larger (or some other effect to make it move 
forward) for the selected window so that it's super clear which window is 
selected.

** Affects: ubuntu-ux
 Importance: High
 Assignee: Teresa Vasi (teresa.vasi)
 Status: New

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

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

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

** Changed in: ubuntu-ux
   Importance: Undecided => High

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

Title:
  too hard to tell which window will be selected in alt-tab window
  switcher

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

Bug description:
  I find it really difficult to tell which window will be selected when
  alt-tabbing through my window list on Unity8. The highlighting of the
  selection is very subtle and there is not change to the window preview
  or the icon. I thought it would get easier after using unity8 a lot
  but it really hasn't.

  I think the following tweaks would make it much more clear which window is 
selected:
  1) The app icon at the bottom should get bigger or some effect applied to it 
when the app window is selected. My eyes tend to look there as it's less 
cluttered than the window preview list
  2) Make the border around the selected window preview thicker/darker to make 
it stand out more as currently the border highlighting is very subtle
  And/Or
  3) Make the actual window preview larger (or some other effect to make it 
move forward) for the selected window so that it's super clear which window is 
selected.

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

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

[Touch-packages] [Bug 1661668] Re: multi-windows titles not being displayed in launcher popup menu

2017-02-03 Thread Michael Zanetti

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

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

Title:
  multi-windows titles not being displayed in launcher popup menu

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Expectation is for the launcher icon popup menus to be on parity with
  unity7 popup menus. Currently it is missing the window titles for
  multi window apps.

  Steps to repro:

  Open the webbrowser-app
  Via the menu, create a new window

  Expected Results:
  - browser icon in launcher should show 2 dots on left of icon
  - right clicking on browser icon should display popup menu listing the window 
titles of all browser windows that are open, selecting the title from the menu 
should bring that window to the foreground

  Actual Results:
  - browser icon in launcher shows 2 dots
  - popup menu does not show window titles

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

-- 
Mailing list: https://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 1661575] Re: printer

hi
tks for your mail. I got after" sudo tail-f/var/log/syslolog" the answer
"commande introuvable" which means command not found. I don't know what to
do specially now when the printer not only doesn't print when I want to
but print all the pc files automatically, when connected, without me asking
for it!!! It is Kafka. I am considering either using the printer only for
copyworks or turning back to windows with much regrets
cheers & tks for your help  jacques

2017-02-03 12:43 GMT+01:00 Paul White <1661...@bugs.launchpad.net>:

> You might find https://wiki.ubuntu.com/DebuggingPrintingProblems
> helpful.
>
> ** Package changed: xorg (Ubuntu) => cups (Ubuntu)
>
> ** Summary changed:
>
> - printer
> + printer doesn't print anymore
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1661575
>
> Title:
>   printer doesn't print anymore
>
> Status in cups package in Ubuntu:
>   New
>
> Bug description:
>   printer doesn't print anymore
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
>   Uname: Linux 4.4.0-62-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.5
>   Architecture: amd64
>   CompizPlugins: No value set for `/apps/compiz-1/general/
> screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   Date: Fri Feb  3 12:02:19 2017
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD
> 4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
>  Subsystem: Samsung Electronics Co Ltd RV710/M92 [Mobility Radeon HD
> 4530/4570/545v] [144d:c07f]
>   InstallationDate: Installed on 2016-07-06 (212 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   MachineType: SAMSUNG ELECTRONICS CO., LTD. R540/R580/R780/SA41/E452/E852
>   ProcEnviron:
>LANGUAGE=fr_FR
>PATH=(custom, no user)
>LANG=fr_FR.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic
> root=UUID=4915e0c4-9b44-4791-91a6-f7ea13097772 ro quiet splash
> vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 09/27/2010
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 03KP.M008.20100927.LDG
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: R540/R580/R780/SA41/E452/E852
>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.board.version: 03KP
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.chassis.version: N/A
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr03KP.M008.20100927.LDG:
> bd09/27/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR540/R580/R780/SA41/E452/
> E852:pvr03KP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR540/R580/R780/SA41/E452/
> E852:rvr03KP:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
>   dmi.product.name: R540/R580/R780/SA41/E452/E852
>   dmi.product.version: 03KP
>   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>   xserver.bootTime: Fri Feb  3 11:54:03 2017
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.18.4-0ubuntu0.2
>   xserver.video_driver: radeon
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1661575/+subscriptions
>

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

Title:
  printer doesn't print anymore

Status in cups package in Ubuntu:
  New

Bug description:
  printer doesn't print anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Archit

[Touch-packages] [Bug 1661668] [NEW] multi-windows titles not being displayed in launcher popup menu

Public bug reported:

Expectation is for the launcher icon popup menus to be on parity with
unity7 popup menus. Currently it is missing the window titles for multi
window apps.

Steps to repro:

Open the webbrowser-app
Via the menu, create a new window

Expected Results:
- browser icon in launcher should show 2 dots on left of icon
- right clicking on browser icon should display popup menu listing the window 
titles of all browser windows that are open, selecting the title from the menu 
should bring that window to the foreground

Actual Results:
- browser icon in launcher shows 2 dots
- popup menu does not show window titles

** Affects: unity8 (Ubuntu)
 Importance: Medium
 Assignee: Michael Zanetti (mzanetti)
 Status: Confirmed

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

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

Title:
  multi-windows titles not being displayed in launcher popup menu

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Expectation is for the launcher icon popup menus to be on parity with
  unity7 popup menus. Currently it is missing the window titles for
  multi window apps.

  Steps to repro:

  Open the webbrowser-app
  Via the menu, create a new window

  Expected Results:
  - browser icon in launcher should show 2 dots on left of icon
  - right clicking on browser icon should display popup menu listing the window 
titles of all browser windows that are open, selecting the title from the menu 
should bring that window to the foreground

  Actual Results:
  - browser icon in launcher shows 2 dots
  - popup menu does not show window titles

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

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

[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what

Why this crashes sometimes and other times spams is that wait_for_all()
is sometimes called on a nullptr MirWaitHandle. The first thing that fn
does is grab a lock. Some libc's seem smart enough to recognize that the
memory isn't there and throw system_error, but its pretty conceivable
that this could segfault if libc wasn't able to detect the memory issue
and throw.

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

Title:
  [regression] Nested server segfaults or rapidly logs exceptions when a
  fullscreen client starts [in mir_presentation_chain_set_dropping_mode
  ... std::exception::what: Operation not permitted]

Status in Mir:
  Triaged
Status in Mir 0.26 series:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Nested server segfaults when a fullscreen client starts

  Using Mir 0.26.0 (zesty release):

  The client dies:

  [2017-02-03 15:05:44.315444]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76):
 Throw in function void mir::client::PromiseStateBase::break_promise() [with 
T = std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::error_info_injector
  std::exception::what: broken_promise

  Because the server died:

  Segmentation fault (core dumped)
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x7fcceb7b4003 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #2  0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fccec0e3a7a in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #4  0x7fccec09fd2d in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #5  0x7fccec09f018 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #6  0x7fccec0e2c79 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #7  0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #8  0x7fcce95326ca in start_thread (arg=0x7fccde2b4700)
  at pthread_create.c:333
  #9  0x7fccec4710ff in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

  However in development builds the server does not die and just floods
  the log instead:

  [2017-02-03 16:52:44.382460]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.399142]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.415823]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.432504]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  *** WORKAROUND ***
  Start your nested server with --nested-passthrough=OFF
  Which works on the 0.26.0 release, but not on anything newer because you'll 
then hit the more recent regression bug 1661521.

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

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

[Touch-packages] [Bug 1661568] Re: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property

2017-02-03 Thread Dimitri John Ledkov

** Changed in: systemd (Ubuntu)
 Assignee: Alexandros Frantzis (afrantzis) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.02

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

Title:
  logind fails to emit change signal for
  org.freedesktop.login1.Seat.ActiveSession DBus property

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  logind fails to emit a DBus PropertiesChanged signal for the
  org.freedesktop.login1.Seat.ActiveSession DBus property. See
  https://github.com/systemd/systemd/issues/5210.

  This breaks repowerd on zesty since repowerd depends on this signal to
  track the active session.

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

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

[Touch-packages] [Bug 1655181] Re: P9 support in binutils

2017-02-03 Thread Breno Leitão

Sorry for the confusing here. The backporting word was used to backport
the patches to 17.04, since Canonical upgraded to a newer binutils, we
are good here.

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

Title:
  P9 support in binutils

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  New

Bug description:
  The upstream binutils (2.27 and trunk) is almost complete for POWER9,
  but unfortunately the changes expected to land in DD2 hardware have
  not yet been set in stone.  With that said, the remaining changes are
  fairly small and will only affect user space; there are no kernel
  dependencies on the unresolved architecture changes.


  == Comment: #3 - Peter E. Bergner  - 2016-11-01 10:43:16 
==
  Complete POWER9 support is upstream and exists in trunk and the binutils 2.27 
and 2.26 release branches.

  == Comment: #4 - Breno Henrique Leitao  - 2016-11-21 
12:45:53 ==
  (In reply to comment #3)
  > Complete POWER9 support is upstream and exists in trunk and the binutils
  > 2.27 and 2.26 release branches.

  Binutils version 2.27 is already in Ubuntu 17.04. Is there anything
  else required?

  == Comment: #5 - William J. Schmidt  - 2016-11-21 
13:32:50 ==
  (In reply to comment #4)
  > (In reply to comment #3)
  > > Complete POWER9 support is upstream and exists in trunk and the binutils
  > > 2.27 and 2.26 release branches.
  > 
  > Binutils version 2.27 is already in Ubuntu 17.04. Is there anything else
  > required?

  Well, as long as they pick up the backported fixes, nothing else is
  required.  That's what this feature is there to ensure.

  == Comment: #6 - Breno Henrique Leitao  - 2016-11-24 
06:52:51 ==
  Hi,

  > Well, as long as they pick up the backported fixes, nothing else is
  > required.  That's what this feature is there to ensure.

  Do you know, at this time, which are the fixes that will be requested
  to be backported?

  == Comment: #7 - William J. Schmidt  - 2016-11-28 
09:17:01 ==
  (In reply to comment #6)
  > Hi,
  > 
  > > Well, as long as they pick up the backported fixes, nothing else is
  > > required.  That's what this feature is there to ensure.
  > 
  > Do you know, at this time, which are the fixes that will be requested to be
  > backported?

  Peter, can you please respond to Breno's question?

  == Comment: #8 - Peter E. Bergner  - 2016-11-29 12:08:11 
==
  CC'ing Alan in case he has an extra input.

  Looking through the binutils-2_27-branch log, I see the following
  commits we would want picked up:

  commit 799b679496c98eb1f31625b00bb5db67a6f608d7
  Author: Peter Bergner 
  Date:   Fri Sep 16 16:17:46 2016 -0500

  Backport lastest POWER9 support to match final ISA 3.0 documentation.
  
  opcodes/
  Apply from master.
  2016-09-14  Peter Bergner 
  
  * ppc-opc.c (powerpc_opcodes) : New mnemonic.
  : Delete mnemonics.
  : Rename mnemonic from ...
  : ...to this.
  : Change to a X form instruction.
  : Change to 1 operand form.
  : Delete mnemonic.
  : Rename mnemonic from ...
  : ...to this.
  : Delete mnemonics.
  : Rename mnemonic from ...
  : ...to this.
  
  gas/
  Apply from master.
  2016-09-14  Peter Bergner 
  
  * testsuite/gas/ppc/power9.d  New tests.
  : Remove 
tests.
  : Update tests.
  * testsuite/gas/ppc/power9.s: Likewise.

  commit c6a7c521c14e0cc188ccc0388e0d5d21c2042c94
  Author: Alan Modra 
  Date:   Thu Sep 1 14:56:52 2016 +0930

  Don't treat .opd section specially when ELFv2
  
  Fixes a gdb segfault if a section named .opd is found in ELFv2 binaries.
  
  * elf64-ppc.c (synthetic_opd): New static var.
  (compare_symbols): Don't treat symbols in .opd specially for 
ELFv2.
  (ppc64_elf_get_synthetic_symtab): Likewise.  Comment.

  commit 2a0b8eb7a7974ff7605cb3ba5dffa5abef286ffa
  Author: Alan Modra 
  Date:   Tue Aug 30 20:57:32 2016 +0930

  ppc apuinfo for spe parsed incorrectly
  
  apuinfo saying SPE resulted in mach = bfd_mach_ppc_vle due to a
  missing break.
  
  PR 20531
  * elf32-ppc.c (_bfd_elf_ppc_set_arch): Add missing "break".

  commit 7f27ccfcd5b86a6517a5c01d1cc29e87ac39c13c
  Author: Alan Modra 
  Date:   Fri Aug 19 11:06:41 2016 +0930

  PR 20472, PowerPC64 ifunc confusion
  
  This patch fixes quite a lot of confusion in allocate_dynrelocs over
  ifuncs.  Function descriptors make ELFv1 quite different to ELFv2.
  
  PR 20472
  * elf64-ppc.c (ppc64_elf_before_check_relocs): Tweak abiversion 
test.
  (readonly_dynrelocs): Co

[Touch-packages] [Bug 1661568] Re: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property

2017-02-03 Thread Brian Murray

** Tags added: zesty

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

Title:
  logind fails to emit change signal for
  org.freedesktop.login1.Seat.ActiveSession DBus property

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  logind fails to emit a DBus PropertiesChanged signal for the
  org.freedesktop.login1.Seat.ActiveSession DBus property. See
  https://github.com/systemd/systemd/issues/5210.

  This breaks repowerd on zesty since repowerd depends on this signal to
  track the active session.

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

-- 
Mailing list: https://launchpad.net/~touch-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-02-03 Thread Ryan Harper

** Patch added: "xenial-dns-before-online-target-lp1649931-v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+attachment/4812597/+files/xenial-dns-before-online-target-lp1649931-v2.debdiff

-- 
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 Committed
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-4ubuntu13
    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
  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.

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

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

[Touch-packages] [Bug 1660762] Comment bridged from LTC Bugzilla

2017-02-03 Thread bugproxy

--- Comment From mu...@br.ibm.com 2017-02-03 10:33 EDT---
I enabled the debug in udev for Ubuntu 17.04 and I am seeing the following in 
the log:

systemd-udevd[4552]: 'ifupdown-hotplug'(err) 'ifquery: error while
loading shared libraries: cannot restore segment prot after reloc:
Operation not permitted'

This command is used in the /lib/udev/ifupdown-hotplug script that is
invoked in the 80-ifupdown.rules

# cat /lib/udev/rules.d/80-ifupdown.rules
# Allow rfkill for users in the netdev group
KERNEL=="rfkill", MODE="0664", GROUP="netdev"

# Handle allow-hotplug interfaces
SUBSYSTEM=="net", ACTION=="add|remove", RUN+="ifupdown-hotplug"

The ifquery command is used in the following net_ifup function of the
script:

net_ifup() {
check_program /sbin/ifup

# exit if the interface is not configured as allow-hotplug or auto
if ! (ifquery --allow hotplug -l; ifquery --allow auto -l) | grep -q 
"^${INTERFACE}\$"; then
exit 0
fi

if [ -d /run/systemd/system ]; then
exec systemctl --no-block start $(systemd-escape --template ifup@.service 
$INTERFACE)
fi

local out=$(ps -C ifup ho args)
if [ "${out%$INTERFACE*}" != "$out" ]; then
mesg "Already ifup-ing interface $INTERFACE"
exit 0
fi

wait_for_interface lo

exec ifup --allow=hotplug $INTERFACE
}

So it is failing the first if and exiting the function when it shouldn't
be doing so for an interface that is supposed to be configured. And
since it uses exit code 0 it doesn't show up as an error in the syslog
and it appears that the script is successfully executed.

I don't see the error with ifquery when testing in Ubuntu 16.04, so it
might be the point of failure we are looking for.

What I find strange is that the script and rule are the same in Ubuntu
16.04 and Ubuntu 17.04 and when I manually run the command in Ubuntu
17.04 I get the proper output.

# ifquery --allow hotplug -l
enP1p12s0f0
# ifquery --allow auto -l
lo
enP1p12s0f0

I still need to take a closer look to try to figure out what is causing
ifquery to fail in the script and not when using it manually.

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

Title:
  [Regression] Interface configuration not restored after driver
  unbind/bind (generic)

Status in ifupdown package in Ubuntu:
  Triaged

Bug description:
  ---Problem Description---
  Interface configuration not restored after driver unbind/bind
   

  root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
  enP28p96s0f0: flags=4163  mtu 1500
  inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
  inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
  ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 13  bytes 1046 (1.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ltciofvtr-s824-lp8:~# cat /etc/network/interfaces
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto ibmveth2
  iface ibmveth2 inet static
address 9.47.68.120
netmask 255.255.240.0
network 9.47.64.0
broadcast 9.47.79.255
gateway 9.47.79.254
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 9.12.18.2
dns-search pok.stglabs.ibm.com

  auto enP28p96s0f0
  iface enP28p96s0f0 inet static
 address 10.10.10.11
 netmask 255.255.255.0

  root@ltciofvtr-s824-lp8:~# ethtool -i enP28p96s0f0
  driver: be2net
  version: 11.1.0.0
  firmware-version: 10.2.252.1913
  expansion-rom-version: 
  bus-info: 001c:60:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no
  supports-priv-flags: yes

  root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
  /sys/bus/pci/drivers/be2net/unbind

  root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net 
  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  remove_id  
uevent  unbind

  root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
  /sys/bus/pci/drivers/be2net/bind

  root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net
  001c:60:00.0  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  
remove_id  uevent  unbind

  root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
  enP28p96s0f0: flags=4098  mtu 1500
  ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ltciofvtr-s824-lp8:~# ifup enP28p96s0

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

2017-02-03 Thread andrew buffa

I'm a newbie

how do I do that & why/how does the printer affect internet connection?

Andrew
On 2/2/2017 10:31 PM, rusbunker wrote:
> yes. I purge driver of printer and reinstall it again. That all.
> Everything ok.
>
>
> 03.02.2017 00:37, andrew buffa пишет:
>> how do I fix?
>>
>> I now have no internet connection
>>
>> am using a backup pc
>>
>> Andrew
>> On 1/31/2017 11:56 PM, rusbunker wrote:
>>> Дмитрий добрый день! Я правильно понимаю что если выполню инструкции
>>> прописанные в этом сообщении, я получу желаемое? А именно устновлю принтер.
>>>
>>>
>>> 31.01.2017 13:33, Dimitri John Ledkov пишет:
 ** Changed in: cups (Ubuntu Zesty)
   Milestone: ubuntu-17.01 => ubuntu-17.02

>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>>

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

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

Status in cups package in Ubuntu:
  Triaged
Status in cups source package in Xenial:
  Triaged
Status in cups source package in Yakkety:
  Triaged
Status in cups source package in Zesty:
  Triaged

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  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/cups/+bug/1642966/+subscriptions

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

[Touch-packages] [Bug 947617] Re: After update, lxc does not start

2017-02-03 Thread Manisha Luthra

apparmor version: AppArmor 2.10 
lxc version: Version 1.1.5

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

Title:
  After update, lxc does not start

Status in apparmor package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  After getting the latest updates, a previously working lucid container
  is failing to start:

  sudo lxc-start -n u1-server
  lxc-start: failed to mount rootfs
  lxc-start: failed to setup rootfs for 'u1-server'
  lxc-start: failed to setup the container
  lxc-start: invalid sequence number 1. expected 2
  lxc-start: failed to spawn 'u1-server'
  lxc-start: Device or resource busy - failed to remove cgroup 
'/mnt/cgroup//lxc/u1-server'

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lxc 0.7.5-3ubuntu32
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic i686
  ApportVersion: 1.94-0ubuntu1
  Architecture: i386
  Date: Mon Mar  5 21:07:22 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 
(2029.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what

yep, was the removal-of waithandle MP. needed some more checks before
waiting for interval configuration.


** Changed in: mir/0.26
 Assignee: (unassigned) => Kevin DuBois (kdub)

** Changed in: mir/0.26
   Status: Triaged => In Progress

** Branch linked: lp:~kdub/mir/fix-1661508

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

Title:
  [regression] Nested server segfaults or rapidly logs exceptions when a
  fullscreen client starts [in mir_presentation_chain_set_dropping_mode
  ... std::exception::what: Operation not permitted]

Status in Mir:
  Triaged
Status in Mir 0.26 series:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Nested server segfaults when a fullscreen client starts

  Using Mir 0.26.0 (zesty release):

  The client dies:

  [2017-02-03 15:05:44.315444]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76):
 Throw in function void mir::client::PromiseStateBase::break_promise() [with 
T = std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::error_info_injector
  std::exception::what: broken_promise

  Because the server died:

  Segmentation fault (core dumped)
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x7fcceb7b4003 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #2  0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fccec0e3a7a in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #4  0x7fccec09fd2d in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #5  0x7fccec09f018 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #6  0x7fccec0e2c79 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #7  0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #8  0x7fcce95326ca in start_thread (arg=0x7fccde2b4700)
  at pthread_create.c:333
  #9  0x7fccec4710ff in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

  However in development builds the server does not die and just floods
  the log instead:

  [2017-02-03 16:52:44.382460]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.399142]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.415823]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.432504]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  *** WORKAROUND ***
  Start your nested server with --nested-passthrough=OFF
  Which works on the 0.26.0 release, but not on anything newer because you'll 
then hit the more recent regression bug 1661521.

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

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

[Touch-packages] [Bug 947617] Re: After update, lxc does not start

2017-02-03 Thread Manisha Luthra

Hi,
I face the same issue 
lxc-start: conf.c: setup_rootfs: 1279 Permission denied - Failed to make / 
rslave
lxc-start: conf.c: do_rootfs_setup: 3801 failed to setup rootfs for 'left'
lxc-start: conf.c: lxc_setup: 3883 Error setting up rootfs mount after spawn
lxc-start: start.c: do_start: 731 failed to setup the container
lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
lxc-start: start.c: __lxc_start: 1213 failed to spawn 'left'
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

even disabling the apparmor profile doesnt help. Also, I need apparmor
anyways because I want to communicate between multiple containers.

Issue is will the following kernel:
Linux ubuntu 4.2.0-16-generic

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

Title:
  After update, lxc does not start

Status in apparmor package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  After getting the latest updates, a previously working lucid container
  is failing to start:

  sudo lxc-start -n u1-server
  lxc-start: failed to mount rootfs
  lxc-start: failed to setup rootfs for 'u1-server'
  lxc-start: failed to setup the container
  lxc-start: invalid sequence number 1. expected 2
  lxc-start: failed to spawn 'u1-server'
  lxc-start: Device or resource busy - failed to remove cgroup 
'/mnt/cgroup//lxc/u1-server'

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lxc 0.7.5-3ubuntu32
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic i686
  ApportVersion: 1.94-0ubuntu1
  Architecture: i386
  Date: Mon Mar  5 21:07:22 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 
(2029.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661629] [NEW] upgrade of kernel fails with mkinitramfs: failed to determine device for /

2017-02-03 Thread Fredrik Tuomas

Public bug reported:

When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
root on ZFS I get this error:

Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /etc/initramfs-tools/

Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'
update-initramfs: failed for  with 1.
run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
 subprocess installed post-installation script returned error exit status 2

version of initramfs-tools is 0.122ubuntu8.8


Output of mount is:

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
rpool/home on /home type zfs (rw,nosuid,noatime,xattr,noacl)
rpool/home/fredrik on /home/fredrik type zfs (rw,nosuid,noatime,xattr,noacl)
rpool/home/root on /root type zfs (rw,nosuid,noatime,xattr,noacl)
rpool/srv on /srv type zfs (rw,noatime,xattr,noacl)
rpool/var/cache on /var/cache type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
rpool/var/log on /var/log type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
rpool/var/spool on /var/spool type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
rpool/var/tmp on /var/tmp type zfs (rw,nosuid,noatime,xattr,noacl)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=1623576k,mode=700,uid=1000,gid=1000)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)

cat /proc/mounts 
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755 
0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=1623576k,mode=755 0 0
rpool/ROOT/ubuntu / zfs rw,relatime,xattr,noacl 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmp

[Touch-packages] [Bug 1583088] Re: Randomly corrupt font / text / characters in Unity8

2017-02-03 Thread Gerry Boland

I'm looking into this now. I took an api trace of some simple font
rendering by Qt on Mir showing the problem, and executed it on my X11
session. It renders ok on X11. Reading through the apitrace, Qt seems to
be doing the right thing.

I suspect the mismatch we have between Mir creating a GLES context and
Qt expecting a GL context is hitting us here.

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

Title:
  Randomly corrupt font / text / characters in Unity8

Status in Canonical System Image:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

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

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

[Touch-packages] [Bug 1661621] [NEW] Icon {} paints different whether color is speified or not

Public bug reported:

I don't know which of the two ways of paining is the correct, but i
think it's unexpected for it to be pained differently whether icon is
set or not

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

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

Title:
  Icon {} paints different whether color is speified or not

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

Bug description:
  I don't know which of the two ways of paining is the correct, but i
  think it's unexpected for it to be pained differently whether icon is
  set or not

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

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

[Touch-packages] [Bug 1661621] Re: Icon {} paints different whether color is speified or not

** Attachment added: "Image used in test file"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1661621/+attachment/4812585/+files/logo.png

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

Title:
  Icon {} paints different whether color is speified or not

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

Bug description:
  I don't know which of the two ways of paining is the correct, but i
  think it's unexpected for it to be pained differently whether icon is
  set or not

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

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

[Touch-packages] [Bug 1661621] Re: Icon {} paints different whether color is speified or not

** Attachment added: "rendering i get"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1661621/+attachment/4812586/+files/rendering.png

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

Title:
  Icon {} paints different whether color is speified or not

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

Bug description:
  I don't know which of the two ways of paining is the correct, but i
  think it's unexpected for it to be pained differently whether icon is
  set or not

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

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

[Touch-packages] [Bug 1661621] Re: Icon {} paints different whether color is speified or not

** Attachment added: "QML file"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1661621/+attachment/4812584/+files/main.qml

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

Title:
  Icon {} paints different whether color is speified or not

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

Bug description:
  I don't know which of the two ways of paining is the correct, but i
  think it's unexpected for it to be pained differently whether icon is
  set or not

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

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

[Touch-packages] [Bug 1661611] Re: apt/unattended-upgrades stalls shutdown

2017-02-03 Thread Jogarem

Solution:

 - fix /usr/share/unattended-upgrades/unattended-upgrades-shutdown to
expect "false" instead of "False"

patching /usr/share/unattended-upgrades/unattended-upgrade-shutdown:


--- /tmp/unattended-upgrade-shutdown2017-02-03 14:53:03.238103238 +0100
+++ /tmp/unattended-upgrade-shutdown_fix2017-02-03 14:53:17.685589001 
+0100
@@ -117,7 +117,7 @@
 # run it
 p = None
 apt_pkg.init_config()
-if apt_pkg.config.find_b("Unattended-Upgrade::InstallOnShutdown", False):
+if apt_pkg.config.find_b("Unattended-Upgrade::InstallOnShutdown", false):
 env = copy.copy(os.environ)
 env["UNATTENDED_UPGRADES_FORCE_INSTALL_ON_SHUTDOWN"] = "1"
 logging.debug("starting unattended-upgrades in shutdown mode")


The above solves the issue for me.

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

Title:
  apt/unattended-upgrades stalls shutdown

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots
  hang while "starting unattended upgrades shutdown". This hang stalls
  the shutdown process for 5-10 mins.

  If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto-
  upgrades and/or 50unattended-upgrades, the problems occurs.

  If I terminate the service before shutdown/reboot (sudo service
  unattended-upgrades stop) the problem still occurs.

  If I remove the package (sudo apt remove unattended-upgrades) the
  problem no longer occurs.

  This occurs on a freshly installed version of Ubuntu Server 16.04.1
  (both unattended-upgrades installed via install GUI or manual install
  of unattended-upgrades)

  Both Kern.log & syslog do not show the shutdown process (I believe
  because the filesystems have already unmounted)

  Original report: http://askubuntu.com/questions/878630/apt-unattended-
  upgrades-stalls-shutdown

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

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

[Touch-packages] [Bug 1661611] [NEW] apt/unattended-upgrades stalls shutdown

2017-02-03 Thread Jogarem

Public bug reported:

When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots
hang while "starting unattended upgrades shutdown". This hang stalls the
shutdown process for 5-10 mins.

If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto-
upgrades and/or 50unattended-upgrades, the problems occurs.

If I terminate the service before shutdown/reboot (sudo service
unattended-upgrades stop) the problem still occurs.

If I remove the package (sudo apt remove unattended-upgrades) the
problem no longer occurs.

This occurs on a freshly installed version of Ubuntu Server 16.04.1
(both unattended-upgrades installed via install GUI or manual install of
unattended-upgrades)

Both Kern.log & syslog do not show the shutdown process (I believe
because the filesystems have already unmounted)

Original report: http://askubuntu.com/questions/878630/apt-unattended-
upgrades-stalls-shutdown

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

** Description changed:

  When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots
  hang while "starting unattended upgrades shutdown". This hang stalls the
  shutdown process for 5-10 mins.
  
  If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto-
  upgrades and/or 50unattended-upgrades, the problems occurs.
  
  If I terminate the service before shutdown/reboot (sudo service
  unattended-upgrades stop) the problem still occurs.
  
  If I remove the package (sudo apt remove unattended-upgrades) the
  problem no longer occurs.
  
  This occurs on a freshly installed version of Ubuntu Server 16.04.1
  (both unattended-upgrades installed via install GUI or manual install of
  unattended-upgrades)
  
  Both Kern.log & syslog do not show the shutdown process (I believe
  because the filesystems have already unmounted)
+ 
+ Original report: http://askubuntu.com/questions/878630/apt-unattended-
+ upgrades-stalls-shutdown

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

Title:
  apt/unattended-upgrades stalls shutdown

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots
  hang while "starting unattended upgrades shutdown". This hang stalls
  the shutdown process for 5-10 mins.

  If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto-
  upgrades and/or 50unattended-upgrades, the problems occurs.

  If I terminate the service before shutdown/reboot (sudo service
  unattended-upgrades stop) the problem still occurs.

  If I remove the package (sudo apt remove unattended-upgrades) the
  problem no longer occurs.

  This occurs on a freshly installed version of Ubuntu Server 16.04.1
  (both unattended-upgrades installed via install GUI or manual install
  of unattended-upgrades)

  Both Kern.log & syslog do not show the shutdown process (I believe
  because the filesystems have already unmounted)

  Original report: http://askubuntu.com/questions/878630/apt-unattended-
  upgrades-stalls-shutdown

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

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

[Touch-packages] [Bug 1639297] Re: Hard coded paths prevent usage in snaps

2017-02-03 Thread Michael Sheldon

** Patch added: "0017-maliit-config-path-environment-variable.patch"
   
https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1639297/+attachment/4812581/+files/0017-maliit-config-path-environment-variable.patch

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

Title:
  Hard coded paths prevent usage in snaps

Status in maliit-framework package in Ubuntu:
  New

Bug description:
  A number of paths are defined at compile time which instead need to be
  set dynamically at run time to allow for usage in snaps.

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

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

[Touch-packages] [Bug 1639297] Re: Hard coded paths prevent usage in snaps

2017-02-03 Thread Michael Sheldon

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

Title:
  Hard coded paths prevent usage in snaps

Status in maliit-framework package in Ubuntu:
  New

Bug description:
  A number of paths are defined at compile time which instead need to be
  set dynamically at run time to allow for usage in snaps.

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

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

[Touch-packages] [Bug 1657845] Re: Unity8 snap can't load the testability libraries

2017-02-03 Thread Santiago Baldassin

much better, now the libraries are present in the testability folder but
I can't still introspect unity8.

phablet@ubuntu:~$ snap run --shell unity8-session
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

phablet@ubuntu:/home/phablet$ ls $SNAP/testability/
libautopilot_driver_qt4.solibautopilot_driver_qt4.so.1.0
libautopilot_driver_qt5.solibautopilot_driver_qt5.so.1.0x86_64-linux-gnu
libautopilot_driver_qt4.so.1  libautopilot_driver_qt4.so.1.0.0  
libautopilot_driver_qt5.so.1  libautopilot_driver_qt5.so.1.0.0

Just to give a little bit of more context, we are trying to introspect
the unity8 process, so the unity8 process should load the testability
libraries and it seems it is not doing it.

sudo cat /proc/U8PID/maps | awk '{print $6}' | grep '\.so' | sort | uniq
shows that the testability libraries are not loaded

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

Title:
  Unity8 snap can't load the testability libraries

Status in Unity8 Session Snap:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  In order to introspect unity8, the testability libraries should be
  available. Such libraries are provided by autopilot-qt snap through a
  content interface called testability

  unity8 snap should add a plug to such interface so that testability
  libraries get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-session-snap/+bug/1657845/+subscriptions

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

[Touch-packages] [Bug 1421293] Re: Icon width is inconsistent when height is specified

** Attachment removed: "The qml file to test"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421293/+attachment/4318108/+files/main.qml

** Description changed:

  The width of an Icon {} depends if the Icon is an SVG coming from
  image://theme/ or a JPG.
  
  For the SVG the width grows as the units.gu grow, but for the JPEG it
  does not and one has to manually add code to maitain the aspect ratio.
  
  See the attached code and files.
- 
- **
- 
- Trying to explain the bug a bit better.
- 
- The problem is basically that the first image looks "correct" at any
- GRID_UNIT_PX value while the second does not, you need to add extra code
- (i.e. the third) for it to look correct. See in
- http://i.imgur.com/EBb8PEU.png how the first and third images always
- keep the aspect ratio nice while the second gets distorted as we
- increase the GRID_UNIT_PX value

** Attachment added: "QML file to try"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421293/+attachment/4812571/+files/main.qml

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

Title:
  Icon width is inconsistent when height is specified

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  The width of an Icon {} depends if the Icon is an SVG coming from
  image://theme/ or a JPG.

  For the SVG the width grows as the units.gu grow, but for the JPEG it
  does not and one has to manually add code to maitain the aspect ratio.

  See the attached code and files.

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

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

[Touch-packages] [Bug 1659058] Re: WIFI after suspend reconnect but no internet connection established

2017-02-03 Thread taiebot65

I have resorted to use WICD wifi is much more stable and reconnects
after suspend

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

Title:
   WIFI  after suspend reconnect but no internet connection established

Status in network-manager package in Ubuntu:
  New

Bug description:
  Distro Lubuntu 16.10
  Computer Gateway 

  Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187
  Wireless Adapter

  After i reconnect from suspend i can see network manager reconnecting to my 
SSID via the nm-applet but i cannot browse the web. I need to do sudo systemctl 
restart network-manager.service to re-establish a valid connection.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-19 (1192 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386 
(20131016.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.21  metric 
600
  Package: network-manager 1.2.6-0ubuntu1
  PackageArchitecture: i386
  PciNetwork:
   
  ProcVersionSignature: Ubuntu 4.8.0-36.38-generic 4.8.16
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety package-from-proposed
  Uname: Linux 4.8.0-36-generic i686
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (102 days ago)
  UserGroups: adm autopilot cdrom dialout dip disk fax floppy fuse lpadmin 
netdev plugdev sambashare sudo tape video
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-01-24T13:52:13.332669
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
Livebox-e849  50004a99-f882-49dd-9cbd-c4fba36d1270  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1658117] Re: Chrome-less shell hint does not work any more

** Branch linked: lp:~lukas-kde/miral/shellchrome-windowinfo

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

Title:
  Chrome-less shell hint does not work any more

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

Bug description:
  Test case.
  - Open camera in device mode.

  Expected result.
  - Camera opens full screen and top menu hides.

  Actual result.
  - Camera opens full screen but top menu is not hidden.

  current build number: 127
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

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

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

[Touch-packages] [Bug 1658117] Re: Chrome-less shell hint does not work any more

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

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

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

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

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

Title:
  Chrome-less shell hint does not work any more

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

Bug description:
  Test case.
  - Open camera in device mode.

  Expected result.
  - Camera opens full screen and top menu hides.

  Actual result.
  - Camera opens full screen but top menu is not hidden.

  current build number: 127
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

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

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

[Touch-packages] [Bug 1661568] Re: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property

2017-02-03 Thread Ubuntu Foundations Team Bug Bot

The attachment "systemd-fix-1661568.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  logind fails to emit change signal for
  org.freedesktop.login1.Seat.ActiveSession DBus property

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  logind fails to emit a DBus PropertiesChanged signal for the
  org.freedesktop.login1.Seat.ActiveSession DBus property. See
  https://github.com/systemd/systemd/issues/5210.

  This breaks repowerd on zesty since repowerd depends on this signal to
  track the active session.

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

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

[Touch-packages] [Bug 1607666] Re: sudo fails with host netgroup returned from freeipa

2017-02-03 Thread Florian Apolloner

Sorry, cannot confirm on yakkety since we do not deploy there yet.

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

Title:
  sudo fails with host netgroup returned from freeipa

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Committed
Status in sudo source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Sudo currently fails to validate netgroups against host netgroups returned 
from the sss plugin, see https://fedorahosted.org/freeipa/ticket/6139 for the 
glory details.

  This was fixed in sudo 1.8.17
  (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which
  I'd very much like to see backported to Ubuntu 16.04. If possible,
  updating sudo completely to 1.8.17 would be nice, since there have
  been quite a few improvements with regards to sss and freeipa and it
  would be a shame if we could not benefit from them given that 16.04 is
  LTS.

  [Test case]
  install the update, test that sudo works on a freeipa installation that uses 
netgroups

  [Regression potential]
   I looked at upstream commits to sssd.c, and there were no commits 
that touch this area, so chance of regressions should be slim

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

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

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional

2017-02-03 Thread John Johansen

James, I can give you access to a custom kernel and library that
provides a fix for the apparmor end if you would like. The issue is that
these are not in the distro yet, and have not been backported to earlier
releases (yet).

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Triaged
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

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

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

[Touch-packages] [Bug 1658117] Re: Chrome-less shell hint does not work any more

Likely culprit: http://bazaar.launchpad.net/~mir-
team/qtmir/trunk/view/head:/src/modules/Unity/Application/mirsurface.cpp#L145

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

Title:
  Chrome-less shell hint does not work any more

Status in Canonical System Image:
  Triaged
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Test case.
  - Open camera in device mode.

  Expected result.
  - Camera opens full screen and top menu hides.

  Actual result.
  - Camera opens full screen but top menu is not hidden.

  current build number: 127
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

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

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

[Touch-packages] [Bug 1660242] Re: Thumbnailer should be packaged as a snap

2017-02-03 Thread James Henstridge

A pull request for a "thumbnailer" snappy interface:

https://github.com/snapcore/snapd/pull/2783

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

Title:
  Thumbnailer should be packaged as a snap

Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  We need to package Thumbnailer as a snap.  Some requirements are:

    1. package should use strict confinement
    2. service should be usable from other strictly confined snaps
    3. thumbnailer-admin should be able to talk to thumbnailer-service
4. ???

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

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

[Touch-packages] [Bug 1661263] Re: printer

2017-02-03 Thread Paul White

You might find https://wiki.ubuntu.com/DebuggingPrintingProblems
helpful.

** Package changed: xorg (Ubuntu) => cups (Ubuntu)

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

Title:
  printer

Status in cups package in Ubuntu:
  New

Bug description:
  i cant configure my printers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Feb  2 15:21:47 2017
  DistUpgraded: 2016-08-02 10:45:18,499 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3034]
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3034]
  InstallationDate: Installed on 2016-01-03 (395 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Hewlett-Packard HP Compaq dc7900 Small Form Factor
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=afddea74-5fdf-4357-a40e-f790f5c89633 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (184 days ago)
  dmi.bios.date: 03/05/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G1 v01.16
  dmi.board.asset.tag: CZC92914YN
  dmi.board.name: 3031h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC92914YN
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G1v01.16:bd03/05/2009:svnHewlett-Packard:pnHPCompaqdc7900SmallFormFactor:pvr:rvnHewlett-Packard:rn3031h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq dc7900 Small Form Factor
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Feb  2 16:19:43 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1661557] Re: Touch tutorial is inescapable on desktop (without a touchscreen)

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

** Branch linked: lp:~lukas-kde/unity8/no-touchscreen-no-tutorial

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

Title:
  Touch tutorial is inescapable on desktop (without a touchscreen)

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  The touch tutorial is inescapable on desktop (without a touchscreen).

  I somehow accidentally started Unity8 in touch mode and could use it
  with a mouse. However after a short while (bug 1607176) the tutorial
  starts, and there I'm stuck.

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

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

[Touch-packages] [Bug 1661575] Re: printer

2017-02-03 Thread Paul White

You might find https://wiki.ubuntu.com/DebuggingPrintingProblems
helpful.

** Package changed: xorg (Ubuntu) => cups (Ubuntu)

** Summary changed:

- printer
+ printer doesn't print anymore

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

Title:
  printer doesn't print anymore

Status in cups package in Ubuntu:
  New

Bug description:
  printer doesn't print anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Feb  3 12:02:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [144d:c07f]
  InstallationDate: Installed on 2016-07-06 (212 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R540/R580/R780/SA41/E452/E852
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=4915e0c4-9b44-4791-91a6-f7ea13097772 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 03KP.M008.20100927.LDG
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: R540/R580/R780/SA41/E452/E852
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 03KP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr03KP.M008.20100927.LDG:bd09/27/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR540/R580/R780/SA41/E452/E852:pvr03KP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR540/R580/R780/SA41/E452/E852:rvr03KP:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: R540/R580/R780/SA41/E452/E852
  dmi.product.version: 03KP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Feb  3 11:54:03 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional

2017-02-03 Thread James Henstridge

I had a go writing a custom interface to allow thumbnailer to access the
private files of another snap here:

https://github.com/snapcore/snapd/pull/2783

Unfortunately access to ~/snap/$name is also guarded by the "owner"
modifier, so it suffers from the same problems as checking for access
granted by the home interface.  So this will be a problem on systems
built on core as well as classic desktops.

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Triaged
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

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

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

[Touch-packages] [Bug 1661568] Re: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property

2017-02-03 Thread Alexandros Frantzis

I have proposed a fix for this issue upstream (merged into master at
[1]) and have cherry-picked the fix as a patch for the zesty systemd
package in the attached debdiff.

[1]
https://github.com/systemd/systemd/commit/7d049e304e8c9f6478bd3c6dc1781adf21d03e80

** Patch added: "systemd-fix-1661568.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1661568/+attachment/4812524/+files/systemd-fix-1661568.debdiff

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

Title:
  logind fails to emit change signal for
  org.freedesktop.login1.Seat.ActiveSession DBus property

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  logind fails to emit a DBus PropertiesChanged signal for the
  org.freedesktop.login1.Seat.ActiveSession DBus property. See
  https://github.com/systemd/systemd/issues/5210.

  This breaks repowerd on zesty since repowerd depends on this signal to
  track the active session.

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

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

[Touch-packages] [Bug 1661575] [NEW] printer

Public bug reported:

printer doesn't print anymore

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Feb  3 12:02:19 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [144d:c07f]
InstallationDate: Installed on 2016-07-06 (212 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. R540/R580/R780/SA41/E452/E852
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=4915e0c4-9b44-4791-91a6-f7ea13097772 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 03KP.M008.20100927.LDG
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: R540/R580/R780/SA41/E452/E852
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 03KP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr03KP.M008.20100927.LDG:bd09/27/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR540/R580/R780/SA41/E452/E852:pvr03KP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR540/R580/R780/SA41/E452/E852:rvr03KP:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: R540/R580/R780/SA41/E452/E852
dmi.product.version: 03KP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Feb  3 11:54:03 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: radeon

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


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

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

Title:
  printer

Status in xorg package in Ubuntu:
  New

Bug description:
  printer doesn't print anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Feb  3 12:02:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [144d:c07f]
  InstallationDate: Installed on 2016-07-06 (212 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R540/R580/R780/SA41/E452/E852
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=4915e0c4-9b44-4791-91a6-f7ea13097772 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 03KP.M008.20100927.LDG
  dmi.board

[Touch-packages] [Bug 1661557] Re: Touch tutorial is inescapable on desktop (without a touchscreen)

Agree, should be an easy fix

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

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

Title:
  Touch tutorial is inescapable on desktop (without a touchscreen)

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  The touch tutorial is inescapable on desktop (without a touchscreen).

  I somehow accidentally started Unity8 in touch mode and could use it
  with a mouse. However after a short while (bug 1607176) the tutorial
  starts, and there I'm stuck.

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

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

[Touch-packages] [Bug 1661568] [NEW] logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property

2017-02-03 Thread Alexandros Frantzis

Public bug reported:

logind fails to emit a DBus PropertiesChanged signal for the
org.freedesktop.login1.Seat.ActiveSession DBus property. See
https://github.com/systemd/systemd/issues/5210.

This breaks repowerd on zesty since repowerd depends on this signal to
track the active session.

** Affects: systemd (Ubuntu)
 Importance: High
 Assignee: Alexandros Frantzis (afrantzis)
 Status: In Progress

** Changed in: systemd (Ubuntu)
   Status: New => 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/1661568

Title:
  logind fails to emit change signal for
  org.freedesktop.login1.Seat.ActiveSession DBus property

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  logind fails to emit a DBus PropertiesChanged signal for the
  org.freedesktop.login1.Seat.ActiveSession DBus property. See
  https://github.com/systemd/systemd/issues/5210.

  This breaks repowerd on zesty since repowerd depends on this signal to
  track the active session.

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

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

[Touch-packages] [Bug 1661564] Re: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

2017-02-03 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade:
  subprocess installed post-installation script was killed by signal
  (Terminated)

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I got the error notifications in the time between my password being
  confirmed and the icons/desktop loading onto the screen, ie when the
  screen contained only the background image.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptOrdering:
   libgnutls-openssl27: Install
   libgnutls30: Install
   ntfs-3g: Install
   libxpm4: Install
   l
  Architecture: amd64
  Date: Fri Feb  3 01:16:51 2017
  DuplicateSignature:
   package:initramfs-tools:0.122ubuntu8.8
   Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
   update-initramfs: Generating /boot/initrd.img-4.4.0-62-generic
   dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script was killed by signal 
(Terminated)
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
  InstallationDate: Installed on 2016-10-19 (107 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: 
subprocess installed post-installation script was killed by signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661564] [NEW] package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

2017-02-03 Thread Rob Moore

Public bug reported:

I got the error notifications in the time between my password being
confirmed and the icons/desktop loading onto the screen, ie when the
screen contained only the background image.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.8
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
AptOrdering:
 libgnutls-openssl27: Install
 libgnutls30: Install
 ntfs-3g: Install
 libxpm4: Install
 l
Architecture: amd64
Date: Fri Feb  3 01:16:51 2017
DuplicateSignature:
 package:initramfs-tools:0.122ubuntu8.8
 Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
 update-initramfs: Generating /boot/initrd.img-4.4.0-62-generic
 dpkg: error processing package initramfs-tools (--configure):
  subprocess installed post-installation script was killed by signal 
(Terminated)
ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
InstallationDate: Installed on 2016-10-19 (107 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.18
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: 
subprocess installed post-installation script was killed by signal (Terminated)
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade:
  subprocess installed post-installation script was killed by signal
  (Terminated)

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I got the error notifications in the time between my password being
  confirmed and the icons/desktop loading onto the screen, ie when the
  screen contained only the background image.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptOrdering:
   libgnutls-openssl27: Install
   libgnutls30: Install
   ntfs-3g: Install
   libxpm4: Install
   l
  Architecture: amd64
  Date: Fri Feb  3 01:16:51 2017
  DuplicateSignature:
   package:initramfs-tools:0.122ubuntu8.8
   Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
   update-initramfs: Generating /boot/initrd.img-4.4.0-62-generic
   dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script was killed by signal 
(Terminated)
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
  InstallationDate: Installed on 2016-10-19 (107 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: 
subprocess installed post-installation script was killed by signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1566437] Re: Scrolling randomly stops working

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

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

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

Title:
  Scrolling randomly stops working

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Usually, scrolling in the terminal window works as expected, which is like 
this:
  - the terminal window has a scrollbar
  - Assuming there are more lines (of commands you have typed + their output) 
than fit in the window, you can scroll up and down both by dragging the 
scrollbar and by using the mouse wheel

  
  However, at random times, the Terminal starts behaving like this:
  1 - the scrollbar's "handle" is as high as the whole scrollbar, as if the 
existing lines didn't exceed the height of the window, even if that is not the 
case
  2 - you can't scroll by dragging the scrollbar (which is consistent with 1)
  3 - the scrollwheel behaves like the up and down arrow keys, that is, it 
scans through previously typed commands in your history.

  
  I have no idea what triggers the nonsense behavior. It seems to start 
happening randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-terminal 3.16.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  5 19:05:18 2016
  InstallationDate: Installed on 2013-10-11 (906 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to wily on 2016-01-18 (78 days ago)

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

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

[Touch-packages] [Bug 1661557] [NEW] Touch tutorial is inescapable on desktop (without a touchscreen)