Description of problem: SELinux is preventing ld-linux.so.2 from loading /usr/lib/libSDL-1.2.so.0.7.3.#prelink#.Cjl0lV which requires text relocation. Version-Release number of selected component (if applicable): RHEL 5.2 i386 Desktop How reproducible: I've run sosreport twice and it's done it both times. Steps to Reproduce: 1. Log into gnome desktop 2. Open gnome terminal 3. run "sudo /usr/sbin/sosreport" Actual results: During the sosreport generation, SELinux alert pops up an alert (see attachment). sos report does complete. Expected results: sos completes without SELinux alert warning. Additional info:
Created attachment 307001 [details] Text dump of the selinux alert notification
After running : chcon -t textrel_shlib_t '/usr/lib/libSDL-1.2.so.0.7.3.#prelink#.Cjl0lV' Does sosreport complete? And are you willing to provide me with the sosreport? Thanks Adam
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Actually, having tried the context change as requested, I've realised that the offending file actually changes each time, so the context change recommended by SELinux alert after one sosreport has no bearing on the next sosreport and as similar alert pops up, just complaining about a different file. I've opened service request #1832408 where I'll put my sosreports. I'll attache a couple more SELinux Alert notifications.
Created attachment 308305 [details] Text dump of the selinux alert notification
Created attachment 308306 [details] Text dump of the selinux alert notification
Created attachment 308307 [details] Text dump of the selinux alert notification
This request was previously evaluated by Red Hat Product Management for inclusion in the current Red Hat Enterprise Linux release, but Red Hat was unable to resolve it in time. This request will be reviewed for a future Red Hat Enterprise Linux release.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Unfortunately, Red Hat is unable to address this request in the current release. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
I'm not able to reproduce this but it seems odd that there are prelink temporary files left lying around like this: /usr/lib/libSDL-1.2.so.0.7.3.#prelink#.Cjl0lV That .#prelink#.<random> indicates that this is a prelink temp file. They should not be lying around the file system. Was prelink running while sos ran?
Hi. Sorry but I no longer work at the site where this host is, so don't have access to it. From what I understand of prelink though (not a whole lot), I think it would be pretty unlikely for it to have been running every time I tried to run the sos report - if I recall correctly, I tried several attempts over the course of several days. It's likely that this host has been decommissioned, so if there have been no other users reporting similar issues, maybe it was just a once-off problem with prelink???
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.