A quick google of "problems with Git" will quickly reveal the various challenges that git brings to the table, for example git push --force. More generally, any team using git needs to decide on a workflow and carefully adhere to it. How do we manage merge workflows? To rebase or not to rebase? etc. With traditional source control, this is significantly easier.
I'm not anti-git, far from it. I introduced Git into the company I work for and love it; and it is absolutely the best source control system for distributed teams that exists. If you have distributed teams, it's an absolute must. But if you can't see that it's more complex, then you obviously haven't had the wonderful experience of having to field complaining from 30+ developers and having to fix the amazingly inventive ways in which they have managed to screw things up.