[Bug 1878577] New: Grammar Mistake
by bugzilla＠redhat.com
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 month
[Bug 1901486] New: Release notes should mention fixes for older
systems impacted by security tightening in F33
by bugzilla＠redhat.com
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/Se...
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/Se...
- 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 month
[Bug 1859811] New: The appdata guidance is out of date
by bugzilla＠redhat.com
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 month
[Bug 1815635] New: Fedora 31 bluetooth stopped working
by bugzilla＠redhat.com
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 month
[Bug 1831872] New: Legacy DNF enable repo documentation from
gnome-wiki
by bugzilla＠redhat.com
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/Di...)
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 month
[Bug 1889931] New: feature request: release notes document status of
systemd-homed for install and upgrade to fedora33
by bugzilla＠redhat.com
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 month
[Bug 2021927] New: Updates and enhancements needed
by bugzilla＠redhat.com
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
1 month