[Bug 1855464] New: how to create and activate swapfiles post-install
by bugzilla＠redhat.com
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.
2 weeks, 3 days
[Bug 1831542] New: Documentation of PEERNTP variable
by bugzilla＠redhat.com
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.
3 weeks, 6 days
[Bug 1662306] New: TigerVNC Configuration Page out of date
by bugzilla＠redhat.com
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-gui...
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.
3 weeks, 6 days
[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.
4 weeks
[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.
4 weeks
[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.
4 weeks
[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.
4 weeks
[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.
4 weeks