Re: [Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[draco]

Hi Felipe
Have a look to Bug #1577197, I have this problem on switching profile, may
it be the same case.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Yakkety:
  Fix Committed

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

[Michi Henning]

I think we can rule out leveldb. It's at revision 1.18-5 in both xenial
and zesty.

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

[Michi Henning]

Taglib fix is in the linked branch.

The thumbnailer test dumps core on all architectures on zesty. The fault
keeps moving around, looks like a race condition. We are not using
threads ourselves, so the problem likely is in a something we call into.
Candidates would be QT and (unlikely) leveldb.

I've run the tests for several hours continuously on my zesty amd64 VM,
without error. The fault shows up only in the silo.

For added amusement, the qml test for vivid arm64 is segfaulting. I have
no idea what might be causing this. The thumbnailer code has been stable
for many months and hasn't ever had this kind of problem.

I suspect that the issue is with something that is installed on the
builder. But there is no way to get a core dump when something fails in
a builder, so I don't know how to debug this. Without a core dump, we
are stabbing around in the dark :-(

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1046820] Re: touch support seems broken since qt4-x11-4.8.1

[Canmor Lam]

After 4 years, we still got a customer complain about the touch event
unavailable on QT-4.8.x today, could anyone please focus on this issue
and get it fix? Or some one tough me what I can do for this?

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

Title:
  touch support seems broken since qt4-x11-4.8.1

Status in qt4-x11 package in Ubuntu:
  Triaged

Bug description:
  I found that touch examples of QT (under /usr/lib/qt4/examples/touch/)
  works well on Ubuntu 11.10(with qt4-x11-4.7.4) but not on Ubuntu
  12.04(with qt4-x11-4.8.1). On Ubuntu 12.04, touch examples of QT such
  as "dials", "fingerpaint", "knobs" and "pinchzoom" seems cannot get
  any touch event.

  Then I download the source code of qt4-x11 by 'apt-get source' and
  debug it. I found that there may be a mistake in file
  "debian/patches/kubuntu_28_xi2.1.patch". Look at the codes near line
  714:

  702 +QApplicationPrivate::TouchDeviceInfo tdi;
  703 +
  704 +for (int k = 0; k < devices[i].num_classes; ++k) {
  705 +XIAnyClassInfo *xiclassinfo = devices[i].classes[k];
  706 +if (xiclassinfo->type == XITouchClass) {
  ..
  712 +} else if (xiclassinfo->type == XIValuatorClass) {
  713 +XIValuatorClassInfo *v = (XIValuatorClassInfo 
*)xiclassinfo;
  714 +tdi.numValuators++;
  ..
  728 +if (is_touch)
  729 +touchDevices[devices[i].deviceid] = tdi;

  Thease codes is the initialization of `touchDevices', note that `tdi' is 
allocated from stack without any initialization, the initial value of 
`tdi.numValuators' is uncertain. Its value is always a negative number on my 
machine, even after couples of post increase(line 714).
  Trouble comes when program reaches to function 
`QETWidget::translateXI2Event', Look at the codes near line 563:

  562 +double *values = dev->valuators.values;
  563 +for (int i = 0; i < qMin(dev->valuators.mask_len * 8, 
tdi.numValuators); ++i) {
  ..
  617 +}

  As I mentioned earlier, `tdi.numValuators' is always a negative number, 
program *never* will enter this `for' loop. As a result, application cannot get 
any touch properties except tracking ID. That is the trouble.
  I add a initializint statement for `tdi.numValuators':

  702 +QApplicationPrivate::TouchDeviceInfo tdi;
  703 +tdi.numValuators = 0;

  The problem is solved.

  Finally, I try to figure out the different between qt4-x11-4.7.4 and
  qt4-x11-4.8.1. Look this commit http://bazaar.launchpad.net/~kubuntu-
  packagers/kubuntu-packaging/qt/revision/279 :

  @@ -699,17 +682,20 @@
   +for (int i = 0; i < count; ++i) {
   +if (!devices[i].enabled)
   +continue;
  ++
  ++bool is_touch = false;
  ++QApplicationPrivate::TouchDeviceInfo tdi;
  ++
   +for (int k = 0; k < devices[i].num_classes; ++k) {
   +XIAnyClassInfo *xiclassinfo = devices[i].classes[k];
   +if (xiclassinfo->type == XITouchClass) {
  ++is_touch = true;
   +XITouchClassInfo *t = (XITouchClassInfo *)xiclassinfo;
  -+QApplicationPrivate::TouchDeviceInfo& tdi = 
touchDevices[devices[i].deviceid];
   +tdi.deviceid = devices[i].deviceid;
   +tdi.directTouch = t->mode == XIDirectTouch;
   +tdi.maxTouches = t->num_touches;
  -+} else if (xiclassinfo->type == XITouchValuatorClass) {
  -+XITouchValuatorClassInfo *v = (XITouchValuatorClassInfo 
*)xiclassinfo;
  -+QApplicationPrivate::TouchDeviceInfo  = 
touchDevices[devices[i].deviceid];
  ++} else if (xiclassinfo->type == XIValuatorClass) {
  ++XIValuatorClassInfo *v = (XIValuatorClassInfo 
*)xiclassinfo;
   +tdi.numValuators++;
   +if (v->label == ATOM(XAbsMTTouchMajor))
   +copy(tdi.xivTouchMajor, *v);

  In the older version, `tdi' is create by `QHash::operator[]'
  implicitly, which is allocated from heap directly, memory in heep may
  be clear than stack I think. Anyway, adding a default constructor for
  struct TouchDeviceInfo should be a beter solution.

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

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

[Touch-packages] [Bug 1640457] Re: Xorg assert failure: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel: Assertion `bkref' failed.

[Oleksandr Pikozh]

apt-cache policy libdrm-nouveau2
libdrm-nouveau2:
  Installed: 2.4.67-1ubuntu0.16.04.2
  Candidate: 2.4.67-1ubuntu0.16.04.2
  Version table:
 *** 2.4.67-1ubuntu0.16.04.2 500
500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2.4.67-1 500
500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Some other info needed?

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

Title:
  Xorg assert failure: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel:
  Assertion `bkref' failed.

Status in libdrm package in Ubuntu:
  New

Bug description:
  I have three options for my video adapter: nvidia-304 (+ nvidia-
  opencl-icd-304 and nvidia-settings) and xserver-xorg-video-nouveau. If
  I uninstall both of them (I was forced to do that because xserver-
  xorg-video-nouveau doesn't work at all and nvidia-304 doesn't work at
  latest version), system seems to work, but periodically (5 minutes to
  1 hour) XOrg crashes.

  Crashes seem to occur at random points of time (unrelated to my
  actions), but persistently.

  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) apt-cache policy xorg xserver-xorg-core
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  xserver-xorg-core:
Installed: 2:1.18.4-0ubuntu0.1
Candidate: 2:1.18.4-0ubuntu0.1
Version table:
   *** 2:1.18.4-0ubuntu0.1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:1.18.3-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) I expected XOrg to run stably (or not to run at all if some
  critical components are missing).

  4) It crashes every 5min-1hour.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AssertionMessage: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel: Assertion 
`bkref' failed.
  Date: Wed Nov  9 13:20:43 2016
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1473867446
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: /usr/lib/xorg/Xorg -nolisten tcp -auth 
/var/run/sddm/{0f1dcf2c-924d-493a-b72a-0d3865f108e8} -background none -noreset 
-displayfd 17 vt7
  ProcCwd: /
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7fd94a537728 "bkref", 
file=file@entry=0x7fd94a53770a "../../nouveau/pushbuf.c", line=line@entry=238, 
function=function@entry=0x7fd94a537768 "pushbuf_krel") at assert.c:92
   __GI___assert_fail (assertion=0x7fd94a537728 "bkref", file=0x7fd94a53770a 
"../../nouveau/pushbuf.c", line=238, function=0x7fd94a537768 "pushbuf_krel") at 
assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   nouveau_pushbuf_reloc () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
  Title: Xorg assert failure: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel: 
Assertion `bkref' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1521518] Re: No way to invoke OSK when a hardware keyboard is connected

[Dadio]

with a Lenovo Yoga 500, same problem. if the screen is rotated 180°, it
deactivates the hardware keyboard. I can't bring up the software
keyboard.

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

Title:
  No way to invoke OSK when a hardware keyboard is connected

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  Incomplete
Status in ubuntu-keyboard:
  New
Status in Ubuntu UX:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  There are mice on the market that claim to be keyboards as well. This
  inhibits OSK. We can try and find out how many keys they have and be
  smart about it.

  Regardless, we should have a way of forcing the OSK, especially on
  touch-enabled devices. Whether it's triggered by a touch (as opposed
  to mouse click) on the text area, or with a button in the text field
  (replaced with the clear icon when you start typing). Another option
  is the copy/paste dropdown.

  :
  
  The on-screen keyboard should appear if:
  * no external keyboard is connected, and a text field becomes focused; or
  * an external keyboard is connected, but the most recent text typed anywhere 
was with the OSK, and a text field becomes focused; or
  * an external keyboard is connected, and the most recent text typed was with 
an external keyboard, but you tap in the already-focused text field. (App 
developers are responsible for emulating this behavior in typable areas that 
are not text fields.)
  

  == original description ==

  1. Boot nexus 7
  2. In the login screen, test that OSK works by tapping the password textfield
  3. swipe keyboard back down after testing it works
  4. Turn on Bluetooth mouse to get a mouse cursor
  5. Click on password textfield

  OSK doesn't pop up, touch tapping on the field doesn't bring up the
  OSK anymore either.

  ie. The login screen is not usable with mouse connected - cannot type
  in password via OSK since it doesn't come up when clicking the
  password textfield with mouse.

  See attached screenshot. Focus on textfield. Would expect OSK to show
  up.

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

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

[Touch-packages] [Bug 1637032] Re: The screen keeps flashing (even in text terminal mode)

[Poldi]

Given the lack of response I assume I have the only laptop with this problem.
What can I do to get help?
Thanks

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

Title:
  The screen keeps flashing (even in text terminal mode)

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to 16.10 the screen (Desktop and Terminal)flashes
  intermittently making the system unusable.

  I get the same behaviour when booting 16.10 from the LiveCD

  Booting with the 4.4.0 Kernel still works

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Oct 27 11:56:38 2016
  InstallationDate: Installed on 2015-02-15 (619 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-10-24 (2 days ago)
  VarLogDistupgradeAptlog: Error: [Errno 13] Permission denied: 
'/var/log/dist-upgrade/apt.log'
  VarLogDistupgradeMainlog: Error: [Errno 13] Permission denied: 
'/var/log/dist-upgrade/main.log'

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

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

[Touch-packages] [Bug 1640670] Re: Crash in GfxICCBasedColorSpace::parse

[Joel Stanley]

libpoppler61:
  Installed: 0.44.0-3ubuntu2

liblcms2-2:
  Installed: 2.7-1ubuntu1

evince:
  Installed: 3.22.0-0ubuntu1

On Ubuntu 16.10 amd64.

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

Title:
  Crash in GfxICCBasedColorSpace::parse

Status in poppler package in Ubuntu:
  New

Bug description:
  #0  cmsGetColorSpace (hProfile=0x0) at cmsio0.c:934
  #1  0x7f174b47b438 in GfxICCBasedColorSpace::parse(Array*, OutputDev*, 
GfxState*, int) ()
 from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
  #2  0x7f174b47a952 in GfxColorSpace::parse(GfxResources*, Object*, 
OutputDev*, GfxState*, int) ()
 from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
  #3  0x7f174b4a0872 in Page::loadThumb(unsigned char**, int*, int*, int*) 
() from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
  #4  0x7f174bbb7de9 in poppler_page_get_thumbnail () from 
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
  #5  0x7f174bdf5b1b in ?? () from 
/usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so
  #6  0x557297930bb2 in evince_thumbnail_pngenc_get 
(document=0x7f1744003700, 
  thumbnail=0x5572995948c0 "/tmp/.gnome_desktop_thumbnail.ZD13QY", 
size=256) at evince-thumbnailer.c:182
  #7  0x5572979307d0 in main (argc=, argv=) 
at evince-thumbnailer.c:301

  
  getColorSpace, part of lcms, is passed a null pointer.

  GfxICCBasedColorSpace::parse has this sequence of code:

  
if (hp == 0) {
  error(errSyntaxWarning, -1, "read ICCBased color space profile error");
} else {
  cmsHPROFILE dhp = (state != NULL && state->getDisplayProfile() != NULL) ? 
state->getDisplayProfile() : displayProfile;
  if (dhp == NULL) dhp = RGBProfile;
  unsigned int cst = getCMSColorSpaceType(cmsGetColorSpace(hp));
  unsigned int dNChannels = getCMSNChannels(cmsGetColorSpace(dhp));
  unsigned int dcst = getCMSColorSpaceType(cmsGetColorSpace(dhp));

  hp can't be null, or else we wouldn't be calling cmsGetColorSpace.
  This means dhp must be NULL, which can only happen if RGBProfile is
  null.

  RGBProfile is set up in GfxColorSpace::setupColorProfiles(). Assuming
  this function has been called, it does the following:

RGBProfile = loadColorProfile("RGB.icc");
if (RGBProfile == NULL) {
  /* use built in sRGB profile */
  RGBProfile = cmsCreate_sRGBProfile();
}

  cmsCreate_sRGBProfile can return NULL in a number of ways.

  I'm not sure what the fix is though.

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

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

[Touch-packages] [Bug 1640670] [NEW] Crash in GfxICCBasedColorSpace::parse

[Joel Stanley]

Public bug reported:

#0  cmsGetColorSpace (hProfile=0x0) at cmsio0.c:934
#1  0x7f174b47b438 in GfxICCBasedColorSpace::parse(Array*, OutputDev*, 
GfxState*, int) ()
   from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
#2  0x7f174b47a952 in GfxColorSpace::parse(GfxResources*, Object*, 
OutputDev*, GfxState*, int) ()
   from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
#3  0x7f174b4a0872 in Page::loadThumb(unsigned char**, int*, int*, int*) () 
from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
#4  0x7f174bbb7de9 in poppler_page_get_thumbnail () from 
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
#5  0x7f174bdf5b1b in ?? () from 
/usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so
#6  0x557297930bb2 in evince_thumbnail_pngenc_get (document=0x7f1744003700, 
thumbnail=0x5572995948c0 "/tmp/.gnome_desktop_thumbnail.ZD13QY", size=256) 
at evince-thumbnailer.c:182
#7  0x5572979307d0 in main (argc=, argv=) at 
evince-thumbnailer.c:301


getColorSpace, part of lcms, is passed a null pointer.

GfxICCBasedColorSpace::parse has this sequence of code:


  if (hp == 0) {
error(errSyntaxWarning, -1, "read ICCBased color space profile error");
  } else {
cmsHPROFILE dhp = (state != NULL && state->getDisplayProfile() != NULL) ? 
state->getDisplayProfile() : displayProfile;
if (dhp == NULL) dhp = RGBProfile;
unsigned int cst = getCMSColorSpaceType(cmsGetColorSpace(hp));
unsigned int dNChannels = getCMSNChannels(cmsGetColorSpace(dhp));
unsigned int dcst = getCMSColorSpaceType(cmsGetColorSpace(dhp));

hp can't be null, or else we wouldn't be calling cmsGetColorSpace. This
means dhp must be NULL, which can only happen if RGBProfile is null.

RGBProfile is set up in GfxColorSpace::setupColorProfiles(). Assuming
this function has been called, it does the following:

  RGBProfile = loadColorProfile("RGB.icc");
  if (RGBProfile == NULL) {
/* use built in sRGB profile */
RGBProfile = cmsCreate_sRGBProfile();
  }

cmsCreate_sRGBProfile can return NULL in a number of ways.

I'm not sure what the fix is though.

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

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

Title:
  Crash in GfxICCBasedColorSpace::parse

Status in poppler package in Ubuntu:
  New

Bug description:
  #0  cmsGetColorSpace (hProfile=0x0) at cmsio0.c:934
  #1  0x7f174b47b438 in GfxICCBasedColorSpace::parse(Array*, OutputDev*, 
GfxState*, int) ()
 from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
  #2  0x7f174b47a952 in GfxColorSpace::parse(GfxResources*, Object*, 
OutputDev*, GfxState*, int) ()
 from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
  #3  0x7f174b4a0872 in Page::loadThumb(unsigned char**, int*, int*, int*) 
() from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
  #4  0x7f174bbb7de9 in poppler_page_get_thumbnail () from 
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
  #5  0x7f174bdf5b1b in ?? () from 
/usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so
  #6  0x557297930bb2 in evince_thumbnail_pngenc_get 
(document=0x7f1744003700, 
  thumbnail=0x5572995948c0 "/tmp/.gnome_desktop_thumbnail.ZD13QY", 
size=256) at evince-thumbnailer.c:182
  #7  0x5572979307d0 in main (argc=, argv=) 
at evince-thumbnailer.c:301

  
  getColorSpace, part of lcms, is passed a null pointer.

  GfxICCBasedColorSpace::parse has this sequence of code:

  
if (hp == 0) {
  error(errSyntaxWarning, -1, "read ICCBased color space profile error");
} else {
  cmsHPROFILE dhp = (state != NULL && state->getDisplayProfile() != NULL) ? 
state->getDisplayProfile() : displayProfile;
  if (dhp == NULL) dhp = RGBProfile;
  unsigned int cst = getCMSColorSpaceType(cmsGetColorSpace(hp));
  unsigned int dNChannels = getCMSNChannels(cmsGetColorSpace(dhp));
  unsigned int dcst = getCMSColorSpaceType(cmsGetColorSpace(dhp));

  hp can't be null, or else we wouldn't be calling cmsGetColorSpace.
  This means dhp must be NULL, which can only happen if RGBProfile is
  null.

  RGBProfile is set up in GfxColorSpace::setupColorProfiles(). Assuming
  this function has been called, it does the following:

RGBProfile = loadColorProfile("RGB.icc");
if (RGBProfile == NULL) {
  /* use built in sRGB profile */
  RGBProfile = cmsCreate_sRGBProfile();
}

  cmsCreate_sRGBProfile can return NULL in a number of ways.

  I'm not sure what the fix is though.

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

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

[Touch-packages] [Bug 1629055] Re: FTBFS on 32-bit arches (i386, armhf, powerpc)

[Launchpad Bug Tracker]

This bug was fixed in the package heimdal - 1.7~git20160703+dfsg-
1ubuntu1

---
heimdal (1.7~git20160703+dfsg-1ubuntu1) zesty; urgency=medium

  * debian/patches/use_off_t_for_constants.patch: Use off_t in for
constants used in iprop log seeks.  Thanks to Nicolas Williams
.  Closes: #822749, LP: #1629055.

 -- Nishanth Aravamudan   Wed, 09 Nov
2016 17:05:58 -0800

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

Title:
  FTBFS on 32-bit arches (i386, armhf, powerpc)

Status in heimdal package in Ubuntu:
  Fix Released

Bug description:
  e.g., https://launchpadlibrarian.net/282067574/buildlog_ubuntu-
  yakkety-armhf.heimdal_1.7~git20160703+dfsg-1_BUILDING.txt.gz

  FAIL: check-kdc
  FAIL: check-kdc-weak

  in particular are the two testcases that fail.

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

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

[Touch-packages] [Bug 1286751] Re: gst-plugin-scanner hangs, eating CPU time

[LAW YAN KIT]

** Also affects: gstreamer1.0
   Importance: Undecided
   Status: New

** No longer affects: gstreamer1.0

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

Title:
  gst-plugin-scanner hangs, eating CPU time

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  gst-plugin-scanner is eating 100% CPU time which leads to unusable Ubuntu. It 
appears couple of times daily. 
  (My guess is that it is causing by application firefox , skype , totem , 
nautilus ).

  Ubuntu 13.10

  apt-cache policy libgstreamer0.10-0
  libgstreamer0.10-0:
Installed: 0.10.36-1.2ubuntu1
Candidate: 0.10.36-1.2ubuntu1
Version table:
   *** 0.10.36-1.2ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status
   0.10.36-1ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages

  apt-cache policy libgstreamer1.0-0
  libgstreamer1.0-0:
Installed: 1.2.0-1
Candidate: 1.2.0-1
Version table:
   *** 1.2.0-1 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status
   1.0.6-1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages

  dpkg -l gstreamer*plugins* | grep ^ii
  ii  gstreamer0.10-plugins-bad:amd64   0.10.23-7ubuntu2
amd64GStreamer plugins from the "bad" set
  ii  gstreamer0.10-plugins-bad-multiverse  0.10.21-1ubuntu1
amd64GStreamer plugins from the "bad" set 
(Multiverse Variant)
  ii  gstreamer0.10-plugins-base:amd64  0.10.36-1.1ubuntu1  
amd64GStreamer plugins from the "base" set
  ii  gstreamer0.10-plugins-base:i386   0.10.36-1.1ubuntu1  
i386 GStreamer plugins from the "base" set
  ii  gstreamer0.10-plugins-base-apps   0.10.36-1.1ubuntu1  
amd64GStreamer helper programs from the "base" set
  ii  gstreamer0.10-plugins-base-dbg:amd64  0.10.36-1.1ubuntu1  
amd64GStreamer plugins from the "base" set
  ii  gstreamer0.10-plugins-good:amd64  0.10.31-3+nmu1ubuntu3   
amd64GStreamer plugins from the "good" set
  ii  gstreamer0.10-plugins-good:i386   0.10.31-3+nmu1ubuntu3   
i386 GStreamer plugins from the "good" set
  ii  gstreamer0.10-plugins-ugly:amd64  0.10.19-2   
amd64GStreamer plugins from the "ugly" set
  ii  gstreamer1.0-plugins-bad:amd641.2.0-3ubuntu5  
amd64GStreamer plugins from the "bad" set
  ii  gstreamer1.0-plugins-base:amd64   1.2.0-1ubuntu1  
amd64GStreamer plugins from the "base" set
  ii  gstreamer1.0-plugins-base-apps1.2.0-1ubuntu1  
amd64GStreamer helper programs from the "base" set
  ii  gstreamer1.0-plugins-good:amd64   1.2.0-1ubuntu1  
amd64GStreamer plugins from the "good" set
  ii  gstreamer1.0-plugins-ugly:amd64   1.2.0-1 
amd64GStreamer plugins from the "ugly" set


  ls -lA `sudo locate gst-plugin-scanner`
 # -rwxr-xr-x 1 u1   ajbos 6240 Mar 22  2013 
/home/u1/.steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner
 # -rwxr-xr-x 1 u1   ajbos 5544 Mar 22  2013 
/home/u1/.steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner
 # -rwxr-xr-x 1 u1   ajbos 6240 Mar 22  2013 
/home/u1/.steam/ubuntu12_32/steam-runtime.old/amd64/usr/lib/x86_64-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner
 # -rwxr-xr-x 1 u1   ajbos 5544 Mar 22  2013 
/home/u1/.steam/ubuntu12_32/steam-runtime.old/i386/usr/lib/i386-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner
 # -rwxr-xr-x 1 root root  5564 May  7  2013 
/usr/lib/i386-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner
 # -rwxr-xr-x 1 root root  6288 May  7  2013 
/usr/lib/x86_64-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner
 # -rwxr-xr-x 1 root root  6288 Oct  1 21:58 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner

  
  Only help is:
  killall -9 gst-plugin-scanner
  (but it appears again sometimes.)

  
  I have attached:
  gst-inspect-1.0 > ~/gst-inspect-1.0.log
  gst-inspect-0.10 > ~/gst-inspect-0.10.log

  
  Kind Regards,
  Martin

To manage notifications about this bug go to:

[Touch-packages] [Bug 1573296] Re: obsolete conffiles not cleaned up on upgrade

[Luke Yelavich]

I can verify that after upgrading from trusty with pulseaudio pre-
installed, that the indicated files are still present. Once upgrading to
pulseaudio in xenial-proposed, the indicated files are removed and the
init script unregistered.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  Impact:

  When upgrading to xenial from earlier releases, some files are left on
  the user's system. They are not used, but may otherwise be mistaken
  for being used by the user if they are attempting to fix a problem.

  Regression potential:

  Low to none, as the relevant files are not used, and are being removed
  when the updated version of Pulseaudio is installed. These files are
  already removed in yakkety and later.

  Test case:

  When updating from trusty to xenial, one will note the presence of the
  below listed files on the system. Updating from pulseaudio in xenial
  or pulseaudio in trusty to what is in xenial-proposed shoudl delete
  the listed files. The /etc/init.d/pulseaudio script should also be
  unregistered.

  
  Original bug report:

  The following files are marked obsolete after the upgrade to 16.04:

   /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
   /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
   /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
   /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete

  
  Those files should be cleaned up and the sysv init script properly 
deregistered.

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

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

[Touch-packages] [Bug 1629055] Re: FTBFS on 32-bit arches (i386, armhf, powerpc)

[Nish Aravamudan]

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

** Changed in: heimdal (Ubuntu)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

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

Title:
  FTBFS on 32-bit arches (i386, armhf, powerpc)

Status in heimdal package in Ubuntu:
  Fix Committed

Bug description:
  e.g., https://launchpadlibrarian.net/282067574/buildlog_ubuntu-
  yakkety-armhf.heimdal_1.7~git20160703+dfsg-1_BUILDING.txt.gz

  FAIL: check-kdc
  FAIL: check-kdc-weak

  in particular are the two testcases that fail.

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

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

[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

[James Henstridge]

** Branch linked: lp:~michihenning/thumbnailer/zesty-test-suppression

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1639853] Re: Unity8 crash while locking/unlocking with HDMI plugged

[Daniel van Vugt]

I ask because it sounds like you might have rediscovered bug 1489689 or
something like it, which would produce a crash in unity-system-
compositor.log that's easy to identify.

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

Title:
  Unity8 crash while locking/unlocking with HDMI plugged

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Environment:

  current build number: 76
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-11-07 08:03:44
  version version: 76
  version ubuntu: 20161105
  version device: 20161014.0
  version custom: 20161105

  Steps to reproduce:

  1º Connect hdmi 
  2º Lock/unlock device several times

  Current result: locking/unlocking device causes greeter to misbehave
  and finally the ubuntu boot logo appears. Attached some logs and crash
  files, hope it helps

  Expected result: unity8 should not crash

  Add info: time stamp 16:07

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

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

[Touch-packages] [Bug 1238194] Re: keyboard doesn't work to enter password with encrypted partitions ubuntu 13.10 saucy

[DWon]

I have sda5_crypt enabled, replaced new GTX1070 with Nvidia driver.
decrpting password area not allowing to type in anything, even keyboard 
connection is checked.

＃68 works for me

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

Title:
  keyboard doesn't work to enter password with encrypted partitions
  ubuntu 13.10 saucy

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Precise:
  Fix Released
Status in initramfs-tools source package in Saucy:
  Fix Released

Bug description:
  [Justification]
  With the kernel in 13.10, some systems use a different USB host driver than 
previously.  Failing to include this driver in the initramfs causes regressions 
for users who need to interact with the system in early boot using a USB 
keyboard, such as users with an encrypted root filesystem.  Such systems are 
not bootable with this host driver missing.

  [Test case]
  1. On an affected system, reboot to a kernel from 13.04.
  2. Install the initramfs-tools package from -proposed.
  3. Reboot to the kernel from 13.10.
  4. Verify that you are able to type your passphrase at the prompt in the 
initramfs.

  [Regression potential]
  Minimal.  The update-initramfs script will ignore missing modules (such as 
the many other modules in the list which are built-ins), and the only change 
made is to copy the module into the initramfs: it will only be loaded in the 
initramfs if udev determines it's needed, just as it would load it after 
switching to the root filesystem.

  
  Is the same problem as here but in the new ubuntu 13.10 saucy 
https://bugs.launchpad.net/bugs/1066376

  I just can't use (i can install) a encrypted partition because when is
  time to introduce the password to unlock partition keyboard is not
  working.

  I don't know how to edit a bug to report it afects other version of
  ubuntu so i created this new bug...

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

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

[Touch-packages] [Bug 1638929] Re: after disabling a display, enabling makes screens go black

[Daniel van Vugt]

Thanks. The logs show Mir knows about the display getting re-enabled and
the backlight coming back on is the only part that Mir is responsible
for. I think the relevant aspects of Mir are working correctly.

** Changed in: mir
   Status: Incomplete => Invalid

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

Title:
  after disabling a display, enabling makes screens go black

Status in Canonical System Image:
  New
Status in Light Display Manager:
  New
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  turn off then turn on some display (output.used = false then output.used = 
true)

  What happens:
  Turning off works fine, turning it back on does not

  What should happen:
  it should work as expected

  USC log: http://pastebin.ubuntu.com/23420797/
  Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/
  Unity8 log (w debug): http://pastebin.ubuntu.com/23451437/

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

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

[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

[Michi Henning]

I have a fix for the taglib issue that does not require changes to
taglib. (taglib 1.11 added a new API for getting images out of
VorbisComments and broke the behavior (not API) of the existing one.)

Still looking at the other issues.

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1639853] Re: Unity8 crash while locking/unlocking with HDMI plugged

[Daniel van Vugt]

OK,

  1. Please provide a copy (as root) of your 
/var/log/lightdm/unity-system-compositor.log
  2. Please report the crash formally using 'ubuntu-bug 
_usr_bin_unity8.32011.crash' and provide a link to the error report or new bug 
that results.

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

Title:
  Unity8 crash while locking/unlocking with HDMI plugged

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Environment:

  current build number: 76
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-11-07 08:03:44
  version version: 76
  version ubuntu: 20161105
  version device: 20161014.0
  version custom: 20161105

  Steps to reproduce:

  1º Connect hdmi 
  2º Lock/unlock device several times

  Current result: locking/unlocking device causes greeter to misbehave
  and finally the ubuntu boot logo appears. Attached some logs and crash
  files, hope it helps

  Expected result: unity8 should not crash

  Add info: time stamp 16:07

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

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

[Touch-packages] [Bug 1639853] Re: Unity8 crash while locking/unlocking with HDMI plugged

[Daniel van Vugt]

Please copy all of /var/log/lightdm/unity-system-compositor.log*
actually.

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

Title:
  Unity8 crash while locking/unlocking with HDMI plugged

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Environment:

  current build number: 76
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-11-07 08:03:44
  version version: 76
  version ubuntu: 20161105
  version device: 20161014.0
  version custom: 20161105

  Steps to reproduce:

  1º Connect hdmi 
  2º Lock/unlock device several times

  Current result: locking/unlocking device causes greeter to misbehave
  and finally the ubuntu boot logo appears. Attached some logs and crash
  files, hope it helps

  Expected result: unity8 should not crash

  Add info: time stamp 16:07

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

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

[Touch-packages] [Bug 1640443] Re: Spread lags a bit at the start

[Daniel van Vugt]

** Tags added: performance

** Tags added: regression

** Changed in: canonical-devices-system-image
   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/1640443

Title:
  Spread lags a bit at the start

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

Bug description:
  N4 rc-proposed

  Steps to reproduce:
  1. Open a couple of apps
  2. Swipe from the right edge to open the spread. Do this few times with 
varying speeds.

  What happens:
  The spread lags a tiny bit while the apps are being cropped into a square 
shape

  What should happen:
  The spread is smooth and fluid like the previous one.

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

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

[Touch-packages] [Bug 1235337] Fix included in openstack/python-tripleoclient 0.0.10

[OpenStack Infra]

This issue was fixed in the openstack/python-tripleoclient 0.0.10
release.

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

Title:
  signon-ui ships files in a wrong directory

Status in Online Accounts: Sign-on UI:
  Fix Committed
Status in signon-ui package in Ubuntu:
  Fix Committed

Bug description:
  The signon-ui package ships a binary, /usr/libexec/signon-ui/browser-
  process, in a location that is disallowed by the FHS.  This needs to
  be moved to /usr/lib/signon-ui/browser-process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: signon-ui 0.15+13.10.20131003.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  4 08:57:30 2013
  InstallationDate: Installed on 2010-09-24 (1106 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MarkForUpload: True
  SourcePackage: signon-ui
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (150 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/signon-ui/+bug/1235337/+subscriptions

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

[Touch-packages] [Bug 1241668] Fix included in openstack/python-tripleoclient 0.0.10

[OpenStack Infra]

This issue was fixed in the openstack/python-tripleoclient 0.0.10
release.

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

Title:
  gdb embeds python3.3, but support scripts are not compatible

Status in Python:
  Fix Released
Status in gdb package in Ubuntu:
  Invalid
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.3 package in Ubuntu:
  Fix Released
Status in gdb source package in Saucy:
  Invalid
Status in python2.7 source package in Saucy:
  Won't Fix
Status in python3.3 source package in Saucy:
  Won't Fix

Bug description:
  The saucy gdb appears to be linked against libpython3.3.

  This results in a conflict when trying to debug python2.7 programs,
  which use the python2.7-dbg.py scripts from python2.7-dbg.  This makes
  debugging Python programs difficult.

  
File "/usr/lib/debug/usr/bin/python2.7-gdb.py", line 54
  Py_TPFLAGS_HEAPTYPE = (1L << 9)
  ^
  SyntaxError: invalid syntax
File "/usr/lib/debug/usr/bin/python2.7-gdb.py", line 54
  Py_TPFLAGS_HEAPTYPE = (1L << 9)

  There are also invalid print statements that show up as well.

  If these are updated, then the file parses, but `py-bt` fails with:

  Error occurred in Python command: global name 'long' is not defined

  Updating all of the long() references to int() doesn't work:

  Error occurred in Python command: 'gdb.Value' object cannot be
  interpreted as an integer

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

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

[Touch-packages] [Bug 1629055] Re: FTBFS on 32-bit arches (i386, armhf, powerpc)

[Nish Aravamudan]

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822749

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

** Changed in: heimdal (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: heimdal (Ubuntu)
   Status: Confirmed => In Progress

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

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

Title:
  FTBFS on 32-bit arches (i386, armhf, powerpc)

Status in heimdal package in Ubuntu:
  In Progress

Bug description:
  e.g., https://launchpadlibrarian.net/282067574/buildlog_ubuntu-
  yakkety-armhf.heimdal_1.7~git20160703+dfsg-1_BUILDING.txt.gz

  FAIL: check-kdc
  FAIL: check-kdc-weak

  in particular are the two testcases that fail.

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

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

[Touch-packages] [Bug 1640457] Re: Xorg assert failure: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel: Assertion `bkref' failed.

[Daniel van Vugt]

The crash is occurring in libdrm_nouveau.so.2 which comes from source
package `libdrm'. So it seems to be just a nouveau driver crash and not
a general Xorg issue.

** Information type changed from Private to Public

** Package changed: xorg-server (Ubuntu) => libdrm (Ubuntu)

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

Title:
  Xorg assert failure: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel:
  Assertion `bkref' failed.

Status in libdrm package in Ubuntu:
  New

Bug description:
  I have three options for my video adapter: nvidia-304 (+ nvidia-
  opencl-icd-304 and nvidia-settings) and xserver-xorg-video-nouveau. If
  I uninstall both of them (I was forced to do that because xserver-
  xorg-video-nouveau doesn't work at all and nvidia-304 doesn't work at
  latest version), system seems to work, but periodically (5 minutes to
  1 hour) XOrg crashes.

  Crashes seem to occur at random points of time (unrelated to my
  actions), but persistently.

  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) apt-cache policy xorg xserver-xorg-core
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  xserver-xorg-core:
Installed: 2:1.18.4-0ubuntu0.1
Candidate: 2:1.18.4-0ubuntu0.1
Version table:
   *** 2:1.18.4-0ubuntu0.1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:1.18.3-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) I expected XOrg to run stably (or not to run at all if some
  critical components are missing).

  4) It crashes every 5min-1hour.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AssertionMessage: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel: Assertion 
`bkref' failed.
  Date: Wed Nov  9 13:20:43 2016
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1473867446
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: /usr/lib/xorg/Xorg -nolisten tcp -auth 
/var/run/sddm/{0f1dcf2c-924d-493a-b72a-0d3865f108e8} -background none -noreset 
-displayfd 17 vt7
  ProcCwd: /
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7fd94a537728 "bkref", 
file=file@entry=0x7fd94a53770a "../../nouveau/pushbuf.c", line=line@entry=238, 
function=function@entry=0x7fd94a537768 "pushbuf_krel") at assert.c:92
   __GI___assert_fail (assertion=0x7fd94a537728 "bkref", file=0x7fd94a53770a 
"../../nouveau/pushbuf.c", line=238, function=0x7fd94a537768 "pushbuf_krel") at 
assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   nouveau_pushbuf_reloc () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
  Title: Xorg assert failure: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel: 
Assertion `bkref' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1640299] Re: Nvidia Quadro FX5600

[Daniel van Vugt]

Response via email:

On Nvidia  Quadro FX5600

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

Title:
  Nvidia Quadro FX5600

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  No Display or Bad Quality

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Nov  8 21:43:17 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-22-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4250] [1002:9715] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. M5A88-V EVO [1043:843e]
   NVIDIA Corporation G80GL [Quadro FX 5600] [10de:019d] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G80GL [Quadro FX 5600] [10de:0409]
  InstallationDate: Installed on 2016-11-07 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=6b81fad4-813f-41e1-aeb9-db6be080c430 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88TD-V EVO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd05/11/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-VEVO/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Tue Nov  8 21:27:55 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1640299] Re: Nvidia Quadro FX5600

[Daniel van Vugt]

OK, can you please provide a photo of the problem and a more detailed
description of what is "bad quality"?

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

Title:
  Nvidia Quadro FX5600

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  No Display or Bad Quality

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Nov  8 21:43:17 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-22-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4250] [1002:9715] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. M5A88-V EVO [1043:843e]
   NVIDIA Corporation G80GL [Quadro FX 5600] [10de:019d] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G80GL [Quadro FX 5600] [10de:0409]
  InstallationDate: Installed on 2016-11-07 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=6b81fad4-813f-41e1-aeb9-db6be080c430 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88TD-V EVO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd05/11/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-VEVO/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Tue Nov  8 21:27:55 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1640457] [NEW] Xorg assert failure: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel: Assertion `bkref' failed.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have three options for my video adapter: nvidia-304 (+ nvidia-opencl-
icd-304 and nvidia-settings) and xserver-xorg-video-nouveau. If I
uninstall both of them (I was forced to do that because xserver-xorg-
video-nouveau doesn't work at all and nvidia-304 doesn't work at latest
version), system seems to work, but periodically (5 minutes to 1 hour)
XOrg crashes.

Crashes seem to occur at random points of time (unrelated to my
actions), but persistently.

1) lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

2) apt-cache policy xorg xserver-xorg-core
xorg:
  Installed: 1:7.7+13ubuntu3
  Candidate: 1:7.7+13ubuntu3
  Version table:
 *** 1:7.7+13ubuntu3 500
