On Thursday, November 24, 2011, Olegaria Ercilurrutigastañazagogeascoa wrote:
> futex(0x7fff1c7de78c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, > NULL, 7f3a58a8a760) = -1 EAGAIN (Resource temporarily unavailable) I don't know enough about the part of our code in question to understand exactly what that's telling me, but I know enough about how it all fits together to guess that Rosegarden is getting stuck waiting for access to the realtime clock for some reason or other. I'd try running as root and see if that gets you anywhere. If Rosegarden continues past this issue as root, then the underlying problem is most likely something you could configure away by tweaking the permissions on something, somewhere. I'm not exactly sure what, where, or how, but that would be the general direction to aim in. Either way, I have a feeling that the "(auto)" timer setting should be robust enough to detect a problem like this, and try using a different timing source or something, instead of just hanging indefinitely. If we can figure out what file open code in Rosegarden is behind this infinite wait, we ought to be able to wrap some kind of timer around it so it will only spin its wheels for a fixed amount of time before aborting and trying something else. I have no idea where this code is, or what steps have already been taken to avoid this kind of situation. I'm interested enough to go have a look, but I have no idea when that might be. -- D. Michael McIntyre ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Rosegarden-user mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
