| Summary: | dbus assertion | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Logan McNaughton <logan> |
| Component: | *don't know* | Assignee: | Sam Lantinga <slouken> |
| Status: | RESOLVED ABANDONED | QA Contact: | Sam Lantinga <slouken> |
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 2.0.5 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
|
Description
Logan McNaughton
2017-02-03 20:07:43 UTC
A discussion about this in m64py is here: https://github.com/mupen64plus/mupen64plus-ui-python/issues/91 Can you reproduce it with the SDL test programs? Do you know what call in m64py is generating the error? Thanks! 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. 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 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. |