[Touch-packages] [Bug 1535058] Re: applications close instantly when launched from the launcher or dash

[Gerry Boland]

@bozubuntu 
hey, thanks for the report, but this bug is for the discontinued unity8 
desktop. I suggest you log a bug against ubuntu-desktop with as much 
information as you can supply:
https://bugs.launchpad.net/~ubuntu-desktop

exo-open is new to me, have you tried xdg-open?

-- 
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 Canonical System Image:
  Fix Released
Status in cgmanager package in Ubuntu:
  Incomplete
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session 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

  ---

  This has been traced to two causes:
  pam was not installed, it is now a dependency of ubuntu-app-launch or can be 
installed directly
  $ sudo apt-get install libpam-cgfs

  and cgmanager is not enabled by default on systems that were upgraded
  and not clean installs. To enable it

  $ sudo systemctl enable cgmanager

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+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 1708326] Re: RM: obsolete product

[Gerry Boland]

Reopening as Mir has sufficiently good Wayland support to support Qt5.
qtubuntu can be removed from the archive

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

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

Title:
  RM: obsolete product

Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  qtubuntu was a component of Ubuntu Phone which is no longer developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:qtubuntu
  No reverse dependencies found

  $ reverse-depends -b src:qtubuntu
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1661295] Re: [vmware] mir 0.26 failing with nested server in protobuf when bringing up NestedDisplay [CHECK failed: (index) >= (0)]

[Gerry Boland]

Ok, VMWare is setting the current crtc mode at a generic 800x600, which isn't 
in the list of modes for the connected display. Only approach I see is to 
compare the mode name with "preferred", for which I see prior art:
https://github.com/wayland-project/weston/blob/master/compositor/main.c#L1068

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

Title:
  [vmware] mir 0.26 failing with nested server in protobuf when bringing
  up NestedDisplay [CHECK failed: (index) >= (0)]

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

Bug description:
  Setup:
  1. VMWare 12, with the following line added to ~/.vmware/preferences:
    mks.gl.allowBlacklistedDrivers = "TRUE"
  2. Created a VM with Xenial + Overlay PPA
  3. Installed unity8-desktop-session-mir, rebooted
  4. Tried to log in to a Unity8 session

  Problem: Unity8 fails to start, but is exiting cleanly as opposed to
  crashing. The following is all that is printed of the log:

  [2017-02-02:07:18:21.137] qtmir.screens: ScreensModel::ScreensModel
  [2017-02-02 07:18:21.143261] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:18:21.143413] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:18:21.144063] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  [2017-02-02:07:18:21.165] CHECK failed: (index) >= (0):
  initctl: No such variable: UNITY_MIR_SOCKET

  USC is coming up correctly however.

  If I try to launch miral-shell manually, I get similar error:

  MIR_SOCKET=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_PROMPT_FILE=1 
MIR_SERVER_HOST_SOCKET=/run/mir_socket 
MIR_SERVER_FILE=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_NAME=session-0 
miral-shell
  [2017-02-02 07:55:56.686669] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:55:56.687395] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:55:56.689036] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  ERROR: Dynamic exception type: google::protobuf::FatalException
  std::exception::what: CHECK failed: (index) >= (0):

  I tried to grab a backtrace at the location of the last call to
  /usr/include/google/protobuf/repeated_field.h:885 which might print
  the error:

  http://pastebin.ubuntu.com/23911595/

  Thread 4 "MirServerThread" hit Breakpoint 1, 
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  8417  in 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc
  #0  
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  #1  0x7fffeba5c3e8 in 
mir::protobuf::DisplayConfiguration::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804b830, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:11436
  #2  0x7fffeb38a615 in 
google::protobuf::MessageLite::SerializeWithCachedSizesToArray(unsigned char*) 
const () from /usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.9
  #3  0x7fffed696798 in mir_blob_from_display_config () from 
/usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #4  0x7fffed1d7ec6 in copy_config (conf=) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:44
  #5  __base_ctor  (other=warning: RTTI symbol not found for class 
'mir::graphics::nested::NestedDisplayConfiguration'
  ..., this=0x7fffd8047300) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:61

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

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

[Touch-packages] [Bug 1661295] Re: [vmware] mir 0.26 failing with nested server in protobuf when bringing up NestedDisplay [CHECK failed: (index) >= (0)]

[Gerry Boland]

Problem is that the "real" KMS platform is unable to determine the
current mode when running on VMware, leaving the current_mode_index at
an invalid value of UINTMAX, which is being passed through to the nested
platform.

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

Title:
  [vmware] mir 0.26 failing with nested server in protobuf when bringing
  up NestedDisplay [CHECK failed: (index) >= (0)]

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

Bug description:
  Setup:
  1. VMWare 12, with the following line added to ~/.vmware/preferences:
    mks.gl.allowBlacklistedDrivers = "TRUE"
  2. Created a VM with Xenial + Overlay PPA
  3. Installed unity8-desktop-session-mir, rebooted
  4. Tried to log in to a Unity8 session

  Problem: Unity8 fails to start, but is exiting cleanly as opposed to
  crashing. The following is all that is printed of the log:

  [2017-02-02:07:18:21.137] qtmir.screens: ScreensModel::ScreensModel
  [2017-02-02 07:18:21.143261] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:18:21.143413] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:18:21.144063] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  [2017-02-02:07:18:21.165] CHECK failed: (index) >= (0):
  initctl: No such variable: UNITY_MIR_SOCKET

  USC is coming up correctly however.

  If I try to launch miral-shell manually, I get similar error:

  MIR_SOCKET=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_PROMPT_FILE=1 
MIR_SERVER_HOST_SOCKET=/run/mir_socket 
MIR_SERVER_FILE=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_NAME=session-0 
miral-shell
  [2017-02-02 07:55:56.686669] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:55:56.687395] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:55:56.689036] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  ERROR: Dynamic exception type: google::protobuf::FatalException
  std::exception::what: CHECK failed: (index) >= (0):

  I tried to grab a backtrace at the location of the last call to
  /usr/include/google/protobuf/repeated_field.h:885 which might print
  the error:

  http://pastebin.ubuntu.com/23911595/

  Thread 4 "MirServerThread" hit Breakpoint 1, 
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  8417  in 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc
  #0  
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  #1  0x7fffeba5c3e8 in 
mir::protobuf::DisplayConfiguration::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804b830, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:11436
  #2  0x7fffeb38a615 in 
google::protobuf::MessageLite::SerializeWithCachedSizesToArray(unsigned char*) 
const () from /usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.9
  #3  0x7fffed696798 in mir_blob_from_display_config () from 
/usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #4  0x7fffed1d7ec6 in copy_config (conf=) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:44
  #5  __base_ctor  (other=warning: RTTI symbol not found for class 
'mir::graphics::nested::NestedDisplayConfiguration'
  ..., this=0x7fffd8047300) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:61

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

-- 
Mailing list: https://launchpad.net/~touch-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 doesn't allow multiple Mir connections from an application instance

[Gerry Boland]

Relevant info to reproduce:

 Saviq, the first way to test the multiple-connection situation
would probably be to create a custom .desktop file that removes
GDK_BACKEND from the app's environment, which will force it to autoprobe
and use Mir instead

-- 
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 doesn't allow multiple Mir connections from an application
  instance

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

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 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

[Gerry Boland]

** Branch linked: lp:~gerboland/qtmir/nouveau-workaround

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

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

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

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

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

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

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

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

[Gerry Boland]

I've an ancient NVidia box at home, can try it out. I'm attaching
patches for qtubuntu/qtmir to force Qt to use single threaded GL on
nouveau.

** Branch linked: lp:~gerboland/qtubuntu/nouveau-workaround

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

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

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

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

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

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

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

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

[Gerry Boland]

Was suspecting this is bug 1536279 but they don't quite match either

-- 
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 1675357] Re: Unity8 spins for a long time after being on an inactive vt

[Gerry Boland]

Turning on input event printing[1], when using Ctrl+Alt+F1 switching
away from unity8, I see a continuous stream of input events being sent
from Mir to Unity8, while on VT1:

[2017-03-23:12:36:53.419] qtmir.mir.input: Received 
MirKeyboardEvent(action=repeat,key_code=0x1008ff2b). Dispatching to 
ShellView(0x558b6b947ea0)
[2017-03-23:12:36:53.428] qtmir.mir.input: Received 
MirKeyboardEvent(action=repeat,key_code=0xffe9). Dispatching to 
ShellView(0x558b6b947ea0)
[2017-03-23:12:36:53.444] qtmir.mir.input: Received 
MirKeyboardEvent(action=repeat,key_code=0xffe3). Dispatching to 
ShellView(0x558b6b947ea0)
[2017-03-23:12:36:53.470] qtmir.mir.input: Received 
MirKeyboardEvent(action=repeat,key_code=0x1008ff2b). Dispatching to 
ShellView(0x558b6b947ea0)
[2017-03-23:12:36:53.480] qtmir.mir.input: Received 
MirKeyboardEvent(action=repeat,key_code=0xffe9). Dispatching to 
ShellView(0x558b6b947ea0)
[2017-03-23:12:36:53.495] qtmir.mir.input: Received 
MirKeyboardEvent(action=repeat,key_code=0xffe3). Dispatching to 
ShellView(0x558b6b947ea0)
[2017-03-23:12:36:53.521] qtmir.mir.input: Received 
MirKeyboardEvent(action=repeat,key_code=0x1008ff2b). Dispatching to 
ShellView(0x558b6b947ea0)
[2017-03-23:12:36:53.531] qtmir.mir.input: Received 
MirKeyboardEvent(action=repeat,key_code=0xffe9). Dispatching to 
ShellView(0x558b6b947ea0)


and actually, switching back to Unity8's VT, the key repeat events don't stop! 
Adding Mir to the bug


[1] qdbus com.canonical.Unity8 /com/canonical/Unity8/Debugging 
com.canonical.Unity8.Debugging.SetLoggingFilterRules "qtmir.mir.input=true"

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

** Summary changed:

- Unity8 spins for a long time after being on an inactive vt
+ Mir sending key repeat events continually to nested shell after VT switch 
(causes Unity8 lockup for a while)

** Changed in: unity8 (Ubuntu)
   Status: Triaged => 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/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 1674296] Re: In Terminal app, when settings window is already opened clicking on the settings icon does not raise it

[Gerry Boland]

Ok, no need for separate bug, the updated description shows me what you
want.

** Package changed: qtmir (Ubuntu) => qtubuntu (Ubuntu)

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

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

Title:
  In Terminal app, when settings window is already opened clicking on
  the settings icon does not raise it

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  New

Bug description:
  Steps:

  0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon

  Expected:
  Settings window is raised and focused

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

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

