Bug 235310

Summary:	smart-gui fails to load
Product:	[Fedora] Fedora	Reporter:	Stephanos Manos <stefmanos>
Component:	smart	Assignee:	Axel Thimm <axel.thimm>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	pmatilai
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-05-25 21:37:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stephanos Manos 2007-04-04 23:30:53 UTC

Description of problem:
when starting synaptic a popup window appears with "unknown error" 

Version-Release number of selected component (if applicable):
smart-0.50-45.fc7
smart-update-0.50-45.fc7
smart-gui-0.50-45.fc7


How reproducible:
always (when selinux is enabled)

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
The problem is with the pam file (/etc/pam.d/smart).
changing it to 
auth            include         config-util
account         include         config-util
session         include         config-util

instead of
auth       sufficient   /lib/security/pam_rootok.so
auth       sufficient   /lib/security/pam_timestamp.so
auth       required     /lib/security/pam_stack.so service=system-auth
session    required     /lib/security/pam_permit.so
session    optional     /lib/security/pam_xauth.so
session    optional     /lib/security/pam_timestamp.so
account    required     /lib/security/pam_permit.so

solves the problem

Comment 1 Stephanos Manos 2007-04-18 06:56:07 UTC

ping

Comment 2 Axel Thimm 2007-04-22 12:15:39 UTC

Can you provide some more details? Why does the above fail under selinux and why
does outsourcing into another config file help?

Also the issue description is a copy and paste from your synaptic bug report.
Perhaps the error is this time different than "unknown error"?

Comment 3 Stephanos Manos 2007-04-22 22:06:08 UTC

(In reply to comment #2)
> Also the issue description is a copy and paste from your synaptic bug report.
> Perhaps the error is this time different than "unknown error"?
Exactly the same

Comment 4 Bill Nottingham 2007-05-25 21:37:03 UTC


*** This bug has been marked as a duplicate of 231735 ***