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

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

 



On Sun, Jun 23, 2019 at 9:34 PM, Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote:
That's your key piece of info. You're missing the debuginfo package, without it the backtrace has no info.

With a native, directly-installed RPM, the debug repo gets automatically enabled, and the debuginfo packages gets automatically fetched and installed. I guess with flatpacks, this is not automatic. Don't know much about flatpaks, but this is what you need to figure out how to make it happen.

That's not right. The backtrace was processed on the retrace server, so installing debuginfo locally should not be required.

I think it's a longstanding ABRT bug.

Michael

_______________________________________________
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