Understood that you don't want to hold the release for this.
However it seems to happen on my system every time. Booting with "noinotify" is a
pretty big stick -- for example, that kills using beagle.
It seems upstream has found and fixed this bug in a new version. I'll try to take
a look at backporting the fix to the breezy version, if that would help.
(In reply to comment 16)
Understood that you don't want to hold the release for this.
However it seems to happen on my system every time. Booting with "noinotify" is a
pretty big stick -- for example, that kills using beagle.
It seems upstream has found and fixed this bug in a new version. I'll try to take
a look at backporting the fix to the breezy version, if that would help.