Consumes too many resources detecting OS vendor and version

[Scott James Remnant (Canonical)]

Jockey calls lsb_release on startup to identify the OS vendor and version that it is running on. This is prohibitively expensive.

This is a jockey bug because the package itself could have that information hard-coded, it does not need to be dynamic. There's no resume to presume that the machine will change from Ubuntu to Slackware overnight, and any version update would assumedly also be accompanied by a jockey update.

I appreciate you might be unhappy hardcoding it, but you do need to find a cheaper way than spawning lsb_release!

[Chris Coulson (chrisccoulson)]

This seems to be an issue with everything calling lsb_release. Perhaps lsb_release should be re-written in something like C so that it doesn't need a full Python interpreter to run

[Chris Coulson (chrisccoulson)]

In fact, Martin already responded to a similar request in bug 262050

[Martin Pitt (pitti)]

This is mitigated by the change I just did which doesn't start jockey at session startup any more if it ran once. Other than that, dupe of 262050.

[Scott James Remnant (Canonical) (canonical-scott)]

I disagree that this is a duplicate, in fact you'll note that I filed this bug *after* fixing the bug you think it is a duplicate.

Read what I wrote.

My assertion is that jockey need not attempt to identify the OS vendor or version on startup at all, ever. This can be done at build time.

[Martin Pitt (pitti)]

Ok, if you insist. :-) It's very cheap now, though, and jockey doesn't run at every session start, so this is really just cosmetical.

[dino99 (9d9)]

Jockey has been superseded by software-properties, which now handles
third-party driver configuration.