I made a "tricky" install of modemmanager 0.6 on 12.04 LTS (which originally uses MM 0.5) and the bug disappeared. So I think it's purely a modemmanager bug, already solved in the last version.
I made a "tricky" install of modemmanager 0.6 on 12.04 LTS (which originally uses MM 0.5) and the bug disappeared.
So I think it's purely a modemmanager bug, already solved in the last version.