Yup, this looks like a Mir crash IMO:
#0 0xffffffff in
mir::graphics::nested::InputPlatform::InputDevice::emit_event(MirInputEvent
const*, mir::geometry::Rectangle const&) (this=0xe7f53350,
event=event@entry=0xd61f8cb8, frame=...)
at
/build/mir-V80GEw/mir-0.24.0+15.04.20160815.3/src/server/graphics/nested/input_platform.cpp:131
pointer_event = <optimized out>
new_event =
{_M_t = {<std::_Tuple_impl> = {<std::_Tuple_impl> =
{<std::_Tuple_impl> = {<No data fields>}, <std::_Head_base> = {_M_head_impl =
0xe9ad4bfc}, <No data fields>}, <std::_Head_base> = {_M_head_impl =
0x4252d328}, <No data fields>}, <No data fields>}}
x = <optimized out>
y = <optimized out>
type = mir_input_event_type_pointer
#1 0xffffffff in std::_Function_handler::_M_invoke(std::_Any_data const&,
MirEvent const&, mir::geometry::Rectangle const&) (area=..., event=...,
__closure=0xe7f0cd20)
at
/build/mir-V80GEw/mir-0.24.0+15.04.20160815.3/src/server/graphics/nested/input_platform.cpp:225
input_ev = 0xd61f8cb8
id = 6
event_type = <optimized out>
this = 0xf1bef72c
#2 0xffffffff in std::_Function_handler::_M_invoke(std::_Any_data const&,
MirEvent const&, mir::geometry::Rectangle const&) (__functor=..., __args#0=...,
__args#1=...) at /usr/include/c++/4.9/functional:2039
#3 0xffffffff in
mir::graphics::nested::detail::DisplayBuffer::event_thunk(MirSurface*, MirEvent
const*, void*) (__args#1=..., __args#0=..., this=<optimized out>) at
/usr/include/c++/4.9/functional:2439
event = @0xd61f8cb8: {type_ = mir_event_type_motion}
this = <optimized out>
#4 0xffffffff in
mir::graphics::nested::detail::DisplayBuffer::event_thunk(MirSurface*, MirEvent
const*, void*) (source_frame=..., event=..., this=<optimized out>)
at
/build/mir-V80GEw/mir-0.24.0+15.04.20160815.3/src/server/graphics/nested/mir_client_host_connection.cpp:419
event = @0xd61f8cb8: {type_ = mir_event_type_motion}
this = <optimized out>
#5 0xffffffff in
mir::graphics::nested::detail::DisplayBuffer::event_thunk(MirSurface*, MirEvent
const*, void*) (event=..., this=<optimized out>)
at
/build/mir-V80GEw/mir-0.24.0+15.04.20160815.3/src/server/graphics/nested/display_buffer.cpp:115
event = @0xd61f8cb8: {type_ = mir_event_type_motion}
this = <optimized out>
** Attachment added: "gdb.txt"
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619720/+attachment/4734703/+files/gdb.txt
** Changed in: unity8 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: canonical-devices-system-image
Assignee: Michał Sawicz (saviq) => Stephen M. Webb (bregma)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1619720
Title:
Unity8 sometimes crashes after Bluetooth reconnect
Status in Canonical System Image:
Confirmed
Status in Mir:
New
Status in mir package in Ubuntu:
New
Status in unity8 package in Ubuntu:
Invalid
Bug description:
Test case.
- In System Settings, pair a Bluetooth keyboard and mouse.
- Wait some minutes so keyboard and mouse suspend.
- Reboot the device.
- Start typing on the password prompt and move the mouse.
Expected result.
- User can log in.
Actual result.
- Unity8 crashes.
It's not an accurate test case but has happened at least three times
in similar scenarios which involve waking up the keyboard (or mouse?).
current build number: 180
device name: frieza
channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
With silo 37.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1619720/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
