The daily scrum's official purpose is as follow:
- Communicating to the rest of the team what you did yesterday
- Communicating to the rest of the team what you are going to do today
- Communicating to the scrum master any impediments or blocked items
Applying this to your case:
- Discussion is not a part of the daily scrum, so whether there's anything to discuss is irrelevant
- "I have done bug 23/24/25 yesterday and I am going to concentrate on CSS bug files today" is a valid and useful scrum status. It tells everyone that one is progressing and what to keep their hands off for today. It also tells people that one hasn't been stuck on the same bug for three days.
- We need to have a check that there is no trouble brewing, problems happening, impediments etc.
The daily scrum's behind the scenes purpose is:
- Embodying the agile principle of transparency
- Minimizing the impact of problems by making sure they are reported as fast as possible
- Have a very quick feedback cycle of one day for many whole-team issues, which is preferable to having only an iteration-long feedback cycle
- To give your developers a place to speak or ask questions to everybody else instead of having to go desk-by-desk
- To have an ahead of time understanding if the team is going to make a sprint or not
- To let the team re-organize if the current workload distribution is not efficient
You can find a very good article by Jeff Sutherland on MSDN:
Individuals and interactions are essential to high-performing teams. Studies of "communication saturation" during one project showed that, when no communication problems exist, teams can perform 50 times better than the industry average. To facilitate communication, agile methodologies rely on frequent inspect-and-adapt cycles. These cycles can range from every few minutes with pair programming, to every few hours with continuous integration, to every day with a daily standup meeting, to every iteration with a review and retrospective.