500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
xserver-xorg-core:
  Installed: 2:1.18.4-0ubuntu0.1
  Candidate: 2:1.18.4-0ubuntu0.1
  Version table:
 *** 2:1.18.4-0ubuntu0.1 500
500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2:1.18.3-1ubuntu2 500
500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

3) I expected XOrg to run stably (or not to run at all if some critical
components are missing).

4) It crashes every 5min-1hour.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.18.4-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AssertionMessage: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel: Assertion 
`bkref' failed.
Date: Wed Nov  9 13:20:43 2016
ExecutablePath: /usr/lib/xorg/Xorg
ExecutableTimestamp: 1473867446
InstallationDate: Installed on 2015-11-10 (364 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
ProcCmdline: /usr/lib/xorg/Xorg -nolisten tcp -auth 
/var/run/sddm/{0f1dcf2c-924d-493a-b72a-0d3865f108e8} -background none -noreset 
-displayfd 17 vt7
ProcCwd: /
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7fd94a537728 "bkref", 
file=file@entry=0x7fd94a53770a "../../nouveau/pushbuf.c", line=line@entry=238, 
function=function@entry=0x7fd94a537768 "pushbuf_krel") at assert.c:92
 __GI___assert_fail (assertion=0x7fd94a537728 "bkref", file=0x7fd94a53770a 
"../../nouveau/pushbuf.c", line=238, function=0x7fd94a537768 "pushbuf_krel") at 
assert.c:101
 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 nouveau_pushbuf_reloc () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
Title: Xorg assert failure: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel: 
Assertion `bkref' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: libdrm (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash xenial
-- 
Xorg assert failure: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel: Assertion 
`bkref' failed.
https://bugs.launchpad.net/bugs/1640457
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to libdrm in Ubuntu.

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

[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

[Michi Henning]

Taglib 1.11 has broken extraction of VorbisComments.

I've opened a bug here: https://github.com/taglib/taglib/issues/770

Looking at the taglib source now to see whether there is an easy fix.

** Changed in: thumbnailer (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

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

** Changed in: thumbnailer (Ubuntu)
   Importance: High => Critical

** Bug watch added: github.com/taglib/taglib/issues #770
   https://github.com/taglib/taglib/issues/770

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1407644] Re: eog doesn't show WebP images

[hackel]

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

** This bug has been marked a duplicate of bug 1318327
   Can't open .webp files

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

Title:
  eog doesn't show WebP images

Status in libwebp:
  Unknown
Status in libwebp package in Ubuntu:
  Confirmed

Bug description:
  eog doesn't show WebP images

  i get this error message while trying to view WebP images

  Could not load image '2_webp_a.webp'.
  Unrecognized image file format

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

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

[Touch-packages] [Bug 605300] Re: ureadahead man page does not include exit status

[Rich McAllister]

** Tags added: manpage

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

Title:
  ureadahead man page does not include exit status

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: ureadahead

  The man page for ureadahead does not include exit status. It should be
  unnecessary to browse internet forums to find out what exit status 5
  means (or 4 for that sake).

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: ureadahead 0.100.0-5
  ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4
  Uname: Linux 2.6.35-7-generic i686
  Architecture: i386
  Date: Wed Jul 14 09:07:50 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100630.2)
  PackDump: Error: command ['ureadahead', '--dump'] failed with exit code 4: 
ureadahead:/var/lib/ureadahead/pack: Permission denied
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: ureadahead

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

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

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

[John Morton]

Separating out u-u from the rest of the apt maintenance script could be
useful, but I prefer running the update, package fetch, upgrade then
cache clean up all in one hit. You *can* delay your reboot time, but the
shutdown command, at least pre-systemd would run until the shutdown
happens, periodically issuing a message to all terminal users before
stopping further logins and finally changing the runlevel to reboot the
machine. Less than ideal in the old cron.daily days, as those jobs run
sequentially and in lexical order. And a is for apt.

In the mixed jessie, trusty, xenial environment we run, we've moved to
taking the apt job out of cron.daily entirely, running the reboot 'now',
and using the cron/timer start time to effectively schedule the reboot.

My grievance is mainly that in making the transition to systemd the
upstream developers chose to:

1) Significantly change the job start time behaviour
2) Not bother to mention this behaviour change in the the changelog

It would be good to see Ubuntu at least set the timer defaults in such a
way that enabling unattended upgrades doesn't result in nasty reboot
during the day default behaviour. Which, given the half hour random
start time default, should be achievable without putting undue load on
the servers.

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Triaged

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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

[Touch-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe

[System76]

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

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

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

Title:
  xenial: invalid opcode when using llvmpipe

Status in OEM Priority Project:
  Fix Released
Status in System76:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in llvm-toolchain-3.8 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Invalid

Bug description:
  [Description updated to reflect state of 16.04 release ISO]

  == In summary ==

  If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
  possibly other GPUs that likewise require use of the llvmpipe opengl
  software fallback), a work-around is needed to install Ubuntu 16.04
  desktop.

  To work-around this, you'll need to:

  1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try
  Ubuntu without installing")

  2) Check "Download updates while installing Ubuntu"

  ** Note: "Download updates while installing Ubuntu" doesn't currently
  seem to be working. If after installing 16.04 on effected Skylake
  hardware you find that Unity/Compiz is broken, switch to a VT with
  Control+Alt+F1, login, and then run:

  sudo apt-get update
  sudo apt-get dist-upgrade

  You should see the `libllvm3.8` package get updated. After a reboot,
  Unity/Compiz should be working.

  == In detail ==

  The Ubuntu 16.04 desktop ISOs include libllvm3.8 1:3.8-2ubuntu1, which
  has a bug that results in invalid JIT code generation when using the
  mesa llvmpipe opengl software fallback on Skylake CPUs.

  When you encounter this bug, Unity/Compiz will fail to start, and
  you'll see something like this in dmesg:

  [ 2092.557913] traps: compiz[10155] trap invalid opcode
  ip:7efc940030d4 sp:7ffccd914ea0 error:0

  libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make
  it onto the 16.04 release ISOs. It will be included on the 16.04.1
  ISOs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions

-- 
Mailing list: https://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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Felipe Lemos]

OK, so maybe I'm experiencing another bug.
The PPA did in fact fixed my problem (profile switching) when I was using
16.04, and I was hoping your proposed package could fixed it for me in
16.10.
I was having a impression that was the same problem, but apparently it is
not.

On Wed, 9 Nov 2016, 20:54 Luke Yelavich, 
wrote:

> The proposed package does *NOT* fix any bugs relating to profile
> switching.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1574324
>
> Title:
>   pulseaudio crashes when connecting to bluetooth headphones (due to
>   ubuntu changes?)
>
> Status in pulseaudio package in Ubuntu:
>   In Progress
> Status in pulseaudio source package in Xenial:
>   Fix Committed
> Status in pulseaudio source package in Yakkety:
>   Fix Committed
>
> Bug description:
>   Impact:
>
>   A patch we carry for Ubuntu touch introduced a change that originally
>   was required to make sure PulseAudio did not crash. This patch was
>   ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
>   hardware that was to hand at the time worked so was assumed to be ok.
>   However, the opposite is now happening, i.e PulseAudio is crashing
>   with a subset of Bluetooth hardware.
>
>   Regression potential:
>
>   Very low to none. As can be read in this report, much debugging and
>   testing has been done to find the problem, and the eventual fix.
>   Moreover the change is the removal of a patch hunk that removed a line
>   of code originally present in PulseAudio.
>
>   Test case:
>
>   NOTE that this test case applies to bluetooth hardware that is
>   identified as not working in this bug report.
>
>   1. Install, or upgrade to Xenial or yakkety.
>   2. Pair your bluetooth device in the bluetooth settings in the relevant
> settings application for your desktop environment.
>   3. Once paired, you will notice that sound stops working, as pulseaudio
> has thrown an assertion error.
>   4. You do not have to remove your audio device from the paired device
> list, but it may be easier to do so for the next part of the testing.
>   5. Update to the version of PulseAudio in xenial-proposed which is
> 1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
>   6. Re-pair your device. Audio should continue to work, and you should be
> able to switch to your bluetooth device and use it.
>
>
>   Original bug report:
>
>   When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
>   pulseaudio crashes, this does *NOT* happen with a Jambox which leads
>   me to believe it's an intermittent problem with some hardware. This
>   did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).
>
>   Ubuntu Release:
>
>   Description:  Ubuntu 16.04 LTS
>   Release:  16.04
>
>   Pulseaudio Version:
>
>   pulseaudio:
> Installed: 1:8.0-0ubuntu3
> Candidate: 1:8.0-0ubuntu3
> Version table:
>*** 1:8.0-0ubuntu3 500
>   500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
> Packages
>   100 /var/lib/dpkg/status
>
>   Device info:
>
>   [bluetooth]# info 44:5E:F3:B4:07:29
>   Device 44:5E:F3:B4:07:29
>Name: BlueBuds X
>Alias: BlueBuds X
>Class: 0x240404
>Icon: audio-card
>Paired: yes
>Trusted: yes
>Blocked: no
>Connected: no
>LegacyPairing: no
>UUID: Headset   (1108--1000-8000-00805f9b34fb)
>UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
>UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
>UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
>UUID: Handsfree (111e--1000-8000-00805f9b34fb)
>UUID: Unknown   (80ff--1000-8000-00805f9b34fb)
>
>   I have also attached a debug dump of Pulseaudio when attempting to
>   connect to the headphones.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions
>

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Yakkety:
  Fix Committed

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to 

Re: [Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Luke Yelavich]

The proposed package does *NOT* fix any bugs relating to profile
switching.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Yakkety:
  Fix Committed

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 1631328] Re: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"

[Martin Pitt]

Hello Ryan, or anyone else affected,

Accepted ceph into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ceph/10.2.3-0ubuntu2.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!

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

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

** No longer affects: systemd (Ubuntu)

** No longer affects: systemd (Ubuntu Yakkety)

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

** Tags added: verification-needed

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

Title:
  ceph-osd stays blocked on Yakkety: "No block devices detected using
  current configuration"

Status in ceph package in Ubuntu:
  Fix Released
Status in ceph source package in Yakkety:
  Fix Committed
Status in ceph-osd package in Juju Charms Collection:
  Invalid

Bug description:
  The "ceph/default," "ceph_radosgw/simple_nonha" and "ceph/harden" mojo
  specs @ Yakkety are failing like so:

  Units are consistently blocked in Juju status:
  ceph-osd stays blocked on Yakkety: "No block devices detected using current 
configuration"

  Snippets from ceph-osd unit syslog:
  mkjournal error creating journal on /var/lib/ceph/tmp/mnt.W59Jhd/journal: 
(13) Permission denied

  Oct  7 03:13:30 juju-osci-sv13-machine-4 systemd[1]: Failed to start
  Ceph disk activation: /dev/vdb1.

  See:

  http://pastebin.ubuntu.com/23288515/

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

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

[Touch-packages] [Bug 1590321] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:get_dpkg_log_content

[Martin Pitt]

Hello errors.ubuntu.com, or anyone else affected,

Accepted unattended-upgrades into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.92ubuntu1.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: unattended-upgrades (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-
  upgrade@1468:main:get_dpkg_log_content

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in unattended-upgrades source package in Yakkety:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  Fix Released

Bug description:
  Test Case
  -
  1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 
and Unattended-Upgrade is 1
  2) sudo apt-get update
  3) sudo /usr/bin/unattended-upgrades (to update the system)
  4) sudo /usr/bin/unattended-upgrades (a second time for some reason)
  5) sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  6) sudo /usr/bin/unattended-upgrades

  Observe the following crash:

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1468, in 
  main(options)
    File "/usr/bin/unattended-upgrade", line 1406, in main
  log_content = get_dpkg_log_content(logfile_dpkg, install_start_time)
    File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content
  with io.open(logfile_dpkg, encoding='utf-8') as fp:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'

  With the version of the package from -proposed you won't receive the
  crash in step 6 and /var/log/unattended-upgrades/unattended-upgrades-
  dpkg.log will exist.

  Regression Potential
  
  This patch just ends up creating a file if it does not exist. Potential 
regressions would be a result of the patch being typo'ed e.g. typo'ing 
os.path.exits instead of os.path.exists and the code failing when a logfile 
does exist. So read the patch carefully!

  
  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with version 0.90, 
the problem page at 
https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a 
contains more details.

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

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

[Touch-packages] [Bug 1624641] Re: security updates with a new dependency don't get installed

[Martin Pitt]

Hello Jarno, or anyone else affected,

Accepted unattended-upgrades into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.92ubuntu1.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: unattended-upgrades (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  security updates with a new dependency don't get installed

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Yakkety:
  Fix Committed

Bug description:
  Test Case
  -
  1) Boot a xenial system w/o chromium browser and w/o libspeechd2 installed
  2) Install the release version of chromium browser e.g. "sudo apt-get install 
chromium-browser=49.0.2623.108-0ubuntu1.1233 
chromium-browser-l10n=49.0.2623.108-0ubuntu1.1233 
chromium-codecs-ffmpeg-extra=49.0.2623.108-0ubuntu1.1233"
  3) Run apt-get update if you didn't already
  4) Run "sudo /usr/bin/unattended-upgrades -v -d"
  5) Observe the following output "Checking: chromium-browser ([, ])
  pkg 'libspeechd2' not in allowed origin
  sanity check failed"

  With the version of unattended-upgrades from -proposed libspeechd2
  should be from an allowed origin and chromium-browser will get
  updated.

  Regression Potential
  
  This change modifies the behavior of unattended-upgrades such that new 
packages will be installed on a user's system and they may not except such 
behavior (e.g. why was libspeechd2 insalled?).  However, this seems better than 
not installing security updates and leaving people's systems vulnerable to 
attack.

  Original Description
  
  E.g. chromium-browser has an update, but U-U does not update it. I saw in 
update-manager that the security update is available before running U-U. 
Afterwards I can install the update by update-manager.

  ProblemType: BugDistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:13:40 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: allSourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1639977] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file

[Martin Pitt]

Hello errors.ubuntu.com, or anyone else affected,

Accepted unattended-upgrades into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.92ubuntu1.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: unattended-upgrades (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-
  upgrade@1468:main:write_stamp_file

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in unattended-upgrades source package in Yakkety:
  Fix Committed

Bug description:
  Test Case
  -
  1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 
and Unattended-Upgrade is 1
  2) sudo apt-get update
  3) sudo rm -fr /var/lib/apt/periodic
  4) sudo /usr/bin/unattended-upgrade
  5) observe the following Traceback

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1468, in 
  main(options)
    File "/usr/bin/unattended-upgrade", line 1419, in main
  write_stamp_file()
    File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file
  with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"):
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/lib/apt/periodic/unattended-upgrades-stamp'

  With the version of the package from -proposed you'll receive no such
  Traceback.

  Regression Potential
  
  This patch just ends up creating a directory if it does not exist.  Potential 
regressions would be a result of the patch being typo'ed e.g. typo'ing 
os.path.exits instead of os.path.exists and the code failing when a statedir 
does exist.  So read the patch carefully!

  Original description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.90ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1632620] Update Released

[Martin Pitt]

The verification of the Stable Release Update for webbrowser-app has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  No audio from webbrowser-app in 16.10

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in apparmor-easyprof-ubuntu source package in Yakkety:
  Confirmed
Status in webbrowser-app source package in Yakkety:
  Fix Released

Bug description:
  [Test case]
  Load the browser on 16.10 in either a U8 or U7 session.
  Browse to YouTube.
  Play a video.
  Notice there is no sound. Nor does the browser show in the sound menu/panel.

  TLDR: this is an apparmor confinement issue: on yakkety pulse audio
  needs write access to /{run,dev}/shm/pulse-shm*, which is being denied
  by the audio and microphone policy groups. The fix consists in
  punching an additional hole in the generated apparmor profile for
  webbrowser-app.

  [Regression potential]
  Low. As the fix consists in weakening the apparmor profile for 
webbrowser-app, the only concerns should be security-related. The change was 
ack’d by Jamie Strandboge (see comment #11 in this bug report).
  It is not anticipated that this change would make the browser’s functionality 
regress.

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

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

[Touch-packages] [Bug 1633439] Update Released

[Martin Pitt]

The verification of the Stable Release Update for webbrowser-app has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  FTBFS on yakkety arm64: Invalid chromium version: ''

Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Yakkety:
  Fix Released

Bug description:
  This error appears to be 100% reproducible on arm64 builds targetting
  yakkety (see e.g. https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/2076/+build/11022370):

  dh build-arch --parallel --with translations
     dh_testdir -a -O--parallel
     dh_update_autotools_config -a -O--parallel
     dh_auto_configure -a -O--parallel
   cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
  -- The C compiler identification is GNU 6.2.0
  -- The CXX compiler identification is GNU 6.2.0
  -- Check for working C compiler: /usr/bin/aarch64-linux-gnu-gcc
  -- Check for working C compiler: /usr/bin/aarch64-linux-gnu-gcc -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Check for working CXX compiler: /usr/bin/aarch64-linux-gnu-g++
  -- Check for working CXX compiler: /usr/bin/aarch64-linux-gnu-g++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Could NOT find Lcov (missing:  LCOV_EXECUTABLE GENHTML_EXECUTABLE)
  -- Could NOT find gcovr (missing:  GCOVR_EXECUTABLE)
  CMake Error at src/Ubuntu/CMakeLists.txt:31 (message):
    Invalid chromium version: ''

  It is fixed in webbrowser-app in zesty (original bug report: bug
  #1599695), the fix needs to be backported to yakkety.

  Running qmlscene inside xvfb at build time to determine the chromium
  version oxide is built upon proved to be unreliable, the patch
  attached dynamically replaces the chromium version at runtime instead.

  [Regression potential]
  Need to verify that the chromium version advertised in user agent overrides 
is still correct. This can be done by browsing to a site for which a UA 
override is defined (e.g. https://www.youtube.com/ on desktop) and observing 
the User-Agent HTTP header of the request (using e.g. wireshark).

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

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

[Touch-packages] [Bug 1632620] Re: No audio from webbrowser-app in 16.10

[Launchpad Bug Tracker]

This bug was fixed in the package webbrowser-app -
0.23+16.10.20161018-0ubuntu1

---
webbrowser-app (0.23+16.10.20161018-0ubuntu1) yakkety; urgency=medium

  * Fix FTBFS on yakkety arm64 and work around a limitation in the sound
and microphone policy groups. (LP: #1632620, #1633439)

 -- Olivier Tilloy   Tue, 18 Oct 2016
07:07:56 +

** Changed in: webbrowser-app (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 apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1632620

Title:
  No audio from webbrowser-app in 16.10

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in apparmor-easyprof-ubuntu source package in Yakkety:
  Confirmed
Status in webbrowser-app source package in Yakkety:
  Fix Released

Bug description:
  [Test case]
  Load the browser on 16.10 in either a U8 or U7 session.
  Browse to YouTube.
  Play a video.
  Notice there is no sound. Nor does the browser show in the sound menu/panel.

  TLDR: this is an apparmor confinement issue: on yakkety pulse audio
  needs write access to /{run,dev}/shm/pulse-shm*, which is being denied
  by the audio and microphone policy groups. The fix consists in
  punching an additional hole in the generated apparmor profile for
  webbrowser-app.

  [Regression potential]
  Low. As the fix consists in weakening the apparmor profile for 
webbrowser-app, the only concerns should be security-related. The change was 
ack’d by Jamie Strandboge (see comment #11 in this bug report).
  It is not anticipated that this change would make the browser’s functionality 
regress.

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

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

[Touch-packages] [Bug 1633439] Re: FTBFS on yakkety arm64: Invalid chromium version: ''

[Launchpad Bug Tracker]

This bug was fixed in the package webbrowser-app -
0.23+16.10.20161018-0ubuntu1

---
webbrowser-app (0.23+16.10.20161018-0ubuntu1) yakkety; urgency=medium

  * Fix FTBFS on yakkety arm64 and work around a limitation in the sound
and microphone policy groups. (LP: #1632620, #1633439)

 -- Olivier Tilloy   Tue, 18 Oct 2016
07:07:56 +

** Changed in: webbrowser-app (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 webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1633439

Title:
  FTBFS on yakkety arm64: Invalid chromium version: ''

Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Yakkety:
  Fix Released

Bug description:
  This error appears to be 100% reproducible on arm64 builds targetting
  yakkety (see e.g. https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/2076/+build/11022370):

  dh build-arch --parallel --with translations
     dh_testdir -a -O--parallel
     dh_update_autotools_config -a -O--parallel
     dh_auto_configure -a -O--parallel
   cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
  -- The C compiler identification is GNU 6.2.0
  -- The CXX compiler identification is GNU 6.2.0
  -- Check for working C compiler: /usr/bin/aarch64-linux-gnu-gcc
  -- Check for working C compiler: /usr/bin/aarch64-linux-gnu-gcc -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Check for working CXX compiler: /usr/bin/aarch64-linux-gnu-g++
  -- Check for working CXX compiler: /usr/bin/aarch64-linux-gnu-g++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Could NOT find Lcov (missing:  LCOV_EXECUTABLE GENHTML_EXECUTABLE)
  -- Could NOT find gcovr (missing:  GCOVR_EXECUTABLE)
  CMake Error at src/Ubuntu/CMakeLists.txt:31 (message):
    Invalid chromium version: ''

  It is fixed in webbrowser-app in zesty (original bug report: bug
  #1599695), the fix needs to be backported to yakkety.

  Running qmlscene inside xvfb at build time to determine the chromium
  version oxide is built upon proved to be unreliable, the patch
  attached dynamically replaces the chromium version at runtime instead.

  [Regression potential]
  Need to verify that the chromium version advertised in user agent overrides 
is still correct. This can be done by browsing to a site for which a UA 
override is defined (e.g. https://www.youtube.com/ on desktop) and observing 
the User-Agent HTTP header of the request (using e.g. wireshark).

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

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

[Touch-packages] [Bug 1303769] Re: xubuntu 14.04 service start, stop, does not work in terminal emulation

[David Coronel]

I just hit this bug with a fresh install of Ubuntu 14.04.4 Desktop.

Inside Unity, I open a terminal and if I do "service ssh status" I get:
status: Unknown job: ssh

But if I ssh to that box with the same user, the same command works
fine.

The workarounds are to do "sudo service ssh status" or to do "unset
UPSTART_SESSION" before doing "service ssh status".

Can anyone look at this?

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

Title:
  xubuntu 14.04 service start,stop, does not work in terminal emulation

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  xubuntu from installer-amd64/20101020ubuntu313 terminal emulation can
  not change service status.

  e.g.

  > service smbd restart
  stop: Unknown job: smbd
  start: Unknown job: smbd


  however on tty1 this works as expected. i.e. the smbd is stopped then
  started again with a process number given in output.

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

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

[Touch-packages] [Bug 1639000] Re: New upstream release 0.4.13

[Launchpad Bug Tracker]

This bug was fixed in the package libproxy - 0.4.13-0ubuntu1

---
libproxy (0.4.13-0ubuntu1) zesty; urgency=medium

  [ FJKong ]
  * New upstream release (LP: #1639000)
  * Remove 3 Patches because of merging to upsteam:
- dont_segfault_on_exit.patch
- fix-mozjs-detection.patch
- 0001-pacrunner_webkit-allow-linking-against-javascriptcor.patch

  [ Iain Lane ]
  * Use @PACKAGE@ consistently in debian/watch
  * debian/rules: Bump SHLIBVER

 -- FJKong   Wed, 09 Nov 2016 17:27:25 +

** Changed in: libproxy (Ubuntu)
   Status: New => Fix Released

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

Title:
  New upstream release 0.4.13

Status in libproxy package in Ubuntu:
  Fix Released

Bug description:
  New in Version 0.4.13
  ==
  * Allow linking webkit pacrunner against javascriptcore-4.0
(webkit2).
  * Allow to disable building of the KDE module (-DWITH_KDE=ON/OFF).
  * Fix compilation errors with CLang on MacOSX.
  * bindings: perl: Add an option to explicitly link against libperl.so
Some distributions want to do it, other prefer not to, the library
is anyway in context of perl.
  * config_kde: Add a basic cache and invalidation: performance improvement
for the KDE module.

  New in version 0.4.12
  ==
  * Move development to github.com/libproxy/libproxy
  * Fix fd leak in get_pac (Bug #185)
  * Detect running MATE session (Bug #186, Part1).
  * Fix linking of perl bindings to pthread (Bug #182)
  * Correctly detect spidermonky (mozjs185) (Bug #188)
  * Stop pxgsettings from segfaulting on exit (Bug #192)
  * Fix test #10 (Bug #189)
  * Fix build on Mac OS X (Bug #183)
  * Add a generic KDE Config module (fix crashes of Qt5 based
  apps) (issue#4)

  We should get this in zesty

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

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

[Touch-packages] [Bug 1303769] Re: xubuntu 14.04 service start, stop, does not work in terminal emulation

[David Coronel]

** Changed in: upstart (Ubuntu)
 Assignee: Ahmad Bin Musa (ahmadbinmusa) => (unassigned)

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

Title:
  xubuntu 14.04 service start,stop, does not work in terminal emulation

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  xubuntu from installer-amd64/20101020ubuntu313 terminal emulation can
  not change service status.

  e.g.

  > service smbd restart
  stop: Unknown job: smbd
  start: Unknown job: smbd


  however on tty1 this works as expected. i.e. the smbd is stopped then
  started again with a process number given in output.

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

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

[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

[Tessa]

When I look at it with apport-retrace -g, it reports the following:

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `avahi-daemon: running [lap'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
58  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.

Not sure if that's valid.

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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

[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

[Tessa]

Recent crash file for avahi-daemon.

** Attachment added: "_usr_sbin_avahi-daemon.0.crash.xz"
   
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+attachment/4775053/+files/_usr_sbin_avahi-daemon.0.crash.xz

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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

[Touch-packages] [Bug 1606946] Re: AppArmor denied opening /dev/shm/lttng-ust-wait*

[Launchpad Bug Tracker]

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

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

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

Title:
  AppArmor denied opening /dev/shm/lttng-ust-wait*

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  When running under the Unity8 desktop session, the kernel log is
  spammed with apparmor messages coming from the webbrowser app profile,
  the same four lines every 5 seconds:

  $ dmesg -w
  [...]
  [85560.662068] audit: type=1400 audit(1469629097.571:50068): 
apparmor="DENIED" operation="open" profile="webbrowser-app" 
name="/dev/shm/lttng-ust-wait-6-1000" pid=17206 comm="QQmlThread" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  [85560.662124] audit: type=1400 audit(1469629097.571:50069): 
apparmor="DENIED" operation="open" profile="webbrowser-app" 
name="/dev/shm/lttng-ust-wait-6" pid=17205 comm="QQmlThread" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=119
  [85560.662173] audit: type=1400 audit(1469629097.571:50070): 
apparmor="DENIED" operation="open" profile="webbrowser-app" 
name="/dev/shm/lttng-ust-wait-6-1000" pid=17206 comm="QQmlThread" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  [85560.662221] audit: type=1400 audit(1469629097.571:50071): 
apparmor="DENIED" operation="open" profile="webbrowser-app" 
name="/dev/shm/lttng-ust-wait-6" pid=17205 comm="QQmlThread" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=119

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

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

[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

[Brian Murray]

Well, this is the mostly frequently reported crash about avahi.

https://errors.ubuntu.com/problem/e3068628ffa22d8ed9dcdcccf7bfa88edaa6b5c7

The stacktrace indicates it OOM'ing.

#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
set = {__val = {0, 13338433739676818176, 140727378437776, 0, 
140727378437776, 140442759178355, 140727378437584, 140442774564936, 
140442776768528, 140442770201056, 140727378438144, 140727378438352, 
18446744073709551615, 140442774633396, 1, 0}}
pid = 
tid = 
#1  0x7fbb606943ea in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, 
sa_mask = {__val = {0, 1, 210453397509, 0, 140442756836096, 135168, 
140442776768528, 140442770201056, 140727378438144, 28, 140442756925040, 28, 
140442772455840, 2, 18446744073709551615, 0}}, sa_flags = 1641156624, 
sa_restorer = 0x7fbb619041bc }
sigs = {__val = {32, 0 }}
#2  0x7fbb618fef7e in oom () at malloc.c:58
msg = "Out of memory, aborting ...\n"
n = 
#3  0x7fbb618ff12f in xmalloc (size=) at malloc.c:69
p = 

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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

[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

[Brian Murray]

Could somebody provide a crash report or a link to one?

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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

[Touch-packages] [Bug 1539995] Re: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

[Brian Murray]

** Information type changed from Private to Public

** Tags added: rls-z-incoming

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

Title:
  apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Partial Upgrade failed (crash)
  Ubuntu Mate 16 Alpha install testing on different machines.
  This machine Dell Optiplex 960

  linuxpusher@linuxpusher-OptiPlex-960:~$ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  
  linuxpusher@linuxpusher-OptiPlex-960:~$ sudo lshw
  [sudo] password for linuxpusher: 
  linuxpusher-optiplex-960  
  description: Computer
  width: 64 bits
  capabilities: smbios-2.5 vsyscall32
*-core
 description: Motherboard
 physical id: 0
   *-memory
description: System memory
physical id: 0
size: 7819MiB
   *-cpu
product: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
vendor: Intel Corp.
physical id: 1
bus info: cpu@0
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl 
aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 xsave lahf_lm dtherm tpr_shadow vnmi flexpriority
   *-pci
description: Host bridge
product: 4 Series Chipset DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 03
width: 32 bits
clock: 33MHz
configuration: driver=agpgart-intel
resources: irq:0
  *-display:0
   description: VGA compatible controller
   product: 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:33 memory:fe80-febf 
memory:d000-dfff ioport:ecb0(size=8)
  *-display:1 UNCLAIMED
   description: Display controller
   product: 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2.1
   bus info: pci@:00:02.1
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: pm bus_master cap_list
   configuration: latency=0
   resources: memory:fe70-fe7f
  *-communication:0
   description: Communication controller
   product: 4 Series Chipset HECI Controller
   vendor: Intel Corporation
   physical id: 3
   bus info: pci@:00:03.0
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list
   configuration: driver=mei_me latency=0
   resources: irq:34 memory:feda6000-feda600f
  *-ide
   description: IDE interface
   product: 4 Series Chipset PT IDER Controller
   vendor: Intel Corporation
   physical id: 3.2
   bus info: pci@:00:03.2
   version: 03
   width: 32 bits
   clock: 66MHz
   capabilities: ide pm msi bus_master cap_list
   configuration: driver=ata_generic latency=0
   resources: irq:18 ioport:fe80(size=8) ioport:fe90(size=4) 
ioport:fea0(size=8) ioport:feb0(size=4) ioport:fef0(size=16)
  *-communication:1
   description: Serial controller
   product: 4 Series Chipset Serial KT Controller
   vendor: Intel Corporation
   physical id: 3.3
   bus info: pci@:00:03.3
   version: 03
   width: 32 bits
   clock: 66MHz
   capabilities: pm msi 16550 bus_master cap_list
   configuration: driver=serial latency=0
   resources: irq:17 ioport:ecb8(size=8) memory:fe6d8000-fe6d8fff
  *-network
   description: Ethernet interface
   product: 82567LM-3 Gigabit Network Connection
   vendor: Intel Corporation
   physical id: 19
   bus info: pci@:00:19.0
   logical name: enp0s25
   version: 02
   serial: 

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

[Brian Murray]

** Tags added: xenial

** Tags added: rls-z-incoming

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Triaged

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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

[Touch-packages] [Bug 1610215] Re: Mir build and test failures with gcc-6 and LTO

[Launchpad Bug Tracker]

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

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

Title:
  Mir build and test failures with gcc-6 and LTO

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

Bug description:
  The exact failure mode is different depending on whether ld.bfd or
  ld.gold is used. In both cases, however, the core issue seems to be
  that implicit destructor symbols cannot be found.

   ld.bfd ===

  Build error for mir_acceptance_tests:

  ../libmir-test-assist.a(fake_display.cpp.o): In function 
`mir::test::doubles::NullDisplaySyncGroup::NullDisplaySyncGroup()':
  /root/mir/include/test/mir/test/doubles/null_display_sync_group.h:68: 
undefined reference to `vtable for mir::test::doubles::NullDisplaySyncGroup'
  ../libmir-test-assist.a(fake_display.cpp.o): In function 
`mir::test::doubles::NullDisplayBuffer::NullDisplayBuffer()':
  /root/mir/include/test/mir/test/doubles/null_display_buffer.h:31: undefined 
reference to `vtable for mir::test::doubles::NullDisplayBuffer'
  ../libmir-test-assist.a(fake_display.cpp.o): In function 
`mir::test::doubles::NullDisplaySyncGroup::NullDisplaySyncGroup()':
  /root/mir/include/test/mir/test/doubles/null_display_sync_group.h:68: 
undefined reference to `vtable for mir::test::doubles::NullDisplaySyncGroup'
  ../libmir-test-assist.a(fake_display.cpp.o): In function 
`mir::test::doubles::NullDisplayBuffer::NullDisplayBuffer()':
  /root/mir/include/test/mir/test/doubles/null_display_buffer.h:31: undefined 
reference to `vtable for mir::test::doubles::NullDisplayBuffer'
  collect2: error: ld returned 1 exit status
  tests/acceptance-tests/CMakeFiles/mir_acceptance_tests.dir/build.make:1450: 
recipe for target 'bin/mir_acceptance_tests.bin' failed
  make[2]: *** [bin/mir_acceptance_tests.bin] Error 1
  CMakeFiles/Makefile2:9407: recipe for target 
'tests/acceptance-tests/CMakeFiles/mir_acceptance_tests.dir/all' failed
  make[1]: *** [tests/acceptance-tests/CMakeFiles/mir_acceptance_tests.dir/all] 
Error 2

  Build error for mir_unit_tests:

  ../mir_test_framework/libmir-test-framework-static.a(stub_session.cpp.o): In 
function `_GLOBAL__sub_I_stub_session.cpp':
  /root/mir/tests/mir_test_framework/stub_session.cpp:161: undefined reference 
to `mir::test::doubles::StubSession::~StubSession()'
  
../mir_test_framework/libmir-test-framework-static.a(stub_session.cpp.o):(.data.rel.ro._ZTVN3mir4test7doubles11StubSessionE[_ZTVN3mir4test7doubles11StubSessionE]+0x10):
 undefined reference to `mir::test::doubles::StubSession::~StubSession()'
  
../mir_test_framework/libmir-test-framework-static.a(stub_session.cpp.o):(.data.rel.ro._ZTVN3mir4test7doubles11StubSessionE[_ZTVN3mir4test7doubles11StubSessionE]+0x18):
 undefined reference to `mir::test::doubles::StubSession::~StubSession()'
  
../mir_test_framework/libmir-test-framework-static.a(stub_session.cpp.o):(.debug_info+0xbb84):
 undefined reference to `mir::test::doubles::StubSession::~StubSession()'
  
../mir_test_framework/libmir-test-framework-static.a(testing_server_options.cpp.o):
 In function `mir::ServerConfiguration::ServerConfiguration()':
  /root/mir/src/include/server/mir/server_configuration.h:89: undefined 
reference to `vtable for mir::ServerConfiguration'
  /root/mir/src/include/server/mir/server_configuration.h:89: undefined 
reference to `vtable for mir::ServerConfiguration'
  
../mir_test_framework/libmir-test-framework-static.a(stubbed_server_configuration.cpp.o):
 In function `mir::ServerConfiguration::ServerConfiguration()':
  /root/mir/src/include/server/mir/server_configuration.h:89: undefined 
reference to `vtable for mir::ServerConfiguration'
  collect2: error: ld returned 1 exit status
  tests/unit-tests/CMakeFiles/mir_unit_tests.dir/build.make:4588: recipe for 
target 'bin/mir_unit_tests.bin' failed
  make[2]: *** [bin/mir_unit_tests.bin] Error 1
  CMakeFiles/Makefile2:10841: recipe for target 
'tests/unit-tests/CMakeFiles/mir_unit_tests.dir/all' failed
  make[1]: *** [tests/unit-tests/CMakeFiles/mir_unit_tests.dir/all] Error 2
  Makefile:138: recipe for target 'all' failed
  make: *** [all] Error 2

  
  === ld.gold ===

  No build errors, but we get segfaults when running the mir_unit_tests
  during the destruction of StubSession objects.

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

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

[Touch-packages] [Bug 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

[Launchpad Bug Tracker]

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

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

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

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

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

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

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

[Touch-packages] [Bug 1612406] Re: numlock turn off alone

[Eduardo Garbin]

Yes!!!
I downloaded the iso and used it all day at work. No sign of the bug.
I think it worked!

Thank you very much for the support and time spent.

Ubuntu Power!

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

Title:
  numlock turn off alone

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Hello;
  Im using Ubuntu 16.04.1 - 64bits, but this bug follow me from Ubuntu 14.04

  No aparecente reason, the numeric keypad buttons are off. To work
  again, i have to press the 'numlock' twice, turn off and on again.
  This occurs many times during use of the machine.

  No matter what application or task I'm doing, it happens repeatedly.

  
  Hardware details:

  Caminho do hardware  Dispositivo  Classe Descrição
  
system 670Z5E (SAMSUNG SENS Series)
  /0busNP670Z5E-XD1BR
  /0/0  memory 64KiB BIOS
  /0/34 memory 512KiB L2 cache
  /0/35 memory 128KiB L1 cache
  /0/36 memory 3MiB L3 cache
  /0/37 memory 8GiB Memória do sistema
  /0/37/0   memory DIMMProject-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 
2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: 
Neliton Pereira Jr. Language-Team: Brazilian Portuguese 
MIME-Version: 1.0Content-Type: text/plain; 
charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 
17:08+X-Generator: Launchpad (build 18115) [vazio]
  /0/37/1   memory DIMMProject-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 
2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: 
Neliton Pereira Jr. Language-Team: Brazilian Portuguese 
MIME-Version: 1.0Content-Type: text/plain; 
charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 
17:08+X-Generator: Launchpad (build 18115) [vazio]
  /0/37/2   memory 8GiB SODIMM DDR3 Síncrono 
1600 MHz (0,6 ns)
  /0/37/3   memory DIMMProject-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 
2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: 
Neliton Pereira Jr. Language-Team: Brazilian Portuguese 
MIME-Version: 1.0Content-Type: text/plain; 
charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 
17:08+X-Generator: Launchpad (build 18115) [vazio]
  /0/38 processor  Intel(R) Core(TM) i5-3230M 
CPU @ 2.60GHz
  /0/100bridge 3rd Gen Core processor DRAM 
Controller
  /0/100/1  bridge Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port
  /0/100/1/0genericIllegal Vendor ID
  /0/100/2  display3rd Gen Core processor 
Graphics Controller
  /0/100/14 bus7 Series/C210 Series Chipset 
Family USB xHCI Host Controller
  /0/100/14/0  usb4 busxHCI Host Controller
  /0/100/14/1  usb3 busxHCI Host Controller
  /0/100/14/1/3 genericUSB2.0-CRW
  /0/100/16 communication  7 Series/C210 Series Chipset 
Family MEI Controller #1
  /0/100/1a bus7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #2
  /0/100/1a/1  usb1 busEHCI Host Controller
  /0/100/1a/1/1 busIntegrated Rate Matching Hub
  /0/100/1a/1/1/2   input  2.4G Keyboard Mouse
  /0/100/1a/1/1/4   multimedia WebCam SC-10HDP12631N
  /0/100/1b multimedia 7 Series/C210 Series Chipset 
Family High Definition Audio Controller
  /0/100/1c bridge 7 Series/C210 Series Chipset 
Family PCI Express Root Port 1
  /0/100/1c/0  wlp2s0   networkCentrino Advanced-N 6235
  /0/100/1c.3   bridge 7 Series/C210 Series Chipset 
Family PCI Express Root Port 4
  /0/100/1c.3/0enp3s0   networkRTL8111/8168/8411 PCI 
Express Gigabit Ethernet Controller
  /0/100/1d bus7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #1
  /0/100/1d/1  usb2 bus 

[Touch-packages] [Bug 1609612] Re: clang builds fail (again)

[Launchpad Bug Tracker]

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

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

Title:
  clang builds fail (again)

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

Bug description:
  clang builds fail (again) since yakkety switched to gcc 6 today.

  And I only got clang working again yesterday :(
  https://code.launchpad.net/~vanvugt/mir/fix-clang-20160803/+merge/301869

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

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

[Touch-packages] [Bug 1612256] Re: [regression] Trust prompt not shown when starting camera

[Launchpad Bug Tracker]

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

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

Title:
  [regression] Trust prompt not shown when starting camera

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Installed bq-aquaris.en (rev 405) and mir 0.24.0 from silo 36.
  Clicking camera, the application appears to be stuck waiting for the
  trust prompt.

  This does not happen with 0.23.5.

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

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

[Touch-packages] [Bug 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working

[Launchpad Bug Tracker]

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

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

Title:
  Nested servers prevent overlays or fullscreen bypass from working

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

Bug description:
  Nested servers prevent fullscreen bypass from working.

  This would explain why nesting fullscreen clients is measurably slower than 
non-nesting:
  Direct (bypass) 2600
  Direct (bypass off) 2400
  Nested (bypass) 2450
  Nested (bypass off) 2330

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

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

[Touch-packages] [Bug 1584894] Re: unity-system-compositor (or any Mir server) crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter and QEMU

[Launchpad Bug Tracker]

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

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

Title:
  unity-system-compositor (or any Mir server) crashes on start-up with
  "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics
  Adapter and QEMU

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

Bug description:
  (separated from bug 1118903)
  unity-system-compositor crashes on start-up with "Mir fatal error: Failed to 
schedule page flip" on VirtualBox Graphics Adapter

  ---

  can not login to Unity8

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-system-compositor 0.4.3+16.04.20160323-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Mon May 23 19:20:43 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-05-19 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160519)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file 
/run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:

  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   mir::fatal_error_abort(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.8
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGABRT in 
mir::fatal_error_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  version.libdrm: libdrm2 2.4.68-1
  version.lightdm: lightdm 1.19.0-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1613352] Re: Test timeout: MesaDisplayConfigurationTest.reads_updated_subpixel_information

[Launchpad Bug Tracker]

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

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

Title:
  Test timeout:
  MesaDisplayConfigurationTest.reads_updated_subpixel_information

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

Bug description:
  MesaDisplayConfigurationTest.reads_updated_subpixel_information
  will timeout under load.

  06:17:37 28: [--] 8 tests from MesaDisplayConfigurationTest
  06:17:37 28: [ RUN ] 
MesaDisplayConfigurationTest.configuration_is_read_correctly
  06:17:37 28: [ OK ] 
MesaDisplayConfigurationTest.configuration_is_read_correctly (196 ms)
  06:17:37 28: [ RUN ] 
MesaDisplayConfigurationTest.reads_subpixel_information_correctly
  06:17:37 28: [ OK ] 
MesaDisplayConfigurationTest.reads_subpixel_information_correctly (264 ms)
  06:17:37 28: [ RUN ] 
MesaDisplayConfigurationTest.reads_updated_subpixel_information
  08:47:37 make[2]: *** [test] Terminated
  08:47:37 make: *** [build] Terminated
  08:47:37 make[1]: *** wait: No child processes.  Stop.
  08:47:37 make[1]: *** Waiting for unfinished jobs
  08:47:37 make[1]: *** wait: No child processes.  Stop.
  08:47:37 Makefile:85: recipe for target 'test' failed
  08:47:37 debian/rules:13: recipe for target 'build' failed
  08:47:37 E: Caught signal ���Terminated���: terminating immediately
  08:47:37 Build killed with signal TERM after 150 minutes of inactivity
  08:47:37 

  First seen here:
  
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/1811/consoleFull
  and reproduced under load locally with lp:mir.

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

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

[Touch-packages] [Bug 1625401] Re: Mir server seems to spin at 100% and steals focus from everything until the server shutdown

[Launchpad Bug Tracker]

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

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

Title:
  Mir server seems to spin at 100% and steals focus from everything
  until the server shutdown

Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  Fix Released
Status in MirAL:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Start a Mir server (doesn't have to be miral-shell, but we'll use that
  example) with gnome-terminal:

  $ miral-shell --startup gnome-terminal

  In the terminal start and detach Xmir:

  $ Xmir -rootless :1&

  Close the terminal.

  When I do hit this, unable to do anything key focus wise. (I can open
  a terminal ctrl+alt+t but i cant type into, mouse events work fine)

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

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

[Touch-packages] [Bug 1615703] Re: [regression] mir demo server fails to start with mx4

[Launchpad Bug Tracker]

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

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

Title:
  [regression] mir demo server fails to start with mx4

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

Bug description:
  mir_demo_server fails to start with mx4. I'd guess failure indicates
  the u8 stack wouldn't start either. Should be fixed for 0.25 series.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Launchpad Bug Tracker]

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

-- 
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 Committed
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 1617865] Re: [regression] Accidental libmircommon.so.6 ABI break in Mir 0.24.0: mir::dispatch::ReadableFd* moved version stanzas

[Launchpad Bug Tracker]

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

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

Title:
  [regression] Accidental libmircommon.so.6 ABI break in Mir 0.24.0:
  mir::dispatch::ReadableFd* moved version stanzas

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

Bug description:
  Accidental libmircommon.so.6 ABI break in Mir 0.24:
  mir::dispatch::ReadableFd* moved version stanzas

  So for example server-mesa-x11.so.9 can no longer load because it expects 
from libmircommon.so.6:
 ZN3mir8dispatch10ReadableFdC1ENS_2FdERKSt8functionIFvvEE@MIR_COMMON_5.1
  but actually in Mir 0.24.0 that got duplicated and changed to:
 ZN3mir8dispatch10ReadableFdC1ENS_2FdERKSt8functionIFvvEE@MIR_COMMON_0.24

  https://bugs.launchpad.net/mir/+bug/1611804/comments/8

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

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

[Touch-packages] [Bug 1617435] Re: libmirserver-dev is missing a depends for uuid-dev

[Launchpad Bug Tracker]

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

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

Title:
  libmirserver-dev is missing a depends for uuid-dev

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

Bug description:
  From building qtmir:

  In file included from 
/«BUILDDIR»/qtmir-0.4.8+15.04.20160826.1/src/modules/Unity/Application/mirsurfacemanager.cpp:41:0:
  /usr/include/mirserver/mir/shell/persistent_surface_store.h:25:23: fatal 
error: uuid/uuid.h: No such file or directory
   #include 
 ^

  libmirserver-dev should depend on uuid-dev

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

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

[Touch-packages] [Bug 1626866] Re: [regression] 'make abi-check' fails to build

[Launchpad Bug Tracker]

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

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

Title:
  [regression] 'make abi-check' fails to build

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

Bug description:
  make abi-check fails to build:

  The GCC parameters:
/usr/bin/c++ -fdump-translation-unit -fkeep-inline-functions -c -x 
c++-header -fpermissive -w  -pthread -g -std=c++14 -Werror -Wall 
-fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC 
"/tmp/rTU25VRtKM/dump1.h"  -I/home/dan/bzr/mir/unbreak/include/common 
-I/home/dan/bzr/mir/unbreak/include/cookie -I/usr/include 
-I/home/dan/bzr/mir/unbreak/src/include/common 
-I/home/dan/bzr/mir/unbreak/build/src/protobuf 
-I/home/dan/bzr/mir/unbreak/include/platform 
-I/home/dan/bzr/mir/unbreak/src/include/platform

  In file included from /tmp/rTU25VRtKM/dump1.h:22:0:
  /home/dan/bzr/mir/unbreak/include/platform/mir/graphics/gamma_curves.h:27:7: 
error: redefinition of ‘class mir::graphics::GammaCurves’
   class GammaCurves
 ^~~
  In file included from 
/home/dan/bzr/mir/unbreak/include/platform/mir/graphics/display_configuration.h:26:0,
   from /tmp/rTU25VRtKM/dump1.h:4:
  /home/dan/bzr/mir/unbreak/include/platform/mir/graphics/gamma_curves.h:27:7: 
error: previous definition of ‘class mir::graphics::GammaCurves’
   class GammaCurves
 ^~~

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

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

[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

[Scott Moser]

I've added a MP for some doc on cloud-init boot and what it is trying to 
accomplish at
 https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/310386

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  In Progress
Status in cloud-init source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  
  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
└─basic.target @11.403s
  └─sockets.target @11.401s
└─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
└─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
└─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
└─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
└─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
└─system.slice @783ms
  └─-.slice @721ms

  
  cloud-init would need networkd to run at or before 'networking.service' so it 
can raise networking to then find and use network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list 
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init /usr/share/snappy/dpkg.list 
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances

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

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

[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""

[Launchpad Bug Tracker]

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

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

Title:
  Clients cannot connect when MIR_SOCKET=""

Status in Mir:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Launch a Unity 8 desktop session, log out, then log into a Unity 7
  session. Launch a Mir-on-X shell like MirAL and then try to launch a
  Mir client like mir_demo_client_egltriangle. The client will refuse to
  connect.

  Unity 8's upstart script always sets MIR_SOCKET to its old value when
  the session ends. If MIR_SOCKET wasn't set, then the post-stop script
  will still set MIR_SOCKET, setting it to "". Mir should interpret this
  as if MIR_SOCKET were unset.

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

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

[Touch-packages] [Bug 1639743] Re: `&` in french translaction "Logiciels & mises à jour" should be escaped as ``

[Gunnar Hjalmarsson]

I think I found it. It seems to be a translation issue after all, but in
the ubuntu-release-upgrader package:

https://translations.launchpad.net/ubuntu/yakkety/+source/ubuntu-
release-upgrader/+pots/ubuntu-release-upgrader/fr/57

So replacing & with  there ought to fix it.

** Package changed: software-properties (Ubuntu) => ubuntu-translations

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

** Changed in: ubuntu-translations
   Status: New => Triaged

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Ubuntu French Translators (ubuntu-l10n-fr)

** No longer affects: update-manager (Ubuntu)

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

Title:
  `&` in french translaction "Logiciels & mises à jour" should be
  escaped as ``

Status in Ubuntu Translations:
  Triaged

Bug description:
  When running update-manager in French the "Logiciels & mises à jour"
  sentence make the update-manager to fail with an empty dialog.

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

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

[Touch-packages] [Bug 1638774] Re: Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-size array

[Launchpad Bug Tracker]

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

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

Title:
  Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-
  size array

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

Bug description:
  Mir FTBFS on zesty:

  In file included from 
/home/dan/bzr/mir/trunk/tests/unit-tests/platforms/android/server/test_buffer.cpp:27:0:
  
/home/dan/bzr/mir/trunk/tests/include/mir/test/doubles/mock_android_native_buffer.h:65:21:
 error: invalid use of ‘struct native_handle’ with a zero-size array in ‘struct 
mir::test::doubles::MockAndroidNativeBuffer’ [-Werror=pedantic]
   native_handle_t native_handle;
   ^
  In file included from /usr/include/android-23/system/window.h:20:0,
   from /usr/include/android-23/hardware/gralloc.h:21,
   from 
/home/dan/bzr/mir/trunk/src/platforms/android/server/buffer.h:27,
   from 
/home/dan/bzr/mir/trunk/tests/unit-tests/platforms/android/server/test_buffer.cpp:20:
  /usr/include/android-23/cutils/native_handle.h:29:15: note: array member ‘int 
native_handle::data [0]’ declared here
   int data[0];/* numFds + numInts ints */
 ^

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

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

[Touch-packages] [Bug 1640518] Re: MongoDB Memory corruption

[Matthias Klose]

** Package changed: gcc-4.8 (Ubuntu) => gcc-5 (Ubuntu)

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

Title:
  MongoDB Memory corruption

Status in gcc-5 package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Calvin L. Sze  - 2016-11-01 23:09:10 ==
  Team has changed to the Bare-metal Ubuntu 16.4.  The problem still exists, so 
it is not related to the virtualization. 

  Since the bug is complicated to reproduce,  Could we use sets of tools
  to collect the data when this happens?

  
  ---Problem Description---
  MongoDB has memory corruption issues which only occurred on Ubuntu 16.04, it 
doesn't occur on Ubuntu 15.
   
  Contact Information =Calvin Sze/Austin/IBM
   
  ---uname output---
  Linux master 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:57 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Model: 2.1 (pvr 004b 0201) Model name: 
   POWER8E (raw), altivec supported 
   
  ---System Hang---
   the system is still alive
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Unfortunately, not very easily. I had a test case that I was running on 
ubuntu1604-ppc-dev.pic.build.10gen.cc and -ppc-dev.pic.build.10gen.cc. I 
understand these to be two VMs running on the same physical host.

  About 3.5% of the test runs on ubuntu1604-ppc-dev.pic.build.10gen.cc
  would fail, but all of the runs on the other machine passed.
  Originally, this failure manifested as the GCC stack protector (from
  -fstack-protector-strong) claiming stack corruption.

  Hoping to be able to see the data that was being written and
  corrupting the stack, I manually injected a guard region into the
  stack of the failing functions as follows:


  
  +namespace {
  +
  +class Canary {
  +public:
  +
  +static constexpr size_t kSize = 1024;
  +
  +explicit Canary(volatile unsigned char* const t) noexcept : _t(t) {
  +::memset(const_cast(_t), kBits, kSize);
  +}
  +
  +~Canary() {
  +_verify();
  +}
  +
  +private:
  +static constexpr uint8_t kBits = 0xCD;
  +static constexpr size_t kChecksum = kSize * size_t(kBits);
  +
  +void _verify() const noexcept {
  +invariant(std::accumulate(&_t[0], &_t[kSize], 0UL) == kChecksum);
  +}
  +
  +const volatile unsigned char* const _t;
  +};
  +
  +}  // namespace
  +

   Status bsonExtractField(const BSONObj& object, StringData fieldName, 
BSONElement* outElement) {
  +
  +volatile unsigned char* const cookie = static_cast(alloca(Canary::kSize));
  +const Canary c(cookie);
  + 

  When running with this, the invariant would sometimes fire. Examining
  the stack cookie under the debugger would show two consecutive bytes,
  always at an offset ending 0x...e, written as either 0 0, or 0 1,
  somewhere at random within the middle of the cookie.

  This indicated that it was not a conventional stack smash, where we
  were writing past the end of a contiguous buffer. Instead it appeared
  that either the currently running thread had reached up some arbitrary
  and random amount on the stack and done either two one-byte writes, or
  an unaligned 2-byte write. Another possibility was that a local
  variable had been transferred to another thread, which had written to
  it.

  However, while looking at the code to find such a thing, I realized
  that there was another possibility, which was that the bytes had never
  been written correctly in the first place. I changed the stack canary
  constructor to be:


  +explicit Canary(volatile unsigned char* const t) noexcept : _t(t) {
  +::memset(const_cast(_t), kBits, kSize);
  +_verify();
  +}  

  So that immediately after writing the byte pattern to the stack
  buffer, we verified the contents we wrote. Amazingly, this *failed*,
  with the same corruption as seen before. This means that either
  between the time we called memset to write the bytes and when we read
  them back, something either overwrote the stack cookie region, or that
  the bytes were never written correctly by memset, or that memset wrote
  the bytes, but the underlying physical memory never took the write.



   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: MongoDB 

  Userspace rpm: mongod 
   
  The userspace tool has the following bit modes: 64bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Lilian Romero/Austin/IBM: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Luciano Chavez  - 2016-11-02 08:41:47 

[Touch-packages] [Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568

[hakon]

I tried to produce a PulseAudio verbose log by editing /etc/pulse/client.conf
and adding this line to the file: 

extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log
--log-time=1

Here is the log file I got after rebooting: see attached file
pulseverbose.log


** Attachment added: "PulseAudio verbose log created at reboot."
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+attachment/4775013/+files/pulseverbose.log

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

Title:
  Sound card not recognized on  Dell Vostro 5568

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just reinstalled a fresh Ubuntu 16.10 on my Dell Vostro 5568 laptop.

  The audio controller on the laptop is a Realtek ALC3246 with Waves
  MaxxAudio Pro. The external interface connector is a microphone
  in/stereo headphones/external speakers connector.

  When I select "System Settings->Sound" the output device in the dialog
  window shows as "Dummy Output" and when I press the "Test Sound"
  button no sound is heard from either front left or front right speaker
  ( I have ensured sound is not muted ).

  Note: Before reinstalling, I asked a question on askubuntu,com:

  http://askubuntu.com/q/841759/156688

  So reinstallation of Ubuntu 16.10 did not help on my sound problem.

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

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

[Touch-packages] [Bug 1639627] Re: Garbled graphic ("zoomed in effect") in fullscreen 3D applications if other window opens

[Michael]

On a Lenovo x201s and x61t with Intel integrated graphics (i7 first gen
& x3100) it was since at least the release of 14.04 (which was a update
series since 7.10 or so), on the Toshiba z20t it was a fresh
installation.

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

Title:
  Garbled graphic ("zoomed in effect") in fullscreen 3D applications if
  other window opens

Status in xorg package in Ubuntu:
  New

Bug description:
  I've a problem with full screen apps since ages (using ubuntu 14.04
  and 16.04 64 bit and gnome flashback+compiz). they are liked "zoomed
  in", so I see only 75% if there is other window layered over it
  (e.g.skype messages or apport)...

  If I disable unredirect_fullscreen_windows completly fullscreen
  windows are always distorted in this way. I both tried the original
  xorg drivers and the ones from http://ppa.launchpad.net/oibaf
  /graphics-drivers/ubuntu . And also the mainline kernel.

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

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

[Touch-packages] [Bug 1639743] Re: `&` in french translaction "Logiciels & mises à jour" should be escaped as ``

[Gunnar Hjalmarsson]

Thanks for the additional info, Natim!

I tested with escaping the French string and, as you can see at the
attached screenshot, doing so would not be a proper fix.

Somehow we need to track down which code is causing the issue you have
demonstrated.

** Attachment added: "software-properties_name-string.png"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1639743/+attachment/4775011/+files/software-properties_name-string.png

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => New

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

Title:
  `&` in french translaction "Logiciels & mises à jour" should be
  escaped as ``

Status in software-properties package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  When running update-manager in French the "Logiciels & mises à jour"
  sentence make the update-manager to fail with an empty dialog.

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

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

[Touch-packages] [Bug 1639743] Re: `&` in french translaction "Logiciels & mises à jour" should be escaped as ``

[Natim]

It talks about software-properties tool rather than "Logiciels & mises à
jour"

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

Title:
  `&` in french translaction "Logiciels & mises à jour" should be
  escaped as ``

Status in software-properties package in Ubuntu:
  Incomplete
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  When running update-manager in French the "Logiciels & mises à jour"
  sentence make the update-manager to fail with an empty dialog.

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

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

[Touch-packages] [Bug 1639743] Re: `&` in french translaction "Logiciels & mises à jour" should be escaped as ``

[Natim]

I don't have the problem with English

** Attachment added: "with-engish.png"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1639743/+attachment/4774998/+files/with-engish.png

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

Title:
  `&` in french translaction "Logiciels & mises à jour" should be
  escaped as ``

Status in software-properties package in Ubuntu:
  Incomplete
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  When running update-manager in French the "Logiciels & mises à jour"
  sentence make the update-manager to fail with an empty dialog.

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

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

[Touch-packages] [Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568

[hakon]

Unfortuneately, the problem was not fixed after all. I was a little bit
to quick to conclude in my last post. Now the sound has stopped working
again (both in Windows and Ubuntu). But it starts with a problem in
Ubuntu. After unplugging the headphones, the "What kind of device did
you plug in?" dialog does not show the next time I replug the headphones
( which is fine, see https://bugs.launchpad.net/ubuntu/+source/unity-
settings-daemon/+bug/1297790 ) however what is not fine is that there is
no sound. System Settings->Sound show "Dummy output" in the Output tab,
and the system does not recognize the sound card any longer. For
example:

$ ls /proc/asound/*
ls: cannot access '/proc/asound/*': No such file or directory

$ aplay -l
aplay: device_list:268: no soundcards found...

$ sudo lspci -v | grep Audio
[no output]

The strange thing is that the problem then propagates to Windows 10. How is 
that possible? 
Is there settings on the sound card that survives a reboot? If that is the 
case, how can
one reset the sound card to its initial configuration?

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

Title:
  Sound card not recognized on  Dell Vostro 5568

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just reinstalled a fresh Ubuntu 16.10 on my Dell Vostro 5568 laptop.

  The audio controller on the laptop is a Realtek ALC3246 with Waves
  MaxxAudio Pro. The external interface connector is a microphone
  in/stereo headphones/external speakers connector.

  When I select "System Settings->Sound" the output device in the dialog
  window shows as "Dummy Output" and when I press the "Test Sound"
  button no sound is heard from either front left or front right speaker
  ( I have ensured sound is not muted ).

  Note: Before reinstalling, I asked a question on askubuntu,com:

  http://askubuntu.com/q/841759/156688

  So reinstallation of Ubuntu 16.10 did not help on my sound problem.

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

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

[Touch-packages] [Bug 1640561] [NEW] package python3-libapparmor 2.10.95-4ubuntu5 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[G Singh]

Public bug reported:

having this trouble and i am new to ubuntu, please help

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: python3-libapparmor 2.10.95-4ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Wed Nov  9 17:33:41 2016
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-11-08 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=63c80f06-d5ed-42a4-b94e-08a8b996817b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: apparmor
Syslog: Nov  9 18:02:44 gurminder-Aspire-5745PG dbus[745]: [system] AppArmor 
D-Bus mediation is enabled
Title: package python3-libapparmor 2.10.95-4ubuntu5 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package python3-libapparmor 2.10.95-4ubuntu5 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in apparmor package in Ubuntu:
  New

Bug description:
  having this trouble and i am new to ubuntu, please help

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: python3-libapparmor 2.10.95-4ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  9 17:33:41 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-11-08 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=63c80f06-d5ed-42a4-b94e-08a8b996817b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: apparmor
  Syslog: Nov  9 18:02:44 gurminder-Aspire-5745PG dbus[745]: [system] AppArmor 
D-Bus mediation is enabled
  Title: package python3-libapparmor 2.10.95-4ubuntu5 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

[Mauricio Faria de Oliveira]

Hi @paelzer,

Thanks!

I had in mind to submit the patch for Debian libvirt if/once the
allocation request is granted on Debian.  Of course, I can submit in
advance and mention it's awaiting for base-passwd.

Could you help w/ the base-passwd process? I believe it's @cjwatson who
handles this on Debian and Ubuntu, right?

For reference, this is the e-mail sent to Debian base-passwd:

 Forwarded Message 
Subject: request uid and gid allocation for libvirt-qemu
Date: Tue, 25 Oct 2016 09:27:00 -0200
From: Mauricio Faria de Oliveira 
To: base-pas...@packages.debian.org
CC: pkg-libvirt-maintain...@lists.alioth.debian.org

Hi,

I'd like to request an uid and gid for the libvirt-qemu user/group.

This is in support of guest migration with disk images over NFS.  That
requires the same uid/gid on source and target host systems, otherwise
IO requests for disk images (owned by libvirt-qemu) fail with -EACCES,
which causes IO errors in a guest undergoing migration.

The patches for libvirt will be submitted if the allocation is granted.

According to 'base-passwd/README':
> You *may not* use any uids or gids in the 6-64999 range without
> *first* requesting an allocation from base-pas...@packages.debian.org
> and waiting for confirmation that the allocation has been granted.

Thanks,

-- 
Mauricio Faria de Oliveira
IBM Linux Technology Center

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in base-passwd package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

  Please see comments for the problem description, and summary of
  originally bridged comments in the description.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

[Jason Gerard DeRose]

Mathieu,

I tested your PPA package with Xenial: with no config changes on my end,
it's working as expected from my use case.

Thanks!

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  In Progress

Bug description:
  [Impact]
   * initramfs-tools SRUs introduced regressions in ip= syntax, which cause 
unexpected behavior

  [Test Case]
   * Create a machine that boots using an nfsroot.
   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.
   * Discover that the device never comes up because, networking is not 
configured correctly.

  [Regression Potential]
  Should be back to original behavior before ipv6 support was introduced in the 
past 2 or 3 SRUs.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
     - The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken
     -
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  This bug is a regression of changes made under bug 1628306.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

[ChristianEhrhardt]

@Mauricio - thanks for your great pre-work on this!
You mentioned you push to Debian - do you also have a debian bug already that 
we should/could link?

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in base-passwd package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

  Please see comments for the problem description, and summary of
  originally bridged comments in the description.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

[ChristianEhrhardt]

Just skimming over the issue and the proposed solution I'm ok
considering for libvirt provided that the change is ok and gone into
base-passwd. Adding that as a task to make that clear.

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

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

** Also affects: base-passwd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in base-passwd package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

  Please see comments for the problem description, and summary of
  originally bridged comments in the description.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1640554] [NEW] package util-linux 2.28.2-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Leon Yu]

Public bug reported:

upgrade from 16.4 to 16.10

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: util-linux 2.28.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Nov  9 12:11:58 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-08-06 (94 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: util-linux
Title: package util-linux 2.28.2-1ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to yakkety on 2016-11-09 (0 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package util-linux 2.28.2-1ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  upgrade from 16.4 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.28.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  9 12:11:58 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-06 (94 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: util-linux
  Title: package util-linux 2.28.2-1ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-11-09 (0 days ago)

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

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

[Touch-packages] [Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

[Joshua Powers]

** Tags added: server-next

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

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

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

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  
  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1640544] [NEW] "indicator-power" says "estimating" when plugged to power.

[Budhajeewa]

Public bug reported:

There seem to be a couple of bug reports from 4 - 5 years ago,
complaining the same thing. Looks like the bug is back in 16.10.

---

>1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

16.10 (yakkety)

>2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

Installed: 12.10.6+16.10.20160708-0ubuntu1
Candidate: 12.10.6+16.10.20160708-0ubuntu1

>3) What you expected to happen

The indicator should say the remaining time to be fully charged, and
display an icon of either a charging battery, or a "power plug" (In case
the battery is fully charged, and the machine is running on direct
power.).

>4) What happened instead

The indicator just says "estimating". It doesn't display whether it is
being charged, or running on direct power.

** Affects: indicator-power (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: indicator-powerd

** Attachment added: "Untitled.png"
   
https://bugs.launchpad.net/bugs/1640544/+attachment/4774947/+files/Untitled.png

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

Title:
  "indicator-power" says "estimating" when plugged to power.

Status in indicator-power package in Ubuntu:
  New

Bug description:
  There seem to be a couple of bug reports from 4 - 5 years ago,
  complaining the same thing. Looks like the bug is back in 16.10.

  ---

  >1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  16.10 (yakkety)

  >2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Installed: 12.10.6+16.10.20160708-0ubuntu1
  Candidate: 12.10.6+16.10.20160708-0ubuntu1

  >3) What you expected to happen

  The indicator should say the remaining time to be fully charged, and
  display an icon of either a charging battery, or a "power plug" (In
  case the battery is fully charged, and the machine is running on
  direct power.).

  >4) What happened instead

  The indicator just says "estimating". It doesn't display whether it is
  being charged, or running on direct power.

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

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

[Touch-packages] [Bug 1640544] Re: "indicator-power" says "estimating" when plugged to power.

[Budhajeewa]

The machine having this issue is an "ASUS X555LI" machine, if it helps.

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

Title:
  "indicator-power" says "estimating" when plugged to power.

Status in indicator-power package in Ubuntu:
  New

Bug description:
  There seem to be a couple of bug reports from 4 - 5 years ago,
  complaining the same thing. Looks like the bug is back in 16.10.

  ---

  >1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  16.10 (yakkety)

  >2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Installed: 12.10.6+16.10.20160708-0ubuntu1
  Candidate: 12.10.6+16.10.20160708-0ubuntu1

  >3) What you expected to happen

  The indicator should say the remaining time to be fully charged, and
  display an icon of either a charging battery, or a "power plug" (In
  case the battery is fully charged, and the machine is running on
  direct power.).

  >4) What happened instead

  The indicator just says "estimating". It doesn't display whether it is
  being charged, or running on direct power.

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

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

[Touch-packages] [Bug 1457400] Re: reduce 90s session kill timeout if the session does not shutdown cleanly

[menin]

Usung Kubuntu 16.04, I've got the same problem. I don't understand why
we're having that problem.

** Attachment added: "webwxgetmsgimg"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400/+attachment/4774935/+files/webwxgetmsgimg

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

Title:
  reduce 90s session kill timeout if the session does not shutdown
  cleanly

Status in lvm2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently
  onwards the ubuntu is taking long to shut down nearly 1:30 minutes.

  I checked the shutdown log messages and I get the follow message.

  A stop job is running for Session c2 of user * (25s/ 1min 30 s)

  It count downs till 1:30 minutes and then shutdown the machine.

  Why is it happening.

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

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

[Touch-packages] [Bug 1638021] Re: [SRU] Update apt/xenial to 1.2.15

[Julian Andres Klode]

It's been more than a month now that I've been running that on my
server, and no regressions popped up, so I think we are good to go.


And the individual bugs have automatic test cases if they can be tested, so 
there's no point in going over each of them individually and doing the same 
tests manually.


** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [SRU] Update apt/xenial to 1.2.15

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  1.2.15 is a somewhat larger bugfix release because I screwed up a bit with 
backporting fixes: 1.2.14 was released in June, and quite a few bugs have been 
fixed since then in the 1.3 series, but I never managed to release a new 1.2.y 
release. See Bug #1595177 for the 1.2.14 details.

  This changes the cache format to fix buffer overflows (the cache
  format is in sync with the 1.3 series and thus has the same version
  number). It also fixes several invalid states in the updating code
  (where we got mismatches before). Then there are several smaller
  bugfixes and more checks for file sanity I cannot really all recall,
  and some translation updates.

  This release also changes the autoremoval algorithm to only protect
  the latest same-source provider of a given package. infinity wanted
  this in for handling virtual ZFS modules provided by the kernel
  causing the kernels not to be autoremoved or something. We have this
  code in Debian testing and unstable since 1.3~pre1 early July and its
  in yakkety, and are reasonably sure it's stable now. This change also
  needs the two refactoring commits for the removal methods and the new
  pretty printers mentioned in the changelog.

  apt (1.2.15) xenial; urgency=medium

    [ Julian Andres Klode ]
    * methods/ftp: Cope with weird PASV responses.
  Thanks to Lukasz Stelmach for the initial patch (Closes: #420940)
    * Fix buffer overflow in debListParser::VersionHash() (Closes: #828812)
    * cache: Bump minor version to 6
    * indextargets: Check that cache could be built before using it
  (Closes: #829651)
    * gpgv: Unlink the correct temp file in error case
    * fileutl: empty file support: Avoid fstat() on -1 fd and check result
    * Ignore SIGINT and SIGQUIT for Pre-Install hooks
    * install-progress: Call the real ::fork() in our fork() method
    * Accept --autoremove as alias for --auto-remove
    * apt-inst: debfile: Pass comp. Name to ExtractTar, not Binary
    * changelog: Respect Dir setting for local changelog getting
    * Fix segfault and out-of-bounds read in Binary fields
    * Merge translations from 1.3~rc3
    * TagFile: Fix off-by-one errors in comment stripping
    * Base256ToNum: Fix uninitialized value
    * VersionHash: Do not skip too long dependency lines
    * Do not read stderr from proxy autodetection scripts

    [ Nicolas Le Cam ]
    * Use the ConditionACPower feature of systemd in the apt-daily service
  (Closes: #827930)

    [ David Kalnischkies ]
    * close server if parsing of header field failed
    * don't do atomic overrides with failed files (Closes: 828908)
    * if reading of autobit state failed, let write fail
    * write auto-bits before calling dpkg & again after if needed
    * factor out Pkg/DepIterator prettyprinters into own header
    * protect only the latest same-source providers from autoremove
    * reinstalling local deb file is no downgrade
    * do not treat same-version local debs as downgrade
    * avoid 416 response teardown binding to null pointer
    * don't change owner/perms/times through file:// symlinks
    * report all instead of first error up the acquire chain
    * keep trying with next if connection to a SRV host failed
    * call flush on the wrapped writebuffered FileFd
    * verify hash of input file in rred
    * use proper warning for automatic pipeline disable
    * rred: truncate result file before writing to it (Closes: #831762)
    * if the FileFd failed already following calls should fail, too
    * pass --force-remove-essential to dpkg only if needed
    * allow user@host (aka: no password) in URI parsing
    * drop incorrect const attribute from DirectoryExists (LP: 1473674)
    * http(s): allow empty values for header fields (Closes: 834048)
    * don't try pipelining if server closes connections (Closes: #832113)
    * don't loop on pinning pkgs from absolute debs by regex (Closes: 835818)
    * try not to call memcpy with length 0 in hash calculations
    * abort connection on '.' target replies in SRV

    [ Andrew Patterson ]
    * Add kernels with "+" in the package name to APT::NeverAutoRemove
  (Closes: #830159)

    [ Mert Dirik ]
    * Turkish program translation update (Closes: 832039)

    [ Zhou Mo ]
    * 

[Touch-packages] [Bug 1639337] Re: Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-xorg-evdev

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-
  xorg-evdev

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Please refer to bug filed with freedesktop.org:

  https://bugs.freedesktop.org/show_bug.cgi?id=98575

  I modified a driver for the Bosto Tablet 22HD and others, this has
  been working without problems across the last several releases and
  continues to work with 16.04.1 LTS.

  When I upgraded to 16.10, pressure readings are lost from all
  applications, X & Y data still visible.

  evtest shows correct EV_ data for ABS_X ABS_Y and ABS_PRESSURE, but
  when xinput is used.

  xinput --list --long 

  The Valuator for pressure is listed, but no changes occur as the tool
  is used. The parameters of the Valuator can still be modified using
  xinput tweaking tools, but no pressure reported.

  All X apps requiring pressure data fail.

  I made a fresh install of 16.10, loaded the driver  same issue.

  I run 16.04.1 LTS, everything fine.
  I have others users of my driver code also using 16.04.1 without issue.

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

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

[Touch-packages] [Bug 1639337] Re: Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-xorg-evdev

[vasdi]

I have Huion 420 tablet, it uses evdev driver and I have the same bug.

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

Title:
  Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-
  xorg-evdev

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Please refer to bug filed with freedesktop.org:

  https://bugs.freedesktop.org/show_bug.cgi?id=98575

  I modified a driver for the Bosto Tablet 22HD and others, this has
  been working without problems across the last several releases and
  continues to work with 16.04.1 LTS.

  When I upgraded to 16.10, pressure readings are lost from all
  applications, X & Y data still visible.

  evtest shows correct EV_ data for ABS_X ABS_Y and ABS_PRESSURE, but
  when xinput is used.

  xinput --list --long 

  The Valuator for pressure is listed, but no changes occur as the tool
  is used. The parameters of the Valuator can still be modified using
  xinput tweaking tools, but no pressure reported.

  All X apps requiring pressure data fail.

  I made a fresh install of 16.10, loaded the driver  same issue.

  I run 16.04.1 LTS, everything fine.
  I have others users of my driver code also using 16.04.1 without issue.

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

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

[Touch-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-47.68

---
linux (4.4.0-47.68) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1636941

  * Add a driver for Amazon Elastic Network Adapters (ENA) (LP: #1635721)
- lib/bitmap.c: conversion routines to/from u32 array
- net: ethtool: add new ETHTOOL_xLINKSETTINGS API
- net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)
- [config] enable CONFIG_ENA_ETHERNET=m (Amazon ENA driver)

  * unexpectedly large memory usage of mounted snaps (LP: #1636847)
- [Config] switch squashfs to single threaded decode

 -- Kamal Mostafa   Wed, 26 Oct 2016 10:47:55 -0700

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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

[Touch-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-47.68

---
linux (4.4.0-47.68) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1636941

  * Add a driver for Amazon Elastic Network Adapters (ENA) (LP: #1635721)
- lib/bitmap.c: conversion routines to/from u32 array
- net: ethtool: add new ETHTOOL_xLINKSETTINGS API
- net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)
- [config] enable CONFIG_ENA_ETHERNET=m (Amazon ENA driver)

  * unexpectedly large memory usage of mounted snaps (LP: #1636847)
- [Config] switch squashfs to single threaded decode

 -- Kamal Mostafa   Wed, 26 Oct 2016 10:47:55 -0700

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

** Changed in: linux (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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1611078

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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

[Touch-packages] [Bug 1621507] Please test proposed package

[Robie Basak]

Hello LaMont, or anyone else affected,

Accepted open-iscsi into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/open-
iscsi/2.0.873+git0.3b4b4500-14ubuntu8.1 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: open-iscsi (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Triaged
Status in isc-dhcp source package in Xenial:
  In Progress
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  In Progress
Status in isc-dhcp source package in Yakkety:
  In Progress
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) 

  
  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1621507] Please test proposed package

[Robie Basak]

Hello LaMont, or anyone else affected,

Accepted open-iscsi into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/open-
iscsi/2.0.873+git0.3b4b4500-14ubuntu3.2 in a few hours, and then in the
-proposed repository.

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

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

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

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Triaged
Status in isc-dhcp source package in Xenial:
  In Progress
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  In Progress
Status in isc-dhcp source package in Yakkety:
  In Progress
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) 

  
  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1610527] Re: 00:00 for all-day events in the Calendar indicator

[Launchpad Bug Tracker]

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

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

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

Title:
  00:00 for all-day events in the Calendar indicator

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  bq M10 rc-proposed

  For all-day events like birthdays, showing 00:00 in the calendar indicator is 
IMO a waste of space.
  Screenshot attached.

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Robie Basak]

We discussed this on IRC in #ubuntu-release and agreed on the following
plan of action:

0. cyphermox has uploaded open-iscsi to xenial and yakkety
1. rbasak will review open-iscsi (only) for acceptance into 
{xenial,yakkety}-proposed. Go back to step 0 for diff changes as needed, but 
there are no other blockers on the bug or on initramfs-tools or isc-dhcp
2. Nobody will upload isc-dhcp or initramfs-tools to the SRU queues in relation 
to this issue until open-iscsi finishes the SRU process in the usual way. Other 
unrelated SRUs to isc-dhcp and initramfs-tools are unaffected.
3. cyphermox will get consensus on the diffs for isc-dhcp and initramfs-tools
4. smoser will review and +1 the diffs (else go back to 3)
5. cypermox will upload isc-dhcp and initramfs-tools together to the xenial and 
yakkety queues for SRU processing in the usual way

This assumes that:
* Nobody has an objection to the current open-iscsi diff 
* Nobody expects the open-iscsi diff to need to change based on the conclusion 
of the changes to be made to isc-dhcp and initramfs-tools

[rbasak] IMHO, the open-iscsi change seems straightforward enough to not
be as concerned about regressions as I am with the previous initramfs-
tools regression. So I think it's OK that open-iscsi dep8 is currently
failing in Zesty. We can check to see that it passes in Xenial and
Yakkety before releasing to -updates. I would still expect future
initramfs-tools and isc-dhcp SRUs to be well tested in the development
release, however.

There is a whitespace indetation inconsistency in the diff, but this
went into zesty-proposed as well, and would create diff noise when
comparing that. The mistake's been made, so I'll leave it as is.

Similarly, the whitespace change dropping an extra space in an if
statement shouldn't really be part of the SRU, but I'll leave it as-is
in order to make progress.

** Changed in: open-iscsi (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags removed: verification-failed

** Tags added: verification-needed

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Triaged
Status in isc-dhcp source package in Xenial:
  In Progress
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  In Progress
Status in isc-dhcp source package in Yakkety:
  In Progress
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) 

  
  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

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

[bugproxy]

--- Comment From gmgay...@us.ibm.com 2016-11-09 10:52 EDT---
Hello Canonical,
Sending this bug to you for awareness and advice.

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

Title:
  MongoDB Memory corruption

Status in gcc-4.8 package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Calvin L. Sze  - 2016-11-01 23:09:10 ==
  Team has changed to the Bare-metal Ubuntu 16.4.  The problem still exists, so 
it is not related to the virtualization. 

  Since the bug is complicated to reproduce,  Could we use sets of tools
  to collect the data when this happens?

  
  ---Problem Description---
  MongoDB has memory corruption issues which only occurred on Ubuntu 16.04, it 
doesn't occur on Ubuntu 15.
   
  Contact Information =Calvin Sze/Austin/IBM
   
  ---uname output---
  Linux master 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:57 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Model: 2.1 (pvr 004b 0201) Model name: 
   POWER8E (raw), altivec supported 
   
  ---System Hang---
   the system is still alive
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Unfortunately, not very easily. I had a test case that I was running on 
ubuntu1604-ppc-dev.pic.build.10gen.cc and -ppc-dev.pic.build.10gen.cc. I 
understand these to be two VMs running on the same physical host.

  About 3.5% of the test runs on ubuntu1604-ppc-dev.pic.build.10gen.cc
  would fail, but all of the runs on the other machine passed.
  Originally, this failure manifested as the GCC stack protector (from
  -fstack-protector-strong) claiming stack corruption.

  Hoping to be able to see the data that was being written and
  corrupting the stack, I manually injected a guard region into the
  stack of the failing functions as follows:


  
  +namespace {
  +
  +class Canary {
  +public:
  +
  +static constexpr size_t kSize = 1024;
  +
  +explicit Canary(volatile unsigned char* const t) noexcept : _t(t) {
  +::memset(const_cast(_t), kBits, kSize);
  +}
  +
  +~Canary() {
  +_verify();
  +}
  +
  +private:
  +static constexpr uint8_t kBits = 0xCD;
  +static constexpr size_t kChecksum = kSize * size_t(kBits);
  +
  +void _verify() const noexcept {
  +invariant(std::accumulate(&_t[0], &_t[kSize], 0UL) == kChecksum);
  +}
  +
  +const volatile unsigned char* const _t;
  +};
  +
  +}  // namespace
  +

   Status bsonExtractField(const BSONObj& object, StringData fieldName, 
BSONElement* outElement) {
  +
  +volatile unsigned char* const cookie = static_cast(alloca(Canary::kSize));
  +const Canary c(cookie);
  + 

  When running with this, the invariant would sometimes fire. Examining
  the stack cookie under the debugger would show two consecutive bytes,
  always at an offset ending 0x...e, written as either 0 0, or 0 1,
  somewhere at random within the middle of the cookie.

  This indicated that it was not a conventional stack smash, where we
  were writing past the end of a contiguous buffer. Instead it appeared
  that either the currently running thread had reached up some arbitrary
  and random amount on the stack and done either two one-byte writes, or
  an unaligned 2-byte write. Another possibility was that a local
  variable had been transferred to another thread, which had written to
  it.

  However, while looking at the code to find such a thing, I realized
  that there was another possibility, which was that the bytes had never
  been written correctly in the first place. I changed the stack canary
  constructor to be:


  +explicit Canary(volatile unsigned char* const t) noexcept : _t(t) {
  +::memset(const_cast(_t), kBits, kSize);
  +_verify();
  +}  

  So that immediately after writing the byte pattern to the stack
  buffer, we verified the contents we wrote. Amazingly, this *failed*,
  with the same corruption as seen before. This means that either
  between the time we called memset to write the bytes and when we read
  them back, something either overwrote the stack cookie region, or that
  the bytes were never written correctly by memset, or that memset wrote
  the bytes, but the underlying physical memory never took the write.



   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: MongoDB 

  Userspace rpm: mongod 
   
  The userspace tool has the following bit modes: 64bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Lilian Romero/Austin/IBM: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace 

[Touch-packages] [Bug 1638929] Re: after disabling a display, enabling makes screens go black

[Jonas G. Drange]

> Is your backlight coming back on? If not then that part is a Mir bug.

The backlights are coming back online.

** Description changed:

  Reproduce:
  turn off then turn on some display (output.used = false then output.used = 
true)
  
  What happens:
  Turning off works fine, turning it back on does not
  
  What should happen:
  it should work as expected
  
  USC log: http://pastebin.ubuntu.com/23420797/
  Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/
+ Unity8 log (w debug): http://pastebin.ubuntu.com/23451437/

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

Title:
  after disabling a display, enabling makes screens go black

Status in Canonical System Image:
  New
Status in Light Display Manager:
  New
Status in Mir:
  Incomplete
Status in QtMir:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  turn off then turn on some display (output.used = false then output.used = 
true)

  What happens:
  Turning off works fine, turning it back on does not

  What should happen:
  it should work as expected

  USC log: http://pastebin.ubuntu.com/23420797/
  Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/
  Unity8 log (w debug): http://pastebin.ubuntu.com/23451437/

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

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

[Touch-packages] [Bug 1640518] [NEW] MongoDB Memory corruption

[bugproxy]

Public bug reported:

== Comment: #0 - Calvin L. Sze  - 2016-11-01 23:09:10 ==
Team has changed to the Bare-metal Ubuntu 16.4.  The problem still exists, so 
it is not related to the virtualization. 

Since the bug is complicated to reproduce,  Could we use sets of tools
to collect the data when this happens?


---Problem Description---
MongoDB has memory corruption issues which only occurred on Ubuntu 16.04, it 
doesn't occur on Ubuntu 15.
 
Contact Information =Calvin Sze/Austin/IBM
 
---uname output---
Linux master 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:57 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = Model: 2.1 (pvr 004b 0201) Model name:   
 POWER8E (raw), altivec supported 
 
---System Hang---
 the system is still alive
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 Unfortunately, not very easily. I had a test case that I was running on 
ubuntu1604-ppc-dev.pic.build.10gen.cc and -ppc-dev.pic.build.10gen.cc. I 
understand these to be two VMs running on the same physical host.

About 3.5% of the test runs on ubuntu1604-ppc-dev.pic.build.10gen.cc
would fail, but all of the runs on the other machine passed. Originally,
this failure manifested as the GCC stack protector (from -fstack-
protector-strong) claiming stack corruption.

Hoping to be able to see the data that was being written and corrupting
the stack, I manually injected a guard region into the stack of the
failing functions as follows:


+namespace {
+
+class Canary {
+public:
+
+static constexpr size_t kSize = 1024;
+
+explicit Canary(volatile unsigned char* const t) noexcept : _t(t) {
+::memset(const_cast(_t), kBits, kSize);
+}
+
+~Canary() {
+_verify();
+}
+
+private:
+static constexpr uint8_t kBits = 0xCD;
+static constexpr size_t kChecksum = kSize * size_t(kBits);
+
+void _verify() const noexcept {
+invariant(std::accumulate(&_t[0], &_t[kSize], 0UL) == kChecksum);
+}
+
+const volatile unsigned char* const _t;
+};
+
+}  // namespace
+

 Status bsonExtractField(const BSONObj& object, StringData fieldName, 
BSONElement* outElement) {
+
+volatile unsigned char* const cookie = static_cast(alloca(Canary::kSize));
+const Canary c(cookie);
+ 

When running with this, the invariant would sometimes fire. Examining
the stack cookie under the debugger would show two consecutive bytes,
always at an offset ending 0x...e, written as either 0 0, or 0 1,
somewhere at random within the middle of the cookie.

This indicated that it was not a conventional stack smash, where we were
writing past the end of a contiguous buffer. Instead it appeared that
either the currently running thread had reached up some arbitrary and
random amount on the stack and done either two one-byte writes, or an
unaligned 2-byte write. Another possibility was that a local variable
had been transferred to another thread, which had written to it.

However, while looking at the code to find such a thing, I realized that
there was another possibility, which was that the bytes had never been
written correctly in the first place. I changed the stack canary
constructor to be:


+explicit Canary(volatile unsigned char* const t) noexcept : _t(t) {
+::memset(const_cast(_t), kBits, kSize);
+_verify();
+}  

So that immediately after writing the byte pattern to the stack buffer,
we verified the contents we wrote. Amazingly, this *failed*, with the
same corruption as seen before. This means that either between the time
we called memset to write the bytes and when we read them back,
something either overwrote the stack cookie region, or that the bytes
were never written correctly by memset, or that memset wrote the bytes,
but the underlying physical memory never took the write.


 
Stack trace output:
 no
 
Oops output:
 no
 
Userspace tool common name: MongoDB 

Userspace rpm: mongod 
 
The userspace tool has the following bit modes: 64bit 
 
System Dump Info:
  The system is not configured to capture a system dump.

Userspace tool obtained from project website:  na 
 
*Additional Instructions for Lilian Romero/Austin/IBM: 
-Post a private note with access information to the machine that the bug is 
occuring on. 
-Attach sysctl -a output output to the bug.
-Attach ltrace and strace of userspace application.

== Comment: #1 - Luciano Chavez  - 2016-11-02 08:41:47 ==
Normally for userspace memory corruption type problems I would recommend 
Valgrind's memcheck tool though if this works on other versions of linux, one 
would want to compare the differences such as whether or not  you are using the 
same version of mongodb, gcc, glibc and the kernel. 

Has a standalone testcase been produced that shows the issue without
mongodb?

== Comment: #2 - Steven J. Munroe  - 2016-11-02 10:27:40 ==
We really need that standalone test case.

Need to look at WHAT c++ is doing with