is there any way to learn how to fix little problems listed by the console logs? in this site i have not found something interesting in this way, so it is possible that for a little bug that can be easily fixed by a normal user, someone needs to disturb a developer. if someone make a little "howto" that teaches to read logs and to fix the problems reported by the same logs, it can be a very useful resource for all who want to begin to fix their wine troubles and perhaps then they could help other users to solve their own problems. i'm sorry if the question is already been asked (i searched and found nothing about it). thanks for replies.
I would have to agree with this suggestion. The "How To" section on the website seems mainly focused for application developers. The only "resource" for users is to goto AppDB and see if you get lucky, or trying this mailing list. As for AppDB, it would be more useful if reports included information on setup/configuration details so other users know what settings need to be changed to make an application run under wine. Right now, any such information is purely voluntary in the "comments" section; it would be nice to see a few questions with drop down lists to select from. For example, my recent attempt to get EE2 working requires that "Emulate Virtual Desktop" be enabled. (i've now posted that info to AppDB) Just my $0.02 ckx3009 wrote:> is there any way to learn how to fix little problems listed by the console logs? > > in this site i have not found something interesting in this way, so it is possible that for a little bug that can be easily fixed by a normal user, someone needs to disturb a developer. > > if someone make a little "howto" that teaches to read logs and to fix the problems reported by the same logs, it can be a very useful resource for all who want to begin to fix their wine troubles and perhaps then they could help other users to solve their own problems. > > i'm sorry if the question is already been asked (i searched and found nothing about it). > > thanks for replies. > > > > > >
ckx3009 wrote:> is there any way to learn how to fix little problems listed by the console logs?Sure - learn C, win32api, Wine source. Find the place that prints that "little problem" and ... fix it or implement missing functionality.
hendrik wrote:> On Mon, May 26, 2008 at 11:35:03AM -0500, vitamin wrote: > > > > > ckx3009 wrote: > > > > > > > > vitamin wrote: > > > > > > > > > > > Sure - learn C, win32api, Wine source. Find the place that prints that "little problem" and ... fix it or implement missing functionality. > > > > > > > > > > but this means to became a wine developer... > > > > > > > > > > Pretty much - yes. > > > > > > ckx3009 wrote: > > > > > > > > this reply seems to want to say: leave to devs the dev's work... > > > > > > > Yup. How else can you fix a ... "fixme" if it's telling about not implemented functionality? > > > > > > ckx3009 wrote: > > > > > but in this way we (users) will never be able to help with our own work about little things the dev team... > > > > > > > What you can do as a user - look for real problems with applications you are running not imaginary problems in a form of some debug information printed by Wine. > > > > I suppose the next question is: How can naive users distinguish real > problems from debug messages? Maybe there should be a guide for that!Just read them and try to understand I guess. If a message says "can't findMFC42.DLL" then install that dll. See FAQ for this.
> If you're app isn't behaving as on windows, then you've got an actual > problem. Whatever the terminal prints out isn't necessarily a problem.I know that. That's not the point. The point is that sometimes when you do have a problem, the terminal may give some useful information, but it's not necessarily as obvious as a dll not found. The preloader page zero problem is a perfect example of the kind of message I'm talking about--it points to a specific problem, with a known workaround, but the error message itself is not something a beginner would understand without reading the sticky at the top of this forum, which I assume is why you put it there. So the question is, are there any other such cryptic error messages that point to problems with known fixes that beginners could apply themselves if they only knew what the message meant in the first place?
austin987 wrote:> > The FAQ has some listed: > http://wiki.winehq.org/FAQOkay, so I should have specified "other than the ones already in the FAQ." :) But since you brought it up, reorganizing the FAQ a bit to make this information more prominent would also be helpful. The "Using Wine" section is getting pretty long, making it harder to find things. Grouping all the error-message-related questions together under their own heading (called something like, say, "Common Error Messages") would make this info easier to find as well as to maintain. (And if no one objects to that suggestion, yeah, I'm willing to do the work.)
Would it be possible to make some kind of index of the most frequent problem, (but not a bugzilla). Like I say "install failed to finalize with error 1603" (for .NET installation) - other places I see that it had been fixed, what does 1603 mean then?? Then I could add reference to all places I found hints of the problems like mentioning that the same error of my logs appeared on Windows during betas and had been cleared with a Patch from Microsoft - it was an installer problem. I could mention that installing a Windows patch on Wine is failing too. Then I would like a category "errors connecting to server", various problems with assemblies etc. People having problems with drivers would get one and another for people having problems with directx. The difference to the Bugzilla is that there would not be a bug with one user and the developers. This could be discussed between users. Bugzilla is not a place for discussing since it would be closed with some mentions like "Bugzilla is not a self-help support" - the difference why people post their problems in forums, they want to know if others experienced the same.