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

[WineHQ Bugzilla]

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

Olivier F. R. Dierick <o.dierick at piezo-forte.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |o.dierick at piezo-forte.be

--- Comment #2 from Olivier F. R. Dierick <o.dierick at piezo-forte.be> ---
(In reply to Bart from comment #0)
> I recently started using Wine and I wonder if I bumped into a bug that's
> also the underlying problem of other bugs.

Hello,

Please read the bug writing guidelines before reporting bugs:
https://wiki.winehq.org/Bugs

There is no point to report errors in the output of wine commands if there is
no issue with the application.

> I had installed iTunes and I was hoping to get access to my iPhone via
> iTunes. (And I may not be the only one. ;-) )

Did you check the AppDB entry of iTunes [1]? There are many successful reports
and there doesn't seem to be an obvious issue with services, so It might 'just
work'.

Try to run the application and if there is an issue, check the bugs that are
already reported.

[1] https://appdb.winehq.org/objectManager.php?sClass=application&iId=1347

If you have intent to contribute to wine, here are some clarifications:

(In reply to Bart from comment #0)
> 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

--- quote from dlls/programs/services/services.c ---
Services - controls services keeps track of their state
--- end quote
This is used internally. Probably not the command that you were looking for.

I believe the nearest you can get is to set WINEDEBUG=+service when running
iTunes.

> Is this something that needs attention?
> 
No, unless there is an issue with the application.

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

That criteria is irrelevant for severity level.
Using third-party software would make the bug _status_ INVALID.

The severity levels are (somewhat) well-defined:

--- quote from https://wiki.winehq.org/Bugs#severity ---
Normal for an application crash or other issue
Major for major loss of functionality for a wide range of applications
--- end quote ---

There is no indication of an issue in your report, so I guess that 'normal'
will do.

> - For readability I added blank lines in attachment:
>    "Wine Services - output.txt". 

That's highly unnecessary and somewhat undesirable. Valid reasons to mangle
files before attaching them are limited to: hiding private information and/or
removing duplicate/unrelated content to make the file smaller.

I find the file harder to read because the blank lines don't group the lines
into meaningful paragraphs and that's what I would expect the blank lines to
do.

> - From time to time I try to look at things the way most users see them.
> That's also why I installed Wine via:
>    Start -> Preferences -> Software -> Utilities
> This gives me wine version:
>    wine-4.0 (Debian 4.0-2) , updated Apr. 22, 2020

User behavior is irrelevant to reporting bugs.
Bugs should be reported with a recent wine development/staging version, as
noted in the bug writing guidelines.

Wine 4.0 is months old, and stable doesn't even have all the fixes and features
of the development/staging branch from the same time.

If a user reports an issue with that version, the first answer will be to
upgrade to a recent version and retest.

> - I'll be happy to install the latest development version next to the stable
> version that I have now, but I'll still have to figure out how to do that.

There is no need to keep or use the old packages. Once you use recent
wine-devel/wine-staging packages (from your distro or WineHQ.org), stick to
them (and keep them up-to-date).

Regards.

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