As per the Fedora 16 schedule [1], Fedora 16 Beta Release Candidate 3
(RC3) is now available for testing. Please see the following pages for
download links (including delta ISOs) and testing instructions. In
general, official live images arrive a few hours after the install
images: see the links be
On 09/27/2011 06:58 AM, Joachim Backes wrote:
> On 09/26/2011 08:21 PM, Tom Horsley wrote:
>> I've been noticing long delays when logging in after booting
>> to my f16 partition. I just tried an experiment.
>>
>> If I boot the system, and login as soon as the KDM prompt
>> appears, there is a 20 or
On 09/26/2011 08:21 PM, Tom Horsley wrote:
> I've been noticing long delays when logging in after booting
> to my f16 partition. I just tried an experiment.
>
> If I boot the system, and login as soon as the KDM prompt
> appears, there is a 20 or 30 second delay between hitting
> return in the log
The following Fedora 14 Security updates need testing:
https://admin.fedoraproject.org/updates/perl-FCGI-0.74-1.fc14
https://admin.fedoraproject.org/updates/tomcat6-6.0.26-21.fc14
https://admin.fedoraproject.org/updates/Django-1.3.1-2.fc14
https://admin.fedoraproject.org/updates/d
The following Fedora 15 Security updates need testing:
https://admin.fedoraproject.org/updates/perl-FCGI-0.74-1.fc15
https://admin.fedoraproject.org/updates/drupal6-views_bulk_operations-1.11-1.fc15
https://admin.fedoraproject.org/updates/bcfg2-1.1.3-1.fc15
https://admin.fedorapro
On 26 September 2011 17:41, Tim Flink wrote:
> Specifically, do we want to have Xen DomU support as a final release
> criteria?
I would certainly appreciate it, it it was. I used to run Fedora with
Xen up until the dom0 removal (I understand the reasons why that
happened and I've also noticed th
On Mon, Sep 26, 2011 at 11:17:38AM -0700, Adam Williamson wrote:
> > Anyhow, thoughts around making DomU support a final release criterion?
>
> I'm kinda ambivalent. I can see the 'should be fixed by install time'
> argument but that doesn't quite count as a compelling argument for
> making
It appears that with older versions of NetworkManager this file existed
in /usr/share/nm-applet/.
With 0.9.1.90-1.fc16 though it disappeared, causing nm-applet to crash
anytime I tried connecting to a wireless network. The error spit out by
nm-applet said it was looking for it at /usr/share/libnm
Apparantly, we have a zombie bug in the beta RC2 ...
A previously closed libreport bug [1] showed up again when the patch
was dropped from the spec. We have a new build to test, but we do need
karma on it.
I've built a test boot.iso with the new libreport, so if anyone has the
time to run through
I've been noticing long delays when logging in after booting
to my f16 partition. I just tried an experiment.
If I boot the system, and login as soon as the KDM prompt
appears, there is a 20 or 30 second delay between hitting
return in the login screen and getting the gnome-shell display
to appear
On Mon, 2011-09-26 at 10:41 -0600, Tim Flink wrote:
> During the discussion around Xen DomU support as a beta release
> criterion in the Fedora QA meeting today, the question of blocking for
> DomU came up.
>
> Specifically, do we want to have Xen DomU support as a final release
> criteria?
>
> I
On Mon, Sep 26, 2011 at 10:41:00AM -0600, Tim Flink wrote:
> During the discussion around Xen DomU support as a beta release
> criterion in the Fedora QA meeting today, the question of blocking for
> DomU came up.
>
> Specifically, do we want to have Xen DomU support as a final release
> criteria?
I just created https://bugzilla.redhat.com/show_bug.cgi?id=741375, and
think that it qualifies as a beta-blocker; at any rate, it is certainly
a regression from older Fedora releases where running the same version
of fedora as both host and a VM guest was able to use the host (rather
than the g
During the discussion around Xen DomU support as a beta release
criterion in the Fedora QA meeting today, the question of blocking for
DomU came up.
Specifically, do we want to have Xen DomU support as a final release
criteria?
I can think of two arguments for making it a release criterion:
1. I
#244: Cloud SIG Test Day
---+
Reporter: rbergero | Owner:
Type: defect| Status: new
Priority: major | Milestone: Fedora 16
Component: Test Day | Version:
R
#244: Cloud SIG Test Day
--+-
Reporter: rbergero | Owner:
Type: defect| Status: new
Priority: major | Milestone: Fedora 16
Component: Test Day | Version:
Keyw
The following Fedora 16 Security updates need testing:
https://admin.fedoraproject.org/updates/stunnel-4.42-1.fc16
https://admin.fedoraproject.org/updates/perl-FCGI-0.74-1.fc16
https://admin.fedoraproject.org/updates/drupal6-views_bulk_operations-1.11-1.fc16
https://admin.fedorapr
==
#fedora-meeting: Fedora QA Meeting
==
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2011-09-26/fedora-meeting.2011-09-26-15.01.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2011-09-26/fedora-meet
On Mon, 26 Sep 2011 11:43:52 -0400
Clyde E. Kunkel wrote:
> OK...was the problem the system would not shutdown in preparation to
> reboot, or was the problem the system tried to go thru the boot(-up)
> process and failed?
Well, since the screen went totally blank, and there was nothing
in the l
On 09/26/2011 10:11 AM, Tom Horsley wrote:
> On Mon, 26 Sep 2011 09:55:19 -0400
> Clyde E. Kunkel wrote:
>
>> I have seen this before after a systemd update. One time occurrence
>> usually.
>
> Judging from the normal messages I see on reboot, the code
> is trying to do some sort of "root pivot" t
On Mon, 26 Sep 2011 09:55:19 -0400
Clyde E. Kunkel wrote:
> I have seen this before after a systemd update. One time occurrence
> usually.
Judging from the normal messages I see on reboot, the code
is trying to do some sort of "root pivot" to swap in a
consistent set of files to run while killi
On Mon, Sep 26, 2011 at 8:34 AM, Tom Horsley wrote:
> I just applied latest f16 updates, had a whole bunch
> of files skipped due to dependency problems, but a
> vast number of updates applied OK.
>
> I then told system to reboot, the screen went totally
> black, and the reboot never happened.
>
>
On 09/26/2011 09:34 AM, Tom Horsley wrote:
> I just applied latest f16 updates, had a whole bunch
> of files skipped due to dependency problems, but a
> vast number of updates applied OK.
>
> I then told system to reboot, the screen went totally
> black, and the reboot never happened.
>
> The only
I just applied latest f16 updates, had a whole bunch
of files skipped due to dependency problems, but a
vast number of updates applied OK.
I then told system to reboot, the screen went totally
black, and the reboot never happened.
The only thing in the /var/log/messages file was the
normal entry
Compose started at Mon Sep 26 08:15:31 UTC 2011
Broken deps for x86_64
--
389-admin-1.1.23-1.fc17.i686 requires libicuuc.so.46
389-admin-1.1.23-1.fc17.i686 requires libicui18n.so.46
389-admin-1.1.23-1.fc17.i686 require
Dne 25.9.2011 23:21, Matthias Clasen napsal(a):
> I need some information on what is hanging where, then. On my system, -2
> 100% fixed a very reproducible hang after hitting Enter in the password
> entry.
For me at-spi2-atk.x86_64 2.1.92-2.fc16 was a pure disaster.
https://bugzilla.redhat.com/sho
Hey, everyone, while we're still busy validating Beta, there's a Test
Day going on today/tomorrow, Monday 2011-09-26, too:
https://fedoraproject.org/wiki/Test_Day:2011-09-26_ABRT
Looking at ABRT, and particularly its integration with libreport (which
some of you may remember has caused a few prob
27 matches
Mail list logo