https://bugzilla.redhat.com/show_bug.cgi?id=982911
Bug ID: 982911
Summary: 7.3.3. Establishing a Mobile Broadband Connection
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
Under section 7.3.3, in 'Procedure 7.3. Adding a New Mobile Broadband
Connection', 'Procedure 7.4. Editing an Existing Mobile Broadband Connection':
network connection editor can also be found at:
activities --> applications --> sundry --> network connections
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982910
Bug ID: 982910
Summary: 7.3.5. Establishing a DSL Connection
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
In section 7.3.5 under 'Procedure 7.6. Adding a New DSL Connection', 'Procedure
7.7. Editing an Existing DSL Connection':
These procedures could also specify that the network connections editor can be
accessed from:
activities --> applications --> Sundry --> Network Connections
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1221780
Bug ID: 1221780
Summary: how to identify firmware types, UEFI vs BIOS
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: swadeley(a)redhat.com
Reporter: bugzilla(a)colorremedies.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
I'm not finding advice in documentation to identify firmware type. Should we,
and if so where should it go?
Identifying firmware type comes in handy e.g. reinstalling grub, see bug
1220066.
The problem is, users overwhelmingly equate UEFI and BIOS, often referring to
it as UEFI BIOS, mainly because OEM's still call firmware updates "BIOS
updates".
Two possible ways to reliably identify UEFI vs BIOS firmware.
On an EFI system:
# ls /sys/firmware/efi
config_table efivars fw_platform_size fw_vendor runtime runtime-map
systab vars
On a BIOS system:
# ls /sys/firmware/efi
ls: cannot access /sys/firmware/efi: No such file or directory
----
On an EFI system:
# efibootmgr
BootCurrent: 0000
Timeout: 5 seconds
BootOrder: 0000,0080
Boot0000* Fedora
Boot0080* Mac OS X
Boot0082*
BootD1A6* AST
BootFFFF*
On a BIOS system:
# efibootmgr
efibootmgr: EFI variables are not supported on this system.
Unknowns:
The first method always works since ls is for sure installed no matter what. I
need to test if efibootmgr is always installed, e.g. netinstall (?), it
definitely is always installed from lives. But if it's not installed, then it's
not a UEFI system.
How does coreboot firmware manifest? I think it's mainly a "better BIOS" and
should behave as such.
ARM firmware?
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1003065
Bug ID: 1003065
Summary: images missing from document
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: low
Assignee: jhradile(a)redhat.com
Reporter: mordred(a)warpmail.net
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
in document:
http://docs.fedoraproject.org/en-US/Fedora/18/html-single/System_Administra…
missing following 5 images under:
http://docs.fedoraproject.org/en-US/Fedora/18/html-single/System_Administra…
images/authconfig-ui.png
images/authconfig-local.png
images/authconfig_LDAP.png
images/authconfig_nis.png
images/authconfig_winbind.png
Version-Release number of selected component (if applicable): n/a
How reproducible: n/a
Steps to Reproduce: n/a
Actual results:
Expected results: n/a
Additional info: n/a
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=987307
Bug ID: 987307
Summary: Section 11.1.2.4 Figure 11.2 requires updating
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Created attachment 777222
--> https://bugzilla.redhat.com/attachment.cgi?id=777222&action=edit
layout of ldap/kerberos options in authentication dialog
Description of problem:
Figure 11.2 in section 11.1.2.4 no longer looks like this as there is a third
'password options tab' on this dialog
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=987301
Bug ID: 987301
Summary: Section 11.1.1 Figure 11.1 missing
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
Section 11.1.1 has a missing screenshot (Figure 11.1)
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=983366
Bug ID: 983366
Summary: Cover Page says "Fedora 17" in 'header' logo
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
Header logo on cover page of System Administrators guide says "Fedora 17" above
first line of text
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982894
Bug ID: 982894
Summary: 7.2.4. User and System Connections
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
the network settings dialogue does not have tabs, instead, the identity section
of the dialogue is concerned with setting the connection to be available to all
users (or not)
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982510
Bug ID: 982510
Summary: 4.3. Using the User Manager Tool
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
In section 4.3, the location of the user manager tool has changed in Gnome
3.8.3:
Activities --> Applications --> Sundry --> Users and Groups
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982504
Bug ID: 982504
Summary: 4.2. Using the User Accounts Tool
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
section 4.2 Using the User Accounts Tool
related to bug 982500
location of the settings dialog is:
activities --> applications --> utilities --> settings
Further:
The 'User Accounts' tool is called 'Users' in Gnome 3.8.3
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982444
Bug ID: 982444
Summary: 1.1 - region and language
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
Sys admin guide information regarding region and language doesn't specify which
desktop environment is assumed to find the region and language. Also to find
region and language in KDE, you click on the applications launcher, go to
applications --> settings --> system settings, but it's also set as a favourite
by default in F19 so can be found under favourites. Also in KDE, under system
settings, the 'region and language' settings are under 'locale',
'country/region and language'.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982500
Bug ID: 982500
Summary: 2.1 Using the Date and Time Configuration Tool
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
Gnome settings menu location has changed in 3.8.3:
Activities --> Applications --> Utilities --> Settings
This is not reflected in section 2.1
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1136030
Bug ID: 1136030
Summary: Need a new chapter about upgrading Fedora
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: pbokoc(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
The current upgrade chapter is pretty much completely useless. We need a new
one that would cover:
* Automatic upgrades with FedUp, including how to prepare and how to clean up
after the update finishes
* Manual upgrade (or reinstall) - manually booting the installer on an existing
system and using the normal installation process to overwrite the root
filesystem while keeping the rest of the system (/home and any other separate
filesystems) intact.
There should be ample documentation on FedUp on the Fedora Wiki.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1018500
Bug ID: 1018500
Summary: There's no section in the documentation for NFS, after
Fedora 14
Product: Fedora Documentation
Version: devel
Component: storage-administration-guide
Assignee: ddomingo(a)redhat.com
Reporter: david.jones74(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, zach(a)oglesby.co
Description of problem:
There's no section in the documentation for current Fedora versions, about how
to configure NFS. There's SAMBA and FTP, but no NFS.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Search or browse documentation.
2.
3.
Actual results:
Can find scattered information about configuring NFS, but no consolidated
section.
Expected results:
Section for configuring NFS clients and servers.
Additional info:
There are many changes in NFS configuration since Fedora 14. There's a
different init system with different service names, There's also a new firewall
manager. I'm just guess at a lot of the details, and it's pretty frustrating.
Why does SAMBA have a large detailed section, and NFS has nothing? This is
Linux, right? Is the Fedora Project moving to SAMBA as the preferred file
sharing method?
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1226101
Bug ID: 1226101
Summary: $expected_checksum not correct in "Verifying checksums
on Windows systems"
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: iam(a)nnutter.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Created attachment 1031533
--> https://bugzilla.redhat.com/attachment.cgi?id=1031533&action=edit
Fedora-Workstation-22-x86_64-CHECKSUM
Description of problem:
When following the steps in "Verifying checksums on Windows systems" the value
of the `$expected_checksum` is 'sha256' because it is splitting the line and
grabbing the first word.
Version-Release number of selected component (if applicable): 22, full URL in
"Additional info".
How reproducible: 100%
Steps to Reproduce:
1. Download Fedora-Live-Workstation-x86_64-22-3.iso.
2. Download Fedora-Workstation-22-x86_64-CHECKSUM.txt.
3. Follow PowerShell instruction from "Verifying checksums on Windows systems".
Actual results:
`$expected_checksum` equals 'sha256'.
PS C:\Users\...\Downloads> $checksum_file =
"Fedora-Workstation-22-x86_64-CHECKSUM.txt"
PS C:\Users\...\Downloads> $image = "Fedora-Live-Workstation-x86_64-22-3.iso"
PS C:\Users\...\Downloads> $expected_checksum = ((Get-Content $checksum_file |
Select-String -Pattern $image) -split " ")[0].ToLower()
PS C:\Users\...\Downloads> $expected_checksum
sha256
Expected results:
`$expected_checksum` equals
'615abfc89709a46a078dd1d39638019aa66f62b0ff8325334f1af100551bb6cf'.
PS C:\Users\...\Downloads> $expected_checksum = ((Get-Content $checksum_file |
Select-String -Pattern $image) -split " ")[3].ToLower()
PS C:\Users\...\Downloads> $expected_checksum
615abfc89709a46a078dd1d39638019aa66f62b0ff8325334f1af100551bb6cf
Additional info:
I've attached the "Fedora-Workstation-22-x86_64-CHECKSUM.txt" since it is not
very large but it's from,
https://getfedora.org/verify
The "Verifying checksums on Windows systems" page is,
https://docs.fedoraproject.org/en-US/Fedora/22/html/Installation_Guide/sect…
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1146950
Bug ID: 1146950
Summary: Test Bug
Product: Fedora Documentation
Version: devel
Component: system-administrator's-reference-guide
Assignee: jhradile(a)redhat.com
Reporter: jhradile(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
This is just a test bug. Please, feel free to ignore it.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1098298
Bug ID: 1098298
Summary: Some problems in "Chapter 11. Storage pools"
Product: Fedora Documentation
Version: devel
Component: virtualization-administration-guide
Assignee: lnovich(a)redhat.com
Reporter: bughunt(a)gluino.name
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
In:
http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administr…
I want to create storage pools using virsh.
Corrections:
Create the storage pool definition
- - - - - - - - - - - - - - - - - -
"The path to a file system directory for storing guest image files. If this
directory does not exist, virsh will create it."
This is incorrect. "You have to create it afterwards using virsh" is correct.
Create the local directory
- - - - - - - - - - - - - -
I create the directory under "/home"
Documentation shows that "ls -la /guest_images" shows the directory having
permissions "700". This is incorrect, the permissions are "755" (at least for
me)
Improvement: Maybe one should also add the output of
ls --lcontext -la /guest_images/
drwxr-xr-x. 2 system_u:object_r:home_root_t:s0 root root 4096 May 15 18:50 .
drwxr-xr-x. 5 system_u:object_r:home_root_t:s0 root root 4096 May 15 18:50 ..
The wrong permissions error is repeated under "6. Verify the storage pool
configuration":
ls -la /guest_images/
total 8
drwxr-xr-x. 2 root root 4096 May 15 18:50 .
drwxr-xr-x. 5 root root 4096 May 15 18:50 ..
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=990252
Bug ID: 990252
Summary: incomplete index for Virtualization Administration
Guide
Product: Fedora Documentation
Version: devel
Component: virtualization-administration-guide
Assignee: lnovich(a)redhat.com
Reporter: stephent98(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
Description of problem:
The index for the Virtualization Administration Guide has only three entries.
Specifically, I was trying to find information on host memory requirements.
Version-Release number of selected component (if applicable):
http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administr…
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1068889
Bug ID: 1068889
Summary: Remove references to version numbers in package
documentation directories
Product: Fedora Documentation
Version: devel
Component: virtualization-deployment-and-administrative-guide
Assignee: lnovich(a)redhat.com
Reporter: sclark(a)fedoraproject.org
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
Created attachment 866496
--> https://bugzilla.redhat.com/attachment.cgi?id=866496&action=edit
The attached archive contains patches to implement this change
Following instructions in
https://fedoraproject.org/wiki/Changes/UnversionedDocdirs remove the version
number from the directory name for all references to any package documentation
directory in /usr/share/doc , leaving just the package's name.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1217953
Bug ID: 1217953
Summary: '--nombr' option from bootloader keyword in kickstart
file is not documented
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: franta(a)hanzlici.cz
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
'ksverdiff -f F20 -t F21' command (among others) print:
"
The following options were added to the bootloader command in F21:
--disabled --nombr
"
But F21 'Installation Guide' in "A.2.2. bootloader" chapter:
http://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/sect-…
not mention '--nombr' option for this keyword.
Version-Release number of selected component (if applicable):
F21 Installation Guide (above URL)
ksverdiff from pykickstart-1.99.65-2.fc21.noarch
Additional info:
- for unknown reason, RH Bugzilla offers only 'devel' version for this issue,
although I want report it again F21.
- of course, there may be bug somewhere in 'ksverdiff'.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1214964
Bug ID: 1214964
Summary: Hold Option to select boot source on Mac hardware
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: beland(a)alum.mit.edu
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
I'm not sure where to find the draft of the Fedora 22 Installation Guide, but I
went through the Fedora 21 version steps in order to install the beta today.
One suggestion for the new version of this page:
http://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/chap-…
I recommend adding something like "On Mac hardware, hold down Option to enter
the boot media selection menu." Mac hardware with Intel chips is rather common
now, so I hope a significant number of people would be aided by that addition.
I spent several hours trying to figure that out the first time I put Fedora on
a Macbook.
Thanks!
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1180524
Bug ID: 1180524
Summary: confining users section unclear
Product: Fedora Documentation
Version: devel
Component: selinux-user-guide
Assignee: mprpic(a)redhat.com
Reporter: nmavrogi(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: mprpic(a)redhat.com, pkennedy(a)redhat.com,
zach(a)oglesby.co
The section 6 (confining users) in Fedora 21 documentation of SELinux is very
unclear.
1. What does confining mean actually? How are they confined? What capabilities
these user lose? These are crucial information, never discussed in the text.
2. In fedora with "seinfo -u" I see several selinux users. These, along with
the limitation each has, are never discussed.
3. "6.5. xguest: Kiosk Mode": I miss some technical info on the restrictions of
the xguest account. What that user can't do and what can it do. Without that
information the text could just say, trust us we've done everything for you
(nothing bad with it, except that in technical documentation you expect more).
4. I miss a "confining a server process/app" section. This is a very common
usage for selinux but no information is provided about that at all. Can I put
some server in a confined state, as the documentation discusses with the user?
Do we provide some preconfigured selinux users, roles, types for that purpose?
What about the sandbox tool we ship? That would be the information I'd expect
from such a section.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1180142
Bug ID: 1180142
Summary: issues in the introduction of selinux-user-guide
Product: Fedora Documentation
Version: devel
Component: selinux-user-guide
Assignee: mprpic(a)redhat.com
Reporter: nmavrogi(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: mprpic(a)redhat.com, pkennedy(a)redhat.com,
zach(a)oglesby.co
[Originally sent to authors of the document]
I was trying to understand selinux using that guide, and had quite some issues
in the introduction. I send you my issues in the hope they will help to improve
the text.
-------------------------------------------------------------
Chapter 2. Introduction to SELinux:
I couldn't really understand what is selinux based on this section. It
says it is mandatory access control mechanism, and then it goes into
length explaining the 'Discretionary Access Control (DAC) system' used
typically in Linux. That's nice if you already know what selinux is,
because you can see the difference, but the opposite what I'd expect at
the moment since I have no idea what selinux is.
My suggestion would be to add the description I saw in
https://www.imperialviolet.org/2009/07/14/selinux.html
"SELinux is fundamentally about answering questions of the form “May x
do y to z?” and enforcing the result (x is subject, z is object) ...
The action (y) boils down to a class and a permission. Each class can
have up to 32 permissions (because they are stored as a bitmask in a
32-bit int). Examples of classes are FILE, TCP_SOCKET and X_EVENT. For
the FILE class, some examples of permissions are READ, WRITE, LOCK etc."
At least for me that was all the information that I needed to understand
what I can do with SELinux. A complete pictures may require to go into a
bit more length with explaining what can be a subject, object and
actions. Then mentioning about MAC and explaining it in addition to DAC
will be more natural IMO.
---------------------------------------------------------------------
2.1. Benefits of running SELinux
This is section vaguely defines domain. I reached "3.1. Domain
Transitions" and didn't know what a domain was.
Maybe add a definition of domain in 3.1 or earlier in the introduction.
---------------------------------------------------------------------
Chapter 3. SELinux Contexts
level:
It explains that in Fedora there is a single sensitivity and multiple
categories. I miss what are these categories intended to be used to? An
example with two different categories would be helpful.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1231578
Bug ID: 1231578
Summary: No valid SHA1 checksums in checksum file
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: misterfluff(a)me.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
Following the installation procedure for Fedora 22 the section in 3,3,2
(verifying checksums on Linux and OS X systems) fails.
Version-Release number of selected component (if applicable):
Fedora-Live-Scientific_KDE-x86_64-22-3.iso
How reproducible:
100%
Steps to Reproduce:
1. Download Fedora-Live-Scientific_KDE-x86_64-22-3.iso from spins page
2. Download Fedora-Spins-x86_64-22-CHECKSUM
3. shasum -a 256 -c *CHECKSUM
Actual results:
Fedora-Spins-x86_64-22-CHECKSUM: no properly formatted SHA1 checksum lines
found
Expected results:
Success, of course...:)
Additional info:
Additional checksum file Fedora-Workstation-22-x86_64-CHECKSUM file gave same
result.
Also performed "curl https://getfedora.org/static/fedora.gpg | gpg --import"
with no change in eventual result.
Is the process the same for checking a spin install versus the regular
workstation?
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1222305
Bug ID: 1222305
Summary: Release notes scattered with references to YUM. DNF
replaces yum
Product: Fedora Documentation
Version: devel
Component: release-notes
Severity: high
Assignee: relnotes(a)fedoraproject.org
Reporter: lsatenstein(a)yahoo.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Description of problem:
The release notes on the web are not current and do not match the Fedora 22
release. The release notes within the Fedora 22 /usr/share/doc are also
refering to Fedora 19 in places.
In preparation for Fedora 22 release notes it looks like someone searched for
Fedora 21 and changed the 21 to 22.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008149
Bug ID: 1008149
Summary: Contraficting info about the need of shared storage
for storing guest images to be migrated
Product: Fedora Documentation
Version: devel
Component: virtualization-getting-started-guide
Assignee: dayleparker(a)redhat.com
Reporter: jrodrigosm(a)yahoo.es
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dayleparker(a)redhat.com, docs(a)lists.fedoraproject.org
Hi,
In the Fedora 19 "Virtualization Getting Started Guide", section 2.2 ("What is
migration?"), URL
http://docs.fedoraproject.org/en-US/Fedora/19/html/Virtualization_Getting_S…
In the paragraph right before the 2.2.1 title, it is stated that "In Fedora 19,
shared storage is not necessary for storing guest images to be migrated. With
live storage migration [...]".
But in the last paragraph of the page, right before the note, it is stated that
"Shared, networked storage must be used for storing guest images to be
migrated. Without shared storage, migration is not possible."
These two statements seem contradictory to me. I just started learning about
virtualization, so I am unable to propose an alternative. But I do think some
clarification is needed.
Thanks,
Rodrigo
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1206351
Bug ID: 1206351
Summary: dnf conversion tracker bug
Product: Fedora Documentation
Version: devel
Component: docs-requests
Assignee: nobody(a)fedoraproject.org
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Additional information:
Tracker for individual documentation blockers.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1206805
Bug ID: 1206805
Summary: convert yum commands to dnf commands - System
Administrators Guide
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: swadeley(a)redhat.com
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
External Bug ID: Red Hat Bugzilla 1206351
External Bug ID: Red Hat Bugzilla 1206351
Description of problem:
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Sys…
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1193135
Bug ID: 1193135
Summary: Review Comments on Multiboot Guide version 0.1
Product: Fedora Documentation
Version: devel
Component: multiboot-guide
Severity: low
Assignee: chris.roberts(a)croberts.org
Reporter: scmccann2000(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: chris.roberts(a)croberts.org
Created attachment 992259
--> https://bugzilla.redhat.com/attachment.cgi?id=992259&action=edit
smccann comments to multiboot guide.
Attaching a pdf with a few comments from the perspective of a newbie to both
Fedora and multiboot. In general, very readable and understandable guide!
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1180202
Bug ID: 1180202
Summary: Overlap with uefi-secure-boot-guide
Product: Fedora Documentation
Version: devel
Component: multiboot-guide
Assignee: chris.roberts(a)croberts.org
Reporter: fweimer(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: chris.roberts(a)croberts.org
With the recent updates, there is now some overlap with the UEFI Secure Boot
guide.
I'm not sure the current state of Secure Boot is useful for non-dual-boot
systems, considering the feature loss and the lack of additional security due
to buggy kernels and permissive signed bootloaders from other vendors. Perhaps
merging the UEFI Secure Boot guide into the multiboot guide makes sense?
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1086052
Bug ID: 1086052
Summary: Include a section on using the Live media for rescue
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: sanjay.ankur(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
The install guide contains a section that documents how one can use the rescue
mode off the dvd. It doesn't document how one can use the live media for simple
rescue operations. The most common use case is when people install Window after
installing Fedora off a live media. They lose grub, and they can't figure out
how to use the live media to reinstall it.
There are a couple of blog posts that document it. For example:
http://thecreationist.expertscolumn.com/article/recover-grub-using-fedora-l…
It would maybe be a good idea to have a section in docs that provides hints on
how the live cd can be used for basic rescue operations.
Thanks,
Warm regards,
Ankur
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982906
Bug ID: 982906
Summary: 7.3.2. Establishing a Wireless Connection
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
Section 7.3.2 under the heading:
'Saving Your New (or Modified) Connection and Making Further Configurations'
it states:
"You can further configure an existing connection by selecting it in the
Network Connections window and clicking Edit to return to the Editing dialog."
This could be clarified by stating that network connections can be found under:
activities --> applications --> sundry --> network connections
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1192174
Bug ID: 1192174
Summary: Unhelpful links on LXDE spin page
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: medium
Assignee: pbokoc(a)redhat.com
Reporter: jhhaynes(a)earthlink.net
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
Several "how to use this file" links on the LXDE spins web page simply point
to the top Fedora documentation page. This is unhelpful when you need to know
how to use this file.
Version-Release number of selected component (if applicable):
F21
How reproducible:
always
Steps to Reproduce:
1.Bring up F21 LXDE spin web page
2.Click on any "how to use this file link"
3.
Actual results:
Gets to top of Fedora documentation tree
Expected results:
Should tell exactly how to use this file
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1152883
Bug ID: 1152883
Summary: Local replication of Product installation trees
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
It doesn't look like there will be a DVD image, the traditional source in our
instructions for site-provided installation repos. Consider conjuring up a
procedure explaining how an administrator could obtain a mirror of the
installation tree for each Product (whatever anaconda is pointed at for the
netinstalls) without having to pull in the entire repo.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=979158
Bug ID: 979158
Summary: Windows Virtio Drivers version 1-59 blue screens
windows when you hot add virtio drives
Product: Fedora Documentation
Version: devel
Component: virtualization-deployment-guide
Severity: high
Priority: unspecified
Assignee: lbailey(a)redhat.com
Reporter: robert.rupert(a)servicemesh.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lbailey(a)redhat.com
Description of problem:
Windows Blue Screens in KVM when using the latest virtio driver 1-59. When hot
adding scsi drive
Version-Release number of selected component (if applicable):
How reproducible:
fresh install with virtio scsi driver 1-59,=. Then hot add virtio scsi driver
in windows 7, 2008r2 and 2012
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
using the previose version 1-52 works fine
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=999762
Bug ID: 999762
Summary: Java FAQ
Product: Fedora Documentation
Version: devel
Component: release-notes
Severity: low
Assignee: relnotes(a)fedoraproject.org
Reporter: pcsnow(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Description of problem: Parts of Java FAQ may need some updates.
https://fedoraproject.org/wiki/Java/FAQ?rd=JavaFAQ
Version-Release number of selected component (if applicable):19
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
1. JPackage does not seem updated since 2009
2. Intelllij complains that non-sun version has performance problems during
install and recommends against use of OpenJDK.
3. It might be helpful to provide some assistance in docs to allow easy
integration of Oracle Java using system-switch-java.
The FAQ does not mention switch-java as an option.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001341
Bug ID: 1001341
Summary: Fedora 20 Boost 1.54 Uplift
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, pmachata(a)redhat.com,
relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Depends On: 991875, 991877, 991878, 991879, 991882, 991883,
991919, 998564
+++ This bug was initially created as a clone of Bug #998564 +++
This is a tracking bug for Change: Fedora 20 Boost 1.54 Uplift
For more details, see: http://fedoraproject.org//wiki/Changes/F20Boost154
This change brings Boost 1.54.0 to Fedora 20.
--- Additional comment from Petr Machata on 2013-08-19 11:30:25 EDT ---
Current state: Boost has been rebased, most clients were rebuilt about two
weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
iwhd, mrpt, pcl, python-tag, sumwars).
--- Additional comment from Jaroslav Reznik on 2013-08-20 08:57:28 EDT ---
(In reply to Petr Machata from comment #1)
> Current state: Boost has been rebased, most clients were rebuilt about two
> weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
> iwhd, mrpt, pcl, python-tag, sumwars).
Could you please set blocks/depends on for broken boost deps (if bug exists?).
Thanks.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001169.h…
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001342
Bug ID: 1001342
Summary: Fedora 20 Boost 1.54 Uplift
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
pmachata(a)redhat.com, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 991875, 991877, 991878, 991879, 991882, 991883,
991919, 998564
+++ This bug was initially created as a clone of Bug #998564 +++
This is a tracking bug for Change: Fedora 20 Boost 1.54 Uplift
For more details, see: http://fedoraproject.org//wiki/Changes/F20Boost154
This change brings Boost 1.54.0 to Fedora 20.
--- Additional comment from Petr Machata on 2013-08-19 11:30:25 EDT ---
Current state: Boost has been rebased, most clients were rebuilt about two
weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
iwhd, mrpt, pcl, python-tag, sumwars).
--- Additional comment from Jaroslav Reznik on 2013-08-20 08:57:28 EDT ---
(In reply to Petr Machata from comment #1)
> Current state: Boost has been rebased, most clients were rebuilt about two
> weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
> iwhd, mrpt, pcl, python-tag, sumwars).
Could you please set blocks/depends on for broken boost deps (if bug exists?).
Thanks.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001169.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001346
Bug ID: 1001346
Summary: Enable SELinux Labeled NFS Support
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, steved(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 984718, 998566
+++ This bug was initially created as a clone of Bug #998566 +++
This is a tracking bug for Change: Enable SELinux Labeled NFS Support
For more details, see: http://fedoraproject.org//wiki/Changes/LabeledNFS
The Linux Kernel has grown support for passing SELinux labels between a client
and server using NFS.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001216.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001345
Bug ID: 1001345
Summary: Enable SELinux Labeled NFS Support
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
steved(a)redhat.com, wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 984718, 998566
+++ This bug was initially created as a clone of Bug #998566 +++
This is a tracking bug for Change: Enable SELinux Labeled NFS Support
For more details, see: http://fedoraproject.org//wiki/Changes/LabeledNFS
The Linux Kernel has grown support for passing SELinux labels between a client
and server using NFS.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001216.h…
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008221
Bug ID: 1008221
Summary: Ryu Network Operating System
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
ymht.fedora(a)gmail.com, zach(a)oglesby.co
Depends On: 998540
+++ This bug was initially created as a clone of Bug #998540 +++
This is a tracking bug for Change: Ryu Network Operating System
For more details, see: http://fedoraproject.org//wiki/Changes/Ryu
Ryu Network Operating System http://osrg.github.com/ryu/
------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/184930.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008220
Bug ID: 1008220
Summary: Ryu Network Operating System
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
wb8rcr(a)arrl.net, ymht.fedora(a)gmail.com,
zach(a)oglesby.co
Depends On: 998540
+++ This bug was initially created as a clone of Bug #998540 +++
This is a tracking bug for Change: Ryu Network Operating System
For more details, see: http://fedoraproject.org//wiki/Changes/Ryu
Ryu Network Operating System http://osrg.github.com/ryu/
-----------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/184930.html
Please document this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
The following is a list of bugs or attachments to bugs in which a user has been
waiting more than 7 days for a response from you. Please take
action on these requests as quickly as possible. (Note that some of these bugs
might already be closed, but a user is still waiting for your response.)
We'll remind you again in another 7 days if these requests are still
outstanding, or if there are any new requests where users have been waiting
more than 7 days for your response.
review
------
Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (272 days old)
https://bugzilla.redhat.com/show_bug.cgi?id=1124344https://bugzilla.redhat.com/attachment.cgi?id=942713&action=edit
To see all your outstanding requests, visit:
https://bugzilla.redhat.com/request.cgi?action=queue&requestee=docs-qa%40li…
https://bugzilla.redhat.com/show_bug.cgi?id=1234615
Bug ID: 1234615
Summary: There is no description on how to activate speech
during installation
Product: Fedora Documentation
Version: devel
Component: accessibility-guide
Severity: medium
Assignee: gerard(a)ryan.lt
Reporter: brandonkeithbiggs(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: gerard(a)ryan.lt, sparks(a)redhat.com, zach(a)oglesby.co
Description of problem:
Under the screen reader section at:
https://docs.fedoraproject.org/en-US/Fedora/14/html-single/Accessibility_Gu…
There is no description on how to activate speech when one first installs
Fedora. For example, Ubuntu requires one to press super+alt+s and Debian
requires one to press s then hit enter in order to activate the text to speech
capability. This is very clear in both the installation and accessibility
manuals.
If I could make a suggestion though:
A mention in both the installation guide as well as in the accessibility guide
on how to activate accessibility options before installing the OS would really
help.
Version-Release number of selected component (if applicable):
How reproducible:
I am installing a VM on VM Player on Windows.
Steps to Reproduce:
1. load an ISO image
2. press alt+s, super+s, ctrl+s and all the combos like alt+super+s,
alt+super+s+ctrl...
3.
Actual results:
Silence
Expected results:
Sound out of my speakers telling me what should happen.
A line in the manual that tells me how to get the speech on the installer.
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
The following is a list of bugs or attachments to bugs in which a user has been
waiting more than 7 days for a response from you. Please take
action on these requests as quickly as possible. (Note that some of these bugs
might already be closed, but a user is still waiting for your response.)
We'll remind you again in another 7 days if these requests are still
outstanding, or if there are any new requests where users have been waiting
more than 7 days for your response.
review
------
Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (265 days old)
https://bugzilla.redhat.com/show_bug.cgi?id=1124344https://bugzilla.redhat.com/attachment.cgi?id=942713&action=edit
To see all your outstanding requests, visit:
https://bugzilla.redhat.com/request.cgi?action=queue&requestee=docs-qa%40li…
https://bugzilla.redhat.com/show_bug.cgi?id=846864
Bug ID: 846864
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: docs(a)lists.fedoraproject.org
Assignee: laine(a)redhat.com
Summary: Need a list of toolsets and when they are appropriate
in the virt Getting Started guide
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: laine(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: virtualization-getting-started-guide
Product: Fedora Documentation
The Getting Started Guide needs an overview of all the different toolsets, and
when each would be appropriate. In particular I'm talking about the following:
1) gnome-boxes
2) virt-manager
3) virsh, virt-install
4) ovirt
5) Should we point some people to OpenStack?
I will write up a first draft of this, and hand it to a qualified docs person
to edit and correctly place in the guide.
--
You are receiving this mail because:
You are the QA Contact for the bug.
The following is a list of bugs or attachments to bugs in which a user has been
waiting more than 7 days for a response from you. Please take
action on these requests as quickly as possible. (Note that some of these bugs
might already be closed, but a user is still waiting for your response.)
We'll remind you again in another 7 days if these requests are still
outstanding, or if there are any new requests where users have been waiting
more than 7 days for your response.
review
------
Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (258 days old)
https://bugzilla.redhat.com/show_bug.cgi?id=1124344https://bugzilla.redhat.com/attachment.cgi?id=942713&action=edit
To see all your outstanding requests, visit:
https://bugzilla.redhat.com/request.cgi?action=queue&requestee=docs-qa%40li…