Auto-complete on address bar not working after keeping system in lock mode for long time and unlocking

RESOLVED INCOMPLETE

Status

()

--
minor
RESOLVED INCOMPLETE
9 years ago
8 years ago

People

(Reporter: navaneethkn, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2010-12-01])

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.14) Gecko/2009090216 Ubuntu/9.04 (jaunty) Firefox/3.0.14
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.14) Gecko/2009090216 Ubuntu/9.04 (jaunty) Firefox/3.0.14

Auto-complete on address bar not working after keeping system in lock mode for long time and unlocking. After system is unlocked, goto address bar and type a website that you already visited. You can see auto-completion fails to work here.

Reproducible: Always

Steps to Reproduce:
1. Open FF and open many tabs. Say 10.
2. Lock the system Ctrl + Alt + L.
3. Unlock after some time.
4. Open a new tab (Ctrl + T)
5. Type an address which is already visited. 
Actual Results:  
The auto-complete not works.

Expected Results:  
It should work and show the auto-completion menu.

This happens only if address is typed immediately on the address bar after the system unlock. All works well if address is typed after some time.

Comment 1

9 years ago
I'm not sure if I'm having the same bug or not.

After unlocking my screen, when trying to type anything into the address or search bar, the following happens.

Type a character, then the character is highlighted. If the right arrow is not pressed to remove the unlock, the character will be replaced by the next character typed. This process continues indefinitely. That is, to type a web address I would literally have to hit the right arrow key after every character to remove the character selection after every key stroke.

Comment 2

8 years ago
This bug is still affecting users. The following text is from a bug report on Launchpad. https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/598043


I leave browser open and suspend the OS or lock desktop (that's Ubuntu with Gnome). When I log back in, the address bar malfunctions. It doesn't display matching recently visited sites as I type, and it even swallows some of the (rapidly typed) characters.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: firefox 3.6.3+nobinonly-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Jun 24 12:15:50 2010
FirefoxPackages:
 firefox 3.6.3+nobinonly-0ubuntu4
 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
 firefox-branding 3.6.3+nobinonly-0ubuntu4
 abroswer N/A
 abrowser-branding N/A
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: firefox

Updated

8 years ago

Comment 3

8 years ago
I confirm this bug (Ubuntu x86_64).

Comment 4

8 years ago
This is a duplicate of bug 507269... but I don't seem to have the power to mark it as a dup.
Reporter, please retest with Firefox 3.6.12 or later in a fresh profile (http://support.mozilla.com/kb/Managing+profiles). Also update your plugins (flash, adobe reader, java, quicktime, silverlight, etc.) Go to the developer's website and download the latest version from there. If you no longer see this issue, please close this bug as RESOLVED, WORKSFORME. If you do see the bug, please post a comment.
Whiteboard: [CLOSEME 2010-12-01]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE

Comment 7

8 years ago
I have retested this bug and still find that it occurs.

Comment 8

8 years ago
Same here.  Still there.  It happens far less frequently in recent version, though.
You need to log in before you can comment on or make changes to this bug.