I know I had that bug at home, with at least some taskbar3 builds (I haven't narrowed the bug's origin down). The solution seems like trying another build. I will send you a mail with a link to the newest taskbar3 and the right settings (that I will convert from the above settings)...