February 2009 - Wine-Devel - list.winehq.org

Re: dinput: joydevs[id].name (EVIOCGNAME) is product name, joydevs[id].device is a path
by Vitaliy Margolen Feb. 10, 2009

Feb. 10, 2009

Vincent Pelletier wrote: > joydevs[id].name value comes from EVIOCGNAME iotcl, and is the product name. > > I think joystick device path qualifies as a "Friendly name for the instance" > (as defined for tszInstanceName on MSDN). > > If not, please tell me and I will extend the patch to generate a "Joystick %i" > name, or maybe put joydevs[id].name in both fields. > > - strcpy(lpddi->tszInstanceName, joydevs[id].name); > - strcpy(lpddi->tszProductName, joydevs[id].device); > + strcpy(lpddi->tszInstanceName, joydevs[id].device); > + strcpy(lpddi->tszProductName, joydevs[id].name); No this is not entirely correct. Native doesn't return any device paths. But it does return proper joystick name: Wine: Instance: Logitech Logitech Dual Action ProductName: /dev/input/event7 Win XP: Instance: Logitech Dual Action USB ProductName: Logitech Dual Action USB Another joystick: Wine: Instance: Logitech Logitech MOMO Racing ProductName: /dev/input/event7 Win XP: Instance: Logitech MOMO Racing USB ProductName: Logitech MOMO Racing USB So I'd suggest copying name into both places. I think some applications looking for particular information there. And append "evdev?" at the end so we can tell how it's handled. Vitaliy.

3 3

Re: ntdll: add a warning about running wine as root (resend)
by James Mckenzie Feb. 10, 2009

Feb. 10, 2009

