Fedora 14 updates-testing report

[updates]

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/updates/openldap-2.4.23-10.fc14
https://admin.fedoraproject.org/updates/librsvg2-2.32.0-4.fc14
https://admin.fedoraproject.org/updates/rsyslog-4.6.3-3.fc14
https://admin.fedoraproject.org/updates/nss-3.12.10-4.fc14
https://admin.fedoraproject.org/updates/bcfg2-1.1.2-2.fc14
https://admin.fedoraproject.org/updates/audacious-plugins-2.4.5-4.fc14
https://admin.fedoraproject.org/updates/tomcat6-6.0.26-21.fc14
https://admin.fedoraproject.org/updates/wireshark-1.4.9-1.fc14
https://admin.fedoraproject.org/updates/zabbix-1.8.7-2.fc14
https://admin.fedoraproject.org/updates/Django-1.3.1-2.fc14

https://admin.fedoraproject.org/updates/php-5.3.8-1.fc14,maniadrive-1.2-32.fc14,php-eaccelerator-0.9.6.1-9.fc14
https://admin.fedoraproject.org/updates/quassel-0.7.3-1.fc14


The following Fedora 14 Critical Path updates have yet to be approved:

https://admin.fedoraproject.org/updates/librsvg2-2.32.0-4.fc14
https://admin.fedoraproject.org/updates/nss-3.12.10-4.fc14
https://admin.fedoraproject.org/updates/livecd-tools-14.3-1.fc14
https://admin.fedoraproject.org/updates/curl-7.21.0-10.fc14
https://admin.fedoraproject.org/updates/system-config-users-1.2.110-1.fc14

https://admin.fedoraproject.org/updates/ModemManager-0.4.998-1.git20110706.fc14
https://admin.fedoraproject.org/updates/unique-1.1.6-3.fc14
https://admin.fedoraproject.org/updates/xorg-x11-drv-savage-2.3.2-3.fc14
https://admin.fedoraproject.org/updates/mash-0.5.22-1.fc14
https://admin.fedoraproject.org/updates/policycoreutils-2.0.85-30.3.fc14

https://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.904-8.fc14.2
https://admin.fedoraproject.org/updates/xorg-x11-drv-qxl-0.0.21-3.fc14

https://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.16-14.20101010git8c8f15c.fc14

https://admin.fedoraproject.org/updates/libconcord-0.23-5.fc14,udev-161-9.fc14,concordance-0.23-2.fc14
https://admin.fedoraproject.org/updates/openldap-2.4.23-10.fc14


The following builds have been pushed to Fedora 14 updates-testing

avrdude-5.11-1.fc14
clamsmtp-1.10-4.fc14
cstream-3.0.0-1.fc14
dspam-3.10.1-1.fc14
grass-6.4.0-4.fc14
nemiver-0.9.0gtk2-1.fc14
ntfs-3g-2011.4.12-5.fc14
postfix-2.7.6-1.fc14
quassel-0.7.3-1.fc14
rubygem-hoe-2.12.3-1.fc14
saphire-3.5.1-1.fc14
shutter-0.87.3-1.fc14
simulavr-0.1.2.7-1.fc14
solfege-3.20.2-1.fc14
terminus-fonts-4.36-1.fc14
texmaker-3.1-1.fc14

Details about builds:



 avrdude-5.11-1.fc14 (FEDORA-2011-12621)
 Software for programming Atmel AVR Microcontroller

Update Information:

Update to Bugfix release 5.11
This release just re-syncs the git source with the actual packages. It should 
not change the actual package content except for changelogs and package version 
number.


ChangeLog:

* Mon Sep 12 2011 Hans Ulrich Niedermann  - 5.11-1
- Update to avrdude-5.11

References:

  [ 1 ] Bug #726919 - Automatic reset (DTR / RTS toggling) fails for "arduino" 
programmer type under Linux.
https://bugzilla.redhat.com/show_bug.cgi?id=726919
  [ 2 ] Bug #736164 - avrdude 5.11 is available
https://bugzilla.redhat.com/show_bug.cgi?id=736164




 clamsmtp-1.10-4.fc14 (FEDORA-2011-12587)
 A SMTP virus scanning system

Update Information:

set default clamav socket location

ChangeLog:

* Sun Sep 11 2011 Nathanael Noblet  - 1.10-4
- Fix bug #670569
* Tue May 24 2011 Nathanael Noblet  - 1.10-3
- Added tmpfiles.d entry
* Tue Feb  8 2011 Fedora Release Engineering  
- 1.10-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild

References:

  [ 1 ] Bug #670569 - Wrong ClamAddress in the default clamsmtpd.conf
https://bugzilla.redhat.com/show_bug.cgi?id=670569




 cstream-3.0.0-1.fc14 (FEDORA-2011-12595)

Fedora 15 updates-testing report

[updates]

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/updates/bcfg2-1.1.2-2.fc15
https://admin.fedoraproject.org/updates/mantis-1.2.8-1.fc15

https://admin.fedoraproject.org/updates/php-5.3.8-1.fc15,php-eaccelerator-0.9.6.1-9.fc15,maniadrive-1.2-32.fc15
https://admin.fedoraproject.org/updates/wireshark-1.4.9-1.fc15
https://admin.fedoraproject.org/updates/zabbix-1.8.7-2.fc15
https://admin.fedoraproject.org/updates/Django-1.3.1-2.fc15
https://admin.fedoraproject.org/updates/cyrus-imapd-2.4.11-1.fc15
https://admin.fedoraproject.org/updates/foomatic-4.0.8-3.fc15
https://admin.fedoraproject.org/updates/rsyslog-5.8.5-1.fc15
https://admin.fedoraproject.org/updates/quassel-0.7.3-1.fc15


