Bug 221835
Summary: | gdm[XXXX]: (null): cannot open shared object file: No such file or directory | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Erik Sohns <erik.sohns> | ||||
Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> | ||||
Status: | CLOSED WONTFIX | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6 | CC: | admin, ajb | ||||
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-03-18 18:41:50 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: | |||||||
Attachments: |
|
Description
Erik Sohns
2007-01-08 14:16:15 UTC
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 /var/log/messages: Feb 12 15:11:32 estrella gdm[17038]: Failed to start X server several times in a short time period; disabling display :0 Feb 12 15:11:40 estrella gdm[18706]: (null): cannot open shared object file: No such file or directory Feb 12 15:11:42 estrella gdm[18740]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 12 15:11:48 estrella gdm[18761]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 12 15:11:53 estrella gdm[18796]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 12 15:11:53 estrella gdm[18706]: deal_with_x_crashes: Running the XKeepsCrashing script 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 /usr/sbin/gdm-binary -nodaemon root 20689 0.0 0.0 4664 1056 ? Ss 15:23 0:00 /bin/sh /etc/gdm/XKeepsCrashing 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 /etc/gdm/XKeepsCrashing -noopen 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 GNU/Linux 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]
estrella_gdmDebug.log
grep -i gdm /var/log/messages , with Enable=true in /etc/gdm/custom.conf under
[debug] section.
Also noted with RHEL 5 update 1 (and was probably present prior to U1). Hi, 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) |