docs-qa December 2020

docs-qa@lists.fedoraproject.org

1 participants
13 discussions

[Bug 1855464] New: how to create and activate swapfiles post-install
by bugzilla＠redhat.com 31 May '24

31 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1855464 Bug ID: 1855464 Summary: how to create and activate swapfiles post-install Product: Fedora Documentation Version: devel Status: NEW Component: docs-requests Assignee: pbokoc(a)redhat.com Reporter: bugzilla(a)colorremedies.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: nobody(a)fedoraproject.org, sparks(a)redhat.com, zach(a)oglesby.co Target Milestone: --- Classification: Fedora This feature means by default there will be no swap partition by default https://fedoraproject.org/wiki/Changes/SwapOnZRAM Some folks might want/need disk based swap. swapfiles: pros: easy to setup; no reboot required; supported on btrfs, ext4, xfs; removable cons: hibernation is sketchy. it should work on ext4, might work on xfs, does not work on btrfs (it can but requires a tool to find an offset, due to the lack of a standard interface across all file systems, for automatically finding the offset) https://lore.kernel.org/linux-btrfs/20200127192548.GA683123@vader/ partition: pros: no limitations cons: takes up space, isn't resizeable; more complicated/risky to create; requires reboot. Notes: The installer's custom partitioning will continue to permit the creation of a swap partition and will configure for hibernation. -- You are receiving this mail because: You are the QA Contact for the bug.

1 2

[Bug 1831542] New: Documentation of PEERNTP variable
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1831542 Bug ID: 1831542 Summary: Documentation of PEERNTP variable Product: Fedora Documentation Version: devel Status: NEW Component: system-administrator's-guide Assignee: pbokoc(a)redhat.com Reporter: mlichvar(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: swadeley(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: The PEERNTP variable, which can be set to "no" in /etc/sysconfig/network in order to disable use of NTP servers provided by the DHCP server, is described in the "Configuring NTP Using ntpd" section, but not in the "Configuring NTP Using the chrony Suite". Both ntp and chrony follow this setting. The documentation should make it clear that NTP servers provided by DHCP are enabled by default. -- You are receiving this mail because: You are the QA Contact for the bug.

1 2