The following Fedora 15 Critical Path updates have yet to be approved:

https://admin.fedoraproject.org/updates/libxfce4util-4.8.2-1.fc15
https://admin.fedoraproject.org/updates/openldap-2.4.24-5.fc15
https://admin.fedoraproject.org/updates/rsyslog-5.8.5-1.fc15
https://admin.fedoraproject.org/updates/grubby-7.0.16-5.fc15
https://admin.fedoraproject.org/updates/lldpad-0.9.41-4.fc15

https://admin.fedoraproject.org/updates/evolution-mapi-3.0.3-2.fc15,evolution-exchange-3.0.3-1.fc15,evolution-3.0.3-1.fc15,evolution-data-server-3.0.3-1.fc15,gtkhtml3-4.0.2-1.fc15
https://admin.fedoraproject.org/updates/livecd-tools-15.8-1.fc15
https://admin.fedoraproject.org/updates/tzdata-2011i-1.fc15
https://admin.fedoraproject.org/updates/udev-167-6.fc15
https://admin.fedoraproject.org/updates/udisks-1.0.3-3.fc15
https://admin.fedoraproject.org/updates/gcc-4.6.1-9.fc15,libtool-2.4-6.fc15
https://admin.fedoraproject.org/updates/libffi-3.0.10-1.fc15
https://admin.fedoraproject.org/updates/sendmail-8.14.5-3.fc15
https://admin.fedoraproject.org/updates/nspr-4.8.8-4.fc15
https://admin.fedoraproject.org/updates/nss-softokn-3.12.10-4.fc15
https://admin.fedoraproject.org/updates/mash-0.5.22-1.fc15

https://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.904-14.fc15.1

https://admin.fedoraproject.org/updates/libfprint-0.4.0-1.fc15,fprintd-0.4.1-1.fc15


The following builds have been pushed to Fedora 15 updates-testing

avrdude-5.11-1.fc15
clamsmtp-1.10-4.fc15
cstream-3.0.0-1.fc15
dspam-3.10.1-1.fc15
eekboard-1.0.3-4.fc15
grass-6.4.0-4.fc15
hercstudio-1.2.0-3.fc15
hyphen-2.7-3.fc15
libprelude-1.0.0-9.fc15
libxfce4util-4.8.2-1.fc15
libxml++-2.34.2-1.fc15
moserial-3.0.1-2.fc15
mumble-1.2.3-4.fc15
ntfs-3g-2011.4.12-5.fc15
openjade-1.3.2-38.fc15
openldap-2.4.24-5.fc15
php-pecl-radius-1.2.5-11.fc15
php-shout-0.9.2-8.fc15
pidgin-sipe-1.12.0-1.fc15
postfix-2.8.5-1.fc15
quassel-0.7.3-1.fc15
rabbitmq-server-2.6.0-1.fc15
rsyslog-5.8.5-1.fc15
rubygem-hoe-2.12.3-1.fc15
rubygem-isolate-3.2.0-1.fc15
saphire-3.5.1-1.fc15
shedskin-0.9-1.fc15
shutter-0.87.3-1.fc15
simulavr-0.1.2.7-1.fc15
solfege-3.20.2-1.fc15
terminus-fonts-4.36-1.fc15
wine-1.3.28-1.fc15

Details about builds:



 avrdude-5.11-1.fc15 (FEDORA-2011-12612)
 Software for programming Atmel AVR Microcontroller

Update Information:

Update to Bugfix release 5.11
This release just re-syncs the git source with the actual packages. It should 
not change the actual package content except for changelogs and package version 
number.


ChangeLog:

* Mon Sep 12 2011 Hans Ulrich Niedermann  - 5.11-1
- Update to avrdude-5.11

References:

  [ 1 ] Bug #726919 - Automatic reset (DTR / RTS toggling) fails for "arduino" 
programmer type under Linux.
https://bugzilla.redhat.com/show_bug.cgi?id=726919
  [ 2 ] Bug #736164 - avrdude 5.11 is available
https://bugzilla.redhat.com/show_bug.cgi?id=736164




 clamsmtp-1.10-4.fc15 (FEDORA-2011-12596)
 A SMTP virus scanning system

Update Information:

set default clamav socket location

ChangeLog:

* Sun Sep 11 2011 Nathanael Noblet  - 1.10-4
- Fix bug #670569

References:

  [ 1 ] 

Re: F16: gnome-screensaver very often becomes inoperable after some time

[Joachim Backes]

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
>>> supposed to be. Probably the same bug. I don't have any abrt crash
>>> reports for gnome-screensaver...
>>
>> Same here on a netbook.
> 
> mclasen pointed me to this gnome-desktop3 update:
> 
> http://koji.fedoraproject.org/koji/buildinfo?buildID=263162
> 
> it fixes my issue, may well fix yours (both of you) too. It's now part
> of the Giganto-GNOME update for 3.1.91.

I installed it, and it fixes my issue indeed :-)

-- 
Joachim Backes 

http://www.rhrk.uni-kl.de/~backes



