Skip to main content
Topic: Bug reporting (Read 1180 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Bug reporting

What is a correct way to report a potential bug or other problem? I'm sorry if this a stupid question, but I'm afraid I'm not aware of the best way.

Actually there's a reason why I'm asking this, as I've discovered a trouble with world/bluez 5.50-5. It won't start, saying that it can't get to the dbus (log message:
Code: [Select]
 D-Bus setup failed: Connection ":1.2360" is not allowed to own the service "org.bluez" due to security policies in the configuration file
). Previous version from extra works totally OK.

Re: Bug reporting

Reply #1
A  bugtracker is a valid question. We currently only have issue system on our gitea, similar to gitbub issues.

If we were to set up a bugtracker, we would likely need people capable to do a bit of report management.
Since we take a majority of arch PKGBUILD, such management would involve to report/redirect issues found related to upstream arch, for example a missing makedepend, so we get some issues related to PKGBUILD back upstream. Anyhow, the bug team would have to know some details when to report a bug upstream arch, and when it is  an issue on our end.

Please share your thoughts on how artix should handle bug tracking.

Re: Bug reporting

Reply #2
Regarding the dbus issue you reported here, I think it is fixed now. It was likely an arch upstream issue.
I'll sticky this thread.

Re: Bug reporting

Reply #3
Some form of keeping tracks of bugs sounds like a good idea.

Re: Bug reporting

Reply #4
A  bugtracker is a valid question. We currently only have issue system on our gitea, similar to gitbub issues.

If we were to set up a bugtracker, we would likely need people capable to do a bit of report management.
/SNIP/
Please share your thoughts on how artix should handle bug tracking.
The biggest barrier to new user involvement in complex issues is the attitude of the project leaders.  So thank you for your views and attitude. ;)
Good instructions (and even 'hand-holding') for quality bug reports will be parmount but any new user that truly wishes to be involved will gladly learn from positive tutelage. 


Old-timer penguin

Re: Bug reporting

Reply #5
Code: [Select]
$ cat /usr/lib/os-release
NAME="Artix Linux"
PRETTY_NAME="Artix Linux"
ID=artix
BUILD_ID=rolling
ANSI_COLOR="0;36"
HOME_URL="https://www.artixlinux.org/"
DOCUMENTATION_URL="https://wiki.artixlinux.org/"
SUPPORT_URL="https://forum.artixlinux.org/"
BUG_REPORT_URL="https://gitea.artixlinux.org/"
LOGO=artixlinux

BUG_REPORT_URL="https://gitea.artixlinux.org/"  ?

Re: Bug reporting

Reply #6
Quote
If we were to set up a bugtracker, we would likely need people capable to do a bit of report management.
/SNIP/
Please share your thoughts on how artix should handle bug tracking.

I am fine with watching over it.
Man is as good as his tools.