Konqueror Location Bar History Retains Entries

Bug #126120 reported by Tom Inglis
8
Affects Status Importance Assigned to Milestone
KDE Base
Invalid
Medium
kdebase (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: konqueror

I am using Kubuntu Feisty i386. I am unable to delete my browsers history. I clear the history, cache, and cookies in the 'Configure Konqueror' setting, but this does not remove URL's from the location bar, so that when you start to type in a URL, all of the similar suggestions remain in there.

I have been unable to find out what is wrong, but perhaps there is a file or folder somewhere with the incorrect permissions on it?

Revision history for this message
Sujee Maniyam (sujee) wrote :

can you check this bug report and see if it is the same issue?
https://bugs.kde.org/show_bug.cgi?id=77677

Revision history for this message
Tom Inglis (tominglis) wrote : Re: [Bug 126120] Re: Konqueror Location Bar History Retains Entries

I think this is the same. It does actually clear the history sidebar, but it
is the autocompletion that is the problem. Surely clearing the history should
also clear the entries from autocompletion, or there should be some kind of
option to do that? Or maybe some kind of delete all private data like in
Firefox and Opera?

Bestest,

Tom

On Monday 16 July 2007 22:19:36 LinuxLover wrote:
> can you check this bug report and see if it is the same issue?
> https://bugs.kde.org/show_bug.cgi?id=77677

Revision history for this message
Tom Inglis (tominglis) wrote :

Is there a way to clear auto complete as it is, since there doesn't seem to be
an option in the settings?

On Monday 16 July 2007 22:19:36 LinuxLover wrote:
> can you check this bug report and see if it is the same issue?
> https://bugs.kde.org/show_bug.cgi?id=77677

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

On my Hardy system, clearing the history in Konqueror 3.5.9 clears the autocompletes, so I think this is fixed. Can you test on Gutsy or Hardy to see if your problem is still there?

Changed in kdebase:
status: New → Incomplete
Changed in kdebase:
status: Unknown → Invalid
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdebase:
status: Incomplete → Invalid
Changed in kdebase:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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