April 2016 - Wine-Devel - list.winehq.org

Re: Winegstreamer entry on Wine FAQ Wiki Page

by Rosanne DiMesio

On Thu, 7 Apr 2016 15:25:26 -0500 Austin English <austinenglish(a)gmail.com> wrote: > Getting winegstreamer to work certainly has been, at least in the past. > Yes, it has. The dominant problems are: 1. I'm trying to build Wine on a 64 bit system. ./configure keeps telling me it can't find the 32 bit gstreamer development files, but I have them installed. 2. My app doesn't work and winegstreamer is complaining about a missing plugin. Which package should I install? (Or the variation, "But I've already installed all the gstreamer plugins available in the repository and it still doesn't work. What should I do?") The info on building with gstreamer support on a 64 bit system does need to be added to the Building Wine page (it's on my wiki todo list). The second item is difficult to handle in the FAQ because the answers vary so much by distro. Specific information could be added to the individual distro pages (Debian in particular seems to need it). -- Rosanne DiMesio dimesio(a)earthlink.net

April 7, 2016

Re: [PATCH 2/2] cmd: Add support for || and &&.

by Sebastian Lackner

On 07.04.2016 22:12, Qian Hong wrote: > Slightly improved based on Mikhail Bystryantsev's patch, add support for those built-in commands which does not change %ERRORLEVEL%. > > Signed-off-by: Qian Hong <qhong(a)codeweavers.com> > --- > programs/cmd/builtins.c | 14 +++++++++++--- > programs/cmd/tests/test_builtins.cmd | 13 +++++++++++++ > programs/cmd/tests/test_builtins.cmd.exp | 13 ++++++++++++- > programs/cmd/tests/test_cmdline.cmd | 20 ++++++++++++++++++++ > programs/cmd/tests/test_cmdline.cmd.exp | 22 ++++++++++++++++++++++ > programs/cmd/wcmd.h | 1 + > programs/cmd/wcmdmain.c | 26 ++++++++++++++++++++++++-- > 7 files changed, 103 insertions(+), 6 deletions(-) > Has it really something to do with builtin-commands which do not change %ERRORLEVEL%? I think the tests only cover one of those commands, a couple of additional tests would probably not hurt. The lack of tests is also the reason why I haven't merged this into Staging yet. If this turns out to be right way to solve it, I would suggest to define a function check_errorlevel() which checks 'errorlevel' and 'changed' at once.

April 7, 2016

Re: Winegstreamer entry on Wine FAQ Wiki Page

by Austin English

On Thu, Apr 7, 2016 at 3:14 PM, Rosanne DiMesio <dimesio(a)earthlink.net> wrote: > On Thu, 7 Apr 2016 12:28:36 -0400 > NP-Hardass <NP-Hardass(a)gentoo.org> wrote: > >> The Wine Wiki has 1 place for troubleshooting information, that's that >> FAQ. > > You obviously haven't read much of the wiki. > >> The entire "Troubleshooting" section of that page is littered >> with troubleshooting information that is devoid of questions. > > You are correct, many items are not phrased as questions, usually because trying to do so would result in tortured syntax. They do, however, all address issues that have come up frequently for ordinary users on the forum and/or bugzilla. "Verifying winegstreamer support" hasn't. Getting winegstreamer to work certainly has been, at least in the past. -- -Austin

April 7, 2016

Re: [PATCH 2/2] cmd: Add support for || and &&.

by Qian Hong