[Touch-packages] [Bug 1674296] Re: When preference window is already opened clicking on the settings icon does not raise it

[Gerry Boland]

Could you log separate bug about QWindow::raise/QWindow::requestActivate
against qtubuntu. Mir has an api for that, but we've not implemented it.

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

Title:
  In Terminal app, when settings window is already opened clicking on
  the settings icon does not raise it

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  New

Bug description:
  Steps:

  0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon

  Expected:
  Settings window is raised and focused

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

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

[Touch-packages] [Bug 1238838] Re: [qpa] QUbuntuIntegration requests screen info which open mir client connection with shell - even if client does not open window

[Gerry Boland]

That's a good question.

I think that QGuiApplication assumes it will be creating a window at
some stage, so will connect to the display server in advance. If you
know for sure you're not going to create a window, QCoreApplication
should be used instead.

To test this hypothesis, I tried another platform: X11 itself. I ran
your test app without a valid X running (actually I faked it by pointing
it to a non-existing X socket):

DISPLAY=:1 QT_QPA_PLATFORM=xcb ./test

and got a very similar crash: http://pastebin.ubuntu.com/24171497/

So I think this is behaving as expected. If you disagree, please re-open this 
bug and say why. I'd definitely like to know what your use-case is.
-G

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

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

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

Title:
  [qpa] QUbuntuIntegration requests screen info which open mir client
  connection with shell - even if client does not open window

Status in qtubuntu package in Ubuntu:
  Invalid

Bug description:
  Take this application and compile it:

  > main.cpp <=
  #include 

  int main(int argc, char *argv[])
  {
  QGuiApplication a(argc, argv);

  return a.exec();
  }
  ==

  > test.pro <=
  QT   += gui
  TARGET = test
  TEMPLATE = app
  SOURCES += main.cpp
  ==

  On desktop, it simply runs, without opening a window, which is fine.

  On phone with Mir, it will fail to run as Mir (due to unity-mir)
  rejects it as a client. Since it does not open a window, why should it
  connect to Mir at all??

  Looking into it:
  #2  0x4200686e in mir::client::DisplayConfiguration::copy_to_client() const 
() from /usr/lib/arm-linux-gnueabihf/libmirclient.so.3
  #3  0x42008a64 in MirConnection::create_copy_of_display_config() () from 
/usr/lib/arm-linux-gnueabihf/libmirclient.so.3
  #4  0x4200761c in mir_connection_get_display_info () from 
/usr/lib/arm-linux-gnueabihf/libmirclient.so.3
  #5  0x41efb344 in ua_ui_display_new_with_index () from 
/usr/lib/arm-linux-gnueabihf/libubuntu_application_api_mirclient.so.1
  #6  0x41ec01f6 in QUbuntuBaseScreen::QUbuntuBaseScreen (this=0x26f98) at 
screen.cc:82
  #7  0x41ebea0a in QUbuntuScreen::QUbuntuScreen (this=0x26f90, 
options=0x282e0) at screen.cc:54
  #8  0x41ebdf80 in QUbuntuIntegration::QUbuntuIntegration (this=0x2a1e8, 
input_factory=0x41edb824 <(anonymous 
namespace)::InputAdaptorFactory::instance()::global_instance>)
  at integration.cc:75
  #9  0x41ebdaaa in QUbuntuMirIntegration::QUbuntuMirIntegration (this=0x2a1e8) 
at integration.cc:39
  #10 0x41ebd536 in QUbuntuMirClientIntegrationPlugin::create (this=, system=..., paramList=...) at main.cc:41
  #11 0x400c0ba8 in QGuiApplicationPrivate::createPlatformIntegration() () from 
/usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
  #12 0x400c11da in QGuiApplicationPrivate::createEventDispatcher() () from 
/usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
  #13 0x4057bc86 in QCoreApplication::init() () from 
/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
  #14 0x4057bcca in 
QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
  #15 0x400c187a in QGuiApplication::QGuiApplication(int&, char**, int) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5

  which makes sense as in
  src/platforms/ubuntu/ubuntucommon/integration.cc
  in the constructor (called on initialization of the QPA plugin)
  QUbuntuIntegration::QUbuntuIntegration(QUbuntuInputAdaptorFactory 
*input_factory)
  there's this line of code:

    // Create default screen.
    screen_ = new QUbuntuScreen(options_);
    screenAdded(screen_);

  QUbuntuScreen creates a Mir connection, as only Mir has screen info.

  So the question is: does QGuiApplication really need Screen
  information, even if it doesn't open a QWindow?

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

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

[Touch-packages] [Bug 1238838] Re: [qpa] QUbuntuIntegration requests screen info which open mir client connection with shell - even if client does not open window

[Gerry Boland]

Oh, I was the original author! Hah :D

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

Title:
  [qpa] QUbuntuIntegration requests screen info which open mir client
  connection with shell - even if client does not open window

Status in qtubuntu package in Ubuntu:
  Invalid

Bug description:
  Take this application and compile it:

  > main.cpp <=
  #include 

  int main(int argc, char *argv[])
  {
  QGuiApplication a(argc, argv);

  return a.exec();
  }
  ==

  > test.pro <=
  QT   += gui
  TARGET = test
  TEMPLATE = app
  SOURCES += main.cpp
  ==

  On desktop, it simply runs, without opening a window, which is fine.

  On phone with Mir, it will fail to run as Mir (due to unity-mir)
  rejects it as a client. Since it does not open a window, why should it
  connect to Mir at all??

  Looking into it:
  #2  0x4200686e in mir::client::DisplayConfiguration::copy_to_client() const 
() from /usr/lib/arm-linux-gnueabihf/libmirclient.so.3
  #3  0x42008a64 in MirConnection::create_copy_of_display_config() () from 
/usr/lib/arm-linux-gnueabihf/libmirclient.so.3
  #4  0x4200761c in mir_connection_get_display_info () from 
/usr/lib/arm-linux-gnueabihf/libmirclient.so.3
  #5  0x41efb344 in ua_ui_display_new_with_index () from 
/usr/lib/arm-linux-gnueabihf/libubuntu_application_api_mirclient.so.1
  #6  0x41ec01f6 in QUbuntuBaseScreen::QUbuntuBaseScreen (this=0x26f98) at 
screen.cc:82
  #7  0x41ebea0a in QUbuntuScreen::QUbuntuScreen (this=0x26f90, 
options=0x282e0) at screen.cc:54
  #8  0x41ebdf80 in QUbuntuIntegration::QUbuntuIntegration (this=0x2a1e8, 
input_factory=0x41edb824 <(anonymous 
namespace)::InputAdaptorFactory::instance()::global_instance>)
  at integration.cc:75
  #9  0x41ebdaaa in QUbuntuMirIntegration::QUbuntuMirIntegration (this=0x2a1e8) 
at integration.cc:39
  #10 0x41ebd536 in QUbuntuMirClientIntegrationPlugin::create (this=, system=..., paramList=...) at main.cc:41
  #11 0x400c0ba8 in QGuiApplicationPrivate::createPlatformIntegration() () from 
/usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
  #12 0x400c11da in QGuiApplicationPrivate::createEventDispatcher() () from 
/usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
  #13 0x4057bc86 in QCoreApplication::init() () from 
/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
  #14 0x4057bcca in 
QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
  #15 0x400c187a in QGuiApplication::QGuiApplication(int&, char**, int) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5

  which makes sense as in
  src/platforms/ubuntu/ubuntucommon/integration.cc
  in the constructor (called on initialization of the QPA plugin)
  QUbuntuIntegration::QUbuntuIntegration(QUbuntuInputAdaptorFactory 
*input_factory)
  there's this line of code:

    // Create default screen.
    screen_ = new QUbuntuScreen(options_);
    screenAdded(screen_);

  QUbuntuScreen creates a Mir connection, as only Mir has screen info.

  So the question is: does QGuiApplication really need Screen
  information, even if it doesn't open a QWindow?

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

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

[Touch-packages] [Bug 1671449] Re: [unity8] windows don't have shadow

[Gerry Boland]

Thanks for that. Can confirm it is nothing gpu/graphics related, it is a
bug in our UITK. Fix on the way...

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

Title:
  [unity8] windows don't have shadow

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  [unity8] windows don't have shadow

  i see this on both 16.04 and 17.04 unity8 after the last update
  i think? i've also seen this before by installing silo 2540 

  see attached screenshot

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

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

[Touch-packages] [Bug 1671449] Re: [unity8] windows don't have shadow

[Gerry Boland]

Hey dinamic! Thanks for the bug!

Did this happen suddenly, or you never see shadows at all?

What GPU and driver are you using?

Could you provide a pastebin of the unity8.log file, ideally just after
unity8 starts up so we get the initial output as unity8 starts.

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

Title:
  [unity8] windows don't have shadow

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  [unity8] windows don't have shadow

  i see this on both 16.04 and 17.04 unity8 after the last update
  i think? i've also seen this before by installing silo 2540 

  see attached screenshot

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

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

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

[Gerry Boland]

Actually, might be easier/more-reliable just to edit /etc/environment
and add "QSG_RENDER_LOOP=basic" and restart.

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

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

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

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

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

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

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

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

[Gerry Boland]

I have Qt configured (in QtUbuntu/QtMir) to use multi-threaded GL
rendering, so we're probably hitting Nouveau's limitations here.

As workaround, I can add code to QtUbuntu/QtMir use single-threaded GL
for Nouveau.

If this is easily reproduced, can you try

initctl set-env --global QSG_RENDER_LOOP=basic

and see if everything is more stable? If so, the workaround should do
the trick

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1670670] Re: Unity8 pointer does not stay in sync with Qemu VM tablet input

[Gerry Boland]

Looking into QtMir, we're only using the relative mouse motion in our
calculation of the cursor position. We need that to implement the push-
against-screen-edge behaviour for a mouse.

We've not considered tablet input devices at all. I see Mir's associates
a device with each input event, so it possible for us to change
behaviour depending on the input device. Overall I don't knom enough to
speak intelligently about what we need to do, needs further
investigation on our side.

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

Title:
  Unity8 pointer does not stay in sync with Qemu VM tablet input

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Each time you login, or come back from the lock screen, you need to
  "recalibrate" the pointer by carefully moving the pointer into each
  corner.

  Contrast this with unity7, where the absolute position of the virtual
  tablet pointer is tracked, and sync is never lost.

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

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

[Touch-packages] [Bug 1670670] Re: Unity8 pointer does not stay in sync with Qemu VM tablet input

[Gerry Boland]

Looking into QtMir, we're using relative

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

