FuBar in general is old and bloated, and there is very little development or support of FuBar plugins. Most authors who wrote FuBar plugins have moved on to the DataBroker platform, as it's not only easier to work with as a developer, but it allows one plugin to work with dozens of different display addons. By contrast, FuBar plugins only work with FuBar.
EDIT: have since updated the mod to repackage with latest libraries, etc. in r127. Installing r127 (or later) will cause it to work without issues.
As mentioned, have yet to find a LDB-equivalent which is as well designed or featured. So get a LDB display, FuBar2Broker and be happy :).
If you really want to switch to a LDB-equivalent, be prepared for less features unless you use a number of different mods (which might overlap features). Or them having poorer coding, weird designs, etc..
On that end: tekability (LDB display for both total percentage damage & individual slots. And percentages on the character frame on items. But no repair costs or auto-repair)
or SmoothDurability. (Armored man modifications & info, character frame info + auto repair. Shows repair costs & total percentage in the character frame (lower left corner) or armored man. But no LDB display at all. And its character frame equipment percentages overlap those provided by tekability). EDIT: you can prevent its character frame ("paper doll") percentages from showing/overlapping with tekability's by heading into options and reducing the Paper Doll Threshold slider to 0%.
RepairBroker actually comes close to duplicating the features of FuBar_DurabilityFu, but its abandoned and is apparently somewhat buggy. Haven't seen anything buggy in my limited WoW 3.3 testing of it, but it may be.
Broker_Repair is currently "supported" & has a similar feature list to BrokerRepair; similar to FuBar_DurabilityFu. But it adds a kitchen-sink feature that's best left to a seperate mod: junk selling. And it uses several obsolete libraries.
A3Fu_Repair "works with FuBar & Broker". But it uses a weird library: "LibCombatLog.lua". It auto repairs & only displays total & item damage percentages in the tooltip. No repair costs.
["message"] = "Blizzard_CombatLog\\Blizzard_CombatLog.lua:3446: attempt to perform arithmetic on local 'uiScale' (a nil value)\nBlizzard_CombatLog\\Blizzard_CombatLog.lua:3495: in function `FCF_DockUpdate'\nInterface\\FrameXML\\UIParent.lua:1944: in function `UIParentManageFramePositions':\nInterface\\FrameXML\\UIParent.lua:1317: in function <Interface\\FrameXML\\UIParent.lua:1304>:\n<in C code>: in function `SetAttribute'\nInterface\\FrameXML\\UIParent.lua:1951: in function <Interface\\FrameXML\\UIParent.lua:1949>:\n<in C code>: in function `Hide'\nStatBlock_Durability-2.1.2\\StatBlock_Durability.lua:10: in main chunk\n\nLocals:|r\noldFCF_DockUpdate = <function> defined @Interface\\FrameXML\\FloatingChatFrame.lua:1050\nBlizzard_CombatLog_AdjustCombatLogHeight = <function> defined @Interface\\AddOns\\Blizzard_CombatLog\\Blizzard_CombatLog.lua:3425\n\n ---",
["type"] = "error",
["session"] = 122,
["counter"] = 1,
DuraBroker is apparently abandoned and it throws up a similar error on logon that StatBlock_Durability above does.
So you can see why I'm still using FuBar_DurabilityFu ;). Anyway, good luck. And in the future, if a mod you like stops working for you, provide more details on the problems you are having than "anyone able to get this to work...?".
Yep, overlooked that one; I stopped using/testing addons by that author long ago.
But...its also abandoned (the author is no longer around; they were an author who liked to rename common libraries). Uses an obsolete library. Apparently doesn't work with DockingStation (among other LDB displays) as it doesn't define a type field (although that can be fixed by editing the LUA). And doesn't provide various rep level repair costs, only a single cost.
But if it works for you, no problem :).
tekability + SmoothDurability or Broker_Repair (mentioned above) are probably the most reasonable currently supported options. I'm still stuck on FuBar_DurabilityFu for now though...heh.