Bug 569116 - "the software is not from a trusted source" dialog doesn't identify what it refers to
Summary: "the software is not from a trusted source" dialog doesn't identify what it r...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 572949 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-28 08:38 UTC by Osma Ahvenlampi
Modified: 2010-12-03 22:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 22:14:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
screenshot of the offending dialog (39.27 KB, image/png)
2010-02-28 08:39 UTC, Osma Ahvenlampi
no flags Details

Description Osma Ahvenlampi 2010-02-28 08:38:48 UTC
Description of problem:

Sometimes a batch of upgrades includes something from a repository which isn't signed. PackageKit will alert the user with a dialog stating "the software is not from a trusted source. Do not update these packages unless you are sure it is safe to do so". However, it fails to tell WHICH packages it's complaining about, making it impossible for the user/administrator to tell what's going on. 

However, the dialog goes on to ask for the root password. How stupid one would have to be to enter a root password here?

The "details" view is especially annoying, since it doesn't actually provide any more details, just the same complaint in a technical jargon.

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

PackageKit-0.5.6-1.fc12.x86_64

Comment 1 Osma Ahvenlampi 2010-02-28 08:39:45 UTC
Created attachment 396844 [details]
screenshot of the offending dialog

Comment 2 Steven M. Parrish 2010-03-13 01:44:03 UTC
This bug has been triaged

Steven M. Parrish
KDE & Packagekit Triager 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Steven M. Parrish 2010-03-13 02:41:05 UTC
*** Bug 572949 has been marked as a duplicate of this bug. ***

Comment 4 Bug Zapper 2010-11-03 21:09:28 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 WONTFIX if it remains open with a Fedora 
'version' of '12'.

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 prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2010-12-03 22:14:58 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.

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.