smime.p7s
Description: S/MIME Cryptographic Signature
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Frederic Muller]

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 I was load testing F 15 and Windows, but
>> after jumping into Windows to try and get the temperatures, as
>> suggested, for a point of comparison the system over heated and shut
>> down. In fact it did it twice in a row, so that is more than enough
>> confirmation for me, I will be talking with Lenovo to get new hardware.
>>
>> I will also close up the bug report I filed. Thanks again for your
>> patience and the information, I learned a lot during this process.
> 
> No problem. The 'compressed air in the fan vents' wheeze is worth a
> shot, though. It can certainly help.

Funnily I went into the same problem on F15 and that happened before and
after I replaced the fan. It's also a Thinkpad, but older generation
(T60). I regularly get shut down because of excessive heat or can't
reboot because of it. Never ever happened before F15 (I assumed it was a
hardware problem).

I'll re-read the thread and see if I can get useful metrics.

Thanks.

Fred
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Adam Williamson]

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 jumping into Windows to try and get the temperatures, as
> suggested, for a point of comparison the system over heated and shut
> down. In fact it did it twice in a row, so that is more than enough
> confirmation for me, I will be talking with Lenovo to get new hardware.
> 
> I will also close up the bug report I filed. Thanks again for your
> patience and the information, I learned a lot during this process.

No problem. The 'compressed air in the fan vents' wheeze is worth a
shot, though. It can certainly help.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Erinn Looney-Triggs]

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, perhaps it is really good at hiding it.
>> [   96.742668] CPU3: Core temperature above threshold, cpu clock
>> throttled (total events = 1)
>> [   96.742676] CPU2: Core temperature above threshold, cpu clock
>> throttled (total events = 1)
>> [   96.743699] CPU2: Core temperature/speed normal
>> [   96.743701] CPU3: Core temperature/speed normal
>> [   99.005684] intel ips :00:1f.6: MCP limit exceeded: Avg temp
> A small data point, I started getting these (and automatic shutdowns) on
> a T410s, which I thought was Fedora 15's fault. Then I swapped the
> harddrive to an identical T410s and the errors stopped... I think pretty
> recent kernels (F15 or some update afterwards) have started reporting
> these. Also there was a bug that caused a way too many of these to be
> reported, but that should be fixed already
>
> Anyway, applying compressed air to the fan is never a bad idea. There
> was quite a bit of dust there in my case, but cleaning it up didn't
> help. The beast is now running sort-of-happily in an air conditioned
> office doing unimportant work.
>
> If you think it's F16, try running from a live cd of F14/15 for a  while
> to be sure? And you can also manually force the fan to run at max speed,
> see if that helps? (modprobe thinkpad_acpi fan_control=1 needed, I
> think)
>
>

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 jumping into Windows to try and get the temperatures, as
suggested, for a point of comparison the system over heated and shut
down. In fact it did it twice in a row, so that is more than enough
confirmation for me, I will be talking with Lenovo to get new hardware.

I will also close up the bug report I filed. Thanks again for your
patience and the information, I learned a lot during this process.

-Erinn

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Pekka Pietikäinen]

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.742668] CPU3: Core temperature above threshold, cpu clock
> throttled (total events = 1)
> [   96.742676] CPU2: Core temperature above threshold, cpu clock
> throttled (total events = 1)
> [   96.743699] CPU2: Core temperature/speed normal
> [   96.743701] CPU3: Core temperature/speed normal
> [   99.005684] intel ips :00:1f.6: MCP limit exceeded: Avg temp

A small data point, I started getting these (and automatic shutdowns) on
a T410s, which I thought was Fedora 15's fault. Then I swapped the
harddrive to an identical T410s and the errors stopped... I think pretty
recent kernels (F15 or some update afterwards) have started reporting
these. Also there was a bug that caused a way too many of these to be
reported, but that should be fixed already

Anyway, applying compressed air to the fan is never a bad idea. There
was quite a bit of dust there in my case, but cleaning it up didn't
help. The beast is now running sort-of-happily in an air conditioned
office doing unimportant work.

If you think it's F16, try running from a live cd of F14/15 for a  while
to be sure? And you can also manually force the fan to run at max speed,
see if that helps? (modprobe thinkpad_acpi fan_control=1 needed, I
think)


-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Erinn Looney-Triggs]

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 when
>>> under heavy load it hits 60's and keeps running along fine. 
>>>
>>> kevin
>>>
>>>
>> Kevin, 
>> Thanks for that info, I too run about 45 or so on idle, but the leap
>> up is huge once load is put on the system. It goes from 45 to about 98
>> in a matter of 10 seconds or so. 
> It'd be interesting to know how hot the system gets in F15 and Windows
> when under load - is it just barely squeaking under 98, or is it way
> lower? You can check with 'acpi -V' or 'sensors' (after setting it up)
> in Linux, and speedfan in Windows - http://www.almico.com/speedfan.php .

Thanks, yeah that was my next planned step, though I didn't know about
speed fan. I also filed a bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=737700. I will let you know
when I do :).

-Erinn
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Adam Williamson]

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 keeps running along fine. 
> > 
> > kevin
> > 
> > 
> 
> Kevin, 
> Thanks for that info, I too run about 45 or so on idle, but the leap
> up is huge once load is put on the system. It goes from 45 to about 98
> in a matter of 10 seconds or so. 

It'd be interesting to know how hot the system gets in F15 and Windows
when under load - is it just barely squeaking under 98, or is it way
lower? You can check with 'acpi -V' or 'sensors' (after setting it up)
in Linux, and speedfan in Windows - http://www.almico.com/speedfan.php .
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Erinn Looney-Triggs]

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 too run about 45 or so on idle, but the leap up
is huge once load is put on the system. It goes from 45 to about 98 in a
matter of 10 seconds or so.

-Erinn

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Adam Williamson]

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 while in Windows, it might
> > reproduce the issue.
> 
> I ran stress -c 5 (I have 4 cores with HT) on the laptop and was able to
> generate the CPU thermal events under F 16.
> 
> So I then ran prime95 in windows for about an hour, didn't get anything
> in the logs, though I don't pretend to understand windows logging
> structure or to even say mine is set up correctly.
> 
> So I then switched to booting F 15 from a rescue disk, and chrooting
> into my F 16 install and running stress -c 5 again (basically a long way
> around to booting an older kernel), and I was unable to generate the CPU
> thermal events.
> 
> I doubt this is an apples to apples comparison, but it is about as close
> as I can get with what I know. Is it possible the F 16 is just logging
> more information and that is why I am seeing this error? Like I said
> never saw this with F 15, you believe it is HW, I don't buy it yet, so
> is there something else that could explain it?

yeah, that does point to something else, which is interesting: it's hard
to see offhand how F16 could be running a lot hotter than F15 or Windows
assuming you ran up a heavy load on all of them. I suppose the graphics
card could be running hotter in F16 for some reason and that'd be
pushing it over the edge.

AIUI, the actual overheat cutoff levels and the overheat shutdown
mechanism itself are implemented in the system firmware (BIOS) and Linux
just passes along the messages, so it's not that these overheat levels
are different in F16, or exist in F16 but don't exist in F15 or Windows,
or anything like that. I'm pretty sure it must actually be the case that
your system really is running physically hotter in F16.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Kevin Fenzi]

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 ventilation setup.

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


signature.asc
Description: PGP signature
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Tom Horsley]

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 and probably will again.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Erinn Looney-Triggs]

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 have 4 cores with HT) on the laptop and was able to
generate the CPU thermal events under F 16.

So I then ran prime95 in windows for about an hour, didn't get anything
in the logs, though I don't pretend to understand windows logging
structure or to even say mine is set up correctly.

So I then switched to booting F 15 from a rescue disk, and chrooting
into my F 16 install and running stress -c 5 again (basically a long way
around to booting an older kernel), and I was unable to generate the CPU
thermal events.

I doubt this is an apples to apples comparison, but it is about as close
as I can get with what I know. Is it possible the F 16 is just logging
more information and that is why I am seeing this error? Like I said
never saw this with F 15, you believe it is HW, I don't buy it yet, so
is there something else that could explain it?

-Erinn

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F16: gnome-screensaver very often becomes inoperable after some time

[Adam Williamson]

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 have any abrt crash
> > reports for gnome-screensaver...
> 
> Same here on a netbook.

mclasen pointed me to this gnome-desktop3 update:

http://koji.fedoraproject.org/koji/buildinfo?buildID=263162

it fixes my issue, may well fix yours (both of you) too. It's now part
of the Giganto-GNOME update for 3.1.91.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F16: gnome-screensaver very often becomes inoperable after some time

[Horst H. von Brand]

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 netbook.
-- 
Dr. Horst H. von Brand   User #22616 counter.li.org
Departamento de InformaticaFono: +56 32 2654431
Universidad Tecnica Federico Santa Maria +56 32 2654239
Casilla 110-V, Valparaiso, Chile 234   Fax:  +56 32 2797513
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fedora 16 Beta.TC2 Upgrade Skip Bootloader Test Case - Sanity Check Questions

[Adam Williamson]

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 
>  2. The system can boot into new version fedora without error 
>  3. The opened terminal, file browser, or other system
> applications should display and work correctly 
> 
> How does the newly installed system boot into new version fedora when
> there is no entry in the bootloader for it.  It seems to me that the
> present way it is written this testcase will always fail.
> 
> A more realistic set of results would be that any non fedora
> bootloader entries still work and that the new fedora can be booted if
> manually grub bootstrapped.
> 
> Unless I am misunderstanding this testcase?

As I wrote in the bug I believe you're correct here, the test case is
not correct as written: this option is supposed to not touch the
bootloader configuration, and hence there is a chance it will result in
an unbootable system (if the kernel from the previous release is still
available I think the configuration will be bootable, but we can't rely
on that).
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: tracker search tool

[Adam Williamson]

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 been looking for in GNOME Shell. ;)
> 
> Where in GNOME Shell would I find it, if I didn't want to run it
> as /usr/bin/gnome-session-properties? The shell's very own search
> feature finds lots of apps but entering "sess" or "autosta" empties
> the screen due to no results.

It's intentionally hidden from the GNOME 3 interface as the GNOME team
considers it deprecated and want to re-do it in a more GNOME 3-y way.
The only way to run is to call it directly from a console or alt-f2.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Adam Williamson]

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 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.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Adam Williamson]

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% CPU use in either of
those cases: the HW issue is that your hardware can't cope with running
under 100% CPU load for very long. But if tracker is thrashing your CPU
more than it should be, that's definitely a tracker issue.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Fedora 16 Beta.TC2 Upgrade Skip Bootloader Test Case - Sanity Check Questions

[Bob Lightfoot]

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 terminal, file browser, or other system applications
 should display and work correctly


How does the newly installed system boot into new version fedora when 
there is no entry in the bootloader for it.  It seems to me that the 
present way it is written this testcase will always fail.


