[Fedora QA] #283: USB 3.0

[Fedora QA]

#283: USB 3.0
--+
 Reporter:  ccui  |   Owner:
 Type:  task  |  Status:  new
 Priority:  major |   Milestone:  Fedora 17
Component:  Test Day  | Version:
 Keywords:  USB 3.0   |  Blocked By:
 Blocking:|
--+
 Propose a Fedora USB 3.0 Test Day on 2012-03-15. This test day will cover
 several of USB 3.0 Class Driver, like: video Class, mass Storage, audio
 Class.

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

Experiences with F17-Alpha-RC4

[Joachim Backes]

Hi,

I made a fresh F17 desktop (gnome3) installation on my box to a real
partition with F17/Alpha/RC4: No problems during install, the system
runs immediately. Applying all available updates.

But there are some flaws:

1. No sound with "00:1b.0 Audio device: Intel Corporation N10/ICH 7
   Family High Definition Audio Controller (rev 01)." The output
   device is not shown by the "system settings" menu.

2. Font "True" not found during boot. The kernel line in
   /boot/grub2/grub.cfg contains such a SYSFONT parameter:

   linux/boot/vmlinuz-3.3.0-0.rc3.git7.2.fc17.x86_64
root=LABEL=F17 ro rd.md=0 rd.lvm=0 rd.dm=0
*SYSFONT=True* rd.luks=0
KEYTABLE=de-latin1-nodeadkeys LANG=en_US.UTF-8
rhgb quiet

3. One ugly problem after quitting a gnome3 session: logging in again
   (via gdm login window) shows in most cases the well know "Oh nO!
   something has gone wrong, logout!" dialog. Searching a little bit in
   /var/log/messages, I saw that there are some (unspecified) problems
   with /run/user/ and/or dot files in /tmp. I could get rid from
   these login problems by removing some files as

/tmp/.ICE-unix /tmp/.X11-unix /tmp/.X0-lock /run/user/

and then login again

4. The login after having entered the password takes a lot
   of time

Anybody made similar experiences?

Kind regards

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: RC4 and NFS

[Adam Williamson]

On Wed, 2012-02-22 at 21:54 -0800, Chuck Forsberg WA7KGX N2469R wrote:
> I was able to fool RC4 into installing on my office machine by
> telling it to use advances sotrage and selecting a drive
> that had no version of Linux on it.
> 
> Unfortunately, attempting to mount a nfs share fails
> with a message about no such device.
> 
> Broken NFS is a real impediment to testing Linux.

Once again your report is massively lacking in detail. I mount NFS
shares daily. Can you provide details of the server's configuration and
the exact mount command or fstab line you're using?
-- 
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: Grub2 mkconfig

[Tom H]

On Wed, Feb 22, 2012 at 10:06 AM, Timothy Davis  wrote:
>
> Once again grub2 has installed dozens (at least 20) different entries in my
> boot menu. I understand that Fedora is bleeding edge and not for the feint
> of heart
>
> I accept that and have no problem tweaking anything. But come on now! I feel
> like I should just rewrite the mkconfig program.
>
> My system is as follows: 160Gb IDE (Windows 7), 120Gb IDE (stuff ext4),
> 160Gb SATA (swap, f16x64, ubuntu 11.10, slackware 13.37, vector linux 6 kde
> classic, f17 alpha) 250Gb SATA 4Gb boot and the rest is home
>
> I know my setup is not typical and tweaking boot will always happen

What do you expect grub2 to do?

Why don't you maintain a custom file in "/etc/grub.d/" and
delete/move/"chmod -x" the ones that you don't want to be run by
"grub2-mkconfig"?
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Fedora 15 updates-testing report

[updates]

The following Fedora 15 Security updates need testing:

https://admin.fedoraproject.org/updates/FEDORA-2012-1283/drupal6-6.24-1.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-2144/glibc-2.14.1-6
https://admin.fedoraproject.org/updates/FEDORA-2012-0752/jetty-6.1.26-7.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-1250/drupal7-7.12-1.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-1656/apr-1.4.6-1.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-1642/httpd-2.2.22-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-2218/systemtap-1.7-2.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-1677/seamonkey-2.7.1-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-1845/xulrunner-10.0.1-3.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-1838/thunderbird-10.0.1-2.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-1930/libpng-1.2.46-2.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-2008/libpng10-1.0.57-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2011-17233/tor-0.2.1.32-1500.fc15

https://admin.fedoraproject.org/updates/FEDORA-2011-16980/asterisk-1.8.7.2-1.fc15


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


https://admin.fedoraproject.org/updates/FEDORA-2012-2218/systemtap-1.7-2.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-2144/glibc-2.14.1-6

https://admin.fedoraproject.org/updates/FEDORA-2012-2025/pycairo-1.8.10-4.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-1937/createrepo-0.9.9-5.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-1930/libpng-1.2.46-2.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-1835/cups-1.4.8-9.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-1843/mdadm-3.2.3-5.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-1838/thunderbird-10.0.1-2.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-1845/xulrunner-10.0.1-3.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-1697/python-kitchen-1.1.1-1.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-1656/apr-1.4.6-1.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-1642/httpd-2.2.22-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-1587/xfce4-session-4.8.3-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2012-1556/xorg-x11-drv-openchrome-0.2.905-1.fc15

https://admin.fedoraproject.org/updates/FEDORA-2011-13190/phonon-backend-gstreamer-4.5.90-2.fc15,phonon-4.5.57-1.20110914.fc15


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

gfal-1.12.0-3.fc15
gridftp-ifce-2.1.3-4.fc15
primer3-2.3.0-1.fc15
python-rhsm-0.99.4-1.fc15
rubygem-rhc-0.86.7-1.fc15
subscription-manager-0.99.8-1.fc15
systemtap-1.7-2.fc15
zanata-python-client-1.3.4-1.fc15

Details about builds:



 gfal-1.12.0-3.fc15 (FEDORA-2012-2225)
 Grid File access library

Update Information:

f15 update




 gridftp-ifce-2.1.3-4.fc15 (FEDORA-2012-2231)
 GridFTP library for FTS and lcgutil

Update Information:

initial import for f15




 primer3-2.3.0-1.fc15 (FEDORA-2012-2229)
 PCR primer design tool

Update Information:

Update primer3 to 2.3.0

ChangeLog:

* Wed Feb 22 2012 Pierre-Yves Chibon  - 2.3.0-1
- Update to release 2.3.0

References:

  [ 1 ] Bug #788068 - primer3-2.3.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=788068




 python-rhsm-0.99.4-1.fc15 (FEDORA-2012-2232)
 A Python library to communicate with a Red Hat Unified Entitlement Platform

Update Information:

Add support for updating consumer's service level, listing service levels 
available in an organization, and detecting when the consumer has been deleted 
remotely. (GoneException)

ChangeLog:

* Wed Feb 22 2012 Devan Goodwin  0.99.4

Fedora 16 updates-testing report

[updates]

The following Fedora 16 Security updates need testing:

https://admin.fedoraproject.org/updates/FEDORA-2012-0730/jetty-6.1.26-8.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-1268/drupal7-7.12-1.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-1709/apr-1.4.6-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-2213/systemtap-1.7-2.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-1306/drupal6-6.24-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-1934/WebCalendar-1.2.4-3.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-2028/libpng10-1.0.57-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2011-14691/tomcat6-6.0.32-19.fc16


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


https://admin.fedoraproject.org/updates/FEDORA-2012-2213/systemtap-1.7-2.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-2223/openssh-5.8p2-25.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-2083/perl-HTTP-Message-6.03-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-2072/xfce4-settings-4.8.3-4.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-2019/pycairo-1.8.10-4.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-1936/createrepo-0.9.9-11.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-1931/phonon-backend-gstreamer-4.6.0-1.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-1862/mdadm-3.2.3-5.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-1720/gtk3-3.2.3-2.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-1695/iscsi-initiator-utils-6.2.0.872-17.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-1691/GConf2-3.2.3-3.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-1709/apr-1.4.6-1.fc16

https://admin.fedoraproject.org/updates/FEDORA-2012-1589/xfce4-session-4.8.3-1.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-1523/dnsmasq-2.59-4.fc16

https://admin.fedoraproject.org/updates/FEDORA-2011-15301/lxpanel-0.5.8-1.fc16,lxinput-0.3.1-1.fc16,lxsession-edit-0.2.0-1.fc16,lxrandr-0.1.2-1.fc16,lxpolkit-0.1.0-1.fc16,lxterminal-0.1.11-1.fc16,lxshortcut-0.1.2-1.fc16


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

libmpdclient-2.7-1.fc16
libwacom-0.3-1.fc16
mpc-0.22-1.fc16
openssh-5.8p2-25.fc16
primer3-2.3.0-1.fc16
python-auth-credential-0.5-2.fc16
python-messaging-0.5-2.fc16
python-rhsm-0.99.4-1.fc16
python-xhtml2pdf-0.0.3-3.fc16
rubygem-rhc-0.86.7-1.fc16
shotwell-0.10.1-3.fc16
subscription-manager-0.99.8-1.fc16
systemtap-1.7-2.fc16
tomcat-7.0.26-1.fc16
zanata-python-client-1.3.4-1.fc16

Details about builds:



 libmpdclient-2.7-1.fc16 (FEDORA-2012-)
 Library for interfacing Music Player Daemon

Update Information:

"Update to upstream release 2.7"

ChangeLog:

* Tue Feb 21 2012 Jamie Nguyen  - 2.7-1
- update to upstream version 2.7
- remove obsolete BuildRoot tag, %clean section and %defattr




 libwacom-0.3-1.fc16 (FEDORA-2012-2220)
 Tablet Information Client Library

Update Information:

Update to v0.3

ChangeLog:





 mpc-0.22-1.fc16 (FEDORA-2012-2228)
 Command-line client for MPD

Update Information:

"Update to upstream release 0.22"

ChangeLog:

* Tue Feb 21 2012 Jamie Nguyen  - 0.22-1
- update to upstream release 0.22
- remove obsolete BuildRoot tag, %clean section and %defattr




 openssh-5.8p2-25.fc16 (FEDORA-2012-2223)
 An open source implementation of SSH protocol versions 1 and 2

Update Information:

Changes method how to detect sockets for x11 forwarding in ipv6 disabled 
environment.

ChangeLog:

* Wed Feb 22 2012 Petr Lautrbach  5.8p2-25 + 0.9.2-31
- Look for x11 forward sockets with AI_ADDRCONFIG flag 

[Test-Announce] Fedora 17 Alpha is hereby declared GOLD(en mustard color)!

[Robyn Bergeron]

At the F17 Alpha Go/No-Go meeting today, the Fedora 17 Alpha release 
(RC4) was declared GOLD, and ready for shipment on February 28, 2012.


GOLD is the color of mustard, and, as you know, mustard indicates 
progress. A huge thank you to everyone who made this on-time(!!!) Alpha 
release possible. My (occasionally inaccurate) research tells me that 
the last time we shipped an Alpha according to schedule was Fedora 10. 
That is some excellent progress, in my humble opinion :)


Meeting details can be seen here:
Minutes: 
http://meetbot.fedoraproject.org/fedora-meeting-1/2012-02-22/f17_alpha_go_no-go_meeting.2012-02-22-22.00.html
Minutes (text): 
http://meetbot.fedoraproject.org/fedora-meeting-1/2012-02-22/f17_alpha_go_no-go_meeting.2012-02-22-22.00.txt
Log: 
http://meetbot.fedoraproject.org/fedora-meeting-1/2012-02-22/f17_alpha_go_no-go_meeting.2012-02-22-22.00.log.html


Full minutes are posted below.

RELEASE THE HOT DOGS!

-Robyn

=
#fedora-meeting-1: F17 Alpha Go No-Go Meeting
=


Meeting started by rbergeron at 22:00:00 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting-1/2012-02-22/f17_alpha_go_no-go_meeting.2012-02-22-22.00.log.html
.



Meeting summary
---
* Roll Call  (rbergeron, 22:00:19)
  * tflink is here for QA  (rbergeron, 22:00:45)
  * nirik here for fesco/devel in some way; dgilmore here for rel-eng
(rbergeron, 22:01:49)
  * also present: rbergeron for wranglin', brunowolff for awesomeness
and helpfulness  (rbergeron, 22:02:07)

* We are Gathered to Serve a Alpha Taste Test of The Beefy Miracle, and
  determine if we are ready to ship said Holiness.  (rbergeron,
  22:02:43)
  * Looking have the blocker list clear:
http://fedoraproject.org/wiki/Current_Release_Blockers  (rbergeron,
22:03:09)
  * Test Matrices need to be complete  (rbergeron, 22:03:17)
  * LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_17_Alpha_RC4_Install
(rbergeron, 22:03:30)
  * LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_17_Alpha_RC4_Desktop
(rbergeron, 22:03:44)
  * This will determine if release criteria have been met, if we can
ship.  (rbergeron, 22:03:57)

* Release Blocker Review  (rbergeron, 22:05:07)
  * LINK: http://fedoraproject.org/wiki/Current_Release_Blockers
(rbergeron, 22:05:16)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=796261   (tflink,
22:06:58)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=796261   (tflink,
22:07:03)
  * Bootloader not installed? (F17 Alpha RC4)  (tflink, 22:07:18)
  * AGREED: - 796261 - RejectedBlocker - This seems to be an isolated
incident since we have several positive results and only the one
negative  (tflink, 22:10:30)
  * No more remaining blockers for F17 alpha.  (rbergeron, 22:10:44)

* Test Matrices  (rbergeron, 22:12:04)
  * LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_17_Alpha_RC4_Install
(rbergeron, 22:12:19)
  * LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_17_Alpha_RC4_Desktop
(rbergeron, 22:12:22)
  * remaining failures on test cases for alpha are not blockers (related
to creation of usb media; issue is with livecd-tools and not alpha
itself, should have a new build in the next few days)  (rbergeron,
22:13:57)
  * AGREED: Test Matrices are acceptably complete, given livecd-tools
fix coming, things look great and we have many other install methods
working properly.  (rbergeron, 22:16:32)

* The Hot Dog Looks Tasty and Ready. Can we ship F17 Alpha?  (rbergeron,
  22:17:05)
  * AGREED: All criteria for shipping F17 alpha are met; QA, rel-eng,
devel are prepared to ship on tuesday.  (rbergeron, 22:20:45)
  * AGREED: F17 Alpha RC4 is accepted as Alpha!  (rbergeron, 22:21:23)
  * Thanks to everyone for an on-time Alpha release, you rock! RELEASE
THE HOT DOGS!  (rbergeron, 22:22:17)
  * ACTION: rbergeron to send out GOLD announcement and meeting logs
(rbergeron, 22:22:34)

* Any other business?  (rbergeron, 22:22:40)

Meeting ended at 22:24:50 UTC.




Action Items

* rbergeron to send out GOLD announcement and meeting logs




