evanevery  You might be able to find more information on what is going on behind the scenes if you tail /var/log/apache2/error_log. Do you get any errors in this log when you attempt to delete the blacklist entry?

Here is a capture of the tail.  Note all sorts of chatter generated by my PC (@10.100.1.1).  (Also note that this is effecting all users - not just my PC). 

Anyway, the 3 log entries at the bottom of the file (14:28:19) are what gets entered into the error log when I click to delete a single selected entry.

It looks like "more than one row returned" from a query and something about "myoptions_confirm" may be relevant but I'm not doing anything special (and no Confirmation Dialog box is presented)...

Any chance you can share your entire log here through the Insert function on a reply after you watch the log, perform the delete and note the exact timestamp on the log?

(I'm new to the forums so I'm not entirely sure if they allow you to post logs here.)

I'm not sure I'm comfortable posting the entire log (for privacy reasons)...  ...and based on the traffic I've seen just for logging in my one workstation for this test, I expect that log file will be quite large.  (I'm not logged into the console right now to check).

The last three log entries in the capture above (at 14:28:19) were exactly what was generated when I hit the delete button...

Please note that I opened a case on this a couple of days ago.

(For those who are following along, Support asked me to try deleting entries from my WhiteList - which DID work...)

Please note that I opened a case on this a couple of days ago.

(For those who are following along, Support asked me to try deleting entries from my WhiteList - which DID work...)

SMG Support got back to me with a resolution to this problem.  Apparently we had TWO blacklist files being serviced by our Blacklist filter.  The first file was apparently manually created (by me) before any USER actually tried to create a "personal" Blacklist entry.  Once QMS started making entries (for users) it used a different file "Linked to QMS".  So, looking at my Blacklist filter, there were actually TWO files in play.  One very small one (with a single entry that was manually created from the Policy Page) and one very large one linked/used by QMS.  (Not sure if its relevant, but the small/manual one was first on the list). 

Anyway, it appears QMS couldn't find the entries to delete as it couldn't find them in the first/small/manually-created file.  (Curious that it WAS displaying the contents of BOTH files though...)  Deleting the first (unlinked) file solved the issue!