A more realistic set of results would be that any non fedora bootloader 
entries still work and that the new fedora can be booted if manually 
grub bootstrapped.


Unless I am misunderstanding this testcase?

Bob Lightfoot

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora QA] #239: proventester request

[Fedora QA]

#239: proventester request
--+-
  Reporter:  ajax |   Owner:  mcloaked
  Type:  proventester request |  Status:  assigned
  Priority:  major|   Milestone:  
 Component:  Proventester Mentor Request  | Version:  
Resolution:   |Keywords:  
--+-
Changes (by mcloaked):

  * owner:  => mcloaked
  * status:  new => assigned

Comment:

 Hi, I will be happy to sponsor you - please just confirm that you have
 read and will follow the requirements at
 http://fedoraproject.org/wiki/Proven_tester, and then apply to join the
 proventester group in FAS and I will then sponsor you.

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Erinn Looney-Triggs]

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 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.

Here is the logs from the first few minutes of the system being up:

[   69.065721] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9053, limit 9000
[   74.055719] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9739, limit 9000
[   76.346477] nautilus used greatest stack depth: 2400 bytes left
[   94.015696] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9110, limit 9000
[   96.742668] CPU3: Core temperature above threshold, cpu clock
throttled (total events = 1)
[   96.742676] CPU2: Core temperature above threshold, cpu clock
throttled (total events = 1)
[   96.743699] CPU2: Core temperature/speed normal
[   96.743701] CPU3: Core temperature/speed normal
[   99.005684] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9687, limit 9000
[  103.995677] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9367, limit 9000
[  108.985716] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9021, limit 9000
[  113.975683] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9598, limit 9000
[  133.935783] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9350, limit 9000
[  138.925640] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9309, limit 9000
[  158.885623] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9638, limit 9000
[  163.875602] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9113, limit 9000
[  193.815559] intel ips :00:1f.6: MCP limit exceeded: Avg temp
10074, limit 9000
[  203.795558] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9029, limit 9000
[  208.785623] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9704, limit 9000
[  218.765551] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9386, limit 9000
[  223.755543] intel ips :00:1f.6: MCP limit exceeded: Avg temp
10147, limit 9000
[  238.725550] intel ips :00:1f.6: MCP limit exceeded: Avg temp
10052, limit 9000

Even by my standards this seems a bit in excess. The fan is working and
throttling up and down as would seem to be required. As I said cooling
isn't really an issue given the docking. Most thing point me back to F 16.

Like I said this machine has never shut down on me because of a thermal
event, since upgrading to Fedora 16 it has happened a number of times
(4-5 I think). As well kernel debugging was disabled to no avail, though
the machine is a bit  more responsive now.

-Erinn
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Erinn Looney-Triggs]

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, my clairvoyance is often in doubt.

-Erinn

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Adam Williamson]

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 CPU.
> 
> >From the logs:
> [ 2718.556684] intel ips :00:1f.6: MCP limit exceeded: Avg temp
> 9497, limit 9000
> [ 2778.415413] intel ips :00:1f.6: MCP limit exceeded: Avg temp
> 9700, limit 9000
> [ 2783.402899] intel ips :00:1f.6: MCP limit exceeded: Avg temp
> 9049, limit 9000
> 
> As well as:
> Sep 11 22:02:31 localhost kernel: [  812.799835] CPU2: Core temperature
> above threshold, cpu clock throttled (total events = 639)
> Sep 11 22:02:31 localhost kernel: [  812.799870] CPU3: Core temperature
> above threshold, cpu clock throttled (total events = 638)
> 
> Smolt profile:
> http://www.smolts.org/client/show/pub_89da1bce-aee0-447a-b859-06a44111f08b
> 
> I don't really know where to begin on this, I figure blame the kernel
> :). Is anyone else experiencing this issue? Any tips for digging out the
> root cause on this?

One, I'd blame your laptop manufacturer, as any hardware which can't
cope with being run at full capacity for a reasonable period is badly
designed hardware. But that's not going to get you very far. =) (to
mitigate, you can get one of those cooling pads for laptops - they look
dumb, but they actually work. I had a similar laptop once that would
overheat-protect-shutdown when building kernels; a cooling pad solved
that problem. Or you can just try and clean out the
externally-accessible heatsinks a bit, that can help.)

Tracker shouldn't eat 100% cpu time for really extended periods, so if
it's doing this for more than, say, an hour, that may well be a bug in
tracker.

You might also want to check if lldpad is installed, and if so, remove
it or upgrade it to fix
https://bugzilla.redhat.com/show_bug.cgi?id=701943 , which could be
contributing to the problem (the update is linked in the bug).
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Jóhann B. Guðmundsson]

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 might have lost 2 laptops ( T61p and Dell inspiron 6000 ) due to this 
exact problem.

Ofcourse the argument can be made it's faulty hardware if this happens.

JBG
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Laptop overheating with F 16

[Mike Chambers]

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 CPU.

Not sure if other laptops are having same issue, but could be because
debugging turned on in the kernels at present, as well as that making it
slow, also making X or some other resource using lot of CPU to
compensate for it.  

Might try booting with kernel as slub_debug=- and see if that helps make
any different.  If it does, then the next kernel build I think is
suppose to have debugging turned off and that might help.  Then again,
might be something totally different.


-- 
Mike Chambers
Madisonville, KY

"The best town on Earth!"

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

[Fedora QA] #239: proventester request

