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. (657 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=977042
Bug ID: 977042
Summary: GUI examples presume GNOME without stating it is GNOME
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
The System Administrator's Guide references a number of GUI utilities, many of
which are specific to GNOME. It isn't immediately obvious to the uninitiated
that this is the case, causing non-GNOME users to find fault with the guide.
I suggest an admonition in the preface along the lines of "Some of the
graphical procedures and menu locations are specific to GNOME, but most command
line instructions will be universally applicable" Comprehensively
differentiating between GNOME procedures, procedures for other DEs, and
universal procedures would probably be prohibitively time consuming.
--Pete
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=997219
Bug ID: 997219
Summary: No "Write to Disk" option for ISO images in Fedora 19
Product: Fedora Documentation
Version: devel
Component: readme-burning-isos
Assignee: oglesbyzm(a)gmail.com
Reporter: sirjake(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, stickster(a)gmail.com
Description of problem:
Guide says that you can right click on a ISO image and choose "Write to disc."
This is not true, at least with Fedora 19.
Version-Release number of selected component (if applicable):
19
How reproducible:
Always, at least in 32 bit.
Steps to Reproduce:
1.
http://docs.fedoraproject.org/en-US/Fedora/19/html/Burning_ISO_images_to_di…
2. Insert a DVD.
3. Attempt to follow the directions above. No "Write to disk" option exists.
Actual results:
No obvious way to burn ISO images in Fedora Linux 19.
Expected results:
Directions to burn ISO disk in Fedora Linux 19
Additional info:
I had a new-to-me computer that I assumed would not support 64 bit, but after
installing 32 bit found out that 64 was supported by my processor. I downloaded
64 ( Fedora-Live-Desktop-x86_64-19-1.iso ), and wanted to burn a disk of it,
but the option was not available and the directions online did not help. I had
to go back to Windows on a different machine to burn it.
Note: I do have a DVD burner on this machine. The same thing occurs with CD's
in the burner.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1336138
Bug ID: 1336138
Summary: System Administrator guide: Documentation of grubby
commands must be run as root
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: low
Assignee: swadeley(a)redhat.com
Reporter: fh.fedora(a)fhenry.fr
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Description of problem:
In chapter: 21.4. Configuring GRUB 2 Using the grubby Tool
The following commands should be mentioned to be executed also as root, like
the other ones, using a sharp caracter at begining of each command;
~]$ grubby --info=ALL
~]$ grubby --info /boot/vmlinuz-4.2.0-1.fc23.x86_64
grubby --remove-args="argX argY" --args="argA argB" --update-kernel
/boot/kernel
~]$ grubby --info /boot/vmlinuz-4.2.0-1.fc23.x86_64
Otherwise, this error is displayed in the console:
Unable to access bootloader configuration file "/etc/grub2-efi.cfg": Permission
denied
Version-Release number of selected component (if applicable):
Fedora 23 - System Administrator Guide
How reproducible:
Run command 'grubby --info /boot/vmlinuz-X.Y.Z-r.fc23.x86_64' as user
Steps to Reproduce:
1.
2.
3.
Actual results:
Error:
Unable to access bootloader configuration file "/etc/grub2-efi.cfg": Permission
denied
Expected results:
Command is executed without error
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1343775
Bug ID: 1343775
Summary: Guide for Fedora 23 still has "DRAFT" watermark
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: low
Assignee: swadeley(a)redhat.com
Reporter: jon(a)endpoint.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Created attachment 1165767
--> https://bugzilla.redhat.com/attachment.cgi?id=1165767&action=edit
simple patch to remove draft status
The web documentation here:
https://docs.fedoraproject.org/en-US/Fedora/23/html/System_Administrators_G…
still has a big "DRAFT" watermark. But Fedora 24 is coming out soon. If the
Fedora 23 docs aren't past draft stage now, they never will be. :) Maybe
there's some official process for promoting a document beyond the draft stage,
but if so, I'm not sure what the point is if it never happens before a new
Fedora release comes out.
Attached is a patch to change that.
--
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. (650 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…
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. (643 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…