Bug 496454 - does not reach gnugo despite proper path is set
Summary: does not reach gnugo despite proper path is set
Status: RESOLVED FIXED
Alias: None
Product: kigo
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Sascha Peilicke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-19 09:44 UTC by antonio
Modified: 2025-02-04 14:41 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description antonio 2024-11-19 09:44:04 UTC
kigo 0.6.24083

SOFTWARE/OS VERSIONS

Linux Ubuntu 24.04.1 LTS 

ADDITIONAL INFORMATION

pc ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513EAN_K513EA

Does not reach gnugo despite proper path is set and gnugo has been made executable. Seems 420814 not really fixed.
Comment 1 Albert Astals Cid 2024-12-03 21:25:18 UTC
Do you know if the kigo you are using is a snap or a deb package?
Comment 2 antonio 2024-12-04 09:24:12 UTC
When I found the issue I tried to fix the problem. I used the ubuntu 
"app center" to remove the app and re-istall.  The issue was still 
present so i tried to download from other sources. Maybe, but do not 
remember, I downloaded packages from two sites (GNU and KDE ?). In the 
trying i finished having two different version of Kigo's installed (I 
did not notice it until I saw the the two Kigo's icons was slightly 
different in color !) one working and one not. Likely the version that 
works is a package of an older version downloaded "somewhere" and 
installed in a terminal session.

Antonio

Il 03/12/24 22:25, Albert Astals Cid ha scritto:
> https://bugs.kde.org/show_bug.cgi?id=496454
>
> Albert Astals Cid <aacid@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|REPORTED                    |NEEDSINFO
>           Resolution|---                         |WAITINGFORINFO
>                   CC|                            |aacid@kde.org
>
> --- Comment #1 from Albert Astals Cid <aacid@kde.org> ---
> Do you know if the kigo you are using is a snap or a deb package?
>
Comment 3 Albert Astals Cid 2024-12-04 21:18:13 UTC
You need to be a bit more precise on what version worked and what not and where did you get each of them, we can't fix anything based on the info you gave us (if there is anything to fix since it works fine for me)
Comment 4 Bug Janitor Service 2024-12-19 03:46:52 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2025-01-03 03:47:36 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Comment 6 NLinPEN 2025-01-31 15:13:08 UTC
I am new to this bug reporting system and don't know the proper etiquette. I created an kde bug reporting account as I have the same problem as was reported by the other user. I'm not sure whether I should place my comments here, or start it as a new bug. 
Today I installed both kigo and gnugo. My OS is Ubuntu 24.04.1. I installed both software packages from the App Center. The gnugo package is a Debian package, version 3.8-11build2. I have tried two versions of kigo: 0.6.24081 and 0.6.24121 (both are installed as a snap package). I can run gnugo in a terminal, but kigo continuously gives the error message that no proper engine can be found. Surprisingly it does show a "green ball" in the Configuration menu, at the line that states "Parameters: --mode gtp"
Comment 7 Albert Astals Cid 2025-02-03 21:13:25 UTC
This is probably snap being snap, don't do snaps if you can, and if you can't well then find someone that cares both about snaps and about kigo to debug the problem.
Comment 8 NLinPEN 2025-02-04 14:41:55 UTC
(In reply to Albert Astals Cid from comment #7)
> This is probably snap being snap, don't do snaps if you can, and if you
> can't well then find someone that cares both about snaps and about kigo to
> debug the problem.

I think that you are correct in your assumption that it is snap related. I removed the snap version of kigo and installed a debian version from the App Center (kigo version 0.6.23085). This time kigo works.