[Touch-packages] [Bug 1415321] Re: [regression] Client functions residing in libmircommon
** Branch linked: lp:ubuntu/wily-proposed/mir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1415321 Title: [regression] Client functions residing in libmircommon Status in Mir: Fix Released Status in mir package in Ubuntu: Triaged Bug description: We seem to now have a bunch of client functions living in libmircommon: $ nm -D lib/libmircommon.so | grep ' mir_' 00010287 T mir_event_get_close_surface_event 0001012a T mir_event_get_input_event 00010264 T mir_event_get_orientation_event 00010241 T mir_event_get_prompt_session_event 0001021e T mir_event_get_resize_event 000101fb T mir_event_get_surface_event 00010105 T mir_event_get_type 0001038e T mir_event_ref 000103c6 T mir_event_unref 0002dae2 T mir_input_event_get_device_id 0002dbea T mir_input_event_get_event_time 0002dcf0 T mir_input_event_get_key_input_event 0002e5b5 T mir_input_event_get_pointer_input_event 0002e003 T mir_input_event_get_touch_input_event 0002d9d8 T mir_input_event_get_type 0002ddc9 T mir_key_input_event_get_action 0002de1e T mir_key_input_event_get_key_code 0002dfab T mir_key_input_event_get_modifiers 0002de43 T mir_key_input_event_get_scan_code 00010368 T mir_orientation_event_get_direction 0002e6bb T mir_pointer_input_event_get_action 0002e7d9 T mir_pointer_input_event_get_axis_value 0002e733 T mir_pointer_input_event_get_button_state 0002e68f T mir_pointer_input_event_get_modifiers 00010342 T mir_prompt_session_event_get_state 0001031c T mir_resize_event_get_height 000102f6 T mir_resize_event_get_width 000102aa T mir_surface_event_get_attribute 000102d0 T mir_surface_event_get_attribute_value 0002dfd7 T mir_touch_input_event_get_modifiers 0002e1df T mir_touch_input_event_get_touch_action 0002e453 T mir_touch_input_event_get_touch_axis_value 0002e0dd T mir_touch_input_event_get_touch_count 0002e0f7 T mir_touch_input_event_get_touch_id 0002e349 T mir_touch_input_event_get_touch_tooltype I think this could cause serious risk to clients/toolkits that call them. As their symbol versions are no longer tied to the stable client ABI, but instead tied to the more volatile mircommon ABI. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1415321/+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
[Touch-packages] [Bug 1415321] Re: [regression] Client functions residing in libmircommon
** Changed in: mir Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1415321 Title: [regression] Client functions residing in libmircommon Status in Mir: Fix Released Status in mir package in Ubuntu: Triaged Bug description: We seem to now have a bunch of client functions living in libmircommon: $ nm -D lib/libmircommon.so | grep ' mir_' 00010287 T mir_event_get_close_surface_event 0001012a T mir_event_get_input_event 00010264 T mir_event_get_orientation_event 00010241 T mir_event_get_prompt_session_event 0001021e T mir_event_get_resize_event 000101fb T mir_event_get_surface_event 00010105 T mir_event_get_type 0001038e T mir_event_ref 000103c6 T mir_event_unref 0002dae2 T mir_input_event_get_device_id 0002dbea T mir_input_event_get_event_time 0002dcf0 T mir_input_event_get_key_input_event 0002e5b5 T mir_input_event_get_pointer_input_event 0002e003 T mir_input_event_get_touch_input_event 0002d9d8 T mir_input_event_get_type 0002ddc9 T mir_key_input_event_get_action 0002de1e T mir_key_input_event_get_key_code 0002dfab T mir_key_input_event_get_modifiers 0002de43 T mir_key_input_event_get_scan_code 00010368 T mir_orientation_event_get_direction 0002e6bb T mir_pointer_input_event_get_action 0002e7d9 T mir_pointer_input_event_get_axis_value 0002e733 T mir_pointer_input_event_get_button_state 0002e68f T mir_pointer_input_event_get_modifiers 00010342 T mir_prompt_session_event_get_state 0001031c T mir_resize_event_get_height 000102f6 T mir_resize_event_get_width 000102aa T mir_surface_event_get_attribute 000102d0 T mir_surface_event_get_attribute_value 0002dfd7 T mir_touch_input_event_get_modifiers 0002e1df T mir_touch_input_event_get_touch_action 0002e453 T mir_touch_input_event_get_touch_axis_value 0002e0dd T mir_touch_input_event_get_touch_count 0002e0f7 T mir_touch_input_event_get_touch_id 0002e349 T mir_touch_input_event_get_touch_tooltype I think this could cause serious risk to clients/toolkits that call them. As their symbol versions are no longer tied to the stable client ABI, but instead tied to the more volatile mircommon ABI. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1415321/+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
[Touch-packages] [Bug 1415321] Re: [regression] Client functions residing in libmircommon
Fix reverted in lp:mir rev 2409. ** Changed in: mir Status: Fix Committed = Triaged ** Changed in: mir Assignee: Alan Griffiths (alan-griffiths) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1415321 Title: [regression] Client functions residing in libmircommon Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Bug description: We seem to now have a bunch of client functions living in libmircommon: $ nm -D lib/libmircommon.so | grep ' mir_' 00010287 T mir_event_get_close_surface_event 0001012a T mir_event_get_input_event 00010264 T mir_event_get_orientation_event 00010241 T mir_event_get_prompt_session_event 0001021e T mir_event_get_resize_event 000101fb T mir_event_get_surface_event 00010105 T mir_event_get_type 0001038e T mir_event_ref 000103c6 T mir_event_unref 0002dae2 T mir_input_event_get_device_id 0002dbea T mir_input_event_get_event_time 0002dcf0 T mir_input_event_get_key_input_event 0002e5b5 T mir_input_event_get_pointer_input_event 0002e003 T mir_input_event_get_touch_input_event 0002d9d8 T mir_input_event_get_type 0002ddc9 T mir_key_input_event_get_action 0002de1e T mir_key_input_event_get_key_code 0002dfab T mir_key_input_event_get_modifiers 0002de43 T mir_key_input_event_get_scan_code 00010368 T mir_orientation_event_get_direction 0002e6bb T mir_pointer_input_event_get_action 0002e7d9 T mir_pointer_input_event_get_axis_value 0002e733 T mir_pointer_input_event_get_button_state 0002e68f T mir_pointer_input_event_get_modifiers 00010342 T mir_prompt_session_event_get_state 0001031c T mir_resize_event_get_height 000102f6 T mir_resize_event_get_width 000102aa T mir_surface_event_get_attribute 000102d0 T mir_surface_event_get_attribute_value 0002dfd7 T mir_touch_input_event_get_modifiers 0002e1df T mir_touch_input_event_get_touch_action 0002e453 T mir_touch_input_event_get_touch_axis_value 0002e0dd T mir_touch_input_event_get_touch_count 0002e0f7 T mir_touch_input_event_get_touch_id 0002e349 T mir_touch_input_event_get_touch_tooltype I think this could cause serious risk to clients/toolkits that call them. As their symbol versions are no longer tied to the stable client ABI, but instead tied to the more volatile mircommon ABI. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1415321/+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
[Touch-packages] [Bug 1415321] Re: [regression] Client functions residing in libmircommon
This bug can be treated as Medium priority, so long as we're careful to not bump the common ABI. Treat it like the client ABI for now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1415321 Title: [regression] Client functions residing in libmircommon Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Bug description: We seem to now have a bunch of client functions living in libmircommon: $ nm -D lib/libmircommon.so | grep ' mir_' 00010287 T mir_event_get_close_surface_event 0001012a T mir_event_get_input_event 00010264 T mir_event_get_orientation_event 00010241 T mir_event_get_prompt_session_event 0001021e T mir_event_get_resize_event 000101fb T mir_event_get_surface_event 00010105 T mir_event_get_type 0001038e T mir_event_ref 000103c6 T mir_event_unref 0002dae2 T mir_input_event_get_device_id 0002dbea T mir_input_event_get_event_time 0002dcf0 T mir_input_event_get_key_input_event 0002e5b5 T mir_input_event_get_pointer_input_event 0002e003 T mir_input_event_get_touch_input_event 0002d9d8 T mir_input_event_get_type 0002ddc9 T mir_key_input_event_get_action 0002de1e T mir_key_input_event_get_key_code 0002dfab T mir_key_input_event_get_modifiers 0002de43 T mir_key_input_event_get_scan_code 00010368 T mir_orientation_event_get_direction 0002e6bb T mir_pointer_input_event_get_action 0002e7d9 T mir_pointer_input_event_get_axis_value 0002e733 T mir_pointer_input_event_get_button_state 0002e68f T mir_pointer_input_event_get_modifiers 00010342 T mir_prompt_session_event_get_state 0001031c T mir_resize_event_get_height 000102f6 T mir_resize_event_get_width 000102aa T mir_surface_event_get_attribute 000102d0 T mir_surface_event_get_attribute_value 0002dfd7 T mir_touch_input_event_get_modifiers 0002e1df T mir_touch_input_event_get_touch_action 0002e453 T mir_touch_input_event_get_touch_axis_value 0002e0dd T mir_touch_input_event_get_touch_count 0002e0f7 T mir_touch_input_event_get_touch_id 0002e349 T mir_touch_input_event_get_touch_tooltype I think this could cause serious risk to clients/toolkits that call them. As their symbol versions are no longer tied to the stable client ABI, but instead tied to the more volatile mircommon ABI. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1415321/+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
[Touch-packages] [Bug 1415321] Re: [regression] Client functions residing in libmircommon
** Changed in: mir Assignee: (unassigned) = Alan Griffiths (alan-griffiths) ** Changed in: mir Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1415321 Title: [regression] Client functions residing in libmircommon Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: We seem to now have a bunch of client functions living in libmircommon: $ nm -D lib/libmircommon.so | grep ' mir_' 00010287 T mir_event_get_close_surface_event 0001012a T mir_event_get_input_event 00010264 T mir_event_get_orientation_event 00010241 T mir_event_get_prompt_session_event 0001021e T mir_event_get_resize_event 000101fb T mir_event_get_surface_event 00010105 T mir_event_get_type 0001038e T mir_event_ref 000103c6 T mir_event_unref 0002dae2 T mir_input_event_get_device_id 0002dbea T mir_input_event_get_event_time 0002dcf0 T mir_input_event_get_key_input_event 0002e5b5 T mir_input_event_get_pointer_input_event 0002e003 T mir_input_event_get_touch_input_event 0002d9d8 T mir_input_event_get_type 0002ddc9 T mir_key_input_event_get_action 0002de1e T mir_key_input_event_get_key_code 0002dfab T mir_key_input_event_get_modifiers 0002de43 T mir_key_input_event_get_scan_code 00010368 T mir_orientation_event_get_direction 0002e6bb T mir_pointer_input_event_get_action 0002e7d9 T mir_pointer_input_event_get_axis_value 0002e733 T mir_pointer_input_event_get_button_state 0002e68f T mir_pointer_input_event_get_modifiers 00010342 T mir_prompt_session_event_get_state 0001031c T mir_resize_event_get_height 000102f6 T mir_resize_event_get_width 000102aa T mir_surface_event_get_attribute 000102d0 T mir_surface_event_get_attribute_value 0002dfd7 T mir_touch_input_event_get_modifiers 0002e1df T mir_touch_input_event_get_touch_action 0002e453 T mir_touch_input_event_get_touch_axis_value 0002e0dd T mir_touch_input_event_get_touch_count 0002e0f7 T mir_touch_input_event_get_touch_id 0002e349 T mir_touch_input_event_get_touch_tooltype I think this could cause serious risk to clients/toolkits that call them. As their symbol versions are no longer tied to the stable client ABI, but instead tied to the more volatile mircommon ABI. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1415321/+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
[Touch-packages] [Bug 1415321] Re: [regression] Client functions residing in libmircommon
** Branch linked: lp:~alan-griffiths/mir/fix-1415321 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1415321 Title: [regression] Client functions residing in libmircommon Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: We seem to now have a bunch of client functions living in libmircommon: $ nm -D lib/libmircommon.so | grep ' mir_' 00010287 T mir_event_get_close_surface_event 0001012a T mir_event_get_input_event 00010264 T mir_event_get_orientation_event 00010241 T mir_event_get_prompt_session_event 0001021e T mir_event_get_resize_event 000101fb T mir_event_get_surface_event 00010105 T mir_event_get_type 0001038e T mir_event_ref 000103c6 T mir_event_unref 0002dae2 T mir_input_event_get_device_id 0002dbea T mir_input_event_get_event_time 0002dcf0 T mir_input_event_get_key_input_event 0002e5b5 T mir_input_event_get_pointer_input_event 0002e003 T mir_input_event_get_touch_input_event 0002d9d8 T mir_input_event_get_type 0002ddc9 T mir_key_input_event_get_action 0002de1e T mir_key_input_event_get_key_code 0002dfab T mir_key_input_event_get_modifiers 0002de43 T mir_key_input_event_get_scan_code 00010368 T mir_orientation_event_get_direction 0002e6bb T mir_pointer_input_event_get_action 0002e7d9 T mir_pointer_input_event_get_axis_value 0002e733 T mir_pointer_input_event_get_button_state 0002e68f T mir_pointer_input_event_get_modifiers 00010342 T mir_prompt_session_event_get_state 0001031c T mir_resize_event_get_height 000102f6 T mir_resize_event_get_width 000102aa T mir_surface_event_get_attribute 000102d0 T mir_surface_event_get_attribute_value 0002dfd7 T mir_touch_input_event_get_modifiers 0002e1df T mir_touch_input_event_get_touch_action 0002e453 T mir_touch_input_event_get_touch_axis_value 0002e0dd T mir_touch_input_event_get_touch_count 0002e0f7 T mir_touch_input_event_get_touch_id 0002e349 T mir_touch_input_event_get_touch_tooltype I think this could cause serious risk to clients/toolkits that call them. As their symbol versions are no longer tied to the stable client ABI, but instead tied to the more volatile mircommon ABI. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1415321/+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
[Touch-packages] [Bug 1415321] Re: [regression] Client functions residing in libmircommon
** Branch unlinked: lp:~alan-griffiths/mir/first-cut-at-lp1415321 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1415321 Title: [regression] Client functions residing in libmircommon Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: We seem to now have a bunch of client functions living in libmircommon: $ nm -D lib/libmircommon.so | grep ' mir_' 00010287 T mir_event_get_close_surface_event 0001012a T mir_event_get_input_event 00010264 T mir_event_get_orientation_event 00010241 T mir_event_get_prompt_session_event 0001021e T mir_event_get_resize_event 000101fb T mir_event_get_surface_event 00010105 T mir_event_get_type 0001038e T mir_event_ref 000103c6 T mir_event_unref 0002dae2 T mir_input_event_get_device_id 0002dbea T mir_input_event_get_event_time 0002dcf0 T mir_input_event_get_key_input_event 0002e5b5 T mir_input_event_get_pointer_input_event 0002e003 T mir_input_event_get_touch_input_event 0002d9d8 T mir_input_event_get_type 0002ddc9 T mir_key_input_event_get_action 0002de1e T mir_key_input_event_get_key_code 0002dfab T mir_key_input_event_get_modifiers 0002de43 T mir_key_input_event_get_scan_code 00010368 T mir_orientation_event_get_direction 0002e6bb T mir_pointer_input_event_get_action 0002e7d9 T mir_pointer_input_event_get_axis_value 0002e733 T mir_pointer_input_event_get_button_state 0002e68f T mir_pointer_input_event_get_modifiers 00010342 T mir_prompt_session_event_get_state 0001031c T mir_resize_event_get_height 000102f6 T mir_resize_event_get_width 000102aa T mir_surface_event_get_attribute 000102d0 T mir_surface_event_get_attribute_value 0002dfd7 T mir_touch_input_event_get_modifiers 0002e1df T mir_touch_input_event_get_touch_action 0002e453 T mir_touch_input_event_get_touch_axis_value 0002e0dd T mir_touch_input_event_get_touch_count 0002e0f7 T mir_touch_input_event_get_touch_id 0002e349 T mir_touch_input_event_get_touch_tooltype I think this could cause serious risk to clients/toolkits that call them. As their symbol versions are no longer tied to the stable client ABI, but instead tied to the more volatile mircommon ABI. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1415321/+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
[Touch-packages] [Bug 1415321] Re: [regression] Client functions residing in libmircommon
** Branch linked: lp:~alan-griffiths/mir/first-cut-at-lp1415321 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1415321 Title: [regression] Client functions residing in libmircommon Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: We seem to now have a bunch of client functions living in libmircommon: $ nm -D lib/libmircommon.so | grep ' mir_' 00010287 T mir_event_get_close_surface_event 0001012a T mir_event_get_input_event 00010264 T mir_event_get_orientation_event 00010241 T mir_event_get_prompt_session_event 0001021e T mir_event_get_resize_event 000101fb T mir_event_get_surface_event 00010105 T mir_event_get_type 0001038e T mir_event_ref 000103c6 T mir_event_unref 0002dae2 T mir_input_event_get_device_id 0002dbea T mir_input_event_get_event_time 0002dcf0 T mir_input_event_get_key_input_event 0002e5b5 T mir_input_event_get_pointer_input_event 0002e003 T mir_input_event_get_touch_input_event 0002d9d8 T mir_input_event_get_type 0002ddc9 T mir_key_input_event_get_action 0002de1e T mir_key_input_event_get_key_code 0002dfab T mir_key_input_event_get_modifiers 0002de43 T mir_key_input_event_get_scan_code 00010368 T mir_orientation_event_get_direction 0002e6bb T mir_pointer_input_event_get_action 0002e7d9 T mir_pointer_input_event_get_axis_value 0002e733 T mir_pointer_input_event_get_button_state 0002e68f T mir_pointer_input_event_get_modifiers 00010342 T mir_prompt_session_event_get_state 0001031c T mir_resize_event_get_height 000102f6 T mir_resize_event_get_width 000102aa T mir_surface_event_get_attribute 000102d0 T mir_surface_event_get_attribute_value 0002dfd7 T mir_touch_input_event_get_modifiers 0002e1df T mir_touch_input_event_get_touch_action 0002e453 T mir_touch_input_event_get_touch_axis_value 0002e0dd T mir_touch_input_event_get_touch_count 0002e0f7 T mir_touch_input_event_get_touch_id 0002e349 T mir_touch_input_event_get_touch_tooltype I think this could cause serious risk to clients/toolkits that call them. As their symbol versions are no longer tied to the stable client ABI, but instead tied to the more volatile mircommon ABI. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1415321/+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
[Touch-packages] [Bug 1415321] Re: [regression] Client functions residing in libmircommon
The problem's getting worse. We now have server code using these... src/server/shell/abstract_shell.cpp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1415321 Title: [regression] Client functions residing in libmircommon Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Bug description: We seem to now have a bunch of client functions living in libmircommon: $ nm -D lib/libmircommon.so | grep ' mir_' 00010287 T mir_event_get_close_surface_event 0001012a T mir_event_get_input_event 00010264 T mir_event_get_orientation_event 00010241 T mir_event_get_prompt_session_event 0001021e T mir_event_get_resize_event 000101fb T mir_event_get_surface_event 00010105 T mir_event_get_type 0001038e T mir_event_ref 000103c6 T mir_event_unref 0002dae2 T mir_input_event_get_device_id 0002dbea T mir_input_event_get_event_time 0002dcf0 T mir_input_event_get_key_input_event 0002e5b5 T mir_input_event_get_pointer_input_event 0002e003 T mir_input_event_get_touch_input_event 0002d9d8 T mir_input_event_get_type 0002ddc9 T mir_key_input_event_get_action 0002de1e T mir_key_input_event_get_key_code 0002dfab T mir_key_input_event_get_modifiers 0002de43 T mir_key_input_event_get_scan_code 00010368 T mir_orientation_event_get_direction 0002e6bb T mir_pointer_input_event_get_action 0002e7d9 T mir_pointer_input_event_get_axis_value 0002e733 T mir_pointer_input_event_get_button_state 0002e68f T mir_pointer_input_event_get_modifiers 00010342 T mir_prompt_session_event_get_state 0001031c T mir_resize_event_get_height 000102f6 T mir_resize_event_get_width 000102aa T mir_surface_event_get_attribute 000102d0 T mir_surface_event_get_attribute_value 0002dfd7 T mir_touch_input_event_get_modifiers 0002e1df T mir_touch_input_event_get_touch_action 0002e453 T mir_touch_input_event_get_touch_axis_value 0002e0dd T mir_touch_input_event_get_touch_count 0002e0f7 T mir_touch_input_event_get_touch_id 0002e349 T mir_touch_input_event_get_touch_tooltype I think this could cause serious risk to clients/toolkits that call them. As their symbol versions are no longer tied to the stable client ABI, but instead tied to the more volatile mircommon ABI. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1415321/+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
[Touch-packages] [Bug 1415321] Re: [regression] Client functions residing in libmircommon
** Changed in: mir (Ubuntu) Importance: Undecided = High ** Changed in: mir (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1415321 Title: [regression] Client functions residing in libmircommon Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Bug description: We seem to now have a bunch of client functions living in libmircommon: $ nm -D lib/libmircommon.so | grep ' mir_' 00010287 T mir_event_get_close_surface_event 0001012a T mir_event_get_input_event 00010264 T mir_event_get_orientation_event 00010241 T mir_event_get_prompt_session_event 0001021e T mir_event_get_resize_event 000101fb T mir_event_get_surface_event 00010105 T mir_event_get_type 0001038e T mir_event_ref 000103c6 T mir_event_unref 0002dae2 T mir_input_event_get_device_id 0002dbea T mir_input_event_get_event_time 0002dcf0 T mir_input_event_get_key_input_event 0002e5b5 T mir_input_event_get_pointer_input_event 0002e003 T mir_input_event_get_touch_input_event 0002d9d8 T mir_input_event_get_type 0002ddc9 T mir_key_input_event_get_action 0002de1e T mir_key_input_event_get_key_code 0002dfab T mir_key_input_event_get_modifiers 0002de43 T mir_key_input_event_get_scan_code 00010368 T mir_orientation_event_get_direction 0002e6bb T mir_pointer_input_event_get_action 0002e7d9 T mir_pointer_input_event_get_axis_value 0002e733 T mir_pointer_input_event_get_button_state 0002e68f T mir_pointer_input_event_get_modifiers 00010342 T mir_prompt_session_event_get_state 0001031c T mir_resize_event_get_height 000102f6 T mir_resize_event_get_width 000102aa T mir_surface_event_get_attribute 000102d0 T mir_surface_event_get_attribute_value 0002dfd7 T mir_touch_input_event_get_modifiers 0002e1df T mir_touch_input_event_get_touch_action 0002e453 T mir_touch_input_event_get_touch_axis_value 0002e0dd T mir_touch_input_event_get_touch_count 0002e0f7 T mir_touch_input_event_get_touch_id 0002e349 T mir_touch_input_event_get_touch_tooltype I think this could cause serious risk to clients/toolkits that call them. As their symbol versions are no longer tied to the stable client ABI, but instead tied to the more volatile mircommon ABI. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1415321/+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
