[Touch-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

[Alok Parlikar]

Hi Konrad,

Please see my syslog attached.


** Attachment added: "aup.syslog"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163/+attachment/4656103/+files/aup.syslog

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions

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

[Touch-packages] [Bug 1578488] [NEW] package shared-mime-info 1.5-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Jesse Gonzalez]

Public bug reported:

This appeared after a do-release upgrade.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu May  5 00:13:38 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.5-2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
UpgradeStatus: Upgraded to xenial on 2016-05-05 (0 days ago)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package shared-mime-info 1.5-2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  This appeared after a do-release upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May  5 00:13:38 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UpgradeStatus: Upgraded to xenial on 2016-05-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1578488/+subscriptions

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

[Touch-packages] [Bug 1578461] Re: Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*) all crash on start-up in libhybris [linker.c:27: android_dlopen: Assertion `0' failed.']

[Daniel van Vugt]

** Description changed:

  Having mir-graphics-drivers-android9:amd64 installed prevents unity-
  system-compositor starting:
  
  [2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  android_dlopen called but not implemented!
  unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.
  
  which was caused by:
  
  sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay
  
  WORKING: hybris 0.1.0+git20151016+6d424c9-0ubuntu7
  FAILING: hybris 0.1.0+git20151016+6d424c9-0ubuntu11
+ 
+ WORKAROUNDS:
+  * Remove ppa:ci-train-ppa-service/stable-phone-overlay from your system to 
completely solve the problem; or
+  * Don't use Unity8 -- other Mir servers will work after you remove package 
mir-graphics-drivers-android9:amd64 which is their last remaining dependency on 
libhybris.

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

Title:
  Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*)
  all crash on start-up in libhybris [linker.c:27: android_dlopen:
  Assertion `0' failed.']

Status in Mir:
  New
Status in Mir 0.22 series:
  New
Status in Mir 0.23 series:
  New
Status in libhybris package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Having mir-graphics-drivers-android9:amd64 installed prevents unity-
  system-compositor starting:

  [2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  android_dlopen called but not implemented!
  unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.

  which was caused by:

  sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay

  WORKING: hybris 0.1.0+git20151016+6d424c9-0ubuntu7
  FAILING: hybris 0.1.0+git20151016+6d424c9-0ubuntu11

  WORKAROUNDS:
   * Remove ppa:ci-train-ppa-service/stable-phone-overlay from your system to 
completely solve the problem; or
   * Don't use Unity8 -- other Mir servers will work after you remove package 
mir-graphics-drivers-android9:amd64 which is their last remaining dependency on 
libhybris.

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

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

[Touch-packages] [Bug 1578410] Re: No way to discover the "side stage" exists

[Launchpad Bug Tracker]

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

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

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

Title:
  No way to discover the "side stage" exists

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

Bug description:
  When using tablet there's no info about "side stage". Only way to know
  about it is from someone who knows and tell you or if you by mistake
  do a gesture to activate "side stage".

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

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

[Touch-packages] [Bug 1576558] Re: Align Hebrew on the right in the Wizard

[Daniel van Vugt]

Surely Arabic and others will have the same issue.

Why not just centre them all?

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

Title:
  Align Hebrew on the right in the Wizard

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  From https://bugs.launchpad.net/avila-private/+bug/1555050

  Steps:
  1. Display de available languages on wizard

  Actual Results:
  the Hebrew language is arranged on the left

  Expected Results:
  language name should be arranged on the right

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

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

[Touch-packages] [Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[Jeromie Rand]

Can confirm that I get the same error as jontyl when clicking on the
Power item in system settings.

Disabling lightdm and manually starting it after booting the computer
does not seem to impact the bug for me.

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+subscriptions

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

[Touch-packages] [Bug 1573862] Re: package apt 1.2.10ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6

[Alberto Salvia Novella]

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

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

Title:
  package apt 1.2.10ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 6

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  updated from 15.10 to 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 22 17:42:24 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 6
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: apt
  Title: package apt 1.2.10ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 6
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

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

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

[Touch-packages] [Bug 1570921] Re: suspend not working

[Alberto Salvia Novella]

** Changed in: pm-utils (Ubuntu)
   Importance: Undecided => High

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

Title:
  suspend not working

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  My computer cannot go to suspend state.  The monitor switch off but the 
cpu/cpu fan keeps running and the hard drive is active.
  It doesn't respond, I need to switch off manually to reboot the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 15 18:42:49 2016
  InstallationDate: Installed on 2016-04-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160414)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Alberto Salvia Novella]

** Changed in: hicolor-icon-theme (Ubuntu)
   Importance: Undecided => High

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

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

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

Bug description:
  This issue first appeared during Dist upgrade for 15 to 16

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 29 06:50:44 2016
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-05-16 (349 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1553211] Re: gnome-software does not treat recommends and suggests as plugins to applications | impossible to install "technical" packages (plugins, kernels...) | Ubuntu desktop

[Alberto Salvia Novella]

** Changed in: gnome-software (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: gnome-software (Ubuntu)
   Importance: Low => Medium

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

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

Title:
  gnome-software does not treat recommends and suggests as plugins to
  applications | impossible to install "technical" packages (plugins,
  kernels...) | Ubuntu desktop no longer provide graphical method to
  install non-GUI software components

Status in GNOME Software:
  Invalid
Status in gnome-software package in Ubuntu:
  Won't Fix
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 will be useless for "normal" people if they can't find every 
software package as they did before.
  To force users to use gnome-software will be a regression!

  Examples:

  In old Software Center, you could add gimp plug-ins (plug-ins are recommends 
and suggests packages of gimp) by going in gimp description and check the 
plug-ins you want!
  In old Software Center, you could install another version of linux kernel by 
typing "linux" then click at bottom left to show the packages.

  Now, they have to use apt-get or install synaptic!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.91~git20160229.ceb6b9d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar  4 15:06:20 2016
  InstallationDate: Installed on 2016-01-07 (57 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160105)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 790433] Re: radeon driver crashes (freezing the system) on 11.04 when forcing KMS on Power G5

[Launchpad Bug Tracker]

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

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

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

Title:
  radeon driver crashes (freezing the system) on 11.04 when forcing KMS
  on Power G5

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Body:

  I enforced KMS by specifying radeon.modeset=1.
  Unity does not start at all. Metacity starts but gnome-panel kills the
  machine, somewhere inside radeon driver. See the last messages from
  /var/log/syslog: http://pastebin.com/6JLUCZXq

   affects ubuntu

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

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

[Touch-packages] [Bug 1474546] Re: [regression] multi monitor, display port to hdmi not working

[Launchpad Bug Tracker]

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

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

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

Title:
  [regression] multi monitor, display port to hdmi not working

Status in xorg package in Ubuntu:
  Expired

Bug description:
  This could very well be a problem further down in kms or elsewhere in the 
graphics stack.
  I recently updated from vivid to wily.
  I had a very reliable setup of being able to connect an external monitor to 
my macbook display port for an "extended" dektop view (not clone). This now 
flickers in quadrants, and the flickering quadrants on the monitor 
  video shows it best
  http://www.youtube.com/watch?v=ElXAyX93Uqw

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

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

[Touch-packages] [Bug 1508573] Re: X11 keeps booting in failsafe mode due to xorg.conf having the nvidia set as primary GPU.

[Launchpad Bug Tracker]

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

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

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

Title:
  X11 keeps booting in failsafe mode due to xorg.conf having the nvidia
  set as primary GPU.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  removing the nvidia-driver and /etc/X11/xorg.conf and manually
  launching lightdm from the command-line solves it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bumblebee 3.2.1-9
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 21 20:56:04 2015
  InstallationDate: Installed on 2014-11-08 (347 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=nl_NL
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: bumblebee
  UpgradeStatus: Upgraded to wily on 2015-10-19 (2 days ago)
  mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-10-21T20:48:11.549384
  mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-10-21T20:48:51.188097

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

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

[Touch-packages] [Bug 1340648] Re: bumblebee & nvidia-driver doesn`t detect discrete graphic card

[Launchpad Bug Tracker]

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

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

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

Title:
  bumblebee & nvidia-driver doesn`t detect discrete graphic card

Status in xorg package in Ubuntu:
  Expired

Bug description:

  After  update xserver-xorg-core & xserver-xorg-common  1.14.5 to 1.14.6,  
  GPU  PCI ID  is  correct  in xserver  conf &  bumblebee co f is also  
correct,  with  xserver 1.15.1  all work  fine.

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

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

[Touch-packages] [Bug 1544653] Re: AMD graphic card 7670m too hot

[Launchpad Bug Tracker]

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

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

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

Title:
  AMD graphic card 7670m too hot

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a toshiba laptop M840, which has a AMD graphic card Radeon HD
  7670m (Intel GPU is disable by default).  With opensource driver, my
  CPU 's temperature is always above 90 celsius. When i try with
  proprietary driver, the temperature is about 80 celsius but is still
  too hot.

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

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

[Touch-packages] [Bug 1406057] Re: Xorg memory leak in Kubuntu

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg memory leak in Kubuntu

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The Xorg process consumed more than 1GB after a few days of up-time, however, 
kwin process only used 60MB of memory, which could indicate it is different bug 
than the #1402551. Scrolling and switching between windows have become 
noticably slower. Probably this happened after I wrote and tested several Java 
GUI applications, but closing all of the GUI applications doesn't reduce the 
memory usage.
  I am using the default intel graphics driver. I have nvidia but didn't use 
it. 

  lsb_release -rd
  Description:Ubuntu 12.04.5 LTS
  Release:12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-core-lts-trusty 2:1.15.1-0ubuntu2~precise4
  ProcVersionSignature: Ubuntu 3.13.0-40.69~precise1-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Sun Dec 28 14:50:23 2014
  ExecutablePath: /usr/bin/Xorg
  InstallationMedia: Kubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: xorg-server-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1574067] Re: Upgraded 14.04 to 16.04 (forcing upgrade from terminal) - after reboot package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Alberto Salvia Novella]

** Changed in: ca-certificates (Ubuntu)
   Importance: Undecided => High

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

Title:
  Upgraded 14.04 to 16.04 (forcing upgrade from terminal) - after reboot
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Never had the issue on 14.04, comes on every reboot on 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  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
  Date: Fri Apr 22 13:27:18 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-01-17 (462 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1574266] Re: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

[Alberto Salvia Novella]

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

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

Title:
  Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  dmesg output :

  [ 8815.416923] [drm] stuck on render ring
  [ 8815.417367] [drm] GPU HANG: ecode 6:0:0x05b2c6c5, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8815.419462] drm/i915: Resetting chip after gpu hang
  [ 8821.417592] [drm] stuck on render ring
  [ 8821.418007] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8821.420108] drm/i915: Resetting chip after gpu hang
  [ 8827.430254] [drm] stuck on render ring
  [ 8827.430672] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8827.432786] drm/i915: Resetting chip after gpu hang
  [ 8833.418862] [drm] stuck on render ring
  [ 8833.419454] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8833.421551] drm/i915: Resetting chip after gpu hang
  [ 8839.419503] [drm] stuck on render ring
  [ 8839.419971] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8839.422060] drm/i915: Resetting chip after gpu hang
  [ 8845.432118] [drm] stuck on render ring
  [ 8845.432647] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8845.434799] drm/i915: Resetting chip after gpu hang
  [ 8851.432751] [drm] stuck on render ring
  [ 8851.433142] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8851.435224] drm/i915: Resetting chip after gpu hang
  [ 8857.457381] [drm] stuck on render ring
  [ 8857.457797] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8857.459883] drm/i915: Resetting chip after gpu hang
  [ 8863.458003] [drm] stuck on render ring
  [ 8863.458555] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8863.460640] drm/i915: Resetting chip after gpu hang
  [ 8869.458654] [drm] stuck on render ring
  [ 8869.459001] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8869.459095] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too 
