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

Re: Bugzilla: A Call to Arms

by Tony Lambregts

Andriy Palamarchuk wrote: >We already had discussion on wine-devel about >importance of polishing Wine, making a set of >applications to work very well. > >Cruicial in this process is prioritizing of the >issues, work distribution between developers. The >companies already have internal testing and bug fixing >process. > >Of course, each company has their own product-specific >work, but most of the problems are general for Wine. >I suggest to share this work more actively using >Bugzilla. > >Recently there was some work done in cleaning the >issues database and it is in pretty much usable >condition. > >To start using bugzilla more actively I suggest >following steps: >1) define subsystem/direction owners. The owners will >get their system-specific bugs. They won't necessary >fix the bugs themselfs, but will have complete picture >about all the issues in their subsystems and >coordinate the bug fixing. > >Developers, please let me know your areas of >expertese. >I can overview Wine applications. > Let me see if I have this right you want an inventory of who has what area of experise right. For example if a bug report seems to point to a problem with sockets you could in theory assign it to Martin Wick, or if the problem was with copy protection It could be assigned to Laurent Pinchart. Of course that assumes that both of them are ok with this. What exactly do you mean by overview applications? I'm guessing you mean the wine lib applications currently under /programs right? Anyway this would be very usefull to the people who want to triage bugzilla. > >2) more formally define process of bugs handling and >use this process. There is no high qualification >needed to filter out bad bug reports, duplicates, >request users for more information, attach relay trace >to the bug, etc, etc. >Result - developers will have to spend less time on >discussion trivial bugs with users, will have better >bug reports to work on, users will be more involved >with more active feedback. Some users are very >cooperative and some bug reports are really excellent! >I see that Tony Lambregts, Michael Cardenas, others do >a great work with the Bugzilla database. >I'm also going to contribute some time for this. > > Think if we can get a few more people to to help with this it would be better >3) Prioritize bugs. This is, probably, part of (2). >Some bugs, while relatively easy to fix provide very >big value for the end user. Often developers do not >choose such issues to work on, exactly because these >issues do not present challenge to them. >BTW, I do not see a field "Priority" in the bugs >entries. > The Severity field is for this and yes we should use it. > >4) Ask users to submit there problems in Bugzilla. >Submitting Bugzilla report allows us to involve users >more actively, persist their bug reports. > >Bugzilla is a more scalable approach than using >mailing list only. Of course we still will discuss >bugs on the mailing lists, bug big part of >communication will be unloaded. > > If there are no objections can we change the official documentation to say that bugzilla is the place to report bugs. I noticed that when the wineinstall script had a bug in it that it told the users to report it to wine-devel when it should point them to bugzilla. One other comment about this is that bugzilla's address is http://wine.codeweavers.com/bugs/ and I think it scares people away from using it. I have nothing against CodeWeavers but I think If bugzilla's address was http://www.winehq.com/bugzilla users would be certain it is the place for wine bugs >There is a lot to do and discuss. >For me the goal is to have this process not worse than >in Mozilla project. This is impressive: >http://webtools.mozilla.org/miscstats/ >http://mothra.mozilla.org/webtools/miscstats/ > >I also like their bug report form: >http://www.mozilla.org/quality/help/bugzilla-helper.html > >And this is for 1 application only! I'm sure Wine can >generate much bigger volume of bug reports ;-) > >Look forward for your comments. >Andriy > >__________________________________________________ >Do You Yahoo!? >Yahoo! Health - your guide to health and wellness >http://health.yahoo.com > > > >

April 29, 2002

Re: [Help]: Notes Client on WINE with XIM (Chinese/Japanese Input)

by Mike McCormack

