docs-qa June 2017

docs-qa@lists.fedoraproject.org

1 participants
69 discussions

[Bug 1420569] New: Fedora 25 networking-guide section 9.2 has wrong package name for the dhcp-server package.
by bugzilla＠redhat.com 11 Jul '17

11 Jul '17

https://bugzilla.redhat.com/show_bug.cgi?id=1420569 Bug ID: 1420569 Summary: Fedora 25 networking-guide section 9.2 has wrong package name for the dhcp-server package. Product: Fedora Documentation Version: devel Component: networking-guide Severity: low Assignee: swadeley(a)redhat.com Reporter: stolidmollusc(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: swadeley(a)redhat.com Description of problem: Wrong package name given in Section 9.2. Configuring a DHCP Server. The document instructs users to install package 'dhcp'; the correct package name is 'dhcp-server'. Version-Release number of selected component (if applicable): 25 How reproducible: Read section 9.2 at https://docs.fedoraproject.org/en-US/Fedora/25/html/Networking_Guide/sec-dh… Steps to Reproduce: 1. See the first few lines about how to install a dhcp server. Actual results: The document states: "The dhcp package contains an Internet Systems Consortium (ISC) DHCP server. Install the package as root: ~]# dnf install dhcp Installing the dhcp package creates a file, /etc/dhcp/dhcpd.conf, ..." Expected results: All mentions of the 'dhcp' package should be changed to the 'dhcp-server' package. I found just the 3 instances quoted above. Additional info: At least since Fedora 24, 'dhcp-server' is the package that provides the documented component. -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 1322076] New: uefi secure boot, update examples that are fedora specific
by Red Hat Bugzilla 11 Jul '17

11 Jul '17

https://bugzilla.redhat.com/show_bug.cgi?id=1322076 Bug ID: 1322076 Summary: uefi secure boot, update examples that are fedora specific Product: Fedora Documentation Version: devel Component: system-administrator's-guide Severity: low Assignee: swadeley(a)redhat.com Reporter: bugzilla(a)colorremedies.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: swadeley(a)redhat.com Super low priority. The existing examples aren't Fedora specific and are more verbose than on a Fedora system. https://docs.fedoraproject.org/en-US/Fedora/23/html/System_Administrators_G… Fedora 23, system without secure boot: # keyctl list %:.system_keyring 1 key in keyring: 436069891: ---lswrv 0 0 asymmetric: Fedora kernel signing key: 123842f3d8cc3f140fa50a22fc9bc014cefcf2bf Fedora 23, system with secure boot enabled: # keyctl list %:.system_keyring 4 keys in keyring: 57620495: ---lswrv 0 0 asymmetric: Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53 17001967: ---lswrv 0 0 asymmetric: Fedora kernel signing key: 123842f3d8cc3f140fa50a22fc9bc014cefcf2bf 462910956: ---lswrv 0 0 asymmetric: Fedora Secure Boot CA: fde32599c2d61db1bf5807335d7b20e4cd963b42 837240830: ---lswrv 0 0 asymmetric: Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4 -- You are receiving this mail because: You are the QA Contact for the bug.

2 7

[Bug 982899] New: 7.3.1. Establishing a Wired (Ethernet) Connection
by Red Hat Bugzilla 11 Jul '17

11 Jul '17

https://bugzilla.redhat.com/show_bug.cgi?id=982899 Bug ID: 982899 Summary: 7.3.1. Establishing a Wired (Ethernet) 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.1: Default connection no longer called 'em1' No field for 'connection name' you can add new settings for the network under different profiles by selecting 'add profile...' you can remove/reset a profile by going to the 'options' button under the profile and selecting the 'reset' item on the left, and then choosing to either 'reset' or 'forget' -- You are receiving this mail because: You are the QA Contact for the bug.

2 6

[Red Hat Bugzilla] Your Outstanding Requests
by bugzilla＠redhat.com 26 Jun '17

26 Jun '17

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. (1000 days old) https://bugzilla.redhat.com/show_bug.cgi?id=1124344 https://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…

1 0

