Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • KWin KWin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 57
    • Issues 57
    • List
    • Boards
    • Service Desk
    • Milestones
  • Bugzilla
    • Bugzilla
  • Merge requests 156
    • Merge requests 156
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PlasmaPlasma
  • KWinKWin
  • Issues
  • #17
Closed
Open
Issue created Oct 19, 2020 by Bhushan Shah@bshah📱Developer

Re-work how we start the input-methods

Currently we start input-method process at start-up of the kwin_wayland. This is not feasible for several of the input-methods, for example, ibus provides the multiple components,

  • ibus-daemon
  • ibus-wayland (https://github.com/ibus/ibus/tree/master/client/wayland)
  • ibus panel

Now, if we start ibus-wayland as input-method, it will fail because the ibus-daemon is not running and it can not connect to it.

We can not start ibus-daemon before it, as display server is not started just yet, and it can't start ibus panel..

So ideally we need to allow the input-method clients to connect at later point, which brings question of how to handle security here? Use something similar to how screenshot bit works? It's worth noting that most input methods do not ship any kind of desktop files at all.

Assignee
Assign to
Time tracking