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

Message boxes crash on X11 if cursor is hidden #965

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

Message boxes crash on X11 if cursor is hidden #965

SDLBugzilla opened this issue Feb 10, 2021 · 0 comments

Comments

@SDLBugzilla
Copy link
Collaborator

@SDLBugzilla SDLBugzilla commented Feb 10, 2021

This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

Reported in version: 2.0.0
Reported for operating system, platform: Linux, x86_64

Comments on the original bug report:

On 2013-07-13 09:07:52 +0000, Sik wrote:

X11 specific bug. If the program calls SDL_ShowCursor(SDL_FALSE) at some point, it results in message boxes crashing (as they can't seem to create the cursor needed for some reason).

Workaround until bug is fixed: make sure to call SDL_ShowCursor(SDL_TRUE) before showing the message box.

On 2013-07-14 22:05:22 +0000, Ryan C. Gordon wrote:

Taking this one.

--ryan.

On 2013-07-15 00:56:48 +0000, Ryan C. Gordon wrote:

Created attachment 1234
test program that doesn't trigger issue.

I can't reproduce this here. I've attached my simple test program. Do you have something that's a little more complex that triggers it?

--ryan.

On 2013-07-15 07:03:19 +0000, Sik wrote:

Created attachment 1235
Test program that shows the behavior

Turns out to be more specific than I thought at first. One needs to call SDL_ShowCursor(SDL_FALSE) and then SDL_Quit() in order for it to trigger. Given this is one of the few functions supposed to work even when SDL isn't initialized (as one of its main purposes is to show error messages), this is probably a rather important bug.

This bug doesn't happen if the function is called without SDL having been ever initialized, nor if the cursor is visible when SDL is deinitialized.

On 2013-07-15 07:05:38 +0000, Sik wrote:

Comment on attachment 1235
Test program that shows the behavior

Turns out to be more specific than I thought at first. One needs to call SDL_ShowCursor(SDL_FALSE) and then SDL_Quit() in order for it to trigger. Given this is one of the few functions supposed to work even when SDL isn't initialized (as one of its main purposes is to show error messages), this is probably a rather important bug.

This bug doesn't happen if the function is called without SDL having been ever initialized, nor if the cursor is visible when SDL is deinitialized.

On 2013-07-15 14:26:33 +0000, Ryan C. Gordon wrote:

Ok, Attachment # 1235 definitely crashes for me. Looking into this.

--ryan.

On 2013-07-15 14:39:03 +0000, Ryan C. Gordon wrote:

Fixed in http://hg.libsdl.org/SDL/rev/f2f794cf85c0

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