Hi Leanne, Which notepad.exe are you using? As far as I understand, Wine has no support for X Input contexts at all, so I don't understand how you can enter Chinese text into Notes... perhaps Notes has it's own input method or you using an Xlib modified for multibyte support? Is your Wine-20020422 tree unmodified? Could you please explain your setup in a bit more detail, for example, which X input method you are using, the XMODIFIERS, LANG, LC_ALL settings, etc. I'm very curious as to how this is working... thanks, Mike leanne wrote: > Dear all, > > We are trying to use WINE (22/4/2002 version) to run Notes Client r6 > with Chinese/Japanese Input. > XIM is started successfully, but in some widgets we could not input > Chinese/Japanese. > > Please find the screenshot here > (http://www.thizlinux.com/~leanne/notes.png) > > We are forwarding a mail (with Chinese) in Notes Client. Chinese can be > displayed but NOT input in > the mail content area (After "Subject" line). What type of widget it is > so that we could fix it? > > We can type Chinese on "Address" line (listbox). > > p.s. We can display and input Chinese/Japanese in Notepad.exe without > any problems. > > Yours, > Leanne > >

April 29, 2002

[Help]: Notes Client on WINE with XIM (Chinese/Japanese Input)

by leanne

Dear all, We are trying to use WINE (22/4/2002 version) to run Notes Client r6 with Chinese/Japanese Input. XIM is started successfully, but in some widgets we could not input Chinese/Japanese. Please find the screenshot here (http://www.thizlinux.com/~leanne/notes.png) We are forwarding a mail (with Chinese) in Notes Client. Chinese can be displayed but NOT input in the mail content area (After "Subject" line). What type of widget it is so that we could fix it? We can type Chinese on "Address" line (listbox). p.s. We can display and input Chinese/Japanese in Notepad.exe without any problems. Yours, Leanne

April 29, 2002

Re: patch for cups printers

by Dmitry Timoshkov

"Michael Cardenas" <michael.cardenas(a)lindows.com> wrote: > --- winehq/dlls/gdi/printdrv.c Thu Mar 28 17:22:05 2002 > +++ wine/dlls/gdi/printdrv.c Mon Apr 29 15:29:42 2002 > @@ -482,6 +482,8 @@ > if (!strncmp("LPR:",pszOutput,4)) > sprintf(psCmd,"|lpr -P%s",pszOutput+4); > + if (!strncmp("CUPS:",pszOutput,4)) > + sprintf(psCmd,"|lp -d%s",pszOutput+4); Something tells me that two '4's above should be replaced by '5's ... -- Dmitry.

April 29, 2002

Re: patch for cups printers

by Huw D M Davies

On Mon, Apr 29, 2002 at 03:39:46PM -0400, Michael Cardenas wrote: > Changelog: > This patch fixes printing on cups systems that don't have complete lpr > implementations. It won't affect non cups systems. > > It changes the device listed in the registry for cups printers to CUPS: > instead of LPR: and uses "lp -d" for a cups printer instead of "lpr -P". > > + if (!strncmp("CUPS:",pszOutput,4)) > + sprintf(psCmd,"|lp -d%s",pszOutput+4); s/4/5/ ? By the way the cups user manual seems to imply that it supplies both lp and lpr commands. Of course we should probably send jobs to cups via the cupsPrintFile() api but I guess that can wait. Huw.

April 29, 2002

Re: debugging focus problem

by degs

On Monday 29 April 2002 23:06, Andreas Mohr wrote: > On Mon, Apr 29, 2002 at 10:33:04PM +0100, degs wrote: > > Hi, > > > > Can anyone suggest what debug channels would be useful for locating the > > cause of focus or mouse input routing problems? > > --debugmsg +relay,+win,+msg,+sendmsg,+message,+event,+x11,+x11drv,+cursor > Mainly relay, event, msg, x11drv, I think. > > Then have a look at search.microsoft.com to locate some docu about one or > another thing, and that's it. Thanks. It looks like mouse messages are going to the window's parent rather than the window itself. I'm not very familiar with win32 so I don't know if this is usual or not but it seems a bit odd. Anyway - at least I have an idea what's going on now. -- degs

April 29, 2002

Re: default windows version

by Andreas Mohr

On Mon, Apr 29, 2002 at 07:07:13PM -0300, rootzz(a)ig.com.br wrote: > Em 29 Apr 2002, andi(a)rhlx01.fht-esslingen.de escreveu: > > >On Mon, Apr 29, 2002 at 04:58:16PM -0300, Insyde wrote: > >> Hi, > >> I had a problem loading a second program under wine. > >> I called the first program with: > >> wine --winver win2000 pgm1 > >> I input a password and it wirtes a data file, unloads itself > >> and loads a second program. But there was an error every > >> time the second program was to start that send me to the > >> debug screen. > >> So I found misc/version.c line 196 that the default value to > >> wine load a program was WIN31, so I changed it to NT2K. > >> > >> Is there any problem doing this? If not, why is the default still > >> WIN31? > >No, it's *not*. > > > >If you examine the code more closely, then you'll notice that > >defaultWinVersion only gets used in case versionForced is TRUE, > >which is only the case once defaultWinVersion gets set to an actually > >specified value. > > > >I know, the code is sort of confusing if you don't examine it closely, > >so feel free to comment on how to improve the situation with regards > >to defaultWinVersion initialization (I'd like to not initialize it at all, > >since it isn't being used unless there's a user setting, > >but that's not very clean of course ;-) > > So it's only used if I force a version? I forced a version as: > wine --winver win2000 pgm1 > when pgm1 stops and start pgm2 which version is used? The one that Wine figures out for the new program. > what is the default version though? There's no such thing as a default version ;-) Wine figures it out from the DLLs the program uses if no version is forced. Hmm, come to think of it: Unless we actually pass all wine cmdline parameters (--winver, --managed etc.) on to the wine child process (not sure about that right now, I think we do), the new process won't use the same forced winver value as the parent process uses. Is this a problem ? Should this info be passed to the wineserver to globalize it ? Oh, BTW: I'll rename defaultWinVersion to cmdlineWinVersion. Much better name. -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/

April 29, 2002

Re: debugging focus problem

by degs

On Monday 29 April 2002 22:50, Mike McCormack wrote: > You'll get most of the information you want from: > > --debugmsg +x11drv,+win,+message > Thanks - that looks like it its going to be useful. > The problem is you'll get too much. Sometimes you can pipe the output > through egrep... Its getting stuck pretty early on so there's not *that* much to wade through... > > Mike > > degs wrote: > > Hi, > > > > Can anyone suggest what debug channels would be useful for locating the > > cause of focus or mouse input routing problems? > > > > thanks > > -- degs

April 29, 2002

Re: debugging focus problem

by Andreas Mohr

On Mon, Apr 29, 2002 at 10:33:04PM +0100, degs wrote: > Hi, > > Can anyone suggest what debug channels would be useful for locating the cause > of focus or mouse input routing problems? --debugmsg +relay,+win,+msg,+sendmsg,+message,+event,+x11,+x11drv,+cursor Mainly relay, event, msg, x11drv, I think. Then have a look at search.microsoft.com to locate some docu about one or another thing, and that's it. -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/

April 29, 2002

Re: debugging focus problem

by Mike McCormack

You'll get most of the information you want from: --debugmsg +x11drv,+win,+message The problem is you'll get too much. Sometimes you can pipe the output through egrep... Mike degs wrote: > Hi, > > Can anyone suggest what debug channels would be useful for locating the cause > of focus or mouse input routing problems? > > thanks > -- degs

April 29, 2002

debugging focus problem

by degs

Hi, Can anyone suggest what debug channels would be useful for locating the cause of focus or mouse input routing problems? thanks -- degs

April 29, 2002

Re: SafeDisc FAQs

by Laurent Pinchart

> I don't think he is. Reverse engineering for the purpose of enabling > interoperability is permitted, and he doesn't know, and therefore > doesn't (and can't) disclose, how to circumvent the copy protection. > > Granted, somebody could take that information and use it to figure out > how to make copies of SafeDisc protected software. The same is true of > debuggers, disassemblers, or In Circuit Emulators, which are all > legitimate engineering tools. That's just a symptom of the DMCA's > biggest problem, which is that it criminalizes perfectly legitimate > activities. The information that I disclosed (which is all the information that I have) wouldn't even help someone trying to make copies of SafeDisc protected games. I implemented a few methods of debugger detection. Some others, already implemented, are used by SafeDisc. Even after weeks of work, I haven't been able to run the executable in winedbg! Laurent Pinchart

