Skip to main content ↑ ↓
Topic: Bug reporting (Read 22646 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 –
Quote from: artoo – on
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.

Re: Bug reporting

Reply #7 –
Quote from: uhmzilighase – on
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. 




Totally agreed about the importance of the attitude of the project leaders. Attitude is everything.

Re: Bug reporting

Reply #8 –
so OP-Question still valid, where do we report bugs? when i searched the forum i got here..

gitea has registering disabled, and for the few repos i checked it did not seem to be any usage of the issues system..

without some kind of working bugtracker everyone will keep hitting the same issues and progress with be slower..

anyway the annoying bugger i found was "restart remote machine over ssh" and it ends up with a broken pipe instead of disconnect like it should.. (openrc as init system)

anyway same type of issue on gentoo (like a decade back..) https://bugs.gentoo.org/259183

hopefully someone will have time to look at that before i got a hole in my schedule to mess with this, especially since there seems to be no official way (bugtracker) to send the info back upstream to you, so the issue goes away and not just get worked around for me..
Why did i choose Linux so many years ago?
< - Privacy - Stability - Usability - >
 

Re: Bug reporting

Reply #9 –
Oh yes, sorry, that was a joke, and it's been updated now if you look at the file:
HOME_URL="https://www.artixlinux.org/"
DOCUMENTATION_URL="https://wiki.artixlinux.org/"
SUPPORT_URL="https://forum.artixlinux.org/"
BUG_REPORT_URL="https://bugs.artixlinux.org/"
(The new BUG_REPORT_URL goes to a 404 if you get past the certificate error warning)
man pacman quote:
"Bugs? You must be kidding; there are no bugs in this software."
You can open a topic on the forum / artix general mailing list / irc to discuss the problem.

Re: Bug reporting

Reply #10 –
Quote from: ####### – on
Oh yes, sorry, that was a joke, and it's been updated now if you look at the file:
HOME_URL="https://www.artixlinux.org/"
DOCUMENTATION_URL="https://wiki.artixlinux.org/"
SUPPORT_URL="https://forum.artixlinux.org/"
BUG_REPORT_URL="https://bugs.artixlinux.org/"
(The new BUG_REPORT_URL goes to a 404 if you get past the certificate error warning)
man pacman quote:
"Bugs? You must be kidding; there are no bugs in this software."
You can open a topic on the forum / artix general mailing list / irc to discuss the problem.


had totally missed that we had a mailing list + archive, that works fine for me..
Why did i choose Linux so many years ago?
< - Privacy - Stability - Usability - >

Re: Bug reporting

Reply #11 –
Hello.
I think in last versions of Artix are some bugs.

Re: Bug reporting

Reply #12 –
Quote from: GM2405 – on
Hello.
I think in last versions of Artix are some bugs.


First of all artix does not use busybox. And as can be clearly seen in that image it says ventoy in the error. Not an artix issue talk to the ventoy people.
Chris Cromer

Re: Bug reporting

Reply #13 –
Yes, it's Ventoy but until 20210628 (28 of June) all worked fine.
After something changed in Artix installer.

Re: Bug reporting

Reply #14 –
Our ISOs work just fine, they can be flashed to pen drive or dvd and they work great. Ventoy does not work with all distros and ISOs, and it is not our responsibility to ensure it does. This is a ventoy issue and should be fixed on their side. They have to make their software work with our ISOs, not the other way around. There are reports of issues for various distros in the ventoy github issues section, not just Artix. Just read their issues on github, problems with Fedora, Arch Linux, Manjaro, Ubuntu, etc.

It is an interesting software... but it is has a ton of problems and issues.
Chris Cromer