[Touch-packages] [Bug 1531787] Re: USC crash (error: Cannot access memory at address ...) at usc::SystemCompositor::run (this=0xbfb4a914) at src/system_compositor.cpp:129

[Stephen M. Webb]

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

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

** 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/1531787

Title:
  USC crash (error: Cannot access memory at address ...) at
  usc::SystemCompositor::run (this=0xbfb4a914) at
  src/system_compositor.cpp:129

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

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.2.0+16.04.20151222.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/d4b27439a92b91952fee0b16b8251e2b6aa65208
  contains more details.

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

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

[Touch-packages] [Bug 1463855] Re: USC spinner fails on Android

[Stephen M. Webb]

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

** Changed in: unity-system-compositor (Ubuntu Vivid)
   Status: New => Fix Released

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

Title:
  USC spinner fails on Android

Status in Unity System Compositor:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Fix Released
Status in unity-system-compositor source package in Vivid:
  Fix Released

Bug description:
  USC spinner from trunk (r218) fails to run on Android with "Can't
  eglMakeCurrent".

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

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

[Touch-packages] [Bug 1324183] Re: [enhancement] FD passing for unity-system-compositor

[Stephen M. Webb]

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

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

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

Title:
  [enhancement] FD passing for unity-system-compositor

Status in Light Display Manager:
  New
Status in systemd:
  New
Status in Unity System Compositor:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Here's the global bug for FD passing from unity-system-compositor to
  unity8 rather than having a socket file.

  The general flow would be:
  *) LightDM gets a client socket from USC
  *) LightDM sends that fd to logind as a part of the session description 
(instead of X server number)
  *) unity8 pulls the fd from logind on startup

  This then needs an apparmour profile so that dbus denies access to the
  system-compositor fd from everything that's not unity.

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

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

[Touch-packages] [Bug 1539300] Re: unity-system-compositor crashed on rethrow with no usable stack trace

[Stephen M. Webb]

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

Marked this as a duplicate of bug #1531787 because they're effectively
the same (not very useful) stack trace, with the difference being due to
ARM EABI vs. x86 API in the C++ runtime library.  I notice that this bug
only occurs on ARM, and #1531787 only occurs on x86.

** This bug has been marked a duplicate of bug 1531787
   USC crash (error: Cannot access memory at address ...) at 
usc::SystemCompositor::run (this=0xbfb4a914) at src/system_compositor.cpp:129

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

Title:
  unity-system-compositor crashed on rethrow with no usable stack trace

Status in Unity System Compositor:
  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.3.1+16.04.20160121.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/43c0c2dadba3b6f445da3ec932dae403bd73f1b2
  contains more details.

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

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

[Stephen M. Webb]

This problem appears to be exlcusively in the Mir libraries and not in
U-S-C.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Confirmed
Status in Mir:
  Confirmed
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Invalid

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()

[Stephen M. Webb]

This problem appears to be exlcusively in the Mir libraries and not in
U-S-C.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Confirmed
Status in Mir:
  Confirmed
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Invalid

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 1557634] Re: Unity8/Mir server crashes when given an invalid keymap

[Stephen M. Webb]

** Changed in: mir (Ubuntu)
   Status: Confirmed => Won't Fix

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

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

Title:
  Unity8/Mir server crashes when given an invalid keymap

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Won't Fix
Status in mir package in Ubuntu:
  Won't Fix
Status in qtmir package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/4b8d65fc943d9604a00af4439b24bf85ddc6d1a7

  I foolishly tested unity8's keymap switching with the keymap "zh" (I
  should have used "cn").

  But I noticed that libmirclient crashed when I switched to "zh".
  While this isn't a supported use case, we shouldn't crash.

  Here's a non-debugful stack trace:

  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb614562e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
  #2  0xb6146332 in abort () from /lib/arm-linux-gnueabihf/libc.so.6
  #3  0xb6283120 in __gnu_cxx::__verbose_terminate_handler() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6281950 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #5  0xb62819a6 in std::terminate() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6281bc6 in __cxa_throw ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #7  0xb3d726ec in ?? () from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #8  0xb3d857f2 in 
mir::events::make_event(mir::IntWrapper const&, long long, std::string const&, std::string const&, std::string 
const&, std::string const&) ()
     from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #9  0xb3e3e5e2 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #10 0xb3e24d1e in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #11 0xb3e2aeb0 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #12 0xb3e26870 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #13 0xaa6476ce in qtmir::MirSurface::setKeymap(QString const&, QString const&)

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

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

[Touch-packages] [Bug 1281192] Re: After removing and restarting: low graphics mode and blank screen

[Stephen M. Webb]

The ubuntu-desktop-mir package was discontinued prior to the release of
Ubuntu 16.10 and removed from this project.  This bug is no longer valid
for this project.

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

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

Title:
  After removing and restarting: low graphics mode and blank screen

Status in One Hundred Papercuts:
  Triaged
Status in Unity System Compositor:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Triaged

Bug description:
  When I remove u-s-c and ubuntu-desktop-mir with `remove --auto-
  remove`, I get greeted with the "Low graphics" dialog and lightdm
  won't start. I can get back to the desktop if I reinstall both
  packages (and run `sudo restart lightdm`).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-desktop-mir 0.0.2+14.04.20140212.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Feb 17 13:07:13 2014
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
  InstallationDate: Installed on 2014-01-14 (34 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140113)
  PackageArchitecture: all
  SourcePackage: unity-system-compositor
  UnitySystemCompositorLog:
   ERROR: 
/build/buildd/mir-0.1.5+14.04.20140212/src/platform/graphics/mesa/linux_virtual_terminal.cpp(125):
 Throw in function virtual void 
mir::graphics::mesa::LinuxVirtualTerminal::set_graphics_mode()
   Dynamic exception type: 
boost::exception_detail::clone_impl
   std::exception::what: Failed to set VT to graphics mode
   5, "Input/output error"
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.libdrm: libdrm2 2.4.52-1
  version.lightdm: lightdm 1.9.7-0ubuntu2
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1204505] Re: [enhancement] unity-system-compositor needs to have hw pointer functionality enabled back

[Stephen M. Webb]

** Changed in: unity-system-compositor
   Status: Fix Committed => Fix Released

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

Title:
  [enhancement] unity-system-compositor needs to have hw pointer
  functionality enabled back

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

Bug description:
  Right now, unity-system-compositor disable hw pointer in Mir through:
  unity-compositor-command=unity-system-compositor --enable-input=false

  This was to workaround an issue with some ati cards that we
  encountered: https://bugs.launchpad.net/mir/+bug/1203070

  Prerequisite fix: bug 1206780

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

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

[Touch-packages] [Bug 1619448] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available()

[Stephen M. Webb]

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

** This bug has been marked a duplicate of bug 1672955
   unity-system-compositor crashed with SIGSEGV in 
libinput_device_config_accel_is_available() from 
libinput_device_config_accel_set_speed() from 
mir::input::evdev::LibInputDevice::apply_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/1619448

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available()

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

Bug description:
  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Sep  1 15:49:59 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor D4xx/D5xx/N4xx/N5xx 
Integrated Graphics Controller [1025:0349]
 Subsystem: Acer Incorporated [ALI] Atom Processor D4xx/D5xx/N4xx/N5xx 
Integrated Graphics Controller [1025:0349]
  InstallationDate: Installed on 2016-08-27 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket 
--from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f6efd9035f0 
:mov0x58(%rdi),%rax
   PC (0x7f6efd9035f0) ok
   source "0x58(%rdi)" (0x3289) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   libinput_device_config_accel_is_available () from 
/usr/lib/x86_64-linux-gnu/libinput.so.10
   libinput_device_config_accel_set_speed () from 
/usr/lib/x86_64-linux-gnu/libinput.so.10
   
mir::input::evdev::LibInputDevice::apply_settings(mir::input::PointerSettings 
const&) () from /usr/lib/x86_64-linux-gnu/mir/server-platform/input-evdev.so.5
   mir::dispatch::ActionQueue::dispatch(unsigned int) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.6
   mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.6
  Title: unity-system-compositor crashed with SIGSEGV in 
libinput_device_config_accel_is_available()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.70-1
  version.lightdm: lightdm 1.19.4-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1539300] Re: unity-system-compositor crashed on rethrow with no usable stack trace

[Stephen M. Webb]

** Changed in: unity-system-compositor
Milestone: 0.4.2 => None

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

Title:
  unity-system-compositor crashed on rethrow with no usable stack trace

Status in Unity System Compositor:
  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.3.1+16.04.20160121.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/43c0c2dadba3b6f445da3ec932dae403bd73f1b2
  contains more details.

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

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

[Touch-packages] [Bug 1676931] Re: logs are not included in unity-system-compositor bugs automatically reported to Ubuntu using apport

[Stephen M. Webb]

** Changed in: unity-system-compositor
Milestone: None => 0.9.2

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

Title:
  logs are not included in unity-system-compositor bugs automatically
  reported to Ubuntu using apport

Status in Canonical System Image:
  In Progress
Status in Unity System Compositor:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  In Progress

Bug description:
  When a crash in unity-system-compositor is automatically reported to
  the Ubuntu bug tracker using the apport tool, additional information
  should be included to make analysis easier.

  At the very least, /var/log/lightdm/unity-system-compositor.log should
  be included.

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

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

[Touch-packages] [Bug 1675364] Re: [regression] GTK and KDE apps fail to start under Unity8 (without gnome-session running)

[Stephen M. Webb]

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

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: William Hua (attente) => (unassigned)

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

** This bug has been marked a duplicate of bug 1675448
   Unity 8 doesnt allow multiple mir connections from an application instance

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

Title:
  [regression] GTK and KDE apps fail to start under Unity8 (without
  gnome-session running)

Status in Canonical System Image:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in libertine package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Recently something has regressed and if i start konsole (using xmir)
  in unity8 all i get is the splash screen with a spinner forever.

  Looking at the ps output it seems that the konsole process has
  actually started.

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

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

[Touch-packages] [Bug 1675448] Re: Unity 8 doesnt allow multiple mir connections from an application instance

[Stephen M. Webb]

Turns out this is the cause of launch failures of any GTK+, Qt, or SDL
application that is trying to use Mir instead of X11.

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

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

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

Title:
  Unity 8 doesnt allow multiple mir connections from an application
  instance

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

Bug description:
  Some clients like to probe to see if a mir connection is available
  such as SDL2 and SDL1.2.

  This is an issue in U8 as it doesnt seem to allow multiple connections
  in one process.

  Example:
  http://paste.ubuntu.com/24235399/

  Output on U8:
  http://paste.ubuntu.com/24235406/

   Proposed solution 

  Related to bug #1589637

  We need to accept multiple connections from the same application
  instance, relying on ubuntu-app-launch to tell us about instances and
  their lifecycle.

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

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

[Stephen M. Webb]

** Changed in: mir/0.26
Milestone: 0.26.3 => None

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

-- 
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:
  Fix Released
Status in Mir:
  Invalid
Status in Mir 0.26 series:
  Invalid
Status in libsdl2 package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Fix Released

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 1668409] Re: Firefox fails to launch in unity8 zesty

[Stephen M. Webb]

It's going to be an issue until Firefox gets fixed upstream to not try
to use X11 when it's using Mir.

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

Title:
  Firefox fails to launch in unity8 zesty

Status in Canonical System Image:
  Incomplete
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  daily iso of zesty exploring clean u8

  to repro
  1) open app drawer
  2) find ff icon, click to launch

  journal shows the following
  http://pastebin.ubuntu.com/24080554/

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

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

[Touch-packages] [Bug 1613601] Re: [MIR] unity-system-compositor

[Stephen M. Webb]

** Changed in: unity-system-compositor (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] unity-system-compositor

Status in unity-system-compositor package in Ubuntu:
  Fix Released

Bug description:
  Note that a much older version of unity-system-compositor had been previously 
accepted into main:
  https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1203588

  [Availability]
  * Available in universe

  [Rationale]
  * This package is the system compositor for our convergence effort
  * Used by default on phablet images and in the Unity8 session on the desktop

  [Security]
  * No known security issues at this time
  * A security review is recommended. The package had been reviewed in the past 
by the security team for use on the phone, but it has changed significantly 
since then.

  [Quality assurance]
  * This package has unit and integration tests that run with each package build
  * CI is used during development

  [Dependencies]
  * All dependencies are in main
  * It 'Suggests' repowerd which already has a MIR:
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1613585

  [Standards compliance]
  * Follows FHS and Debian Policy.
  * This package uses cmake.

  [Maintenance]
  * This package is maintained by Canonical and actively in use on the phone 
images
  * mir-development-team/unity-system-compositor-team are subscribed to project 
and ubuntu package bugs respectively (The unity-system-compositor developers 
are the Mir developers)

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

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

[Touch-packages] [Bug 1442508] Re: /usr/sbin/unity-system-compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::Protob

[Stephen M. Webb]

** Tags added: protobuf

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

Title:
  /usr/sbin/unity-system-
  
compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

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.0.5+15.04.20150227-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/009ff218f16e78b57614e9a3a0e4ddae9cb0750a
  contains more details.

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

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

[Touch-packages] [Bug 1442505] Re: /usr/sbin/unity-system-compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor:

[Stephen M. Webb]

** Tags added: protobuf

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

Title:
  /usr/sbin/unity-system-
  
compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch:mir::frontend::detail::SocketConnection::on_new_message:mir::frontend::detail::SocketConnection::on_read_size

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

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.0.5+15.04.20150227-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/f97c1aceb8c847481ec0aed856e113739a423e7b
  contains more details.

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

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

[Touch-packages] [Bug 1479030] Re: unity-system-compositor crashes with SIGABRT in google::protobuf::internal::LogMessage::Finish

[Stephen M. Webb]

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

** 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/1479030

Title:
  unity-system-compositor crashes with SIGABRT in
  google::protobuf::internal::LogMessage::Finish

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

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.0.5+15.10.20150722-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/17e8c095201d404cdb3a785f4870e95f200fea1d
  contains more details.

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

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

[Touch-packages] [Bug 1665307] Re: unity-system-compositor crashed with SIGSEGV in mir::frontend::detail::invoke

[Stephen M. Webb]

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

** 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/1665307

Title:
  unity-system-compositor crashed with SIGSEGV in
  mir::frontend::detail::invokehttps://bugs.launchpad.net/mir/+bug/1665307/+subscriptions

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

[Touch-packages] [Bug 1676931] Re: logs are not included in bugs automatically reported to Ubuntu using apport

[Stephen M. Webb]

** Changed in: unity-system-compositor
   Status: Triaged => In Progress

** Changed in: unity-system-compositor (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  logs are not included in bugs automatically reported to Ubuntu using
  apport

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

Bug description:
  When a crash in unity-system-compositor is automatically reported to
  the Ubuntu bug tracker using the apport tool, additional information
  should be included to make analysis easier.

  At the very least, /var/log/lightdm/unity-system-compositor.log should
  be included.

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

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

[Touch-packages] [Bug 1536662] Re: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random

[Stephen M. Webb]

** Changed in: unity-system-compositor
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Black screen: Mir hangs and then crashes on startup/login
  due to reading from /dev/random

Status in Mir:
  Fix Released
Status in Mir 0.19 series:
  Won't Fix
Status in Mir 0.20 series:
  Won't Fix
Status in Mir 0.21 series:
  Triaged
Status in Unity System Compositor:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Fix Released

Bug description:
  cookie_factory attempts to read data from /dev/random at boot, and
  blocks until it has enough random data or timesout after 30 seconds.

  How I can reproduce
  1. Run the Unity8 greeter as a mir server
  2. Reboot

  Expected behavior: Greeter is displayed as mir && USC run happily
  Actual behavior: Mir throws an exception after 30 seconds

  Work-around:
  Before logging in, move the mouse around lots, for at least 20 seconds. And 
after logging in, while you're looking at a black screen, move the mouse around 
furiously. This will populate the kernel entropy pool sufficiently to avoid the 
hang and crash.

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

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

[Touch-packages] [Bug 1479030] Re: unity-system-compositor crashes with SIGABRT in google::protobuf::internal::LogMessage::Finish

[Stephen M. Webb]

** Tags added: protobuf

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

Title:
  unity-system-compositor crashes with SIGABRT in
  google::protobuf::internal::LogMessage::Finish

Status in Unity System Compositor:
  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.0.5+15.10.20150722-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/17e8c095201d404cdb3a785f4870e95f200fea1d
  contains more details.

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

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

[Touch-packages] [Bug 1543594] Re: unity-system-compositor locked up in __libc_do_syscall()

[Stephen M. Webb]

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

** Changed in: unity-system-compositor (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/1543594

Title:
  unity-system-compositor locked up in __libc_do_syscall()

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in Mir 0.19 series:
  Fix Released
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  This happened when I got an incoming call, couldn't wake the screen
  up, even though the phone worked fine otherwise.

  powerd-cli list took ~20s to return

  https://paste.ubuntu.com/15001777/ for u-s-c trace
  https://paste.ubuntu.com/15001805/ tamer powerd trace

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity-system-compositor 0.4.1+15.04.20160203-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Feb  9 15:06:13 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1454530118
  GraphicsCard:
   
  InstallationDate: Installed on 2016-02-06 (3 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160206-020305)
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 10 --to-dm-fd 13 --vt 1
  ProcCwd: /
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46
   __lll_lock_wait (futex=futex@entry=0x6402fc, private=0) at lowlevellock.c:46
   __GI___pthread_mutex_lock (mutex=0x6402fc) at pthread_mutex_lock.c:80
   __gthread_mutex_lock (__mutex=0x6402fc) at 
/usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748
   lock (this=0x6402fc) at /usr/include/c++/4.9/mutex:135
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.60-2
  version.lightdm: lightdm 1.14.4-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1665307] Re: unity-system-compositor crashed with SIGSEGV in mir::frontend::detail::invoke

[Stephen M. Webb]

** Tags added: protobuf

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

Title:
  unity-system-compositor crashed with SIGSEGV in
  mir::frontend::detail::invokehttps://bugs.launchpad.net/mir/+bug/1665307/+subscriptions

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

[Stephen M. Webb]

** Tags added: protobuf

-- 
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/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:
  Confirmed
Status in Mir:
  Confirmed
Status in Unity System Compositor:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

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 1676931] Re: logs are not included in bugs automatically reported to Ubuntu using apport

[Stephen M. Webb]

** Changed in: unity-system-compositor
 Assignee: (unassigned) => Stephen M. Webb (bregma)

** Changed in: unity-system-compositor (Ubuntu)
 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 unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1676931

Title:
  logs are not included in bugs automatically reported to Ubuntu using
  apport

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

Bug description:
  When a crash in unity-system-compositor is automatically reported to
  the Ubuntu bug tracker using the apport tool, additional information
  should be included to make analysis easier.

  At the very least, /var/log/lightdm/unity-system-compositor.log should
  be included.

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

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

[Touch-packages] [Bug 1676931] [NEW] logs are not included in bugs automatically reported to Ubuntu using apport

[Stephen M. Webb]

Public bug reported:

When a crash in unity-system-compositor is automatically reported to the
Ubuntu bug tracker using the apport tool, additional information should
be included to make analysis easier.

At the very least, /var/log/lightdm/unity-system-compositor.log should
be included.

** Affects: unity-system-compositor
 Importance: Medium
 Status: Triaged

** Affects: unity-system-compositor (Ubuntu)
 Importance: Medium
 Status: Triaged

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

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

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

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

Title:
  logs are not included in bugs automatically reported to Ubuntu using
  apport

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

Bug description:
  When a crash in unity-system-compositor is automatically reported to
  the Ubuntu bug tracker using the apport tool, additional information
  should be included to make analysis easier.

  At the very least, /var/log/lightdm/unity-system-compositor.log should
  be included.

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

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

[Touch-packages] [Bug 1471866] Re: /usr/bin/unity8:11:google::protobuf::internal::Mutex::Lock:MutexLock:google::protobuf::internal::OnShutdown:google::protobuf::internal::FunctionClosure0::Run:google:

[Stephen M. Webb]

Since error.ubuntu.com shows this only occurring in Ubuntu releases that
are out of support, I'm closing this as Wont Fix.

** Changed in: mir
   Status: New => Won't Fix

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

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

Title:
  
/usr/bin/unity8:11:google::protobuf::internal::Mutex::Lock:MutexLock:google::protobuf::internal::OnShutdown:google::protobuf::internal::FunctionClosure0::Run:google::protobuf::GoogleOnceInitImpl

Status in Mir:
  Won't Fix
Status in unity8 package in Ubuntu:
  Invalid

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

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

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

[Stephen M. Webb]

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

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

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

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

** 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 mir 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:
  Confirmed
Status in Mir:
  Confirmed
Status in Unity System Compositor:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

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 1598243] Re: Mir does not support multiple GPUs/cards simultaneously

[Stephen M. Webb]

** Changed in: mir
   Status: Triaged => In Progress

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

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

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

Title:
  Mir does not support multiple GPUs/cards simultaneously

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

Bug description:
  I have a Lenovo laptop which has a hybrid graphics chipset.
  When I have a monitor connected to the displayport, the displayport monitor 
is on /dev/dri/card0 while the LVDS (integrated lcd) is at /dev/dri/card1.

  Our kms implementation only supports a single device; that which is
  found first with a valid connection. We need to support multiple
  devices.

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

-- 
Mailing list: https://launchpad.net/~touch-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: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib

[Stephen M. Webb]

This should not have been set to Fix Committed on system images until
it's available on system images.

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

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

Title:
  unity-system-compositor crashed with SIGSEGV 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:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Invalid

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

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

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 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

[Stephen M. Webb]

This should not be set to Fix Committed on system images until it's
available on System Images.

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

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

Title:
  Mir sending key repeat events continually to nested shell after VT
  switch (causes Unity8 lockup for a while)

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt

  Expected:
  * session is locked, but working

  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all

  It seems it's "catching up" in some way, maybe with input, maybe
  frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

  Causes:
  The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
    Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.

  This applies to all currently pressed buttons. I.e. you can open an
  edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to
  switch to another VT. On return 'w' will be repeated indefinitely.

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

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

[Touch-packages] [Bug 1661163] Re: [regression] mirout crashes when connecting to unity8 or any nested server: [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed: (ind

[Stephen M. Webb]

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

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

Title:
  [regression] mirout crashes when connecting to unity8 or any nested
  server: [libprotobuf FATAL
  /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed:
  (index) < (current_size_):

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

Bug description:
  mirout crashes when connecting to unity8 or any nested server.

  $ mirout -- --desktop_file_hint=unity8
  Connected to server: 
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK 
failed: (index) < (current_size_):
  terminate called after throwing an instance of 
'google::protobuf::FatalException'
    what():  CHECK failed: (index) < (current_size_):
  Aborted (core dumped)

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

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

[Touch-packages] [Bug 1393578] Re: Subpixel order not included in Mir display information

[Stephen M. Webb]

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

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

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Just capturing something mentioned by Trevinho on IRC this morning.
  MirDisplayOutput does not include subpixel ordering, it could and
  should though. The information is exposed on the drm side
  (drmModeSubPixel). Marking as wishlist in absence of other
  information.

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

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

[Touch-packages] [Bug 1664760] Re: Mir server crashed with SIGSEGV in mir::compositor::TemporaryBuffer::size() called from mir::gl::tessellate_renderable_into_rectangle()

[Stephen M. Webb]

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

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

Title:
  Mir server crashed with SIGSEGV in
  mir::compositor::TemporaryBuffer::size() called from
  mir::gl::tessellate_renderable_into_rectangle()

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

Bug description:
  I run mir exempla:
  ./bin/mir_demo_server --launch-client ./bin/mir_demo_client_multistrea
  mir_demo_server crash when I move central animated object to right border and 
back.

  Cause of crash is to call size() function from invalid pointer in
  temporaty_buffers.cpp mc::TemporaryBuffer::size() - line: return
  buffer->size();

  I have checked why pointer is invalid:

  In function: 
  std::shared_ptr 
mc::MultiMonitorArbiter::compositor_acquire(compositor::CompositorID id) from 
multi_monitor_arbiter.cpp 

  auto& last_entry = onscreen_buffers.front();
  last_entry.use_count++;
  if (mode == mc::MultiMonitorMode::multi_monitor_sync)
  clean_onscreen_buffers(lk);

  last_entry reference pointing not existing object (object is not longer in 
onscreen_buffers) after calling clean_onscreen_buffers() function.
  clean_onscreen_buffers() function looks correct for me - but after calling 
it, data remains inconsistent.

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

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

[Touch-packages] [Bug 1673533] Re: Presentation chains should support various Vulkan presentation modes

[Stephen M. Webb]

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

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

Title:
  Presentation chains should support various Vulkan presentation modes

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

Bug description:
  Specifically, Vulkan modes:

  mir_present_mode_immediate, //same as VK_PRESENT_MODE_IMMEDIATE_KHR
  mir_present_mode_mailbox, //same as VK_PRESENT_MODE_MAILBOX_KHR
  mir_present_mode_fifo, //same as VK_PRESENT_MODE_FIFO_KHR
  mir_present_mode_fifo_relaxed, //same as VK_PRESENT_MODE_FIFO_RELAXED_KHR

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

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

[Touch-packages] [Bug 1673534] Re: Need an extension for GBM buffers to replace mir_buffer_get_buffer_package()

[Stephen M. Webb]

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

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

Title:
  Need an extension for GBM buffers to replace
  mir_buffer_get_buffer_package()

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

Bug description:
  We need for Mesa EGL

  typedef struct MirExtensionGbmBufferV2
  {
  MirConnectionAllocateBufferGbm allocate_buffer_gbm;
  MirConnectionAllocateBufferGbmSync allocate_buffer_gbm_sync;
  MirBufferIsGbmImportable is_gbm_importable;
  MirBufferGbmFd fd;
  MirBufferGbmStride stride;
  MirBufferGbmFormat format;
  MirBufferGbmFlags flags;
  MirBufferGbmAge age;
  } MirExtensionGbmBufferV2;

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

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

[Touch-packages] [Bug 1660017] Re: EDID does not change when hotplugging a monitor

[Stephen M. Webb]

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

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

Title:
  EDID does not change when hotplugging a monitor

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

Bug description:
  EDID does not change when hotplugging a monitor

  It appears Mir only gets the EDID right if the monitor was plugged in
  before the server started.

  If you change monitors, then Mir continues to report the old monitor's
  EDID. And similarly if the server started before the monitor was
  plugged in, Mir always reports no EDID for it.

  Other attributes like physical size appear to change correctly when
  hotplugging. Only the EDID is wrong.

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

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

[Touch-packages] [Bug 1667645] Re: If the only surface in a session cannot take focus the server crashes

[Stephen M. Webb]

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

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

Title:
  If the only surface in a session cannot take focus the server crashes

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in miral package in Ubuntu:
  Fix Released

Bug description:
  The problem is in ms::ApplicationSession::surface_after() it can
  dereference the surfaces.end() iterator.

  Original description:

  $ bin/miral-desktop
  ...
  terminate called after throwing an instance of 
'boost::exception_detail::clone_impl'
    what():  surface_after: surface is not a member of this session
  Aborted (core dumped)

  Using tiling WM doesn't exhibit this problem:

  $ bin/miral-desktop --window-manager tiling

  I would guess this is something to do with the recent addition of
  wallpaper. And possibly due to this test box being slow (14 years
  old), not due to Xenial/Mir 21.0.

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

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

[Touch-packages] [Bug 1669444] Re: [regression] OSK input shaping no longer works correctly

[Stephen M. Webb]

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

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

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

Title:
  [regression] OSK input shaping no longer works correctly

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-keyboard package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  1) Run the keyboard under Unity8 (silo 2481 can be helpful in making this 
more usable at present)
  2) Click in an input field
  3) Move the mouse over the keyboard
  4) Attempt to click on the app again

  Expected result:

  The mouse click should be passed through to the app

  Actual result:

  The click is swallowed by the keyboard surface instead. However, it is
  still possible to click on the app if this is done prior to the mouse
  entering the visible keyboard area.

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

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

[Touch-packages] [Bug 1666372] Re: Nested servers (Unity8) periodically stutter (half frame rate) with Mir 0.26.1

[Stephen M. Webb]

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

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

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

Title:
  Nested servers (Unity8) periodically stutter (half frame rate) with
  Mir 0.26.1

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

Bug description:
  Nested servers periodically stutter (half frame rate) with Mir 0.26.1

  On an old laptop, it's about half the time stuttering and half the
  time smooth.

  On a fast desktop, it only stutters occasionally like when a large
  blur is active.

  It seems the problem is Mir's predictive bypass optimization
  conflicting with the new client-side vsync optimization. Both are
  correct and desirable when used alone, but when used together they
  conflict, presumably because the former requires perfect vsync phase
  and the latter lacks correct vsync phase (which is still an exercise
  for later).

  A workaround to get more reliably smooth frame rates is to create a file:
/etc/lightdm/lightdm.conf.d/foo.conf
  with contents:

  [Seat:*]
  unity-compositor-command=/usr/sbin/unity-system-compositor --composite-delay=0

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

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

[Touch-packages] [Bug 1675364] Re: [regression] GTK and KDE apps fail to start under Unity8 (without gnome-session running)

[Stephen M. Webb]

@dinamic I think you're seeing a different problem with similar
symptoms, probably related to libSDL2 probing order.

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

Title:
  [regression] GTK and KDE apps fail to start under Unity8 (without
  gnome-session running)

Status in Canonical System Image:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in libertine package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Recently something has regressed and if i start konsole (using xmir)
  in unity8 all i get is the splash screen with a spinner forever.

  Looking at the ps output it seems that the konsole process has
  actually started.

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

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

[Touch-packages] [Bug 1675364] Re: [regression] GTK and KDE apps fail to start under Unity8 (without gnome-session running)

[Stephen M. Webb]

** Summary changed:

- [regression] GTK apps fail to start under Unity8 (without gnome-session 
running)
+ [regression] GTK and KDE apps fail to start under Unity8 (without 
gnome-session running)

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

Title:
  [regression] GTK and KDE apps fail to start under Unity8 (without
  gnome-session running)

Status in Canonical System Image:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in libertine package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Recently something has regressed and if i start konsole (using xmir)
  in unity8 all i get is the splash screen with a spinner forever.

  Looking at the ps output it seems that the konsole process has
  actually started.

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

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

[Stephen M. Webb]

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

-- 
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:
  Fix Released
Status in Mir:
  Invalid
Status in Mir 0.26 series:
  Invalid
Status in libsdl2 package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Fix Released

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 1675364] Re: [Regression] applications linked to GTK fail to start without gnome-session running

[Stephen M. Webb]

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

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

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

Title:
  [Regression] applications linked to GTK fail to start without gnome-
  session running

Status in Canonical System Image:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  New
Status in libertine package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Recently something has regressed and if i start konsole (using xmir)
  in unity8 all i get is the splash screen with a spinner forever.

  Looking at the ps output it seems that the konsole process has
  actually started.

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

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

[Touch-packages] [Bug 1675364] Re: [Regression] applications linked to GTK fail to start without gnome-session running

[Stephen M. Webb]

** Summary changed:

- [Regression] xmir applications fail to render
+ [Regression] applications linked to GTK fail to start without gnome-session 
running

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

** Changed in: libertine (Ubuntu)
   Status: New => Invalid

** 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 unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1675364

Title:
  [Regression] applications linked to GTK fail to start without gnome-
  session running

Status in Canonical System Image:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Recently something has regressed and if i start konsole (using xmir)
  in unity8 all i get is the splash screen with a spinner forever.

  Looking at the ps output it seems that the konsole process has
  actually started.

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

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

[Touch-packages] [Bug 1675364] Re: [Regression] xmir applications fail to render

[Stephen M. Webb]

I get the same behaviour from gedit.  It seems any application relying
on gnome-session running is going to hang.  I would point at some Gnome
library as being the casue of this.

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

Title:
  [Regression] xmir applications fail to render

Status in Canonical System Image:
  Triaged
Status in libertine package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Incomplete
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Recently something has regressed and if i start konsole (using xmir)
  in unity8 all i get is the splash screen with a spinner forever.

  Looking at the ps output it seems that the konsole process has
  actually started.

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

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

[Touch-packages] [Bug 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

[Stephen M. Webb]

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

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

Title:
  Mir sending key repeat events continually to nested shell after VT
  switch (causes Unity8 lockup for a while)

Status in Canonical System Image:
  Triaged
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt

  Expected:
  * session is locked, but working

  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all

  
  It seems it's "catching up" in some way, maybe with input, maybe frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

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

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

[Touch-packages] [Bug 1675364] Re: [Regression] xmir applications fail to render

[Stephen M. Webb]

It seems the difference between my two test machines is that one one I
had logged in to Unity 7 previously, and that left gnome-session-binary
running.  After a reboot to kill all systemd --user units, konsole now
hangs on both test machines.

It looks like this problem is in konsole, which requires gnome-session
to be running in order to function normally.

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

Title:
  [Regression] xmir applications fail to render

Status in Canonical System Image:
  Triaged
Status in libertine package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Incomplete
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Recently something has regressed and if i start konsole (using xmir)
  in unity8 all i get is the splash screen with a spinner forever.

  Looking at the ps output it seems that the konsole process has
  actually started.

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

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

[Touch-packages] [Bug 1675364] Re: [Regression] xmir applications fail to render

[Stephen M. Webb]

More information: the system on which this occurring shows konsole is
stuck waiting for a child bash process.

12414 ?Ss 0:00  \_ /usr/bin/python3 /usr/bin/libertine-launch 
konsole
12415 ?Sl 0:00  |   \_ Xmir -rootless -displayfd 3 -mir 
org.kde.konsole
12420 ?Sl 0:00  |   \_ pasted
12421 ?Sl 0:00  |   \_ konsole
12450 pts/4Ss+0:00  |   \_ /bin/bash

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

Title:
  [Regression] xmir applications fail to render

Status in Canonical System Image:
  Triaged
Status in libertine package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Incomplete
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Recently something has regressed and if i start konsole (using xmir)
  in unity8 all i get is the splash screen with a spinner forever.

  Looking at the ps output it seems that the konsole process has
  actually started.

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

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

[Touch-packages] [Bug 1675364] Re: [Regression] xmir applications fail to render

[Stephen M. Webb]

OK, I can repro this on one machine but not another (not sure what the
difference is yet).  For the record, journalctl is spammed with error
like the following when it does happen.

Mar 23 09:00:01 xt2-17 konsole[12421]: g_application_get_application_id: 
assertion 'G_IS_APPLICATION (application)' failed
Mar 23 09:00:01 xt2-17 konsole[12421]: g_variant_new_string: assertion 'string 
!= NULL' failed
Mar 23 09:00:01 xt2-17 konsole[12421]: g_application_get_application_id: 
assertion 'G_IS_APPLICATION (application)' failed
Mar 23 09:00:01 xt2-17 konsole[12421]: g_variant_new_string: assertion 'string 
!= NULL' failed
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-fallback-icon-theme
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-icon-sizes
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property 
gtk-alternative-button-order
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property 
gtk-show-input-method-menu
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-show-unicode-menu
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-timeout-initial
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-timeout-repeat
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-timeout-expand
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-color-scheme
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-touchscreen-mode
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-tooltip-timeout
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property 
gtk-tooltip-browse-timeout
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property 
gtk-tooltip-browse-mode-timeout
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-keynav-cursor-only
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-keynav-wrap-around
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property color-hash
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-file-chooser-backend
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-print-backends
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property 
gtk-print-preview-command
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-recent-files-limit
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-fontconfig-timestamp
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-sound-theme-name
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property 
gtk-enable-input-feedback-sounds
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-enable-event-sounds
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-enable-tooltips
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-toolbar-style
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-toolbar-icon-size
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-auto-mnemonics
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-visible-focus
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property 
gtk-entry-password-hint-timeout
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-menu-bar-popup-delay
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property 
gtk-scrolled-window-placement
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-can-change-accels
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-menu-popup-delay
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-menu-popdown-delay
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-color-palette
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-im-preedit-style
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-im-status-style
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property 
gtk-titlebar-middle-click
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-titlebar-right-click
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-enable-primary-paste
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-keynav-use-caret
Mar 23 09:00:01 xt2-17 konsole[12421]: GtkSettings Cursor Theme: Unsupported 
GDK backend
Mar 23 09:00:01 xt2-17 konsole[12421]: unknown property gtk-fallback-icon-theme

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

Title:
  [Regression] xmir applications fail to render

Status in Canonical System Image:
  Triaged
Status in libertine package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Incomplete
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Recently something has regressed and if i start konsole (using xmir)
  in unity8 all i get is the splash screen with a spinner forever.

  Looking at the ps output it seems that the konsole process has
  actually started.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1675364] Re: [Regression] xmir applications fail to render

[Stephen M. Webb]

Does the problem persist after a reboot?

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

Title:
  [Regression] xmir applications fail to render

Status in Canonical System Image:
  Triaged
Status in libertine package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Incomplete
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Recently something has regressed and if i start konsole (using xmir)
  in unity8 all i get is the splash screen with a spinner forever.

  Looking at the ps output it seems that the konsole process has
  actually started.

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

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

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

[Stephen M. Webb]

** 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/1671731

Title:
  [xmir] closing an app while a child window is opened leaves an Xmir
  process opened eating 100% CPU

Status in Canonical System Image:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity 8
  [xmir] closing an app while a child window is opened leaves an Xmir process 
opened eating 100% CPU

  launch solitaire (just click on the sol icon from launcher, it will just run 
on Xmir)
  open the about window from the menu (Help \ About)
  now close the main window 

  now top in a terminal (see attached)

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

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

[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Stephen M. Webb]

** 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/1669524

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

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

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

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

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

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

[Stephen M. Webb]

This is simple to reproduce.  The application has disappeared from the
screen but continues to run.

It looks like qtmir is closing the window (as requested) but no word
gets out to the actual process (ie. there is no session management).
I'm suspecting the Unity 8 lifecycle for desktops is not in place yet.

Here's a snippet from $HOME/.cahe/upstart/unity8.log.

