> if the problems happens to someone every time they run the software the issue is that those bugs don't happen every time, read the description and comments from this bug or the duplicates, they are not really useful :-(
> it happens in your environment so that you can fix it it doesn't happen, the fix comes from reading the code and figuring what might happen... > 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? right, "some conditions," could be timing, a memory corruption which will lead to a segfault every 25 restarts, etc. How bugs can be fixed without being reproduced? Those segfault have a "stacktrace", which tells us the code path followed which has been leading to the bug, by understanding the code logic it's often possible to see what could go wrong, or to see what part of the code is not robust enough against issues > 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. Right, not discussing that, it's just not always possible to get those informations... -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
