On Mon, 2008-08-11 at 15:04 +0000, Pedro Villavicencio wrote: > See that's why it's bad to submit two differents traces in one report. > let me edit it again. and please do not do it again.
Or of course you could just leave them both in there as one is supplementary information for the other. What's with this "rule" that there can be only one stack trace in a bug even if they are all related? Is there a real reason for this policy? FWIW, I discount your reason above because the bug description clearly stated what the problem being reported was and what information was related to what. Anyway... whatever. b. -- segfault in connection_listen_cb() https://bugs.launchpad.net/bugs/256933 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