fast, banning!
  [ 8869.461116] drm/i915: Resetting chip after gpu hang
  [ 8875.435238] [drm] stuck on render ring
  [ 8875.435606] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8875.437697] drm/i915: Resetting chip after gpu hang
  [ 8881.447863] [drm] stuck on render ring
  [ 8881.448251] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8881.450331] drm/i915: Resetting chip after gpu hang
  [ 8887.436497] [drm] stuck on render ring
  [ 8887.436876] [drm] GPU HANG: ecode 6:0:0xbb88, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8887.438961] drm/i915: Resetting chip after gpu hang
  [ 8893.437078] [drm] stuck on render ring
  [ 8893.437471] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8893.439562] drm/i915: Resetting chip after gpu hang

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Sun Apr 24 15:57:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2002]
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=45576678-3e92-4769-b6d3-3e3cafa54c2e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: 

[Touch-packages] [Bug 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

[Alberto Salvia Novella]

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

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

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  Don't run aplication after upgrade from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  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
  Date: Sun Apr 24 21:08:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1285444] Re: Login Successful, Desktop Never Loads

[Alberto Salvia Novella]

** Changed in: at-spi2-core (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Login Successful, Desktop Never Loads

Status in at-spi2-core package in Ubuntu:
  Confirmed

Bug description:
  Here is what I encounter
  1. Boot computer, boot proceeds normally
  2. Reach standard Ubuntu login screen, nothing seems to be amiss
  3. Enter user name and password
  4. Login disappears, just see the pink "Ubuntu 14.04" background

  The desktop never loads, not even after ~30 minutes. The launcher
  never appears, and the Desktop background never changes to the user-
  configured background.

  Other features:
  * Cursor works fine, it can be moved around the screen
  * No error messages pop up
  * ALT+F1 etc. can be used to switch to different TTYs; all files on the 
system appear to be intact
  * Print screen button works (I will upload a screen shot when I get a chance 
to copy it onto a USB drive)
  * Hitting power button pops up a window prompting the user to decide whether 
to shut down
  * CTRL+ALT+DELETE prompts the user to log out
  * Desktop does not load on any user accounts, including the guest account

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions

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

[Touch-packages] [Bug 1578469] [NEW] Crashes in unity8 cause infinite restarts and/or a permanently black screen

[Daniel van Vugt]

Public bug reported:

Crashes in unity8 cause infinite restarts and/or a permanently black
screen.

As experienced in bug 1578462.

I guess the problem is the 'respawn' keyword in:
   /usr/share/upstart/sessions/unity8.conf
[http://upstart.ubuntu.com/cookbook/#respawn]

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


** Tags: black-screen

** Tags added: black-screen

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

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

Title:
  Crashes in unity8 cause infinite restarts and/or a permanently black
  screen

Status in unity8 package in Ubuntu:
  New

Bug description:
  Crashes in unity8 cause infinite restarts and/or a permanently black
  screen.

  As experienced in bug 1578462.

  I guess the problem is the 'respawn' keyword in:
 /usr/share/upstart/sessions/unity8.conf
  [http://upstart.ubuntu.com/cookbook/#respawn]

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

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

[Touch-packages] [Bug 1550972] Re: Nvidia Prime graphics: unity8-dash crashed with SIGSEGV in glGetString()

[Daniel van Vugt]

** Changed in: mir
 Assignee: (unassigned) => Chris Halse Rogers (raof)

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

** Tags added: black-screen

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

Title:
  Nvidia Prime graphics: unity8-dash crashed with SIGSEGV in
  glGetString()

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Lenovo Y50 notebook with NVidia Prime profile. Login with unity8 shows
  black screen. Login with ubuntu works fine.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Feb 28 19:27:08 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2014-10-02 (514 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   glGetString () from /usr/lib/nvidia-340-updates/libGL.so.1
   QOpenGLContext::makeCurrent(QSurface*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   start_thread (arg=0x7f1e26dc9700) at pthread_create.c:333
  Title: unity8-dash crashed with SIGSEGV in glGetString()
  UpgradeStatus: Upgraded to xenial on 2016-02-21 (7 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1284655] Re: unity8 crashed with SIGABRT in qt_message_fatal()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1407556
   Wrong Qt backend used in desktop session (xcb vs. Mir)
** This bug has been marked a duplicate of bug 1526658
   Mir clients (including Unity8 itself) crash in XGetXCBConnection() if 
multiple versions of mir-client-platform-mesa are installed.

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

Title:
  unity8 crashed with SIGABRT in qt_message_fatal()

Status in unity8 package in Ubuntu:
  Expired

Bug description:
  failed to start unity8

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140221-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Feb 25 14:17:48 2014
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2014-01-31 (24 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140130)
  ProcCmdline: unity8
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QGuiApplicationPrivate::createPlatformIntegration() () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: unity8 crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1407556] Re: Wrong Qt backend used in desktop session (xcb vs. Mir)

[Daniel van Vugt]

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

I'm assuming we fixed this in bug 1526658

** This bug has been marked a duplicate of bug 1526658
   Mir clients (including Unity8 itself) crash in XGetXCBConnection() if 
multiple versions of mir-client-platform-mesa are installed.

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

Title:
  Wrong Qt backend used in desktop session (xcb vs. Mir)

Status in unity8 package in Ubuntu:
  Incomplete
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  I installed unity8-desktop-session-mir in my vmplayer vivid guest and
  tried logging into it, got only a black screen, and found a unity8
  crash file in the /var/crash afterwards.

  I also almost always (9 out of 10 times) get a black screen if I try
  to log into a ubuntu-desktop-mir session, and if I do manage to get a
  normal screen with ubuntu-desktop-mir, resizing it gives me the black
  screen. So this might be related to a bug in mir.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20141216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  Date: Mon Jan  5 11:03:29 2015
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1418728702
  InstallationDate: Installed on 2015-01-03 (1 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141220)
  ProcCmdline: unity8
  ProcCwd: /home/rocko
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: unity8 crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.unity8.log:
   ()
   QXcbConnection: Could not connect to display

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

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

[Touch-packages] [Bug 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

[Daniel van Vugt]

** Tags added: black-screen

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

Title:
  Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT:
  "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtdeclarative package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

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

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

[Touch-packages] [Bug 1433013] Re: Super -> exec vs Alt-F2 -> exec have different environment

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.13.2-0ubuntu23

---
upstart (1.13.2-0ubuntu23) yakkety; urgency=medium

  * Cherry-pick upstream fix to publish global session variable changes to
the dbus environment.  LP: #1433013.

 -- Steve Langasek   Fri, 29 Apr 2016
14:38:53 -0700

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

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

Title:
  Super -> exec vs Alt-F2 -> exec have different environment

Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Won't Fix
Status in upstart source package in Vivid:
  Confirmed

Bug description:
  upstart in user session manages environmental variables and most
  things have them, however Alt-f2 started proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

  Alt+F2 -> "xterm" -> Enter -> env | grep SSH

  via Super Key -> the environment is correct

  via Alt-F2 -> it is not

  
  I believe Alt+F2 code path should call into upstart dbus api to "list-env" 
and import that environment before executing the search result.

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

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

[Touch-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

[Gunnar Hjalmarsson]

Fixed in lightdm 1.19.0-0ubuntu1

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

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Fix Committed
Status in lxsession source package in Xenial:
  New

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1438150] Re: AllDay events imported from Google displayed on 2 days

[Phil UK]

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

This is still an issue and as yet there has not been any update to
resolve this. Is there any update or eta for this fix?

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

Title:
  AllDay events imported from Google displayed on 2 days

Status in Ubuntu Calendar App:
  New
Status in qtorganizer5-eds package in Ubuntu:
  New

Bug description:
  AllDay events like Birthday imported from Google calendar are always
  displayed on 2 days. May be this is because of unexpected time zone,
  my location is Germany.

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

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

[Touch-packages] [Bug 1577641] Re: Unity8 creates a blank black window for windowless apps

[Daniel van Vugt]

In xenial it's still a problem.

I also just tried the PPA where dandrader says new fixes exist, but
can't test it due to many crashes: bug 1578461

** Changed in: unity8 (Ubuntu)
   Status: Incomplete => 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/1577641

Title:
  Unity8 creates a blank black window for windowless apps

Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 creates a blank black window for windowless apps.

  Windowless apps are closer thank you think:   Xmir -rootless
  is one such example while no X apps have started yet.

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

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

[Touch-packages] [Bug 1578461] Re: Mir servers (unity8, unity-syste-compositor, mir_demo*) crash on start-up in libhybris [linker.c:27: android_dlopen: Assertion `0' failed.']

[Daniel van Vugt]

See bug 1578462 which shows removing the android graphics driver is not
enough to stop the crash from happening. Because unity8 seems to use
hybris directly.

** Summary changed:

- Mir servers (unity8, unity-syste-compositor, mir_demo*) crash on start-up in 
libhybris [linker.c:27: android_dlopen: Assertion `0' failed.']
+ Black screen: Mir servers (unity8, unity-syste-compositor, mir_demo*) all 
crash on start-up in libhybris [linker.c:27: android_dlopen: Assertion `0' 
failed.']

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

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

** Also affects: unity-system-compositor (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-system-compositor (Ubuntu)
   Importance: Undecided => Critical

** Summary changed:

- Black screen: Mir servers (unity8, unity-syste-compositor, mir_demo*) all 
crash on start-up in libhybris [linker.c:27: android_dlopen: Assertion `0' 
failed.']
+ Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*) all 
crash on start-up in libhybris [linker.c:27: android_dlopen: Assertion `0' 
failed.']

** Description changed:

  Having mir-graphics-drivers-android9:amd64 installed prevents unity-
  system-compositor starting:
  
  [2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  android_dlopen called but not implemented!
  unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.
  
  which was caused by:
  
  sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay
+ 
+ WORKING: hybris 0.1.0+git20151016+6d424c9-0ubuntu7
+ FAILING: hybris 0.1.0+git20151016+6d424c9-0ubuntu11

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

Title:
  Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*)
  all crash on start-up in libhybris [linker.c:27: android_dlopen:
  Assertion `0' failed.']

Status in Mir:
  New
Status in Mir 0.22 series:
  New
Status in Mir 0.23 series:
  New
Status in libhybris package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Having mir-graphics-drivers-android9:amd64 installed prevents unity-
  system-compositor starting:

  [2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  android_dlopen called but not implemented!
  unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.

  which was caused by:

  sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay

  WORKING: hybris 0.1.0+git20151016+6d424c9-0ubuntu7
  FAILING: hybris 0.1.0+git20151016+6d424c9-0ubuntu11

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

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

[Touch-packages] [Bug 1578461] Re: Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*) all crash on start-up in libhybris [linker.c:27: android_dlopen: Assertion `0' failed.']

[Daniel van Vugt]

This sounds relevant:

libhybris (0.1.0+git20151016+6d424c9-0ubuntu11) xenial; urgency=medium

  * hybris: common: add stub linker implementation<- 
  * debian: split out common parts of the default configuration
  * debian: add build support for arm64
  * hybris: add README file stating which architectures are supported
  * hybris: autotools want it to be README

 -- Simon Fels   Tue, 03 May 2016 17:29:41
+0200

** Changed in: libhybris (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

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

Title:
  Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*)
  all crash on start-up in libhybris [linker.c:27: android_dlopen:
  Assertion `0' failed.']

Status in Mir:
  New
Status in Mir 0.22 series:
  New
Status in Mir 0.23 series:
  New
Status in libhybris package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Having mir-graphics-drivers-android9:amd64 installed prevents unity-
  system-compositor starting:

  [2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  android_dlopen called but not implemented!
  unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.

  which was caused by:

  sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay

  WORKING: hybris 0.1.0+git20151016+6d424c9-0ubuntu7
  FAILING: hybris 0.1.0+git20151016+6d424c9-0ubuntu11

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

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

[Touch-packages] [Bug 1578461] Re: Having mir-graphics-drivers-android9:amd64 installed prevents unity-system-compositor starting: 'unity-system-compositor: linker.c:27: android_dlopen: Assertion `0'

[Daniel van Vugt]

It appears the crash is in libhybris. Which is not only used by the Mir
Android platform, but also used by Unity8 directly!

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

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

** Tags added: black-screen

** Summary changed:

- Having mir-graphics-drivers-android9:amd64 installed prevents 
unity-system-compositor starting: 'unity-system-compositor: linker.c:27: 
android_dlopen: Assertion `0' failed.'
+ Mir servers (unity8, unity-syste-compositor, mir_demo*) crash on start-up in 
libhybris [linker.c:27: android_dlopen: Assertion `0' failed.']

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

Title:
  Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*)
  all crash on start-up in libhybris [linker.c:27: android_dlopen:
  Assertion `0' failed.']

Status in Mir:
  New
Status in Mir 0.22 series:
  New
Status in Mir 0.23 series:
  New
Status in libhybris package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Having mir-graphics-drivers-android9:amd64 installed prevents unity-
  system-compositor starting:

  [2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  android_dlopen called but not implemented!
  unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.

  which was caused by:

  sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay

  WORKING: hybris 0.1.0+git20151016+6d424c9-0ubuntu7
  FAILING: hybris 0.1.0+git20151016+6d424c9-0ubuntu11

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

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

[Touch-packages] [Bug 1578462] Re: Black screen: Unity8 crashes and restarts continuously: unity8: linker.c:27: android_dlopen: Assertion `0' failed.

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1578461
   Mir servers (unity8, unity-syste-compositor, mir_demo*) crash on start-up in 
libhybris [linker.c:27: android_dlopen: Assertion `0' failed.']

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

Title:
  Black screen: Unity8 crashes and restarts continuously: unity8:
  linker.c:27: android_dlopen: Assertion `0' failed.

Status in Mir:
  New
Status in libhybris package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Black screen: Unity8 crashes and restarts continuously:

  qtmir.sessions: SessionManager::SessionManager - this= 
qtmir::SessionManager(0xff6630)
  qtmir.surfaces: MirSurfaceManager::MirSurfaceManager - this= 
qtmir::MirSurfaceManager(0xff7500)
  qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0)
  unity.topsurfacelist: 
setApplicationsModel(qtmir::ApplicationManager(0xfccf80, name = 
qtmir::ApplicationManager))
  GStreamer; Unable to pause - "file:///system/media/audio/ui/camera_click.ogg"
  qtmir.mir: SessionAuthorizer::connection_is_allowed - this= 
SessionAuthorizer(0x7f5ae8129990) pid= 25176
  android_dlopen called but not implemented!
  unity8: linker.c:27: android_dlopen: Assertion `0' failed.
  ()
  qtmir.screens: ScreensModel::ScreensModel
  [2016-05-05 10:28:39.273657] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  [2016-05-05 10:28:39.273699] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.22.0)
  [2016-05-05 10:28:39.273813] mirplatform: Found graphics driver: dummy 
(version 0.22.0)
  [2016-05-05 10:28:39.273822] mirplatform: Found graphics driver: 
throw-on-creation (version 0.22.0)
  qtmir.mir: MirServer created

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

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

[Touch-packages] [Bug 1543467] Re: Unity8 can't correctly display multi-surface apps (including menus and tooltips)

[Daniel van Vugt]

Sorry, that PPA killed my machine:  bug 1578461 and bug 1578462

Can we make the qtmir and unity8 tasks Fix Committed instead? At least
till the fixes reach the Ubuntu distro?

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

Title:
  Unity8 can't correctly display multi-surface apps (including menus and
  tooltips)

Status in QtMir:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Unity8 can't display multi-surface apps (including menus and
  tooltips).

  Fixing bug 1497085 was a great start. However instead of crashing
  Unity8 now just shows the most recently created window by the app in
  the apps /single window/, and stretches it too. When such a secondary
  window like a menu or tooltip closes, you never get back to the
  original app window. So existing apps still aren't quite usable yet.

  Test case:
  sudo apt-get install mir-demos
  mir_demo_client_multiwin -- --desktop_file_hint=unity8

  Expected: Three windows (red, green, blue)
  Observed: Only the blue window

  You can also experience the same bug with lots of apps via:  Xmir
  -rootless under Unity8.

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

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

[Touch-packages] [Bug 1578462] Re: Black screen: Unity8 crashes and restarts continuously: unity8: linker.c:27: android_dlopen: Assertion `0' failed.

[Daniel van Vugt]

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

It appears the crash is in libhybris. Which is not only used by the Mir
Android platform, but also used by Unity8 directly!

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

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

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

Title:
  Black screen: Unity8 crashes and restarts continuously: unity8:
  linker.c:27: android_dlopen: Assertion `0' failed.

Status in Mir:
  New
Status in libhybris package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Black screen: Unity8 crashes and restarts continuously:

  qtmir.sessions: SessionManager::SessionManager - this= 
qtmir::SessionManager(0xff6630)
  qtmir.surfaces: MirSurfaceManager::MirSurfaceManager - this= 
qtmir::MirSurfaceManager(0xff7500)
  qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0)
  unity.topsurfacelist: 
setApplicationsModel(qtmir::ApplicationManager(0xfccf80, name = 
qtmir::ApplicationManager))
  GStreamer; Unable to pause - "file:///system/media/audio/ui/camera_click.ogg"
  qtmir.mir: SessionAuthorizer::connection_is_allowed - this= 
SessionAuthorizer(0x7f5ae8129990) pid= 25176
  android_dlopen called but not implemented!
  unity8: linker.c:27: android_dlopen: Assertion `0' failed.
  ()
  qtmir.screens: ScreensModel::ScreensModel
  [2016-05-05 10:28:39.273657] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  [2016-05-05 10:28:39.273699] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.22.0)
  [2016-05-05 10:28:39.273813] mirplatform: Found graphics driver: dummy 
(version 0.22.0)
  [2016-05-05 10:28:39.273822] mirplatform: Found graphics driver: 
throw-on-creation (version 0.22.0)
  qtmir.mir: MirServer created

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

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

[Touch-packages] [Bug 1554803] Re: apparmor: missing stub hardware directories

[xtrchessreal]

fyi after install of apparmor-easyprof-ubuntu:

x@x-NICEPUTER:~$ dpkg -l webbrowser-app | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
rc  webbrowser-app 0.23+16.04.20160413-0ubuntu1 amd64Ubuntu web browser

x@x-NICEPUTER:~$ dpkg -S /usr/share/apparmor/hardware/audio.d
apparmor-easyprof-ubuntu: /usr/share/apparmor/hardware/audio.d
x@x-NICEPUTER:~$ dpkg -S /usr/share/apparmor/hardware/graphics.d
apparmor-easyprof-ubuntu: /usr/share/apparmor/hardware/graphics.d
x@x-NICEPUTER:~$ dpkg -S /usr/share/apparmor/hardware/video.d
apparmor-easyprof-ubuntu: /usr/share/apparmor/hardware/video.d

Thanks again and lemme know :)

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

Title:
  apparmor: missing stub hardware directories

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  ● apparmor.service - LSB: AppArmor initialization
 Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
 Active: failed (Result: exit-code) since Tue 2016-03-08 14:34:04 EST; 4h 
23min ago
   Docs: man:systemd-sysv-generator(8)
Process: 2909 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 08 14:34:04 ogre apparmor[2909]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in 
/etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open 
'/usr/share/apparmor/hardware/graphics.d'
  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 08 14:34:04 ogre apparmor[2909]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in 
/etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open 
'/usr/share/apparmor/hardware/graphics.d'
  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 08 14:34:04 ogre apparmor[2909]:...fail!
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Control process exited, 
code=exited status=123
  Mar 08 14:34:04 ogre systemd[1]: Failed to start LSB: AppArmor initialization.
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Unit entered failed state.
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Failed with result 
'exit-code'.

  /usr/share/apparmor/hardware/graphics.d doesn't in fact exist on my
  system. I'm not sure what package would provide it, but it seems
  curious to me that the package doesn't supply its relevant apparmor
  bits. I'd have expected the apparmor package to not complain about
  bits belonging to packages that aren't installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10-3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  8 18:53:31 2016
  InstallationDate: Installed on 2016-02-24 (13 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160219)
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro net.ifnames=0 biosdevname=0
  SourcePackage: apparmor
  Syslog: Mar  8 14:34:05 ogre dbus[3062]: [system] AppArmor D-Bus mediation is 
enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1578462] Re: Black screen: Unity8 crashes and restarts continuously: unity8: linker.c:27: android_dlopen: Assertion `0' failed.

[Daniel van Vugt]

I'm using Unity8 from ppa:ci-train-ppa-service/stable-phone-overlay ...

ii  unity8
8.12+16.04.20160429.2-0ubuntu1  amd64Unity 8
shell

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

Title:
  Black screen: Unity8 crashes and restarts continuously: unity8:
  linker.c:27: android_dlopen: Assertion `0' failed.

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Black screen: Unity8 crashes and restarts continuously:

  qtmir.sessions: SessionManager::SessionManager - this= 
qtmir::SessionManager(0xff6630)
  qtmir.surfaces: MirSurfaceManager::MirSurfaceManager - this= 
qtmir::MirSurfaceManager(0xff7500)
  qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0)
  unity.topsurfacelist: 
setApplicationsModel(qtmir::ApplicationManager(0xfccf80, name = 
qtmir::ApplicationManager))
  GStreamer; Unable to pause - "file:///system/media/audio/ui/camera_click.ogg"
  qtmir.mir: SessionAuthorizer::connection_is_allowed - this= 
SessionAuthorizer(0x7f5ae8129990) pid= 25176
  android_dlopen called but not implemented!
  unity8: linker.c:27: android_dlopen: Assertion `0' failed.
  ()
  qtmir.screens: ScreensModel::ScreensModel
  [2016-05-05 10:28:39.273657] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  [2016-05-05 10:28:39.273699] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.22.0)
  [2016-05-05 10:28:39.273813] mirplatform: Found graphics driver: dummy 
(version 0.22.0)
  [2016-05-05 10:28:39.273822] mirplatform: Found graphics driver: 
throw-on-creation (version 0.22.0)
  qtmir.mir: MirServer created

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

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

[Touch-packages] [Bug 1578462] Re: Black screen: Unity8 crashes and restarts continuously: unity8: linker.c:27: android_dlopen: Assertion `0' failed.

[Daniel van Vugt]

Note that this happens _after_ I have uninstalled the Android graphics
driver (see bug 1578461)

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

** Tags added: black-screen

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

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

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

Title:
  Black screen: Unity8 crashes and restarts continuously: unity8:
  linker.c:27: android_dlopen: Assertion `0' failed.

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Black screen: Unity8 crashes and restarts continuously:

  qtmir.sessions: SessionManager::SessionManager - this= 
qtmir::SessionManager(0xff6630)
  qtmir.surfaces: MirSurfaceManager::MirSurfaceManager - this= 
qtmir::MirSurfaceManager(0xff7500)
  qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0)
  unity.topsurfacelist: 
setApplicationsModel(qtmir::ApplicationManager(0xfccf80, name = 
qtmir::ApplicationManager))
  GStreamer; Unable to pause - "file:///system/media/audio/ui/camera_click.ogg"
  qtmir.mir: SessionAuthorizer::connection_is_allowed - this= 
SessionAuthorizer(0x7f5ae8129990) pid= 25176
  android_dlopen called but not implemented!
  unity8: linker.c:27: android_dlopen: Assertion `0' failed.
  ()
  qtmir.screens: ScreensModel::ScreensModel
  [2016-05-05 10:28:39.273657] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  [2016-05-05 10:28:39.273699] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.22.0)
  [2016-05-05 10:28:39.273813] mirplatform: Found graphics driver: dummy 
(version 0.22.0)
  [2016-05-05 10:28:39.273822] mirplatform: Found graphics driver: 
throw-on-creation (version 0.22.0)
  qtmir.mir: MirServer created

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

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

[Touch-packages] [Bug 1578462] [NEW] Black screen: Unity8 crashes and restarts continuously: unity8: linker.c:27: android_dlopen: Assertion `0' failed.

[Daniel van Vugt]

Public bug reported:

Black screen: Unity8 crashes and restarts continuously:

qtmir.sessions: SessionManager::SessionManager - this= 
qtmir::SessionManager(0xff6630)
qtmir.surfaces: MirSurfaceManager::MirSurfaceManager - this= 
qtmir::MirSurfaceManager(0xff7500)
qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0)
unity.topsurfacelist: setApplicationsModel(qtmir::ApplicationManager(0xfccf80, 
name = qtmir::ApplicationManager))
GStreamer; Unable to pause - "file:///system/media/audio/ui/camera_click.ogg"
qtmir.mir: SessionAuthorizer::connection_is_allowed - this= 
SessionAuthorizer(0x7f5ae8129990) pid= 25176
android_dlopen called but not implemented!
unity8: linker.c:27: android_dlopen: Assertion `0' failed.
()
qtmir.screens: ScreensModel::ScreensModel
[2016-05-05 10:28:39.273657] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
[2016-05-05 10:28:39.273699] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.22.0)
[2016-05-05 10:28:39.273813] mirplatform: Found graphics driver: dummy (version 
0.22.0)
[2016-05-05 10:28:39.273822] mirplatform: Found graphics driver: 
throw-on-creation (version 0.22.0)
qtmir.mir: MirServer created

