Note the root cause of the problem is possibly bug 1526658 (soon to be
Fix Released in Mir 0.19.0)
--
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
Fix Released in Mir 0.18.0. Although it's good to mention this bug got
different fixes between the 0.18 and 0.19 branches, it's probably still
best to only mention it in the changelog for one of them.
** Changed in: mir
Status: Fix Committed => Fix Released
** Changed in: mir
** Changed in: mir
Status: Fix Released => 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/1526209
Title:
[regression] Clients of nested Mir servers silently crash/exit
** Changed in: mir/0.18
Status: Fix Committed => Fix Released
** 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/1526209
Title:
Wrt to the segmentation fault more details in
https://bugs.launchpad.net/mir/+bug/1526658
--
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
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?
Yes i can also remember seeing that stacktrace when toying around with
our reload hack, to get mesa to find our symbols during egl display
detection. But I dont get that anymore on xenial with lp:mir or
lp:mir/0.18
--
You received this bug notification because you are a member of Ubuntu
Bugs,
So my problem noted in #8 was just a mis-match of packages on my system.
Cannot reproduce with xenial + silo 021, nor with on-system builds of
lp:mir, lp:mir/0.18, or lp:mir/0.17.
After standup today, it seems like we weren't able to reproduce the
problem, provided that we had updated systems,
I could not reproduce on xenial. Both mir-on-x and mesa worked for me.
Note that there is a known issue with the nested server not being able
to detect the platform (lp:1515558) so a '--vt' switch is needed on the
server for correct behaviour.
--
You received this bug notification because you
Haven't been able to confirm this specific scenario today, but another
issue (not a crash, rather incorrect platform loading) was noticed
related to rev 3098. Seems best to back out that rev for lp:mir and
lp:mir/0.18 release.
--
You received this bug notification because you are a member of
Connecting a software client to the affected nested server actually made
the nested server crash:
ERROR: /home/dan/bzr/mir/fixmirout/src/gl/recently_used_cache.cpp(44): Throw in
function virtual std::shared_ptr
mir::gl::RecentlyUsedCache::load(const mir::graphics::Renderable&)
Dynamic exception
Annoyingly bisection is going to be slow, because of a separate
regression - bug 1526225.
--
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
seems to be mesa-specific
--
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
Confirmed, reverting r3098 fixes the problem.
** Tags added: nested
--
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
Bisected. The problem originated in:
revno: 3098 [merge]
author: Cemil Azizoglu
committer: Tarmac
branch nick: development-branch
timestamp: Tue 2015-11-10 23:10:22 +
message:
Tighten probing rules.
I swear I've also seen Mir 0.17.1 fail similarly (Unity8 on xenial
desktop). I might be imagining things, or I might have been seeing some
side-effect of bug 1506707 that perhaps also led to similar problems?...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Branch linked: lp:~mir-team/mir/revert-3098
--
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
hmm, and now after doing a reinstall and upgrade of all packages (on
xenial), I can no longer reproduce the issue.
--
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
** Changed in: mir
Status: Incomplete => In Progress
** Changed in: mir
Assignee: (unassigned) => Mir development team (mir-team)
** Changed in: mir/0.18
Status: Incomplete => Triaged
** Changed in: mir (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
I also can see the nested server crash scenario when connecting
mir_demo_client_egltriangle. I haven't seen the client crash yet
--
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:
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
duflu, could you also try
1. with the '--vt' option ?
2. on another machine with a different GPU?
--
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
Fix committed into lp:mir at revision 3198, scheduled for release in
mir, milestone 0.19.0
** 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.
Fix committed to lp:mir/0.18 at revision 3182, scheduled for release in
Mir 0.18.0
** Changed in: mir/0.18
Status: Triaged => Fix Committed
** Changed in: mir/0.18
Assignee: (unassigned) => Mir development team (mir-team)
--
You received this bug notification because you are a
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).
25 matches
Mail list logo