EeeBotu announces bugs multiple times
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
EeeBotu |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
here's an excerpt from #u-b-a on the 17th November 2009 Berlin local time:
[18:17:22] <EeeBotu> New bug #484318 in ubuntuone-client (main): "ubuntuone needs keyring unlock" [Undecided, New] https:/
[18:18:27] <EeeBotu> New bug #484309 in sound-juicer (universe): "Sound Juicer has a mind of its own...(grrrrr!)" [Undecided, New] https:/
[18:18:32] <EeeBotu> New bug #484310 in kvm (main): "XP guest bluescreens on startup" [Undecided, New] https:/
[18:20:46] <EeeBotu> New bug #484317 in gdm (main): "GDM allows root logins" [Undecided, New] https:/
[18:20:48] <EeeBotu> New bug #484318 in ubuntuone-client (main): "ubuntuone needs keyring unlock" [Undecided, New] https:/
[18:21:52] <EeeBotu> New bug #484309 in sound-juicer (universe): "Sound Juicer has a mind of its own...(grrrrr!)" [Undecided, New] https:/
[18:21:54] <EeeBotu> New bug #484310 in kvm (main): "XP guest bluescreens on startup" [Undecided, New] https:/
[18:23:00] <EeeBotu> New bug #484317 in gdm (main): "GDM allows root logins" [Undecided, New] https:/
[18:23:06] <EeeBotu> New bug #484318 in ubuntuone-client (main): "ubuntuone needs keyring unlock" [Undecided, New] https:/
notice bug #484318 being announced 3 times. This is very confusing especially for people new to the bug triaging process as they might think those are duplicate bug reports (like the reporter pressing the button multiple times) only to find out that they're one and the same. It makes the bug announcements hard to read too since you need to filter out what bugs weren't already announced.
Related branches
description: | updated |
Thank you for opening this bug and helping make triaging, er, Ubuntu, better. ;-)
I did a quick look at the eeeBotu logs, and indeed I see duplicate announcements. I am not sure to what attribute it right now, but I am tending to some sort of problem on the interface.
I will increase the eeeBotu log level, and will check on the interface also.