** Affects: mir
 Importance: Critical
 Status: New

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

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


** Tags: android black-screen regression

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

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

Title:
  Black screen: Unity8 crashes and restarts continuously: unity8:
  linker.c:27: android_dlopen: Assertion `0' failed.

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Black screen: Unity8 crashes and restarts continuously:

  qtmir.sessions: SessionManager::SessionManager - this= 
qtmir::SessionManager(0xff6630)
  qtmir.surfaces: MirSurfaceManager::MirSurfaceManager - this= 
qtmir::MirSurfaceManager(0xff7500)
  qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0)
  unity.topsurfacelist: 
setApplicationsModel(qtmir::ApplicationManager(0xfccf80, name = 
qtmir::ApplicationManager))
  GStreamer; Unable to pause - "file:///system/media/audio/ui/camera_click.ogg"
  qtmir.mir: SessionAuthorizer::connection_is_allowed - this= 
SessionAuthorizer(0x7f5ae8129990) pid= 25176
  android_dlopen called but not implemented!
  unity8: linker.c:27: android_dlopen: Assertion `0' failed.
  ()
  qtmir.screens: ScreensModel::ScreensModel
  [2016-05-05 10:28:39.273657] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  [2016-05-05 10:28:39.273699] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.22.0)
  [2016-05-05 10:28:39.273813] mirplatform: Found graphics driver: dummy 
(version 0.22.0)
  [2016-05-05 10:28:39.273822] mirplatform: Found graphics driver: 
throw-on-creation (version 0.22.0)
  qtmir.mir: MirServer created

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

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

[Touch-packages] [Bug 1578461] [NEW] Having mir-graphics-drivers-android9:amd64 installed prevents unity-system-compositor starting: 'unity-system-compositor: linker.c:27: android_dlopen: Assertion `0

[Daniel van Vugt]

Public bug reported:

Having mir-graphics-drivers-android9:amd64 installed prevents unity-
system-compositor starting:

[2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
android_dlopen called but not implemented!
unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.

which was caused by:

sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay

** Affects: mir
 Importance: Critical
 Status: New

** Affects: mir/0.22
 Importance: Critical
 Status: New

** Affects: mir/0.23
 Importance: Critical
 Status: New

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


** Tags: android regression

** Description changed:

  Having mir-graphics-drivers-android9:amd64 installed prevents unity-
  system-compositor starting:
  
  [2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  android_dlopen called but not implemented!
  unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.
+ 
+ which was caused by:
+ 
+ sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay

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

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

** Changed in: mir
Milestone: None => 0.24.0

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

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

** Changed in: mir/0.22
Milestone: None => 0.22.1

** Changed in: mir/0.23
Milestone: None => 0.23.0

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

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

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

Title:
  Having mir-graphics-drivers-android9:amd64 installed prevents unity-
  system-compositor starting: 'unity-system-compositor: linker.c:27:
  android_dlopen: Assertion `0' failed.'

Status in Mir:
  New
Status in Mir 0.22 series:
  New
Status in Mir 0.23 series:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  Having mir-graphics-drivers-android9:amd64 installed prevents unity-
  system-compositor starting:

  [2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  android_dlopen called but not implemented!
  unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.

  which was caused by:

  sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay

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

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

[Touch-packages] [Bug 960157] Re: lightdm exits on SIGHUP

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.19.0-0ubuntu1

---
lightdm (1.19.0-0ubuntu1) yakkety; urgency=medium

  * New upstream release:
- Use /dev/tty0 instead of /dev/console for VT operations (LP: #1566073)
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix lxsession running in guest session
- Drop support for legacy XMir
- Fix g_spawn compiler warning
  * debian/rules:
- Fix usage of dh_installinit (LP: #1292990)

 -- Robert Ancell   Thu, 05 May 2016
12:23:45 +1200

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

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

Title:
  lightdm exits on SIGHUP

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Committed
Status in lightdm source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  LightDM quits when it receives SIGUSR1, SIGUSR2 or SIGHUP. But convention 
these signals should not quit a service (they should get it to dump state, 
reload configuration etc).

  [Test Case]
  1. Start lightdm
  2. sudo killall -SIGHUP lightdm

  Expected result:
  Nothing happens

  Observed result:
  LightDM restarts

  [Regression Potential]
  Low. We now just quit only on SIGTERM and SIGINT.

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

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

[Touch-packages] [Bug 1509829] Re: lightdm-guest-session profile is too strict to input Japanese text with fcitx-mozc

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.19.0-0ubuntu1

---
lightdm (1.19.0-0ubuntu1) yakkety; urgency=medium

  * New upstream release:
- Use /dev/tty0 instead of /dev/console for VT operations (LP: #1566073)
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix lxsession running in guest session
- Drop support for legacy XMir
- Fix g_spawn compiler warning
  * debian/rules:
- Fix usage of dh_installinit (LP: #1292990)

 -- Robert Ancell   Thu, 05 May 2016
12:23:45 +1200

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

Title:
  lightdm-guest-session profile is too strict to input Japanese text
  with fcitx-mozc

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in fcitx package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in fcitx source package in Xenial:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Committed
Status in mozc source package in Xenial:
  Fix Released

Bug description:
  When logging into lightdm guest session, mozc gives an error saying
  "Failed to start Kana/Kanji conversion program. You need to reboot".
  Thus Japanese text cannot be input.

  [possibly related messages]
  10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 
audit(1445787629.866:709): apparmor="DENIED" operation="link" 
profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/dev/shm/sem.69ef545277bb" pid=9534 comm="fcitx" requested_mask="l" 
denied_mask="l" fsuid=120 ouid=120 target="/dev/shm/oFbWJv"
  10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 
audit(1445787629.870:710): apparmor="DENIED" operation="bind" 
profile="/usr/lib/lightdm/lightdm-guest-session" pid=9554 comm="mozc_server" 
family="unix" sock_type="stream" protocol=0 requested_mask="bind" 
denied_mask="bind" addr="@tmp/.mozc.d23bc799563c3f748fa591c15f46c971.session"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 26 00:45:41 2015
  InstallationDate: Installed on 2015-10-25 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1292990] Re: lightdm overrides dh_installinit in debian/rules and shouldn't

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.19.0-0ubuntu1

---
lightdm (1.19.0-0ubuntu1) yakkety; urgency=medium

  * New upstream release:
- Use /dev/tty0 instead of /dev/console for VT operations (LP: #1566073)
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix lxsession running in guest session
- Drop support for legacy XMir
- Fix g_spawn compiler warning
  * debian/rules:
- Fix usage of dh_installinit (LP: #1292990)

 -- Robert Ancell   Thu, 05 May 2016
12:23:45 +1200

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

Title:
  lightdm overrides dh_installinit in debian/rules and shouldn't

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  The debian/rules for lightdm includes the following:

  override_dh_installinit:
  dh_installinit --no-start

  This appears to have been in place since the beginning of the
  package's history, with no reason given.  And the result of this
  override is that if you install lightdm on a running system, lightdm
  will not be automatically started at install time like it should be.

  Please drop this override from the package.

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

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

[Touch-packages] [Bug 1575200] Re: Error connecting to X server via IPv6

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.19.0-0ubuntu1

---
lightdm (1.19.0-0ubuntu1) yakkety; urgency=medium

  * New upstream release:
- Use /dev/tty0 instead of /dev/console for VT operations (LP: #1566073)
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix lxsession running in guest session
- Drop support for legacy XMir
- Fix g_spawn compiler warning
  * debian/rules:
- Fix usage of dh_installinit (LP: #1292990)

 -- Robert Ancell   Thu, 05 May 2016
12:23:45 +1200

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

Title:
  Error connecting to X server via IPv6

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Committed

Bug description:
  I've discovered a problem in lightdm XDMCP using link-local IPv6 addresses 
without interface index to connect to X server.
  It has been originally reported at 
https://bugzilla.redhat.com/show_bug.cgi?id=1322775.

  The problem can be fixed by having the XDMCP client not transmitting
  link-local addresses in the request, but if it does, lightdm XDMCP
  server can be a lot smarter if the attached patch is applied.

  It changes the X server address selection order to set the lowest
  preference to link-local addresses, even if matching the source
  address or family.

  This is not 100% full-proof: if only link-local addresses have been
  received, one of them is used anyway. In this case, a complete
  solution would be to determine and set the address interface index if
  not ambiguous.

  However, this patch fixes the problem for most of the non-pathological 
  cases.

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

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

[Touch-packages] [Bug 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.19.0-0ubuntu1

---
lightdm (1.19.0-0ubuntu1) yakkety; urgency=medium

  * New upstream release:
- Use /dev/tty0 instead of /dev/console for VT operations (LP: #1566073)
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix lxsession running in guest session
- Drop support for legacy XMir
- Fix g_spawn compiler warning
  * debian/rules:
- Fix usage of dh_installinit (LP: #1292990)

 -- Robert Ancell   Thu, 05 May 2016
12:23:45 +1200

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

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

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

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

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

[Touch-packages] [Bug 1558531] Re: Set up VPN page breaks navigation pattern

[Selene Scriven]

I tested the fix and it does not appear to make the UI any more
consistent compared to the rest of the system-settings app.

For example, look at the UI to add a new APN.  Instead of "cancel" and
"ok" at the bottom, it has a back button and a checkmark in the header.

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

Title:
  Set up VPN page breaks navigation pattern

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  Every page that I have come across in Ubuntu Touch apps, use a back
  header button to exit the page. The "Set up VPN" places the "Cancel"
  and "Ok" buttons at the bottom of the page which makes it confusing
  and undiscoverable for a user. To compound the issue, if the user
  panics and just closes the system settings app at that point, a VPN
  connection is still created (bug 1558530).

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

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

[Touch-packages] [Bug 1543467] Re: Unity8 can't correctly display multi-surface apps (including menus and tooltips)

[Daniel van Vugt]

I will retest but FYI your usage of the Launchpad status 'Fix Released'
is incorrect.

Fix Released on the Ubuntu task means the fix is in one of these:
   https://launchpad.net/ubuntu/+source/unity8
which it is not.

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

Title:
  Unity8 can't correctly display multi-surface apps (including menus and
  tooltips)

Status in QtMir:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Unity8 can't display multi-surface apps (including menus and
  tooltips).

  Fixing bug 1497085 was a great start. However instead of crashing
  Unity8 now just shows the most recently created window by the app in
  the apps /single window/, and stretches it too. When such a secondary
  window like a menu or tooltip closes, you never get back to the
  original app window. So existing apps still aren't quite usable yet.

  Test case:
  sudo apt-get install mir-demos
  mir_demo_client_multiwin -- --desktop_file_hint=unity8

  Expected: Three windows (red, green, blue)
  Observed: Only the blue window

  You can also experience the same bug with lots of apps via:  Xmir
  -rootless under Unity8.

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

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

[Touch-packages] [Bug 1578381] Re: mir tests fail in yakkety on amd64 and i386

[Daniel van Vugt]

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

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

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

Title:
  mir tests fail in yakkety on amd64 and i386

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

Bug description:
  mir tests fail in yakkety on amd64 and i386. we urgently need a
  building package to push

  
  https://launchpad.net/ubuntu/+source/mir/0.21.0+16.04.20160330-0ubuntu3

  8/18 Test #18: Protobuf-can-be-reloaded ..
  Passed0.01 sec

  94% tests passed, 1 tests failed out of 18

  Total Test time (real) = 211.54 sec

  The following tests FAILED:
  8 - mir_acceptance_tests (Failed)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

[Martin Pitt]

Also note that blocking the uevents will not actually work for the
renaming if there is an initramfs involved. I. e. it will work in
containers, but not QEMU or bare metal.

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

Title:
  Drop unnecessary blocking of all net udev rules

Status in cloud-init package in Ubuntu:
  Triaged
Status in ifupdown package in Ubuntu:
  Invalid

Bug description:
  cloud-inits networking setup currently jumps through a lot of bad
  hoops to make sure that ifup@ does not run until after cloud-init-
  local.service. This includes blocking udev rules for an indefinite
  time, which is racy, a potential deadlock, and highly non-elegant.

  This is also not necessary: while ifupdown's net udev rule certainly
  can fire before cloud-init-local, it only asynchronously starts
  ifup@.service which will be deferred until after network-pre.target
  and thus after cloud-init-local.service.

  ---
  Original description, which turned out to be completely false and just us 
being misled:

  ifup@.service can (and often does) run for a particular interface
  before networking.service runs. This is brittle as during early boot
  ifup is prone to fail: / might still be read-only, /var might not yet
  exist or be writable, dhclient-enter-hooks.d/ or if-up.d/ hooks might
  silently fail, etc. It is also unnecessary as networking.service will
  bring up all "auto" and all present "allow-hotplug" interfaces anyway,
  and it runs at the right time.

  We should make either 80-ifupdown.rules or ifup@.service ignore events
  until networking.service is active, or wait until after it has run
  (slower, but avoids race conditions when hotplug events happen while
  networking.service is running). Thus we need to add
  After=networking.service to ifup@.service, so that this only does
  stuff after doing the "coldplug" configuration.

  This also affects cloud-init's setup of networking: this currently
  jumps through a lot of bad hoops to make sure that ifup@ does not run
  until after cloud-init-local.service. This includes blocking udev
  rules for an indefinite time, which is racy, a potential deadlock, and
  highly non-elegant.

  https://bugs.debian.org/752919 is related to this issue.

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

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

[Touch-packages] [Bug 1554803] Re: apparmor: missing stub hardware directories

[xtrchessreal]

Seth, Thanks for your effort and input to my question.  Here is the
output you requested :)

x@x-NICEPUTER:~$ dpkg -l webbrowser-app | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
rc  webbrowser-app 0.23+16.04.20160413-0ubuntu1 amd64Ubuntu web browser
x@x-NICEPUTER:~$ dpkg -S /usr/share/apparmor/hardware/video.d
dpkg-query: no path found matching pattern /usr/share/apparmor/hardware/video.d
x@x-NICEPUTER:~$ 

Lemme know if there is anything else I can do
Thanks

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

Title:
  apparmor: missing stub hardware directories

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  ● apparmor.service - LSB: AppArmor initialization
 Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
 Active: failed (Result: exit-code) since Tue 2016-03-08 14:34:04 EST; 4h 
23min ago
   Docs: man:systemd-sysv-generator(8)
Process: 2909 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 08 14:34:04 ogre apparmor[2909]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in 
/etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open 
'/usr/share/apparmor/hardware/graphics.d'
  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 08 14:34:04 ogre apparmor[2909]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in 
/etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open 
'/usr/share/apparmor/hardware/graphics.d'
  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 08 14:34:04 ogre apparmor[2909]:...fail!
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Control process exited, 
code=exited status=123
  Mar 08 14:34:04 ogre systemd[1]: Failed to start LSB: AppArmor initialization.
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Unit entered failed state.
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Failed with result 
'exit-code'.

  /usr/share/apparmor/hardware/graphics.d doesn't in fact exist on my
  system. I'm not sure what package would provide it, but it seems
  curious to me that the package doesn't supply its relevant apparmor
  bits. I'd have expected the apparmor package to not complain about
  bits belonging to packages that aren't installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10-3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  8 18:53:31 2016
  InstallationDate: Installed on 2016-02-24 (13 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160219)
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro net.ifnames=0 biosdevname=0
  SourcePackage: apparmor
  Syslog: Mar  8 14:34:05 ogre dbus[3062]: [system] AppArmor D-Bus mediation is 
enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1554803] Re: apparmor: missing stub hardware directories

[Seth Arnold]

xtrchessreal,l I think the easiest way forward for you is:
apt-get install apparmor-easyprof-ubuntu

I'm surprised this is still happening though. Can you paste the output of:
dpkg -l webbrowser-app | cat
and
dpkg -S /usr/share/apparmor/hardware/video.d

Thanks

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

Title:
  apparmor: missing stub hardware directories

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  ● apparmor.service - LSB: AppArmor initialization
 Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
 Active: failed (Result: exit-code) since Tue 2016-03-08 14:34:04 EST; 4h 
23min ago
   Docs: man:systemd-sysv-generator(8)
Process: 2909 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 08 14:34:04 ogre apparmor[2909]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in 
/etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open 
'/usr/share/apparmor/hardware/graphics.d'
  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 08 14:34:04 ogre apparmor[2909]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in 
/etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open 
'/usr/share/apparmor/hardware/graphics.d'
  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 08 14:34:04 ogre apparmor[2909]:...fail!
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Control process exited, 
code=exited status=123
  Mar 08 14:34:04 ogre systemd[1]: Failed to start LSB: AppArmor initialization.
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Unit entered failed state.
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Failed with result 
'exit-code'.

  /usr/share/apparmor/hardware/graphics.d doesn't in fact exist on my
  system. I'm not sure what package would provide it, but it seems
  curious to me that the package doesn't supply its relevant apparmor
  bits. I'd have expected the apparmor package to not complain about
  bits belonging to packages that aren't installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10-3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  8 18:53:31 2016
  InstallationDate: Installed on 2016-02-24 (13 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160219)
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro net.ifnames=0 biosdevname=0
  SourcePackage: apparmor
  Syslog: Mar  8 14:34:05 ogre dbus[3062]: [system] AppArmor D-Bus mediation is 
enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1562875] Re: Totem can't play H264 on fresh 16.04 beta install

[snerge]

@Hamidreze,

I have just tested it with a new user account and Totem was working
fine. I digged a little and deleted the folder "gstreamer-1.0" in the
".cache" folder in my home and it's now working again in my other
account

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

Title:
  Totem can't play H264 on fresh 16.04 beta install

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Totem can't play neither find the correct codec to play H264 *.mp4
  video in last 16.04 beta.

  Terminal says :

  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile)
  decoder|decoder-video/x-h264, stream-format=(string)avc,
  alignment=(string)au, level=(string)4, profile=(string)main, max-
  input-size=(int)51696, parsed=(boolean)true (H.264 (Main Profile)
  decoder)

  
  Totem tries to find the correct codec but fails, see attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 15:51:47 2016
  InstallationDate: Installed on 2016-03-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1509829] Re: lightdm-guest-session profile is too strict to input Japanese text with fcitx-mozc

[Robert Ancell]

** Changed in: lightdm
   Status: Fix Committed => Fix Released

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

Title:
  lightdm-guest-session profile is too strict to input Japanese text
  with fcitx-mozc

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in fcitx package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Committed
Status in mozc package in Ubuntu:
  Fix Released
Status in fcitx source package in Xenial:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Committed
Status in mozc source package in Xenial:
  Fix Released

Bug description:
  When logging into lightdm guest session, mozc gives an error saying
  "Failed to start Kana/Kanji conversion program. You need to reboot".
  Thus Japanese text cannot be input.

  [possibly related messages]
  10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 
audit(1445787629.866:709): apparmor="DENIED" operation="link" 
profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/dev/shm/sem.69ef545277bb" pid=9534 comm="fcitx" requested_mask="l" 
denied_mask="l" fsuid=120 ouid=120 target="/dev/shm/oFbWJv"
  10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 
audit(1445787629.870:710): apparmor="DENIED" operation="bind" 
profile="/usr/lib/lightdm/lightdm-guest-session" pid=9554 comm="mozc_server" 
family="unix" sock_type="stream" protocol=0 requested_mask="bind" 
denied_mask="bind" addr="@tmp/.mozc.d23bc799563c3f748fa591c15f46c971.session"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 26 00:45:41 2015
  InstallationDate: Installed on 2015-10-25 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 960157] Re: lightdm exits on SIGHUP

[Robert Ancell]

** Changed in: lightdm
   Status: Fix Committed => Fix Released

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

Title:
  lightdm exits on SIGHUP

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Committed
Status in lightdm source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  LightDM quits when it receives SIGUSR1, SIGUSR2 or SIGHUP. But convention 
these signals should not quit a service (they should get it to dump state, 
reload configuration etc).

  [Test Case]
  1. Start lightdm
  2. sudo killall -SIGHUP lightdm

  Expected result:
  Nothing happens

  Observed result:
  LightDM restarts

  [Regression Potential]
  Low. We now just quit only on SIGTERM and SIGINT.

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

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

[Touch-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

[Robert Ancell]

** Changed in: lightdm
   Status: Fix Committed => Fix Released

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

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Fix Committed
Status in lxsession source package in Xenial:
  New

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Robert Ancell]

** Changed in: lightdm
   Status: Fix Committed => Fix Released

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

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

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

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

[Touch-packages] [Bug 1575200] Re: Error connecting to X server via IPv6

[Robert Ancell]

** Changed in: lightdm
   Status: Fix Committed => Fix Released

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

Title:
  Error connecting to X server via IPv6

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Committed

Bug description:
  I've discovered a problem in lightdm XDMCP using link-local IPv6 addresses 
without interface index to connect to X server.
  It has been originally reported at 
https://bugzilla.redhat.com/show_bug.cgi?id=1322775.

  The problem can be fixed by having the XDMCP client not transmitting
  link-local addresses in the request, but if it does, lightdm XDMCP
  server can be a lot smarter if the attached patch is applied.

  It changes the X server address selection order to set the lowest
  preference to link-local addresses, even if matching the source
  address or family.

  This is not 100% full-proof: if only link-local addresses have been
  received, one of them is used anyway. In this case, a complete
  solution would be to determine and set the address interface index if
  not ambiguous.

  However, this patch fixes the problem for most of the non-pathological 
  cases.

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

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

[Touch-packages] [Bug 1562875] Re: Totem can't play H264 on fresh 16.04 beta install

[snerge]

@Hamidreza,

I upgraded from 15.10 to 16.04 and I now have the issue. The audio plays
in Totem but no video. VLC does work but is pretty laggy when I scroll.

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

Title:
  Totem can't play H264 on fresh 16.04 beta install

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Totem can't play neither find the correct codec to play H264 *.mp4
  video in last 16.04 beta.

  Terminal says :

  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile)
  decoder|decoder-video/x-h264, stream-format=(string)avc,
  alignment=(string)au, level=(string)4, profile=(string)main, max-
  input-size=(int)51696, parsed=(boolean)true (H.264 (Main Profile)
  decoder)

  
  Totem tries to find the correct codec but fails, see attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 15:51:47 2016
  InstallationDate: Installed on 2016-03-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1566073] Re: Use /dev/tty0 instead of /dev/console for VT operations

[Robert Ancell]

** Changed in: lightdm
   Status: Fix Committed => Fix Released

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

Title:
  Use /dev/tty0 instead of /dev/console for VT operations

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  New

Bug description:
  LightDM currently uses /dev/console for VT operations. In Ubuntu 16.04
  this does not appear to work anymore. Switching to /dev/tty0 works,
  and this matches what logind and GDM use.

  When these operations don't work this can affect the ability to switch
  between sessions.

  There doesn't seem to be any documentation on what the correct device
  to use for VT operations is, so matching other software is probably
  just reducing the risk of hitting bugs.

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

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

[Touch-packages] [Bug 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Robert Ancell]

** Changed in: lightdm/1.2
   Status: New => Won't Fix

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

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

** Changed in: lightdm (Ubuntu Precise)
   Status: New => Won't Fix

** Changed in: lightdm/1.18
Milestone: None => 1.18.2

** Changed in: lightdm
Milestone: None => 1.19.0

** Changed in: lightdm/1.10
Milestone: None => 1.10.7

** Changed in: lightdm/1.16
Milestone: None => 1.16.8

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

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

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

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

[Touch-packages] [Bug 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Launchpad Bug Tracker]

** Branch linked: lp:lightdm/1.10

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

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

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

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

[Touch-packages] [Bug 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Robert Ancell]

** Changed in: lightdm/1.16
   Status: New => Fix Committed

** Changed in: lightdm/1.2
   Importance: Undecided => Medium

** Changed in: lightdm/1.18
   Importance: Undecided => High

** Changed in: lightdm/1.16
   Importance: Undecided => Medium

** Changed in: lightdm/1.18
   Importance: High => Medium

** Changed in: lightdm/1.10
   Importance: Undecided => Medium

** Changed in: lightdm/1.10
   Status: New => Fix Committed

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

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

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

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

[Touch-packages] [Bug 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Launchpad Bug Tracker]

** Branch linked: lp:lightdm/1.18

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

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

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

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

[Touch-packages] [Bug 1578442] [NEW] XDMCP Willing/Unwilling messages do not report hostname

[Robert Ancell]

Public bug reported:

[Impact]
When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

[Test Case]
1. Start LightDM with the XDMCP server enabled
2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

Expected result:
An appropriate label is used for the LightDM XDMCP server

Observed result:
No label is shown

[Regression potential]
Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

** Affects: lightdm
 Importance: Medium
 Status: Fix Committed

** Affects: lightdm/1.10
 Importance: Medium
 Status: Fix Committed

** Affects: lightdm/1.16
 Importance: Medium
 Status: Fix Committed

** Affects: lightdm/1.18
 Importance: Medium
 Status: Fix Committed

** Affects: lightdm/1.2
 Importance: Medium
 Status: New

** Affects: lightdm (Ubuntu)
 Importance: Medium
 Status: Triaged

** Affects: lightdm (Ubuntu Trusty)
 Importance: Medium
 Status: Triaged

** Affects: lightdm (Ubuntu Wily)
 Importance: Medium
 Status: Triaged

** Affects: lightdm (Ubuntu Xenial)
 Importance: Medium
 Status: Triaged

** Also affects: lightdm/1.18
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.2
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.10
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.16
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

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

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

[Touch-packages] [Bug 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Robert Ancell]

** Changed in: lightdm/1.18
   Status: New => Fix Committed

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

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

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

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

[Touch-packages] [Bug 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Launchpad Bug Tracker]

** Branch linked: lp: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/1578442

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

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

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

[Touch-packages] [Bug 1550490] Re: network-manager unresponsive after suspend

[Dragon Ball]

that link doesn't work for me either

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1578406] Re: No indication which app is highlighted when using hardware keyboard

[Rodney Dawes]

** Package changed: unity-scope-click (Ubuntu) => unity8 (Ubuntu)

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

Title:
  No indication which app is highlighted when using hardware keyboard

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

Bug description:
  bq M10 with OTA-10.1

  I use external bluetooth keyboard. 
  I noticed I can use Tab key to switch between app icons. Unfortunately I have 
no idea which app get focus until I press Enter and start that app. Would be 
great to have some indication which app icon is focused.

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

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

[Touch-packages] [Bug 1578406] [NEW] No indication which app is highlighted when using hardware keyboard

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

bq M10 with OTA-10.1

I use external bluetooth keyboard. 
I noticed I can use Tab key to switch between app icons. Unfortunately I have 
no idea which app get focus until I press Enter and start that app. Would be 
great to have some indication which app icon is focused.

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

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

-- 
No indication which app is highlighted when using hardware keyboard
https://bugs.launchpad.net/bugs/1578406
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unity8 in Ubuntu.

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

[Touch-packages] [Bug 1575313] Re: [Ubuntu Touch] Today Scope doesn't display current location status

[Launchpad Bug Tracker]

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

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

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

Title:
  [Ubuntu Touch] Today Scope doesn't display current location status

Status in Canonical System Image:
  Confirmed
Status in Today Scope:
  Triaged
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  Today scope doesn't display a users current location.  It is confusing
  for the weather, sunrise and sunset information as it is not clear
  what location that is for.  It came to my attention as I'm on
  corporate VPN and Today-Scope is proving information based on IP
  address, which for me, is thousands of kilometers away.  My Aquaris
  M10 tablet is also inside so is not picking up GPS signal.

  When I enable GPS only, Today-Scope still defaults back to IP address
  location data.  Appears that there is no way to manually set location
  and when I set location in The Weather Channel app it defaults back to
  IP location when I switch back to Today-Scope.

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

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

[Touch-packages] [Bug 1578430] Re: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade:
  trying to overwrite shared '/etc/xdg/Trolltech.conf', which is
  different from other instances of package libqtcore4:i386

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  Happened while installing skype

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Wed May  4 19:07:03 2016
  DuplicateSignature:
   Unpacking libqtcore4:i386 (4:4.8.7+dfsg-5ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-5ubuntu2_i386.deb (--unpack):
trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different 
from other instances of package libqtcore4:i386
  ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:i386
  InstallationDate: Installed on 2016-04-10 (24 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: qt4-x11
  Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: 
trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from 
other instances of package libqtcore4:i386
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (12 days ago)

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

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

[Touch-packages] [Bug 1578430] [NEW] package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances o

[houde]

Public bug reported:

Happened while installing skype

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Wed May  4 19:07:03 2016
DuplicateSignature:
 Unpacking libqtcore4:i386 (4:4.8.7+dfsg-5ubuntu2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-5ubuntu2_i386.deb (--unpack):
  trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from 
other instances of package libqtcore4:i386
ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:i386
InstallationDate: Installed on 2016-04-10 (24 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: qt4-x11
Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: 
trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from 
other instances of package libqtcore4:i386
UpgradeStatus: Upgraded to xenial on 2016-04-22 (12 days ago)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade:
  trying to overwrite shared '/etc/xdg/Trolltech.conf', which is
  different from other instances of package libqtcore4:i386

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  Happened while installing skype

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Wed May  4 19:07:03 2016
  DuplicateSignature:
   Unpacking libqtcore4:i386 (4:4.8.7+dfsg-5ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-5ubuntu2_i386.deb (--unpack):
trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different 
from other instances of package libqtcore4:i386
  ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:i386
  InstallationDate: Installed on 2016-04-10 (24 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: qt4-x11
  Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: 
trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from 
other instances of package libqtcore4:i386
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (12 days ago)

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

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

[Touch-packages] [Bug 1554803] Re: apparmor: missing stub hardware directories

[xtrchessreal]

I have the exact output (I'm also running 16.04 upgraded from 15.10) the
originator published.  If it was fixed in webbrowser-app package 16.04
then this would not be seen in 16.04.  I agree this bug should be left
open.  I looked everywhere on AskUbuntu etc before finally asking and
was referred to this bug.  Thanks for your time and effort. :)

How do I apply the apparmor-easyprof-ubuntu package? 
Is this a workaround or the fix?
Should I remove and purge the current apparmor etc packages then reinstall?  
I also invite any here to post the proper steps to the answer to my question on 
AskUbuntu: 
http://askubuntu.com/questions/767272/apparmor-init-failed-exit-code-123/767686#767686

Once again thank you for your effort and time please let me know if
there is anything I can provide to help. :)

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

Title:
  apparmor: missing stub hardware directories

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  ● apparmor.service - LSB: AppArmor initialization
 Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
 Active: failed (Result: exit-code) since Tue 2016-03-08 14:34:04 EST; 4h 
23min ago
   Docs: man:systemd-sysv-generator(8)
Process: 2909 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 08 14:34:04 ogre apparmor[2909]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in 
/etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open 
'/usr/share/apparmor/hardware/graphics.d'
  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 08 14:34:04 ogre apparmor[2909]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in 
/etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open 
'/usr/share/apparmor/hardware/graphics.d'
  Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 08 14:34:04 ogre apparmor[2909]:...fail!
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Control process exited, 
code=exited status=123
  Mar 08 14:34:04 ogre systemd[1]: Failed to start LSB: AppArmor initialization.
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Unit entered failed state.
  Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Failed with result 
'exit-code'.

  /usr/share/apparmor/hardware/graphics.d doesn't in fact exist on my
  system. I'm not sure what package would provide it, but it seems
  curious to me that the package doesn't supply its relevant apparmor
  bits. I'd have expected the apparmor package to not complain about
  bits belonging to packages that aren't installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10-3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  8 18:53:31 2016
  InstallationDate: Installed on 2016-02-24 (13 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160219)
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro net.ifnames=0 biosdevname=0
  SourcePackage: apparmor
  Syslog: Mar  8 14:34:05 ogre dbus[3062]: [system] AppArmor D-Bus mediation is 
enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1575455] Re: New AppArmor profile: usr.sbin.nslcd

[Daniel Richard G.]

Thank you Seth :-)  Next rev in each release should have this, right?

No copyright line is needed; this was trivial to derive from the nscd
profile.

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

Title:
  New AppArmor profile: usr.sbin.nslcd

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  nslcd is a good program to be covered by an AppArmor profile, as it
  communicates with an LDAP server and services queries from arbitrary
  local applications.

  This new profile used the existing usr.sbin.nscd profile as a starting
  point.

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

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

[Touch-packages] [Bug 1578381] Re: mir tests fail in yakkety on amd64 and i386

[Matthias Klose]

succeeded when given back

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

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

Title:
  mir tests fail in yakkety on amd64 and i386

Status in mir package in Ubuntu:
  Invalid

Bug description:
  mir tests fail in yakkety on amd64 and i386. we urgently need a
  building package to push

  
  https://launchpad.net/ubuntu/+source/mir/0.21.0+16.04.20160330-0ubuntu3

  8/18 Test #18: Protobuf-can-be-reloaded ..
  Passed0.01 sec

  94% tests passed, 1 tests failed out of 18

  Total Test time (real) = 211.54 sec

  The following tests FAILED:
  8 - mir_acceptance_tests (Failed)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1493386] Re: IN CAR: SIM2 calls cann not be routed via car audio

[Uranicus]

Are there any news on this bug? How about the implementation progress on
supporting 2 SIM cards used with bluetooth?

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

Title:
  IN CAR: SIM2 calls cann not be routed via car audio

Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  Requirements: Aquaris E4.5 with 2 SIMs, 2nd phone, a car with blue tooth 
phone support (Seat Alhambra 2012 in my case)

  1. Connect the Aquaris to the car (with two SIM cards, car kid shows the 
provider of the 2nd SIM card in the display)
  2. From the second device call the number of SIM1
  3. Phone & car sound rings and call can be taken

  4. From the second device call the number of SIM2
  5. Phone does ring but car kit not.

  6. Call 2nd phone from Aquaris connected to the car with SIM1 (via the phone 
directly or using the car kit)
  7. Normal behaviour with in car phone & audio system

  8. Call 2nd phone from Aquaris connected to car with SIM2 (only possible 
dialling from the phone)
  9. No sound on the phone, no microphone support

  EXPECTED:
  I expect that calls from SIM2 can be taken and performed as from SIM1

  ACTUAL:
  SIM2 seems not to work when phone is connected to blue tooth of car whereby 
SIM1 works flawlessly

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

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

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

[Touch-packages] [Bug 1578412] [NEW] /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:11:std::_Sp_counted_base:std::__shared_count:std::__shared_ptr:std::shared_ptr:core::Connection::~Connection

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding qtdeclarative-opensource-src.  This problem was most recently
seen with version 5.5.1-2ubuntu3, the problem page at
https://errors.ubuntu.com/problem/acbe91bb50e669b06d507571cfce5b29f394e0f8
contains more details.

** Affects: qtdeclarative-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

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

Title:
  /usr/lib/arm-linux-
  
gnueabihf/qt5/bin/qmlscene:11:std::_Sp_counted_base:std::__shared_count:std::__shared_ptr:std::shared_ptr:core::Connection::~Connection

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding qtdeclarative-opensource-src.  This problem was most
  recently seen with version 5.5.1-2ubuntu3, the problem page at
  https://errors.ubuntu.com/problem/acbe91bb50e669b06d507571cfce5b29f394e0f8
  contains more details.

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

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

[Touch-packages] [Bug 1578410] [NEW] No way to discover the "side stage" exists

[Michal Predotka]

Public bug reported:

When using tablet there's no info about "side stage". Only way to know
about it is from someone who knows and tell you or if you by mistake do
a gesture to activate "side stage".

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

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

** Also affects: ubuntu-ux
   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/1578410

Title:
  No way to discover the "side stage" exists

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

Bug description:
  When using tablet there's no info about "side stage". Only way to know
  about it is from someone who knows and tell you or if you by mistake
  do a gesture to activate "side stage".

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

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

[Touch-packages] [Bug 1571640] Re: lightdm changing resolution

[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/1571640

Title:
  lightdm changing resolution

Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

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

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

[Touch-packages] [Bug 1578015] Re: Yet another system hangs at shutdown (16.04)

[Lauren Weinstein]

Following the specified procedure to track on VT9, no apparent
differences at all. Shutdown proceeds all the way to the final "power
off" line then the system hangs.

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

Title:
  Yet another system hangs at shutdown (16.04)

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Yet another of the annoying "system hangs at shutdown" bug reports. A
  fresh complete install of 16.04. Just like the others, gets down to:

  Reached target shutdown

  then stops. I've tried all the workarounds discussed, including
  swapoff -a, before shutdown attempt, etc. No joy. Have to hold power
  switch for hard shutdown very time.

  One observation of possible value. I also very recently installed
  16.04 server on two other identical boxes. Neither of them exhibit
  this problem and both shut down cleanly. Only this system, which is a
  16.04 desktop version -- again on an identical box -- is having this
  problem.

  Frankly, it's stuff like this that makes my efforts to move ordinary
  consumers over to Linux very difficult!

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

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

[Touch-packages] [Bug 1572525] Re: Header adds to Flickable topMargin instead of replacing it.

[Alberto Mardegan]

Could it be that this change has a bad effect when combined with the 
PullToRefresh item? I'm experiencing some weird behaviour (maybe the same as 
bug 1404884) on rc-proposed which I don't see on the OTA 10.
I hope to get some time tomorrow to investigate this better and produce a test 
case, but this is just a heads up.

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

Title:
  Header adds to Flickable topMargin instead of replacing it.

Status in ubuntu-ui-toolkit package in Ubuntu:
  Won't Fix

Bug description:
  Th attached test application works fine under qml-module-ubuntu-
  components 1.3.1918+16.04.20160404-0ubuntu3 but breaks with the latest
  1.3.1938+16.04.20160416. At a first examination, I believe that the
  change which cause the regression is this one:

  https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/invisible-
  header-topmargin/+merge/290659

  Run the attached test case with QML scene. You can scroll the view
  horizontally to see the other model items. Under the old version of
  the toolkit, all items have their page headers correctly aligned; with
  the new version, an extra spacing is added below the header.

  I found this bug while testing my ttrss app in rc-proposed; please
  don't let this UITK version reach our users, as more apps might be
  affected.

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

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

[Touch-packages] [Bug 1571640] Re: lightdm changing resolution

[Ian Canino]

I am having a similar problem to this on the Macbook Pro 11,1 (Retina) on a 
tabula rasa install of 16.04 LTS). However this resolution switch only occurs 
on the first time (from boot-up). Each subsequent times, it maintains the 
correct resolution and remembers the user's wallpaper. 
After a reboot, the wallpaper is set to default (purple background) instead of 
remember the user's last used wallpaper.

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

Title:
  lightdm changing resolution

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

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

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

[Touch-packages] [Bug 1575455] Re: New AppArmor profile: usr.sbin.nslcd

[Seth Arnold]

Thanks, I added the profile to the 16.04 and 16.10 directories:
http://bazaar.launchpad.net/~apparmor-dev/apparmor-profiles/master/revision/167
http://bazaar.launchpad.net/~apparmor-dev/apparmor-profiles/master/revision/168

If you want a copyright line on the files, either propose one here or a
merge request. I'm sorry I didn't notice it earlier.

Thanks!

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

Title:
  New AppArmor profile: usr.sbin.nslcd

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  nslcd is a good program to be covered by an AppArmor profile, as it
  communicates with an LDAP server and services queries from arbitrary
  local applications.

  This new profile used the existing usr.sbin.nscd profile as a starting
  point.

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

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

[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Konrad Zapałowicz]

** Branch linked: lp:~kzapalowicz/ubuntu-system-settings/fix-1539158

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

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

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

[Touch-packages] [Bug 1578394] [NEW] Keyboard shortcut F11 does not work as expected

[Michal Predotka]

Public bug reported:

bq M10 with OTA-10.1

After pressing F11 button on external keyboard I expect an app window
which is focused will go full screen but it does not happen.

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

Title:
  Keyboard shortcut F11 does not work as expected

Status in unity8 package in Ubuntu:
  New

Bug description:
  bq M10 with OTA-10.1

  After pressing F11 button on external keyboard I expect an app window
  which is focused will go full screen but it does not happen.

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

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

[Touch-packages] [Bug 1578396] [NEW] missing dependencies are not listed

[Coeur Noir]

Public bug reported:

Hi,

ubuntu 16.04 here.

Using gdebi I've noticed it does not display the list of missing
dependencies :

http://hpics.li/6ca144f

but yet works fine.

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

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

Title:
  missing dependencies are not listed

Status in gdebi package in Ubuntu:
  New

Bug description:
  Hi,

  ubuntu 16.04 here.

  Using gdebi I've noticed it does not display the list of missing
  dependencies :

  http://hpics.li/6ca144f

  but yet works fine.

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

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

[Touch-packages] [Bug 1578392] [NEW] Keyboard shortcut Alt+F4 does not work in staged mode

[Michal Predotka]

Public bug reported:

bq M10 with OTA-10.1

I use external bluetooth keyboard with the tablet. 
In the desktop mode I can close apps using shortcut Alt+F4. Unfortunately that 
does not work in staged mode.

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

Title:
  Keyboard shortcut Alt+F4 does not work in staged mode

Status in unity8 package in Ubuntu:
  New

Bug description:
  bq M10 with OTA-10.1

  I use external bluetooth keyboard with the tablet. 
  In the desktop mode I can close apps using shortcut Alt+F4. Unfortunately 
that does not work in staged mode.

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

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

[Touch-packages] [Bug 1578391] Re: Initial Wi-Fi connection (from wizard) not reflected in indicator

[Allan LeSage]

** Attachment added: "screenshot20160504_142609684.png"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578391/+attachment/4655953/+files/screenshot20160504_142609684.png

** Also affects: indicator-network
   Importance: Undecided
   Status: New

** Also affects: indicator-network (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: indicator-network

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

Title:
  Initial Wi-Fi connection (from wizard) not reflected in indicator

Status in Canonical System Image:
  New
Status in indicator-network package in Ubuntu:
  New

Bug description:
  Able to connect to Wi-Fi during initial wizard, but indicator never
  reflects connected state.  Reboot remedies.

  TEST CASE
  Fresh flash, navigate through wizard to network setup
  1. Connect to access point, input password, tap 'ok'
  2. "Connected" appears below selected access point
  EXPECTED
  Network indicator reflects Wi-Fi connected
  ACTUAL
  Network indicator dark

  Data evidently connected (although possibly via edge).  Note that
  navigating to settings and disabling cellular data "kicks" network
  indicator, indicator reflects Wi-Fi connected state.  Some signal not
  being received by or expressed to i-n?

  awe instructed in adding some debugging infos to n-m but I see no
  syslog.

  current build number: 324
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-05-04 14:18:22
  version version: 324
  version ubuntu: 20160503
  version device: 20160329-a9bacdb
  version custom: 20160324--36-54-vivid

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

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

[Touch-packages] [Bug 1578381] [NEW] mir tests fail in yakkety on amd64 and i386

[Matthias Klose]

Public bug reported:

mir tests fail in yakkety on amd64 and i386. we urgently need a building
package to push


https://launchpad.net/ubuntu/+source/mir/0.21.0+16.04.20160330-0ubuntu3

8/18 Test #18: Protobuf-can-be-reloaded ..
Passed0.01 sec

94% tests passed, 1 tests failed out of 18

Total Test time (real) = 211.54 sec

The following tests FAILED:
  8 - mir_acceptance_tests (Failed)
Errors while running CTest
Makefile:85: recipe for target 'test' failed
make[2]: *** [test] Error 8

** Affects: mir (Ubuntu)
 Importance: Critical
 Assignee: Mir development team (mir-team)
 Status: Confirmed


** Tags: ftbfs

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

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

Title:
  mir tests fail in yakkety on amd64 and i386

Status in mir package in Ubuntu:
  Confirmed

Bug description:
  mir tests fail in yakkety on amd64 and i386. we urgently need a
  building package to push

  
  https://launchpad.net/ubuntu/+source/mir/0.21.0+16.04.20160330-0ubuntu3

  8/18 Test #18: Protobuf-can-be-reloaded ..
  Passed0.01 sec

  94% tests passed, 1 tests failed out of 18

  Total Test time (real) = 211.54 sec

  The following tests FAILED:
  8 - mir_acceptance_tests (Failed)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1578308] Re: package apt 1.0.1ubuntu2.11 failed to install/upgrade: unable to make backup link of `./usr/share/locale/de/LC_MESSAGES/apt.mo' before installing new version: Input/

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

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

** Tags added: hardware-error

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

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

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

Title:
  package apt 1.0.1ubuntu2.11 failed to install/upgrade: unable to make
  backup link of `./usr/share/locale/de/LC_MESSAGES/apt.mo' before
  installing new version: Input/output error

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I got a lot of security updates, but those were impossible to install
  ("..not succesful.."). My sysinfo shows:

  Release: Ubuntu 14.04 (trusty)
  Kernel: 3.13.0-85-generic (#129-Ubuntu SMP Thu Mar 17 20:50:41 UTC 2016)
  GCC-Version: 4.8 (i686-linux-gnu)
  Xorg-Version: 1.15.1 (12 February 2015  02:49:46PM)
  Hostname: wolfgang-ThinkPad-R60

  Is it helpful for you?
  I can work then with the Laptop as usual, but just can't get Updates.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.11
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Wed May  4 17:04:14 2016
  DpkgTerminalLog:
   Preparing to unpack .../apt_1.0.1ubuntu2.13_i386.deb ...
   Unpacking apt (1.0.1ubuntu2.13) over (1.0.1ubuntu2.11) ...
   dpkg: error processing archive 
/var/cache/apt/archives/apt_1.0.1ubuntu2.13_i386.deb (--unpack):
unable to make backup link of `./usr/share/locale/de/LC_MESSAGES/apt.mo' 
before installing new version: Input/output error
  DuplicateSignature: package:apt:1.0.1ubuntu2.11:unable to make backup link of 
`./usr/share/locale/de/LC_MESSAGES/apt.mo' before installing new version: 
Input/output error
  ErrorMessage: unable to make backup link of 
`./usr/share/locale/de/LC_MESSAGES/apt.mo' before installing new version: 
Input/output error
  InstallationDate: Installed on 2012-08-16 (1357 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.11
  SourcePackage: apt
  Title: package apt 1.0.1ubuntu2.11 failed to install/upgrade: unable to make 
backup link of `./usr/share/locale/de/LC_MESSAGES/apt.mo' before installing new 
version: Input/output error
  UpgradeStatus: Upgraded to trusty on 2014-10-08 (574 days ago)

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

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

[Touch-packages] [Bug 1571686] Re: "Ask me each time" for SMS does not work

[Launchpad Bug Tracker]

** Branch linked: lp:~tiagosh/messaging-app/do-not-preselect-sim

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

Title:
  "Ask me each time" for SMS does not work

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  BQ Aquaris E4.5 with OTA 10.1
  Settings "Ask me each time" in "For messages, use" in "Cellular" in "Settings"

  I am using 2 SIM cards and since the beginning of my usage (started
  with release21 this settings was working as expected -> when I wanted
  to send SMS and did not select SIM card by myself (so no SIM card was
  highlighted in the Messages app), I was asked to select one.

  Since some time (OTA-9?) there is always (first one) SIM card selected
  despite the above mentioned settings. And, by whatever reason
  sometimes the SMS is send from other then selected SIM card. Because
  it is now happening much more often and I see that "nice" info: "You
  switched to XXX XX" (PS: no I did not!), it becomes really annoying (I
  have one SIM card in roaming mode) and people are receiving my
  messages from different number and therefore I decided to open this
  bug report.

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

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

[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Konrad Zapałowicz]

It seems that I know what is happening and why the pairing is denied. I
think that it is because the device when added to the internal data
structures is not yet fully initialized as the properties are gathered
asynchronously. In the same time the pin request is executed  that tries
to use the yet not valid device. As a consequence the pairing is denied
as the whole procedure is interrupted.

Now, just to confirm what is happening on the Ubuntu System Settings
side I would like to look at the Ubuntu System Settings log. You can
find somewhere in .cache/upstart/application [now I'm not sure] legacy
/ubuntu-system-settings.log It would be awesome if you could search for
it and paste here. Thanks in advance.

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

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

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

[Touch-packages] [Bug 1578032] Re: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Jamie Strandboge]

It sounds like at some point in the past you moved /lib/ufw/user*.rules
into /etc/ufw and then created symlinks from /lib/ufw/user*.rules to
/lib/ufw. Does this sound plausible?

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

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

Title:
  package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in ufw package in Ubuntu:
  Incomplete

Bug description:
  when i start my computer,it happens the report problem,then i click it
  ,it show that

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  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
  Date: Tue May  3 23:34:43 2016
  DpkgHistoryLog:
   Start-Date: 2016-05-03  23:34:26
   Commandline: aptdaemon role='role-commit-packages' sender=':1.107'
   Upgrade: google-chrome-stable:amd64 (50.0.2661.86-1, 50.0.2661.94-1), 
ubuntu-core-launcher:amd64 (1.0.27, 1.0.27.1)
  DuplicateSignature:
   Setting up ufw (0.35-0ubuntu2) ...
   mv: '/lib/ufw/user.rules' and '/etc/ufw/user.rules' are the same file
   dpkg: error processing package ufw (--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 2015-10-30 (186 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: ufw
  Title: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (12 days ago)
  mtime.conffile..etc.rsyslog.d.20-ufw.conf: 2015-09-09T03:01:36

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

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

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

The problem persists after sorting the oddity with the unity-settings-
daemon, which appears to have been a one-off problem. (See bug #1577906
for more detail.)

Now I find that suspend only works if "HandleLidSwitchDocked=suspend" is
in logind.conf.

Without that I return to the bug condition.

In the bug condition suspend works fine from the session indicator.


neilw@NWPS-LAP:~$ systemd-inhibit
 Who: neilw (UID 1000/neilw, PID 1558/unity-settings-)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block

 Who: NetworkManager (UID 0/root, PID 2267/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

 Who: Telepathy (UID 1000/neilw, PID 1797/mission-control)
What: shutdown:sleep
 Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay

 Who: neilw (UID 1000/neilw, PID 1558/unity-settings-)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: Unity (UID 1000/neilw, PID 1566/compiz)
What: sleep
 Why: Unity needs to lock the screen
Mode: delay

5 inhibitors listed.



** Attachment added: "As requested in post #22"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+attachment/4655927/+files/journal.txt

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  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: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Touch-packages] [Bug 1578301] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

[Martin Pitt]

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

** This bug has been marked a duplicate of bug 1560797
   apt does not configure Pre-Depends: before depending package

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

Title:
  package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  New

Bug description:
  Vboxclient kernal is not running on startup of ubuntu.. Also Ubuntu
  16.04 is not properly installed. Broadcon reciever for wifi is
  missing.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Wed May  4 15:37:58 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-07-10 (298 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (0 days ago)

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

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

[Touch-packages] [Bug 1574322] Re: "webbrowser-app: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory" error when attempting to launch webbrow

[Olivier Tilloy]

** Package changed: webbrowser-app (Ubuntu) => oxide

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

Title:
  "webbrowser-app: error while loading shared libraries: libGL.so.1:
  cannot open shared object file: No such file or directory" error when
  attempting to launch webbrowser-app

Status in Oxide:
  New

Bug description:
  I have recently found that on Ubuntu 16.04 (in a 64-bit VirtualBox VM)
  that the webbrowser-app application does not start when launched from
  the launcher (it flashes for a little bit but then stops and does
  nothing else). If I however try to launch it from Terminal I get:

  webbrowser-app: error while loading shared libraries: libGL.so.1:
  cannot open shared object file: No such file or directory

  This may be related to bug #1573762 but note that this was in a VM and
  that I have Intel drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-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
  Date: Sun Apr 24 17:08:51 2016
  InstallationDate: Installed on 2016-04-23 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Rafael David Tinoco]

Okay, Tks Talat.

Ill propose this fix into all versions relying on the IB patches
submitted in fix:

https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141

Check:

https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1401141/comments/31

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

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Wily:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress

Bug description:
  
  DHCP client is sending discover with Unicast type request for the offer, in 
this configuration of IB to ETH through a relay we need the type to be 
broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  
  DHCP CLIENT (IPoIB) 
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

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

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

[Touch-packages] [Bug 1578341] [NEW] bug with nvidia

[Anton]

Public bug reported:

Nvidia bug i dont really know what it is

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Är en katalog: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  364.19  Tue Apr 19 14:44:55 
PDT 2016
 GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
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: Wed May  4 20:41:08 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
 nvidia, 364.19, 4.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 970] 
[1462:3160]
InstallationDate: Installed on 2016-04-24 (10 days ago)
InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--kylin--vg-root ro nouveau.blacklist=1 quiet splash 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B150M-DS3H DDR3-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd08/19/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB150M-DS3HDDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.68+git1604280630.fc09c5~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 
11.3+gallium-nine~git1604180800.9ce58a~gd~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
11.3+gallium-nine~git1604180800.9ce58a~gd~x
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May  4 17:56:06 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install 
third-party-packages ubuntu xenial

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

Title:
  bug with nvidia

Status in xorg package in Ubuntu:
  New

Bug description:
  Nvidia bug i dont really know what it is

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Är en katalog: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  364.19  Tue Apr 19 14:44:55 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 

[Touch-packages] [Bug 1575313] Re: [Ubuntu Touch] Today Scope doesn't display current location status

[Will Atwood]

To clarify for Frieze, the Nearby Scope picks up its location from
either GPS or IP geolocation using unity-scope-shell even thought under
"Location Settings>>Using GPS only" is selected?  At least Nearby
displays "Where am I" ... except for me the location data is incorrect
(corporate VPN issue) and there is no way to custom modify location as
far as I can tell.

This will lead to a situation where IP and GPS location data may not
coincide and cause confusion in the scopes.  If "Using GPS only" is
selected with no gps data, then unity-scopes-shell shouldn't pass any
location data to the scopes and instead should ask the user for current
desired location.

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

Title:
  [Ubuntu Touch] Today Scope doesn't display current location status

Status in Canonical System Image:
  Confirmed
Status in Today Scope:
  Triaged
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  Today scope doesn't display a users current location.  It is confusing
  for the weather, sunrise and sunset information as it is not clear
  what location that is for.  It came to my attention as I'm on
  corporate VPN and Today-Scope is proving information based on IP
  address, which for me, is thousands of kilometers away.  My Aquaris
  M10 tablet is also inside so is not picking up GPS signal.

  When I enable GPS only, Today-Scope still defaults back to IP address
  location data.  Appears that there is no way to manually set location
  and when I set location in The Weather Channel app it defaults back to
  IP location when I switch back to Today-Scope.

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

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

[Touch-packages] [Bug 1574322] Re: "webbrowser-app: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory" error when attempting to launch webbrow

[Nikita Yerenkov-Scott]

Right, sorry, don't know how that mistake got in there, but with the
correct version it doesn't really work that much better. I see a small
black box (I adjusted the URL to a proper one) which upon being enlarged
does a while flashing stairs like pattern and flashes the top and right
side when I try to enlarge it. It also shows me the clicking cursor when
I go over it but upon clicking it the only thing that seems to change is
that when I mouse over different parts of it the cursor changes to
different things (e.g.: normal and text cursor mode). I assume that this
is because it is providing an interactive experience with the website
it's just only showing black instead of the site? I don't know, anyway,
throughout the time it was active this was the output (the last line got
outputted when I closed the window in the standard way with the little
cross):

[0504/191704:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score 
of renderer with pid 2332: Permission denied
OpenGL Warning: glXCreatePbuffer not implemented by Chromium
[0504/191705:ERROR:layer_tree_host_impl.cc(2218)] Forcing zero-copy tile 
initialization as worker context is missing
[0504/191705:ERROR:buffer_manager.cc(361)] 
[.CommandBufferContext.Context-For-Testing-0x1391870]GL ERROR :GL_INVALID_ENUM 
: glBufferData: <- error from previous GL command
[0504/191711:ERROR:texture_manager.cc(2421)] 
[.CommandBufferContext.RenderCompositor-0x3e5f51043780]GL ERROR 
:GL_INVALID_ENUM : glTexImage2D: <- error from previous GL command
[0504/191711:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_ENUM : 
GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
[0504/191711:ERROR:gles2_cmd_decoder.cc(2138)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR 
:GL_INVALID_OPERATION : ScopedTextureBinder::ctor: was unhandled
[0504/191711:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191711:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191711:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191711:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191712:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191713:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191713:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191714:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191714:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191714:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191714:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191716:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191716:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191718:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191718:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191718:ERROR:gles2_cmd_decoder.cc(2134)] 
[.CommandBufferContext.RenderWorker-0x3e5f51043900]GL ERROR :GL_INVALID_VALUE : 
ScopedTextureBinder::dtor: <- error from previous GL command
[0504/191719:ERROR:gles2_cmd_decoder.cc(2134)]