Fullscreen doesn't work since Lucid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mupen64plus (Debian) |
Fix Released
|
Unknown
|
|||
mupen64plus (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mupen64plus
After an update to Lucid Lynx, the fullscreen mode in mupen64plus (1.5+dfsg1-7build1) doesn't work anymore. Neither can you switch to fullscreen by pressing Alt+Return, nor does the "Always start in fullscreen mode" option work.
Everything worked fine in Karmic Koala.
TEST CASE: To test the problem just use a driver with a very long vendor string. Just patch your libgl to output such a string (256 bytes should be sufficient). Use different random strings and test it on different platforms to create the different types of crashes/random misbehavior.
The m_strDeviceStats is only used in one place:
{{{
sprintf(
TRACE0(
printf("%s\n", m_strDeviceStats);
}}}
Changed in mupen64plus (Ubuntu): | |
status: | Incomplete → Fix Committed |
Changed in mupen64plus (Debian): | |
status: | Unknown → Fix Committed |
Changed in mupen64plus (Debian): | |
status: | Fix Committed → Fix Released |
Changed in mupen64plus (Ubuntu): | |
status: | Fix Released → Confirmed |
Changed in mupen64plus (Ubuntu): | |
assignee: | nobody → Shane Wolfram (dazinmad) |
assignee: | Shane Wolfram (dazinmad) → nobody |
tags: | added: verification-needed |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
tags: | added: testcase |
There were no changes to mupen64plus. Please contact the sdl maintainer or your the maintainer of the graphics driver.
You didn't provide any kind of information about your used plugins or your graphics driver. That would be useful in that kind of bug report. rice just uses SDL_WM_ ToggleFullScree n to enable the fullscreen mode and glide64 just sets the SDL_FULLSCREEN flag. So it should not be a real mupen64plus problem if it worked before.
It could also be kms or uxa related if there were such changes in your driver. Have you tried to use a resolution which is exact the native resolution?