Mir does associate resources with a client socket that are not released
until one of two things happen:
1. The client explicitly disconnects
2. An operation (like the outstanding read attempt) on the socket reports an
error
AFAIK there is no *guarantee* that the latter happens in a timely mann
bin/mir_demo_server --window-manager fullscreen
** Changed in: mir
Status: Triaged => Invalid
** Changed in: mir (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Branch linked: lp:~alan-griffiths/mir/remove-constraints-on-surface-
placement
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447882
Title:
mir_demo_server(_minimal): Can't move surfac
Public bug reported:
When compiz is closed down (typically as a result of replacing the
window manager) it incorrectly dumps windows into the first workspace.
** Affects: compiz (Ubuntu)
Importance: Undecided
Assignee: Alan Griffiths (alan-griffiths)
Status: New
** Changed in
> Is this possibly related to bug 804036?
Doesn't seem like it (at least the fix for this isn't a fix for that).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980026
Title:
Compiz should not move w
** Changed in: compiz-core
Assignee: Robert Carr (robertcarr) => Alan Griffiths (alan-griffiths)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/804036
Title:
Removing an external monitor cau
There are two elements to this:
/1/ a fairly unusual error condition that I've yet to identify; and,
/2/ poor error handling in compiz
The error condition causes CompositeScreen::CompositeScreen to call
setFailed() - which should simply cause the composite plugin to fail
loading (and normally wo
** Changed in: compiz-core
Status: Triaged => In Progress
** Changed in: compiz-core
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Branch linked: lp:~alan-griffiths/compiz-core/Bug.833729
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/833729
Title:
compiz crashed with SIGSEGV in CompositeScreen::compositingActive()
To
"exit(1)" - that may be the best quick fix. There is too much flaky
code around in plugins that have a transitive dependency on
CompositeScreen. (If the code were exception-neutral then I could throw
an exception and clean up neatly.)
--
You received this bug notification because you are a memb
I can't reproduce unfortunately. However, I believe the code derives
from r2993 - where there was a indeed sequencing issue that has been
fixed on trunk (r2998 "Fix teardown sequence").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~alan-griffiths/compiz-core/Bug-931283
** Changed in: compiz-core
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932125
Title:
com
** Changed in: compiz-core
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954305
Title:
compiz crashed with SIGSEGV in shared_
"Cancelled" would appear to be a behaviour that is "out there" - so
adding it to libinput & Mir is a natural solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547864
Title:
libinput doesn't h
** Changed in: mir
Status: Fix Committed => 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/1532607
Title:
Phone not usable while a call comes in - followed by "restart"
To manage
** Changed in: mir
Status: Fix Committed => 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/1528384
Title:
unity-system-compositor crashed with std::runtime_error in
mir::composi
** Changed in: mir/0.20
Status: Fix Committed => 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/1546676
Title:
EglSyncFence tests depend on android platform
To manage notificatio
** Changed in: mir/0.20
Status: Fix Committed => 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/1517597
Title:
[regression] mouse pointer support on emulator is broken
To manage
** Changed in: mir/0.20
Status: New => Fix Released
** Changed in: mir/0.20
Importance: Undecided => Critical
** Changed in: mir/0.20
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: mir
Status: Fix Committed => 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/1517205
Title:
[mali] egl_demo_client_flicker has graphics corruption on android
To man
** Changed in: mir
Status: Fix Committed => 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/1546676
Title:
EglSyncFence tests depend on android platform
To manage notifications ab
** Changed in: mir
Status: Fix Committed => 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/1532202
Title:
[android] External monitor slows rendering
To manage notifications about
** Changed in: mir
Status: Fix Committed => 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/1517597
Title:
[regression] mouse pointer support on emulator is broken
To manage notif
** Changed in: mir
Status: Fix Committed => 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/1539268
Title:
Display::create_gl_context may create context with incorrect
attributes
** Changed in: mir
Status: Fix Committed => 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/1543594
Title:
unity-system-compositor locked up in __libc_do_syscall()
To manage notif
** Changed in: mir
Status: Fix Committed => 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/1538632
Title:
UI freezes when simultaneously moving mouse & plug/unplug HDMI
To manage
** Changed in: mir
Status: Fix Committed => 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/1539338
Title:
Mir fails to build on xenial today:
android_graphic_buffer_allocator.h:
** Changed in: mir
Status: Fix Committed => 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/1525003
Title:
[testsfail] Intermittent failure in
TestClientCursorAPI.cursor_passed_t
** Changed in: mir (Ubuntu)
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/1546676
Title:
EglSyncFence tests depend on android platform
To manage notifications
** Changed in: mir
Status: Fix Committed => 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/1537798
Title:
NestedServer.client_sees_set_scaling_factor intermittent failure
To mana
** Changed in: mir/0.20
Status: Triaged => Won't Fix
** Changed in: mir/0.19
Status: Triaged => Won't Fix
** Changed in: mir
Milestone: 0.21.0 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Changed in: mir/0.19
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1544878
Title:
Mir servers crash if I press the side mouse button (thumb)
To manage notific
** Description changed:
Since updating to the 4.4.0-2 kernel recvmsg() fails SCM_CREDENTIALS
request with EOPNOTSUPP.
This manifests as a test failure in Mir:
- [ RUN ] PromptSessionClientAPI.client_pid_is_associated_with_session
- unknown file: Failure
+ [ RUN ]
-final fails
-rc6 fails
-rc4 succeeds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540731
Title:
SocketMessenger::update_session_creds() fails to get client PID,
causing "[ FAILED ]
PromptSess
Also "This happens with kernel-4.5.0-0.rc1.git2.1.fc24.x86_64 as well."
(from https://sourceware.org/bugzilla/show_bug.cgi?id=19557)
** Bug watch added: Sourceware.org Bugzilla #19557
http://sourceware.org/bugzilla/show_bug.cgi?id=19557
--
You received this bug notification because you are a
-rc5 succeeds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540731
Title:
SocketMessenger::update_session_creds() fails to get client PID,
causing "[ FAILED ]
PromptSessionClientAPI.client_pid_
Confirmed:
http://kernel.ubuntu.com/~jsalisbury/lp1540731/Commit3822b5cReverted/
fixes this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540731
Title:
SocketMessenger::update_session_cred
the
whole problem but needs to be eliminated.
** Branch linked: lp:~alan-griffiths/mir/fix-
SystemCompositorWindowManager-remove_surface
** Also affects: mir
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Branch unlinked: lp:~alan-griffiths/mir/fix-
SystemCompositorWindowManager-remove_surface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543594
Title:
unity-system-compositor locked up in
Too old to care about
** Changed in: mir
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/134
Title:
unity-system-compositor crashed with SIGABRT in ~InputReaderThr
There's slightly more involved than adding mir_surface_state_automatic
as the surface state will change to maximized/restored etc. but there
needs to be a persistent "automatic" attribute as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Adding qtmir as that needs to handle the Window Management metadata
Saviq alludes to.
** Also affects: qtmir
Importance: Undecided
Status: New
** Changed in: qtmir
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Having discussed this a few times I've reached the following conclusion:
"automatic" is not a MirSurfaceState - if it were a MirSurfaceState,
then it would be correct to return it from get_state() and for it to be
implemented as "looking the same as fullscreen or restored".
By comparison, "restor
To clarify, the desired behaviour /can/ be implemented client-side with
the existing Mir API. This would require implementation code in each
toolkit (or client). The limitation of this approach being that the
shell isn't required to respect set_state() requests issued by the
client.
We /can/ also
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/336/consoleFull
09:55:24 9: [ RUN ] LP.1540731
09:55:24 9:
/��BUILDDIR��/mir-0.20.1+16.04.20160225.1+vivid345bzr3362/tests/acceptance-tests/test_prompt_session_client_api.cpp:672:
Now affecting trusty 3.13.0-79-generic (which is what a lot of CI slaves
are running today)
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
As discussed above, the nested server doesn't have enough information to
select the correct drivers and more work is needed on supplying this
from the host before this can be closed.
** Changed in: mir
Status: Fix Committed => Triaged
** Changed in: mir/0.18
Status: Fix Released =>
** Changed in: mir/0.18
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515558
Title:
[regression] Nested servers on mesa-kms select wrong (dummy) guest
platform
Having a (hopefully) temporary workaround that handles some common
scenarios isn't a fix. Here (copied from the email discussion) are some
notes about resolving this:
as discussed following today's standup the problems we face involves a
number of issues beyond the probing logic.
There are three
** Changed in: mir
Status: Triaged => In Progress
** Changed in: mir
Assignee: Mir development team (mir-team) => Alan Griffiths
(alan-griffiths)
** Summary changed:
- [regression] Nested servers on mesa-kms select wrong (dummy) guest platform
+ [regression] Nested serve
** Branch linked: lp:~alan-griffiths/mir/nested-server-uses-host-
graphics-platform
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515558
Title:
[regression] Nested servers can select wrong
** Changed in: mir
Status: Incomplete => 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/1488863
Title:
nexus4 & nexus7 hotplug survival
To manage notifications about this bug go
This sounds like the cumulative effect of a number of Mir bugs in the
display configuration handling that resulted in the surfaces composited
by a nested server appearing in the wrong place.
It is plausible that the fixes landed up to -r3056 have resolved this
(they certainly address Mir issues in
Can't reproduce on wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526209
Title:
[regression] Clients of nested Mir servers silently crash/exit
instantly
To manage notifications about this bu
Please clarify how to reproduce:
If run from a terminal window we don't need any of the "sudo's" as we
simply load up the Mir-on-X stack and connect via $DISPLAY. In any case,
sudo should only be require for the host mir server when using kms
(--arw-file will make the endpoint accessible to all).
Missing information to aid reproducing:
1. Are you running from a terminal, a VT or a ssh session?
1.1. AFAICS the commands as given in the instructions can only work from a
terminal session, but Mir-on-X doesn't *need* "sudo", so what happens without
"sudo"?
2. Are you running a local build?
** Changed in: mir
Milestone: 0.20.0 => 0.21.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240909
Title:
[performance] Restore support for better-than-triple buffering by
default.
To manag
** Changed in: mir
Milestone: 0.20.0 => 0.21.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262116
Title:
Nested servers prevent overlays or fullscreen bypass from working
To manage notificat
** Changed in: mir
Milestone: 0.20.0 => 0.21.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536662
Title:
[regression] Black screen: Mir hangs and then crashes on login due to
reading from /
** Changed in: mir
Milestone: 0.20.0 => 0.21.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1544878
Title:
Mir servers crash if I press the side mouse button (thumb)
To manage notifications ab
Fix landed in 0.19.2
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
Title:
unity-system-compositor crashed with std::runtime_er
As a note to Chris's comment #9:
While what is being asked for is state associated with a surface, it
isn't a distinct "surface state".
If modelled as surface state it requires at least new two states
mir_surface_state_automatic_restored and
mir_surface_state_automatic_fullscreen (and possibly
mi
My concerns are threefold:
1. there is no good name for this feature: "automatic" doesn't capture specific
behaviour;
2. I don't understand why this specific use case needs any special support; and,
3. what advantage is expected from Mir being involved?
As discussed above:
Clients can implement
** Branch linked: lp:~alan-griffiths/mir/add-
mir_surface_spec_set_shell_chrome
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535397
Title:
[enhancement] Implement support for QWindow::visibility
I don't think MultiThreadedCompositor::start()/stop() locking is the
real issue. They are only called by MirScreen's "*_l()" functions which
(if I understand the convention correctly) should only be invoked under
lock of its mutex.
However, usc::MirScreen::power_off_alarm_notification() calls
con
Actually, I've misunderstood. power_off_alarm_notification() is only
called from MirScreen::PowerOffLockableCallback - which acquires the
lock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
Ti
Digging into the code (without being able to reproduce) the likeliest
cause seems to be incorrect error handling in
mir::compositor::CompositingFunctor::operator()().
In Mir 0.18 this function can plausibly terminate via an exception
before setting the promise (on line 116) - it has a catch block,
Agreed, this is the behaviour I'd expect lp:1528384 to exhibit. Occum's
razor suggests we don't needlessly look for another explanation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
** Branch linked: lp:~alan-griffiths/mir/better-error-reporting-in-
MultiThreadedCompositor-start
** Changed in: mir
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
** Changed in: unity-system-compositor
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
** Chan
** Branch linked: lp:~alan-griffiths/unity-system-compositor/report-
warnings-instead-of-crashing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
Title:
unity-system-compositor crashed with
Note:
lp:~alan-griffiths/mir/better-error-reporting-in-MultiThreadedCompositor-start
lp:~alan-griffiths/unity-system-compositor/report-warnings-instead-of-crashing
These linked branches may not be a full solution but:
1. they log the underlying problem (which is "eaten" by
I would guess that the correct dependency would be mir-graphics-drivers-
desktop.
Mir itself doesn't depend on either mir-graphics-drivers-desktop nor
mir-graphics-drivers-android to avoid pulling both.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Branch linked: lp:~alan-griffiths/mir/fix-1526658
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526658
Title:
Mir clients (including Unity8 itself) crash in XGetXCBConnection() if
multiple
: (unassigned) => Alan Griffiths (alan-griffiths)
** Changed in: mir
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376324
Title:
/usr/sbin/unity-system-comp
I've not been able to reproduce yet[1], but looking at the code I can't
see anything that prevents a buffer stream being owned by the compositor
(for composition) after the corresponding Surface and Session have been
closed. If that then attempts to "complete" a buffer swap then we would
see the ab
Our experience clearly differs.
I find that it is often the second free of a block that triggers the
error. As the occasions when the free list has previously been corrupted
take disproportionately more time to solve I'm hoping this is an "easy"
one. ;)
--
You received this bug notification beca
** Branch linked: lp:~alan-griffiths/mir/fix-1376324
** Changed in: mir
Status: Incomplete => 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/1376324
Title:
/usr/sbin/unity-sys
There are a number of reasons for not fixing and "the team has decided
to move to C++14 instead" is not one of them.
Trusty has out of date versions of a number of build dependencies:
android headers, gmock and g++ all cause problems. There are also binary
compatibility issues between g++4.8 and g
alan_g: the next update is tracked here:
https://launchpad.net/canonical-devices-system-image/+milestone/ww51-2014
alan_g: that's also the project name to connect the bug to
the product team will triage it and set the importance to approve or
defer the fix
** Also affects: canonical-devices-s
** Branch linked: lp:~alan-griffiths/mir/fix-1377968-backport-to-0.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377968
Title:
a prompt session with an invalid application pid should be an error
The abort in this (and related) tests is correct: it is the behaviour
being tested for.
The error is in such tests being reported by Ubuntu Error Tracker - is
there any way to flag executables as "do not error track"?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
- just
not pushed to the website.)
--
Alan Griffiths +44 (0)798 9938 758
Octopull Ltdhttp://www.octopull.co.uk/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256116
Title:
Documentation i
** Changed in: mir (Ubuntu)
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
** Changed in: mir (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.ne
I'm not sure what's causing the observed symptoms - certainly calling
set_focus_to() does seem to invoke SurfaceStack::raise() as seen in the
integration test added in the linked branch.
** Branch linked: lp:~alan-griffiths/mir/fix-1302689
--
You received this bug notification because
the problems seems to be getting hold of the MirConnection to call this
(and other) APIs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313832
Title:
[enhancement] Allow nested mirservers to listen
Kevin, looks like you're seeing bug 1271604 can you rm
$XDG_RUNTIME_DIR/mir_socket and retry?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262754
Title:
Intermittent acceptance test failure in
D
I've tried to reproduce. The only way I can get the above error is to
omit "LD_PRELOAD=libumockdev-preload.so.0" when running the unit tests.
Either ctest or make test seems to work. As does:
$ LD_PRELOAD=libumockdev-preload.so.0 bin/mir_unit_tests
--
You received this bug notification because
I think a significant part of the problem experienced is bug 1284739
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279422
Title:
[enhancement] permit clients to perform prep logic while screen is
A better solution is to ensure that we don't leave stale sockets on
exit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235159
Title:
Mir fails to start if there's a stale socket
To manage notific
** Changed in: mir (Ubuntu)
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235159
Title:
Mir fails to start if there's a stal
** Branch linked: lp:~alan-griffiths/mir/remove-endpoint-first-when-
shutting-down
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235159
Title:
Mir fails to start if there's a stale socke
** Changed in: mir (Ubuntu)
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235159
Title:
Mir fails to start if there's a stal
** Branch linked: lp:~mir-team/mir/fix-1236912
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236912
Title:
please use XDG_RUNTIME_DIR instead of /tmp for mir_socket
To manage notifications about t
> terminate called after throwing an instance of 'std::system_error'
> what(): Operation not permitted
...
> #7 0x40606f8a in std::__throw_system_error (__i=1) at
> ../../../../../src/libstdc++-v3/src/c++11/functexcept.cc:104
> #8 0x420245fc in mir::client::DisplayConfiguration::copy_to_client()
In Progress
** Changed in: mir (Ubuntu)
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1342694
Title:
qmlscene crashed with SIGS
** Branch linked: lp:~mir-team/mir/enable-late-release-0.5-backport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1342694
Title:
qmlscene crashed with SIGSEGV in _M_release() on quit
To manage noti
This looks like a likely cause:
$ cat libmirclient-dev.install
usr/include/mirclient
usr/lib/*/pkgconfig/mirclient.pc
usr/lib/*/libmirclient.so
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297100
T
Oops - is the cause the "Recommends: mir-doc"? If that is installed then
so are the -dev packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297100
Title:
Installing mir-demos also unexpectedly
** Changed in: mir
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
** Changed in: mir
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/1297100
Workaround in #7 worked for me.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1102960
Title:
dia crashes on startup
To manage notifications about this bug go to:
https://bugs.launchpad.net/
401 - 500 of 520 matches
Mail list logo