Your message dated Tue, 12 May 2020 18:49:13 +0000 with message-id <[email protected]> and subject line Bug#957284: fixed in steam 1.0.0.62-2 has caused the Debian Bug report #957284, regarding /usr/games/steam: redirects Steam stderr, games' stderr to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 957284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957284 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: steam Version: 1.0.0.47-1 Severity: normal File: /usr/games/steam Since 1.0.0.47-1, the Debian /usr/games/steam wrapper script redirects steam.sh's stderr to ~/.steam/root/error.log (or in older versions ~/.steam/error.log). This was presumably intended to make debugging easier, but it results in several issues: - Upstream developers of Steam and games cannot give instructions to get extra debug information that will work on all distributions, because different distributions and packages send stderr to different places. - Game and library developers are not always very consistent about where they send diagnostic messages. If they send some messages to stdout and some to stderr, those messages get separated, making debugging more difficult. - Sometimes games or the Steam client have bugs that cause them to produce a very large amount of output, which in the worst cases can fill up disks. If we were writing to something like the systemd Journal (which is what ends up happening under at least GNOME), then its rate-limiting can mitigate this, but writing to a program-specific log file doesn't have rate-limiting available. The upstream steam-launcher package from which this one is derived used to log both stdout and stderr to /tmp/dumps/${USER}_stdout.txt, but version 1.0.0.62 stopped doing this, for several reasons: it was susceptible to symlink attacks in some kernel configurations, sometimes filled /tmp as noted above, and according to Steam developers it was not actually particularly useful for debugging. As a result of the issues described above, the upstream Steam maintainers have asked downstream distributors to stop writing Steam output to a log file. Their intention is that the standard steps to diagnose Steam issues will include: open a terminal (xterm or similar), run Steam from there, and copy/paste output from the terminal. This means the wrapper script should at least not redirect its output if its stderr is a tty. Before changing anything about the logging, I'd like to understand why this redirection was added. Is it there to meet a goal that is still relevant? If so, there some other way we can meet that goal without the issues above? For example, on systemd systems, we could consider writing to stdout/stderr if it's a tty, or to the Journal (by wrapping Steam with systemd-cat or systemd-run) if not? Or the logging destination could perhaps depend on whether Steam was run from its .desktop file or directly, with output to stdout/stderr if run directly, but output to the Journal or to /dev/null if run from the .desktop file? In the longer term, I'd like to investigate whether we can use the upstream bin_steam.sh (possibly with enhancements, modifications, or a Debian-specific wrapper that points ~/.steam/steam to ~/.steam/debian-installation for new installations), rather than reinventing it. smcv
--- End Message ---
--- Begin Message ---Source: steam Source-Version: 1.0.0.62-2 Done: Simon McVittie <[email protected]> We believe that the bug you reported is fixed in the latest version of steam, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie <[email protected]> (supplier of updated steam package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 12 May 2020 18:58:38 +0100 Source: steam Architecture: source Version: 1.0.0.62-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team <[email protected]> Changed-By: Simon McVittie <[email protected]> Closes: 930613 957284 Changes: steam (1.0.0.62-2) unstable; urgency=medium . * steam(6): Don't redirect stderr to a log file. The upstream developers of Steam recently removed its own launch script's redirection (to /tmp/dumps), which has been noted to sometimes fill /tmp, and is less useful in practice than it was hoped to be. They have asked that we remove the similar redirection from Debian's equivalent script, so that when debugging game launch issues they can instruct users to run steam from an interactive terminal, and expect it to produce both stdout and stderr, regardless of whether their launch script or ours is in use. (Closes: #957284) * Remove libtxc-dxtn0 alternative dependency. We now require libgl1-mesa-dri (>= 17.3), which is available in Debian 10 and up, as well as Debian 9 backports. * Release to unstable. Version 1.0.0.62 has been promoted from beta to stable status. . steam (1.0.0.62-1) experimental; urgency=medium . * New upstream release (currently considered to be a beta) - New directory layout - Update steam binary - Update steam-devices udev rules from <https://github.com/ValveSoftware/steam-devices/>: add ZeroPlus P4 (hitbox) hidraw device, 0c12:0ef6 * d/rules: Make .orig directory configurable. It's canonically "..", but users of git-buildpackage often separate the directory with git repositories from the directory with large binaries. * d/rules: Add support for downloading beta steam-launcher versions. The 1.0.0.62 launcher release is currently considered to be a beta, which will be promoted to stable status after it has had more testing. * d/rules: Cope with the upstream release having an epoch. Ubuntu's modified version of this package has an epoch as a result of an older, unrelated package "sTeam" with a higher version number, which used to be in Debian and Ubuntu many years ago. Valve's steam package now has an epoch so that their 1:1.0.0.62 will be compared correctly against Ubuntu's 1:1.0.0.61. * d/rules: Be more verbose about the extraction process * d/rules: Keep most upstream files in the orig tarball. The upstream "source" tarball has been restructured, and in particular the udev rules (which are MIT-licensed and come from a separate git repository) are now in subprojects/steam-devices. bootstrap*.tar.* contains precompiled libraries without their corresponding source code (it's available from repo.steampowered.com but not part of the "source" package), which we intentionally don't ship. The crashhandler module and the steamerrorreporter executable are also non-essential binaries. The other scripts and auxiliary files in the orig tarball are likely to be useful references, even if we don't actually ship them in binary packages. * d/copyright.in: Update * d/steam-devices.install: Update for upstream restructuring * d/steam.install: Update for new location of steam binary. I've left it in a subdirectory to reduce confusion with the top-level ./steam in upstream's "source" tarball, which is a symlink to bin_steam.sh. * Standards-Version: 4.5.0 (no changes required) * d/rules: Don't run upstream Makefile * Build-Depend on the libraries Valve put in their bootstrap tarball. This ensures that we have all the necessary metadata for dpkg-shlibdeps to generate the ${shlibs:Depends} for the proprietary steam executable. * d/scripts/steam: Distinguish between ~/.steam/steam and ~/.steam/root * Explicitly depend on the libraries that we delete from the Steam Runtime. We probably shouldn't be deleting these any more, because the Steam Runtime explicitly prefers newer versions from the host system in all cases, and if there are bugs in that mechanism that make deleting them necessary, Valve would like to know about them so they can be fixed - but for now, preserve historical behaviour. * d/steam-bug.presubj: Recommend running steam-runtime-system-info. This diagnostic tool was written for use in upstream bug reports, but is equally valuable for downstream distributors like us. * Depend on libgl1 instead of transitional libgl1-mesa-glx (Closes: #930613) * Use https for more URLs. In particular, https://repo.steampowered.com now works, and appears in upstream documentation. * d/copyright: Set Upstream-Name to steam-launcher. The upstream dpkg source package is still named steam for historical reasons, but it builds steam-launcher_*.deb, and calling it "steam-launcher" is a good way to disambiguate between the launcher/bootstrapper (which is what we're actually packaging here) and the full Steam client (which is downloaded by the launcher, and is what users normally see). * Move steam-devices Recommends into sorted order * Add Depends on file, used by the Steam Runtime setup scripts * Add Recommends on xdg-utils, which is used to launch URL handlers * Add Recommends on zenity, which Steam assumes is present * Add Depends on curl, used to download Steam updates * d/scripts/steam: Put location and version in environment variables. Recent Steam diagnostic tools use this to identify how Steam was launched. Checksums-Sha1: f92690525c96b474bc1d015ea15a75496411e196 2295 steam_1.0.0.62-2.dsc b4118fafad85071751a5843499cb871799d358e5 29960 steam_1.0.0.62-2.debian.tar.xz c38bc7add045446d559e76d2322ab3ddeb2d3af8 6008 steam_1.0.0.62-2_source.buildinfo Checksums-Sha256: a6d923771241177a788315fb3378761ea542b46af37f839b6d516f5a54eb9638 2295 steam_1.0.0.62-2.dsc bc9934dbb5da022bc4b9ce2617f17eb9af44e76887536c8e546aa3a1966fb1ad 29960 steam_1.0.0.62-2.debian.tar.xz 0f3407eb28e4e31ea1cec5f7611e920b19593a5637a3de11eec7a031678a3486 6008 steam_1.0.0.62-2_source.buildinfo Files: 9da4d5c464a5c217c346c7be73e83042 2295 non-free/games optional steam_1.0.0.62-2.dsc 10a945a37719ef1ee60c694cd907bac8 29960 non-free/games optional steam_1.0.0.62-2.debian.tar.xz dc170e45f29588b2ee35c2f0f806ece5 6008 non-free/games optional steam_1.0.0.62-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl66618ACgkQ4FrhR4+B TE9QbRAAmzApDYa5R50veh6spS098sYZks1VTZp8dvZK7chX2KkhgwbDj7SZUK8S zrozncMYhHWv6NKYCd3LYzhSx9uLpsEViORLl+QM8zimvqXuBonepNEuESF9Clb9 CHPgz6tEgynFon9wLf7p9VFwW6Ta8YqDMIQM/ZErbFSSFeixrpKfYZgDAbJ6v2uB zg9FskYcdZqFrtEjbxOI/Wp6RMaw4cnrLnZL9NBH9PSmkOKyH7V/JFmIuQC0+4Sw vAYbBhpKksGtbxVyMYi8pBdhLV8zWtr8j11i22aLIxCKVAVLjUSVpxTmphzwC/Ny HmUumH+VVKrUh9Avg1Sqoe9RiCGqax3BD2UF1f7m9XMs/di3KcVQkJSHKFXTycao qOMmrPbk6f8/qWzJIBEiq/9i7PZd0WhHobHCvKV4AW98ydwIGplC6JYNrJSTMwEQ +aWtzbAKwZtPTKTIFfylVl899nfAcwNTg4r+y6aS3F5KvqJnevVa53BWaKZXXfOK s+Ef26LZliFqMv8ZBpf1z2V9g59lhFrswkV7OKbFosRqBH6GezRoezrH75vWInFn GcUWBSwsFaIExn8NjyelOyBSI2GhNsAuzsC5gQ+RcPnvdJSLlIK/USpQKrSTQhVS 6ckjhQJSzIiZ111boLnH0Z1UWuwCizZ2Ki4gnf/HQjWwYms2eSc= =9Kss -----END PGP SIGNATURE-----
--- End Message ---