April 29, 2002

Re: SafeDisc FAQs

by Laurent Pinchart

> Aren't you actually violating the DMCA? since you're practically reverse > engineering and making wine work with copy protection based games.. Most of my work was implementing missing features. No problem there. The only problem could be the implementation of secdrv.sys, but IMHO it doesn't violate the DMCA, as secdrv.sys doesn't protect the game againt copying, and as my implementation of SafeDisc support doesn't allow the user to play the game with a copied disc. Laurent Pinchart

April 29, 2002

Re: default windows version

by Andreas Mohr

On Mon, Apr 29, 2002 at 04:58:16PM -0300, Insyde wrote: > Hi, > I had a problem loading a second program under wine. > I called the first program with: > wine --winver win2000 pgm1 > I input a password and it wirtes a data file, unloads itself > and loads a second program. But there was an error every > time the second program was to start that send me to the > debug screen. > So I found misc/version.c line 196 that the default value to > wine load a program was WIN31, so I changed it to NT2K. > > Is there any problem doing this? If not, why is the default still > WIN31? No, it's *not*. If you examine the code more closely, then you'll notice that defaultWinVersion only gets used in case versionForced is TRUE, which is only the case once defaultWinVersion gets set to an actually specified value. I know, the code is sort of confusing if you don't examine it closely, so feel free to comment on how to improve the situation with regards to defaultWinVersion initialization (I'd like to not initialize it at all, since it isn't being used unless there's a user setting, but that's not very clean of course ;-) -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/

