March 2012 - test - Fedora Mailing-Lists

by Adam Williamson

Hey, folks. So I've been doing the TC / RC requests for a while, and James did them before that. It occurred to me that while it's theoretically 'obvious' how this happens, and mostly defined by the release validation process, in practice it's probably worth having an explicit SOP to describe how to do this, for raptor-proofing purposes. I wrote a kind of proto-SOP to the list back last year: https://lists.fedoraproject.org/pipermail/test/2011-November/104402.html so I just expanded that out into this draft formal SOP: https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_SOP_compose_request It features me being my typical wordy self, but I think it's not *too* long or eye-glazey and I hope it pretty comprehensively explains the hows and whys of doing a compose request. Please review it and provide any feedback that occurs to you - factual, linguistical or otherwise. Thanks! Note I tried to follow the vague Fedora convention with regards to 'must' and 'should' - 'must' is used specifically to mean 'this absolutely must happen', 'should' is used to mean 'you really ought to do this but it's possible that in some weird cases there might be a reason not to, I guess, and the world doesn't automatically end if you don't'. I think it'd be a neat raptor-proofing test for someone else to do the F17 Beta or Final compose requests, maybe. Anyone feel like they want to get involved with that? James, CCing you just in case you have any insights into the process which have been lost on my bumbling watch. thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

12 years

8
22
0 / 0

[Fedora QA] #271: L10N and i18n Test Day

by fedora-badges

#271: L10N and i18n Test Day ----------------------+------------------------ Reporter: aalam | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 17 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ for localized and i18n testing, need two test days (including anaconda/installation) testing. Fedora 16 has test week. We can contiune with test week [https://fedorahosted.org/fedora-qa/ticket/222], After Software Translation Deadline (2012-03-13), it will be helpful for testing desktop. Proposed Days:2012-03-22 or 2012-03-29 Some i18n Feaure in Fedora 17: http://fedoraproject.org/wiki/Features/Inscript2_Keymaps https://fedoraproject.org/wiki/I18N/Meetings/2011-12-22 -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/271> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

12 years

1
22
0 / 0

Weird F17 effect: New gdm-3.4.0.1 presents mysql server account on the login screen

by Joachim Backes

Anybody sees this too: After applying all F17 updates (including gnome-3.4... packages), the GDM login window presents the mysql server account on the login screen. Why that? Kind regards -- Joachim Backes <joachim.backes(a)rhrk.uni-kl.de> http://www.rhrk.uni-kl.de/~backes

12 years

7
17
0 / 0

F17: restarting gnome-shell produces a mangled desktop

by Joachim Backes

Hi, after having updated to gnome-shell-3.3.92-1.fc17.x86_64 (included in the todays updates) and restarting gnome-shell with alt+f2->r, the desktop is mangled: a second nautilus desktop window is appears on the screen, shifted from the left/top corner by about 1 inch. Anybody sees this too? Kind regards Joachim Backes <joachim.backes(a)rhrk.uni-kl.de> http://www.rhrk.uni-kl.de/~backes

12 years, 1 month

3
4
0 / 0

[Test-Announce] 2012-03-30 @ 17:00 UTC - F17 Beta Blocker Bug Review #4

by Tim Flink

# F17 Beta Blocker Review meeting #4 # Date: 2012-03-30 # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT) # Location: #fedora-bugzappers on irc.freenode.net Since F17 beta has officially slipped a week, we're having another beta blocker bug review meeting! The fourth (and hopefully final) F17 beta blocker bug review meeting will be this Friday at 17:00 UTC in #fedora-bugzappers. We'll be running through the beta blockers and nice-to-haves. An updated list of blocker bugs is available at: https://fedoraproject.org/wiki/Current_Release_Blockers. We'll be reviewing the bugs to determine ... 1. Whether they meet the beta release criteria [1] and should stay on the list 2. Whether they are getting the attention they need [1] http://fedoraproject.org/wiki/Fedora_17_Beta_Release_Criteria For guidance on Blocker and Nice-to-have (NTH) bugs, please refer to - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_nth_bug_process For the blocker review meeting protocol, see - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Tim _______________________________________________ test-announce mailing list test-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce

