This bug was fixed in the package mir - 0.8.1+15.04.20150112.2~rtm-
0ubuntu1
---
mir (0.8.1+15.04.20150112.2~rtm-0ubuntu1) 14.09; urgency=medium
[ Daniel van Vugt ]
* Bug fix release 0.8.1 (https://launchpad.net/mir/+milestone/0.8.1)
- ABI summary: Servers need rebuilding,
** Branch linked: lp:ubuntu/utopic-proposed/mir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358191
Title:
[regression] Clients are crashing (SIGSEGV) on mir_connect() failure
To manage
This bug was fixed in the package mir - 0.7.0+14.10.20140829-0ubuntu1
---
mir (0.7.0+14.10.20140829-0ubuntu1) utopic; urgency=medium
[ Daniel van Vugt ]
* New upstream release 0.7.0 (https://launchpad.net/mir/+milestone/0.7.0)
- Enhancements:
. Test suite: Reworked
** Changed in: mir/0.7
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/1358191
Title:
[regression] Clients are crashing (SIGSEGV) on mir_connect() failure
** Changed in: mir
Status: Fix Committed = Fix Released
** Changed in: mir
Milestone: 0.8.0 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358191
Title:
[regression] Clients are
Fix committed to lp:mir/0.7 at revision 1880, scheduled for release in
Mir 0.7.0
** Changed in: mir/0.7
Assignee: (unassigned) = Alexandros Frantzis (afrantzis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:mir/0.7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358191
Title:
[regression] Clients are crashing (SIGSEGV) on mir_connect() failure
To manage notifications about this
** Changed in: mir/0.6
Status: Triaged = Won't Fix
** Changed in: mir
Milestone: 0.8.0 = 0.7.0
** Changed in: mir/0.7
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mir
Milestone: 0.7.0 = 0.8.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358191
Title:
[regression] Clients are crashing (SIGSEGV) on mir_connect() failure
To manage
** Branch linked: lp:~afrantzis/mir/fix-1358191-connect-segv
** Changed in: mir
Assignee: Daniel van Vugt (vanvugt) = Alexandros Frantzis (afrantzis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fix committed into lp:mir/devel at revision None, scheduled for release
in mir, milestone Unknown
** 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.
** Summary changed:
- [regression] Clients are crashing (SIGSEGV) on mir_connect()
+ [regression] Clients are crashing (SIGSEGV) on mir_connect() failure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mir
Milestone: 0.7.0 = 0.8.0
** Also affects: mir/0.7
Importance: Undecided
Status: New
** Changed in: mir/0.7
Importance: Undecided = Critical
** Changed in: mir/0.7
Status: New = Triaged
** Changed in: mir/0.7
Milestone: None = 0.7.0
--
You
** Tags added: touch-2014-08-28
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mir (Ubuntu)
Importance: Undecided = Critical
** Changed in: mir (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of
And today I can reproduce it again :)
ii libmirclient8:armhf
0.6.1+14.10.20140814-0ubuntu1 armhf
Display server for Ubuntu - client library
current build number: 203
device name: mako
channel: devel
alias: ubuntu-touch/utopic
last update: 2014-08-25 03:13:36
version
Ugh. Ignore comment #6. I've finally got my phone in a state where I can
reproduce the crash and it keeps happening even with r1834 reverted.
Same problem, but apparently r1834 didn't cause it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Branch linked: lp:~vanvugt/mir/fix-1358191
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358191
Title:
[regression] Clients are crashing (SIGSEGV) on mir_connect()
To manage notifications
Here's the valgrind output of the error from earlier in the day when I
could reproduce it (on mako):
==8894== Invalid read of size 4
==8894==at 0x4867B78:
std::_Sp_counted_base(__gnu_cxx::_Lock_policy)2::_M_weak_release()
(shared_ptr_base.h:190)
==8894==by 0x4866B39:
** Branch linked: lp:~afrantzis/mir/fix-1358191-connect-segv-spike
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358191
Title:
[regression] Clients are crashing (SIGSEGV) on mir_connect()
To
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
20 matches
Mail list logo
