After discussion on irc between ogra, pitti and I:
workaround #1 - blacklist that uevent in upstart-udev-bridge, thus neither system init event will not be emitted, nor re-emitted to session upstart.
workaround #2 - blacklist that uevent in systemd-udev (via socket filter) if not needed by Mir.
The first one is proposed in a branch already, and that still leaves 5% cpu usage by systemd-udev constantly whilst the screen is on.
After discussion on irc between ogra, pitti and I: udev-bridge, thus neither system init event will not be emitted, nor re-emitted to session upstart.
workaround #1 - blacklist that uevent in upstart-
workaround #2 - blacklist that uevent in systemd-udev (via socket filter) if not needed by Mir.
The first one is proposed in a branch already, and that still leaves 5% cpu usage by systemd-udev constantly whilst the screen is on.