Title:
  Unity8 pointer does not stay in sync with Qemu VM tablet input

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Each time you login, or come back from the lock screen, you need to
  "recalibrate" the pointer by carefully moving the pointer into each
  corner.

  Contrast this with unity7, where the absolute position of the virtual
  tablet pointer is tracked, and sync is never lost.

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

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

[Touch-packages] [Bug 1662145] Re: [regression] Some apps fail to start with [QPA] UbuntuClientIntegration: connection to Mir server failed.

[Gerry Boland]

> Also very important that those apps (toolkits) choose native Mir over 
> X when both are available.
Qt isn't designed to make the choice itself, it expects to be told if either X 
or Mir should be used.

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

Title:
  [regression] Some apps fail to start with [QPA]
  UbuntuClientIntegration: connection to Mir server failed.

Status in Canonical System Image:
  Confirmed
Status in platform-api:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in Unity8 Session Snap:
  Invalid
Status in platform-api package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Invalid

Bug description:
  Zesty
  unity8-session  16.04   396   canonical  
devmode

  Test Case
  1. Open the app drawer
  2. Launch an app (eg calculator)

  Expected result
  It starts successfully and the app works as expected

  Actual Result
  It launches, the loading screen then a black screen is shown for a sort 
moment, then the window closes.

  They all report:

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

  Mir returned: "Failed to connect to server socket: Permission denied"
  <<<

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

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

[Touch-packages] [Bug 1670670] Re: Unity8 pointer does not stay in sync with Qemu VM tablet input

[Gerry Boland]

** Changed in: mir (Ubuntu)
   Status: Invalid => 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/1670670

Title:
  Unity8 pointer does not stay in sync with Qemu VM tablet input

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

Bug description:
  Each time you login, or come back from the lock screen, you need to
  "recalibrate" the pointer by carefully moving the pointer into each
  corner.

  Contrast this with unity7, where the absolute position of the virtual
  tablet pointer is tracked, and sync is never lost.

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

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

[Touch-packages] [Bug 1670670] Re: Unity8 pointer does not stay in sync with Qemu VM tablet input

[Gerry Boland]

> AFAIK the only thing stopping us from using Mir's native input coordinates
> was the inability to implement barriers/edge resistance in places.

We had other use-cases where unity8 having control over mouse position
was useful. One example coming to mind is phone docked to an external
display, we wanted to limit the cursor to the external display only. And
we had a few other pie-in-the-sky design ideas which would be much
easier if unity8 had cursor control.

I still don't see why Mir can't just let Unity8 (a nested) position the
cursor (like it could, if it were a host server)!

And absolute vs relative. If we're doing it wrong, we can fix it.

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

Title:
  Unity8 pointer does not stay in sync with Qemu VM tablet input

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

Bug description:
  Each time you login, or come back from the lock screen, you need to
  "recalibrate" the pointer by carefully moving the pointer into each
  corner.

  Contrast this with unity7, where the absolute position of the virtual
  tablet pointer is tracked, and sync is never lost.

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

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

[Touch-packages] [Bug 1654974] Re: webbrowser-app locks up my session (zesty)

[Gerry Boland]

I tried on Zesty with my AMD machine, no lock up for me. Browser comes
up ok. I do get lots of libGL errors though

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

Title:
  webbrowser-app locks up my session (zesty)

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  My setup:
   * up-to-date zesty
   * unity8-greeter as greeter
   * unity7 as desktop

  How to reproduce:
   * open xterm
   * start webbrowser-app from xterm

  Everything locks up and have to hard reboot the computer.

  I tried catching the output to a file with &> but got nothing, so i
  took a picture.

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

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

[Gerry Boland]

@vanvugt - yep it's not ideal. For phone/tablet, to make device rotation
animation as good as we could, was easiest to give the OSK a fullscreen
surface and have it rotate itself, letting application shine through in
the translucent area.

But that is certainly an area we can improve.

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Invalid

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

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

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
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 1669444] Re: [regression] OSK input shaping no longer works correctly

[Gerry Boland]

I've tracked this down to the following mir bug:
https://bugs.launchpad.net/mir/+bug/1670876

-- 
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:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
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 1670717] Re: Unity8/mir working on VMware due to bypass not working

[Gerry Boland]

Probably also relevant: https://bugs.launchpad.net/mir/+bug/1560498

** Tags added: unity8-desktop

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

Title:
  Unity8/mir working on VMware due to bypass not working

Status in mesa package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Related to this bug (bug #1480755) - this is the issue preventing
  unity8/mir working in VMware.

  Bringing it out into its own issue to improve visibility.

  Choice quotes from previous bug:

  The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell)
  returns 7 compatible EGLConfigs for EGL_ALPHA_SIZE=0 but all of them
  have EGL_ALPHA_SIZE == 8 set.

  Added a Mesa task. RAOF has suggested we should just fix Mesa. When
  asking for RGBA of 8880 it should provide at least one EGLConfig that
  is 8880 instead of always .

  This should be possible. It's not entirely clear why we're not getting
  XRGB visuals currently, but it's fixable.

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

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

[Touch-packages] [Bug 1670713] Re: Automatic screen resizing for virtual machines

[Gerry Boland]

Mir needs to support whatever API VMs use to communicate the "display"
size changed. QtMir supporta display sizes changing already (can been
seen by changing resolution)

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

Title:
  Automatic screen resizing for virtual machines

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

Bug description:
  Currently in when you resize the virtual display in qemu (with
  QXL/spice display) the unity8 screen resolution stays the same.
  However in e.g. Gnome3, the shell is informed of a suggestion to
  change size, and complies.

  There appears to be an emerging de-facto standard in virtual display
  resizing, as described below by Thomas Hellstrom
   from VMware, which is supported by both qemu
  and VMware.

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

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

[Touch-packages] [Bug 1670681] Re: If OSK restarts, new OSK surface ignored by shell

[Gerry Boland]

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

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

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

Title:
  If OSK restarts, new OSK surface ignored by shell

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  (Probably need current state of silo 2481 to reproduce)

  Running unity8, check OSK can come on screen. Dismiss it, then do:
  stop maliit-server
  start maliit-server

  Then try to bring up the OSK again.

  OSK surface does not come up, and unity8 log reports "Multiple Input
  Method Surfaces created, removing the old one!" but it fails to work
  anyway.

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

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

[Touch-packages] [Bug 1670681] [NEW] If OSK restarts, new OSK surface ignored by shell

[Gerry Boland]

Public bug reported:

(Probably need current state of silo 2481 to reproduce)

Running unity8, check OSK can come on screen. Dismiss it, then do:
stop maliit-server
start maliit-server

Then try to bring up the OSK again.

OSK surface does not come up, and unity8 log reports "Multiple Input
Method Surfaces created, removing the old one!" but it fails to work
anyway.

** Affects: unity8 (Ubuntu)
 Importance: Medium
 Assignee: Gerry Boland (gerboland)
 Status: 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/1670681

Title:
  If OSK restarts, new OSK surface ignored by shell

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  (Probably need current state of silo 2481 to reproduce)

  Running unity8, check OSK can come on screen. Dismiss it, then do:
  stop maliit-server
  start maliit-server

  Then try to bring up the OSK again.

  OSK surface does not come up, and unity8 log reports "Multiple Input
  Method Surfaces created, removing the old one!" but it fails to work
  anyway.

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

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

[Touch-packages] [Bug 1655644] Re: unity8 crash after create a new online account

[Gerry Boland]

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

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

Title:
  unity8 crash after create a new online account

Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu xenial with overlay ppa.
  Unity8 installed from ppa (debian).
  arch: amd64

  
  Unity8 crashes after create a new account

  How to reproduce:

  1- start system settings
  2- Go to online accounts
  3- Click to create a new account
  4- Choose any account on the list (Eg. google)
  5- Follow the steps to create the new account
  6- After create the account click on it

  Expected

  Show Account information

  Current

  Unity8 crash.

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

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

[Touch-packages] [Bug 1624407] Re: Add a 'quit' message that is app-wide, as opposed to mir_event_type_close_surface

[Gerry Boland]

Does Mir provide enough api to allow application ask user a question
before shutdown? In Unity7, typically that is requesting focus and
popping up a dialog - should be ok, but good to think about it.

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

Title:
  Add a 'quit' message that is app-wide, as opposed to
  mir_event_type_close_surface

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Currently in unity8, when requesting to "Quit" a running application
  from the launcher, what happens is that qtmir goes through all its
  associated windows/surfaces, and closes them one by one. Supposedly,
  when the last window is closed, the application terminates itself (but
  this is not necessarily the case, see
  https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed-
  prop).

  This prevents application authors from doing proper cleanup before the
  app is closed. For example in Qt, the QCoreApplication::aboutToQuit()
  signal is emitted only after all windows have been closed, so the
  application doesn’t get a chance to e.g. save the list of open windows
  (real use case for multi-window browser application which saves the
  current session).

  This is similar to unity7’s implementation by the way, but I think
  it’s wrong. Surely there must be a way (maybe toolkit-specific) to
  request an app to terminate itself (and fall back to closing all
  windows if not).

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

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

[Touch-packages] [Bug 1597205] Re: Not sending relative mouse events to clients

[Gerry Boland]

** Changed in: qtmir
   Status: In Progress => Fix Released

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

Title:
  Not sending relative mouse events to clients

Status in Canonical System Image:
  Fix Released
