[Test-Announce] Fedora 16 Beta Release Candidate 1 (RC1) Available Now!

Dan Scott dan at coffeecode.net
Thu Sep 15 21:01:48 UTC 2011


On Thu, Sep 15, 2011 at 4:44 PM, Tim Flink <tflink at redhat.com> wrote:
> On 09/15/2011 02:22 PM, Adam Williamson wrote:
>> On Thu, 2011-09-15 at 16:19 -0400, Dan Scott wrote:
>>> On Thu, Sep 15, 2011 at 3:17 PM, Adam Williamson <awilliam at redhat.com> wrote:
>>>> On Thu, 2011-09-15 at 12:22 -0400, Dan Scott wrote:
>>>>> I downloaded http://dl.fedoraproject.org/pub/alt/stage/16-Beta.RC1/Live/x86_64/Fedora-16-Beta-x86_64-Live-Desktop.iso
>>>>> and wrote it to a LiveUSB; system with i915 graphics boots up but is
>>>>> in the GNOME 3 "Oh no! Something has gone wrong" loop. gsettings-data
>>>>> was repeatedly reporting:
>>>>>
>>>>> "segfault at 18 ip ... error 4 in libgio-2.0.so.0.29990"
>>>>>
>>>>> and avc was reporting:
>>>>>
>>>>> "avc: denied {read} for pid=766 comm="dbus-daemon"
>>>>> path="/home/liveuser/.local/share/icc/edid-eaf3aa369b5533aad29891cf327dd3d7.icc"
>>>>> dev=dm-0 ino=147569
>>>>> scontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023
>>>>> tcontext=unconfined_u:object_r:data_home_t:s0 tclass=file
>>>>>
>>>>> Tried rebooting and the same thing happened again.
>>>>>
>>>>> Curiously, the TC2 Live image worked just fine earlier this morning; I
>>>>> was about to try an install and thought it would be best to use the
>>>>> beta now that it was announced.
>>>>
>>>> If you boot with 'enforcing=0' does that help?
>>>
>>> Yep. I went ahead and downloaded the x86_64 DVD installer for beta
>>> RC1, installed, and when I logged in it began the "Oh no!" loop again.
>>>
>>> Rebooting with enforcing=0 fixed that.
>>
>> Oop - if multiple people are seeing this, it sounds bad. Strange that I
>> didn't hit it when I built a test live image with what I thought was the
>> full RC1 package set.
>>
>> Can someone please file a bug using sealert (if you booted in permissive
>> mode, the AVCs should still show up and be reportable) and mark it as a
>> Beta blocker? Thanks!
>
> For some reason, selaert didn't detect any issues but I grabbed the
> errors by hand. Reported and marked as beta blocker:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=738803

Thanks Tim. I was getting there but slower than you :)

I can confirm, fwiw, that I didn't see any sealerts popping up once I
was in enforcing=0, but the avc's were in dmesg.


More information about the test mailing list