*IMPORTANT*: All DVDs and Lives are oversized, so will not fit on the
standard media.
As per the Fedora 19 schedule [1], Fedora 19 Alpha Test Compose 2 (TC2)
is now available for testing. Content information, including changes,
can be found at https://fedorahosted.org/rel-eng/ticket/5545#comment:3
Adam Williamson wrote:
> * TC1 DVD install fails on dependency issues, so we need a TC2
> soon without those
Hi, I can confirm that, but I could install minimal system .
Initially system doesn't start d-bus, after check /var/log/messages I
saw that was a selinux restriction.
After disable selin
As always, minutes and IRC transcript available on the wiki at
https://fedoraproject.org/wiki/QA/Meetings/20130325
Next meeting is scheduled for 2013-04-01 at 1500 UTC in #fedora-meeting.
If you have topics you think we should bring up at the
meeting, please add them to the Wiki page at
https
On Mar 25, 2013, at 5:26 PM, John Reiser wrote:
>> So, new bug, but file it against kernel or xorg-x11-drv-nouveau?
>
> If "kill -TERM " does restart the X server
> and results in a graphical display, then perhaps -nouveau might be better?
>
X doesn't even start. dmesg reports inability to
> So, new bug, but file it against kernel or xorg-x11-drv-nouveau?
If "kill -TERM " does restart the X server
and results in a graphical display, then perhaps -nouveau might be better?
This report:
[NVA8][Nouveau] GPU lockup - switching to software fbcon
https://bugzilla.redhat.com/sho
On Mon, 2013-03-25 at 16:37 -0600, Chris Murphy wrote:
> I'm seeing a nouveau regression in 3.9.0-0.rc4.git0.1.fc19.x86_64 that was
> not in rc3.git0.3. With rc3.git0.3 the plymouth screen was slightly
> corrupted, but once gnome loaded, everything worked OK. With rc4.git0.1 I
> have a totally b
On Mar 25, 2013, at 4:37 PM, Chris Murphy wrote:
> I'm seeing a nouveau regression in 3.9.0-0.rc4.git0.1.fc19.x86_64 that was
> not in rc3.git0.3. With rc3.git0.3 the plymouth screen was slightly
> corrupted, but once gnome loaded, everything worked OK. With rc4.git0.1 I
> have a totally blac
The following Fedora 17 Security updates need testing:
Age URL
262
https://admin.fedoraproject.org/updates/FEDORA-2012-10269/revelation-0.4.14-1.fc17
75
https://admin.fedoraproject.org/updates/FEDORA-2013-0455/fedora-business-cards-1-0.1.beta1.fc17
45
https://admin.fedoraproject.org/up
The following Fedora 18 Security updates need testing:
Age URL
76
https://admin.fedoraproject.org/updates/FEDORA-2013-0416/fedora-business-cards-1-0.1.beta1.fc18
45
https://admin.fedoraproject.org/updates/FEDORA-2013-2131/rubygem-rdoc-3.12-6.fc18
41
https://admin.fedoraproject.org/upd
I'm seeing a nouveau regression in 3.9.0-0.rc4.git0.1.fc19.x86_64 that was not
in rc3.git0.3. With rc3.git0.3 the plymouth screen was slightly corrupted, but
once gnome loaded, everything worked OK. With rc4.git0.1 I have a totally black
screen.
So, new bug, but file it against kernel or xorg-x
This took a bit longer than I was hoping but we finally have a staging
instance of the new blocker tracking app up and running:
https://qa.stg.fedoraproject.org/blockerbugs/
There are still a few kinks to work out around syncing with bugzilla
and on the app administration side of things but it is
On Mon, 2013-03-25 at 09:40 -0500, Mike Chambers wrote:
> Thought would try to do a test install this morning, using boot.iso. I
> got to the installer and started to configure, via graphical mode. When
> I got to the partitioning section, selected the disk, hit done, get a
> menu that shows my c
On Mon, 2013-03-25 at 06:01 -0400, Kamil Paral wrote:
> > So now we have to test not configure something in anaconda and see if
> > initial setup picks it up or not hurray for needles complication
> > instead
> > of just using either the installer or the initial setup tool to
> > completely handle
Thought would try to do a test install this morning, using boot.iso. I
got to the installer and started to configure, via graphical mode. When
I got to the partitioning section, selected the disk, hit done, get a
menu that shows my current partitions, and got stuck. The only
selections I saw was
Compose started at Mon Mar 25 09:15:07 UTC 2013
Broken deps for x86_64
--
[aeolus-conductor]
aeolus-conductor-0.10.6-2.fc19.noarch requires ruby(abi) = 0:1.9.1
[aeolus-configserver]
aeolus-configserver-0.5.1-2.fc19.noarch requ
> So, we add a new installer criterion:
>
> * The graphical installer interface must be able to create a working
> user account.
Do we want to hard-code this functionality, or do we want to say "if the
installer allows a user account creation, it must work properly"?
In the past I think I've he
> So now we have to test not configure something in anaconda and see if
> initial setup picks it up or not hurray for needles complication
> instead
> of just using either the installer or the initial setup tool to
> completely handle this.
I have to agree here, the new approach have some benefits
17 matches
Mail list logo