Status in QtMir:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  QtMir is not sending relative mouse movements in mouse events.

  Relevant code from mirsurface.cpp:

  
  mir::EventUPtr makeMirEvent(QMouseEvent *qtEvent, MirPointerAction action)
  {
  auto timestamp = 
uncompressTimestamp(qtmir::Timestamp(qtEvent->timestamp()));
  auto modifiers = getMirModifiersFromQt(qtEvent->modifiers());
  auto buttons = getMirButtonsFromQt(qtEvent->buttons());

  return mir::events::make_event(0 /*DeviceID */, timestamp, 
std::vector{} /* cookie */, modifiers, action,
 buttons, qtEvent->x(), qtEvent->y(), 0, 0, 
0, 0);

  
  The last 2 parameters in the make_event call should be the relative x & y 
motion.

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

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

[Touch-packages] [Bug 1667001] Re: [amd] screen-unblanking seems to flicker backlight on/off 8 times before display resumes

[Gerry Boland]

One small warning message is printed during display on flicker:
http://pastebin.ubuntu.com/24053776/

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

Title:
  [amd] screen-unblanking seems to flicker backlight on/off 8 times
  before display resumes

Status in Canonical System Image:
  Incomplete
Status in Mir:
  New
Status in repowerd:
  Invalid
Status in mir package in Ubuntu:
  Incomplete
Status in repowerd package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  I've a Lenovo Flex 2-14D which has an AMD GPU. I'm using the free
  driver. I have unity8 installed.

  If I let the screen blank, and hit a key to unblank, it takes about 5
  seconds until screen turns on properly. During those 5 seconds, I see
  the display backlight turn on & off about 5 times, all the while with
  a black picture.

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

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

[Touch-packages] [Bug 1667001] Re: [amd] screen-unblanking seems to flicker backlight on/off 5 times before display resumes

[Gerry Boland]

Ok, with Alexandros' help I've dug a bit more.

On my hardware, I tear everything down and just run 
sudo mir_demo_server_basic --arw-file
I can see clients ok.

I forked mir_demo_client_display_config to add extra bits:
https://code.launchpad.net/~gerboland/+git/display-configurator
which adds an "O" option to power off the display

When I run it, and hit "O", the display flickers 8 times and then stays
off (mir_power_mode_off)

If I hit "P" to turn it on again, nothing happens (mir_power_mode_on).
Applying the configuration appears to hang the client - I get no success
or fail response from Mir.

If I kill the client, Mir re-activates the display (flickering 8 times)

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

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

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

** Summary changed:

- [amd] screen-unblanking seems to flicker backlight on/off 5 times before 
display resumes
+ [amd] screen-unblanking seems to flicker backlight on/off 8 times before 
display resumes

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

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

Title:
  [amd] screen-unblanking seems to flicker backlight on/off 8 times
  before display resumes

Status in Canonical System Image:
  Incomplete
Status in Mir:
  New
Status in repowerd:
  Invalid
Status in mir package in Ubuntu:
  Incomplete
Status in repowerd package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  I've a Lenovo Flex 2-14D which has an AMD GPU. I'm using the free
  driver. I have unity8 installed.

  If I let the screen blank, and hit a key to unblank, it takes about 5
  seconds until screen turns on properly. During those 5 seconds, I see
  the display backlight turn on & off about 5 times, all the while with
  a black picture.

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

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

[Touch-packages] [Bug 1667001] Re: [amd] screen-unblanking seems to flicker backlight on/off 5 times before display resumes

[Gerry Boland]

@alf:
http://pastebin.ubuntu.com/24053520/

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

Title:
  [amd] screen-unblanking seems to flicker backlight on/off 5 times
  before display resumes

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Incomplete
Status in repowerd:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in repowerd package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I've a Lenovo Flex 2-14D which has an AMD GPU. I'm using the free
  driver. I have unity8 installed.

  If I let the screen blank, and hit a key to unblank, it takes about 5
  seconds until screen turns on properly. During those 5 seconds, I see
  the display backlight turn on & off about 5 times, all the while with
  a black picture.

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

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

[Touch-packages] [Bug 1666902] [NEW] Enable screencast utilities

[Gerry Boland]

Public bug reported:

Peek is a utility to grab screencast to animated GIFs.

They have an open bug to add Mir support:
https://github.com/phw/peek/issues/39

Current mirscreencast util only works as root, due to Unity8 replacing
the renderer with its own custom one (which does not support
screenshotting yet). We need to get screencasting working for third
party applications running as the user.

Mediation of screencasting application is also needed - so user is aware
screencast in progress.

** Affects: qtmir
 Importance: Undecided
 Status: New

** Affects: qtmir (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

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

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

Title:
  Enable screencast utilities

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

Bug description:
  Peek is a utility to grab screencast to animated GIFs.

  They have an open bug to add Mir support:
  https://github.com/phw/peek/issues/39

  Current mirscreencast util only works as root, due to Unity8 replacing
  the renderer with its own custom one (which does not support
  screenshotting yet). We need to get screencasting working for third
  party applications running as the user.

  Mediation of screencasting application is also needed - so user is
  aware screencast in progress.

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt font / text / characters in Unity8

[Gerry Boland]

Here is what Qt is doing, on upload:
https://code.woboq.org/qt5/qtdeclarative/src/quick/scenegraph/qsgdefaultdistancefieldglyphcache.cpp.html#158
It saves & restores the alignment, and assumes the default alignment of 4 for 
drawing. IMO Mir isn't playing along, as it changes the alignment but does not 
restore it.

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

Title:
  Randomly corrupt font / text / characters in Unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  Won't Fix
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Won't Fix
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Corrupted characters in text rendering.

  Only happens after starting non-GL application, like GTK application
  or mir_demo_client_fingerpaint.

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

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

[Touch-packages] [Bug 1665705] Re: Deleting a QRasterWindow crashes

[Gerry Boland]

** Branch linked: lp:~gerboland/qtubuntu/delete-qraster-crash

** Changed in: qtubuntu
   Status: New => In Progress

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

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

** Changed in: qtubuntu
 Assignee: (unassigned) => Gerry Boland (gerboland)

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

Title:
  Deleting a QRasterWindow crashes

Status in qtubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  The attached program crashes when run under unity8/qtubuntu, works
  fine with other QPAs

  terminal log says "pure virtual method called"

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

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

[Touch-packages] [Bug 1665705] Re: Deleting a QRasterWindow crashes

[Gerry Boland]

Yep can reproduce easily. Obvious fix is to remove the makeCurrent call
from the BackingStore destructor, but that undoes a previous fix I made
for surface resizing errors. I need to study the other QPAs to see what
they do

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

Title:
  Deleting a QRasterWindow crashes

Status in qtubuntu:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  The attached program crashes when run under unity8/qtubuntu, works
  fine with other QPAs

  terminal log says "pure virtual method called"

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

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

[Touch-packages] [Bug 1665705] Re: Deleting a QRasterWindow crashes

[Gerry Boland]

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

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

Title:
  Deleting a QRasterWindow crashes

Status in qtubuntu:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  The attached program crashes when run under unity8/qtubuntu, works
  fine with other QPAs

  terminal log says "pure virtual method called"

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

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

[Touch-packages] [Bug 1665705] Re: Deleting a QRasterWindow crashes

[Gerry Boland]

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

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

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

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

Title:
  Deleting a QRasterWindow crashes

Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  The attached program crashes when run under unity8/qtubuntu, works
  fine with other QPAs

  terminal log says "pure virtual method called"

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

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

[Gerry Boland]

I've hacked qtmir to print the subpixel hint that Mir is supplying.

http://pastebin.ubuntu.com/24007971/ is my output. First I run a simple
qml demo shell as nested server under USC, get "0" hint.

Then I run again as host server, get a hint "1 = RGB".

The "Subpixel hint" output of the 2 cases do not match for me, hence the
complaint.

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

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  In Progress
Status in QtMir:
  Triaged
Status in qtubuntu:
  Triaged
Status in mir 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 1393578] Re: Subpixel order not included in Mir display information

[Gerry Boland]

Just testing it now, AFAICS a nested server is not getting the correct
subpixel data passed to it.

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

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  In Progress
Status in QtMir:
  Triaged
Status in qtubuntu:
  Triaged
Status in mir 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 1536751] Re: Font/text rendering is irregular and not pixel-aligned on low DPI screens

[Gerry Boland]

UITK already using NativeRendering for text when GU<10.

Text *might* be improved by setting Qt's DPI and sub-pixel rendering
hints correctly.

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

Title:
  Font/text rendering is irregular and not pixel-aligned on low DPI
  screens

Status in Canonical System Image:
  Confirmed
Status in fontconfig package in Ubuntu:
  Incomplete
Status in freetype package in Ubuntu:
  Incomplete
Status in harfbuzz package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  This is a Dell Vostro 3550 laptop with a fresh install of 16.04 and
  unity8 Mir session

  the version of qtdeclarative5-qtmir-plugin is
  0.4.7+16.04.20160104-0ubuntu1

  As you can see from the screenshots the text has low details and, in
  the case of indicators descriptions at the top, almost disappears.

  The text could be fixed by using Text.NativeRendering instead of 