[2017-03-20:19:34:52.953] qtmir.sessions: TaskController::onSessionStarting - 
sessionName=sol^M
[2017-03-20:19:34:52.954] qtmir.applications: 
Application["sol"]::setSession(session=qtmir::Session(0x4ecb3290))^M
[2017-03-20:19:34:53.457] 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/1.3/Icon.qml:115:5: 
QML Image: Cannot open: file:///home/stephenw/.face^M
[2017-03-20:19:34:57.992] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::MirSurface(type=normal,state=restored,size=(480,376),parentSurface=QObject(0x0))^M
[2017-03-20:19:34:58.015] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::registerView(268052752) after=1^M
[2017-03-20:19:34:58.032] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setKeymap("us")^M
[2017-03-20:19:34:58.467] toplevelwindowmodel: prependSurface appId=sol 
surface=qtmir::MirSurface(0x3c828f80), filling out placeholder. after: 
(index=0,appId=sol,surface=0x3c828f80,id=11),(index=1,appId=unity8-dash,surface=0x225db2f0,id=4)^M
[2017-03-20:19:34:58.468] toplevelwindowmodel: setFocusedWindow(0x0)^M
[2017-03-20:19:34:58.499] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(true)^M
[2017-03-20:19:34:58.514] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setReady()^M
[2017-03-20:19:34:58.520] qtmir.applications: 
Application["sol"]::setInternalState(state=Running)^M
[2017-03-20:19:34:58.537] toplevelwindowmodel: 
setFocusedWindow(Window[0x28c28060, id=11, 
MirSurface[0x3c828f80,"AisleRiot"]])^M
[2017-03-20:19:34:58.664] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::requestState(restored)^M
[2017-03-20:19:34:58.673] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:19.651] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::MirSurface(type=menu,state=restored,size=(172,66),parentSurface=qtmir::MirSurface(0x3c828f80))^M
[2017-03-20:19:35:19.801] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::registerView(745266864) after=1^M
[2017-03-20:19:35:20.080] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(false)^M
[2017-03-20:19:35:20.093] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setFocused(true)^M
[2017-03-20:19:35:20.098] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setReady()^M
[2017-03-20:19:35:20.123] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:20.126] toplevelwindowmodel: 
setFocusedWindow(Window[0x33e53dc0, id=12, 
MirSurface[0x28beec90,"AisleRiot"]])^M
[2017-03-20:19:35:20.128] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setKeymap("us")^M
[2017-03-20:19:35:23.549] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setLive(false)^M
[2017-03-20:19:35:23.552] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::unregisterView(745266864) after=0 live=false^M
[2017-03-20:19:35:23.553] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::updateExposure(false)^M
[2017-03-20:19:35:23.555] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(true)^M
[2017-03-20:19:35:23.622] toplevelwindowmodel: 
setFocusedWindow(Window[0x28c28060, id=11, MirSurface[0x3c828f80,"Klondike"]])^M
[2017-03-20:19:35:23.625] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::~MirSurface() viewCount=0^M
[2017-03-20:19:35:23.684] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::MirSurface(type=dialog,state=restored,size=(468,353),parentSurface=qtmir::MirSurface(0x3c828f80))^M
[2017-03-20:19:35:23.711] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::registerView(744596304) after=1^M
[2017-03-20:19:35:23.893] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(false)^M
[2017-03-20:19:35:23.904] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setFocused(true)^M
[2017-03-20:19:35:23.911] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setReady()^M
[2017-03-20:19:35:23.921] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:23.923] toplevelwindowmodel: 
setFocusedWindow(Window[0x2e53a140, id=13, MirSurface[0x35577d70,"About 
Aisleriot"]])^M
[2017-03-20:19:35:23.924] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setKeymap("us")^M
[2017-03-20:19:35:26.995] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::activate()^M
[2017-03-20:19:35:57.911] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::close()^M
[2017-03-20:19:36:00.995] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::onCloseTimedOut()^M
[2017-03-20:19:36:01.013] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setLive(false)^M
[2017-03-20:19:36:01.018] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::unregisterView(268052752) after=0 live=false^M
[2017-03-20:19:36:01.020] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::updateExposure(false)^M
[2017-03-20:19:36:01.025] qtmir.surfaces: 

[Touch-packages] [Bug 1668700] Re: Blank default scope in unity8-deb

[Stephen M. Webb]

How does unity-scope-mediascanner2 have anything to do with an empty
dash in Unity 8?  Adding it does not make the Dash have any content, so
it does not appear to be a relevant for for this bug.

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

Title:
  Blank default scope in unity8-deb

Status in Canonical System Image:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  unity8-deb on a fresh zesty installation in kvm

  Steps:

  1º Install zesty on kvm image
  2º Enter unity8-deb
  3º Check the default scope

  Expected result: some scopes should be marked by default as favorite,
  unity-scope-mediascanner2 wasn't installed along with zesty so some
  scopes are missing

  Current result: default scope is blank and only 3rd party scopes are
  available

  Add info: Bug #1668701

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

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

[Touch-packages] [Bug 1668429] Re: X apps fail to launch with failure to open display (no Xmir running or no access to it)

[Stephen M. Webb]

The log shows Firefox is being run natively under Unity 8 (no Xmir).
Firefox is known to not be built natively for Mir, so it's not a
surprise that it it not start.

Assuming that an Xmir instance should be launched just in case for any
and all applications run under Unity 8 was purposefully disabled to
prevent unwanted empty black windows from covering the screen.

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

Title:
  X apps fail to launch with failure to open display (no Xmir running or
  no access to it)

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in libertine package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Feb 27 iso build of zesty, clean u8 exploration

  repro:
  1) open app drawer, find the thunderbird app
  2) click on icon to launch
  3) window closes immediately

  not a very useful journal log
  http://pastebin.ubuntu.com/24080860/

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

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

[Touch-packages] [Bug 1654581] Re: unity8 crashed with SIGSEGV in Screen::makeCurrent()

[Stephen M. Webb]

** 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/1654581

Title:
  unity8 crashed with SIGSEGV in Screen::makeCurrent()

Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Using latest zesty, also reproduced in xenial+overlay.

  All I did is leave Unity 8 running for ~30 minutes and it crashed.
  This crash is reproducible with or without running Xmir. Unity 8 just
  suddenly restarts.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20161215-0ubuntu1
  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: Unity:Unity8
  Date: Fri Jan  6 09:37:16 2017
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1481818649
  InstallationDate: Installed on 2016-06-24 (196 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160623)
  ProcCmdline: unity8 --mode=full-shell
  ProcCwd: /home/lrp
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   Screen::makeCurrent() () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
   MirOpenGLContext::makeCurrent(QPlatformSurface*) () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
   QOpenGLContext::makeCurrent(QSurface*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: unity8 crashed with SIGSEGV in Screen::makeCurrent()
  UpgradeStatus: Upgraded to zesty on 2016-10-27 (70 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1646655] Re: unity8 provides no way or means to access information on USB stick

[Stephen M. Webb]

The Libertine problem is going to be a different problem tracked
separately in bug #1647006.  This particular problem is more likely
because the usual Gnome session daemons are not run in the non-Gnome
Unity 8 desktop session.

** Package changed: libertine (Ubuntu) => unity8-desktop-session
(Ubuntu)

** Changed in: unity8-desktop-session (Ubuntu)
   Status: Incomplete => New

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

Title:
  unity8 provides no way or means to access information on USB stick

Status in Canonical System Image:
  New
Status in content-hub package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in unity8-desktop-session package in Ubuntu:
  New

Bug description:
  Trying several different methods there is just no way that unity8 or
  any xapps in a container will allow access to information on a USB
  stick.

  entrical@ventrical-MS-7850:~$ inxi -Fxz
  System:Host: ventrical-MS-7850 Kernel: 4.8.0-27-generic x86_64 (64 bit 
gcc: 6.2.0)
     Console: tty 24
     Distro: Ubuntu Zesty Zapus (development branch)
  Machine:   Device: desktop Mobo: MSI model: B85-G41 PC Mate(MS-7850) v: 1.0
     UEFI: American Megatrends v: V2.8 date: 07/17/2014
  CPU:   Dual core Intel Pentium G3240 (-MCP-) cache: 3072 KB
     flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 12399
     clock speeds: max: 3100 MHz 1: 799 MHz 2: 877 MHz
  Graphics:  Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated 
Graphics Controller
     bus-ID: 00:02.0
     Display Server: X.org 1.18.4 drivers: (unloaded: fbdev,vesa)
     tty size: 68x26 Advanced Data: N/A out of X
  Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
     driver: snd_hda_intel bus-ID: 00:1b.0
     Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller
     driver: snd_hda_intel bus-ID: 00:03.0
     Sound: ALSA v: k4.8.0-27-generic
  Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
     driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
     IF: enp2s0 state: up speed: 100 Mbps duplex: full
     mac: 
  Drives:HDD Total Size: 160.3GB (30.4% used)
     ID-1: /dev/sda model: SAMSUNG_MZ7PA128 size: 128.0GB
     ID-2: USB /dev/sdb model: PDM09_32G_B9J2.0 size: 32.3GB

     ID-1: / size: 113G used: 23G (22%) fs: ext4 dev: /dev/sda2
     ID-2: swap-1 size: 4.15GB used: 0.01GB (0%) fs: swap dev: /dev/sda3
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
     Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 233 Uptime: 1:25 Memory: 1300.0/3813.7MB
     Init: systemd runlevel: 5 Gcc sys: 6.2.1
     Client: Shell (bash 4.4.51) inxi: 2.3.4
  ventrical@ventrical-MS-7850:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20161129-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:Unity8
  Date: Thu Dec  1 19:59:16 2016
  InstallationDate: Installed on 2016-10-06 (56 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161006)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Stephen M. Webb]

** Changed in: url-dispatcher (Ubuntu)
 Assignee: (unassigned) => Larry Price (larryprice)

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

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

Title:
  Complains about bad url on libertine scope urls

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

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

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

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

[Touch-packages] [Bug 1603453] Re: Network indicator does not run on Unity 8 desktop sessions, which also means the Ubuntu Store does not show any app pictures (just greyed out Ubuntu logos)

[Stephen M. Webb]

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

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

Title:
  Network indicator does not run on Unity 8 desktop sessions, which also
  means the Ubuntu Store does not show any app pictures (just greyed out
  Ubuntu logos)

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  The network indicator stopped running after a recent upgrade to the
  Unity 8 desktop session.

  The cause is that the session name changed and the upstart job is
  using the incorrect session name.

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

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

[Touch-packages] [Bug 1488413] Re: connected BT mouse should unblank screen (windowed mode)

[Stephen M. Webb]

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

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

Title:
  connected BT mouse should unblank screen (windowed mode)

Status in Canonical System Image:
  Fix Released
Status in Canonical Pocket Desktop:
  Fix Released
Status in Unity System Compositor:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Fix Released

Bug description:
  when switching into windowed mode && a BT mouse is connected && screen
  is blanked (from time out or pwr key press) the BT mouse motion should
  unblank the screen

  this may effect multiple projects so sort of shotgunning the effected
  project list

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

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

[Touch-packages] [Bug 1605327] Re: Opening terminal-app does not focus on password prompt

[Stephen M. Webb]

** 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/1605327

Title:
  Opening terminal-app does not focus on password prompt

Status in ubuntu-terminal-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in unity8-desktop-session package in Ubuntu:
  New

Bug description:
  When I open the terminal app, I get asked for my password. If I just
  start typing, the password gets written in the terminal bash and not
  in the correct popup prompt.

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

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

[Touch-packages] [Bug 1603453] Re: Network indicator does not run on Unity 8 desktop sessions, which also means the Ubuntu Store does not show any app pictures (just greyed out Ubuntu logos)

[Stephen M. Webb]

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

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

** Changed in: unity8-desktop-session (Ubuntu)
 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 indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1603453

Title:
  Network indicator does not run on Unity 8 desktop sessions, which also
  means the Ubuntu Store does not show any app pictures (just greyed out
  Ubuntu logos)

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress
Status in unity8-desktop-session package in Ubuntu:
  In Progress

Bug description:
  The network indicator stopped running after a recent upgrade to the
  Unity 8 desktop session.

  The cause is that the session name changed and the upstart job is
  using the incorrect session name.

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

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

