Re: How do I use abrt to report bugs?

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

 



On Wed, Dec 16, 2020 at 11:04 PM Sumantro Mukherjee <sumukher@xxxxxxxxxx> wrote:
>
> Hey,
>
> Best to talk about bugs in the @test@xxxxxxxxxxxxxxxxxxxxxxx  list.
> But, overall, "how" is simple,
> 1. Login to https://bugzilla.redhat.com/ with your FAS
> 2. write up the description and other mandatory feilds
> 3. fill in the right component, in your case abrt
> 4. write in the steps to reproduce with as much details as possible
> 5. create the report and might be a good idea to talk about it in the
> QA weekly meeting when "Open Floor" is called upon
>
> Hope that helps

I keep getting the error:

"Retace failed. Try again later and if the problem persists report this issue."


This is my entire log:

--- Running report_uReport ---
('report_uReport' completed successfully)

--- Skipping collect_GConf ---
No matching actions found for this event.

--- Skipping collect_vimrc_system ---
No matching actions found for this event.

--- Skipping collect_vimrc_user ---
No matching actions found for this event.

--- Skipping collect_xsession_errors ---
No matching actions found for this event.

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your
answer is 'No', a stack trace will be generated locally. (It may
download a huge amount of data). 'YES'
Querying server settings
Preparing an archive to upload
Uploading 2.7 MiB
Upload successful
Retrace job started
Analyzing crash data
................................................................................
......................................
Generating backtrace
................................................................................
.........................................
Retrace job failed
Retrace failed. Try again later and if the problem persists report
this issue please.
[2020-12-17 10:14:43] [I] Analyzing crash data

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). 'NO'
('analyze_CCpp' exited with 1)


-- 
Regards,
Sreyan Chakravarty
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux