We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 4476

Summary: Don't keep trying to connect to non-existent DBus
Product: SDL Reporter: Lukas Braun <sdl-bugzilla>
Component: *don't know*Assignee: Ryan C. Gordon <icculus>
Status: RESOLVED FIXED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 Keywords: target-2.0.12
Version: 2.0.9   
Hardware: x86_64   
OS: Linux   

Description Lukas Braun 2019-01-27 23:51:59 UTC 
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
Comment 1 Ryan C. Gordon 2019-07-30 17:49:37 UTC 
(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.
Comment 2 Ryan C. Gordon 2019-09-20 20:47:38 UTC 
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.
Comment 3 Ryan C. Gordon 2019-09-20 20:48:39 UTC 
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.
Comment 4 Ryan C. Gordon 2019-10-09 23:42:06 UTC 
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.
Comment 5 Lukas Braun 2019-10-10 11:54:28 UTC 
Looks good, but I also can't reproduce the problem on my current system... Thanks for the fix anyway.

Lukas