[Touch-packages] [Bug 1678299] [NEW] Search in app drawer doens't seem to look in many fields

[Daniel d'Andrada]

Public bug reported:

1 - search for "Text Editor"

You get the gedit icon, which has a "Text Editor" caption/name

2 - search for "gedit"

You get nothing at all.

Looks like app drawer search is not looking into all desktop file fields
or something. 1 & 2 works in unity7 dash just fine.

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

Title:
  Search in app drawer doens't seem to look in many fields

Status in unity8 package in Ubuntu:
  New

Bug description:
  1 - search for "Text Editor"

  You get the gedit icon, which has a "Text Editor" caption/name

  2 - search for "gedit"

  You get nothing at all.

  Looks like app drawer search is not looking into all desktop file
  fields or something. 1 & 2 works in unity7 dash just fine.

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

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

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

[Daniel d'Andrada]

Have a fix for it. Just gotta update qtmir tests now before I can
propose it for merging.

** Branch linked: lp:~dandrader/qtmir/multiSessionApp

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

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

Status in Canonical System Image:
  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 1673415] Re: QDockWidgets don't work at all

[Daniel d'Andrada]

Latest landings improved the situation but this bug is not completely
fixed yet.

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

** Changed in: unity8 (Ubuntu)
 Assignee: Daniel d'Andrada (dandrader) => (unassigned)

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

Title:
  QDockWidgets don't work at all

Status in qtubuntu package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  How to reproduce:
   * Install tiled
   * Start tiled
   * Press the small square button next to properties
   * That should undock the properties widget, make it a window and you should 
be able to drag it freely around the desktop, that doesn't happen
   * Alternatively, drag the properties widget from the "properties" text, 
you'll be able to drag it, but only inside the window, instead of around the 
desktop, and once you release it, you can't drag it anymore

  To "reset" the docked status, remove
  ~/.config/mapeditor.org/tiled.conf

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

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

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

[Daniel d'Andrada]

** Changed in: unity8 (Ubuntu)
   Status: In Progress => 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/1675448

Title:
  Unity 8 doesnt 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 1675448] Re: Unity 8 doesnt allow multiple mir connections from an application instance

[Daniel d'Andrada]

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

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

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

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

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

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

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

   Proposed solution 

  Related to bug #1589637

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

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

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

[Touch-packages] [Bug 1589637] Re: Unable to open multiple instances of the same app

[Daniel d'Andrada]

** Changed in: qtmir (Ubuntu)
   Status: Triaged => 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/1589637

Title:
  Unable to open multiple instances of the same app

Status in Canonical System Image:
  Triaged
Status in qtmir package in Ubuntu:
  In Progress
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  You're unable to open two instances of the same app. Such as gedit or
  firefox.

  qtmir needs instance-based signals: app instance started, app instance 
stopped, etc
  As in 
http://bazaar.launchpad.net/~indicator-applet-developers/ubuntu-app-launch/trunk.16.10/view/head:/libubuntu-app-launch/registry.h#L77

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

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

[Touch-packages] [Bug 1672337] Re: [unity8] can't restore an app if you minimize it while a child window, menu or context menu is opened

[Daniel d'Andrada]

Looking at the logs, when the top-level surface is minimized its child
still keeps focused and in the same state. Not sure if the child should
also go to minimized state (probably yes) but I'm sure it should not be
kept focused.

This looks like a miral bug.

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

** Also affects: miral (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/1672337

Title:
  [unity8] can't restore an app if you minimize it while a child window,
  menu or context menu is opened

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

Bug description:
  ubuntu 17.04 unity8

  [unity8] can't restore an app if you minimize it while a child window,
  menu or context menu is opened

  open whatever app, kate without Xmir, right click to open a context
  menu or just open a child window. minize the app then try to restore
  it by clicking on the icon on the launcher

  doesn't seem to work here

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

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

[Touch-packages] [Bug 1675572] Re: GUI of desktop apps are too big on high-dpi screens

[Daniel d'Andrada]

** Tags removed: patch

** Description changed:

  On a 13" 1080p display, fonts and UI in general is too big when running
  desktop Qt-based apps like konsole, QtCreator and Kate.
  
- Strangely, hardcoding to 96 dpi in qtubuntu fixes it.
+ Strangely, hardcoding logical dpi to 96 in qtubuntu fixes it.

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

Title:
  GUI of desktop apps are too big on high-dpi screens

Status in Canonical System Image:
  New
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  On a 13" 1080p display, fonts and UI in general is too big when
  running desktop Qt-based apps like konsole, QtCreator and Kate.

  Strangely, hardcoding logical dpi to 96 in qtubuntu fixes it.

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

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

[Touch-packages] [Bug 1675572] Re: GUI of desktop apps are too big on high-dpi screens

[Daniel d'Andrada]

** Patch added: "Hack that fixes qtubuntu to 96 dpi"
   
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1675572/+attachment/4843782/+files/fixed_96dpi.patch

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

Title:
  GUI of desktop apps are too big on high-dpi screens

Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  On a 13" 1080p display, fonts and UI in general is too big when
  running desktop Qt-based apps like konsole, QtCreator and Kate.

  Strangely, hardcoding to 96 dpi in qtubuntu fixes it.

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

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

[Touch-packages] [Bug 1675572] [NEW] GUI of desktop apps are too big on high-dpi screens

[Daniel d'Andrada]

Public bug reported:

On a 13" 1080p display, fonts and UI in general is too big when running
desktop Qt-based apps like konsole, QtCreator and Kate.

Strangely, hardcoding to 96 dpi in qtubuntu fixes it.

** Affects: qtubuntu (Ubuntu)
 Importance: Undecided
 Assignee: Daniel d'Andrada (dandrader)
 Status: In Progress

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

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

Title:
  GUI of desktop apps are too big on high-dpi screens

Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  On a 13" 1080p display, fonts and UI in general is too big when
  running desktop Qt-based apps like konsole, QtCreator and Kate.

  Strangely, hardcoding to 96 dpi in qtubuntu fixes it.

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

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

[Touch-packages] [Bug 1673415] Re: QDockWidgets don't work at all

[Daniel d'Andrada]

One of the prerequisite fixes is bug 1671424

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

Title:
  QDockWidgets don't work at all

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

Bug description:
  How to reproduce:
   * Install tiled
   * Start tiled
   * Press the small square button next to properties
   * That should undock the properties widget, make it a window and you should 
be able to drag it freely around the desktop, that doesn't happen
   * Alternatively, drag the properties widget from the "properties" text, 
you'll be able to drag it, but only inside the window, instead of around the 
desktop, and once you release it, you can't drag it anymore

  To "reset" the docked status, remove
  ~/.config/mapeditor.org/tiled.conf

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

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

[Touch-packages] [Bug 1671424] Re: qtmir destroys windows after requesting them to close

[Daniel d'Andrada]

** Changed in: qtmir (Ubuntu)
 Assignee: Lukáš Tinkl (lukas-kde) => Daniel d'Andrada (dandrader)

** Changed in: unity8 (Ubuntu)
 Assignee: Lukáš Tinkl (lukas-kde) => Daniel d'Andrada (dandrader)

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

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

Title:
  qtmir destroys windows after requesting them to close

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

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

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

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

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

[Touch-packages] [Bug 1671072] Re: Child windows don't get focused

[Daniel d'Andrada]

Turns out mir client got confused because the key release events sent by
unity8 where missing device id and timestamp.

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

** Changed in: mir
   Status: Incomplete => 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/1671072

Title:
  Child windows don't get focused

Status in Canonical System Image:
  In Progress
Status in Mir:
  Invalid
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  Invalid
Status in miral package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

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

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

[Touch-packages] [Bug 1671072] Re: Child windows don't get focused

[Daniel d'Andrada]

"""
Remember we use the 'Mir' project for tracking bugs primarily and not 'mir 
(Ubuntu)'. 
"""

unity8 & friends use an opposite policy.

"""
Although I don't know if either is actually relevant to this bug.
"""

My understanding is that XKBMapper::modifier_state on the client side
failing to update as expected and is therefore getting stuck with a ctrl
modifier

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

Title:
  Child windows don't get focused

Status in Canonical System Image:
  In Progress
Status in Mir:
  Incomplete
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  Incomplete
Status in miral package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

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

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

[Touch-packages] [Bug 1671424] Re: qtmir destroys windows after requesting them to close

[Daniel d'Andrada]

qtmir always destroys a window if it doesn't do so itself after being
requested to close.

Specially on desktop, requesting a window to close doesn't necessarily
mean it should destroy itself. It's a common idiom for an application to
just hide it instead, so it can be reused next time it's needed
(particularly for child windows).

Some might even stay around and just popup a dialog if there's modified
content that hasn't been saved yet.

So on desktop we should just send the close request without further
expectations. On phone though, we should keep the current behavior of
forcibly destroying the window if it doesn't comply after some time.

I wouldn't mix this bug with gtk+

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

Title:
  qtmir destroys windows after requesting them to close

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

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

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

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

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

[Touch-packages] [Bug 1671424] Re: qtmir destroys windows after requesting them to close

[Daniel d'Andrada]

** Summary changed:

- Applications fail to interrupt closing them
+ qtmir destroys windows after requesting them to close

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

Title:
  qtmir destroys windows after requesting them to close

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

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

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

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

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

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

[Daniel d'Andrada]

Maybe a fix for bug 1674749 is what you want.

-- 
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 1672722] Re: Unclickable gap between adjacent titlebar menus in Unity8

[Daniel d'Andrada]

** Description changed:

  Ubuntu 17.04 unity8
  
- i'm starting to hit more and more the gab in the menu (space between the
+ i'm starting to hit more and more the gap in the menu (space between the
  menu strings). clicking there won't open the submenu.
  
  launch kate native, hover the menu, click on the space between the menu
  strings. should not be such a thing. the space between the hitboxes
  should be 0 so you don't end up in situations like this
  
  see screenshot

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

Title:
  Unclickable gap between adjacent titlebar menus in Unity8

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

Bug description:
  Ubuntu 17.04 unity8

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

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

  see screenshot

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

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

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

[Daniel d'Andrada]

Don't know what's different in my system but here vlc won't launch. I
can launch firefox though which displays the same bug (menus immediately
disappearing) but it doesn't cause unity8 to 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/1672012

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

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

Bug description:
  ubuntu 17.04 unity8

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

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

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

[Touch-packages] [Bug 1671072] Re: Child windows don't get focused

[Daniel d'Andrada]

qtmir sends a key event to mir::scene::Surface->consume() without any
modifiers but it still arrives with a modifier when it surfaces from the
mir client lib in the client process.

Looks like some sort of key input validation in mir got confused and is
adding the modifier back even though the key ctrl got released.

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

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

Title:
  Child windows don't get focused

Status in Canonical System Image:
  In Progress
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  New
Status in miral package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

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

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

[Touch-packages] [Bug 1673415] Re: QDockWidgets don't work at all

[Daniel d'Andrada]

This actually goes deeper than simply supporting satellite window types.

** Summary changed:

- Missing support for satellite (Qt::Tool) windows
+ QDockWidgets don't work at all

** Branch linked: lp:~dandrader/unity8/satelliteWindow

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

Title:
  QDockWidgets don't work at all

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

Bug description:
  How to reproduce:
   * Install tiled
   * Start tiled
   * Press the small square button next to properties
   * That should undock the properties widget, make it a window and you should 
be able to drag it freely around the desktop, that doesn't happen
   * Alternatively, drag the properties widget from the "properties" text, 
you'll be able to drag it, but only inside the window, instead of around the 
desktop, and once you release it, you can't drag it anymore

  To "reset" the docked status, remove
  ~/.config/mapeditor.org/tiled.conf

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

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

[Touch-packages] [Bug 1673415] Re: QDockWidgets don't work at all

[Daniel d'Andrada]

Other issues being:
1 - we are forcibly killing windows that are closed. it's perfectly ok for an 
application to simply hide a window whose close button was clicked.

2 - this whole drag and drop behavior/interaction between the dockable
satellite/tool and the main window is still to be investigated.

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

Title:
  QDockWidgets don't work at all

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

Bug description:
  How to reproduce:
   * Install tiled
   * Start tiled
   * Press the small square button next to properties
   * That should undock the properties widget, make it a window and you should 
be able to drag it freely around the desktop, that doesn't happen
   * Alternatively, drag the properties widget from the "properties" text, 
you'll be able to drag it, but only inside the window, instead of around the 
desktop, and once you release it, you can't drag it anymore

  To "reset" the docked status, remove
  ~/.config/mapeditor.org/tiled.conf

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

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

[Touch-packages] [Bug 1673415] Re: QDockWidgets don't work at all

[Daniel d'Andrada]

We are missing support for satellite windows.

** Summary changed:

- QDockWidgets don't work at all
+ Missing support for satellite (Qt::Tool) windows

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

Title:
  Missing support for satellite (Qt::Tool) windows

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

Bug description:
  How to reproduce:
   * Install tiled
   * Start tiled
   * Press the small square button next to properties
   * That should undock the properties widget, make it a window and you should 
be able to drag it freely around the desktop, that doesn't happen
   * Alternatively, drag the properties widget from the "properties" text, 
you'll be able to drag it, but only inside the window, instead of around the 
desktop, and once you release it, you can't drag it anymore

  To "reset" the docked status, remove
  ~/.config/mapeditor.org/tiled.conf

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

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

[Touch-packages] [Bug 1673415] Re: QDockWidgets don't work at all

[Daniel d'Andrada]

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

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Changed in: qtubuntu (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/1673415

Title:
  Missing support for satellite (Qt::Tool) windows

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

Bug description:
  How to reproduce:
   * Install tiled
   * Start tiled
   * Press the small square button next to properties
   * That should undock the properties widget, make it a window and you should 
be able to drag it freely around the desktop, that doesn't happen
   * Alternatively, drag the properties widget from the "properties" text, 
you'll be able to drag it, but only inside the window, instead of around the 
desktop, and once you release it, you can't drag it anymore

  To "reset" the docked status, remove
  ~/.config/mapeditor.org/tiled.conf

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

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

[Touch-packages] [Bug 1673415] Re: QDockWidgets don't work at all

[Daniel d'Andrada]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

Title:
  QDockWidgets don't work at all

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  How to reproduce:
   * Install tiled
   * Start tiled
   * Press the small square button next to properties
   * That should undock the properties widget, make it a window and you should 
be able to drag it freely around the desktop, that doesn't happen
   * Alternatively, drag the properties widget from the "properties" text, 
you'll be able to drag it, but only inside the window, instead of around the 
desktop, and once you release it, you can't drag it anymore

  To "reset" the docked status, remove
  ~/.config/mapeditor.org/tiled.conf

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

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

[Touch-packages] [Bug 1671072] Re: Child windows don't get focused

[Daniel d'Andrada]

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

** Also affects: miral (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/1671072

Title:
  Child windows don't get focused

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

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

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

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

[Touch-packages] [Bug 1671072] Re: Child windows don't get focused

[Daniel d'Andrada]

Child window not getting qml active focus when it gets MirSurface focus
is one bug.

The top-level window is not getting qml active focus when its child is
closed because its MirSurface is also not getting focus. That's a
different bug and it's at qtmir/miral level (most likely miral).

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

Title:
  Child windows don't get focused

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

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

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

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

[Touch-packages] [Bug 1671072] Re: Child windows don't get focused

[Daniel d'Andrada]

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

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

Title:
  Child windows don't get focused

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

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

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

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

[Touch-packages] [Bug 1672931] Re: [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt (and so menus don't appear in the titlebar)

[Daniel d'Andrada]

*can 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/1672931

Title:
  [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of
  native GTK/Qt (and so menus don't appear in the titlebar)

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

Bug description:
  Qt & GTK apps on Unity8 are defaulting to Xmir instead of native
  GTK/Qt on Mir.

  I noticed a slight change in appearance and performance, but also:

  dan  25410  0.1  0.2 423316 38996 ?Sl   11:14   0:00 Xmir 
-rootless -displayfd 3 -mir org.gnome.Calculator
  dan  25456  1.8  0.5 606084 91736 ?Sl   11:14   0:03 Xmir 
-rootless -displayfd 3 -mir org.gnome.Nautilus
  dan  25611  1.7  0.2 345312 35520 ?Sl   11:18   0:00 Xmir 
-rootless -displayfd 3 -mir webbrowser-app_webbrowser-app_10

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

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

[Touch-packages] [Bug 1672931] Re: [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt (and so menus don't appear in the titlebar)

[Daniel d'Andrada]

I don't think unity8, qtubuntu or gtk-3.0 can't do anything about it.

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

Title:
  [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of
  native GTK/Qt (and so menus don't appear in the titlebar)

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

Bug description:
  Qt & GTK apps on Unity8 are defaulting to Xmir instead of native
  GTK/Qt on Mir.

  I noticed a slight change in appearance and performance, but also:

  dan  25410  0.1  0.2 423316 38996 ?Sl   11:14   0:00 Xmir 
-rootless -displayfd 3 -mir org.gnome.Calculator
  dan  25456  1.8  0.5 606084 91736 ?Sl   11:14   0:03 Xmir 
-rootless -displayfd 3 -mir org.gnome.Nautilus
  dan  25611  1.7  0.2 345312 35520 ?Sl   11:18   0:00 Xmir 
-rootless -displayfd 3 -mir webbrowser-app_webbrowser-app_10

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

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

[Touch-packages] [Bug 1672703] Re: some GTK+3 apps don't fill the window

[Daniel d'Andrada]

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

Fix for bug 1670390 should also contemplate the cases you describe here

** This bug has been marked a duplicate of bug 1670390
   Desktop applications don't get properly resized when launched in staged mode

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

Title:
  some GTK+3 apps don't fill the window

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 Unity 8

  some GTK+3 apps don't fill the window (see attached screenshots)
  launch eog or terminix without Xmir (if the window is bigger than the 
minimum? size) then you'll see transparent regions. if you then resize the 
window it fills the window and works fine until you close the app and then you 
get the same stuff the next time. try to launch the apps, resize the window, 
close (loop). other gtk3 apps seems to work fine such as like sol and such as 
like mines and such

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

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

[Touch-packages] [Bug 1665286] Re: [unity8] A ghost (shadow only) window opens with some app windows/menus

[Daniel d'Andrada]

** Changed in: qtubuntu (Ubuntu)
   Status: In Progress => 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/1665286

Title:
  [unity8] A ghost (shadow only) window opens with some app
  windows/menus

Status in Canonical System Image:
  In Progress
Status in Mir:
  Incomplete
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in miral package in Ubuntu:
  Incomplete
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8

  - install tiled, apt install tiled
  - Add "X-Ubuntu-XMir-Enable=false" to /usr/share/applications/tiled.desktop 
so that it doesn't get launched inside an xmir wrapper
  - launch tiled

  you'll see a transparent window opened beneath the main window called
  "Object Types Editor"

  see attached screenshot

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

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

[Touch-packages] [Bug 1665286] Re: [unity8] A ghost (shadow only) window opens with some app windows/menus

[Daniel d'Andrada]

** Description changed:

  ubuntu 17.04 unity8
  
- install tiled, apt install tiled
- launch tiled, you'll see a transparent window opened beneath the main window 
called "Object Types Editor"
+ - install tiled, apt install tiled
+ - Add "X-Ubuntu-XMir-Enable=false" to /usr/share/applications/tiled.desktop 
so that it doesn't get launched inside an xmir wrapper
+ - launch tiled
+ 
+ you'll see a transparent window opened beneath the main window called
+ "Object Types Editor"
  
  see attached screenshot

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

Title:
  [unity8] A ghost (shadow only) window opens with some app
  windows/menus

Status in Canonical System Image:
  In Progress
Status in Mir:
  Incomplete
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in miral package in Ubuntu:
  Incomplete
Status in qtubuntu package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8

  - install tiled, apt install tiled
  - Add "X-Ubuntu-XMir-Enable=false" to /usr/share/applications/tiled.desktop 
so that it doesn't get launched inside an xmir wrapper
  - launch tiled

  you'll see a transparent window opened beneath the main window called
  "Object Types Editor"

  see attached screenshot

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

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

[Touch-packages] [Bug 1527737] Re: Apps do not start if restarted quickly after closing

[Daniel d'Andrada]

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

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

** Changed in: qtmir (Ubuntu)
   Status: Triaged => 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/1527737

Title:
  Apps do not start if restarted quickly after closing

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  rc-proposed

  Close a running app and as quickly as possible open it again from the click 
scope
  the app will crash much of the time

  This happens on all apps I tried (dialer, messages, contacts, camera)
  This does not occur in OTA 8.5
  First noticed on 12/17

  I generally do not see a crash file although the first time I got one
  for contacts and the spinner

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

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

[Touch-packages] [Bug 1668429] Re: X apps (LibreOffice, Thunderbird) fail to launch with failure to open display (no Xmir is running)

[Daniel d'Andrada]

*qt5 apps I mean

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

Title:
  X apps (LibreOffice, Thunderbird) fail to launch with failure to open
  display (no Xmir is running)

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

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

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

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

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

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

[Touch-packages] [Bug 1668429] Re: X apps (LibreOffice, Thunderbird) fail to launch with failure to open display (no Xmir is running)

[Daniel d'Andrada]

With that "fix", now qt5 are unusable as they go under XMir.

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

Title:
  X apps (LibreOffice, Thunderbird) fail to launch with failure to open
  display (no Xmir is running)

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

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

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

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

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

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

[Touch-packages] [Bug 1665286] Re: [unity8] A ghost (shadow only) window opens with some app windows/menus

[Daniel d'Andrada]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

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

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

Title:
  [unity8] A ghost (shadow only) window opens with some app
  windows/menus

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Incomplete
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in miral package in Ubuntu:
  Incomplete
Status in qtubuntu package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8

  install tiled, apt install tiled
  launch tiled, you'll see a transparent window opened beneath the main window 
called "Object Types Editor"

  see attached screenshot

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

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

[Touch-packages] [Bug 1665286] Re: [unity8] A ghost (shadow only) window opens with some app windows/menus

[Daniel d'Andrada]

Ignore what I said earlier. I can reproduce the bug now.

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

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

Title:
  [unity8] A ghost (shadow only) window opens with some app
  windows/menus

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Incomplete
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in miral package in Ubuntu:
  Incomplete
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install tiled, apt install tiled
  launch tiled, you'll see a transparent window opened beneath the main window 
called "Object Types Editor"

  see attached screenshot

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

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

[Touch-packages] [Bug 1665286] Re: [unity8] A ghost (shadow only) window opens with some app windows/menus

[Daniel d'Andrada]

Can't reproduce it with trunk (released) versions of unity8 and qtmir.

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

Title:
  [unity8] A ghost (shadow only) window opens with some app
  windows/menus

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in miral package in Ubuntu:
  Incomplete
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install tiled, apt install tiled
  launch tiled, you'll see a transparent window opened beneath the main window 
called "Object Types Editor"

  see attached screenshot

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

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

[Touch-packages] [Bug 1670390] Re: Desktop applications don't get properly resized when launched in staged mode

[Daniel d'Andrada]

@vanvugt

Could you please explain why you invalidated the gtk+3.0 bug?

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

** Changed in: gtk+3.0 (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/1670390

Title:
  Desktop applications don't get properly resized when launched in
  staged mode

Status in Canonical System Image:
  In Progress
Status in QtMir:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce the issue:

  1 - Put unity8 in staged mode
  2 - Launch a desktop application like kate or qtcreator

  Expected outcome:
  The launched application takes up the entire stage area

  Actual outcome:
  The launched application starts with some windowed size it wanted to have, 
not filling the entire stage area. As if launched in desktop mode.

  Comments:
  Leaving staged mode and going back into it again gets the application to 
resize correctly and fill the entire stage area.

  Going from desktop to staged mode while the desktop application is
  already running also works fine.

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

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

[Touch-packages] [Bug 1670390] Re: Desktop applications don't get properly resized when launched in staged mode

[Daniel d'Andrada]

With gtk+ apps, when they get launched the ask for a resize. If in
tablet/phone mode unity8 will deny/ignore it, but gtk thinks the resize
was successful and renders as if its window had the size it requested
(that's with the qtmir and unity8 branches attached to this bug)

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Desktop applications don't get properly resized when launched in
  staged mode

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce the issue:

  1 - Put unity8 in staged mode
  2 - Launch a desktop application like kate or qtcreator

  Expected outcome:
  The launched application takes up the entire stage area

  Actual outcome:
  The launched application starts with some windowed size it wanted to have, 
not filling the entire stage area. As if launched in desktop mode.

  Comments:
  Leaving staged mode and going back into it again gets the application to 
resize correctly and fill the entire stage area.

  Going from desktop to staged mode while the desktop application is
  already running also works fine.

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

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

[Touch-packages] [Bug 1670442] Re: Improve splash screen behaviour

[Daniel d'Andrada]

The biggest problem with splash screens is on desktop: the first time an
application is launched Unity8 has no idea of its window constraints
(minimum, maximum and preferred sizes) so that it can choose an adequate
size for the splash screen.

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

Title:
  Improve splash screen behaviour

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

Bug description:
  Related to bug #1577641, we may want to improve the way the splash
  screen logic is implemented.

  The shell-managed splash screens serve as a way to provide immediate
  feedback for an application being launched, so that the user doesn't
  need to find out whether they failed to launch the app or the app's
  just slow to launch (or maybe even crashed on startup).

  My proposal is that:
  - we delay showing the splash screen for a very short interval (50ms to start 
with?)
  - *if* the splash screen is shown, it has to be shown for at least a certain 
time (500ms?) to avoid "flicker" between the splash screen and the app surface
  - if possible, let the user know that the app crashed/exited with an error 
and give the user an option to restart or close (long-term maybe also report 
the issue?)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170303.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar  6 18:33:05 2017
  InstallationDate: Installed on 2016-05-06 (303 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (104 days ago)

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

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

[Touch-packages] [Bug 1669432] Re: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

[Daniel d'Andrada]

The second issue is bug 1670390.

As for the crashes you mention, please be more specific (with a step-by-
step use case), preferably in a separate bug report.

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

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

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

Title:
  [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

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

Bug description:
  ubuntu 17.04 unity8
  [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

  turn desktop mode off, and now launch random apps and see how it
  behave

  kate, the icon bar don't quite works, try to hover or click on the new
  document, open etc icons. only works on the buttom side of the icons,
  probably the hitboxes or something are wrong, same with tiled. some
  gtk apps don't even resize to fullscreen (gnome-mines), and if you
  click on the menu icon the apps just crash etc

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

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

[Touch-packages] [Bug 1670390] [NEW] Desktop applications don't get properly resized when launched in staged mode

[Daniel d'Andrada]

Public bug reported:

Steps to reproduce the issue:

1 - Put unity8 in staged mode
2 - Launch a desktop application like kate or qtcreator

Expected outcome:
The launched application takes up the entire stage area

Actual outcome:
The launched application starts with some windowed size it wanted to have, not 
filling the entire stage area. As if launched in desktop mode.

Comments:
Leaving staged mode and going back into it again gets the application to resize 
correctly and fill the entire stage area.

Going from desktop to staged mode while the desktop application is
already running also works fine.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Assignee: Daniel d'Andrada (dandrader)
 Status: In Progress

** Description changed:

  Steps to reproduce the issue:
  
  1 - Put unity8 in staged mode
  2 - Launch a desktop application like kate or qtcreator
  
  Expected outcome:
  The launched application takes up the entire stage area
  
  Actual outcome:
  The launched application starts with some windowed size it wanted to have, 
not filling the entire stage area. As if launched in desktop mode.
  
  Comments:
- Leaving desktop mode and going into desktop mode again gets the application 
to resize all correctly fill the entire stage area.
+ Leaving staged mode and going into desktop mode again gets the application to 
resize all correctly fill the entire stage area.
  
  Going from desktop to staged mode while the desktop application is
  already running also works fine.

** Description changed:

  Steps to reproduce the issue:
  
  1 - Put unity8 in staged mode
  2 - Launch a desktop application like kate or qtcreator
  
  Expected outcome:
  The launched application takes up the entire stage area
  
  Actual outcome:
  The launched application starts with some windowed size it wanted to have, 
not filling the entire stage area. As if launched in desktop mode.
  
  Comments:
- Leaving staged mode and going into desktop mode again gets the application to 
resize all correctly fill the entire stage area.
+ Leaving staged mode and going back into it again gets the application to 
resize all correctly fill the entire stage area.
  
  Going from desktop to staged mode while the desktop application is
  already running also works fine.

** Description changed:

  Steps to reproduce the issue:
  
  1 - Put unity8 in staged mode
  2 - Launch a desktop application like kate or qtcreator
  
  Expected outcome:
  The launched application takes up the entire stage area
  
  Actual outcome:
  The launched application starts with some windowed size it wanted to have, 
not filling the entire stage area. As if launched in desktop mode.
  
  Comments:
- Leaving staged mode and going back into it again gets the application to 
resize all correctly fill the entire stage area.
+ Leaving staged mode and going back into it again gets the application to 
resize correctly and fill the entire stage area.
  
  Going from desktop to staged mode while the desktop application is
  already running also works fine.

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

Title:
  Desktop applications don't get properly resized when launched in
  staged mode

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce the issue:

  1 - Put unity8 in staged mode
  2 - Launch a desktop application like kate or qtcreator

  Expected outcome:
  The launched application takes up the entire stage area

  Actual outcome:
  The launched application starts with some windowed size it wanted to have, 
not filling the entire stage area. As if launched in desktop mode.

  Comments:
  Leaving staged mode and going back into it again gets the application to 
resize correctly and fill the entire stage area.

  Going from desktop to staged mode while the desktop application is
  already running also works fine.

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

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

[Touch-packages] [Bug 1669432] Re: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

[Daniel d'Andrada]

This is the first bug: Bug 1670361

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

Title:
  [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  ubuntu 17.04 unity8
  [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

  turn desktop mode off, and now launch random apps and see how it
  behave

  kate, the icon bar don't quite works, try to hover or click on the new
  document, open etc icons. only works on the buttom side of the icons,
  probably the hitboxes or something are wrong, same with tiled. some
  gtk apps don't even resize to fullscreen (gnome-mines), and if you
  click on the menu icon the apps just crash etc

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

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

[Touch-packages] [Bug 1670361] [NEW] Area near the top edge of window not clickable when in tablet mode

[Daniel d'Andrada]

Public bug reported:

Steps to reproduce the issue:
1 - be in desktop mode
2 - launch kate
3 - Ensure the "Show toolbar" in the Setings menu is checked
4 - Ensure kate is windowed (ie, not maximized)
5 - See that you can highlight and click on the "Open", "New" and "Close" 
buttons
6 - Switch to tablet mode
7 - Try to highlight and click on those same "Open", "New" and "Close" buttons

Expected outcome:
Works just like in desktop mode

Actual outcome:
Buttons don't respond as you they don't get any input events

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Assignee: Daniel d'Andrada (dandrader)
 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/1670361

Title:
  Area near the top edge of window not clickable when in tablet mode

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce the issue:
  1 - be in desktop mode
  2 - launch kate
  3 - Ensure the "Show toolbar" in the Setings menu is checked
  4 - Ensure kate is windowed (ie, not maximized)
  5 - See that you can highlight and click on the "Open", "New" and "Close" 
buttons
  6 - Switch to tablet mode
  7 - Try to highlight and click on those same "Open", "New" and "Close" buttons

  Expected outcome:
  Works just like in desktop mode

  Actual outcome:
  Buttons don't respond as you they don't get any input events

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

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

[Touch-packages] [Bug 1669432] Re: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

[Daniel d'Andrada]

Anyway, will investigate the one about kate toolbar buttons.

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

Title:
  [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  ubuntu 17.04 unity8
  [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

  turn desktop mode off, and now launch random apps and see how it
  behave

  kate, the icon bar don't quite works, try to hover or click on the new
  document, open etc icons. only works on the buttom side of the icons,
  probably the hitboxes or something are wrong, same with tiled. some
  gtk apps don't even resize to fullscreen (gnome-mines), and if you
  click on the menu icon the apps just crash etc

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

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

[Touch-packages] [Bug 1669432] Re: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

[Daniel d'Andrada]

Looks like you have multiple bugs in a single report. Not good.

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

Title:
  [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  ubuntu 17.04 unity8
  [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode

  turn desktop mode off, and now launch random apps and see how it
  behave

  kate, the icon bar don't quite works, try to hover or click on the new
  document, open etc icons. only works on the buttom side of the icons,
  probably the hitboxes or something are wrong, same with tiled. some
  gtk apps don't even resize to fullscreen (gnome-mines), and if you
  click on the menu icon the apps just crash etc

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

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

[Touch-packages] [Bug 1657215] Re: "Highlighting" submenu in Kate is shown empty

[Daniel d'Andrada]

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

** Changed in: unity8 (Ubuntu)
 Assignee: Nick Dedekind (nick-dedekind) => (unassigned)

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

Title:
  "Highlighting" submenu in Kate is shown empty

Status in unity8 package in Ubuntu:
  New

Bug description:
  - Launch Kate
  - Click on "Tools" menu
  - Click on "Highlighting" menu item

  Expected outcome:
  - A submenu with around 11 items is shown

  Actual outcome:
  - An empty submenu is shown

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

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

[Touch-packages] [Bug 1664151] Re: [performance] unity8.log flooded with debug messages about cursor position and appearance

[Daniel d'Andrada]

** Branch linked: lp:~dandrader/qtmir/reduceLogVerbosity

** Summary changed:

- [performance] unity8.log flooded with debug messages about cursor position 
and appearance
+ [performance] unity8.log flooded with debug messages about window position 
and cursor shape

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

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

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

Title:
  [performance] unity8.log flooded with debug messages about window
  position and cursor shape

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

Bug description:
  [performance] qtmir.surfaces messages about cursor position and
  appearance flood unity8.log when dragging a window, or when moving the
  cursor over some apps:

  [2017-02-13:14:03:45.132] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(577,109))
  [2017-02-13:14:03:45.140] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(580,109))
  [2017-02-13:14:03:45.148] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(582,109))
  [2017-02-13:14:03:45.148] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(582,107))
  [2017-02-13:14:03:45.162] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(586,107))
  [2017-02-13:14:03:45.164] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(588,107))
  [2017-02-13:14:03:45.172] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(591,107))
  [2017-02-13:14:03:45.180] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(593,107))
  [2017-02-13:14:03:45.188] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(595,107))
  [2017-02-13:14:03:45.196] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(597,107))
  [2017-02-13:14:03:45.196] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(597,108))
  [2017-02-13:14:03:45.204] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(599,108))
  [2017-02-13:14:03:45.220] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(601,108))
  [2017-02-13:14:03:45.279] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(602,108))
  [2017-02-13:14:03:53.564] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:53.572] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:53.604] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:53.612] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:53.620] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:53.628] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:54.916] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:54.972] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:54.988] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:55.012] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:55.044] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:55.100] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:55.156] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:55.196] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)

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

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

[Touch-packages] [Bug 1666469] Re: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes

[Daniel d'Andrada]

I meant the child windows of those apps.

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

Title:
  [unity8] child windows don't have a minimum size, you can resize the
  windows to ludicrous sizes

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

Bug description:
  unitu 17.04 unity8 deb session
  [unity8] child windows don't have a minimum size, you can resize the windows 
to ludicrous sizes 

  open a random app, open a child window (help>about or whatever),
  resize the window as small as it's allowed. see attached screenshot

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

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

[Touch-packages] [Bug 1664947] Re: [unity8] alt drag a child window doesn't work

[Daniel d'Andrada]

I don't get those crashes with gtk applications.

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

Title:
  [unity8] alt drag a child window doesn't work

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

Bug description:
  ubuntu 17.04 unity8

  open a random app, tiled or kate or whatever, open a child window
  (help/about or whatever) and then try to move the window with alt left
  click, press alt left click inside the window and drag (move the
  mouse). it doesn't work. it does work with the main window

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

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

[Touch-packages] [Bug 1666469] Re: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes

[Daniel d'Andrada]

I guess the bug is really that those child dialogs shouldn't be
resizable in the first place, like in Unity 7, right?

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

Title:
  [unity8] child windows don't have a minimum size, you can resize the
  windows to ludicrous sizes

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

Bug description:
  unitu 17.04 unity8 deb session
  [unity8] child windows don't have a minimum size, you can resize the windows 
to ludicrous sizes 

  open a random app, open a child window (help>about or whatever),
  resize the window as small as it's allowed. see attached screenshot

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

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

[Touch-packages] [Bug 1666469] Re: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes

[Daniel d'Andrada]

Just tried with calculator. It does set seem to be setting a minimum and
a maximum width with the same value since I cannot resize it
horizontally.

And vertically, I can only enlarge it but not shrink beyond its original
size.

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

Title:
  [unity8] child windows don't have a minimum size, you can resize the
  windows to ludicrous sizes

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

Bug description:
  unitu 17.04 unity8 deb session
  [unity8] child windows don't have a minimum size, you can resize the windows 
to ludicrous sizes 

  open a random app, open a child window (help>about or whatever),
  resize the window as small as it's allowed. see attached screenshot

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

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

[Touch-packages] [Bug 1666892] Re: [unity8] dolphin, closing one instance/window closes all

[Daniel d'Andrada]

In my machine dolphin doesn't quite work in a unity8 session.
It complains about klauncher, so doesn't show any files in its main area. But, 
most importantly, "New Window" has no effect.

Is there another application I can use to reproduce the bug?

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

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

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

Title:
  [unity8] dolphin, closing one instance/window closes all

Status in Canonical System Image:
  New
Status in qtubuntu package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.04 unity8

  launch dolphin, from the menu open a new window "File > New Window", now 
close the new window
  expected: first window to still be open. result all windows are closed, 
dolphin closed

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

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

[Touch-packages] [Bug 1666481] Re: [unity8] kate, selecting a document tab freezes unity8 for a second, i see hight unity8 cpu usage 80% while changing tabs (documents)

[Daniel d'Andrada]

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

** This bug has been marked a duplicate of bug 1666701
   unity8 freezes for a second while opening a client-side submenu in kate

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

Title:
  [unity8] kate, selecting a document tab freezes unity8 for a second, i
  see hight unity8 cpu usage 80% while changing tabs (documents)

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

Bug description:
  ubuntu 17.04 unity8 deb session

  [unity8] kate, selecting a document tab freezes unity8 for a second, i
  see hight unity8 cpu usage 80% while changing tabs (documents)

  launch kate, create 7-8 new documents and then change from one to
  another by clicking the tabs, also see the unity8 cpu usage

  see attached screenshot

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

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

[Touch-packages] [Bug 1664947] Re: [unity8] alt drag a child window doesn't work

[Daniel d'Andrada]

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

Title:
  [unity8] alt drag a child window doesn't work

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

Bug description:
  ubuntu 17.04 unity8

  open a random app, tiled or kate or whatever, open a child window
  (help/about or whatever) and then try to move the window with alt left
  click, press alt left click inside the window and drag (move the
  mouse). it doesn't work. it does work with the main window

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

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

[Touch-packages] [Bug 1666701] Re: unity8 freezes for a second while opening a client-side submenu in kate

[Daniel d'Andrada]

** Changed in: qtubuntu (Ubuntu)
 Assignee: Daniel d'Andrada (dandrader) => Albert Astals Cid (aacid)

** Changed in: unity8 (Ubuntu)
 Assignee: Daniel d'Andrada (dandrader) => Albert Astals Cid (aacid)

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

Title:
  unity8 freezes for a second while opening a client-side submenu in
  kate

Status in QtMir:
  Invalid
Status in qtubuntu package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps:

  - Launch kate
  - Right-click on its main, text editor, area. A pop-up menu should show up.
  - Hover your mouse pointer over the "Bookmarks" menu item. A sub menu with 
"Set Bookmark" and "Clear All Bookmarks" options will show up.

  Expected outcome:
  The sub menu opens immediately and the mouse pointer is responsive throughout

  Actual outcome:
  unity8 freezes for a bit, with mouse pointer becoming unresponsive, before 
finally resuming and showing up the submenu.

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

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

[Touch-packages] [Bug 1666701] Re: unity8 freezes for a second while opening a client-side submenu in kate

[Daniel d'Andrada]

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

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

Title:
  unity8 freezes for a second while opening a client-side submenu in
  kate

Status in QtMir:
  Invalid
Status in qtubuntu package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps:

  - Launch kate
  - Right-click on its main, text editor, area. A pop-up menu should show up.
  - Hover your mouse pointer over the "Bookmarks" menu item. A sub menu with 
"Set Bookmark" and "Clear All Bookmarks" options will show up.

  Expected outcome:
  The sub menu opens immediately and the mouse pointer is responsive throughout

  Actual outcome:
  unity8 freezes for a bit, with mouse pointer becoming unresponsive, before 
finally resuming and showing up the submenu.

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

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

[Touch-packages] [Bug 1666701] Re: unity8 freezes for a second while opening a client-side submenu in kate

[Daniel d'Andrada]

Doing "sudo rm /usr/lib/x86_64-linux-
gnu/qt5/plugins/platformthemes/libubuntuappmenu.so" and commenting out
menu code in DecoratedWindow.qml fixes those freezes

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

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

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

Title:
  unity8 freezes for a second while opening a client-side submenu in
  kate

Status in QtMir:
  Invalid
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps:

  - Launch kate
  - Right-click on its main, text editor, area. A pop-up menu should show up.
  - Hover your mouse pointer over the "Bookmarks" menu item. A sub menu with 
"Set Bookmark" and "Clear All Bookmarks" options will show up.

  Expected outcome:
  The sub menu opens immediately and the mouse pointer is responsive throughout

  Actual outcome:
  unity8 freezes for a bit, with mouse pointer becoming unresponsive, before 
finally resuming and showing up the submenu.

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

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

[Touch-packages] [Bug 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent

[Daniel d'Andrada]

Alt+Up and Alt+Down to switch between tabs in Kate also doesn't work
currently. Could it have the same cause as this Ctrl+C issue?

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

Title:
  qtubuntu sends wrong text as part of QKeyEvent

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  When using Unity7 or Plasma a key event created by Ctrl+C is
    QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003")

  But Unity8+ qtubuntu send to the application
    QKeyEvent(KeyPress, Key_C, ControlModifier, text="c")

  This is most likely because QMirClientInput::dispatchKeyEvent is using
  xkb_keysym_to_utf8 to get the text of the event instead of using
  xkb_state_key_get_utf8

  This breaks for example Konsole that expects the correct text to be
  sent.

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

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

[Touch-packages] [Bug 1666701] Re: unity8 freezes for a second while opening a client-side submenu in kate

[Daniel d'Andrada]

Switching between tabs in kate also causes unity8 to freeze momentarily.

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

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

Title:
  unity8 freezes for a second while opening a client-side submenu in
  kate

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

Bug description:
  Steps:

  - Launch kate
  - Right-click on its main, text editor, area. A pop-up menu should show up.
  - Hover your mouse pointer over the "Bookmarks" menu item. A sub menu with 
"Set Bookmark" and "Clear All Bookmarks" options will show up.

  Expected outcome:
  The sub menu opens immediately and the mouse pointer is responsive throughout

  Actual outcome:
  unity8 freezes for a bit, with mouse pointer becoming unresponsive, before 
finally resuming and showing up the submenu.

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

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

[Touch-packages] [Bug 1662827] Re: Some named cursors are not working anymore

[Daniel d'Andrada]

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

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

Title:
  Some named cursors are not working anymore

Status in QtMir:
  In Progress
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  $ bzr branch lp:~dandrader/+junk/animatedDemos
  $ cd animatedDemos/CustomCursor
  $ qmake && make
  $ cd ..
  $ qmlscene CursorShapes.qml -I . -- 
--desktop_file_hint=/usr/share/applications/gedit.desktop

  Currently only the following named cursors still work:
  UpArrow, Cross, WhatsThis, DragCopy, Busy, DragMove, DragLink

  Might also be due to a change in cursor theme itself (didn't check)?

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

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

[Touch-packages] [Bug 1662827] Re: Some named cursors are not working anymore

[Daniel d'Andrada]

That explains everything

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

** Changed in: qtmir
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

Title:
  Some named cursors are not working anymore

Status in QtMir:
  In Progress
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  $ bzr branch lp:~dandrader/+junk/animatedDemos
  $ cd animatedDemos/CustomCursor
  $ qmake && make
  $ cd ..
  $ qmlscene CursorShapes.qml -I . -- 
--desktop_file_hint=/usr/share/applications/gedit.desktop

  Currently only the following named cursors still work:
  UpArrow, Cross, WhatsThis, DragCopy, Busy, DragMove, DragLink

  Might also be due to a change in cursor theme itself (didn't check)?

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

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

[Touch-packages] [Bug 1662827] [NEW] Some named cursors are not working anymore

[Daniel d'Andrada]

Public bug reported:

$ bzr branch lp:~dandrader/+junk/animatedDemos
$ cd animatedDemos/CustomCursor
$ qmake && make
$ cd ..
$ qmlscene CursorShapes.qml -I . -- 
--desktop_file_hint=/usr/share/applications/gedit.desktop

Currently only the following named cursors still work:
UpArrow, Cross, WhatsThis, DragCopy, Busy, DragMove, DragLink

Might also be due to a change in cursor theme itself (didn't check)?

** Affects: qtmir
 Importance: Undecided
 Status: New

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

** Description changed:

  $ bzr branch lp:~dandrader/+junk/animatedDemos
  $ cd animatedDemos/CustomCursor
  $ qmake && make
  $ cd ..
  $ qmlscene CursorShapes.qml -I . -- 
--desktop_file_hint=/usr/share/applications/gedit.desktop
  
  Currently only the following named cursors still work:
  UpArrow, Cross, WhatsThis, DragCopy, Busy, DragMove, DragLink
  
- Might also be due so a change in cursor theme itself (didn't check)?
+ Might also be due to a change in cursor theme itself (didn't check)?

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

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

Title:
  Some named cursors are not working anymore

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

Bug description:
  $ bzr branch lp:~dandrader/+junk/animatedDemos
  $ cd animatedDemos/CustomCursor
  $ qmake && make
  $ cd ..
  $ qmlscene CursorShapes.qml -I . -- 
--desktop_file_hint=/usr/share/applications/gedit.desktop

  Currently only the following named cursors still work:
  UpArrow, Cross, WhatsThis, DragCopy, Busy, DragMove, DragLink

  Might also be due to a change in cursor theme itself (didn't check)?

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

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

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

[Daniel d'Andrada]

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

** No longer affects: qtmir

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

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

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

Status in Canonical System Image:
  Triaged
Status in qtubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

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

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

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

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

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

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

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

[Touch-packages] [Bug 1656727] Re: Unity8 crashes and restarts when clicking on a menu [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Daniel d'Andrada]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

** Changed in: qtmir
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

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

** Branch linked: lp:~dandrader/unity8/childWindows

** Branch linked: lp:~dandrader/qtmir/miral-surfaceLocalPos

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

Title:
  Unity8 crashes and restarts when clicking on a menu [terminate called
  after throwing an instance of 'std::out_of_range' what():  map::at]

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in MirAL:
  Invalid
Status in QtMir:
  Confirmed
Status in miral package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Unity8 crashes and restarts when clicking on a menu:

  terminate called after throwing an instance of 'std::out_of_range'
    what():  map::at

  Test case:
    1. Launch AisleRiot
    2. Click on a menu

  Expected: Menu opens
  Observed: Unity8 crashes and restarts every time

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170110.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  Date: Mon Jan 16 10:29:08 2017
  InstallationDate: Installed on 2016-11-03 (74 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1657399] Re: Menu reopens after closing the dialog that was opened by the menu item

[Daniel d'Andrada]

Problem is more general than that. In Kate, for instance. A submenu that
you opened will show up again when you hover the mouse over the window
title bar

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

Title:
  Menu reopens after closing the dialog that was opened by the menu item

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:
   * Open dolphin
   * Use the menu to do Help->About Dolphin
   * See the About Dolphin dialog
   * See the menu is closed
   * Close the About Dolphin dialog
   * See how the menu reopens

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

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

[Touch-packages] [Bug 1657215] [NEW] "Highlighting" submenu in Kate is shown empty

[Daniel d'Andrada]

Public bug reported:

- Launch Kate
- Click on "Tools" menu
- Click on "Highlighting" menu item

Expected outcome:
- A submenu with around 11 items is shown

Actual outcome:
- An empty submenu is shown

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Assignee: Nick Dedekind (nick-dedekind)
 Status: New

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  "Highlighting" submenu in Kate is shown empty

Status in unity8 package in Ubuntu:
  New

Bug description:
  - Launch Kate
  - Click on "Tools" menu
  - Click on "Highlighting" menu item

  Expected outcome:
  - A submenu with around 11 items is shown

  Actual outcome:
  - An empty submenu is shown

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

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

[Touch-packages] [Bug 1657206] Re: must click on a menu item to get its submenu

[Daniel d'Andrada]

Note: I'm using a laptop with a touchscreen, if that matters.

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

Title:
  must click on a menu item to get its submenu

Status in unity8 package in Ubuntu:
  New

Bug description:
  - Launch kate
  - Click on "Tools" menu in the window title
  - Put the mouse pointer over the "Encoding" menu item.

  Expected outcome:
  - Encoding submenu gets displayed

  
  Actual outcome:
  - Nothing happens. I have to click it in order to the the "Encoding" submenu 
displayed.

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

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

[Touch-packages] [Bug 1657206] [NEW] must click on a menu item to get its submenu

[Daniel d'Andrada]

Public bug reported:

- Launch kate
- Click on "Tools" menu in the window title
- Put the mouse pointer over the "Encoding" menu item.

Expected outcome:
- Encoding submenu gets displayed


Actual outcome:
- Nothing happens. I have to click it in order to the the "Encoding" submenu 
displayed.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Assignee: Nick Dedekind (nick-dedekind)
 Status: New

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  must click on a menu item to get its submenu

Status in unity8 package in Ubuntu:
  New

Bug description:
  - Launch kate
  - Click on "Tools" menu in the window title
  - Put the mouse pointer over the "Encoding" menu item.

  Expected outcome:
  - Encoding submenu gets displayed

  
  Actual outcome:
  - Nothing happens. I have to click it in order to the the "Encoding" submenu 
displayed.

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

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

[Touch-packages] [Bug 1651580] Re: mouseFlick in testWindowResizeArea is incredibly slow now

[Daniel d'Andrada]

Changing the call parameters in the test is fine. Whatever it takes to
get mouse flicks in testWindowResizeArea to be reasonable again.
Rephrased bug title accordingly.

Saw that similar adjustments have been made to other tests in revision
2730.

** Summary changed:

- UnityTestCase.mouseFlick is incredibly slow now
+ mouseFlick in testWindowResizeArea is incredibly slow now

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

Title:
  mouseFlick in testWindowResizeArea is incredibly slow now

Status in unity8 package in Ubuntu:
  New

Bug description:
  Regression caused by http://bazaar.launchpad.net/~unity-
  team/unity8/trunk/revision/2730.

  Using xenial+overlay.

  mouseFlick() in "make testWindowResizeArea" take a long time now.

  These are the numbers in my machine:

  """
  QDEBUG : qmltestrunner::WindowResizeArea::test_minimumSize() qml: timeStep = 
1944.543648263006, (iterations / speed) = 3.3335
  """

  That commit increased the time between mouse moves from 3.3 ms to a
  whopping 2 secs.

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

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

[Touch-packages] [Bug 1651580] [NEW] UnityTestCase.mouseFlick is incredibly slow now

[Daniel d'Andrada]

Public bug reported:

Regression caused by http://bazaar.launchpad.net/~unity-
team/unity8/trunk/revision/2730.

Using xenial+overlay.

mouseFlick() in "make testWindowResizeArea" take a long time now.

These are the numbers in my machine:

"""
QDEBUG : qmltestrunner::WindowResizeArea::test_minimumSize() qml: timeStep = 
1944.543648263006, (iterations / speed) = 3.3335
"""

That commit increased the time between mouse moves from 3.3 ms to a
whopping 2 secs.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Assignee: Albert Astals Cid (aacid)
 Status: New

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

** Description changed:

- Regression caused by revision 2730 "Use timeStep as delay time".
+ Regression caused by http://bazaar.launchpad.net/~unity-
+ team/unity8/trunk/revision/2730.
  
  Using xenial+overlay.
  
  mouseFlick() in "make testWindowResizeArea" take a long time now.
  
  These are the numbers in my machine:
  
  """
  QDEBUG : qmltestrunner::WindowResizeArea::test_minimumSize() qml: timeStep = 
1944.543648263006, (iterations / speed) = 3.3335
  """
  
  That commit increased the time between mouse moves from 3.3 ms to a
  whopping 2 secs.

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

Title:
  UnityTestCase.mouseFlick is incredibly slow now

Status in unity8 package in Ubuntu:
  New

Bug description:
  Regression caused by http://bazaar.launchpad.net/~unity-
  team/unity8/trunk/revision/2730.

  Using xenial+overlay.

  mouseFlick() in "make testWindowResizeArea" take a long time now.

  These are the numbers in my machine:

  """
  QDEBUG : qmltestrunner::WindowResizeArea::test_minimumSize() qml: timeStep = 
1944.543648263006, (iterations / speed) = 3.3335
  """

  That commit increased the time between mouse moves from 3.3 ms to a
  whopping 2 secs.

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

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

[Daniel d'Andrada]

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

** Changed in: qtmir
   Status: Triaged => Fix Released

-- 
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:
  Fix Released
Status in lttng-ust package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Fix Released
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 1346633] Re: [enhancement] Autopilot testing needs to know screen coordinates of widgets on screen

[Daniel d'Andrada]

** Branch unlinked: lp:~dandrader/qtmir/coordinateTranslator

** Branch linked: lp:~gerboland/qtubuntu/fix-debug-mode-56

** Branch linked: lp:~dandrader/unity8/miral

** Branch linked: lp:~unity-team/qtmir/miral-qt-integration

** Branch unlinked: lp:ubuntu/utopic-proposed/qtubuntu

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

Title:
  [enhancement] Autopilot testing needs to know screen coordinates of
  widgets on screen

Status in Autopilot:
  Won't Fix
Status in Mir:
  Fix Released
Status in QtMir:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  On phablet devices, Autopilot needs to determine the absolute
  coordinates of any item on screen, in order to generate input events
  to interact with those items.

  Most toolkits give AP the ability to calculate the coordinates of an
  item inside the surface, i.e. relative to the surface top-left corner,
  and then obtain the position of the window from the display server
  (X11 usually) to calculate the absolute position.

  However Mir does not have an API to let its clients find the surface
  position relative to the screen. There is also a desire from the Mir
  team not to supply this information.

  We need to discuss how to solve this problem in a way everyone is
  happy

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

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

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

[Daniel d'Andrada]

** Branch linked: lp:~gerboland/qtubuntu/windows-hidden-on-creation

** Branch linked: lp:~gerboland/qtubuntu/rasterGLSurface-fixes

** Branch linked: lp:~gerboland/qtubuntu/add--more-surface-type-support

** Branch linked: lp:~gerboland/qtubuntu/active-decision-refactor

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

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

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

** Branch linked: lp:~dandrader/unity8/childWindows

** Branch linked: lp:~dandrader/qtmir/miral-childWindows

** Changed in: unity8 (Ubuntu)
 Assignee: Nick Dedekind (nick-dedekind) => Daniel d'Andrada (dandrader)

** Changed in: qtmir (Ubuntu)
 Assignee: Nick Dedekind (nick-dedekind) => Daniel d'Andrada (dandrader)

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1591384] Re: Dialog of Blinken app is painted all wrong the first time it is open

[Daniel d'Andrada]

** Branch linked: lp:~dandrader/unity8/childWindows

** Branch linked: lp:~dandrader/qtmir/miral-childWindows

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

Title:
  Dialog of Blinken app is painted all wrong the first time it is open

Status in unity8 package in Ubuntu:
  New

Bug description:
  How to reproduce:
   * Be in unity8 on the desktop
   * Install blinken from repository
   * Edit /usr/share/applications/org.kde.blinken.desktop and add a 
X-Ubuntu-Touch=true after [Desktop Entry]
   * refresh the app scope
   * start blinken from the app scope
   * Show the about dialog in blinken (use the bottom right circle for it)
   * See how it is badly painted (screenshot attached)
   * If you close it and open it again it will look good (you may or may not 
have to remove the .cache/unity8 file that stores windows sizes for making the 
bug happen the next time)

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

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

[Touch-packages] [Bug 1591384] Re: Dialog of Blinken app is painted all wrong the first time it is open

[Daniel d'Andrada]

Will be fixed once untiy8 with miral + child windows support lands

** Attachment added: "blinken_with_unity8_miral.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1591384/+attachment/4775923/+files/blinken_with_unity8_miral.jpg

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

Title:
  Dialog of Blinken app is painted all wrong the first time it is open

Status in unity8 package in Ubuntu:
  New

Bug description:
  How to reproduce:
   * Be in unity8 on the desktop
   * Install blinken from repository
   * Edit /usr/share/applications/org.kde.blinken.desktop and add a 
X-Ubuntu-Touch=true after [Desktop Entry]
   * refresh the app scope
   * start blinken from the app scope
   * Show the about dialog in blinken (use the bottom right circle for it)
   * See how it is badly painted (screenshot attached)
   * If you close it and open it again it will look good (you may or may not 
have to remove the .cache/unity8 file that stores windows sizes for making the 
bug happen the next time)

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

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

[Touch-packages] [Bug 1623861] Re: Switching between two windows of the same app using quick swipe from right edge breaks focus

[Daniel d'Andrada]

** Changed in: qtubuntu (Ubuntu)
 Assignee: Daniel d'Andrada (dandrader) => Nick Dedekind (nick-dedekind)

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

Title:
  Switching between two windows of the same app using quick swipe from
  right edge breaks focus

Status in Canonical System Image:
  Fix Committed
Status in qtmir package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  Switching between two windows of the same app using quick swipe from
  right edge breaks focus.

  What happened:
  1) Install the multi-window version of webbrowser (silo 084)
  2) Open the webbrowser
  3) Focus the address bar, notice that keyboard raises correctly
  3) Spawn a second window
  4) Perform a quick swipe from the right edge to switch back to the first 
window
  5) Focus the address bar and notice that the keyboard doesn't raise

  Note at step 3, sometimes the keyboard does raise and sometimes not
  but after a quick swipe this is always reproducible for me.

  What I expected to happen:
  At step 5) for the keyboard to raise when the focus is given.

  
  When investigating the unity8 log I noticed that when the issue occurs there 
is a second "MirSurface[0x2358780,"webbrowser-app"]::updateActiveFocus() 
unfocused" on the old window after it has given focus to the old window.

  A change window that works: http://pastebin.ubuntu.com/23181435/
  A change window that fails: http://pastebin.ubuntu.com/23181436/

  
  Note a full swipe, which displays the spread, works as expected on my device.

  
  $ apt-cache policy qtmir-android qtubuntu-android webbrowser-app
  qtmir-android:
Installed: 0.4.8+15.04.20160906-0ubuntu1
Candidate: 0.4.8+15.04.20160906-0ubuntu1
Version table:
   *** 0.4.8+15.04.20160906-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   0.4.4+15.04.20150318-0ubuntu1 0
   50 http://ports.ubuntu.com/ubuntu-ports/ vivid/universe armhf 
Packages
  qtubuntu-android:
Installed: 0.63+15.04.20160912-0ubuntu1
Candidate: 0.63+15.04.20160912-0ubuntu1
Version table:
   *** 0.63+15.04.20160912-0ubuntu1 0
 1001 http://ppa.launchpad.net/ci-train-ppa-service/landing-084/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   0.63+15.04.20160831-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
   0.60+15.04.20150318-0ubuntu3 0
   50 http://ports.ubuntu.com/ubuntu-ports/ vivid/universe armhf 
Packages
  webbrowser-app:
Installed: 0.23+16.10.20160825-0ubuntu1local~1473859555
Candidate: 0.23+15.04.20160912-0ubuntu1
Version table:
   *** 0.23+16.10.20160825-0ubuntu1local~1473859555 0
  100 /var/lib/dpkg/status
   0.23+15.04.20160912-0ubuntu1 0
 1001 http://ppa.launchpad.net/ci-train-ppa-service/landing-084/ubuntu/ 
vivid/main armhf Packages
   0.23+15.04.20160825-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
   0.23+15.04.20150416-0ubuntu1 0
   50 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

  $ system-image-cli -i
  current build number: 398
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-09-12 15:18:40
  version version: 398
  version ubuntu: 20160910
  version device: 20160401.1
  version custom: 20160904-9-vivid

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

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

[Touch-packages] [Bug 1629455] [NEW] dashconnection.cpp causes assertion failure in Qt

[Daniel d'Andrada]

Public bug reported:

It only happens if you build Qt in debug mode. Packaged Qt is built in
release mode, where all Q_ASSERT* are NOOPS.

This is the error message:

ASSERT failure in QDBusAbstractInterface: "Interface name cannot be
empty", file /home/dandrader/packages/qtbase-opensource-
src-5.6.1+dfsg/src/dbus/qdbusabstractinterface.cpp, line 88


And this is the stack trace:

#0  0x7f1ecbf98418 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
#1  0x7f1ecbf9a01a in __GI_abort () at abort.c:89
#2  0x7f1ecc970b17 in qt_message_fatal (context=..., message=...) at 
/home/dandrader/packages/qtbase-opensource-src-5.6.1+dfsg/src/corelib/global/qlogging.cpp:1648
#3  0x7f1ecc96cb6a in QMessageLogger::fatal (this=0x7f1e7b821e10, 
msg=0x7f1ebd98 "ASSERT failure in %s: \"%s\", file %s, line %d") at 
/home/dandrader/packages/qtbase-opensource-src-5.6.1+dfsg/src/corelib/global/qlogging.cpp:790
#4  0x7f1ecc965361 in qt_assert_x (where=0x7f1eceb6b4be 
"QDBusAbstractInterface", what=0x7f1eceb6b3b8 "Interface name cannot be empty", 
file=0x7f1eceb6b460 
"/home/dandrader/packages/qtbase-opensource-src-5.6.1+dfsg/src/dbus/qdbusabstractinterface.cpp",
 line=88)
at 
/home/dandrader/packages/qtbase-opensource-src-5.6.1+dfsg/src/corelib/global/qglobal.cpp:3007
#5  0x7f1eceb25f2e in checkIfValid (service=..., path=..., interface=..., 
isDynamic=false, isPeer=false) at 
/home/dandrader/packages/qtbase-opensource-src-5.6.1+dfsg/src/dbus/qdbusabstractinterface.cpp:88
#6  0x7f1eceb26143 in 
QDBusAbstractInterfacePrivate::QDBusAbstractInterfacePrivate 
(this=0x7f1e74003860, serv=..., p=..., iface=..., con=..., isDynamic=false) at 
/home/dandrader/packages/qtbase-opensource-src-5.6.1+dfsg/src/dbus/qdbusabstractinterface.cpp:110
#7  0x7f1eceb2761e in QDBusAbstractInterface::QDBusAbstractInterface 
(this=0x7f1e74003720, service=..., path=..., interface=0x7f1e74003068 "", 
con=..., parent=0x0) at 
/home/dandrader/packages/qtbase-opensource-src-5.6.1+dfsg/src/dbus/qdbusabstractinterface.cpp:334
#8  0x7f1e869fc343 in AsyncDBusInterface::AsyncDBusInterface 
(this=0x7f1e74003720, service=..., path=..., interface=..., connection=..., 
parent=0x0) at 
/home/dandrader/unity8/miral/plugins/Unity/DashCommunicator/dashconnection.cpp:39
#9  0x7f1e869fbe80 in DashConnection::createInterface (this=0x7f1e74002d90, 
service=..., path=..., interface=..., connection=...) at 
/home/dandrader/unity8/miral/plugins/Unity/DashCommunicator/dashconnection.cpp:55
#10 0x7f1eac1b1881 in AbstractDBusServiceMonitor::onServiceRegistered 
(this=0x7f1e74002d90) at 
/home/dandrader/unity8/miral/src/libunity8-private/abstractdbusservicemonitor.cpp:65
#11 0x7f1eac1b2074 in QtPrivate::FunctorCall, 
QtPrivate::List, void, void 
(AbstractDBusServiceMonitor::*)(QString const&)>::call (f=
(void (AbstractDBusServiceMonitor::*)(AbstractDBusServiceMonitor * const, 
const QString &)) 0x7f1eac1b17c0 
, 
o=0x7f1e74002d90, arg=0x7f1e7b8222d0) at 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:501
#12 0x7f1eac1b1fe9 in QtPrivate::FunctionPointer::call (f=
(void (AbstractDBusServiceMonitor::*)(AbstractDBusServiceMonitor * const, 
const QString &)) 0x7f1eac1b17c0 
, 
o=0x7f1e74002d90, arg=0x7f1e7b8222d0) at 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:520
#13 0x7f1eac1b1f53 in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x7f1e74002ff0, r=0x7f1e74002d90, 
a=0x7f1e7b8222d0, ret=0x0) at 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:143
#14 0x7f1eccc1d681 in QtPrivate::QSlotObjectBase::call 
(this=0x7f1e74002ff0, r=0x7f1e74002d90, a=0x7f1e7b8222d0) at 
/home/dandrader/packages/qtbase-opensource-src-5.6.1+dfsg/include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#15 0x7f1eccc1a3b8 in QMetaObject::activate (sender=0x7f1e740013a0, 
signalOffset=3, local_signal_index=0, argv=0x7f1e7b8222d0) at 
/home/dandrader/packages/qtbase-opensource-src-5.6.1+dfsg/src/corelib/kernel/qobject.cpp:3715
#16 0x7f1eccc19cac in QMetaObject::activate (sender=0x7f1e740013a0, 
m=0x7f1eceb9e600 , local_signal_index=0, 
argv=0x7f1e7b8222d0) at 
/home/dandrader/packages/qtbase-opensource-src-5.6.1+dfsg/src/corelib/kernel/qobject.cpp:3595
#17 0x7f1eceb62ce2 in QDBusServiceWatcher::serviceRegistered 
(this=0x7f1e740013a0, _t1=...) at .moc/moc_qdbusservicewatcher.cpp:208
#18 0x7f1eceb61f89 in QDBusServiceWatcherPrivate::_q_serviceOwnerChanged 
(this=0x7f1e74002e60, service=..., oldOwner=..., newOwner=...) at 
/home/dandrader/packages/qtbase-opensource-src-5.6.1+dfsg/src/dbus/qdbusservicewatcher.cpp:72
#19 0x7f1eceb6292c in QDBusServiceWatcher::qt_static_metacall 
(_o=0x7f1e740013a0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7f1e7b822520) 
at 

[Touch-packages] [Bug 1540702] Re: While resizing Qt apps window contents jitter about erratically (including during animations)

[Daniel d'Andrada]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

Title:
  While resizing Qt apps window contents jitter about erratically
  (including during animations)

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

Bug description:
  Resizing a window (Scopes) the window contents jitter about
  erratically. Obviously they should appear to remain stationary unless
  being significantly repositioned.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Tue Feb  2 10:23:02 2016
  InstallationDate: Installed on 2015-12-03 (60 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity8-dash.log:
   ubuntumirclient: Got invalid serialized mime data. Ignoring it.
   ubuntumirclient: Got invalid serialized mime data. Ignoring it.
   ubuntumirclient: Got invalid serialized mime data. Ignoring it.

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

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

Re: [Touch-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

[Daniel d'Andrada]

On 13/09/2016 08:49, Gerry Boland wrote:
> 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?

It works fine.

-- 
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 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

[Daniel d'Andrada]

qtbase-opensource-src did get a new release on september 3rd. But xenial
stable-phone-overlay and yakkety seem to be carrying the very same qt
version, so scrap my theory from comment #30...

-- 
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:
  Invalid
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 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

[Daniel d'Andrada]

Maybe the culprit is different Qt versions between xenial and yakkety?

-- 
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:
  Invalid
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 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

[Daniel d'Andrada]

This only happens in yakkety. The same qtmir, qtubuntu and unity8 runs
fine in xenial. Lost a couple of hours on this issue yesterday and my
"solution" was to reboot my test laptop into a xenial partition so I
could unblock myself.

-- 
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:
  Invalid
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

[Daniel d'Andrada]

libc6  2.21-0ubuntu4.0.1

-- 
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 1618201] Re: deadlock in lttng_ust_init

[Daniel d'Andrada]

But on CI it also deadlocks in amd64.

-- 
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 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

[Daniel d'Andrada]

** Branch unlinked: lp:~dandrader/qtmir/cursorConfinement

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

Title:
  Need to support pointer confinement in Mir and toolkits using Mir

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in MirAL:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

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

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

[Daniel d'Andrada]

** Branch unlinked: lp:~dandrader/qtmir/mouseMovement

-- 
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 Committed
Status in QtMir:
  In Progress
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 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

[Daniel d'Andrada]

** Branch linked: lp:~unity-team/qtmir/cursorConfinement

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

Title:
  Need to support pointer confinement in Mir and toolkits using Mir

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in MirAL:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

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

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

[Daniel d'Andrada]

liblttng-ust 2.7.1-1~vividoverlay1
libglib2.0   2.44.1-1ubuntu1

About comments #4 and #5: what seems more relevant is actually ubuntu
release/pkg versions since my desktop runs xenial+stable-phone-overlay
whereas my arm devices run vivid+stable-phone-overlay.

-- 
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 1618201] Re: deadlock in lttng_ust_init

[Daniel d'Andrada]

It might have something to do with arm or chroot envs (likely what CI
does) as tests run fine on my amd64 desktop but deadlock in a chroot on
an arm device (like mako or flo).

-- 
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 1589637] Re: Need to support multiple instances of applications

[Daniel d'Andrada]

** Description changed:

  You're unable to open two instances of the same app. Such as gedit or
  firefox.
  
- qtmir needs UAL to provide instance-based signals: app instance started,
- app instance stopped, etc
+ qtmir needs instance-based signals: app instance started, app instance 
stopped, etc
+ As in 
http://bazaar.launchpad.net/~indicator-applet-developers/ubuntu-app-launch/trunk.16.10/view/head:/libubuntu-app-launch/registry.h#L77

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

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

Title:
  Need to support multiple instances of applications

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  You're unable to open two instances of the same app. Such as gedit or
  firefox.

  qtmir needs instance-based signals: app instance started, app instance 
stopped, etc
  As in 
http://bazaar.launchpad.net/~indicator-applet-developers/ubuntu-app-launch/trunk.16.10/view/head:/libubuntu-app-launch/registry.h#L77

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

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

[Touch-packages] [Bug 1407730] Re: [Apps] Support multiple app instances in the spread

[Daniel d'Andrada]

Assuming this is about multiple surfaces/windows per app, not multiple
application instances (processes). Therefore the unity8 and qtmir parts
are done.

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

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

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

Title:
  [Apps] Support multiple app instances in the spread

Status in Ubuntu UX:
  Triaged
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Related to bug #1198714 and design http://design.canonical.com/2014/05
  /the-browser-is-dead-long-live-the-browser/.

  I've a feeling that tabs in a phone factor browser are a bit
  shoehorned in, I'd actually be much happier having separate items in
  the right-edge spread for the open websites instead of introducing a
  second "axis" on which to switch between tabs.

  I remember it was a desire to "explode" tabbed UIs in the Super+S
  spread in Unity, but it was not possible technically. Maybe it could
  be made possible today?

  Whether tabs would exist grouped in the same right-edge stack, or as
  completely independent entities, remains to be investigated. Maybe
  we'd explode the tabs on touch or pinch or something. I just can't see
  the purpose of tabs if they're not readily available, which on a phone
  form factor would be a waste of precious screen estate.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: webbrowser-app 0.23+15.04.20141217-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15-0ubuntu3
  Architecture: armhf
  Date: Mon Jan  5 17:25:55 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141218-020204)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1341761] Re: WindowStack doesn't work in the emulator

[Daniel d'Andrada]

This D-Bus interface is gone.

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

** No longer affects: unity-mir

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

Title:
  WindowStack doesn't work in the emulator

Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  How to reproduce: start a i386 emulator instance with image 128, start
  a few apps, then call the WindowStack method.

  What happens?

  $ qdbus --literal com.canonical.Unity.WindowStack 
/com/canonical/Unity/WindowStack GetWindowStack
   [Argument: a(usbu) {}]

  What should happen?

  $ qdbus --literal com.canonical.Unity.WindowStack 
/com/canonical/Unity/WindowStack GetWindowStack
  [Argument: a(usbu) {[Argument: (usbu) 0, "com.ubuntu.calendar_calendar", 
false, 0], [Argument: (usbu) 0, "webbrowser-app", false, 0]}]

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

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

[Touch-packages] [Bug 1423985] Re: Crash when opening QtQuick Controls ComboBox

[Daniel d'Andrada]

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

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

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

Title:
  Crash when opening QtQuick Controls ComboBox

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

Bug description:
  Although QtQuick Controls aren't installed by default on the device
  they may be packaged with click applications (such as GCompris).
  Currently the ComboBox component from QtQuick Controls exposes a crash
  in unity8.

  Steps to reproduce:

  1) Install qml-module-qtquick-controls

   2) Run the following QML:

  import QtQuick 2.2
  import QtQuick.Controls 1.2

  ApplicationWindow {

  ComboBox {

  }

  }

   3) Tap the combo box

  Expected output:

   ComboBox should open

  Actual output:

   Unity switches back to the dash and then crashes with a segmentation
  fault (the application itself continues running)

  
  Backtrace:

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0xaadd1344 in qtmir::MirSurfaceItem::updateMirSurfaceFocus(bool) ()
 from 
/usr/lib/arm-linux-gnueabihf/qt5/qml/Unity/Application/libunityapplicationplugin.so
  (gdb) bt
  #0  0xaadd1344 in qtmir::MirSurfaceItem::updateMirSurfaceFocus(bool) ()
 from 
/usr/lib/arm-linux-gnueabihf/qt5/qml/Unity/Application/libunityapplicationplugin.so
  #1  0xb64e671e in QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
  #2  0xb6876cd8 in QQuickItem::activeFocusChanged(bool) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
  #3  0xb688618e in QQuickWindowPrivate::notifyFocusChangesRecur(QQuickItem**, 
int) () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
  #4  0xb688b170 in QQuickWindowPrivate::setFocusInScope(QQuickItem*, 
QQuickItem*, Qt::FocusReason, QFlags) ()
 from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
  #5  0xb687a802 in QQuickItem::setFocus(bool, Qt::FocusReason) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
  #6  0xb6882a78 in QQuickItem::qt_metacall(QMetaObject::Call, int, void**) () 
from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
  #7  0xb6b3fe40 in QQmlVMEMetaObject::metaCall(QMetaObject::Call, int, void**) 
() from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
  #8  0xbeb90720 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

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

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

[Touch-packages] [Bug 1373312] Re: Phablet album art not coming through from media-hub

[Daniel d'Andrada]

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

Title:
  Phablet album art not coming through from media-hub

Status in media-hub package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu RTM:
  Fix Released

Bug description:
  Not showing the correct album art if it is present.

  dict entry(
     string "art-url"
     variantstring 
"file:///usr/share/unity/icons/album_missing.png"
  )

  We also shouldn't be using "album_missing.png". It's supplied by
  libunity-core. We should be using the icon theme.

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

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

[Touch-packages] [Bug 1326513] Re: Applications are orphaned when unity8 crashes

[Daniel d'Andrada]

** No longer affects: qtmir

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

Title:
  Applications are orphaned when unity8 crashes

Status in Mir:
  Expired
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 source package in Vivid:
  New

Bug description:
  For some reason Unity8 crashed on me. The applications I had open are
  now orphaned. They're still running but you can't get to it as it no
  longer shows up under the recent applications. In addition if I
  attempt to start the app, it fails to run or come back from orphaned
  state, so I have to restart.

  My unity process where Unity8 died an hour or two back.

  lightdm   1871  0.0  0.0   1392   464 ?Ss   10:06   0:00 /bin/sh 
/usr/lib/lightdm/lightdm-greeter-session /usr/bin/unity8-greeter-wrapper 
/usr/bin/unity8-greeter
  lightdm   1875  0.0  0.0   1392   472 ?S10:06   0:00 /bin/sh 
/usr/bin/unity8-greeter-wrapper /usr/bin/unity8-greeter
  lightdm   2362  0.2  5.0 343724 95000 ?Sl   10:06   1:47 
/usr/bin/unity8-greeter
  phablet  22852  0.4  5.6 452692 105852 ?   Ssl  19:03   0:34 unity8

  The application:-

  phablet   8503 10.3  8.6 297792 161652 ?   Ssl  11:33  59:33
  /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene ubuntu-calculator-
  app.qml

  Now when I start calculator it just white-screens.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.87+14.10.20140603.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Wed Jun  4 21:04:34 2014
  InstallationDate: Installed on 2014-06-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140604)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1618580] Re: rc proposed App scope can have the apps filling only from half the screen

[Daniel d'Andrada]

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

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

Title:
  rc proposed App scope can have the apps filling only from half the
  screen

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

Bug description:
  Device Mako
  os ubuntu 15.04 r390

  Ok i have my phone in a weird state where the app scope is playing up.

  I can have the apps being displayed only from half way down the
  screen.

  Like that https://ibin.co/2tNGdrqJ9bEg.png

  I can reproduce easily

  Open the app scope
  Search for an app (tele)   >Already i notice the app is displayed half way 
down the screen https://ibin.co/2tNJTxU1cQpe.png

  Do a left edge swipe in order to see all the apps. > header is missing


  Pull down to see the header > Apps are appearing from half way down.

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

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] deadlock in lttng_ust_init

[Daniel d'Andrada]

Public bug reported:

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

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

-- 
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 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/ubuntu/+source/ust/+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