I should add "From Mikhail Bystryantsev." in commit message, but something was wrong with my mail client. (Could you please use git send-email to send patches in the future? --- from Henri. :D) On Fri, Apr 8, 2016 at 4:12 AM, Qian Hong <qhong(a)codeweavers.com> wrote: > Slightly improved based on Mikhail Bystryantsev's patch, add support for > those built-in commands which does not change %ERRORLEVEL%. > > Signed-off-by: Qian Hong <qhong(a)codeweavers.com> > --- > programs/cmd/builtins.c | 14 +++++++++++--- > programs/cmd/tests/test_builtins.cmd | 13 +++++++++++++ > programs/cmd/tests/test_builtins.cmd.exp | 13 ++++++++++++- > programs/cmd/tests/test_cmdline.cmd | 20 ++++++++++++++++++++ > programs/cmd/tests/test_cmdline.cmd.exp | 22 ++++++++++++++++++++++ > programs/cmd/wcmd.h | 1 + > programs/cmd/wcmdmain.c | 26 ++++++++++++++++++++++++-- > 7 files changed, 103 insertions(+), 6 deletions(-) > > > > > -- Regards, Qian Hong - http://www.codeweavers.com

April 7, 2016

Re: Winegstreamer entry on Wine FAQ Wiki Page

by Rosanne DiMesio

