Bug 771538

Summary: XDG_SESSION_COOKIE is set on non-gdm login.
Product: [Fedora] Fedora Reporter: Chaim Frenkel <chaimf>
Component: ConsoleKitAssignee: Lennart Poettering <lpoetter>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: johannbg, lpoetter, metherid, notting, plautrba, systemd-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 16:22:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Chaim Frenkel 2012-01-04 01:18:12 UTC
Description of problem:

XDG_SESSION_COOKIE is set on non-gdm login, preventing proper access to sound (pulse-audio) when using startx.

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


How reproducible:
Consistently reproducable

Steps to Reproduce:
1. Change default.target to runlevel3.target
2. Reboot
3. Login to system with non-root id
4. env | grep XDG
5. startx
7. Use and sound app. No sound.
8. Open Sound Control Applet. Nothing shows under hardware
  
Actual results:


Expected results:


Additional info:

Comment 1 Bill Nottingham 2012-01-04 15:09:42 UTC
Why wouldn't you want login sessions on the console to also be considered sessions?

Comment 2 Lennart Poettering 2012-01-12 15:12:41 UTC
Note that XDG_SESSION_COOKIE is a ConsoleKit feature, not a systemd one. And it's set for all CK sessions regardless whether X or console, and is used for access control.

I am not sure I understand what this bug is about?

Comment 3 Chaim Frenkel 2012-01-23 00:54:29 UTC
I've been unable to run my machine properly with runlevel 3. 

When starting in runlevel 3, startx does not properly give me access to the sound card. The only way I've even been able to get any access is to unset XDG_* variables before running startx.

It's probably my lack of understanding of how all the new moving parts work together. But I've been unable to track down any documentation how all the pieces work, and what is needed to get all the ducks (permissions) lined up.

Comment 4 Fedora End Of Life 2013-01-16 15:00:50 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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 Fedora End Of Life 2013-02-13 16:22:11 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.