Non noob here. I've hit a strange problem while testing non-session-manager (from current git). It runs fine on my test system, but after installing it on my production system NSM no longer works. The GUI starts up with greyed out buttons and won't respond.
netstat -lptu shows for the non-working system: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name udp 0 0 *:18804 *:* 4434/non-session-ma udp 0 0 *:11385 *:* 4437/nsmd and for the working system: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name udp 0 0 *:16327 *:* 2691/nsmd udp 0 0 *:10891 *:* 2688/non-session-ma NSM console messages on non-working system: [non-session-manager] Starting daemon... [nsmd] Session root is: /home/sound/NSM Sessions X_ChangeProperty: BadValue (integer parameter out of range for operation) 0x0 and on the working system (after starting NSM then clicking on Quit): [non-session-manager] ../nonlib/OSC/Endpoint.C:202 init(): Creating OSC server [non-session-manager] ../session-manager/src/session-manager.C:1394 main(): Starting daemon... [non-session-manager] ../nonlib/OSC/Endpoint.C:1148 osc_thread(): OSC Thread running [nsmd] ../session-manager/src/nsmd.C:2242 main(): Going to connect to GUI at: osc.udp://zann0.localdomain:10891/ [nsmd] ../session-manager/src/nsmd.C:2265 main(): Session root is: /home/sound/NSM Sessions [nsmd] ../nonlib/OSC/Endpoint.C:202 init(): Creating OSC server [nsmd] ../session-manager/src/nsmd.C:2140 announce_gui(): Registered with GUI X_ChangeProperty: BadValue (integer parameter out of range for operation) 0x0 [nsmd] ../session-manager/src/nsmd.C:1562 osc_list(): Listing sessions [non-session-manager] ../session-manager/src/session-manager.C:1433 main(): Telling server to quit NSM_URL=osc.udp://zann0.localdomain:16327/ Note that the "X_ChangeProperty: BadValue" message appears on both, so I don't think that's the problem. Both systems have identical software configuration, apart from a few extra debugging utilities on the test system. There are a couple of hardware differences. The test system uses a 2.5GHz AthlonIIX4 and the production system uses a 2.6GHz Athlon64X2. The test system uses a 1280x1024 monitor and the production system uses 1680x1050. Both motherboards use the same AMD 780G/SB700 chipsets with 4GB unbuffered ECC DDR2 RAM. Both systems run Debian 7.4 amd64 with Window Maker, with 3.12.10 kernels with CONFIG_PREEMPT=y. Both run non-timeline and non-mixer without a problem. I'm wondering if there's a race condition which trips up the 2-core system but doesn't affect the 4-core, but that's just a guess. Any ideas? John
