[Touch-packages] [Bug 1639745] Re: Mir GL clients never appear at all on VirtualBox

[Daniel van Vugt]

** Branch linked: lp:~vanvugt/mir/log-unhandled-exceptions

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

Title:
  Mir GL clients never appear at all on VirtualBox

Status in Mir:
  In Progress
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Mir GL clients never appear at all on VirtualBox.

  After digging for a while, it appears the issue is that vboxvideo does
  not support DRM_CAP_PRIME and so only supports GEM flink names. Sadly
  Mir is the opposite now: Mir only supports PRIME but not flink names.

  Internally some exceptions are being thrown in Mir at present, but we
  seem to catch and silence them all. So you never see any error
  messages at all. Just Mir GL clients never appear on screen in
  VirtualBox.

  For the record, Wayland supports falling back to flink names in the
  absence of PRIME. We should too.

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

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

[Touch-packages] [Bug 1640290] Re: Update Qt to 5.7

[Dmitry Shachnev]

Note that in Debian we had to rush with a snapshot because of the
transition freeze. In Ubuntu it would make sense to at least wait until
5.7.1 final release.

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

Title:
  Update Qt to 5.7

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Tracking bug.

  https://people.canonical.com/~ubuntu-archive/transitions/html/html
  /qtbase-abi-5-7-1.html

  Debian successfully completed the 5.7 transition.

  Ubuntu PPA to be populated: https://bileto.ubuntu.com/#/ticket/1985
  More information: https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1640290] Re: Update Qt to 5.7

[Timo Jyrinki]

I unfortunately won't have time to properly work on this until January,
so help is welcome if you want to populate the PPA earlier. Qtbase is
now done, which is the biggest module, but all others and fixing the
builds of reverse dependencies is pending.

Thanks to my earlier started 5.7.0 work updating to 5.7.1 might not be
too problematic. 5.7.0 showed initially lots of problems, hopefully
5.7.1 fixes the upstream problems.

In addition to the packages in Debian, Ubuntu has the twin -gles Qt
module packages, ubuntu-ui-toolkit, ciborium, unity8 etc which are
needed to work before publishing the PPA to archives, as well as
autopkgtests.

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

Title:
  Update Qt to 5.7

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Tracking bug.

  https://people.canonical.com/~ubuntu-archive/transitions/html/html
  /qtbase-abi-5-7-1.html

  Debian successfully completed the 5.7 transition.

  Ubuntu PPA to be populated: https://bileto.ubuntu.com/#/ticket/1985
  More information: https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1640290] Re: Update Qt to 5.7

[Timo Jyrinki]

** Description changed:

  Tracking bug.
  
  https://people.canonical.com/~ubuntu-archive/transitions/html/html
  /qtbase-abi-5-7-1.html
  
  Debian successfully completed the 5.7 transition.
+ 
+ Ubuntu PPA to be populated: https://bileto.ubuntu.com/#/ticket/1985
+ More information: https://wiki.ubuntu.com/Touch/QtTesting

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

Title:
  Update Qt to 5.7

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Tracking bug.

  https://people.canonical.com/~ubuntu-archive/transitions/html/html
  /qtbase-abi-5-7-1.html

  Debian successfully completed the 5.7 transition.

  Ubuntu PPA to be populated: https://bileto.ubuntu.com/#/ticket/1985
  More information: https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1634220] Re: Wallpaper does not resize correctly when adding external display

[Andreas Büsching]

It looks like it is related to the positions of the two displays to each
other. I normally like the internal display to be below the external
one. By default it tries to layout the display next to each other. When
adding the external display I can see the wallpaper twice on the
external display. On the left the small one that should probably be
shown on the internal display and on the right side the large one that
should normally be used for the external display. After a few moments
the large one is shown on the exeternal display and the internal display
has a black background. When I switch to the virtual desktop on the
right side I do see the small wallpaper in the top left corner
surrounded by the flickering.

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

Title:
  Wallpaper does not resize correctly when adding external display

Status in Compiz:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I add a second (external) display to my laptop (Dell Latitude)
  the wallpaper/background is not resized correctly.

  1. just an internal display with a resolution of 1366x768
  2. adding an external display with a full HD resolution

  Adding the external display results in
  - the wallper is shown in the upper left corner of the external display 
(probably with the resolution of the internal display.
  - The rest of the screen is filled with random segments of windows that have 
been shown at these positions before
  - the internal display does not show any wallpaper (completely black)

  Additionally it looks like the left side panels (one for internal and
  one for external) are drawn over each other on the external display.
  See attachment Auswal_001.png

  Deactivating the internal display does not change anything

  Locking the screen shows a correctly resized wallpaper in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog: /dev/sda6: clean, 1281257/10911744 files, 22096310/43622400 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Oct 17 20:23:39 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.8.0-21-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04a9]
  InstallationDate: Installed on 2013-11-10 (1072 days ago)
  InstallationMedia: elementary OS 0.2 "Luna" - Stable amd64 (20130810)
  MachineType: Dell Inc. Latitude E6220
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=f1d78d25-23cf-4217-9db2-0750a8eb2b53 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0R97MN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/17/2012:svnDellInc.:pnLatitudeE6220:pvr01:rvnDellInc.:rn0R97MN:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6220
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1634220/+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 1618988] Re: unity8 goes to black screen 'n freeze after logout attempt

[Launchpad Bug Tracker]

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

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

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

Title:
  unity8 goes to black screen 'n freeze after logout attempt

Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  as in subject header ... when logging out of unity8 it will go to
  blackspace and freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160826-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 31 13:09:15 2016
  InstallationDate: Installed on 2016-08-31 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160616)
  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/1618988/+subscriptions

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

[Touch-packages] [Bug 1572653] Re: keyboard does not show up on xenial

[Kris]

I think that logically, if XMir is provided in the default image, the
maliit-inputcontext-gtk3 and maliit-inputcontext-gtk2 packages should be
included by default as well. They don't even weight anything, couple
hundreds of KB in total.

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

Title:
  keyboard does not show up on xenial

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Expected behaviour:

  Install ubuntu-keyboard, run maliit-server, click on place to enter
  text -> keyboard shows up.

  What happens:

  Running maliit-server after installing ubuntu-keyboard-english in
  terminal shows following error:

  WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const
  QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is
  not enabled

  Clicking on fields for entering text, does not cause the keyboard to
  show up.

  What I tried so far:

  export QT_IM_MODULE=Maliit
  export GTK_IM_MODULE=Maliit

  and

  gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled 
"[llibubuntu-keyboard-plugin.so,en_gb]"
  gconftool-2 -s --type list --list-type string /maliit/onscreen/active 
"[libubuntu-keyboard-plugin.so,en_gb]"

  according to

  https://github.com/maliit/framework

  and

  https://github.com/maliit/plugins

  but it still won't show up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 20 18:03:03 2016
  InstallationDate: Installed on 2016-04-03 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.maliit.org.server.conf: [modified]
  mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195

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

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

[Daniel van Vugt]

Fix committed to lp:mir/0.24 at revision 3644, scheduled for release in
Mir 0.24.2 (if that gets released)

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

** Branch unlinked: lp:mir/0.24

-- 
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 1638774] Re: Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-size array

[Launchpad Bug Tracker]

** Branch linked: lp:mir/0.24

-- 
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 1636473] Re: random cursor jumps when clicking on dell xps 13

[s.illes79]

Bug still happens with
- 16.10 Yakkety Yak 
- 14.04 Trusty - dell version ...

did not managed to test 17.04

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

Title:
  random cursor jumps when clicking on dell xps 13

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1 out of 20-40 clicks on the touch pad results in a pointer jump and a
  "random" click.

  Hard to reproduce, but mostly happens when I use my middle finger to
  move the cursor and click with index finger. Sometimes the double
  touch of middle/index finger is interpreted as mouse move, the jump is
  more or less the same distance as if i had moved the index to the
  middle finger position.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 25 22:04:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0704]
  InstallationDate: Installed on 2016-09-08 (46 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=fe8099eb-a258-42d6-8f67-69496f1e0fcf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Oct 22 20:20:44 2016
  xserver.configfile: default
  xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.1

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

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

You seem to have two graphics cards installed - Nvidia and AMD. Which
one is plugged in and not working?


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/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 1639674] Re: tearing

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-367
(Ubuntu)

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

Title:
  tearing

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  New

Bug description:
  Video tearing is all time. Nvidia and novus drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .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
  CurrentDesktop: Unity
  Date: Mon Nov  7 05:13:25 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-22-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.8.0-22-generic, x86_64: installed
   nvidia-367, 367.57, 4.8.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 520 [1043:1ccd]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a]
  InstallationDate: Installed on 2016-11-07 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: ASUSTeK COMPUTER INC. X555UB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=16c193c2-1248-47f0-91ce-31ece06b8894 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.300:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  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: Mon Nov  7 05:08:52 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1639674/+subscriptions

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

[Touch-packages] [Bug 1522675] Re: Can't drop privileges for downloading : _apt user not allowed

[kroenecker]

Check to see if you have an _apt user:

cat /etc/passwd | grep apt

_apt:x:105:65534::/nonexistent:/bin/false

If you do, no need to add the user.  Otherwise,

adduser --force-badname --system --home /nonexistent --no-create-home
--quiet _apt || true

I haven't verified that it creates precisely the user necessary.  If I
remember correctly, /bin/false means no shell access so make sure the
user created does in fact have /bin/false in passwd.  Also it has no
group (65534).  That is it really.

Finally check the directory situation:

ls -la /var/lib/update-notifier/package-data-downloads/

drwxr-xr-x 2 _apt root 4096 Nov  9 10:23 partial

As you can see "_apt" is properly listed as the owner.  If not,

sudo chown _apt /var/lib/update-notifier/package-data-downloads/partial/

My system already had an _apt user, but did not have proper directory
permissions.  At least, I have to assume that this is a proper fix.  If
not, somebody more knowledgeable should be speaking up and sorting this
out...

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

Title:
  Can't drop privileges for downloading : _apt user not allowed

Status in apt package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1639695] Re: package dbus 1.10.6-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package dbus 1.10.6-1ubuntu3.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Sun Nov  6 21:48:29 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-18 (49 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: dbus
  Title: package dbus 1.10.6-1ubuntu3.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dimitri John Ledkov]

Adding taglib task for inspection, there was a big version bump in
taglib in zesty from 1.9 -> 1.11

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

-- 
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 1638774] Re: Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-size array

[Daniel van Vugt]

** Also affects: mir/0.24
   Importance: Undecided
   Status: New

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

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

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

** Changed in: mir/0.24
   Importance: Undecided => Critical

** Changed in: mir/0.24
   Status: New => Triaged

** Changed in: mir/0.24
Milestone: None => 0.24.2

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Triaged
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 1637205] Re: Side stage available in portrait

[Daniel van Vugt]

** Summary changed:

- Side stage available  in portrait
+ Side stage available in portrait

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

Title:
  Side stage available in portrait

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

Bug description:
  bq M10 rc-proposed r219

  It is possible to create the side stage in when the tablet is in portrait 
orientation.
  1. Turn the tablet to portrait
  2. Open an app
  3. Use 3 fingers drag to move the app to the side stage
  Result attached

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

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

[Touch-packages] [Bug 1640322] Re: FTBFS in zesty on armhf arm64 only

[Daniel van Vugt]

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

Duplicate of bug 1638774

** This bug has been marked a duplicate of bug 1638774
   Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-size 
array

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

Title:
  FTBFS in zesty on armhf arm64 only

Status in mir package in Ubuntu:
  New

Bug description:
  A no change rebuild of mir failed on armhf/arm64 in zesty

  Please see build logs at:
  https://launchpad.net/ubuntu/+source/mir/0.24.1+16.10.20160928-0ubuntu2

  Please help to fix this issue.

  
  n file included from 
/<>/mir-0.24.1+16.10.20160928/tests/mir_test_doubles/stub_buffer.cpp:22:0:
  
/<>/mir-0.24.1+16.10.20160928/tests/include/mir/test/doubles/stub_android_native_buffer.h:54:21:
 error: invalid use of ‘struct native_handle’ with a zero-size array in ‘struct 
mir::test::doubles::StubAndroidNativeBuffer’ [-Werror=pedantic]
   native_handle_t native_handle;
   ^
  In file included from /usr/include/android-23/system/window.h:20:0,
   from 