Action Items, by person
---
* rbergeron
  * rbergeron to send out GOLD announcement and meeting logs
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* rbergeron (65)
* tflink (20)
* adamw (14)
* dgilmore (7)
* nirik (6)
* brunowolff (5)
* zodbot (5)
* satellit_ (3)
* jsmith (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


___
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: Installation from USB-written images (3/5): Live.iso + LiveCD-tools

[Adam Williamson]

On Mon, 2012-01-30 at 08:04 -0500, Josef Skladanka wrote:
> This testcase [1] should ensure, that if the user uses LiveCD tools to 
> transfer the Fedora Live.iso to USB stick, the boot process works 'as 
> expected'.
> 
> I propose this as a Alpha verification testcase.

I just realized, this test case is bad. It's basically a duplicate of
QA:Testcase_USB_stick_Live Live-ISO-to-Disk: they both come from the
same reference guide, and the 'livecd-tools' section of that guide is
really just ensuring that livecd-iso-to-disk is installed.

What this test case ought to do is ask the tester to use livecd-creator
to create the USB image. That's the case we're currently missing.
-- 
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: A question about "Software rendering for gnome-shell"

[Michal Jaegermann]

On Wed, Feb 22, 2012 at 08:46:30PM +0100, drago01 wrote:
> On Wed, Feb 22, 2012 at 8:42 PM, Michal Jaegermann  
> wrote:

> > In summary this is deep into a "dancing pig" teritory; no question of
> > dancing well but one marvels that she is dancing at all.
> 
> What is your screen resolution?
1600x1200 on a DVI output.

> Single or dual monitor setup?
Single.  Samsung SyncMaster 213T.  Nothing particularly fancy.

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

Re: test Digest, Vol 96, Issue 80

[Chuck Forsberg WA7KGX N2469R]

Too many different Linux systems on my office machine to add some random
file to each of them.  I'll wait until Anaconda gets over its temper 
tantrum.


I was able to install the 64 bit live Xfce to sda11 and grub2.
No problems seen with grub2.  yum update fails with a flurry
of 404 errors.

On 02/22/2012 11:52 AM, Adam Williamson wrote:

On Wed, 2012-02-22 at 06:55 -0500, Timothy Davis wrote:

 Chuck Forsberg WA7KGX N2469R  wrote:
 >  RC4 installed unhandled exception on simple storage
 devices check.
 >  Unfortunately, upload of traceback failed also.
 >
 >  RC3 did install on a different computer with just
 one hard disk.
 Sounds kind of like
 https://bugzilla.redhat.com/show_bug.cgi?id=791317
 The bug is in POST, so I don't think that the fix has
 made it into
 anaconda yet but hopefully, it will be included soon.
 Tim
 Same here, can't get past "examining storage" on RC4, had to
 "fanagle" the LiveCD to get past it but was able to finally.


The workaround for this bug is to create a /etc/redhat-release file, of
the approximate format "Fedora release 17 (Beefy Miracle)", for any OS
installed on the system which has a /etc/fstab file but
no /etc/redhat-release file. Sounds dumb, but it works. bcl says he'll
try and remember to stick an updates.img in the bug soon for people to
use instead.


--
Chuck Forsberg WA7KGX N2469R c...@omen.com   www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
  Omen Technology Inc  "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231   503-614-0430

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

Re: test Digest, Vol 96, Issue 80

[Adam Williamson]

On Wed, 2012-02-22 at 06:55 -0500, Timothy Davis wrote:
> Chuck Forsberg WA7KGX N2469R  wrote:
> > RC4 installed unhandled exception on simple storage
> devices check.
> > Unfortunately, upload of traceback failed also.
> >
> > RC3 did install on a different computer with just
> one hard disk.
> Sounds kind of like
> https://bugzilla.redhat.com/show_bug.cgi?id=791317
> The bug is in POST, so I don't think that the fix has
> made it into
> anaconda yet but hopefully, it will be included soon.
> Tim
> Same here, can't get past "examining storage" on RC4, had to
> "fanagle" the LiveCD to get past it but was able to finally.
 
The workaround for this bug is to create a /etc/redhat-release file, of
the approximate format "Fedora release 17 (Beefy Miracle)", for any OS
installed on the system which has a /etc/fstab file but
no /etc/redhat-release file. Sounds dumb, but it works. bcl says he'll
try and remember to stick an updates.img in the bug soon for people to
use instead.
-- 
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: A question about "Software rendering for gnome-shell"

[drago01]

On Wed, Feb 22, 2012 at 8:42 PM, Michal Jaegermann  wrote:
> On Wed, Feb 22, 2012 at 09:40:18AM -0500, Adam Jackson wrote:
>> On Tue, 2012-02-21 at 16:35 -0700, Michal Jaegermann wrote:
>>
>> > This particular one is a 64-bit (albeit quite old) processor:
>> >
>> > vendor_id   : AuthenticAMD
>> > cpu family  : 15
>> > model               : 5
>> > model name  : AMD Opteron(tm) Processor 142
>> > stepping    : 1
>> > cpu MHz             : 1600.062
>> > cache size  : 1024 KB
>> >
>> > on a board with 2GB of a physical memory.  I know some machines around,
>> > and doing useful job, where this is a quite powerhouse in a comparison.
>> > When forced with LIBGL_ALWAYS_SOFTWARE=1 gnome shell was taking all the
>> > time between 94% and 96% of CPU and a response latency for a keystroke
>> > or a mouse movement was in a order of few seconds.
>>
>> Shot in the dark here, but with the LIBGL_ALWAYS_SOFTWARE=1 force in
>> place, try an xorg.conf that looks like this:
>>
>> Section "Device"
>>     Identifier "radeon"
>>     Driver "radeon"
>>     Option "NoAccel"
>> EndSection
>
> First of all results do not seem to depend at all if with
> gnome-session-3.3.5-2.fc17.jx I am using mesa-...-8.0.1-1.fc17.jx
> or mesa-...-8.0.1-1.fc18 drivers and libraries.  If anything a CPU
> usage and latencies seem to be a tad higher with "8.0.1-1.fc17.jx"
> but differences are so minimal that this is not likely significant.
>
> Dropping such config fragment as above into /etc/X11/xorg.conf.d does
> change the situation somewhat.  Starting with
> /usr/libexec/gnome-session-check-accelerated-helper not segfaulting
> anymore.  As a result after a very long wait a "standard" gnome shell
> session does show up without a need to force it with
> LIBGL_ALWAYS_SOFTWARE=1.  A gnome-shell CPU usage also goes down from
> 96% to something like 85% (after a longer period of a complete
> inactivity it may even drop to something like 20% but a single keystroke
> somewhere sends this immediately back to the previous levels).  Input
> latencies are somewhat decreased, so you will likely catch yourself
> before pushing that power switch to recover a "crashed" machine, but are
> still way beyond what can be remotely acceptable.
>
> If booting 3.3.0-0.rc4.git1.4.fc17.x86_64 kernel (the latest one for F17
> from koji) instead 3.3.0-0.rc4.git0.1.fc18.x86_64 then a CPU usage maybe
> further drops to 82-83%, which is hard to tell as that may depend to
> is happening on a screen even if I tried to behave the same way in all
> cases, but an overall "feel" does not really change.
>
> In summary this is deep into a "dancing pig" teritory; no question of
> dancing well but one marvels that she is dancing at all.
>
>> That kind of latency just doesn't make sense unless EXA is trying to
>> keep pixmaps in vram, which will be a net loss with llvmpipe since we'll
>> need to copy them back out of vram all the time, which is unbearable.
>
> I am afraid that I am not qualified to sensibly discuss underlying
> mechanisms.  I can only report what I see.  In this thread
> mwes...@verizon.net wrote "the processor gets pegged at 100%
> continuously and it's not usable".  I am not sure what was the hardware.
> I wonder if turning off acceleration changes anything to him.

What is your screen resolution?
Single or dual monitor setup?
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: A question about "Software rendering for gnome-shell"

[Michal Jaegermann]

On Wed, Feb 22, 2012 at 09:40:18AM -0500, Adam Jackson wrote:
> On Tue, 2012-02-21 at 16:35 -0700, Michal Jaegermann wrote:
> 
> > This particular one is a 64-bit (albeit quite old) processor:
> > 
> > vendor_id   : AuthenticAMD
> > cpu family  : 15
> > model   : 5
> > model name  : AMD Opteron(tm) Processor 142
> > stepping: 1
> > cpu MHz : 1600.062
> > cache size  : 1024 KB
> > 
> > on a board with 2GB of a physical memory.  I know some machines around,
> > and doing useful job, where this is a quite powerhouse in a comparison.
> > When forced with LIBGL_ALWAYS_SOFTWARE=1 gnome shell was taking all the
> > time between 94% and 96% of CPU and a response latency for a keystroke
> > or a mouse movement was in a order of few seconds.
> 
> Shot in the dark here, but with the LIBGL_ALWAYS_SOFTWARE=1 force in
> place, try an xorg.conf that looks like this:
> 
> Section "Device"
> Identifier "radeon"
> Driver "radeon"
> Option "NoAccel"
> EndSection

First of all results do not seem to depend at all if with
gnome-session-3.3.5-2.fc17.jx I am using mesa-...-8.0.1-1.fc17.jx
or mesa-...-8.0.1-1.fc18 drivers and libraries.  If anything a CPU
usage and latencies seem to be a tad higher with "8.0.1-1.fc17.jx"
but differences are so minimal that this is not likely significant.

Dropping such config fragment as above into /etc/X11/xorg.conf.d does
change the situation somewhat.  Starting with
/usr/libexec/gnome-session-check-accelerated-helper not segfaulting
anymore.  As a result after a very long wait a "standard" gnome shell
session does show up without a need to force it with
LIBGL_ALWAYS_SOFTWARE=1.  A gnome-shell CPU usage also goes down from
96% to something like 85% (after a longer period of a complete
inactivity it may even drop to something like 20% but a single keystroke
somewhere sends this immediately back to the previous levels).  Input
latencies are somewhat decreased, so you will likely catch yourself
before pushing that power switch to recover a "crashed" machine, but are
still way beyond what can be remotely acceptable.

If booting 3.3.0-0.rc4.git1.4.fc17.x86_64 kernel (the latest one for F17
from koji) instead 3.3.0-0.rc4.git0.1.fc18.x86_64 then a CPU usage maybe
further drops to 82-83%, which is hard to tell as that may depend to
is happening on a screen even if I tried to behave the same way in all
cases, but an overall "feel" does not really change.

In summary this is deep into a "dancing pig" teritory; no question of
dancing well but one marvels that she is dancing at all.

> That kind of latency just doesn't make sense unless EXA is trying to
> keep pixmaps in vram, which will be a net loss with llvmpipe since we'll
> need to copy them back out of vram all the time, which is unbearable.

I am afraid that I am not qualified to sensibly discuss underlying
mechanisms.  I can only report what I see.  In this thread
mwes...@verizon.net wrote "the processor gets pegged at 100%
continuously and it's not usable".  I am not sure what was the hardware.
I wonder if turning off acceleration changes anything to him.

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

Fedora 17 updates-testing report

[updates]

The following Fedora 17 Security updates need testing:

https://admin.fedoraproject.org/updates/FEDORA-2012-2123/glibc-2.15-23.fc17
https://admin.fedoraproject.org/updates/FEDORA-2012-2187/krb5-1.10-4.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-1800/xulrunner-10.0.1-3.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-1794/thunderbird-10.0.1-2.fc17
https://admin.fedoraproject.org/updates/FEDORA-2012-1892/libpng-1.5.8-2.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-1898/WebCalendar-1.2.4-3.fc17

https://admin.fedoraproject.org/updates/FEDORA-2012-2003/libpng10-1.0.57-1.fc17


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

apache-commons-lang-2.6-6.fc17
bacula-5.2.6-1.fc17
bacula-docs-5.2.6-1.fc17
colord-0.1.17-1.fc17
corosync-1.99.5-1.fc17
evince-3.3.90-1.fc17
evolution-3.3.90-1.fc17
evolution-couchdb-0.5.91-10.fc17
evolution-data-server-3.3.90-2.fc17
evolution-ews-3.3.90-1.fc17
evolution-exchange-3.3.5-2.fc17
evolution-mapi-3.3.90-1.fc17
evolution-rss-0.3.90-7.20120221git.fc17
kde-workspace-4.8.0-10.fc17
libdrm-2.4.31-3.fc17
lohit-telugu-fonts-2.5.0-3.fc17
mail-notification-5.4-52.fc17
maven-anno-plugin-1.4.1-2.fc17
openssh-5.9p1-19.fc17
poppler-0.18.4-1.fc17
primer3-2.3.0-1.fc17
python-auth-credential-0.5-2.fc17
python-flexmock-0.9.2-1.fc17
python-messaging-0.5-2.fc17
rubygem-net-ldap-0.2.2-2.fc17
share-like-connect-0.2-1.fc17
sssd-1.8.0-5.fc17.beta3
tracker-0.12.10-1.fc17
xscope-1.3.1-1.fc17

Details about builds:



 apache-commons-lang-2.6-6.fc17 (FEDORA-2012-2195)
 Provides a host of helper utilities for the java.lang API

Update Information:

Fix JDK 1.7 compatibility

ChangeLog:

* Wed Feb 22 2012 Stanislav Ochotnicky  - 2.6-6
- Add backported fix for JDK 1.7
* Thu Jan 12 2012 Fedora Release Engineering  
- 2.6-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild




 bacula-5.2.6-1.fc17 (FEDORA-2012-2202)
 Cross platform network backup for Linux, Unix, Mac and Windows

Update Information:

Update to 5.2.6 to solve various bacula bugs.

ChangeLog:

* Wed Feb 22 2012 Simone Caronni  - 5.2.6-1
- Update to 5.2.6.




 bacula-docs-5.2.6-1.fc17 (FEDORA-2012-2202)
 Bacula documentation

Update Information:

Update to 5.2.6 to solve various bacula bugs.

ChangeLog:

* Wed Feb 22 2012 Simone Caronni  - 5.2.6-1
- Update to 5.2.6.




 colord-0.1.17-1.fc17 (FEDORA-2012-2208)
 Color daemon

Update Information:

- New upstream version
- Add an LED sample type
- Add PrivateNetwork and PrivateTmp to the systemd service file
- Fix InstallSystemWide() when running as the colord user

ChangeLog:

* Wed Feb 22 2012 Richard Hughes  0.1.17-1
- New upstream version
- Add an LED sample type
- Add PrivateNetwork and PrivateTmp to the systemd service file
- Fix InstallSystemWide() when running as the colord user




 corosync-1.99.5-1.fc17 (FEDORA-2012-2212)
 The Corosync Cluster Engine and Application Programming Interfaces

Update Information:

This update improves stability and addresses several bugs

ChangeLog:

* Wed Feb 22 2012 Jan Friesse  - 1.99.5-1
- New upstream release




 evince-3.3.90-1.fc17 (FEDORA-2012-2205)
 Document viewer

Re: Grub2 mkconfig

[T.C. Hollingsworth]

On Wed, Feb 22, 2012 at 8:38 AM, Timothy Davis  wrote:
> On Wed, 2012-02-22 at 08:22 -0700, T.C. Hollingsworth wrote:
>> On Wed, Feb 22, 2012 at 8:06 AM, Timothy Davis  wrote:
>> > Once again grub2 has installed dozens (at least 20) different entries in my
>> > boot menu. I understand that Fedora is bleeding edge and not for the feint
>> > of heart
>> > I accept that and have no problem tweaking anything. But come on now! I 
>> > feel
>> > like I should just rewrite the mkconfig program.
>> > My system is as follows: 160Gb IDE (Windows 7), 120Gb IDE (stuff ext4),
>> > 160Gb SATA (swap, f16x64, ubuntu 11.10, slackware 13.37, vector linux 6 kde
>> > classic, f17 alpha) 250Gb SATA 4Gb boot and the rest is home
>> > I know my setup is not typical and tweaking boot will always happen
>>
>> Is it just the (recovery mode entries bothering you?  Add
>> 'GRUB_DISABLE_LINUX_RECOVERY=true' to /etc/default/grub kill those.
>>
>> -T.C.
>>
> It's not the recovery mode entry that bothers me, but the fact that for
> all of the kernels in my boot parttion gets assigned to F17 or what
> every the last distro installed. Maybe the mkconfig program isn't samrt
> enought or maybe I should go ahead and write my own.

You share a boot partition between all the distros?  Yeah,
grub2-mkconfig as it stands really has no way of figuring out which
one's which in that case.

You don't strictly have to edit/rewrite grub2-mkconfig, as long as
Fedora is the only distro messing with GRUB.  Fedora does not rerun
grub2-mkconfig on update, the grub2.cfg is patched by grubby.  If you
go in and fix /boot/grub2/grub.cfg, it should stay.  (This is *not*
the case for most other distros, however.)

If you do want to hack on grub2-mkconfig, it runs scripts located in
/etc/grub.d/ to make up the configuration.  See /etc/grub.d/README for
details.  Note that changes there could get clobbered on grub2
updates, so be careful.

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

Re: Grub2 mkconfig

[Timothy Davis]

On Wed, 2012-02-22 at 08:22 -0700, T.C. Hollingsworth wrote:
> On Wed, Feb 22, 2012 at 8:06 AM, Timothy Davis  wrote:
> > Once again grub2 has installed dozens (at least 20) different entries in my
> > boot menu. I understand that Fedora is bleeding edge and not for the feint
> > of heart
> > I accept that and have no problem tweaking anything. But come on now! I feel
> > like I should just rewrite the mkconfig program.
> > My system is as follows: 160Gb IDE (Windows 7), 120Gb IDE (stuff ext4),
> > 160Gb SATA (swap, f16x64, ubuntu 11.10, slackware 13.37, vector linux 6 kde
> > classic, f17 alpha) 250Gb SATA 4Gb boot and the rest is home
> > I know my setup is not typical and tweaking boot will always happen
> 
> Is it just the (recovery mode entries bothering you?  Add
> 'GRUB_DISABLE_LINUX_RECOVERY=true' to /etc/default/grub kill those.
> 
> -T.C.
> 
It's not the recovery mode entry that bothers me, but the fact that for
all of the kernels in my boot parttion gets assigned to F17 or what
every the last distro installed. Maybe the mkconfig program isn't samrt
enought or maybe I should go ahead and write my own. 

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

Re: Grub2 mkconfig

[Clyde E. Kunkel]

On 02/22/2012 10:06 AM, Timothy Davis wrote:

Once again grub2 has installed dozens (at least 20) different entries in
my boot menu. I understand that Fedora is bleeding edge and not for the
feint of heart
I accept that and have no problem tweaking anything. But come on now! I
feel like I should just rewrite the mkconfig program.
My system is as follows: 160Gb IDE (Windows 7), 120Gb IDE (stuff ext4),
160Gb SATA (swap, f16x64, ubuntu 11.10, slackware 13.37, vector linux 6
kde classic, f17 alpha) 250Gb SATA 4Gb boot and the rest is home
I know my setup is not typical and tweaking boot will always happen


--
Fedora, Ubuntu and Slackware user
Linux counter #386175






A NO_OS_Prober cmd line parm would be useful in anaconda or an option in 
the install dialogue to skip os probing.  That said, it isn't too much 
trouble to add GRUB_DISABLE_OS_PROBER=true to /etc/default/grub.


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

Re: Grub2 mkconfig

[T.C. Hollingsworth]

On Wed, Feb 22, 2012 at 8:06 AM, Timothy Davis  wrote:
> Once again grub2 has installed dozens (at least 20) different entries in my
> boot menu. I understand that Fedora is bleeding edge and not for the feint
> of heart
> I accept that and have no problem tweaking anything. But come on now! I feel
> like I should just rewrite the mkconfig program.
> My system is as follows: 160Gb IDE (Windows 7), 120Gb IDE (stuff ext4),
> 160Gb SATA (swap, f16x64, ubuntu 11.10, slackware 13.37, vector linux 6 kde
> classic, f17 alpha) 250Gb SATA 4Gb boot and the rest is home
> I know my setup is not typical and tweaking boot will always happen

Is it just the (recovery mode entries bothering you?  Add
'GRUB_DISABLE_LINUX_RECOVERY=true' to /etc/default/grub kill those.

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

Grub2 mkconfig

[Timothy Davis]

Once again grub2 has installed dozens (at least 20) different entries in my
boot menu. I understand that Fedora is bleeding edge and not for the feint
of heart
I accept that and have no problem tweaking anything. But come on now! I
feel like I should just rewrite the mkconfig program.
My system is as follows: 160Gb IDE (Windows 7), 120Gb IDE (stuff ext4),
160Gb SATA (swap, f16x64, ubuntu 11.10, slackware 13.37, vector linux 6 kde
classic, f17 alpha) 250Gb SATA 4Gb boot and the rest is home
I know my setup is not typical and tweaking boot will always happen


-- 
Fedora, Ubuntu and Slackware user
Linux counter #386175
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: A question about "Software rendering for gnome-shell"

[Adam Jackson]

On Tue, 2012-02-21 at 16:35 -0700, Michal Jaegermann wrote:

> This particular one is a 64-bit (albeit quite old) processor:
> 
> vendor_id : AuthenticAMD
> cpu family: 15
> model : 5
> model name: AMD Opteron(tm) Processor 142
> stepping  : 1
> cpu MHz   : 1600.062
> cache size: 1024 KB
> 
> on a board with 2GB of a physical memory.  I know some machines around,
> and doing useful job, where this is a quite powerhouse in a comparison.
> When forced with LIBGL_ALWAYS_SOFTWARE=1 gnome shell was taking all the
> time between 94% and 96% of CPU and a response latency for a keystroke
> or a mouse movement was in a order of few seconds.  My guess is that
> more of CPU would be grabbed if only it would be available.  At the
> first moment I thought that the whole thing just locked up and only
> after some delay I realized that I was mistaken.

Shot in the dark here, but with the LIBGL_ALWAYS_SOFTWARE=1 force in
place, try an xorg.conf that looks like this:

Section "Device"
Identifier "radeon"
Driver "radeon"
Option "NoAccel"
EndSection

That kind of latency just doesn't make sense unless EXA is trying to
keep pixmaps in vram, which will be a net loss with llvmpipe since we'll
need to copy them back out of vram all the time, which is unbearable.
I've run software shell on a slower [1] machine and things were almost
acceptable, but it was an Intel GPU which means the host/video ram
distinction is basically nil.

[1] - Well, synthetically slower, by clamping to the slowest P state.

- ajax


signature.asc
Description: This is a digitally signed message part
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

unable to run tests requiring "updates=http://jlaska.fedorapeople.org/updates/traceback.img" option

[Andre Robatino]

Kamil Paral  redhat.com> writes:

> > QA:Testcase_Anaconda_save_traceback_to_remote_system
> > QA:Testcase_Anaconda_save_traceback_to_bugzilla (Alpha)
> > QA:Testcase_Anaconda_save_traceback_to_disk (Alpha)
> > QA:Testcase_Anaconda_traceback_debug_mode
> 
> I have tried Alpha RC4 (anaconda 17.11), it's there. I'll update the test
cases now.

I hadn't checked past the first anaconda screen (where the traceback appeared
previously). Going through the first few screens as indicated in the new test
cases, I see it now. It might have been in RC3 as well. Anyway, I verified that
the last 3 tests work as advertised.
QA:Testcase_Anaconda_save_traceback_to_remote_system did not work, using an URL
of the form "scp://andre:mypassword@192.168.1.2:/tmp" (which worked previously).
The installer claims it wrote the file successfully, and tells you the exact
name of the file, but it never actually appears on the remote system.




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

Re: test Digest, Vol 96, Issue 80

[Timothy Davis]

>
> Chuck Forsberg WA7KGX N2469R  wrote:
> > RC4 installed unhandled exception on simple storage devices check.
> > Unfortunately, upload of traceback failed also.
> >
> > RC3 did install on a different computer with just one hard disk.
> Sounds kind of like https://bugzilla.redhat.com/show_bug.cgi?id=791317
> The bug is in POST, so I don't think that the fix has made it into
> anaconda yet but hopefully, it will be included soon.
> Tim
>
> Same here, can't get past "examining storage" on RC4, had to "fanagle" the
> LiveCD to get past it but was able to finally.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[Fedora QA] #282: Test Day proposal - ABRT & deduplication service

[Fedora QA]

#282: Test Day proposal - ABRT & deduplication service
--+
 Reporter:  rmarko|   Owner:
 Type:  task  |  Status:  new
 Priority:  major |   Milestone:  Fedora 17
Component:  Test Day  | Version:
 Keywords:|  Blocked By:
 Blocking:|
--+
 We propose a test day for ABRT and deduplication infrastructure for
 2012-04-19. It will be similar to the previous one with focus on
 deduplication service. We probably won't need any assistance from qa team.

 Feature page:
 http://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication

 Thanks!

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

F-17 Branched report: 20120222 changes

[Branched Report]

Compose started at Wed Feb 22 08:15:07 UTC 2012

Broken deps for x86_64
--
[HippoDraw]
HippoDraw-devel-1.21.3-2.fc17.i686 requires python-numarray
HippoDraw-devel-1.21.3-2.fc17.x86_64 requires python-numarray
HippoDraw-python-1.21.3-2.fc17.x86_64 requires python-numarray
[Pound]
Pound-2.6-2.fc17.x86_64 requires libtcmalloc.so.0()(64bit)
[aeolus-conductor]
aeolus-conductor-0.4.0-2.fc17.noarch requires ruby(abi) = 0:1.8
[aeolus-configserver]
aeolus-configserver-0.4.1-5.fc17.noarch requires ruby-nokogiri
[alexandria]
alexandria-0.6.8-2.fc17.1.noarch requires ruby(abi) = 0:1.8
[asterisk]
asterisk-ais-10.0.0-1.fc17.1.x86_64 requires 
libSaEvt.so.3(OPENAIS_EVT_B.01.01)(64bit)
asterisk-ais-10.0.0-1.fc17.1.x86_64 requires libSaEvt.so.3()(64bit)
asterisk-ais-10.0.0-1.fc17.1.x86_64 requires 
libSaClm.so.3(OPENAIS_CLM_B.01.01)(64bit)
asterisk-ais-10.0.0-1.fc17.1.x86_64 requires libSaClm.so.3()(64bit)
[aunit]
aunit-2010-3.fc16.i686 requires libgnat-4.6.so
aunit-2010-3.fc16.x86_64 requires libgnat-4.6.so()(64bit)
[banshee]
banshee-meego-2.2.1-3.fc17.x86_64 requires mutter-meego
[catfish]
catfish-engines-0.3.2-4.fc17.1.noarch requires pinot
[coccinella]
coccinella-0.96.20-3.fc17.noarch requires memchan
[comoonics-cdsl-py]
comoonics-cdsl-py-0.2-19.noarch requires comoonics-base-py
[comoonics-cluster-py]
comoonics-cluster-py-0.1-25.noarch requires comoonics-base-py
[contextkit]
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]
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)
[curry]
curry-0.9.11-7.fc12.x86_64 requires libgmp.so.3()(64bit)
[dh-make]
dh-make-0.55-4.fc17.noarch requires debhelper
[dlm]
dlm-3.99.0-5.fc17.x86_64 requires libcfg.so.4(COROSYNC_CFG_0.82)(64bit)
dlm-3.99.0-5.fc17.x86_64 requires libcfg.so.4()(64bit)
[elice]
elice-0.323-6.fc17.x86_64 requires ruby(abi) = 0:1.8
[eruby]
eruby-1.0.5-17.fc17.x86_64 requires libruby.so.1.8()(64bit)
eruby-libs-1.0.5-17.fc17.i686 requires ruby(abi) = 0:1.8
eruby-libs-1.0.5-17.fc17.i686 requires libruby.so.1.8
eruby-libs-1.0.5-17.fc17.x86_64 requires ruby(abi) = 0:1.8
eruby-libs-1.0.5-17.fc17.x86_64 requires libruby.so.1.8()(64bit)
[fantasdic]
fantasdic-1.0-0.9.beta7.fc17.noarch requires ruby(gettext-package)
[gcc-python-plugin]
gcc-python2-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 
0:4.7.0-0.10.fc17
gcc-python2-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17
gcc-python3-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 
0:4.7.0-0.10.fc17
gcc-python3-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17
[gdal]
gdal-ruby-1.7.3-12.fc17.x86_64 requires libruby.so.1.8()(64bit)
[gearmand]
gearmand-0.23-2.fc17.x86_64 requires libtcmalloc.so.0()(64bit)
gearmand-0.23-2.fc17.x86_64 requires 
libboost_program_options-mt.so.1.47.0()(64bit)
[genius]
genius-1.0.12-2.fc15.x86_64 requires libgmp.so.3()(64bit)
gnome-genius-1.0.12-2.fc15.x86_64 requires libgmp.so.3()(64bit)
[geos]
geos-ruby-3.3.2-1.fc17.x86_64 requires libruby.so.1.8()(64bit)
[gnatcoll]
gnatcoll-2011-6.fc17.i686 requires libgnat-4.6.so
gnatcoll-2011-6.fc17.i686 requires libgnarl-4.6.so
gnatcoll-2011-6.fc17.x86_64 requires libgnat-4.6.so()(64bit)
gnatcoll-2011-6.fc17.x86_64 requires libgnarl-4.6.so()(64bit)
[gnome-phone-manager]
gnome-phone-manager-0.66-9.fc17.x86_64 requires 
libgnome-bluetooth.so.9()(64bit)
[gnome-user-share]
gnome-user-share-3.0.1-3.fc17.x86_64 requires 
libgnome-bluetooth.so.9()(64bit)
[gnucash]
gnucash-2.4.8-1.fc17.x86_64 requires libgoffice-0.8.so.8()(64bit)
[gorm]
gorm-1.2.13-0.2.20110331.fc17.i686 requires libobjc.so.3
gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-gui.so.0.20
gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-base.so.1.23
gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libobjc.so.3()(64bit)
gorm-1.2.13-0.2.20110331.fc17.x86_64 requires 
libgnustep-gui.so.0.20()(64bit)
gorm-1.2.13-0.2.20110331.fc17.x86_64 requires 
libgnustep-base.so.1.23()(64bit)
[gphpedit]
gphpedit-0.9.95-0.2.20090209snap.fc15.x86_64 requires 
libgtkhtml-2.so.0()(64bit)
[gpsdrive]
gpsdrive-2.11-10.fc17.x86_64 requires libmapnik.so.0.7()(64bit)
gpsdrive-2.11-10.fc17.x86_64 requires 
libboost_thread-mt.so.1.47.0()(64bit)
gpsdrive-2.11-10.fc17.x86_64 requires 
libboost_system-mt.so.1.47.0()(64bit)
gpsdrive-2.11-10.fc17.x86_64 requires 
libboost_

Re: unable to run tests requiring "updates=http://jlaska.fedorapeople.org/updates/traceback.img" option

[Kamil Paral]

> QA:Testcase_Anaconda_save_traceback_to_remote_system
> QA:Testcase_Anaconda_save_traceback_to_bugzilla (Alpha)
> QA:Testcase_Anaconda_save_traceback_to_disk (Alpha)
> QA:Testcase_Anaconda_traceback_debug_mode

Test cases updated. However, for "save_traceback_to_bugzilla" we used to have 
the option to randomize traceback in order to force creation of a new bug 
(compare wiki page history). That is no longer available with the new method, 
so for every anaconda release we will probably have just one new bug and the 
rest will be duplicates. If we decide we need the previous behavior (randomize 
traceback), I can talk to mgracik again and ask him to extend current 
functionality. I won't do that if we don't see it as so important.

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

Re: unable to run tests requiring "updates=http://jlaska.fedorapeople.org/updates/traceback.img" option

[Kamil Paral]

> > The new feature is implemented and should be part of the next
> > anaconda release
> (17.9 probably). We just use
> > 'traceback' boot option. Once a new compose with the new anaconda
> > is ready,
> I'll re-write the test cases.
> 
> The 'traceback' boot option does NOT appear to be implemented in 17
> Alpha RC3,
> which includes anaconda 17.10. This means that the 4 tests, two of
> which are
> marked as Alpha-level, still cannot be done. I tried both 'traceback'
> and
> 'inst.traceback'. (BTW, the inst.* options are still not implemented,
> although I
> get messages during installation saying to use them in the future as
> the
> non-inst.* options are deprecated.)
> 
> QA:Testcase_Anaconda_save_traceback_to_remote_system
> QA:Testcase_Anaconda_save_traceback_to_bugzilla (Alpha)
> QA:Testcase_Anaconda_save_traceback_to_disk (Alpha)
> QA:Testcase_Anaconda_traceback_debug_mode

I have tried Alpha RC4 (anaconda 17.11), it's there. I'll update the test cases 
now.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test