Ticket #416 (closed usability: fixed)
Race condition on X startup
|Reported by:||cobbe@…||Owned by:||jeremyhu@…|
|Priority:||Nice to Have||Milestone:||2.6.2|
I typically start XQuartz by means of a login item, a program that I wrote myself (in C) which establishes certain environment settings and then execs /opt/X11/bin/xterm. This pokes the launchd socket and starts the X server as expected. I also have a file ~/.xinitrc.d/00-resources.sh, which is executable, that calls "/opt/X11/bin/xrdb ~/.Xresources" in the foreground.
There's a race condition between these two programs on X startup. Sometimes the xterm starts first, sometimes the resources get loaded (as demonstrated by the fact that the xterm respects the resource settings only sometimes). I know that the resources are always loaded, because in cases where the xterm starts first, I can type "xterm" at its prompt and get a new xterm that does respect the resource settings.
Additional details available upon request, including the source code of the program that starts xterm.
- Status changed from new to assigned
- Milestone set to 2.6.0
- Status changed from assigned to closed
- Resolution set to fixed