Text.QtRendering for the QML labels on low dpi screens, although text doesn't 
seem to be the only issue here. The icons are definitely lacking detail as well 
(QML Image's smoothing is enabled maybe?).
  Also the dots of the infographic don't look like circles at all, they're 
missing pixels and many of them look like a C more than an O.

  It looks to me like something is setting the wrong resolution, because
  it looks quite bad. But the screenshots are 1366x768 so I think that's
  not the case.

  NOTE: Unity7 looks perfectly fine and detailed

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt font / text / characters in Unity8

[Gerry Boland]

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

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

Title:
  Randomly corrupt font / text / characters in Unity8

Status in Canonical System Image:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Corrupted characters in text rendering.

  Only happens after starting non-GL application, like GTK application
  or mir_demo_client_fingerpaint.

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt font / text / characters in Unity8

[Gerry Boland]

@vanvugt
you were right that glPixelStorei was to blame. In ShmBuffer Mir uses 
glPixelStorei to change the GL_UNPACK_ALIGNMENT from 4 (that Qt set) to 1 (that 
Mir sets, as it is more careful about stride). 

Mir fails to restore the state the Qt set, which broke Qt's rendering
from then on.

ShmBuffer only used for clients that do not use GL to draw, so Gtk and
mir demos like fingerpaint, which is why this bug was "random"


Could Mir be patched to revert any GL state changes it makes, when called into 
by Qt?

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

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

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

** Description changed:

- Corrupted characters in text rendering, mainly in Unity8 window
- titlebars.
+ Corrupted characters in text rendering.
  
- I think this is a new issue. It only started happening (on xenial
- desktop) in the past month or two.
+ Only happens after starting non-GL application, like GTK application or
+ mir_demo_client_fingerpaint.

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

Title:
  Randomly corrupt font / text / characters in Unity8

Status in Canonical System Image:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Corrupted characters in text rendering.

  Only happens after starting non-GL application, like GTK application
  or mir_demo_client_fingerpaint.

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt font / text / characters in Unity8

[Gerry Boland]

I'm looking into this now. I took an api trace of some simple font
rendering by Qt on Mir showing the problem, and executed it on my X11
session. It renders ok on X11. Reading through the apitrace, Qt seems to
be doing the right thing.

I suspect the mismatch we have between Mir creating a GLES context and
Qt expecting a GL context is hitting us here.

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

Title:
  Randomly corrupt font / text / characters in Unity8

Status in Canonical System Image:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt font / text / characters in Unity8

[Gerry Boland]

@kgunn - yes I can reproduce it quite reliably too. No need to try the
glyph cache workaround thing, I checked it and it had no impact.

@duflu - Qt is rendering the text.

Since Qt renders text ok in Unity7, there must be some GL configuration
problem in QtMir/QtUbuntu causing this kind of issue. At the moment,
I've not really dug into why.

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

Title:
  Randomly corrupt font / text / characters in Unity8

Status in Canonical System Image:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

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

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

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

[Gerry Boland]

I've a bunch of questions. Any time you see EGL complaints, it is often
down to the graphics driver.

1. is this complaint for an NVidia-based system only? The log indicates
it has the proprietary nvidia driver installed, which Mir does not
support (and so Unity8 does not run). How are you testing?

I've tested recent Zesty on my AMD machine, and it didn't crash like
this! (It was getting graphics distortion though)

2. can you export QSG_INFO=1, run the browser and pastebin the output
please?

3. was there a recent webbrowser release or something that showed this
problem, or has it been around for a while?

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

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

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

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

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

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

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

[Touch-packages] [Bug 1649077] Re: [regression] OSK appears blank and/or flickers in the lock screen

[Gerry Boland]

** Changed in: qtmir
   Status: In Progress => Fix Released

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

Title:
  [regression] OSK appears blank and/or flickers in the lock screen

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in QtMir:
  Fix Released
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  After using OTA-14 a while, the OSK starts to exhibit a strange
  behaviour.

  1. It appears blank after a while in the lock screen. You can still
  press randomly which then makes the OSK to appear fully. When you
  press a character again it starts to flicker.

  2. OSK starts to flicker similar to bug #1590765 which was fixed in
  OTA-12. It seems to have resurfaced in OTA-14.

  Systems Info:
  OTA-14 Stable Channel
  Devices: E4.5, E5

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

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

[Touch-packages] [Bug 1655644] Re: unity8 crash after create a new online account

[Gerry Boland]

One backtrace, slightly confusing: http://pastebin.ubuntu.com/23874652/

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

Title:
  unity8 crash after create a new online account

Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu xenial with overlay ppa.
  Unity8 installed from ppa (debian).
  arch: amd64

  
  Unity8 crashes after create a new account

  How to reproduce:

  1- start system settings
  2- Go to online accounts
  3- Click to create a new account
  4- Choose any account on the list (Eg. google)
  5- Follow the steps to create the new account
  6- After create the account click on it

  Expected

  Show Account information

  Current

  Unity8 crash.

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

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

[Touch-packages] [Bug 1655644] Re: unity8 crash after create a new online account

[Gerry Boland]

Relevant unity8.log output before crash:

http://pastebin.ubuntu.com/23874565/

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

Title:
  unity8 crash after create a new online account

Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu xenial with overlay ppa.
  Unity8 installed from ppa (debian).
  arch: amd64

  
  Unity8 crashes after create a new account

  How to reproduce:

  1- start system settings
  2- Go to online accounts
  3- Click to create a new account
  4- Choose any account on the list (Eg. google)
  5- Follow the steps to create the new account
  6- After create the account click on it

  Expected

  Show Account information

  Current

  Unity8 crash.

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

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

[Touch-packages] [Bug 1645372] Re: support display scaling slider in unity8

[Gerry Boland]

Yes mir_output_set_scale_factor is needed, as the settings app needs an
API to communicate the desired scale factor to unity8

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

Title:
  support display scaling slider in unity8

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

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

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

[Touch-packages] [Bug 1657763] Re: Mouse position should not be taken into account for anything other than menus when a menu is open

[Gerry Boland]

So while a menu is open, only that surface should get mouse hover
events.

That is how things work today. Do we want Design input on that?

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

Title:
  Mouse position should not be taken into account for anything other
  than menus when a menu is open

Status in unity8 package in Ubuntu:
  New

Bug description:
  How to reproduce: 
   * Open an app that has menus (i'm using dolphin but any should work)
   * Put the mouse over the window decoration
   * Open a menu
   * Move the mouse over the Close/Maximize/Minimize buttons of the window 
decoration
   * See how they animate

  But clicking only just closes the menu and not activate the button (as
  does in unity7) so I understand what we should do is not trigger their
  animation (same as unity7).

  Not sure if should be fixed at the same time or not but this also
  happens to window contents itself (i.e. the window has areas that
  react on mouse over in unity7 they don't do anything when the menu is
  open but in unity8 they do)

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

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

[Touch-packages] [Bug 1658706] [NEW] version in pkgconfig file (0.2) older than packaging version (0.3.x)

[Gerry Boland]

Public bug reported:

Version in the pkgconfig file is 0.2
Version of libcontent-hub according to the debian packaging is 0.3.x

The minor version should match at least, no?

** Affects: content-hub (Ubuntu)
 Importance: Undecided
 Status: 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/1658706

Title:
  version in pkgconfig file (0.2) older than packaging version (0.3.x)

Status in content-hub package in Ubuntu:
  New

Bug description:
  Version in the pkgconfig file is 0.2
  Version of libcontent-hub according to the debian packaging is 0.3.x

  The minor version should match at least, no?

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

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

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

[Gerry Boland]

Ok, rather marginal use-cases then :)

At least Mir allows this kind of request can be filtered by Unity8 in
future, to prevent this kind of thing being abused. Perhaps need a
system so that privileged clients can do this if they need.

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

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

Status in Canonical System Image:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
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.11+15.04.20151130.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6cee045a96ab5c9a03847aeb290f4860eea1034d
  contains more details.

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

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

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

[Gerry Boland]

> It is actually valid for apps to be able to change the power mode 
> of the display. mirout in Mir 0.26.0 has such an option. But I agree
> it's bad for apps to do it unexpectedly

@vanvugt can you share examples of times when this is valid? I'm of the
opinion display on/off/suspend should be solely the shell's decision.

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

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

Status in Canonical System Image:
  New
Status in qtmir package in Ubuntu:
  In Progress
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.11+15.04.20151130.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6cee045a96ab5c9a03847aeb290f4860eea1034d
  contains more details.

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

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

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

[Gerry Boland]

Yeah I figured it out. Non rootless (rooted!) XMir wants to decide the
display power state (DPMS). Unity8/QtMir never had to deal with clients
doing that before.

Longer term Unity8 should filter such requests as it's quite rude for an
app to be able to turn off your display on you, but I've a branch up to
at least not crash.

I've more work to do on this though, as waking up the display isn't
working with that branch. To be continued

** Branch linked: lp:~gerboland/qtmir/fix-glcontext-loss-on-reconfigure

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

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

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

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

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

Status in qtmir package in Ubuntu:
  In Progress
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.11+15.04.20151130.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6cee045a96ab5c9a03847aeb290f4860eea1034d
  contains more details.

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

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

[Touch-packages] [Bug 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

[Gerry Boland]

** Branch linked: lp:~gerboland/qtubuntu/quit-gracefully-on-no-
mirconnection

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

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

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

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

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

Title:
  clients crash with "UbuntuClientIntegration: connection to Mir server
  failed."

Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  According to
  https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
  it seems to be common-ish.

  This happens when unity8-dash can't find unity8 (mir server) and
  crashing (via QFatal) is our controlled way of exiting (not very
  clean, but it is how it is)[1].

  This will happen for example if you try to start unity8-dash directly (not 
through upstart) from a ssh shell in the phone, i.e
  phablet-shell
  stop unity8-dash
  unity8-dash

  And it may happen after a unity8 crash.

  In general we think that it's not a pressing issue users have since
  there seems to have not been any report of unity8-dash failing to
  start, but we're creating this bug to track it from time to time and
  make sure it doesn't get worse.

  [1] Qt platform plugins (also know as QPA) don't have a way to say
  they had a problem initiating themselves, Qt code is prepared for the
  QPlatformIntegrationPlugin::create() function to return, but all it
  does when that happens is call qFatal anyway [2]

  [2]
  
http://code.qt.io/cgit/qt/qtbase.git/tree/src/gui/kernel/qguiapplication.cpp#n1132

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

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

[Touch-packages] [Bug 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

[Gerry Boland]

So is actual desired fix to not crash, just quit gracefully?

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

Title:
  clients crash with "UbuntuClientIntegration: connection to Mir server
  failed."

Status in mir package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  According to
  https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
  it seems to be common-ish.

  This happens when unity8-dash can't find unity8 (mir server) and
  crashing (via QFatal) is our controlled way of exiting (not very
  clean, but it is how it is)[1].

  This will happen for example if you try to start unity8-dash directly (not 
through upstart) from a ssh shell in the phone, i.e
  phablet-shell
  stop unity8-dash
  unity8-dash

  And it may happen after a unity8 crash.

  In general we think that it's not a pressing issue users have since
  there seems to have not been any report of unity8-dash failing to
  start, but we're creating this bug to track it from time to time and
  make sure it doesn't get worse.

  [1] Qt platform plugins (also know as QPA) don't have a way to say
  they had a problem initiating themselves, Qt code is prepared for the
  QPlatformIntegrationPlugin::create() function to return, but all it
  does when that happens is call qFatal anyway [2]

  [2]
  
http://code.qt.io/cgit/qt/qtbase.git/tree/src/gui/kernel/qguiapplication.cpp#n1132

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

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

[Touch-packages] [Bug 1655687] Re: webbrowser-app graphics garbled in unity8 session

[Gerry Boland]

I'm adding Oxide to the bug, as the browser chrome is being rendered ok.
I also see these strings in the browser log:

[0111/095625:ERROR:layer_tree_host_impl.cc(2189)] Forcing zero-copy tile 
initialization as worker context is missing
[0111/095625:ERROR:oxide_compositor_gpu_shims.cc(258)] Error creating EGLImage: 
EGL_BAD_PARAMETER
Cannot find EGLConfig, returning null config

Which make sense as those kinds of visual artefacts are typically GPU
tiling problems.

** Also affects: oxide-qt (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/1655687

Title:
  webbrowser-app graphics garbled in unity8 session

Status in oxide-qt package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Web pages appear garbled and graphically corrupt when displayed on the
  webbrowser-app under unity8 on a Kabylake Dell Inspiron 5378 using the
  default unity8 session currently included with Ubuntu 16.10:


  This behavior occurs 100% of the time on this hardware under unity8
  and does not occur when webbrowser-app is started under unity7.

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

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

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

[Gerry Boland]

I'm failing to reproduce this unfortunately. I'm also failing to create
a libertine container. It was failing due to bug 1653973, so I installed
silo 2341, but now it fails with:

Failed to download http://images.linuxcontainers.org//meta/1.0/index-user
LxcContainer.py:254: ERROR: create_libertine_container(): Failed to create 
container
libertine-container-manager:94: ERROR: create():Failed to create container

This is odd, as networking is fine, and I can wget that URL
successfully.


I've left my AMD laptop running with unity8 for hours yesterday, and no crash.

Can you paste more of that unity8.log please? From the output, it
indicates that the physical display state changed somehow, or at least
Mir thinks it did. Disabling screen blanking was a good idea, but are
you sure it worked? How did you try it?

Also, what GPU have you got?

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

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

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

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

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

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

[Touch-packages] [Bug 1649077] Re: [regression] OSK appears blank and/or flickers in the lock screen

[Gerry Boland]

** Branch linked: lp:~gerboland/qtmir/initial-surface-expose

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

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

** Changed in: qtmir
   Status: Confirmed => In Progress

** Changed in: qtmir
 Assignee: (unassigned) => Gerry Boland (gerboland)

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

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

Title:
  [regression] OSK appears blank and/or flickers in the lock screen

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  After using OTA-14 a while, the OSK starts to exhibit a strange
  behaviour.

  1. It appears blank after a while in the lock screen. You can still
  press randomly which then makes the OSK to appear fully. When you
  press a character again it starts to flicker.

  2. OSK starts to flicker similar to bug #1590765 which was fixed in
  OTA-12. It seems to have resurfaced in OTA-14.

  Systems Info:
  OTA-14 Stable Channel
  Devices: E4.5, E5

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

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

[Touch-packages] [Bug 1655052] Re: unity8-greeter aborts at start in libprotobuf

[Gerry Boland]

Please paste in the output of 
dpkg -l | grep mir
and the contents of the greeter process log around the time of this crash.

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

Title:
  unity8-greeter aborts at start in libprotobuf

Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Machine is a MacBook with intel graphics.
  After installing unity8-greeter and rebooting all I get is a black screen and 
this core dump. I've heard this from other people too by now so it doesn't seem 
to be my machine only.

  #0  0x7f483d554428 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
  #1  0x7f483d55602a in __GI_abort () at abort.c:89
  #2  0x7f483d5967ea in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7f483d6af2e0 "*** Error in `%s': %s: 0x%s ***\n") at 
../sysdeps/posix/libc_fatal.c:175
  #3  0x7f483d59ee0a in malloc_printerr (ar_ptr=, 
ptr=, str=0x7f483d6ac0ca "free(): invalid size", action=3) at 
malloc.c:5004
  #4  _int_free (av=, p=, have_lock=0) at 
malloc.c:3865
  #5  0x7f483d5a298c in __GI___libc_free (mem=) at 
malloc.c:2966
  #6  0x7f47faafb901 in 
google::protobuf::internal::DestroyDefaultRepeatedFields() () from 
/usr/lib/x86_64-linux-gnu/libprotobuf.so.9
  #7  0x7f483320f72b in google::protobuf::ShutdownProtobufLibrary() () from 
/usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.9
  #8  0x7f48338df0d9 in ?? () from 
/usr/lib/x86_64-linux-gnu/libmirprotobuf.so.3
  #9  0x7f483fc0bc17 in _dl_fini () at dl-fini.c:235
  #10 0x7f483d558ff8 in __run_exit_handlers (status=0, listp=0x7f483d8e25f8 
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
  #11 0x7f483d559045 in __GI_exit (status=) at exit.c:104
  #12 0x7f483d53f837 in __libc_start_main (main=0x4077e0, argc=2, 
argv=0x7ffd3ee9bab8, init=, fini=, 
rtld_fini=, stack_end=0x7ffd3ee9baa8)
  at ../csu/libc-start.c:325
  #13 0x00407bd9 in _start ()

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

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

[Touch-packages] [Bug 1413121] Re: MainView is missing an API to dynamically set supported orientations

[Gerry Boland]

** Tags added: unity8

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

Title:
  MainView is missing an API to dynamically set supported orientations

Status in QtMir:
  Confirmed
Status in qtubuntu:
  New
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  The MainView offered an api to lock the app to portrait. When
  shellRotation landed, that was replaced by entries in the .desktop
  file (X-Ubuntu-Supported-Orientations).

  However, still this isn't really enough for some use cases. For
  example an app might want to be locked to portrait while showing the
  main menu, but when displaying certain content enable allowing
  rotation.

  For that, there would be the need of an API, similar to the .desktop
  entries, but changeable at runtime.

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

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

[Touch-packages] [Bug 1504551] Re: Text input popover and selection cursors not oriented properly in shell

[Gerry Boland]

** Tags added: unity8

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

Title:
  Text input popover and selection cursors not oriented properly in
  shell

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  See attached screenshot, tapping twice on the password entry shows the
  text overlay, but it's in hardware orientation, not the real one.

  It's been fixed for dialogs, but we must've missed popovers somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 
1.3.1627+15.10.20150908-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  9 15:17:56 2015
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1462489] Re: Allow apps to keep the screen on

[Gerry Boland]

** Tags added: unity8

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

Title:
  Allow apps to keep the screen on

Status in Canonical System Image:
  Fix Released
Status in Canonical Click Reviewers tools:
  Fix Released
Status in Ubuntu Developer Portal:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Support an interface in QML and HTML to allow an app to keep the
  screen on while the app is active. This has come up in several
  scenarios, such as an ebook reader, a clock in night mode.

  First step is to hook up QtSystemInfo screenSaverEnabled

  One solution to inhibit the screen blanking:

  Add a new dbus rule to the default template
  Provide a mediator (unity8) to control this, so it can restore the screen 
blanking when the app is not active or has been closed
  Prompt the user for confirmation the first time the app accesses it
  use the trust store to avoid prompts each time
  add to the System settings Other app access panel an entry for Screen or 
Display so the setting could be revoked

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

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

[Touch-packages] [Bug 1510968] Re: external monitor grid units are not set correctly

[Gerry Boland]

** Tags added: unity8

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

Title:
  external monitor grid units are not set correctly

Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  external monitor grid units are not set correctly so the desktop is
  incorectly scaled.

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

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

[Touch-packages] [Bug 1558663] Re: Ubuntu Components is hard on the disk and CPU when loading images

[Gerry Boland]

** Tags added: unity8

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

Title:
  Ubuntu Components is hard on the disk and CPU when loading images

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
   * Take the following simple example of a listview with an image.
   * run it with strace qmlscene
   * scroll the list to the bottom

  
  When not including "import Ubuntu.Components 1.3" there is exactly one disk 
access to load the image
  open("/home/tsdgeos_work/test/face.png", O_RDONLY|O_CLOEXEC) = 19

  When including "import Ubuntu.Components 1.3" there are around 500
  disk access including stats for the file and listing the directory
  containing the file (see disk_access file).

  Also for each of those directory listings we're also creating and
  destroying the same QRegExp again and again.

  I understand that some of this overhead is needed since we have that
  thing that loads the best possible file for the given grid units, but
  doing it again and again for the same file seems a bit of overkill,
  maybe we could cache that?

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

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

[Touch-packages] [Bug 1621370] Re: UITK on Intel i915 (atom)is very slow

[Gerry Boland]

** Tags added: unity8

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

Title:
  UITK on Intel i915 (atom)is very slow

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  use unity8 and mir on computers with processor based on i915 (ex.atom
  and old processors) is impossible because it is very slow due to UITK.
  when you open the application takes a long time and any action on the
  pop-up locks the computer

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

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

[Touch-packages] [Bug 1647415] Re: units.gu() emits changed signal before completion

[Gerry Boland]

** Tags added: unity8

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

Title:
  units.gu() emits changed signal before completion

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Consider this snippet of code:

  ---
  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  property int bla: units.gu(10)
  onBlaChanged: print("bla changed", bla);

  property int blubb: 80
  onBlubbChanged: print("blubb changed", blubb);

  Component.onCompleted: print("completed", bla);
  }
  --

  The output of this is:

  qml: bla changed 80
  qml: completed 80

  the changed signal should not be emitted before completion, given it
  is its initial value and not actually changed.

  The current behavior triggers all the onChanged handlers when there's
  units.gu() involved, which results in things like change animations
  being played at startup and lots of wasted cpu cycles for evaluating
  all those changed events.

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

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

