Let me try to clear some things up. su-to-root "will automatically call either gksu (default) or kdesu (when being launched under KDE) for better integration into the running desktop environment." Otzenpunk's script seems to attempt to do the same thing. One issue I have come across is that menu does not suggests gksu, kdebase-bin, kdebase- runtime, or sux. It does not depend on them. As a result, By just adding menu as a recommended package in wireshark, we are not guaranteeing that the user is able to use gksu (or any of the variants). Personally, I think we should recommend menu in wireshark, and then try to get menu to depend on (instead of suggest) gksu, kdebase-bin, kdebase-runtime, or sux.
I am not sure what Debian/Ubuntu policy has to say about this. gksu is fine for use on Ubuntu. However, I don't think we should be using it for applications installed on Kubuntu. su-to-root was designed to solve this issue. I think it is much simpler to recommend menu, and then use su-to- root for the .desktop file than to have to create a custom shell script like Otzenpunk did, for each application that needs to be run as root. -- no run as root in menu in hardy https://bugs.launchpad.net/bugs/209084 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
