Bug in 10.0 after loading screen sometimes
jquick opened this issue · 3 comments
1x [ADDON_ACTION_BLOCKED] AddOn 'Rarity' tried to call the protected function 'UIParentRightManagedFrameContainer:SetPoint()'.
[string "@Interface/AddOns/!BugGrabber/BugGrabber.lua"]:480: in function <Interface/AddOns/!BugGrabber/BugGrabber.lua:480>
[string "=[C]"]: in function `SetPoint'
[string "@Interface/SharedXML/AnchorUtil.lua"]:34: in function `SetPoint'
[string "@Interface/FrameXML/UIParent.lua"]:3086: in function `UIParentManageFramePositions'
[string "@Interface/FrameXML/UIParent.lua"]:2561: in function <Interface/FrameXML/UIParent.lua:2548>
[string "=[C]"]: in function `SetAttribute'
[string "@Interface/FrameXML/UIParent.lua"]:3104: in function `UIParent_ManageFramePositions'
[string "@Interface/AddOns/Blizzard_ObjectiveTracker/Blizzard_ObjectiveTracker.lua"]:1470: in function `ObjectiveTracker_Update'
[string "@Interface/AddOns/Blizzard_ObjectiveTracker/Blizzard_ObjectiveTracker.lua"]:878: in function <...zzard_ObjectiveTracker/Blizzard_ObjectiveTracker.lua:876>
That taint log contains messages from lots of other addons. It would be more useful to only have Rarity enabled.
Either way, I only see the usual Blizzard UI stuff that has been reported many times before. Clearly, their new edit mode functionality has some issues, but I can't do anything about that and there's no mention of anything in Rarity's code that would cause this.
It's not evident whether this is a problem caused by Rarity, or just another Blizzard UI bug (I assume the latter).
Please provide a taint log showing more information, else I won't be able to do much :)
Copy/paste of the instructions from the Discord below:
🔸 Rarity has been blocked from an action only available to the Blizz UI. You can disable this addon and reload the UI
This message is frequently misleading since it tends to name "arbitrary" addons, which may or may not actually be responsible for the problem.
In order to make sure that the blame actually lies with Rarity and not another addon (or even Blizzard's UI itself), please do the following:
- Enable taint logging by typing
/console taintLog 2
in the game's chat window - Once the error has occurred, relog or exit the WOW client (to have it update its log files)
- Post the full contents of
World of Warcraft\_retail_\Logs\taint.log
with your report
For more background information, check out these links:
Here is an example
taint.log