[Fedora QA]

#239: proventester request
-+--
 Reporter:  ajax |   Owner: 
 Type:  proventester request |  Status:  new
 Priority:  major|   Milestone: 
Component:  Proventester Mentor Request  | Version: 
 Keywords:   |  
-+--
 As an experienced packager and tester, I am applying for proventester so
 that I can speed the flow of tested critical packages into Fedora.

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Laptop overheating with F 16

[Erinn Looney-Triggs]

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 exceeded: Avg temp
9497, limit 9000
[ 2778.415413] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9700, limit 9000
[ 2783.402899] intel ips :00:1f.6: MCP limit exceeded: Avg temp
9049, limit 9000

As well as:
Sep 11 22:02:31 localhost kernel: [  812.799835] CPU2: Core temperature
above threshold, cpu clock throttled (total events = 639)
Sep 11 22:02:31 localhost kernel: [  812.799870] CPU3: Core temperature
above threshold, cpu clock throttled (total events = 638)

Smolt profile:
http://www.smolts.org/client/show/pub_89da1bce-aee0-447a-b859-06a44111f08b

I don't really know where to begin on this, I figure blame the kernel
:). Is anyone else experiencing this issue? Any tips for digging out the
root cause on this?

Thanks,
-Erinn
 
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Pre-BetaTC2 Installer Testing

[Tom H]

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 custom boot.iso that could use some testing and karma before
 we kick off the F16 Beta TC2 (hopefully later today). If you have the
 time, please give these a spin:

 http://tflink.fedorapeople.org/iso/20110908_pre-betaTC2_x64.boot.iso
 http://tflink.fedorapeople.org/iso/20110908_pre-betaTC2_x64.boot.iso.sha256

 A normal install should be enough for:
    - https://admin.fedoraproject.org/updates/anaconda-16.17-1.fc16

 The "save anaconda traceback to bugzilla" testcase would be good for
 libreport:
 https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla
    - https://admin.fedoraproject.org/updates/libreport-2.0.5-7.fc16

 EFI installs would be good to test:
    - https://admin.fedoraproject.org/updates/grub-0.97-77.fc16
>>
>>> GPFs with what seems to be raid issues on this one.
>>
>> Clyde, it's great that you test, but it's really frustrating to get such
>> vague feedback: this is really no use at all. Is this a new problem? Did
>> you have the same problem in TC1? What type of install were you trying?
>> What's the existing partition layout? What partition layout did you
>> choose for the install? thanks.
>
> Ok, Mr. Williamson, go look at 737278.  My basement is drying, ruined
> crap on the curb and new drainage ditches being dug.  So I can now take
> some time to do the testing you like and which I like.
>
> This bug is a regression as it was not seen on any earlier F16 alpha
> dvds or live cds.  I see that another person has also reported a GPF.

I can't install F16betaTC2 with mdadm. The installation's OK but at
first reboot, I'm dropped to a "grub rescue" prompt (similar to what
happened previously with an alpha but this time with the latest
grub2).

I tried to boot into Anaconda's rescue mode twice but I got a GPF
after hitting "continue" and my computer froze completely. I'm using
VirtualBox on OS X.

I re-installed and hit the "grub rescue" prompt again. I've
unfortunately deleted the two vistual disks but if I have the time
later today, I'll do a re-install and both look at the array before
Anaconda shuts down and try to bring up it through another install.

