date:20170125

This bug was fixed in the package qtubuntu -
0.63+17.04.20170119.2-0ubuntu1

---
qtubuntu (0.63+17.04.20170119.2-0ubuntu1) zesty; urgency=medium

  [ Daniel d'Andrada ]
  * Resize menus and toolips when told to do so

  [ Gerry Boland ]
  * Quit gracefully if Mir connection failed (LP: #1655936)

 -- Michał Sawicz   Thu, 19 Jan 2017
22:55:05 +

** Changed in: qtubuntu (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  clients crash with "UbuntuClientIntegration: connection to Mir server
  failed."

Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  According to
  https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
  it seems to be common-ish.

  This happens when unity8-dash can't find unity8 (mir server) and
  crashing (via QFatal) is our controlled way of exiting (not very
  clean, but it is how it is)[1].

  This will happen for example if you try to start unity8-dash directly (not 
through upstart) from a ssh shell in the phone, i.e
  phablet-shell
  stop unity8-dash
  unity8-dash

  And it may happen after a unity8 crash.

  In general we think that it's not a pressing issue users have since
  there seems to have not been any report of unity8-dash failing to
  start, but we're creating this bug to track it from time to time and
  make sure it doesn't get worse.

  [1] Qt platform plugins (also know as QPA) don't have a way to say
  they had a problem initiating themselves, Qt code is prepared for the
  QPlatformIntegrationPlugin::create() function to return, but all it
  does when that happens is call qFatal anyway [2]

  [2]
  
http://code.qt.io/cgit/qt/qtbase.git/tree/src/gui/kernel/qguiapplication.cpp#n1132

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

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

[Touch-packages] [Bug 1634868] Re: Add support for returning monitor EDIDs

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

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

Title:
  Add support for returning monitor EDIDs

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

Bug description:
  Add support for returning monitor EDIDs

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

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

[Touch-packages] [Bug 1640366] Re: [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA dropping_latency_is_closer_to_zero_than_one)

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

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

Title:
  [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one (AKA
  dropping_latency_is_closer_to_zero_than_one)

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

Bug description:
  20:35:16 10: [ RUN  ] ClientLatency.dropping_latency_is_limited_to_one
  20:35:16 10: [2016-11-08 20:35:16.713374] mirserver: Starting
  20:35:16 10: [2016-11-08 20:35:16.713544] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.714686] mirserver: Using software cursor
  20:35:16 10: [2016-11-08 20:35:16.733467] mirserver: Initial display 
configuration:
  20:35:16 10: [2016-11-08 20:35:16.734637] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.734766] mirserver: Mir version 0.25.0
  20:35:18 10: 
/<>/mir-0.25.0+yakkety2807bzr3804/tests/acceptance-tests/test_latency.cpp:341:
 Failure
  20:35:18 10: Value of: max_latency
  20:35:18 10: Expected: is <= 1
  20:35:18 10:   Actual: 2 (of type unsigned int)
  20:35:18 10: [  debug   ] 98 frames sampled, averaging 1.0 frames latency
  20:35:18 10: [  debug   ]  0:  1  1  1  1  1  1  1  2  1  1
  20:35:18 10: [  debug   ] 10:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 20:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 30:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 40:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 50:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 60:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 70:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 80:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 90:  1  1  1  1  1  1  1  1
  20:35:18 10: [2016-11-08 20:35:18.575646] mirserver: Stopping
  20:35:18 10: [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one 
(1879 ms)

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2781/consoleFull]

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

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

[Touch-packages] [Bug 1641166] Re: Server::override_the_coordinate_translator() cannot be effectively used downstream

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

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

Title:
  Server::override_the_coordinate_translator() cannot be effectively
  used downstream

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

Bug description:
  Being able to switch the debug APIs on at runtime is needed by Unity8
  to address autopilot issues.

  According to the documentation in
  include/server/mir/scene/coordinate_translator.h the
  CoordinateTranslator interface can be implemented by throwing
  std::runtime_error. Vis:

   * \note It is acceptable for this call to unconditionally throw a 
std::runtime_error.
   *   It is not required for normal functioning of the server or 
clients; clients which
   *   use the debug extension will receive an appropriate failure 
notice.

  However, the relevant code in
  src/server/frontend/protobuf_message_processor.cpp is:

  try
  {
  ...
  }
  catch (mir::frontend::unsupported_feature const&)
  {
  ...
  }

  As mir::frontend::unsupported_feature subclasses std::runtime_error
  this does not correctly handle std::runtime_error.

  Further, as unsupported_feature is not a public class, this can't be
  thrown by downstream code. (Although I suspect throwing an identical
  class with the same name will trick the RTTI implementation.)

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

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

[Touch-packages] [Bug 1643432] Re: [ FAILED ] NestedServer.nested_platform_connects_and_disconnects

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

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

Title:
  [ FAILED ] NestedServer.nested_platform_connects_and_disconnects

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

Bug description:
  [ FAILED ] NestedServer.nested_platform_connects_and_disconnects:

  05:45:16 11: [ RUN ] NestedServer.nested_platform_connects_and_disconnects
  ...
  05:45:19 11: [2016-11-21 05:45:19.675640] mirserver: Stopping
  05:45:19 11: [2016-11-21 05:45:19.935809] mirserver: Stopping
  05:45:20 11: 
/<>/mir-0.25.0+xenial2940bzr3835/tests/acceptance-tests/test_nested_mir.cpp:721:
 Failure
  05:45:20 11: Actual function call count doesn't match 
EXPECT_CALL(*mock_session_mediator_report, session_disconnect_called(_))...
  05:45:20 11: Expected: to be called once
  05:45:20 11: Actual: never called - unsatisfied and active
  05:45:20 11: [ FAILED ] NestedServer.nested_platform_connects_and_disconnects 
(4157 ms)

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

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

[Touch-packages] [Bug 1576600] Re: Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS

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

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

Title:
  Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS

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

Bug description:
  Mir-on-X mouse input is irregular and stutters a bit, compared to Mir-
  on-KMS.

  Test case:
env MIR_CLIENT_INPUT_RATE=59 mir_demo_client_fingerpaint

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

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

[Touch-packages] [Bug 1591328] Re: Pointer/cursor input lag in unity8 session

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

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

Title:
  Pointer/cursor input lag in unity8 session

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Mouse pointer suffers of heavy input lag on my laptop, might also
  affect tablet

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

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

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

2017-01-25 Thread Rik Mills

On 25/01/17 13:22, Andre Heinecke wrote:
> I've changed the start script of the gpg-agent in gpgme accordingly
> with:
> 
> https://git.gnupg.org/cgi-
> bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=a98951a30a6ae603ffac4ec8c5168aa6d1019933
> 
> To also use that option. Please confirm if this fixes the Problem in
> your build environment.
> 

Applied the patch to 1.8.0-3, and does not seem to have made any
difference.

am64, i386 and armhf builds still hang at the same point and are killed
by launchpad with

"Build killed with signal TERM after 150 minutes of inactivity"

arm64 build just fails somewhere, and LP fails to render a buildlog for
some strange reason

ppc64el, as it did before, hangs for a bit then completes ok.

-- 
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 1388490] Re: Frame rate is artificially low on Diamondville Intel Atom systems due to aggressive power management

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

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

Title:
  Frame rate is artificially low on Diamondville Intel Atom systems due
  to aggressive power management

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

Bug description:
  Running a server and a few clients on an Atom N270 (requires vivid) is
  very stuttery and apparently limited to around 20 FPS.

  However this limitation is a bug. Firstly I notice the system is still
  70% idle according to top. And if I drag the mouse constantly over a
  surface or move a window constantly, the rendering (of everything)
  becomes perfectly smooth ~60 FPS. Also using --compositor-report=log
  on the Mir server shows the compositor render time even on this very
  weak machine is only 2.6ms.

  So we have a scheduling problem and forcing re-compositing via input
  is working around it. Obviously the clients themselves are not able to
  wake up the compositor frequently enough to ensure new frames get
  scheduled. However if I wake up the compositor using demo-shell mouse
  gestures then all is fast and smooth.

  This seems to be the same kind of scheduling problem also observed on
  higher-end systems when the compositor buffer pipeline is reduced -->
  bug 1377872

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

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

[Touch-packages] [Bug 1394369] Re: [testsfail] failure in CI in AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping

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

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

Title:
  [testsfail] failure in CI in
  AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping

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

Bug description:
  Failure seen in CI, could not reproduce locally:
  
https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-vivid-armhf/190/console

  Test seems to check timing (and today the CI server seemed
  particularly bogged-down).

  Not sure if this is the same root-cause as: lp: #1373826 (which has a
  similar description).

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

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

[Touch-packages] [Bug 1240909] Re: [performance] Restore support for better-than-triple buffering by default.

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

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

Title:
  [performance] Restore support for better-than-triple buffering by
  default.

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

Bug description:
  We really should restore support for double-buffering (or better)
  where possible. Presently we're on triple-buffering all the time.

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

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

[Touch-packages] [Bug 1494197] Re: [trusted prompt sessions] Can't open two prompt sessions at the same time

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

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

Title:
  [trusted prompt sessions] Can't open two prompt sessions at the same
  time

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

Bug description:
  current build number: 109
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-09-10 06:07:46
  version version: 109
  version ubuntu: 20150910
  version device: 20150818-0b38025
  version custom: 20150814-887-8-46

  Steps:
  1. Open the note app , and it opens at the regesiter page
  2.Don't sign in the note account and open twitter app

  Expectation:
  After step 2#,we can open the twitter ,and it will at the sign in page

  Actual result:
   we can't open twitter account ,there is a hint that we can only open one 
account at the same time :Account window could not be opened. You can only 
create one account at a time ;please try again after closing all other account 
windows.

  Note: I attached a screenshot

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

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

[Touch-packages] [Bug 1642504] Re: [regression] mir_proving_server crashes with std::exception::what: add_options() must be called before the_options()

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

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

Title:
  [regression] mir_proving_server crashes with std::exception::what:
  add_options() must be called before the_options()

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

Bug description:
  [regression] mir_proving_server (from lp:mir) crashes with:

  $ sudo bin/mir_proving_server
  MIR_CLIENT_PLATFORM_PATH=bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=bin/../lib/server-modules/
  LD_LIBRARY_PATH=bin/../lib
  exec=bin/mir_proving_server.bin
  [2016-11-17 16:33:52.015996]  eglstream: EGLStream platform is 
unsupported: Missing required extensions: EGL_EXT_platform_device 
EGL_EXT_device_base
  [2016-11-17 16:33:52.016058] mirplatform: Found graphics driver: 
mir:eglstream-kms (version 0.25.0)
  [2016-11-17 16:33:52.016648] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.25.0)
  [2016-11-17 16:33:52.016689] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.25.0)
  [2016-11-17 16:33:52.016838] mirplatform: Found graphics driver: mir:android 
(version 0.25.0)
  [2016-11-17 16:33:52.016965] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.25.0)
  [2016-11-17 16:33:52.016979] mirplatform: Found graphics driver: 
throw-on-creation (version 0.25.0)
  ERROR: 
/home/dan/bzr/mir/trunk/src/platform/options/default_configuration.cpp(250): 
Throw in function boost::program_options::options_description_easy_init 
mir::options::DefaultConfiguration::add_options()
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: add_options() must be called before the_options()

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

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

[Touch-packages] [Bug 1639749] Re: When pointer motion crosses window borders SurfaceInputDispatcher injected events increase accumulated relative motion

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

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

Title:
  When pointer motion crosses window borders SurfaceInputDispatcher
  injected events increase accumulated relative motion

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

Bug description:
  SurfaceInputDispatcher keeps track of input event targets - for
  historic reason those are called guesture owners - when it detects
  that the receiver of a pointer event is a different window it will
  send enter events to the new window and exit events to the old window.
  Those events contain the same attributes as the original pointer
  event. After sending the enter event the original motion event is also
  dispatched.

  Now if the new window accumulates the pointer events (like the nested
  server) to track a cursor position this tracking will now add the
  relative motion of the original event twice.

  We could decide to not send the original motion event after having
  provided the enter event. But that might not work for cases where the
  original event was a pointer button up/down event. Since we would have
  to emit that state change too. So that leaves us with nullifying the
  relative motion event in one case, or ignoring relative motion in
  enter exit events in our own cursor position tracker..

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

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

[Touch-packages] [Bug 1628794] Re: Valgrind failure on mir_acceptance_tests - leak on incoming buffer in Requests::free_buffer(int)

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

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

Title:
  Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
  Requests::free_buffer(int)

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

