[Touch-packages] [Bug 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
** 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 qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Status in qtubuntu package in Ubuntu: In Progress Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
This bug was fixed in the package mir - 0.27.0+17.10.20170630-0ubuntu1 --- mir (0.27.0+17.10.20170630-0ubuntu1) artful; urgency=medium [ Daniel van Vugt ] * New upstream release 0.27.0 (https://launchpad.net/mir/+milestone/0.27.0) - ABI summary: . mirclient ABI unchanged at 9 . mirserver ABI bumped to 44 . mircommon ABI unchanged at 7 . mirplatform ABI bumped to 61 . mirprotobuf ABI unchanged at 3 . mirplatformgraphics ABI bumped to 13 . mirclientplatform ABI unchanged at 5 . mirinputplatform ABI bumped to 7 . mircore ABI unchanged at 1 - Enhancements: . Mostly groundwork required to support major enhancements coming in future Mir versions. . Removed android-input and eliminated the entire "3rd_party/" subtree. Now the Mir source tree contains original code only. . Added mir_prompt_session_new_fds_for_prompt_providers_sync API. . mirout: Added load and save options for keeping display configs on disk. . mirout: Added "--" support for applying configuration changes under Unity8. . Fixed failure of DRM hardware cursor {hide(); show(image);} . Added server option: "--cursor software" (MIR_SERVER_CURSOR=software) . Added letterboxing/black bars support to the GL renderer in preparation for generic output cloning. . Added client API for getting the logical size of an output. . Migrated MirCookie to use SHA-256. . Ensure RealKMSOutputConfiguration stays in sync with actual hardware state. . Added support for drag-and-drop. . Lots of other client API enhancements. . Minor clean-ups, optimizations and dead code removal. . Added support for building on Ubuntu 17.10 artful. . Update example code to use undeprecated API. . mesa-kms: Support hardware cursors in hybrid setups. . Rework and publish the graphics platform APIs - Bugs fixed: . [enhancement] Make able to get version information from client / server APIs (LP: #1195540) . Touch screen coordinates don't rotate with the screen (LP: #1349660) . Subpixel order not included in Mir display information (LP: #1393578) . [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows) (LP: #1420334) . Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching) (LP: #1536279) . NBS never uses mc::MultiMonitorMode::single_monitor_fast, even when only a single monitor is plugged in (LP: #1561418) . Inconsistent behaviour of Num Lock (LP: #1588237) . A scaled (not panned or clipped) mirror/clone mode is desired (LP: #1639226) . Rotating an output left or right without restarting the compositor distorts the image (LP: #1643488) . support display scaling slider in unity8 (LP: #1645372) . [ FAILED ] NestedInputWithMouse.mouse_pointer_coordinates_in_nested_ server_are_accumulated (LP: #1646375) . [ FAILED ] NestedInputWithMouse.mouse_pointer_position_is_in_sync_with_ host_server (LP: #1646558) . abi_check doesn't check mircore (LP: #1649354) . [testsfail] PromptSessionClientAPI.client_pid_is_associated_with_ session hangs and times out (LP: #1655929) . EDID does not change when hotplugging a monitor (LP: #1660017) . [regression] Mir 0.26.0 - spinner loading animation, minimize, maximize too fast (LP: #1661072) . [regression] Unity8 stutters constantly (like half frame rate) using Mir 0.26.0 (LP: #1661128) . [regression] mir_demo_server refuses to quit on Ctrl+Alt+Backspace or Ctrl+C in its terminal (deadlock in DefaultInputDeviceHub::add_device) (LP: #1661151) . [regression] mirout crashes when connecting to unity8 or any nested server: [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed: (index) < (current_size_): (LP: #1661163) . [ FAILED ] DefaultInputManagerTest.forwards_pause_continue_state_ changes_to_platform (LP: #1661187) . [regression] Segfault on detect_fd_leaks during acceptance tests (in DisplayConfiguration/{DisplayFormatSetting,DisplaySubpixelSetting}) (LP: #1661498) . [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] (LP: #1661508) . [regression] Windowed clients of nested servers are all black (LP: #1661521) . mir_window_request_persistent_id_sync seg faults when called twice (LP: #1661704) . mir_acceptance_tests now takes 10 seconds longer (in r4002 compared to r4001) (LP: #1662044) . Mir graphics platform ABI broke in series 0.26 but so
[Touch-packages] [Bug 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2818 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: In Progress Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-artful-2806 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: In Progress Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: In Progress Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
Don't think so, Alt+Up/Alt+Down don't have text attached. Also http://paste.ubuntu.com/24045824/ seems to report the same presses in both unity7 and unity8 -- 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/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: In Progress Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
Alt+Up and Alt+Down to switch between tabs in Kate also doesn't work currently. Could it have the same cause as this Ctrl+C issue? -- 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/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: In Progress Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 1.0.0 ** Changed in: mir Status: In Progress => Fix Committed -- 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/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: In Progress Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: In Progress Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: In Progress Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
** Changed in: mir Importance: Undecided => Medium ** Changed in: qtubuntu (Ubuntu) Importance: Undecided => Medium ** Changed in: qtubuntu (Ubuntu) Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) ** Changed in: mir Status: Confirmed => In Progress ** Changed in: qtubuntu (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
Went for the second approach key entry text is attached to every press and repeat event. ** Branch linked: lp:~andreas-pokorny/mir/fix-1664610 ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) ** Changed in: mir (Ubuntu) Assignee: Andreas Pokorny (andreas-pokorny) => (unassigned) ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) ** Package changed: mir (Ubuntu) => mir ** Changed in: mir Milestone: None => 1.0.0 -- 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/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: Confirmed Status in qtubuntu package in Ubuntu: New Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
Mir either has to expose the xkb_state (which we currently do not - and might be only on the server) or provide the keysym text directly with the event. ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => Confirmed ** Tags added: input -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in mir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: New Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1664610/+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