Logging in to FC6T1 after updating overnight, The following error message window pops up:
There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work correctly.
The Settings Daemon restarted too many times.
The last error message was:
There was an unknown activation error.
GNOME will still try to restart the Settings Daemon next time you log in.
Here are my system particulars: [root@osprey ~]# rpm -q gdm gdm-2.15.6-1 [root@osprey ~]# uname -rm 2.6.17-1.2391.fc6 x86_64
And a related (?) message from /var/log/messages: Jul 14 06:50:58 osprey gdm[2204]: /usr/lib64/pkcs11/libcoolkeypk11.so: cannot open shared object file: No such file or directory
Hi,
And a related (?) message from /var/log/messages: Jul 14 06:50:58 osprey gdm[2204]: /usr/lib64/pkcs11/libcoolkeypk11.so: cannot open shared object file: No such file or directory
This should be a harmless message. It just means that it tried to use the new smartcard security token support I added, but couldn't because you don't have smartcard support installed on your system.
It's a confusing message though, I should probably change it to something like:
"this system is not configured for smart card support, disabling..."
or maybe just not log anything at all.
--Ray
On Fri, 2006-07-14 at 09:43 +0200, Ray Strode wrote:
Hi,
And a related (?) message from /var/log/messages: Jul 14 06:50:58 osprey gdm[2204]: /usr/lib64/pkcs11/libcoolkeypk11.so: cannot open shared object file: No such file or directory
This should be a harmless message. It just means that it tried to use the new smartcard security token support I added, but couldn't because you don't have smartcard support installed on your system.
It's a confusing message though, I should probably change it to something like:
"this system is not configured for smart card support, disabling..."
or maybe just not log anything at all.
Thanks. The larger issue remains then, inasmuch as I encounter the Gnome error popup upon login. We just know now that the missing DSO isn't the cause.
Is anyone else seeing the Gnome error described in the OP?
On 7/14/06, Ray Strode rstrode@redhat.com wrote:
Hi,
And a related (?) message from /var/log/messages: Jul 14 06:50:58 osprey gdm[2204]: /usr/lib64/pkcs11/libcoolkeypk11.so: cannot open shared object file: No such file or directory
This should be a harmless message. It just means that it tried to use the new smartcard security token support I added, but couldn't because you don't have smartcard support installed on your system.
It's a confusing message though, I should probably change it to something like:
"this system is not configured for smart card support, disabling..."
or maybe just not log anything at all.
Well if its compiled against something like a smartcard library surely gdm should depend on that library, hence during the upgrade it would just pull in the new deps.
Peter
On Fri, 2006-07-14 at 09:43 +0200, Ray Strode wrote:
Hi,
And a related (?) message from /var/log/messages: Jul 14 06:50:58 osprey gdm[2204]: /usr/lib64/pkcs11/libcoolkeypk11.so: cannot open shared object file: No such file or directory
This should be a harmless message. It just means that it tried to use the new smartcard security token support I added, but couldn't because you don't have smartcard support installed on your system.
It's a confusing message though, I should probably change it to something like:
"this system is not configured for smart card support, disabling..."
or maybe just not log anything at all.
--Ray
Just for the record. Does this newly added smart card support work with the OpenPGP smartcards by any chance?
Thanks, Jurgen
And a related (?) message from /var/log/messages: Jul 14 06:50:58 osprey gdm[2204]: /usr/lib64/pkcs11/libcoolkeypk11.so: cannot open shared object file: No such file or directory
This should be a harmless message. It just means that it tried to use the new smartcard security token support I added, but couldn't because you don't have smartcard support installed on your system.
It's a confusing message though, I should probably change it to something like:
"this system is not configured for smart card support, disabling..."
or maybe just not log anything at all.
--Ray
Just for the record. Does this newly added smart card support work with the OpenPGP smartcards by any chance?
Not sure, it should do. I have one at home but i haven't had a chance to test it properly. It detects my openpgp smart card in my USB CCID Card reader (O2Micro on a Dell D620 - with user bogus firmware option turned on) as well as a couple of other cards I plugged in for testing but I haven't had a chance to go through the rest of the procedure to test (read/write etc).
Peter
On Mon, 2006-07-17 at 20:25 +0100, Peter Robinson wrote:
And a related (?) message from /var/log/messages: Jul 14 06:50:58 osprey gdm[2204]: /usr/lib64/pkcs11/libcoolkeypk11.so: cannot open shared object file: No such file or directory
This should be a harmless message. It just means that it tried to use the new smartcard security token support I added, but couldn't because you don't have smartcard support installed on your system.
It's a confusing message though, I should probably change it to something like:
"this system is not configured for smart card support, disabling..."
or maybe just not log anything at all.
--Ray
Just for the record. Does this newly added smart card support work with the OpenPGP smartcards by any chance?
Not sure, it should do. I have one at home but i haven't had a chance to test it properly. It detects my openpgp smart card in my USB CCID Card reader (O2Micro on a Dell D620 - with user bogus firmware option turned on) as well as a couple of other cards I plugged in for testing but I haven't had a chance to go through the rest of the procedure to test (read/write etc).
Peter
Sounds promising! I hope that FC6's Evolution now knows how to use it properly as well. With FC5 it does not seem to know that it needs to ask for a passphrase when signing an email.
Jurgen
Jay Cliburn wrote:
Here are my system particulars: [root@osprey ~]# rpm -q gdm gdm-2.15.6-1 [root@osprey ~]# uname -rm 2.6.17-1.2391.fc6 x86_64
And a related (?) message from /var/log/messages: Jul 14 06:50:58 osprey gdm[2204]: /usr/lib64/pkcs11/libcoolkeypk11.so: cannot open shared object file: No such file or directory
The recently introduced smart card stuff seems to require a updated SELinux policy. File a bug report against SELinux targeted policy with the AVC denied messages from /var/log/messages.
Rahul
On Fri, 2006-07-14 at 18:20 +0530, Rahul wrote:
Jay Cliburn wrote:
Here are my system particulars: [root@osprey ~]# rpm -q gdm gdm-2.15.6-1 [root@osprey ~]# uname -rm 2.6.17-1.2391.fc6 x86_64
And a related (?) message from /var/log/messages: Jul 14 06:50:58 osprey gdm[2204]: /usr/lib64/pkcs11/libcoolkeypk11.so: cannot open shared object file: No such file or directory
The recently introduced smart card stuff seems to require a updated SELinux policy. File a bug report against SELinux targeted policy with the AVC denied messages from /var/log/messages.
I'm a bit confused. The error seems to indicate a missing shared object, not an AVC denied, although there *are* AVC denied messages associated with gdm-binary that I posted in another message to the SELinux list.
Just to make sure I understand, you wish me to file a BZ against selinux-policy-targeted for the missing libcoolkeypk11?
Thanks, Jay
Jay Cliburn wrote:
I'm a bit confused. The error seems to indicate a missing shared object, not an AVC denied, although there *are* AVC denied messages associated with gdm-binary that I posted in another message to the SELinux list.
Just to make sure I understand, you wish me to file a BZ against selinux-policy-targeted for the missing libcoolkeypk11?
There is two different issues. One is missing library which should be reported against the package supposed to be providing it. Another is the AVC denied messages confirmed as fixed upstream in fedora-selinux list just now.
Rahul
On Fri, 2006-07-14 at 18:47 +0530, Rahul wrote:
Jay Cliburn wrote:
I'm a bit confused. The error seems to indicate a missing shared object, not an AVC denied, although there *are* AVC denied messages associated with gdm-binary that I posted in another message to the SELinux list.
Just to make sure I understand, you wish me to file a BZ against selinux-policy-targeted for the missing libcoolkeypk11?
There is two different issues. One is missing library which should be reported against the package supposed to be providing it. Another is the AVC denied messages confirmed as fixed upstream in fedora-selinux list just now.
Understood. Thanks.
-
Jay Cliburn -
Jurgen Kramer -
Peter Robinson -
Rahul Sundaram -
Ray Strode