Description of problem: I installed Steam 1.0.0.50 and at first run after accepti g the license agreement I got a popup Console window telling me to write my password as sudo. Problem is that the group sudoers isn't created during the installation and my user isn't added to that group so my password won't work. I believe that there should be a rule for this. Version-Release number of selected component (if applicable): 1.0.0.50 How reproducible: Everytime that you do a fresh install of Steam. Steps to Reproduce: 1. Open terminal. 2. Log in as root. 3. Type urpmi steam --auto 4. Now start Steam client. 5. Let it update. 6. Accept the license agreement. 7. Voila! A console window pops up asking you to confirm with a sudo password. I should mention that I only have KDE4 installed. Kernel that I'm running is 3.19.8. Reproducible: Steps to Reproduce:
Summary: Steam first run demands the user to run a command as sudo i a popup console window in KDE4 => Steam first run demands the user to run a command as sudo in a popup console window in KDE4
CC: (none) => kristoffer.grundstrom1983
Target Milestone: --- => Mageia 5
Can you test steam-1.0.0.50-1.1.mga5.noarch from bug 13307?
Assignee: bugsquad => rverschelde
I don't manage to reproduce this issue, neither on KDE4 nor on GNOME. Can you attach the output of rpm -qa?
I did now and it looks like the same issue exists: Steam needs to install these additional packages: curl, python-apt, xterm, xz-utils, zenity, libgl1-mesa-dri:i386, libgl1-mesa-glx:i386, libc6:i386 [sudo] password for kristoffer: There is no sudoers group made before Steam is installed/updated and therefor my user is not added to install thoose deps.
Created attachment 6837 [details] Here's the output you requested
Take a look at the file steamdeps inside the source archive and search for sudo. It seems to be written to only run in Ubuntu. I even tried the older version of steam-launcher from PCLOS and got the same message, to install thoose deps as sudo that is. I even made a group called sudoers and added my user to that group and I still couldn't install thoose deps.
Attachment 6837 mime type: application/octet-stream => text/plain
Yes the steamdeps file is not compatible with Mageia, and the dependencies that it asks for are already installed on your system. The bug is not that you should be in a sudoers list, it's just that we should hide this warning (by making sure the terminal is not shown up, there will still be warnings when running steam from a terminal, but we can't do much against it). Which terminal does it open? Konsole?
(In reply to Rémi Verschelde from comment #6) > Which terminal does it open? Konsole? Konsole.
Is PCLOS is forked from Mageia, are they different in handling source code?
(In reply to Kristoffer Grundström from comment #8) > Is PCLOS is forked from Mageia, are they different in handling source code? I meant If instead of Is.
Did not steamdeps get removed (renamed) by the update? https://bugs.mageia.org/show_bug.cgi?id=13307#c10
CC: (none) => fri
(In reply to Morgan Leijström from comment #10) > Did not steamdeps get removed (renamed) by the update? > https://bugs.mageia.org/show_bug.cgi?id=13307#c10 Indeed. It still can't reproduce the issue reported here, whether steamdeps is installed or not.
Ever confirmed: 1 => 0Status: NEW => UNCONFIRMED
Hi, I encounter the same bug than Kritoffer. The RPM version is: 1.0.0.49-2.mga5.nonfree
Status: UNCONFIRMED => NEWCC: (none) => mageiaEver confirmed: 0 => 1
Thanks for the confirmation Bertrand. Can you test steam-1.0.0.50-1.1.mga5.nonfree [1] from Nonfree Updates Testing to see if it still happens? Thanks. [1] https://bugs.mageia.org/show_bug.cgi?id=13307#c10
Hello Rémi, No more konsole message with steam-1.0.0.50-1.1.mga5.nonfree. At first sight, it seems to work fine.
As per comment 14, I'll assume the bug was fixed by the update. I was myself never able to reproduce it though, so I can't confirm it.
Status: NEW => RESOLVEDResolution: (none) => FIXED