(I'll add this to BZ 737278.)
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: What does fallback mode use for window manager?

[Adam Jackson]

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.org/mailman/listinfo/test

Re: Release criteria: virtualization tweak

[Peter Jones]

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
>> Fedora release.
>
> Hum, I think that's pretty bulletproof, neat. pjones, does it read okay
> to you?

Works for me.

-- 
 Peter
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

rawhide report: 20110912 changes

[Rawhide Report]

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 requires libicudata.so.46
389-admin-1.1.23-1.fc17.x86_64 requires libicuuc.so.46()(64bit)
389-admin-1.1.23-1.fc17.x86_64 requires libicui18n.so.46()(64bit)
389-admin-1.1.23-1.fc17.x86_64 requires libicudata.so.46()(64bit)
389-adminutil-1.1.14-1.fc16.i686 requires libicuuc.so.46
389-adminutil-1.1.14-1.fc16.i686 requires libicui18n.so.46
389-adminutil-1.1.14-1.fc16.i686 requires libicudata.so.46
389-adminutil-1.1.14-1.fc16.x86_64 requires libicuuc.so.46()(64bit)
389-adminutil-1.1.14-1.fc16.x86_64 requires libicui18n.so.46()(64bit)
389-adminutil-1.1.14-1.fc16.x86_64 requires libicudata.so.46()(64bit)
389-dsgw-1.1.7-1.fc16.x86_64 requires libicuuc.so.46()(64bit)
389-dsgw-1.1.7-1.fc16.x86_64 requires libicui18n.so.46()(64bit)
389-dsgw-1.1.7-1.fc16.x86_64 requires libicudata.so.46()(64bit)
R-core-2.13.1-4.fc17.i686 requires libicuuc.so.46
R-core-2.13.1-4.fc17.i686 requires libicui18n.so.46
R-core-2.13.1-4.fc17.x86_64 requires libicuuc.so.46()(64bit)
R-core-2.13.1-4.fc17.x86_64 requires libicui18n.so.46()(64bit)
acheck-0.5.1-4.fc15.noarch requires perl(Text::Aspell)
assogiate-0.2.1-5.fc15.x86_64 requires libgnomevfsmm-2.6.so.1()(64bit)
awn-extras-applets-0.4.2-0.4.bzr1537.fc17.x86_64 requires 
gnome-python2-gtkmozembed
bibletime-2.8.1-1.fc16.x86_64 requires libicuuc.so.46()(64bit)
bibletime-2.8.1-1.fc16.x86_64 requires libicui18n.so.46()(64bit)
bibletime-2.8.1-1.fc16.x86_64 requires libclucene.so.0()(64bit)
claws-mail-plugins-geolocation-3.7.9-9.fc17.x86_64 requires 
libchamplain-gtk-0.10.so.0()(64bit)
claws-mail-plugins-geolocation-3.7.9-9.fc17.x86_64 requires 
libchamplain-0.10.so.0()(64bit)
cluster-snmp-0.18.7-1.fc16.x86_64 requires libnetsnmp.so.25()(64bit)
coda-backup-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit)
coda-backup-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit)
coda-backup-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires libseglwp.so.1()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires librvmlwp.so.1()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires librdslwp.so.1()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires rvm-tools
coda-server-6.9.5-6.fc16.x86_64 requires libseglwp.so.1()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires librvmlwp.so.1()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires librdslwp.so.1()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit)
comoonics-cdsl-py-0.2-18.noarch requires comoonics-base-py
comoonics-cluster-py-0.1-24.noarch requires comoonics-base-py
contextkit-0.5.15-2.fc15.i686 requires libcdb.so.1
contextkit-0.5.15-2.fc15.x86_64 requires libcdb.so.1()(64bit)
couchdb-1.0.3-2.fc16.x86_64 requires libicuuc.so.46()(64bit)
couchdb-1.0.3-2.fc16.x86_64 requires libicui18n.so.46()(64bit)
couchdb-1.0.3-2.fc16.x86_64 requires libicudata.so.46()(64bit)
dh-make-0.55-3.fc15.noarch requires debhelper
dwdiff-1.9-2.fc16.x86_64 requires libicuuc.so.46()(64bit)
dwdiff-1.9-2.fc16.x86_64 requires libicui18n.so.46()(64bit)
dwdiff-1.9-2.fc16.x86_64 requires libicudata.so.46()(64bit)
emacs-spice-mode-1.2.25-5.fc15.noarch requires gwave
emerillon-0.1.90-1.fc16.x86_64 requires 
libchamplain-gtk-0.10.so.0()(64bit)
emerillon-0.1.90-1.fc16.x86_64 requires libchamplain-0.10.so.0()(64bit)
emerillon-devel-0.1.90-1.fc16.i686 requires pkgconfig(champlain-0.10)
emerillon-devel-0.1.90-1.fc16.x86_64 requires pkgconfig(champlain-0.10)
eog-plugins-3.1.2-2.fc16.x86_64 requires 
libchamplain-gtk-0.10.so.0()(64bit)
eog-plugins-3.1.2-2.fc16.x86_64 requires libchamplain-0.10.so.0()(64bit)
fawkes-core-0.4.2-4.fc16.i686 requires libopencv_video.so.2.2
fawkes-core-0.4.2-4.fc16.i686 requires libopencv_objdetect.so.2.2
fawkes-core-0.4.2-4.fc16.i686 requires libopencv_ml.so.2.2
fawkes-core-0.4.2-4.fc16.i686 requires libopencv_legacy.so.2.2
fawkes-core-0.4.2-4.fc16.i686 requires libopencv_imgproc.so.2.2
fawkes-core-0.4.2-4.fc16.i686 requires libopencv_hi

F-16 Branched report: 20110912 changes

[Branched Report]

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-6.fc16.x86_64 requires libOpenThreads.so.11()(64bit)
FlightGear-2.0.0-6.fc16.x86_64 requires libosgViewer.so.74()(64bit)
FlightGear-2.0.0-6.fc16.x86_64 requires libosgUtil.so.74()(64bit)
FlightGear-2.0.0-6.fc16.x86_64 requires libosgParticle.so.74()(64bit)
FlightGear-2.0.0-6.fc16.x86_64 requires libosgGA.so.74()(64bit)
FlightGear-2.0.0-6.fc16.x86_64 requires libosgDB.so.74()(64bit)
FlightGear-2.0.0-6.fc16.x86_64 requires libosgSim.so.74()(64bit)
FlightGear-2.0.0-6.fc16.x86_64 requires libosgFX.so.74()(64bit)
SimGear-2.0.0-6.fc16.i686 requires libosg.so.74
SimGear-2.0.0-6.fc16.i686 requires libOpenThreads.so.11
SimGear-2.0.0-6.fc16.i686 requires libosgParticle.so.74
SimGear-2.0.0-6.fc16.i686 requires libosgDB.so.74
SimGear-2.0.0-6.fc16.x86_64 requires libosg.so.74()(64bit)
SimGear-2.0.0-6.fc16.x86_64 requires libOpenThreads.so.11()(64bit)
SimGear-2.0.0-6.fc16.x86_64 requires libosgParticle.so.74()(64bit)
SimGear-2.0.0-6.fc16.x86_64 requires libosgDB.so.74()(64bit)
acheck-0.5.1-4.fc15.noarch requires perl(Text::Aspell)
askbot-0.7.17-1.fc16.noarch requires django-recaptcha-works
assogiate-0.2.1-5.fc15.x86_64 requires libgnomevfsmm-2.6.so.1()(64bit)
awn-extras-applets-0.4.2-0.1.bzr1523.fc16.x86_64 requires 
libgnome-menu.so.2()(64bit)
bibletime-2.8.1-1.fc16.x86_64 requires libclucene.so.0()(64bit)
cluster-snmp-0.18.7-1.fc16.x86_64 requires libnetsnmp.so.25()(64bit)
coda-backup-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit)
coda-backup-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit)
coda-backup-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires libseglwp.so.1()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires librvmlwp.so.1()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit)
coda-client-6.9.5-6.fc16.x86_64 requires librdslwp.so.1()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires rvm-tools
coda-server-6.9.5-6.fc16.x86_64 requires libseglwp.so.1()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires librvmlwp.so.1()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit)
coda-server-6.9.5-6.fc16.x86_64 requires librdslwp.so.1()(64bit)
comoonics-cdsl-py-0.2-18.noarch requires comoonics-base-py
comoonics-cluster-py-0.1-24.noarch requires comoonics-base-py
contextkit-0.5.15-2.fc15.i686 requires libcdb.so.1
contextkit-0.5.15-2.fc15.x86_64 requires libcdb.so.1()(64bit)
dh-make-0.55-3.fc15.noarch requires debhelper
ekiga-3.3.2-2.fc16.x86_64 requires libcamel-1.2.so.28()(64bit)
emacs-spice-mode-1.2.25-5.fc15.noarch requires gwave
evolution-rss-0.2.90-27.20110818git.fc16.x86_64 requires 
libcamel-provider-1.2.so.28()(64bit)
evolution-rss-0.2.90-27.20110818git.fc16.x86_64 requires 
libedataserver-1.2.so.14()(64bit)
evolution-rss-0.2.90-27.20110818git.fc16.x86_64 requires 
libebook-1.2.so.11()(64bit)
evolution-rss-0.2.90-27.20110818git.fc16.x86_64 requires 
libcamel-1.2.so.28()(64bit)
exaile-0.3.2.1-1.fc16.noarch requires hal
fawkes-guis-0.4.2-4.fc16.i686 requires libgvc.so.5
fawkes-guis-0.4.2-4.fc16.i686 requires libcdt.so.4
fawkes-guis-0.4.2-4.fc16.i686 requires libgraph.so.4
fawkes-guis-0.4.2-4.fc16.x86_64 requires libgvc.so.5()(64bit)
fawkes-guis-0.4.2-4.fc16.x86_64 requires libcdt.so.4()(64bit)
fawkes-guis-0.4.2-4.fc16.x86_64 requires libgraph.so.4()(64bit)
fawkes-plugin-player-0.4.2-4.fc16.x86_64 requires 
libboost_signals-mt.so.1.46.1()(64bit)
fawkes-plugin-player-0.4.2-4.fc16.x86_64 requires 
libboost_thread-mt.so.1.46.1()(64bit)
fawkes-plugin-player-0.4.2-4.fc16.x86_64 requires 
libgeos-3.2.1.so()(64bit)
fgrun-1.5.2-8.fc16.x86_64 requires libosg.so.74()(64bit)
fgrun-1.5.2-8.fc16.x86_64 requires libosgText.so.74()(64bit)
fgrun-1.5.2-8.fc16.x86_64 requires libOpenThreads.so.11()(64bit)
fgrun-1.5.2-8.fc16.x86_64 requires libosgViewer.so.74()(64bit)
fgrun-1.5.2-8.fc16.x86_64 requires libosgUtil.so.74()(64bit)
fgrun-1.5.2-8.fc16.x86_64 requires libosgParticle.so.74()(64bit)
fgrun-1.5.2-8.fc16.x86_64 re

FC15 TFTP open timeout.

[Francis SOUYRI]

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 alias" (cluster address) for the tftp server (next-server 
in the dhcp), when I use the real ip I have no problem.

I do some test from a fc15 tftp client, to an "ip alias" I have this:

tftp> trace
Packet tracing on.
tftp> get /thinstation/dell/pxelinux.0
sent RRQ 
received DATA 
sent ACK 
received DATA 
sent ACK 
received DATA 
sent ACK 
received DATA 
sent ACK 
received DATA 
sent ACK 
received DATA 
sent ACK 
sent ACK 
received DATA 
sent ACK 
received DATA 
sent ACK 
sent ACK 
sent ACK 

I found some information about a "Service Guard environment" from HP and 
an option to enable it:

"This option is required for some tftp clients. These clients reject the 
tftp reply received from a
different IP address than the one requested when the server’s interface 
is configured with
an alias IP address."

I do not see an option like that in the tftpd server of the FC15.

Best regards.

Francis
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

[Test-Announce] 2011-09-12 @ 15:00 UTC - Fedora QA Meeting

[Adam Williamson]

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 whoever ends up running the meeting will add it. Thanks!

Proposed agenda:
* Previous meeting follow-up
(https://fedoraproject.org/wiki/QA/Meetings/20110829)
* Beta preparation
* Update policy changes?
* Upcoming events
* AutoQA update
* Open discussion
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F16: gnome-screensaver very often becomes inoperable after some time

[Adam Williamson]

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, gnome-screensaver runs well (as child of
> gnome-session), but after some time (can't say how long), no more
> screensaver is running. I have to logout and login again for getting a
> running screensaver.
> 
> Anybody sees this too?

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...
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test