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 2862 - D-Bus error message on application start
Summary: D-Bus error message on application start
Status: RESOLVED FIXED
Alias: None
Product: SDL
Classification: Unclassified
Component: *don't know* (show other bugs)
Version: HG 2.0
Hardware: x86_64 Linux
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords: triage-2.0.4
Depends on:
Blocks:
 
Reported: 2015-02-02 13:35 UTC by Alex
Modified: 2015-04-07 01:41 UTC (History)
2 users (show)

See Also:


Attachments
Potential fix (842 bytes, patch)
2015-03-20 19:51 UTC, Alex Baines
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2015-02-02 13:35:08 UTC
Every time I start my SDL2-based application, I see error message in terminal:

process 2470: arguments to dbus_connection_open_private() were incorrect, assertion "address != NULL" failed in file ../../dbus/dbus-connection.c line 2647.
This is normally a bug in some application using the D-Bus library.


Looks like my app works fine for now, but this error message bother me. May be later this error can harm my app normal working.

Latest hg version of SDL on which I tested it is ad4f430cc9f5. On older version I had this bug too.

Please fix this bug.
Comment 1 Ryan C. Gordon 2015-02-19 05:22:21 UTC
Marking a large number of bugs with the "triage-2.0.4" keyword at once. Sorry if you got a lot of email from this. This is to help me sort through some bugs in regards to a 2.0.4 release. We may or may not fix this bug for 2.0.4, though!
Comment 2 Alex Baines 2015-03-20 19:51:15 UTC
Created attachment 2075 [details]
Potential fix

Here is a patch that might fix the issue.
Comment 3 Ryan C. Gordon 2015-04-07 01:41:25 UTC
This patch is now https://hg.libsdl.org/SDL/rev/0288195afd8c, thanks!

I'm resolving this bug under the assumption this was the problem; please reopen if this doesn't fix the issue for you.

Thanks,
--ryan.