Comment 6 for bug 252026

I tested tovidgui (installed from repositories) on a new Hardy install and it does seem to work properly. I'm not sure what was wrong before, but it's possible that I was using the package from the tovid site, which may not be fixed to address the removal of makemenu from the user's path. If that's the case, I apologize; I really thought I was using the package from the repositories, but maybe in the initial confusion of trying to figure out what was going on, I installed the tovid project's .deb instead and didn't realize it. In any case, it seems that tovidgui works as long as it's installed from the Ubuntu repositories.

Also, all of the tovid tutorials that I know of assume that makemenu, etc. are in the user's path. In order to make things easier, how difficult would it be to tell users where to find makemenu when they try to call it unsuccessfully? I'm thinking of something along the lines of the messages that come up when a non-installed program is called, e.g.:

The program 'makemenu' is installed but is not in your path. You can run it by typing:
/usr/share/tovid/makemenu

I don't know how hard it would be to implement something like that, but I think it would make things easier on users who don't know how to locate makemenu manually.