** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
** Changed in:
I can't repro this any more. Closing
** Changed in: unity8 (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: unity8 (Ubuntu)
Status: Won't Fix => Invalid
** Changed in: unity8 (Ubuntu Vivid)
Status: In Progress => Invalid
--
You received this bug notification
arm64? Should it not be using a hybris-based driver instead of mesa?
What hardware is this?
--
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/1585942
Title:
Mesa causes a
Yep. The branch has been approved, will take a while to get it landed.
Note that it will be almost unusable until bug 1585723 is resolved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
@Emanuele yes I did - but only via SSH. A colleague will verify it works
visually before approving
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1549455
Title:
Newer version of LTTng landed
** Changed in: telegram-app
Status: New => Invalid
** Changed in: webbrowser-app (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub
Ouch, on the hardware I have access to to test on, even a single Ubuntu
Shape in a simple QML file has a massive hit on rendering performance.
Rendering times went up 130ms *per shape*!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
FYI: INTEL_DEBUG=all is useful, it shows the opcodes mesa is generating
from your shaders.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1585723
Title:
I've updated the attached branch with my proposed fix.
--
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/1549455
Title:
Unity8-dash on Intel Atom graphics crashes and restarts
Using simple test apps (lp:~gerboland/+junk/openglwindow &
lp:~gerboland/+junk/qquickwindow-debug), it appears that yes Qt is using
OpenGL 1.4 on X for both raw GL and QtQuick apps.
./qquickwindow-debug
Window format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize
24,
/me has to stop using "Ok, " at the start of his sentences
--
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/1549455
Title:
Unity8-dash on Intel Atom graphics crashes and
Ok, I suspect I have found the issue. Seems this hardware only supports
OpenGL 1.4 compatibility profile. Qt's EGL code is asking for at least
version 2.0, and so getting no valid context back.
Could you please install "mesa-utils" package and run "glxinfo". On the
hardware I have access to, I
Public bug reported:
I'm digging into unity8 performance problems on older generation Intel
GPUs - specifically i915 Atom GPUs.
I've tested a simple QML file with a single empty UbuntuShape in it:
import QtQuick 2.4
import Ubuntu.Components 1.3
Rectangle {
width: 400
height: 300
Ok, I figured out hte EGL issue, it was my misunderstanding. Modifying the
tools to act correctly, I get this for eglinfo:
http://pastebin.ubuntu.com/16686113/
and the qteglchooser correctly chooses a valid Mir EGL config. Why Qt itself
cannot do this, I have yet to understand.
--
You received
Forgot to say, that was reproduced running the qteglchooser while there
was no X server running, instead just a Mir server running.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
Ok, progress, my tools can exhibit the problem:
http://pastebin.ubuntu.com/16677278/
Problems include:
1. libEGL warning: DRI3: xcb_connect failed<- should not be trying that
2. EGL version: 8.-1225087968<- this is garbage
I suspect that there is an issue with EGL.
--
You received this
Googling around I found this:
https://bugs.freedesktop.org/show_bug.cgi?id=87478
which puts some blame on Qt's shaders for distance field text rendering.
Happier news is that Qt has options to either use a lower quality
distance field rendering approach (fewer ALU instructions) or disabling
Hey Emanuele,
Albert got me the data I wanted from those tools, and the results are still
inconclusive. I think I need access to the hardware to make real progress on
this. So there's no need to bother with the trying those tools.
If you fancy a go, just to play:
1. Install build dependencies
faenil: well that used to be the case and then the appscope was
updated to auto refresh but still takes a little while to do that so the the
blue bouncing bar was at the bottom when you tried to open it initially it
might of still been updating the appscope which would mean you were using the
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1585127
Title:
Apps sometimes get stuck on
Hi Emanuele,
you attached a branch of mine to this bug - it makes our GL/EGL managing code
more robust. I had hoped it would fix this issue, but unfortunately it doesn't.
That's why I didn't attach that branch to this bug.
Annoyingly I don't have the hardware to hand either, so I'm flying
It has been a year, I've not heard this complaint in some time. I'm
marking this as fixed, please re-open if it happens to you.
** Changed in: qtmir
Status: Triaged => Fix Released
** Changed in: qtubuntu
Status: Confirmed => Fix Released
** Changed in: qtmir (Ubuntu RTM)
QtMir not deciding to resample, that's unity8.
** Changed in: qtmir
Status: New => Invalid
** Changed in: qtmir (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
In that case, shell should not resample events, and leave that up the
client, no?
--
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/1497105
Title:
Clients can't get high
I cannot reproduce this, must have been fixed along the way. Please re-
open if not
** Changed in: qtmir
Status: New => Fix Released
** Changed in: trust-store
Status: New => Fix Released
** Changed in: location-service (Ubuntu)
Status: New => Fix Released
--
You received
*** This bug is a duplicate of bug 1434584 ***
https://bugs.launchpad.net/bugs/1434584
** This bug is no longer a duplicate of bug 1304257
[enhancement] There should be a quit signal sent to sessions instead of
killing them directly
** This bug has been marked a duplicate of bug 1434584
*** This bug is a duplicate of bug 1434584 ***
https://bugs.launchpad.net/bugs/1434584
** This bug has been marked a duplicate of bug 1434584
closing an app by swiping it should graceful quit
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Lifecycle decisions now made by unity8, not qtmir/unity-mir.
Reassigning.
** Changed in: qtmir
Status: New => Invalid
** Changed in: unity-mir
Status: Triaged => Invalid
** Changed in: unity-mir (Ubuntu)
Status: Triaged => Invalid
** Also affects: unity8 (Ubuntu)
How do I reproduce this Daniel?
** Changed in: qtmir
Status: New => Incomplete
** Changed in: qtmir (Ubuntu)
Status: New => Incomplete
** Changed in: unity8 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: qtmir
Status: Fix Committed => 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/1560497
Title:
Unity8 (QtMir) crashed (on login or display
** Changed in: qtmir
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1421241
Title:
OOM score for apps waiting on content hub should be
This is on Intel I guess? Your investigations into bug 1580792 does
point out that the driver complains of a bad argument to
glCopyTexSubImage - the only consumer of glCopyTexSubImage that I can
find is in the Qt's font rendering system - so if it fails, it would
cause font rendering issues.
It possible QtMir mis-using the Mir DisplayConfiguration API. Here is
our implementation:
http://bazaar.launchpad.net/~mir-
team/qtmir/trunk/view/head:/src/platforms/mirserver/mirdisplayconfigurationpolicy.cpp#L51
Let me know if something obviously wrong
--
You received this bug notification
There appears to be a problem with the DisplayConfiguration::power_mode
flag in Mir.
I've added debug logging inside
ms::MediatingDisplayChanger::update_input_rectangles to print the
display configuration state. At startup, once unity8 starts, I see this
output from USC:
mi::DisplayInputRegion::confine(geom::Point& point) is responsible for
confining the cursor position inside the display rectangles.
void
ms::MediatingDisplayChanger::update_input_rectangles(mg::DisplayConfiguration
const& config)
is that which configures DisplayInputRegion with the display
Looking at Mir's SurfaceInputDispatcher::deliver_pointer,
auto target = find_target_surface(event_x_y);
printf("input event target %p, pos: (%d,%d)\n", target.get(),
event_x_y.x.as_int(), event_x_y.y.as_int());
prints this when hitting the barrier:
input event target 0x562470,
Public bug reported:
PUK entry screen being pushed down by snap decisions/notifications.
Krillin, flashed yesterday.
See screenshot
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "screenshot"
I've reported https://bugs.launchpad.net/mir/+bug/1580277 to raise the
GL/GLES combination problem with the Mir team
--
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/1580792
http://paste.ubuntu.com/16357238/ the output Qt gave me for the failing
eglCreateContext
--
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/1549455
Title:
Qt clients on Intel
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
** Changed in: unity8 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
Just considering the Dash problem, the crash is a symptom of a bigger
problem: seems qtubuntu is unable to choose or manage the egl config
correctly. If a correct/working egl config was chosen, then this code
path wouldn't be entered (which has the "delete when not created" bug
seen here).
The
Public bug reported:
(problem forked from bug 1549455)
Unity8 on Intel Pineview performs very poorly. Frame times appears to be
up to 900ms, Qt's renderer thread using 100% CPU.
Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA errors:
http://paste.ubuntu.com/16344427/
I suspect https://github.com/libhybris/libhybris/issues/315 is exactly
this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1490956
Title:
QOpenGL widget-based
** Branch linked: lp:~aacid/unity8/lvwph_qt56_fix
** Changed in: unity8 (Ubuntu)
Status: New => In Progress
** Changed in: unity8 (Ubuntu)
Importance: Undecided => High
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Albert Astals Cid (aacid)
--
You received this bug
I've looked into this a bit. Seems there's a change in behaviour between
Qt5.5 and 5.6 in how the Flickable's contentItem->width is initially set
- and this impacts the LVWPH
Try this demo Qt5.6 and LVWPH:
http://pastebin.ubuntu.com/16348569/
If you use anchors.fill, the contentItem width stays
Albert was able to reproduce this on his netbook.
The dash issues we suspect are due to:
https://bugs.launchpad.net/qtubuntu/+bug/1580124
https://bugs.launchpad.net/qtubuntu/+bug/1580118
I suspect also that the poor unity8 performance is due to a GL/GLES mismatch in
unity8. Running unity8 with
Qt has a bug report of a similar issue:
https://bugreports.qt.io/browse/QTBUG-48024 which may be avoidable with
care in qtmir.
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtmir
Yep, as of now, you can fetch the shell mode by using the
QPlatformNativeInterface::windowProperty api to fetch a "formFactor"
property which will return an enum (look in mir for the enum
interpretation) indicating what mode the shell is in. Connect to
windowPropertyChanged for signal on change.
** Branch unlinked: lp:~gerboland/unity8/window-width-height-changes-
acted-upon-always
--
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/1534682
Title:
Not requesting
Doing a grep in my directory which holds a bunch of applications, I see
quite a few are using the desktop_file_hint flag. I think those that
point it to /usr/share/applications will succeed, so they'll be ok. But
we might break other AP tests I don't have locally
--
You received this bug
Public bug reported:
I'm trying to run the ubuntu-ui-toolkit autopilot tests on today's
image.
First off, they could cause unity8 to crash, which is bug 1578258 which can be
resolved with
https://code.launchpad.net/~gerboland/qtmir/ual-catch-exception/+merge/293805
That causes unity8 to
Basic support of this has landed. Proper window management of these
surfaces remains to be done
--
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/1417655
Title:
Support
** Branch linked: lp:~unity-team/qtubuntu/screen-info-without-dpr
--
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/1534682
Title:
Not requesting desktop content when
I've attached a branch I worked on for dynamic grid unit support. This
rewrites the icon image loader to follow the exact behaviour of qt's
image loader, and solved my icon sizing/blur issue. It needs tests
though
** Branch linked: lp:~gerboland/ubuntu-ui-toolkit/staging-fix-icon-svg-
** Branch linked: lp:~dandrader/qtmir/coordinateTranslator
--
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
Log file has a lot of these messages for each scope:
:7:1: QML AbstractButton: Binding loop detected for property
"implicitWidth"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
Public bug reported:
I have a Meizu MX4 here connected to wifi via my router. The screen was
off.
For some reason, it decided to turn on the screen and show me the wifi
password snap decision. Possibly the connection dropped & was re-
established by NM?
But I've noticed this happening on other
** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
Need to profile and check the code to see how this could have regressed.
Stutter could be due to the GPU having to do too much work per frame,
inefficiencies in unity8's code. Can't say for certain without
measuring.
I know of several optimizations to be done with spread still.
--
You received
I agree with Chris' assessment. eglSwapBuffers blocking for so long
(over 32ms, i.e. 2 frames at 60Hz) is causing Qt's main loop to block,
compounding the stutter.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Please ensure the egl context Qt is getting has rgba , depth 8 and
stencil 24. Can read what Qt gets with QSG_INFO=1
--
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/1549226
I've attached the QtUbuntu branch which
1. correctly updates applications of the screen their window is on, so the
Screen information is correct
2. has getters and notifiers for these properties: scale & form factor
This branch relies on a QtMir branch to function correctly. All in
progress
**
** Branch linked: lp:~gerboland/unity8/window-width-height-changes-
acted-upon-always
--
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/1534682
Title:
Not requesting
Ok, I have an idea. content-hub links to libubuntu-app-launch.so, which
links to liblttng-ust.so. On load of liblttng-ust.so, it registers 2
tracepoint providers by default: ust_baddr_statedump and
lttng_ust_tracef. These are causing our repeating error messages.
Instead, I think we need to
** Branch linked: lp:~gerboland/qtmir/fix-orientation-after-unplug
--
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/1545286
Title:
[regression] ubuntu-pd instability
Status
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
** Changed in: qtubuntu (Ubuntu)
Status: New => Confirmed
** Changed in: qtubuntu
Status: New => Confirmed
** Changed in: qtmir
Status: New => Confirmed
--
You received this bug notification because you are a
===test2.qml
import QtQuick 2.3
import Ubuntu.Content 0.1
Rectangle { color: "pink" }
===test.qml==
import QtQuick 2.0
Rectangle {
color: "red"
Loader { id: loader; anchors.fill: parent; }
MouseArea {
anchors.fill: parent
Playing around with the camera app, I found that if I removed the
"Ubuntu.Content" plugin, the LTTng message stopped. So suspect something
content hub is linking with
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Yep, as test, inside
/usr/share/click/preinstalled/com.ubuntu.camera/current create this
simple QML file: test.qml:
import QtQuick 2.0
import Ubuntu.Content 0.1
Rectangle {
color: "red"
}
and execute with:
aa-exec-click -p com.ubuntu.camera_camera_3.0.0.611 -- qmlscene test.qml
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
** Changed in: qtmir
Status: New => Confirmed
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
** Changed in: qtmir
Importance: Undecided => Medium
** Changed in: qtmir (Ubuntu)
Importance: Undecided =>
Correct window resizing has not been implemented yet. What's currently
in place is indeed suboptimal.
--
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/1539011
Title:
Reassigning to Unity8. Will probably need work in UITK too
** Package changed: qtmir (Ubuntu) => unity8 (Ubuntu)
--
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/1536751
My understanding is that Qt's distance field approach to font rendering
does not do grid-fitting of characters. So for small font sizes on low-
dpi screens, font characters can be poorly antialiased, with 1-pixel
wide aspects of the character being rendered between pixels.
Distance field text is
Works for me
--
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/1536751
Title:
Unreadable text and broken infrographic dots on 1366x768 screen
Status in unity8 package in
Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1534682
Title:
Not requesting desktop content when
/me has to retract comment #13, it is indeed the app printing the
message. Camera app has 2 threads printing it
sudo strace -f -e write -p `pidof camera-app` 2>&1 | grep ust
[pid 14107] write(2, "libust[14085/14107]: Error: Erro"..., 114
[pid 14106] write(2, "libust[14085/14106]: Error:
** Branch linked: lp:~gerboland/qtubuntu/fix-max-full-switch-size
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1526328
Title:
[regression] blank area at the bottom
@pat we need more of Ted's input then, as I don't follow what he's
suggesting as a fix.
My understanding is that lttng reporting is only enabled with a
particular env var. So it should always be off by default. But these
errors printing in logs would suggest otherwise.
** Changed in: qtmir
I don't think it is the application printing this message. Attaching to
it with strace, it's not printing out when these lines appear in the
log. Upstart is reading these lines from *somewhere*, and writing them
to the log fine. But no idea from where yet
--
You received this bug notification
Qtubuntu reads the physical display size from Mir's
DisplayConfiguration. That is then used by Qt to calculate
physicalDotsPerInch().
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Also affects: qtubuntu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1525293
Title:
Comes from Mock sensor backend, which reads the pipe
/tmp/sensor-fifo-$PID
if nothing feeding that pipe, this will block
** Changed in: platform-api (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Note we've landed a hack to guess absolute positioning of surfaces for the
phone. But a proper solution requires more thorough approach:
1. via the mir-client-debug API, a client can ask for the surface's absolute
position
2. the server, if it is in debug mode, can reply with this information.
** Changed in: unity8 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1517878
Title:
Non-default cursor themes fail to load
https://tinyurl.com/ocsa8of looks like the culprit
--
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/1517571
Title:
Unity8 is crashing under UITK tests
Status in qtmir
http://pastebin.ubuntu.com/13216662/ is useful log. It indicates that 2
displays are detected by mir, and are not being cloned. However it
appears that there is only a single DisplayBuffer available
(Screen::setMirDisplayBuffer should be called for each DisplayBuffer,
but only called once)
--
http://bazaar.launchpad.net/~mir-
team/qtmir/trunk/view/head:/src/platforms/mirserver/screencontroller.cpp#L157
is the relevant line of code. This triggers after compositor start, to
match mir DisplayBuffers with Qt Screens. I've designed it under the
assumption that each Mir Display will always
oops wrong bug, please ignore above
--
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/1514519
Title:
Font in Terminal is incorrectly massive since recent update
Status in
Investigating, after hotplugging a second monitor, it appears that
sometimes Mir has only 1 display buffer ready, when there should be 2 -
one for each screen. Need to ask Mir team help
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
http://bazaar.launchpad.net/~mir-
team/qtmir/trunk/view/head:/src/platforms/mirserver/screencontroller.cpp#L157
is the relevant line of code. This triggers after compositor start, to
match mir DisplayBuffers with Qt Screens. I've designed it under the
assumption that each Mir Display will always
I'd need to dig, but I'd guess the DPI value in the QPA is now being
correctly calculated, since we've wired up the physical size, qt can
calculate a DPI. But we also live in the X world where DPI is nearly
always 96.
So need to figure out the right thing to do...
--
You received this bug
Testing mir_demo_server_minimal with mir_demo_client_egltriangle, I'm
seeing 30% CPU usage by the mir server just drawing a single spinny
triangle.
Testing a simple QML demo shell, we get same CPU usage as mir. So
punting to Mir team for investigation.
** Also affects: mir
Importance:
Public bug reported:
It appears that app windows are turning on clipping when the spread is
opened. This is really inefficient graphically because it is a
transformed rectangle and so Qt falls back to stencil-based clipping. We
should avoid clipping in this case at all cost
** Affects: unity8
Note the upside-down shell on the external monitor is a separate unity8
bug.
--
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/1511538
Title:
1/2 screen on external monitor
ded
Status: New
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
** Changed in: qtubuntu (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
** Changed in: qtmir (Ubuntu)
Status: New => In Progress
** Changed in: qtub
Device reboot a bad thing. The output of "adb shell /system/bin/logcat"
around the time of the reboot may be valuable (might indicate GPU reset,
bringing down everything with it)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: unity8 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1510407
Title:
Cursor image is dislocated on start up
The solution to https://bugs.launchpad.net/qtmir/+bug/1417655 will at
least prevent the 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/1488588
Title:
Terminal
but the Terminal app should never be trying to open a second surface
while on phone/tablet. Reopening Terminal app's bug.
** Changed in: ubuntu-terminal-app
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
It appears the terminal is trying to create another surface while you
are selecting. This is the output just before the crash:
qtmir.mir: MirWindowManagerImpl::add_surface(): size requested ( 0 , -26 ) and
placed ( 1366 , 768 )
qtmir.mir: SessionListener::surface_created - this=
101 - 200 of 404 matches
Mail list logo
