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 3580 - dbus assertion
Summary: dbus assertion
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: *don't know* (show other bugs)
Version: 2.0.5
Hardware: x86_64 Linux
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-03 20:07 UTC by Logan McNaughton
Modified: 2018-08-06 21:20 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Logan McNaughton 2017-02-03 20:07:43 UTC 
I am trying to run m64py (https://github.com/mupen64plus/mupen64plus-ui-python). It uses PySDL2 to interface with SDL2.

I am getting this message:

dbus[11726]: arguments to dbus_connection_ref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../dbus/dbus-connection.c line 2686.
This is normally a bug in some application using the D-Bus library.

dbus[11726]: arguments to dbus_connection_close() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../dbus/dbus-connection.c line 2935.
This is normally a bug in some application using the D-Bus library.

This is on Fedora 25, SDL2 2.0.5, dbus 1.11.8
Comment 1 Logan McNaughton 2017-02-03 20:08:55 UTC 
A discussion about this in m64py is here: https://github.com/mupen64plus/mupen64plus-ui-python/issues/91
Comment 2 Sam Lantinga 2017-02-03 23:22:51 UTC 
Can you reproduce it with the SDL test programs? Do you know what call in m64py is generating the error?

Thanks!
Comment 3 Logan McNaughton 2017-02-04 03:00:32 UTC 
Where can I find the SDL test programs?

The last few lines of the trace for the application looks like this:

mainwindow.py(175):         size = self.size()
mainwindow.py(176):         desktop = QApplication.desktop()
mainwindow.py(177):         width, height = size.width(), size.height()
mainwindow.py(178):         dwidth, dheight = desktop.width(), desktop.height()
mainwindow.py(179):         cw, ch = (dwidth/2)-(width/2), (dheight/2)-(height/2)
mainwindow.py(180):         self.move(cw, ch)
m64py(60):     window.raise_()
m64py(62):     try:
m64py(63):         try:
m64py(64):             signal.siginterrupt(signal.SIGCHLD, False)
m64py(65):             signal.signal(signal.SIGINT, signal.SIG_DFL)
m64py(68):         sys.exit(app.exec_())

The dbus message happens right after that line.
Comment 4 Sam Lantinga 2017-02-04 18:08:46 UTC 
After the app.exec_() call?

The SDL test programs are in the test directory of the SDL source archive:
https://www.libsdl.org/release/SDL2-2.0.5.zip
Comment 5 Ryan C. Gordon 2018-08-06 21:20:25 UTC 
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.