can i be given accessibility to send picture to show my game lfg panel to a customer support ? I have tried everything, reset game turning off all addons, repair / scan, reload game, etc. How can i fix this bug. i cant list up to any group and it seems to be only on my side and not something for everyone.
btw forums are also bugged for my account. I cant even use anything apart from this lvl 12 shaman and a lvl 60 dk to put at my character avatar.
Upload to Imgur and link here. There is no direct image upload on the forum for any user level.
http s://imgur.com/a/wEujYlV
there is the link !
doesn’t let me send links tho
Did you unload addons or remove them? This really matters when troubleshooting. Plus, it definitely looks like another process is adding icons on top of the existing frame.
Same issue. Did not remove addons, I did unload all addons with no change
Unloading them is not enough for testing if they are a problem in many cases, especially addons that modify the UI.
i am having the same issue and tried what you suggested it did not fix the problem
it’s a bug turn on your language filter and it works after that.
Mine looks exactly the same. Just started tonight. While everyone else has been having issues, I’ve been playing and using LFG just fine since the patch. I’ve been playing all morning too. Then suddenly tonight it’s a problem. I tried turning the language filter on, turning it off, restarting the client, nothing works.
LFG is not working for me either.
What I’ve tried:
Nothing is working for me.
I work 6 days a week and to my joy I had 2 days off this week.
Sadly, I haven’t been able to play WoW because of this crippling LFG bug.
Please blizzard I’ll send you $20 just to help me fix this. 
Update: So turning on the Mature Language Filter and reloading the UI fixes LFG for every type of group except for Arenas. Questing, Dungeons, Raids, RBGs, all working. Soon as I try viewing Arena, I get the smashed icons and it breaks the other LFG sections until I reload the UI again.
It’s simply broken. All I want at this point is an official response on whether this bug exists or not. Right now those still have the issue are second guessing themselves just cuz the workaround did work for some, but not ALL of us.