[Touch-packages] [Bug 1337825] Re: Cannot connect to display

[Stephen M. Webb]

Ubuntu 14.10 is no longer supported.

** Changed in: unity8-desktop-session
   Status: New => Invalid

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

Title:
  Cannot connect to display

Status in unity8-desktop-session:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  In unity8 desktop-next session of today's build.

  (gdb) run
  Starting program: /usr/bin/webbrowser-app 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  QXcbConnection: Could not connect to display 

  Program received signal SIGABRT, Aborted.
  0x74d8f117 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  (gdb) 

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: webbrowser-app 0.23+14.10.20140630.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  Date: Fri Jul  4 13:53:36 2014
  InstallationDate: Installed on 2014-07-03 (0 days ago)
  InstallationMedia: Ubuntu-Desktop-Next 14.10 "Utopic Unicorn" - Alpha amd64 
(20140703)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-desktop-session/+bug/1337825/+subscriptions

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

[Touch-packages] [Bug 1376715] Re: No longer need to reference "Mir" in the session name since it is implied

[Stephen M. Webb]

** Changed in: unity8-desktop-session
Milestone: None => 1.0.12

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

Title:
  No longer need to reference "Mir" in the session name since it is
  implied

Status in unity8-desktop-session:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  In packaging unity8-lxc, Robert Ancell made a strong suggestion that
  any references to Mir in the session name should be removed since it
  is implied.  He made that change in lp:unity8-preview-lxc and we
  should do that for this project to be consistent.

  Instead of it saying "Unity8-Mir", it should say "Unity 8".

  Also related, the unity8-desktop-session-mir package should be named
  unity8-desktop-session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-desktop-session/+bug/1376715/+subscriptions

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

[Touch-packages] [Bug 1604433] Re: Listening audio does not work on the desktop

[Stephen M. Webb]

I also get no sound from the browser-app or the Music app, but no
problem playing from the Music scope.

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

Title:
  Listening audio does not work on the desktop

Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Incomplete

Bug description:
  Playing any audio (eg. youtube video) does not produce any sound on
  the desktop

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

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

[Touch-packages] [Bug 1604374] Re: Lock screen/greeter shown when switching user sessions

[Stephen M. Webb]

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

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

Title:
  Lock screen/greeter shown when switching user sessions

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

Bug description:
  I have two users one set to use Unity7 and one using Unity8.

  Switching from 7 to 8 I login at the normal prompt then several
  seconds later the greeter is shown and need to login again.

  Switching from 8 to 7 is similar, login then get the lock screen. In
  this case the screen is black after the first login until you provide
  some mouse input.

  My settings are set to lock the screen on suspend or when screen goes
  off

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

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

[Touch-packages] [Bug 1603186] Re: Apps scope not shown in the dash (but is installed)

[Stephen M. Webb]

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

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

Title:
  Apps scope not shown in the dash (but is installed)

Status in Canonical System Image:
  In Progress
