#26 OCM won\'t run on Gentoo

open
nobody
5
2012-10-15
2011-04-16
Mark Nowiasz
No

Hi,

after compiling and installing OCM on Gentoo Linux, opencachemanager-0.23.13 and 0.23.12 crashes at startup:

There\'s a GUI window opening and then the program crashes:

(ocm-gtk:16511): Gtk-WARNING **: menu: missing action (null)
Inconsistency detected by ld.so: dl-close.c: 736: _dl_close: Assertion `map->l_init_called\' failed!

After deleting the created sqlite, there\'s also a window complaining about the msising db just before crash.

(BTW - I tried to restart the \"wizard\" by deleting every config item I\'ve found related to OCM (.gconfd, .config, the ocm directory and so on and still wasn\'t able to get the wizard at startup. What else did I miss?)

Unfortunately there doesn\'t seem to be a \"debug\" option when running ocm-gtk, so the only help I could give you is a strace file :-/

Discussion

  • kmcamp_ott
    kmcamp_ott
    2011-04-16

    After deleting the created sqlite, there\'s also a window complaining about the msising db just before crash.
    That error is supposed to happen if you delete the DB. You can create a new one or open another when prompted

    still wasn\'t able to get the wizard at startup. What else did I miss?)
    I don't think the wizard will help you, but you need to delete ~/.gconf/app/ocm

    Unfortunately there doesn\'t seem to be a \"debug\" option when running ocm-gtk, so the only help I could give you is a strace file :-/
    OCM 1.0 is going to have some debug logging to help me figure out problems. You can though in a terminal try "mono --debug ocm-gtk.exe" it might give some more information.

    Inconsistency detected by ld.so: dl-close.c: 736: _dl_close: Assertion `map->l_init_called\' failed!
    I've never seen this error before, but a quick google search makes it look like a problem where 32 bit and 64 bit libraries are mixed. Are you running a 64 bit Gentoo?

     
  • kmcamp_ott
    kmcamp_ott
    2011-04-18

    The first dev build of OCM 1.0 will be coming within the next couple of weeks. It's a major rewrite of a lot of the underlying OCM code which I hope should fix this judying by the stack trace.

     


Anonymous


Cancel   Add attachments