[opensuse-factory] Non-functional Steam in Tumbleweed
Dear Community, Since January, openQA has been reporting on steam crashing on startup. A bug had beenfiled for the maintainer, but since then, no reaction has happened. So, as the designated maintainer seems to have other tasks at hand, I'm sure he'd welcome if somebody else from the community could jump in and help out. If nobody steps up, I'm afreaid we'll have to drop Steam from the repos. Which, for one, sounds like a shame. On the other hand, seems nobody in the userbase realized in the last two months that steam was not working?!? So it might not even be that big of an issue if we drop it. Cheers Dominique
On Fri, 8 Mar 2019 at 14:29, Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
Dear Community,
Since January, openQA has been reporting on steam crashing on startup. A bug had beenfiled for the maintainer, but since then, no reaction has happened.
So, as the designated maintainer seems to have other tasks at hand, I'm sure he'd welcome if somebody else from the community could jump in and help out.
If nobody steps up, I'm afreaid we'll have to drop Steam from the repos. Which, for one, sounds like a shame. On the other hand, seems nobody in the userbase realized in the last two months that steam was not working?!? So it might not even be that big of an issue if we drop it.
Steam is working for me on all of my Tumbleweed machines... I last used it yesterday, as the first thing after my zypper dup and reboot.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, March 8, 2019 2:28:10 PM CET Dominique Leuenberger / DimStar wrote:
...
If nobody steps up, I'm afreaid we'll have to drop Steam from the repos. Which, for one, sounds like a shame. On the other hand, seems nobody in the userbase realized in the last two months that steam was not working?!? So it might not even be that big of an issue if we drop it. Hi,
last time I checked and it still seems to be the case steam crashes in swrast_dri, so I suspect it being problem in Mesa/DRI or software rendering usage and not in steam. In real world usage steam works perfectly fine (at least with AMDGPU drivers I use at home). It would be shame to drop it from repos due to nonfunctioning openQA test since openQA does not tests AMD and NVIDIA drivers anyway. Ondrej
Cheers Dominique
On Fri, 2019-03-08 at 14:55 +0100, Ondrej Holecek wrote:
On Friday, March 8, 2019 2:28:10 PM CET Dominique Leuenberger / DimStar wrote:
...
If nobody steps up, I'm afreaid we'll have to drop Steam from the repos. Which, for one, sounds like a shame. On the other hand, seems nobody in the userbase realized in the last two months that steam was not working?!? So it might not even be that big of an issue if we drop it. Hi,
last time I checked and it still seems to be the case steam crashes in swrast_dri, so I suspect it being problem in Mesa/DRI or software rendering usage and not in steam. In real world usage steam works perfectly fine (at least with AMDGPU drivers I use at home).
It would be shame to drop it from repos due to nonfunctioning openQA test since openQA does not tests AMD and NVIDIA drivers anyway.
Thanks for your feedbacks! OF course, if steam works, it's not going to be dropped. It's just that this worked for quite a while in openQA and suddenly stopped. And without a maintainer looking at the bugs, there is not much to go by. In this case, we're likely better off removing that test from openQA - until somebody finds the will, time and power to make a test that actually makes sense and gives a reliable information about the package. The test as-is serves no purpose, other than having a red blob. Cheers Dominique
On 3/8/19 8:58 AM, Dominique Leuenberger / DimStar wrote:
On Fri, 2019-03-08 at 14:55 +0100, Ondrej Holecek wrote:
On Friday, March 8, 2019 2:28:10 PM CET Dominique Leuenberger / DimStar wrote:
...
If nobody steps up, I'm afreaid we'll have to drop Steam from the repos. Which, for one, sounds like a shame. On the other hand, seems nobody in the userbase realized in the last two months that steam was not working?!? So it might not even be that big of an issue if we drop it. Hi,
last time I checked and it still seems to be the case steam crashes in swrast_dri, so I suspect it being problem in Mesa/DRI or software rendering usage and not in steam. In real world usage steam works perfectly fine (at least with AMDGPU drivers I use at home).
It would be shame to drop it from repos due to nonfunctioning openQA test since openQA does not tests AMD and NVIDIA drivers anyway.
Steam did not work for almost all of february. Seems to me kernel updates are the main cause of steam problems. Steam is working again now. I surely do not know about who was maintaining it, so I do not complain anymore. Sure would be bad to delete it if it works. Thanks to anyone who has helped. To me I would think it would be courteous for a maintainer to express a desire to pass it on. mike s
Thanks for your feedbacks! OF course, if steam works, it's not going to be dropped. It's just that this worked for quite a while in openQA and suddenly stopped. And without a maintainer looking at the bugs, there is not much to go by.
In this case, we're likely better off removing that test from openQA - until somebody finds the will, time and power to make a test that actually makes sense and gives a reliable information about the package. The test as-is serves no purpose, other than having a red blob.
Cheers Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 8. März 2019 10:58:49 GMT-03:00 schrieb Dominique Leuenberger / DimStar <dimstar@opensuse.org>:
On Fri, 2019-03-08 at 14:55 +0100, Ondrej Holecek wrote:
On Friday, March 8, 2019 2:28:10 PM CET Dominique Leuenberger / DimStar wrote:
...
If nobody steps up, I'm afreaid we'll have to drop Steam from the repos. Which, for one, sounds like a shame. On the other hand, seems nobody in the userbase realized in the last two months that steam was not working?!? So it might not even be that big of an issue if we drop it. Hi,
last time I checked and it still seems to be the case steam crashes in swrast_dri, so I suspect it being problem in Mesa/DRI or software rendering usage and not in steam. In real world usage steam works perfectly fine (at least with AMDGPU drivers I use at home).
It would be shame to drop it from repos due to nonfunctioning openQA test since openQA does not tests AMD and NVIDIA drivers anyway.
Thanks for your feedbacks! OF course, if steam works, it's not going to be dropped. It's just that this worked for quite a while in openQA and suddenly stopped. And without a maintainer looking at the bugs, there is not much to go by.
In this case, we're likely better off removing that test from openQA - until somebody finds the will, time and power to make a test that actually makes sense and gives a reliable information about the package. The test as-is serves no purpose, other than having a red blob.
I have the same problem with GNU Health testing: openQA reports an error, but it installs and runs perfect. I've forwarded the bug to openQA maintainer, but no reaction so far. Schöne Grüße Axel -- Written from cell phone - excuses for typos -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
hi all, Am 08.03.19 um 14:28 schrieb Dominique Leuenberger / DimStar:
Since January, openQA has been reporting on steam crashing on startup. A bug had beenfiled for the maintainer, but since then, no reaction has happened.
i just used it without problems. i use nvidia proprietary binary driver installed the "hard way" (https://en.opensuse.org/SDB:NVIDIA_the_hard_way) works perfectly. thanks for the steam package! -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales *DI Rainer Klier* DevOps, Research & Development -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 08.03.19 15:58, Rainer Klier wrote:
hi all,
Am 08.03.19 um 14:28 schrieb Dominique Leuenberger / DimStar:
Since January, openQA has been reporting on steam crashing on startup. A bug had beenfiled for the maintainer, but since then, no reaction has happened.
i just used it without problems.
i use nvidia proprietary binary driver installed the "hard way" (https://en.opensuse.org/SDB:NVIDIA_the_hard_way)
works perfectly.
thanks for the steam package!
Works fine here as well, maybe there is just a system package missing (which should be pulled in with steam). Greetings, Tobias -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Works for me also for long time with AMD open source drivers (RX580 GPU, playing CiV6 when I'm finding some free time). Stratos On Fri, Mar 8, 2019 at 5:04 PM Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de> wrote:
On 08.03.19 15:58, Rainer Klier wrote:
hi all,
Am 08.03.19 um 14:28 schrieb Dominique Leuenberger / DimStar:
Since January, openQA has been reporting on steam crashing on startup. A bug had beenfiled for the maintainer, but since then, no reaction has happened.
i just used it without problems.
i use nvidia proprietary binary driver installed the "hard way" (https://en.opensuse.org/SDB:NVIDIA_the_hard_way)
works perfectly.
thanks for the steam package!
Works fine here as well, maybe there is just a system package missing (which should be pulled in with steam).
Greetings,
Tobias
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
As reported in the bug, the first-run experience of Steam can be either perfect or completely terrible depending on your hardware and the day of the week. All errors that I have seen on my systems can be resolved via a quick search for the error message. After resolving the issues do not come back and Steam works fine. Last I checked, this was true of all non-officially supported distros (read Ubuntu). The further away from officially supported (in terms of lib versions) the more problems one can encounter. I had an issue open on streamtricks to try and wrap the Steam startup script and handle the different fail scenarios, but ran out of energy. Otherwise, given that Steam is actively used on Tumbleweed by a fairly large number of users (as evident via forums, separate IRC communities, and community sites) I would expect to hear about a large scale issue. Otherwise, most issue (even for Tumbleweed) are reported on the upstream github issue repo by Valve as they are truely the only ones that can resolve most issues. Based on the feedback to this mail already and the above I see no reason to remove the Steam package. That said improvements welcome. -- Jimmy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi there, I ran up Steam on my openSUSE 15.1 Beta box in KVM and it installed fine. The first started stopped somehow: comrad@linux-9lzl:~> steam Setting up Steam content in /home/comrad/.local/share/Steam Running Steam on opensuse-leap 15.1 64-bit STEAM_RUNTIME is enabled automatically Installing breakpad exception handler for appid(steam)/version(0) libGL error: unable to load driver: swrast_dri.so libGL error: failed to load driver: swrast But when I closed the terminal an ran Steam a second time it downloaded the data files and updated itself. Login and downloading a game also worked fine. I even could run Uplink in KVM (screenshot here: https://imgur.com/a/D54RtJD). Cheers, Bernd On 08.03.19 17:56, Jimmy Berry wrote:
As reported in the bug, the first-run experience of Steam can be either perfect or completely terrible depending on your hardware and the day of the week. All errors that I have seen on my systems can be resolved via a quick search for the error message. After resolving the issues do not come back and Steam works fine.
Last I checked, this was true of all non-officially supported distros (read Ubuntu). The further away from officially supported (in terms of lib versions) the more problems one can encounter. I had an issue open on streamtricks to try and wrap the Steam startup script and handle the different fail scenarios, but ran out of energy.
Otherwise, given that Steam is actively used on Tumbleweed by a fairly large number of users (as evident via forums, separate IRC communities, and community sites) I would expect to hear about a large scale issue. Otherwise, most issue (even for Tumbleweed) are reported on the upstream github issue repo by Valve as they are truely the only ones that can resolve most issues.
Based on the feedback to this mail already and the above I see no reason to remove the Steam package. That said improvements welcome.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Sound about right, the first run is just odd like that and differently depending on graphics driver primarily and Steam version. A side note, the fact that Steam updates independent of bootstrap tarball found in package means the openQA test does not know if TW changes broke Steam or Steam broke Steam. Not much that could be done there short of keeping snapshots of steam and not allowing it to update until done independent of TW updates. Basically, a workaround for this is to catch the different error output like the one you got and handle it. In some cases just need to re-launch Steam, in others nuke a few files and then relaunch. Not sure if nastier ones are resolved as there were some that took 3-4 stages. The general Steam runtime fixes are present which resolve that class of issue, but still require a relaunch which could also be automated. -- Jimmy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (10)
-
Axel Braun -
Bernd Ritter -
Dominique Leuenberger / DimStar -
Jimmy Berry -
mike -
Ondrej Holecek -
Rainer Klier -
Richard Brown -
Stratos Zolotas -
Tobias Klausmann