[Red Hat Bugzilla] Your Outstanding Requests
by bugzilla＠redhat.com 19 Jun '17

19 Jun '17

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. (993 days old) https://bugzilla.redhat.com/show_bug.cgi?id=1124344 https://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…

1 0

[Bug 1461375] New: SAGE | Contact U.S. | 8443134859 | Sage PeachTREE
by bugzilla＠redhat.com 14 Jun '17

14 Jun '17

https://bugzilla.redhat.com/show_bug.cgi?id=1461375 Bug ID: 1461375 Summary: SAGE | Contact U.S. | 8443134859 | Sage PeachTREE Product: Fedora Documentation Version: devel Component: readme Severity: high Assignee: stickster(a)gmail.com Reporter: poisner(a)ip6.pp.ua QA Contact: docs-qa(a)lists.fedoraproject.org CC: stickster(a)gmail.com, zach(a)oglesby.co Introduction Explain one or two situations in which a user would need to use the process you will describe. Don’t explain the process here. The point of the introduction is to introduce the concepts the reader will put to use later, and to explain why it’s even useful to begin with. Here’s a short example for an article about setting the hostname: “The computer’s hostname helps distinguish the system on a network. If you have appropriate privileges, you can set your system’s hostname to something that helps you identify it in your home or office network.” If there’s anything the user needs to know in order to use the process, describe it here. For instance, in the hostname example, you would describe that only lowercase letters a-z, numerals 0-9, or the dash “-” may appear in a hostname. You might also tell them whether they need to be on a specific Fedora edition or version. Running the most common process Describe the process one step at a time. Describe the simplest and most common usage first. Assume the reader will try the first process they see. https://blueprints.launchpad.net/adblockforchrome/+spec/bolggerboltahe Use a graphical interface as the first and most common process. Document the default installation wherever possible. Use a screenshot, and don’t use your own customized user account. Use a fresh user account so it has a non-customized and stock appearance. You may follow this case with a command-line equivalent in an additional section. Running a more complex or less common process You can describe a less common process as well. In this case, describe why it is useful. Be honest with yourself about whether this process is actually useful. Don’t use the article as a way of showing off your deep knowledge of a tool. Conclusion If there are common references, you can include them at the bottom. Do not point to dated information. Only use resources that are unlikely to change, are undated, or are well maintained.Fedora 25 is the first of the major Linux distros to employ the Wayland graphics stack by default. Wayland is one of the biggest low-level changes to hit Linux distros in recent memory and what's most remarkable at least when it comes to Fedora 25 is the move is almost totally transparent. Provided your graphics card is supported, you're unlikely to even notice that you're using Wayland. That's partly a testament to the Wayland project's efforts but also to Fedora in particular, a result of the Fedora developers' decision to wait before making the switch. https://blueprints.launchpad.net/account-plugin-github/+spec/veryspeacialch… It's been disappointing to see Wayland postponed time after time for the past few Fedora releases, but the waiting has paid off in stability and seamlessness. I haven't hit any major bugs or had any apps that won't work (some of this is no doubt due to XWayland, which is the fallback X server that runs in situations where Wayland isn't supported). I have, on the other hand, noticed the default GNOME desktop in Fedora is considerably snappier, particularly animations. That doesn't mean everything is perfect in the world of Wayland. I like to use Redshift or f.lux to tint-shift my screen at night as I find that much easier on my eyes. Neither application seems to work under Wayland thanks to changes in the security model of Wayland versus X. Fortunately it seems Redshift-like features may be coming straight to GNOME itself. In the meantime, if you want to get tint-shifting working in Fedora 25 with GNOME, there's a COPR repo available that adds some new colour profiles to GNOME and a dawn/dusk timer to switch between them. There's some good instructions here. Other than the tint-shift problem, my transition to Wayland has been smooth and largely uneventful. Some people with other graphic card/driver combos have reported problems with video playback but I haven't run into that in my testing (mplayer works fine on my Lenovo and a Dell XPS 13 I happened to be testing when Fedora 25 came out). While the move to Wayland is definitely the big news in this release of Fedora, it's not the only thing that's new by any means. There's a major GNOME update, a brand new kernel and some changes in the Fedora Next lineup. The most visually noticeable thing is the update to GNOME 3.22, which has some nice new features in the Files app (the application formerly known as Nautilus). There's a batch-renaming tool that makes it easy to add a prefix, suffix, or do date-based renaming of files. Files now includes a built-in file compression tool so when you double-click a .zip file it just extracts the contents to a folder without opening File Roller.https://blueprints.launchpad.net/bugzilla/+spec/moment-ago-after-ser… This release also sees the GNOME extensions API being declared "stable". That's mostly good news for extension developers, but it also means that updates will no longer run the risk of breaking all the extensions you rely on to customise GNOME Shell. The GNOME Software app continues to improve too. GNOME 3.22 sees Software adding better support for Flatpak apps. If you haven't had a chance to dive into the world of Flatpak apps yet, Fedora 25 makes a good platform to experiment on. Not only can you install Flatpaks using the GNOME Software app, with Fedora 25 you can even search or browse specifically for Flatpaks via Software. You'll now be able to see the source information and sandboxing status of Flatpaks before you install them. Flatpaks are still a bit rough around the edges and the very tight sandboxing model that governs them can mean that Flatpak versions of your favourite apps are missing a few features, but they're getting closer to usable status. The other big news in GNOME Software actually arrived in the previous Fedora release – system upgrades from the Software apps. I was able to upgrade from Fedora 24 to 25 by clicking a button in Software and everything just worked. Long-time Fedora users will know that this is nothing short of a miracle. I should note that I run a mostly stock install of Fedora with few GNOME extensions or other customisations. Most of the system update problems I've seen people mentioning on forums and bug reports around the web come from library conflicts so the more stuff you have installed the greater the chances GNOME Software won't work. Still, it's worth a try. From what I've seen, its one weak point is a lack of debugging messages when things do go wrong. If it doesn't work I'd jump over to the terminal and try using DNF to see what's causing the problem before you resort to the old Fedora nuke and pave upgrade path. Along with Wayland and a new version of GNOME, this Fedora is notable for the update to Linux kernel 4.8.6, which should go a long way to fixing many of the Skylake bugs that cropped up with Fedora 24. -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Red Hat Bugzilla] Your Outstanding Requests
by bugzilla＠redhat.com 12 Jun '17

12 Jun '17

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. (986 days old) https://bugzilla.redhat.com/show_bug.cgi?id=1124344 https://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…

1 0

[Red Hat Bugzilla] Your Outstanding Requests
by bugzilla＠redhat.com 05 Jun '17

05 Jun '17

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. (979 days old) https://bugzilla.redhat.com/show_bug.cgi?id=1124344 https://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…

1 0

[Bug 1457890] New: Incorrect quoting of efibootmgr command-line example
by bugzilla＠redhat.com 01 Jun '17

01 Jun '17

https://bugzilla.redhat.com/show_bug.cgi?id=1457890 Bug ID: 1457890 Summary: Incorrect quoting of efibootmgr command-line example Product: Fedora Documentation Version: devel Component: multiboot-guide Assignee: me(a)petetravis.com Reporter: dinechin(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: me(a)petetravis.com Description of problem: The page https://docs.fedoraproject.org/en-US/Fedora/22/html/Multiboot_Guide/GRUB-re… shows the following command for re-creating the Fedora boot entry: # efibootmgr -c -w -L Fedora -d /dev/sda -p 2 -l \EFI\fedora\shim.efi I naively copy-pasted that. And it does not work, because of \ not being escaped: # echo efibootmgr -c -w -L Fedora -d /dev/sda -p 2 -l \EFI\fedora\shim.efi efibootmgr -c -w -L Fedora -d /dev/sda -p 2 -l EFIfedorashim.efi The example should be changed to: # efibootmgr -c -w -L Fedora -d /dev/sda -p 2 -l '\EFI\fedora\shim.efi' -- You are receiving this mail because: You are the QA Contact for the bug.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa June 2017