docs-qa March 2020

docs-qa@lists.fedoraproject.org

1 participants
25 discussions

[Bug 1802159] New: Default login for Fedora core os either undocumented or missing
by bugzilla＠redhat.com 25 Jun '20

25 Jun '20

https://bugzilla.redhat.com/show_bug.cgi?id=1802159 Bug ID: 1802159 Summary: Default login for Fedora core os either undocumented or missing Product: Fedora Documentation Version: devel Status: NEW Component: install-guide Assignee: pbokoc(a)redhat.com Reporter: hadmut(a)danisch.de QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co Target Milestone: --- Classification: Fedora Description of problem: I was just giving Fedora Core OS a first try and installed it from the ISO image to the bare metal following the instructions at https://docs.fedoraproject.org/en-US/fedora-coreos/bare-metal/ Since I didn't have an ignition file yet, I just ran sudo coreos-installer install /dev/sda with out the ignition file, and this worked. After rebooting, the system came up, but I could not login on the console. The Docs do not contain a hint about what username and what password to use. When i mounted the file system on a different linux machine I saw that there is a core use with no password set. Since I'm not familiar with ostree, I wasn't sure whether I was breaking anything if I just changed the password in the /etc/shadow on that disk, and this is probably not the intended way to use the system. You end up with having a system that's of no use since you can't login. Either the docs should tell how to login after plain install, or coreos-installer should prevent from installing a system with no use and no login. regards -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 1706205] New: fedora 30 kde live image contains the squashfs image from fedora 27 and its gnome
by bugzilla＠redhat.com 26 May '20

26 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1706205 Bug ID: 1706205 Summary: fedora 30 kde live image contains the squashfs image from fedora 27 and its gnome Product: Fedora Documentation Version: devel Status: NEW Component: about-fedora Assignee: pbokoc(a)redhat.com Reporter: rob.verduijn(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: stickster(a)gmail.com, zach(a)oglesby.co Target Milestone: --- Classification: Fedora Description of problem: When booting the recovery option you get the squashfs image from the image found in the LiveOS folder This is a gnome image (a bit strange on a kde live image) And it is from fedora27 Version-Release number of selected component (if applicable): fedora 30 kde live image iso How reproducible: boot the recovery option from that iso and you will see Steps to Reproduce: 1. 2. 3. Actual results: gnome squashfs image from fedora27 Expected results: kde squashfs image from fedora30 Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

1 2

[Red Hat Bugzilla] Your Outstanding Requests
by bugzilla＠redhat.com 30 Mar '20

30 Mar '20

The following is a list of bugs or attachments to bugs in which a user has been waiting more than 3 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 tomorrow if these requests are still outstanding, or if there are any new requests where users have been waiting more than 3 days for your response. review ------ Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (2009 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 29 Mar '20

29 Mar '20

The following is a list of bugs or attachments to bugs in which a user has been waiting more than 3 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 tomorrow if these requests are still outstanding, or if there are any new requests where users have been waiting more than 3 days for your response. review ------ Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (2008 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 26 Mar '20

26 Mar '20

The following is a list of bugs or attachments to bugs in which a user has been waiting more than 3 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 tomorrow if these requests are still outstanding, or if there are any new requests where users have been waiting more than 3 days for your response. review ------ Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (2005 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 25 Mar '20

25 Mar '20

The following is a list of bugs or attachments to bugs in which a user has been waiting more than 3 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 tomorrow if these requests are still outstanding, or if there are any new requests where users have been waiting more than 3 days for your response. review ------ Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (2004 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 24 Mar '20

24 Mar '20

The following is a list of bugs or attachments to bugs in which a user has been waiting more than 3 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 tomorrow if these requests are still outstanding, or if there are any new requests where users have been waiting more than 3 days for your response. review ------ Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (2003 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 23 Mar '20

23 Mar '20

The following is a list of bugs or attachments to bugs in which a user has been waiting more than 3 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 tomorrow if these requests are still outstanding, or if there are any new requests where users have been waiting more than 3 days for your response. review ------ Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (2002 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 22 Mar '20

22 Mar '20

The following is a list of bugs or attachments to bugs in which a user has been waiting more than 3 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 tomorrow if these requests are still outstanding, or if there are any new requests where users have been waiting more than 3 days for your response. review ------ Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (2001 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 1815635] New: Fedora 31 bluetooth stopped working
by bugzilla＠redhat.com 20 Mar '20

20 Mar '20

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 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa March 2020