[Bug 997219] New: No "Write to Disk" option for ISO images in Fedora 19
by Red Hat Bugzilla
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_...
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.
7 years, 9 months
[Bug 1336138] New: System Administrator guide: Documentation of
grubby commands must be run as root
by Red Hat Bugzilla
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.
7 years, 9 months
Predator drone adaptation of coding
by GARY SKEETE
Surveillance of Lone wolfs and other terror suspects
The juxtaposition of frequencies projected to within the brain to be adjusted to the brains frequency of 40 Hz be adaptation of visuals within the brain visual cortex centre the adaptation of qubit strategically placed to allow for the magnification and visualization of brainwaves frequencies speech thought word and deed cognition memory brief response reflex action as well as emotional content be adaptation of split second decision making of change of mind of spur of the moment thinking the realization that within these patterns like a distinct method of contributing to actions which are not covered by Internet coverage but are equally covered by this type of noninvasive surveillanc
7 years, 10 months
[Bug 948823] New: Need a search solution for docs.fedoraproject.org
by Red Hat Bugzilla
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=948823
Bug ID: 948823
Summary: Need a search solution for docs.fedoraproject.org
Product: Fedora Documentation
Version: devel
Component: project-tracking
Severity: unspecified
Priority: unspecified
Assignee: nobody(a)fedoraproject.org
Reporter: sparks(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, sparks(a)redhat.com,
stickster(a)gmail.com
Category: ---
Description of problem: Due to the removal of Google search feature (see bug
616876) we no longer have a search solution for docs.fp.o.
We need to investigate an alternate solution and bring the search feature back.
--
You are receiving this mail because:
You are the QA Contact for the bug.
7 years, 11 months
[Bug 1220066] New: grub2-install suggestion doesn't distinguish between BIOS and UEFI installs
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1220066
Bug ID: 1220066
Summary: grub2-install suggestion doesn't distinguish between
BIOS and UEFI installs
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
ttps://docs.fedoraproject.org/en-US/Fedora/21/html/System_Administrators_...
Section 20.4 and 20.4.1 apply only to BIOS computers, not UEFI. On UEFI:
1. grub2-install fails
https://bugzilla.redhat.com/show_bug.cgi?id=1101352
2. If grub2-efi-modules is installed, grub2-install succeeds but then:
2a. This will break UEFI Secure Boot systems because the core.img/grubx64.efi
binary that gets created isn't signed and therefore UEFI Secure Boot will
reject it.
2b. On UEFI systems without Secure Boot, GRUB behavior is different in a number
of ways including that it will no longer look to /boot/efi/EFI/fedora/grub.cfg
but rather to /boot/grub2/grub.cfg.
Two ways to fix the documentation:
a.) A side bar that says this section doesn't apply to systems with UEFI
firmware (maybe a link to where we give them a hint "how to find out what kind
of firmware you have"), and/or that this section is effectively done by 20.4.2
step 3.
b.) Reorganize 20.4 into discreet BIOS and UEFI sections.
--
You are receiving this mail because:
You are the QA Contact for the bug.
7 years, 11 months