On 4/24/21 7:26 PM, home user wrote:
On 4/24/21 4:01 PM, Samuel Sieb wrote:
On 2021-04-24 12:37 p.m., home user wrote:
The problem report implies that a bug should not be submitted because
the backtrace does not contain enough meaningful function frames to
be reported.
Not really. What it said is that it can't be automatically submitted,
but you can still file a bug report yourself.
It also implies to me that submitting a bug would be useless because the
backtrace does not contain enough meaningful function frames to the
problem be reported.
You don't need a backtrace to report a bug. "This program crashed and I
don't know why" is still a valid bug report.
By the way, if I don't know what to submit the bug against, what do I
put in the component field? It's a required field, but I didn't see an
option for unknown when I submitted the 2 bugs I submitted this week.
Also, what do I put in the component field if it seems the problem could
be two things? A selinux alert could be a selinux problem, or it could
be a problem with whatever was trying to do something when the alert was
triggered. Example: the caja problem dealt with in this list earlier
this month.
If you don't know for sure, then file it against wherever you see it.
If further investigations indicate the cause is elsewhere, then it can
be re-assigned to that other component.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
