Yes, this is easily reproducible on krillin with the instructions
mentioned previously (mir_demo_server_shell + progressbar or
egltriangle).
--
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
** Description changed:
In some cases (like bug #1371593) unity8 crashes leaving the mir_socket
and mir_socket_trusted sockets in the filesystem. When unity8 tries to
restart it fails with "bind: address already in use" because of the left
over mir_socket_trusted.
There are two aspect
** Description changed:
In some cases (like bug #1371593) unity8 crashes leaving the mir_socket
and mir_socket_trusted sockets in the filesystem. When unity8 tries to
restart it fails with "bind: address already in use" because of the left
over mir_socket_trusted.
There are two aspect
Public bug reported:
In some cases (like bug #1371593) unity8 crashes leaving the mir_socket
and mir_socket_trusted sockets in the filesystem. When unity8 tries to
restart it fails with "bind: address already in use" because of the left
over mir_socket_trusted.
There are two aspects to this bug:
Public bug reported:
Unity8 crashes on 'sudo stop lightdm' with the following error in the
log:
terminate called after throwing an instance of 'std::runtime_error'
what(): org.freedesktop.DBus.Error.Disconnected: Connection is closed
Backtrace is:
#0 __libc_do_syscall () at
../ports/sysdep
I am still having trouble consistently hitting the "delete number"
button in the latest images, since one needs to be very exact when doing
so (especially when using the thumb), which is frustrating.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
** Also affects: mir/0.7
Importance: Undecided
Status: New
** Changed in: mir/0.7
Milestone: None => 0.7.2
** Changed in: mir/0.7
Status: New => Fix Committed
** Changed in: mir/0.7
Importance: Undecided => High
** Changed in: mir/0.7
Assignee: (unassigned) => Danie
Have we seen this recently?
--
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/1292472
Title:
unity8 crashed with what(): Requesting handle for an unregistered
channel
Status
The core issue seems to be that in this scenario the platform shared
library is unloaded before the configuration object is being destroyed.
The configuration object is holding a weak pointer to a shared pointer
object (shared_ptr for the client platform factory) that was
instantiated inside the pl
** Changed in: unity-system-compositor
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1343919
Title:
USC does no
** Changed in: mir
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: mir
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
As I mentioned before, the failures shown in both the errors.u.c reports
(and which are really confusing, I don't really trust the backtraces to
be correct there, they don't make much sense) and the original
backtrace, just indicate that that the server has died and the clients
fail to communicate
** Changed in: mir
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: mir
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Changed in: qtubuntu
Status: Fix Committed => Fix Released
--
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/1237052
Title:
Apps that close themselves crash trying
** Changed in: unity-system-compositor
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1339843
Title:
Last user s
** Branch linked: lp:~alan-griffiths/mir/fix-1297100
--
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/1297100
Title:
Installing mir-demos also unexpectedly installs *-dev packag
My understanding of the traces: the clients are failing because the
server has crashed (or is otherwise unreachable). The problem seems to
be that the failure happens in the context of a callback from the
Android driver which presumably doesn't handle C++ exceptions well
(probably not at all), caus
The crash as retraced in https://bugs.launchpad.net/ubuntu/+bug/1340571
, is caused by qtubuntu not being able to connect to the mir
server/shell. It doesn't necessarily indicate there is a problem in
qtubuntu (of course it doesn't preclude it either). For example you
would get the same "crash" if
igating.
** Changed in: mir
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
--
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/1335481
Title:
unity-system-
This seems related to https://code.launchpad.net/~mir-
team/mir/fix-1339700/+merge/226233 , so it may be a different
manifestation of bug 1339700.
>From Alberto's last comment in the MP above:
"Ok, after staring at TimeoutFrameDroppingPolicy there are scenarios
that can lead to an assert." (refe
201 - 220 of 220 matches
Mail list logo