April 29, 2002

Re: SafeDisc FAQs

by Ori Pessach

I don't think he is. Reverse engineering for the purpose of enabling interoperability is permitted, and he doesn't know, and therefore doesn't (and can't) disclose, how to circumvent the copy protection. Granted, somebody could take that information and use it to figure out how to make copies of SafeDisc protected software. The same is true of debuggers, disassemblers, or In Circuit Emulators, which are all legitimate engineering tools. That's just a symptom of the DMCA's biggest problem, which is that it criminalizes perfectly legitimate activities. -Ori Pessach Hetz Ben Hamo wrote: > And thats in wine cvs? > > Aren't you actually violating the DMCA? since you're practically reverse > engineering and making wine work with copy protection based games.. > > Thanks, > Hetz > > On Monday 29 April 2002 22:32, Laurent Pinchart wrote: > >>Hi, >> >>For those interrested, here's a FAQs about my SafeDisc support >>implementation. >> >>Feel free to comment. >> >>Laurent Pinchart >> > >

April 29, 2002

Re: cups support apparently broken

by Huw D M Davies

On Mon, Apr 29, 2002 at 09:51:00AM -0400, Michael Cardenas wrote: > On Sat, Apr 27, 2002 at 10:53:20PM +0200, Marcus Meissner wrote: > > Actually I just did a full recompile and I am still able to print. > > (Tested using standard 32bit notepad.exe.) > > I apologize for the erroneous bug report. I didn't have libcupsys2-dev > on my machine. Now that I have that and I did a full recompile, I can > get a print dialog from word with the correct printer description, but > when I click the print button, it doesn't print. > > Printing from notepad doesn't work either, it seems to do something, and > gives me an hourglass that goes away once you move the mouse. I've > attached the output of +psdrv to this email. > > > Are you still using the same test application? Did you compile in CUPS support? > > (ldd winspooldrv.so shoud show libcups.so referenced). > > I usually use word as my test application. > > Crossover office can actually print from word, excel, outlook and ie, > but not notepad. You might want to run with +print,+winspool to check that the job is being piped to the right command. Huw.

April 29, 2002

Re: cups support apparently broken

by Marcus Meissner

