https://bugzilla.redhat.com/show_bug.cgi?id=1997970
Bug ID: 1997970
Summary: Typo on release page of a package on
package.fedoraproject.org
Product: Fedora Documentation
Version: devel
Status: NEW
Component: homepage
Assignee: pbokoc(a)redhat.com
Reporter: eva.timbs(a)you-spam.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dimitris(a)glezos.com, zach(a)oglesby.co
Target Milestone: ---
Classification: Fedora
When clicking on a release of a package the new site, e.g. [1], displays a back
link near the top with the description "↵ Retrun to the main page of <pkg>".
Note the misspelled "Return".
[1] https://packages.fedoraproject.org/pkgs/kernel/kernel/fedora-rawhide.html
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2011723
Bug ID: 2011723
Summary: Backport fix to ps man page documentation
Product: Fedora Documentation
Version: devel
OS: Linux
Status: NEW
Component: docs-requests
Severity: medium
Assignee: pbokoc(a)redhat.com
Reporter: mallika.bachan(a)gmail.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
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2011723
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.
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=2021927
Bug ID: 2021927
Summary: Updates and enhancements needed
Product: Fedora Documentation
Version: devel
Status: NEW
Component: freeipa-guide
Severity: medium
Assignee: pbokoc(a)redhat.com
Reporter: ricky.tigg(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: mkosek(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1841070
--> https://bugzilla.redhat.com/attachment.cgi?id=1841070&action=edit
Observations and suggestions
Hello. Here is a well composed and written document that has aged without
having suffered hard the passage of time. Well done. According to my
observations, some few sections deserve to be up-to-date as they lead the
reader to conclude that the guide is obsolete and therefore do not apply to
contemporary release of Fedora products. Who knows, maybe the required
rectifications could be produced in correlation with the up-coming releases of
Fedora 36 products – that’s Fedora 2x18!
Source: https://docs.fedoraproject.org | Fedora 18 | Edition 3.1.5 | Ella Deon
Lackey | Release year: 2012 | Version number of component freeipa this document
was made against: 2.2.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2021927
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.
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1790615
Bug ID: 1790615
Summary: AppStream (formerly AppData) packaging guidelines use
outdated terms and example code
Product: Fedora Documentation
Version: devel
Status: NEW
Component: packager-guide
Assignee: pbokoc(a)redhat.com
Reporter: andrew(a)tosk.in
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pkovar(a)redhat.com
Target Milestone: ---
Classification: Fedora
I'm referring to the docs at "Packaging Guidelines for AppData Files"
<https://docs.fedoraproject.org/en-US/packaging-guidelines/AppData/>
The AppStream project has made a number of changes since these Fedora
guidelines were written, and the conflicting information confused me at first,
as I looked up how to add AppStream metadata to a new package I'm working on...
* In the Fedora guidelines, the second sentence
("Installed .appdata.xml files MUST follow the AppData specification page.")
links to
<http://people.freedesktop.org/~hughsient/appdata/>
but this URL now redirects to
<https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html#se…>
* As far as I can tell, the AppStream specification no longer
uses the filename to distinguish between applications and
addons, and all AppStream metadata files should now be named
.metainfo.xml. Files for GUI applications are no longer named
.appdata.xml.
See
<https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html#se…>
* The example .appdata.xml file in the Fedora guidelines is
therefore also out of date. The current AppStream spec,
for example, states that the component type should be
"desktop-application" instead of just "desktop".
Unless I'm misunderstanding something, the Fedora guidelines here will need to
be rewritten somewhat.
--
You are receiving this mail because:
You are the QA Contact for the bug.