Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't remove AdAway blocklist on Edge #5700

Closed
3 tasks done
devipasigner opened this issue Apr 9, 2023 · 5 comments
Closed
3 tasks done

Can't remove AdAway blocklist on Edge #5700

devipasigner opened this issue Apr 9, 2023 · 5 comments
Assignees
Milestone

Comments

@devipasigner
Copy link

Prerequisites

  • I have checked the Wiki and Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to report a bug and not ask a question

Operating system type

Linux, Other (please mention the version in the description)

CPU architecture

AMD64

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.108.0-a.508+15bba281

Description

What did you do?

Fresh install AdGuard Home Edge Build, go to blocklist tab, and remove both default blocklists.

Expected result

Both the AdGuard DNS filter and AdAway blocklist are removed.

Actual result

Only AdGuard DNS filter is able to removed. AdAway remains, and cannot be removed no matter what.

Screenshots (if applicable)

Nah.

Additional information

Another question, why is this blocklist even selected by default? Theres no point in adding it if its in a disabled state. If users want to use the AdAway blocklist they can select it through the "Choose from the list" options, just like every other blocklist. What makes AdAway so special?

@ainar-g ainar-g changed the title [Edge] Can't remove AdAway blocklist Can't remove AdAway blocklist on Edge Apr 10, 2023
@ainar-g
Copy link
Contributor

ainar-g commented Apr 10, 2023

We cannot reproduce this behavior, although it could be caused by #5647. When you say that “AdAway remains”, do you mean that you see it there after a page refresh, or does it not disappear at all?

Another question, why is this blocklist even selected by default? […]

Please direct questions to the Discussions, as we strive to keep the Issues section dedicated to bugs and improvements only.

@ainar-g ainar-g added the waiting for data Waiting for users to provide more data. label Apr 10, 2023
@devipasigner
Copy link
Author

We cannot reproduce this behavior, although it could be caused by #5647. When you say that “AdAway remains”, do you mean that you see it there after a page refresh, or does it not disappear at all?

It does not disappear at all, after pressing the delete button the blocklist remains on the web interface. I can however removed the blocklist after I enable the list first and then remove it, so in a disabled state I cannot remove it. Also this is in a fresh install, not an existing one.

@ainar-g ainar-g added needs investigation Needs to be reproduced reliably. and removed waiting for data Waiting for users to provide more data. labels Apr 12, 2023
@ainar-g ainar-g added this to the v0.107.28 milestone Apr 12, 2023
@ainar-g
Copy link
Contributor

ainar-g commented Jun 21, 2023

I have recently been able to reproduce this. The log:

2023/06/21 15:43:24.754135 [error] deleting filter 2: renaming file "/tmp/AdGuardHome/data/filters/2.txt": rename /tmp/AdGuardHome/data/filters/2.txt /tmp/AdGuardHome/data/filters/2.txt.old: no such file or directory

@Mizzick, seems like an issue in internal/filtering/http.go, with os.ErrNotExist not being properly handled.

@ainar-g ainar-g assigned Mizzick and unassigned EugeneOne1 Jun 21, 2023
@ainar-g ainar-g added bug P3: Medium and removed needs investigation Needs to be reproduced reliably. labels Jun 21, 2023
@Mizzick
Copy link
Contributor

Mizzick commented Jun 22, 2023

Please have a look, the requested changes have been implemented.
The new build version=v0.108.0-a.578+66345e85 has been just published to the edge channel.

@ainar-g
Copy link
Contributor

ainar-g commented Jun 27, 2023

We'll close this issue for now. Please feel free to tell us if the issue isn't fixed for you.

@ainar-g ainar-g closed this as completed Jun 27, 2023
@ainar-g ainar-g modified the milestones: v0.107.34, v0.107.33 Jul 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants