[Bug 982510] New: 4.3. Using the User Manager Tool
by Red Hat Bugzilla
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.
8 years
[Bug 982504] New: 4.2. Using the User Accounts Tool
by Red Hat Bugzilla
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.
8 years
[Bug 982444] New: 1.1 - region and language
by Red Hat Bugzilla
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.
8 years
[Bug 982500] New: 2.1 Using the Date and Time Configuration Tool
by Red Hat Bugzilla
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.
8 years
[Bug 1245533] New: Documentation for setting up tftp server is missing for last two documentation releases
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1245533
Bug ID: 1245533
Summary: Documentation for setting up tftp server is missing
for last two documentation releases
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: swadeley(a)redhat.com
Reporter: valent.turkovic(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Description of problem:
I have tried setting up tftp server on fedora and failed miseably after 2 hours
of trying. There is only a brief mention in Fedora 20 docs:
https://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/s1...
But crucial config file is missing after installing tftpd server.
Is this method abandoned? There is no mention of allowing ports for tftp in
firewall. On previous Fedora installs this worked, I installed tftpd and
allowed tftp ports in firewall, but now it doesn't work anymore. Is there some
additional layer of security that it preventing clients from connecting to tftp
server?
Please document this and also show how to troubleshoot.
Thanks.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
Description of problem:
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.
8 years, 1 month
[Bug 1136030] New: Need a new chapter about upgrading Fedora
by Red Hat Bugzilla
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.
8 years, 2 months
[Bug 1018500] New: There's no section in the documentation for NFS, after Fedora 14
by Red Hat Bugzilla
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.
8 years, 2 months
[Bug 1226101] New: $expected_checksum not correct in "Verifying checksums on Windows systems"
by Red Hat Bugzilla
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/se...
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 3 months
[Bug 1146950] New: Test Bug
by Red Hat Bugzilla
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.
8 years, 3 months