The following Fedora 14 Security updates need testing:
https://admin.fedoraproject.org/updates/ecryptfs-utils-90-2.fc14
https://admin.fedoraproject.org/updates/libsoup-2.32.2-2.fc14
https://admin.fedoraproject.org/updates/foomatic-4.0.8-3.fc14
https://admin.fedoraproject.org/update
The following Fedora 15 Security updates need testing:
https://admin.fedoraproject.org/updates/seamonkey-2.3.3-1.fc15
https://admin.fedoraproject.org/updates/ecryptfs-utils-90-2.fc15
https://admin.fedoraproject.org/updates/roundcubemail-0.5.4-1.fc15
https://admin.fedoraproject.org/
On 09/12/2011 11:04 PM, Adam Williamson wrote:
> On Mon, 2011-09-12 at 17:53 -0300, Horst H. von Brand wrote:
>> Adam Williamson wrote:
>>
>> [...]
>>
>>> I don't manually lock the screen, but I've noticed a lot of times, when
>>> I come back from screen blank mode, the screen isn't locked. It's
>
On 09/13/2011 07:42 AM, Adam Williamson wrote:
> On Mon, 2011-09-12 at 15:23 -0800, Erinn Looney-Triggs wrote:
>
>> Well folks, thank you all so much for your time and energy. Adam, thanks
>> for your patience. Looks like this is a hardware issue, I don't know why
>> it didn't crop up before when
On Mon, 2011-09-12 at 15:23 -0800, Erinn Looney-Triggs wrote:
> Well folks, thank you all so much for your time and energy. Adam, thanks
> for your patience. Looks like this is a hardware issue, I don't know why
> it didn't crop up before when I was load testing F 15 and Windows, but
> after jumpi
On 09/12/2011 02:58 PM, Pekka Pietikäinen wrote:
> On Mon, 2011-09-12 at 10:37 -0800, Erinn Looney-Triggs wrote:
>
>> I know we hear this all the time in this business, but it used to work
>> just fine. Perhaps it is hardware failing, but why then would windows
>> never display any thermal issues,
On Mon, 2011-09-12 at 10:37 -0800, Erinn Looney-Triggs wrote:
>
> I know we hear this all the time in this business, but it used to work
> just fine. Perhaps it is hardware failing, but why then would windows
> never display any thermal issues, perhaps it is really good at hiding it.
> [ 96.742
On 09/12/2011 02:31 PM, Adam Williamson wrote:
> On Mon, 2011-09-12 at 14:11 -0800, Erinn Looney-Triggs wrote:
>> On 09/12/2011 01:56 PM, Kevin Fenzi wrote:
>>> Just as a datapoint, I am typing this on a thinkpad T510 running f16,
>>> and I see no heat issues. In normal operation I see 45-46C, and
On Mon, 2011-09-12 at 14:11 -0800, Erinn Looney-Triggs wrote:
> On 09/12/2011 01:56 PM, Kevin Fenzi wrote:
> >
> > Just as a datapoint, I am typing this on a thinkpad T510 running f16,
> > and I see no heat issues. In normal operation I see 45-46C, and when
> > under heavy load it hits 60's and k
On 09/12/2011 01:56 PM, Kevin Fenzi wrote:
>
> Just as a datapoint, I am typing this on a thinkpad T510 running f16,
> and I see no heat issues. In normal operation I see 45-46C, and when
> under heavy load it hits 60's and keeps running along fine.
>
> kevin
>
>
Kevin,
Thanks for that info, I to
On Mon, 2011-09-12 at 13:39 -0800, Erinn Looney-Triggs wrote:
> On 09/12/2011 11:45 AM, Adam Williamson wrote:
> >
> > If you don't do anything in Windows to cause extended high CPU usage,
> > then obviously the system temperature will remain lower.
> >
> > I suspect if you, say, ran Prime95 for a
On Mon, 12 Sep 2011 10:37:01 -0800
Erinn Looney-Triggs wrote:
> Adam,
>
> I suppose it could be the manufacturers fault, I have had this Lenovo
> ThinkPad T510 for a long time and never had any issues with it. As
> well, this thing isn't even on my lap it is in a dock with a pretty
> decent vent
On Mon, 12 Sep 2011 13:39:55 -0800
Erinn Looney-Triggs wrote:
> I don't buy it yet, so
> is there something else that could explain it?
I suspect it is a good idea to go ahead and
file a bugzilla against the kernel pointing
to all this info. Power management issues
have bit linux kernels before a
On 09/12/2011 11:45 AM, Adam Williamson wrote:
>
> If you don't do anything in Windows to cause extended high CPU usage,
> then obviously the system temperature will remain lower.
>
> I suspect if you, say, ran Prime95 for a while in Windows, it might
> reproduce the issue.
I ran stress -c 5 (I ha
On Mon, 2011-09-12 at 17:53 -0300, Horst H. von Brand wrote:
> Adam Williamson wrote:
>
> [...]
>
> > I don't manually lock the screen, but I've noticed a lot of times, when
> > I come back from screen blank mode, the screen isn't locked. It's
> > supposed to be. Probably the same bug. I don't h
Adam Williamson wrote:
[...]
> I don't manually lock the screen, but I've noticed a lot of times, when
> I come back from screen blank mode, the screen isn't locked. It's
> supposed to be. Probably the same bug. I don't have any abrt crash
> reports for gnome-screensaver...
Same here on a netbo
On Mon, 2011-09-12 at 15:29 -0400, Bob Lightfoot wrote:
> The
> https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_Skip_Bootloader
> says the expected results are as follows:
>
>
> Expected Results
> 1. The system should be upgraded to Fedora 16 version without
> error
>
On Sat, 2011-09-10 at 15:20 +0200, Michael Schwendt wrote:
> On Sat, 10 Sep 2011 13:12:50 +, JBG (Jóhann) wrote:
>
> > Tracker can be disabled in gnome-session-properties I myself did that
> > sometime during alpha since it caused excessive load on my laptop...
>
> Which is the tool I've bee
On Mon, 2011-09-12 at 10:37 -0800, Erinn Looney-Triggs wrote:
> I know we hear this all the time in this business, but it used to work
> just fine. Perhaps it is hardware failing, but why then would windows
> never display any thermal issues, perhaps it is really good at hiding it.
If you don't d
On Mon, 2011-09-12 at 10:02 -0800, Erinn Looney-Triggs wrote:
> Yeah the argument can always be made that it is a HW issue. In this
> case, running under windows I run into no thermal issues. As well,
> running under F 15 created no thermal issues.
Well, it's unlikely your system is running at 100
The
https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_Skip_Bootloader
says the expected results are as follows:
Expected Results
1. The system should be upgraded to Fedora 16 version without error
2. The system can boot into new version fedora without error
3. The opened term
#239: proventester request
--+-
Reporter: ajax | Owner: mcloaked
Type: proventester request | Status: assigned
Priority: major| Milestone:
Adam,
I suppose it could be the manufacturers fault, I have had this Lenovo
ThinkPad T510 for a long time and never had any issues with it. As well,
this thing isn't even on my lap it is in a dock with a pretty decent
ventilation setup.
I know we hear this all the time in this business, but it us
Yeah the argument can always be made that it is a HW issue. In this
case, running under windows I run into no thermal issues. As well,
running under F 15 created no thermal issues. I will give a shot at
disabling debugging to see what happens but this feels more deep seated
than that to me. However
On Mon, 2011-09-12 at 09:15 -0800, Erinn Looney-Triggs wrote:
> Since moving to Fedora 16 my laptop has been constantly overheating. In
> fact with the tracker-store taking up so much CPU it creates a perfect
> storm and the system will sometimes shut itself off because of the high
> heat in the CP
On 09/12/2011 05:15 PM, Erinn Looney-Triggs wrote:
> Since moving to Fedora 16 my laptop has been constantly overheating. In
> fact with the tracker-store taking up so much CPU it creates a perfect
> storm and the system will sometimes shut itself off because of the high
> heat in the CPU.
>
I mig
On Mon, 2011-09-12 at 09:15 -0800, Erinn Looney-Triggs wrote:
> Since moving to Fedora 16 my laptop has been constantly overheating. In
> fact with the tracker-store taking up so much CPU it creates a perfect
> storm and the system will sometimes shut itself off because of the high
> heat in the CP
#239: proventester request
-+--
Reporter: ajax | Owner:
Type: proventester request | Status: new
Priority: major| Milestone:
Component:
Since moving to Fedora 16 my laptop has been constantly overheating. In
fact with the tracker-store taking up so much CPU it creates a perfect
storm and the system will sometimes shut itself off because of the high
heat in the CPU.
>From the logs:
[ 2718.556684] intel ips :00:1f.6: MCP limit e
On Sat, Sep 10, 2011 at 10:51 AM, Clyde E. Kunkel
wrote:
> On 09/08/2011 06:16 PM, Adam Williamson wrote:
>> On Thu, 2011-09-08 at 17:28 -0400, Clyde E. Kunkel wrote:
>>> On 09/08/2011 01:57 PM, Tim Flink wrote:
Who's ready for some pre-betaTC2 installer testing fun?
I built a custo
On Sat, 2011-09-10 at 11:02 -0400, Tom Horsley wrote:
> Is metacity still the right component to use to report
> this?
Yes.
Be sure to check for messages from metacity in ~/.xsession-errors
- ajax
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.o
On 09/08/2011 02:26 PM, Adam Williamson wrote:
> On Thu, 2011-09-08 at 19:19 +0100, agraham wrote:
>
>>> I'm still not super happy with the wording, but I guess it's clearer.
>>> Any better ideas?
>>
>> Suggestions:
>>
>> A Fedora release must be able host virtual guest instances of the same
>> Fed
Compose started at Mon Sep 12 08:15:06 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
Compose started at Mon Sep 12 08:15:36 UTC 2011
Broken deps for x86_64
--
FlightGear-2.0.0-6.fc16.x86_64 requires libosg.so.74()(64bit)
FlightGear-2.0.0-6.fc16.x86_64 requires libosgText.so.74()(64bit)
FlightGear-2.0.0
Hello,
Since I upgrade our cluster from the FC14 to the FC15 I have a bad
problem with the tftpd server.
I have some thinstations booting over the network after the update the
boot failed with the message "TFTP open timeout". I have also the
problem with a fresh FC15 install.
I use an "ip alia
WHAT: Fedora QA Meeting
WHEN: 15:00 UTC (11:00 EDT, 08:00 PDT)
WHERE: #fedora-meeting
It's meeting time again! We missed last week, so a double dose of
meeting-y...excitement...this week. Same bat time, same bat channel.
If anyone has anything to add to the agenda, please reply to this mail,
and
On Mon, 2011-09-12 at 07:17 +0200, Joachim Backes wrote:
> Hi,
>
> having very often the problem that the screen can't be locked by the
> gnome-shell user menu or by the ctrl+alt+l key combination.
>
> This seems to be related to a crashing (??) gnome-gnomesceensaver:
>
> after having logged in,
37 matches
Mail list logo
