Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

D-Bus error message on application start #1754

Closed
SDLBugzilla opened this issue Feb 10, 2021 · 0 comments
Closed

D-Bus error message on application start #1754

SDLBugzilla opened this issue Feb 10, 2021 · 0 comments

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

Reported in version: HG 2.0
Reported for operating system, platform: Linux, x86_64

Comments on the original bug report:

On 2015-02-02 13:35:08 +0000, Alex wrote:

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.

On 2015-02-19 05:22:21 +0000, Ryan C. Gordon wrote:

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!

On 2015-03-20 19:51:15 +0000, Alex Baines wrote:

Created attachment 2075
Potential fix

Here is a patch that might fix the issue.

On 2015-04-07 01:41:25 +0000, Ryan C. Gordon wrote:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant