Cannot type in evince search field in Ubuntu 13.10

[Benjamin ABEL]

Since I've upgraded to ubuntu 13.10, and evince 3.10.0, the search field doesn't works. I can't type any text on it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ubuntu version:
*** 3.10.0-0ubuntu2 0
        500 http://fr.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

Evince version:
*** 3.10.0-0ubuntu2 0
        500 http://fr.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Sebastien Bacher (seb128)]

Thank you for your bug report, I can't confirm that though. Does it happen on any document? What desktop do you use?

[Benjamin ABEL (bjn-abel-deactivatedaccount)]

I'm using Ubuntu13.10-64bits upgraded from the 13.04 version(AMD64).
Finally, I don't think the bug comes from evince because I downgraded to evince's version used in Ubuntu 13.04(Evince 3.6.1) and the search field doesn't works neither even if it was working previously when I was using Ubuntu 13.04 before I've upgraded to Ubuntu 13.10.
I can't test any other documents than pdf I only use this ones.

[Sebastien Bacher (seb128)]

The search feature is only available if the document is made of text (some are "images") ... did you try other pdf examples?

[Benjamin ABEL (bjn-abel-deactivatedaccount)]

Of couse i did. I switched to okular and the search field workds with these
documents.
Le 4 nov. 2013 14:05, "Sebastien Bacher" <email address hidden> a écrit :

> The search feature is only available if the document is made of text
> (some are "images") ... did you try other pdf examples?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1247621
>
> Title:
> Search field doesn't works in ubuntu 13.10
>
> Status in “evince” package in Ubuntu:
> Incomplete
>
> Bug description:
> Since I've upgraded to ubuntu 13.10, and evince 3.10.0, the search field
> doesn't works. I can't type any text on it.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Ubuntu version:
> *** 3.10.0-0ubuntu2 0
> 500 http://fr.archive.ubuntu.com/ubuntu/ saucy/main amd64
> Packages
>
> Evince version:
> *** 3.10.0-0ubuntu2 0
> 500 http://fr.archive.ubuntu.com/ubuntu/ saucy/main amd64
> Packages
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1247621/+subscriptions
>

[Sebastien Bacher (seb128)]

do you use unity? I still can't confirm that issue...

[Benjamin ABEL (bjn-abel-deactivatedaccount)]

Yes i'm using unity.
Le 4 nov. 2013 14:35, "Sebastien Bacher" <email address hidden> a écrit :

> do you use unity? I still can't confirm that issue...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1247621
>
> Title:
> Search field doesn't works in ubuntu 13.10
>
> Status in “evince” package in Ubuntu:
> Incomplete
>
> Bug description:
> Since I've upgraded to ubuntu 13.10, and evince 3.10.0, the search field
> doesn't works. I can't type any text on it.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Ubuntu version:
> *** 3.10.0-0ubuntu2 0
> 500 http://fr.archive.ubuntu.com/ubuntu/ saucy/main amd64
> Packages
>
> Evince version:
> *** 3.10.0-0ubuntu2 0
> 500 http://fr.archive.ubuntu.com/ubuntu/ saucy/main amd64
> Packages
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1247621/+subscriptions
>

[Sebastien Bacher (seb128)]

Ok, that bug description doesn't make any sense to me.

Could you:
- try in a guest session
- describe exact steps of what you are doing and is happening
- provide a screenshot showing the issue?

[Benjamin ABEL (bjn-abel-deactivatedaccount)]

When i use the guest session, the search field works. What canton i do?
Le 4 nov. 2013 15:35, "Sebastien Bacher" <email address hidden> a écrit :

> Ok, that bug description doesn't make any sense to me.
>
> Could you:
> - try in a guest session
> - describe exact steps of what you are doing and is happening
> - provide a screenshot showing the issue?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1247621
>
> Title:
> Search field doesn't works in ubuntu 13.10
>
> Status in “evince” package in Ubuntu:
> Incomplete
>
> Bug description:
> Since I've upgraded to ubuntu 13.10, and evince 3.10.0, the search field
> doesn't works. I can't type any text on it.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Ubuntu version:
> *** 3.10.0-0ubuntu2 0
> 500 http://fr.archive.ubuntu.com/ubuntu/ saucy/main amd64
> Packages
>
> Evince version:
> *** 3.10.0-0ubuntu2 0
> 500 http://fr.archive.ubuntu.com/ubuntu/ saucy/main amd64
> Packages
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1247621/+subscriptions
>

[Sebastien Bacher (seb128)]

Can you still describe what you are doing and add the screenshot?

[Evan Carroll (evancarroll)]

I have this problem too. If I search in a multipage document for a term and I hit next it jumps in the view between the occurances on a single page, and in the pane on the left where it shows all occurrences in the documents it continues through the list.

PG 1

a1 Foo
a1 Bar
a2 Foo

PG 2

b1 Foo
b1 Bar
b2 Foo

If I search for "Foo" the left pane will show
a1 Foo
a2 Foo
b1 Foo
b2 Foo

If I hit enter the `a1 Foo` will be highlighted, if I hit enter again `a2 Foo` will be higlighted. If I hit enter a third time, `a1 Foo` will be highlighted but the left bar will highlight `b1 Foo`.

[Justyn Butler (justyn)]

I have the same problem as described in the bug description.

I cannot type text in the find bar, whether it's brought up using ctrl-f or clicking the magnifying icon.

However, find itself does actually work, if I paste into it using the mouse and the right-click menu. I just can't type in it.

I also find that the problem disappeared in a guest session. It only occurs occurs in my own user session.

This is a fresh 64-bit 13.10 installation.

Any ideas?

[Benjamin ABEL (bjn-abel-deactivatedaccount)]

I tried to paste in the search field of evince via the right click menu and it works on my own user session. The bug is exactly the same that what described Justyn Butler in the message #11.

[Justyn Butler (justyn)]

I have found a workaround, although it is a bit of a pain to do every time.

If I right-click in the search bar and select a different "Input Method" then I can type and find works as expected.

Whenever evince is opened the input method always already selected is:
"System (IBus (Intelligent Input Bus))"

If I select something else from the list, including "None", "Simple" or "X Input Method" then I can type.
If I select "System (IBus)" then I can't type again. So the problem seems to be related to this in some way.

If I try the same thing in gedit then I find I can type with "System (IBus)" selected without any problems. Evince is the only thing I have seen this behaviour in so far.

[Justyn Butler (justyn)]

I believe I have found the solution to this problem, I think it was caused by an incorrect AppArmor setup.

My home directory is not located in /home/ but the AppArmor /etc/apparmor.d/tunables/home tunable had not been updated to reflect this as described in:
https://wiki.ubuntu.com/DebuggingApparmor#Adjusting_Tunables

After adding my home directory to the @{HOME} list, or alternatively the location to @{HOMEDIRS}, the problem with evince has gone away.

[Benjamin ABEL (bjn-abel-deactivatedaccount)]

The solution provided by Justyn Butler in post #14 works for me.
My home directory is in `/media/home/`, so I've edited the `/etc/apparmor.d/tunables` file to change the `@{HOMEDIRS}` value like this:

    @{HOMEDIRS}=/home/ /media/home/

After that, you need to reload your apparmor profile:

    sudo invoke-rc.d apparmor reload

And then I can type in the search fireld as expected. Thank you very much justyn.

[Sebastien Bacher (seb128)]

great, thanks for figuring that out, closing the bug since that was a local configuration issue is not an evince bug!