[0130/234541:ERROR:object_proxy.cc(239)] Failed to call method: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
The fact that libnm is required essentially means network manager is a requirement. Steam has no business deciding or finding out on what network I'm running. I'm the owner of the system and I know and decide what goes. There's also a load of other dependencies that seem to be mixed. For example, libudev.so.0 and libudev.so.1 are both referenced.
@GoLD-ReaVeR steam only references libudev.so.0, dependencies of steam are pulling in libudev.so.1 depending what distro you are on.
@GoLD-ReaVeR I don't think it's steam intention to change your network configuration behind your back. I guess they need it for the network settings of the big picture mode. Thing is: They can't rely on everybody using just NetworkManager, so having a hard dependency on it is a bit weird.
Without NetworkManager steam does not detect when connection changes and i need to restart it to get VAC games to work.
Still, any reason why NetworkManager should be enforced? Not everyone uses NetworkManager for network configuration, and some people don't even have it installed at all.
I second that emotion. I hate NetworkManager. HATE it. I always uninstall it and use good old /etc/sysconfig/network-scripts configuration with /etc/init.d/network, which I understand and feel I can actually control. It works. But, for example, firewall-config seems to want the NetworkManager service even though it doesn't need it and it's no longer required by the RPM.
I don’t mind so much the dependency of libnm, but the dependency of the legacy version of libnm (libnm-glib) is a big issue, performance and security wise.
libnm in itself as a dependency is a problem. It means steam purports to
control the way the system functions. This would be no problem for Steam
OS, but for regular Linux distributions this is a hard NO-NO. Furthermore,
not everyone uses network manager, especially those with an ethernet card
have absolutely no use for it. It clogs the system with extra unnecessary
dependencies as well. Steam should by all accounts be able to live without,
as it is a gaming platform and not a control panel.
On Mon, Nov 11, 2019 at 2:22 AM Vincent Grande [email protected]
wrote:
I don’t mind so much the dependency of libnm, but the dependency of the
legacy version of libnm (libnm-glib) is a big issue, performance and
security wise.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/3129?email_source=notifications&email_token=ABRU5L2E3H5NAO5B6VTCUXDQTCXT3A5CNFSM4ALWKK52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDVMUPI#issuecomment-552258109,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRU5LZYCZPXZTKQOFPVVXTQTCXT3ANCNFSM4ALWKK5Q
.
I assumed Steam used libnm for streaming or P2P things, I didn’t know it manipulated libnm like that. So I decided to look at the dependency tree for “networkmanager” and “libnm”, and here’s what I found (I’m on Arch).
networkmanager had no hard dependencies on my machine, so I ran “sudo pacman -Rs networkmanager” to uninstall the whole dependency tree. To my surprise, there was like 6 other packages that got removed (libteam, libpgm, and libnewt come to mind).
It made me wonder what I installed that required networkmanager to begin with. Anyway, I then investigated the libnm package, and found that this is what Steam truly depends on (libnm-glib technically).
Steam is also the only package on my system that requires libnm and libnm-glib. Upon learning all these things, I also totally advocate for the removal of the libnm dependency from Steam, especially since it’s also using the legacy version, libnm-glib.
Sadly in 2020 this is still an issue. Are there any plans to remove this deprecated and no longer supported libraries? Everybody who uses a native steam-runtime will be hit by this issue sooner or later.
Keep in mind, that it was removed in March 2019: https://github.com/NetworkManager/NetworkManager/pull/308
cheers.
Steam is not working on my Fedora 33:
`[jonathan.souza@mymachine bin32]
$ LD_LIBRARY_PATH=".:${LD_LIBRARY_PATH}" ldd $(file |sed '/ELF/!d;s/:.//g')|grep 'not found'|sort|uniq
libnm-glib.so.4 => not found
libnm-util.so.2 => not found
libudev.so.0 => not found
`
@jojo-qa
Does fedora have libnm-glib in its repos? It is legacy software, although I would hope the Steam runtime includes it.
Hello, Steam is no longer linked against these libraries.
I can confirm that legacy libnm-glib isn't required, thank you.
I'm not using NetworkManager, but steam still forces me to have the libraries installed for no reason when not using the runtime. Steam starts and runs just fine without NetworkManager, but obviously complains that it didn't find a running instance.
I would greatly appreciate if you could fix this.