http://bugs.winehq.org/show_bug.cgi?id=19194
Summary: battlefield 2 fullscreen issues under xfce Product: Wine Version: 1.1.25 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: michael.s.gilbert@gmail.com
first off, i just want to say that it is awesome that battlefield 2 is now (apparently) fully working. however, when using xfce, the fullscreen mode only gets partially rendered on screen (an 800x600 section for me), which makes it impossible to play. however, the game works perfectly under gnome, which is great! but my day-to-day desktop environment is xfce, and i would like to stay there when i play. thanks for the great work on wine!
http://bugs.winehq.org/show_bug.cgi?id=19194
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2009-07-11 02:21:38 --- Have you tried to report the bug to xfce developers? Most likely its an xfce bug.
http://bugs.winehq.org/show_bug.cgi?id=19194
Michael Gilbert michael.s.gilbert@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.1.25 |1.1.26 Severity|minor |normal
--- Comment #2 from Michael Gilbert michael.s.gilbert@gmail.com 2009-07-19 19:59:26 --- i don't see how this could be a problem with the desktop environment... and even if it is, could may i request that you work with xfce upstream developers to get them to fix the problem, rather than taking the easy road and ignoring the issue?
note that i've tried half-life 2 and counter-strike, and their fullscreens work just fine under xfce with wine 1.1.26. i understand that this isn't a significant enough sample to "prove" this point, but it does provide evidence that wine has the problem and not the desktop environment.
http://bugs.winehq.org/show_bug.cgi?id=19194
--- Comment #3 from Michael Gilbert michael.s.gilbert@gmail.com 2009-07-19 20:11:50 --- xfce bug submitted [1].
[1] http://bugzilla.xfce.org/show_bug.cgi?id=5592
http://bugs.winehq.org/show_bug.cgi?id=19194
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.1.26 |1.1.25 Severity|normal |minor
--- Comment #4 from Vitaliy Margolen vitaliy@kievinfo.com 2009-07-19 20:18:51 --- You've been told countless times not to change Wine version. You doing it why? You've been linked to severity description, and yet you still fail to read definitions of severity levels.
http://bugs.winehq.org/show_bug.cgi?id=19194
--- Comment #5 from Michael Gilbert michael.s.gilbert@gmail.com 2009-07-19 22:41:18 --- first of all, is this attitude really necessary? does it really help make wine better? is it constructive?
secondly, i have not been "told" any of these things and would like to see evidence otherwise.
thirdly, if you expect users not to modify these things, then the ability to do so should be disabled.
fourthly, the severity bins are certainly not black and white (no text ever is, which is legal systems and religions are such messes), and should not be. and really, in the end, the bins don't matter a whole lot any way. so, unless i was trying to say that this is critical or something obviously wrong, it isn't a big deal. and it's certainly not worth getting worked up about...
and finally, i tested against wine 1.1.26, and found that the bug still exists, so i see no reason why i should not be allowed to update the affected version...but i will not change it because i don't feel like dealing with this rediculous conflict.
good day to you.
http://bugs.winehq.org/show_bug.cgi?id=19194
Richard shiningarcanine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |shiningarcanine@gmail.com
--- Comment #6 from Richard shiningarcanine@gmail.com 2010-05-26 18:16:15 --- I think that the issue here is that the WINE version reported by the bug is meant to be the version where the bug first manifested and it is assumed to still be an issue in newer versions until the bug is closed.
http://bugs.winehq.org/show_bug.cgi?id=19194
--- Comment #7 from Austin English austinenglish@gmail.com 2012-03-19 14:53:00 CDT --- This is your friendly reminder that there has been no bug activity for 650 days. Is this still an issue in current (1.4 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=19194
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |frederic.delanoy@gmail.com Resolution| |DUPLICATE
--- Comment #8 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-04-02 19:06:57 CDT --- Likely a dupe (bug 30213 has better info, so marking this bug as dupe).
*** This bug has been marked as a duplicate of bug 30213 ***
http://bugs.winehq.org/show_bug.cgi?id=19194
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-04-02 19:07:15 CDT --- Closing.
-
wine-bugs＠winehq.org