So there are two parts to this bug:
What libUAL is doing is saying "was I able to ask upstart to start this
application?" and returning whether it was able to do that. If the
application was started or failed to start is signaled in the started or
failed signals. I think this is useful as it allows the distinction of
what happened in a relatively low level library. Perhaps higher level
functions are needed, I'm not sure.
Aborting on invalid app ids. I think that it's important that we get bug
reports on invalid appids being sent to UAL, it shouldn't happen and is
a sign of a bug in higher levels of the stack. Perhaps it should be a
recoverable error instead of a crash, but really they're both just ways
of getting the info into whoopsie. More than happy to discuss ideas on
how to better report this, but I do think it needs to be reported so
that we start to see those higher level bugs.
** Changed in: upstart-app-launch (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285321
Title:
desktop-exec crashes when using gir bindings to launch a non-existant
app
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart-app-launch/+bug/1285321/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
