test June 2014

test@lists.fedoraproject.org

49 participants
177 discussions

[Fedora QA] #61: make VirtioSerial Test cases clearer
by fedora-badges 28 Jan '15

28 Jan '15

#61: make VirtioSerial Test cases clearer ----------------------+----------------------------------------------------- Reporter: liam | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Test Day | Version: Keywords: | ----------------------+----------------------------------------------------- we have VirtioSerial Test cases here: https://fedoraproject.org/wiki/Test_Day:2010-04-08_Virtualization_VirtioSer… but during test day, none of these cases was executed. I think testers did not know how to run these cases, so Amit, could you like to rewrite these cases with template and make it clearer? The good cases can help make VirtioSerial better and better,it also can involve more fedora people in virtio.Thanks in advance. These cases that are written with template for your reference: https://fedoraproject.org/wiki/QA:Fedora_13_Install_Results_Template#Test_M… Or if you don't know how to use template, just write the test step more specific and send the cases to me, I will convert them to standard format. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/61> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 4

[Fedora QA] #46: Write Test cases for LXDE components.
by fedora-badges 27 Jan '15

27 Jan '15

#46: Write Test cases for LXDE components. ----------------------+----------------------------------------------------- Reporter: johannbg | Owner: johannbg Type: task | Status: new Priority: major | Milestone: Component: Test Day | Version: Keywords: | ----------------------+----------------------------------------------------- An ticket to keep track on LXDE components that need test cases and how to debug pages * PCManFM: File manager, provides desktop icons * LXPanel: Feature-rich desktop panel * LXSession: Standard-compliant X11 session manager with shutdown/reboot/suspend support via HAL ( FEI https://fedoraproject.org/wiki/Features/HalRemoval ) * LXSession-edit: GUI to configure what’s automatically started in LXDE * lxde-settings-daemon: XSettings Daemon * LXInput: Keyboard and mouse settings dialog * LXRandR: Configuration tool for monitors and external projectors * LXAppearance: Feature-rich GTK+ theme switcher able to change GTK+ themes, icon themes, and fonts * LXTask: Lightweight task manager derived from xfce4 task manager * LXTerminal: Desktop-independent VTE-based terminal emulator * LXLauncher: Open source replacement for the Asus Launcher on the EeePC * LXShortcut: Small utility to edit application shortcuts, used by lxpanel and lxlauncher * LXNM (still under development): Lightweight network manager for LXDE supporting wireless connections (not yet in Fedora ) * LXRandR (still under development): Monitor configuring tool * Openbox: Lightweight, standard-compliant, and highly-configurable window manager. * GPicView: A very simple, fast, and lightweight image viewer featuring immediate startup * Leafpad: Lightweight and simple text editor * XArchiver: Lightweight, fast, and desktop-independent gtk+-based file archiver * LXDM: Display manager -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/46> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 7

mount -t nfs delayed
by Felix Miata 23 Oct '14

23 Oct '14

For several weeks, maybe several months, most of my Rawhide installations generate an error trying to mount noauto nfs items in fstab: Job for rpc-statd.service failed. See 'systemctl status rpc-statd.service' and 'journalctl -xn' for details. Output from those: [start]rpc-statd.service - NFS status monitor for NFSv2/3 locking. Loaded: loaded (/usr/lib/systemd/system/rpc-statd.service; enabled) Active: failed (Result: exit-code) since Thu 2014-05-29 00:41:00 EDT; 3min 12s ago Process: 691 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=1/FAILURE) May 29 00:40:00 g5eas systemd[1]: Starting NFS status monitor for NFSv2/3 locking.... May 29 00:40:00 g5eas rpc.statd[692]: Version 1.3.0 starting May 29 00:40:00 g5eas rpc.statd[692]: Flags: TI-RPC May 29 00:41:00 g5eas rpc.statd[692]: failed to create RPC listeners, exiting May 29 00:41:00 g5eas systemd[1]: rpc-statd.service: control process exited, code=exited status=1 May 29 00:41:00 g5eas systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking.. May 29 00:41:00 g5eas systemd[1]: Unit rpc-statd.service entered failed state. -- Logs begin at Sat 2014-03-22 18:49:34 EDT, end at Thu 2014-05-29 00:41:00 EDT. -- May 29 00:40:00 g5eas rpcbind[693]: cannot create socket for tcp6 May 29 00:40:00 g5eas systemd[1]: Started RPC bind service. -- Subject: Unit rpcbind.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rpcbind.service has finished starting up. -- -- The start-up result is done. May 29 00:40:07 g5eas systemd[1]: Starting Stop Read-Ahead Data Collection... -- Subject: Unit systemd-readahead-done.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-readahead-done.service has begun starting up. May 29 00:40:07 g5eas systemd[1]: Started Stop Read-Ahead Data Collection. -- Subject: Unit systemd-readahead-done.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-readahead-done.service has finished starting up. -- -- The start-up result is done. May 29 00:41:00 g5eas rpc.statd[692]: failed to create RPC listeners, exiting May 29 00:41:00 g5eas systemd[1]: rpc-statd.service: control process exited, code=exited status=1 May 29 00:41:00 g5eas systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking.. -- Subject: Unit rpc-statd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rpc-statd.service has failed. -- -- The result is failed. May 29 00:41:00 g5eas systemd[1]: Unit rpc-statd.service entered failed state. May 29 00:41:00 g5eas rpc.statd[709]: Version 1.3.0 starting May 29 00:41:00 g5eas rpc.statd[709]: Flags: TI-RPC [end] I see no similar problem in Factory or Cauldron using identical fstab entries and mount syntax. What needs to be done to eliminate this delay? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

3 12

NM controlled bridge turns on netfilter
by Paul Knox-Kennedy 05 Oct '14

05 Oct '14

I have a host recently updated to f20, with virtual machines using bridged networking. When I switch to NetworkManager controlled networking, the virtual machines' DHCP requests failed. After much messing around, I have found that when NM is on, by the time the system has booted, bridge-nf-call-iptables, bridge-nf-call-ip6-tables and bridge-nf-call-arptables have all been set to 1, so something has overriden the setting from /usr/lib/sysctl.d/00-system.conf. Is there some setting I am missing here? Thanks Paul NOTICE & DISCLAIMER This email including attachments (this "Document") is confidential and may contain legally privileged information. If you have received this Document in error please notify the sender immediately and delete this Document from your system without using, copying, disclosing or disseminating it or placing any reliance upon its contents. We cannot accept liability for any breaches of confidence arising through use of this Document. The information contained in this Document is provided solely for information purposes on an "as is" basis without warranty of any kind, either express or implied, including without limitation any implied warranty of satisfactory or merchantable quality, fitness for a particular purpose or freedom from error or infringement. The user relies on the information contained herein, and its accuracy or otherwise, entirely at their own risk. Any opinions expressed in this Document are those of the author and do not necessarily reflect the opinions of Telsis. We will not accept responsibility for any commitments made by our employees outside the scope of our business.

7 11

Criterion revision proposal: KDE default applications
by Adam Williamson 10 Sep '14

10 Sep '14

It was clear at the Go/No-Go meeting today that KDE SIG does not consider this release criterion applicable/desired: "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test." https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria#Default_app… jreznik says they consider the live image their 'polished product' where everything must work, while the DVD install is more of a grab-bag - they install a whole bunch of stuff, and don't think it's the end of the world if one or two bits are broken. Given that, I propose re-wording as follows: "All applications that can be launched using the standard graphical mechanism of a release-blocking live image after an installation of that image must start successfully and withstand a basic functionality test." So, that doesn't just apply to KDE. True, but I actually think it's a reasonable revision for GNOME as well. It makes sense to see the live images as defining what our 'polished core desktops' consist of, and the DVD as more of a grab-bag of packages. The lives will (should) always contain the bits the desktop SIGs think are absolutely key pieces of the desktop. And I think we could generally do with a bit of criteria watering-down; we're starting to do a lot of fudges and waives, which indicates the criteria are currently too tight for us to realistically enforce. Things are better when we can stand solidly behind the criteria without fudging stuff. CCing KDE and desktop lists. If folks feel that we should restrict this change to KDE only, please do yell, but I'm kinda liking the simple version. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

18 37

[Fedora QA] #445: Proposed Test Day - Wayland
by fedora-badges 26 Aug '14

26 Aug '14

#445: Proposed Test Day - Wayland ----------------------+------------------------ Reporter: vbenes | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ I would like to schedule a test day for Wayland. Anytime between alpha and beta -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/445> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 5

[Fedora QA] #430: Printing Test Day
by fedora-badges 11 Aug '14

11 Aug '14

#430: Printing Test Day ----------------------+------------------------ Reporter: twaugh | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 20 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ = phenomenon = I would like to arrange a Printing Test Day for Fedora 20. Proposed date is 5th November 2013. = background analysis = Fedora 20 comes with CUPS 1.7 and Ghostscript 9.10, as well as some changes to the cups-filters package. = implementation recommendation = The main focus will be regression testing. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/430> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #424: Proposed Test Day - KDE 4.11
by fedora-badges 11 Aug '14

11 Aug '14

#424: Proposed Test Day - KDE 4.11 ----------------------+------------------------ Reporter: mbriza | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 20 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ = phenomenon = KDE Plasma Workspaces test day for Fedora 20 Proposed date is 7th November, 2013. = implementation recommendation = We, as the KDE SIG need to test our three proposed features: * KDE Plasma Workspaces 4.11 * Plasma-nm * SDDM as the default KDE display manager instead of KDM as well as the regular KDE tests ran before every Fedora release -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/424> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #420: Power management testday
by fedora-badges 11 Aug '14

11 Aug '14

#420: Power management testday ----------------------+------------------------ Reporter: jskarvad | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 20 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ We would like to run Power management test day. The arrangement will be similar to our previous Power management test days. We can prepare the live medium ourselves. We propose 2013-11-14, but any other date should fit. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/420> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #409: Fedora 20 i18n Test Day
by fedora-badges 11 Aug '14

11 Aug '14

#409: Fedora 20 i18n Test Day ----------------------+------------------------ Reporter: aalam | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 20 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ I18N (Internationalization) Test Day Test Date: TBD Fedora 20 Schedule: http://fedoraproject.org/wiki/Releases/20/Schedule Required: Live ISO, it may not be same as l10n test day. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/409> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 10

← Newer
1
2
3
4
5
6
7
8
...
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test June 2014