Status in unity-scope-click package in Ubuntu:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When opening the dash I just see Music, XApps and Videos scope. But
  there is no Apps scope.

  The only way to reach the Apps scope is opening the menu from the
  bottom edge and selecting it from there.

  So the scope is there and installed, the problem is that's not among
  the enabled (starred) scopes (and there's no way to enable it).

  
  This bug is not a duplicate of #1579551:
   - I am able to launch apps, I'm just missing the Apps scope
   - unity-scope-click is already installed, but the problem is still there

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

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

[Touch-packages] [Bug 1603070] Re: [dash] ubuntu store doesn't show app preview images

[Stephen M. Webb]

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

** This bug has been marked a duplicate of bug 1603453
   Indicator does not run on Unity 8 desktop sessions

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

Title:
  [dash] ubuntu store doesn't show app preview images

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.10 desktop
  [dash] ubuntu store doesn't show app preview images 

  please see attached image

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

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

[Touch-packages] [Bug 1603183] Re: Right button doesn't trigger contextual menus

[Stephen M. Webb]

I do not get anything when I right-click in the webbrowser-app.

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

Title:
  Right button doesn't trigger contextual menus

Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  I'm used to have the contextual menus with the right button on the
  desktop, while on unity8 they still appear pressing and holding (which
  is fine for touch based devices). When I use the webbrowser-app I
  can't even open links in different pages.

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

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

[Touch-packages] [Bug 1603190] Re: Ubuntu Store does not show any app pictures (just greyed out Ubuntu logos)

[Stephen M. Webb]

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

** This bug is no longer a duplicate of bug 1603070
   [dash] ubuntu store doesn't show app preview images 
** This bug has been marked a duplicate of bug 1603453
   Indicator does not run on Unity 8 desktop sessions

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

Title:
  Ubuntu Store does not show any app pictures (just greyed out Ubuntu
  logos)

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

Bug description:
  When exploring the ubuntu store I cannot see the icons of the apps nor
  the pictures when you enter in the app description. Every picture is
  replaced by the Ubuntu logo

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

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

[Touch-packages] [Bug 1603453] Re: Indicator does not run on Unity 8 desktop sessions

[Stephen M. Webb]

** Changed in: indicator-network (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Indicator does not run on Unity 8 desktop sessions

Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  The network indicator stopped running after a recent upgrade to the
  Unity 8 desktop session.

  The cause is that the session name changed and the upstart job is
  using the incorrect session name.

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

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

[Touch-packages] [Bug 1603453] [NEW] Indicator does not run on Unity 8 desktop sessions

[Stephen M. Webb]

Public bug reported:

The network indicator stopped running after a recent upgrade to the
Unity 8 desktop session.

The cause is that the session name changed and the upstart job is using
the incorrect session name.

** Affects: indicator-network (Ubuntu)
 Importance: Medium
 Assignee: Stephen M. Webb (bregma)
 Status: Triaged

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

Title:
  Indicator does not run on Unity 8 desktop sessions

Status in indicator-network package in Ubuntu:
  Triaged

Bug description:
  The network indicator stopped running after a recent upgrade to the
  Unity 8 desktop session.

  The cause is that the session name changed and the upstart job is
  using the incorrect session name.

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

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

[Touch-packages] [Bug 1603183] Re: Right button doesn't trigger contextual menus

[Stephen M. Webb]

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

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

** Changed in: unity8-desktop-session (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/1603183

Title:
  Right button doesn't trigger contextual menus

Status in unity8 package in Ubuntu:
  New
Status in unity8-desktop-session package in Ubuntu:
  Triaged

Bug description:
  I'm used to have the contextual menus with the right button on the
  desktop, while on unity8 they still appear pressing and holding (which
  is fine for touch based devices). When I use the webbrowser-app I
  can't even open links in different pages.

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

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

[Touch-packages] [Bug 1289072] Re: Nested servers lack cursor support

[Stephen M. Webb]

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

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

Title:
  Nested servers lack cursor support

Status in Light Display Manager:
  Fix Released
Status in Mir:
  Fix Released
Status in unity-mir:
  Invalid
Status in Unity System Compositor:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Nested servers lack functional cursor support.  The code just returns
  a null pointer.

  One of the symptoms of this is that it is not possible to use a mouse
  or trackpad when running Unity8 as the desktop shell.

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

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

[Touch-packages] [Bug 1596069] Re: recent LightDM changes stop XApps from launching in Unity 8

[Stephen M. Webb]

Bug fixed by unrelated change http://bazaar.launchpad.net/~unity-
team/unity8/trunk/revision/2502

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

** Changed in: unity8-desktop-session
   Status: In Progress => Fix Released

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

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

Title:
  recent LightDM changes stop XApps from launching in Unity 8

Status in unity8-desktop-session:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Changes made to LightDM to fix bug #1583624 cause Unity 8
  configuration to fail in its upstart job, which causes the symptom
  that XApps no longer launch.  It may cause other problems as well.

  The root of the problem is that the variable MIR_SOCKET is no longer
  present in the enviroment when Unity 8 is started.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-desktop-session/+bug/1596069/+subscriptions

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

[Touch-packages] [Bug 1596069] Re: recent LightDM changes stop XApps from launching in Unity 8

[Stephen M. Webb]

** Also affects: unity8-desktop-session
   Importance: Undecided
   Status: New

** Changed in: unity8-desktop-session
   Status: New => In Progress

** Changed in: unity8-desktop-session
   Importance: Undecided => Critical

** Changed in: unity8-desktop-session
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

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

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

** Changed in: unity8-desktop-session (Ubuntu)
 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/1596069

Title:
  recent LightDM changes stop XApps from launching in Unity 8

Status in unity8-desktop-session:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8-desktop-session package in Ubuntu:
  In Progress

Bug description:
  Changes made to LightDM to fix bug #1583624 cause Unity 8
  configuration to fail in its upstart job, which causes the symptom
  that XApps no longer launch.  It may cause other problems as well.

  The root of the problem is that the variable MIR_SOCKET is no longer
  present in the enviroment when Unity 8 is started.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-desktop-session/+bug/1596069/+subscriptions

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

[Touch-packages] [Bug 1596069] [NEW] recent LightDM changes stop XApps from launching in Unity 8

[Stephen M. Webb]

Public bug reported:

Changes made to LightDM to fix bug #1583624 cause Unity 8 configuration
to fail in its upstart job, which causes the symptom that XApps no
longer launch.  It may cause other problems as well.

The root of the problem is that the variable MIR_SOCKET is no longer
present in the enviroment when Unity 8 is started.

** Affects: unity8 (Ubuntu)
 Importance: High
 Assignee: Stephen M. Webb (bregma)
 Status: In Progress

** Description changed:

- Changes made to LightDM to fix #1583624 cause Unity 8 configuration to
- fail in its upstart job, which causes the symptom that XApps no longer
- launch.  It may cause other problems as well.
+ Changes made to LightDM to fix bug #1583624 cause Unity 8 configuration
+ to fail in its upstart job, which causes the symptom that XApps no
+ longer launch.  It may cause other problems as well.
  
  The root of the problem is that the variable MIR_SOCKET is no longer
  present in the enviroment when Unity 8 is started.

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

Title:
  recent LightDM changes stop XApps from launching in Unity 8

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Changes made to LightDM to fix bug #1583624 cause Unity 8
  configuration to fail in its upstart job, which causes the symptom
  that XApps no longer launch.  It may cause other problems as well.

  The root of the problem is that the variable MIR_SOCKET is no longer
  present in the enviroment when Unity 8 is started.

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

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

[Touch-packages] [Bug 1592691] Re: mir fails to build in xenial

[Stephen M. Webb]

** Changed in: mir/0.21
Milestone: None => 0.21.1

** Changed in: mir/0.21
   Status: Confirmed => Triaged

** Changed in: mir/0.21
   Importance: High => Low

** Changed in: mir
   Importance: High => Low

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

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

Title:
  mir fails to build in xenial

Status in Mir:
  Invalid
Status in Mir 0.21 series:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  seen in a xenial test rebuild using ppa:ubuntu-toolchain-r/ppa
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-xenial.html

  In file included from 
/«BUILDDIR»/mir-0.21.0+16.04.20160330/tests/unit-tests/input/evdev/test_libinput_device.cpp:31:0:
  /«BUILDDIR»/mir-0.21.0+16.04.20160330/include/test/mir/test/event_matchers.h: 
In instantiation of ‘bool mir::test::TouchContactMatcherP4::gmock_Impl::MatchAndExplain(arg_type, 
testing::MatchResultListener*) const [with arg_type = MirEvent&; slot_type = 
int; action_type = MirTouchAction; x_type = float; y_type = float]’:
  
/«BUILDDIR»/mir-0.21.0+16.04.20160330/tests/unit-tests/input/evdev/test_libinput_device.cpp:752:1:
   required from here
  
/«BUILDDIR»/mir-0.21.0+16.04.20160330/include/test/mir/test/event_matchers.h:340:17:
 error: call of overloaded ‘abs(float)’ is ambiguous
   if (std::abs(mir_touch_event_axis_value(tev, slot, mir_touch_axis_x) - 
x) > 0.5f)
   ^
  In file included from /usr/include/c++/5/cstdlib:72:0,
   from /usr/include/c++/5/bits/stl_algo.h:59,
   from /usr/include/c++/5/algorithm:62,
   from /usr/include/gmock/gmock-actions.h:43,
   from /usr/include/gmock/gmock.h:58,
   from 
/«BUILDDIR»/mir-0.21.0+16.04.20160330/tests/unit-tests/precompiled.hpp:22:
  /usr/include/stdlib.h:774:12: note: candidate: int abs(int)
   extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
  ^
  In file included from /usr/include/c++/5/bits/stl_algo.h:59:0,
   from /usr/include/c++/5/algorithm:62,
   from /usr/include/gmock/gmock-actions.h:43,
   from /usr/include/gmock/gmock.h:58,
   from 
/«BUILDDIR»/mir-0.21.0+16.04.20160330/tests/unit-tests/precompiled.hpp:22:
  /usr/include/c++/5/cstdlib:166:3: note: candidate: long int std::abs(long int)
 abs(long __i) { return __builtin_labs(__i); }
 ^
  /usr/include/c++/5/cstdlib:174:3: note: candidate: long long int 
std::abs(long long int)
 abs(long long __x) { return __builtin_llabs (__x); }
 ^
  In file included from 
/«BUILDDIR»/mir-0.21.0+16.04.20160330/tests/unit-tests/input/evdev/test_libinput_device.cpp:31:0:
  
/«BUILDDIR»/mir-0.21.0+16.04.20160330/include/test/mir/test/event_matchers.h:342:17:
 error: call of overloaded ‘abs(float)’ is ambiguous
   if (std::abs(mir_touch_event_axis_value(tev, slot, mir_touch_axis_y) - 
y) > 0.5f)
   ^
  In file included from /usr/include/c++/5/cstdlib:72:0,
   from /usr/include/c++/5/bits/stl_algo.h:59,
   from /usr/include/c++/5/algorithm:62,
   from /usr/include/gmock/gmock-actions.h:43,
   from /usr/include/gmock/gmock.h:58,
   from 
/«BUILDDIR»/mir-0.21.0+16.04.20160330/tests/unit-tests/precompiled.hpp:22:
  /usr/include/stdlib.h:774:12: note: candidate: int abs(int)
   extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
  ^
  In file included from /usr/include/c++/5/bits/stl_algo.h:59:0,
   from /usr/include/c++/5/algorithm:62,
   from /usr/include/gmock/gmock-actions.h:43,
   from /usr/include/gmock/gmock.h:58,
   from 
/«BUILDDIR»/mir-0.21.0+16.04.20160330/tests/unit-tests/precompiled.hpp:22:
  /usr/include/c++/5/cstdlib:166:3: note: candidate: long int std::abs(long int)
 abs(long __i) { return __builtin_labs(__i); }
 ^
  /usr/include/c++/5/cstdlib:174:3: note: candidate: long long int 
std::abs(long long int)
 abs(long long __x) { return __builtin_llabs (__x); }
 ^
  In file included from 
/«BUILDDIR»/mir-0.21.0+16.04.20160330/tests/unit-tests/input/evdev/test_libinput_device.cpp:31:0:
  /«BUILDDIR»/mir-0.21.0+16.04.20160330/include/test/mir/test/event_matchers.h: 
In instantiation of ‘bool mir::test::TouchEventMatcherP2::gmock_Impl::MatchAndExplain(arg_type, 
testing::MatchResultListener*) const [with arg_type = MirEvent&; x_type = 
float; y_type = float]’:
  
/«BUILDDIR»/mir-0.21.0+16.04.20160330/tests/unit-tests/input/evdev/test_libinput_device.cpp:752:1:
   required from here
  

[Touch-packages] [Bug 1572888] Re: XMir applications have wrong scaling

[Stephen M. Webb]

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

Title:
  XMir applications have wrong scaling

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

Bug description:
  On my BQ Aquaris M10, when I launch a Xapp (ex: Firefox or
  LibreOffice), scaling is not good. I have to zoom around 150% to enjoy
  a good scaling for my screen size. If not, text is a bit too small to
  be read well.

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

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

[Touch-packages] [Bug 1591356] Re: keyboard autorepeat in libertine apps does not work

[Stephen M. Webb]

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

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

** Changed in: libertine (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/1591356

Title:
  keyboard autorepeat in libertine apps does not work

Status in libertine package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

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

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

[Touch-packages] [Bug 1337613] Re: ubuntu-location-service crash

[Stephen M. Webb]

** Changed in: unity8-desktop-session (Ubuntu)
   Status: New => Invalid

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

Title:
  ubuntu-location-service crash

Status in location-service package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Invalid

Bug description:
  Hallo
  Testing unity8-MIR image ubuntu-desktop-next in dmesg there was this repeated 
a bunch of times:

  [   13.446215] init: ubuntu-location-service main process (682) killed by 
SEGV signal
  [   13.446228] init: ubuntu-location-service main process ended, respawning
  [   13.454540] init: ubuntu-location-service main process (817) killed by 
SEGV signal
  [   13.454551] init: ubuntu-location-service main process ended, respawning

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-location-service-bin 1.0.0+14.10.20140630-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: amd64
  Date: Fri Jul  4 00:44:15 2014
  InstallationDate: Installed on 2014-07-03 (0 days ago)
  InstallationMedia: Ubuntu-Desktop-Next 14.10 "Utopic Unicorn" - Alpha amd64 
(20140703)
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1541787] Re: Printing from legacy apps on the pocket desktop

[Stephen M. Webb]

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

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

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

Title:
  Printing from legacy apps on the pocket desktop

Status in avahi package in Ubuntu:
  New
Status in cups-filters package in Ubuntu:
  New
Status in libertine package in Ubuntu:
  Triaged

Bug description:
  I have worked out a concept on how to introduce printing support to
  the phone (tablet, mobile devices) keeping the resource consumption
  low, starting the needed daemons on-demand.

  The daemons needed for printing are avahi-daemon, cups-browsed, and
  CUPS. avahi-daemon discovers printers on the network, cups-browsed
  creates local CUPS queues pointing to the remote printers and CUPS
  does the actual printing.

  CUPS is started socket-activated by Upstart and stops by itself when
  it gets idle. So CUPS for example starts when cups-browsed tries to
  create a print queue or an app sends a job to be printed. avahi-daemon
  and cups-browsed will be started by the print dialog of Ubuntu Touch,
  right before the dialog opens, making available printers on the
  network appear within seconds in the dialog. When the dialog closes,
  either because the user sent the print job or because he has
  cancelled, it kills avahi-daemon. cups-browsed and CUPS terminate
  automatically then as soon as the user's job is printed (plus a
  timeout).

  If you connect a monitor to the pone and so fire up the pocket desktop
  you are able to run legacy apps (apps designed for a conventional PC)
  which have print functionalities but their print dialogs do not start
  and kill daemons, they assume that all daemons and print queues are
  readily available. CUPS would be fired up automatically by any app's
  print functionality due to the socket activation, but then we would
  not have print queues on our phone as avahi-daemon and cups-browsed
  are not running.

  So what has to be made sure is that cups-browsed and avahi-daemon are
  running if at least one of

   - the native print dialog of Ubuntu Touch
   - any legacy app

  are running. So when one of these get started the two daemons need to
  get started and if all of these terminate avahi-daemon needs to get
  killed, so that the rest of the printing stack shuts down when all
  jobs get done.

  We assume that ubuntu-app-launch is the place where this should be
  done, please re-assign if this is not correct. I also add cups-filters
  (source of cups-browsed) and avahi-daemon tasks for the case that
  perhaps here something needs to get done, too.

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

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

[Touch-packages] [Bug 1543351] Re: Add on-screen-keyboard support for Xmir/Libertine apps

[Stephen M. Webb]

** Changed in: libertine
   Status: New => Triaged

** Changed in: libertine
   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/1543351

Title:
  Add on-screen-keyboard support for Xmir/Libertine apps

Status in Canonical Pocket Desktop:
  New
Status in Libertine:
  Triaged
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  From perspective of product management - this is currently not a
  requirement, just want to capture it for future

  we currently can't interact with puritine apps relying on the OSK

  to add this feature in where text-box selection on an xapp results in
  triggering the osk, in unity8 would be a very large/complicated
  effort. However, with a manual capability to trigger the OSK this
  could be achieved.

  For design team
  one idea was to add a show/hide button for the OSK.
  realizing this may be undesirable to add another indicator item - a follow-on 
idea might be to add an alpha button in the corner of the xmir-root window (the 
window that holds any xapp at the moment)
  this way the button presence would only be limited to the Xapp interaction.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1543351/+subscriptions

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

[Touch-packages] [Bug 1543351] Re: Add on-screen-keyboard support for Xmir/Libertine apps

[Stephen M. Webb]

** Summary changed:

- Add on-screen-keyboard support for Xmir/Puritine apps
+ Add on-screen-keyboard support for Xmir/Libertine apps

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

** Changed in: libertine
 Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)

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

Title:
  Add on-screen-keyboard support for Xmir/Libertine apps

Status in Canonical Pocket Desktop:
  New
Status in Libertine:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  From perspective of product management - this is currently not a
  requirement, just want to capture it for future

  we currently can't interact with puritine apps relying on the OSK

  to add this feature in where text-box selection on an xapp results in
  triggering the osk, in unity8 would be a very large/complicated
  effort. However, with a manual capability to trigger the OSK this
  could be achieved.

  For design team
  one idea was to add a show/hide button for the OSK.
  realizing this may be undesirable to add another indicator item - a follow-on 
idea might be to add an alpha button in the corner of the xmir-root window (the 
window that holds any xapp at the moment)
  this way the button presence would only be limited to the Xapp interaction.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1543351/+subscriptions

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Stephen M. Webb]

