Arguably enough, if the problems happens to someone every time they run the software in a particular way and it happens in your environment so that you can fix it, I don't see how this is something that happens "randomly". It may not happen every time you shutdown but surely there are some conditions that trigger the issue. Otherwise I am not sure how you can say the fix is committed, if you don't know how to reproduce it?
It would be a huge help for QA to start getting this kind of input from the engineers so that we can build a meaningful regression test suite. It is not up to the developer to decide what the test cases should be like, you can give us the information on how you reproduced it so that we can decide whether it is worth adding or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/863930 Title: indicator-session-service crashed with SIGABRT (assertion failed: (0 <= index && index < 24)) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/863930/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
