Stable: 2.5.2
Development: 2.6-alpha3
When I run MOC (svn version), it appears to go fine until it suddenly stops and says
FATAL_ERROR: Server exited!
After messing around with gdb and getting it to follow the child fork (the server), I was able to track it down to a segfault on line 1144 of tags_cache.c, c->db_env->set_msgcall (c->db_env, db_msg_cb);
.
I have no clue about anything with BerkeleyDB, so I don't really know what this line does or why it might be causing problems. I didn't file this under bug reports because I think it may be a problem with my db installation. This is on a newly installed arch install that may have some screwiness that I am unaware of.
Any help would be appreciated.
computerguy505
Sun, 2013-04-07 02:00
Permalink
I didn't really specify this
I didn't really specify this well, but the error comes up after the driver is detected (alsa in my case) but before the gui is initialized.
jcf
Sun, 2013-04-07 03:10
Permalink
It Does Seem Odd...
... especially as the near-identical line above executed without problems. We pounded this area of code recently in testing the solution to another problem and I have had no reports of this problem from other users (but someone always has to report it first).
computerguy505
Sun, 2013-04-07 15:04
Permalink
Yes, the above line runs
Yes, the above line runs fine.
The latest commit according to
svn log
issudo pacman -S db
gives meJust yesterday I cloned it and immediately ran
./configure
. After that I modified the hard-coded strings in the screen_set_title function in interface_elements.c to be shorter. I then ranmake
. That didn't work. Withmocp -D
I gotcomputerguy505
Sun, 2013-04-07 15:14
Permalink
It works now...
I have no clue why, but it has magically started working now. Maybe it's because I reinstalled db (like about but answering y). Probably something just went wrong when I installed db the first time.
Thanks, though!
jcf
Sun, 2013-04-07 19:38
Permalink
Consider It Gone
I reproduced what you did as closely as possible but had no problem. Some glitch in the BDB install would explain it.