Bug 918506 - abrt usability: confusing popups, bad interaction with user
Summary: abrt usability: confusing popups, bad interaction with user
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Toman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-06 12:18 UTC by David Tonhofer
Modified: 2015-12-02 16:04 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 02:44:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot of popups (145.81 KB, image/jpeg)
2013-03-06 12:18 UTC, David Tonhofer
no flags Details

Description David Tonhofer 2013-03-06 12:18:46 UTC
Created attachment 705898 [details]
Screenshot of popups

Description of problem:
-----------------------

  > In KDE:
  > Getting a problem with the nepomuk server
  > Submit a bug report as not root
  > ABRT asks for the "'default' keyring" password (that would be the
    Gnome keyring, but that's another problem)
  > Enter password...
  > Bug is submitted
  > FINE! 
  
  Now it's getting dicey:

  > ABRT seems to do some second step
  > A dialog pops up (probably from some Gnome application?)

     "Reading others problems requires authentication
      An application is attempting to perform an action that requires
      privileges. Authentication is required to perform this action
      Password for root
      Action: Get problems from all users
      Vendor: The ABRT team"

    If this wasn't Linux, I would suspect a hack.

  > As I don't answer the dialog in a timely manner, ABRT complains with
    ANOTHER popup:

     "Can't get problem list from abrt-dbus: Timeout was reached."


It is very unclear why ABRT would do what it does or what the user is supposed to do or whether he should be trusty enough to enter the system root password into a mystery dialogue. Clearly this procedure has to be thought over. 

See attached screenshot.

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

abrt-2.0.20-1.fc17.x86_64

How reproducible:
-----------------

Happens from time to time.

Comment 1 Jiri Moskovcak 2013-03-06 12:26:35 UTC
You have checked the checkbox "Show all problems" which means showing problems of all users on the machine, which of course requires root password. The "mysterious dialogue" comes from policyKit not from ABRT. The only thing we could improve is the "Timeout reached" dialog, to make it more clear that it timed out because user didn't enter the password. What do you think?

Comment 2 Fedora End Of Life 2013-03-22 13:08:49 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry.)

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Michal Toman 2013-08-09 12:19:34 UTC
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem.

Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.

In addition, abrt-gui has been replaced by gnome-abrt.

Comment 4 James (purpleidea) 2015-09-11 05:27:38 UTC
I can confirm that I just experienced this popup on Fedora 21... Had no idea what it was, and a search engine led me here. I'm using GNOME.

Reopening...

Comment 5 Fedora End Of Life 2015-11-04 10:33:51 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 6 Fedora End Of Life 2015-12-02 02:44:57 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.