New info: I have discovered that midnight commander does start when I am logged in as myself. Or at least it has seemed to start when I have been patient enough to wait. Startup time can be anything from 8s to 5 minutes. When it takes several minutes, ps will not report an mc process until a good few of those minutes have passed.
I set up a clean user account and tried to launch mc a few times from there. I noted startup times ranging between 8s and 30s. I don't know if it was just luck that it didn't take longer to start up on any of these attempts. Hold on More new info... I tried to run mc again and this time it hung for about 15 minutes, for most of which time (I don't know if anything happened right at the end) ps did not report an mc process. At the end of about 15 minutes it gave up and the command prompt came up again. As I said before, this problem started just after mc was last updated by apt-get. -- new version of midnight commander is completely broken https://bugs.launchpad.net/bugs/130318 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
