Red Hat Bugzilla – Bug 276881
citrix client installs and works but can't log back into GDM and X session.
Last modified: 2008-08-02 19:40:37 EDT
Description of problem:
My box is a Intel P4 D945GTP, Nvidia 7200...
In my case using either the Default Nvidia driver or using the restricted Nvidia
driver, the Citrix 10.6 Client Install worked fine and the client worked
perfectly; HOWEVER, the next time that I tried to log into GDM I got an error
saying something like "...my X session had lasted less than 10 seconds and would
I like to see the error log...".
Version-Release number of selected component (if applicable):
Happens every time on fresh system installs
Steps to Reproduce:
1. Ran a fresh Fedora 7 format/install/updates
2. Installed the Citrix Client and it worked
3. Logged out of Gnome and then couldn't log back in.
Completely ruins the system for end users. Same results with latest build of
Ubuntu Feisty and Gutsy.
Please see about adding the Citrix Client to the Fedora Repositories. No Citrix
Client is a Linux Deal-Breaker for me and most of my clients. -thanks
do you log in and log out within 10 seconds?
I was paraphrasing the error message about "..X session lasted less than 10
seconds...". Sorry. I wrote it down but left it at home. I can quote it later
tonight if needed.
It seems to be an X message.
To answer your question, the system will not log into GDM even after 10 seconds
or after full reboot.
I built a test system today with fresh Fedora 7 install with all updates and the
debugging packages installed. I can run some tests in the morning when I get to
the office. Is there anything specific that you would like me to test?
If you could set Enable=true in the [debug] section of /etc/gdm/custom.conf,
restart, reproduce the problem, and attach /var/log/messages, that would be good.
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.