Artix Linux Forum

General Category => Discussion about Artix => Topic started by: LonelyPenguin on 14 January 2019, 09:19:09

Title: Bug reporting
Post by: LonelyPenguin on 14 January 2019, 09:19:09
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.
Title: Re: Bug reporting
Post by: artoo on 14 January 2019, 15:57:59
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.
Title: Re: Bug reporting
Post by: artoo on 14 January 2019, 16:13:22
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.
Title: Re: Bug reporting
Post by: Relih on 17 January 2019, 15:31:05
Some form of keeping tracks of bugs sounds like a good idea.
Title: Re: Bug reporting
Post by: uhmzilighase on 15 February 2019, 04:33:27
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. 


Title: Re: Bug reporting
Post by: ####### on 05 September 2019, 04:52:48
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/"  ?
Title: Re: Bug reporting
Post by: SGOrava on 05 September 2019, 16:42:08
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.
Title: Re: Bug reporting
Post by: Pebble on 25 December 2020, 16:47:14
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.
Title: Re: Bug reporting
Post by: BjornS on 25 July 2021, 08:37:49
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..
Title: Re: Bug reporting
Post by: ####### on 25 July 2021, 13:31:05
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.
Title: Re: Bug reporting
Post by: BjornS on 27 July 2021, 10:22:48
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..
Title: Re: Bug reporting
Post by: GM2405 on 27 July 2021, 20:03:52
Hello.
I think in last versions of Artix are some bugs.
(https://thumbs4.imagebam.com/17/60/f2/ME2DSKW_t.png) (https://www.imagebam.com/view/ME2DSKW)
Title: Re: Bug reporting
Post by: Chris Cromer on 29 July 2021, 04:15:27
Hello.
I think in last versions of Artix are some bugs.
(https://thumbs4.imagebam.com/17/60/f2/ME2DSKW_t.png) (https://www.imagebam.com/view/ME2DSKW)

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.
Title: Re: Bug reporting
Post by: GM2405 on 30 July 2021, 21:52:52
Yes, it's Ventoy but until 20210628 (28 of June) all worked fine.
After something changed in Artix installer.
Title: Re: Bug reporting
Post by: Chris Cromer on 31 July 2021, 01:14:51
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.
Title: Re: Bug reporting
Post by: GM2405 on 31 July 2021, 10:10:37
I don't know man. I checked a lot of Linux distros: Fedora 34, openSUSE Tumbleweed, Ubuntu 16.04/18.04/20.04/21.04/21.10, Mx Linux 19.4.1, AntiX 19.4, Linux Mint 20.2, Debian 11 Testing, Devuan Chimaera 4.0 Alpha, Manjaro 21.0.7, Artix, ArchLab, RebornOS, Void Linux with different kernels - start from 4.9 and up to 5.13. All OS’es with different DE’s (XFCE, Gnome3, Cinnamon, Mate, KDE, JWM, FluxBox, IceWM). With Ventoy I had problem only with LATEST Artix and Porteus Linux XFCE.

On Githab I described the problem https://github.com/ventoy/Ventoy/issues/1028
Let's wait answer.
But I can't understand you guys. I did not say that Artix never worked/not booted through Ventoy. I booted perfectly and installed this OS month and more ago. But in July, something has changed. Why are everyone always trying to redirect the problem and say that it is not their fault? For example Manjaro also recently had problems with the loading their LiveCD mode in a virtual machine (Vmware) and did not recognize the problems for a long time (about 2 months!!!). Then fixed.
Title: Re: Bug reporting
Post by: Chris Cromer on 31 July 2021, 10:37:26
I don't know man. I checked a lot of Linux distros: Fedora 34, openSUSE Tumbleweed, Ubuntu 16.04/18.04/20.04/21.04/21.10, Mx Linux 19.4.1, AntiX 19.4, Linux Mint 20.2, Debian 11 Testing, Devuan Chimaera 4.0 Alpha, Manjaro 21.0.7, Artix, ArchLab, RebornOS, Void Linux with different kernels - start from 4.9 and up to 5.13. All OS’es with different DE’s (XFCE, Gnome3, Cinnamon, Mate, KDE, JWM, FluxBox, IceWM). With Ventoy I had problem only with LATEST Artix and Porteus Linux XFCE.

On Githab I described the problem https://github.com/ventoy/Ventoy/issues/1028
Let's wait answer.
But I can't understand you guys. I did not say that Artix never worked/not booted through Ventoy. I booted perfectly and installed this OS month and more ago. But in July, something has changed. Why are everyone always trying to redirect the problem and say that it is not their fault? For example Manjaro also recently had problems with the loading their LiveCD mode in a virtual machine (Vmware) and did not recognize the problems for a long time (about 2 months!!!). Then fixed.
I never said that it never worked. But as our distro evolves and changes things work differently. Just because ventoy works with distro X today doesn't mean it will work with a new version of the distro in the future. It is ventoy's responsibility to adapt to those distros as they change over time. Distros don't follow ventoy development, ventoy follows their development. As far as the Manjaro issue, that is a stupid point, the fact that their ISO didn't work in cd mode shows they had a bug and didn't test their ISOs. Our stable ISOs we test and work when burned to dvd or pendrive. The fact that our ISOs work 100% clearly means its a bug or problem in ventoy.
Title: Re: Bug reporting
Post by: ####### on 31 July 2021, 13:55:34
I was looking for multiboot USB solutions a couple of years ago, there are lots of these, some in the AUR, and instructions on the Arch wiki and elsewhere to create your own. I didn't find anything that worked well with Artix. I suggest using an older ISO version with Ventoy for now, if it ever worked, that's amazing.  :D
Title: Re: Bug reporting
Post by: Chris Cromer on 01 August 2021, 17:39:07
The ventoy devs fixed the issue. In fact the new version fixes both arch linux and artix linux. As I said before, ventoy issues are ventoy issues they have to fix them.
Title: Re: Bug reporting
Post by: dreieck on 15 August 2021, 20:49:12

In which part of the Forum bugs should be reported?

Since I don't see a clear space in the forum for bug reporting, I report it here:

---

digikam linked against wrong openexr version

digikam is linked against wrong openexr library:

Code: [Select]
pacman -Syy
pacman -S --asdeps world/openexr
pacman -S world/digikam

does currently install openexr version 3.1.1-1 and digikam version 7.3.0-4.

When launching digikam, the following error is printed:
Code: [Select]
digikam: error while loading shared libraries: libOpenEXR-3_0.so.29: cannot open shared object file: No such file or directory

ls -1 /usr/lib/libOpenEXR* shows
Code: [Select]
/usr/lib/libOpenEXR-3_1.so
/usr/lib/libOpenEXR-3_1.so.30
/usr/lib/libOpenEXR-3_1.so.30.1.0
/usr/lib/libOpenEXR.so
/usr/lib/libOpenEXRCore-3_1.so
[...]

There is .so.30 installed, but digikam expects .so.29, so it seems like linking against wrong library version.
Title: Re: Bug reporting
Post by: ndowens on 15 August 2021, 23:56:41
In which part of the Forum bugs should be reported?

Since I don't see a clear space in the forum for bug reporting, I report it here:

---

digikam linked against wrong openexr version

digikam is linked against wrong openexr library:

Code: [Select]
pacman -Syy
pacman -S --asdeps world/openexr
pacman -S world/digikam

does currently install openexr version 3.1.1-1 and digikam version 7.3.0-4.

When launching digikam, the following error is printed:
Code: [Select]
digikam: error while loading shared libraries: libOpenEXR-3_0.so.29: cannot open shared object file: No such file or directory

ls -1 /usr/lib/libOpenEXR* shows
Code: [Select]
/usr/lib/libOpenEXR-3_1.so
/usr/lib/libOpenEXR-3_1.so.30
/usr/lib/libOpenEXR-3_1.so.30.1.0
/usr/lib/libOpenEXR.so
/usr/lib/libOpenEXRCore-3_1.so
[...]

There is .so.30 installed, but digikam expects .so.29, so it seems like linking against wrong library version.

I found two packages that needed a rebuild, somehow they didn't get built against correct version. Passed info about digikam, so it will be rebuilt ASAP.

Edit: digikam has been rebuilt.
Title: Re: Bug reporting
Post by: ####### on 16 August 2021, 02:43:24
"In which part of the Forum bugs should be reported?"
https://forum.artixlinux.org/ (https://forum.artixlinux.org/)
If you read the forum index there are several sections which can apply for various problems, for example:
Applications & Software
Issues related to applications, WM/DE, configuration, mounting, printing,sound, video, productivity, office, graphics, games
Package management
Updating, upgrading, downgrading, conflicts and Artix repositories issues
System
Kernel, hardware, administration, servers. daemons, networking

Perhaps it is less clear in non-English translations, but "issue" is a synonym for "bug" and it is up to you to decide where your bug / issue / problem / malfunction is best described. The categories don't seem to be strictly enforced, but it can be helpful sometimes for those reading the post if an appropriate section is used.
Title: Re: Bug reporting
Post by: d1nuc0m on 23 May 2022, 22:47:54
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.

Almost a year later the bug tracker url is still reported in /usr/lib/os-release, but if I understand correctly has never been operational... Are there any plans to deploy one?
Title: Re: Bug reporting
Post by: nous on 25 May 2022, 00:21:25
Almost a year later the bug tracker url is still reported in /usr/lib/os-release, but if I understand correctly has never been operational... Are there any plans to deploy one?
Not any time soon, the people involved in infrastructure are overwhelmed at the moment...
Title: Re: Bug reporting
Post by: d1nuc0m on 25 May 2022, 10:54:44
Not any time soon, the people involved in infrastructure are overwhelmed at the moment...

May I suggest "outsourcing" the bug tracker using a empty GitHub repository? No pull requests, just issues
Title: Re: Bug reporting
Post by: SalamiMommy on 06 May 2024, 06:05:47
Artix 6.8.9 will no longer launch Overwatch2 successfully. Rolling back to 6.8.8 solves the issue, so I'm pretty sure its a kernel issue and not related to mesa or proton. Some other games on 6.8.9 work, some others are also broken.
Title: Re: Bug reporting
Post by: corysanin on 06 May 2024, 16:50:10
Artix 6.8.9 will no longer launch Overwatch2 successfully. Rolling back to 6.8.8 solves the issue, so I'm pretty sure its a kernel issue and not related to mesa or proton. Some other games on 6.8.9 work, some others are also broken.

Create a new thread. It's been nearly two years since the last post.
Title: Re: Bug reporting
Post by: SalamiMommy on 06 May 2024, 22:47:59
Artix 6.8.9 will no longer launch Overwatch2 successfully. Rolling back to 6.8.8 solves the issue, so I'm pretty sure its a kernel issue and not related to mesa or proton. Some other games on 6.8.9 work, some others are also broken.

Create a new thread. It's been nearly two years since the last post.
Sorry, I thought that was the point of it being a pinned post, I will do that
Title: Re: Bug reporting
Post by: corysanin on 07 May 2024, 04:42:59
Sorry, I thought that was the point of it being a pinned post, I will do that

It was a meta post about reporting bugs. Not a thread for actually posting bugs.
Title: Re: Bug reporting
Post by: TheUnknownCynic on 24 May 2024, 13:51:59
Regarding Bug reporting on https://bugs.artixlinux.org/lost_pwd.php

I just tried to report a setup issue that wipes out data.

Here's the error message I got:

APPLICATION ERROR #1903
The provided information does not match any registered account!
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.

it also says Powered by MantisBT
Copyright © 2000 - 2024 MantisBT Team
Contact administrator for assistance

...which may mean being a registered in the forum doesn't infer being registered to report bugs.

Doesn't matter too much to me.  I LOVE Artix Linux.  Thank you all.  I'll make a donaation (ALLEGEDLY) #FTIRS