Description of problem:
recurring bootup syslog entry:
Jan 8 13:12:27 worms gdm: (null): cannot open shared object file: No such
file or directory
Version-Release number of selected component (if applicable):
Name : gdm Relocations: (not relocatable)
Version : 2.16.4 Vendor: Red Hat, Inc.
Release : 1.fc6 Build Date: Fri 15 Dec 2006 05:28:53
Install Date: Mon 18 Dec 2006 12:20:19 AM CET Build Host:
Group : User Interface/X Source RPM: gdm-2.16.4-1.fc6.src.rpm
Size : 11191239 License: LGPL/GPL
Signature : DSA/SHA1, Fri 15 Dec 2006 07:51:51 PM CET, Key ID b44269d04f2a6fd2
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL : ftp://ftp.gnome.org/pub/GNOME/sources/gdm
Summary : The GNOME Display Manager.
Steps to Reproduce:
that's a harmless warning related to the smart card code. It should probably
only be printed if debugging is enabled though.
(In reply to comment #1)
> that's a harmless warning related to the smart card code. It should probably
> only be printed if debugging is enabled though.
I have the same issue on my Fedora 7 laptop. My question is this, what is
the "smart card code"? Is it something built into the GDM binary. I'm hoping
its something that I can uninstall to rid my messages log of this warning.
as a workaround, I think if you install coolkey the message should go away.
I'm not so sure if it's harmless. I no longer have a gui nor can I see the
console on my system (ssh still works). I have the following error messages in
Feb 12 15:11:32 estrella gdm: Failed to start X server several times in a
short time period; disabling display :0
Feb 12 15:11:40 estrella gdm: (null): cannot open shared object file: No
such file or directory
Feb 12 15:11:42 estrella gdm: gdm_slave_xioerror_handler: Fatal X error -
Feb 12 15:11:48 estrella gdm: gdm_slave_xioerror_handler: Fatal X error -
Feb 12 15:11:53 estrella gdm: gdm_slave_xioerror_handler: Fatal X error -
Feb 12 15:11:53 estrella gdm: deal_with_x_crashes: Running the
There are no warnings or errors with the nv or nvidia drivers in
/var/log/Xorg.0.log . Trying the latest nvidia 171.05 driver just causes the
nvidia splash to flash the same number of times gdm tries to restart itself.
After the crash gdm is still running:
[root@estrella X11]# ps aux | grep gdm
root 20570 0.0 0.1 15600 3568 ? Ss 15:23 0:00
root 20689 0.0 0.0 4664 1056 ? Ss 15:23 0:00 /bin/sh
root 20710 0.0 0.0 1628 344 ? S 15:23 0:00
/usr/libexec/gdmopen -l /bin/sh -c /etc/gdm/XKeepsCrashing -noopen
root 20711 0.0 0.0 4664 1056 tty9 Ss+ 15:23 0:00 /bin/sh
root 21318 0.0 0.0 3896 668 pts/8 S+ 15:31 0:00 grep gdm
[root@estrella X11]# lspci | grep -i vga
01:00.0 VGA compatible controller: nVidia Corporation NV34GL [Quadro FX 500/600
PCI] (rev a1)
it's actually an agp. I can show you the outputs of cat /proc/driver/nvidia
files if necessary but I'm trying to get nv working again first. any ideas?
btw this is on:
Linux estrella 2.6.18-79.el5 #1 SMP Fri Feb 8 01:28:14 EST 2008 i686 i686 i386
Red Hat Enterprise Linux Server release 5.1 (Tikanga)
can you turn on Enable=true in the [debug] section of /etc/gdm/custom.conf and
post /var/log/messages with the updated debugging messages?
Created attachment 294843 [details]
grep -i gdm /var/log/messages , with Enable=true in /etc/gdm/custom.conf under
Also noted with RHEL 5 update 1 (and was probably present prior to U1).
We no longer support Fedora Core 6 and I am currently trying to get my open bug
count down to a more manageable state. I'm going to close this bug as WONTFIX.
If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?
(this is a mass message)