** Changed in: mir
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Stephen M. Webb]

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

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

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

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1572888] Re: XMir applications have wrong scaling

[Stephen M. Webb]

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

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

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

Title:
  XMir applications have wrong scaling

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

Bug description:
  On my BQ Aquaris M10, when I launch a Xapp (ex: Firefox or
  LibreOffice), scaling is not good. I have to zoom around 150% to enjoy
  a good scaling for my screen size. If not, text is a bit too small to
  be read well.

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

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

[Touch-packages] [Bug 1535058] Re: applications close instantly when launched from the launcher or dash

[Stephen M. Webb]

If you think the problem is related to cgroups (there really is no
application log in ~/.cache/upstart and no clues in ~/.xession-errors),
try watching the systemd output (use 'journalctl -f | tee ~/jc.log') for
messages related to cgroups or alternatively, apparmor.

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

Title:
  applications close instantly when launched from the launcher or dash

Status in cgmanager package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  xenial
  applications close instantly when launched from the launcher or dash
  but... if i launch the apps from a VT (for ex firefox using Xmir or gedit 
native --), the app loads ok.

  what close instantly means.. it opens the window and then it closes
  instantly in ~0.3s

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

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

[Touch-packages] [Bug 1538659] Re: Unity8 on Vivid doesn't boot, due to old unity8-desktop-session-mir in Vivid archive

[Stephen M. Webb]

Ubuntu 15.04 ("Vivid Vervet") is not longer in support and reached end
of life on February 4, 2016.

** Changed in: unity8-desktop-session (Ubuntu)
   Status: New => Invalid

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

Title:
  Unity8 on Vivid doesn't boot, due to old unity8-desktop-session-mir in
  Vivid archive

Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid

Bug description:
  On a fresh vivid setup, installing unity8-desktop-session-mir doesn't pull in
  the platform and client packages required to be able to run unity8

  I had to install
  mir-client-platform-mesa3
  mir-platform-graphics-mesa-km7
  mir-platform-input-evdev4

  PS I have the Overlay PPA installed,
  unity8-desktop-session-mir is version 1.0.12+15.04.20150309-0ubuntu1 (which 
is really old, and could be the cause of these issues!)

  
  UPDATE: turns out it's because vivid has an old version of the package (March 
2015) and unity8-desktop-session-mir added a dependency to Mir graphics drivers 
in June 2015 
http://bazaar.launchpad.net/~unity8-desktop-session-team/unity8-desktop-session/trunk/revision/79.2.1

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

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

[Touch-packages] [Bug 1068960] Re: crash when touch grab fails

[Stephen M. Webb]

Ran the attached test program and verified it was grabbing the touches,
but Compiz did not crash on startup or use.  I'm closing this bug on the
assumption that the fix for #1080386 was also the solution for this bug.

** Changed in: geis (Ubuntu)
   Status: Triaged => Invalid

** Changed in: geis (Ubuntu)
 Assignee: Stephen M. Webb (bregma) => (unassigned)

** Changed in: geis
Milestone: 2.2.18 => None

** Changed in: geis
   Status: Triaged => Invalid

** Changed in: geis
Milestone: None => 2.2.18

** Changed in: geis
 Assignee: Stephen M. Webb (bregma) => (unassigned)

** Changed in: geis
Milestone: 2.2.18 => None

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

Title:
  crash when touch grab fails

Status in Geis:
  Invalid
Status in geis package in Ubuntu:
  Invalid

Bug description:
  If another client already has a touch grab on the root window, libgeis
  crashes, taking unity down in the process.

  To reproduce, compile the attached program, and then add it to the
  startup applications.  The command should be '/path/to/touchgrab 2 0
  reject'.  Then log out and log back into unity, which results in the
  crash.  Tested on quantal.

  This might be the underlying cause of bug #1038455.

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

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

[Touch-packages] [Bug 1543133] Re: Desktop: Black screen after logging into unity8 session

[Stephen M. Webb]

Possibly https://bugs.launchpad.net/mir/+bug/1526658?

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

Title:
  Desktop: Black screen after logging into unity8 session

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

Bug description:
  On xenial amd64 desktop after logging into the unity8 session, I'm
  greeted by a black screen, no mouse cursor, nothing. Only Magic SysRq
  gets me out of the session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  8 15:07:17 2016
  InstallationDate: Installed on 2015-04-30 (283 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity8
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1542906] [NEW] unity::scopes::testing::TypedScopeFixture<> usage always fails

[Stephen M. Webb]

Public bug reported:

Following the official documentation at the Ubuntu developer gateway
https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04.1 I tried to
create a scope fixture to use in my test cases using the
unity::scopes::testing::TypedScopeFixture<> template to wrap my Scope
class.

The unit tests always fail at runtime with an error similar to the following.
  [ RUN  ] ScopeFixture.surfacing_query
  /usr/include/unity-scopes-1.0/unity/scopes/testing/TypedScopeFixture.h:90: 
Failure
  Expected: scope->start(ScopeTraits::name()) doesn't throw an exception.

Turns out the problem is that the TypedScopeFixture template class does
not call the required initialization functions in its constructor.  It's
not possible to work around this by driving from TypedScopeFixture
because the required initialization functions (for example,
TypedScopeFixtureHelper::set_scope_directory()) are private static
member functions in another class.  The only workaround is to include a
modified copy of TypedScopeFixture.h in my own project.

** Affects: unity-scopes-api (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "possible change that fixes the problem"
   https://bugs.launchpad.net/bugs/1542906/+attachment/4566287/+files/api.diff

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

Title:
  unity::scopes::testing::TypedScopeFixture<> usage always fails

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

Bug description:
  Following the official documentation at the Ubuntu developer gateway
  https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04.1 I tried to
  create a scope fixture to use in my test cases using the
  unity::scopes::testing::TypedScopeFixture<> template to wrap my Scope
  class.

  The unit tests always fail at runtime with an error similar to the following.
[ RUN  ] ScopeFixture.surfacing_query
/usr/include/unity-scopes-1.0/unity/scopes/testing/TypedScopeFixture.h:90: 
Failure
Expected: scope->start(ScopeTraits::name()) doesn't throw an 
exception.

  Turns out the problem is that the TypedScopeFixture template class
  does not call the required initialization functions in its
  constructor.  It's not possible to work around this by driving from
  TypedScopeFixture because the required initialization functions (for
  example, TypedScopeFixtureHelper::set_scope_directory()) are private
  static member functions in another class.  The only workaround is to
  include a modified copy of TypedScopeFixture.h in my own project.

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

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

[Touch-packages] [Bug 1530807] Re: Bluetooth cannot be activated on Nexus 7

[Stephen M. Webb]

Definitely happens on mako using the -pd image (r127) which renders it
completely useless as a -pd image.

** Changed in: canonical-pocket-desktop
   Status: New => Confirmed

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

Title:
  Bluetooth cannot be activated on Nexus 7

Status in Canonical System Image:
  Confirmed
Status in canonical-pocket-desktop:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Using RC proposed 04/01/2016 bluetooth cannot be enabled.

  Tested on a nexus 7.

  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list

  Experienced behavior: 
  Bluetooth slider is moved to on
  Activity spinners appear 
  Bluetooth slider moves to off.

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

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

[Touch-packages] [Bug 1533758] Re: applications are not loading

[Stephen M. Webb]

Is this on the desktop?  What hardware?

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

Title:
  applications are not loading

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New
Status in unity8-desktop-session package in Ubuntu:
  New

Bug description:
  applications do not load and get stuck on the boot screen with the
  symbol of the applications and the wheel of 'application that runs
  without charge.all applications initially available from the sidebar
  and the app scopes are blocked The web browser , the settings
  application and scope.it also makes the operating system unusable
  except for the notification bar. it makes it unusable ubuntu

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

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

[Touch-packages] [Bug 1528384] Re: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started()

[Stephen M. Webb]

** Changed in: mir
Milestone: 0.19.0 => 0.20.0

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

Title:
  unity-system-compositor crashed with std::runtime_error in
  mir::compositor::CompositingFunctor::wait_until_started()

Status in Canonical System Image:
  Confirmed
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:
  Top crash over past week (ww02) on errors.u.c for rc-proposed
  channels.

  Started with u-s-c 0.2.0+15.04.20151216.1-0ubuntu1

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

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

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

[Touch-packages] [Bug 1488413] Re: connected BT mouse should unblank screen (windowed mode)

[Stephen M. Webb]

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

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

Title:
  connected BT mouse should unblank screen (windowed mode)

Status in Canonical System Image:
  Confirmed
Status in canonical-pocket-desktop:
  New
Status in Mir:
  Incomplete
Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  when switching into windowed mode && a BT mouse is connected && screen
  is blanked (from time out or pwr key press) the BT mouse motion should
  unblank the screen

  this may effect multiple projects so sort of shotgunning the effected
  project list

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

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