If the .bug-script doesn't ask any questions (ie is completely non- interactive - which I think is the case), calling the script from the apport hook via an apport_utils command and include its output as one field in the report seems reasonable.
-- Apport Hook https://bugs.launchpad.net/bugs/609177 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
