I also saw this interesting process running
root 814 1 0 10:28 ?00:00:00
/usr/bin/abrt-watch-log -F Backtrace /var/log/Xorg.0.log --
/usr/bin/abrt-dump-xorg -xD
root 815 1 0 10:28 ?00:00:00
/usr/bin/abrt-watch-log -F BUG: WARNING: at INFO: possible recursive
below is Xorg.0.log
http://pastebin.com/kvwYPZLZ
Kevin
DON'T PANIC
On Sat, Apr 6, 2013 at 1:00 AM, fedora wrote:
> How about correcting that (your last log entries):
>
> Apr 5 18:45:40 localhost abrtd: Duplicate: core backtrace
> Apr 5 18:45:40 localhost abrtd: DUP_OF_DIR:
> /var/tmp/abrt/c
Allegedly, on or about 05 April 2013, Kevin sent:
> I read that `setenforce 0` should fix the problem and it did for about
> a week, but
Turning off the thing that catches a fault (amongst other things that
it's meant to do, to protect you) is not fixing the fault.
--
[tim@localhost ~]$ uname -
How about correcting that (your last log entries):
Apr 5 18:45:40 localhost abrtd: Duplicate: core backtrace
Apr 5 18:45:40 localhost abrtd: DUP_OF_DIR:
/var/tmp/abrt/ccpp-2013-03-24-13:37:37-1596
Apr 5 18:45:40 localhost abrtd: Deleting problem directory
ccpp-2013-04-05-18:45:31-1533 (dup o
I been having Gnome fail at the login screen intermittently since I
reinstalled a few weeks ago. I read that `setenforce 0` should fix
the problem and it did for about a week, but this time I'm really
stuck. `getenforce` returns Permissive and the problem persists. In
the attached paste from /var
