Created attachment 413515 [details]
part of /var/log/messages showing the segfaults
Description of problem:
Whenever my computer has been on for a number of hours (3 or 4 in this case), ALL programs (and I really do mean ALL, except for the most basic programs such as cat or dmesg) suddenly start to segfault upon launch. Some programs also crash even though they have already been running for a while, but this is sporadic, the only sure way to get a program to crash is to launch a new instance of it.
I know this probably sounds really strange to you, but I can't describe it any better - when I launch a program from terminal it just says "Segmentation fault".
Version-Release number of selected component (if applicable):
13, latest updates applied.
I've had this for a while now, the first two or three times I thought it was just a glitch, but now I'm absolutely sure this is a bug in Fedora.
Steps to Reproduce:
I don't know. But it USUALLY (but far from always) happens when the computer has been running for a long time. It seems to happen more often if I have played fullscreen games.
EVERY program segfaults the second it's started.
. . .
I really don't know how to be helpful on this, but I have collected:
- relevant part from /var/log/messages
- the first of 8 or so crashes in abrt's list after rebooting
I do not know what all these apps have in common, but dmesg said ld-2.12.so and according to yum that belongs to glibc.
Created attachment 413516 [details]
The trace abrt provided of the first program in its list.
What are the latest updated packages?
Do you mean this?
glibc.i686 2.12-1 @fedora
glibc-common.i686 2.12-1 @fedora
glibc-devel.i686 2.12-1 @fedora
glibc-headers.i686 2.12-1 @fedora
rpm -qa --last
Created attachment 414045 [details]
rpm -qa --last
Does prelink -au help?
I can't say with certainty, as I don't know what conditions trigger this problem. But it seemed to happen more often after playing fullscreen games, and I just played SuperTux for half an hour and the system was still stable afterwards. So it looks like it did help. I'll report back to you if I notice my system going south again.
This is unlikely to be a software problem.