[BUG-2745] User spammed with notifications if SLPlugin.exe can't be found. #11841
Comments
Whirly Fizzle commented at 2013-06-01T03:47:06Z
They do block slplugin, all the time! I can reproduce the "No Media Plugin was found to handle the "text/html" mime type." notifications spam on Second Life 3.5.3 (276452) May 24 2013 02:06:23 (Second Life Release) when I deliberately blocked my slplugin with AVG. I am actually able to close out the notifications but there are so many of them, it appears that they arnt closing because they are replaced so quickly. If you enable debug console, you can see that the notification toasts are actually closing when you click on OK.
|
Whirly Fizzle commented at 2014-07-11T01:27:14Z Heya Marissa, Can this issue be set to Public security level? It's been collecting a few dupes lately. |
Marissa Linden commented at 2014-07-11T02:35:26Z Done! :) |
Whirly Fizzle commented at 2016-01-06T16:29:29Z Fix for the spam problem (not a fix for the slplugin failure) in Lion. |
Lucia Nightfire commented at 2016-01-06T19:31:59Z Music to my ears, heh. |
Whirly Fizzle commented at 2016-02-21T11:56:05Z Fixed in MAINT-RC: http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/4.0.2.310545 |
Steps to Reproduce
Another way to reproduce this is to rename slplugin.exe (i.e. slplugin_ren.exe) then launch SL. The error notifications should appear once you load into the world.
Actual Behavior
After building my first prim with an external media attachment, the virus scan software blocked the slplugin.exe. Once this happened, I couldn't view the youtube that was linked to my prim, and I started getting spammed with error notification dialogs that read:
"No Media Plugin was found to handle the "text/html" mime type. Media of this type will be unavailable."
I couldn't close the notification dialogs out, because when I hovered my mouse pointer over the top most dialog, focus was given to the dialog below where I hovering the mouse. Clicking in the dialog wouldn't give it focus.
Expected Behavior
Other information
Attachments
Links
Duplicates
Related
Original Jira Fields
The text was updated successfully, but these errors were encountered: