[Bug 49284] Running "$ wine services" gives a list of errors

WineHQ Bugzilla wine-bugs at winehq.org
Thu May 28 16:04:15 CDT 2020


https://bugs.winehq.org/show_bug.cgi?id=49284

Zebediah Figura <z.figura12 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |z.figura12 at gmail.com
           Severity|major                       |normal

--- Comment #1 from Zebediah Figura <z.figura12 at gmail.com> ---
(In reply to Bart from comment #0)
> I had installed iTunes and I was hoping to get access to my iPhone via
> iTunes. (And I may not be the only one. ;-) )

This is probably a valid bug, but it's generally best to report the bug you
see, not the bug you think is underlying.

> I know that a few Apple services need to be running on a Windows computer
> for that. That's why I decided to check the services that were running under
> Wine. I started a terminal box, and I ran:
>    $ wine services

That's not what services.exe does. On Windows, if you want to list services,
you can run "net start". This works on Wine too. Of course, even then it's not
necessarily the cause of the bug...

> Before I knew it I had a decent list of errors on the screen. No problem,
> I've seen errors before in a lot of situations and from many programs.
> 
> Since I wasn't running any third-party program, I wondered if this could be
> the underlying problem of other bugs. As a start I searched the bug list for
> "SIO_ADDRESS_LIST_CHANGE". That gave a list of seven other bugs and these
> users were all running different third-party programs. These other bugs may
> or may not be related. I find that difficult to tell, as I'm not yet
> familiar enough with Wine.
> 
> Is this something that needs attention?

As a general rule, FIXME and even ERR messages are not bugs. Frequently
applications are satisfied when we fake success from some API function, and
don't depend on it actually doing what they think it's doing. Moreover, many
errors occur during normal operation that programs can handle. For example,
status 0x2733 is WSAEWOULDBLOCK, indicating that no address list change has
occurred yet. We should probably avoid printing ERR messages in such cases, but
that's often more work than its worth.

> PS:
> - For "Severity" I choose "major", because I wasn't running any third-party
> software. Feel free to change this if you think I'm wrong.

Please see <https://bugs.winehq.org/page.cgi?id=fields.html> for a description
of the "severity" field; it has nothing to do with third-party software.

-- 
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.



More information about the wine-bugs mailing list