date:20170219

Accepted unity-control-center into -proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/unity-control-
center/15.04.0+16.10.20170214-0ubuntu1 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: unity-control-center (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: unity-control-center (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Changed in: unity-control-center (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: unity-control-center (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1630156

Title:
  No password needed to Log in after cancel the password and then reset
  again

Status in Light Display Manager:
  New
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Confirmed
Status in unity-control-center source package in Xenial:
  Fix Committed
Status in lightdm source package in Yakkety:
  Confirmed
Status in unity-control-center source package in Yakkety:
  Fix Committed

Bug description:
  [ Description ]

  If you use unity-control-center to set the current user from "Log in
  without a password" to having a password again, the user is not
  removed from the 'nopasswdlogin' UNIX group, and so can log in without
  a password still.

  [ Test case ]

  1. Open the dash, type "User Accounts", open the user accounts panel of 
unity-control-center.
  2. Make sure the current user (which must be an admin) is selected in the 
list of user's on the left hand side.
  3. Click "Unlock" at the top right, and enter the user's password.
  4. Click the dots to the right of "Password", to open the dialog where you 
can change the password mode.
  5. In the combo box at the top, select "Log in without a password". Save the 
dialog.
  6. Open a terminal, and execute `grep nopasswdlogin /etc/group'. Note that 
the current user is present.
  7. Re-open the password dialog as in step 4.
  8. Select "Set a password now", and set a password. Save the dialog.
  9. Open a terminal, and execute `grep nopasswdlogin /etc/group'.

  At step 9, if the bug is present then the user will still be in the
  group. If it is fixed then the user will not.

  [ Fix ]

  unity-control-center's user-accounts panel contains a codepath to call
  `passwd' directly when changing the current user's password. There's
  another path when setting the password for a different user which uses
  AccountsService. In the former codepath, the AccountsService call
  required to remove the user from `nopasswdlogin' is not executed
  (act_user_set_password_mode (..., ACT_USER_PASSWORD_MODE_REGULAR)).

  The proposed fix (in the attached MP) is to always make this call when
  setting a password, even in this passwd case.

  [ QA ]

  Run the test case above. Additionally,

   - Try to use the dialog to change passwords without unlocking it.
   - Try to change both the current and another user's password.

  Make sure the nopasswdlogin membership is right at all times and the
  new password always gets applied (e.g. try logging out and in to check
  the settings).

  [ Regression potential ]

  The fix changes a couple of things

- We now call act_user_set_password_mode () after running passwd.
- We now call act_user_set_password () before act_user_set_password_mode 
(), which is the opposite of the previous order.

  AFAIK both of these changes are fine, but we should run the QA tests
  above to get confidence that they didn't break password setting.

  [ Original description ]

  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password. (as doing so, the user is added to group "nopasswdlogin")

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

** Changed in: gpgme1.0 (Ubuntu)
   Importance: Undecided => High

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

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

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

[Touch-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

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

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

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

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


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

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

** Changed in: qtbase-opensource-src (Ubuntu Xenial)
   Importance: Undecided => High

** Tags added: verification-needed

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Fix Committed
Status in libappindicator source package in Xenial:
  Fix Committed
Status in qtbase-opensource-src source package in Xenial:
  New
Status in snapd source package in Xenial:
  New
Status in sni-qt source package in Xenial:
  Fix Committed

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator

  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.

  When snaps are generated in non updated systems, the icon will be
  still missing.

  [Regression potential]

  If $SNAP is defined for an app not running in snap confinement the
  icons couldn't be properly visible

  


  SRU bug for appmenu-qt5:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run qt5-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

  


  SRU bug for sni-qt:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as 
snapcraft.yaml
in any folder you want
  * Run:
- snapcraft prime

[Touch-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

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

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

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

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

** Changed in: sni-qt (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: sni-qt (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Fix Committed
Status in libappindicator source package in Xenial:
  Fix Committed
Status in qtbase-opensource-src source package in Xenial:
  New
Status in snapd source package in Xenial:
  New
Status in sni-qt source package in Xenial:
  Fix Committed

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator

  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.

  When snaps are generated in non updated systems, the icon will be
  still missing.

  [Regression potential]

  If $SNAP is defined for an app not running in snap confinement the
  icons couldn't be properly visible

  


  SRU bug for appmenu-qt5:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run qt5-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

  


  SRU bug for sni-qt:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as 
snapcraft.yaml
in any folder you want
  * Run:
- snapcraft prime
- sudo snap try prime
- snap run qt4-systray

  An indicator should open, with the

[Touch-packages] [Bug 1666111] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

2017-02-19 Thread Сергей Иванников

Public bug reported:

ubuntu 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
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.5
Architecture: amd64
Date: Fri Feb 17 21:45:57 2017
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
InstallationDate: Installed on 2017-02-17 (2 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in fontconfig package in Ubuntu:
  New

Bug description:
  ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  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.5
  Architecture: amd64
  Date: Fri Feb 17 21:45:57 2017
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2017-02-17 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1662044] Re: mir_acceptance_tests now takes 10 seconds longer (in r4002 compared to r4001)

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

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

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  mir_acceptance_tests now takes 10 seconds longer (in r4002 compared to
  r4001)

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

Bug description:
  mir_acceptance_tests now takes 10 seconds longer (in lp:mir compared
  to lp:mir/0.26)

  We may decide this isn't a bug, but sometimes these are simple
  mistakes...

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

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

[Touch-packages] [Bug 1661163] Re: [regression] mirout crashes when connecting to unity8 or any nested server: [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed: (ind

Fix committed to lp:mir/0.26 at revision 4029, scheduled for release in
Mir 0.26.2 (if at all)

** Changed in: mir/0.26
   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/1661163

Title:
  [regression] mirout crashes when connecting to unity8 or any nested
  server: [libprotobuf FATAL
  /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed:
  (index) < (current_size_):

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

Bug description:
  mirout crashes when connecting to unity8 or any nested server.

  $ mirout -- --desktop_file_hint=unity8
  Connected to server: 
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK 
failed: (index) < (current_size_):
  terminate called after throwing an instance of 
'google::protobuf::FatalException'
    what():  CHECK failed: (index) < (current_size_):
  Aborted (core dumped)

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

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

[Touch-packages] [Bug 1664760] Re: Mir server crashed with SIGSEGV in mir::compositor::TemporaryBuffer::size() called from mir::gl::tessellate_renderable_into_rectangle()

Fix committed to lp:mir/0.26 at revision 4028, scheduled for release in
Mir 0.26.2 (if at all)

** Changed in: mir/0.26
   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/1664760

Title:
  Mir server crashed with SIGSEGV in
  mir::compositor::TemporaryBuffer::size() called from
  mir::gl::tessellate_renderable_into_rectangle()

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

Bug description:
  I run mir exempla:
  ./bin/mir_demo_server --launch-client ./bin/mir_demo_client_multistrea
  mir_demo_server crash when I move central animated object to right border and 
back.

  Cause of crash is to call size() function from invalid pointer in
  temporaty_buffers.cpp mc::TemporaryBuffer::size() - line: return
  buffer->size();

  I have checked why pointer is invalid:

  In function: 
  std::shared_ptr 
mc::MultiMonitorArbiter::compositor_acquire(compositor::CompositorID id) from 
multi_monitor_arbiter.cpp 

  auto& last_entry = onscreen_buffers.front();
  last_entry.use_count++;
  if (mode == mc::MultiMonitorMode::multi_monitor_sync)
  clean_onscreen_buffers(lk);

  last_entry reference pointing not existing object (object is not longer in 
onscreen_buffers) after calling clean_onscreen_buffers() function.
  clean_onscreen_buffers() function looks correct for me - but after calling 
it, data remains inconsistent.

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

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

[Touch-packages] [Bug 1643488] Re: Rotating an output left or right without restarting the compositor distorts the image

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

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

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

** Changed in: mir
   Importance: High => Medium

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

Title:
  Rotating an output left or right without restarting the compositor
  distorts the image

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

Bug description:
  Rotating an output left or right without restarting the compositor
  distorts the image.

  Test case (using Mir 0.26 or later):
  1. Start a server
  2. Start a client
  3. mirout rotate right

  Expected: No distortion
  Observed: Distortion

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

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

[Touch-packages] [Bug 1660017] Re: EDID does not change when hotplugging a monitor

Fix committed to lp:mir/0.26 at revision 4027, scheduled for release in
Mir 0.26.2 (if at all)

** Changed in: mir/0.26
   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/1660017

Title:
  EDID does not change when hotplugging a monitor

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

Bug description:
  EDID does not change when hotplugging a monitor

  It appears Mir only gets the EDID right if the monitor was plugged in
  before the server started.

  If you change monitors, then Mir continues to report the old monitor's
  EDID. And similarly if the server started before the monitor was
  plugged in, Mir always reports no EDID for it.

  Other attributes like physical size appear to change correctly when
  hotplugging. Only the EDID is wrong.

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

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

[Touch-packages] [Bug 1661163] Re: [regression] mirout crashes when connecting to unity8 or any nested server: [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed: (ind

** Changed in: mir/0.26
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: mir (Ubuntu)
   Importance: Medium => High

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

Title:
  [regression] mirout crashes when connecting to unity8 or any nested
  server: [libprotobuf FATAL
  /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed:
  (index) < (current_size_):

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

Bug description:
  mirout crashes when connecting to unity8 or any nested server.

  $ mirout -- --desktop_file_hint=unity8
  Connected to server: 
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK 
failed: (index) < (current_size_):
  terminate called after throwing an instance of 
'google::protobuf::FatalException'
    what():  CHECK failed: (index) < (current_size_):
  Aborted (core dumped)

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

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

[Touch-packages] [Bug 1660017] Re: EDID does not change when hotplugging a monitor

** Changed in: mir/0.26
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  EDID does not change when hotplugging a monitor

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

Bug description:
  EDID does not change when hotplugging a monitor

  It appears Mir only gets the EDID right if the monitor was plugged in
  before the server started.

  If you change monitors, then Mir continues to report the old monitor's
  EDID. And similarly if the server started before the monitor was
  plugged in, Mir always reports no EDID for it.

  Other attributes like physical size appear to change correctly when
  hotplugging. Only the EDID is wrong.

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

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

[Touch-packages] [Bug 1664760] Re: Mir server crashed with SIGSEGV in mir::compositor::TemporaryBuffer::size() called from mir::gl::tessellate_renderable_into_rectangle()

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

Title:
  Mir server crashed with SIGSEGV in
  mir::compositor::TemporaryBuffer::size() called from
  mir::gl::tessellate_renderable_into_rectangle()

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

Bug description:
  I run mir exempla:
  ./bin/mir_demo_server --launch-client ./bin/mir_demo_client_multistrea
  mir_demo_server crash when I move central animated object to right border and 
back.

  Cause of crash is to call size() function from invalid pointer in
  temporaty_buffers.cpp mc::TemporaryBuffer::size() - line: return
  buffer->size();

  I have checked why pointer is invalid:

  In function: 
  std::shared_ptr 
mc::MultiMonitorArbiter::compositor_acquire(compositor::CompositorID id) from 
multi_monitor_arbiter.cpp 

  auto& last_entry = onscreen_buffers.front();
  last_entry.use_count++;
  if (mode == mc::MultiMonitorMode::multi_monitor_sync)
  clean_onscreen_buffers(lk);

  last_entry reference pointing not existing object (object is not longer in 
onscreen_buffers) after calling clean_onscreen_buffers() function.
  clean_onscreen_buffers() function looks correct for me - but after calling 
it, data remains inconsistent.

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

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

[Touch-packages] [Bug 1661163] Re: [regression] mirout crashes when connecting to unity8 or any nested server: [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed: (ind

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

Title:
  [regression] mirout crashes when connecting to unity8 or any nested
  server: [libprotobuf FATAL
  /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed:
  (index) < (current_size_):

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

Bug description:
  mirout crashes when connecting to unity8 or any nested server.

  $ mirout -- --desktop_file_hint=unity8
  Connected to server: 
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK 
failed: (index) < (current_size_):
  terminate called after throwing an instance of 
'google::protobuf::FatalException'
    what():  CHECK failed: (index) < (current_size_):
  Aborted (core dumped)

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

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

[Touch-packages] [Bug 1660017] Re: EDID does not change when hotplugging a monitor

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

Title:
  EDID does not change when hotplugging a monitor

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

Bug description:
  EDID does not change when hotplugging a monitor

  It appears Mir only gets the EDID right if the monitor was plugged in
  before the server started.

  If you change monitors, then Mir continues to report the old monitor's
  EDID. And similarly if the server started before the monitor was
  plugged in, Mir always reports no EDID for it.

  Other attributes like physical size appear to change correctly when
  hotplugging. Only the EDID is wrong.

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

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

[Touch-packages] [Bug 1664760] Re: Mir server crashed with SIGSEGV in mir::compositor::TemporaryBuffer::size() called from mir::gl::tessellate_renderable_into_rectangle()

** Summary changed:

- mir_demo_server crashed with SIGSEGV in 
mir::compositor::TemporaryBuffer::size() called from 
mir::gl::tessellate_renderable_into_rectangle()
+ Mir server crashed with SIGSEGV in mir::compositor::TemporaryBuffer::size() 
called from mir::gl::tessellate_renderable_into_rectangle()

** Changed in: mir/0.26
 Assignee: (unassigned) => Michał Kuchta (kuchtam)

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

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

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

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

Title:
  Mir server crashed with SIGSEGV in
  mir::compositor::TemporaryBuffer::size() called from
  mir::gl::tessellate_renderable_into_rectangle()

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

Bug description:
  I run mir exempla:
  ./bin/mir_demo_server --launch-client ./bin/mir_demo_client_multistrea
  mir_demo_server crash when I move central animated object to right border and 
back.

  Cause of crash is to call size() function from invalid pointer in
  temporaty_buffers.cpp mc::TemporaryBuffer::size() - line: return
  buffer->size();

  I have checked why pointer is invalid:

  In function: 
  std::shared_ptr 
mc::MultiMonitorArbiter::compositor_acquire(compositor::CompositorID id) from 
multi_monitor_arbiter.cpp 

  auto& last_entry = onscreen_buffers.front();
  last_entry.use_count++;
  if (mode == mc::MultiMonitorMode::multi_monitor_sync)
  clean_onscreen_buffers(lk);

  last_entry reference pointing not existing object (object is not longer in 
onscreen_buffers) after calling clean_onscreen_buffers() function.
  clean_onscreen_buffers() function looks correct for me - but after calling 
it, data remains inconsistent.

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

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

[Touch-packages] [Bug 1662942] Re: libmirclient-dev missing build depndency on libmircore-dev

Fix committed to lp:mir/0.26 at revision 4021, which was released in Mir
0.26.1

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

** Changed in: mir/0.26
Milestone: 0.26.2 => 0.26.1

** Changed in: mir/0.26
 Assignee: (unassigned) => Alan Griffiths (alan-griffiths)

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

Title:
  libmirclient-dev missing build depndency on libmircore-dev

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

Bug description:
  There is a broken build-dep in the Mir 0.26 packaging.

  Dialogue taken from IRC revealing the details:

   alan_g, when I include mir_toolkit header files in chromium I get 
this error:
   In file included from 
/usr/include/mirclient/mir_toolkit/events/event.h:90:
   #include "mir_toolkit/mir_input_device_types.h"
   and apt-file search doesn't return anything
   I wonder what I am missing
   is this a bug or there's a lib I should have installed?
   locate also cant find this file
   that's in libmircore-dev.  What do you get from $ pkg-config 
--cflags mirclient
   $ pkg-config --cflags mirclient
   -pthread -I/usr/include/mirclient -I/usr/include/mircookie 
-I/usr/include/mircore
   that lib was missing :)
   Then /usr/include/mircore/mir_toolkit/mir_input_device_types.h ought 
to be there
   :s
   ok installing mircore-dev fixed that
   apt-file should return it though :/
   Hmm. $ apt depends libmirclient-dev doesn't list libmircore-dev - 
sounds like a bug
   yes, when I ran apt-get build-dep libmirclient-dev mircore-dev was 
not installed

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

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

[Touch-packages] [Bug 460925] Re: Kernel log message corruption due to incomplete /proc separation

2017-02-19 Thread gilberto de lara

** Changed in: lxc (Ubuntu)
   Status: Triaged => Confirmed

** Changed in: linux (Ubuntu)
   Status: Triaged => Incomplete

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

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

Title:
  Kernel log message corruption due to incomplete /proc separation

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: lxc

  When using LXC (linux containers), /proc/kmsg can be read in guest
  systems in their filtered view of /proc.  This special file should
  never be present in guest systems, and if created within a guest
  system, it should be effectively using /dev/null as it's source.  The
  effect of this bug ranges from simply annoying to potentially a
  security issue in that kernel messages are allowed to be destroyed and
  never fully logged on the host system, which could be used to cover
  evidence of some sort of attack on the system.

  I'm adding the kernel team as well, as this could be an issue inside
  the kernel.  I'm not sure if /proc filtration happens there or in the
  context of the lxc userland utilities.

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

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

[Touch-packages] [Bug 1594266] Re: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Expired for hicolor-icon-theme (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: hicolor-icon-theme (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  Expired

Bug description:
  lors de la mise à jour d'Ubuntu vers la version 16.04 j'ai eu de nombreux 
messages d'erreurs dont je ne sais que faire. je ne suis pas developpeur et vos 
mises a jour intempestives m'ont mis dans l'embarras pour rester poli.
  que faire ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun 19 18:58:38 2016
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-01-04 (532 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-06-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1594266/+subscriptions

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

[Touch-packages] [Bug 1603620] Re: Package lists are not updated before Unattended upgrades runs automatically.

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Package lists are not updated before Unattended upgrades runs
  automatically.

Status in unattended-upgrades package in Ubuntu:
  Expired

Bug description:
  Newest kernel available currently is 4.4.0-31-generic, but

  $ linux-version list
  4.2.0-38-generic
  4.4.0-24-generic
  4.4.0-28-generic

  `apt-get dist-upgrade` does not upgrade kernel either, unless I run
  `apt-get update` first.

  I wonder why kernel was not upgraded 2016-07-16 morning.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jul 16 11:40:07 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (237 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (21 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-02-15T22:39:19.560937
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2016-06-24T18:13:45.181749

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

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

[Touch-packages] [Bug 1649419] Re: unable to install apps from ubuntu store

[Expired for ubuntu-system-settings-online-accounts (Ubuntu) because
there has been no activity for 60 days.]

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  unable to install apps from ubuntu store

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Expired

Bug description:
  Since OTA 13 I am not able to install ANY app from the ubuntu store on my BQ 
E5.
  I do click on install, then I am asked to confirm access to my UbuntuOne 
account and thats it, back to the install page.
  I tried several apps with the same negative result.
  I do have over 4GB free space, so that should not cause trouble.
  The phone has been rebooted a couple of times i.e. to upgrade to OTA 14.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1649419/+subscriptions

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

[Touch-packages] [Bug 363700] Re: Ctrl + right/left reversed in RTL

2017-02-19 Thread Bug Watch Updater

** Changed in: gtk
   Status: Confirmed => Fix Released

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

Title:
  Ctrl + right/left reversed in RTL

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

Bug description:
  Binary package hint: metacity

  Dear friends,

  When typing text in RTL (Hebrew here) and pressing Ctrl + right arrow,
  the text cursor goes one word to the LEFT and vice versa. Very
  amusing.

  It will be a pleasure to have it go the right way.

  Many blessings.

  This bug has a bounty on it:
  http://www.fossfactory.org/project/p197

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Package: metacity 1:2.25.144-0ubuntu2
  ProcEnviron:
   LANG=he_IL.UTF-8
   SHELL=/bin/bash
  SourcePackage: metacity
  Uname: Linux 2.6.28-11-generic i686

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

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

[Touch-packages] [Bug 1562344] Re: Not working hotkeys for brightness in HP ProBook 640 G2

2017-02-19 Thread Ying-Chun Liu

Verified. It works on HP ProBook. With 3.19 kernel at least. 3.13 kernel 
doesn't support the backlight of this machine.
Thanks.

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

Title:
  Not working hotkeys for brightness in HP ProBook 640 G2

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Released

Bug description:
  Description
  =

  It seems like a new HP laptops are using new vendor string which brokes
  hotkeys.

  
  Workaround
  ==

  Just to put following lines to fix hotkeys for brithness.

  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
   KEYBOARD_KEY_92=brightnessdown
   KEYBOARD_KEY_97=brightnessup

  
  Proposed solution
  ===

  The issue was already solved by upstream systemd[1] developers 25 days
  ago, so resync of hwdb/60-keyboard.hwdb should be enough.

[1]: commit 325de0ac23596209c252ebcc934dd5f5926fe2b6

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 26 17:20:25 2016
  InstallationDate: Installed on 2016-02-25 (30 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:7053 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 0a5c:640b Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 640 G2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic 
root=UUID=4bccba3c-0c3c-430f-bfef-b033d9fcd45c ro 
cryptopts=target=root,source=/dev/disk/by-uuid/9108c404-6977-4914-afd8-40b3e8824d30
 quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N76 Ver. 01.00
  dmi.board.name: 80FD
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 22.36
  dmi.chassis.asset.tag: 5CG605253R
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook640G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 640 G2
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2017-02-19 Thread Diego Liedo

I too have this bug on a Lenovo W520 with Ubuntu 16.04 kernel 4.4.0-62-generic
The only solution that has worked is restarting the network-manager service, 
however if I attach an USB WiFi adapter based on rtl8187, the icon becomes 
normal and I can choose a network for that adapter. The Intel Centrino 
Advanced-N 6205 remains unusable.
Also the interface name is wlp3s0 instead of the usual wlan0 on other 
installations I've made.
If I try $ ifdown wlp3s0 results in Unknown interface wlp3s0
As to comment #133 nm-applet still crashes after hardware switching off/on WiFi 
and resuming from 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/1589401

Title:
  cannot view wifi networks after re-enabling wifi

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

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

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

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

[Touch-packages] [Bug 1665598] Re: python-crypto throws exception ValueError: CTR mode needs counter parameter, not IV

2017-02-19 Thread Hung Nguyen Viet

I upgraded to 2.6.1-4ubuntu0.2
and no more exception, only see the warning print now.
Thank you for the fix

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

Title:
  python-crypto throws exception ValueError: CTR mode needs counter
  parameter, not IV

Status in OpenStack Charm Test Infra:
  Fix Released
Status in python-crypto package in Ubuntu:
  Fix Released

Bug description:
  We've recently upgraded python-crypto package on 14.04 due to this USN
  https://www.ubuntu.com/usn/usn-3199-1/

  
  apt history log

  ```
  Start-Date: 2017-02-16  23:43:48
  Commandline: apt-get -q -y -o DPkg::Options::=--force-confold -o 
DPkg::Options::=--force-confdef dist-upgrade
  Upgrade: bind9-host:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), 
liblwres90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), 
python-crypto:amd64 (2.6.1-4build1, 2.6.1-4ubuntu0.1), libdns100:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccfg90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libbind9-90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), dnsutils:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9utils:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccc90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisc95:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13)
  End-Date: 2017-02-16  23:43:52
  ```

  Then our python script which uses paramiko failed with this exception

  ```
  Traceback (most recent call last):
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1583, in run
  self.kex_engine.parse_next(ptype, m)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", 
line 68, in parse_next
  return self._parse_kexdh_reply(m)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", 
line 107, in _parse_kexdh_reply
  self.transport._activate_outbound()
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1881, in _activate_outbound
  engine = self._get_cipher(self.local_cipher, key_out, IV_out)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1500, in _get_cipher
  return self._cipher_info[name]['class'].new(key, 
self._cipher_info[name]['mode'], iv, counter)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 94, in 
new
  return AESCipher(key, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 59, in 
__init__
  blockalgo.BlockAlgo.__init__(self, _AES, key, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py", line 
141, in __init__
  self._cipher = factory.new(key, *args, **kwargs)
  ValueError: CTR mode needs counter parameter, not IV

  ```

  packages versions

  ```
  pycrypto==2.6.1
  paramiko==1.12.0
  ```

  which works okay BEFORE the upgrade.

  Maybe Debian bug report: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=850025

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-test-infra/+bug/1665598/+subscriptions

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

[Touch-packages] [Bug 1663048] Re: libmirclient in snaps gets out of sync with archive

** Summary changed:

- mirclient gets out of sync
+ libmirclient in snaps gets out of sync with archive

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

Title:
  libmirclient in snaps gets out of sync with archive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8-desktop-session package in Ubuntu:
  In Progress

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

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

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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

** Summary changed:

- Mir does not reset key states when paused or resumed
+ Mir does not reset key states when paused or resumed (modifiers get stuck 
after VT switching)

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

Title:
  Mir does not reset key states when paused or resumed (modifiers get
  stuck after VT switching)

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in QtMir:
  New
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Mir switches away from the current VT when ALT+FXX is pressed. During
  that key sequence the alt modifier is pressed. While away and mir does
  not receive the alt release. When you switch back to mir there is a
  chance that mir is not receiving the alt release either.

  So switching away and back to mir makes the alt key stick...

  Proposed solution:
  - track regular keys in mir::input::Seat or in SurfaceDispatcher
  - inform client(s) about pause / resume with a focus lost / focus gain event
  - attach key state to focus event or send separate key state event
  - adapt gdk/qt backends
  - fix alt key tracking in unity8 to rely on the provided modifier state

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

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

[Touch-packages] [Bug 1665682] Re: Popup menus stop working correctly after changing VT

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

Duplicate of bug 1536279 it seems.

** This bug has been marked a duplicate of bug 1536279
   Mir does not reset key states when paused or resumed (modifiers get stuck 
after VT switching)

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

Title:
  Popup menus stop working correctly after changing VT

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  My setup:
   * unity8-greeter as greeter
   * Logg in as user A to unity7 in VT8
   * Go back to the greeter 
   * Log in as user B to unity8 in VT7
   * Start kate
   * Right mouse button click on the document area
   * See popup menu correctly
   * close kate
   * Now change to VT8
   * Now change to VT7
   * Start kate
   * Right mouse button click on the document area
   * See popup menu just shows for a brief moment and hides immediately
  https://www.youtube.com/watch?v=f9aSC3CvCTs

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

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

[Touch-packages] [Bug 1665723] Re: Maximized window hidden under launcher after exit fullscreen

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

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

** Also affects: miral
   Importance: Undecided
   Status: New

** Changed in: miral
   Importance: Undecided => High

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

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

** Tags added: unity8-desktop

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

Title:
  Maximized window hidden under launcher after exit fullscreen

Status in Canonical System Image:
  New
Status in MirAL:
  New
Status in miral package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Running unity8 deb session on xenial + overlay

  Steps to reproduce
  1) Launcher set for always show
  2) start webbrowser-app, maximize browser with window control, note that 
browser is not obscured at all by launcher
  3) press F11 to go full screen, window correctly goes fullscreen
  4) press F11 to exit full screen, 
  5) Expected results: window should be maximized but not obscured by launcher. 
Actual results: window is maximized bu obscured by launcher

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

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

[Touch-packages] [Bug 1665724] Re: Child window leaving fullscreen when move mouse to bottom right corner of screen

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

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

** Tags added: unity8-desktop

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

Title:
  Child window leaving fullscreen when move mouse to bottom right corner
  of screen

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

Bug description:
  running unity8 desktop deb session on xenial + overlay

  - Launcher set to always show
  1) open youtube.com in webbrowser-app
  2) maximize browser
  3) play a video 
  4) click the fullscreen button on bottom right, video now playing in 
fullscreen mode
  5) move mouse cursor to bottom right of screen, 
  6) Expected result: no change in window. 

  Actual result: 
  window leaves fullscreen mode, shows window controls and black border where 
launcher usually is, bottom of window is cutoff. Stuck in this state until you 
press esc, which then causes parent browser window to be obscured by launcher 
again (see lp:1665723)

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

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

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

If /etc/apparmor.d/usr.bin.webbrowser-app is related to the
problem/solution then the correct package is 'webbrowser-app'. Re-
confirmed.

** Changed in: webbrowser-app (Ubuntu)
   Status: Invalid => Confirmed

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

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

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 1666088] [NEW] In my notebook Samsung Q330 excess VGA-1 display

2017-02-19 Thread unicorp99

Public bug reported:

After install excess VGA-1 display.
I may disable VGA-1 in screen. I use Laptop Screen, 1366x768.
If i conncect external monitor through vga cable, In displays appears VGA-1-2, 
it is work.
My video:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated 
Graphics Controller (rev 02)
02:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] 
(rev a2)

lsmod:
nouveau  1404928  1
i915 1245184  21

it is in 4.8 kernel and in 4.4 kernel KUBUNTU 16.04.2 LTS

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg (not installed)
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
Date: Mon Feb 20 05:40:12 2017
InstallationDate: Installed on 2016-05-03 (292 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 xenial

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

Title:
  In my notebook Samsung Q330 excess VGA-1 display

Status in xorg package in Ubuntu:
  New

Bug description:
  After install excess VGA-1 display.
  I may disable VGA-1 in screen. I use Laptop Screen, 1366x768.
  If i conncect external monitor through vga cable, In displays appears 
VGA-1-2, it is work.
  My video:
  00:02.0 VGA compatible controller: Intel Corporation Core Processor 
Integrated Graphics Controller (rev 02)
  02:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] 
(rev a2)

  lsmod:
  nouveau  1404928  1
  i915 1245184  21

  it is in 4.8 kernel and in 4.4 kernel KUBUNTU 16.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Mon Feb 20 05:40:12 2017
  InstallationDate: Installed on 2016-05-03 (292 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1666084] [NEW] external monitor not supported on 16.10

2017-02-19 Thread Richard Pickett

Public bug reported:

Lenovo w530 w/ Nvidia GK107GLM [Quadro K2000M]

Nouveau finds the VGA monitor and everything works *but* the monitor is
laggy. Seems that's a known issue.

So I install the nvidia driver (add-apt-repository ppa:graphics-
drivers/ppa; apt-get update; apt-get install nvidia-378), but when the
laptop reboots I don't have the second monitor. It doesn't show up in
nvidia-setup.

I've gone back as far as nvidia-304 (yes, one at a time, yes rebuilding
ramdisk and full rebooting, and yes it's slow and painful), but none of
them give me the plugged in monitor.

I'm happy if you want to walk me through get/patch/compile to do
testing. I'd just like (a) a non-laggy experience on the second monitor.

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  378.13  Tue Feb  7 20:10:06 
PST 2017
 GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Feb 19 18:05:39 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.8.0-37-generic, x86_64: installed
 nvidia-378, 378.13, 4.8.0-37-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
 NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
InstallationDate: Installed on 2017-02-19 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: LENOVO 2436CTO
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/17/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G5ET91WW (2.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2436CTO
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET91WW(2.51):bd01/17/2013:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2436CTO
dmi.product.version: ThinkPad W530
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Sun Feb 19 17:51:44 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1

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


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

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

Title:
  external monitor not supported on 16.10

Status in xorg package in Ubuntu:
  New

Bug description:
  Lenovo w530 w/ Nvidia GK107GLM [Quadro K2000M]

  Nouveau finds the VGA monitor and everything works *but* the monitor
  is laggy. Seems that's a known issue.

  So I install the nvidia driver (add-apt-repository ppa:graphics-
  drivers/ppa; apt-get update; apt-get install nvidia-378), but when the
  laptop reboots I don't have the second monitor. It doesn't show up in
  nvidia-setup.

  I've gone back as far as nvidia-304 (yes, one at a time, yes
  rebuilding ramdisk and full rebooting, and yes it's slow and

[Touch-packages] [Bug 1663345] Re: 10-15 seconds delay until host is resolved

2017-02-19 Thread Null_Sieben

Sorry  with or without "nameserver 127.0.0.1" in
/etc/resolvconf/resolv.conf.d/head:

DNS queries are running normal .. seems I cannot reproduce the
error.   :-(

@jdthood: Thanks a lot! Hopefully your hints help others.

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

Title:
  10-15 seconds delay until host is resolved

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  I have the problem that every new DNS query takes about 10 - 15
  seconds.

  This is the first time I used "ubuntu-bug resolvconf". Hopefully all
  information of my system are attached to this report.

  Thanks for help or hints:)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: resolvconf 1.79ubuntu1
  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: Thu Feb  9 19:36:34 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-22 (18 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.resolvconf.resolv.conf.d.head:
   # Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
   # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
   nameserver 127.0.0.1
  mtime.conffile..etc.resolvconf.resolv.conf.d.head: 2017-02-09T18:49:48.934789

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2017-02-19 Thread Kevin Cook

** Also affects: unattended-upgrades
   Importance: Undecided
   Status: 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/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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

[Touch-packages] [Bug 1665914] Re: Ubuntu 16.04 freezes on Thinkpad X61 Tablet when touched by the stylus

2017-02-19 Thread František Kučera

This issue is probably related to the Wacom driver w8001 (see [1] and
[2], thanks [3]).

When I tried `cat /dev/input/mice` in console, system crashed in the
same way as in X, but I got at least some error message (see
attachement).

[1] https://lkml.org/lkml/2016/5/22/169
[2]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/input/touchscreen/wacom_w8001.c
[3] https://www.abclinuxu.cz/poradna/hardware/show/423751

** Attachment added: "error message after `cat /dev/input/mice` and touching
the screen by the stylus"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1665914/+attachment/4822261/+files/ThinkPad%20X61%20Tablet%20-%20crash%20-%20freeze.jpeg

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

Title:
Ubuntu 16.04 freezes on Thinkpad X61 Tablet when touched by the stylus

Status in xorg package in Ubuntu:
New

Bug description:
I have (up to date) Ubuntu 16.04 on IBM Thinkpad X61 Tablet. I can use
the stylus to move the cursor – but when I touch the screen with it
(i.e. click), the system immediately freezes.

When I touch it without X, in the text mode (Ctrl+Alt+F1) it does not
freeze.

I tried to debug it over network, but the network also freezes at the
same moment.

When I try QubesOS (with kernel 4.1.13-9.pvops.qubes.x86_64) on the
same machine, the stylus works correctly and the system does not
freeze.

Any tips how to debug it? Maybe using the serial port (I have the
docking station with RS232). Or I can try some older releases and find
the last one that was working if it helps.

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

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

[Touch-packages] [Bug 1665902] Re: Update zeitgeist to 1.0

2017-02-19 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Update zeitgeist to 1.0

Status in zeitgeist package in Ubuntu:
  Triaged

Bug description:
  Zeitgeist 1.0 has been released!

  https://launchpad.net/zeitgeist/1.0/1.0

   - Drop dependency on gnome-common and intltool
   - Use GNU gettext only
   - Fix some valac warnings
   - Use $PYTHON to check for rdflib
   - Install zeitgeist-fts to pkglibexecdir rather than
 libexecdir
   - Use correct names for D-Bus service files
   - Add systemd user service for each D-Bus session service
   - Fix bash auto-completions script
   - Add --vacuum option to Daemon to perform VACUUM SQLite
 database

  Libzeitgeist:
   - Ensure the log mainloop uses the current thread's context
 when waiting

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

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

[Touch-packages] [Bug 1665902] Re: Update zeitgeist to 1.0

** Changed in: zeitgeist (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Update zeitgeist to 1.0

Status in zeitgeist package in Ubuntu:
  Triaged

Bug description:
  Zeitgeist 1.0 has been released!

  https://launchpad.net/zeitgeist/1.0/1.0

   - Drop dependency on gnome-common and intltool
   - Use GNU gettext only
   - Fix some valac warnings
   - Use $PYTHON to check for rdflib
   - Install zeitgeist-fts to pkglibexecdir rather than
 libexecdir
   - Use correct names for D-Bus service files
   - Add systemd user service for each D-Bus session service
   - Fix bash auto-completions script
   - Add --vacuum option to Daemon to perform VACUUM SQLite
 database

  Libzeitgeist:
   - Ensure the log mainloop uses the current thread's context
 when waiting

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

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

[Touch-packages] [Bug 1666044] Re: package dash 0.5.5.1-3ubuntu2 failed to install/upgrade: подпроцесс dpkg-deb --fsys-tarfile возвратил код ошибки 2

2017-02-19 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: fsys-tarfile-error

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

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

Title:
  package dash 0.5.5.1-3ubuntu2 failed to install/upgrade: подпроцесс
  dpkg-deb --fsys-tarfile возвратил код ошибки 2

Status in dash package in Ubuntu:
  Invalid

Bug description:
  sergey@sergey-laptop:~$ sudo apt-get upgrade
  Чтение списков пакетов... Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии... Готово
  Пакеты, которые будут оставлены в неизменном виде:
adduser aisleriot alacarte alsa-base alsa-utils anacron apparmor 
apparmor-utils apport apport-gtk apt apt-transport-https
apt-utils apt-xapian-index aptdaemon aptitude apturl apturl-common aspell 
at avahi-daemon banshee base-files bash
bash-completion bind9-host binfmt-support bluez bluez-cups bogofilter-bdb 
brltty brltty-x11 bsdmainutils bsdutils
ca-certificates checkbox cheese cheese-common command-not-found 
console-setup consolekit coreutils couchdb-bin cpio cpp
cpu-checker cron cryptsetup cups cups-bsd cups-client dbus dbus-x11 dcraw 
debianutils desktop-file-utils
dictionaries-common diffutils dmraid dmsetup dnsmasq-base dnsutils doc-base 
docbook-xml dpkg dvd+rw-tools e2fslibs
e2fsprogs ecryptfs-utils empathy empathy-common eog erlang-base 
erlang-crypto erlang-inets erlang-mnesia
erlang-public-key erlang-runtime-tools erlang-ssl erlang-syntax-tools 
erlang-xmerl esound-common espeak espeak-data
evince evolution evolution-common evolution-data-server 
evolution-data-server-common evolution-indicator
evolution-plugins fancontrol file file-roller findutils firefox 
flashplugin-installer fontconfig fontconfig-config
foomatic-db foomatic-db-engine foomatic-filters friendly-recovery ftp gamin 
gawk gcalctool gconf-defaults-service
gconf-editor gconf2 gconf2-common gdb gdebi gdebi-core gdm gedit 
gedit-common genisoimage gettext-base ghostscript
ghostscript-x gnome-applets gnome-applets-data gnome-bluetooth 
gnome-control-center gnome-disk-utility gnome-doc-utils
gnome-icon-theme gnome-keyring gnome-mahjongg gnome-menus gnome-nettool 
gnome-orca gnome-panel gnome-panel-data
gnome-power-manager gnome-screensaver gnome-session gnome-session-bin 
gnome-session-canberra gnome-settings-daemon
gnome-sudoku gnome-system-monitor gnome-system-tools gnome-terminal 
gnome-terminal-data gnome-user-guide gnome-user-share
gnupg gparted grub-common grub-pc gstreamer0.10-alsa gstreamer0.10-nice 
gstreamer0.10-plugins-base
gstreamer0.10-plugins-base-apps gstreamer0.10-plugins-good 
gstreamer0.10-pulseaudio gstreamer0.10-tools gstreamer0.10-x
gtk2-engines gtk2-engines-murrine gtk2-engines-pixbuf gucharmap 
guile-1.8-libs gvfs gvfs-backends gvfs-bin gvfs-fuse gzip
hostname hplip hplip-data humanity-icon-theme ibus ibus-gtk ibus-m17n 
ibus-table ifupdown imagemagick indicator-applet
indicator-applet-session indicator-application indicator-messages 
indicator-session indicator-sound info initramfs-tools
initramfs-tools-bin initscripts inputattach install-info intel-gpu-tools 
iproute iptables iputils-ping iputils-tracepath
irqbalance kerneloops-daemon keyutils klibc-utils language-pack-bn 
language-pack-bn-base language-pack-de
language-pack-de-base language-pack-en language-pack-en-base 
language-pack-es language-pack-es-base language-pack-fr
language-pack-fr-base language-pack-gnome-bn language-pack-gnome-bn-base 
language-pack-gnome-de
language-pack-gnome-de-base language-pack-gnome-en 
language-pack-gnome-en-base language-pack-gnome-es
language-pack-gnome-es-base language-pack-gnome-fr 
language-pack-gnome-fr-base language-pack-gnome-pt
language-pack-gnome-pt-base language-pack-gnome-xh 
language-pack-gnome-xh-base language-pack-pt language-pack-pt-base
language-pack-xh language-pack-xh-base language-selector-common less lftp 
libaa1 libacl1 libapparmor-perl libapparmor1
libart-2.0-2 libart2.0-cil libasound2 libasound2-plugins libaspell15 
libatasmart4 libatk1.0-0 libatm1 libattr1 libaudio2
libavahi-client3 libavahi-gobject0 libavahi-ui0 libblkid1 libbluetooth3 
libbonobo2-0

[Touch-packages] [Bug 1629541] Re: Ubuntu Touch should indicate that battery is charging with LED indicator on device

2017-02-19 Thread Norbert

Same on M10 with staging r148.

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

Title:
  Ubuntu Touch should indicate that battery is charging with LED
  indicator on device

Status in indicator-power package in Ubuntu:
  New

Bug description:
  I have BQ M10 FHD Ubuntu Edition with OTA-13.
  This device has LED indicator.

  Steps to reproduce:
  1. Boot device.
  2. Connect microusb charger.
  3. Device will start to charge (tray indicator becomes green with zigzag, but 
device's LED is off).

  Expected result:
  Device LED indicates charge level as on Android devices:
  * red for critical level
  * orange for middle
  * yellow for low 
  * green for almost charged).

  Actual result:
  Device LED is off.

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

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

[Touch-packages] [Bug 1665902] Re: Update zeitgeist to 1.0

Marco, could you look into updating startup-database-vacuum.patch for
this new version?

I'm attaching a debdiff against the current version in zesty with
everything else needed for this update except that patch update.

This is the current patch:
https://sources.debian.net/src/zeitgeist/0.9.16-0.2/debian/patches/startup-database-vacuum.patch/

And this is what was merged into zeitgeist 1.0:
https://cgit.freedesktop.org/zeitgeist/zeitgeist/commit/?id=1a15b1c1

** Patch added: "update-zeitgeist-lp1665902.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1665902/+attachment/4822231/+files/update-zeitgeist-lp1665902.debdiff

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

Title:
  Update zeitgeist to 1.0

Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  Zeitgeist 1.0 has been released!

  https://launchpad.net/zeitgeist/1.0/1.0

   - Drop dependency on gnome-common and intltool
   - Use GNU gettext only
   - Fix some valac warnings
   - Use $PYTHON to check for rdflib
   - Install zeitgeist-fts to pkglibexecdir rather than
 libexecdir
   - Use correct names for D-Bus service files
   - Add systemd user service for each D-Bus session service
   - Fix bash auto-completions script
   - Add --vacuum option to Daemon to perform VACUUM SQLite
 database

  Libzeitgeist:
   - Ensure the log mainloop uses the current thread's context
 when waiting

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

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

[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

2017-02-19 Thread Serious Diman

After upgrade to Ubuntu 16.10 from 15.04 or 15.10 (I can't remember). Same 
here. NetworkManager does not manage my wired eth0 connection.
/etc/network/interfaces and /etc/NetworkManager/NetworkManager.conf exactly as 
in "Aron Xu (happyaron) wrote on 2017-01-26" post.
Additionally my NetworkManager shows previously working bluetooth-modem 
connection "device not managed."

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Touch-packages] [Bug 1533343] Re: No sound from internal speakers after boot with connected headphones

2017-02-19 Thread Jimisola Laursen

Asus UX303U. Problem started on Ubuntu 16.04 after a regular software upgrade 
(apt upgrade).
I have sound through headphones but not internal speakers. The sound in the 
speakers came back after I plugged and unplugged my headphones several times 
and remained until after reboot.

I've check all sound settings including using alsamixer (nothing is
muted). This bug really limits the use of my laptop.


** Attachment added: "Update of packages that most likely caused the problem."
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1533343/+attachment/4822195/+files/apt-failed-sound-upgrade.log

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

Title:
  No sound from internal speakers after boot with connected headphones

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On Lenovo L450 laptop, when I boot the PC with headphones attached,
  then the sound via headphones will work, but there will be no sound
  from internal speakers when headphones are detached.

  I tested this couple of times and the problem is always reproduced.
  This is the procedure A:

  1. When the problem is not present, sound is present in laptop's speakers, 
connect the headphones
  2. initiate reboot
  3. once booted, initiate playing of some audio and check the sound from 
headphones - it will work OK
  4. disconnect the headphones - there is no sound from internal speakers

  Procedure B:
  1. turn off the laptop (power off)
  2. connect the headphones to the laptop
  3. power on the laptop and boot into Ubuntu 15.10
  4. once booted, initiate playing of some audio and check the sound from 
headphones - it will work OK
  5. disconnect the headphones - there is no sound from internal speakers

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ygzo   2125 F pulseaudio
   /dev/snd/controlC0:  ygzo   2125 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 12 20:44:49 2016
  InstallationDate: Installed on 2015-10-05 (99 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [20DT0003XS, Realtek ALC3232, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to wily on 2015-11-03 (70 days ago)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET54WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET54WW(1.16):bd08/19/2015:svnLENOVO:pn20DT0003XS:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT0003XS
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1587326] Re: package gconf2 3.2.6-3ubuntu5 failed to install/upgrade: problèmes de dépendances - actions différées non exécutées

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

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

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

Title:
  package gconf2 3.2.6-3ubuntu5 failed to install/upgrade: problèmes de
  dépendances - actions différées non exécutées

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  When I was upgrading the system (with do-release-upgrade), I've encountered 
the following error:
  dpkg: des problèmes de dépendances empêchent le traitement des actions 
différées pour gconf2 :
   gconf2 dépend de python3 ; cependant :
   Le paquet python3 n'est pas encore configuré.

  dpkg: erreur de traitement du paquet gconf2 (--configure) :
   problèmes de dépendances - actions différées non exécutées
  Error in function:

  SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 480, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 433, in write
  block = f.read(1048576)
File "/usr/lib/python3.4/codecs.py", line 319, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was: 
  SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gconf2.0.crash'

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Tue May 31 10:05:41 2016
  DuplicateSignature: package:gconf2:3.2.6-3ubuntu5:problèmes de dépendances - 
actions différées non exécutées
  ErrorMessage: problèmes de dépendances - actions différées non exécutées
  InstallationDate: Installed on 2016-01-12 (139 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu5 failed to install/upgrade: problèmes de 
dépendances - actions différées non exécutées
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (0 days ago)

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

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

[Touch-packages] [Bug 1665902] Re: Update zeitgeist to 1.0

2017-02-19 Thread Rico Tzschichholz

** Description changed:

  Zeitgeist 1.0 has been released!
  
- https://launchpad.net/zeitgeist/0.9/1.0
+ https://launchpad.net/zeitgeist/1.0/1.0
  
   - Drop dependency on gnome-common and intltool
   - Use GNU gettext only
   - Fix some valac warnings
   - Use $PYTHON to check for rdflib
   - Install zeitgeist-fts to pkglibexecdir rather than
 libexecdir
   - Use correct names for D-Bus service files
   - Add systemd user service for each D-Bus session service
   - Fix bash auto-completions script
   - Add --vacuum option to Daemon to perform VACUUM SQLite
 database
  
  Libzeitgeist:
   - Ensure the log mainloop uses the current thread's context
 when waiting

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

Title:
  Update zeitgeist to 1.0

Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  Zeitgeist 1.0 has been released!

  https://launchpad.net/zeitgeist/1.0/1.0

   - Drop dependency on gnome-common and intltool
   - Use GNU gettext only
   - Fix some valac warnings
   - Use $PYTHON to check for rdflib
   - Install zeitgeist-fts to pkglibexecdir rather than
 libexecdir
   - Use correct names for D-Bus service files
   - Add systemd user service for each D-Bus session service
   - Fix bash auto-completions script
   - Add --vacuum option to Daemon to perform VACUUM SQLite
 database

  Libzeitgeist:
   - Ensure the log mainloop uses the current thread's context
 when waiting

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

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

[Touch-packages] [Bug 1663345] Re: 10-15 seconds delay until host is resolved

2017-02-19 Thread Thomas Hood

Wait a sec, I just noticed that you have the line "nameserver 127.0.0.1"
in your /etc/resolvconf/resolv.conf.d/head file. Remove that line, it
shouldn't be there.

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

Title:
  10-15 seconds delay until host is resolved

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  I have the problem that every new DNS query takes about 10 - 15
  seconds.

  This is the first time I used "ubuntu-bug resolvconf". Hopefully all
  information of my system are attached to this report.

  Thanks for help or hints:)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: resolvconf 1.79ubuntu1
  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: Thu Feb  9 19:36:34 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-22 (18 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.resolvconf.resolv.conf.d.head:
   # Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
   # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
   nameserver 127.0.0.1
  mtime.conffile..etc.resolvconf.resolv.conf.d.head: 2017-02-09T18:49:48.934789

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

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

[Touch-packages] [Bug 1663345] Re: 10-15 seconds delay until host is resolved

2017-02-19 Thread Thomas Hood

Please post the output of /usr/share/resolvconf/dump-debug-info run from
a terminal.

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

Title:
  10-15 seconds delay until host is resolved

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  I have the problem that every new DNS query takes about 10 - 15
  seconds.

  This is the first time I used "ubuntu-bug resolvconf". Hopefully all
  information of my system are attached to this report.

  Thanks for help or hints:)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: resolvconf 1.79ubuntu1
  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: Thu Feb  9 19:36:34 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-22 (18 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.resolvconf.resolv.conf.d.head:
   # Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
   # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
   nameserver 127.0.0.1
  mtime.conffile..etc.resolvconf.resolv.conf.d.head: 2017-02-09T18:49:48.934789

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

2017-02-19 Thread LaMont Jones

Also true when TERM=screen -- I suspect it doesn't care what terminal
you're using, if it can grab mouse events, it does.

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

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

[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

2017-02-19 Thread O. Farid

Here is a screenshot that I made when the fonts are missing.

** Attachment added: "ScreenshotBugCharNautilus.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4822150/+files/ScreenshotBugCharNautilus.png

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1666044] [NEW] package dash 0.5.5.1-3ubuntu2 failed to install/upgrade: подпроцесс dpkg-deb --fsys-tarfile возвратил код ошибки 2

2017-02-19 Thread Sergey Zhitar

Public bug reported:

sergey@sergey-laptop:~$ sudo apt-get upgrade
Чтение списков пакетов... Готово
Построение дерева зависимостей   
Чтение информации о состоянии... Готово
Пакеты, которые будут оставлены в неизменном виде:
  adduser aisleriot alacarte alsa-base alsa-utils anacron apparmor 
apparmor-utils apport apport-gtk apt apt-transport-https
  apt-utils apt-xapian-index aptdaemon aptitude apturl apturl-common aspell at 
avahi-daemon banshee base-files bash
  bash-completion bind9-host binfmt-support bluez bluez-cups bogofilter-bdb 
brltty brltty-x11 bsdmainutils bsdutils
  ca-certificates checkbox cheese cheese-common command-not-found console-setup 
consolekit coreutils couchdb-bin cpio cpp
  cpu-checker cron cryptsetup cups cups-bsd cups-client dbus dbus-x11 dcraw 
debianutils desktop-file-utils
  dictionaries-common diffutils dmraid dmsetup dnsmasq-base dnsutils doc-base 
docbook-xml dpkg dvd+rw-tools e2fslibs
  e2fsprogs ecryptfs-utils empathy empathy-common eog erlang-base erlang-crypto 
erlang-inets erlang-mnesia
  erlang-public-key erlang-runtime-tools erlang-ssl erlang-syntax-tools 
erlang-xmerl esound-common espeak espeak-data
  evince evolution evolution-common evolution-data-server 
evolution-data-server-common evolution-indicator
  evolution-plugins fancontrol file file-roller findutils firefox 
flashplugin-installer fontconfig fontconfig-config
  foomatic-db foomatic-db-engine foomatic-filters friendly-recovery ftp gamin 
gawk gcalctool gconf-defaults-service
  gconf-editor gconf2 gconf2-common gdb gdebi gdebi-core gdm gedit gedit-common 
genisoimage gettext-base ghostscript
  ghostscript-x gnome-applets gnome-applets-data gnome-bluetooth 
gnome-control-center gnome-disk-utility gnome-doc-utils
  gnome-icon-theme gnome-keyring gnome-mahjongg gnome-menus gnome-nettool 
gnome-orca gnome-panel gnome-panel-data
  gnome-power-manager gnome-screensaver gnome-session gnome-session-bin 
gnome-session-canberra gnome-settings-daemon
  gnome-sudoku gnome-system-monitor gnome-system-tools gnome-terminal 
gnome-terminal-data gnome-user-guide gnome-user-share
  gnupg gparted grub-common grub-pc gstreamer0.10-alsa gstreamer0.10-nice 
gstreamer0.10-plugins-base
  gstreamer0.10-plugins-base-apps gstreamer0.10-plugins-good 
gstreamer0.10-pulseaudio gstreamer0.10-tools gstreamer0.10-x
  gtk2-engines gtk2-engines-murrine gtk2-engines-pixbuf gucharmap 
guile-1.8-libs gvfs gvfs-backends gvfs-bin gvfs-fuse gzip
  hostname hplip hplip-data humanity-icon-theme ibus ibus-gtk ibus-m17n 
ibus-table ifupdown imagemagick indicator-applet
  indicator-applet-session indicator-application indicator-messages 
indicator-session indicator-sound info initramfs-tools
  initramfs-tools-bin initscripts inputattach install-info intel-gpu-tools 
iproute iptables iputils-ping iputils-tracepath
  irqbalance kerneloops-daemon keyutils klibc-utils language-pack-bn 
language-pack-bn-base language-pack-de
  language-pack-de-base language-pack-en language-pack-en-base language-pack-es 
language-pack-es-base language-pack-fr
  language-pack-fr-base language-pack-gnome-bn language-pack-gnome-bn-base 
language-pack-gnome-de
  language-pack-gnome-de-base language-pack-gnome-en 
language-pack-gnome-en-base language-pack-gnome-es
  language-pack-gnome-es-base language-pack-gnome-fr 
language-pack-gnome-fr-base language-pack-gnome-pt
  language-pack-gnome-pt-base language-pack-gnome-xh 
language-pack-gnome-xh-base language-pack-pt language-pack-pt-base
  language-pack-xh language-pack-xh-base language-selector-common less lftp 
libaa1 libacl1 libapparmor-perl libapparmor1
  libart-2.0-2 libart2.0-cil libasound2 libasound2-plugins libaspell15 
libatasmart4 libatk1.0-0 libatm1 libattr1 libaudio2
  libavahi-client3 libavahi-gobject0 libavahi-ui0 libblkid1 libbluetooth3 
libbonobo2-0 libbonobo2-common libbonoboui2-0
  libbsd0 libc-bin libc6 libcaca0 libcairo-perl libcairo2 
libcanberra-gtk-module libcanberra-gtk0 libcanberra-pulse
  libcanberra0 libcdparanoia0 libck-connector0 libclutter-1.0-0 libcomerr2 
libcups2 libcupscgi1 libcupsimage2 libcupsmime1
  libcupsppdc1 libcurl3 libcurl3-gnutls libdaemon0 libdbus-1-3 libdbus-glib-1-2 
libdc1394-22 libdca0 libdevmapper1.02.1
  libdjvulibre21 libdrm-intel1 libdrm-radeon1 libdrm2 libedit2 libeet1 
libelementary-data libenchant1c2a libesd0 libespeak1
  libexempi3 libexif12 libfaad2 libfakekey0 libfftw3-3 libfontconfig1 libfs6 
libfuse2 libgadu3 libgail-common libgail18
  libgamin0 libgcc1 libgconf2-4 libgconf2.0-cil libgdbm3 libgdiplus libgksu2-0 
libgl1-mesa-dri libgl1-mesa-glx libglade2-0
  libglade2.0-cil libglib-perl libglib2.0-0 libglib2.0-cil libgnome-keyring0 
libgnome-keyring1.0-cil libgnome-vfs2.0-cil
  libgnome2-0 libgnome2-canvas-perl libgnome2-common libgnome2-perl 
libgnome2-vfs-perl libgnome2.24-cil libgnomecanvas2-0
  libgnomekbd-common libgnomeui-0 libgnomevfs2-0 libgnomevfs2-common 
libgnomevfs2-extra libgomp1 libgpg-error0 libgpgme11
  libgpm2 libgpod-common libgpod4 libgsf-1-114

[Touch-packages] [Bug 563719] Re: Ctrl+Left/Right in a right-to-left written language moves the curser incorrectly

2017-02-19 Thread Bug Watch Updater

** Changed in: gtk
   Status: Confirmed => Fix Released

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

Title:
  Ctrl+Left/Right in a right-to-left written language moves the curser
  incorrectly

Status in GTK+:
  Fix Released
Status in gedit package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  When writing in a right-to-left written language, such as Hebrew, the
  left and right keys on their keyboard change their meaning: left moves
  to the next character, and right moves the cursor to the previous
  character. This works correctly in gedit. However, when using the Ctrl
  modifier, Ctrl-Left should move to the next word, and Ctrl-Right
  should move to the previous word. This currently doesn't work in
  gedit. Instead Ctrl-Left/Right works the same as in English.

  To test this in gedit you can copy the following Hebrew text into gedit:
  משפט קצר לנסיון.
  Put the cursor at the sentence beginning (which is the rightmost word. By 
using Home for example), and then press Ctrl-Left. Instead of moving to the 
next word (the middle one), the cursor just stays at the beginning. Now press 
Ctrl-Right. Instead of staying, the cursor moves to the next word.

  Regards,
  Haggai

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gedit 2.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  Architecture: i386
  Date: Thu Apr 15 13:46:01 2010
  ExecutablePath: /usr/bin/gedit
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 
(20091028.4)
  ProcEnviron:
   PATH=(custom, user)
   LANG=he_IL.utf8
   SHELL=/bin/bash
  SourcePackage: gedit

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

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

[Touch-packages] [Bug 1666021] Re: zesty systemd-resolve timeout

I worked around the high CPU usage by running

sudo systemctl restart systemd-resolved.service

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

Title:
  zesty systemd-resolve timeout

Status in systemd package in Ubuntu:
  New

Bug description:
  I rebooted my zesty install today so it has network-manager
  1.4.4-1ubuntu2 (re-enabled resolved by default for DNS) and systemd
  232-17ubuntu1 (which is supposed to fix the CNAME problems that got
  resolved by default reverted earlier in zesty).

  I had various DNS issues so I rebooted.

  When I rebooted, I opened up Firefox and browsed several sites.
  I opened a terminal and ran sudo apt update. I disabled a PPA and enabled a 
different PPA and ran sudo apt update then sudo apt dist-upgrade (there were 3 
updates).

  When apt was downloading one of those new packages, it paused mid-
  download. I was unable to browse sites in Firefox. I ran this command
  in a different terminal:

  $ systemd-resolve --status
  Failed to get global data: Connection timed out

  I checked journalctl and there was a very large number of these entries:
  systemd-resolved[3260]: Processing query...

  Finally followed by this repeated 3 times:
  dnsmasq[3563]: Maximum number of concurrent DNS queries reached (max: 150)

  Eventually, after I guess a couple minutes, things returned to normal.
  The apt upgrade completed. systemd-resolve --status looked better and
  I'm able to use Firefox again (to report this bug).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-17ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Feb 19 09:54:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (191 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80SA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=352e459f-ebca-4dc8-86e3-b078a000910b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2016-12-20 (60 days ago)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0VCN22WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1470
  dmi.modalias: 
dmi:bvnLENOVO:bvr0VCN22WW(V1.06):bd09/26/2016:svnLENOVO:pn80SA:pvrLenovoideapadFLEX4-1470:rvnLENOVO:rnLenovoideapadF:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1470:
  dmi.product.name: 80SA
  dmi.product.version: Lenovo ideapad FLEX 4-1470
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1666021] Re: zesty systemd-resolve timeout

Look at the top two items using my CPU in the attached screenshot
(systemd-resolve and dnsmasq)

** Attachment added: "systemd-resolve-high-cpu.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1666021/+attachment/4822091/+files/systemd-resolve-high-cpu.png

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

Title:
  zesty systemd-resolve timeout

Status in systemd package in Ubuntu:
  New

Bug description:
  I rebooted my zesty install today so it has network-manager
  1.4.4-1ubuntu2 (re-enabled resolved by default for DNS) and systemd
  232-17ubuntu1 (which is supposed to fix the CNAME problems that got
  resolved by default reverted earlier in zesty).

  I had various DNS issues so I rebooted.

  When I rebooted, I opened up Firefox and browsed several sites.
  I opened a terminal and ran sudo apt update. I disabled a PPA and enabled a 
different PPA and ran sudo apt update then sudo apt dist-upgrade (there were 3 
updates).

  When apt was downloading one of those new packages, it paused mid-
  download. I was unable to browse sites in Firefox. I ran this command
  in a different terminal:

  $ systemd-resolve --status
  Failed to get global data: Connection timed out

  I checked journalctl and there was a very large number of these entries:
  systemd-resolved[3260]: Processing query...

  Finally followed by this repeated 3 times:
  dnsmasq[3563]: Maximum number of concurrent DNS queries reached (max: 150)

  Eventually, after I guess a couple minutes, things returned to normal.
  The apt upgrade completed. systemd-resolve --status looked better and
  I'm able to use Firefox again (to report this bug).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-17ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Feb 19 09:54:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (191 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80SA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=352e459f-ebca-4dc8-86e3-b078a000910b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2016-12-20 (60 days ago)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0VCN22WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1470
  dmi.modalias: 
dmi:bvnLENOVO:bvr0VCN22WW(V1.06):bd09/26/2016:svnLENOVO:pn80SA:pvrLenovoideapadFLEX4-1470:rvnLENOVO:rnLenovoideapadF:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1470:
  dmi.product.name: 80SA
  dmi.product.version: Lenovo ideapad FLEX 4-1470
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1650729] Re: package apt 1.2.15ubuntu0.2 failed to install/upgrade: end of file on stdin at conffile prompt

2017-02-19 Thread Alberto Salvia Novella

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

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

Title:
  package apt 1.2.15ubuntu0.2 failed to install/upgrade: end of file on
  stdin at conffile prompt

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.15ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sat Dec 17 11:51:35 2016
  ErrorMessage: end of file on stdin at conffile prompt
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: apt
  Title: package apt 1.2.15ubuntu0.2 failed to install/upgrade: end of file on 
stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

2017-02-19 Thread LaMont Jones

A very unexpected, and totally unwelcome change to vim.

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

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

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

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

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

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

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

[Touch-packages] [Bug 1661523] Re: AppArmor profile for Firefox (51.0.1) after took in enforced mode falls back into unconfined

2017-02-19 Thread Sziráki Tamás

OK, thanks.

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

Title:
  AppArmor profile for Firefox (51.0.1) after took in enforced mode
  falls back into unconfined

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  The profile for Firefox after took in enforced mode falls back into
  unconfined mode, and download into any selected folders in my account,
  not only the allowed one.

  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  apt-cache policy apparmor
  apparmor:
Telepítve: 2.10.95-0ubuntu2.5
Jelölt:2.10.95-0ubuntu2.5
Verziótáblázat:
   *** 2.10.95-0ubuntu2.5 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.10.95-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Feb  3 09:03:18 2017
  InstallationDate: Installed on 2015-09-19 (502 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=429aedd2-83c1-4b53-b23f-c8099109f278 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1666021] [NEW] zesty systemd-resolve timeout