Menu

#982 Doesn't start on Ubuntu - error 13

General
closed
None
1
2019-01-16
2018-11-19
GerardW
No

Doesn't start for me -- invoking ./CAMed just immediately returns a 13.

System info:
Linux 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"

Discussion

  • drrwebber

    drrwebber - 2018-11-19
    • summary: Doesn't --> Doesn't start on Ubuntu - error 13
     
  • drrwebber

    drrwebber - 2018-11-19

    I looked up error 13 - its related to root access permissions.

    I suspect you installed CAMed folder in a system folder. If you move the folder to your home/user/ area and run it there - I believe that will correct the problem.

     

    Last edit: drrwebber 2018-11-19
  • GerardW

    GerardW - 2018-11-19

    No, it's in a user owned directory. Here's a gdb trace, if that's any help:

    gweatherby@boxcode:/hard/tools/CAMEd-3.2.2$ gdb CAMed
    GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
    Copyright (C) 2016 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law. Type "show copying"
    and "show warranty" for details.
    This GDB was configured as "x86_64-linux-gnu".
    Type "show configuration" for configuration details.
    For bug reporting instructions, please see:
    http://www.gnu.org/software/gdb/bugs/.
    Find the GDB manual and other documentation resources online at:
    http://www.gnu.org/software/gdb/documentation/.
    For help, type "help".
    Type "apropos word" to search for commands related to "word"...
    Reading symbols from CAMed...done.
    (gdb) run
    Starting program: /hard/tools/CAMEd-3.2.2/CAMed
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
    process 4970 is executing new program: /hard/tools/CAMEd-3.2.2/CAMed
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
    [New Thread 0xb4dd3b40 (LWP 4974)]
    [New Thread 0xb4bffb40 (LWP 4975)]
    [New Thread 0xb49ffb40 (LWP 4976)]
    [New Thread 0xb47ffb40 (LWP 4977)]
    [New Thread 0xb45ffb40 (LWP 4978)]
    [New Thread 0xb43ffb40 (LWP 4979)]
    [New Thread 0xb41ffb40 (LWP 4980)]
    [New Thread 0xb3fffb40 (LWP 4981)]
    [New Thread 0xb3c70b40 (LWP 4982)]
    [New Thread 0xb4b7eb40 (LWP 4983)]
    [New Thread 0xb497eb40 (LWP 4984)]
    [New Thread 0xb477eb40 (LWP 4985)]
    [New Thread 0xb3befb40 (LWP 4986)]
    [New Thread 0xb457eb40 (LWP 4987)]
    [New Thread 0xb35ffb40 (LWP 4988)]
    [New Thread 0xb437eb40 (LWP 4989)]
    [New Thread 0xb417eb40 (LWP 4990)]
    [New Thread 0xb3f7eb40 (LWP 4991)]
    [New Thread 0xb3b6eb40 (LWP 4992)]
    [New Thread 0xb357eb40 (LWP 4993)]
    [Thread 0xb357eb40 (LWP 4993) exited]
    [Thread 0xb417eb40 (LWP 4990) exited]
    [Thread 0xb3f7eb40 (LWP 4991) exited]
    [Thread 0xb3b6eb40 (LWP 4992) exited]
    [Thread 0xb437eb40 (LWP 4989) exited]
    [New Thread 0xb437eb40 (LWP 4994)]
    [Thread 0xb437eb40 (LWP 4994) exited]
    [Thread 0xb35ffb40 (LWP 4988) exited]
    [Thread 0xb457eb40 (LWP 4987) exited]
    [Thread 0xb3befb40 (LWP 4986) exited]
    [Thread 0xb477eb40 (LWP 4985) exited]
    [Thread 0xb497eb40 (LWP 4984) exited]
    [Thread 0xb4b7eb40 (LWP 4983) exited]
    [Thread 0xb3c70b40 (LWP 4982) exited]
    [Thread 0xb3fffb40 (LWP 4981) exited]
    [Thread 0xb41ffb40 (LWP 4980) exited]
    [Thread 0xb45ffb40 (LWP 4978) exited]
    [Thread 0xb47ffb40 (LWP 4977) exited]
    [Thread 0xb49ffb40 (LWP 4976) exited]
    [Thread 0xb4bffb40 (LWP 4975) exited]
    [Thread 0xb4dd3b40 (LWP 4974) exited]
    [Thread 0xf7dd8700 (LWP 4970) exited]
    [Inferior 1 (process 4970) exited with code 015]
    (gdb)

     
  • drrwebber

    drrwebber - 2018-11-19

    OK - the only file I know it opens with write access is the Momentos.xml in the workspace/CAMEditor folder. Is the whole folder structure there open? If there is no Momentos.xml file it will create a default one.

    On Windows you have to run it with Administrator rights if this folder is inside /Program Files/ .

    I am running Ubuntu 16.04 and it has been working for years both from command line ./CAMed and simply clicking on the icon in Unity desktop. Trying to figure out how your setup is different.

    It is a bit heavy handed - but you could try: sudo ./CAMed

     
  • GerardW

    GerardW - 2018-11-19

    I ran strace and found I was missing a library:
    sudo apt install libgtk2.0-0:i386 got me further, but then the JVM crashed :(
    Logs attached.

     
  • drrwebber

    drrwebber - 2018-11-19

    Also I see the GTK err log gives missing components. I'm wondering if display is failing. Now you have install the libgtk maybe do a general system update to see if more dependencies needed.

     

    Last edit: drrwebber 2018-11-19
  • drrwebber

    drrwebber - 2019-01-16
    • status: open --> closed
    • assigned_to: drrwebber
     

Log in to post a comment.