[Bug 30154] New: wine is blocking X and flooding Xorg log with EDID requests
http://bugs.winehq.org/show_bug.cgi?id=30154 Bug #: 30154 Summary: wine is blocking X and flooding Xorg log with EDID requests Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mikopp(a)gmail.com Classification: Unclassified Product Name: CrossOver Linux Public Version: 11.0.0 Product Version: 11.0.0.25949 Build Tag: cxoffice-11.0.0rc2 Build Timestamp: 20120302T180027Z wine is flooding xorg with EDID requests (xrandr) and causing X to block for several seconds!. Every progress bar update triggers an xrandr request and a block of X. I am aware that there is a standing kernel bug, and that there has been an old wine bug for this (bug 11470), but the real problem is that: 1) wine is calling xrandr repeatedly for every app start (and during running) which it shouldn't. 2) wine should use xrandr --current which does not reprobe but takes the current results and does not block at all! ( also see active conversation https://lkml.org/lkml/2012/2/24/22) Using xrandr --current would solve the issue. It is still the question why wine needs to probe so often in the first place, no other app needs to do this. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #1 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-13 06:36:39 CDT --- Please report this to the creators of the product you are using. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #2 from mikopp(a)gmail.com 2012-03-13 07:02:21 CDT --- It is a wine issue as can be seen from the kernel discussion. and it's wine 1.4-rc5. I have reported it to cross over but as it is a wine issue I wanted to report it to the source. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #3 from mikopp(a)gmail.com 2012-03-13 07:08:29 CDT --- oh BTW, http://wiki.jswindle.com/index.php/Wine_Registry setting UseXRandR to "N" also makes this go away. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID --- Comment #4 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-13 22:11:30 CDT --- (In reply to comment #3)
oh BTW, http://wiki.jswindle.com/index.php/Wine_Registry setting UseXRandR to "N" also makes this go away.
This clearly indicates a bug in the xrandr implementation of your video drivers. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh(a)gmail.com Version|unspecified |1.4-rc5 Resolution|INVALID |UPSTREAM --- Comment #5 from Jerome Leclanche <adys.wh(a)gmail.com> 2012-03-14 08:06:29 CDT --- Hi mikopp, could you link us to the upstream bug report once created? I'm not sure how it's obvious that it's a driver bug, but still. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #6 from mikopp(a)gmail.com 2012-03-15 04:41:03 CDT --- Hi there are multiple upstream bugs * XRANDR operations very slow unless https://bugs.freedesktop.org/show_bug.cgi?id=41059 * Connection probing causes stalls https://bugs.freedesktop.org/show_bug.cgi?id=29536 But I maintain that there is a wine bug! wine is using this interface wrong! Why is wine even using xrandr in my situation and why is it doing so many many times? * I have disabled changing of resolution or anything by wine, so why is it even calling xrandr. BTW nothing in the behaviour of wine changes by disabling xrandr via the mentioned regedit setting! so in my configuration it is clearly not needed! * wine should not request this 8 times during an application start, and multiple times thereafter during things like file open or save. * if it does it should use "xrandr --current" instead of forcing a probe! These things should be fixed in wine in my mind, because while there is an upstream bug it has long been there and never effected any applications at all! So please consider to reopen this and fix wines usage of the interface. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #7 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-15 06:57:39 CDT --- Wine doesn't use command line xrandr tool, Wine uses xrandr APIs directly. Wine queries xrandr once at start up to enumerate available video modes, so it can return the data to the apps which query them. Also Wine calls xrandr API to change the display mode on behalf of an application request. If a simple video modes query makes your X block for several seconds that's clearly a bug in your video drivers. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #8 from mikopp(a)gmail.com 2012-03-15 08:29:50 CDT --- Oh it is a bug in the video layer don't get me wrong. But - wine is requesting the information again and again - and is forcing xrandr to do a reprobe instead of just getting the current information. Those two things are wine bugs. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|UPSTREAM | Ever Confirmed|0 |1 --- Comment #9 from Jerome Leclanche <adys.wh(a)gmail.com> 2012-03-15 08:36:32 CDT --- I'm reopening until someone who worked with xrandr on wine can shed some light on this. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #10 from Henri Verbeet <hverbeet(a)gmail.com> 2012-03-15 09:54:45 CDT --- I think there's a legitimate issue, although it's more of an enhancement than a Wine bug as such. Even on more reasonable hardware that doesn't take several seconds to probe outputs or causes e.g. screen corruption while probing, probing isn't entirely free. Getting screen configuration info without probing is a XRandR 1.3 feature though, while Wine's XRandR code is still all XRandR 1.2. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |UPSTREAM --- Comment #11 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-15 10:30:38 CDT --- (In reply to comment #8)
Oh it is a bug in the video layer don't get me wrong. But
- wine is requesting the information again and again - and is forcing xrandr to do a reprobe instead of just getting the current information.
Those two things are wine bugs.
No, Wine doesn't behave like you describe it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|UPSTREAM | Severity|normal |enhancement --- Comment #12 from Jerome Leclanche <adys.wh(a)gmail.com> 2012-03-15 10:58:24 CDT --- Dmitry, as Henri said there is a legitimate issue at root. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |UPSTREAM --- Comment #13 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-15 11:36:50 CDT --- (In reply to comment #12)
Dmitry, as Henri said there is a legitimate issue at root.
No, there is no one, please do not reopen. See an explanation above. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #14 from mikopp(a)gmail.com 2012-03-15 11:45:44 CDT --- My xorg log proves that wine applications do as i described. There is a kernel discussion about this as well explicitly talking about wine flooding xorg with these requests. if somebody is interested let me know. i am happy with the workaround... -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Henri Verbeet <hverbeet(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|UPSTREAM | --- Comment #15 from Henri Verbeet <hverbeet(a)gmail.com> 2012-03-15 12:11:12 CDT --- (In reply to comment #13)
(In reply to comment #12)
Dmitry, as Henri said there is a legitimate issue at root.
No, there is no one, please do not reopen. See an explanation above. Here you go: http://cgit.freedesktop.org/xorg/xserver/tree/randr/rrscreen.c?id=xorg-serve...
How this relates to Wine causing EDID polls is left as a (trivial) exercise for the reader, although I'll help a bit by saying that ProcRRGetScreenInfo() is the X server request handler for the RRGetScreenInfo request, and that you'll want to look at how RRGetInfo() is implemented. Please do research these things a bit before just closing bugs. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #16 from Austin English <austinenglish(a)gmail.com> 2012-03-15 13:10:47 CDT --- (In reply to comment #14)
My xorg log proves that wine applications do as i described. There is a kernel discussion about this as well explicitly talking about wine flooding xorg with these requests. if somebody is interested let me know. i am happy with the workaround...
A link would be helpful. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #17 from Henri Verbeet <hverbeet(a)gmail.com> 2012-03-15 13:24:20 CDT --- (In reply to comment #16)
(In reply to comment #14)
My xorg log proves that wine applications do as i described. There is a kernel discussion about this as well explicitly talking about wine flooding xorg with these requests. if somebody is interested let me know. i am happy with the workaround...
A link would be helpful.
https://lkml.org/lkml/2012/2/23/268, I imagine. It mostly talks about the hardware / kernel side of this though, not so much about Wine. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #18 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-15 18:13:12 CDT --- (In reply to comment #15)
Here you go: http://cgit.freedesktop.org/xorg/xserver/tree/randr/rrscreen.c?id=xorg-serve...
How this relates to Wine causing EDID polls is left as a (trivial) exercise for the reader, although I'll help a bit by saying that ProcRRGetScreenInfo() is the X server request handler for the RRGetScreenInfo request, and that you'll want to look at how RRGetInfo() is implemented. Please do research these things a bit before just closing bugs.
Wine is a user level application, it's by definition a kernel/vidoe driver bug if doing a simple video modes query (just once at start up!) makes X block for several seconds. Wine doesn't do anything of the listed below things as the reporter claims:
- wine is requesting the information again and again - and is forcing xrandr to do a reprobe instead of just getting the current information.
https://lkml.org/lkml/2012/2/23/268, I imagine. It mostly talks about the hardware / kernel side of this though, not so much about Wine.
It talks about a bug in the Intel video driver. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #19 from Henri Verbeet <hverbeet(a)gmail.com> 2012-03-15 19:23:09 CDT --- (In reply to comment #18)
Wine is a user level application, it's by definition a kernel/vidoe driver bug if doing a simple video modes query (just once at start up!) makes X block for several seconds.
I don't think anyone denied there was a driver/hardware bug involved as well. But that doesn't change the fact that the way XRandR is currently used in Wine causes completely unnecessary EDID polls. This doesn't happen just once on startup either. As the linked source shows, calling XRRGetScreenInfo() causes a poll. X11DRV_XRandR_GetCurrentMode() calls XRRGetScreenInfo(). This is what is used to implement the ENUM_CURRENT_SETTINGS part of the EnumDisplaySettings*() calls, and it's certainly not unheard of for applications to call those. You can certainly argue that this bug isn't a very high priority for Wine, and that it's more important to get the driver fixed so that polls aren't so expensive. You can't argue that Wine doesn't cause these polls.
Wine doesn't do anything of the listed below things as the reporter claims:
- wine is requesting the information again and again Calls to EnumDisplaySettings*() with ENUM_CURRENT_SETTINGS do this.
- and is forcing xrandr to do a reprobe instead of just getting the current information. Just about any XRandR 1.2 query will do this. The way to fix it is to use XRandR 1.3 RRGetScreenResourcesCurrent for querying, and e.g. RRScreenChangeNotify events to get notified of configuration changes. This is practically needed for proper multi-head support anyway, and listening for the appropriate events will also fix the issue where applications are unaware of mode changes by other applications.
-- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #20 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-15 23:17:10 CDT --- (In reply to comment #19)
I don't think anyone denied there was a driver/hardware bug involved as well. But that doesn't change the fact that the way XRandR is currently used in Wine causes completely unnecessary EDID polls.
(1)
- wine is requesting the information again and again Calls to EnumDisplaySettings*() with ENUM_CURRENT_SETTINGS do this.
- and is forcing xrandr to do a reprobe instead of just getting the current information. Just about any XRandR 1.2 query will do this.
(2) Aren't (1) and (2) assume that Wine has nothing to do with broken xrandr implementations?
The way to fix it is to use XRandR 1.3 RRGetScreenResourcesCurrent for querying, and e.g. RRScreenChangeNotify events to get notified of configuration changes. This is practically needed for proper multi-head support anyway, and listening for the appropriate events will also fix the issue where applications are unaware of mode changes by other applications.
The fact that setting UseXRandR to "N" in the registry makes the problem go away, and that you think that using xrandr 1.3 will avoid the bug suggests that video driver is able to behave sanely. Why underlying behaviour of the driver is so drastically different, and what Wine has to do with it is left as an exercise for the reader. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #21 from Henri Verbeet <hverbeet(a)gmail.com> 2012-03-16 03:23:24 CDT --- It's a valid request to ask Wine to take advantage of new XRandR 1.3 features. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #22 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-16 04:31:19 CDT --- (In reply to comment #21)
It's a valid request to ask Wine to take advantage of new XRandR 1.3 features.
Yes, but it has nothing to do with this bug report, and should be filed as a separate enhancement request. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #23 from Jerome Leclanche <adys.wh(a)gmail.com> 2012-03-16 05:31:43 CDT --- (In reply to comment #22) Holy politics, give it a rest Dmitry. User files bug, valid issue + driver bug uncovered, valid issue is targeted. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |UPSTREAM --- Comment #24 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-16 05:47:30 CDT --- (In reply to comment #23)
(In reply to comment #22) Holy politics, give it a rest Dmitry. User files bug, valid issue + driver bug uncovered, valid issue is targeted.
I don't understand where you saw politics or a valid Wine issue. If you admit that it's a driver bug, then this report should be closed. There are at least 2 problems with this report: 1. it's filed for CrossOver Linux -> INVALID 2. it's about an Intel driver bug -> UPSTREAM Go ahead and create a separate enhancement request for xrandr 1.3 support. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #25 from Jerome Leclanche <adys.wh(a)gmail.com> 2012-03-16 05:48:09 CDT --- (In reply to comment #24) The least you could do is do that yourself. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #26 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-16 06:02:16 CDT --- (In reply to comment #25)
The least you could do is do that yourself.
I don't see any single reason for that. Comment 20 has some points why. If you think that adding xrandr 1.3 support will help to workaround problems with broken xrandr implementations in drivers - good luck with that. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #27 from Jerome Leclanche <adys.wh(a)gmail.com> 2012-03-16 06:04:44 CDT --- (In reply to comment #26) The reason for that is you keep insisting *this* bug be closed and *another* bug be opened when it's completely fine to use this one. So yes, it's the least you could do. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=30184 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #28 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-16 06:16:58 CDT --- (In reply to comment #27)
The reason for that is you keep insisting *this* bug be closed and *another* bug be opened when it's completely fine to use this one. So yes, it's the least you could do.
I insist on opening a separate request for xrandr 1.3 support because it has nothing to do with this report. Please do not hijack this report for that. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #29 from Alexandre Julliard <julliard(a)winehq.org> 2012-03-16 06:50:10 CDT --- Dmitry, please stop being such a PITA. Yes, there's a driver bug, but that one can be tracked in its own bug tracker. Here it's perfectly fine to make this bug be about adding a work around to Wine to mitigate the problem, even if that's not how the reporter described it initially. If we only handle bugs that have been perfectly described by the user from the beginning, we might as well shut bugzilla down. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #30 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-16 07:12:47 CDT --- (In reply to comment #29)
Dmitry, please stop being such a PITA.
Thanks for the nice introductory words.
Yes, there's a driver bug, but that one can be tracked in its own bug tracker. Here it's perfectly fine to make this bug be about adding a work around to Wine to mitigate the problem, even if that's not how the reporter described it initially. If we only handle bugs that have been perfectly described by the user from the beginning, we might as well shut bugzilla down.
Then I suggest to reopen all bugs closed as INVALID in the first place, and target them to some other problem not related to the reporter's issue since it's not the reporter's fault that she/he not described it properly. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #31 from Jerome Leclanche <adys.wh(a)gmail.com> 2012-03-16 07:15:16 CDT --- (In reply to comment #30) Bugzilla is not a contest for best bug description, it's a user-friendly tool to help developers. If the user files a valid bug but does not describe it properly, theres no need to make them file another. And yes, a lot of bugs you close as invalid could just as well be refined. Discussion is moot, I filed bug #30184 anyway. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #32 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-16 11:01:37 CDT --- (In reply to comment #31)
And yes, a lot of bugs you close as invalid could just as well be refined.
Be my guest, go ahead and reopen all of them. Don't waste your time arguing about validity of a bug, user is always right. Oh well, just don't forget to put some time into each of them and investigate the problem, ask for some logs. Have fun, it's so much easier to do that kind of thing instead of investigating/fixing some real bug. Nothing personal, feel free to join Henri and request banning my bugzilla permissions (although no Henri, I'm not a bugzilla admin). -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #33 from Henri Verbeet <hverbeet(a)gmail.com> 2012-03-16 11:17:58 CDT --- (In reply to comment #32)
Nothing personal, feel free to join Henri and request banning my bugzilla permissions (although no Henri, I'm not a bugzilla admin). I don't think I did such a thing. I did openly question if the way you use your bugzilla privileges is in the best interest of the Wine project, but given the way this bug in particular was handled I don't think that was inappropriate.
-- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #34 from Austin English <austinenglish(a)gmail.com> 2012-03-16 13:57:17 CDT --- (In reply to comment #32)
(In reply to comment #31)
And yes, a lot of bugs you close as invalid could just as well be refined.
Be my guest, go ahead and reopen all of them. Don't waste your time arguing about validity of a bug, user is always right. Oh well, just don't forget to put some time into each of them and investigate the problem, ask for some logs. Have fun, it's so much easier to do that kind of thing instead of investigating/fixing some real bug.
No one forces you to do bugzilla triage. If you prefer, please spend your efforts coding and let others handle bugzilla. Not all invalid bugs were immediately invalid on filing, but instead were determined, e.g., to be a driver bug that wine exposes. Other bugs that could potentially be closed as invalid after the first comment were instead fixed, because someone asked for logs and helped the user to get a valid bug report. Many current active bug reporters have started by filing "invalid" bug reports (myself included), but are now a very valuable resource of valid, targeted bugs. It's like my grandmother used to say, "If you don't have anything nice to say, don't say anything at all." -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #35 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-16 15:05:13 CDT --- Why don't you just reopen this bug then, if you think I shouldn't have closed it? Simply provide a technical explanation why you think it's a Wine bug, then reopen other similar bugs about crashes in video drivers - be it OpenGL or xrandr related, if you believe that Wine should have workarounds for such driver bugs. Also please stop closing bugs reported for PlayOnLinux, IEs4Linux and others like you do now, this bug is reported for Crossover, why do you treat it differently? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #36 from Alexandre Julliard <julliard(a)winehq.org> 2012-03-16 17:44:10 CDT --- (In reply to comment #35)
Why don't you just reopen this bug then, if you think I shouldn't have closed it?
3 different people already did that, and every time you closed it again. How long do we have to keep doing it?
Simply provide a technical explanation why you think it's a Wine bug, then reopen other similar bugs about crashes in video drivers - be it OpenGL or xrandr related, if you believe that Wine should have workarounds for such driver bugs.
In some cases it should have workarounds, and in some cases it shouldn't. Is it so hard to understand that different bugs may need different treatment? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #37 from Austin English <austinenglish(a)gmail.com> 2012-03-16 18:51:40 CDT --- (In reply to comment #35)
Why don't you just reopen this bug then, if you think I shouldn't have closed it? Simply provide a technical explanation why you think it's a Wine bug, then reopen other similar bugs about crashes in video drivers - be it OpenGL or xrandr related, if you believe that Wine should have workarounds for such driver bugs. Also please stop closing bugs reported for PlayOnLinux, IEs4Linux and others like you do now, this bug is reported for Crossover, why do you treat it differently?
Regarding PlayOnLinux and similar bugs, simply ask the reporter to retest with vanilla wine and a clean WINEPREFIX. If the bug is still present, valid. If not or they don't retest, close invalid/abandoned. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #38 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-16 20:41:48 CDT --- (In reply to comment #37)
Regarding PlayOnLinux and similar bugs, simply ask the reporter to retest with vanilla wine and a clean WINEPREFIX. If the bug is still present, valid. If not or they don't retest, close invalid/abandoned.
I don't see in the comments of this report that you did that. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|UPSTREAM | Ever Confirmed|1 |0 --- Comment #39 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-16 20:45:26 CDT --- (In reply to comment #36)
Simply provide a technical explanation why you think it's a Wine bug, then reopen other similar bugs about crashes in video drivers - be it OpenGL or xrandr related, if you believe that Wine should have workarounds for such driver bugs.
In some cases it should have workarounds, and in some cases it shouldn't. Is it so hard to understand that different bugs may need different treatment?
Please add a workaround for this one. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #40 from Jerome Leclanche <adys.wh(a)gmail.com> 2012-03-16 21:08:48 CDT --- *** Bug 30184 has been marked as a duplicate of this bug. *** -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #41 from Austin English <austinenglish(a)gmail.com> 2012-03-17 01:57:07 CDT --- (In reply to comment #38)
(In reply to comment #37)
Regarding PlayOnLinux and similar bugs, simply ask the reporter to retest with vanilla wine and a clean WINEPREFIX. If the bug is still present, valid. If not or they don't retest, close invalid/abandoned.
I don't see in the comments of this report that you did that.
I did not in this bug, I got to the discussion a bit late. If you'd like a reference where I did, I can find one, but I think that would be somewhat petty. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #42 from Dmitry Timoshkov <dmitry(a)baikal.ru> 2012-03-17 04:04:32 CDT --- (In reply to comment #41)
Regarding PlayOnLinux and similar bugs, simply ask the reporter to retest with vanilla wine and a clean WINEPREFIX. If the bug is still present, valid. If not or they don't retest, close invalid/abandoned.
I don't see in the comments of this report that you did that.
I did not in this bug, I got to the discussion a bit late. If you'd like a reference where I did, I can find one, but I think that would be somewhat petty.
There is no need, I know that you do that most of the time. The question was why this report was treated differently, and even once you joined lately, instead of doing things you mentioned above you preferred to teach me some of your grandmother's wisdom. I'd ask for some consistency at least. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Fernando Martins <fernando(a)cmartins.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fernando(a)cmartins.nl --- Comment #43 from Fernando Martins <fernando(a)cmartins.nl> 2012-03-17 19:49:50 CDT ---
I'd ask for some consistency at least.
Hmm, some useful quotes about consistency: Although: "Consistency is the foundation of virtue." in reality. "Inconsistency is the only thing in which men are consistent." and more importantly for the current case, no offense meant: "Consistency requires you to be as ignorant today as you were a year ago." I do only occasional bug testing and probably I'm wrong, but maybe people are realizing that it is not very productive to strictly close bugs which are "not for wine" when in fact there is still something useful in it? (and pointless to spend time in opening another bug) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 --- Comment #44 from Austin English <austinenglish(a)gmail.com> 2012-03-18 10:40:18 CDT --- (In reply to comment #42)
(In reply to comment #41)
Regarding PlayOnLinux and similar bugs, simply ask the reporter to retest with vanilla wine and a clean WINEPREFIX. If the bug is still present, valid. If not or they don't retest, close invalid/abandoned.
I don't see in the comments of this report that you did that.
I did not in this bug, I got to the discussion a bit late. If you'd like a reference where I did, I can find one, but I think that would be somewhat petty.
There is no need, I know that you do that most of the time. The question was why this report was treated differently, and even once you joined lately, instead of doing things you mentioned above you preferred to teach me some of your grandmother's wisdom. I'd ask for some consistency at least.
Another bug was already filed by that time, bug 30184, to request the transition to Xrandr 1.3. Honestly, I'd rather close this bug and reopen that one, since this one has a lot of unrelated discussion, but I don't feel strongly about it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE --- Comment #45 from Jerome Leclanche <adys.wh(a)gmail.com> 2012-03-26 08:00:32 CDT --- Dupe. *** This bug has been marked as a duplicate of bug 30184 *** -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30154 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #46 from Jerome Leclanche <adys.wh(a)gmail.com> 2012-03-26 08:00:55 CDT --- Closing. Further discussion in the other bug, as austin said theres too much offtopic in here. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org