Public bug reported:
Booting from the Ubuntu 18.04 installation USB stick.
- Chose "Try Ubuntu"
- set up wifi network
- From a terminal I upgraded ubiquity to 18.04.14.3
- clicked on "Install Ubuntu 18.04 LTS"
- did a Normal installation (with option to download updates) on a blank
harddrive
Pro
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.
** Affec
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675448
T
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
** Changed in: unity8 (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675448
Title:
Unity 8 doesnt allow multiple mir connections from an application
** 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
Bugs, which is subs
Public bug reported:
1- I get an Application::Instance in a Manager::startingRequest call.
2- Later on a Registry::appStarted signal is received with an
Application::Instance.
I would like to know if the Application::Instance from 1 is referring to
the same application instance as the Applicatio
** Changed in: qtmir (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589637
Title:
Unable to open multiple instances of the same app
To manage notifica
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)
S
** 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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
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&#x
One of the prerequisite fixes is bug 1671424
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673415
Title:
QDockWidgets don't work at all
To manage notifications about this bug go to:
https://bugs.l
** 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
**
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
"""
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 upda
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
*** This bug is a duplicate of bug 1671424 ***
https://bugs.launchpad.net/bugs/1671424
** This bug has been marked a duplicate of bug 1671424
Applications fail to interrupt closing them
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671424
Title:
qtmir destroys
** Changed in: qtmir (Ubuntu)
Assignee: Daniel d'Andrada (dandrader) => (unassigned)
** Changed in: qtmir (Ubuntu)
Status: In Progress => Confirmed
** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you a
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
** Changed in: qtmir (Ubuntu)
Status: New => In Progress
** Description changed:
qtmir always destroys a window if it doesn't do so itself after being
requested to close.
Maybe a fix for bug 1674749 is what you want.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624407
Title:
Add a 'quit' message that is app-wide, as opposed to
mir_event_type_close_surface
To man
** Description changed:
+ qtmir always destroys a window if it does do so itself after being
+ requested to close.
+
Specially on desktop, requesting a window to close doesn't necessarily
means it should destroy itself. It's a common idiom to just hide the
window, for instance.
Some mi
Public bug reported:
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
means it should destroy itself. It's a common idiom for an application
to just hide it instead, so it can be reused
** 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, cl
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
Bugs, which is subscribed to
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
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 investigat
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/167
** 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 becaus
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671072
T
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 rec
** 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 (Ub
*can do
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672931
Title:
[regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead
*** 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
** Changed in: qtubuntu (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665286
Title:
[unity8] A ghost (shadow only) window opens with some app
window
** 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/tile
** 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
Bu
With that "fix", now qt5 are unusable as they go under XMir.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668429
Title:
X apps (LibreOffice, Thunderbird) fail to launch with failure to open
disp
*qt5 apps I mean
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668429
Title:
X apps (LibreOffice, Thunderbird) fail to launch with failure to open
display (no Xmir is running)
To manage notifica
** 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
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
Bugs, which is subscrib
Can't reproduce it with trunk (released) versions of unity8 and qtmir.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665286
Title:
[unity8] A ghost (shadow only) window opens with some app
window
@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
Bugs, which is subscribed
** Changed in: qtmir (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670710
Title:
/usr/bin/unity8:11:qtmir::DBusFocusInfo::findQmlSurface:qtmir::DBusF
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
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
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
--
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 qtcr
This is the first bug: Bug 1670361
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669432
Title:
[unity8] qt/gtk apps don't quite work in fullscreen/tablet mode
To manage notifications about this bu
"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 even
Anyway, will investigate the one about kate toolbar buttons.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669432
Title:
[unity8] qt/gtk apps don't quite work in fullscreen/tablet mode
To manage n
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 membe
*** 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
Bugs, which is subscribed to Ubuntu.
htt
)
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
Bugs, which
I don't get those crashes with gtk applications.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664947
Title:
[unity8] alt drag a child window doesn't work
To manage notifications about this bug go
I meant the child windows of those apps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666469
Title:
[unity8] child windows don't have a minimum size, you can resize the
windows to ludicrous size
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666469
Title:
[unity8] child wind
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 Ubu
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: Ne
*** 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
Bu
** Changed in: unity8 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664947
Title:
[unity8] alt drag a child window doesn't work
To manage notifications a
** 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 Ub
** 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 (Ub
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
--
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664610
Title:
qtubun
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662827
Title:
Some n
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
Bugs, which is subscribed to Ub
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, WhatsTh
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** 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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
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-dedeki
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.
**
Note: I'm using a laptop with a touchscreen, if that matters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657206
Title:
must click on a menu item to get its submenu
To manage notifications about
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
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_minimum
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618201
Title:
deadloc
** 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 receiv
indows
** 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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1591384
Title:
Dialog of Blinken app is pa
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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623861
Title:
Switching bet
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
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540702
Title:
While resizing Qt apps window content
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 Ubun
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
Bugs, which is subscribed to Ubun
Maybe the culprit is different Qt versions between xenial and yakkety?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620934
Title:
Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
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
libc6 2.21-0ubuntu4.0.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618201
Title:
deadlock in lttng_ust_init
To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/
** Branch linked: lp:~unity-team/qtmir/cursorConfinement
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590099
Title:
Need to support pointer confinement in Mir and toolkits using Mir
To manage not
** Branch unlinked: lp:~dandrader/qtmir/cursorConfinement
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590099
Title:
Need to support pointer confinement in Mir and toolkits using Mir
To manage no
** Branch unlinked: lp:~dandrader/qtmir/mouseMovement
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597205
Title:
Not sending relative mouse events to clients
To manage notifications about this bu
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 notificatio
But on CI it also deadlocks in amd64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618201
Title:
deadlock in lttng_ust_init
To manage notifications about this bug go to:
https://bugs.launchpad.ne
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
Bugs, which is subscribed to Ubuntu.
https://bug
1 - 100 of 711 matches
Mail list logo
