This bug report was migrated from our old Bugzilla tracker.

Reported in version: 2.0.9
Reported for operating system, platform: Linux, x86_64

Comments on the original bug report:

On 2019-01-27 23:51:59 +0000, Lukas Braun wrote:

If 'dbus-launch' is not installed SDL futilely keeps trying to establish a DBus connection, which involves a fork plus a bunch of failing execs, causing quite a lot of unnecessary load. I noticed this while trying to play the game teeworlds, which uses 'SDL_PollEvent()' and hanged for seconds every time I moved my mouse.

I don't know if this type of error can reliably be distinguished in the DBus API, but in any case some kind of rate-limiting might be reasonable?

Cheers,
Lukas

On 2019-07-30 17:49:37 +0000, Ryan C. Gordon wrote:

(Sorry if you get several emails like this, we're marking a bunch of bugs.)

We're hoping to ship SDL 2.0.11 on a much shorter timeframe than we have historically done releases, so I'm starting to tag bugs we hope to have closed in this release cycle.

Note that this tag means we just intend to scrutinize this bug for the 2.0.11 release: we may fix it, reject it, or even push it back to a later release for now, but this helps give us both a goal and a wishlist for the next release.

If this bug has been quiet for a few months and you have new information (such as, "this is definitely still broken" or "this got fixed at some point"), please feel free to retest and/or add more notes to the bug.

--ryan.

On 2019-09-20 20:47:38 +0000, Ryan C. Gordon wrote:

We're changing how we do SDL release versions; now releases will be even numbers (2.0.10, 2.0.12, etc), and as soon as we tag a release, we'll move the internal version number to an odd number (2.0.12 ships, we tag the latest in revision control as 2.0.13 immediately, which will become 2.0.14 on release, etc).

As such, I'm moving the bugs tagged with target-2.0.11 to target 2.0.12. Sorry if you get a lot of email from this change!

Thanks,
--ryan.

On 2019-09-20 20:48:39 +0000, Ryan C. Gordon wrote:

We're changing how we do SDL release versions; now releases will be even numbers (2.0.10, 2.0.12, etc), and as soon as we tag a release, we'll move the internal version number to an odd number (2.0.12 ships, we tag the latest in revision control as 2.0.13 immediately, which will become 2.0.14 on release, etc).

As such, I'm moving the bugs tagged with target-2.0.11 to target 2.0.12. Sorry if you get a lot of email from this change!

Thanks,
--ryan.

On 2019-10-09 23:42:06 +0000, Ryan C. Gordon wrote:

I couldn't coerce my system into a state where SDL would keep trying to initialize D-Bus over and over, but as of https://hg.libsdl.org/SDL/rev/074c42dbf8c9, if D-Bus doesn't initialize, we won't try to initialize it again if requested, which should solve the problem you're describing. Let me know if it doesn't!

--ryan.

On 2019-10-10 11:54:28 +0000, Lukas Braun wrote:

Looks good, but I also can't reproduce the problem on my current system... Thanks for the fix anyway.

Lukas