[FHD] gedit does not accept input in document window

Could this possibly be a duplicate of bug #1532862?

I could reproduce this on my frieza with John's image built mid of last week. However, I can not reproduce this with an up to date flo and also kdub's frieza with a self built image from tuesday would not suffer from this issue.

So I believe this might be fixed in more recent images. Can anyone confirm with newer images?

@townsend, no it's not a dupe of 1532862. We have a fix for 1532862 in the queue tho.

ok. still happening on the latest frieza image. I am very confident it's not an issue in unity8 tho. I'd require the legacy container stuff people to have a look at this.

Strange that it worked on a different Frieza when I tried it. Not really sure why there is different behavior on different Frieza's...

I've been working on mzanetti's Frieza and can definitely reproduce on it. I'm still trying to figure out what is causing this, but one strange thing is that if I start gedit via command line, it works as expected. At this point, I'm wondering if it's some environment variable causing the issue. I dumped the env var's and will compare....

After looking through the environment variables that are set between cases that are working and that aren't working, I found that DCONF_PROFILE=custom is being set in the case that is not working. Of course, there is no custom dconf profile inside of the Puritine chroot.

As a further test for my theory, I did "DCONF_PROFILE=custom gedit" on my normal Ubuntu machine and lo and behold, I could not type into the Gedit window just like on the Frieza.

I'm not really sure why DCONF_PROFILE=custom is being set on Frieza which should probably be investigated. I can also explicitly unset DCONF_PROFILE when launching apps in Puritine and in Libertine containers in general.

I assume this is a side effect of how custom tarballs set things on
'standard' phone images. penk can advise. But from what I know we need to
cope with this somehow in custom tarballs that contain puritine (either by
modifying how puritine is managed in that tarball, or puritine itself).

On 23 January 2016 at 03:01, Christopher Townsend <
<email address hidden>> wrote:

> After looking through the environment variables that are set between
> cases that are working and that aren't working, I found that
> DCONF_PROFILE=custom is being set in the case that is not working. Of
> course, there is no custom dconf profile inside of the Puritine chroot.
>
> As a further test for my theory, I did "DCONF_PROFILE=custom gedit" on
> my normal Ubuntu machine and lo and behold, I could not type into the
> Gedit window just like on the Frieza.
>
> I'm not really sure why DCONF_PROFILE=custom is being set on Frieza
> which should probably be investigated. I can also explicitly unset
> DCONF_PROFILE when launching apps in Puritine and in Libertine
> containers in general.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1536311
>
> Title:
> gedit does not accept input in document window
>
> Status in The Avila project:
> Confirmed
> Status in Canonical System Image:
> Confirmed
> Status in Puritine:
> In Progress
>
> Bug description:
> Using a recent pocket-desktop image, on freezer, set up your system
> with an external keyboard.
>
> Open Gedit, and attempt to type in the blank document it presents
>
> No characters are placed in the document.
>
> Expected result: characters in the document!
>
> Note that other key navigation seems ok (eg alt+key for menus), and
> input seems fine in other puritine apps (such as libreoffice)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/avila/+bug/1536311/+subscriptions
>

@penk, can you comment on #7 & #8 please?

Hi, indeed DCONF_PROFILE was set because custom tarball ships precompiled dconf db.

In current implementation I do think unsetting DCONF_PROFILE for apps in Puritine/Libertine is a feasible idea.

@townsend could it be a change to com.ubuntu.puritine package?

@penk,

I will have to make the change in Libertine itself, but yes it can be done.

I just hope that there aren't any other future surprise environment variable changes that affect applications running in the container:)

Fix committed into lp:libertine at revision 165, scheduled for release in libertine, milestone Unknown

How does this migrate to a rootfs in ubuntu-pd channel?

This bug was fixed in the package libertine - 0.99.9+16.04.20160128-0ubuntu1

---------------
libertine (0.99.9+16.04.20160128-0ubuntu1) xenial; urgency=medium

  [ Chris Townsend ]
  * puritine-click.conf: Instead of just creating the user-data dir,
    we should actually copy the contents of the click package's user-data
    in case there are things in it we need.
  * GUI: Add a page to the GUI to display basic package info for a
    container.
  * GUI: When using the GUI to install a container, remove the whole
    concept of choosing a distro and just use the host's installed distro
    as the container's distro. (LP: #1533731)
  * GUI: Add an info page for containers that reports various information
    about the chosen container.
  * libertine-container-manager: Add option to run arbitrary commands
    in a container.
  * GUI: Get the package version from the container when viewing the
    package info page.
  * python/libertine/ChrootContainer.py: Workaround issue where a custom
    dconf profile is on a machine. Of course the profile is not in the
    chroot, so it messes up some applications. (LP: #1536311)
  * debian/control: Revert r155 as this has an unintended effect of pulling
    in the kernel on phones when it's not needed.

  [ CI Train Bot ]
  * No-change rebuild.

 -- Christopher Townsend <email address hidden> Thu, 28 Jan 2016 17:57:04 +0000

Hi all,

The issue is fixed in r17 firmware version.

Best regards.

Hi @John,

OSK is not displayed in Gedit app with tablet mode active, but you are able to write in Convergence mode with a keyboard. It is a normal behaviour?.

Best regards.

Yes, that is the currently designed behaviour

On Friday, 19 February 2016, Javier Ibáñez <email address hidden> wrote:

> Hi @John,
>
> OSK is not displayed in Gedit app with tablet mode active, but you are
> able to write in Convergence mode with a keyboard. It is a normal
> behaviour?.
>
> Best regards.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1536311
>
> Title:
> gedit does not accept input in document window
>
> Status in The Avila project:
> Fix Released
> Status in Canonical System Image:
> Fix Released
> Status in Libertine:
> Fix Released
> Status in Puritine:
> Invalid
> Status in libertine package in Ubuntu:
> Fix Released
>
> Bug description:
> Using a recent pocket-desktop image, on freezer, set up your system
> with an external keyboard.
>
> Open Gedit, and attempt to type in the blank document it presents
>
> No characters are placed in the document.
>
> Expected result: characters in the document!
>
> Note that other key navigation seems ok (eg alt+key for menus), and
> input seems fine in other puritine apps (such as libreoffice)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/avila/+bug/1536311/+subscriptions
>