On Mon, Apr 29, 2002 at 01:56:51PM -0400, Michael Cardenas wrote: > Hmmm... > > thanks huw! apparently, wine is getting the wrong print command. > > Printing from kwrite, I see this on the console: > > cmd1 = /bin/apsprint -P'eng' --format=application/postscript > --attrmultiple-document-handling=separate-documents-uncollated-copies > > whereas using +print in wine I get this message: > > trace:print:OpenJob16 'LPR:eng' 'Untitled - Notepad' 0b50 > trace:print:CreateSpoolFile Got printerSpoolCommand '|lpr -Peng' for > output device 'LPR:eng' > > trying to do an > > echo "print" | lpr -Peng > > doesn't create any output from the printer. Actually WINE assumes that a CUPS printer can be sent jobs using lpr -P<printername> on stdin. If this is not the case, you will have to change dlls/gdi/printdrv.c and dlls/winspool/info.c. Ciao, Marcus

April 29, 2002

Bugzilla: A Call to Arms

by Andriy Palamarchuk

We already had discussion on wine-devel about importance of polishing Wine, making a set of applications to work very well. Cruicial in this process is prioritizing of the issues, work distribution between developers. The companies already have internal testing and bug fixing process. Of course, each company has their own product-specific work, but most of the problems are general for Wine. I suggest to share this work more actively using Bugzilla. Recently there was some work done in cleaning the issues database and it is in pretty much usable condition. To start using bugzilla more actively I suggest following steps: 1) define subsystem/direction owners. The owners will get their system-specific bugs. They won't necessary fix the bugs themselfs, but will have complete picture about all the issues in their subsystems and coordinate the bug fixing. Developers, please let me know your areas of expertese. I can overview Wine applications. 2) more formally define process of bugs handling and use this process. There is no high qualification needed to filter out bad bug reports, duplicates, request users for more information, attach relay trace to the bug, etc, etc. Result - developers will have to spend less time on discussion trivial bugs with users, will have better bug reports to work on, users will be more involved with more active feedback. Some users are very cooperative and some bug reports are really excellent! I see that Tony Lambregts, Michael Cardenas, others do a great work with the Bugzilla database. I'm also going to contribute some time for this. 3) Prioritize bugs. This is, probably, part of (2). Some bugs, while relatively easy to fix provide very big value for the end user. Often developers do not choose such issues to work on, exactly because these issues do not present challenge to them. BTW, I do not see a field "Priority" in the bugs entries. 4) Ask users to submit there problems in Bugzilla. Submitting Bugzilla report allows us to involve users more actively, persist their bug reports. Bugzilla is a more scalable approach than using mailing list only. Of course we still will discuss bugs on the mailing lists, bug big part of communication will be unloaded. There is a lot to do and discuss. For me the goal is to have this process not worse than in Mozilla project. This is impressive: http://webtools.mozilla.org/miscstats/ http://mothra.mozilla.org/webtools/miscstats/ I also like their bug report form: http://www.mozilla.org/quality/help/bugzilla-helper.html And this is for 1 application only! I'm sure Wine can generate much bigger volume of bug reports ;-) Look forward for your comments. Andriy __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com

April 29, 2002

default windows version

by Insyde

Hi, I had a problem loading a second program under wine. I called the first program with: wine --winver win2000 pgm1 I input a password and it wirtes a data file, unloads itself and loads a second program. But there was an error every time the second program was to start that send me to the debug screen. So I found misc/version.c line 196 that the default value to wine load a program was WIN31, so I changed it to NT2K. Is there any problem doing this? If not, why is the default still WIN31? Thanks, Ricardo.

April 29, 2002

Re: SafeDisc FAQs

by Hetz Ben Hamo

And thats in wine cvs? Aren't you actually violating the DMCA? since you're practically reverse engineering and making wine work with copy protection based games.. Thanks, Hetz On Monday 29 April 2002 22:32, Laurent Pinchart wrote: > Hi, > > For those interrested, here's a FAQs about my SafeDisc support > implementation. > > Feel free to comment. > > Laurent Pinchart

April 29, 2002

Re: default windows version

by Michael Cardenas

