Saw the same thing just now. wvdialconf was trying to figure out what's behind my /dev/ttyS2.
What actually is behind that device is a Bluetooth adapter, which confused wvdialconf. So (according to strace) it did a bunch of strange things with that device, and then busy-waited forever in a select() loop. This was a new edgy install. It seems that wvdialconf needs a hard timeout, preferably in the shell script that calls it. -- System lock on upgrade or new install https://launchpad.net/bugs/50041 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
