protonscr

Slow downloads

steamclosed
ValveSoftware/steam-for-linux#10773 · opened 2024-04-09 by MEGA-Dawg68 · updated 2024-04-15 · 6 comments · github
MMEGA-Dawg68 2024-04-09 github

Your system information

  • Steam client version (build number or date):

  • Distribution (e.g. Ubuntu): Fedora 39

  • Opted into Steam client beta?: No

  • Have you checked for system updates?: Yes

  • Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
    steam-logs.tar.gz

  • GPU: AMD Rx 6700

Please describe your issue in as much detail as possible:

I can download 30mb/s on windows but on linux only 3-6mb/s. I have seen the other issue that has the commands for the console. That only slowed it down.

Steps for reproducing this issue:

  1. Download anything from steam
Kkisak-valve maintainer 2024-04-09 github

Hello @MEGA-Dawg68, you've presented exactly the same information as #10762, with logs that are strongly hinting that it's the same issue as #10248.

Please do not intentionally post duplicate issue reports.

Closing as a duplicate of #10762 / #10248.

MMEGA-Dawg68 2024-04-11 github

@kisak-valve
you have to be kidding me. You shut down my last issue! Nobody is going to go into closed issues to see if anyone needs help. #10248 doesn't help me. Open up either of the two issues please

MMEGA-Dawg68 2024-04-12 github

@kisak-valve
Not replying is just going to drive me to start another issue. Either help me or open the issue back up please

Kkisak-valve maintainer 2024-04-12 github

You're literally written "You must respond or I will abuse this issue tracker by creating yet another duplicate issue report." This line of thought can only end badly. Fragmenting the discussion of an issue across multiple issue reports helps nobody, in particular, to the people working to fix issues.

The information written on #10248 is not a solution, it's a problem that needs to be resolved by a Steam dev. You have the option to add what you're seeing to the older discussion with others, or submit evidence that reasonably shows that there's a separate issue from the symptoms already being discussed. You've chosen neither, instead, resubmitting identical logs claiming there's a separate issue because ... no reason given and expected a different result than the first time.

MMEGA-Dawg68 2024-04-14 github

You're literally written "You must respond or I will abuse this issue tracker by creating yet another duplicate issue report." This line of thought can only end badly. Fragmenting the discussion of an issue across multiple issue reports helps nobody, in particular, to the people working to fix issues.

The information written on #10248 is not a solution, it's a problem that needs to be resolved by a Steam dev. You have the option to add what you're seeing to the older discussion with others, or submit evidence that reasonably shows that there's a separate issue from the symptoms already being discussed. You've chosen neither, instead, resubmitting identical logs claiming there's a separate issue because ... no reason given and expected a different result than the first time.

If your "solution" didn't help me, then that usually would mean the issue would stay open, but you decided "No, I am obviously correct! I am a Valve moderator. Now I will close the issue because I have the power to!". Someone could have the solution but no, you decided that I cannot get the help I needed.
I getting power abuse vibes.

MMEGA-Dawg68 2024-04-15 github

@kisak-valve
obviously you don't want me to get help so I give up on your stupid repo. You may not realise it but you are contributing to the fear that the linux community is toxic and gatekeepers. It doesn't matter if you run windows, it is the fact of you are active in a linux repo. So I give up, I am swapping back to Windows where at least I might get a helpful person from valve help me (You could learn a thing or two from them)
good riddance

Nothing extracted yet.