/<>/mir-0.24.1+16.10.20160928/src/platforms/android/include/native_buffer.h:23,
   from 
/<>/mir-0.24.1+16.10.20160928/tests/include/mir/test/doubles/stub_android_native_buffer.h:22,
   from 
/<>/mir-0.24.1+16.10.20160928/tests/mir_test_doubles/stub_buffer.cpp:22:
  /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 */
 ^
  [ 38%] Building CXX object 
src/server/frontend/CMakeFiles/mirfrontend.dir/default_ipc_factory.cpp.o
  cd 
/<>/mir-0.24.1+16.10.20160928/obj-aarch64-linux-gnu/src/server/frontend
 && /usr/bin/c++   -DLOG_NDEBUG=1 -DMESA_EGL_NO_X11_HEADERS 
-DMIR_LOG_COMPONENT_FALLBACK=\"mirserver\" 
-DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API 
-DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT 
-DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" 
-DMIR_SERVER_GRAPHICS_PLATFORM_VERSION=\"MIR_GRAPHICS_PLATFORM_0.24\" 
-DMIR_SERVER_INPUT_PLATFORM_VERSION=\"MIR_INPUT_PLATFORM_0.19\" 
-DMIR_SERVER_PLATFORM_PATH=\"/usr/lib/aarch64-linux-gnu/mir/server-platform\" 
-DMIR_VERSION=\"0.24.1\" -DMIR_VERSION_MAJOR=0 -DMIR_VERSION_MICRO=1 
-DMIR_VERSION_MINOR=24 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE 
-I/<>/mir-0.24.1+16.10.20160928/include/common 
-I/<>/mir-0.24.1+16.10.20160928/include/cookie 
-I/<>/mir-0.24.1+16.10.20160928/src/include/common 
-I/<>/mir-0.24.1+16.10.20160928/obj-aarch64-linux-gnu/src/protobuf 
-I/<>/mir-0.24.1+16.10.20160928/include/platform 
-I/<>/mir-0.24.1+16.10.20160928/include/client 
-I/<>/mir-0.24.1+16.10.20160928/include/server 
-I/<>/mir-0.24.1+16.10.20160928/include/renderers/gl 
-I/<>/mir-0.24.1+16.10.20160928/src/include/platform 
-I/<>/mir-0.24.1+16.10.20160928/src/include/client 
-I/<>/mir-0.24.1+16.10.20160928/src/include/server 
-I/<>/mir-0.24.1+16.10.20160928/src/include/cookie 
-I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include  -g -O2 
-fdebug-prefix-map=/<>/mir-0.24.1+16.10.20160928=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing 
-pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects   -o 
CMakeFiles/mirfrontend.dir/default_ipc_factory.cpp.o -c 
/<>/mir-0.24.1+16.10.20160928/src/server/frontend/default_ipc_factory.cpp
  cc1plus: all warnings being treated as errors
  tests/mir_test_doubles/CMakeFiles/mir-public-test-doubles.dir/build.make:161: 
recipe for target 
'tests/mir_test_doubles/CMakeFiles/mir-public-test-doubles.dir/stub_buffer.cpp.o'
 failed
  make[3]: *** 
[tests/mir_test_doubles/CMakeFiles/mir-public-test-doubles.dir/stub_buffer.cpp.o]
 Error 1
  make[3]: Leaving directory 
'/<>/mir-0.24.1+16.10.20160928/obj-aarch64-linux-gnu'
  CMakeFiles/Makefile2:11488: recipe for target 
'tests/mir_test_doubles/CMakeFiles/mir-public-test-doubles.dir/all' failed
  make[2]: *** 
[tests/mir_test_doubles/CMakeFiles/mir-public-test-doubles.dir/all] Error 2
  make[2]: *** Waiting for unfinished jobs

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

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

[Scott Moser]

the suggested further changes here make the ipv4 path basically not
touched.


** Patch added: "suggested further changes"
   
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507/+attachment/4774679/+files/out.diff

-- 
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:
  In Progress
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:
  In Progress
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] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Scott Moser]

I just had the thought.. is there any reason that we are using dhclient
for ipv4 rather than leaving the old path in place entirely for ip= ?

If we just change back to letting klibc's ipconfig take care of the ipv4
dhcp, then that resolves my 'b' and 'c' (for the ipv4 case).

We can then also go back to the original test for "done" of just
checking for presense of /run/net-"$DEVICE".conf to idnicate ipv4 is
done.  All in all, the change to taking 'ip6=' on the command line makes
it fairly easy to ensure we do not regress the ipv4 use case.

-- 
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:
  In Progress
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:
  In Progress
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 1508905] Re: Graphics disorder, a large "claw" ('>') appearing

[Michał Sawicz]

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

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

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

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

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

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Albert Astals Cid (aacid)

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

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

Title:
  Graphics disorder, a large "claw" ('>') appearing

Status in Canonical System Image:
  In Progress
Status in Today Scope:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Hi,

  Currently I have this bug. It was already present in the OTA-6.
  Usually a reboot fix the problem, but after a while it come back
  again.

  It only appears ate the bottom of the scope! If I swipe back to the
  top the "claw" fade out.

  I've attached a screenshot.

  Thanks!

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

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

[Touch-packages] [Bug 1378814] Re: greeter does not properly update infographic after unlock

[Michał Sawicz]

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Tomás Tormo (tomas-tormo)

** Changed in: canonical-devices-system-image
 Assignee: Pat McGowan (pat-mcgowan) => Michał Sawicz (saviq)

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

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

Title:
  greeter does not properly update infographic after unlock

Status in Band-aids for Ubuntu Phone:
  In Progress
Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  This bug has been here since forever, but really needs to get cleaned
  up for rtm.

  Steps to reproduce:
  - send 2 text messages
  - lock your phone
  - unlock your phone
  - confirm infographic says "2 text messages sent today"
  - lock your phone for the night and go to sleep
  - unlock your phone the next day

  Expected results:
  - infographic should be cleared, or show relevant information for today

  Actual results:
  - infographic still says "2 text messages sent today"

  When the phone is unlocked the greeter should update the infographic
  text

To manage notifications about this bug go to:
https://bugs.launchpad.net/band-aids-uphone/+bug/1378814/+subscriptions

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

[Touch-packages] [Bug 1607427] Re: super key not showing scopes home

[Michał Sawicz]

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

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

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

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

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

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

Title:
  super key not showing scopes home

Status in Canonical System Image:
  In Progress
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Hey,

  if I press super key, the scopes home does not appear. In OTA-11 it
  worked as it should, but in OTA-12 it doesn't work.

  I use M10 FHD tablet with OTA-12 and external keyboard Logitech k810.

  Thanks

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

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

[Touch-packages] [Bug 1637712] Re: Pixelated icon in notification bubble

[Michał Sawicz]

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

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

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

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

Title:
  Pixelated icon in notification bubble

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

Bug description:
  bq M10 rc-proposed r220 and bq e4.5 OTA13

  Icon visible in the notification bubble looks pixelated. Screenshot
  attached.

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

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

[Touch-packages] [Bug 1622423] Re: My activity child link disappears after logged in fitbit account

[Michał Sawicz]

** Changed in: unity-scopes-shell (Ubuntu)
   Status: New => Invalid

** Changed in: today-scope
   Status: Confirmed => Invalid

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

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

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

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

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

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

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

Title:
  My activity child link disappears after logged in fitbit account

Status in Canonical System Image:
  In Progress
Status in Today Scope:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  $ system-image-cli -i
  current build number: 15
  device name: turbo
  channel: ubuntu-touch/rc/meizu-pd.en
  last update: 2016-09-05 03:19:44
  version version: 15
  version ubuntu: 20160903
  version tag: OTA-13-rc
  version device: 20160824-d33b825
  version custom: 20160831-992-8-12

  The child arrow link of My Activity session disappears once logged in
  fitbit account in Today scope, so unable to open My Activity child
  scope from Today scope

  Steps to reproduce:
  1. Open Today scope and navigate to My Activity session, 
  2. Existing a child link, tap it will open My Activity scope
  2. Tap 'Add your fitbit account' and login with Google account
  3. Once logged in, back to Today scope and refresh, check if the child link 
still exist.

  Actual results:
  Once logged in fitbit account, some items of fitbit displayed in session, but 
the child scope link has gone, unable to open My Activity scope from Today scope
  If open My Activity scope from manage page by swiping up, blank scope page 
shown

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

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

[Touch-packages] [Bug 1637502] Re: Keyboard stays on screen when doing spread

[Michał Sawicz]

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

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

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

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

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

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

Title:
  Keyboard stays on screen when doing spread

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

Bug description:
  bq M10 rc-proposed r220

  If the OSK is visible and I'm starting to do swipe from the right, I
  expect OSK to hide. Meanwhile the OSK hides only when the spread is
  complete and I take my finger off the screen.

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

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

[Touch-packages] [Bug 1637249] Re: Removing app from the spread closes the spread

[Michał Sawicz]

** Changed in: canonical-devices-system-image
   Status: Triaged => In Progress

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

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

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

Title:
  Removing app from the spread closes the spread

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

Bug description:
  bq M10 rc-proposed r219

  Steps to reproduce
  1 open 3 apps
  2 put one of them in the side stage
  3 do the spread
  4 swipe out the app which was in the side stage

  Expected result
  The spread stays

  What happens instead
  The spread closes and only one app is visible

  What I've noticed: if you swipe an app which was not in the side
  stage, the spread stays just fine. Also if there is more than one app
  in the side stage and you swipe one of them, the spread stays. It
  seems it closes only if there's one app in the side stage.

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

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

[Touch-packages] [Bug 1637258] Re: Side stage hides after rotating

[Michał Sawicz]

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

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

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

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

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

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

Title:
  Side stage hides after rotating

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

Bug description:
  bq M10 rc-proposed r219

  Steps to reproduce:
  1. Open an app
  2. Put it in the side stage
  3. Rotate the tablet to portrait
  At this point you should see the app which was in the side stage on the whole 
screen
  4. Rotate the tablet back to landscape

  Expected result:
  The app is visible in the side stage

  What happens instead:
  The side stage is closed but the app still has focus as its name is visible 
in the top bar (screenshot attached)

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

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

[Touch-packages] [Bug 1637205] Re: Side stage available in portrait

[Michał Sawicz]

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

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

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

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

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

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

Title:
  Side stage available  in portrait

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

Bug description:
  bq M10 rc-proposed r219

  It is possible to create the side stage in when the tablet is in portrait 
orientation.
  1. Turn the tablet to portrait
  2. Open an app
  3. Use 3 fingers drag to move the app to the side stage
  Result attached

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

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

[Touch-packages] [Bug 1638848] Re: [unity8][app switcher] apps previews are active in mid animation

[Michał Sawicz]

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

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

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

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

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

Title:
  [unity8][app switcher] apps previews are active in mid animation

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

Bug description:
  [unity8][app switcher] apps previews are active in mid animation

  swipe from the right to trigger the app switcher and drag to the left
  but don't let go (keep teh finger on the screen) and with your other
  finger tap on an icon in apps scope for ex, you'll launch and app and
  the preview will look weird. same with other apps you can tap inside
  em.

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

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

[Touch-packages] [Bug 1640345] Re: Please check about these issues

[Paul White]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.

We'd be grateful if you would then provide a more complete description
of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

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

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

Title:
  Please check about these issues

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Please check about these issues

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov  9 00:18:36 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
  InstallationDate: Installed on 2016-08-24 (76 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug=1 quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.04
  dmi.board.name: Newark
  dmi.board.vendor: FOXCONN
  dmi.board.version: HP P/N
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: NQ918AA-ABZ CQ5023IT
  dmi.sys.vendor: Compaq-Presario
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Nov  8 19:35:43 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)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login

[Ads20000]

First time I restarted (after running Update Manager), the menus were
still broken. Second time I restarted (didn't update), they were fine.
Third time I restarted (after sudo apt update ; sudo apt dist-upgrade),
they were broken again. Fourth time I restarted (didn't update), they
were fine. Fifth time I restarted, also fine. Sixth time, also fine.
Seventh time (after sudo apt update ; sudo apt dist-upgrade), also fine.

Systemd version: 232-2git1
Lightdm version: 1.20.0-0ubuntu2

I've attached a list of changes made by Apt and reboot times.

Can people try rebooting a few times and see if they can try and
reproduce the bug (at least, the one in my duplicates)?

** Attachment added: "1637758 - Terminal output of recent changes made by Apt"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637758/+attachment/4774658/+files/1637758%20-%20Terminal%20output%20of%20recent%20changes%20made%20by%20Apt

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

Title:
  lightdm greeter session not properly shut down at login

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  I am using lightdm with 2 seats. After 2409 revision randomly one of
  two seats does not work correctly.

  xsettings plugin from unity-settings-daemon or gnome-settings-deamon
  fails to start because there is already _XSESSION_S* manager running.

  After revision 2409 in system monitor I see that there is still
  running unity-settings-daemon started by lightdm. Reverting this
  revision fixes my problem.

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

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

[Touch-packages] [Bug 1640345] [NEW] Please check about these issues

[giorgio]

Public bug reported:

Please check about these issues

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
Uname: Linux 4.4.0-46-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Nov  9 00:18:36 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
InstallationDate: Installed on 2016-08-24 (76 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
ProcEnviron:
 LANGUAGE=it_IT
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug=1 quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.04
dmi.board.name: Newark
dmi.board.vendor: FOXCONN
dmi.board.version: HP P/N
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: NQ918AA-ABZ CQ5023IT
dmi.sys.vendor: Compaq-Presario
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Nov  8 19:35:43 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)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: nouveau

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  Please check about these issues

Status in xorg package in Ubuntu:
  New

Bug description:
  Please check about these issues

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov  9 00:18:36 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
  InstallationDate: Installed on 2016-08-24 (76 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug=1 quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.04
  dmi.board.name: Newark
  dmi.board.vendor: FOXCONN
  dmi.board.version: HP P/N
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: NQ918AA-ABZ CQ5023IT
  dmi.sys.vendor: Compaq-Presario
  version.compiz: 

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

[Michi Henning]

Unfortunately, just suppressing the Qt tests doesn't fix this. It turns
out that, on zesty, the tests for all architectures fail. It looks like
a problem with taglib. Every test that tries to extract artwork from an
ogg video file fails.

There is also a segfault in the thumbnailer test. That failure is either
caused by a problem with max_size_in_bytes(), or by a problem in
gsettings on zesty. Need to follow up.

There are also a bunch of gstreamer critical messages in the test log:

10: (vs-thumb:9542): GStreamer-CRITICAL **: Registering meta implementation 
'GstVideoMeta' without init function
10: thumbnailer-service: [22:50:37.499] "thumbnail: 
/<>/thumbnailer-2.4+17.04.20161108/tests/media/testvideo.ogg 
(256,256): 0.832444 [q: 0.01, d: 0.524390] sec (MISS)"

These are not normal, need to figure out what is going on there.

It doesn't look like this will be a quick fix :-(

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

Title:
  FTBFS on zesty

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/thumbnailer/+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 1576539] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Mikkel Kirkgaard Nielsen]

Follow up to my comment #7:

Inspecting log files I find what to me looks like a bad recursion in
dependency checking when setting up the package gcr (GNOME crypto
services). The apt-term log shows 50 of the same error message about
unability to run triggers for gconf2 because python3 is unconfigured.

/var/log/dist-upgrade/apt-term.log:
---
Setting up dbus (1.10.6-1ubuntu3.1) ...
A reboot is required to replace the running dbus-daemon.
Please reboot the system when convenient.
Removing obsolete conffile /etc/dbus-1/session.conf ...
Removing obsolete conffile /etc/dbus-1/system.conf ...
Setting up dbus-x11 (1.10.6-1ubuntu3.1) ...
Setting up gcr (3.18.0-1ubuntu1) ...
dpkg: dependency problems prevent processing triggers for gconf2:
 gconf2 depends on python3; however:
  Package python3 is not configured yet.

* repeats 50 times 
dpkg: error processing package gconf2 (--configure):
 dependency problems - leaving triggers unprocessed
dpkg: dependency problems prevent processing triggers for gconf2:
 gconf2 depends on python3; however:
  Package python3 is not configured yet.
*

dpkg: error processing package gconf2 (--configure):
 dependency problems - leaving triggers unprocessed
dpkg: too many errors, stopping
Errors were encountered while processing:
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
 gconf2
Processing was halted because there were too many errors.
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database 
... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading 
database ... 40%^M(Reading database ... 45%^M(Reading database ... 
50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database 
... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading 
database ... 80%^M(Reading database ... 85%^M(Reading database ... 
90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database 
... 278060 files and directories currently installed.)
Preparing to unpack .../gnupg2_2.1.11-6ubuntu2_amd64.deb ...
---

The unconfigured gconf2 state looks like it generates a cascade of dependency 
errors in subsequent packages, from the main log 
/var/log/dist-upgrade/main.log; 
---
2016-11-08 12:14:00,647 ERROR got an error from dpkg for pkg: 'gconf2': 
'dependency problems - leaving triggers unprocessed'
2016-11-08 12:14:00,648 DEBUG running apport_pkgfailure() gconf2: dependency 
problems - leaving triggers unprocessed
2016-11-08 12:14:00,657 ERROR got an error from dpkg for pkg: 'gconf2': 
'dependency problems - leaving triggers unprocessed'
2016-11-08 12:36:56,197 WARNING no activity on terminal for 300 seconds 
(Installed libsecret-common (amd64))
2016-11-08 12:36:56,377 ERROR got an error from dpkg for pkg: 'gnupg2': 
'dependency problems - leaving unconfigured'
2016-11-08 12:36:56,377 DEBUG running apport_pkgfailure() gnupg2: dependency 
problems - leaving unconfigured
2016-11-08 12:36:56,377 DEBUG dpkg error because of dependency problems, not 
reporting against gnupg2 
2016-11-08 12:36:56,377 ERROR got an error from dpkg for pkg: 'gnupg2': 
'dependency problems - leaving unconfigured'
2016-11-08 12:47:33,520 ERROR got an error from dpkg for pkg: 'gnome-keyring': 
'dependency problems - leaving unconfigured'
2016-11-08 12:47:33,520 DEBUG running apport_pkgfailure() gnome-keyring: 
dependency problems - leaving unconfigured
2016-11-08 12:47:33,520 DEBUG dpkg error because of dependency problems, not 
reporting against gnome-keyring 
2016-11-08 12:47:33,520 ERROR got an error from dpkg for pkg: 'gnome-keyring': 
'dependency problems - leaving unconfigured'
2016-11-08 12:47:33,531 ERROR got an error from dpkg for pkg: 
'evolution-data-server': 'dependency problems - leaving unconfigured'
2016-11-08 12:47:33,531 DEBUG running apport_pkgfailure() 
evolution-data-server: dependency problems - leaving unconfigured
2016-11-08 12:47:33,531 DEBUG dpkg error because of dependency problems, not 
reporting against evolution-data-server 
2016-11-08 12:47:33,531 ERROR got an error from dpkg for pkg: 
'evolution-data-server': 'dependency problems - leaving unconfigured'
2016-11-08 12:47:33,728 ERROR got an error from dpkg for pkg: 'libfolks-eds25': 
'76.5689:dependency problems - leaving unconfigured'
2016-11-08 12:47:33,728 DEBUG running apport_pkgfailure() libfolks-eds25: 
76.5689:dependency problems - leaving unconfigured
2016-11-08 12:47:33,728 DEBUG dpkg error because of dependency problems, not 
reporting against libfolks-eds25 
2016-11-08 12:47:33,728 ERROR got an error from dpkg for pkg: 'libfolks-eds25': 

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

[Sander Jonkers]

@Hansen ... I did that, did a reboot, did a suspend/resume (arrows
appeared), and the logging is 1997 lines long. Can you advice what to do
with that logging?

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

Title:
  cannot view wifi networks after re-enabling wifi

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

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

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

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

[Touch-packages] [Bug 1640330] Re: I don't know

[Paul White]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.

We'd be grateful if you would then provide a more complete description
of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

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

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

Title:
  I don't know

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm sorry I do't know

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Nov  8 20:31:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
  InstallationDate: Installed on 2016-08-24 (75 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug=1 quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.04
  dmi.board.name: Newark
  dmi.board.vendor: FOXCONN
  dmi.board.version: HP P/N
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: NQ918AA-ABZ CQ5023IT
  dmi.sys.vendor: Compaq-Presario
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Nov  8 19:35:43 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)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1640330] [NEW] I don't know

[giorgio]

Public bug reported:

I'm sorry I do't know

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
Uname: Linux 4.4.0-46-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Nov  8 20:31:22 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
InstallationDate: Installed on 2016-08-24 (75 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
ProcEnviron:
 LANGUAGE=it_IT
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug=1 quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.04
dmi.board.name: Newark
dmi.board.vendor: FOXCONN
dmi.board.version: HP P/N
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: NQ918AA-ABZ CQ5023IT
dmi.sys.vendor: Compaq-Presario
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Nov  8 19:35:43 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)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: nouveau

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  I don't know

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm sorry I do't know

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Nov  8 20:31:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
  InstallationDate: Installed on 2016-08-24 (75 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug=1 quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.04
  dmi.board.name: Newark
  dmi.board.vendor: FOXCONN
  dmi.board.version: HP P/N
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: NQ918AA-ABZ CQ5023IT
  dmi.sys.vendor: Compaq-Presario
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 

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

[Michi Henning]

Fix is in a silo: https://bileto.ubuntu.com/#/ticket/2175

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

Title:
  FTBFS on zesty

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/thumbnailer/+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]

Thanks for that, will fix now.

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

Title:
  FTBFS on zesty

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/thumbnailer/+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 1638586] Re: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Michi Henning]

Looks like this is caused by packages installed in /usr/local that
conflict with click.

** Changed in: unity-scopes-api (Ubuntu)
   Status: New => Invalid

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

Title:
  package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unity-scopes-api package in Ubuntu:
  Invalid

Bug description:
  no se instalo al actualizar version

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 03:56:47 2016
  DuplicateSignature:
   package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2
   Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-04 (211 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1638586/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] FTBFS on zesty

[Dimitri John Ledkov]

Public bug reported:

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

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


** Tags: boost1.62 ftbfs zesty

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

Title:
  FTBFS on zesty

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/thumbnailer/+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 1640322] [NEW] FTBFS in zesty on armhf arm64 only

[Dimitri John Ledkov]

Public bug reported:

A no change rebuild of mir failed on armhf/arm64 in zesty

Please see build logs at:
https://launchpad.net/ubuntu/+source/mir/0.24.1+16.10.20160928-0ubuntu2

Please help to fix this issue.


n file included from 
/<>/mir-0.24.1+16.10.20160928/tests/mir_test_doubles/stub_buffer.cpp:22:0:
/<>/mir-0.24.1+16.10.20160928/tests/include/mir/test/doubles/stub_android_native_buffer.h:54:21:
 error: invalid use of ‘struct native_handle’ with a zero-size array in ‘struct 
mir::test::doubles::StubAndroidNativeBuffer’ [-Werror=pedantic]
 native_handle_t native_handle;
 ^
In file included from /usr/include/android-23/system/window.h:20:0,
 from 
/<>/mir-0.24.1+16.10.20160928/src/platforms/android/include/native_buffer.h:23,
 from 
/<>/mir-0.24.1+16.10.20160928/tests/include/mir/test/doubles/stub_android_native_buffer.h:22,
 from 
/<>/mir-0.24.1+16.10.20160928/tests/mir_test_doubles/stub_buffer.cpp:22:
/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 */
   ^
[ 38%] Building CXX object 
src/server/frontend/CMakeFiles/mirfrontend.dir/default_ipc_factory.cpp.o
cd 
/<>/mir-0.24.1+16.10.20160928/obj-aarch64-linux-gnu/src/server/frontend
 && /usr/bin/c++   -DLOG_NDEBUG=1 -DMESA_EGL_NO_X11_HEADERS 
-DMIR_LOG_COMPONENT_FALLBACK=\"mirserver\" 
-DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API 
-DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT 
-DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" 
-DMIR_SERVER_GRAPHICS_PLATFORM_VERSION=\"MIR_GRAPHICS_PLATFORM_0.24\" 
-DMIR_SERVER_INPUT_PLATFORM_VERSION=\"MIR_INPUT_PLATFORM_0.19\" 
-DMIR_SERVER_PLATFORM_PATH=\"/usr/lib/aarch64-linux-gnu/mir/server-platform\" 
-DMIR_VERSION=\"0.24.1\" -DMIR_VERSION_MAJOR=0 -DMIR_VERSION_MICRO=1 
-DMIR_VERSION_MINOR=24 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE 
-I/<>/mir-0.24.1+16.10.20160928/include/common 
-I/<>/mir-0.24.1+16.10.20160928/include/cookie 
-I/<>/mir-0.24.1+16.10.20160928/src/include/common 
-I/<>/mir-0.24.1+16.10.20160928/obj-aarch64-linux-gnu/src/protobuf 
-I/<>/mir-0.24.1+16.10.20160928/include/platform 
-I/<>/mir-0.24.1+16.10.20160928/include/client 
-I/<>/mir-0.24.1+16.10.20160928/include/server 
-I/<>/mir-0.24.1+16.10.20160928/include/renderers/gl 
-I/<>/mir-0.24.1+16.10.20160928/src/include/platform 
-I/<>/mir-0.24.1+16.10.20160928/src/include/client 
-I/<>/mir-0.24.1+16.10.20160928/src/include/server 
-I/<>/mir-0.24.1+16.10.20160928/src/include/cookie 
-I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include  -g -O2 
-fdebug-prefix-map=/<>/mir-0.24.1+16.10.20160928=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing 
-pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects   -o 
CMakeFiles/mirfrontend.dir/default_ipc_factory.cpp.o -c 
/<>/mir-0.24.1+16.10.20160928/src/server/frontend/default_ipc_factory.cpp
cc1plus: all warnings being treated as errors
tests/mir_test_doubles/CMakeFiles/mir-public-test-doubles.dir/build.make:161: 
recipe for target 
'tests/mir_test_doubles/CMakeFiles/mir-public-test-doubles.dir/stub_buffer.cpp.o'
 failed
make[3]: *** 
[tests/mir_test_doubles/CMakeFiles/mir-public-test-doubles.dir/stub_buffer.cpp.o]
 Error 1
make[3]: Leaving directory 
'/<>/mir-0.24.1+16.10.20160928/obj-aarch64-linux-gnu'
CMakeFiles/Makefile2:11488: recipe for target 
'tests/mir_test_doubles/CMakeFiles/mir-public-test-doubles.dir/all' failed
make[2]: *** 
[tests/mir_test_doubles/CMakeFiles/mir-public-test-doubles.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs

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


** Tags: arm64 armhf boost1.62 ftbfs zesty

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

Title:
  FTBFS in zesty on armhf arm64 only

Status in mir package in Ubuntu:
  New

Bug description:
  A no change rebuild of mir failed on armhf/arm64 in zesty

  Please see build logs at:
  https://launchpad.net/ubuntu/+source/mir/0.24.1+16.10.20160928-0ubuntu2

  Please help to fix this issue.

  
  n file included from 
/<>/mir-0.24.1+16.10.20160928/tests/mir_test_doubles/stub_buffer.cpp:22:0:
  
/<>/mir-0.24.1+16.10.20160928/tests/include/mir/test/doubles/stub_android_native_buffer.h:54:21:
 error: invalid use of ‘struct native_handle’ with a zero-size array in ‘struct 
mir::test::doubles::StubAndroidNativeBuffer’ [-Werror=pedantic]
   native_handle_t native_handle;
   ^
  In file included from /usr/include/android-23/system/window.h:20:0,
   from 
/<>/mir-0.24.1+16.10.20160928/src/platforms/android/include/native_buffer.h:23,
   from 

[Touch-packages] [Bug 1640320] [NEW] FTBFS in zesty

[Dimitri John Ledkov]

Public bug reported:

FTBFS in zesty during a no change rebuild against new boost

Please see build logs at: https://launchpad.net/ubuntu/+source/location-
service/3.0.0+16.10.20160912-0ubuntu2

Please help fix this

[ 10%] Building CXX object 
src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
cd 
/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location
 && /usr/bin/g++   -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 
-DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS 
-Dubuntu_location_service_connectivity_EXPORTS 
-I/<>/location-service-3.0.0+16.10.20160912/3rd-party 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/json-c 
-I/<>/location-service-3.0.0+16.10.20160912/include/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/src/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service
 -I/usr/include/ubuntu  -g -O2 
-fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra 
-fPIC -Wno-error=unused-local-typedefs -fPIC   -o 
CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
 -c 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp
In file included from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0,
 from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19:
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14:
 error: ‘vector’ in namespace ‘std’ does not name a template type
 std::vector xtra_hosts
  ^~
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10:
 warning: extra ‘;’ [-Wpedantic]
 };
  ^
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18:
 error: ‘vector’ in namespace ‘std’ does not name a template type
 virtual std::vector download_xtra_data(const Configuration& config) 
= 0;
  ^~
make -f po/CMakeFiles/pofiles_70.dir/build.make 
po/CMakeFiles/pofiles_70.dir/depend

