** Branch linked: lp:~gerboland/unity8/window-width-height-changes-
acted-upon-always
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534682
Title:
Not requesting desktop content when connected to
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
**
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545286
Title:
[regression] ubuntu-pd instability
To manage notifications about
** 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
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
===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
Bugs, which is subscribed to Ubuntu.
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539011
Title:
[regression] Window resizing is
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536751
Title:
Unreadable text and
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536751
Title:
Unreadable text and broken infrographic dots on 1366x768 screen
To manage notifications about this bug go to:
Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534682
Title:
Not requesting desktop content when connected to monitor
To manage noti
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531517
In my testing it does appear the pinch gesture is failing to be
recognized more frequently than before. In camera photo roll, if I zoom
in, then try to zoom out immediately, often that zoom-out fails.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
greyback: easiest way for me to repro is to open a picture in
camera photo roll then pinch to zoom and unzoom, double tapping also
gets it into the state, usually first time it works then not after that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bug more pronounced on Bq than Mako
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531517
Title:
pinch to zoom not working reliably
To manage notifications about this bug go to:
/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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526328
Title:
[regression] blank area at the bottom of the screen in full screen
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525293
Title:
** Also affects: qtubuntu (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/1525293
Title:
"window->screen()->physicalDotsPerInch() / 25.4" may be
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
Bugs, which is subscribed to
Public bug reported:
This happens to me a lot:
1. I flash a device
2. I run citrain to install a PPA on the device.
3. tool reboots device, but as network had not connected, the whole PPA install
step failed. But it reboots anyway.
A log:
http://pastebin.ubuntu.com/13622209/
** Affects:
Reopening - but appears to be different issue this time. Unity8 has this
failure logged:
[qtmir.mir: SessionListener::stopping - this= SessionListener(0xb1be1ffc)
session= 0x157099c
1448884391.745199] mircommon: Caught exception at Mir/EGL driver
boundary (in queueBuffer):
Music app is part of the lifecycle exemptions list. When it is launched,
QtMir obtains a wakelock for it to stop the system deep-suspending. This
means that while Music app is open, your system cannot deep suspend,
which is mainly a low-power CPU state.
Other apps however will still be frozen if
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: qtmir (Ubuntu)
Status: New => In Progress
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Changed in: unity8 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517878
Title:
Non-default cursor themes fail to load
To manage notifications about
qtmir release fixing this blocked in migration, due to liburcu issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515356
Title:
After a boot the dash doesn't display until touched
To manage
Suspect a race between the frameSwapped signal firing, and the
MirSurface being deleted. We should ensure MirSurface disconnects from
the frameSwapped signal asap on destruction
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://tinyurl.com/ocsa8of looks like the culprit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517571
Title:
Unity8 is crashing under UITK tests
To manage notifications about this bug go to:
** Branch linked: lp:~nick-dedekind/qtmir/drop-frame-texture-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515356
Title:
After a boot the dash doesn't display until touched
To manage
** Branch linked: lp:~gerboland/qtmir/xenial-armhf-fix
** Changed in: qtmir (Ubuntu)
Status: New => In Progress
** Changed in: qtmir (Ubuntu)
Importance: Undecided => Medium
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
--
You
oops wrong bug, please ignore above
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514519
Title:
Font in Terminal is incorrectly massive since recent update
To manage notifications about this bug
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
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)
--
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511538
Title:
1/2 screen on external monitor
To manage notifications
** Changed in: qtmir (Ubuntu)
Status: New => In Progress
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Michael Terry (mterry)
** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Branch linked: lp:~unity-team/qtmir/1510571.ms-timestamp-compression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511076
Title:
Qt timestamps seem off
To manage notifications about this bug
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
Bugs, which is subscribed to Ubuntu.
** Changed in: unity8 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510407
Title:
Cursor image is dislocated on start up
To manage notifications about
USC log:
ERROR:
/build/mir-U8WSgm/mir-0.17.0+15.04.20151008.2/src/platforms/android/server/gl_context.cpp(191):
Throw in function virtual void
mir::graphics::android::FramebufferGLContext::swap_buffers() const
Dynamic exception type:
Doing some plug/unplug with Nexus7, I got a black screen situation.
dmesg logs:
[ 4330.578460] kgsl kgsl-3d0: |kgsl_iommu_fault_handler| GPU PAGE FAULT: addr =
C1D59A00 pid = 3052
[ 4330.578613] kgsl kgsl-3d0: |kgsl_iommu_fault_handler| context = 0 FSR =
4001000A FSYNR0 = E08 FSYNR1 =
** Description changed:
- with latest vivid+o + silo0
+ with latest vivid+o
doing some hotplugging the phone seems robust, always changing modes from
full screen to windowed mode, and no rebooting. However, the result of the
hotplug (in) doesn't always seem to result in a frame on the monitor
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
Bugs, which is subscribed to
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=
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488588
Title:
Terminal crashes on selecting text, takes
Public bug reported:
Sending SIGTERM to unity8 causes this slightly concerning error message
to be printed:
QThread: Destroyed while thread is still running
Going a quick dig, I see it came from DashCommunicator:
(gdb) break src/corelib/thread/qthread.cpp:417
Breakpoint 1 at 0x7fafce6bd935:
DashCommunicator inherits QThread. From the QThread docs:
"Note that deleting a QThread object will not stop the execution of the
thread it manages. Deleting a running QThread (i.e. isFinished() returns
false) will probably result in a program crash. Wait for the finished()
signal before deleting
Public bug reported:
With MultiMonitor, enable QtMir input debug logging with:
initctl set-env --global QT_LOGGING_RULES="qtmir.*.debug=true"
Now watch the UI, while running this AP test:
autopilot3 run -v -v
Well we could always talk with Qt upstream about making the parameters
which define scrolling more configurable (so can be set in the QPA
plugin we have)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hey,
we'll shortly be releasing OTA7, which hopefully resolves this issue. Can you
please update this bug when you've tested the next release, and if the issue
still there, I'll start investigating this with you.
Thanks
-G
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status:
QtMir not responsible for window positioning.
** Changed in: qtmir (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/1438465
Title:
It's possible to put a
** Branch linked: lp:~dandrader/qtmir/multiSurfaceApp
** Changed in: qtmir (Ubuntu)
Status: New => In Progress
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
** Changed in: unity8 (Ubuntu)
Status: New => In Progress
** Changed in: qtmir
Just checked with working unity8 (with mir 0.16), Alpha buffer reported
missing there too. Must be unrelated issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502093
Title:
unity8 crash on mako
Here's a simple way to reproduce the fail. Stick the following into a
file test.qml:
import QtQuick 2.4
import Ubuntu.Components 1.2
Rectangle {
color: 'green'
UbuntuShape {}
}
Do "stop unity8" to stop unity8 reboot loop. Then do:
MIR_SERVER_NAME=session-0 MIR_SOCKET=/run/mir_socket
Something suspicious to me, the GL context Mir is giving to Qt is
missing the alpha channel:
Settings "QSG_INFO=1", you get:
qt.scenegraph.info: texture atlas dimensions: 2048x2048
qt.scenegraph.info: R/G/B/A Buffers:8 8 8 0
qt.scenegraph.info: Depth Buffer: 24
qt.scenegraph.info:
Apitrace of the failing scenario:
http://pastebin.ubuntu.com/12638037/
Driver appears to be crashing while compiling the UbuntShape shader
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502093
Title:
Also experiencing it with Flo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502093
Title:
unity8 crash on mako rc-proposed/ubuntu with latest unity8/mir/powerd
To manage notifications about this
qtmir has very little to do with shell orientation, reassigning to
unity8
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtmir (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: qtmir
Status: New => Incomplete
** Changed in:
** Changed in: platform-api (Ubuntu)
Status: New => Confirmed
** Also affects: platform-api
Importance: Undecided
Status: New
** Changed in: platform-api
Status: New => Confirmed
** Changed in: platform-api
Importance: Undecided => Medium
** Changed in: platform-api
** Also affects: qtubuntu
Importance: Undecided
Status: New
** Branch linked: lp:~gerboland/qtubuntu/mouse-enter-leave-events
** Changed in: qtubuntu
Status: New => In Progress
** Changed in: qtubuntu
Assignee: (unassigned) => Gerry Boland (gerboland)
--
You re
Dear Michael,
thanks for the report. Unfortunately Unity2D is not actively developed any
more, so only security critical fixes will be applied.
It's been ages since I looked at the code, but I don't see any evidence
of hotkeys being hardwired.
I think by "half-transparent search window." you
Watching the eventfd2 & close calls to see which one leaks:
sudo strace -p `pidof unity8` 2>&1 | grep -P "(eventfd|close)"
I get on app open:
eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 118
eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 117
close(117) = 0
eventfd2(0,
** Changed in: qtubuntu
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/1278780
Title:
apport takes too long to write crash report, appears to lock up phone
To
Ok, task is for Qt clients to intercept the sigsegv signal, and in a
handler close the mir connection which should release all its video
buffers, then re-raise segv. Would it be of interest to have all mir
clients exhibit this behaviour by default? If so, should put this
behaviour in "mirclient"
Unsure if related, but if I mash the vol up/down keys on arale a bit, it
makes unity8 freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not responsive after an incoming SMS
I assigned you Daniel as I recall we had this same issue last week with
the welcome wizard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492185
Title:
unity8 crashes when running ubuntu keyboard
Shell rejecting OSK's re-connection attempts, which is wrong. It
shouldn't also crash...
** Changed in: unity8 (Ubuntu)
Importance: Undecided => Critical
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
** Changed in: unity8 (Ubuntu)
Status:
** Changed in: qtmir
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.launchpad.net/bugs/1371282
Title:
Mir Motion event tool type on touch device is 0
Think this more a Unity8 issue, as it decides what mode to be in
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtmir (Ubuntu)
Status: New => Incomplete
** Changed in: qtmir
Status: New => Incomplete
--
You received this bug
the latest is lp:unity-api/15.04 which corresponds to vivid+overlay.
Wily is behind, release 7.99, which is why you see this. People are
fixing it. Is not qtmir's fault
** Changed in: qtmir
Status: New => Won't Fix
** Changed in: qtmir (Ubuntu)
Status: New => Won't Fix
--
You
** Also affects: ubuntu-system-settings (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
** Changed in: qtmir (Ubuntu)
Status: Confirmed => Invalid
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
** Changed in: unity8 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification
** Branch linked: lp:~gerboland/qtmir/multimonitor
** Changed in: mir
Status: New => Invalid
** Changed in: qtmir
Status: New => In Progress
** Changed in: canonical-pocket-desktop
Status: New => In Progress
** Changed in: qtmir
Assignee: (unassigned) =>
Status: New
** Changed in: qtmir
Status: New => In Progress
** Changed in: qtmir
Importance: Undecided => High
** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
** Changed in: qtmir
Assignee: (unassigned) => Gerry Boland (gerboland)
** Change
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
** Also affects: qtmir
Importance: Undecided
Status: New
** Changed in: qtmir
Status: New => Incomplete
** Changed in: qtmir
Status: Incomplete
This hasn't happened in a while. It is usually due to the Qt GUI loop
being blocked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436860
Title:
unity8 is hung in
This still happening?
** Changed in: mir
Status: New => Incomplete
** Changed in: qtmir (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403936
Title:
cal-pocket-desktop
Status: New => In Progress
** Changed in: qtmir (Ubuntu)
Status: New => In Progress
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
QtMir relying on ubuntu-app-launch to set OOM scoring
** Changed in: qtmir (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/1478853
Title:
OOM scoring
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
** Changed in: qtmir
Status: New => Confirmed
** Changed in: qtmir
Importance: Undecided => Low
** Changed in: qtmir (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member
** Changed in: qtmir
Status: New => Confirmed
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
** Changed in: qtmir (Ubuntu)
Status: Confirmed => In Progress
** Changed in: qtmir
Status: Confirmed => In Progress
** Changed in: qtmir (Ubuntu)
Importance:
Is Mir's job to interpret such gestures, QtMir just passes the
interpreted events to the shell.
** 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
Bugs, which is
flash has nothing to do with qtmir afaict
** Changed in: qtmir (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1467807
Title:
flash light on camera
** Changed in: qtmir
Status: In Progress => Fix Released
** Changed in: qtmir (Ubuntu)
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.launchpad.net/bugs/1483840
Title:
I cannot reproduce on today's image. Yay for year's progress
** Changed in: qtmir (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355263
Title:
If foreground
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
** Changed in: qtmir
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426443
Title:
Add support for
** Changed in: qtmir
Status: Confirmed => In Progress
** Changed in: qtmir
Assignee: (unassigned) => 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/1434584
** Changed in: qtmir
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.launchpad.net/bugs/1437357
Title:
Crash because uncaught exception in mir::events::add_touch
To manage
201 - 300 of 1278 matches
Mail list logo
