Hello all, got a possibly (hopefully) small issue and I need a hint. I’ve been searching the site but this seems to be my own flavor of fail
Today I built panda3d-1.7.0 by hand on my Gentoo notebook using python-2.6 and everything looked great. I did basically just
python makepanda/makepanda.py --everything
sudo python makepanda/installpanda.py
pview works great, opens models-- no problem. I tried to run some samples, but got a completely unresponsive solid black window named Panda every time. The hello-world example does the same thing, black instead of gray. In the terminal where I run “python foobar.py”, Ctrl+C does nothing, nor does trying to close the Panda window with the window manager. There are two ways to stop the interpreter-- closing the terminal, or a regular “killall python2.6”. I’ve tried switching to all-software rendering and it didn’t change anything except the details of the console output which originally looks like this:
$ python game.py
Known pipe types:
glxGraphicsPipe
(all display modules loaded.)
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Terminated
$
I can get the “Cannot connect” messages to go away by starting jackd beforehand but that does nothing to stop the hang, either. I watched with strace and the last lines are typically like this:
shutdown(5, 2 /* send and receive */) = -1 EBADF (Bad file descriptor)
close(5) = -1 EBADF (Bad file descriptor)
write(2, "jack server is not running or ca"..., 48jack server is not running or cannot be started
) = 48
futex(0x890dea4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x890dea0, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0xaedcebd8, FUTEX_WAIT, 10104, NULL
I know that’s only jack and probably irrelevant; I’m just wondering about the FUTEX_WAIT. At least with strace running, Ctrl+C worked normally.
For the record, I started by building 1.6.2 but something was supposedly missing and the install script aborted early… when I tried to run some samples, it would run for a second and segfault without opening a window. Anyway, I hunted down and manually deleted everything from 1.6.2 (afaict) before installing and trying 1.7.0 so that’s probably not the issue.
Whatever’s going on is probably my machine’s fault, i.e. my fault… I’m updating the whole system and then rebuilding 1.7.0 to see what happens. I also know that getting some things to build and run on Gentoo is often “like trying to nail jello to a wall” so thanks in advance for any help.