F16--Something went wrong in Gnome...
nathelbiya at gmail.com
Wed Nov 9 16:22:23 UTC 2011
2011/11/9 Antonio M <antonio.montagnani at gmail.com>:
> 2011/11/9 Niels Weber <nathelbiya at gmail.com>:
>> I have a similar issue.
>> 2011/11/9 Daniel J Walsh <dwalsh at redhat.com>:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>> On 11/08/2011 07:15 PM, Joe Zeff wrote:
>>>> On 11/08/2011 04:10 PM, antonio montagnani wrote:
>>>>> I rebooted disabling Selinux on the command line and I could use
>>>>> Gnome, then I restarted and system relabeled all files and I
>>>>> could login in Gnome. No idea what was going on, but that's it
>>>> I'm glad you found it. The reason I asked was that I've seen
>>>> people blame SELinux for random problems so often without the
>>>> slightest evidence that it's involved that I tend to be skeptical
>>>> about such claims unless there are alerts. BTW, when you were
>>>> using KDE did you check the troubleshooter for alerts? I'm not
>>>> sure if they'd still be there at this point, but it would be nice
>>>> to know if there were any and what they were.
>>> If you have a problem with SELinux please boot in permissive mode and
>>> not disabled, to report what SELinux is complaining about. That way
>>> we can figure out what the problem is and hopefully fix it for others.
>>> Usually it is a minor labeling problem. If you turn SELinux back on,
>>> the system should relabel itself, and the problem will be fixed.
>> the login screen didn't work, switching to runlevel 3 and startx worked though.
>> Setting selinux to permissive allowed the login screen to run.
>> Relabelling the file system didn't help at all.
>>> If you still have the auditlogs availabel could you email me the
>>> compressed output of
>>> ausearch -m avc
>> There is nothing in the timeframe in the output.
>> Any ideas?
>> users mailing list
>> users at lists.fedoraproject.org
>> To unsubscribe or change subscription options:
>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Are you sure to have relabeled ?? or did you switch from permissive to
> Just to clear
I did a
I think it said something about rebuilding the targeted setup and it
took quite some time.
More information about the users