On Thu, 2021-03-18 at 21:56 -0400, Richard Ryniker wrote:
> Tried again after a few hours.  Still trouble with the retrace server,
> but local analysis was able to say I experienced the already-reported
>    https://bugzilla.redhat.com/show_bug.cgi?id=1937073
>    
> 
> 
> 
> Temporary unavailability of the server sounds plausible for the original 
> problem.
> 
> There are still some sharp edges in abrt.  A different problem report 
> complains
> thus:
> 
>    Querying server settings
>    Retrace server is unable to process package 
> 'tracker3-3.1.0~rc-1.fc34.x86_64'.
>    Is it a part of official 'Fedora 34 (Workstation Edition Prerelease)' 
> repositories?
>    Unknown package sent to Retrace server.
>    Do you want to generate a stack trace locally? (It may download a huge 
> amount of data but reporting can't continue without stack trace). 'YES'
>    Analyzing coredump 'coredump'
>    Cleaning cache...
>    Cache cleaning has finished
>    Coredump references 45 debuginfo files
>    Initializing package manager
>    Setting up repositories
>    Looking for needed packages in repositories
>    Going to install 35 debuginfo packages
>    Can't find packages for 45 debuginfo files
>    Packages to download: 35
>    Downloading 134.08Mb, installed size: 419.17Mb. Continue? 'YES'
>    Downloading (1 of 35) libffi-debuginfo-3.1-28.fc34.x86_64.rpm: 100%
>    Extracting cpio from 
> /var/tmp/dnf-ryniker-6l_rpqco/fedora-debuginfo-9605faba16ec80df/packages/libffi-debuginfo-3.1-28.fc34.x86_64.rpm
>    Caching files from unpacked.cpio made from 
> libffi-debuginfo-3.1-28.fc34.x86_64.rpm
>    Can't extract files from 
> '/var/tmp/abrt-tmp-debuginfo.aazm1A/unpacked.cpio'. For more information see 
> '/tmp/abrt-unpacking-ja455rpl'
>    Unpacking failed, aborting download...
>    Can't download debuginfos: [Errno 1] Operation not permitted: 
> '/var/cache/abrt-di/usr'
> 
> There appear to be two problems here:
> 
> The tracker3-3.1.0~rc-1.fc34.x86_64 package was installed from
> updates-testing.  Might the failure to recognize it be an issue with a
> server not up-to-date?  If so, I should welcome a less ambiguous
> diagnostic.
> 
> The /tmp/abrt-unpacking-ja455rpl file with details about the second
> problem contains:
> 
>    cpio: ./usr/lib/debug: Cannot change mode to rwxr-xr-x: Operation not 
> permitted
>    cpio: ./usr/lib/debug/.build-id: Cannot change mode to rwxr-xr-x: 
> Operation not permitted
>    cpio: ./usr/lib/debug/usr: Cannot change mode to rwxr-xr-x: Operation not 
> permitted
>    cpio: ./usr/lib/debug/usr/lib64: Cannot change mode to rwxr-xr-x: 
> Operation not permitted
>    249 blocks

Yeah, I had about the same experience trying to report a crash with
abrt today. Wound up just backtracing it with coredumpctl gdb instead.

The second issue could be filed against gnome-abrt or libreport, I
think. The first issue probably at
https://github.com/abrt/retrace-server/issues - I've mentioned it in
https://github.com/abrt/retrace-server/issues/414 , but it might need
its own issue.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net


_______________________________________________
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to