alan_g, why did you do that?
oh wait
yes
i know
so we should file it upstream?
first
maybe ask the maintainer if he'd want us to file it
The issue was we had a giant pile of C and C++ code we were trying to follow. This was our first foray into Mir, and the diff we made *very* hard to debug.
right
but we just need to upstream it
does mir-next do something like this?
Yes, but our upstream Mir devels wouldn't know if they wanted us to file it or not.
ahh
interesting
are you writing any of the downstream Mir?
or are you only maintaining it?
I'm only maintaining. The team is split between upstream and downstream Mir.
ah okay
so for right now we should just continue on with what we have
with bug 589106
Launchpad bug 589106 in mir (Ubuntu) "mir_demo_server_shell crashed with SIGABRT in __assert_fail_base()" [Medium,Triaged]
alan_g, do you think upstream will want us to follow up with this bug report as well?
we have similar bug reports
e.g. mir_demo_server_shell_accelerated_2.11.so crashed with SIGABRT in __assert_fail_base ()
upstream are used to getting bug reports in IRC and mailing lists. IMO they'd be happy to know about it here, but I can't speak for them.
okay
I'm out for the night. Night all
#ubuntu-mir 2015-08-27
RAOF: In case you missed the conversation earlier...
Related links: