Bug 280841
Summary: | gdmXnest and gdmXnestchooser don't work | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | P Jones <bugzilla> |
Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 7 | CC: | bnocera |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-25 04:34:38 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
P Jones
2007-09-06 16:00:09 UTC
$ strace -ofoo -v gdmflexiserver -n $ grep -i xnest foo sendto(5, "FLEXI_XNEST :0 500 aac1966a15510"..., 68, MSG_NOSIGNAL, NULL, 0) = 68 Looks like a define isn't getting substituted. I think it does send the literal string over the wire... P Jones, would you mind attaching /etc/gdm/custom.conf? I can reproduce this on my system, the custom.conf looks hopelessly empty: $ cat /etc/gdm/custom.conf | grep -v ^# | grep -v "^$" [daemon] [security] [xdmcp] [gui] [greeter] GlobalFaceDir=/usr/share/pixmaps/ [chooser] [debug] [servers] okay that's fine, empty entries get pulled from /usr/share/gdm/defaults.conf What's the output of grep Xnest /usr/share/gdm/defaults.conf ? It could be we're setting Xnest wrong by default (I have some vague notion of running across this bug before. It could be I fixed it in rawhide, but not F-7) Never mind, it seems to work for me in gdm-2.20.1-5.fc8 P Jones? The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance. Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9. |