[Touch-packages] [Bug 1672960] [NEW] unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size()

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.8.0+17.04.20161206-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/322176398baf670e4e9e5bb140a0aed0bbf0a00e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

** Affects: canonical-devices-system-image
 Importance: Critical
 Status: New

** Affects: mir
 Importance: Critical
 Status: New

** Affects: unity-system-compositor
 Importance: Critical
 Status: New

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

** Affects: unity-system-compositor (Ubuntu)
 Importance: Critical
 Status: New


** Tags: unity8-desktop yakkety zesty

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

Title:
  unity-system-compositor crashed with SIGSEGV in invoke() from
  mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message()
  from on_read_size()

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.8.0+17.04.20161206-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/322176398baf670e4e9e5bb140a0aed0bbf0a00e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1672960] Re: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size()

[Daniel van Vugt]

** Summary changed:

- 
/usr/sbin/unity-system-compositor:11:invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message:on_read_size:std::function
+ unity-system-compositor crashed with SIGSEGV in invoke() from 
mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from 
on_read_size()

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

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

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

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

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

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

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

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

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

** Tags added: unity8-desktop

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

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

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

Title:
  unity-system-compositor crashed with SIGSEGV in invoke() from
  mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message()
  from on_read_size()

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.8.0+17.04.20161206-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/322176398baf670e4e9e5bb140a0aed0bbf0a00e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1610828] Re: unity-system-compositor crashed with SIGBUS in util_fill_rect from util_fill_box from lp_rast_clear_color from do_rasterize_bin from rasterize_bin

[Daniel van Vugt]

** Summary changed:

- 
/usr/sbin/unity-system-compositor:7:util_fill_rect:util_fill_box:lp_rast_clear_color:do_rasterize_bin:rasterize_bin
+ unity-system-compositor crashed with SIGBUS in util_fill_rect from 
util_fill_box from lp_rast_clear_color from do_rasterize_bin from rasterize_bin

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

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

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

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

Title:
  unity-system-compositor crashed with SIGBUS in util_fill_rect from
  util_fill_box from lp_rast_clear_color from do_rasterize_bin from
  rasterize_bin

Status in Unity System Compositor:
  New
Status in mesa package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.4.3+16.04.20160323-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/da25ea8387d82ab51ac1e8bcc507d7a7c35a101f
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1610828/+subscriptions

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

[Touch-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

[Daniel van Vugt]

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

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

Title:
  Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
  especially with multiple monitors, webbrowser-app or system settings

Status in Canonical System Image:
  Triaged
Status in Mir:
  Confirmed
Status in Nouveau Xorg driver:
  Unknown
Status in Unity System Compositor:
  Confirmed
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1658239] Re: base abstraction missing glibc /proc/$pid/ things

[Gary Mercer]

** Changed in: apparmor/2.10
   Status: Fix Committed => Fix Released

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

Title:
  base abstraction missing glibc /proc/$pid/ things

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.10 series:
  Fix Released
Status in AppArmor 2.11 series:
  Fix Committed
Status in AppArmor 2.9 series:
  Fix Committed
Status in AppArmor master series:
  Fix Committed
Status in apparmor package in Ubuntu:
  New

