I think it's Apport that is started and I think it's quite usable program. However I don't know if/how it reports screenlets exceptions (we should check that). If we could create some better logs/reports for users (and maybe better manuals for reporting bugs), this is good, but disabling/enabling Apport is up to user, I think. It can be turned on/off from system privacy settings I think and is enabled by default in alphas/dailies (maybe betas too). Interfering with Ubuntu policies doesn't seem generally a good idea. And duplicating it doesn't seem reasonable too. If we are better off spawning screenlets as subprocesses, that's okay for me.
How bad are the comments in Software Center? -- You received this bug notification because you are a member of Screenlets Dev Team, which is subscribed to Screenlets. https://bugs.launchpad.net/bugs/1015684 Title: Screenlet launching To manage notifications about this bug go to: https://bugs.launchpad.net/screenlets/+bug/1015684/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~screenlets-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~screenlets-dev More help : https://help.launchpad.net/ListHelp
