Red Hat Bugzilla – Bug 302961
Live CD GDM Logon Problems
Last modified: 2007-11-30 17:12:16 EST
Description of problem:
Can not logon to Fedora 8 Test 2 from USB stick on an Acer Aspire 7520. Other
computers seem fine.
When attempting to log in by pressing enter the counter is reset to 1 min. If I
click on Fedoralive username the same happens.
Version-Release number of selected component (if applicable):
Occurs on every boot attempt. No other steps needed.
Steps to Reproduce:
Do you need any additional info? If so please msg me an I will provide as much
as I can.
I have posted in fedoraforum.org but as yet there has been no response so I am
unsure if anyone else is having a similar problem.
is the clock set right on the machine?
Yes the clock is set correctly in the BIOS.
Once the GDM countdown has got to 0 the countdown changes to -1... -2... -3 etc.
The same problem also occurs with the x86_64 but this time there is no touchpad
Adding to F8Target list.
I just ran the Fedora 8 Test 3 x86_64 Live CD, and I am experiencing the same
Fedora 8 eventually boots all the way up to GDM, and then I can double-click on
the Fedora user, or type his name and press enter, but it will never log in.
Once, the counter would always restart. Another time, it stopped where it was
(at 57 seconds). GDM just sits and waits. I can still access options like
session and language.
My machine is an Acer Aspire 5100:
startx never successfully brought up a session for me from one of the terminals,
Couldn't have the GUI.
i've got a startx problem.
It says :
xinit: Ressource temporarily unavailable (errno 11): unable to connect to X server.
xinit: No such process (errno 3): Server error
Please keep separate problems in separate bugs.
If this prevents people from logging in, it is blocker material
Looking at the greeter/daemon interaction, the countdown timer is only stopped
when the daemon sends a STOPTIMER command to the greeter, otherwise the greeter
will happily count below 0. So for some reason, th edaemon fails to send
STOPTIMER when the counter reaches 0.
*** Bug 328621 has been marked as a duplicate of this bug. ***
So I found a machine that was experiencing this today, and it had an atheros
wireless network card in it.
In syslog there was a kernel oops. A bunch of other things didn't work either:
gdb, yum, ifconfig all hung in an unkillable state.
I pulled the wireless card out, there was no oops, and the gdm problem went away.
I'd appreciate if those affected could mention what kind of network card they
have installed, and if they could attach /var/log/messages.
Created attachment 229261 [details]
hardware4linux.info describes my wireless card as:
"AMBIT Microsystem (by Atheros Communications) / AR5005G 802.11abg NIC
[Ethernet controller] (3.66666666667 x 6)"
which is confirmed by my installed hardware browser.
I don't feel comfortable uploading my /var/log/messages (it's paranoia), so
here's a symmetrically encrypted version, which will be chased with the
password right soon. Sorry for the inconvenience.
WiFi: Atheros A5007EG http://www.atheros.com/pt/AR5007EG.htm
Will try to get more info later and post.
moving to kernel.
*** This bug has been marked as a duplicate of 254192 ***