"ability not learned" really odd

Hiya folks. Was wondering if anyone has some insight on an error I've been getting lately, "ability not learned"

I've had this happen on my hunter clones and never on my main shammy. It mostly occurs when I have to call my pet or revive it but not all the time. I'll go to feed my pet and the cursor changes to the grab pointer and I get the message in red on the middle of the screen. I have also had this happen when I try to loot or open an item like a chest.

The last thing that I changed was a new shot rotation macro on the clones of:

/castsequence reset=120 Bladefist's Breadth,Ogre Mauler's Badge
/cast [target=pettarget,nodead,exists] Kill Command
/castsequence [nocombat] Aimed Shot; [combat] reset=8 Serpent Sting, Arcane Shot, Steady Shot, Steady Shot, Steady Shot

None of the clones have any addons or anything special and my setup has been the same for weeks now. I tried searching the WOW forums but it's acting as if the search function isn't working this morning (for me anyways).

Thanks

This may be indirectly related - Since the last patch I've been getting an intermittent error message when applying armor kits to my groups armor. "Enchantment failed" (something close to that) will popup on one of the shaman or the druid. But when I inspect the armor, the armor kit was applied even though the message says it didn't.

This isn't giving any help to you directly, but may be both errors are caused by something in the last patch.

This behavior is similar to was happening right after 2.4 launched and mashing certain macros would cause the UI to basically "lock" - there were many many threads on the UI forums about it. Specifically the kill command / shot rotation macro was mentioned several times.

It seems fairly unrelated, the only reason i bring that up is because when I was having difficulties with it happening to one or more of my sham, it was the "ability not learned" message that would pop up... while trying to do something like open a chest, or interact with an npc or cast a spell via the clicking on a friendly.

The only way to get out of this state of stuckness is/was either to completely restart the game (logging out/in didnt work), or to successfully finish the ability that was "stuck" ... most often times it was a purge that had been mashed more or less the same instant that the mob-to-be-purged died. Occasionally this would result in the purge spell being highlighted as though it were being pressed/clicked and would remain that way until I could find something to purge... the first night I ran into this issue I ended up dueling myself *alot*

I think Blizzard has narrowed it down to the Kill Command in a macro. Its because the kill command has a small delay and its causing the macro to get stuck. They are testing a fix on the current PTR.

thanks for the info!