Bug description:
  Valgrind failure on mir_acceptance_tests - leak in
  mir::client::BufferVault::wire_transfer_inbound(int)

  It's happened twice now. Yesterday on kdub's branch and today on mine:

  05:20:36 9: ==2515== 80 (32 direct, 48 indirect) bytes in 1 blocks are 
definitely lost in loss record 20 of 37
  05:20:36 9: ==2515== at 0x4C2D1AF: operator new(unsigned long) (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  05:20:36 9: ==2515== by 0x54C74F2: NewCallback 
(callback.h:412)
  05:20:36 9: ==2515== by 0x54C74F2: (anonymous 
namespace)::Requests::free_buffer(int) (buffer_stream.cpp:274)
  05:20:36 9: ==2515== by 0x54CDB88: free_buffer (buffer_vault.cpp:111)
  05:20:36 9: ==2515== by 0x54CDB88: 
mir::client::BufferVault::wire_transfer_inbound(int) (buffer_vault.cpp:265)
  05:20:36 9: ==2515== by 0x54D11DD: operator() (functional:2136)
  05:20:36 9: ==2515== by 0x54D11DD: 
mir::client::AtomicCallback<>::operator()() const (atomic_callback.h:56)
  05:20:36 9: ==2515== by 0x54E1128: 
mir::client::rpc::MirProtobufRpcChannel::process_event_sequence(std::__cxx11::basic_string const&) 
(mir_protobuf_rpc_channel.cpp:341)
  05:20:36 9: ==2515== by 0x54E2208: 
mir::client::rpc::MirProtobufRpcChannel::on_data_available() 
(mir_protobuf_rpc_channel.cpp:470)
  05:20:36 9: ==2515== by 0x54E68AD: 
operator() 
(stream_socket_transport.cpp:40)
  05:20:36 9: ==2515== by 0x54E68AD: std::_Function_handler const&), 
mir::client::rpc::TransportObservers::on_data_available()::$_0>::_M_invoke(std::_Any_data
 const&, std::shared_ptr const&) 
(functional:1740)
  05:20:36 9: ==2515== by 0x54E6B7F: operator() (functional:2136)
  05:20:36 9: ==2515== by 0x54E6B7F: 
mir::ThreadSafeList::for_each(std::function const&)> const&) 
(thread_safe_list.h:80)
  05:20:36 9: ==2515== by 0x54E679D: on_data_available 
(stream_socket_transport.cpp:40)
  05:20:36 9: ==2515== by 0x54E679D: 
mir::client::rpc::StreamSocketTransport::dispatch(unsigned int) 
(stream_socket_transport.cpp:208)
  05:20:36 9: ==2515== by 0x5B700E3: 
mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int) 
(multiplexing_dispatchable.cpp:210)
  05:20:36 9: ==2515== by 0x5B700E3: 
mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int) 
(multiplexing_dispatchable.cpp:210)
  05:20:36 9: ==2515== by 0x5B726B6: (anonymous 
namespace)::dispatch_loop(std::__cxx11::basic_string const&, 
std::shared_ptr,
 std::shared_ptr, std::function const&) 
(threaded_dispatcher.cpp:211)
  05:20:36 9: ==2515== by 0x5B7684E: void std::_Bind_simple, 
std::allocator >, 
std::shared_ptr,
 std::shared_ptr, std::function))(std::__cxx11::basic_string const&, 
std::shared_ptr,
 std::shared_ptr, std::function 
const&)>::_M_invoke<0ul, 1ul, 2ul, 3ul>(std::_Index_tuple<0ul, 1ul, 2ul, 3ul>) 
(functional:1399)
  05:20:36 9: ==2515== by 0x695350E: ??? (in 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.22)
  05:20:36 9: ==2515== by 0x6E3E709: start_thread (pthread_create.c:333)
  05:20:36 9: ==2515== by 0x715D0FE: clone (clone.S:105)
  05:20:36 9: ==2515==
  05:20:36 9: ==2515== 80 (32 direct, 48 indirect) bytes in 1 blocks are 
definitely lost in loss record 21 of 37
  05:20:36 9: ==2515== at 0x4C2D1AF: operator new(unsigned long) (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  05:20:36 9: ==2515== by 0x54C7363: NewCallback 
(callback.h:412)
  05:20:36 9: ==2515== by 0x54C7363: (anonymous 
namespace)::Requests::allocate_buffer(mir::geometry::Size, MirPixelFormat, int) 
(buffer_stream.cpp:262)
  05:20:36 9: ==2515== by 0x54CDBE8: alloc_buffer (buffer_vault.cpp:106)
  05:20:36 9: ==2515== by 0x54CDBE8: 
mir::client::BufferVault::wire_transfer_inbound(int) (buffer_vault.cpp:267)
  05:20:36 9: ==2515== by 0x54D11DD: operator() (functional:2136)
  05:20:36 9: ==2515== by 0x54D11DD: 
mir::client::AtomicCallback<>::operator()() const (atomic_callback.h:56)
  05:20:36 9: ==2515== by 0x54E1128: 
mir::client::rpc::MirProtobufRpcChannel::process_event_sequence(std::__cxx11::basic_string const&) 
(mir_protobuf_rpc_channel.cpp:341)
  05:20:36 9: ==2515== by 0x54E2208: 
mir::client::rpc::MirProtobufRpcChannel::on_data_available() 
(mir_protobuf_rpc_channel.cpp:470)
  05:20:36 9: ==2515== by 0x54E68AD: 
operator() 
(stream_socket_transport.cpp:40)
  05:20:36 9: ==2515== by 0x54E68AD: std::_Function_handler const&),

[Touch-packages] [Bug 1586311] Re: [regression] Two fingers in mir_proving_server now resizes/moves app windows (two finger apps unusable)

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

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

Title:
  [regression] Two fingers in mir_proving_server now resizes/moves app
  windows (two finger apps unusable)

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

Bug description:
  [regression] Two fingers in mir_proving_server now resizes/moves app
  windows (two finger apps unusable)

  Two finger gestures are commonly used by apps for pinch/zoom and
  should never be captured by the shell.

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

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

[Touch-packages] [Bug 1654478] Re: [regression] mir_acceptance_tests' death tests leave behind core files

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

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

Title:
  [regression] mir_acceptance_tests' death tests leave behind core files

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

Bug description:
  [regression] mir_acceptance_tests' death tests leave behind core files

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

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

[Touch-packages] [Bug 1651391] Re: Package mirtest-dev is missing a dependency on mir-renderer-gl-dev

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

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

Title:
  Package mirtest-dev is missing a dependency on mir-renderer-gl-dev

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

Bug description:
  tests/mirtest.pc.in contains the line:

  Requires: mirserver mirplatform mirclient mir-renderer-gl-dev

  But debian/control doesn't have the corresponding dependency on mir-
  renderer-gl-dev

  (I also think that mir-renderer-gl-dev.pc ought to be renamed mir-
  renderer-gl.pc, but that's a secondary issue.)

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

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

[Touch-packages] [Bug 1653658] Re: Race between MirConnection::released() and MirConnection::~MirConnection() causes deadlocks, possible crashes and memory corruption

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

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

Title:
  Race between MirConnection::released() and
  MirConnection::~MirConnection() causes deadlocks, possible crashes and
  memory corruption

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

Bug description:
  Race between MirConnection::released() and
  MirConnection::~MirConnection() causes deadlocks, possible crashes and
  memory corruption.

  This is happening reliably only in one of my branches on krillin,
  where the thread calling released() is deadlocked trying to use
  internal locking primitives that another thread calling ~MirConnection
  is in the process of destructing.

  It appears this is a known problem already judging by this comment:

  MirConnection::~MirConnection() noexcept
  {
  // We don't die while if are pending callbacks (as they touch this).
  // But, if after 500ms we don't get a call, assume it won't happen.
  connect_wait_handle.wait_for_pending(std::chrono::milliseconds(500));

  std::lock_guard lock(mutex);
  surface_map.reset();

  Although that code only waits for connections and doesn't bother to
  wait for releases which are the problem here.

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

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

[Touch-packages] [Bug 1655293] Re: [ FAILED ] RaiseSurfaces.key_event_with_cookie

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

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

Title:
  [ FAILED ] RaiseSurfaces.key_event_with_cookie

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

Bug description:
  08:59:51 11: 
/<>/mir-0.26.0+zesty3446bzr3915/tests/acceptance-tests/test_surface_raise.cpp:198:
 Failure
  08:59:51 11: Expected: mir_surface_get_focus(surface2)
  08:59:51 11: Which is: 0
  08:59:51 11: To be equal to: mir_surface_focused
  08:59:51 11: Which is: 1
  08:59:56 11: [2017-01-10 08:59:56.047566] mirserver: Stopping
  08:59:56 11: [ FAILED ] RaiseSurfaces.key_event_with_cookie (5757 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/3416/consoleFull

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

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

[Touch-packages] [Bug 1653789] Re: DisplayConfigurationTest.configure_session_removed_display failure

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

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

Title:
  DisplayConfigurationTest.configure_session_removed_display failure

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

Bug description:
  19:32:28 11: [2017-01-03 19:32:28.499435] mirserver: Session virtual void 
mir_test_framework::ConnectedClientHeadlessServer::SetUp() removed display 
configuration
  19:32:28 11: 
  19:32:28 11: GMOCK WARNING:
  19:32:28 11: Uninteresting mock function call - returning directly.
  19:32:28 11: Function call: session_configuration_removed(@0xbc0ca80 16-byte 
object <00-A8 97-0A 00-00 00-00 F0-A7 97-0A 00-00 00-00>)
  19:32:28 11: Stack trace:
  19:32:38 11: [2017-01-03 19:32:38.595943] mirserver: Stopping
  19:32:38 11: 
/<>/mir-0.26.0+xenial3324bzr3948/tests/acceptance-tests/test_new_display_configuration.cpp:1810:
 Failure
  19:32:38 11: Actual function call count doesn't match EXPECT_CALL(*observer, 
session_configuration_removed(_))...
  19:32:38 11: Expected: to be called once
  19:32:38 11: Actual: never called - unsatisfied and active
  19:32:38 11: [ FAILED ] 
DisplayConfigurationTest.configure_session_removed_display (11053 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial+overlay/3294/consoleFull

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

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

[Touch-packages] [Bug 1654612] Re: Setting the event handler after the surface has been created does nothing

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

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

Title:
  Setting the event handler after the surface has been created does
  nothing

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

Bug description:
  Setting the surface spec for the event handler after the surface has
  been created does nothing.

  Reason:

  We dont set the event handler and recreate the input thread!

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

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

[Touch-packages] [Bug 1644062] Re: googletest 1.8.0-2 (on zesty) breaks existing builds [add_library cannot create target "gmock" ...]

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

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

Title:
  googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
  cannot create target "gmock" ...]

Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Fix Released
Status in cmake-extras package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu:
  Fix Released
Status in googletest package in Ubuntu:
  Won't Fix
Status in mir package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to 1.8.0-2 (from 1.7.0-4), our previously-working
  builds break:

  CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock" because another target with the
 same name already exists.  The existing target is a static library created
 in source directory "/usr/src/googletest/googlemock".  See documentation
 for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:84 (cxx_library)


   CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock_main" because another target with
 the same name already exists.  The existing target is a static library
 created in source directory "/usr/src/googletest/googlemock".  See
 documentation for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:89 (cxx_library)


   CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
 install TARGETS given target "gmock" which does not exist in this
 directory.

  The CMakeLists.txt in our project that triggers this error does this:

  set(old_cxx_flags ${CMAKE_CXX_FLAGS})
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -Wno-old-style-cast 
-Wno-missing-field-initializers")
  find_package(GMock)
  set(CMAKE_CXX_FLAGS ${old_cxx_flags})

  This used to work fine, but no breaks on zesty.

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

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

[Touch-packages] [Bug 1646704] Re: [regression] Cross compiling from zesty to yakkety fails with *** No rule to make target 'gmock/libs/googlemock/gtest/libgtest.a'

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

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

Title:
  [regression] Cross compiling from zesty to yakkety fails with *** No
  rule to make target 'gmock/libs/googlemock/gtest/libgtest.a'

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

Bug description:
  Try cross-compiling from zesty to yakkety:

  $ ./cross-compile-chroot.sh -d yakkety -a host
  ...
  make[2]: *** No rule to make target 'gmock/libs/googlemock/gtest/libgtest.a', 
needed by 'bin/mir_android_diagnostics'.  Stop.

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

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

[Touch-packages] [Bug 1646700] Re: mir_proving_server's four finger swipe to switch apps leaks touch events to the clients

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

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

Title:
  mir_proving_server's four finger swipe to switch apps leaks touch
  events to the clients

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

Bug description:
  mir_proving_server's four finger swipe to switch apps leaks touch
  events to the clients.

  Before the gesture completes, some touch apps (e.g.
  mir_demo_client_target/fingerpaint) incorrectly receive and interpret
  the four-finger touches.

  Is this a regression or did I just never test enough on a large
  touchscreen with touch-sensitive apps?...

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

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

[Touch-packages] [Bug 1654023] Re: [regression] Development headers reference unknown header "mir_toolkit/mir_input_device_types.h" so some clients can't build at all any more

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

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

Title:
  [regression] Development headers reference unknown header
  "mir_toolkit/mir_input_device_types.h" so some clients can't build at
  all any more

Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Invalid
Status in mir package in Ubuntu:
  Invalid

Bug description:
  Trying to build GTK+ which uses mircommon and mirclient, I'm getting:

  In file included from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmircursor.c:22:
  
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48:
 fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory
   #include "mir_toolkit/mir_input_device_types.h"
  ^ 
   
  compilation terminated.
  Makefile:652: recipe for target 'gdkmircursor.lo' failed
  make[4]: *** [gdkmircursor.lo] Error 1
  make[4]: *** Waiting for unfinished jobs
  In file included from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdevicemanager.c:25:
  
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48:
 fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory
   #include "mir_toolkit/mir_input_device_types.h"
  ^ 
   
  compilation terminated.   

  Makefile:652: recipe for target 'gdkmirdevicemanager.lo' failed   

  make[4]: *** [gdkmirdevicemanager.lo] Error 1 
 
  In file included from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24,
 
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21,
  
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdisplay.c:24:

  
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48:
 fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory
   #include "mir_toolkit/mir_input_device_types.h"

  It seems like this header was moved, or possibly it wasn't installed.

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

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

[Touch-packages] [Bug 1644075] Re: [regression] Those mir_demo_client_* which default to fullscreen now ignore the size parameter (-s WIDTHxHEIGHT)

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

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

Title:
  [regression] Those mir_demo_client_* which default to fullscreen now
  ignore the size parameter (-s WIDTHxHEIGHT)

Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  Those mir_demo_client_* which default to fullscreen now ignore the
  size parameter (-s WIDTHxHEIGHT), instead choosing to stay in
  fullscreen mode.

  This applies to mirvanity too, making testing of windowed client
  latency difficult.

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

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

[Touch-packages] [Bug 1644189] Re: Shell doesn't know when base display config has changed

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

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

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Committed
Status in MirAL:
  In Progress
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  New

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

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

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

[Touch-packages] [Bug 1647573] Re: [ FAILED ] ThreadedDispatcherDeathTest.destroying_dispatcher_from_a_callback_is_an_error

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

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

Title:
  [  FAILED  ]
  ThreadedDispatcherDeathTest.destroying_dispatcher_from_a_callback_is_an_error

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

Bug description:
  Test failed but really just looks like an assertion failure inside
  pthreads:

  04:22:35 [ RUN  ] 
ThreadedDispatcherDeathTest.destroying_dispatcher_from_a_callback_is_an_error
  04:22:35
  04:22:35 [WARNING] /usr/src/gtest/src/gtest-death-test.cc:825:: Death tests 
use fork(), which is unsafe particularly in a threaded context. For this test, 
Google Test couldn't detect the number of threads.
  04:22:35 
/<>/mir-0.25.0+xenial3092bzr3867/tests/unit-tests/dispatch/test_threaded_dispatcher.cpp:416:
 Failure
  04:22:35 Death test: { ::mir::test::disable_core_dump(); { { 
md::ThreadedDispatcher* dispatcher; auto dispatchable = 
std::make_shared([]() { delete dispatcher; }); 
dispatchable->trigger(); dispatcher = new md::ThreadedDispatcher("Death 
thread", dispatchable); std::this_thread::sleep_for(10s); } ; } }
  04:22:35 Result: died but not with expected error.
  04:22:35   Expected: .*Destroying ThreadedDispatcher.*
  04:22:35 Actual msg:
  04:22:35 [  DEATH   ] mir_unit_tests.bin: tpp.c:84: 
__pthread_tpp_change_priority: Assertion `new_prio == -1 || (new_prio >= 
fifo_min_prio && new_prio <= fifo_max_prio)' failed.
  04:22:35 [  DEATH   ]
  04:22:35 [  FAILED  ] 
ThreadedDispatcherDeathTest.destroying_dispatcher_from_a_callback_is_an_error 
(159 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial+overlay/3063/consoleFull

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

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

[Touch-packages] [Bug 1645284] Re: miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager tiling) are broken by lp:mir

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

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

Title:
  miral::ActiveOutputsMonitor (and therefore miral-shell --window-
  manager tiling) are broken by lp:mir

Status in Mir:
  Fix Committed
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  New

Bug description:
  The change from DisplayConfigurationReport to
  DisplayConfigurationObserver means that downstream can no longer
  subscribe early enough to get the initial display configuration.

  This is because they need call
  "server.the_display_configuration_observer_registrar()" which is not
  available until after the server is initialized.

  The internal reports avoid this by being wired into the
  DefaultServerConfiguration constructor so they are registered at the
  start of initialization.

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

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

[Touch-packages] [Bug 1647575] Re: [regression] eglapps now all have window title "default"

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

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

Title:
  [regression] eglapps now all have window title "default"

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

Bug description:
  eglapps now all have window title "default"

  Previously (in Mir 0.24 at least) they each had unique titles.

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

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

[Touch-packages] [Bug 1651633] Re: EDID data is missing in nested servers

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

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

Title:
  EDID data is missing in nested servers

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

Bug description:
  EDID data is missing in nested servers... or so I believe.

  The first server logs it:
  [2016-12-21 11:37:11.642422] mirserver:   Output 48: DisplayPort connected, 
used
  [2016-12-21 11:37:11.642434] mirserver:   EDID monitor name: DELL U2413
  [2016-12-21 11:37:11.642441] mirserver:   EDID manufacturer: DEL
  [2016-12-21 11:37:11.642448] mirserver:   EDID product code: 61510
  [2016-12-21 11:37:11.642463] mirserver:   Physical size 24.0" 520x320mm
  [2016-12-21 11:37:11.642470] mirserver:   Power is on

  But then the nested server does not:
  [2016-12-21 11:37:14.334128] mirserver:   Output 48: DisplayPort connected, 
used
  [2016-12-21 11:37:14.334142] mirserver:   Physical size 24.0" 520x320mm
  [2016-12-21 11:37:14.334148] mirserver:   Power is on

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

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

[Touch-packages] [Bug 1651638] Re: [regression] Latency for fullscreen interval 0 clients (e.g. games and benchmarks) increased with the introduction of nested passthrough

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

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

Title:
  [regression] Latency for fullscreen interval 0 clients (e.g. games and
  benchmarks) increased with the introduction of nested passthrough

Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  Nested fullscreen interval 0 clients in Mir 0.25.0 had higher latency
  than interval 1 nested fullscreen clients.

  I've reproduced this a couple of times and it is concerning:

  Mir 0.25:
     Interval 0: 81ms  <-- regression
     Interval 1: 64ms  <-- improvement

  Mir 0.24:
 Interval 0: 70ms
 Interval 1: 96ms

  It's the obvious green spike in this chart:
  
https://docs.google.com/spreadsheets/d/1RbTVDbx04ohkF4-md3wAlgmxbSI1DttstnT6xdcXhZQ/pubchart?oid=1566479835=interactive

  Although this regression appears to be resolved in the 0.26 series
  (lp:mir) it's serious enough that we should look into finding what the
  cause was so that Mir 0.25.1 can get the same fix.

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

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

[Touch-packages] [Bug 1658604] Re: Mir FTBFS with MIR_USE_PRECOMPILED_HEADERS=OFF: error: ISO C++11 requires at least one argument for the "..." in a variadic macro [-Werror]

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

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

Title:
  Mir FTBFS with MIR_USE_PRECOMPILED_HEADERS=OFF: error: ISO C++11
  requires at least one argument for the "..." in a variadic macro
  [-Werror]

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

Bug description:
  Mir fails to build (on zesty) using cmake
  -DMIR_USE_PRECOMPILED_HEADERS=OFF

  Several occurrences of:

  error: ISO C++11 requires at least one argument for the "..." in a
  variadic macro [-Werror]

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

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

[Touch-packages] [Bug 1656164] Re: Black screen with Raspberry Pi 3 VC4 Mesa driver

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

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

Title:
  Black screen with Raspberry Pi 3 VC4 Mesa driver

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

Bug description:
  Using mir 0.25 on a rpi3 using the vc4 mesa driver, a blank screen is
  seen when starting mir_demo_server for example.

  Mir 0.24.1 works fine.

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

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

[Touch-packages] [Bug 1657755] Re: android: overlays no longer are activated

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

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

Title:
  android: overlays no longer are activated

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

Bug description:
  android is using the fallback path with lp:mir ever since activating
  framedropping-by-default in rev3592 (activating the frame timing).
  Android disables overlays to avoid fencing issues (hangs) that can
  happen during framedropping (more info in LP: #1369763)

  This can be seen by running
  mir_demo_server_minimal --compositor-report log
  alongside 
  mir_demo_client_egltriangle  -f

  The overlay % drops from 100 to 0 after rev3592.

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

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

[Touch-packages] [Bug 1656633] Re: i386 FTBFS: src/platforms/eglstream-kms/server/kms_display_configuration.cpp:88:47: error: narrowing conversion of ‘..._drmModeConnector::connector_id’ from ‘uint32_

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

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

Title:
  i386 FTBFS: src/platforms/eglstream-
  kms/server/kms_display_configuration.cpp:88:47: error: narrowing
  conversion of ‘..._drmModeConnector::connector_id’ from ‘uint32_t {aka
  unsigned int}’ to ‘EGLAttrib {aka int}’ inside { } [-Werror=narrowing]

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

Bug description:
  lp:mir fails to build on zesty i386:

  
/home/dan/bzr/mir/trunk/src/platforms/eglstream-kms/server/kms_display_configuration.cpp:
 In function 
‘std::vector 
{anonymous}::create_outputs(int, EGLDisplay)’:
  
/home/dan/bzr/mir/trunk/src/platforms/eglstream-kms/server/kms_display_configuration.cpp:88:47:
 error: narrowing conversion of ‘(& connector)->std::unique_ptr<_Tp, 
_Dp>::operator-><_drmModeConnector, std::function 
>()->_drmModeConnector::connector_id’ from ‘uint32_t {aka unsigned int}’ to 
‘EGLAttrib {aka int}’ inside { } [-Werror=narrowing]
   EGL_DRM_CONNECTOR_EXT, connector->connector_id,
  ~~~^~~~

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

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

[Touch-packages] [Bug 1658605] Re: [regression] Mir cross-compile to vivid/armhf FTBFS with: mock_input_device_hub.h:33:18: error: ‘add_observer’ is not a type

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

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

Title:
  [regression] Mir cross-compile to vivid/armhf FTBFS with:
  mock_input_device_hub.h:33:18: error: ‘add_observer’ is not a type

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

Bug description:
  xenial$ ./cross-compile-chroot.sh -d vivid -a armhf

  In file included from 
/home/dan/bzr/mir/fixy/tests/unit-tests/input/test_config_changer.cpp:29:0:
  
/home/dan/bzr/mir/fixy/include/test/mir/test/doubles/mock_input_device_hub.h:33:18:
 error: ‘add_observer’ is not a type
   MOCK_METHOD1(add_observer, 
void(std::shared_ptr const&));
^
  
/home/dan/bzr/mir/fixy/include/test/mir/test/doubles/mock_input_device_hub.h:33:88:
 error: ISO C++ forbids declaration of ‘MOCK_METHOD1’ with no type 
[-fpermissive]
   MOCK_METHOD1(add_observer, 
void(std::shared_ptr const&));

  ^
  
/home/dan/bzr/mir/fixy/include/test/mir/test/doubles/mock_input_device_hub.h:34:18:
 error: ‘remove_observer’ is not a type
   MOCK_METHOD1(remove_observer, 
void(std::weak_ptr const&));
^
  ..

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

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

[Touch-packages] [Bug 1659191] Re: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also in

2017-01-25 Thread Hans Joachim Desserud

** Tags added: package-conflict

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

Title:
  package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying
  to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-
  evoldap.so', which is also in package gconf-service-backend
  3.2.6-3ubuntu6

Status in gconf package in Ubuntu:
  New

Bug description:
  No idea

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: gconf-service 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Jan 25 11:58:29 2017
  DpkgTerminalLog:
   Preparing to unpack .../gconf-service_3.2.6-4_amd64.deb ...
   Unpacking gconf-service (3.2.6-4) over (3.2.6-3ubuntu6) ...
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/gconf-service_3.2.6-4_amd64.deb (--unpack):
trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also 
in package gconf-service-backend 3.2.6-3ubuntu6
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also 
in package gconf-service-backend 3.2.6-3ubuntu6
  RelatedPackageVersions:
   dpkg 1.18.15kali1
   apt  1.4~beta3
  SourcePackage: gconf
  Title: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying 
to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', 
which is also in package gconf-service-backend 3.2.6-3ubuntu6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1659131] Re: package lib32z1-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:

2017-01-25 Thread Hans Joachim Desserud

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

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

** This bug has been marked a duplicate of bug 1512992
   package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying 
to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package 
lib32z1-dev 1:1.2.8.dfsg-2ubuntu4

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

Title:
  package lib32z1-dev (not installed) failed to install/upgrade: trying
  to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in
  package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4

Status in zlib package in Ubuntu:
  New

Bug description:
  failed to install and gave this error --> Sub-process /usr/bin/dpkg
  returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lib32z1-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Jan 25 09:25:50 2017
  DuplicateSignature:
   package:lib32z1-dev:(not installed)
   Unpacking lib32z1-dev (1:1.2.8.dfsg-2ubuntu4) ...
   dpkg: error processing archive 
/var/cache/apt/archives/lib32z1-dev_1%3a1.2.8.dfsg-2ubuntu4_amd64.deb 
(--unpack):
trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in 
package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
  ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', 
which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
  InstallationDate: Installed on 2017-01-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: zlib
  Title: package lib32z1-dev (not installed) failed to install/upgrade: trying 
to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package 
zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1657897] Re: Failure to report rhosts

2017-01-25 Thread Joshua Powers

@James, big thanks for the information I think your clarity about the
logging of the rhost and the redhat bug helped a bit.

To help get work completed on this bug I tried to reproduce this by
setting up a mail server using sasl using these steps [1]. I was then
able to telnet to it from a remote host and attempt to login. In
mail.log I got the following messages:

Jan 25 16:55:58 uvt-yakkety postfix/smtpd[3313]: connect from 
unknown[192.168.122.1]
Jan 25 16:56:13 uvt-yakkety postfix/smtpd[3313]: warning: 
unknown[192.168.122.1]: SASL login authentication failed: authentication failure

which show the remote host IP, however in auth.log I see:

Jan 25 16:56:12 uvt-yakkety saslauthd[3020]: pam_unix(smtp:auth): 
authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=  user=powersj
Jan 25 16:56:13 uvt-yakkety saslauthd[3020]: DEBUG: auth_pam: pam_authenticate 
failed: Authentication failure
Jan 25 16:56:13 uvt-yakkety saslauthd[3020]: do_auth : auth failure: 
[user=powersj] [service=smtp] [realm=uvt-yakkety] [mech=pam] [reason=PAM auth 
error]

I believe this replicated the issue, can you confirm?

[1] https://wiki.debian.org/PostfixAndSASL

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

Title:
  Failure to report rhosts

Status in cyrus-sasl2 package in Ubuntu:
  Incomplete

Bug description:
  
  When using sasl2-bin and saslauthd it will fail to work correctly with pam.

  The first major problem is that that it will fail to report the rhost
  address in the log which means auth failures cannot be policed and no
  useful data (the ip address) is reported to the log file. Example
  below during a password brute force attempt.

  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): check pass; user 
unknown
  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): authentication 
failure; logname= uid=0 euid=0 tty= ruser= rhost=

  The other issue is that it would be great to be able to ip restrict
  logins based on pam module configuration. Based on previous reading
  and as far as I can tell the remote ip address is not supported
  between the imap/pop/smtp process and sasl2 is it possible to add
  support for this?

  Technically this is a long standing security issue because fail2ban
  cannot be used to process the syslog file and auto block the host
  during brute force password attempts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1657897/+subscriptions

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

[Touch-packages] [Bug 1626435] Re: Keyboard layout not applied on the shell

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-zesty-2404

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

Title:
  Keyboard layout not applied on the shell

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Released
Status in Mir 0.24 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Split out from bug #1611859:

  Steps:
  * connect a BT or a physical keyboard
  * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot
  * go through the wizard

  Expected:
  * I can use the selected layout in the wizard
  * and in snap decisions

  Current:
  * you can only use us layout in the shell

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.14+16.04.20160914-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-078]
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 10:07:47 2016
  InstallationDate: Installed on 2016-05-06 (138 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1648173] Re: App drawer stays on screen after activating launcher item

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-zesty-2404

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

Title:
  App drawer stays on screen after activating launcher item

Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  In https://bileto.ubuntu.com/#/ticket/2150 - after fixing bug #1591311

  Steps:
  * press Super+A or long-left-swipe to invoke the app drawer
  * click on an item in launcher

  Expected:
  * drawer is closed, as it is when you launch an item from the drawer

  Current:
  * drawer stays on, likely covering part of the activated window

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20161129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec  7 18:17:15 2016
  InstallationDate: Installed on 2016-05-06 (214 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago)

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

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

[Touch-packages] [Bug 1656896] Re: unity8 need keyboard shortcut for indicators

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-zesty-2404

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

Title:
  unity8 need keyboard shortcut for indicators

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  unity8 need keyboard shortcut for indicators

  in unity7 pressing ALT F10 opens the indicator menu, in unity8 ALT F10 
doesn't seem to do anything
  silo 2272

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

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

[Touch-packages] [Bug 1646457] Re: No feedback when changing Launcher's icon size

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-zesty-2404

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

Title:
  No feedback when changing Launcher's icon size

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

Bug description:
  bq M10 FHD rc-proposed r243

  Steps to reproduce:
  0. Make sure 'Desktop mode' is switched off
  1. Go to System Setting > Launcher
  2. Move the slider to change 'Icon size'

  Expected result:
  The launcher is revealed so I can see what changes I'm making with the slider

  What happens instead:
  If I move the slider to the left: nothing happens.
  If I move the slider to the right: the launcher 'jumps' a bit like it was 
trying to show up but never really shows up.

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

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

[Touch-packages] [Bug 1657050] Re: unity8 menus are too narrow (don't adapt to content)

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-zesty-2404

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

Title:
  unity8 menus are too narrow (don't adapt to content)

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  See http://i.imgur.com/pSmWi3l.png

  Every single line in those menus is cut.

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

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

[Touch-packages] [Bug 1510203] Re: Bluetooth headset (MDR-XB950BT) detected but playback No sound at all

2017-01-25 Thread FRLinux

I ended up using blueman that you can install from the repos. It just
works. On occasions, I have to unplug my dongle and re-plug to make it
work. So not really fixed, just worked around.

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

Title:
  Bluetooth headset (MDR-XB950BT) detected but playback  No sound at all

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Upgraded to Ubuntu 15.10 from 15.04 a few days ago. Following update,
  peering of device is fine but I no longer can select my bluetooth
  headset to output sound. I see it in the list but I cannot switch
  sound to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 26 17:27:39 2015
  InstallationDate: Installed on 2014-03-05 (599 days ago)
  InstallationMedia: It
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: MDR-XB950BT
  Symptom_Type: No sound at all
  Title: [MDR-XB950BT, playback] No sound at all
  UpgradeStatus: Upgraded to wily on 2015-10-23 (2 days ago)
  dmi.bios.date: 12/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1202
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T DELUXE V2
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1202:bd12/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

This bug was fixed in the package apt - 1.4~beta4ubuntu1

---
apt (1.4~beta4ubuntu1) zesty; urgency=medium

  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Workaround debian/copyright symlink

 -- Julian Andres Klode   Wed, 25 Jan 2017 12:07:50
+0100

** Changed in: apt (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

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

Re: [Touch-packages] [Bug 1652348] Re: initrd dhcp fails / ignores valid response

2017-01-25 Thread Steve Langasek

On Tue, Jan 24, 2017 at 10:51:56PM -, Paul Graydon wrote:
> Given this is a fundamental bug in klibc, is there a plan to try to
> upstream this patch?

It has been upstreamed to the Debian git repository.  Given that we will be
looking at removing klibc from the initramfs altogether in future releases
(in favor of just using isc-dhcp), I don't intend to pursue it any further
than that.

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

Title:
  initrd dhcp fails / ignores valid response

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Xenial:
  Triaged

Bug description:
  [SRU justification]
  Changes to ordering of kernel enumeration of network interfaces, which may 
happen in any release, can regress network configuration from an initramfs.  
Support for netbooting should not depend on interface order, it should work 
reliably on all systems.

  [Test case]
  Detailed reproducer described in 
  .

  [Regression potential]
  Moderate regression potential, because of a relatively large patch touching a 
not-widely-used but still critical piece of code.  Regression testing should 
include verifying that MAAS-booted cloud images still work as expected in a 
variety of environments.

  Between kernel versions 4.4.0-53 and 4.4.0-57 a bug has been (re?)introduced 
that is breaking dhcp booting in the initrd environment.  This is stopping 
instances that use iscsi storage from being able to connect.

  Over serial console it outputs:

  IP-Config: no response after 2 secs - giving up
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f1 hardware address 90:e2:ba:d1:36:39 mtu 1500 DHCP RARP
  IP-Config: no response after 3 secs - giving up

  with increasing delays until it fails.  At which point a simple
  ipconfig -t dhcp -d "ens2f0"  works.  The console output is slightly
  garbled but should give you an idea:

  (initramfs) ipconfig -t dhcp -[  728.379793] ixgbe :13:00.0 ens2f0: 
changing MTU from 1500 to 9000
  d "ens2f0"
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f0 guessed broadcast address 10.0.1.255
  IP-Config: ens2f0 complete (dhcp from 169.254.169.254):
   addres[  728.980448] ixgbe :13:00.0 ens2f0: detected SFP+: 3
  s: 10.0.1.56broadcast: 10.0.1.255   netmask: 255.255.255.0
   gateway: 10.0.1.1   [  729.148410] ixgbe :13:00.0 ens2f0: NIC Link is Up 
10 Gbps, Flow Control: RX/TX
    dns0 : 169.254.169.254  dns1   : 0.0.0.0
   rootserver: 169.254.169.254 rootpath:
   filename  : /ipxe.efi

  tcpdumps show that dhcp requests are being received from the host, and
  responses sent, but not accepted by the host.  When the ipconfig
  command is issued manually, an identical dhcp request and response
  happens, only this time it is accepted.  It doesn't appear to be that
  the messages are being sent and received incorrectly, just silently
  ignored by ipconfig.

  I was seeing this behaviour earlier this year, which I was able to fix
  by specifying "ip=dhcp" as a kernel parameter.  About a month ago that
  was identified as causing us other problems (long story) and we
  dropped it, at which point we discovered the original bug was no
  longer an issue.

  Putting "ip=dhcp" back on with this kernel no longer fixes the
  problem.

  I've compared the two initrds and effectively the only thing that has
  changed between the two is the kernel components.

  Ubuntu kernel bisect offending commit:
  # first bad commit: [fd4b5fa6e3487d15ede746f92601af008b2abbc0] mnt: Add a per 
mount namespace limit on the number of mounts

  Ubuntu kernel bisect offending commit submission:
  https://lkml.org/lkml/2016/10/5/308

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

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

[Touch-packages] [Bug 1659255] Re: memory leak

I observed this with x+o, deb based.

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

Title:
  memory leak

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Not having looked into what exactly uses it, but after keeping unity8
  running over night, it consumes over 5GB of memory.

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

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

[Touch-packages] [Bug 1659316] Re: compiz

2017-01-25 Thread Paul White

nemo, please don't confirm your own bug reports, that's for others to do
if they see the same problem.

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

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

Title:
  compiz

Status in xorg package in Ubuntu:
  New

Bug description:
  i want start compiz but i have vesa driver installed

  Gathering information about your system...

   Distribution:  Ubuntu 15.10
   Desktop environment:   GNOME
   Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated 
Graphics Controller (rev 07)
   Driver in use: vesa
   Rendering method:  AIGLX

  Checking if it's possible to run Compiz on your system...  [SKIP]

  At least one check had to be skipped:
   Error: vesa driver in use

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Jan 25 15:49:04 2017
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-42-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
  MachineType: Acer TravelMate 5730
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=dbf84782-3125-4254-83ec-9f0a4e9f125b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.19
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd08/05/2008:svnAcer:pnTravelMate5730:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: TravelMate 5730
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Jan 25 15:07:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   32884 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Touch-packages] [Bug 1654624] Re: dhcp apparmor profile comlains about lxd client

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

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  dhcp apparmor profile comlains about lxd client

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  strange problem recently occured:

  I'm having some ubuntu machines running in LXD (nothing unusual, just
  based on the regular ubuntu LXD images) on a ubuntu host. Worked well
  for some time.

  But now the host generates messages like


  Jan  6 19:17:05 monstrum kernel: [ 1063.263531] audit: type=1400
  audit(1483726625.388:247): apparmor="DENIED" operation="file_perm"
  namespace="root//lxd-rackadmin_" profile="/sbin/dhclient"
  name="/apparmor/.null" pid=5125 comm="dhclient" requested_mask="w"
  denied_mask="w" fsuid=165536 ouid=0

  
  in /var/log/kern.log. 

  For some reason the apparmor running on the host interferes with the
  containers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12.6
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jan  6 19:19:12 2017
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (275 days ago)

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

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

[Touch-packages] [Bug 1659255] Re: memory leak

2017-01-25 Thread kevin gunn

curious - is this zesty? or xenial+overlay?
also, is this debs or snaps?

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

Title:
  memory leak

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Not having looked into what exactly uses it, but after keeping unity8
  running over night, it consumes over 5GB of memory.

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

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

[Touch-packages] [Bug 1659288] Re: appear.in on phones won't enter a chat room

2017-01-25 Thread Pat McGowan

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

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

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

Title:
  appear.in on phones won't enter a chat room

Status in Canonical System Image:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  (initially reported as https://lists.launchpad.net/ubuntu-
  phone/msg23290.html).

  When creating a new chat room on https://appear.in/, the user is
  informed that she has been invited to a conversation, and there is a
  "join" button, but tapping it does nothing. The following can be seen
  in the logs:

  WARNING **: Unable to dispatch url 'intent://appear.in/spectacular-
  
scorpion#Intent;scheme=http;action=android.intent.action.VIEW;end;':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'intent://appear.in/spectacular-
  scorpion#Intent;scheme=http;action=android.intent.action.VIEW;end;' is
  not handleable by the URL Dispatcher

  It seems appear.in thinks it’s being used on android, and wants the
  user to install their native app? A simple UA override should do the
  trick.

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

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

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

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

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

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

Title:
  App Drawer does not refresh

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

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

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

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

[Touch-packages] [Bug 1658190] Re: Searching with the app drawer causes Unity 8 to crash in some circumstances

The speed at which the search is done doesn't matter... It is even
possible to

search "xterm", delete that, type "s", switch to another vt, attach gdb
to unity8, switch back and then type "a" to make it happen.

Sadly, the stack traces always seem to end up in some Qt metacall magic
for invalidating the filters.

** Summary changed:

- Searching rapidly with the app drawer causes Unity 8 to crash
+ Searching with the app drawer causes Unity 8 to crash in some circumstances

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

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

Title:
  Searching with the app drawer causes Unity 8 to crash in some
  circumstances

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Latest zesty
  unity8 8.15+17.04.20170110.4-0ubuntu1

  Searching rapidly for apps in the app drawer is causing a crash for
  me. I have quite a few applications (including libertine apps)
  available. To reproduce:

  1. Open app drawer
  2. Enter a few characters to match an app
  3. Clear searchbar with backspaces
  4. Goto step 2 (switching characters from time to time)

  This crashes Unity 8 for me sometimes as quickly as 20 searches, but
  other times it takes up to 50 searches.

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

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

[Touch-packages] [Bug 1591384] Re: Dialog of Blinken app is painted all wrong the first time it is open

2017-01-25 Thread Albert Astals Cid

Seems fixed.

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

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

Title:
  Dialog of Blinken app is painted all wrong the first time it is open

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce:
   * Be in unity8 on the desktop
   * Install blinken from repository
   * Edit /usr/share/applications/org.kde.blinken.desktop and add a 
X-Ubuntu-Touch=true after [Desktop Entry]
   * refresh the app scope
   * start blinken from the app scope
   * Show the about dialog in blinken (use the bottom right circle for it)
   * See how it is badly painted (screenshot attached)
   * If you close it and open it again it will look good (you may or may not 
have to remove the .cache/unity8 file that stores windows sizes for making the 
bug happen the next time)

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

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

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

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

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

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

Title:
  App Drawer does not refresh

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

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

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

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

[Touch-packages] [Bug 1658190] Re: Searching rapidly with the app drawer causes Unity 8 to crash

Ok, I can reproduce this now. Some findings:

I seems to only happen when searching for "xt" (xterm), then searching
something in the "S" section and when the search result gives only one
result within that section after the second letter. E.g. for me it
crashes when searching for "sa" (sakura), "su" (sudoku) and "sn"
(screenshot) but not with anything else in the "S" section.

Also, the "S" section is the largest one for me. I could not find any
other section where it happens.

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

Title:
  Searching rapidly with the app drawer causes Unity 8 to crash

Status in unity8 package in Ubuntu:
  New

Bug description:
  Latest zesty
  unity8 8.15+17.04.20170110.4-0ubuntu1

  Searching rapidly for apps in the app drawer is causing a crash for
  me. I have quite a few applications (including libertine apps)
  available. To reproduce:

  1. Open app drawer
  2. Enter a few characters to match an app
  3. Clear searchbar with backspaces
  4. Goto step 2 (switching characters from time to time)

  This crashes Unity 8 for me sometimes as quickly as 20 searches, but
  other times it takes up to 50 searches.

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

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

[Touch-packages] [Bug 1659331] [NEW] user background disappears

2017-01-25 Thread DLCBurggraaff

Public bug reported:

For some users lightdm displays the user's background for a second or two and 
then shows a solid blue background. Login etc. is OK.
I have seen this behavior for over a year now (so things already started with 
14.04) on several boxes.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Jan 25 16:10:20 2017
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  user background disappears

Status in lightdm package in Ubuntu:
  New

Bug description:
  For some users lightdm displays the user's background for a second or two and 
then shows a solid blue background. Login etc. is OK.
  I have seen this behavior for over a year now (so things already started with 
14.04) on several boxes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 25 16:10:20 2017
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1659319] Re: Changing language mid-word results in duplicated words

** Description changed:

  Steps:
- * start typing a word (think "foo")
- * change language
- * continue typing (think "foob")
- * select the auto-completed word (think "foobar")
+ * switch to En layout
+ * type "bar"
+ * change to Pl layout
+ * type "dz"
+ * select the auto-completed "bardzo"
  
  Expected:
- * "foobar" is put into the input field
+ * "bardzo" is put into the input field
  
  Current:
- * "foofoobar" is put into the input field
+ * "barbardzo" is put into the input field
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-keyboard 0.100+17.04.20170110-0ubuntu1
  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: Wed Jan 25 15:45:00 2017
  InstallationDate: Installed on 2016-05-06 (263 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (64 days ago)

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

Title:
  Changing language mid-word results in duplicated words

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  * switch to En layout
  * type "bar"
  * change to Pl layout
  * type "dz"
  * select the auto-completed "bardzo"

  Expected:
  * "bardzo" is put into the input field

  Current:
  * "barbardzo" is put into the input field

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-keyboard 0.100+17.04.20170110-0ubuntu1
  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: Wed Jan 25 15:45:00 2017
  InstallationDate: Installed on 2016-05-06 (263 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (64 days ago)

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

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

[Touch-packages] [Bug 1659316] Re: compiz

2017-01-25 Thread nemo

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

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

Title:
  compiz

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  i want start compiz but i have vesa driver installed

  Gathering information about your system...

   Distribution:  Ubuntu 15.10
   Desktop environment:   GNOME
   Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated 
Graphics Controller (rev 07)
   Driver in use: vesa
   Rendering method:  AIGLX

  Checking if it's possible to run Compiz on your system...  [SKIP]

  At least one check had to be skipped:
   Error: vesa driver in use

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Jan 25 15:49:04 2017
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-42-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
  MachineType: Acer TravelMate 5730
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=dbf84782-3125-4254-83ec-9f0a4e9f125b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.19
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd08/05/2008:svnAcer:pnTravelMate5730:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: TravelMate 5730
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Jan 25 15:07:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   32884 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Touch-packages] [Bug 1659319] Re: Changing language mid-word results in duplicated words

2017-01-25 Thread Michael Sheldon

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-keyboard (Ubuntu)
 Assignee: (unassigned) => Michael Sheldon (michael-sheldon)

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Changing language mid-word results in duplicated words

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  * switch to En layout
  * type "bar"
  * change to Pl layout
  * type "dz"
  * select the auto-completed "bardzo"

  Expected:
  * "bardzo" is put into the input field

  Current:
  * "barbardzo" is put into the input field

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-keyboard 0.100+17.04.20170110-0ubuntu1
  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: Wed Jan 25 15:45:00 2017
  InstallationDate: Installed on 2016-05-06 (263 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (64 days ago)

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

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

[Touch-packages] [Bug 1510203] Re: Bluetooth headset (MDR-XB950BT) detected but playback No sound at all

2017-01-25 Thread Mariusz Czapski

I have the same issue on 16.04, so maybe this issue is connected to the
bluetooth dongle. Can you check this issue ones more, because now the
solution is to buy new computer or change linux distro or even linux
because this is now working. Btw on macOsx and Windows my hadset MDR-
XB950BT works fine. My distro is xubuntu 16.04, and my computer is dell
e5320.

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

Title:
  Bluetooth headset (MDR-XB950BT) detected but playback  No sound at all

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Upgraded to Ubuntu 15.10 from 15.04 a few days ago. Following update,
  peering of device is fine but I no longer can select my bluetooth
  headset to output sound. I see it in the list but I cannot switch
  sound to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 26 17:27:39 2015
  InstallationDate: Installed on 2014-03-05 (599 days ago)
  InstallationMedia: It
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: MDR-XB950BT
  Symptom_Type: No sound at all
  Title: [MDR-XB950BT, playback] No sound at all
  UpgradeStatus: Upgraded to wily on 2015-10-23 (2 days ago)
  dmi.bios.date: 12/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1202
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T DELUXE V2
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1202:bd12/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1659316] [NEW] compiz

2017-01-25 Thread nemo

Public bug reported:

i want start compiz but i have vesa driver installed

Gathering information about your system...

 Distribution:  Ubuntu 15.10
 Desktop environment:   GNOME
 Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated 
Graphics Controller (rev 07)
 Driver in use: vesa
 Rendering method:  AIGLX

Checking if it's possible to run Compiz on your system...  [SKIP]

At least one check had to be skipped:
 Error: vesa driver in use

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Jan 25 15:49:04 2017
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.14, 4.2.0-42-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:013c]
   Subsystem: Acer Incorporated [ALI] Device [1025:013c]
MachineType: Acer TravelMate 5730
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=dbf84782-3125-4254-83ec-9f0a4e9f125b ro quiet splash vt.handoff=7
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.19
dmi.board.name: Homa
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd08/05/2008:svnAcer:pnTravelMate5730:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: TravelMate 5730
dmi.product.version: 0100
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Jan 25 15:07:31 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   32884 
 vendor AUO
xserver.version: 2:1.17.2-1ubuntu9.1

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


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

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

Title:
  compiz

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  i want start compiz but i have vesa driver installed

  Gathering information about your system...

   Distribution:  Ubuntu 15.10
   Desktop environment:   GNOME
   Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated 
Graphics Controller (rev 07)
   Driver in use: vesa
   Rendering method:  AIGLX

  Checking if it's possible to run Compiz on your system...  [SKIP]

  At least one check had to be skipped:
   Error: vesa driver in use

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Jan 25 15:49:04 2017
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-42-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
  MachineType: Acer TravelMate 5730
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine:

[Touch-packages] [Bug 1659319] [NEW] Changing language mid-word results in duplicated words

Public bug reported:

Steps:
* start typing a word (think "foo")
* change language
* continue typing (think "foob")
* select the auto-completed word (think "foobar")

Expected:
* "foobar" is put into the input field

Current:
* "foofoobar" is put into the input field

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubuntu-keyboard 0.100+17.04.20170110-0ubuntu1
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: Wed Jan 25 15:45:00 2017
InstallationDate: Installed on 2016-05-06 (263 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: ubuntu-keyboard
UpgradeStatus: Upgraded to zesty on 2016-11-22 (64 days ago)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Changing language mid-word results in duplicated words

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Steps:
  * start typing a word (think "foo")
  * change language
  * continue typing (think "foob")
  * select the auto-completed word (think "foobar")

  Expected:
  * "foobar" is put into the input field

  Current:
  * "foofoobar" is put into the input field

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-keyboard 0.100+17.04.20170110-0ubuntu1
  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: Wed Jan 25 15:45:00 2017
  InstallationDate: Installed on 2016-05-06 (263 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (64 days ago)

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-25 Thread Dan Streetman

So the only new autopkgtest failures are:

> Regression in autopkgtest for umockdev (armhf): test log

this fails with:
ERROR:tests/test-umockdev-record.c:706:t_system_single: assertion failed 
(_tmp10_ == ""): ("Cannot access device /dev/loop0: No such file or 
directory\n" == "")

this is the first test failure on trusty/armhf:
http://autopkgtest.ubuntu.com/packages/umockdev/trusty/armhf

however, it's failed for xenial, yakkety, and zesty on armhf for a long time, 
with the same failure:
http://autopkgtest.ubuntu.com/packages/umockdev/xenial/armhf
http://autopkgtest.ubuntu.com/packages/umockdev/yakkety/armhf
http://autopkgtest.ubuntu.com/packages/umockdev/zesty/armhf

so it seems like whatever was causing the failures for X/Y/Z on armhf is
now also causing the failure for trusty on armhf; I think it's unlikely
a systemd change caused the failure.

> Regression in autopkgtest for upstart (amd64): test log

this fails with:
test_state: tests/test_state.c:4048: test_upstart_with_apparmor_upgrade: 
Assertion `(state_from_string (json_string)) == 0' failed.

Closer looks shows it's complaining about the JSON data, the test was
expecting a comment:

(null): Detected invalid serialisation data: expected comment
test_state: tests/test_state.c:4048: test_upstart_with_apparmor_upgrade: 
Assertion `(state_from_string (json_string)) == 0' failed.

I can't tell why it's failing now but not before, but it's also hard to
see any relation between a systemd/udev update and upstart JSON
serialization failure.

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in maas-images:
  New
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug

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

2017-01-25 Thread Alexey Bazhin

apport information

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (68 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: xorg 1:7.7+13ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1656808] Re: unity8 fullscreen breaks tiling

2017-01-25 Thread Lukáš Tinkl

** Branch linked: lp:~lukas-kde/unity8/minimized-and-fullscreen-window-
fixes

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

Title:
  unity8 fullscreen breaks tiling

Status in Canonical System Image:
  New
Status in MirAL:
  Invalid
Status in Ubuntu UX:
  New
Status in miral package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  open the webbrowser
  snap it to the right or left
  press F11 to full screen the app
  press F11 again to exit full screen
  the webbrowser app should return to the original snaped position

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

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

[Touch-packages] [Bug 1652253] Re: Xorg crash

2017-01-25 Thread Alexey Bazhin

apport information

** Tags added: apport-collected

** Description changed:

  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.3-0ubuntu8.2
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 16.10
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2016-11-18 (68 days ago)
+ InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
+ Package: xorg 1:7.7+13ubuntu4
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
+ Tags:  yakkety
+ Uname: Linux 4.8.0-34-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux

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

2017-01-25 Thread Alexey Bazhin

apport information

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (68 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: xorg 1:7.7+13ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1659288] Re: appear.in on phones won't enter a chat room

** Branch linked: lp:webbrowser-app/staging

** Branch linked: lp:~ci-train-bot/webbrowser-app/webbrowser-app-ubuntu-
zesty-2396

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

Title:
  appear.in on phones won't enter a chat room

Status in Canonical System Image:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  (initially reported as https://lists.launchpad.net/ubuntu-
  phone/msg23290.html).

  When creating a new chat room on https://appear.in/, the user is
  informed that she has been invited to a conversation, and there is a
  "join" button, but tapping it does nothing. The following can be seen
  in the logs:

  WARNING **: Unable to dispatch url 'intent://appear.in/spectacular-
  
scorpion#Intent;scheme=http;action=android.intent.action.VIEW;end;':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'intent://appear.in/spectacular-
  scorpion#Intent;scheme=http;action=android.intent.action.VIEW;end;' is
  not handleable by the URL Dispatcher

  It seems appear.in thinks it’s being used on android, and wants the
  user to install their native app? A simple UA override should do the
  trick.

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

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

[Touch-packages] [Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

2017-01-25 Thread Nick

I'm possibly experiencing this bug, but I'm using the Nvidia proprietary 
driver, particularly the 367.57 version.
I tried to switch the clocksource to acpi_pm, as suggested in some forums, but 
it doesn't help.

While that's EQ overflowing, I couldn't check anything but reboot.

Attached is the Xorg.0.log.old file.

** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+attachment/4808950/+files/Xorg.0.log.old

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

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

Title:
  graphic system freezes after a while, can still ssh into machine

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 desktop with all updates up to date
  Gigagyte GA-Z170 motherboard, Intel i7-6700 3.4gHz, 64GB RAM, Samsung 840 
SSD, Gigabyte GEForce GT710 graphics (nvidia chipset)

  Very light load. A few terminal windows, a few Firefox pages,
  Thunderbird, and VirtualBox (with the extension pack loaded) running
  one small Linux VM with 512Mb memory (very lightly loaded as it's only
  running bind9). I think (but don't have perfect certainty on this)
  that some of the crashes have happened without VirtualBox running.
  Also running rsync so that backuppc on a separate machine can back it
  up over the network (backuppc has been a real lifesaver with all the
  reinstallations!)

  After booting the system runs happily for a while then the GUI
  freezes. This can take a few hours or up to a day or two. You can
  still ssh into the system, and if you do "top" it typically shows 100%
  CPU load on systemd-timesync.

  The same happens whether I use nouveau or the proprietary nvidia driver (361)
  I have tried a complete reinstallation (4 times already, starting to get 
quite frustrating) using the proprietary drivers and NOT using the proprietary 
drivers and the same still happens. The most recent time was with nouveau, and 
Xorg.log has a number of entries like this:
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5652cde325ce]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x5652cde14083]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x5652cdcec662]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x61f3) 
[0x7f31f98621f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x6a5d) 
[0x7f31f9862a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x5652cdc8+0x94228) [0x5652cdd14228]
  (EE) 6: /usr/lib/xorg/Xorg (0x5652cdc8+0xb96f2) [0x5652cdd396f2]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 8: /usr/lib/xorg/Xorg (GiveUp+0x0) [0x5652cde37330]
  (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f3202debcf3]
  (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1d7) [0x5652cde2f307]
  (EE) 12: /usr/lib/xorg/Xorg (0x5652cdc8+0x539ee) [0x5652cdcd39ee]
  (EE) 13: /usr/lib/xorg/Xorg (0x5652cdc8+0x57c33) [0x5652cdcd7c33]
  (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f3202d0f830]
  (EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x5652cdcc1f59]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
   
  Then at the end the last few are:

  [  6265.543] [mi] Increasing EQ size to 1024 to prevent dropped events.
  [  6265.543] [mi] EQ processing has resumed after 1070 dropped events.
  [  6265.543] [mi] This may be caused by a misbehaving driver monopolizing the 
server's resources.

  What cna the problem possibly be, especially as 16.04 is meant to be a
  stable release and an Nvidia GT710 card is hardly bleeding-edge? Help
  greatly appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jun  1 13:22:13 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation Device [10de:128b] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd

[Touch-packages] [Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

2017-01-25 Thread Nick

P.S. mine is also GT710 and Xubuntu 16.04, with kernel 4.4.0-59-generic.

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

Title:
  graphic system freezes after a while, can still ssh into machine

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 desktop with all updates up to date
  Gigagyte GA-Z170 motherboard, Intel i7-6700 3.4gHz, 64GB RAM, Samsung 840 
SSD, Gigabyte GEForce GT710 graphics (nvidia chipset)

  Very light load. A few terminal windows, a few Firefox pages,
  Thunderbird, and VirtualBox (with the extension pack loaded) running
  one small Linux VM with 512Mb memory (very lightly loaded as it's only
  running bind9). I think (but don't have perfect certainty on this)
  that some of the crashes have happened without VirtualBox running.
  Also running rsync so that backuppc on a separate machine can back it
  up over the network (backuppc has been a real lifesaver with all the
  reinstallations!)

  After booting the system runs happily for a while then the GUI
  freezes. This can take a few hours or up to a day or two. You can
  still ssh into the system, and if you do "top" it typically shows 100%
  CPU load on systemd-timesync.

  The same happens whether I use nouveau or the proprietary nvidia driver (361)
  I have tried a complete reinstallation (4 times already, starting to get 
quite frustrating) using the proprietary drivers and NOT using the proprietary 
drivers and the same still happens. The most recent time was with nouveau, and 
Xorg.log has a number of entries like this:
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5652cde325ce]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x5652cde14083]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x5652cdcec662]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x61f3) 
[0x7f31f98621f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x6a5d) 
[0x7f31f9862a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x5652cdc8+0x94228) [0x5652cdd14228]
  (EE) 6: /usr/lib/xorg/Xorg (0x5652cdc8+0xb96f2) [0x5652cdd396f2]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 8: /usr/lib/xorg/Xorg (GiveUp+0x0) [0x5652cde37330]
  (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f3202debcf3]
  (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1d7) [0x5652cde2f307]
  (EE) 12: /usr/lib/xorg/Xorg (0x5652cdc8+0x539ee) [0x5652cdcd39ee]
  (EE) 13: /usr/lib/xorg/Xorg (0x5652cdc8+0x57c33) [0x5652cdcd7c33]
  (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f3202d0f830]
  (EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x5652cdcc1f59]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
   
  Then at the end the last few are:

  [  6265.543] [mi] Increasing EQ size to 1024 to prevent dropped events.
  [  6265.543] [mi] EQ processing has resumed after 1070 dropped events.
  [  6265.543] [mi] This may be caused by a misbehaving driver monopolizing the 
server's resources.

  What cna the problem possibly be, especially as 16.04 is meant to be a
  stable release and an Nvidia GT710 card is hardly bleeding-edge? Help
  greatly appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jun  1 13:22:13 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation Device [10de:128b] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:36ec]
  InstallationDate: Installed on 2016-06-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. Z170-D3H
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=79d1ab40-4431-445f-87bb-6a8d44370cee ro quiet splash

[Touch-packages] [Bug 1657085] Re: Submenus don't open on mouse hover

2017-01-25 Thread Albert Astals Cid

** Branch linked: lp:~aacid/unity8/autoOpenSubMenus

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

Title:
  Submenus don't open on mouse hover

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  In Unity 7 if you leave the mouse over a menu item that has children
  (e.g. in firefox View -> Page Size) the submenu opens in some time
  (seems to be around the half a second).

  In Unity 8 you actually have to click on the item to open the submenu.

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

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

[Touch-packages] [Bug 1659302] Re: Wallpaper crossfade between users stutters

** Summary changed:

- Wallpaper crossfade between users not stutters
+ Wallpaper crossfade between users stutters

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

Title:
  Wallpaper crossfade between users stutters

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  When you toggle between users with different wallpapers in the
  greeter, the crossfade animation gets stuck for a couple seconds,
  seemingly while the infographic gets updated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170124-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2272]
  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: Wed Jan 25 14:28:42 2017
  InstallationDate: Installed on 2016-05-06 (263 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (63 days ago)

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

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

[Touch-packages] [Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)

2017-01-25 Thread Anatoli

Maintainers, please set a priority (severe IMO) and assign this bug to
someone, it's extremely annoying to wait up to 5 minutes for the
computer to shutdown and get some errors during the process.

Network-manager should have some mechanism to instruct it not to
shutdown the network before some signal or other indication. It can't
just cut the network when other processes are using it. Maybe an order
of shutdown could be defined via systemd.

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

Title:
  120sec delay during shutdown or reboot with still mounted cifs (via
  Wifi)

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
  with no issue.

  I prepare for mounting with the following entry in /etc/fstab my
  Synology NAS :

  //192.168.178.61/data /media/server/server_data cifs
  
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
  0

  After login to unity, I mount it with a bash-script (mount -a) which
  is called from ~/.config/autostart/myMounts.desktop

  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
  process stops at the command "umount /media/server ..."

  I have not tested if this also occurs when I am connected via
  ethernet. I think it is because the (Wifi)Network is already disabled
  prior all umounts are done.

  This issue happens even if I type in a shutdown command into a
  Terminal or if I choose shutdown form the menue, also if I use the
  power-button.

  Failure can be avoided if I umount the network-drives manually
  previouse to reboot.

  Interim solution was, to create an alias for "shutdown" like "sh
  /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-25 Thread Dan Streetman

> Could someone please look at the autopkgtest regressions in 
> http://people.canonical.com/~ubuntu-
> archive/pending-sru.html against systemd please?

I'll ignore the no-longer-supported LTS kernel tests, so that leaves:

> Regression in autopkgtest for network-manager (ppc64el): test log

This has been failing since late 2015, with the same failure each time.
http://autopkgtest.ubuntu.com/packages/n/network-manager/trusty/ppc64el

> Regression in autopkgtest for linux-lts-xenial (ppc64el): test log
> Regression in autopkgtest for linux-lts-xenial (i386): test log
> Regression in autopkgtest for linux-lts-xenial (armhf): test log

These are failing either because the running and test kernel versions
don't match, or because the test timed out.  Again, they appear to have
been failing for a long time; no new failures for the latest systemd.

> Regression in autopkgtest for ubuntu-drivers-common (i386): test log

another test that's failed for a long time in the same way each time.
nothing new.

> Regression in autopkgtest for umockdev (armhf): test log

this fails with:
ERROR:tests/test-umockdev-record.c:706:t_system_single: assertion failed 
(_tmp10_ == ""): ("Cannot access device /dev/loop0: No such file or 
directory\n" == "")

it's not clear why there's no /dev/loop0, and previous test runs didn't
fail.

> Regression in autopkgtest for open-iscsi (armhf): test log

this has failed the same way for the last 6 tests, because open-iscsi
isn't running.  Not sure what introduced that, but it happened before
the last systemd update.

> Regression in autopkgtest for upstart (amd64): test log

this fails with:
test_state: tests/test_state.c:4048: test_upstart_with_apparmor_upgrade: 
Assertion `(state_from_string (json_string)) == 0' failed.

obviously not a helpful test failure message.

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in maas-images:
  New
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

2017-01-25 Thread Ernst Sjöstrand

The Redhat patch is the same patch as the one that fixes Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834722

That patch is already upstream, where the debian package seems to be maintained 
also:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=0682b7795cd0c25553b91de89c2a3b3d3ff17014;hp=b637d7815da89b5fb04c27b1d9a361fe5b2622a0

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

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

Title:
  Name resolution stops working after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

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

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

[Touch-packages] [Bug 1659302] [NEW] Wallpaper crossfade between users not stutters

Public bug reported:

When you toggle between users with different wallpapers in the greeter,
the crossfade animation gets stuck for a couple seconds, seemingly while
the infographic gets updated.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity8 8.15+17.04.20170124-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2272]
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: Wed Jan 25 14:28:42 2017
InstallationDate: Installed on 2016-05-06 (263 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: unity8
UpgradeStatus: Upgraded to zesty on 2016-11-22 (63 days ago)

** Affects: unity8 (Ubuntu)
 Importance: Low
 Assignee: Michael Terry (mterry)
 Status: Triaged


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

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

Title:
  Wallpaper crossfade between users not stutters

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  When you toggle between users with different wallpapers in the
  greeter, the crossfade animation gets stuck for a couple seconds,
  seemingly while the infographic gets updated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170124-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2272]
  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: Wed Jan 25 14:28:42 2017
  InstallationDate: Installed on 2016-05-06 (263 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (63 days ago)

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

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

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-01-25 Thread Jaakko Salo

As a workaround, you can do the following (using the original report's
config as an example):

# systemctl edit ifup@bond0.3000

Add the following and save the file:

[Unit]
After=ifup@bond0.service

Then, let's add Type=oneshot to the ifup@ template so that the above
After= actually has some effect:

# systemctl edit ifup@

Add the following and save the file:

[Service]
Type=oneshot

Then reboot.

The problem seems to be a race condition introduced with systemd
integration. For me, the missing default route triggered around 80% of
the time, but not always.

On Ubuntu 16, systemd executes the ifup@ template units in parallel in a
way that is not adequately controlled. For instance, ifup@bond0.3000 and
ifup@bond0 will execute in parallel. The ifup for bond0 will involve "ip
link ... down", then "up" from ifenslave hooks. I believe that if the
link down comes after default route from bond0.3000, the default route
will be deleted. My journalctl observations support this.

Debugging tip: use systemctl edit ifup@, and add --verbose to the ifup
invocations (note, there are 2 of them!). Adding the verbose option to
/etc/default/networking does not work, except for lo interface.

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

Title:
  default gateway route not installed for bond interfaces through reboot

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Expectation:  After reboot, route for default gateway specified on
  bonded interface is installed according to "gateway x.x.x.x"  (where
  x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces
  or files sourced per /etc/network/interfaces

  Actual Result: After reboot, route is not installed. Interface does
  work otherwise (I can ping the gateway on that subnet, for instance).
  'ifdown -a' followed by  'ifup -a' (run with proper permission... so
  sudo) brings the gateway back until next reboot.

  Package:  I'm not familiar enough to be certain what is causing this,
  but I was seeing this in beta2 of 16.04 as well.

  *username snipped*@*hostname snipped*:~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04
  *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave
  ifenslave:
Installed: 2.7ubuntu1
Candidate: 2.7ubuntu1
Version table:
   *** 2.7ubuntu1 100
  100 /var/lib/dpkg/status

  *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown
  ifupdown:
Installed: 0.8.10ubuntu1
Candidate: 0.8.10ubuntu1
Version table:
   *** 0.8.10ubuntu1 100
  100 /var/lib/dpkg/status
  
  




  
/etc/network/interfaces

  --
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto enp2s0f1
  iface enp2s0f1 inet manual
  bond-master bond0

  auto enp2s0f0
  iface enp2s0f0 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  address 10.96.96.2
  netmask 255.255.255.0
  network 10.96.96.0
  broadcast 10.96.96.255
  # dns-* options are implemented by the resolvconf package, if 
installed
  dns-search *snip*
  bond-mode balance-alb
  bond-slaves none
  bond-miimon 100
  auto bond0.3000 
  iface bond0.3000 inet static
  address 172.21.33.29
  netmask 255.255.255.0
  network 172.21.33.0
  broadcast 172.21.33.255
  gateway 172.21.33.1
  dns-search *snip*
  vlan-raw-device bond0
  dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2
  
  -
  interfaces.d is empty:

  *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d
  total 8.0K
  10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 .
  10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 ..

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

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

[Touch-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

2017-01-25 Thread Amr Ibrahim

** Changed in: upower (Ubuntu Xenial)
   Status: Fix Committed => Confirmed

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in upower source package in Xenial:
  Confirmed

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

  
  To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

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

2017-01-25 Thread Andre Heinecke

> https://www.python.org/dev/peps/pep-0524/

This has nothing to do with it. GpgME does not gather the entropy /
randomness itself but leaves this to libgcrypt / gpg-agent. On Linux
system this means to add some entropy from /dev/random into the mix. If
nothing is available there it will block indefinitely until enough
entropy is available.

So I agree with dkg's suggestion that a lack of entropy in your build 
environments is a likely explanation.
I can reproduce a fairly long hang by starving my system of entropy using "cat 
/dev/random > /dev/null" and then running make check.

It could be worked around by something like "rngd -r /dev/urandom" but
the testsuite should not rely on hard entropy. GnuPG's testsuite itself
includes a solution to that problem, launching gpg-agent with --debug-
quick-random.

I've changed the start script of the gpg-agent in gpgme accordingly
with:

https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=a98951a30a6ae603ffac4ec8c5168aa6d1019933

To also use that option. Please confirm if this fixes the Problem in
your build environment.

-- 
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 1659288] [NEW] appear.in on phones won't enter a chat room

2017-01-25 Thread Olivier Tilloy

Public bug reported:

(initially reported as https://lists.launchpad.net/ubuntu-
phone/msg23290.html).

When creating a new chat room on https://appear.in/, the user is
informed that she has been invited to a conversation, and there is a
"join" button, but tapping it does nothing. The following can be seen in
the logs:

WARNING **: Unable to dispatch url 'intent://appear.in/spectacular-
scorpion#Intent;scheme=http;action=android.intent.action.VIEW;end;':GDBus.Error:com.canonical.URLDispatcher.BadURL:
URL 'intent://appear.in/spectacular-
scorpion#Intent;scheme=http;action=android.intent.action.VIEW;end;' is
not handleable by the URL Dispatcher

It seems appear.in thinks it’s being used on android, and wants the user
to install their native app? A simple UA override should do the trick.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: In Progress

** Affects: webbrowser-app (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: In Progress

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

** Changed in: webbrowser-app (Ubuntu)
   Status: New => In Progress

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

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

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

Title:
  appear.in on phones won't enter a chat room

Status in Canonical System Image:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  (initially reported as https://lists.launchpad.net/ubuntu-
  phone/msg23290.html).

  When creating a new chat room on https://appear.in/, the user is
  informed that she has been invited to a conversation, and there is a
  "join" button, but tapping it does nothing. The following can be seen
  in the logs:

  WARNING **: Unable to dispatch url 'intent://appear.in/spectacular-
  
scorpion#Intent;scheme=http;action=android.intent.action.VIEW;end;':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'intent://appear.in/spectacular-
  scorpion#Intent;scheme=http;action=android.intent.action.VIEW;end;' is
  not handleable by the URL Dispatcher

  It seems appear.in thinks it’s being used on android, and wants the
  user to install their native app? A simple UA override should do the
  trick.

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

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

[Touch-packages] [Bug 1659288] Re: appear.in on phones won't enter a chat room

** Branch linked: lp:~ci-train-bot/webbrowser-app/webbrowser-app-ubuntu-
vivid-2398

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

Title:
  appear.in on phones won't enter a chat room

Status in Canonical System Image:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  (initially reported as https://lists.launchpad.net/ubuntu-
  phone/msg23290.html).

  When creating a new chat room on https://appear.in/, the user is
  informed that she has been invited to a conversation, and there is a
  "join" button, but tapping it does nothing. The following can be seen
  in the logs:

  WARNING **: Unable to dispatch url 'intent://appear.in/spectacular-
  
scorpion#Intent;scheme=http;action=android.intent.action.VIEW;end;':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'intent://appear.in/spectacular-
  scorpion#Intent;scheme=http;action=android.intent.action.VIEW;end;' is
  not handleable by the URL Dispatcher

  It seems appear.in thinks it’s being used on android, and wants the
  user to install their native app? A simple UA override should do the
  trick.

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

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

[Touch-packages] [Bug 1648173] Re: App drawer stays on screen after activating launcher item

** Branch unlinked: lp:~mzanetti/unity8/appdrawer-improvements

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

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

Title:
  App drawer stays on screen after activating launcher item

Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  In https://bileto.ubuntu.com/#/ticket/2150 - after fixing bug #1591311

  Steps:
  * press Super+A or long-left-swipe to invoke the app drawer
  * click on an item in launcher

  Expected:
  * drawer is closed, as it is when you launch an item from the drawer

  Current:
  * drawer stays on, likely covering part of the activated window

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20161129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec  7 18:17:15 2016
  InstallationDate: Installed on 2016-05-06 (214 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago)

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

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

[Touch-packages] [Bug 1656785] Re: nc -d -l does not return data (only empty strings)

2017-01-25 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 netcat-openbsd in Ubuntu.
https://bugs.launchpad.net/bugs/1656785

Title:
  nc -d -l does not return data (only empty strings)

Status in netcat-openbsd package in Ubuntu:
  New
Status in netcat-openbsd package in Debian:
  New

Bug description:
  The Zesty (17.04) version of nc (1.130-1ubuntu1) no longer returns the
  received data when using the '-d' (do not listen on stdin) flag
  together with the '-l' (listen on socket) flag. This used to work in
  previous releases (1.105-7ubuntu1 Trusty-Yakkety). In fact, in the
  previous version, the '-d' flag seems to be required to make the data
  transfer more reliable in scripts.

  Testcase: Attached script passes on older versions, fails with the
  current version of nc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1656785/+subscriptions

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

[Touch-packages] [Bug 1622686] Please test proposed package

Hello Dave, or anyone else affected,

Accepted humanity-icon-theme into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/humanity-icon-theme/0.6.11.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation 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!

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Committed
Status in ubiquity source package in Xenial:
  New
Status in humanity-icon-theme source package in Yakkety:
  Fix Committed
Status in ubiquity source package in Yakkety:
  New

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

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

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

[Touch-packages] [Bug 1622686] Re: double header in 16.10

Hello Dave, or anyone else affected,

Accepted humanity-icon-theme into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/humanity-icon-theme/0.6.10.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation 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: humanity-icon-theme (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: humanity-icon-theme (Ubuntu Yakkety)
   Status: New => Fix Committed

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Committed
Status in ubiquity source package in Xenial:
  New
Status in humanity-icon-theme source package in Yakkety:
  Fix Committed
Status in ubiquity source package in Yakkety:
  New

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

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

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

[Touch-packages] [Bug 1657863] Please test proposed package

Hello David, or anyone else affected,

Accepted humanity-icon-theme into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/humanity-icon-theme/0.6.11.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation 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!

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

Title:
  Icons are too big or the wrong icon is shown on hidpi screens

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Committed
Status in humanity-icon-theme source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  Humanity icons are sometimes displayed too big on hidpi screens in
  16.04.  On both 16.04 and 16.10, different icons are used on hidpi
  screens than non-hidpi screens.  Sometimes the icons look similar but
  with much thinner strokes, while other times an icon with a different
  metaphor is used.  Users on hidpi screens will notice that icons in
  applications like Nautilus, Transmission, etc. look different (not
  just clearer) on hidpi screens.

  The fix here is to add support for @2 icons to the Humanity theme by
  adding symbolic links for @2 icons and updating the index.theme files
  accordingly.

  We should backport the fix to 16.04 and 16.10, so Humanity icons look
  the same on hidpi screens as non-hidpi screens.

  
  [Test Case]

  Here are a few test cases: 
  1) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi 
screen are much larger.  (This applies to icons on the desktop as well.)
  -The fix should result in icons being the same size on both hidpi and 
lowdpi.
  
  2) Using a computer with a hidpi screen and one with a lowdpi screen running 
Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the 
toolbar uses an icon with a different metaphor on hidpi screens (an up arrow 
emerging from a folder) than on lowdpi screens (a sheet of paper emerging from 
a folder).
  - The fix should result in the "sheet of paper emerging from a folder" 
icon being used here on both hidpi and lowdpi screens.

  3) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons 
look sutbly different.  The strokes in icons on the hidpi screen will be 
visibly thinner on the hidpi screen because icons for bigger scale are used 
(say 48 on hidpi instead of 24) rather than rendering the original size icon at 
a larger resolution.
  - The fix should result in icons that have the same stroke width on hidpi 
and lowdpi screens.  The icons will still be sharper on the hidpi screen, but 
the lines won't be thinner.
  

  [Regression Potential]

  The patch is designed for compatibility where @2 support is not
  available by listing the @2 directories under "ScaledDirectories="
  rather than "Directories=".  However it's possible there could be
  other kinds of issues not found in testing.  If there are any
  omissions or errors in the index.theme, this could cause rendering
  issues for some categories of icons.  Comparing icons on a broad range
  of applications and systems should catch this class of issues.

  Hidpi users may find that their machine looks different after the
  update than it did before.  This is not a regression, but a fix to a
  bug that's been present all along.

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

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

[Touch-packages] [Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens

Hello David, or anyone else affected,

Accepted humanity-icon-theme into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/humanity-icon-theme/0.6.10.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation 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: humanity-icon-theme (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: humanity-icon-theme (Ubuntu Yakkety)
   Status: New => Fix Committed

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

Title:
  Icons are too big or the wrong icon is shown on hidpi screens

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Committed
Status in humanity-icon-theme source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  Humanity icons are sometimes displayed too big on hidpi screens in
  16.04.  On both 16.04 and 16.10, different icons are used on hidpi
  screens than non-hidpi screens.  Sometimes the icons look similar but
  with much thinner strokes, while other times an icon with a different
  metaphor is used.  Users on hidpi screens will notice that icons in
  applications like Nautilus, Transmission, etc. look different (not
  just clearer) on hidpi screens.

  The fix here is to add support for @2 icons to the Humanity theme by
  adding symbolic links for @2 icons and updating the index.theme files
  accordingly.

  We should backport the fix to 16.04 and 16.10, so Humanity icons look
  the same on hidpi screens as non-hidpi screens.

  
  [Test Case]

  Here are a few test cases: 
  1) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi 
screen are much larger.  (This applies to icons on the desktop as well.)
  -The fix should result in icons being the same size on both hidpi and 
lowdpi.
  
  2) Using a computer with a hidpi screen and one with a lowdpi screen running 
Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the 
toolbar uses an icon with a different metaphor on hidpi screens (an up arrow 
emerging from a folder) than on lowdpi screens (a sheet of paper emerging from 
a folder).
  - The fix should result in the "sheet of paper emerging from a folder" 
icon being used here on both hidpi and lowdpi screens.

  3) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons 
look sutbly different.  The strokes in icons on the hidpi screen will be 
visibly thinner on the hidpi screen because icons for bigger scale are used 
(say 48 on hidpi instead of 24) rather than rendering the original size icon at 
a larger resolution.
  - The fix should result in icons that have the same stroke width on hidpi 
and lowdpi screens.  The icons will still be sharper on the hidpi screen, but 
the lines won't be thinner.
  

  [Regression Potential]

  The patch is designed for compatibility where @2 support is not
  available by listing the @2 directories under "ScaledDirectories="
  rather than "Directories=".  However it's possible there could be
  other kinds of issues not found in testing.  If there are any
  omissions or errors in the index.theme, this could cause rendering
  issues for some categories of icons.  Comparing icons on a broad range
  of applications and systems should catch this class of issues.

  Hidpi users may find that their machine looks different after the
  update than it did before.  This is not a regression, but a fix to a
  bug that's been present all along.

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

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

[Touch-packages] [Bug 1659028] Re: lockscreen does not follow the keyboard layout

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

@fcole90, this is under our QA right now, should hopefully land in the
overlay today.

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

Title:
  lockscreen does not follow the keyboard layout

Status in unity8 package in Ubuntu:
  New

Bug description:
  I have set an Italian keyboard layout in unity8, and it works as
  expected until I lock the screen. I need to prompt my password as if I
  had a US keyboard, so it's probably using the default layout.

  Is there any workaround available until that's solved?

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

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

[Touch-packages] [Bug 1659255] Re: memory leak

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

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

Title:
  memory leak

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Not having looked into what exactly uses it, but after keeping unity8
  running over night, it consumes over 5GB of memory.

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

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

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

2017-01-25 Thread bugproxy

--- Comment From heinz-werner_se...@de.ibm.com 2017-01-25 06:34 EDT---
IBM Bugzilla -> closed

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in glibc source package in Xenial:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in glibc source package in Yakkety:
  Fix Released
Status in util-linux source package in Yakkety:
  Fix Released

Bug description:
  [Testcase]
  * $ LC_ALL=fo_FOO.UTF-8 getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- 
--help
  Expected result:
/usr/sbin/mkinitramfs: unrecognized option '--help'
 --
Exit code 1
  Current result:
Segmentation fault
Exit code 139.

  There are two bugs in play here. glibc bug was fixed, and util-linux
  bug needs an upload still.

  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d ,
  s1@entry=0x2e6575634a500a6a ,
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, argv=0x40,
  optstring=0x20030 , longopts=,
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=,
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=,
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1577460/+subscriptions

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

[Touch-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting

2017-01-25 Thread Xwarman

I just tested it, just by installing the 4.8.0 Kernel in Ubuntu 16.04,
without any workaround and Nvidia drivers enabled. Nothing changed so
far.

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

Title:
Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-
lan setting

Status in Linux:
Unknown
Status in linux package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Triaged

Bug description:
=== Update: This bug was reported from BIOS version F13 of my board,
in the meantime I upgraded to the most recent version F14, but this
had no impact on the bug. ===

Hello,

using Suspend-to-RAM on my system has stopped working reliably on
Vivid when booting with Systemd. When I try to suspend my PC the
following happens:

- PC turns off
- PC unwantedly wakes up (turns on) by itself again. This time span until it
turns on again can reach from a second (almost immediately) until two or three
minutes.
- In a few cases (<25%), the PC stays suspended properly.

A way to workaround this problem is to boot my PC with Upstart instead
of Systemd, then this problem never happens (and has never happened in
any of the previous Ubuntu versions since 2008). Thus it seems to be a
bug somehow related to Systemd.

Other steps I have tried to solve the problem (without any success):

- Checking BIOS settings, all options are set that way that the PC should
never wake up by any event other than pressing the power button.
- Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device
could cause wake up events. This lists my USB controller, but deactivating it
(with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the
problem. Also suspend while running Upstart works fine despite the USB
controller listed as "enabled".

In the system logs I could see no hint what causes the undesired wake-
ups.

Allthough there is one factor which seems to have a certain influence:
If I close programs like Pidgin, Skype or Firefox that cause
continuous network traffic, the chance is higher that my PC will stay
suspened (while runinng Systemd).

Kind regards,
Jan

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 30 11:24:46 2015
InstallationDate: Installed on 2015-04-16 (13 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415)
MachineType: Gigabyte Technology Co., Ltd. P35-DS3
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/10/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F13
dmi.board.name: P35-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-25 Thread Robie Basak

Could someone please look at the autopkgtest regressions in
http://people.canonical.com/~ubuntu-archive/pending-sru.html against
systemd please?

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in maas-images:
  New
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1647485/+subscriptions

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

[Touch-packages] [Bug 1577460] Re: mkinitramfs --help > Core dumped

This bug was fixed in the package util-linux - 2.28.2-1ubuntu1.1

---
util-linux (2.28.2-1ubuntu1.1) yakkety; urgency=medium

  * Cherrypick upstream fix to prevent segfaults in getopt by ensuring
that options array is correctly terminated. LP: #1577460

 -- Dimitri John Ledkov   Fri, 16 Dec 2016 14:27:53
+

** Changed in: util-linux (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in glibc source package in Xenial:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in glibc source package in Yakkety:
  Fix Released
Status in util-linux source package in Yakkety:
  Fix Released

Bug description:
  [Testcase]
  * $ LC_ALL=fo_FOO.UTF-8 getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- 
--help
  Expected result:
/usr/sbin/mkinitramfs: unrecognized option '--help'
 --
Exit code 1
  Current result:
Segmentation fault
Exit code 139.

  There are two bugs in play here. glibc bug was fixed, and util-linux
  bug needs an upload still.

  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d ,
  s1@entry=0x2e6575634a500a6a ,
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, argv=0x40,
  optstring=0x20030 , longopts=,
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=,
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=,
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1577460/+subscriptions

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

[Touch-packages] [Bug 1659255] [NEW] memory leak

Public bug reported:

Not having looked into what exactly uses it, but after keeping unity8
running over night, it consumes over 5GB of memory.

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

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

Title:
  memory leak

Status in unity8 package in Ubuntu:
  New

Bug description:
  Not having looked into what exactly uses it, but after keeping unity8
  running over night, it consumes over 5GB of memory.

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

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

[Touch-packages] [Bug 1637731] Re: [SRU] Update to 2.48.2 in Xenial

This bug was fixed in the package glib2.0 - 2.48.2-0ubuntu1

---
glib2.0 (2.48.2-0ubuntu1) xenial; urgency=medium

  * New upstream release (LP: #1637731)
  * debian/patches/0001-Fix-trashing-on-overlayfs.patch: Update with new
version from the upsstream report to hopefully fix trashing of files in
directories which are symlinks to different devices. (Closes: #800047)
(LP: #1638245)

 -- Iain Lane   Thu, 24 Nov 2016 17:39:06
+

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Update to 2.48.2 in Xenial

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Released

Bug description:
  [Description]
  Upstream have released a new bugfix release 2.48.2.

  [Changes]
  https://git.gnome.org/browse/glib/tree/NEWS?h=glib-2-48

  Bugs fixed:
   547200 g_utf8_find_next_char() issues
   673101 resource compiler dependency generation not working for generated 
files
   700756 GFile.new_for_path arguments misses (type filename) annotation
   725902 build: simplify dtrace configuration
   728207 gsocketservice: Documentation does not mention that is already 
active...
   730187 glocalfileoutputstream: Fix an FD leak in an error path
   746685 Doc: clarify that g_variant_get_data() can be used instead of 
g_varia...
   750257 GSettings changed signal should clearly state the order required
   753231 Memory is potentially used after free
   755439 Memory leak in gdbusproxy.c
   760115 gtestutils: add missing dash in seed argument's --help documentation
   760423 gio-querymodules prints error messages as question marks on some 
locales
   761810 gio: Support using GDBusObjectManagerServer at path ‘/’
   766211 Fix the upper bound in g_unichar_iswide_bsearch
   766899 Superflous HTML/XML comments in GDBusProxyTypeFunc documentation 
string
   766933 GSocketAddress leaks in 
gnetworkmonitornetlink.c:read_netlink_messages()
   767172 docs: Move GIO_USE_VFS to "okay for production" section
   767218 Remove a UTF-8 ellipsis from gsignal.h
   767824 Some UTC timezones incorrectly recognized on Windows 7
   767949 Typos in glib docs
   768453 Gdbus test: compilation fails due to -Werror=format-y2k errors
   768504 keyfile: g_key_file_get_double behavior doesn't follow documentation
   768551 Test failure: test_socket_address_to_string
   768560 gio/tests/gsettings: fix GSettings reference leaks in some tests
   768806 gdbus tool must swallow -- argument
   769027 Docs misleadingly imply G_CHECKSUM_SHA512 is available since 2.16

  Translations updated:
   Indonesian
   Portuguese
   Turkish

  [QA, testing, regression potential]
  Under the GNOME MRE, you can believe all bugs upstream says are fixed are 
really fixed. Just test the system and make sure there are no regressions (e.g. 
look at errors.ubuntu.com).

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

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

[Touch-packages] [Bug 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package