[Touch-packages] [Bug 1585723] Re: UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

[Gerry Boland]

** Tags added: unity8

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

Title:
  UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I'm digging into unity8 performance problems on older generation Intel
  GPUs - specifically i915 Atom GPUs.

  I've tested a simple QML file with a single empty UbuntuShape in it:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Rectangle {
  width: 400
  height: 300
  color: "blue"

  UbuntuShape {}
  }

  Running it with INTEL_DEBUG=perf env var set, I get this output:

  i915_program_error: Exceeded max ALU instructions (76 out of 64)
  ENTER FALLBACK 1: Program
  Mapping a busy BO, causing a stall on the GPU.

  which implies that MESA was unable to compile one of the UbuntuShape
  shaders as it created more ALU instructions than the GPU could deal
  with. MESA falls back to CPU rendering as a result.

  The GPU stall message I guess is related to that.

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

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

[Touch-packages] [Bug 1573118] Re: "units" context property is app-global

[Gerry Boland]

** Tags added: unity8

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

Title:
  "units" context property is app-global

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  The "units" context property has no idea about which screen it is on,
  making it impossible to have different grid unit values per window in
  a single app. This would be the case, for example, when one app has
  multiple windows on different screens.

  We're landing a workaround for this for use in unity8 (the only case
  supported today where a single app has multiple windows on different
  screens).

  Long-term we might need UITK 2.0 to fix this proper.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qml-module-ubuntu-components 1.3.1918+16.04.20160404-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 21 17:54:33 2016
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1542029] Re: New windows have incorrect dimensions on launch (not the dimensions the app specifies)

[Gerry Boland]

Unity8 is overriding the client-requested window size in phone/tablet
mode, but this shouldn't be happening for desktop mode.

We also need to save the client-requested window geometry in case shell
later wishes to apply that.

Agreed I'd like a specific example

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

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

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

Title:
  New windows have incorrect dimensions on launch (not the dimensions
  the app specifies)

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in Ubuntu UX:
  Invalid
Status in miral package in Ubuntu:
  Incomplete
Status in puritine package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  currently, the shell is picking some random window size.
  They are about to change it to be close to what is on the phone - as this 
will match most apps.
  however the Xapps should have something "larger"

  shell is landing the ability to communicate to it, the desire default
  first launch window size

  it would also be good to have design input on this selection

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

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