On Thu, 7 Apr 2016 12:28:36 -0400 NP-Hardass <NP-Hardass(a)gentoo.org> wrote: > The Wine Wiki has 1 place for troubleshooting information, that's that > FAQ. You obviously haven't read much of the wiki. > The entire "Troubleshooting" section of that page is littered > with troubleshooting information that is devoid of questions. You are correct, many items are not phrased as questions, usually because trying to do so would result in tortured syntax. They do, however, all address issues that have come up frequently for ordinary users on the forum and/or bugzilla. "Verifying winegstreamer support" hasn't. > I'm a downstream maintainer, and in bumping Wine, I had to verify that > the Gstreamer functionality was working. The FAQ is aimed at ordinary users. Your needs are obviously quite different. > In my experience trying to > get and verify that Winegstreamer is working, even with > WINEDEBUG=+gstreamer, Wine will often output ABSOLUTELY nothing > related to Gstreamer, even when it is running Gstreamer. Moreover, > when Wine encounters a lack of Gstreamer plugin, it straight up > crashes Wine (sometimes just a straight up core dump, I encountered no > recommendation of plugins, just straight, meaningless coredump), > meaning people aren't going to say, "I wonder why I seem to be missing > this Gstreamer plugin..." They are going to be saying, "Time to file > a bug report on WineHQ, wine-x.x.x crashes when trying to run app xyz." > Ordinary users faced with a crash and no console output mentioning gstreamer or winegstreamer would never think to look under an item entitled "Verifying winegstreamer support" for a solution to their problem. > Let's be clear here, Winegstreamer uses Gstreamer to create DirectShow > filter graphs, so investigating filter graphs is the most > straightforward means of identifying if support is working correctly. > To that end, one can either use the Microsot provided "graphedit.exe" > which requires installing the Microsoft SDK (which isn't even > supported, and is extremely heavyweight), or one can install one of > the third party DirectShow filter graph viewing/editing programs. > That leaves you with several options, one of the the proprietary, > nonfree applications, or one of several open source or free > applications. That sounds like information that might be suitable for one of the pages aimed at developers. -- Rosanne DiMesio dimesio(a)earthlink.net

April 7, 2016

Re: Winegstreamer entry on Wine FAQ Wiki Page

by NP-Hardass

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 04/07/2016 07:14 AM, Rosanne DiMesio wrote: > On Thu, 7 Apr 2016 02:54:28 -0400 NP-Hardass > <NP-Hardass(a)gentoo.org> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> Hello, >> >> About a month ago, I created a Wine Wiki account and requested >> that it be activated, explicitly so that I could add an entry to >> the FAQ page [1]. After going to reference this new entry to >> someone today, I noticed that my changes were reverted soon after >> my submission and the page was subsequently locked [2]. This >> submission was made after consulting wine developer, Sebastian >> Lackner. >> >> I think this information would be very useful to users starting >> to adopt Winegstreamer, now that Andrew Eikum has updated it to >> gstreamer 1.0 and it is functioning again. I'd like to inquire >> why the change was reverted, if my content is deemed unnecessary, >> and if not, why it was not moved elsewhere. >> >> - -- NP-Hardass Gentoo Wine maintainer >> >> [1] https://wiki.winehq.org/index.php?title=FAQ [2] >> https://wiki.winehq.org/index.php?title=FAQ&action=history > > I reverted the item because: > > 1. It is not a frequently asked question. As written, it is not > even a question. The Wine Wiki has 1 place for troubleshooting information, that's that FAQ. The entire "Troubleshooting" section of that page is littered with troubleshooting information that is devoid of questions. It's the only source of troubleshooting information that you have. > 2. The "answer" to this non-question served no purpose other than > to advertise a third party project, giving the impression that it > was officially recommended and supported here. > > The "information" in that item is not needed. If users are missing > a gstreamer plugin needed by one of their apps, they will find it > out as soon as they try to run the app. The console output will > have a message from gstreamer complaining about the codec that was > not found, and one from Wine suggesting a missing plugin. Users > might need help figuring out exactly which package to install, but > the "tool for developers to build and test DirectShow Graphs" > project you were trying to drive traffic to won't help with that. I'm a downstream maintainer, and in bumping Wine, I had to verify that the Gstreamer functionality was working. In my experience trying to get and verify that Winegstreamer is working, even with WINEDEBUG=+gstreamer, Wine will often output ABSOLUTELY nothing related to Gstreamer, even when it is running Gstreamer. Moreover, when Wine encounters a lack of Gstreamer plugin, it straight up crashes Wine (sometimes just a straight up core dump, I encountered no recommendation of plugins, just straight, meaningless coredump), meaning people aren't going to say, "I wonder why I seem to be missing this Gstreamer plugin..." They are going to be saying, "Time to file a bug report on WineHQ, wine-x.x.x crashes when trying to run app xyz." Let's be clear here, Winegstreamer uses Gstreamer to create DirectShow filter graphs, so investigating filter graphs is the most straightforward means of identifying if support is working correctly. To that end, one can either use the Microsot provided "graphedit.exe" which requires installing the Microsoft SDK (which isn't even supported, and is extremely heavyweight), or one can install one of the third party DirectShow filter graph viewing/editing programs. That leaves you with several options, one of the the proprietary, nonfree applications, or one of several open source or free applications. In this case, the recommendation was to use an open source project. I am not associated with it at all, it just fits the bill. Directly accusing me of trying to advertise for a piece of software is, quite frankly, rude, and serves no purpose here. > > The wiki is not a venue for free advertising. > I repeat the above. - -- NP-Hardass -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXBoq0AAoJEBzZQR2yrxj7zGsQAJB0LyxLttKk9sPeYreIxUSG 3S0HTD/hT+PxpcRCkOSrcVxqEgRWPrA330gs4UJ+qTmq6Gp9ouVUkoxx++ExamZN Qu1BkDbepKN+AKP9pyRB7H/iC9DARrMmPC4QBwTpWw+NC41dEoVJVXhQxZOyD47H toClDxkTPu3tFimFrLJSekGLJSLD49OODDFWcLOPKTdLxDjhjLEQJOlnZf2nKsDx FirIONSPiCd2fYBVcyON8KRglummh1jPbJ/wSuJZRlZESrr2b1Wfn/5i995v870b dLA8XOy+Y2fnxQdPuS9MfpgAigSViuBd7XHWt7PTn1YGLtHnrEdl4zgwA5RWSqrd 4obQsqdleTT3xXQw7FhlrUe4k6TGFEmmV6r4AbXuKGqkLUa7pb075R4/k9MZrT6p QlFqdk9nh0Hu++yhKVTQmEoJkWuvzdrW0/K8awDG0nNr5NDwpg1s491TjoTkeJxC ynDk7Z2+Iimn/IxbIKLDIRCpOj/xRZCR54pWZDAVV34icmgxw8JmBSLmgrjmc5Wr mj3pZLkLrbcJRON9j+1JG6JKKhH/Wkbz9gcY9s5C7Gg6wqsTUh7HIEpinxOrftMb uVNjSnvcsH/lpkSnRk8WQmLW2hmvR0kv/dFE4Fx8CdGkldzypwtMvf9KMmO0aDDS P3dKEFEjOIn8tqiA29fn =Z18C -----END PGP SIGNATURE-----