Bug description:
  There are yet more glibc-needed files missing from the base
  abstraction:

  --- base2017-01-20 15:37:50.0 -0800
  +++ /etc/apparmor.d/abstractions/base   2016-12-06 14:13:58.0 -0800
  @@ -92,7 +92,7 @@
 /sys/devices/system/cpu/online r,

 # glibc's *printf protections read the maps file
  -  @{PROC}/@{pid}/mapsr,
  +  @{PROC}/@{pid}/{maps,auxv,status}r,

 # libgcrypt reads some flags from /proc
 @{PROC}/sys/crypto/*   r,

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

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

[Touch-packages] [Bug 1672956] Re: unity-system-compositor crashed with SIGSEGV in operator() () at ./src/server/input/default_device.cpp:108

[Daniel van Vugt]

** Summary changed:

- 
/usr/sbin/unity-system-compositor:11:operator:_M_invoke:std::function:mir::dispatch::ActionQueue::dispatch:mir::dispatch::MultiplexingDispatchable::dispatch
+ unity-system-compositor crashed with SIGSEGV in operator() () at 
./src/server/input/default_device.cpp:108

** Tags added: input

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

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

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

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

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

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

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

** Tags added: unity8-desktop

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

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

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

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

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

Title:
  unity-system-compositor crashed with SIGSEGV in operator() () at
  ./src/server/input/default_device.cpp:108

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.0+17.04.20170127-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/534f8add6680a8cf76ac04d37b0f78561d1d3a6e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1672954] Re: /usr/sbin/unity-system-compositor:11:dri2_initialize_drm:dri2_initialize:_eglMatchAndInitialize:_eglMatchDriver:eglInitialize

[Daniel van Vugt]

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

Probably a duplicate of bug 1118903?

** This bug has been marked a duplicate of bug 1118903
   [enhancement] Mir lacks a software rendering backend (and doesn't work in 
virtual machines)

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

Title:
  /usr/sbin/unity-system-
  
compositor:11:dri2_initialize_drm:dri2_initialize:_eglMatchAndInitialize:_eglMatchDriver:eglInitialize

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.7.1+16.10.20160909.1-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/b026ac0724df21293f6603361979ea709d9da276 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1672954/+subscriptions

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

[Touch-packages] [Bug 1672954] [NEW] /usr/sbin/unity-system-compositor:11:dri2_initialize_drm:dri2_initialize:_eglMatchAndInitialize:_eglMatchDriver:eglInitialize

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.7.1+16.10.20160909.1-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/b026ac0724df21293f6603361979ea709d9da276 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: yakkety zesty

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

Title:
  /usr/sbin/unity-system-
  
compositor:11:dri2_initialize_drm:dri2_initialize:_eglMatchAndInitialize:_eglMatchDriver:eglInitialize

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.7.1+16.10.20160909.1-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/b026ac0724df21293f6603361979ea709d9da276 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1672954/+subscriptions

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

[Touch-packages] [Bug 1672955] Re: /usr/sbin/unity-system-compositor:11:libinput_device_config_accel_is_available:libinput_device_config_accel_set_speed:mir::input::evdev::LibInputDevice::apply_settin

[Daniel van Vugt]

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

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

** Summary changed:

- 
/usr/sbin/unity-system-compositor:11:libinput_device_config_accel_is_available:libinput_device_config_accel_set_speed:mir::input::evdev::LibInputDevice::apply_settings:std::function:mir::dispatch::ActionQueue::dispatch
+ unity-system-compositor crashed with SIGSEV in 
libinput_device_config_accel_is_available() from 
libinput_device_config_accel_set_speed() from 
mir::input::evdev::LibInputDevice::apply_settings()

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

** Tags added: input

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

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

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

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

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

** Tags added: unity8-desktop

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

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

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

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

Title:
  unity-system-compositor crashed with SIGSEV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1672955] [NEW] unity-system-compositor crashed with SIGSEV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Li

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

** Affects: canonical-devices-system-image
 Importance: Critical
 Status: New

** Affects: mir
 Importance: Critical
 Status: New

** Affects: unity-system-compositor
 Importance: Critical
 Status: New

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

** Affects: unity-system-compositor (Ubuntu)
 Importance: Critical
 Status: New


** Tags: input unity8-desktop xenial yakkety zesty

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

Title:
  unity-system-compositor crashed with SIGSEV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1672956] [NEW] unity-system-compositor crashed with SIGSEGV in operator() () at ./src/server/input/default_device.cpp:108

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.0+17.04.20170127-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/534f8add6680a8cf76ac04d37b0f78561d1d3a6e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

** Affects: canonical-devices-system-image
 Importance: Critical
 Status: New

** Affects: mir
 Importance: Critical
 Status: New

** Affects: unity-system-compositor
 Importance: Critical
 Status: New

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

** Affects: unity-system-compositor (Ubuntu)
 Importance: Critical
 Status: New


** Tags: input unity8-desktop yakkety zesty

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

Title:
  unity-system-compositor crashed with SIGSEGV in operator() () at
  ./src/server/input/default_device.cpp:108

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.0+17.04.20170127-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/534f8add6680a8cf76ac04d37b0f78561d1d3a6e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update

[Kai-Heng Feng]

Systemd PR: https://github.com/systemd/systemd/pull/5591

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

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

Title:
  Laptop stick and touchpad problems after linux 4.4 update

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Incomplete
Status in systemd source package in Xenial:
  New

Bug description:
  Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have 
behaved erratically on my Dell Precision 7510:
  * The trackpoint moves WAY too fast and there don't seem to be any parameters 
I can change in xinput to fix this. It is essentially unusable.
  * The touchpad starts with parameters set incorrectly.
  * Touchpad tap to click is now turned on again and is very sensitive. This I 
can change through xinput but the change is still odd.
  * The two finger scrolling is set incorrectly to be highly sensitive. This I 
can also change through xinput.
  * Two finger scrolling still activates often during normal use of the 
trackpad. To the extent that I had to turn off two finger scrolling to stop 
inadvertent scrolling.

  All of the above behavior is new going from 4.4.0-47 to -53.
  Previously this all worked perfectly on this machine.

  Seems to be symptoms noted by these other users on askubuntu here as
  well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
  problems-after-linux-4-4-update-on-14-04

  The touchpad symptoms I seem to be able to work around my changing
  xinput parameters, but the trackpoint I have not been able to fix at
  all (which is sad since that is my primary mouse device normally).
  Would appreciate any suggestions as to how to revert the old behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpeverill   2813 F pulseaudio
   /dev/snd/controlC0:  jpeverill   2813 F pulseaudio
  Date: Wed Jan 18 10:21:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-17 (916 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
  dmi.bios.date: 01/24/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

[Daniel van Vugt]

Even easier workaround for Mir/USC: Just default to clone mode instead
of side-by-side, which is the problem in today's duplicate bug 1672793.
Mir's legacy clone mode will at least ensure there is only one
compositor thread, so nouveau should be stable then.

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

** Changed in: unity-system-compositor
   Importance: Undecided => Medium

** Changed in: unity-system-compositor
   Status: New => Confirmed

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

Title:
  Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
  especially with multiple monitors, webbrowser-app or system settings

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Confirmed
Status in Nouveau Xorg driver:
  Unknown
Status in Unity System Compositor:
  Confirmed
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1672941] [NEW] FTBFS with older versions of OpenSSL

[Logan Rosen]

Public bug reported:

cyrus-sasl2 currently FTBFS in Yakkety because we have an older version
of OpenSSL than in Debian (1.0.2 vs 1.1.0). There was a patch upstream
to fix this: https://github.com/cyrusimap/cyrus-
sasl/commit/ccb394dc857c0f1ef03a6be5011b5aedc1dbf042

debdiff attached. Tested building with pbuilder.

** Affects: cyrus-sasl2 (Ubuntu)
 Importance: High
 Status: New

** Patch added: "cyrus-openssl.debdiff"
   
https://bugs.launchpad.net/bugs/1672941/+attachment/4837916/+files/cyrus-openssl.debdiff

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

Title:
  FTBFS with older versions of OpenSSL

Status in cyrus-sasl2 package in Ubuntu:
  New

Bug description:
  cyrus-sasl2 currently FTBFS in Yakkety because we have an older
  version of OpenSSL than in Debian (1.0.2 vs 1.1.0). There was a patch
  upstream to fix this: https://github.com/cyrusimap/cyrus-
  sasl/commit/ccb394dc857c0f1ef03a6be5011b5aedc1dbf042

  debdiff attached. Tested building with pbuilder.

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

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

[Touch-packages] [Bug 1574776] Re: Only one subtitle displayed at any given time

[Launchpad Bug Tracker]

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

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Only one subtitle displayed at any given time

Status in gstreamer1.0 package in Ubuntu:
  Expired

Bug description:
  Many of the videos I watch are subtitled foreign works; they generally
  have multiple subtitles onscreen at once, with one translating the
  speech and others translating onscreen text. Gstreamer invariably only
  displays one and more often than not it's the less helpful one,
  leaving me unable to tell what's  been said because "episode 2" is
  deemed more important information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr 25 18:25:16 2016
  InstallationDate: Installed on 2015-06-28 (302 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to xenial on 2016-04-19 (6 days ago)

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

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

[Touch-packages] [Bug 1649105] Re: ubuntu 16.04 conflict with nvidia GeForce 6150SE

[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/1649105

Title:
  ubuntu 16.04 conflict with nvidia GeForce 6150SE

Status in xorg package in Ubuntu:
  Expired

Bug description:
  seems conflictual behaviour between compiz version and available
  drivers (private and free). No solution found yet to stabilize.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  BootLog:
   [  OK  ] Started LSB: Speech Dispatcher.
   [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Dec 11 18:05:40 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] 
[1025:0394]
  InstallationDate: Installed on 2016-12-01 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser 
Printer
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: eMachines EL1358
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=b5bf3784-f5af-4627-8503-a82a628a8998 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-B1
  dmi.board.name: EL1358
  dmi.board.vendor: eMachines
  dmi.chassis.type: 3
  dmi.chassis.vendor: eMachines
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr:
  dmi.product.name: EL1358
  dmi.sys.vendor: eMachines
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Dec 11 17:55:46 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1672693] Re: GTK theme in apps appears different under Unity8 compared to Unity7

[Daniel van Vugt]

** Also affects: ubuntu-app-launch (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  GTK theme in apps appears different under Unity8 compared to Unity7

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  New

Bug description:
  Ubuntu 17.05 Unity8
  some submenus in GTK3 apps look like widgets (see attached screenshots)
  run whatever gtk3 apps native (without Xmir), sol or eog
  open the menu/submenus. the first time you open the menu everything is fine 
but the next times it shows this widget like submenus. just open and close 
submenus (hover the mouse over the main menu left right, right left)

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

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

[Touch-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

[Daniel van Vugt]

Per comment #17 it might actually be easiest to build a workaround in
Mir for now... Either disable secondary compositor threads, or build a
SingleThreadedCompositor to replace MultiThreadedCompositor.

In my spare time I'm working on an idea where post() could be made non-
blocking. So that would eliminate the need for Mir's compositor to be
threaded, and nouveau should then work (as well as it ever did for X).

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

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

** Tags added: multimonitor

** Changed in: qtmir (Ubuntu)
   Importance: Critical => Medium

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

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

Title:
  Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
  especially with multiple monitors, webbrowser-app or system settings

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Confirmed
Status in Nouveau Xorg driver:
  Unknown
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1663125] Re: Multiple apps fail to start, all with the same error message ([QPA] UbuntuClientIntegration: connection to Mir server failed.)

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Multiple apps fail to start, all with the same error message ([QPA]
  UbuntuClientIntegration: connection to Mir server failed.)

Status in Canonical System Image:
  New
Status in platform-api:
  New
Status in qtubuntu:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  Multiple apps are failing to start under Unity8 (or Mir demo servers).
  This includes webbrowser-app and ubuntu-calendar-app. They all report:

  >>>
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  [QPA] UbuntuClientIntegration: connection to Mir server failed.

  Mir returned: "Failed to connect to server socket: No such file or directory"
  <<<

  However there is actually no problem with the Mir socket at all. Not
  only do mir-demos still work OK but other clients like 'system-
  settings' and 'gallery-app' also start just fine.

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

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

[Touch-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

[Daniel van Vugt]

** Summary changed:

- Mir/Unity8 crashes/freezes on nouveau (nv50) in pushbuf_kref() especially 
with multiple monitors, webbrowser-app or system settings
+ Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially 
with multiple monitors, webbrowser-app or system settings

** Summary changed:

- Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially 
with multiple monitors, webbrowser-app or system settings
+ nouveau (nv50) crashes/freezes in pushbuf_kref()

** Summary changed:

- nouveau (nv50) crashes/freezes in pushbuf_kref()
+ Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially 
with multiple monitors, webbrowser-app or system settings

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

Title:
  Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
  especially with multiple monitors, webbrowser-app or system settings

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Confirmed
Status in Nouveau Xorg driver:
  Unknown
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1672793] Re: unity-system-compositor crashed with SIGSEGV

[Daniel van Vugt]

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

The nouveau driver is too unstable to handle multi-threaded rendering
(which Mir and Unity8 uses by default). If you want to use nouveau maybe
try unplugging one of your monitors.

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

Title:
  unity-system-compositor crashed with SIGSEGV

Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  I just got this on the first login to my new Ubuntu user profile

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: unity-system-compositor 0.9.1+17.04.20170216-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Tue Mar 14 20:14:24 2017
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2013-09-15 (1275 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket 
--from-dm-fd 13 --to-dm-fd 22 --vt 8
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f8dc76dd07f:mov0x8(%r15),%edx
   PC (0x7f8dc76dd07f) ok
   source "0x8(%r15)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
  Title: unity-system-compositor crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.75-1ubuntu1
  version.lightdm: lightdm 1.21.5-0ubuntu1
  version.mesa: libegl1-mesa-dev 13.0.4-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1672793/+subscriptions

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

[Touch-packages] [Bug 1672793] Re: unity-system-compositor crashed with SIGSEGV

[Daniel van Vugt]

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

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


** Information type changed from Private to Public

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

** This bug has been marked a duplicate of bug 1553328
   Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() 
especially with multiple monitors, webbrowser-app or system settings

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

Title:
  unity-system-compositor crashed with SIGSEGV

Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  I just got this on the first login to my new Ubuntu user profile

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: unity-system-compositor 0.9.1+17.04.20170216-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Tue Mar 14 20:14:24 2017
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2013-09-15 (1275 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket 
--from-dm-fd 13 --to-dm-fd 22 --vt 8
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f8dc76dd07f:mov0x8(%r15),%edx
   PC (0x7f8dc76dd07f) ok
   source "0x8(%r15)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
  Title: unity-system-compositor crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.75-1ubuntu1
  version.lightdm: lightdm 1.21.5-0ubuntu1
  version.mesa: libegl1-mesa-dev 13.0.4-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1672793/+subscriptions

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

[Touch-packages] [Bug 1671424] Re: Applications fail to interrupt closing them

[Daniel van Vugt]

See also bug 1672751

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

Title:
  Applications fail to interrupt closing them

Status in Canonical System Image:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Using unity7:
   * Open kate
   * write something very important in the text area
   * Press Alt+F4 because you're not very smart
   * Get dialog saying you have unsaved changes
   * You can:
 * save (which ends in a quit after saving)
 * cancel the close

  Using unity8
   * Open kate
   * write something very important in the text area
   * Press Alt+F4 because you're not very smart
   * You lost your very important text

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

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

[Touch-packages] [Bug 1672751] Re: Alt+F4 closes the whole app in Unity8 (should only close the current window)

[Daniel van Vugt]

See also bug 1671424

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

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

Title:
  Alt+F4 closes the whole app in Unity8 (should only close the current
  window)

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

Bug description:
  ubuntu 17.04 unity8

  ALT F4 closes the app along with the opened child windows
  not sure if a bug or a feature. in unity7 if you have a child window opened 
and you hit ALT F4 it only closes the child window. in unity8 it closes the app 
along with everything else. for example if you only use the keyboard you can't 
close the Help\About Kate child window because ALT F4 closes the app and you 
can't press enter on the Close button because although it looks like the focus 
is not there (this is just another bug #1671072).

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

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

[Touch-packages] [Bug 1672751] Re: Alt+F4 closes the whole app in Unity8 (should only close the current window)

[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/1672751

Title:
  Alt+F4 closes the whole app in Unity8 (should only close the current
  window)

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

Bug description:
  ubuntu 17.04 unity8

  ALT F4 closes the app along with the opened child windows
  not sure if a bug or a feature. in unity7 if you have a child window opened 
and you hit ALT F4 it only closes the child window. in unity8 it closes the app 
along with everything else. for example if you only use the keyboard you can't 
close the Help\About Kate child window because ALT F4 closes the app and you 
can't press enter on the Close button because although it looks like the focus 
is not there (this is just another bug #1671072).

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

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

[Touch-packages] [Bug 1672722] Re: there is a gap in the menu and clicking on the gap doesn't open the submenu

[Daniel van Vugt]

Can't reproduce this today, due to bug 1672931 moving the menus into the
window.

But I understand what you meant...

** Summary changed:

- there is a gap in the menu and clicking on the gap doesn't open the submenu
+ Unclickable gap between adjacent titlebar menus in Unity8

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

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

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

** Tags added: unity8-desktop

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

Title:
  Unclickable gap between adjacent titlebar menus in Unity8

Status in Canonical System Image:
  Triaged
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 17.04 unity8

  i'm starting to hit more and more the gab in the menu (space between
  the menu strings). clicking there won't open the submenu.

  launch kate native, hover the menu, click on the space between the
  menu strings. should not be such a thing. the space between the
  hitboxes should be 0 so you don't end up in situations like this

  see screenshot

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

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

[Touch-packages] [Bug 1672751] Re: Alt+F4 closes the whole app in Unity8 (should only close the current window)

[Launchpad Bug Tracker]

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

** Changed in: qtmir (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/1672751

Title:
  Alt+F4 closes the whole app in Unity8 (should only close the current
  window)

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

Bug description:
  ubuntu 17.04 unity8

  ALT F4 closes the app along with the opened child windows
  not sure if a bug or a feature. in unity7 if you have a child window opened 
and you hit ALT F4 it only closes the child window. in unity8 it closes the app 
along with everything else. for example if you only use the keyboard you can't 
close the Help\About Kate child window because ALT F4 closes the app and you 
can't press enter on the Close button because although it looks like the focus 
is not there (this is just another bug #1671072).

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

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

[Touch-packages] [Bug 1672751] Re: ALT F4 closes the app along with the opened child windows

[Daniel van Vugt]

Yeah, it works correctly in Mir demo servers. Just not in Unity8.

** Summary changed:

- ALT F4 closes the app along with the opened child windows
+ Alt+F4 closes the whole app in Unity8 (should only close the current window)

** Tags added: unity8-desktop

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

** Also affects: qtmir (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/1672751

Title:
  Alt+F4 closes the whole app in Unity8 (should only close the current
  window)

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

Bug description:
  ubuntu 17.04 unity8

  ALT F4 closes the app along with the opened child windows
  not sure if a bug or a feature. in unity7 if you have a child window opened 
and you hit ALT F4 it only closes the child window. in unity8 it closes the app 
along with everything else. for example if you only use the keyboard you can't 
close the Help\About Kate child window because ALT F4 closes the app and you 
can't press enter on the Close button because although it looks like the focus 
is not there (this is just another bug #1671072).

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

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

[Touch-packages] [Bug 1672401] Re: Screen is black for too long during login to Unity8

[Daniel van Vugt]

** Changed in: unity-system-compositor
   Status: New => Confirmed

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

Title:
  Screen is black for too long during login to Unity8

Status in Canonical System Image:
  Triaged
Status in Unity System Compositor:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  This makes me worry there's something gone wrong on every login.

  It's only this slow on a cold boot. It's somewhat faster on a second
  login.

  It'd be nice for there to be something like:

  * Splash screen
  * Progress bar
  * User's wallpaper (blurred?)

  during this time.

  Maybe it's faster on bare metal, but I'm waiting a while in a Qemu VM.

  == Note ==

  The experience might differ depending on whether you use unity-greeter
  (X11-based, default in 17.04) or unity8-greeter (not installed by
  default yet), which is better suited for this.

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

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

[Touch-packages] [Bug 1672401] Re: Screen is black for too long during login to Unity8

[Launchpad Bug Tracker]

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

** Changed in: unity-system-compositor (Ubuntu)
   Status: New => Confirmed

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

Title:
  Screen is black for too long during login to Unity8

Status in Canonical System Image:
  Triaged
Status in Unity System Compositor:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  This makes me worry there's something gone wrong on every login.

  It's only this slow on a cold boot. It's somewhat faster on a second
  login.

  It'd be nice for there to be something like:

  * Splash screen
  * Progress bar
  * User's wallpaper (blurred?)

  during this time.

  Maybe it's faster on bare metal, but I'm waiting a while in a Qemu VM.

  == Note ==

  The experience might differ depending on whether you use unity-greeter
  (X11-based, default in 17.04) or unity8-greeter (not installed by
  default yet), which is better suited for this.

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

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

[Touch-packages] [Bug 1672693] Re: GTK theme in apps appears different under Unity8 compared to Unity7

[Launchpad Bug Tracker]

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  GTK theme in apps appears different under Unity8 compared to Unity7

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.05 Unity8
  some submenus in GTK3 apps look like widgets (see attached screenshots)
  run whatever gtk3 apps native (without Xmir), sol or eog
  open the menu/submenus. the first time you open the menu everything is fine 
but the next times it shows this widget like submenus. just open and close 
submenus (hover the mouse over the main menu left right, right left)

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

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

[Touch-packages] [Bug 1672693] Re: GTK theme in apps appears different under Unity8 compared to Unity7

[Daniel van Vugt]

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

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

Title:
  GTK theme in apps appears different under Unity8 compared to Unity7

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.05 Unity8
  some submenus in GTK3 apps look like widgets (see attached screenshots)
  run whatever gtk3 apps native (without Xmir), sol or eog
  open the menu/submenus. the first time you open the menu everything is fine 
but the next times it shows this widget like submenus. just open and close 
submenus (hover the mouse over the main menu left right, right left)

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

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

[Touch-packages] [Bug 1672693] Re: GTK theme in apps appears different under Unity8 compared to Unity7

[Daniel van Vugt]

Because they are widgets. :)

This is just a difference in the theme appearance.

** Summary changed:

- some submenus in GTK3 apps look like widgets 
+ GTK theme in apps appears different under Unity8 compared to Unity7

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

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

** Tags added: gtk-mir unity8-desktop visual-quality

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

Title:
  GTK theme in apps appears different under Unity8 compared to Unity7

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.05 Unity8
  some submenus in GTK3 apps look like widgets (see attached screenshots)
  run whatever gtk3 apps native (without Xmir), sol or eog
  open the menu/submenus. the first time you open the menu everything is fine 
but the next times it shows this widget like submenus. just open and close 
submenus (hover the mouse over the main menu left right, right left)

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

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

[Touch-packages] [Bug 1672651] Re: Logging out stuck in a loop (looks like it's trying to kill the terminal)

[Daniel van Vugt]

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

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

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

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

Title:
  Logging out stuck in a loop (looks like it's trying to kill the
  terminal)

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

Bug description:
  I had terminal running, and the dash minimised.

  Then I used the ctrl-alt-del shortcut to bring up the logout menu.

  Then clicked logout.

  

  [2017-03-14:09:06:01.311] qtmir.surfaces: 
MirSurface[0x55ba4f943130,"unity8-dash"]::unregisterView(94258687984992) 
after=0 live=true
  [2017-03-14:09:06:01.312] toplevelwindowmodel: removeAt after 
  [2017-03-14:09:06:01.312] void LauncherModel::applicationRemoved(const 
QModelIndex&, int) appIndex not found
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()

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

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

[Touch-packages] [Bug 1672401] Re: Lacks animated transition between greeter and session

[Daniel van Vugt]

OK, I see a couple of seconds of blackness on a Xeon desktop still (even
after the dbus fix landed) so it's easy to extrapolate that a VM will
have even more noticeable blackness.

This is possibly related to Unity8 setting up/compiling QML things.

Although it would be nice to have transitions in USC (and that's the
whole point of it existing and the nested architecture), that's probably
just a "nice to have" on the USC side. I would like to be responsible
for that too, as native GL animation is something close to my heart and
what I've been working toward in the Mir architecture for years.

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

** Changed in: unity-system-compositor
   Importance: Undecided => Wishlist

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

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

** Summary changed:

- Lacks animated transition between greeter and session
+ Screen is black for too long during login to Unity8

** Tags added: black-screen

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

Title:
  Screen is black for too long during login to Unity8

Status in Canonical System Image:
  Triaged
Status in Unity System Compositor:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  This makes me worry there's something gone wrong on every login.

  It's only this slow on a cold boot. It's somewhat faster on a second
  login.

  It'd be nice for there to be something like:

  * Splash screen
  * Progress bar
  * User's wallpaper (blurred?)

  during this time.

  Maybe it's faster on bare metal, but I'm waiting a while in a Qemu VM.

  == Note ==

  The experience might differ depending on whether you use unity-greeter
  (X11-based, default in 17.04) or unity8-greeter (not installed by
  default yet), which is better suited for this.

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

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

[Touch-packages] [Bug 1672024] Re: Xmir crashed with SIGABRT in require()

[Daniel van Vugt]

It's this one:

static MirWaitHandle* mir_window_request_persistent_id_helper(
MirWindow* window, MirWindowIdCallback callback, void* context)
{
mir::require(mir_window_is_valid(window));

try
{
return window->request_persistent_id(callback, context);
}
catch (std::exception const& ex)
{
MIR_LOG_UNCAUGHT_EXCEPTION(ex);
return nullptr;
}
}


** Information type changed from Private to Public

** Tags added: xmir

** Changed in: xorg-server (Ubuntu)
   Importance: Medium => High

** Summary changed:

- Xmir crashed with SIGABRT in require()
+ Xmir crashed with SIGABRT in require() from 
mir_surface_request_persistent_id_sync()

** Changed in: mir (Ubuntu)
   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/1672024

Title:
  Xmir crashed with SIGABRT in require() from
  mir_surface_request_persistent_id_sync()

Status in mir package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xmir crashed with SIGABRT in mir_surface_request_persistent_id_sync()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: xmir 2:1.18.4-1ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-12.14-generic 4.10.1
  Uname: Linux 4.10.0-12-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-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
  CrashCounter: 1
  CurrentDesktop: Unity:Unity8
  Date: Sat Mar 11 11:18:53 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [1849:0102]
  InstallationDate: Installed on 2016-12-12 (88 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: Xmir -rootless -displayfd 3 -mir synfigstudio
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-12-generic 
root=UUID=61c77455-e5f4-4663-b879-b62378732cb9 ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   mir_surface_request_persistent_id_sync () from 
/usr/lib/x86_64-linux-gnu/libmirclient.so.9
   ?? ()
   ?? ()
   ?? ()
  Title: Xmir crashed with SIGABRT in mir_surface_request_persistent_id_sync()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 03/03/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H61M-VS
  dmi.board.vendor: ASRock
  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.:bvrP1.10:bd03/03/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-VS:rvr: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: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.75-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.1-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1
  xserver.bootTime: Sat Mar 11 12:44:05 2017
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu9
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1671047] Re: Starting rsibreak aborts in mir_create_menu_window_spec

[Daniel van Vugt]

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

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

Title:
  Starting rsibreak aborts in mir_create_menu_window_spec

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

Bug description:
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
  #1  0x73a6f3ea in __GI_abort () at abort.c:89
  #2  0x7fffe5ea1378 in mir_create_menu_window_spec ()
 from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fffe61515a1 in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #4  0x7fffe615279d in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #5  0x7fffe613fe1b in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #6  0x74be60c9 in QWindowPrivate::create (this=0x55aff260, 
  recursive=recursive@entry=false) at kernel/qwindow.cpp:406
  #7  0x74be64db in QWindow::create (this=this@entry=0x55aff200)
  at kernel/qwindow.cpp:584
  #8  0x753ab585 in QWidgetPrivate::create_sys 
(this=this@entry=0x55b8cb30, 
  window=window@entry=0, initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1480
  #9  0x753aad7d in QWidget::create (this=0x55b91a60, 
window=window@entry=0, 
  initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1342
  #10 0x753ab1ae in QWidgetPrivate::createWinId (this=)
  at kernel/qwidget.cpp:2579
  #11 0x753ab1e9 in QWidget::winId (this=0x55b91a60) at 
kernel/qwidget.cpp:2547
  #12 0x5557f68c in ?? ()
  #13 0x5557fb7d in ?? ()
  #14 0x55568ddf in ?? ()
  #15 0x5557010b in ?? ()
  #16 0x555709e6 in ?? ()
  #17 0x55566955 in ?? ()
  #18 0x73a583f1 in __libc_start_main (main=0x55566230, argc=3, 
  argv=0x7fffe718, init=, fini=, 
  rtld_fini=, stack_end=0x7fffe708) at 
../csu/libc-start.c:291
  #19 0x55566a2a in _start ()

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

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

[Touch-packages] [Bug 1640970] Re: 16.10: VPN Connections -> Configure VPN grayed out

[steve]

I have the same problem mint 18.1 16.04  it came in the update manager

we really need to fix this vpn  disconnect and configure

I know if I reinstall  the  OS from a iso I have it will fix it but it
would be a older network manager a lot of trouble

would have watch out for these  updates to stop it happening again  a
fix would be better

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

Title:
  16.10: VPN Connections -> Configure VPN grayed out

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10, in the nm applet menu, VPN
  Connections -> Configure VPN is grayed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 10 16:04:49 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-04 (951 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  IpRoute:
   default via 172.28.77.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.28.77.0/24 dev wlan0  proto kernel  scope link  src 172.28.77.23  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-11-07 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-07T11:36:55.286063
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/0  
BlueCedar-GUEST  f7b79954-9427-47eb-adba-875b5b152f37  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

[Daniel van Vugt]

** Changed in: protobuf (Ubuntu)
 Assignee: (unassigned) => Alexandros Frantzis (afrantzis)

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

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

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in neverball package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

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

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

[Touch-packages] [Bug 1314160] Re: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb

[Seth Arnold]

Hi Till, can you give this another look?

What is cups doing with smb here? Does it make more sense to give write
access to this entire directory as Stefan suggests or just to the
specific /var/cache/samba/gencache.tdb that was in the original report?

Thanks

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

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

Title:
  Apparmor profile violated: cupsd does mknod on
  /var/cache/samba/gencache.tdb

Status in cups package in Ubuntu:
  New

Bug description:
  When I print to my smb printer, I get a dbus notification of the
  following entries in my syslog:

  Apr 29 12:27:15 tinker kernel: [ 3359.467314] type=1400 
audit(1398770835.923:150): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.467453] type=1400 
audit(1398770835.923:151): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.469047] type=1400 
audit(1398770835.923:152): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7

  I get new entries every time I print. I'm running Ubuntu 14.04 with
  cups-daemon 1.7.2-0ubuntu1 on btrfs, fwiw.

  I saw this replicated on http://www.dedoimedo.com/computers/ubuntu-
  trusty-tahr-laptop-ultrabook.html .

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

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

[Touch-packages] [Bug 1444656] Re: GnuTLS TLS 1.2 handshake failure

[Seth Arnold]

Hello Samuel, thanks for doing this investigation. This feels like a
reasonable change to address through a Stable Release Update; the
process is a bit involved, but largely so we're sure we don't break
existing users in the process.

Are you in a position where you can prepare a debdiff? There's some
guidelines on https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation
(it's not a perfect match since that page is for security updates, not
SRUs, but it's hopefully helpful.)

See also https://wiki.ubuntu.com/StableReleaseUpdates

Thanks

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

Title:
  GnuTLS TLS 1.2 handshake failure

Status in gnutls26 package in Ubuntu:
  Invalid
Status in gnutls26 source package in Trusty:
  Triaged

Bug description:
  I'm experiencing the same issue as here:

  http://comments.gmane.org/gmane.network.gnutls.general/3713

  
  I came across a SSL handshake problem with gnutls-cli when connecting to 
  some websites, see below. It is somehow specific to gnutls as 
  openssl/Chrome/Firefox can connect fine. 

  Is this is a bug in gnutls or do you have any ideas how to
  troubleshoot it?

  $ gnutls-cli --version
  gnutls-cli (GnuTLS) 2.12.23
  Packaged by Debian (2.12.23-12ubuntu2.1)

  $ gnutls-cli www.openlearning.com
  Resolving 'www.openlearning.com'...
  Connecting to '119.9.9.205:443'...
  *** Fatal error: A TLS fatal alert has been received.
  *** Received alert [40]: Handshake failed
  *** Handshake has failed
  GnuTLS error: A TLS fatal alert has been received.

  $ gnutls-cli sequencewiz.com
  Resolving 'sequencewiz.com'...
  Connecting to '50.112.144.117:443'...
  *** Fatal error: A TLS packet with unexpected length was received.
  *** Handshake has failed
  GnuTLS error: A TLS packet with unexpected length was received.

  Thank you,

  
  Please back port the latest GnuTLS to Trusty as it is an LTS release and 
clearly GnuTLS 2.12 is an old branch.

  I've also attached packet captures of this.

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

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

[Touch-packages] [Bug 1547193] Re: Impossible to answer "disk drive not ready" question on serial console

[Nish Aravamudan]

Any chance you've been able to reproduce this with 16.04 or later? the
upstart -> systemd differences are rather significant.

I wonder if upstart is not opening /dev/console for input early enough
or so.

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

Title:
  Impossible to answer "disk drive not ready" question on serial console

Status in mountall package in Ubuntu:
  Incomplete

Bug description:
  When booting a server that is suffering from a (probably unrelated)
  bug in multipath-tools, I get the following questions posed on the
  serial console during bootup:

  The disk drive for /opt/vnx is not ready yet or not present.
  Continue to wait, or Press S to skip mounting or M for manual recovery

  Problem is, pressing "S" or "M" (even if followed by a newline) does
  absolutely nothing on the serial console. It does work on the KVM
  console, but that might not be available. You might very well need to
  send someone to a physical data centre somewhere in the middle of
  nowhere. (I ended up with powercycling the server, temporarily network
  booting it into a ramdisk, mounting the rootfs and commenting out the
  problematic entry from /etc/fstab, and rebooting again - which went
  fine, allowing me to later mount the missing filesystem manually via
  ssh.)

  I found no way to make the boot finish or break out to a debug shell,
  and it happens before sshd starts, so you're basically stuck with no
  apparent way to recover.  For this reason I feel the bug is quite
  severe.

  For what it's worth I'm running 14.04.4 LTS, mountall package version
  is 2.53. The kernel command line is
  «BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-77-generic
  root=UUID=2a141a43-97b0-4084-8816-ed1c41ac43e0 ro rootflags=subvol=@
  console=tty1 console=ttyS0,115200n8».

  Tore

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

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

[Touch-packages] [Bug 610869] Re: mountall ignores nofail mount option

[Mario]

Also affected by this on trusty! In my case somehow the message to skip
is showing up when mounting an LVM over LUKS over LVM partition however
the boot continues fine without any interaction... would be good to get
rid of that failure

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

Title:
  mountall ignores nofail mount option

Status in mountall package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mountall

  mountall ignores nofail mount option. Ubuntu can not be started if
  external sas device is down, for example.

  Description:  Ubuntu 10.04.1 LTS
  Release:  10.04, 10.10, 12.10, 14.04

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

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

[Touch-packages] [Bug 1652325] Re: Libxml2 2.9.3 fails to parse multi-byte character in large CDATA section that is split across buffer

[Bug Watch Updater]

** Changed in: libxml2
   Status: Unknown => Fix Released

** Changed in: libxml2
   Importance: Unknown => Medium

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

Title:
  Libxml2 2.9.3 fails to parse multi-byte character in large CDATA
  section that is split across buffer

Status in libxml2:
  Fix Released
Status in libxml2 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 packages libxml2 version 2.9.3*, which contains a
  regression documented here:
  
https://git.gnome.org/browse/libxml2/commit/?id=4f8606c13cb7f2684839f850b83de5ce647d3ca7

  Full release notes of 2.9.4 can be seen here:
  http://xmlsoft.org/news.html

  The bug will affect XML push parser that fails with bogus UTF-8
  encoding error when multi-byte character in large CDATA section is
  split across buffer, which can be quite common.

  As Xenial is an LTS version and this bug is quite *critical*, I wonder
  if we should provide an update to fix this one. If I remember
  correctly, we're not supposed to update to a newer version a given
  package for a given version of Ubuntu, but as this version of Ubuntu
  will be used in many servers in the coming years and XML parsing is
  quite a common task, it may help a lot of developers to have a
  backported fix of this issue.

  Let me know you if you need more information.

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

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

[Touch-packages] [Bug 1670745] Re: ssh-keyscan : bad host signature when using port option

[Bug Watch Updater]

** Changed in: openssh (Debian)
   Status: Unknown => New

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

Title:
  ssh-keyscan : bad host signature when using port option

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  In Progress
Status in openssh package in Debian:
  New

Bug description:
  When I use the port option with ssh-keygen, the result is not
  compatible with ssh known_host file format.

  UBUNTU VERSION :
  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  
  BAD :
  
  :~/.ssh$ cat /etc/issue
  Ubuntu 16.04.1 LTS \n \l
  :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...]
  debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400
  # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we see the port number because it is not hashed !

  GOOD :
  
  rm ~/.ssh/known_hosts
  :~/$ ssh -p [...port...] [...snip...]
  The authenticity of host '[[...snip...]]:[...port...] 
([[...snip...]]:[...port...])' can't be established.
  ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 
'[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list 
of known hosts.
  [...snip...]@[...snip...]'s password: 

  :~/$ !cat
  cat ~/.ssh/known_hosts
  |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=
  |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we cannot see the port number as it is well hashed !

  REMARKS :
  ==
  Same problem has already reported here (on macOS): 
https://github.com/ansible/ansible-modules-extras/issues/2651

  It seems that ssh-keyscan version and open-ssh version differs :
  dpkg -l | grep openssh :: ii  openssh-client  1:7.2p2-4ubuntu2.1  [...]
  ssh-keyscan -v [...] :: debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat 
OpenSSH* compat 0x0400

  It is very annoying because I am trying to manage hand installed VMs
  with Ansible. For that I want to automate SSH host keys storing in
  known_hosts database. And because of this bug I can't. (ansible KIKIN
  project in development).

  Thank you,
  BR,
  Gautier HUSSON.

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

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

[Touch-packages] [Bug 1672099] Re: DNS loop, >5, 000 queries per second for minutes at a time

[Paul]

I just found that I can reproduce this loop state by reconnecting to my
Wi-Fi access point. The storm starts right after this line, 5 seconds
after the link comes up:

systemd-resolved[1188]: Server 127.0.0.1 does not support DNSSEC,
downgrading to non-DNSSEC mode.

The (much shorter this time) syslog extract is attached.


The only reference I can find to 127.0.0.53 in the settings (other than comment 
lines) is in /run/resolvconf/interface/systemd-resolved:

nameserver 127.0.0.53

So I also don't know how dnsmasq gets that address unless it reads that
config file for some reason (no mention of it in source), derives it
from an incoming request, or gets it via D-Bus.

** Attachment added: "syslog_dns_storm_1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1672099/+attachment/4837813/+files/syslog_dns_storm_1.txt

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

Title:
  DNS loop, >5,000 queries per second for minutes at a time

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Since upgrading a desktop to 17.04, several times a day a DNS storm
  occurs. The same A or  record is requested over and over again.
  The storm lasts 10 to 15 minutes and can clog name resolution
  entirely, making the computer unusable for that time.

  Mar 12 08:55:12 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:13 hostname systemd-resolved[1188]: message repeated 5401 times: 
[ Processing query...]
  Mar 12 08:55:13 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:13 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:14 hostname kernel: [185434.365153] proc_thermal :00:04.0: 
Unsupported event [0x84]
  Mar 12 08:55:19 hostname systemd-resolved[1188]: message repeated 40288 
times: [ Processing query...]
  Mar 12 08:55:19 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:19 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:25 hostname systemd-resolved[1188]: message repeated 44022 
times: [ Processing query...]
  Mar 12 08:55:25 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:25 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:31 hostname systemd-resolved[1188]: message repeated 43874 
times: [ Processing query...]

  Both Firefox and Transmission originated hostnames have appeared in
  the storms, so it does not seem like an individual application is
  causing the problem.

  There are so many requests that running tcpdump on a random port (port
  29381 is used below) soon catches part of the storm. Example output
  below. Note that throughout the duration of these captures, identical
  DNS requests were being sent from pretty much every other port as
  well.

  

  = Transmission looking up mgtracker.org, got stuck on this single hostname 
for =
  = about 15 minutes (this is just the tail end of yesterday morning's storm).  
 = 
  


  08:40:24.667302 IP localhost.29381 > 127.0.0.53.domain: 60802+% [1au] ? 
mgtracker.org. (42)
  E..F..@.@..5r..5.2.y  mgtracker.org...)
  08:40:24.685708 IP 127.0.0.53.domain > localhost.29381: 60802 0/0/1 (42)
  E..Fdd@.@..5.5r..2.y  mgtracker.org...)
  08:40:33.580735 IP localhost.29381 > 127.0.0.53.domain: 53746+% [1au] A? 
mgtracker.org. (42)
  E..F.+@.@.9F...5r..5.2.y  mgtracker.org...)
  08:40:33.594830 IP 127.0.0.53.domain > localhost.29381: 53746 6/0/1 A 
92.241.171.245, A 37.19.5.139, A 77.91.229.218, A 5.79.83.194, A 5.79.83.193, A 
37.19.5.155 (138)
  E.@.@.t8...5.5r.  
mgtracker.org..X..\X..%X..M[...X...OS..X...OS..X..%.)
  08:41:30.717640 IP localhost.29381 > 127.0.0.53.domain: 63667+% [1au] ? 
mgtracker.org. (42)
  E..F\.@.@..5r..5.2.y  mgtracker.org...)
  08:41:30.733855 IP 127.0.0.53.domain > localhost.29381: 63667 0/0/1 (42)
  E..F .@.@..5.5r..2.y  mgtracker.org...)
  08:42:35.768840 IP localhost.29381 > 127.0.0.53.domain: 18342+% [1au] ? 
mgtracker.org. (42)
  E..FeH@.@..(...5r..5.2.yG...  mgtracker.org...)
  08:42:35.786098 IP 127.0.0.53.domain > localhost.29381: 18342 0/0/1 (42)
  E..F)N@.@..#...5.5r..2.yG...  mgtracker.org...)
  08:42:38.568885 IP localhost.29381 > 127.0.0.53.domain: 43765+% [1au] ? 
mgtracker.org. (42)
  E..F..@.@.s5r..5.2.y  

[Touch-packages] [Bug 1547193] Re: Impossible to answer "disk drive not ready" question on serial console

[Tore Anderson]

Yes.

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

Title:
  Impossible to answer "disk drive not ready" question on serial console

Status in mountall package in Ubuntu:
  Incomplete

Bug description:
  When booting a server that is suffering from a (probably unrelated)
  bug in multipath-tools, I get the following questions posed on the
  serial console during bootup:

  The disk drive for /opt/vnx is not ready yet or not present.
  Continue to wait, or Press S to skip mounting or M for manual recovery

  Problem is, pressing "S" or "M" (even if followed by a newline) does
  absolutely nothing on the serial console. It does work on the KVM
  console, but that might not be available. You might very well need to
  send someone to a physical data centre somewhere in the middle of
  nowhere. (I ended up with powercycling the server, temporarily network
  booting it into a ramdisk, mounting the rootfs and commenting out the
  problematic entry from /etc/fstab, and rebooting again - which went
  fine, allowing me to later mount the missing filesystem manually via
  ssh.)

  I found no way to make the boot finish or break out to a debug shell,
  and it happens before sshd starts, so you're basically stuck with no
  apparent way to recover.  For this reason I feel the bug is quite
  severe.

  For what it's worth I'm running 14.04.4 LTS, mountall package version
  is 2.53. The kernel command line is
  «BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-77-generic
  root=UUID=2a141a43-97b0-4084-8816-ed1c41ac43e0 ro rootflags=subvol=@
  console=tty1 console=ttyS0,115200n8».

  Tore

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

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

[Touch-packages] [Bug 1664352] Re: dhclient-script doesn't use configured metric for rfc3442 classless routes

[Matt Heller]

In my environment we have some dual-homed Ubuntu hosts that have one
network interface with a WAN IP and one on a private network. For proper
network connectivity we need to use the configurable metric value to
prioritize the default route provided by the WAN connected interface
over the default route (a NAT gateway) provided by the private network
DHCP server. Unfortunately the current dhclient script ignores the
configured metric when adding DHCP provided rfc3442 classless routes to
the routing table. This patch from Tom fixes dhclient behavior for my
use case.

--Matt

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

Title:
  dhclient-script doesn't use configured metric for rfc3442 classless
  routes

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  apt-cache policy isc-dhcp-client
  isc-dhcp-client:
Installed: 4.3.3-5ubuntu12.6
Candidate: 4.3.3-5ubuntu12.6
Version table:
   *** 4.3.3-5ubuntu12.6 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.3.3-5ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  If the metric option is set in interfaces(5), dhclient is executed
  with the variable IF_METRIC set to the configured administrative
  metric. The exit-hook rfc3442-classless-routes doesn't use the
  variable; thus, a multi-interface box will experience a race condition
  if multiple interfaces are supplied with one or more duplicate rfc3442
  routes. The attached patch adds support for IF_METRIC handling.

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

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

[Touch-packages] [Bug 1365375] Re: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 2.19-0ubuntu6.3

[Ben Johnson]

The fact that this was reported on 2014-09-04 and *still* has not been
fixed is unbelievable.

It seems related to (or the same as)
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1512992 , which was
opened on 2015-11-04 and has not been fixed yet either.

Only ten days ago was a fix proposed, which, by the way, doesn't seem to
resolve the problem. That is to say nothing of the obsoleted
instructions at https://wiki.ubuntu.com/Testing/EnableProposed , which
still mention the "aptitude" executable, which doesn't even exist in
Ubuntu 16.

Pretty disappointing, all around.

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

Title:
  package libc6-dev-i386 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/include/gnu', which is also in package libc6
  -dev-amd64 2.19-0ubuntu6.3

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  apt-get install gcc-multilib broke it!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6-dev-i386 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep  4 08:50:46 2014
  DpkgTerminalLog:
   Preparing to unpack .../libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb ...
   Unpacking libc6-dev-i386 (2.19-0ubuntu6.3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb (--unpack):
    trying to overwrite '/usr/include/gnu', which is also in package 
libc6-dev-amd64 2.19-0ubuntu6.3
  DuplicateSignature: package:libc6-dev-i386:(not installed):trying to 
overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 
2.19-0ubuntu6.3
  ErrorMessage: trying to overwrite '/usr/include/gnu', which is also in 
package libc6-dev-amd64 2.19-0ubuntu6.3
  SourcePackage: eglibc
  Title: package libc6-dev-i386 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/include/gnu', which is also in package 
libc6-dev-amd64 2.19-0ubuntu6.3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1664352] Re: dhclient-script doesn't use configured metric for rfc3442 classless routes

[Launchpad Bug Tracker]

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

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

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

Title:
  dhclient-script doesn't use configured metric for rfc3442 classless
  routes

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  apt-cache policy isc-dhcp-client
  isc-dhcp-client:
Installed: 4.3.3-5ubuntu12.6
Candidate: 4.3.3-5ubuntu12.6
Version table:
   *** 4.3.3-5ubuntu12.6 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.3.3-5ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  If the metric option is set in interfaces(5), dhclient is executed
  with the variable IF_METRIC set to the configured administrative
  metric. The exit-hook rfc3442-classless-routes doesn't use the
  variable; thus, a multi-interface box will experience a race condition
  if multiple interfaces are supplied with one or more duplicate rfc3442
  routes. The attached patch adds support for IF_METRIC handling.

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

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

[Touch-packages] [Bug 1672881] Re: package systemd 225-1ubuntu9 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-remova

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1672881

Title:
  package systemd 225-1ubuntu9 [modified: usr/share/dbus-1/system-
  services/org.freedesktop.systemd1.service] failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Could not install
  '/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb'

  The upgrade will continue but the
  '/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb' package may
  not be in a working state. Please consider submitting a bug report
  about it.

  subprocess installed pre-removal script returned error exit status 2

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 225-1ubuntu9 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  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
  Date: Tue Mar 14 22:25:06 2017
  DuplicateSignature: package:systemd:225-1ubuntu9 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]:subprocess 
installed pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationDate: Installed on 2017-03-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 20BSCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=5d5f9c69-cbf8-416b-a492-c4a499169055 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd 225-1ubuntu9 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 2
  UpgradeStatus: Upgraded to xenial on 2017-03-14 (0 days ago)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1672881] [NEW] package systemd 225-1ubuntu9 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-remo

[Ole Aamot]

Public bug reported:

Could not install
'/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb'

The upgrade will continue but the
'/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb' package may not
be in a working state. Please consider submitting a bug report about it.

subprocess installed pre-removal script returned error exit status 2

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 225-1ubuntu9 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
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
Date: Tue Mar 14 22:25:06 2017
DuplicateSignature: package:systemd:225-1ubuntu9 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]:subprocess 
installed pre-removal script returned error exit status 2
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
InstallationDate: Installed on 2017-03-14 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: LENOVO 20BSCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=5d5f9c69-cbf8-416b-a492-c4a499169055 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: systemd
Title: package systemd 225-1ubuntu9 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 2
UpgradeStatus: Upgraded to xenial on 2017-03-14 (0 days ago)
dmi.bios.date: 08/13/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N14ET32W (1.10 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BSCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BSCTO1WW
dmi.product.version: ThinkPad X1 Carbon 3rd
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package systemd 225-1ubuntu9 [modified: usr/share/dbus-1/system-
  services/org.freedesktop.systemd1.service] failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Could not install
  '/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb'

  The upgrade will continue but the
  '/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb' package may
  not be in a working state. Please consider submitting a bug report
  about it.

  subprocess installed pre-removal script returned error exit status 2

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 225-1ubuntu9 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  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
  Date: Tue Mar 14 22:25:06 2017
  DuplicateSignature: package:systemd:225-1ubuntu9 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]:subprocess 
installed pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationDate: Installed on 2017-03-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 20BSCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=5d5f9c69-cbf8-416b-a492-c4a499169055 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd 225-1ubuntu9 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 2
  UpgradeStatus: Upgraded to xenial on 2017-03-14 (0 days ago)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Touch-packages] [Bug 1547193] Re: Impossible to answer "disk drive not ready" question on serial console

[Nish Aravamudan]

Hello,

Does your serial console work normally? e.g., if you run a getty on it,
can you login over it?

Thanks,
Nish

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

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

Title:
  Impossible to answer "disk drive not ready" question on serial console

Status in mountall package in Ubuntu:
  Incomplete

Bug description:
  When booting a server that is suffering from a (probably unrelated)
  bug in multipath-tools, I get the following questions posed on the
  serial console during bootup:

  The disk drive for /opt/vnx is not ready yet or not present.
  Continue to wait, or Press S to skip mounting or M for manual recovery

  Problem is, pressing "S" or "M" (even if followed by a newline) does
  absolutely nothing on the serial console. It does work on the KVM
  console, but that might not be available. You might very well need to
  send someone to a physical data centre somewhere in the middle of
  nowhere. (I ended up with powercycling the server, temporarily network
  booting it into a ramdisk, mounting the rootfs and commenting out the
  problematic entry from /etc/fstab, and rebooting again - which went
  fine, allowing me to later mount the missing filesystem manually via
  ssh.)

  I found no way to make the boot finish or break out to a debug shell,
  and it happens before sshd starts, so you're basically stuck with no
  apparent way to recover.  For this reason I feel the bug is quite
  severe.

  For what it's worth I'm running 14.04.4 LTS, mountall package version
  is 2.53. The kernel command line is
  «BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-77-generic
  root=UUID=2a141a43-97b0-4084-8816-ed1c41ac43e0 ro rootflags=subvol=@
  console=tty1 console=ttyS0,115200n8».

  Tore

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

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

[Touch-packages] [Bug 1669081] Re: Ubuntu doesnt boot stuck on FSCK prompt - Press S to skip mounting or M for manual recovery

[Nish Aravamudan]

"console=ttyS0, console=ttyS0,115200n8"

Is that actually what you are passing? That doesn't seem correct for
serial consoles.

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

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

Title:
  Ubuntu doesnt boot stuck on FSCK prompt  - Press S to skip mounting or
  M for manual recovery

Status in mountall package in Ubuntu:
  Incomplete

Bug description:
  
  Working with headless server, my kernel boot console=ttyS0, 
console=ttyS0,115200n8
  Ubuntu stuck during boot , fsck prompt for user input
  and wait for user input however keyboard console does not function
  so system keep stuck ,
  i expect that keyboard will be operation so i will be able to press S to skip 
or R to recovery ,
  or to workaround it with 10 seconds timeout and automatic Skip later on 


  
 68.810067] init: plymouth-upstart-bridge main process ended, respawning
 
  [   68.822144] init: plymouth-upstart-bridge main process (178) terminated 
with 
  status 1  
  
  [   68.830078] init: plymouth-upstart-bridge main process ended, respawning   
  
  [   68.842770] init: plymouth-upstart-bridge main process (180) terminated 
with 
  status 1  
  
  [   68.850655] init: plymouth-upstart-bridge main process ended, respawning   
  
   * Stopping Read required files in advance[ OK ]  
  
   * Starting Mount filesystems on boot[ OK ]   
  
   * Stopping Track if upstart is running in a container[ OK ]  
  
   * Starting Initialize or finalize resolvconf[ OK ]   
  
   * Starting set console keymap[ OK ]  
  
   * Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
  
   * Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
  
   * Starting Bridge udev events into upstart[ OK ] 
  
   * Starting Signal sysvinit that remote filesystems are mounted[ OK ] 
  
   * Starting device node and kernel event manager[ OK ]
  
   * Starting load modules from /etc/modules[ OK ]  
  
   * Starting cold plug devices[ OK ]   
  
   * Starting log initial device creation[ OK ] 
  
   * Stopping set console keymap[ OK ]  
  
   * Stopping load modules from /etc/modules[ OK ]  
  
   * Starting Uncomplicated firewall[ OK ]  
  
   * Starting configure network device security[ OK ]   
  
   * Starting configure network device[ OK ]
  
   * Starting configure network device security[ OK ]   
  
   * Starting configure network device[ OK ]
  
   * Starting configure network device security[ OK ]   
  
   * Starting configure network device[ OK ]
  
   * Starting configure network device security[ OK ]   
  
   * Starting configure network device security[ OK ]   
  
   * Starting Mount network filesystems[ OK ]   
  
   * Stopping Mount network filesystems[ OK ]   
  
   * Starting Signal sysvinit that the rootfs is mounted[ OK ]  
  
   * Starting Clean /tmp directory[ OK ]
  
   * Stopping Clean /tmp directory[ OK ]
  
   * Starting configure network device[ OK ]
  
   * Starting Bridge socket events into upstart[ OK ]   
  
   * Stopping Read required files in advance (for other mountpoints)[ OK ]  
  
   * Stopping cold plug devices[ OK ]   
  
   * Stopping log initial device creation[ OK ] 
  
   * Starting set console font[ OK ]
  
   * Stopping set console font[ OK ]
  
   * Starting userspace bootsplash[ OK ]
  
   * Stopping userspace bootsplash[ OK ]
  
   * Starting Send an event to indicate plymouth is up[ OK ]
  
   * Stopping Send an event to indicate plymouth is up[ OK ]
  
  The disk drive for /rescuecd is not ready yet or not present. 
  

[Touch-packages] [Bug 1672797] Re: indicators-client broken as of r2752

[Michał Sawicz]

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

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

Title:
  indicators-client broken as of r2752

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Seems there was a bunch of refactoring in the indicator panel that
  didn't include the indicators-client code in
  "qml/Panel/Indicators/client".

  The error is:

  qml: Error:
  
file:///usr/share/unity8//Panel/Indicators/client/IndicatorRepresentation.qml:80
  IndicatorPage is not a type

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

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

[Touch-packages] [Bug 1670657] Re: No log out option in session indicator in unity8 in Qemu VM

[Michał Sawicz]

Right, sounds like QEMU does not pass our Platform plugin's "isPC"
criteria:

http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/plugins/Unity/Platform/platform.cpp#L29
> m_isPC = (m_chassis == "desktop" || m_chassis == "laptop" || m_chassis == 
> "server");

We really should not be making decisions based on that... Maybe in the
indicator, certainly not in unity8.

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

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

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

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

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

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

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

Title:
  No log out option in session indicator in unity8 in Qemu VM

Status in Canonical System Image:
  Triaged
Status in indicator-session package in Ubuntu:
  Invalid
Status in qmenumodel package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

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

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

[Touch-packages] [Bug 1671843] Re: Title bar menu transition is wrong

[Lukáš Tinkl]

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

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

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

Title:
  Title bar menu transition is wrong

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  When hovering your mouse over the title bar, the app title fades out
  and the app menu is shown, but without an animation.

  It should probably be a cross-fade instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170221-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 10 15:33:44 2017
  InstallationDate: Installed on 2016-05-06 (307 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (108 days ago)

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

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

[Touch-packages] [Bug 1644237] Re: unity8 fails to start as guest user

[Michael Terry]

Hmm, unity8 also doesn't show the "this session and all its data will be
deleted when you log out" warning that unity7 does.  Because zenity
isn't allowed to connect to Mir.  Looking at how we might deal with
that.

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

Title:
  unity8 fails to start as guest user

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

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

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

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

[Touch-packages] [Bug 1657440] Re: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated

[Vej]

> So my verdict is that this fix should go through as it allows automated 
> tooling to simply do apt-get update retries and self-resolve the missing gpg 
> issue.
I agree and will update the tags accordingly. 

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

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

Title:
  apt won't redownload Release.gpg after inconsistent cache updates made
  while UCA is being updated

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  In Progress

Bug description:
  # apt --version
  apt 1.2.18 (amd64)

  xenial

  I got myself into a situation where a repository has a Release and a
  Release.gpg file, but apt is just ignoring the gpg one and won't
  download it via apt update for some reason:

  The repository in question is http://ubuntu-
  cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
  how locally I have just the Release file:

  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
  -rw-r--r-- 1 root root 100K Jan 15 18:03 
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
  -rw-r--r-- 1 root root 242K Apr 21  2016 
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
  -rw-r--r-- 1 root root 7.7K Jan 18 11:45 
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release

  Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a 
"Get:":
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
  Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
InRelease
  Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
  Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release
  Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release.gpg [543 B]
  Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
  Fetched 205 kB in 0s (395 kB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  8 packages can be upgraded. Run 'apt list --upgradable' to see them.

  And I can't install packages:
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
    python3-setuptools
  The following packages will be upgraded:
    dh-python dnsmasq-base python-pkg-resources python-setuptools 
python3-cryptography python3-pkg-resources python3-requests python3-urllib3
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,193 kB of archives.
  After this operation, 808 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  WARNING: The following packages cannot be authenticated!
    dh-python dnsmasq-base python-setuptools python-pkg-resources 
python3-pkg-resources python3-setuptools python3-cryptography python3-requests 
python3-urllib3
  Install these packages without verification? [y/N] n
  E: Some packages could not be authenticated
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists#

  Somehow apt is thinking it has the Release.gpg file, but it doesn't?

  This server is behind a squid proxy.


  [Impact]
  An apt update of an apt repository that does not use InRelease during the 
time it is being updated can cause the gpg file to not be downloaded and 
updated. This makes the packages from the repository be unable to be 
authenticated.

  The Ubuntu Cloud Archive is one of the archives that meets this
  criteria.

  The impact to downstream automation deployment code is that if they
  are adding the UCA repo to a system and calling apt update during the
  time the UCA is being updated by Canonical, the repo can get into a
  state where the Release.gpg file is not there and all package installs
  will fail due to "unauthenticated packages" error.

  [Test Case]
  A detailed python script was attached.

  To reproduce this outside that script you would want to:
  1. Add the UCA repo
  2. Do the following in a loop starting at 43 minutes after the hour and run 
it until 55 minutes after the hour:
  2.1 Remove these files to simulate the UCA repo being added the first time.
  
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release
  

[Touch-packages] [Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present

[Mario]

Is there any workaround for this on on trusty in the meantime ?

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

Title:
  The disk drive for /tmp is not ready yet or not present

Status in mountall package in Ubuntu:
  Won't Fix
Status in mountall source package in Precise:
  Triaged
Status in mountall source package in Quantal:
  Won't Fix
Status in mountall source package in Trusty:
  Triaged

Bug description:
  I'm using Ubuntu 13.04 dev with mountall 2.46 and on booting I'm
  getting the message "The disk drive for /tmp is not ready yet or not
  present". But it seems that this message doesn't make any troubles.
  I'm able to use /tmp without any problems. Maybe something is trying
  to mount /tmp too early.

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

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

[Touch-packages] [Bug 1535297] Re: Unity8 reliably crashes on logout due to heap corruption (libprotobuf.so.9 called from libprotobuf-lite.so.9), causing delays while it dumps core and reports errors.

[Pat McGowan]

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

Title:
  Unity8 reliably crashes on logout due to heap corruption
  (libprotobuf.so.9 called from libprotobuf-lite.so.9), causing delays
  while it dumps core and reports errors.

Status in Canonical System Image:
  Confirmed
Status in Mesa:
  New
Status in Mir:
  Triaged
Status in libphonenumber package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/72327e33abf9e9da2cd9ed1ac28b9d843c18b5bb

  This is happening on a fresh setup, which is basically:
  Xenial 17Jan iso + unity8-desktop-session-mir package

  When I logout, I get a black screen. Turns out unity8 is crashing with
  a "double free or linked list corruption"

  Please find unity8.log attached

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

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

[Touch-packages] [Bug 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Pat McGowan]

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in Mir 0.26 series:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

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

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

[Touch-packages] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

[Pat McGowan]

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

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

Title:
  Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

Status in Canonical System Image:
  Fix Committed
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20151130.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6cee045a96ab5c9a03847aeb290f4860eea1034d
  contains more details.

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

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

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

[Pat McGowan]

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

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

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

Status in Canonical System Image:
  In Progress
Status in Oxide:
  Invalid
Status in apparmor package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

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

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

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

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

[Touch-packages] [Bug 1160804] Re: signond hangs and uses all CPU resources

[Ren�alendy]

I did not experience this behavior on 16.04.2 LTS (not tested on the
EliteBook I had when I marked myself affected, but on my new machine)

Mem: 7.7 GiB
Processor: Intel Core i5-4460 CPU @ 3.20GHz × 4
GPU: GeForce GTX 960/PCIe/SSE2 (with NVidia driver)
OS: 64bit
(diy desktop machine)

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

Title:
  signond hangs and uses all CPU resources

Status in signon package in Ubuntu:
  Incomplete

Bug description:
  Today I noticed my CPU fan going crazy and couldn't find any reason at
  first, having pretty much only a browser window open.

  Checking the system monitor, I noticed that signond used up 96% of my
  CPU resources, which caused the problem. It steadily hung at this
  level. Since I have an i7, my laptop still worked fine, I guess
  because it only used up one core.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: signond 8.43-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Wed Mar 27 10:52:27 2013
  InstallationDate: Installed on 2013-01-06 (79 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: signon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1644237] Re: unity8 fails to start as guest user

[Michael Terry]

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

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

Title:
  unity8 fails to start as guest user

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

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

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

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

[Touch-packages] [Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present

[Sworddragon]

Edit: Weird, even as reporter I can't change the Won't Fix state.

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

Title:
  The disk drive for /tmp is not ready yet or not present

Status in mountall package in Ubuntu:
  Won't Fix
Status in mountall source package in Precise:
  Triaged
Status in mountall source package in Quantal:
  Won't Fix
Status in mountall source package in Trusty:
  Triaged

Bug description:
  I'm using Ubuntu 13.04 dev with mountall 2.46 and on booting I'm
  getting the message "The disk drive for /tmp is not ready yet or not
  present". But it seems that this message doesn't make any troubles.
  I'm able to use /tmp without any problems. Maybe something is trying
  to mount /tmp too early.

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

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

[Touch-packages] [Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present

[Sworddragon]

mountall is still available in Ubuntu 17.04 dev and the bug might still
exist in this package.

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

Title:
  The disk drive for /tmp is not ready yet or not present

Status in mountall package in Ubuntu:
  Won't Fix
Status in mountall source package in Precise:
  Triaged
Status in mountall source package in Quantal:
  Won't Fix
Status in mountall source package in Trusty:
  Triaged

Bug description:
  I'm using Ubuntu 13.04 dev with mountall 2.46 and on booting I'm
  getting the message "The disk drive for /tmp is not ready yet or not
  present". But it seems that this message doesn't make any troubles.
  I'm able to use /tmp without any problems. Maybe something is trying
  to mount /tmp too early.

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

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Anders Kaseorg]

Carl: I’m not sure whether that “@Andres” was directed at Andreas or me
(I’m Anders), but I still believe the situation is explained by my
comments #31 and #33; it is not a mystery why this is seen only
occasionally.  The bug is triggered every time the console-setup package
is installed or upgraded: specifically, when dpkg runs console-
setup.postinst which runs ‘setupcon --force’.  You can reproduce either
by running ‘sudo apt install --reinstall console-setup’ or by running
‘sudo setupcon --force’ directly.  The problem is cleared by rebooting
or by logging out and in again.

** Tags added: zesty

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 1672797] Re: indicators-client broken as of r2752

[Pete Woods]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

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

Title:
  indicators-client broken as of r2752

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Seems there was a bunch of refactoring in the indicator panel that
  didn't include the indicators-client code in
  "qml/Panel/Indicators/client".

  The error is:

  qml: Error:
  
file:///usr/share/unity8//Panel/Indicators/client/IndicatorRepresentation.qml:80
  IndicatorPage is not a type

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

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

[Touch-packages] [Bug 1652325] Re: Libxml2 2.9.3 fails to parse multi-byte character in large CDATA section that is split across buffer

[Marc Deslauriers]

** Bug watch added: GNOME Bug Tracker #760183
   https://bugzilla.gnome.org/show_bug.cgi?id=760183

** Also affects: libxml2 via
   https://bugzilla.gnome.org/show_bug.cgi?id=760183
   Importance: Unknown
   Status: Unknown

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

Title:
  Libxml2 2.9.3 fails to parse multi-byte character in large CDATA
  section that is split across buffer

Status in libxml2:
  Unknown
Status in libxml2 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 packages libxml2 version 2.9.3*, which contains a
  regression documented here:
  
https://git.gnome.org/browse/libxml2/commit/?id=4f8606c13cb7f2684839f850b83de5ce647d3ca7

  Full release notes of 2.9.4 can be seen here:
  http://xmlsoft.org/news.html

  The bug will affect XML push parser that fails with bogus UTF-8
  encoding error when multi-byte character in large CDATA section is
  split across buffer, which can be quite common.

  As Xenial is an LTS version and this bug is quite *critical*, I wonder
  if we should provide an update to fix this one. If I remember
  correctly, we're not supposed to update to a newer version a given
  package for a given version of Ubuntu, but as this version of Ubuntu
  will be used in many servers in the coming years and XML parsing is
  quite a common task, it may help a lot of developers to have a
  backported fix of this issue.

  Let me know you if you need more information.

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

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

[Touch-packages] [Bug 1672838] Re: Please sync libxml2 version 2.9.4 into Ubuntu 16.04.3

[Marc Deslauriers]

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

** This bug has been marked a duplicate of bug 1652325
   Libxml2 2.9.3 fails to parse multi-byte character in large CDATA section 
that is split across buffer

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

Title:
  Please sync libxml2 version 2.9.4 into Ubuntu 16.04.3

Status in libxml2 package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.2 ships with libxml2 version 2.9.3, which introduced a
  regression causing valid XML to fail parsing when CDATA sections are
  split across buffers, as documented here:

  https://bugzilla.gnome.org/show_bug.cgi?id=760183

  This bug was fixed in libxml2 version 2.9.4, released 2016-05-23:

  http://xmlsoft.org/news.html

  This particular bug makes large XML file parsing virtually impossible
  using the package-standard version of libxml2 in 16.04.2. Therefore, I
  strongly urge that libxml2 be upgraded to version 2.9.4 for
  distribution with Ubuntu 16.04.3.

  Thanks!

  Specific details:

  Release: Ubuntu 16.04.2 LTS
  Current Package Version: 2.9.3+dfsg1-1ubuntu0.1
  Recommended Package Version: 2.9.4+dfsg1-2 (as ships with 16.10, or 
equivalent)

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

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

[Touch-packages] [Bug 1644237] Re: unity8 fails to start as guest user

[Michael Terry]

** Branch linked: lp:~mterry/unity8/guest-lockscreen

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

Title:
  unity8 fails to start as guest user

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

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

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

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

[Touch-packages] [Bug 1672838] [NEW] Please sync libxml2 version 2.9.4 into Ubuntu 16.04.3

[Kevin Fodness]

Public bug reported:

Ubuntu 16.04.2 ships with libxml2 version 2.9.3, which introduced a
regression causing valid XML to fail parsing when CDATA sections are
split across buffers, as documented here:

https://bugzilla.gnome.org/show_bug.cgi?id=760183

This bug was fixed in libxml2 version 2.9.4, released 2016-05-23:

http://xmlsoft.org/news.html

This particular bug makes large XML file parsing virtually impossible
using the package-standard version of libxml2 in 16.04.2. Therefore, I
strongly urge that libxml2 be upgraded to version 2.9.4 for distribution
with Ubuntu 16.04.3.

Thanks!

Specific details:

Release: Ubuntu 16.04.2 LTS
Current Package Version: 2.9.3+dfsg1-1ubuntu0.1
Recommended Package Version: 2.9.4+dfsg1-2 (as ships with 16.10, or equivalent)

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

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

Title:
  Please sync libxml2 version 2.9.4 into Ubuntu 16.04.3

Status in libxml2 package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.2 ships with libxml2 version 2.9.3, which introduced a
  regression causing valid XML to fail parsing when CDATA sections are
  split across buffers, as documented here:

  https://bugzilla.gnome.org/show_bug.cgi?id=760183

  This bug was fixed in libxml2 version 2.9.4, released 2016-05-23:

  http://xmlsoft.org/news.html

  This particular bug makes large XML file parsing virtually impossible
  using the package-standard version of libxml2 in 16.04.2. Therefore, I
  strongly urge that libxml2 be upgraded to version 2.9.4 for
  distribution with Ubuntu 16.04.3.

  Thanks!

  Specific details:

  Release: Ubuntu 16.04.2 LTS
  Current Package Version: 2.9.3+dfsg1-1ubuntu0.1
  Recommended Package Version: 2.9.4+dfsg1-2 (as ships with 16.10, or 
equivalent)

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

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

[Touch-packages] [Bug 1670745] Re: ssh-keyscan : bad host signature when using port option

[Colin Watson]

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

** Also affects: openssh (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857736
   Importance: Unknown
   Status: Unknown

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

Title:
  ssh-keyscan : bad host signature when using port option

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  In Progress
Status in openssh package in Debian:
  Unknown

Bug description:
  When I use the port option with ssh-keygen, the result is not
  compatible with ssh known_host file format.

  UBUNTU VERSION :
  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  
  BAD :
  
  :~/.ssh$ cat /etc/issue
  Ubuntu 16.04.1 LTS \n \l
  :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...]
  debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400
  # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we see the port number because it is not hashed !

  GOOD :
  
  rm ~/.ssh/known_hosts
  :~/$ ssh -p [...port...] [...snip...]
  The authenticity of host '[[...snip...]]:[...port...] 
([[...snip...]]:[...port...])' can't be established.
  ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 
'[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list 
of known hosts.
  [...snip...]@[...snip...]'s password: 

  :~/$ !cat
  cat ~/.ssh/known_hosts
  |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=
  |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we cannot see the port number as it is well hashed !

  REMARKS :
  ==
  Same problem has already reported here (on macOS): 
https://github.com/ansible/ansible-modules-extras/issues/2651

  It seems that ssh-keyscan version and open-ssh version differs :
  dpkg -l | grep openssh :: ii  openssh-client  1:7.2p2-4ubuntu2.1  [...]
  ssh-keyscan -v [...] :: debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat 
OpenSSH* compat 0x0400

  It is very annoying because I am trying to manage hand installed VMs
  with Ansible. For that I want to automate SSH host keys storing in
  known_hosts database. And because of this bug I can't. (ansible KIKIN
  project in development).

  Thank you,
  BR,
  Gautier HUSSON.

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

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

[Touch-packages] [Bug 1657440] Re: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated

[Samuel Matzek]

I setup a test environment to re-run the recreation script I attached
above while using the fix from xenial-proposed.

What I found was that the fix helps but is not perfect.

While the UCA repo is in the hourly update time window, the apt-get
update can still leave the user in the error case where you have the
Release file but not the Release.gpg file.  However, WITH this fix a
subsequent apt-get update resolves the issue and will pull down the
Release.gpg file.  This is in contrast to WITHOUT the fix no amount of
apt-get update calls would fix the issue until after the next hourly UCA
update.

So my verdict is that this fix should go through as it allows automated
tooling to simply do apt-get update retries and self-resolve the missing
gpg issue.

Any further changes are probably required in the Ubuntu Cloud Archive
itself to close the "partially updated" window that is part of the error
case trigger.

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

Title:
  apt won't redownload Release.gpg after inconsistent cache updates made
  while UCA is being updated

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  In Progress

Bug description:
  # apt --version
  apt 1.2.18 (amd64)

  xenial

  I got myself into a situation where a repository has a Release and a
  Release.gpg file, but apt is just ignoring the gpg one and won't
  download it via apt update for some reason:

  The repository in question is http://ubuntu-
  cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
  how locally I have just the Release file:

  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
  -rw-r--r-- 1 root root 100K Jan 15 18:03 
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
  -rw-r--r-- 1 root root 242K Apr 21  2016 
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
  -rw-r--r-- 1 root root 7.7K Jan 18 11:45 
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release

  Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a 
"Get:":
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
  Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
InRelease
  Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
  Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release
  Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release.gpg [543 B]
  Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
  Fetched 205 kB in 0s (395 kB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  8 packages can be upgraded. Run 'apt list --upgradable' to see them.

  And I can't install packages:
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
    python3-setuptools
  The following packages will be upgraded:
    dh-python dnsmasq-base python-pkg-resources python-setuptools 
python3-cryptography python3-pkg-resources python3-requests python3-urllib3
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,193 kB of archives.
  After this operation, 808 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  WARNING: The following packages cannot be authenticated!
    dh-python dnsmasq-base python-setuptools python-pkg-resources 
python3-pkg-resources python3-setuptools python3-cryptography python3-requests 
python3-urllib3
  Install these packages without verification? [y/N] n
  E: Some packages could not be authenticated
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists#

  Somehow apt is thinking it has the Release.gpg file, but it doesn't?

  This server is behind a squid proxy.


  [Impact]
  An apt update of an apt repository that does not use InRelease during the 
time it is being updated can cause the gpg file to not be downloaded and 
updated. This makes the packages from the repository be unable to be 
authenticated.

  The Ubuntu Cloud Archive is one of the archives that meets this
  criteria.

  The impact to downstream automation deployment code is that if they
  are adding the UCA repo to a system and calling apt update during the
  time the UCA is being updated by Canonical, the repo can get into a

[Touch-packages] [Bug 1672542] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

[Seth Forshee]

The cause seems to be that TEST-12-ISSUE-3171 is hanging. I've
reproduced the problem with the 4.10.0-11 and 4.10.0-13 kernels and with
systemd 232-18ubuntu1 and 232-19. I'm attaching the journal from one of
the test runs, taken from within the nspawn container while the test was
hung (using linux 4.10.0-13 and systemd 232-19).

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672542/+attachment/4837758/+files/journal.txt

** Description changed:

  Testing failed on:
-   amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
-   i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
-   ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz
+   amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
+   i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
+   ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz
  
  Upstream tests time out. Last thing displayed in the logs before the
- timeout is the login prompt from a VM.
+ timeout is the login prompt from a container running one of the tests.

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
    amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
    i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
    ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz

  Upstream tests time out. Last thing displayed in the logs before the
  timeout is the login prompt from a container running one of the tests.

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

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

[Touch-packages] [Bug 1672822] [NEW] sound only coming from left speaker on acer predator (fresh install)

[thijs boumans]

Public bug reported:

Ubuntu version: Ubuntu  16.10 and a fresh install of 17.04 and even
fedora F25-WORK-x86_64-20170228 via live usb

Device: acer predator: G9-593-7757 15,6"/i7-7700/32 GB RAM/512 GB SSD/1
TB HDD/GTX1070

expected: sound comes out of both left and right speaker and the
subwoofer

what happened instead:
Sound only comes out of the left speaker or subwoofer.

More system information:

$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

audio chip (on motherboard): VGA Chip nVidia N17E-G2-A1 GP104-725-A1

note that that is only 1 device, one would expect several here.

I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following:
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; enable-remixing = yes
 enable-lfe-remixing = yes
; lfe-crossover-freq = 0

flat-volumes = no

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 20

; default-sample-format = s16le
; default-sample-rate = 44100
; alternate-sample-rate = 48000
default-sample-channels = 3
default-channel-map = front-left,front-right,lfe

; default-fragments = 4
; default-fragment-size-msec = 25

; enable-deferred-volume = yes
deferred-volume-safety-margin-usec = 1
; deferred-volume-extra-delay-usec = 0

but this did not work. I also tried various other permutations to see if
changing the order of  front-left,front-right,lfe would work but it did
not. I also tried to see if it would work in fedora but the same problem
occurred there. When on ubuntu 16.10 at first only the subwoofer seemed
to be working and altering the file only the left speaker was working.
On ubuntu 17.04 only the left speaker was working regardless of how I
altered the above file.


Note that the speakers work perfectly fine on windows 10. 

Looking around online there seem to be a lot of problems with acer
predator laptops and sound on ubuntu.

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


** Tags: acer

** Description changed:

  Ubuntu version: Ubuntu  16.10 and a fresh install of 17.04 and even
  fedora F25-WORK-x86_64-20170228 via live usb
  
  Device: acer predator: G9-593-7757 15,6"/i7-7700/32 GB RAM/512 GB SSD/1
  TB HDD/GTX1070
  
  expected: sound comes out of both left and right speaker and the
  subwoofer
  
  what happened instead:
- Sound only comes out of the left speaker or subwoofer.  
+ Sound only comes out of the left speaker or subwoofer.
  
  More system information:
  
  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
-   Subdevices: 1/1
-   Subdevice #0: subdevice #0
+   Subdevices: 1/1
+   Subdevice #0: subdevice #0
  
  audio chip (on motherboard): VGA Chip nVidia N17E-G2-A1 GP104-725-A1
  
  note that that is only 1 device, one would expect several here.
  
- I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following: 
+ I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following:
  # This file is part of PulseAudio.
  #
  # PulseAudio is free software; you can redistribute it and/or modify
  # it under the 

[Touch-packages] [Bug 1672821] [NEW] browser crashing after remove and reinstall

[Bill Filler]

Public bug reported:

removed previous version of webbrowser-app using apt-get purge

then installed latest version from overlay 0.23+16.04.20170310-0ubuntu1

Browser stopped launching on unity8 afer doing this and getting crash.
Once I moved my .local/share/webbrowser-app directory out of the way it
started working again

Here is the stack trace:

[Current thread is 1 (Thread 0x7f50ea5d8740 (LWP 6212))]
(gdb) bt
#0  0x7f50e9fff6dd in QQmlEngine::imageProvider(QString const&) const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#1  0x7f50ea2c12b2 in QQuickPixmap::load(QQmlEngine*, QUrl const&, QSize 
const&, QFlags, AutoTransform) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#2  0x7f50ea3c42d0 in QQuickImageBase::load() () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f50c519a07b in UCQQuickImageExtension::reloadSource() ()
   from /usr/lib/x86_64-linux-gnu/libUbuntuToolkit.so.5
#4  0x7f50c51cb005 in ?? () from 
/usr/lib/x86_64-linux-gnu/libUbuntuToolkit.so.5
#5  0x7f50e8d88769 in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f50e989bddc in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x7f50e98a1316 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7f50e8d5b2f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f50e8d5d1ba in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f50e8db01d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f50e70ec197 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f50e70ec3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7f50e70ec49c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7f50e8db05df in 
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f50e8d5904a in 
QEventLoop::exec(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f50e8d6170c in QCoreApplication::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00426b35 in main ()
(gdb)

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

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

Title:
  browser crashing after remove and reinstall

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  removed previous version of webbrowser-app using apt-get purge

  then installed latest version from overlay
  0.23+16.04.20170310-0ubuntu1

  Browser stopped launching on unity8 afer doing this and getting crash.
  Once I moved my .local/share/webbrowser-app directory out of the way
  it started working again

  Here is the stack trace:

  [Current thread is 1 (Thread 0x7f50ea5d8740 (LWP 6212))]
  (gdb) bt
  #0  0x7f50e9fff6dd in QQmlEngine::imageProvider(QString const&) const ()
 from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
  #1  0x7f50ea2c12b2 in QQuickPixmap::load(QQmlEngine*, QUrl const&, QSize 
const&, QFlags, AutoTransform) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
  #2  0x7f50ea3c42d0 in QQuickImageBase::load() () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
  #3  0x7f50c519a07b in UCQQuickImageExtension::reloadSource() ()
 from /usr/lib/x86_64-linux-gnu/libUbuntuToolkit.so.5
  #4  0x7f50c51cb005 in ?? () from 
/usr/lib/x86_64-linux-gnu/libUbuntuToolkit.so.5
  #5  0x7f50e8d88769 in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #6  0x7f50e989bddc in QApplicationPrivate::notify_helper(QObject*, 
QEvent*) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #7  0x7f50e98a1316 in QApplication::notify(QObject*, QEvent*) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #8  0x7f50e8d5b2f8 in QCoreApplication::notifyInternal2(QObject*, 
QEvent*) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #9  0x7f50e8d5d1ba in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #10 0x7f50e8db01d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #11 0x7f50e70ec197 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x7f50e70ec3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #13 0x7f50e70ec49c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #14 0x7f50e8db05df in 
QEventDispatcherGlib::processEvents(QFlags) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #15 0x7f50e8d5904a in 

[Touch-packages] [Bug 1658528] Re: Sound not working anymore

[Mina]

Oh no it stopped working again.

But I guess this excludes hardware issues.

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

Title:
  Sound not working anymore

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Didn't do anything strange but the sound just stopped working for my
  headphones. Just like that.

  I have multiple soundcards. The one affected is CA0132 which is the
  built-in card of the motherboard. The other card isn't affected
  (CA0106) and is working fine with external speakers. I also tried with
  a plug and play usb soundcard (USB PnP Sound Device). also not
  affected and is working (as expected I guess).

  Tried restarting. Tried playing around with alsamixer and pavucontrol.
  Tried checking for updates and updating to latest. ...Didn't try doing
  a back-flip tho hehe XD

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf]
  ProcVersionSignature: Ubuntu 3.13.0-107.154-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-107-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 22 23:30:29 2017
  InstallationDate: Installed on 2015-02-19 (703 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: G1.Sniper Z87
  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: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd11/21/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperZ87:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperZ87:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: G1.Sniper Z87
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1670657] Re: No log out option in session indicator in unity8 in Qemu VM

[Pete Woods]

I'm pointing the finger at: http://bazaar.launchpad.net/~unity-
team/unity8/trunk/view/head:/qml/Panel/Indicators/IndicatorMenuItemFactory.qml#L69

** Changed in: indicator-session (Ubuntu)
   Status: New => Invalid

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

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

Title:
  No log out option in session indicator in unity8 in Qemu VM

Status in indicator-session package in Ubuntu:
  Invalid
Status in qmenumodel package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

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

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

[Touch-packages] [Bug 1670657] Re: No log out option in session indicator in unity8 in Qemu VM

[Pete Woods]

This is starting to look like it's somewhere in unity8 stack - see
attached screenshot of unity7 + indicators-client under Zesty

** Attachment added: "Screenshot_ubuntu-17.04_2017-03-14_16&%53&%43.png"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1670657/+attachment/4837721/+files/Screenshot_ubuntu-17.04_2017-03-14_16%26%2553%26%2543.png

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

Title:
  No log out option in session indicator in unity8 in Qemu VM

Status in indicator-session package in Ubuntu:
  Invalid
Status in qmenumodel package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

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

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

[Touch-packages] [Bug 1672797] Re: indicators-client broken as of r2752

[Launchpad Bug Tracker]

** Branch linked: lp:~pete-woods/unity8/fix-indicators-client-lp1672797

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

Title:
  indicators-client broken as of r2752

Status in unity8 package in Ubuntu:
  New

Bug description:
  Seems there was a bunch of refactoring in the indicator panel that
  didn't include the indicators-client code in
  "qml/Panel/Indicators/client".

  The error is:

  qml: Error:
  
file:///usr/share/unity8//Panel/Indicators/client/IndicatorRepresentation.qml:80
  IndicatorPage is not a type

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

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

[Touch-packages] [Bug 1672804] [NEW] can't login to dropbox.com on desktop

[Bill Filler]

Public bug reported:

when I try to access dropbox.com on webbrowser-app on desktop I get an
banner saying our browser is not supported, and it's displayed on top of
the login button so there is no way to login.

Guessing we need an override for this site

** Affects: canonical-devices-system-image
 Importance: High
 Assignee: Bill Filler (bfiller)
 Status: New

** Affects: webbrowser-app (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: New

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  can't login to  dropbox.com on desktop

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

Bug description:
  when I try to access dropbox.com on webbrowser-app on desktop I get an
  banner saying our browser is not supported, and it's displayed on top
  of the login button so there is no way to login.

  Guessing we need an override for this site

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

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

[Touch-packages] [Bug 1672795] [NEW] launching apps while in spread is a bit messy

[dinamic]

Public bug reported:

ubuntu 17.04 unity8

launching apps while in spread is a bit messy
enter spread (app switcher) with the mouse (bang the mouse to the right side of 
the screen) and let it there, don't move the mouse

now press Super 2, 3 etc to open more apps
you'll get broken previews and weird positions see screenshot

you can't exit the spread until you move the mouse

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

** Attachment added: "screenshot20170314_182129950.png"
   
https://bugs.launchpad.net/bugs/1672795/+attachment/4837712/+files/screenshot20170314_182129950.png

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

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

Title:
  launching apps while in spread is a bit messy

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

Bug description:
  ubuntu 17.04 unity8

  launching apps while in spread is a bit messy
  enter spread (app switcher) with the mouse (bang the mouse to the right side 
of the screen) and let it there, don't move the mouse

  now press Super 2, 3 etc to open more apps
  you'll get broken previews and weird positions see screenshot

  you can't exit the spread until you move the mouse

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

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

[Touch-packages] [Bug 1672797] [NEW] indicators-client broken as of r2752

[Pete Woods]

Public bug reported:

Seems there was a bunch of refactoring in the indicator panel that
didn't include the indicators-client code in
"qml/Panel/Indicators/client".

The error is:

qml: Error:
file:///usr/share/unity8//Panel/Indicators/client/IndicatorRepresentation.qml:80
IndicatorPage is not a type

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

** Summary changed:

- ind
+ indicators-client broken as of r2752

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

Title:
  indicators-client broken as of r2752

Status in unity8 package in Ubuntu:
  New

Bug description:
  Seems there was a bunch of refactoring in the indicator panel that
  didn't include the indicators-client code in
  "qml/Panel/Indicators/client".

  The error is:

  qml: Error:
  
file:///usr/share/unity8//Panel/Indicators/client/IndicatorRepresentation.qml:80
  IndicatorPage is not a type

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

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

[Touch-packages] [Bug 1672722] Re: there is a gap in the menu and clicking on the gap doesn't open the submenu

[Albert Astals Cid]

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

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

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

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

Title:
  there is a gap in the menu and clicking on the gap doesn't open the
  submenu

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

Bug description:
  Ubuntu 17.04 unity8

  i'm starting to hit more and more the gab in the menu (space between
  the menu strings). clicking there won't open the submenu.

  launch kate native, hover the menu, click on the space between the
  menu strings. should not be such a thing. the space between the
  hitboxes should be 0 so you don't end up in situations like this

  see screenshot

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

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

[Touch-packages] [Bug 1646956] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From ru...@us.ibm.com 2017-03-14 11:57 EDT---
iputils (3:20161105-1ubuntu2) validated and closing out on our end.

Thanks.

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

Title:
  ping -I support broken in yakkety version 3:20150815-2ubuntu3
  (multicast test failure)

Status in iputils package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 ==
  ---Problem Description---
  Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x)
   
  Machine Type = S822l1 
   
  ---Steps to Reproduce---
   On Host:  Enable multicast for the test interface
  1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
  2. ip link set enP5p1s0f1 allmulticast on
  root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1
  enP5p1s0f1: flags=4675  mtu 1500
  inet 170.1.1.20  netmask 255.255.255.0  broadcast 170.1.1.255
  inet6 fe80::9abe:94ff:fe5c:f1c1  prefixlen 64  scopeid 0x20
  ether 98:be:94:5c:f1:c1  txqueuelen 1000  (Ethernet)
  RX packets 488  bytes 50254 (50.2 KB)
  RX errors 0  dropped 442  overruns 0  frame 0
  TX packets 25  bytes 2226 (2.2 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 226  memory 0x3d400100-3d40017f 


  On Peer: --> catch the Test interface from the multicast group
  ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20

   
  ---uname output---
  Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 ==

  I'm able to replicate this behavior in a KVM environment with Yakkety,
  so it does not appear to be related to the specific type of interface.

  From my testing, it looks like the SO_BINDTODEVICE option is not being
  honored, so both broadcasts and multicasts are going out the default
  route device instead of the device specified by -I option to ping.

  I am unable to replicate this on a xenial host with the same 4.8.0-27
  kernel version. so I suspect some other setting is interfering with
  the ability to bind the output to a specific device.

  From my own testing:

  Xenial:

  # ip addr show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: enp0s6:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff
  inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fe15:b7ba/64 scope link 
 valid_lft forever preferred_lft forever
  3: enp0s1:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fee1:35be/64 scope link 
 valid_lft forever preferred_lft forever

  # ping -I enp0s6 -i 30 224.0.0.1
  PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data.
  64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms
  64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!)
  ^C
  ...

  Yakkety:

  # ip addr show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: enp0s5:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff
  inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:febe:97ab/64 scope link 
 valid_lft forever preferred_lft forever
  3: enp0s1:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fe30:d014/64 scope link 
 valid_lft forever preferred_lft forever

  # ping -I enp0s5 -i 30 224.0.0.1
  PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data.
  64 

[Touch-packages] [Bug 1653495] Re: systemd-resolved breaks Steam

[Brian Murray]

** Tags added: rls-z-incoming

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

Title:
  systemd-resolved breaks Steam

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When systemd-resolved is active and /etc/resolv.conf points to
  127.0.0.53, steam fails to resolve domain names, and refuses to update
  or install games.  Often, it doesn't even start, because it wants to
  update itself, but cannot reach its content servers.

  Manually (dig/host/nslookup/etc), resolving works fine, and also
  Chrome etc do'nt show any problems.  It seems Steam uses some uncommon
  type of DNS records or so?

  If I change the nameserver in /etc/resolv.conf to 8.8.8.8, of to my
  local resolver, everything works fine again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-8
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan  2 11:04:03 2017
  InstallationDate: Installed on 2016-12-22 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Latitude E7470
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro nosplash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.3
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.resolved.conf: 2016-12-27T13:33:33.754548

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

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[Brian Murray]

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

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

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0


  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)


  
  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Touch-packages] [Bug 1668608] Re: [unity8] main menu active when kate is maximized, you can open multiple child window

[dinamic]

** Tags added: unity8-desktop

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

Title:
  [unity8] main menu active when kate is maximized, you can open
  multiple child window

Status in Canonical System Image:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 Unity 8
  [unity8] main menu active when kate is maximized, you can open multiple child 
windows (kinda cool but probably wrong) but if you close kate while the child 
windows are opened the windows close but the kate process remains noming 100% 
CPU until forever (or until the process is killed/terminated)

  see attached screenshot

  launch kate, maximize, from the menu About -> Kate, About KDE, File
  Open etc, open a lot of child windows

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

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

[Touch-packages] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

[FFab]

Upstream kernel test - kernel 4.11-rc2

installation: 
when installing, error message: header file not installed;
dpkg -i displays  header file 4.11-rc2.

results:
backlight change similar that reported on 2017-02-26.
dmesg - 1 of the error messages: 
  Direct firmware load for amdgpu/topaz_k_smc.bin failed with error -2
  
brightness adjustment: not possible

remote login:  > 4 minutes after entering grub-selection (kernel 4.4, ubuntu 
16.04.1 about 1 minute (not 2))
booting (workaround): <1 minute

** Tags removed: yakket
** Tags added: kernel-bug-exists-upstream-4.11-rc2 yakkety

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

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

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

[Touch-packages] [Bug 1668535] Re: Ubuntu17.04-Failed to activate (encrypted) Swap Partition

[Adam Dingle]

This looks pretty similar to bug #1670336.  Should one of these be
marked as a duplicate?

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

Title:
  Ubuntu17.04-Failed to activate (encrypted) Swap Partition

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Zesty:
  In Progress

Bug description:
  ---Problem Description---
  Ubuntu17.04 installation with swap encryption ,Fails to activate Swap 
Partition.

  ---uname output---
  Linux tuleta4u-lp7 4.9.0-11-generic #12-Ubuntu SMP Mon Dec 12 16:16:45 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  ---boot type---
  VDVD installtion 

  ---Steps to reproduce--
  1.Install creating a prep boot, swap and root partition.
  2.Encrypt swap partition.
  3.Installation completes, and after reboot can see the failed messages for 
activating swap partition.

  --Error--
  While booting,

  [  OK  ] Started AppArmor initialization.
  [FAILED] Failed to activate swap Swap Partition.
  See 'systemctl status dev-sda2.swap' for details.
  [FAILED] Failed to start Cryptography Setup for sda2_crypt.
  See 'systemctl status systemd-cryptsetup@sda2_crypt.service' for details.
  [DEPEND] Dependency failed for Encrypted Volumes.
   Starting Raise network interfaces...

  ---Logs---

  root@tuleta4u-lp7:~# systemctl status systemd-cryptsetup@sda2_crypt.service
  ? systemd-cryptsetup@sda2_crypt.service - Cryptography Setup for sda2_crypt
 Loaded: loaded (/etc/crypttab; generated; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2017-01-02 01:58:14 EST; 1min 
57
   Docs: man:crypttab(5)
 man:systemd-cryptsetup-generator(8)
 man:systemd-cryptsetup@.service(8)
   Main PID: 2023 (code=exited, status=0/SUCCESS)

  Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for 
sda2_cr
  Jan 02 01:58:14 tuleta4u-lp7 mkswap[2057]: mkswap: error: 
/dev/mapper/sda2_crypt
  Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service: 
  Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup 
for 
  Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service: 
  Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service: 

  
  root@tuleta4u-lp7:~# systemctl start systemd-cryptsetup@sda2_crypt.service
  Job for systemd-cryptsetup@sda2_crypt.service failed because the control 
process exited with error code.
  See "systemctl status systemd-cryptsetup@sda2_crypt.service" and "journalctl 
-xe" for details.

  root@tuleta4u-lp7:~# journalctl -xe
  -- The start-up result is done.
  Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session 
opened 
  Jan 02 03:17:01 tuleta4u-lp7 CRON[3956]: (root) CMD (   cd / && run-parts 
--repo
  Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session 
closed 
  Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for 
sda2_cr
  -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- Unit systemd-cryptsetup@sda2_crypt.service has begun starting up.
  Jan 02 03:37:57 tuleta4u-lp7 systemd-cryptsetup[3960]: Volume sda2_crypt 
already
  Jan 02 03:37:57 tuleta4u-lp7 mkswap[3962]: mkswap: error: 
/dev/mapper/sda2_crypt
  Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service: 
  Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup 
for 
  -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has failed
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- Unit systemd-cryptsetup@sda2_crypt.service has failed.
  -- 
  -- The result is failed.
  Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service: 
  Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service:

  root@tuleta4u-lp7:~# cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  #
  # / was on /dev/sda3 during installation
  UUID=44e6ba68-4cbb-4978-8d90-6077796b3715 /   xfs defaults
0   0

  root@tuleta4u-lp7:~# lsblk
  NAME   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
  sda  8:00   235G  0 disk  
  ??sda1   8:10 7M  0 part  
  ??sda2   8:2028G  0 part  
  ? ??sda2_crypt 253:0028G  0 crypt [SWAP]
  ??sda3   8:30 167.7G  0 part  /
  ??sda4   8:4028G  0 part  
  sdb  8:16   0   235G  0 disk  
  sr0 11:01 631.3M  0 rom   
  sr1 11:11 

[Touch-packages] [Bug 1672673] Re: Application menus should hide when triggering the spread

[Albert Astals Cid]

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

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

Title:
  Application menus should hide when triggering the spread

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Having the menu open makes using the spread hard.

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

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

[Touch-packages] [Bug 1314160] Re: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb

[Stefan Taferner]

The bug is still present in 16.04.2

Add this line to /etc/apparmor.d/local/usr.sbin.cupsd:

/var/cache/samba/* w,

Then 'sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.cupsd'

The reason why including abstractions/samba does not work is because in
abstractions/samba is the '*' missing.

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

Title:
  Apparmor profile violated: cupsd does mknod on
  /var/cache/samba/gencache.tdb

Status in cups package in Ubuntu:
  Expired

Bug description:
  When I print to my smb printer, I get a dbus notification of the
  following entries in my syslog:

  Apr 29 12:27:15 tinker kernel: [ 3359.467314] type=1400 
audit(1398770835.923:150): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.467453] type=1400 
audit(1398770835.923:151): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.469047] type=1400 
audit(1398770835.923:152): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7

  I get new entries every time I print. I'm running Ubuntu 14.04 with
  cups-daemon 1.7.2-0ubuntu1 on btrfs, fwiw.

  I saw this replicated on http://www.dedoimedo.com/computers/ubuntu-
  trusty-tahr-laptop-ultrabook.html .

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

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

[Touch-packages] [Bug 1672398] Re: Newly launched Ubuntu Terminal doesn't have keyboard focus

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu-terminal-app/staging

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

Title:
  Newly launched Ubuntu Terminal doesn't have keyboard focus

Status in Canonical System Image:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  After entering your password at the prompt, you cannot type in the
  Ubuntu Terminal because it doesn't have focus.

  Visually the terminal appears to have focus, but the reality is it
  doesn't.

  As soon as you click on the terminal, you can type normally.

  Unsure if the fault lies with the terminal app or unity8.

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

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

[Touch-packages] [Bug 1659339] Re: "libmtp error: Could not send object" when copying a file to MTP folder

[Vej]

** Package changed: ubuntu => mtp (Ubuntu)

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

Title:
  "libmtp error: Could not send object" when copying a file to MTP
  folder

Status in Linux Mint:
  New
Status in mtp package in Ubuntu:
  New

Bug description:
  Linux Mint 17.2/17.3/18/18.1 (problem arises in all of these).

  I connect my Android phone over MTP, LM opens the folder (for example
  "mtp://[usb:001,005]/Almacenamiento%20del%20tel%C3%A9fono"), then I
  try to copy a file from my filesystem to the phone.

  I get a window that says:

  Error while copying "foo.png".//There was an error copying the file
  into
  mtp://[usb:001,005]/Almacenamiento%20del%20tel%C3%A9fono/.//libmtp
  error:  Could not send object info.//Cancel/Skip.

  I think that the copy operation should proceed and having my file
  "foo.png" in phone's memory.

  The problem happens always, indeed the copy never worked for me in any
  of the LM versions mentioned above, that is, from the very first time
  I used LM.

  I can read (copy) files from the phone to the laptop, and I can delete
  files from the phone.

  $ lsusb
  Bus 002 Device 002: ID 13b1:0041 Linksys 
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
  Bus 001 Device 005: ID 0bb4:0c02 HTC (High Tech Computer Corp.) Dream / ADP1 
/ G1 / Magic / Tattoo (Debug)
  Bus 001 Device 002: ID 0458:00f2 KYE Systems Corp. (Mouse Systems) 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

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

[Touch-packages] [Bug 1659339] Re: "libmtp error: Could not send object" when copying a file to MTP folder

[Launchpad Bug Tracker]

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

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

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

Title:
  "libmtp error: Could not send object" when copying a file to MTP
  folder

Status in Linux Mint:
  New
Status in mtp package in Ubuntu:
  New

Bug description:
  Linux Mint 17.2/17.3/18/18.1 (problem arises in all of these).

  I connect my Android phone over MTP, LM opens the folder (for example
  "mtp://[usb:001,005]/Almacenamiento%20del%20tel%C3%A9fono"), then I
  try to copy a file from my filesystem to the phone.

  I get a window that says:

  Error while copying "foo.png".//There was an error copying the file
  into
  mtp://[usb:001,005]/Almacenamiento%20del%20tel%C3%A9fono/.//libmtp
  error:  Could not send object info.//Cancel/Skip.

  I think that the copy operation should proceed and having my file
  "foo.png" in phone's memory.

  The problem happens always, indeed the copy never worked for me in any
  of the LM versions mentioned above, that is, from the very first time
  I used LM.

  I can read (copy) files from the phone to the laptop, and I can delete
  files from the phone.

  $ lsusb
  Bus 002 Device 002: ID 13b1:0041 Linksys 
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
  Bus 001 Device 005: ID 0bb4:0c02 HTC (High Tech Computer Corp.) Dream / ADP1 
/ G1 / Magic / Tattoo (Debug)
  Bus 001 Device 002: ID 0458:00f2 KYE Systems Corp. (Mouse Systems) 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

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

[Touch-packages] [Bug 1672682] Re: Eclipse crashes due to misbehaviour of the "g_type_check_instance_cast" function

[Alberto Salvia Novella]

** Package changed: glib2.0 (Ubuntu) => eclipse (Ubuntu)

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

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

Title:
  Eclipse crashes due to misbehaviour of the
  "g_type_check_instance_cast" function

Status in GLib:
  Unknown
Status in eclipse package in Ubuntu:
  Confirmed

Bug description:
  During normal Eclipse IDE usage it crashed. The Java log, which is
  attached, shows that it's a problem in the
  "g_type_check_instance_cast" function from the "libgobject-2.0"
  library.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0 2.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 14 12:04:08 2017
  InstallationDate: Installed on 2016-05-02 (315 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1672398] Re: Newly launched Ubuntu Terminal doesn't have keyboard focus

[Florian Boucault]

** Changed in: ubuntu-terminal-app (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Newly launched Ubuntu Terminal doesn't have keyboard focus

Status in Canonical System Image:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  After entering your password at the prompt, you cannot type in the
  Ubuntu Terminal because it doesn't have focus.

  Visually the terminal appears to have focus, but the reality is it
  doesn't.

  As soon as you click on the terminal, you can type normally.

  Unsure if the fault lies with the terminal app or unity8.

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

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