The command line options are passed. That's how the debug options get to newly created processes. On Tue, Apr 30, 2002 at 12:19:12AM +0200, Andreas Mohr wrote: > > >On Mon, Apr 29, 2002 at 04:58:16PM -0300, Insyde wrote: > > >> Hi, > > >> I had a problem loading a second program under wine. > > >> I called the first program with: > > >> wine --winver win2000 pgm1 > > >> I input a password and it wirtes a data file, unloads itself > > >> and loads a second program. But there was an error every > > >> time the second program was to start that send me to the > > >> debug screen. ... > Unless we actually pass all wine cmdline parameters (--winver, --managed etc.) > on to the wine child process (not sure about that right now, I think we do), > the new process won't use the same forced winver value as the > parent process uses. > Is this a problem ? Should this info be passed to the wineserver to globalize > it ? > > Oh, BTW: I'll rename defaultWinVersion to cmdlineWinVersion. > Much better name. > > -- > Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany > Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/ > > > -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

April 29, 2002

SafeDisc FAQs

by Laurent Pinchart

Hi, For those interrested, here's a FAQs about my SafeDisc support implementation. Feel free to comment. Laurent Pinchart

April 29, 2002

Re: Wineconsole using all memory

by Sylvain Petreolle

> did you try to erase all registry entries and start > from > scratch ? > A+ I tried this today. result is the same and no values are saved in the registry. is this the normal behaviour ? I suggest this : if there is no HKCR\Console key, we could call WINECON_RegSave to ensure all default values are saved. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

April 29, 2002

Re: cups support apparently broken

by Michael Cardenas

On Mon, Apr 29, 2002 at 10:09:19PM +0200, Marcus Meissner wrote: > > trying to do an > > > > echo "print" | lpr -Peng > > Actually WINE assumes that a CUPS printer can be sent jobs using > lpr -P<printername> on stdin. > > If this is not the case, you will have to change dlls/gdi/printdrv.c > and dlls/winspool/info.c. Apparently, the correct command for cups is lp and -P needs to be replaced with -d so by changing if (!strncmp("LPR:",pszOutput,4)) sprintf(psCmd,"|lpr -P%s",pszOutput+4); to if (!strncmp("LPR:",pszOutput,4)) sprintf(psCmd,"|lp -d%s",pszOutput+4); in wine/dlls/gdi/printdrv.c it now works, but only for CUPS printers. I'll send a patch that checks the registry for a description with CUPS in it and uses lp -d if appropriate. thanks for the help. -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

April 29, 2002

Re: PATCH: make twain compile again

by Sylvain Petreolle

Thanks ! --- Marcus Meissner <marcus(a)jet.franken.de> a écrit : > On Mon, Apr 29, 2002 at 01:27:28AM +0200, Sylvain > Petreolle wrote: > > Hi, > > > > Following patch make wine not compile for me : > > (have last sane cvs code) > > > > gcc -c -I. -I. -I../../include -I../../include > > -I/usr/local/include -g -O2 -Wall > > -mpreferred-stack-boundary=2 -fPIC -D__WINE__ > > -D_REENTRANT -I/usr/X11R6/include -o dsm_ctrl.o > > dsm_ctrl.c > > dsm_ctrl.c: In function `TWAIN_IdentityGetFirst': > > dsm_ctrl.c:134: warning: `pSourceIdentity' might > be > > used uninitialized in this function > > dsm_ctrl.c: In function `TWAIN_OpenDSM': > > dsm_ctrl.c:367: warning: dereferencing `void *' > > pointer > > dsm_ctrl.c:367: void value not ignored as it ought > to > > be > > make[2]: *** [dsm_ctrl.o] Erreur 1 > > make[2]: Quitte le répertoire > `/home/wine/dlls/twain' > > make[1]: *** [twain/twain_32.dll.so] Erreur 2 > > make[1]: Quitte le répertoire `/home/wine/dlls' > > make: *** [dlls] Erreur 2 > > The patch is not yet applied. If you apply it, it > will compile again. > > (It got broken by something else.) > > Ciao, Marcus ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

April 29, 2002