Another duplicate today.
This bug in libmirclient is now causing Untiy8 to fail start-up
sometimes, and black-screen.
** Tags added: black-screen unity8-desktop
** Summary changed:
- libmirclient gives up and terminates prematurely with "std::exception::what:
disconnected: no new buffers" via
It wasn't till today, but finally there's a bug report of this happening
in the wild on desktop -> bug 1603739
** Changed in: mir
Milestone: None => 0.25.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mir
Milestone: 0.25.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/1506358
Title:
libmirclient gives up and terminates prematurely with
"std::exception::what:
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
"std::exception::what:
If there's an issue in the transport in
mclr::MirProtobufRpcChannel::send_message during the sending of the
message, it will trigger the disconnection code.
If the client happens to be mid-mir_buffer_stream_swap_buffers at the
same time that the the connection error trips the disconnection
I targeted to 0.24, should probably have a look, especially if we're
getting error reports from the 'field'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and
Hmm, if the server isn't dying, perhaps we're getting a false
disconnection signal from the rpc code?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and
And again from:
==3839== Process terminating with default action of signal 6 (SIGABRT)
==3839==at 0x6EB8418: raise (raise.c:54)
==3839==by 0x6EBA019: abort (abort.c:89)
==3839==by 0x7DE184C: __gnu_cxx::__verbose_terminate_handler() (in
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
==3369== Process terminating with default action of signal 6 (SIGABRT)
==3369==at 0x6EB8418: raise (raise.c:54)
==3369==by 0x6EBA019: abort (abort.c:89)
==3369==by 0x7DE184C: __gnu_cxx::__verbose_terminate_handler() (in
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
==3369==by
Still crashing the same way in xenial with Mir
0.21.0+16.04.20160330-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
** Changed in: canonical-devices-system-image
Milestone: 11 => backlog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => 11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
** Changed in: canonical-devices-system-image
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
** Changed in: canonical-devices-system-image
Milestone: ww04-2016 => ww08-2016
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely
This is expected behavior though when a nested server has its host
server die (so I'd say this as described doesnt really describe a
"bug")... The bug that this one was made a duplicate of seems to be the
root cause.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
In the description I mentioned the server does not die at all. Only the
client dies and the server keeps working (can reconnect to it).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
Dropped to High. If this bug only occurs /in the lab/ now then it's not
a blocker for the phone any more.
** Changed in: mir
Importance: Critical => High
** Changed in: mir (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- libmirclient gives up and exits prematurely with "std::exception::what:
disconnected: no new buffers" via ExchangeSemantics::submit()
+ libmirclient gives up and terminates prematurely with "std::exception::what:
disconnected: no new buffers" via
18 matches
Mail list logo