Public bug reported:
Steps to Repro:
1. Multimonitor setup needed
2. Open QtCreator, open a Qt project of some kind
3. Move the QtCreator window to the monitor you can unplug
4. unplug that monitor
Expected result
Window Manager relocates the QtCreator window to the remaining monitor
Actual
** Branch linked: lp:~dandrader/qtmir/supportedOrientations
** Changed in: qtmir
Status: New = In Progress
** Changed in: qtmir
Importance: Undecided = High
** Changed in: qtmir
Assignee: (unassigned) = Daniel d'Andrada (dandrader)
--
You received this bug notification because
Is using Mir 12.0: http://paste.ubuntu.com/10683940/
--
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/1436860
Title:
unity8 is deadlocked
Status in mir package in Ubuntu:
** Changed in: hundredpapercuts
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/1297334
Title:
Text on music is sometimes unreadable.
Public bug reported:
Take this code:
#include QApplication
#include QWidget
int main(int argc, char *argv[])
{
QApplication app(argc, argv);
QWidget *w = new QWidget();
w-showMaximized();
return app.exec();
}
and this Qt pro file:
QT += core gui widgets
TARGET =
** Changed in: qtmir
Importance: Undecided = High
** 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 unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1425593
Title:
Public bug reported:
I open QtCreator (Qt5.4) and open unity8's CMakeFiles.txt. Crash appears
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: qtdeclarative5-dev-tools 5.4.0-4ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
This bug consistently evades me. I've spent much time trying to
reproduce this to no avail.
This fail will occur if mir client process are *not* launched via
ubuntu-app-launch - as unity8 will not accept mir connections it doesn't
expect, causing the client to crash with this error. The obvious
Please read previous comments before re-assigning affected project.
Unity8's main loop is blocked, which will cause qtmir to block mir when
mir is asking if a session should be authorized or not - as that
decision made in unity8's main loop.
** Also affects: unity8 (Ubuntu)
Importance:
I agree with Alberto's assessment. Qt's mainloop appears blocked. Would
need more frames of thread1 to get a good idea why.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
A little more digging: bringing up mir_proving_server and xeyes manually:
1. sudo stop lightdm
2. sudo mir_proving_server
3. sudo chown $USER /tmp/mir_socket
4. sudo chmod 777 /tmp/mir_socket
5. Xmir :1 -mirSocket /tmp/mir_socket
6. in separate shell, do:
DISPLAY=:1 xeyes
I can tell X to blank
Top frame of LP's backtrace rubbish. I got the following:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fb6d7051700 (LWP 3053)]
0x7fb73bf9c463 in DisplayWindow::makeCurrent() () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
(gdb) bt
: (unassigned) = Gerry Boland (gerboland)
** Summary changed:
- unity8 crashed with SIGSEGV in QHashint,
QWindowSystemInterface::TouchPoint::remove()
+ DisplayWindow::makeCurrent crash with xmir apps
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Changed in: unity8 (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 unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1410457
Title:
unity8 crashed
unity8 has a big log file, because qtmir has all debug logging info turned on
by default.
This can be changed just for unity8 by setting adding this env var to its
upstart job:
QT_LOGGING_RULES=*.debug=false
Alternatively can apply this policy for all Qt apps in the system by
creating
Mir does provide an api for client to specify this to shell. But nothing
is using it yet
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qtubuntu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qtubuntu
Importance: Undecided
Do we want Mir to have an ecosystem of configuration tools around it?
Because this won't happen if every shell has to implement their own
configuration save/restore/change system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
.
** Changed in: unity8 (Ubuntu)
Status: Triaged = In Progress
** Changed in: unity8 (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 unity8 in Ubuntu
** Branch linked: lp:~gerboland/qtmir/acquire-wakelock
** Changed in: qtmir (Ubuntu)
Importance: Undecided = Critical
** Changed in: qtmir (Ubuntu)
Status: New = In Progress
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) = Gerry Boland (gerboland)
--
You received this bug
Public bug reported:
Not sure if this desirable or not, but I noticed when I opened the
networking indicator, and tapped on the currently connected network (the
green one) that the connection was broken and re-established.
To see, open shell on device and run ping 8.8.8.8. Watch the output,
then
Public bug reported:
Steps to repro:
1. Open Power indicator
2. Disable auto brightness. Move the slider to change screen brightness - all ok
3. Enable auto brightness. Try moving slider
Expected result
brightness still adjusted, but tempered based on the auto's decisions
Actual result
** Changed in: qtmir (Ubuntu RTM)
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/1309915
Title:
foreground app should keep wakelock open
After chat with ricmm, am going to have AppMan hold a system wakelock
while any app is non-suspended - this should ensure app state is always
updated before the device is put into deep sleep.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Still trying to get my head around this. If I manually create a wakelock:
sudo bash -c echo mylock /sys/power/wake_lock
then I can't reproduce the bug (tried 20 times anyway). If I remove that
wakelock:
sudo bash -c echo mylock /sys/power/wake_unlock
then yes, I get the bug again. Sadly
QtMir needs extending to support multiple surfaces per application.
Unity8 will need to not rely directly on the ApplicationManager model
then, but form its own model of application surfaces derived from it.
** Changed in: qtmir (Ubuntu)
Status: New = Confirmed
** Changed in: qtmir
Also, I suppose for phablet we can only let certain apps have multiple
entries in the spread? (/me foresees app surface creation bomb attack) -
what will define that policy (that qtmir will implement)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
Dash Unity8 communicate via DBus, so unity8 can tell Dash to switch to
a scope when needed. This implemented by a DashCommunicator plugin.
DashCommunicator inherits AbstractDBusServiceMonitor, which monitors the
DBus bus for when the Dash service appears, and when it does,
This bug is in our list for land for next RTM release, should happen
soon
--
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/1394208
Title:
Unity8 unable to find the dash,
The RTM release process is slow. This fix is in the next batch of fixes
to land. If things go well, will land by the end of the week. If not,
unfortunately it'll have to be after the holidays.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Mir does support changing the display configuration, yes. But does Mir
support saving the last display configuration to disk somehow, so it is
re-applied after reboot, if possible? I didn't think so anyway.
I'm also thinking that not every application should be able to customize
the display
*** This bug is a duplicate of bug 1381292 ***
https://bugs.launchpad.net/bugs/1381292
This was fixed in trunk with this commit:
https://code.launchpad.net/~josharenson/unity8/fix_trust_store_focus/+merge/239567
Commit needs backporting to RTM
--
You received this bug notification because
unity8/qtmir relies on ubuntu-app-launch for all application management,
so fix is for UAL to get systemd support
** Also affects: ubuntu-app-launch (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
*** This bug is a duplicate of bug 1396244 ***
https://bugs.launchpad.net/bugs/1396244
** This bug has been marked a duplicate of bug 1396244
Unlocking the phone over fullscreen app is very slow
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Summary changed:
- Unlocking the phone over dialer is very slow
+ Unlocking the phone over fullscreen app is very slow
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
When locking phone with dialer in front, I see it tries to make itself
fullscreen
qtmir.surfaces: MirSurfaceManager::onSurfaceAttributeChanged - surface=
0x1c36080 state=fullscreen
qtmir.sessions: Session::setFullscreen - session= qtmir::Session(0x1b2e608)
fullscreen= true
qtmir.applications:
Is dialer fullscreening itself on lock?
mterry greyback_, yes
mterry greyback_, well the greeter enforces fullscreen / locked-down UI when
you're in the emergency dialer (doesn't present launcher or indicators). So
the dialer requests fullscreen because otherwise there'd be a blank bar at the
https://code.launchpad.net/~thomas-voss/qtubuntu-media/reuse-precreated-
objects/+merge/240644 fixes this issue for me
** Branch linked: lp:~thomas-voss/qtubuntu-media/reuse-precreated-
objects
** Changed in: unity8 (Ubuntu)
Status: New = Invalid
** Changed in: qtubuntu-media (Ubuntu)
Public bug reported:
On desktop Vivid, with qtubuntu-media installed, unity8 crashes on
startup.
Removing qtubuntu-media fixes this, but presumably qtubuntu-media will
be our desired multimedia playback plugin. So something needs fixing
there.
** Affects: qtubuntu-media (Ubuntu)
http://pastebin.ubuntu.com/8818402/ the backtrace of 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/1389276
Title:
[desktop] unity8 crashes on startup at
** Also affects: qtubuntu-media (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/1389276
Title:
[desktop] unity8 crashes
==relevent log file output ==
Initializing AalServicePlugin
Creating a new static Service instance
Failed to start a new media-hub player session:
org.freedesktop.DBus.Error.ServiceUnknown: The name core.ubuntu.media.Service
was not provided by any .service files
Failed to create a new media
Ok, am happy to land Ted's branch.
** Branch linked: lp:~ted/qtmir/ual-pause
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1382039
Title:
[TOPBLOCKER] Apps
For iteration 1, the SDK team team agreed that setting the supported
orientation in a desktop file hint is sufficient. Should we need more
granularity, we can create an API for applications to set it themselves.
But the lack of an existing API in Qt's QScreen class means that API
would be custom
Just found https://bugs.launchpad.net/mir/+bug/1382209 [Enhancement] Add an
API to lock surface orientation
so a UX decision would help clarify what we really need
** Summary changed:
- [Dash] Allow applications to specify the orientations supported
+ Allow applications to specify the
qtmir.applications: TaskController::isApplicationPid - appId=
com.ubuntu.calculator_calculator pid= 18567
is where above appears be to stuck
--
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:
Currently unity8 shell has a partial implementation of orientation
support. It trusts applications to rotate their own contents, if they
want to. The shell doesn't reposition the panel (at the top) though, so
a landscape app still has a portrait panel on the side.
For proper
So the two options we thought of to solve this are:
1. add hack to unity8, so suppress showing splash screen for online-accounts
alone
2. add extra flag to desktop file like X-Ubuntu-Splash=False which tells unity8
not to draw splash screen, and have OA set that.
I dislike option 2 more, as it
Unity8 tries to draw a splash screen for an app as soon as possible, so the UI
is responsive to the user. It will paint a splash screen when either of these
things happen:
1. user taps an app icon in launcher
2. when upstart notifies it an app is starting
3. when Mir notifies it an app connected
Public bug reported:
Steps to repro:
1. in Dash, scroll it up a small bit so the header half off screen
2. tap the bit of the search icon that's still visible
Expected result
Search box appears in header, header fully reveals to you can see entire search
box
Actual result
Search box appears in
Public bug reported:
Steps to repro
1. freshly boot the device
2. ssh in
3. stop unity8
It will often hang there for some time.
From the backtrace (http://pastebin.ubuntu.com/8527967/), this is the thread I
most suspect:
Thread 3 (Thread 0xa2ab6450 (LWP 3462)):
#0 0xb5ff2554 in
And ofc now I'm struggling to reproduce it
** Summary changed:
- unity8 often hangs on shutdown - but if you touch the screen it stops
correctly
+ unity8 sometimes hangs on shutdown
** Description changed:
Steps to repro
1. freshly boot the device
2. ssh in
3. stop unity8
- It will
Public bug reported:
This was after a bit of random finger mashing of image 73 on the stable
device
See screenshot attached for how the UI appears with this bug.
The Dash is still responding, as I can still do a bottom edge swipe to
bring up the scope view. But I'm unable to swipe the app list
After opening scope view, and trying to select the Video scope, now the
dash is failing to respond to any input. Working on backtrace in case it
helps
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
http://pastebin.ubuntu.com/8520251/ a backtrace, nothing appears blocked
to me, threads are waiting for something to do
--
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/1378760
Public bug reported:
Running unity8-dash in gdb, I noticed these messages repeating
continually:
[New Thread 0xa69b6450 (LWP 22737)]
[Thread 0xa69b6450 (LWP 22737) exited]
[New Thread 0xa69b6450 (LWP 22740)]
[Thread 0xa69b6450 (LWP 22740) exited]
[New Thread 0xa69b6450 (LWP 22743)]
[Thread
@mzanetti - with your steps, I can do further gestures and dash starts
working again. Unfortunately I find the list it totally stuck
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
From reading the backtrace in comment 3, I'm guessing that Thread3 is the Qt
GUI thread, which is blocked on a WaitCondition.
Thread 15 is a Mir thread, is blocked on
SessionAuthorizer::requestAuthorizationForSession which is waiting for the Qt
GUI thread to reply to it.
But as GUI thread
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: camera-app
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.
Unity8 appears to not deal well with applications closing themselves. Is
unity8 bug
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1375267
Title:
camera-app not useable
Public bug reported:
Dash sometimes fails to appear during Autopilot tests - causes failures
** Affects: unity8 (Ubuntu)
Importance: Critical
Assignee: Gerry Boland (gerboland)
Status: In Progress
** Branch linked: lp:~unity-team/unity8/upstart-always-sigstop
--
You
** Branch linked: lp:~unity-team/qtmir/no-upstart-notification
** Branch linked: lp:~unity-team/ubuntu-system-settings/sigstop-for-
upstart
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
This is message from a client trying to start, and unity8 either not
expecting it and thus rejecting the client connection, or due to bug
1368101. Hard to know for certain
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Steps to repro:
1. Install qt3d5-examples package
2. Run the following command:
/usr/lib/arm-linux-gnueabihf/qt5/examples/qt3d/cylinder
--desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop
You'll see a cylinder on screen, but the dash underneath it.
By
qtmir.applications: ApplicationManager::onProcessStarting - appId=
webbrowser-app
ApplicationManager::onProcessStarting application already found with appId
webbrowser-app
qtmir.mir: SessionAuthorizer::connection_is_allowed - this=
SessionAuthorizer(0x1494bec) pid= 24699
qtmir.applications:
Is unity8 bug, I doubt qtmir to blame
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity8 (Ubuntu)
Status: New = Confirmed
** Changed in: unity8 (Ubuntu)
Importance: Undecided = Medium
** Changed in: qtmir
Status: New = Opinion
I'd like to point you to:
https://qt-project.org/doc/qt-5/qquickwindow.html#grabWindow
QtMir exposes a Mir display as a QWindow, so this method will generate
the image you want.
I suspect this would be better implemented in unity8
--
You received this bug notification because you are a member
AppMan has no idea that an application is being used while in the
background - and thus treats it like any other background app.
To fix this, would need a way for shell to control AppMan's lifecycle
decisions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: qtmir
Status: New = Confirmed
** Changed in: qtmir
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1346633
Title:
** No longer affects: unity-mir
** Changed in: qtmir
Status: New = Opinion
--
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/1234901
Title:
Need DBus application
Clarification: only happens with a short right-edge flick between app
dash
--
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/1372654
Title:
Qt.Application.active changes the
Introspect error on :1.391:/com/canonical/Autopilot/Introspection:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did
not receive a reply.
This nearly always means the application under test has either crashed
or has hung.
Digging, I found that indeed unity8 is handing.
** Changed in: unity8 (Ubuntu)
Assignee: Michael Zanetti (mzanetti) = Gerry Boland (gerboland)
** Changed in: unity8 (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8
Public bug reported:
Just booted phone. I have a 4 digit PIN set for the lockscreen
1. Right-edge swipe Greeter away to reveal lock screen
2. do a left-edge swipe - you can see the Greeter and Launcher both slide in.
Greeter slides away again though. Launcher is now stuck open
Really,
** Changed in: qtmir
Status: Confirmed = In Progress
** Changed in: qtmir (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,
So far, I've tracked the problem down to the sensors part of platform-
api.
android/hybris/ubuntu_application_sensors_for_hybris.cpp -
looper_callback function - there's a leak somewhere
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Is unity8-dash definitely being started after unity8 emits SIGSTOP -
which is its way of telling upstart that the mir server is ready for
incoming connections?
If not, dash might have tried to connect to mir, before unity8 has
brought up mir.
--
You received this bug notification because you
Public bug reported:
Brendan Donegan found that unity8 froze
Was only able to get a partial backtrace: http://pastebin.com/REPjL5Pq
which points to the external translation process (the gettext binary) for
libusermetrics acting weird (quoting Pete Woods)
The unity8.log
Confirmed on my device. Using perf I see quite a few memory allocations
and frees happening while device is idle.
** 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
I ran unity8 through valgrind with massif, with the commands
stop unity8
export MIR_SERVER_NAME=session-0
export MIR_SOCKET=/run/mir_socket
export QT_QPA_PLATFORM=mirserver
valgrind --tool=massif --time-unit=ms --detailed-freq=1 /usr/bin/unity8
attached is a visualization of the data. unity8
Public bug reported:
Steps to repro:
1. Set a PIN or password
2. Hit power to lock device
3. Hit power
4. at Greeter, do a left-edge swipe
It unlocks the device even though I never entered the PIN/password
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You
** Information type changed from Private to Public
--
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/1367461
Title:
Crash on closing a qml file using
** Branch linked: lp:~gerboland/platform-api/exposeOrientation
** Branch linked: lp:~gerboland/qtubuntu/exposeOrientation
** Branch linked: lp:~gerboland/qtmir/exposeOrientation
** Branch linked: lp:~gerboland/unity8/orientationLock
--
You received this bug notification because you are a
I'd prefer we didn't have clashing module names. What if we want to use
functionality from the public instance as well as our private one? But
initial fix to reorder directory list would do short-term
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I'm curious why it takes u8 so long to respond to the power key press.
It should be almost instantly receiving the dbus message and drawing a
frame with the greeter shown. DBus isn't /that/ slow.
Do we show greeter as soon as power-off is hit? I hope we don't draw
Greeter on power-on only.
--
** 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 mir in Ubuntu.
https://bugs.launchpad.net/bugs/1353855
Title:
Explicit g++ 4.9 dependency breaks
** Changed in: unity8 (Ubuntu)
Status: Confirmed = In Progress
** Changed in: unity8 (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 unity8 in Ubuntu
** Changed in: unity-2d
Assignee: Gerry Boland (gerboland) = (unassigned)
** Changed in: unity-2d
Status: In Progress = Won't Fix
** Changed in: unity-2d (Ubuntu)
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: unity-2d
Assignee: Gerry Boland (gerboland) = (unassigned)
** Changed in: unity-2d
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https
** Changed in: unity-2d
Assignee: Gerry Boland (gerboland) = (unassigned)
** Changed in: unity-2d
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https
** Changed in: platform-api
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1266674
Title:
platform-api fails build
Hmm, it's the Mock LightDM implementation being used
QLightDM::GreeterImpl::converseWithPam (num_msg=optimized out, msg=optimized
out, resp=0x7fcd243bdb30, appdata_ptr=optimized out)
at
/build/buildd/unity8-8.00+14.10.20140811/tests/mocks/LightDM/demo/GreeterPrivate.cpp:153
** Changed in:
Ok reproduced! From the backtrace, I see these 2 threads, the main
thread (thread1) owns the threadpool and is waiting for one of these
threads to complete. Thread 2 has a QThreadPoolThread which is blocked
at QFutureInterfaceBase::waitForResult due to some PAM lightdm stuff.
Thread 2 (Thread
Following these steps exactly, calendar sync seemed to fail, so they
didn't work for me.
But when I manually created 2 events, with names 5 minute reminders,
then I could reproduce the bug
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: qtmir
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-mir in Ubuntu.
https://bugs.launchpad.net/bugs/1346367
Title:
Window stack reports app in focus even
** Also affects: qtmir
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-mir in Ubuntu.
https://bugs.launchpad.net/bugs/1241185
Title:
Should provide policy based lifecycle
** Also affects: qtmir
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1304257
Title:
[enhancement] There should be a quit
** Changed in: unity-mir
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-mir in Ubuntu.
https://bugs.launchpad.net/bugs/1281075
Title:
quickly starting multiple apps breaks
** Also affects: qtmir
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1326513
Title:
Applications are orphaned when unity8
** Changed in: unity8 (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 unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1351097
Title:
[emulator] bottom edge
We've not tested QtMir/Unity8 handling an app changing to fullscreen and
then back to normal, so that needs to be done.
Also need to check qtubuntu allows a client app to ask for fullscreen
and back again to normal.
** Also affects: qtmir
Importance: Undecided
Status: New
** Changed
301 - 400 of 404 matches
Mail list logo
