| Summary: | [6.8.3] Displays :1 and up don't get utmp entries | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Mike A. Harris <mharris> | ||||||||||
| Component: | App/xdm | Assignee: | Xorg Project Team <xorg-team> | ||||||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||||||
| Severity: | normal | ||||||||||||
| Priority: | high | CC: | twaugh | ||||||||||
| Version: | 6.8.2 | ||||||||||||
| Hardware: | x86 (IA32) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| URL: | https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=20901 | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Bug Depends on: | |||||||||||||
| Bug Blocks: | 7247 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Mike A. Harris
2005-04-10 16:29:33 UTC
Created attachment 2375 [details] [review] Fix for xdm-config.cpp to ensure logins on all displays make it to utmp Created attachment 2376 [details]
Xstartup file for xdm
Created attachment 2377 [details]
Xreset file for xdm
The attached patch for xdm-config was made against the 6.8.2 release. I'll also attach a unified diff containing all changes in one patch. Created attachment 2378 [details] [review] xorg-x11-6.8.2-xdm-config-utmp-fixes.patch This unified diff was created against stock 6.8.2 sources. It contains of all of the above changes plus changes to the Imakefile to install the new files in the right place. It applies cleanly to 6.8.2, as well as CVS head (as of today). Please review and apply this to CVS head. It should also be considered for the stable branch, as there are security ramifications of displays not getting logged in utmp. Comment on attachment 2378 [details] [review] xorg-x11-6.8.2-xdm-config-utmp-fixes.patch Nominating for approval for 6.8.x branch, once it is committed to CVS head first. applied to head. Assuming from last comment, that this bug is now resolved. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.