[09:32] <Jo_> hi, someone can help me please ?
[09:34] <Jo_> I have a bug on ubuntu 14.04, and seems like nobody have solved it on google
[09:38] <rbasak> Jo_: try #ubuntu for community support. This channel is for bug triage, not bug reporting or fixing.
[11:59] <eliasps> Hello, everyone. I have a question about bug triaging. When a bug report is incomplete, lacks information, and there is a way to identify the issue and collect information using ubuntu-bug, is it better to attach those information to the existing bug report or a new one to be created? Because I don't know if the information containing the CoreDump.gz or any personal info in stacktrace will turn the existing report to private when attached aft
[11:59] <eliasps> erwards. Thank you.
[12:15] <hggdh> eliasps: a coredump should never be attached to an already opened bug. The coredump can carry a lot of personal data
[12:15] <hggdh> eliasps: on the other hand, ubuntu-bug does NOT collect a coredump
[12:16] <hggdh> eliasps: finally -- if you have the bug #, we can have a look at it and be more precise
[12:17] <eliasps> hggdh, Thank you. I knew about the sensitivity of the CoreDump but didn't know that ubuntu-bug will not include it.
[12:19] <eliasps> hggdh, I'm new to the bug triaging process so I try to do it using the guide. Maybe I handled that one poorly. Take a look if you will: 1457703. Any pointers would be helpful for me to get familiar with bug triaging.
[12:19] <eliasps> https://bugs.launchpad.net/ubuntu-gnome/+bug/1457703
[12:19] <hggdh> bug 1457703
[12:19] <hggdh> heh
[12:33] <hggdh> eliasps: it might be the video driver crashing -- but IDK much about X -- what I remember about it is that X used to coredump out of apport; the ibus crash is probably not related.
[12:35] <eliasps> hggdh, thanks again! So how do one help the reporter identify the package affected in cases like this? Like you said, this one is probably because of X. How to move on from that? Use ubuntu-bug to collect information?