There is no one size fits all solution and each project is different. Bugs might also be categorized from mission critical to hardly worth fixing.
Unless critical to the running of the system, I prefer bugs to become story cards. That makes the priority of feature development vs. bug fixing really explicit. In a scenario where bug fixes are considered to be "outside of the sprint" the bug fixing might move toward fixing really trivial bugs while really important business features aren't being developed.
We've gone trough a number of permutations before setting on the bug as a story approach. Try some different things and replay them at team retro meetings.
