Bug 191482

Summary: [Konqueror 3.5.8] Ad Block Plus doesn't work after list upgrade
Product: [Applications] konqueror Reporter: jonathan aquilina <eagles051387>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: frank78ac
Priority: NOR    
Version: 4.2.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description jonathan aquilina 2009-05-03 16:09:06 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    I Don't Know

Binary package hint: konqueror

I've tried to upgrade the Ad Block Plus definition list. I've done the following:

1. exported the current list (Last Modified: 26Sep07) to a local file
2. downloaded the new one from the website at http://easylist.adblockplus.org/adblock_rick752.txt
3. erased the current list
4. imported the new one
5. closed and re-open the browser

Now everything (also non-ad contents) gets filtered out, unless I disable the filter.
What's worst is that by restoring the exported file I'm not able to have the Ad Block Plus working anymore.
I'd like to be able to upgrade to the new definitions or, at least, to restore the old ones.

this bug can be found at https://bugs.edge.launchpad.net/ubuntu/+source/kdebase/+bug/176114
Comment 1 Frank Reininghaus 2009-05-03 17:28:22 UTC
(In reply to comment #0)
> Version:            (using KDE 4.2.2)

If I understand the bug report on Launchpad correctly, this is a bug in Konqueror 3.5.8, right? Can you reproduce this also in KDE 4.2.2 or later? I just tried that and couldn't reproduce.

BTW, you should use the severity 'wishlist' only for reports which are about ideas for new functionality, not for bugs.
Comment 2 jonathan aquilina 2009-05-04 13:13:07 UTC
downstream on launchpad this was filed as something to be wishlisted.
Comment 3 jonathan aquilina 2009-05-04 14:30:34 UTC
i have tested this bug on kde 4.2.2 and am unable to reproduce this either.
Comment 4 Frank Reininghaus 2009-05-04 15:28:51 UTC
Thanks for the update, I'll close the report then.

BTW, I think it makes sense to try to reproduce the bug *before* you forward a 1 1/2 year old report from Launchpad ;-)