Alexandre Julliard <julliard(a)winehq.org> wrote: >Sent: Feb 9, 2009 7:26 AM >To: James Mckenzie <jjmckenzie51(a)earthlink.net> >Cc: Austin English <austinenglish(a)gmail.com>, wine-devel(a)winehq.org >Subject: Re: ntdll: add a warning about running wine as root (resend) > >James Mckenzie <jjmckenzie51(a)earthlink.net> writes: > >> Second, the problem is that newbies, figuring that their favorite >> program will not run as an ordinary user, gets a wiff that root has >> more privileges, will attempt run as root totally hosing their Wine >> directory. This then starts the 'you should not run Wine as root' >> mantra on Wine-Users. This then causes the newbie to question why did >> I go to Linux/Wine when I had a perfectly running Windows system? > >Please explain how running as root will screw their Wine directory. If >that's really true, surely it should be fixed instead of simply throwing >out a warning and proceeding. New wine installation: su (no dash so root's environment is not picked up) wine notepad install various programs and use them. exit User logs in a second time after learning how to properly use Wine. Attempt to do anything with Wine in user space. Cannot do due to permissions problems. The solution: sudo rm -rf .wine User now upset because everything they did is gone. Yes, there are legit reasons to run as root, one of them is the now famous ICMP 'Ping' unavailability issue in Linux. Experts know about this and how to work around it. Newbies, used to Windows and how it works, just figure that this is restricted to administrators, and switch to root to get around it. The proper command, as I have learned through years of UNIX administration, is 'su -' but newbies don't know this and most just use 'su'. Thus, the need for the warning. Experts tend to know what they are doing, newbies don't for the most part. And yes, I borked many a system as a newbie and as an expert (building kernels for RedHat/Fedora for my Thinkpad. James McKenzie

10 12

Regression in 1.1.14 for Athena Visual Studio
by Erich Hoover Feb. 9, 2009

Feb. 9, 2009

In Wine 1.1.14 Athena Visual Studio fails to build Fortran applications and returns with an error, doing a git bisect gives this result: ---- ebe4a9e321800fbe6d2004a640cd276a28d15c38 is first bad commit commit ebe4a9e321800fbe6d2004a640cd276a28d15c38 Author: Dan Kegel <dank(a)kegel.com> Date: Sun Jan 18 19:19:46 2009 -0800 msvcrt: Remove CRs earlier in ascii mode. :040000 040000 44cfaec7cd552af4c92f220ad34a06d864eff79d 685d15aa69a9e0f91e0d4cbc933191a29837dce9 M dlls ---- However, removing this patch from the latest git doesn't do enough - Athena instead hangs indefinitely trying to build. I guessed that it would also be necessary to remove the related patch "msvcrt: Remove CRs earlier in ascii mode in fseek, too.": http://source.winehq.org/git/wine.git/?a=blob;f=dlls/msvcrt/file.c;hb=7f3c7… Fortunately, that did the trick and got things working again. I don't have a lot of free time right now, but if there's some information I can give that will help in fixing this issue then please let me know and I will do my best to provide it. A 15 day trial of Athena is available, this error can be reproduced by attempting to build any sample in the "Curve Fitting Models" folder.

2 1

Re: ntdll: add a warning about running wine as root (resend)
by James Mckenzie Feb. 9, 2009

Feb. 9, 2009

Aurimas Fišeras <aurimas(a)gmail.com> wrote: >Sent: Feb 9, 2009 7:45 AM >To: James Mckenzie <jjmckenzie51(a)earthlink.net> >Cc: wine-devel(a)winehq.org >Subject: Re: ntdll: add a warning about running wine as root (resend) > >James Mckenzie wrote: >> Alexandre Julliard <julliard(a)winehq.org> wrote: >>[...] >> New wine installation: >> >> su (no dash so root's environment is not picked up) >> wine notepad >> install various programs and use them. >> exit >> >> User logs in a second time after learning how to properly use Wine. >> Attempt to do anything with Wine in user space. Cannot do due to permissions problems. >> >> The solution: >> >> sudo rm -rf .wine >No, the solution is >sudo chown -R user:user .wine Correct. However, this is not being given as the solution. Also, if the user is on an alternate wine prefix this would change to: sudo chown -R <username>:users $WINEPREFIX Is this in the FAQ somewhere? James McKenzie

3 2

[try2] dinput: joydevs[id].name (EVIOCGNAME) is product name, joydevs[id].device is a path
by Vincent Pelletier Feb. 9, 2009

Feb. 9, 2009

Le Saturday 07 February 2009 14:16:15 Vincent Pelletier, vous avez écrit : > If not, please tell me and I will extend the patch to generate a "Joystick > %i" name, or maybe put joydevs[id].name in both fields. Same patch as first proposed on wine-devel, no reaction so I guess it's correct. -- Vincent Pelletier

2 2

Re: comctl32/tests: [try 2] Make the test dpi and Theme aware: use SM_CYSIZE
by Paul Vriens Feb. 9, 2009

Feb. 9, 2009

Detlef Riekenberg wrote: > try 2: without the check for win9x > > > The status test failed on installations with 120 dpi. > > After a lot of "try and error" from 72 to 144 dpi with > different formula for the min height, different results on my machine > and a failing XP machine at 96dpi, I found the reason: > > The minimal height depends on the appearance setting > "[In]Active Title Bar", which is SM_CYSIZE. > > The test now pass on win98se, win2k and Wine with a different height > for the title bar (tested from 18 to 30). > > To reduce the test log size, I moved the dump of the current tested > font name from a trace to the ok. > > > Why is MS so stupid and use BYTE in ENUMLOGFONTEXA and > WCHAR in ENUMLOGFONTEXW for the strings in wingdi.h, > while MSDN document them as TCHAR? > > > > > ------------------------------------------------------------------------ > > Hi Detlef, This patch introduced a lot of failures on specifically some XP and W2K3 boxes. Could you have a look? -- Cheers, Paul.

2 1

Re: ntdll: add a warning about running wine as root (resend)
by James Mckenzie Feb. 9, 2009

Feb. 9, 2009

Michael Stefaniuc <mstefani(a)redhat.com> wrote: >Sent: Feb 9, 2009 7:39 AM >To: James Mckenzie <jjmckenzie51(a)earthlink.net> >Cc: wine-devel(a)winehq.org >Subject: Re: ntdll: add a warning about running wine as root (resend) > >> sudo rm -rf .wine >Solution is sudo chmod -R $username.$groupname .wine > Correct. However, this is not the solution given on Wine Users. >> User now upset because everything they did is gone. >Not if you do it right. > I agree, but some users are very sensitive and are worse that a colicy baby. The problem is that we should not need to direct users to run as root to perform any function. Some Linux distributions restrict network functions, such as ICMP, to only root. This is sillines in my opinion and actually employs poor security practices. However, a new that receives a message like the following "You must be an Administrator to run this program" when attempting to run a program in Wine will think "Administrator == root" and try to run the program as root. The program does not run, and they are futher frustrated. Also, some new users think, incorrectly, that running Wine as root will give them more permissions. It does not and should not. Again, the warning should address this. What I don't want to see, and I agree with AJ, is the disablement of running Wine as the root user. There are situations where this is necessary. A short notification message is all that is necessary and Austin's change does exactly that. James McKenzie

1 0

Re: ntdll: add a warning about running wine as root (resend)
by James Mckenzie Feb. 9, 2009

Feb. 9, 2009

Chris Howe <mrmessiah(a)gmail.com> wrote: >Sent: Feb 9, 2009 8:06 AM >To: wine-devel(a)winehq.org >Subject: Re: ntdll: add a warning about running wine as root (resend) > >It would seem to me that the right place for this to go would be >not in Wine itself but in the likes of Crossover and Cedega - the >"distributions" and value added apps built around Wine. > >I can't reconcile in my head the case where you have a newbie >running the latest GIT of Wine needing this kind of thing at all. > Newbies don't run GITs, they download a prebuild version of Wine from a repository. Thus, this 'fix' would not appear to them until the release of 1.1.15 at the earliest. >Either they want the power and compatibility of the latest GIT >version, and all that that entails, including the potential for doing >things they didn't intend if they run it as root, or they want some >newbie friendly environment that seizes back the reins a little >and stops them doing that. > All versions of Wine that I've run into have the ability to run as root. This is inherent as a part of any UNIX program. What we are discussing is that running as root may make your system vulnerable and may cause problems later when Wine is run in user space. My example is that a user logs in and installs a program as root because they were told that it 'runs better' as root. When it is discovered to not be true, the user then attempts to run in user space only to be advised they have no access to the program. The solution given is to remove the user space Wine directories and to start over. The user gets upset, sometimes with implied violence, and then abandons Wine. What happens is that this user gets on other areas and talks bad about Wine. Thus, Wine gets another black eye to overcome. The idea is to warn users that problems may be encountered if they run Wine as root. If they continue on, it is on them. A message box or warning on the screen, shown one time, is all most newbies need to come back to the forum and ask how to do something. Experts will charge on and if they mess up their system, they know how to fix it. James McKenzie

2 1

Fwd: EVE online losing its Linux Client
by Andrew Fenn Feb. 9, 2009

Feb. 9, 2009

On Mon, Feb 9, 2009 at 2:22 PM, James Mckenzie <jjmckenzie51(a)earthlink.net> wrote: > Since there is not a great Wine audience for the Mac, the Eve Online Mac client should not be abandoned just for that reason. The real reason may be that there is not a great deal of demand for an on-line game interface for the Mac. Most Mac users loath having to use X11 for any purpose, and a game tops the list. I'm pretty sure they're not abandoning the mac client which has shown growth compared to the Linux client.

1 0

Re: ntdll: add a warning about running wine as root (resend)
by James Mckenzie Feb. 9, 2009

Feb. 9, 2009

David Gerard <dgerard(a)gmail.com> wrote: >Sent: Feb 9, 2009 7:45 AM >To: wine-devel(a)winehq.org >Subject: Re: ntdll: add a warning about running wine as root (resend) > >2009/2/9 James Mckenzie <jjmckenzie51(a)earthlink.net>: > >> Thus, the need for the warning. Experts tend to know what they are doing, newbies don't for the >>most part. And yes, I borked many a system as a newbie and as an expert (building kernels for >>RedHat/Fedora for my Thinkpad. > > >Yep. The problem is that newbies are coming from Windows - (a) where >the answer to inability to do something is to try again as >administrator (b) which sometimes takes precautions to keep you from >shooting your foot off. Which is why most establishments have disabled users from having access to Administrator level functions. > >Solutions: > >1. Get better newbies. (Strikes me as unlikely.) I agree and the situation is getting worse rather than better. We have to be able to gently guide newbies from causing harm to themselves. Sort of like handing a new soldier an unloaded weapon and telling them it is. This is what the warning should do. If a newbie carries on, then they 'have been warned' and they cannot blame Wine for causing harm to their system. >2. Something to help stop them shooting their foot off that won't >hamper those who really want to do this. > Again, the one-time warning should suffice. This can set a Registry value so the warning will not display again in that WINEPREFIX. Experts will just ignore the message whereas newbies might just heed it and stop. Then again, some won't. James McKenzie

1 0