April 7, 2016

Re: [PATCH 1/2] user32/tests: Message filtering tests for broadcast messages

by Nikolay Sivov

On 07.04.2016 17:57, Marvin wrote: > Hi, > > While running your changed tests on Windows, I think I found new failures. > Being a bot and all I'm not very good at pattern recognition, so I might be > wrong, but could you please double-check? > Full results can be found at > https://testbot.winehq.org/JobDetails.pl?Key=21970 > > Your paranoid android. > > > === w864 (32 bit msg) === > msg.c:6417: Test failed: Update region shouldn't be empty > msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 > msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 > msg.c:6423: Test failed: Regions are different > msg.c:6423: Test failed: Regions are different > msg.c:6423: Test failed: Regions are different > > === w1064 (32 bit msg) === > msg.c:6417: Test failed: Update region shouldn't be empty > msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 > msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 > msg.c:6423: Test failed: Regions are different > msg.c:6423: Test failed: Regions are different > msg.c:6423: Test failed: Regions are different > > === w864 (64 bit msg) === > msg.c:6417: Test failed: Update region shouldn't be empty > msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 > msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 > msg.c:6423: Test failed: Regions are different > msg.c:6423: Test failed: Regions are different > msg.c:6423: Test failed: Regions are different > > === w1064 (64 bit msg) === > msg.c:6417: Test failed: Update region shouldn't be empty > msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 > msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 > msg.c:6423: Test failed: Regions are different > msg.c:6423: Test failed: Regions are different > msg.c:6423: Test failed: Regions are different > > All those failures already exist.

April 7, 2016

Re: [PATCH 2/2] user32: Limit broadcast messages to system and registered ones

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=21971 Your paranoid android. === wvistau64 (32 bit msg) === msg.c:11018: Test failed: expected PeekMessage to return FALSE, got 1 msg.c:11030: Test failed: msg.message = 275 instead of WM_USER msg.c:11032: Test failed: expected PeekMessage to return FALSE, got 1 msg.c:11041: Test failed: msg.message = 1024 instead of WM_TIMER msg.c:11043: Test failed: expected PeekMessage to return FALSE, got 1 === w864 (32 bit msg) === msg.c:6417: Test failed: Update region shouldn't be empty msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different === w1064 (32 bit msg) === msg.c:6417: Test failed: Update region shouldn't be empty msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different === w864 (64 bit msg) === msg.c:6417: Test failed: Update region shouldn't be empty msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different === w1064 (64 bit msg) === msg.c:6417: Test failed: Update region shouldn't be empty msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different

April 7, 2016

Re: [PATCH 1/2] user32/tests: Message filtering tests for broadcast messages

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=21970 Your paranoid android. === w864 (32 bit msg) === msg.c:6417: Test failed: Update region shouldn't be empty msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different === w1064 (32 bit msg) === msg.c:6417: Test failed: Update region shouldn't be empty msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different === w864 (64 bit msg) === msg.c:6417: Test failed: Update region shouldn't be empty msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different === w1064 (64 bit msg) === msg.c:6417: Test failed: Update region shouldn't be empty msg.c:6651: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6653: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different msg.c:6423: Test failed: Regions are different

April 7, 2016

Re: [PATCH 3/3] mshtml: Added more IHTMLXMLHttpRequst::send tests.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=21965 Your paranoid android. === w1064 (64 bit xmlhttprequest) === The test timed out

April 7, 2016