[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop

[Gerry Boland]

Could you also share hte output of

xargs -n 1 -0 < /proc/`pidof unity8`/enviro | grep QT_

in case there are Qt dynamic scaling env vars set in your environment
too. (e.g. QT_DEVICE_PIXEL_RATIO, QT_AUTO_SCREEN_SCALE_FACTOR,
QT_SCALE_FACTOR, QT_SCREEN_SCALE_FACTORS)

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

Title:
  incorrect UI scale on high-resolution desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop

[Gerry Boland]

Oops, safer to use grep:

xargs -n 1 -0 < /proc/`pidof unity8`/environ | grep GRID_UNIT

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

Title:
  incorrect UI scale on high-resolution desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop

[Gerry Boland]

Contents of $HOME/.cache/upstart/unity8.log might be handy too

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

Title:
  incorrect UI scale on high-resolution desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop

[Gerry Boland]

Hey,
this is weird. Would you be able to open a terminal and run the following 
command:

xargs -n 1 -0 < /proc/`pidof unity8`/environ | ag GRID_UNIT

(it prints all the environment variables that the unity8 process has, and just 
returns the GRID_UNIT_PX one)
Thanks
-G

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

Title:
  incorrect UI scale on high-resolution desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

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

[Gerry Boland]

Yeah the unity8 log makes me suspect qtmir, it deals with disabling the
display ok, but enabling it doesn't yield 2 screens again

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

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

** Changed in: qtmir
   Importance: Undecided => High

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

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

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

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

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

  What should happen:
  it should work as expected

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

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

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

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

[Gerry Boland]

QtMir/Unity8 is designed to deal with spanning displays - it is actually
cloned displays it needs work to support!

@jonas Could you give us a means to test this behaviour?

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

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

Status in Canonical System Image:
  New
Status in Light Display Manager:
  New
Status in Mir:
  Incomplete
Status in lightdm package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

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

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

  What should happen:
  it should work as expected

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

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

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

[Touch-packages] [Bug 1628646] Re: new windows not respecting width and height

[Gerry Boland]

Can you give me steps to repro the problem clearly?

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

Title:
  new windows not respecting width and height

Status in Canonical System Image:
  New
Status in qtmir package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  testing on unity8 xenial + overlay + silo 2010 browser multi window

  The browser code attempts to create new windows at the same size as
  their parent window. However the windows are always created in unity8
  at the size of the initial parent window, not the current size of the
  window if it's resized.

  Here is the code:
  
https://bazaar.launchpad.net/~system-apps-team/webbrowser-app/multiple-windows/revision/1495

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

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

[Touch-packages] [Bug 1625853] Re: Mouse cursor disappears (or just never changes) when entering the windows of Qt apps

[Gerry Boland]

Why is there not a better fallback cursor than a fully blank one?

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

Title:
  Mouse cursor disappears (or just never changes) when entering the
  windows of Qt apps

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

Bug description:
  To reproduce:
  1) Open qtcreator in mir
  2) Move mouse around window

  Expect:
  Able to see cursor

  Result:
  Cursor goes away as if disabled.

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

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

[Touch-packages] [Bug 1624407] Re: Closing an application doesn’t actually close it, it merely requests all its windows to be closed

[Gerry Boland]

AFAICS Mir has means to ask clients to close windows, but I don't see an
API to ask the client itself to quit.

** No longer affects: unity (Ubuntu)

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

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

Title:
  Closing an application doesn’t actually close it, it merely requests
  all its windows to be closed

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

Bug description:
  Currently in unity8, when requesting to "Quit" a running application
  from the launcher, what happens is that qtmir goes through all its
  associated windows/surfaces, and closes them one by one. Supposedly,
  when the last window is closed, the application terminates itself (but
  this is not necessarily the case, see
  https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed-
  prop).

  This prevents application authors from doing proper cleanup before the
  app is closed. For example in Qt, the QCoreApplication::aboutToQuit()
  signal is emitted only after all windows have been closed, so the
  application doesn’t get a chance to e.g. save the list of open windows
  (real use case for multi-window browser application which saves the
  current session).

  This is similar to unity7’s implementation by the way, but I think
  it’s wrong. Surely there must be a way (maybe toolkit-specific) to
  request an app to terminate itself (and fall back to closing all
  windows if not).

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

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

[Touch-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

[Gerry Boland]

Note it is only Unity8 which is mixing GL and GLES calls, clients are
not doing that. Qt clients are only doing GL calls on desktop.

Nothing obvious comes to mind here.

It may be Qt's EGL configuration code is failing - code that QtUbuntu is
using. Another consumer of that same code is the EGL backend for the XCB
QPA plugin - the non-default - as usually the GLX backend is used.

Could someone with a problematic system log into Unity7, and for a simple qml 
file, run:
QT_XCB_GL_INTEGRATION=xcb_egl qmlscene ~/test.qml
and see does it fail?

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init

[Gerry Boland]

This issue was worked around, but with a far-from-ideal solution

** Also affects: lttng-ust (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

** Branch linked: lp:~dandrader/qtmir/no-lttng-on-tests

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

Title:
  deadlock in lttng_ust_init

Status in QtMir:
  Triaged
Status in lttng-ust package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Triaged
Status in ust package in Ubuntu:
  New

Bug description:
  Happens when running tests for
  https://code.launchpad.net/~dandrader/qtmir/content-hub-
  clipboard/+merge/303863 by CI.

  This is the backtrace of where it gets stuck:
  #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 
<_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51
  #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, 
the_map=) at dl-tls.c:778
  #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158
  #3 0x in lttng_ust_init () at lttng-ust-comm.c:369
  #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481
  #5 0x in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72
  #6 0x in _dl_init (env=, argv=, 
argc=, l=) at dl-init.c:30
  #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, 
env=0xbefff3dc) at dl-init.c:120
  #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3

  It gets stuck during initialization, more specifically, inside
  lttng_fixup_urcu_bp_tls()

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

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

[Touch-packages] [Bug 1596524] Re: /usr/bin/webbrowser-app:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

[Gerry Boland]

I'd be interested if this makes any impact:
https://code.launchpad.net/~gerboland/qtubuntu/eglconvenience-
retry/+merge/298114

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

Title:
  /usr/bin/webbrowser-
  
app:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

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

  started with 0.23+15.04.20160615-0ubuntu1
  similar signature than bug 1596523

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

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

[Touch-packages] [Bug 1605513] Re: Touchpad scrolling is disproportionately faster than mouse wheel scrolling

[Gerry Boland]

Ah no, I'm reading the API wrong (kudos to faenil for correcting me):
QPoint pixelDelta
is in integers, as are all QWheelEvent calculations. So that's not going to 
work without breaking Qt APIs, which is unlikely.

An alternative option might be to us Qt's support for native gesture
events - this is used on OS X. These do let Qt do Pan/Swipe gestures
with float precision.

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

Title:
  Touchpad scrolling is disproportionately faster than mouse wheel
  scrolling

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

Bug description:
  Touchpad scrolling is disproportionately faster than mouse wheel
  scrolling in Unity8 (web browser and system settings).

  I can only say this with confidence today because I implemented
  accurate smooth scrolling in Xmir yesterday, so I know how it should
  behave.

  It's possible QtMir is overreacting to the large number of events that
  touchpads generate compared to a mouse wheel, without taking into
  account the scroll magnitude of each one is smaller.

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

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

[Touch-packages] [Bug 1605513] Re: Touchpad scrolling is disproportionately faster than mouse wheel scrolling

[Gerry Boland]

Are you looking at the right code? I see this from Qt5.4 source
(qtbase/src/gui/kernel/qwindowsysteminterface.h)

static void handleWheelEvent(QWindow *w, const QPointF & local, const 
QPointF & global, QPoint pixelDelta, QPoint angleDelta, Qt::KeyboardModifiers 
mods = Qt::NoModifier, Qt::ScrollPhase phase = Qt::ScrollUpdate);
static void handleWheelEvent(QWindow *w, ulong timestamp, const QPointF & 
local, const QPointF & global, QPoint pixelDelta, QPoint angleDelta, 
Qt::KeyboardModifiers mods = Qt::NoModifier, Qt::ScrollPhase phase = 
Qt::ScrollUpdate);

Scroll units are floats. The line you're quoting is a QtMir internal
thing, which we mistakenly used ints for.

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

Title:
  Touchpad scrolling is disproportionately faster than mouse wheel
  scrolling

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

Bug description:
  Touchpad scrolling is disproportionately faster than mouse wheel
  scrolling in Unity8 (web browser and system settings).

  I can only say this with confidence today because I implemented
  accurate smooth scrolling in Xmir yesterday, so I know how it should
  behave.

  It's possible QtMir is overreacting to the large number of events that
  touchpads generate compared to a mouse wheel, without taking into
  account the scroll magnitude of each one is smaller.

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

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

[Touch-packages] [Bug 1594198] Re: Terminal app crashes with "Failed to load libGLESv2"

[Gerry Boland]

https://github.com/libhybris/libhybris/pull/316 has been landed. I can
remove the QtUbuntu workaround

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

Title:
  Terminal app crashes with "Failed to load libGLESv2"

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

Bug description:
  Most likely due to [1] (checking), terminal app crashes on startup,
  printing:

  > Failed to load libGLESv2

  An example OOPS can be seen under [2].

  [1] 
https://code.launchpad.net/~gerboland/qtubuntu/adopt-more-eglconvenience2/+merge/295248
  [2] https://errors.ubuntu.com/oops/020da136-3673-11e6-9055-fa163eec78fa

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qtubuntu-android 0.62+15.04.20160527.1-0ubuntu1
  Uname: Linux 3.10.100-user-01767-gf5aa556-dirty aarch64
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Mon Jun 20 01:05:39 2016
  InstallationDate: Installed on 2016-06-18 (1 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160618-020304)
  SourcePackage: qtubuntu
  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/1594198/+subscriptions

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

[Touch-packages] [Bug 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]

[Gerry Boland]

Of course we will. We need to re-land the fix. It was reverted because
it broke something else, but that's been solved now. Sorry for the
delay, but it takes time to get things done just right.

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

Title:
  Unity8-dash on Intel Atom graphics crashes and restarts continuously
  [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) ==
  EGL_TRUE"]

Status in Mir:
  Invalid
Status in qtubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Qt clients are failing to create an egl context when running on Intel
  Pineview systems under Mir.

  eglCreateContext fails with a EGL_BAD_MATCH error code.

  When it fails, Qt tries to delete & recreate the context, which then
  crashes the client (bug 1580118)

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

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt characters in Unity8

[Gerry Boland]

That would imply the distance field texture is corrupted.

As a note to myself, there is a nice glyph test application in this bug:
https://bugreports.qt.io/browse/QTBUG-49490

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

Title:
  Randomly corrupt characters in Unity8

Status in gnome-desktop package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt characters in Unity8

[Gerry Boland]

Also worth noting, there are env vars:
QT_DEFAULT_TEXTURE_GLYPH_CACHE_WIDTH & HEIGHT to set the size of the glyph 
cache. Need to see what size texture Qt is creating, perhaps it is creating one 
too large for the 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/1583088

Title:
  Randomly corrupt characters in Unity8

Status in gnome-desktop package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt characters in Unity8

[Gerry Boland]

