| Summary: | Proprietary game Minecraft fails to enter fullscreen | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | andre35822 |
| Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED INVALID | QA Contact: | Default DRI bug account <dri-devel> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | dmesg output when opening the game and trying to set it in fullscreen | ||
We haven't had any other reports of this issue over the past 5 years. I'm going to assume it was either fixed or was an issue with the OPs setup. Closing as invalid, feel free to reopen and add updated information if it is indeed still a problem. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 121095 [details] dmesg output when opening the game and trying to set it in fullscreen I am on Arch Linux with Mesa 11.1, Kernel 4.3.3, llvm 3.7.1-1 and have an AMD 7950. The issue that is occurring is that Minecraft is failing to enter fullscreen with multiple DEs (Openbox, XFCE, and Cinnamon are the ones that I have tried, and all do not properly enter fullscreen). When I hit the fullscreen option in the game, the window sort of turns completely transparent or sometimes the theme of my desktop environment but I can not see anything. I can hear sounds from the game and clicking/pressing keyboard buttons are actually working in the game so it is as if the game is working fine just it is not rendering the window correctly. (I can hear myself breaking blocks). If I quit the game in this state and re-open it, the game will launch in fullscreen, but if I alt-tab or set it back to window mode and try to enter fullscreen mode, the same that I stated above occurs. I would like to note that I am using OpenJRE and not Sun Java's though someone with an AMD GPU and Sun java stated they experience the same issue. So I really think it is down to a mesa bug or something? I am not sure how it works.