12 years, 1 month

2
2
0 / 0

New criterion for updates.img using

by Petr Schindler

I propose new beta criterion: "The installer must be able to use updates.img obtained by any supported way" I think, that this should be at criteria too. There are test cases which uses this feature - [1], [2] [1] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_insta... [2] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_local...

12 years, 1 month

3
8
0 / 0

Some errors from package install in F17

by stan

In general, install went very well. Of the several thousand packages I installed, these were the only errors. I was really impressed. These packages had dependency errors during dependency resolution: Packages skipped because of dependency problems: bootconf-1.4-5.fc17.noarch from fedora bootconf-gui-1.4-5.fc17.noarch from fedora 1:emacs-24.0.94-3.fc17.x86_64 from updates-testing emacs-a2ps-4.14-14.fc17.x86_64 from fedora emacs-a2ps-el-4.14-14.fc17.x86_64 from fedora emacs-anthy-9100h-17.fc17.noarch from fedora emacs-apel-10.8-3.fc17.noarch from fedora emacs-auctex-11.86-7.fc17.noarch from fedora emacs-auctex-el-11.86-7.fc17.noarch from fedora 1:emacs-bbdb-2.35-6.fc17.noarch from fedora 1:emacs-bbdb-el-2.35-6.fc17.noarch from fedora emacs-bigloo-3.7a-3.fc17.noarch from fedora emacs-cdargs-1.35-8.fc17.noarch from fedora emacs-common-tuareg-2.0.4-2.fc17.noarch from fedora emacs-ebib-1.8.0-3.fc17.noarch from fedora emacs-ebib-el-1.8.0-3.fc17.noarch from fedora emacs-ess-5.14-2.fc17.noarch from fedora emacs-ess-el-5.14-2.fc17.noarch from fedora emacs-gambit-4.6.3-1.fc17.noarch from fedora emacs-git-1.7.9.3-1.fc17.noarch from fedora emacs-gnu-smalltalk-3.2.4-2.fc17.2.noarch from fedora emacs-gnuplot-4.4.4-3.fc17.noarch from fedora emacs-gnuplot-el-4.4.4-3.fc17.noarch from fedora emacs-gtypist-2.9-2.fc17.x86_64 from fedora emacs-lua-20071122-9.fc17.noarch from fedora emacs-lua-el-20071122-9.fc17.noarch from fedora emacs-mew-6.4-3.fc17.x86_64 from fedora emacs-muse-3.20-4.fc17.noarch from fedora emacs-muse-el-3.20-4.fc17.noarch from fedora emacs-pyrex-0.9.9-4.fc17.noarch from fedora emacs-tuareg-2.0.4-2.fc17.noarch from fedora emacs-tuareg-el-2.0.4-2.fc17.noarch from fedora emacs-uim-1.7.3-1.fc17.x86_64 from fedora emacs-vala-0.15.2-1.fc17.noarch from updates-testing emacs-verilog-mode-531-3.fc17.noarch from fedora emacs-vm-8.1.1-4.fc17.x86_64 from fedora emacs-vm-el-8.1.1-4.fc17.x86_64 from fedora emacs-w3m-1.4.435-0.2.20110225cvs.fc17.noarch from fedora emacs-w3m-el-1.4.435-0.2.20110225cvs.fc17.noarch from fedora emacspeak-29.0-5.fc17.noarch from fedora eruby-1.0.5-17.fc17.x86_64 from fedora eruby-devel-1.0.5-17.fc17.x86_64 from fedora eruby-libs-1.0.5-17.fc17.x86_64 from fedora flim-1.14.9-4.fc17.noarch from fedora genius-1.0.12-2.fc15.x86_64 from fedora genius-devel-1.0.12-2.fc15.x86_64 from fedora git-all-1.7.9.3-1.fc17.noarch from fedora glibc-2.15-28.fc17.i686 from updates-testing gnome-genius-1.0.12-2.fc15.x86_64 from fedora gnome-user-share-3.0.1-3.fc17.x86_64 from fedora gnutls-2.12.17-1.fc17.i686 from fedora kazehakase-ruby-0.5.8-11.svn3873_trunk.fc17.x86_64 from fedora libgcc-4.7.0-1.fc17.i686 from updates-testing libgcrypt-1.5.0-3.fc17.i686 from fedora libgpg-error-1.10-2.fc17.i686 from fedora libopenvrml-0.18.8-2.fc16.x86_64 from fedora libopenvrml-devel-0.18.8-2.fc16.x86_64 from fedora libopenvrml-doc-0.18.8-2.fc16.noarch from fedora libopenvrml-gl-0.18.8-2.fc16.x86_64 from fedora libopenvrml-gl-devel-0.18.8-2.fc16.x86_64 from fedora 1:libprelude-1.0.0-11.fc17.i686 from fedora 1:libprelude-ruby-1.0.0-11.fc17.x86_64 from fedora libstdc++-4.7.0-1.fc17.i686 from updates-testing libtasn1-2.12-1.fc17.i686 from updates-testing nss-softokn-freebl-3.13.3-1.fc17.i686 from fedora ocaml-augeas-0.4-9.fc15.x86_64 from fedora ocaml-augeas-devel-0.4-9.fc15.x86_64 from fedora ocaml-emacs-3.12.1-1.fc17.x86_64 from fedora openhpi-subagent-2.3.4-17.fc17.x86_64 from fedora openvrml-0.18.8-2.fc16.x86_64 from fedora openvrml-java-0.18.8-2.fc16.x86_64 from fedora openvrml-javascript-0.18.8-2.fc16.x86_64 from fedora openvrml-mozilla-plugin-0.18.8-2.fc16.x86_64 from fedora openvrml-nodes-0.18.8-2.fc16.x86_64 from fedora openvrml-player-0.18.8-2.fc16.x86_64 from fedora openvrml-xembed-0.18.8-2.fc16.x86_64 from fedora p11-kit-0.11-1.fc17.i686 from fedora php-pecl-runkit-0.9-15.CVS20090215.fc17.x86_64 from fedora psgml-1.2.5-14.fc17.noarch from fedora puppet-2.6.14-1.fc17.noarch from fedora puppet-server-2.6.14-1.fc17.noarch from fedora qtparted-0.4.5-26.fc15.x86_64 from fedora ruby-gtkglext-0.90.4-1.8.fc17.x86_64 from fedora ruby-openbabel-2.3.1-1.fc17.x86_64 from fedora ruby-shadow-1.4.1-15.fc17.x86_64 from fedora rubygem-activeldap-1.2.2-3.fc17.noarch from fedora rubygem-fastercsv-1.5.4-2.fc17.noarch from fedora tango-devel-2-5.20120215git7aec6a1.fc17.x86_64 from updates-testing tango-doc-2-5.20120215git7aec6a1.fc17.noarch from updates-testing tetex-tex4ht-1.0.2008_09_16_1413-5.fc17.x86_64 from fedora tmda-emacs-1.1.12-6.fc17.noarch from fedora xemacs-tuareg-2.0.4-2.fc17.noarch from fedora xemacs-tuareg-el-2.0.4-2.fc17.noarch from fedora zlib-1.2.5-6.fc17.i686 from fedora These packages failed at transaction check: Transaction Check Error: file /etc/logrotate.d/syslog from install of syslog-ng-3.2.5-5.fc17.x86_64 conflicts with file from package rsyslog-5.8.7-1.fc17.x86_64 Transaction Check Error: file /usr/bin/ftdump from install of dtc-1.3.0-3.fc17.x86_64 conflicts with file from package freetype-demos-2.4.8-2.fc17.x86_64 These packages passed all the checks but had errors during install: Non-fatal POSTIN scriptlet failure in rpm package clamav-update-0.97.3-1703.fc17.x86_64 Error in PREIN scriptlet in rpm package ircd-ratbox-2.2.8-8.fc17.x86_64 Non-fatal POSTIN scriptlet failure in rpm package 2:qemu-system-x86-1.0-6.fc17.x86_64 Non-fatal POSTIN scriptlet failure in rpm package postgresql-pgpoolAdmin-2.2-2.fc12.noarch Non-fatal POSTIN scriptlet failure in rpm package util-vserver-legacy-0.30.215+svn2929-1602.fc17.x86_64 Error in PREIN scriptlet in rpm package smstools-3.1.14-3.fc17.x86_64 Both ircd-ratbox and smstools failed to install because of the errors.

12 years, 1 month

3
5
0 / 0

GNOME shell broken after suspend and resume for driver r300_dri

by Christoph Frieben

Can anybody report success for the suspend and resume cycle triggered from within the GNOME shell when the graphics card is based on some R300/R400 variant? In my case, the shell is still broken after resume. The video device is some ATI Radeon X800 card which is using the R420 chip. Only a black desktop, a mouse pointer and the GNOME panel are visible after resume. The desktop is not completely frozen since I am still able to move the mouse pointer. It is also possible to switch to a VT in order to reboot the system. Thanks, ~C PS: The F15 development cycle is nearing completion, and in my opinion, this is a major usability issue.

12 years, 1 month

3
7
0 / 0

nautilus-dropbox-0.7.1

by Rob Healey

Greetings: In trying to compile this from source3 downloaded from http://www.dropbox.com ... Here is what I got on my terminal winddow: No package 'libnautilus-extension' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables NAUTILUS_CFLAGS and NAUTILUS_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. [Frog@PouncingAliens nautilus-dropbox-0.7.1]$ su -l Password: [root@PouncingAliens ~]# yum provides \*libnautilus-extension Loaded plugins: fastestmirror, langpacks, refresh-packagekit Loading mirror speeds from cached hostfile * rpmfusion-free-rawhide: mirror.web-ster.com * rpmfusion-nonfree-rawhide: mirror.web-ster.com google-chrome/filelists | 1.1 kB 00:00 rpmfusion-free-rawhide/filelists | 211 kB 00:00 rpmfusion-nonfree-rawhide/filelists | 274 kB 00:00 nautilus-devel-3.3.91-1.fc17.i686 : Support for developing nautilus extensions Repo : rawhide Matched from: Filename : /usr/include/nautilus/libnautilus-extension nautilus-devel-3.3.91-1.fc17.x86_64 : Support for developing nautilus extensions Repo : rawhide Matched from: Filename : /usr/include/nautilus/libnautilus-extension -- Sincerely yours, Rob G. Healey

