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

[WineHQ Bugzilla]

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

Bart <bart-wa at tushmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |ABANDONED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #3 from Bart <bart-wa at tushmail.com> ---
I installed the developer version and now I have different results. (Not better
or worse, mainly different.) But that also calls for new reports and I changed
the status of this report to "resolved / abandoned".


Nevertheless I still wanted to address the questions and remarks that were
raised:


(In reply to Zebediah Figura from comment #1)
> We should probably avoid printing ERR messages in such cases,
> but that's often more work than its worth.

At my side, I would appreciate it a lot if messages like ERR and FIXME were
avoided. ERR and FIXME messages give me the feeling that something didn't go
well. Also, if these messages are avoided, the remaining messages should
probably be included with a bug report. I no longer have to scratch behind my
ear and wonder which messages should be included and which not.


(In reply to Olivier F. R. Dierick from comment #2)
> There is no point to report errors in the output of wine 
> commands if there is no issue with the application.

The issue that I had was that iTunes didn't show my iPhone. I also had a list
of error messages on the screen when opening a terminal box and when giving the
command:
   $ wine iTunes.exe
I assumed that these messages, and the iPhone not showing up, were related to
each other. I also had these messages when giving the command:
   $ wine services
I have seen situations where developers wanted to have these error messages and
this information also, because sometimes they lead to the cause of an issue.
That's why I included them.


(In reply to Olivier F. R. Dierick from comment #2)
> 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'.

I did and I found many reports that iTunes was working, but none that the
iPhone was showing up or not in iTunes:
   https://bugs.winehq.org/buglist.cgi?quicksearch=iTunes%20iPhone

Because I hoped that someone else had found a solution, I also did an online
search for "Linux Wine iTunes iPhone" and here's what I found:

"I was never able to make it talk with my iPhone":
https://medium.com/@miguel.nunes.72/how-to-install-itunes-on-linux-using-wine-6d5485fb3e85

"I solved my problems with iphone by dumping it in favour of an android phone.
I could not get it to work with linux":
https://forums.linuxmint.com/viewtopic.php?p=1811609

"Then, there is the issue of iTunes not detecting my iPhone":
https://www.computerworld.com/article/2509003/30-days-with-ubuntu-linux--day-3--where-is-my-itunes-.html

"Has anyone managed to get it working & syncing?":
https://www.reddit.com/r/Ubuntu/comments/dof3rm/has_anyone_successfully_installed_itunes_in_wine/


(In reply to Olivier F. R. Dierick from comment #2)
> 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).

I also did some bug reporting for LibreOffice and I even tried to confirm bugs
from others. I had installed LibreOffice 6.1 , 6.3 , 6.4 and 7.0. Sometimes I
was able to report when a certain bug appeared (i.e. in which version). This
information sometimes leads to the specific feature that introduced the bug.
Sure, it's more work for me to install and try different versions, but it can
mean less work for developers who want to fix a bug.


(In reply to Olivier F. R. Dierick from comment #2)
> If you have intent to contribute to wine, here are some clarifications:

I do. Thank you for the clarifications!


Thank you both for the links that you provided!

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