On 4/24/21 10:04 PM, Samuel Sieb wrote:
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.
ok.
one more question about filing bugs...
After filling in the required fields and any optional fields that I
think are helpful, is there something more I should do before clicking
the submit button? The past few bugs I've submitted seem to just stay
in the new state.