** Affects: location-service (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: boost1.62 ftbfs zesty

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

Title:
  FTBFS in zesty

Status in location-service package in Ubuntu:
  New

Bug description:
  FTBFS in zesty during a no change rebuild against new boost

  Please see build logs at: https://launchpad.net/ubuntu/+source
  /location-service/3.0.0+16.10.20160912-0ubuntu2

  Please help fix this

  [ 10%] Building CXX object 
src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
  cd 
/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location
 && /usr/bin/g++   -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 
-DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS 
-Dubuntu_location_service_connectivity_EXPORTS 
-I/<>/location-service-3.0.0+16.10.20160912/3rd-party 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/json-c 
-I/<>/location-service-3.0.0+16.10.20160912/include/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/src/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service
 -I/usr/include/ubuntu  -g -O2 
-fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra 
-fPIC -Wno-error=unused-local-typedefs -fPIC   -o 
CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
 -c 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp
  In file included from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0,
   from 

[Touch-packages] [Bug 1370008] Re: URL Dispatcher Should Prompt on Bad URL

[Launchpad Bug Tracker]

This bug was fixed in the package url-dispatcher -
0.1+17.04.20161107-0ubuntu1

---
url-dispatcher (0.1+17.04.20161107-0ubuntu1) zesty; urgency=medium

  [ Florian Boucault ]
  * Crossbuilding Fixes

  [ Larry Price ]
  * App ID should allow package names with dots. (LP: #1591342) (LP: #1606498)

  [ Ted Gould ]
  * Check versions of appid:// urls to reduce the number of invalid appids
we send to UAL (LP: #1352656)
  * Scope testing for the scope:// URL and overlays that should be over
the dash
  * Protect the dash from getting NULL urls (LP: #1476257)
  * Make sure URL Overlays are shutdown on exit
  * Remove the wildcard that is confusing the update script (LP: #1461496)
  * Not using a message that isn't set properly (LP: #1608009)
  * Fixing tests to adjust for UAL changes
  * Add a small GUI helper tool for testing
  * Show error dialog over apps that use Bad URLs (LP: #1370008)

 -- Ted Gould   Mon, 07 Nov 2016 16:33:15 +

** Changed in: url-dispatcher (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  URL Dispatcher Should Prompt on Bad URL

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gallery-app.  This problem was most recently seen with
  version 13.10.0+14.10.20140908.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/b1f16000af092461aeb85b5c7edfd3dc3f1271c8
  contains more details.

  : "Whenever
  the URL dispatcher is called on to open an address of a protocol that
  it does not understand (url-dispatcher-bad-url), it should open an
  alert with the title “Unrecognized Address”, text of the form ‘Ubuntu
  can’t open addresses of type “{protocol:}”.’, and an “OK” button. To
  prevent denial of UI service, however, the alert should not open if it
  has already opened more than three times in the past minute."

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

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

[Touch-packages] [Bug 1461496] Re: initctl start url-dispatcher-update-user does not update the protocols database

[Launchpad Bug Tracker]

This bug was fixed in the package url-dispatcher -
0.1+17.04.20161107-0ubuntu1

---
url-dispatcher (0.1+17.04.20161107-0ubuntu1) zesty; urgency=medium

  [ Florian Boucault ]
  * Crossbuilding Fixes

  [ Larry Price ]
  * App ID should allow package names with dots. (LP: #1591342) (LP: #1606498)

  [ Ted Gould ]
  * Check versions of appid:// urls to reduce the number of invalid appids
we send to UAL (LP: #1352656)
  * Scope testing for the scope:// URL and overlays that should be over
the dash
  * Protect the dash from getting NULL urls (LP: #1476257)
  * Make sure URL Overlays are shutdown on exit
  * Remove the wildcard that is confusing the update script (LP: #1461496)
  * Not using a message that isn't set properly (LP: #1608009)
  * Fixing tests to adjust for UAL changes
  * Add a small GUI helper tool for testing
  * Show error dialog over apps that use Bad URLs (LP: #1370008)

 -- Ted Gould   Mon, 07 Nov 2016 16:33:15 +

** Changed in: url-dispatcher (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  initctl start url-dispatcher-update-user does not update the protocols
  database

Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  I want to register a protocol for an application putting it in
  ~/.config/url-dispatcher/urls. According to Ted, after running

  $ initctl start url-dispatcher-update-user

  the url dispatcher database should be updated with the new protocol. But 
that's not working.
  It only works if I run /usr/lib/*/url-dispatcher/update-directory with the 
path or my .url-dispatcher file.

  To check the database after the update:

  echo .quit | sqlite3 -batch -csv -cmd "select urls.protocol,
  urls.domainsuffix, configfiles.name from urls, configfiles where
  urls.sourcefile = configfiles.rowid;" ~/.cache/url-
  dispatcher/urls-1.db

  Here is the branch where I'm automating this test:
  
https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/register_url_dispatcher/+merge/260923

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

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

[Touch-packages] [Bug 1352656] Re: ubuntu-app-launch-invalid-appid

[Launchpad Bug Tracker]

This bug was fixed in the package url-dispatcher -
0.1+17.04.20161107-0ubuntu1

---
url-dispatcher (0.1+17.04.20161107-0ubuntu1) zesty; urgency=medium

  [ Florian Boucault ]
  * Crossbuilding Fixes

  [ Larry Price ]
  * App ID should allow package names with dots. (LP: #1591342) (LP: #1606498)

  [ Ted Gould ]
  * Check versions of appid:// urls to reduce the number of invalid appids
we send to UAL (LP: #1352656)
  * Scope testing for the scope:// URL and overlays that should be over
the dash
  * Protect the dash from getting NULL urls (LP: #1476257)
  * Make sure URL Overlays are shutdown on exit
  * Remove the wildcard that is confusing the update script (LP: #1461496)
  * Not using a message that isn't set properly (LP: #1608009)
  * Fixing tests to adjust for UAL changes
  * Add a small GUI helper tool for testing
  * Show error dialog over apps that use Bad URLs (LP: #1370008)

 -- Ted Gould   Mon, 07 Nov 2016 16:33:15 +

** Changed in: url-dispatcher (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  ubuntu-app-launch-invalid-appid

Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding url-dispatcher.  This problem was most recently seen with
  version 8.00+14.10.20140731.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/50ef8ac2301b5a70acb47d40d1efff412014d40b
  contains more details.

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

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

[Touch-packages] [Bug 1476257] Re: /usr/lib/arm-linux-gnueabihf/url-dispatcher/url-dispatcher:11:g_variant_is_trusted:g_variant_builder_add_value:g_variant_builder_close:send_to_dash:dispatcher_send_t

[Launchpad Bug Tracker]

This bug was fixed in the package url-dispatcher -
0.1+17.04.20161107-0ubuntu1

---
url-dispatcher (0.1+17.04.20161107-0ubuntu1) zesty; urgency=medium

  [ Florian Boucault ]
  * Crossbuilding Fixes

  [ Larry Price ]
  * App ID should allow package names with dots. (LP: #1591342) (LP: #1606498)

  [ Ted Gould ]
  * Check versions of appid:// urls to reduce the number of invalid appids
we send to UAL (LP: #1352656)
  * Scope testing for the scope:// URL and overlays that should be over
the dash
  * Protect the dash from getting NULL urls (LP: #1476257)
  * Make sure URL Overlays are shutdown on exit
  * Remove the wildcard that is confusing the update script (LP: #1461496)
  * Not using a message that isn't set properly (LP: #1608009)
  * Fixing tests to adjust for UAL changes
  * Add a small GUI helper tool for testing
  * Show error dialog over apps that use Bad URLs (LP: #1370008)

 -- Ted Gould   Mon, 07 Nov 2016 16:33:15 +

** Changed in: url-dispatcher (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  /usr/lib/arm-linux-gnueabihf/url-dispatcher/url-
  
dispatcher:11:g_variant_is_trusted:g_variant_builder_add_value:g_variant_builder_close:send_to_dash:dispatcher_send_to_app

Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding url-dispatcher.  This problem was most recently seen with
  version 0.1+15.10.20150612-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/64c5a23f81476af20831b29844a2abcb607d5dc6
  contains more details.

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

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

[Touch-packages] [Bug 1591342] Re: Complains about bad url on libertine scope urls

[Launchpad Bug Tracker]

This bug was fixed in the package url-dispatcher -
0.1+17.04.20161107-0ubuntu1

---
url-dispatcher (0.1+17.04.20161107-0ubuntu1) zesty; urgency=medium

  [ Florian Boucault ]
  * Crossbuilding Fixes

  [ Larry Price ]
  * App ID should allow package names with dots. (LP: #1591342) (LP: #1606498)

  [ Ted Gould ]
  * Check versions of appid:// urls to reduce the number of invalid appids
we send to UAL (LP: #1352656)
  * Scope testing for the scope:// URL and overlays that should be over
the dash
  * Protect the dash from getting NULL urls (LP: #1476257)
  * Make sure URL Overlays are shutdown on exit
  * Remove the wildcard that is confusing the update script (LP: #1461496)
  * Not using a message that isn't set properly (LP: #1608009)
  * Fixing tests to adjust for UAL changes
  * Add a small GUI helper tool for testing
  * Show error dialog over apps that use Bad URLs (LP: #1370008)

 -- Ted Gould   Mon, 07 Nov 2016 16:33:15 +

** Changed in: url-dispatcher (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Complains about bad url on libertine scope urls

Status in Canonical System Image:
  In Progress
Status in libertine-scope package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  ** (process:4255): WARNING **: Unable to dispatch url
  
'appid://xenial/org.kde.kate/0.0':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'appid://xenial/org.kde.kate/0.0' is not handleable by the URL
  Dispatcher

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

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

[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-system-settings -
0.4+17.04.20161101.1-0ubuntu1

---
ubuntu-system-settings (0.4+17.04.20161101.1-0ubuntu1) zesty; urgency=medium

  * Drop repowerd to a Recommends and stop depending on gnome-settings-
daemon to fix a component mismatch

 -- Ken VanDine   Tue, 01 Nov 2016 17:51:36
+

** Changed in: ubuntu-system-settings (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 ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1629009

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

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

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

[Touch-packages] [Bug 1639737] Re: New Version of JasPer JPEG2000 Software Available

[Hans Joachim Desserud]

** Tags added: upgrade-software-version

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

Title:
  New Version of JasPer JPEG2000 Software Available

Status in jasper package in Ubuntu:
  New

Bug description:
  I hope that this is not inappropriate to submit as a bug report.

  As best I can tell, it seems that Ubuntu Zesty (as well as other
  versions) is using JasPer version 1.900.1.  This version of the JasPer
  software is very old and numerous bug fixes have been made since the
  time that this old version was released. It is possible to adopt a
  newer version of JasPer the from upstream source?

  The most recent version of JasPer is 1.900.22.  See the JasPer web site for 
details:
  http://www.ece.uvic.ca/~mdadams/jasper

  A link to the 1.900.22 release tarball is as follows:
  http://www.ece.uvic.ca/~frodo/jasper/software/jasper-1.900.22.tar.gz

  Or alternatively you could just pull code from the master branch of the 
official JasPer Git repository on GitHub:
  https://github.com/mdadams/jasper

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

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

[Touch-packages] [Bug 1606712] Re: Crash/error report text can't be copied to clipboard

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1133184
   apport-gtk: Allow copy to clipboard from detailed view

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

Title:
  Crash/error report text can't be copied to clipboard

Status in Apport:
  New
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When an application crashes, the "The application XXX has closed
  unexpectedly" dialog doesn't allow copying the text to the clipboard.
  I want to send to the developer only the title of the crash, or I want
  to do a web search for it, so going to /var/crash and hunting for the
  right file is overkill.

  Please make the text in that dialog copy/pastable.

  More reports from users who were blocked by this:

  http://askubuntu.com/questions/659731/how-to-copy-paste-from-sorry-
  the-application-xxx-has-stopped-unexpectedly/659748

  http://askubuntu.com/questions/152914/how-can-i-copy-the-text-of-an-
  unreportable-error

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

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] Nvidia Quadro FX5600

[Peter]

Public bug reported:

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

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


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

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

Title:
  Nvidia Quadro FX5600

Status in xorg package in Ubuntu:
  New

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
 

[Touch-packages] [Bug 1639440] Re: [desktop] apps don't start, missing logs

[Christopher Townsend]

I'm seeing this behavior too on Zesty.

@serge-hallyn,

Yes, parts of the Unity 8 stack are still relying on cgmanager.  The
future plan is to use systemd and get rid of the cgmanager dependence,
but The Future is not now:)

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

Title:
  [desktop] apps don't start, missing logs

Status in Canonical System Image:
  Incomplete
Status in cgmanager package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  update. Fresh install of 17.04 same result, the apps don't start

  Ubuntu 17.04 + proposed (unity8 desktop session)
  unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 
[installed,automatic]

  apps don't load and i can't find the logs in ~/.cache/upstart for the
  apps. i'll upload the logs that i do have for unity8

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

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

[Touch-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login

[Martin Pitt]

** Changed in: lightdm (Ubuntu)
Milestone: ubuntu-16.11 => None

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

Title:
  lightdm greeter session not properly shut down at login

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  I am using lightdm with 2 seats. After 2409 revision randomly one of
  two seats does not work correctly.

  xsettings plugin from unity-settings-daemon or gnome-settings-deamon
  fails to start because there is already _XSESSION_S* manager running.

  After revision 2409 in system monitor I see that there is still
  running unity-settings-daemon started by lightdm. Reverting this
  revision fixes my problem.

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

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

[Touch-packages] [Bug 1640278] Re: Login box in LightDM should be center centered on wide screens

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)

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

Title:
  Login box in LightDM should be center centered on wide screens

Status in Ubuntu UX:
  New
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  Login box in LightDM should be center centered on wide screens

  it's sooper annoying to login on wide screens, you have to turn your
  head to see the login screen.

  please see attachment

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

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

[Touch-packages] [Bug 1640293] Re: Backport graphical-session{, -pre}.target to xenial

[Martin Pitt]

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-xenial=affd57d806

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

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

Title:
  Backport graphical-session{,-pre}.target to xenial

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Ted Gould and Dimitri Ledkov requested that the graphical-
  session{,-pre}.target user units introduced in yakkety should be
  backported to xenial, so that snapd units can use them.

  At the moment they will *not* be used by default by any desktop
  session in xenial, so they will stay inert. The net effect is solely
  to ship those two new unit files.

  TEST CASE: Verify that these two new units exist in the -proposed
  version:

/usr/lib/systemd/user/graphical-session-pre.target
/usr/lib/systemd/user/graphical-session.target

  and that they are *not* running (systemctl --user status graphical-
  session{,-pre}.target)

  REGRESSION POTENTIAL: Practically zero.

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

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

[Touch-packages] [Bug 1640288] Re: Malformed url-dispatcher file

[Michael Terry]

** Branch linked: lp:~mterry/dialer-app/dispatcher-typo

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

Title:
  Malformed url-dispatcher file

Status in dialer-app package in Ubuntu:
  New

Bug description:
  The current /usr/share/url-dispatcher/urls/dialer-app.url-dispatcher
  file installed on the system is:

  {
{
   "protocol": "tel"
}
{
   "protocol": "dialer"
}
  }

  But it's missing a comma between the two inner sections.  So url-
  dispatcher doesn't register the protocols.

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

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

[Touch-packages] [Bug 1640293] [NEW] Backport graphical-session{, -pre}.target to xenial

[Martin Pitt]

Public bug reported:

Ted Gould and Dimitri Ledkov requested that the graphical-
session{,-pre}.target user units introduced in yakkety should be
backported to xenial, so that snapd units can use them.

At the moment they will *not* be used by default by any desktop session
in xenial, so they will stay inert. The net effect is solely to ship
those two new unit files.

TEST CASE: Verify that these two new units exist in the -proposed
version:

  /usr/lib/systemd/user/graphical-session-pre.target
  /usr/lib/systemd/user/graphical-session.target

and that they are *not* running (systemctl --user status graphical-
session{,-pre}.target)

REGRESSION POTENTIAL: Practically zero.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: systemd (Ubuntu Xenial)
 Importance: Undecided
 Status: In Progress

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

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

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

Title:
  Backport graphical-session{,-pre}.target to xenial

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Ted Gould and Dimitri Ledkov requested that the graphical-
  session{,-pre}.target user units introduced in yakkety should be
  backported to xenial, so that snapd units can use them.

  At the moment they will *not* be used by default by any desktop
  session in xenial, so they will stay inert. The net effect is solely
  to ship those two new unit files.

  TEST CASE: Verify that these two new units exist in the -proposed
  version:

/usr/lib/systemd/user/graphical-session-pre.target
/usr/lib/systemd/user/graphical-session.target

  and that they are *not* running (systemctl --user status graphical-
  session{,-pre}.target)

  REGRESSION POTENTIAL: Practically zero.

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

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

[Touch-packages] [Bug 1640293] Re: Backport graphical-session{, -pre}.target to xenial

[Martin Pitt]

Sorry, this is the correct one: https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntu-xenial=087e8815862fbc

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

Title:
  Backport graphical-session{,-pre}.target to xenial

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Ted Gould and Dimitri Ledkov requested that the graphical-
  session{,-pre}.target user units introduced in yakkety should be
  backported to xenial, so that snapd units can use them.

  At the moment they will *not* be used by default by any desktop
  session in xenial, so they will stay inert. The net effect is solely
  to ship those two new unit files.

  TEST CASE: Verify that these two new units exist in the -proposed
  version:

/usr/lib/systemd/user/graphical-session-pre.target
/usr/lib/systemd/user/graphical-session.target

  and that they are *not* running (systemctl --user status graphical-
  session{,-pre}.target)

  REGRESSION POTENTIAL: Practically zero.

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

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

[Touch-packages] [Bug 1638301] Re: systemctl start auto-completion shows error

[Martin Pitt]

This got fixed in version 232, now in zesty.

** Changed in: systemd (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  systemctl start  auto-completion shows error

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  When i try to auto-complete the "systemctl start " the
  following error message is shown in bash:

  Unit org.freedesktop.network1.busname could not be found.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  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: Unity
  Date: Tue Nov  1 10:42:37 2016
  InstallationDate: Installed on 2015-06-20 (499 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Dell System Vostro 3450
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=7468e7be-a2e1-48dd-ba72-244c33698364 ro cgroup_enable=memory 
swapaccount=1 quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (12 days ago)
  dmi.bios.date: 07/22/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0GG0VM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/22/2011:svnDellInc.:pnDellSystemVostro3450:pvr:rvnDellInc.:rn0GG0VM:rvrA01:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System Vostro 3450
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1640290] [NEW] Update Qt to 5.7

[Jeremy Bicha]

Public bug reported:

Tracking bug.

https://people.canonical.com/~ubuntu-archive/transitions/html/html
/qtbase-abi-5-7-1.html

Debian successfully completed the 5.7 transition.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Wishlist
 Status: Confirmed


** Tags: upgrade-software-version zesty

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

Title:
  Update Qt to 5.7

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Tracking bug.

  https://people.canonical.com/~ubuntu-archive/transitions/html/html
  /qtbase-abi-5-7-1.html

  Debian successfully completed the 5.7 transition.

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

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

[Touch-packages] [Bug 1639478] Re: Merge with Debian 0.48.0

[Jeremy Bicha]

** Description changed:

  I successfully test-built poppler 0.48 on zesty. I did not test-build
  the rdepends.
  
  From looking at the transition tracker, I guess we should wait for the
  gdal transition to complete first.
  
- https://release.debian.org/transitions/html/auto-poppler.html
+ https://people.canonical.com/~ubuntu-archive/transitions/html/poppler.html
  https://people.canonical.com/~ubuntu-archive/transitions/html/gdal.html
  
  I dropped the change to not build-depend on openjpeg2; the (universe)
  build-depends is fine since we do still disable openjpeg2.
  
  Changes since Ubuntu version 0.44.0-3ubuntu2
  ===
  
  https://cgit.freedesktop.org/poppler/poppler/tree/NEWS
  
  poppler (0.48.0-2) unstable; urgency=medium
  
    * Upload to unstable. (See #839869)
    * autopkgtest: build the qt5 test with -std=c++11, required with Qt5 >= 5.6.
    * Backport upstream commit 5d15a52aade68c618c356fe403ca500e74917ef7 to 
remove
  an extra '%' in an error message of pdfseparate; patch
  upstream_pdfseparate-remove-extra-in-error-message.patch. (Closes: 
#835202)
  
   -- Pino Toscano   Sat, 05 Nov 2016 08:29:43 +0100
  
  poppler (0.48.0-1) experimental; urgency=medium
  
    * New upstream release:
  - fixes UTF-16 decoding of document outline title (Closes: #702082)
  - fixes crashes in PDF documents (Closes: #830565)
    * Rename packages according to the new SONAMEs:
  - libpoppler61 -> libpoppler64
    * Update copyright.
    * Bump the libglib2.0-dev (build-)dependency to 2.41, as noted in the
  upstream build system.
    * Update symbols files.
    * Bump shlibs for libpoppler-cpp0v5 to >= 0.46.0, following the new APIs
  added.
    * Install the GObject introspection data in a multi-arch directory:
  - bump the libgirepository1.0-dev, and gobject-introspection to
    >= 1.42.0-2~, as providing a fixed dh_girepository
  - update gir1.2-poppler-0.18.install
  - mark gir1.2-poppler-0.18 as Multi-Arch: same
  
   -- Pino Toscano   Sat, 08 Oct 2016 20:14:42 +0200

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

Title:
  Merge with Debian 0.48.0

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  I successfully test-built poppler 0.48 on zesty. I did not test-build
  the rdepends.

  From looking at the transition tracker, I guess we should wait for the
  gdal transition to complete first.

  https://people.canonical.com/~ubuntu-archive/transitions/html/poppler.html
  https://people.canonical.com/~ubuntu-archive/transitions/html/gdal.html

  I dropped the change to not build-depend on openjpeg2; the (universe)
  build-depends is fine since we do still disable openjpeg2.

  Changes since Ubuntu version 0.44.0-3ubuntu2
  ===

  https://cgit.freedesktop.org/poppler/poppler/tree/NEWS

  poppler (0.48.0-2) unstable; urgency=medium

    * Upload to unstable. (See #839869)
    * autopkgtest: build the qt5 test with -std=c++11, required with Qt5 >= 5.6.
    * Backport upstream commit 5d15a52aade68c618c356fe403ca500e74917ef7 to 
remove
  an extra '%' in an error message of pdfseparate; patch
  upstream_pdfseparate-remove-extra-in-error-message.patch. (Closes: 
#835202)

   -- Pino Toscano   Sat, 05 Nov 2016 08:29:43 +0100

  poppler (0.48.0-1) experimental; urgency=medium

    * New upstream release:
  - fixes UTF-16 decoding of document outline title (Closes: #702082)
  - fixes crashes in PDF documents (Closes: #830565)
    * Rename packages according to the new SONAMEs:
  - libpoppler61 -> libpoppler64
    * Update copyright.
    * Bump the libglib2.0-dev (build-)dependency to 2.41, as noted in the
  upstream build system.
    * Update symbols files.
    * Bump shlibs for libpoppler-cpp0v5 to >= 0.46.0, following the new APIs
  added.
    * Install the GObject introspection data in a multi-arch directory:
  - bump the libgirepository1.0-dev, and gobject-introspection to
    >= 1.42.0-2~, as providing a fixed dh_girepository
  - update gir1.2-poppler-0.18.install
  - mark gir1.2-poppler-0.18 as Multi-Arch: same

   -- Pino Toscano   Sat, 08 Oct 2016 20:14:42 +0200

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

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

[Touch-packages] [Bug 1640288] [NEW] Malformed url-dispatcher file

[Michael Terry]

Public bug reported:

The current /usr/share/url-dispatcher/urls/dialer-app.url-dispatcher
file installed on the system is:

{
  {
 "protocol": "tel"
  }
  {
 "protocol": "dialer"
  }
}

But it's missing a comma between the two inner sections.  So url-
dispatcher doesn't register the protocols.

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Malformed url-dispatcher file

Status in dialer-app package in Ubuntu:
  New

Bug description:
  The current /usr/share/url-dispatcher/urls/dialer-app.url-dispatcher
  file installed on the system is:

  {
{
   "protocol": "tel"
}
{
   "protocol": "dialer"
}
  }

  But it's missing a comma between the two inner sections.  So url-
  dispatcher doesn't register the protocols.

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

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

[Touch-packages] [Bug 1640286] [NEW] DNS failure for certain sites

[M Willis Monroe]

Public bug reported:

(Ubuntu Gnome 16.10)

Recently after upgrading to 16.10 I have a frequent loss of DNS response
for certain sites while browsing in Chrome.  This occurs both after
resuming from sleep or sometimes at other (seemingly) random times.

Steps to reproduce:
1) Browse sites in Chrome
2) A site will stop responding and DNS queries will timeout

There's not much more that I can add besides that, however the solution
I've found might give some more information.  I was digging around in
the /etc/resolvconf files and found that running the script
"/etc/resolvconf/update.d/libc" fixes the issue immediately, sometimes
even before the script finishes executing.  I've tried to read through
the script but I'm not sure I really understand what's going on there.

To give an example of a recent case of this happening.  I loaded
politico.com, all the text and css loaded just fine, but every image was
a dead link.  Turns out the images were hosted at static2.politico.com.
As soon as I ran the above script and reloaded the page, everything
loaded just fine.

Another case, is upon waking from sleep often Gmail will load the most
recent new e-mails and then when I go to click on one or try to respond,
the interface will timeout and a reload will result in a DNS timeout
until I run the above script.

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

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

Title:
  DNS failure for certain sites

Status in resolvconf package in Ubuntu:
  New

Bug description:
  (Ubuntu Gnome 16.10)

  Recently after upgrading to 16.10 I have a frequent loss of DNS
  response for certain sites while browsing in Chrome.  This occurs both
  after resuming from sleep or sometimes at other (seemingly) random
  times.

  Steps to reproduce:
  1) Browse sites in Chrome
  2) A site will stop responding and DNS queries will timeout

  There's not much more that I can add besides that, however the
  solution I've found might give some more information.  I was digging
  around in the /etc/resolvconf files and found that running the script
  "/etc/resolvconf/update.d/libc" fixes the issue immediately, sometimes
  even before the script finishes executing.  I've tried to read through
  the script but I'm not sure I really understand what's going on there.

  To give an example of a recent case of this happening.  I loaded
  politico.com, all the text and css loaded just fine, but every image
  was a dead link.  Turns out the images were hosted at
  static2.politico.com.  As soon as I ran the above script and reloaded
  the page, everything loaded just fine.

  Another case, is upon waking from sleep often Gmail will load the most
  recent new e-mails and then when I go to click on one or try to
  respond, the interface will timeout and a reload will result in a DNS
  timeout until I run the above script.

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

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

[Touch-packages] [Bug 1639440] Re: [desktop] apps don't start, missing logs

[Launchpad Bug Tracker]

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

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

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

Title:
  [desktop] apps don't start, missing logs

Status in Canonical System Image:
  Incomplete
Status in cgmanager package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  update. Fresh install of 17.04 same result, the apps don't start

  Ubuntu 17.04 + proposed (unity8 desktop session)
  unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 
[installed,automatic]

  apps don't load and i can't find the logs in ~/.cache/upstart for the
  apps. i'll upload the logs that i do have for unity8

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

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

[Touch-packages] [Bug 1640278] Re: Login box in LightDM should be center centered on wide screens

[Launchpad Bug Tracker]

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

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

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

Title:
  Login box in LightDM should be center centered on wide screens

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

Bug description:
  Login box in LightDM should be center centered on wide screens

  it's sooper annoying to login on wide screens, you have to turn your
  head to see the login screen.

  please see attachment

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

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

[Touch-packages] [Bug 1639440] Re: [desktop] apps don't start, missing logs

[Launchpad Bug Tracker]

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

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

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

Title:
  [desktop] apps don't start, missing logs

Status in Canonical System Image:
  Incomplete
Status in cgmanager package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  update. Fresh install of 17.04 same result, the apps don't start

  Ubuntu 17.04 + proposed (unity8 desktop session)
  unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 
[installed,automatic]

  apps don't load and i can't find the logs in ~/.cache/upstart for the
  apps. i'll upload the logs that i do have for unity8

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

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

[Touch-packages] [Bug 1639558] Re: message regarding ignoring 50unattended-upgrades.ucf-dist is annoying

[richud]

great, also bug #1236059

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

Title:
  message regarding ignoring 50unattended-upgrades.ucf-dist is annoying

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Regression problem, (in the sense it didn't happen before the update
  although not directly from the code changes)

  Since update to 0.90ubuntu0.1 (ubuntu 16.04)  I am constantly now
  getting this notification performing anything with apt.

  N: Ignoring file '50unattended-upgrades.ucf-dist' in directory
  '/etc/apt/apt.conf.d/' as it has an invalid filename extension

  
  Secondly I am also now getting this, triggering apport bug report on every 
boot (program is not checking/creating a dir before trying to write to log in 
it)

  syslog.1:Nov  6 10:36:26 PortegeR830 apt.systemd.daily[815]:
  FileNotFoundError: [Errno 2] No such file or directory: '/var/log
  /unattended-upgrades/unattended-upgrades-dpkg.log'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .var.log.unattended-upgrades.unattended-upgrades.log:
   2016-11-06 10:36:05,682 INFO Initial blacklisted packages: 
   2016-11-06 10:36:05,682 INFO Initial whitelisted packages: 
   2016-11-06 10:36:05,683 INFO Starting unattended upgrades script
   2016-11-06 10:36:05,683 INFO Allowed origins are: 
['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates', 
'o=Ubuntu,a=xenial-backports']
   2016-11-06 10:36:21,473 INFO Packages that will be upgraded:
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  6 10:59:28 2016
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "1";
   APT::Periodic::AutocleanInterval "7";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2015-05-30T16:31:54.137714
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2015-05-30T16:31:21.861600

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

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

[Touch-packages] [Bug 1640278] [NEW] Login box in LightDM should be center centered on wide screens

[dinamic]

Public bug reported:

Login box in LightDM should be center centered on wide screens

it's sooper annoying to login on wide screens, you have to turn your
head to see the login screen.

please see attachment

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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

** Attachment added: "yuge.jpg"
   https://bugs.launchpad.net/bugs/1640278/+attachment/4774508/+files/yuge.jpg

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

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

Title:
  Login box in LightDM should be center centered on wide screens

Status in Ubuntu UX:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Login box in LightDM should be center centered on wide screens

  it's sooper annoying to login on wide screens, you have to turn your
  head to see the login screen.

  please see attachment

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

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

[scotte]

It's been resolved for us in xenial for quite awhile...

-- 
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 1637300] Re: procps upgrades fail in a LXD container

[Lars Bo Rasmussen]

root@vps137255:~# apt-get install procps/xenial-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '2:3.3.10-4ubuntu2.2' (Ubuntu:16.04/xenial-proposed [amd64]) 
for 'procps'
The following packages were automatically installed and are no longer required:
  initramfs-tools-core libapt-inst1.5 linux-base
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  procps
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
Need to get 222 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 procps amd64 
2:3.3.10-4ubuntu2.2 [222 kB]
Fetched 222 kB in 0s (2,235 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 21894 files and directories currently installed.)
Preparing to unpack .../procps_2%3a3.3.10-4ubuntu2.2_amd64.deb ...
Unpacking procps (2:3.3.10-4ubuntu2.2) over (2:3.3.10-4ubuntu2) ...
Processing triggers for systemd (229-4ubuntu12) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up procps (2:3.3.10-4ubuntu2.2) ...
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Setting up udev (229-4ubuntu12) ...
Installing new version of config file /etc/init.d/udev ...
Installing new version of config file /etc/init/udevmonitor.conf ...
addgroup: The group `input' already exists as a system group. Exiting.
Removing obsolete conffile /etc/init.d/udev-finish ...
Removing obsolete conffile /etc/init/udev-finish.conf ...
Removing obsolete conffile /etc/init/udev-fallback-graphics.conf ...
Removing obsolete conffile /etc/init.d/lvm2 ...
Setting up initramfs-tools-core (0.122ubuntu8.5) ...
Installing new version of config file /etc/initramfs-tools/initramfs.conf ...
Setting up openssh-server (1:7.2p2-4ubuntu2.1) ...
Installing new version of config file /etc/network/if-up.d/openssh-server ...
Processing triggers for systemd (229-4ubuntu12) ...

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

Title:
  procps upgrades fail in a LXD container

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  Fix Committed
Status in procps package in Debian:
  Fix Released

Bug description:
  [Impact]
  procps cannot be upgraded - or even reinstalled - in an LXD container. This 
means we cannot deliver updates (like the pending fix for LP: #1637026 in 
xenial-proposed) w/o putting container users in a bad state that requires a 
container restart to resolve.

  [Test Case]
  $ lxc launch ubuntu:xenial procpstest
  Creating procpstest
  Starting procpstest
  $ lxc exec procpstest -- /bin/bash
  root@procpstest:~# apt --reinstall install procps
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 209 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 procps arm64 
2:3.3.10-4ubuntu2 [209 kB]
  Fetched 209 kB in 1s (113 kB/s)  
  (Reading database ... 25398 files and directories currently installed.)
  Preparing to unpack .../procps_2%3a3.3.10-4ubuntu2_arm64.deb ...
  Unpacking procps (2:3.3.10-4ubuntu2) over (2:3.3.10-4ubuntu2) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for systemd (229-4ubuntu11) ...
  Setting up procps (2:3.3.10-4ubuntu2) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Job for systemd-sysctl.service failed because the control process exited with 
error code. See "systemctl status systemd-sysctl.service" and "journalctl -xe" 
for details.
  invoke-rc.d: initscript procps, action "start" failed.
  dpkg: error processing package procps (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   procps
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  root@procpstest:~#

  [Regression Risk]
  The proposed fix is to disable invoking the procps initscript on 
install/upgrade. This fix is already in yakkety, and I didn't find any bugs 
related to it in LP.

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

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

[Touch-packages] [Bug 1640267] Re: Softwarecenter there's no Employment

[Julian Andres Klode]

** Package changed: apt (Ubuntu) => gnome-software (Ubuntu)

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

Title:
  Softwarecenter there's no Employment

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Hello
  I have new installed ubuntu 16.10 64 bit.
  I have made all updates. System is up-to-date.

  I have tested my .deb pakage.

  Softwarecenter there's no employment and finish from the Install.

  Install is finished, the program is in function,  i cannot see the
  finish it in the window.

  The button is not red, the name from button is not finish.

  See the picture.

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

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

[Touch-packages] [Bug 1640267] [NEW] Softwarecenter there's no Employment

[Marko Preuss]

Public bug reported:

Hello
I have new installed ubuntu 16.10 64 bit.
I have made all updates. System is up-to-date.

I have tested my .deb pakage.

Softwarecenter there's no employment and finish from the Install.

Install is finished, the program is in function,  i cannot see the
finish it in the window.

The button is not red, the name from button is not finish.

See the picture.

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


** Tags: window

** Attachment added: "apt"
   
https://bugs.launchpad.net/bugs/1640267/+attachment/4774504/+files/forwarding%20view%20install%20.deb%20pakage.png

** Summary changed:

- Softwarecenter there's no Employmend
+ Softwarecenter there's no Employment

** Description changed:

  Hello
  I have new installed ubuntu 16.10 64 bit.
+ I have made all updates. System is updated.
  
  I have tested my .deb pakage.
  
  Softwarecenter there's no employment and finish from the Install.
  
  Install is finished, the program is in function,  i cannot see the
  finish it in the window.
  
  The button is not red, the name from button is not finish.
  
  See the picture.

** Description changed:

  Hello
  I have new installed ubuntu 16.10 64 bit.
- I have made all updates. System is updated.
+ I have made all updates. System is up-to-date.
  
  I have tested my .deb pakage.
  
  Softwarecenter there's no employment and finish from the Install.
  
  Install is finished, the program is in function,  i cannot see the
  finish it in the window.
  
  The button is not red, the name from button is not finish.
  
  See the picture.

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

Title:
  Softwarecenter there's no Employment

Status in apt package in Ubuntu:
  New

Bug description:
  Hello
  I have new installed ubuntu 16.10 64 bit.
  I have made all updates. System is up-to-date.

  I have tested my .deb pakage.

  Softwarecenter there's no employment and finish from the Install.

  Install is finished, the program is in function,  i cannot see the
  finish it in the window.

  The button is not red, the name from button is not finish.

  See the picture.

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

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

[Mathieu Trudel-Lapierre]

scotte, Jason, could either of you verify that the revert returned
initramfs-tools in a state that works for you?

-- 
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 1637996] Re: app switcher not responsive

[Michał Sawicz]

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

** This bug has been marked a duplicate of bug 1518935
   When an application is suspended or closed it causes a large UI stutter

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

Title:
  app switcher not responsive

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

Bug description:
  MX4 running 451

  After some period of use, the switched frequently becomes
  unresponsive, either it does not reveal right away on a right edge
  gesture, or when revealed selecting an app does nothing for some
  seconds. When in this state it is inconsistent, will work a few times,
  then not work.

  This regressed with the new implementation.

  It does seem to require that the browser or a webapp is open. I cannot
  reproduce it otherwise.

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

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

The original string is "Software & Updates", so if you are right, a lot
of users (not only French) ought to run into the issue and there would
be a need to either change the original string or make whatever uses the
string when upgrading Ubuntu via update-manager capable of dealing with
an unescaped '&' character.

What makes you think that the single '&' character is the culprit? What
does the error alert say?

-- 
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 1639558] Re: message regarding ignoring 50unattended-upgrades.ucf-dist is annoying

[Brian Murray]

** Summary changed:

- regression-update  from #1624641
+ message regarding ignoring 50unattended-upgrades.ucf-dist is annoying

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  message regarding ignoring 50unattended-upgrades.ucf-dist is annoying

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Regression problem, (in the sense it didn't happen before the update
  although not directly from the code changes)

  Since update to 0.90ubuntu0.1 (ubuntu 16.04)  I am constantly now
  getting this notification performing anything with apt.

  N: Ignoring file '50unattended-upgrades.ucf-dist' in directory
  '/etc/apt/apt.conf.d/' as it has an invalid filename extension

  
  Secondly I am also now getting this, triggering apport bug report on every 
boot (program is not checking/creating a dir before trying to write to log in 
it)

  syslog.1:Nov  6 10:36:26 PortegeR830 apt.systemd.daily[815]:
  FileNotFoundError: [Errno 2] No such file or directory: '/var/log
  /unattended-upgrades/unattended-upgrades-dpkg.log'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .var.log.unattended-upgrades.unattended-upgrades.log:
   2016-11-06 10:36:05,682 INFO Initial blacklisted packages: 
   2016-11-06 10:36:05,682 INFO Initial whitelisted packages: 
   2016-11-06 10:36:05,683 INFO Starting unattended upgrades script
   2016-11-06 10:36:05,683 INFO Allowed origins are: 
['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates', 
'o=Ubuntu,a=xenial-backports']
   2016-11-06 10:36:21,473 INFO Packages that will be upgraded:
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  6 10:59:28 2016
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "1";
   APT::Periodic::AutocleanInterval "7";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2015-05-30T16:31:54.137714
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2015-05-30T16:31:21.861600

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

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

[Touch-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login

[Alberts Muktupāvels]

Restart did help. :)

** Changed in: lightdm (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  lightdm greeter session not properly shut down at login

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  I am using lightdm with 2 seats. After 2409 revision randomly one of
  two seats does not work correctly.

  xsettings plugin from unity-settings-daemon or gnome-settings-deamon
  fails to start because there is already _XSESSION_S* manager running.

  After revision 2409 in system monitor I see that there is still
  running unity-settings-daemon started by lightdm. Reverting this
  revision fixes my problem.

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

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

[Touch-packages] [Bug 1588526] Re: [mako] Alarm doesn't ring when screen locked

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-datetime -
15.10+17.04.20161104-0ubuntu1

---
indicator-datetime (15.10+17.04.20161104-0ubuntu1) zesty; urgency=medium

  [ Charles Kerr ]
  * Remember the system bus instead of fetching it asynchronously (LP:
#1588526)

 -- charles.k...@canonical.com (charles.k...@canonical.com)  Fri, 04 Nov
2016 16:45:17 +

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  In Progress
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

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

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

[Touch-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login

[Ads20000]

Installing all updates and rebooting still affects my duplicates (I'm
not using two seats(?) but they're duplicates according to Ian Lane).

** Attachment added: "#1637758 loginctl Terminal output"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637758/+attachment/4774494/+files/%231637758%20loginctl%20Terminal%20output

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

Title:
  lightdm greeter session not properly shut down at login

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  I am using lightdm with 2 seats. After 2409 revision randomly one of
  two seats does not work correctly.

  xsettings plugin from unity-settings-daemon or gnome-settings-deamon
  fails to start because there is already _XSESSION_S* manager running.

  After revision 2409 in system monitor I see that there is still
  running unity-settings-daemon started by lightdm. Reverting this
  revision fixes my problem.

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

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

[Brian Murray]

** Description changed:

  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.

-- 
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:
  In Progress
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

Re: [Touch-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login

[Iain Lane]

On Tue, Nov 08, 2016 at 04:19:33PM -, Alberts Muktupāvels wrote:
> What do you mean with current zesty? I just installed all updates (I
> don't use proposed), but I have not restarted pc and/or lightdm...

Try to restart. For me the problem is gone indeed. I don't really
understand why, but it looks like the new systemd (232-2git1) fixed it.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  lightdm greeter session not properly shut down at login

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I am using lightdm with 2 seats. After 2409 revision randomly one of
  two seats does not work correctly.

  xsettings plugin from unity-settings-daemon or gnome-settings-deamon
  fails to start because there is already _XSESSION_S* manager running.

  After revision 2409 in system monitor I see that there is still
  running unity-settings-daemon started by lightdm. Reverting this
  revision fixes my problem.

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

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

[Brian Murray]

** Changed in: unattended-upgrades (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: Triaged => In Progress

-- 
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:
  In Progress

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 1640233] [NEW] package libqt5dbus5:i386 (not installed) failed to install/upgrade: package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because libqt5dbus5:amd64 i

[Fabio Cresci]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libqt5dbus5:i386 (not installed)
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
Date: Mon Nov  7 11:17:39 2016
DuplicateSignature:
 package:libqt5dbus5:i386:(not installed)
 Unpacking mesa-utils:i386 (8.3.0-2) over (8.3.0-2) ...
 dpkg: error processing package libqt5core5a:i386 (--configure):
  package libqt5core5a:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because 
libqt5core5a:amd64 is at a different version 
(5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2)
ErrorMessage: package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be 
configured because libqt5dbus5:amd64 is at a different version 
(5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2)
InstallationDate: Installed on 2016-04-13 (209 days ago)
InstallationMedia:
 
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: qtbase-opensource-src
Title: package libqt5dbus5:i386 (not installed) failed to install/upgrade: 
package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because 
libqt5dbus5:amd64 is at a different version 
(5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2)
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (25 days ago)

** Affects: qtbase-opensource-src (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 qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1640233

Title:
  package libqt5dbus5:i386 (not installed) failed to install/upgrade:
  package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured
  because libqt5dbus5:amd64 is at a different version (5.6.1+dfsg-
  3ubuntu7~~xenialoverlay1~2)

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libqt5dbus5:i386 (not installed)
  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
  Date: Mon Nov  7 11:17:39 2016
  DuplicateSignature:
   package:libqt5dbus5:i386:(not installed)
   Unpacking mesa-utils:i386 (8.3.0-2) over (8.3.0-2) ...
   dpkg: error processing package libqt5core5a:i386 (--configure):
package libqt5core5a:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured 
because libqt5core5a:amd64 is at a different version 
(5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2)
  ErrorMessage: package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be 
configured because libqt5dbus5:amd64 is at a different version 
(5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2)
  InstallationDate: Installed on 2016-04-13 (209 days ago)
  InstallationMedia:
   
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: qtbase-opensource-src
  Title: package libqt5dbus5:i386 (not installed) failed to install/upgrade: 
package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because 
libqt5dbus5:amd64 is at a different version 
(5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2)
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (25 days ago)

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

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

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

[Erik Brinkman]

The proposed packages worked for me on yakkety.

-- 
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 1591328] Re: Pointer/cursor input lag in unity8 session

[kevin gunn]

** Changed in: canonical-devices-system-image
Milestone: 14 => backlog

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

Title:
  Pointer/cursor input lag in unity8 session

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1640214] Re: [unity8][desktop] wrong network indicator icon - cogwheel

[dinamic]

i'm also affected by this bug https://bugs.launchpad.net/canonical-
devices-system-image/+bug/1639440

first i thought that is because i had proposed enabled but then i made a
clean install, same result, apps don't start.

can you please test on a desktop pc with a clean 17.04 install?

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

Title:
  [unity8][desktop] wrong network indicator icon  - cogwheel

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

Bug description:
  clean 17.04 install on a desktop PC (NOT laptop, only wired connection
  does not have a wireless network card)

  the network indicator, top bar/panel is wrong. it is showing the
  cogwheel. it is like this since i can remember (15.04 + on desktop)

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

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

[Touch-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login

[Alberts Muktupāvels]

What do you mean with current zesty? I just installed all updates (I
don't use proposed), but I have not restarted pc and/or lightdm...

If /usr/lib/lightdm/lightdm-greeter-session has this line:
eval `dbus-launch --sh-syntax`

Then my second seat / session works - I can logout & login without
problems.

When I restore this line:
[ -n "$DBUS_SESSION_BUS_ADDRESS" ] || eval `dbus-launch --sh-syntax`

Problem is back. Every time I try to login unity-settings-daemon started
from lightdm is still running...

alberts@ga-b75m-d3h:~$ loginctl
   SESSIONUID USER SEAT TTY 
c4   1001 flashbackseat1
 2120 debian-spamd  /dev/pts/8  
   c42   1001 flashbackseat1
c3   1000 alberts  seat0
   c43111 lightdm  seat1
   c44   1001 flashbackseat1

6 sessions listed.

alberts@ga-b75m-d3h:~$ loginctl session-status c43
c43 - lightdm (111)
   Since: Tue 2016-11-08 18:16:59 EET; 2min 3s ago
  Leader: 20942
Seat: seat1
 Display: :0
 Service: lightdm-greeter; type x11; class greeter
   State: closing
Unit: session-c43.scope
  ├─20972 /usr/lib/at-spi2-core/at-spi2-registryd 
--use-gnome-session
  ├─20983 nm-applet
  └─20985 /usr/lib/unity-settings-daemon/unity-settings-daemon

nov 08 18:16:59 ga-b75m-d3h systemd[1]: Started Session c43 of user lightdm.
nov 08 18:16:59 ga-b75m-d3h org.a11y.atspi.Registry[20970]: SpiRegistry daemon 
is running with well-known name - org.a11y.atsp
nov 08 18:17:03 ga-b75m-d3h lightdm[20942]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

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

Title:
  lightdm greeter session not properly shut down at login

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I am using lightdm with 2 seats. After 2409 revision randomly one of
  two seats does not work correctly.

  xsettings plugin from unity-settings-daemon or gnome-settings-deamon
  fails to start because there is already _XSESSION_S* manager running.

  After revision 2409 in system monitor I see that there is still
  running unity-settings-daemon started by lightdm. Reverting this
  revision fixes my problem.

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

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

[Touch-packages] [Bug 1640214] Re: [unity8][desktop] wrong network indicator icon - cogwheel

[dinamic]

indicator-network log (if it helps)

Debug: nmofono::KillSwitch::KillSwitch(const QDBusConnection&) reply.isValid() 
false reply.value() true reply.error() 
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name 
org.freedesktop.URfkill was not provided by any .service files") ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/0" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/1" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/2" ((null):0, 
(null))
Debug: Unlock all modems ((null):0, (null))

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

Title:
  [unity8][desktop] wrong network indicator icon  - cogwheel

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

Bug description:
  clean 17.04 install on a desktop PC (NOT laptop, only wired connection
  does not have a wireless network card)

  the network indicator, top bar/panel is wrong. it is showing the
  cogwheel. it is like this since i can remember (15.04 + on desktop)

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

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

[Brian Murray]

** Changed in: unattended-upgrades (Ubuntu Yakkety)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: unattended-upgrades (Ubuntu Yakkety)
   Status: Triaged => In Progress

-- 
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:
  Triaged
Status in unattended-upgrades source package in Yakkety:
  In Progress

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

[Brian Murray]

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

-- 
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 1639249] Re: Result art not displayed when run in a snap

[Paweł Stołowski]

Here is the error returned by thumbnailer in the unity8-dash.log when
processing image://thumbnailer/file:/// uris:

[2016-11-08:16:59:24.600] Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus 
error: Handler::checkFinished(): no artwork for thumbnail: 
/snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/albumart3.png
 (67,0): NO ARTWORK
[2016-11-08:16:59:24.601] Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus 
error: Handler::checkFinished(): no artwork for thumbnail: 
/snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/art2.jpg
 (184,0): NO ARTWORK
[2016-11-08:16:59:24.604] Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus 
error: Handler::checkFinished(): no artwork for thumbnail: 
/snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/albumart2.png
 (67,0): NO ARTWORK
[2016-11-08:16:59:24.622] :46:33: QML 
CroppedImageMinimumSourceSize: Thumbnailer: RequestImpl::dbusCallFinished(): 
D-Bus error: Handler::checkFinished(): no artwork for thumbnail: 
/snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/albumart3.png
 (67,0): NO ARTWORK
[2016-11-08:16:59:24.622] :46:33: QML 
CroppedImageMinimumSourceSize: Thumbnailer: RequestImpl::dbusCallFinished(): 
D-Bus error: Handler::checkFinished(): no artwork for thumbnail: 
/snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/art2.jpg
 (184,0): NO ARTWORK
[2016-11-08:16:59:24.622] :46:33: QML 
CroppedImageMinimumSourceSize: Thumbnailer: RequestImpl::dbusCallFinished(): 
D-Bus error: Handler::checkFinished(): no artwork for thumbnail: 
/snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/albumart2.png
 (67,0): NO ARTWORK

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

Title:
  Result art not displayed when run in a snap

Status in unity-scopes-api package in Ubuntu:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  When a scope calls result.set_art() the path is not adjusted to take
  in consideration $SNAP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1639249/+subscriptions

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

[Touch-packages] [Bug 1640214] Re: [unity8][desktop] wrong network indicator icon - cogwheel

[dinamic]

i can't take attach a screenshot because if i press the print screen key
it crashes/locks the shell. the shell is inactive, with the mouse
locked, i can't move the mouse.

so this is a clean install, i changed nothing, i don't have proposed
active etc. just a clean daily build install

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

Title:
  [unity8][desktop] wrong network indicator icon  - cogwheel

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

Bug description:
  clean 17.04 install on a desktop PC (NOT laptop, only wired connection
  does not have a wireless network card)

  the network indicator, top bar/panel is wrong. it is showing the
  cogwheel. it is like this since i can remember (15.04 + on desktop)

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

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

[Brian Murray]

** Tags added: yakkety

-- 
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:
  Triaged
Status in unattended-upgrades source package in Yakkety:
  In Progress

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 1589401] Re: cannot view wifi networks after re-enabling wifi

[Hansen]

On Bugzilla one ask's:
---
It would be useful to have also NM logs. Would you please set:

  [logging]
  level=TRACE

in /etc/NetworkManager/NetworkManager.conf, restart the NM service,
reproduce the issue and then attach the journal log ('journalctl -u
NetworkManager -b')? Thanks!

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

Title:
  cannot view wifi networks after re-enabling wifi

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

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

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

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

[Touch-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login

[Martin Pitt]

> This is from https://code.launchpad.net/~pitti/unity-greeter/systemd-
indicators/+merge/309321, we need to stop nm-applet and the unity-
settings-daemon from the lightdm session. I retitle the bug accordingly.

Actually, no -- this MP didn't even land yet, so the leaked unity-
settings-daemon and nm-applet are still from the upstart-controlled
session. So, can you please upgrade to current zesty and re-confirm? If
you still get this, please give me the output of "loginctl" and
"loginctl session-status XX" where XX is the session number (like "c1")
from the first command that applies to lightdm.

** Changed in: unity-greeter (Ubuntu)
   Status: In Progress => Incomplete

** Package changed: unity-greeter (Ubuntu) => lightdm (Ubuntu)

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

Title:
  lightdm greeter session not properly shut down at login

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I am using lightdm with 2 seats. After 2409 revision randomly one of
  two seats does not work correctly.

  xsettings plugin from unity-settings-daemon or gnome-settings-deamon
  fails to start because there is already _XSESSION_S* manager running.

  After revision 2409 in system monitor I see that there is still
  running unity-settings-daemon started by lightdm. Reverting this
  revision fixes my problem.

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

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

[Touch-packages] [Bug 1640214] Re: [unity8][desktop] wrong network indicator icon - cogwheel

[Lukáš Tinkl]

Is indicator-network running for you? Can you please attach a
screenshot?

$ indicator-network

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

Title:
  [unity8][desktop] wrong network indicator icon  - cogwheel

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

Bug description:
  clean 17.04 install on a desktop PC (NOT laptop, only wired connection
  does not have a wireless network card)

  the network indicator, top bar/panel is wrong. it is showing the
  cogwheel. it is like this since i can remember (15.04 + on desktop)

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

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

[Touch-packages] [Bug 1589005] Re: After update DNS work unstable

[Arno Mühren]

I also still have this problem with 1.2.2-0ubuntu0.16.04.3 amd64
Only version 1.1.93 works for me on 16.04.

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => 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/1589005

Title:
  After update DNS work unstable

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.

  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'

  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal
  update.

  workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
  and lock version 
  echo "network-manager hold" | sudo dpkg --set-selections

  "apt update" going to show network-manager as upgradable but "apt
  upgrage" going to ignore it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 01:39:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-01 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.100.1 dev enp8s0  proto static  metric 100
   169.254.0.0/16 dev enp8s0  scope link  metric 1000
   192.168.100.0/24 dev enp8s0  proto kernel  scope link  src 192.168.100.9  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  802-3-ethernet 
  1464993435  Sat 04 Jun 2016 01:37:15 MSK  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  yes enp8s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
   HUAWEI-KpW2 1   8087b7e0-51dc-43c4-8928-4d03c85a5762  
802-11-wireless  1464546384  Sun 29 May 2016 21:26:24 MSK  yes  0   
  no/org/freedesktop/NetworkManager/Settings/1  no  --  
-- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   enp8s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  
/org/freedesktop/NetworkManager/ActiveConnection/0
   wlp9s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1640214] [NEW] [unity8][desktop] wrong network indicator icon - cogwheel

[dinamic]

Public bug reported:

clean 17.04 install on a desktop PC (NOT laptop, only wired connection
does not have a wireless network card)

the network indicator, top bar/panel is wrong. it is showing the
cogwheel. it is like this since i can remember (15.04 + on desktop)

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

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

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

Title:
  [unity8][desktop] wrong network indicator icon  - cogwheel

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

Bug description:
  clean 17.04 install on a desktop PC (NOT laptop, only wired connection
  does not have a wireless network card)

  the network indicator, top bar/panel is wrong. it is showing the
  cogwheel. it is like this since i can remember (15.04 + on desktop)

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

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