Yeah, this also affects volume applet hotkeys.
You can't use Fn hotkeys to adjust volume until focus is reacquired.
** Also affects: indicator-applet (Ubuntu)
Importance: Undecided
Status: New
--
Numerous applications have focus issues after emerging from a screensaver or
suspend
I did a little more investigation. On comment #23 at
https://bugzilla.mozilla.org/show_bug.cgi?id=507269 , Mikhail Zabaluev
describes the very same problem I have with Kile, but for him, it
happens with Eclipse. I dont know which OS Mikhail Zabaluev uses, nor if
he is running compiz, but it really
Comment #50 is interesting. Maybe a combination of FF + Compiz +
emerging from an screensaver is making the awesome bar been drawn behind
FF window. As a simple fix, we would suggest FF devs to set the awesome
bar window as always on top; I think that is the simplest way to fix
this issue.
Also,
Compiz is very likely a factor here. Following diego's advice, I
switched the window manager to Metacity (using Compiz Fusion Icon),
restarted Firefox, checked if the awesomebar was working (it was, no
surprise here), suspended, resumed and immediately tried the awesomebar
again. It was still
I checked browser.urlbar.clickSelectsAll in my browser and it is already
set to false. I commented here, because all the bugs that describe more
of my behavior are pointing to this one as a duplicate. Someone seems to
be pretty sure that they are different manifestations of the same bug. I
see it
Guys, take a look at comments #85 and #87. It looks like it is a compiz
bug. Anyone can confirm if it does not happen if compiz is not enabled?
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a screensaver or suspend
I use KWin in Kubuntu 10.04 Beta 2 and I have no problems after
emerging from a screensaver or suspend.
On 26.04.2010 20:42, diego wrote:
Guys, take a look at comments #85 and #87. It looks like it is a compiz
bug. Anyone can confirm if it does not happen if compiz is not enabled?
--
I use compiz all the time, so I can't say whether or not it is related
to compiz. It is hard to reproduce, as it does not always happen, and it
never happens if I try to reproduce it by using preview screensaver in
the preferences. It may very well be that it is related to compiz, but
at the same
My workaround is to minimize Firefox and unminimize (which I do by just
clicking the program name in the window button list in the bottom
panel). The awesomebar works normally then.
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a screensaver or
I've seen this behavior in the search bar portion (automatically
highlighting the text you just typed so your next keystroke deletes it)
for several Ubuntu releases. Really annoying as I use that for searches
all the time. My workaround has been to use the firefox build from
Mozilla. I've only
@Jonathan CrockettI believe that's a completely different bug than
the one in this bug report. In this report you can type normally, it's
just the awesomebar matching results don't pop up at all unless you
first alt-tab to another window. With this bug there's no highlighting
and no text being
The but that J Crockett described happens to me at the same time that
this bug happens, so they seem to be related.
No awesome bar comes up, no search auto suggest window comes up as you
type, instead of when the window would normally come up, all of the text
is highlighted. So, if you were
Same bug here:
Ubuntu 9.10 Desktop 32-bit
Firefox 3.6.3 from http://ppa.launchpad.net/mozillateam/firefox-stable/ubuntu/
Compiz and nvidia-190 enabled
Only workaround working for me: minimize then maximize Firefox window
(thanks to BlackSir for comment #35).
--
Address bar autocomplete and
Me too! Another workaround is to open a new Firefox window (Ctrl+N)
after resuming from suspend, optionally closing the previous one with
the non-functioning awesomebar. Much faster than restarting the browser,
but still a nuisance of course.
--
Address bar autocomplete and search bar
I am glad to have finally found the bug report on this bug! It has been
driving me crazy for months. On the other hand, I am very disappointed
that this won't be fixed in Lucid. At least I know that bringing up the
context menu with a right click on the page will fix it when it does
happen so I
I can confirm this behavior on Karmic with Firefox 3.6.3 taken from the
Ubuntuzilla repository. I have Compiz enabled NVidia GEforce Go 7900.
It is really annoying.
I can also confirm the bug stated in #40. Both really annoying.
--
Address bar autocomplete and search bar autocomplete doesn't
Another small point, I'm affected by this bug and I am NOT using an
Ubuntu packaged firefox at the moment.
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a screensaver or suspend
https://bugs.launchpad.net/bugs/438868
You received this bug
I can confirm that, with KWin in Kubuntu 10.04 I have no problems.
On 17.04.2010 23:17, diego wrote:
It really seems compiz related. If I wait for the screensaver to come,
it comes and the bug is triggered. To restore normal behavior I switch
back and forth to another desktop. That makes the
It really seems compiz related. If I wait for the screensaver to come,
it comes and the bug is triggered. To restore normal behavior I switch
back and forth to another desktop. That makes the bug go away.
So, it really seems compiz related or, at least, there is an ugly
compiz-hack-way to fix it.
I can confirm that this bug can be reproduced on VERY rare occasions
with Firefox on Windows 7 64-bit.
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a screensaver or suspend
https://bugs.launchpad.net/bugs/438868
You received this bug
It just seems like its being put off, since its been around since karmic
and since there's been no reassurance about it at least being fixed for
lucid.
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a screensaver or suspend
I understand your frustration, but let me assure you that it's not being
put off. It's just that, since firefox is a highly used program, there
are a lot of reported bugs (255 open ones as of this writing). The
developers have limited time, so higher priority bugs get handled first.
If you want to
So in other words, it's too hard to fix so you are not fixing it?
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a screensaver or suspend
https://bugs.launchpad.net/bugs/438868
You received this bug notification because you are a member of Ubuntu
So in other words, it's too hard to fix so you are not fixing it?
Allow me to address this. The papercuts project is designed to fix bugs
that don't require a lot of work but potentially affect a lot of users.
This bug does affect a lot of users, but does not have an easy fix.
However, this only
Can we get this bug elevated to papercut status?
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a screensaver or suspend
https://bugs.launchpad.net/bugs/438868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I believe the papercuts for Lucid are done. Round 10, the last one, was
targeted to 2010-02-18.
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a screensaver or suspend
https://bugs.launchpad.net/bugs/438868
You received this bug notification
This bug is not suitable for inclusion in the papercuts project, if it
continues in Maverick, as it apparently involves a non-trivial fix that
needs new code to be written, most likely upstream.
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a
As Alan Pater (#63) notes, in Lucid beta this issue is harder to work
around than in Karmic due to the right-click and favicon area click
trick no longer working. It's also very random, the address bar will
start auto-completing again after some time (or some actions, but
nothing I can pinpoint).
Another workaround for me is to enable the widget layer.
1. In the CompizConfig Settings Manager filter for Wiedget Layer and enable
the tool
2. Create some widgets which will show and make not of the Toggle Widget
Display shortcut - F9 by default
3. Close CompizConfig Settings Manager
4. Wait
we no longer use versioning. closing all but the one needed.
** Changed in: firefox-3.0 (Ubuntu)
Status: New = Invalid
** Changed in: firefox-3.5 (Ubuntu)
Status: Triaged = Invalid
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a
Can someone please decline the nominations since this is not required
since Mozilla moved to non-versioning
** Changed in: firefox (Ubuntu)
Status: New = Triaged
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a screensaver or suspend
This is sounding like a resume bug from screen saver more so than a Mozilla
bug, or there are more than 1 bug in this bug report.
When i say resume i mean after screen saver is deactivated by moving mouse/keys
being hit/unlocking
--
Address bar autocomplete and search bar autocomplete doesn't
I just noticed a very similar problem in thunderbird which I suspect has
the same origin. I could not find a bug report so I filed a new one
here: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/539853
. Can anyone with the firefox bug confirm the thunderbird bug, too?
--
Address bar
If the same bug affects Firefox and Thunderbird, then it may be a
xulrunner problem.
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a screensaver or suspend
https://bugs.launchpad.net/bugs/438868
You received this bug notification because you are
I am able to reproduce both this bug bug #539853 in an up-to-date
Lucid install.
$ uname -a
Linux mitch-lucid 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:52 UTC 2010
i686 GNU/Linux
$ sudo apt-cache policy thunderbird
thunderbird:
Installed: 3.0.3+nobinonly-0ubuntu1
Candidate:
It happens with firefox 3.6 too (karmic)
As a workaround, when this occurs, I unfocus firefox window by for
example clicking on the desktop. I then go back to firefox and auto-
complete works again.
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from
I can confirm this behaviour with FF3.5/Karmic and FF3.6/LucidAlpha3
(both update as of today).
- Awesome bar stops working randomly
Systems I have seen this on are both laptops. LucidA3 with nvidia binary
driver, Karmic with Intel. Both use Compiz. None have active screensaver
(but power save
correction to #66: screensaver is active: uses blank screen.
--
Address bar autocomplete and search bar autocomplete doesn't always work after
emerging from a screensaver or suspend
https://bugs.launchpad.net/bugs/438868
You received this bug notification because you are a member of Ubuntu
Additional testing with my Karmic system indicates that the problem is
strongly coupled with screen-saver and Compiz.
5/5 attempts after screen-saver with compiz shows the problem.
The problem disappears when de-activating compiz (tested with two
screensaver activations), and re-appears when
** Summary changed:
- Address bar autocomplete and search bar autocomplete doesn't work after
emerging from a screensaver or suspend
+ Address bar autocomplete and search bar autocomplete doesn't always work
after emerging from a screensaver or suspend
** Also affects: firefox (Ubuntu)
40 matches
Mail list logo
