Difference between revisions of "Where to Report Bugs"

From PINE64
Jump to navigation Jump to search
 
(6 intermediate revisions by one other user not shown)
Line 3: Line 3:
== Overview ==
== Overview ==


Issues should '''only''' be reported in the correct '''bug trackers''', not in the community chats. The reasons for this can be found in the following information box.
Issues should '''only''' be reported in the correct '''bug trackers''', not in the community chats. The following list is a selection of common bug trackers.
 
{{hint|Why shouldn't I report issues in the community chats?
 
* Development takes place in platforms such as GitLab, sourcehut and Github with a certain procedure (issue reports, commits, linking to the issues and marking them solved). Reports in the chat are not designated to be a part of that process (until an advanced artificial intelligence some day can evaluate them and automatically ask the user for more details).
* Talking about an issue and workarounds carries the discussion further away from the actual development and leads to discussions in forums and chatrooms.
* Shared and accepted workarounds don't find their way back into the code and may be accepted as "tolerable evil".
* Bug reports in chats are getting scrolled out, repeated and as a result repetitive for everyone involved and leads to future users with the same or similar issues not getting pointed to the correct places anymore.
* It is expected that people mentioning issues will also report them properly. Conversations about bugs without reporting them makes users and developers think it is reported already and as a result the issue will never be reported (and therefore not fixed).
* Unlike many commercial and/or proprietary projects, developers are part of the open community and there is therefore no need of having to solve issues via side channels.
}}


== PinePhone and PinePhone Pro ==
== PinePhone and PinePhone Pro ==
Line 19: Line 9:
Issues with the PinePhone and the PinePhone Pro can be reported on the following bug trackers (selection).
Issues with the PinePhone and the PinePhone Pro can be reported on the following bug trackers (selection).


===Bootloaders and Firmwares===
===Operating Systems and Distributions===
* U-Boot: TBD
* Tow-Boot: https://github.com/Tow-Boot/Tow-Boot/issues?q=
* Levinboot: https://gitlab.com/DeltaGem/levinboot/-/issues?sort=created_date&state=all
* Crust: https://github.com/crust-firmware/crust/issues?q=is%3Aissue
* Pinephone Modem SDK: https://github.com/Biktorgj/pinephone_modem_sdk/issues?q=is%3Aissue
 
===User Interfaces===
* Plasma Mobile: https://invent.kde.org/plasma/plasma-mobile/-/issues
** Plasma Mobile applications: https://invent.kde.org/groups/plasma-mobile/-/issues
* Phosh: https://gitlab.gnome.org/World/Phosh/phosh/-/issues?scope=all&state=all
** Phosh projects: https://gitlab.gnome.org/World/Phosh
 
===Operating Systems===
* Arch Linux ARM (DanctNIX): https://github.com/dreemurrs-embedded/Pine64-Arch/issues?q=is%3Aissue
* Arch Linux ARM (DanctNIX): https://github.com/dreemurrs-embedded/Pine64-Arch/issues?q=is%3Aissue
* ExpidusOS: https://github.com/orgs/ExpidusOS/repositories
* ExpidusOS: https://github.com/orgs/ExpidusOS/repositories
Line 57: Line 34:
* Swmo: https://todo.sr.ht/~mil/sxmo-tickets
* Swmo: https://todo.sr.ht/~mil/sxmo-tickets
* Ubuntu Touch: https://gitlab.com/ubports/community-ports/pinephone/-/issues?sort=created_date&state=all
* Ubuntu Touch: https://gitlab.com/ubports/community-ports/pinephone/-/issues?sort=created_date&state=all
===User Interfaces===
* Plasma Mobile: https://invent.kde.org/plasma/plasma-mobile/-/issues
** Plasma Mobile applications: https://invent.kde.org/groups/plasma-mobile/-/issues
* Phosh: https://gitlab.gnome.org/World/Phosh/phosh/-/issues?scope=all&state=all
** Phosh projects: https://gitlab.gnome.org/World/Phosh
===Bootloaders and Firmwares===
* U-Boot: TBD
* Tow-Boot: https://github.com/Tow-Boot/Tow-Boot/issues?q=
* Levinboot: https://gitlab.com/DeltaGem/levinboot/-/issues?sort=created_date&state=all
* Crust: https://github.com/crust-firmware/crust/issues?q=is%3Aissue
* Pinephone Modem SDK: https://github.com/Biktorgj/pinephone_modem_sdk/issues?q=is%3Aissue


===Hardware Issues===
===Hardware Issues===
The page [[PinePhone Hardware Issues]] can be used to track known problems with the hardware (and how to fix them). If you're not exactly sure how to describe the issue, try the discussion tab for that page, or other community resources.
=== Accessories ===
TBD
TBD
== PineTime ==
* InfiniTime: https://github.com/InfiniTimeOrg/InfiniTime/issues?q=is%3Aissue
== PineTab ==
* Arch Linux ARM: https://github.com/dreemurrs-embedded/Pine64-Arch/issues?q=is%3Aissue+label%3A%22device%3A+pinetab%22
* Manjaro ARM: https://gitlab.manjaro.org/manjaro-arm/issues
* Mobian: https://gitlab.com/mobian1/issues
* postmarketOS: https://gitlab.com/postmarketOS/pmaports/-/issues?sort=created_date&state=opened&label_name%5B%5D=device-pine64-pinetab
* Ubuntu Touch: https://gitlab.com/ubports/community-ports/pinephone/-/issues?sort=created_date&state=all

Latest revision as of 18:26, 2 July 2022

Reporting bugs is a great way to contribute and to help bringing order at managing and solving issues.

Overview

Issues should only be reported in the correct bug trackers, not in the community chats. The following list is a selection of common bug trackers.

PinePhone and PinePhone Pro

Issues with the PinePhone and the PinePhone Pro can be reported on the following bug trackers (selection).

Operating Systems and Distributions

User Interfaces

Bootloaders and Firmwares

Hardware Issues

The page PinePhone Hardware Issues can be used to track known problems with the hardware (and how to fix them). If you're not exactly sure how to describe the issue, try the discussion tab for that page, or other community resources.

Accessories

TBD

PineTime

PineTab

Retrieved from "https://wiki.pine64.org/index.php?title=Where_to_Report_Bugs&oldid=13240"