Bug 1869129 - "Export the data for manual report" doesn't work well
Summary: "Export the data for manual report" doesn't work well
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libreport
Version: 33
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-17 03:08 UTC by lnie
Modified: 2021-11-30 17:30 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-30 17:30:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot1 (258.34 KB, image/png)
2020-08-17 03:08 UTC, lnie
no flags Details
screenshot2 (233.87 KB, image/png)
2020-08-17 03:08 UTC, lnie
no flags Details
screenshot2 (238.93 KB, image/png)
2020-08-17 03:09 UTC, lnie
no flags Details

Description lnie 2020-08-17 03:08:13 UTC
Created attachment 1711531 [details]
screenshot1

Description of problem:
As auto report doesn't work as expected#1869126,I try "Export the data for manual report"option, but there are two problems.
1)If I try to the example scp format,the report process fails every time,as shown in the attached screenshot1.I'm able to scp the log with the following format,but pop-up will be prompted to ask me put user and password,as shown in the screenshot2.If I omitting the ":" in password part,the process will fail.So,I'm not sure what the exact format should be used.
scp://lnie[:xxxd]@10.72.13.99/home/lnie/file4.tar.gz
2)As shown in the attached screenshot3,the message box comes up to ask me to put the reproducer steps,I don't think this is wanted behavior

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2020-08-17 03:08:56 UTC
Created attachment 1711532 [details]
screenshot2

Comment 2 lnie 2020-08-17 03:09:45 UTC
Created attachment 1711533 [details]
screenshot2

Comment 3 Ben Cotton 2021-11-04 16:27:51 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2021-11-30 17:30:45 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.