[Bug 39744] No sound with winepulse.drv in multiple applications when using Debian Wine packages (PULSE_LATENCY_MSEC set to 60 in wine wrapper script)

[wine-bugs at winehq.org]

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

--- Comment #22 from jre.winesim at gmail.com ---
[Not sure if we should move discussion about unrelated Debian/Wine topics to
wine-devel. But since this bug is mostly taken care of now, it doesn't hurt too
much discussing it here.]


> --- Comment #17 from Sebastian Lackner <sebastian at fds-team.de> ---
> (In reply to Andrew Eikum from comment #16)
>> jre, has this been removed from the Debian Wine package? Would you like an
>> upstream bug filed?
> 
> The latest version in Debian repos is 1.7.55-4 (on Stretch and Sid), which
> still contains the line with PULSE_LATENCY_MSEC. If someone here is motivated
> enough to improve those packages and/or to file bug reports for all the
> individual issues, I am aware of several other problems besides the
> PULSE_LATENCY_MSEC environment variable, which should be fixed too.

Agreed, filing bug reports at bugs.debian.org for issues relating to Debian is
probably the most constructive way. It's as easy as sending a mail to
submit at bugs.debian.org, with the following first lines (Debian users should use
"reportbug"):

Source: wine       (or wine-development)
Version: 1.8~rc4-1 (must be a valid Debian version)
Severity: normal   (or wishlist, higher severities might be counterproductive)

Use these links to see the current version for every dist (not only testing or
whatever):
https://packages.debian.org/wine (stable releases, including RC)
https://packages.debian.org/wine-development (the rest)


> file-handling.patch is not necessary
> anymore, the bug is already fixed upstream - applying the patch nevertheless
> breaks tests

Thanks for pointing that out, I just removed that in the Debian git repo.


> frequent user complaints about missing
> "wineconsole" and other winelib apps

I'm only aware of wineconsole (https://bugs.debian.org/792695), which was fixed
2015-11-21.
I'm not sure though, if we should create symlinks for every possible app
(currently we have regedit, winecfg, winedbg, wineboot, winepath, winefile,
regsvr32 and wineconsole.) Maybe add msiexec to the wine package, and the rest
to the -tools packages which are optional.
Without symlink every app still may be called with "wine [app]".


> WINEDEBUG=-all is used by default, making bug reports here useless

Agreed.
But that way you can at least see that the bug report is coming for a
debian.org package ;->


(In reply to Sebastian Lackner from comment #19)
> (In reply to Nikolay Sivov from comment #18)
> > > Various autogenerated files (unicode tables, OpenGL extension
> > > tables, wineserver request tables) are regenerated during the build process,
> > > which potentially introduces new bugs / incompatibilities not present in
> > > official WineHQ builds.
> > 
> > That should not be a problem if they want to regenerate from Unicode data,
> > as we depend on particular versions of those that don't change once
> > released. But sure, there's no need to do that in practice.
> 
> I still see a high risk of introducing new problems. See for example the
> OpenGL tables, which are generated based on the XML files shipped in the
> "khronos-api" package. Last update is from March 2015, but in Wine we had a
> commit to update them in April for example.
> 
> Also, in order to regenerate various files, they are first replaced with an
> "empty" version, then the script is executed - however, not all of those
> files are static. They can easily get out of sync with the Wine source tree.

[I haven't really looked into the specific regenerate stuff that we do in
Debian-Wine or am a general expert for this.]
Generally Debian requires to build from source. And downloading during a
package build (e.g. wget --no-check-certificate
https://cvs.khronos.org/svn/repos/ogl/trunk/doc/registry/public/api/gl.xml) is
a no-go (or I guess and hope so).
[Unless I'm completly mistaken:] this topic reminds me of Debian's recent
discussion about minified javascript code
(https://lists.debian.org/debian-devel/2015/08/msg00427.html). That thread
might help to understand Debian's position. 
If there is a better way to regenerate these files, I'd be happy to hear about
it.

I'm not sure how to best handle updates of e.g. khronos. Maybe add such changes
to Wine's release announcement, like it is done for gecko?

I now filed a bugreport for an updated khronos-api package.

Greets
jre

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