12 years, 1 month

3
2
0 / 0

F17 video annoyances, old hardware

by stan

F17 boots using nouveau for my old Nvidia hardware (MX420). There are two problems with this for me. - nouveau doesn't allow different resolutions on consoles and gui. - mplayer can't adjust brightness and contrast. This is strange since qiv can. On F15 I'm running the old nv driver to get around these issues, and it works fine. However, when I try to use it in F17, with an xorg.conf file, it gives the following error, and refuses to start. [ 26704.014] (II) Loading sub module "xaa" [ 26704.014] (II) LoadModule: "xaa" [ 26704.016] (WW) Warning, couldn't open module xaa [ 26704.016] (II) UnloadModule: "xaa" [ 26704.016] (II) Unloading xaa [ 26704.016] (EE) NV: Failed to load module "xaa" (module does not exist, 0) [ 26704.016] (II) UnloadModule: "nv" [ 26704.016] (II) UnloadSubModule: "fb" [ 26704.016] (II) Unloading fb [ 26704.016] (II) UnloadSubModule: "vgahw" [ 26704.016] (II) Unloading vgahw [ 26704.016] (II) UnloadSubModule: "int10" [ 26704.016] (II) Unloading int10 [ 26704.016] (EE) Screen(s) found, but none have a usable configuration. [ 26704.016] Fatal server error: [ 26704.016] no screens found I can't find this module xaa. Can anyone tell me where it is? Thanks.

12 years, 1 month

6
17
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test March 2012