Comment 48 for bug 1767402

*sigh*

You are missing the point.

>I tried to post it to similar bug report.

No. This is entirely the wrong thing to do.

If you are posting about a new issue, you create a new bug report. You don't post about your issue in a "similar bug report." That's not how bug reporting is supposed to work.

If it's a different bug, it needs to be tracked as a different bug report, not as a comment on an existing bug report.

No one is going to work on or fix your issue if you post it as a comment on an existing bug report about a different issue. Do you understand? It will be ignored. It will never get fixed. The fact that you commented will not be in any way helpful to you or anyone else. If you want to actually accomplish something useful, then when you discover a new bug, you need to report it in a new bug report. it's that simple.

Even when you're not sure it's a new bug, if it _might be_ a new issue, you should report it in a new bug report. The maintainer of the package can always mark it as a duplicate.

>If you feel that I am trolling here, you have all rights to remove my bug report or posts.

1) I don't have the authority to remove your comments, I'm just another user here.

2) In fact, it is extremely rare for anyone to ever remove comments from a bug report here or on any of the various bug-tracking platforms, because that destroys audit trails. It would only be done if there were an extremely serious confidentiality or security issue raised by the presence of a comment.

3) When you post a comment on a bug report, all the other people who have participated in that bug report get email about it. These emails can't be "removed" or "taken back" once they are sent. In other words, when you post a comment that is not actually about the bug you post it on, you cause useless email that the recipients don't care about to a bunch of people. That's rude an obnoxious. Please don't do it again.