Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: iGNUGO problems in openSuse13.2

  1. #1

    Default iGNUGO problems in openSuse13.2

    Hello,

    I used standard YAST and updated my openSUSE 13.1 to install GNUGO (3.91 version) using QGO and glGO as clients.

    While I can start in a terminal GNUGO using --mode GTP --quiet options (no error message), when using the client(s) to play the game, I have diverse problems:
    - for QGO I get the error message saying that starting GNUGO encountered an error and things stop at that: the QGO graphical interface comes up but the game can not be played.
    - for glGo things are different: the program says it can not find some version of libSDL. Using ldd on the binary I found it does not find many libraries and all seem to be 32 bit versions. Also the program seem to look for them in games/lib where there are none of those it is looking for. The required libSDL exists in 64 bit version, so I am kind of confused.

    mayeb someone can help me, thanks friendly yours SH.

  2. #2
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,649

    Default Re: iGNUGO problems in openSuse13.2

    Confusing here too since you did not tell use the errors.

  3. #3

    Default Re: iGNUGO problems in openSuse13.2

    For qgo the popup comes and says: "error opening program: could not start /usr/bin/gnugo --mode gtp --quiet" and things stop.

    For glGo I get

    ioan@Netghost:~> /usr/games/glGo
    /usr/games/glGo: error while loading shared libraries: libSDL-1.2.so.0: cannot open shared object file: No such file or directory
    ioan@Netghost:~>


    as i said , the library exists but in 64 bit veersion...thanks for the help, friendly SH

  4. #4

    Default Re: iGNUGO problems in openSuse13.2

    It seems nobody really cares, I even do not understand what is missing to send the right information..

  5. #5
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,504
    Blog Entries
    15

    Default Re: iGNUGO problems in openSuse13.2

    On Fri 14 Nov 2014 08:46:01 PM CST, sharphawk64 wrote:


    For qgo the popup comes and says: "error opening program: could not
    start /usr/bin/gnugo --mode gtp --quiet" and things stop.

    For glGo I get

    ioan@Netghost:~> /usr/games/glGo
    /usr/games/glGo: error while loading shared libraries: libSDL-1.2.so.0:
    cannot open shared object file: No such file or directory
    ioan@Netghost:~>


    as i said , the library exists but in 64 bit veersion...thanks for the
    help, friendly SH


    Hi
    But why running /usr/games/glGo?

    Use gdb or strace;
    Code:
    gdb gnugo --mode gtp --quiet
    .....
    .....
    run <press enter>
    
    or
    
    strace gnugo --mode gtp --quiet
    Might provide more output...


    --
    Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
    SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  6. #6

    Default Re: GNUGO problems in openSuse13.2

    Quote Originally Posted by malcolmlewis View Post
    Hi
    But why running /usr/games/glGo?

    Use gdb or strace;
    Code:
    gdb gnugo --mode gtp --quiet
    .....
    .....
    run <press enter>
    
    or
    
    strace gnugo --mode gtp --quiet
    Might provide more output...


    --
    Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
    SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!
    I think the problem was not clearly described: I try to play GO on my computer. For that I tried two different ways which would lead to the same result I am using 2 different GUI-client programs qgo and glGo.These clients are supposed to start /usr/bin/gnugo server when I want to play GO against the computer. I have to configure, in the GUI interface of the client, the server location and params, which I did! The client(s) and the server are located in the directory where they were installed by openSUSE 13.2.
    Let's look at one of them 1st: i start qgo, the program starts well, but I encounter a problem when trying to start a game against the computer and thus have to start the GNUGO server. At that point the error message mentioned in the posts above indicate that "an error ocured when starting gnugo server" as I indicated in the posts above.
    If I try to use (for the same purpose) another client (e.g. glGo) the problem is quite different: libraries are missing and the program does not even start.
    In 13.1 all these operations were simple, direct and worked without any problem on the same computer (Intel-I7 64 bits) but since 13.2 the same operations do not work.

    How do you advise me to use gdb or strace? If I understand well, starting the server with gdb will not help because gnugo server must be started by the GUI-client (qgo or glGo).

    thanks for the help, friendly yours SH.

  7. #7
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,504
    Blog Entries
    15

    Default Re: iGNUGO problems in openSuse13.2

    Hi
    Ahh ok, well whichever client your trying to run, open a terminal and use either;

    Code:
    gdb /some/client
    ....
    {gdb starting output}
    ....
    run <press enter>
    
    OR
    
    strace /some/client
    That should provide output and where the issue may be.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  8. #8

    Arrow Re: iGNUGO problems in openSuse13.2

    Hi,

    I think I found the problem: qgo client, started under non-root user, can NOT access the /usr/bin/gnugo program though it says " ERROR OPENING PROGRAM; could not start ...." .
    Once i start the game under "root" all works fine and no error encountered.
    The idea came from looking at the huge trace file. To make it shorter and I asked to watch the path /usr/bin and then I got only 2 lines with "access" verb in the last. Then the opening error strike at me and I tried under root.

    Now I wonder how come, because at all file and directory levels the rights are R-X for group and others and for the owner (root) is RWX. Even more, I allowed the write access on the gnugo program but I got the same error.

    I am surprised that one needs write access to use this program. have any security rules changed lately in 13.2 ? can you help? friendly yours SH.

  9. #9

    Default Re: iGNUGO problems in openSuse13.2

    Worse, it worked under root and now it does not work any more...I swear it did work and now it does not.... I am really very upset.;please help!! friendly yours SH.:

  10. #10
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,504
    Blog Entries
    15

    Default Re: iGNUGO problems in openSuse13.2

    On Thu 27 Nov 2014 07:26:01 PM CST, sharphawk64 wrote:


    Worse, it worked under root and now it does not work any more...I swear
    it did work and now it does not.... I am really very
    upset.;please help!! friendly yours SH.:


    Hi
    That's quite possible since it was run as root user...changed something
    somewhere....

    If you force the re-install of the package, then if duplicate I think
    it would be best to raise a bug....


    --
    Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
    SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •