can't use the search in okular when using mozplugger

Bug #343182 reported by Schmirrwurst on 2009-03-15
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Mozplugger
Confirmed
Medium
mozplugger (Ubuntu)
Low
Unassigned
Jaunty
Undecided
Unassigned
Karmic
Undecided
Unassigned

Bug Description

Binary package hint: mozplugger

When opening a pdf document from the web in firefox, with mozplugger installed, then it is opening with okular, but CTRL F is not working to open seach box, and if I open it from the okular menu, then I can't write in it, when tipping, nothing is appearing...

hants (andreowitsch) wrote :

confirmed in ubuntu 8.10 and 9.04.

enabling okular in mozpluggerrc makes firefox open pdfs in okular. But okular doesnt receive pressed keys (so no search possible).
scrolling with the mouse works. There are no problems with okular in konqueror though.

flying sheep (flying-sheep) wrote :

confirmed in (k)ubuntu 9.04

keys also do not work for me. (which is odd since the go-back-mousebutton neither dosen’t work. so the keys pressed in the iokular tab are neither forwarded to firefox nor to okular)

Changed in mozplugger (Ubuntu):
status: New → Confirmed

I can confirm this as well in Kubuntu Jaunty. It is discussed at this KDE bug (http://bugs.kde.org/show_bug.cgi?id=172858), which mentions a QT bug (http://qt.nokia.com/developer/task-tracker/index_html?method=entry&id=249189) which may be responsible.

Alessio Treglia (quadrispro) wrote :

Is this reproducible with Karmic?

Changed in mozplugger (Ubuntu):
status: Confirmed → Incomplete
RZ (rufei-z) wrote :

I can confirm this in Ubuntu Karmic. Nothing is passed from the keyboard to Okular or even to Firefox when an Okular tab is open.

Changed in mozplugger (Ubuntu):
status: Incomplete → Confirmed
hants (andreowitsch) wrote :

Mairan`s solution on this page: http://www.google.com/support/forum/p/Chrome/thread?tid=543f0c80bace6c42&hl=en
Namely this:
1 - echo 'deb http://ppa.launchpad.net/setack/stuff/ubuntu karmic main' >> /etc/apt/sources.list
2 - aptitude update
3 - aptitude install mozplugger

seems to solve the problem.

Alessio Treglia (quadrispro) wrote :

Fixed in Lucid.

Changed in mozplugger (Ubuntu):
status: Confirmed → Fix Released
Robert Bredereck (rbredereck) wrote :

Sorry, but the bug with not-functional keyboard in qt-plugins still exists.
Please read: https://www.mozdev.org/bugs/show_bug.cgi?id=22359

I can confirm that neither mozplugger from http://ppa.launchpad.net/setack/stuff/ubuntu nor from lucid (1.13.1) nor from debian unstable (1.13.2) solve that problem.

hants (andreowitsch) wrote :

1.13.1 introduces new problems for me - but at least keyboard input (in chrome) continues to work.

January (january-weiner) wrote :

I am using Lucid, Firefox 3.6 and mozplugger 1.13.1. Programs that run in the swallowed window do not receive keypresses. Instead, some keypresses go to FF (e.g. Meta-F), and some are lost (e.g. Ctrl-F).

January (january-weiner) wrote :

@Alessio: the problem seems to persist in Lucid, at least in my case. Why is the bug marked "fix released"? What fix?

hants (andreowitsch) wrote :

changed status to "new" because no fix is released yet (but one of the comments shows a solution which at least works on older versions).
problem remains from 8.04 to 10.04.

Changed in mozplugger (Ubuntu):
status: Fix Released → New
Changed in mozplugger:
status: Unknown → Confirmed
Changed in mozplugger (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
Skipper Seabold (jsseabold) wrote :

Any workaround for this in Lucid?

Changed in mozplugger:
importance: Unknown → Medium
JC Hulce (soaringsky) wrote :

Jaunty and Karmic are EOL, so this issue will not be fixed in those versions.

Changed in mozplugger (Ubuntu Jaunty):
status: New → Invalid
Changed in mozplugger (Ubuntu Karmic):
status: New → Invalid
hants (andreowitsch) wrote :

May not matter anymore in current releases since using "kpartsplugin"(introduced in oneiric) instead of "mozplugger" solves the problem (for me).

Oliver R. (oliverr) wrote :

Bug is still present in Precise. And it seems related to bug #439540.

kpartsplugin didn't solve the problem for me.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.