Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 999707
| Summary: | pam fails to properly handle env variables when launching gui apps from root | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | The PowerTool <ThePowerTool_SC> | ||||
| Component: | pam | Assignee: | Tomas Mraz <tmraz> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | ThePowerTool_SC, tmraz | ||||
| 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: | 2013-08-22 07:07:36 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 753882 *** |
Created attachment 789004 [details] Session log during documented failure Description of problem: Apparent system crash: actual system lock-up (system still running and accessible via ssh) Version-Release number of selected component (if applicable): Fedora 18 How reproducible: Steps to Reproduce: 1. Log in as normal user in gnome under Fedora 18 2. start a terminal session 3. su - 4. enter gedit on CL Actual results: ]$ ls -la /run/user/1000/dconf/ -rw------- 1 root root 2 Aug 21 17:52 user subsequent system lock because current user doesn't have access Expected results: ]$ ls -la /run/user/1000/dconf/ -rw------- 1 username username 2 Aug 21 17:52 user system continues to operate normally because current-user is owner Additional info: session log will display: gnome-session[7489]: CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.