If you can reproduce this relative easily, could you try setting
QML_USE_GLYPHCACHE_WORKAROUND=1 for unity8. This should do the trick:

stop unity8 && start unity8 QML_USE_GLYPHCACHE_WORKAROUND=1

Can also try these:
QSG_DISTANCEFIELD_ANTIALIASING=subpixel-lowq or gray

Need to determine if that text is being drawn by the DistanceField approach, or 
using the "native" rendering technique
http://doc.qt.io/qt-5/qml-qtquick-text.html#renderType-prop

If distance field, perhaps the contents of the distance field texture is
corrupted somehow. Grabbing the contents of the texture to visually
verify it is corrupt or not would be my next step. apitrace might be
able to grab the texture. Else would need to write code..


** Changed in: gnome-desktop (Ubuntu)
   Status: Confirmed => 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/1583088

Title:
  Randomly corrupt characters in Unity8

Status in gnome-desktop package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

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

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

[Touch-packages] [Bug 1596041] Re: corrupted text various elements on unity8-desktop

[Gerry Boland]

QPA has nothing to do with rendering itself, and only selects the
default unix font renderer for Qt to use.

We need information on your hardware, linux install, GPU, etc. I suspect
a MESA bug.

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

Title:
  corrupted text various elements on unity8-desktop

Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Seen 2 varities of this problem.

  #1) while running unity8 desktop and clicking for tooltip on launcher on my 
open applications, I see the first letter corrupted in the action words "Unpin" 
and "Quit" (so "U" and "Q" respectively are what is corrupted.
  Interesting is the Application's name is not corrupted.
  This seems intermittent as well

  #2) selecting "Shut down" provides the usual user prompt to cancel or power 
off, in this case only the "ff"s were corrupted
  See attached image for this case

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

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

[Touch-packages] [Bug 1585723] Re: UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

[Gerry Boland]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

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

Title:
  UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I'm digging into unity8 performance problems on older generation Intel
  GPUs - specifically i915 Atom GPUs.

  I've tested a simple QML file with a single empty UbuntuShape in it:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Rectangle {
  width: 400
  height: 300
  color: "blue"

  UbuntuShape {}
  }

  Running it with INTEL_DEBUG=perf env var set, I get this output:

  i915_program_error: Exceeded max ALU instructions (76 out of 64)
  ENTER FALLBACK 1: Program
  Mapping a busy BO, causing a stall on the GPU.

  which implies that MESA was unable to compile one of the UbuntuShape
  shaders as it created more ALU instructions than the GPU could deal
  with. MESA falls back to CPU rendering as a result.

  The GPU stall message I guess is related to that.

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

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

[Touch-packages] [Bug 1594198] Re: Terminal app crashes with "Failed to load libGLESv2"

[Gerry Boland]

https://github.com/libhybris/libhybris/pull/316 has a better solution to
this issue for now

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

Title:
  Terminal app crashes with "Failed to load libGLESv2"

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

Bug description:
  Most likely due to [1] (checking), terminal app crashes on startup,
  printing:

  > Failed to load libGLESv2

  An example OOPS can be seen under [2].

  [1] 
https://code.launchpad.net/~gerboland/qtubuntu/adopt-more-eglconvenience2/+merge/295248
  [2] https://errors.ubuntu.com/oops/020da136-3673-11e6-9055-fa163eec78fa

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qtubuntu-android 0.62+15.04.20160527.1-0ubuntu1
  Uname: Linux 3.10.100-user-01767-gf5aa556-dirty aarch64
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Mon Jun 20 01:05:39 2016
  InstallationDate: Installed on 2016-06-18 (1 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160618-020304)
  SourcePackage: qtubuntu
  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/1594198/+subscriptions

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

[Touch-packages] [Bug 1594198] Re: Terminal app crashes with "Failed to load libGLESv2"

[Gerry Boland]

Digging into the actual root cause, QOpenGLES3Helper has QLibrary load
"libGLESv2.so" but this is failing. Using LD_DEBUG=libs you can see:

  5646: find library=libGLESv2.so [0]; searching
  5646:  search path=/vendor/lib:/system/lib
(LD_LIBRARY_PATH)
  5646:   trying file=/vendor/lib/libGLESv2.so
  5646:   trying file=/system/lib/libGLESv2.so
  5646:  search cache=/etc/ld.so.cache
  5646:  search 
path=/lib/arm-linux-gnueabihf:/usr/lib/arm-linux-gnueabihf/vfp:/usr/lib/arm-linux-gnueabihf:/lib/tls/v7l/neon/vfp:/lib/tls/v7l/neon:/lib/tls/v7l/vfp:/lib/tls/v7l:/lib/tls/neon/vfp:/lib/tls/neon:/lib/tls/vfp:/lib/tls:/lib/v7l/neon/vfp:/lib/v7l/neon:/lib/v7l/vfp:/lib/v7l:/lib/neon/vfp:/lib/neon:/lib/vfp:/lib:/usr/lib/tls/v7l/neon/vfp:/usr/lib/tls/v7l/neon:/usr/lib/tls/v7l/vfp:/usr/lib/tls/v7l:/usr/lib/tls/neon/vfp:/usr/lib/tls/neon:/usr/lib/tls/vfp:/usr/lib/tls:/usr/lib/v7l/neon/vfp:/usr/lib/v7l/neon:/usr/lib/v7l/vfp:/usr/lib/v7l:/usr/lib/neon/vfp:/usr/lib/neon:/usr/lib/vfp:/usr/lib
 (system search path)
and off it goes searching all those paths.

Problem is the library is actually called libGLESv2.so.2 on hybris. Qt
isn't able to locate the file as a result. I don't know if the library
should be called libGLESv2.so only for GLESv3, but if so, it would
explain a lot.

For fun, I symlinked libGLESv2.so.2 to libGLESv2.so, for which I got this error:
"OpenGL ES 3.0 entry points not found"
which makes sense as hybris is only exporting GLESv2 symbols, and nothing from 
GLESv3 yet.

So my patch above is actually the best solution until hybris supports
GLESv3.

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

Title:
  Terminal app crashes with "Failed to load libGLESv2"

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

Bug description:
  Most likely due to [1] (checking), terminal app crashes on startup,
  printing:

  > Failed to load libGLESv2

  An example OOPS can be seen under [2].

  [1] 
https://code.launchpad.net/~gerboland/qtubuntu/adopt-more-eglconvenience2/+merge/295248
  [2] https://errors.ubuntu.com/oops/020da136-3673-11e6-9055-fa163eec78fa

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qtubuntu-android 0.62+15.04.20160527.1-0ubuntu1
  Uname: Linux 3.10.100-user-01767-gf5aa556-dirty aarch64
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Mon Jun 20 01:05:39 2016
  InstallationDate: Installed on 2016-06-18 (1 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160618-020304)
  SourcePackage: qtubuntu
  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/1594198/+subscriptions

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

[Touch-packages] [Bug 1594198] Re: Terminal app crashes with "Failed to load libGLESv2"

[Gerry Boland]

My eglconvenience branch does cause this, but annoyingly by doing the
correct thing.

Before eglconvenience, we hardcoded GLESv2.0 into QtUbuntu. With
eglconvenience, we query the GL version string and correctly fetch the
GL version the driver supports. On several of our devices, that is
actually GLESv3.0

If GLESv3 is available (not all devices have it), Qt tries to use it
instead of alternative GLv2 calls (as they're usually better). It does
this by creating a QOpenGLES3Helper class internally, when particular GL
calls are made.

Most of our pure QML apps don't end up calling any of those particular
GL calls, so work just fine. But Terminal app does.

QOpenGLES3Helper on creation uses QLibrary to load libGLESv2.so and
resolve some symbols in it. This is failing for some reason, and prints
the "Failed to load libGLESv2.so" message as a result. I suspect this
fail has to do with lp:1490956

I've proposed lp:~gerboland/qtubuntu/disable-gles3-for-now as a
workaround for this issue

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

Title:
  Terminal app crashes with "Failed to load libGLESv2"

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

Bug description:
  Most likely due to [1] (checking), terminal app crashes on startup,
  printing:

  > Failed to load libGLESv2

  An example OOPS can be seen under [2].

  [1] 
https://code.launchpad.net/~gerboland/qtubuntu/adopt-more-eglconvenience2/+merge/295248
  [2] https://errors.ubuntu.com/oops/020da136-3673-11e6-9055-fa163eec78fa

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qtubuntu-android 0.62+15.04.20160527.1-0ubuntu1
  Uname: Linux 3.10.100-user-01767-gf5aa556-dirty aarch64
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Mon Jun 20 01:05:39 2016
  InstallationDate: Installed on 2016-06-18 (1 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160618-020304)
  SourcePackage: qtubuntu
  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/1594198/+subscriptions

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

[Touch-packages] [Bug 1591391] [NEW] [desktop] Launcher bounces any time you install/remove a package

[Gerry Boland]

Public bug reported:

Using Unity8 as desktop, using Terminal app, the Launcher pops out
quickly any time you install/remove any package.

To repro:
  apt-get install  

It should really only pop out when something in the Launcher changes

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

Title:
  [desktop] Launcher bounces any time you install/remove a package

Status in unity8 package in Ubuntu:
  New

Bug description:
  Using Unity8 as desktop, using Terminal app, the Launcher pops out
  quickly any time you install/remove any package.

  To repro:
apt-get install  

  It should really only pop out when something in the Launcher changes

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

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

[Touch-packages] [Bug 1400580] Re: Color Inverse on display. Toggle Negative Image

[Gerry Boland]

Hi Mikodo,
thank you for your messages on this topic. Accessibility is something we need 
to work on for Unity8. We have plenty to do, from the visual assistance 
features you've mentioned, to proper keyboard navigation and text-to-speech 
support. We have a solid list of TODOs (we had a meeting on this topic only 
this week), we just need to get to work.

I've been doing desktops since the Unity2d days, which had reasonably
good accessibility support. We intend to make Unity8 even better.

The unfortunate reality is that features like convergence do tend to get
more business focus than important usability features. It is messages
like yours that give us not only the motivation but also persuasive
arguments and evidence ("users are asking for this") to give more
resources to this topic.

Thanks for commenting here. We'll be in touch when we've features ready for 
testing.
-G

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

Title:
   Color Inverse on display. Toggle Negative Image

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  I would like to see a feature that allowed Unity8, to easily inverse
  the desktop colors.  To be able to easily turn on and off a negative
  (inverse) display of the desktop. For now, it can be done with X
  (xcalib). It would be nice to see Unity8 do this natively, instead of
  Ubuntu users needing this feature hoping, X-11 support will always be
  available.

  This is a feature I use, due to impaired eye-sight.

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

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