Results 1 to 5 of 5

Thread: Bug with zone filter loading

Hybrid View

  1. #1
    Registered User
    Join Date
    Aug 2020
    Posts
    131

    Re: Bug with zone filter loading

    I started with the existing tarball and it was extracted to "/usr/local/share/showeq/filters"

    I have been in a hurry sometimes while editing filters when tracking rare NPCs/placeholders. The combination that always correctly edits the zone filters and reloads is this workflow:


    1. Filters > Edit Zone Filters > (correctly shows the filters under /usr)
    2. Save File
    3. Filters > Reload Zone Filters
    4. Changes correctly show up


    There are other filter settings in the menu that I don't normally use. SEQ is always ran as root, so permissions shouldn't be an issue. I'm guessing whatever app logic that determines to use the local filters in the user's home directory is incorrectly saving an old/default copy to ~/.showeq/filters instead of updating the main file. I did not have any filters in ~/.showeq/filters and have to periodically clear them out, as something is causing them to occasionally be created there. The app seems to prefer filters in ~/.showeq/filters over the /usr location. That logic can probably be stripped out completely, as SEQ seems to always need to be ran as root, and should have access to /usr.

  2. #2
    Administrator
    Join Date
    Oct 2019
    Posts
    507

    Re: Bug with zone filter loading

    Your 4-step process is the same thing I do for filters, so that looks fine to me. Though, if I'm not mistaken, the save/reload isn't strictly necessary if you just want the filters temporarily (you'll lose them on zone unless you save).

    The app does prioritize data in the user's home directory over data in /usr/. I think part of the intent was to eventually separate the program into to parts so that only the part that needs root (the packet capture) would run as root, and the rest of the program would run as an unprivileged user. So in that context, it makes sense. Also, historically, /usr was sometimes mounted read-only except for when upgrades were being done. So it makes sense in that context as well.

    Since the app prioritizes the data in the user's home dir, it should load from there if data is found there. So the base filters could be in /usr, changes made and saved (to /root/.showeq), and then reloading the filter would load from /root/.showeq if it was there, or /usr if it wasn't. This is the same way loading/saving of maps and preferences works.

    So it sounds to me like the actual bug here is that it's sometimes saving to /usr and sometimes to /root/.showeq, when it should really only be saving to /root/.showeq. I've added it my list of stuff to look at, but I don't have a lot of EQ/SEQ time right now, so it may be a bit before it's fixed.

    In the short term, I think you should be able to work around this by moving all the filters from /usr to /root/.showeq/filters.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

You may post new threads
You may post replies
You may post attachments
You may edit your posts
HTML code is Off
vB code is On
Smilies are On
[IMG] code is On