[Bug 1662306] New: TigerVNC Configuration Page out of date
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1662306 Bug ID: 1662306 Summary: TigerVNC Configuration Page out of date Product: Fedora Documentation Version: devel Hardware: x86_64 OS: Linux Status: NEW Component: system-administrator's-guide Severity: medium Assignee: pbokoc(a)redhat.com Reporter: colin.henry(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: swadeley(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Documentation does not reflect current file configuration Version-Release number of selected component (if applicable): Fedora 29 How reproducible: Try and follow the instructions on the configuration page, it tells you to change settings that aren't there. For instance, users are told to edit the and change: ExecStart=/sbin/runuser -l USER -c "/usr/bin/vncserver %i -geometry 1280x1024" PIDFile=/home/USER/.vnc/%H%i.pid Whereas the actual file contains: ExecStart=/usr/bin/vncserver -autokill %i PIDFile=/home/<USER>/.vnc/%H%i.pid Steps to Reproduce: 1. Go to the documentation page: https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide… 2. Install tigervnc-server 3. Look at the configuration file /lib/systemd/system/vncserver@.service Actual results: The files differ significantly, also following the instructions in the configuration file fails to start vnc successfully, but I'll file a bug for that separately. Expected results: Configuration documentation should match the files on the host Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 1878577] New: Grammar Mistake
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1878577 Bug ID: 1878577 Summary: Grammar Mistake Product: Fedora Documentation Version: devel Status: NEW Component: documentation-guide Severity: low Assignee: pbokoc(a)redhat.com Reporter: ali.cruz(a)me.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jhradile(a)redhat.com, pkovar(a)redhat.com, sparks(a)redhat.com, zach(a)oglesby.co Target Milestone: --- Group: fedora_contrib_private Classification: Fedora Created attachment 1714711 --> https://bugzilla.redhat.com/attachment.cgi?id=1714711&action=edit Grammar mistake Document URL: selinux-managing-confined-services-guide Section Number and Name: LOGO Describe the issue: DOUMENTACIÓN de Fedora Suggestions for improvement: Additional information: selinux-managing-confined-services-guide -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 1815635] New: Fedora 31 bluetooth stopped working
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1815635 Bug ID: 1815635 Summary: Fedora 31 bluetooth stopped working Product: Fedora Documentation Version: devel Hardware: x86_64 OS: Linux Status: NEW Component: technical-notes Severity: high Assignee: pbokoc(a)redhat.com Reporter: super250(a)g.uky.edu QA Contact: docs-qa(a)lists.fedoraproject.org CC: wb8rcr(a)arrl.net, zach(a)oglesby.co Target Milestone: --- Classification: Fedora Description of problem: bluetooth stopped working Version-Release number of selected component (if applicable): 31 How reproducible: Steps to Reproduce: 1.\<edit\> /usr/lib/systemd/system/bluetooth.service \<add '-d' to ExecStart line as option to bluetoothd\> 2. systemctl daemon-reload 3. systemctl restart bluetooth (Capture the logs to put in bugzilla report) journalctl -r -u bluetooth > /tmp/bluetoothd.out Actual results: bluetooth.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing Expected results: bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2017-10-04 16:07:40 EDT; 1 day 22h ago Docs: man:bluetoothd(8) Main PID: 27427 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─27427 /usr/libexec/bluetooth/bluetoothd Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 1889931] New: feature request: release notes document status of systemd-homed for install and upgrade to fedora33
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1889931 Bug ID: 1889931 Summary: feature request: release notes document status of systemd-homed for install and upgrade to fedora33 Product: Fedora Documentation Version: devel OS: Linux Status: NEW Component: release-notes Severity: medium Assignee: pbokoc(a)redhat.com Reporter: william.garber(a)att.net QA Contact: docs-qa(a)lists.fedoraproject.org CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net, zach(a)oglesby.co Target Milestone: --- Classification: Fedora Description of problem: would like some easy to find documentation on status of systemd-homed setup for install and/or upgrade to fedora33. i.e. what happens to standard home directory on upgrade. Version-Release number of selected component (if applicable): fedora 32 upgrade to fedora 33 How reproducible: would like to know how this works before installing. Additional info: was not so easy to find on web. should be more easy to find on fedora website. -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 1901486] New: Release notes should mention fixes for older systems impacted by security tightening in F33
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1901486 Bug ID: 1901486 Summary: Release notes should mention fixes for older systems impacted by security tightening in F33 Product: Fedora Documentation Version: devel Status: NEW Component: release-notes Assignee: pbokoc(a)redhat.com Reporter: russ+bugzilla-redhat(a)gloomytrousers.co.uk QA Contact: docs-qa(a)lists.fedoraproject.org CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net, zach(a)oglesby.co Target Milestone: --- Classification: Fedora Description of problem: On booting my system after upgrade from F31 to F33, neither httpd nor dovecot would start. This system is quite an old one that's been upgraded through many versions of Fedora. This appears to be a result of "Strong Crypto Settings - Phase 2" mentioned on https://docs.fedoraproject.org/en-US/fedora/f33/release-notes/sysadmin/Secu… The relevant errors were: * Apache (/var/log/httpd/error_log): [Mon Nov 23 11:44:11.517501 2020] [ssl:emerg] [pid 13680:tid 13680] AH02562: Failed to configure certificate gigalith.gloomytrousers.co.uk:443:0 (with chain), check /etc/pki/tls/certs/localhost.crt [Mon Nov 23 11:44:11.517525 2020] [ssl:emerg] [pid 13680:tid 13680] SSL Library Error: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small This cert was 1024 bit, first generated in 2010. The fix was to remove /etc/pki/tls/certs/localhost.crt and /etc/pki/tls/private/localhost.key then run /usr/libexec/httpd-ssl-gencerts. * Dovecot (journal): Nov 23 12:35:27 gigalith.gloomytrousers.co.uk dovecot[31160]: config: Warning: please set ssl_dh=</etc/dovecot/dh.pem Nov 23 12:35:27 gigalith.gloomytrousers.co.uk dovecot[31160]: config: Warning: You can generate it with: dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /etc/dovecot/dh.pem /etc/dovecot/dh.pem was present, dating from from 2013. The recommended fix did NOT work (I recall having run this in the past) - it just generated an identical file. The actual fix (stumbled across in bug 1882939) was to regenerate the DH params with `openssl dhparam -out /etc/dovecot/dh.pem 4096` (this took 32 mins on my machine!) I suspect Exim might also have similar problems for some people, although I didn't have a problem (my cert was 2048 bit from 2010, although I think I generated this in a non-default way at the time). The fix in this case would be to remove /etc/pki/tls/certs/exim.pem and /etc/pki/tls/private/exim.pem then run /usr/libexec/exim-gen-cert. I suggest these workarounds which might be required for older systems be documented on https://docs.fedoraproject.org/en-US/fedora/f33/release-notes/sysadmin/Secu… - along with anything else that might suffer from similar issues. -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 1831872] New: Legacy DNF enable repo documentation from gnome-wiki
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1831872 Bug ID: 1831872 Summary: Legacy DNF enable repo documentation from gnome-wiki Product: Fedora Documentation Version: devel Status: NEW Component: documentation-guide Assignee: pbokoc(a)redhat.com Reporter: csiterallat(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jhradile(a)redhat.com, pkovar(a)redhat.com, sparks(a)redhat.com, stickster(a)gmail.com, zach(a)oglesby.co Target Milestone: --- Classification: Fedora Document URL: https://fedoraproject.org/wiki/StackTraces#gdb Section Number and Name: nstalling debuginfo RPMs using DNF Describe the issue: This command is doesn't work, it's Legacy! dnf --enablerepo=fedora-debuginfo --enablerepo=updates-debuginfo install <pkg-spec>-debuginfo Suggestions for improvement: TRUE ENABLE REPO COMMAND ON FEDORA 32: sudo dnf config-manager --set-enabled fedora-debuginfo updates-debuginfo Additional information: This link is come frome gnome-wiki (https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Dist…) I try to install debuginfo packages for totem, but this documentation is not so helpful :( -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 1850288] New: Page Missing - v22 - multiboot-guide - "6.3.2.2. Reinstalling GRUB on BIOS systems."
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1850288 Bug ID: 1850288 Summary: Page Missing - v22 - multiboot-guide - "6.3.2.2. Reinstalling GRUB on BIOS systems." Product: Fedora Documentation Version: devel Status: NEW Component: multiboot-guide Assignee: pbokoc(a)redhat.com Reporter: sy(a)josiahluscher.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: me(a)petetravis.com Target Milestone: --- Classification: Fedora Description of problem: Entire documentation section missing. Version-Release number of selected component (if applicable): v22 How reproducible: Very Easy Steps to Reproduce: 1. Open the following page with web browser: https://docs.fedoraproject.org/en-US/Fedora/22/html/Multiboot_Guide/GRUB-re… Actual results: Header is displayed with no content. Expected results: Enlightenment(?) Additional info: My server won't boot! Plasse HALP! [Sad Human] -- Thanks! -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 1859811] New: The appdata guidance is out of date
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1859811 Bug ID: 1859811 Summary: The appdata guidance is out of date Product: Fedora Documentation Version: devel Status: NEW Component: packager-guide Assignee: pbokoc(a)redhat.com Reporter: t0dd(a)protonmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: pkovar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: If you go looking for guidance for how to package RPMs, there is really no better guide than what Fedora produces. It is therefore that much more important that Fedora keeps up with Freedesktop.org standards. The problem is that the "Packaging Guidelines for AppData Files" is out of date and wrong. Version-Release number of selected component (if applicable): https://docs.fedoraproject.org/en-US/packaging-guidelines/AppData/ As of July 23, 2020 Actual results: Let's just tick off the problems (just a few, it needs a revamp) - .metainfo.xml files are now preferred and .appdata.xml is deprecated - example .xml file has wrong component type and id """ <component type="desktop"> <id>comical.desktop</id> """ ...that should be... """ <component type="desktop-application"> <id>comical</id> """ ...better yet, that should be... """ <component type="desktop-application"> <id>com.example.Comical</id> """ It's also missing the launchable tag """ <launchable type="desktop-id">com.example.Comical.desktop</lauchable> """ Expected results: See above. Additional info: https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html -- You are receiving this mail because: You are the QA Contact for the bug.

1 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa December 2020