Bug 144358 - kmail restores konqueror history (data safety!)
Summary: kmail restores konqueror history (data safety!)
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-17 20:59 UTC by Maciej Pilichowski
Modified: 2008-12-07 13:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2007-04-17 20:59:31 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    SuSE RPMs

I set in Konqueror to clear entire history. I run KMail and it seems like KMail restores Konqueror "memory". Well, you can call it a feature, but I think the downside is rather major. There is somewhere complete Konqueror history, not wiped out at all, in spite of (fake)erasing.
Comment 1 Dominik Tritscher 2008-08-03 20:55:23 UTC
I can't reproduce that behaviour. Can you give us a more detailed description on how to reproduce that problem?
Comment 2 Maciej Pilichowski 2008-08-03 21:18:00 UTC
Ok, maybe I rephrase -- when you clear entire history of Konq. and then when you start typing address there should be no suggestion, right? Because history (in theory) is empty.

So no matter if address is in KMail address book, or there are some addresses in mails, or you clicked (before) at some of those links, running KMail should not restore Konq. history (or part of it).
The same goes for other apps and for other Konq. features (like bookmarks) but this is different story.

So the problem is -- the "cleared" history is not cleared because after running KMail I see suggestions again (now I cannot repeat it because I have too valuable entries in Konq. history).
Comment 3 Dominik Tritscher 2008-12-07 13:57:26 UTC
I tried this again, and i found no way to reproduce that behaviour.
Please try to reproduce that bug with a more recent KDE version. You should at least update to the current KDE3 release (3.5.10!) or even better to KDE4 series.
For now I close this bug, please leave a comment if you manage to reproduce that bug with a recent KDE4 series release (most recent is 4.1.3).