Hide Forgot
Version-Release number of selected component (if applicable): gnome-abrt-1.2.2-1.fc23.x86_64 How reproducible: always Steps to Reproduce: 1. Run into a crash that has already been reported to bugzilla 2. Report the crash (again) 3. check "Restrict access to the report" 4. complete bug reporting wizard until you get the message (dialog) that private comments cannot be made on public bugzilla reports. Actual results: Users can choose to either abort or create a new private bug report and immediately close it as duplicate of the original bug report. Expected results: I want to subscribe (add me to CC) to the original bug report. There currently is no UI to directly do that. I have to click on the URL, open a browser and login to bugzilla and subscribe there. Additional info: I don't know whether this should become a third option or aborting is being replaced by subscribing. I favor the second because I don't see a use case for the first, but I don't have a strong opinion on this.
Thank you for the report. I favor the second too because libreport dialogues support only 2 states - yes/no.
(In reply to Jakub Filak from comment #1) > Thank you for the report. I favor the second too because libreport dialogues > support only 2 states - yes/no. About that: Gnome/Gtk+ devs and some usability people keep trying to educate devs to not use "yes/no" but more meaningful buttons.
(In reply to Christian Stadelmann from comment #2) > (In reply to Jakub Filak from comment #1) > > Thank you for the report. I favor the second too because libreport dialogues > > support only 2 states - yes/no. > > About that: Gnome/Gtk+ devs and some usability people keep trying to educate > devs to not use "yes/no" but more meaningful buttons. I would love to use more meaningful buttons and we will get there once but currently the libreport communication protocol supports only "yes/no" dialogues. The reporting window (report-gtk) spawns a child process (reporter-bugzilla) that communicates with Red Hat Bugzilla. The parent and child communicate over standard input/output. We know its limitation and we are trying to extend it but we just don't have spare time for "research & development" because we are overwhelmed with maintenance.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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.