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?
On Sun, Jun 23, 2019 at 8:35 PM Sam Varshavchik wrote:
>
> Chris Murphy writes:
>
> > Please try to install debuginfo manually using the command:
> > "debuginfo-install flatpak-1.4.1-1.fc30" and try again.
>
> That's your key piece of info. You're missing the debuginfo package, without
> it the ba
Chris Murphy writes:
Please try to install debuginfo manually using the command:
"debuginfo-install flatpak-1.4.1-1.fc30" and try again.
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 deb
I've got a 100% reproducible crash ([chris@flap ~]$ flatpak install
--from com.slack.Slack.flatpakref from flathub.org) and every time
abrt+retrace server puke on it as having low informational value.
That strikes me as either a bug in abrt or the package or libraries it
depends on but I can't fig
The following packages fail to build from source from at least Fedora 28 and
their FTBFs bugs are still in the NEW state.
Please make them build or retire them from Fedora. If you cannot work on the
packages but still consider them useful, orphan them:
PyPE https://bugzilla.redhat.com/show_bu
