Bug 110369
Summary: | gtk_init_check () doesn't handle xauth failures | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Matthew Galgoci <mgalgoci> |
Component: | gtk2 | Assignee: | Matthias Clasen <mclasen> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | aleksey, mitr, nalin, 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: | 2007-10-19 19:32:58 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
Matthew Galgoci
2003-11-18 21:48:52 UTC
It is not a good idea to give access to the X11 session per se. If the user has restricted access to not-X11 programs, he can get access to the full X11 session with this. Closing as won't fix. Usermod is apparently at fault here because /usr/bin/up2date is a symlink to consolehelper. Alternatively, consolehelper should not fail critically if it barfs on xauth, and instead should fall back to console mode. This should probably be re-assigned to nalin :) When an X11 session is rejected as described in comment 0, gtk_init_check () or something it uses calls exit (1) instead of returning FALSE. This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |