Description of problem:
I have installed the xfce4-websearch-plugin in a xfce4 panel, but when I try to type in the search box (clicking on it before), one cannot type.
Actually, the search box is not highlighted, and the focus continues on the window it was before.
Steps to Reproduce:
1. Install the plugin in a xfce4 panel.
2. Click on the search box
3. Try to type your favourite search topic
I have just realized that the same happens for the command line verve plugin. So it seems to be something related to the xfce4 panel in general.
In my configuration I have two panels and the problem appears no matter in which panel I place the plugin in.
I can confirm this with verve plugin.
Are you set to focus follows mouse? Does it work if you change to click to focus?
Upstream bug report for xfce4-dict: http://bugzilla.xfce.org/show_bug.cgi?id=6649
I have the focus follows mouse set. If I change to click to focus then it works. So it seems that the problem appears only when using "focus follows mouse".
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
I can confirm that the bug is still present in Fedora 15. Version bumped.
Odd. Upstream claims there is a workaround in xfwm4 now.
rpm -q xfwm4 ?
# rpm -q xfwm4
Hum. I can't find the commit... asked on the upstream bug.
This is going to be fixed in the next update.
xfwm4-4.8.2-1.fc16 has been submitted as an update for Fedora 16.
xfwm4-4.8.2-1.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xfwm4-4.8.2-1.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
As I commented in the updates page, the new xfwm4-4.8.2-1.fc15.x86_64
solves the problem with verve, but there is a regression error, since now the already defined keyboard application shortcuts don't work. However, if I define a new keyboard shortcut, then it works. Somehow some of the old shortcuts don't work (the only ones that still work are <Alt>F2 and <Alt>F1).
An update: I have realized that it is only those shortcuts which contained <Control>. When I define the same shortcut now, <Shift><Control>Return is transformed into <Primary><Alt>Return. Maybe this can be reported in another bug, right?
Sorry, I ment <Control><Alt>Return is transformed now to <Primary><Alt>Return
Please don't hijack other bugs but open a new one. Include all relevant information and attach your ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml. TIA!
xfwm4-4.8.2-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
xfwm4-4.8.2-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.