touch-packages team mailing list archive

[David Cesarino de Sousa <1464915@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

# PROBLEM DESCRIPTION

Input method does not work in the Unity Dash.

Currently, my input method defined in ~/.xinputrc is xim. The files
reads:

run_im xim

This allows me to keep a custom mapping of Compose sequences in
~/.XCompose. It works everywhere inside the graphical environment,
except in the Unity dash/Launcher, where keyboard sequences behave like
in a standard installation (i.e., without defining xim as input method).

# EXPECTED BEHAVIOR

I should be able to use my compose sequences defined in ~/.XCompose .
For example, one of the sequences is:

<dead_acute> <c>                        : "ç"   ccedilla # LATIN SMALL
LETTER C WITH CEDILLA

However, in the dash I get a ć (c-acute). See screenshot provided.

# CURRENT BEHAVIOR

None of my compose sequences in ~/.XCompose work. This problem happens
100% of the time.

# COMMAND OUTPUT

david@zurg:~$ lsb_release -rd
Description:	Ubuntu 15.04
Release:	15.04
david@zurg:~$ apt-cache policy unity
unity:
  Installed: 7.3.2+15.04.20150420-0ubuntu1
  Candidate: 7.3.2+15.04.20150420-0ubuntu1
  Version table:
 *** 7.3.2+15.04.20150420-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
        100 /var/lib/dpkg/status

** Affects: unity (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "Screenshot showing that compose sequences are wrong in dash."
   https://bugs.launchpad.net/bugs/1464915/+attachment/4414383/+files/unity_input_bug.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1464915

Title:
  Input method does not work in the Unity Dash

Status in unity package in Ubuntu:
  New

Bug description:
  # PROBLEM DESCRIPTION

  Input method does not work in the Unity Dash.

  Currently, my input method defined in ~/.xinputrc is xim. The files
  reads:

  run_im xim

  This allows me to keep a custom mapping of Compose sequences in
  ~/.XCompose. It works everywhere inside the graphical environment,
  except in the Unity dash/Launcher, where keyboard sequences behave
  like in a standard installation (i.e., without defining xim as input
  method).

  # EXPECTED BEHAVIOR

  I should be able to use my compose sequences defined in ~/.XCompose .
  For example, one of the sequences is:

  <dead_acute> <c>                        : "ç"   ccedilla # LATIN SMALL
  LETTER C WITH CEDILLA

  However, in the dash I get a ć (c-acute). See screenshot provided.

  # CURRENT BEHAVIOR

  None of my compose sequences in ~/.XCompose work. This problem happens
  100% of the time.

  # COMMAND OUTPUT

  david@zurg:~$ lsb_release -rd
  Description:	Ubuntu 15.04
  Release:	15.04
  david@zurg:~$ apt-cache policy unity
  unity:
    Installed: 7.3.2+15.04.20150420-0ubuntu1
    Candidate: 7.3.2+15.04.20150420-0ubuntu1
    Version table:
   *** 7.3.2+15.04.20150420-0ubuntu1 0
          500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
          100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1464915/+subscriptions