Re: Reporting is disabled because the generated backtrace has low informational value

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



OK so after spending three hours downloading and installing debug
symbols, because the generation can't tell me all the symbols needed
in one whack, I get to learn that this is a dup of another bug. I'm
perplexed why a locally generated back trace figures this out, but the
retrace server gives up?

It's also an old bug from April. I wasn't encounting this problem
until I did a clean install of Fedora 30 on my laptop today.

Mine
https://bugzilla.redhat.com/show_bug.cgi?id=1723242
The apparent dup
https://bugzilla.redhat.com/show_bug.cgi?id=1697566

Not a good UX.


Chris Murphy
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux