Sorry for being a paid in the ass, but I don't get it. I install the `vim' (which, judging from the `apt-cache show vim' description is the console version). Then I get the same error message as Steffen, about libgailutil.so.18, and vim doesn't run. And that's not a bug?
James> "simply doing "apt-get install vim" when vim-gnome is installed isn't going to change the binary that is used for the vim alternative." Shouldn't installing vim then prompt the user to choose a different alternative, suggesting the one that was just installed? (or at least one that works... ?) Should I have manually done one of the installation steps (updating the alternatives)? Of all the alternative-ized programs I've run, I've only come across this problem (of installing it, then it not working) with vim; is vim a special case? Or did I somehow manually remove libgail without removing vim-gnome? Or was this an issue in a version of vim-gnome different from the one Colin was examining? Or...? As far as I can tell, I've installed vim, observed that running '$ vim' doesn't work, and been told that it's not a bug for newly installed programs to not work. Where am I wrong? -- vim should depend on libgail18 https://bugs.launchpad.net/bugs/333843 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
