As a fellow wicd user, I can sympathize, however, wicd development has effectively halted a couple years back as the upstream devs lost interest.
Hi Tele42,
Yes I know wicd came to a halt, such a shame, but it still works great, and when all you run like me is just a small WM, who needs NetworkManager, to much bloat.
Blackbox, Openbox, Fluxbox, awesome, i3, etc, with networkmanger, give me a break...
Just because Valve came over to Linux, please don't think we're all running KDE, or Gnome.
In time Valve will hopefully realize a lot of end users move away from big DEs into smaller...
Also it doesn't matter if it's been halted until it's not functional and wicd is very functional still.
I'm also playing with ConnMan, this is backed by Intel, and it's in development, so there are alternatives.
Valve should be able to code Steam to just look and use whatever it finds and display it.
I'm glad someone else posted this. I'm a user of connman and if you launch steam with -bigpicture it will get to the network config screen and you won't be able to do anything because it can't detect any networks.
I have tried to work around this by creating a fake dbus instance of NetworkManager but have only gotten so far.
Here is my issue from a while back, #3165
Are any of the Valve developers going to comment on this?
I'm starting to see a lack of replies on a lot of posts people report on.
I said it before and I'll say it again, Github is where we, even the end-users work with you to resolve issues, we are Geeks here, but there must be communication, and someone willing to respond.
I'm a Unix/Linux Geek, I've been working 15 years helping developers troubleshoot and resolve and fix bugs, sorry with no disrespect to anyone, we're not all Windows Noobs and Kiddies making posts!
I've since this report, switched to connman https://01.org/connman This is suppose to be a project backed by Intel, this is certainly something that Valve should keep their eye on.
And I use cmst, a QT5 gui for connman; https://github.com/andrew-bibb/cmst
So using connman, I still do not see anything for my network in the Big Picture... :(
I've recently switch from connman back to wicd, since wicd just released a new version.
When I'm running Steam there is no networking detected, it also says there's no wired and wireless...
Why wouldn't steam at least detect the wired and wiireless hardware? Hmm
lspci for my wired and wireless;
03:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)
04:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0)
@Tele42 wicd development has not been halted, a new version was released on Dec. 2014, version 1.7.3
While steam is still throwing a warning if there isn't a running instance of networkmanager, there should be no other show stoppers left here that prevents users from using other connection managers. As long as Steam is able to reach Valve's servers in general, then there should not be a functional problem.
Nothing extracted yet.
Hi,
To start with I know that the Steam client is only supported on Ubuntu, or at least that's my understanding, or another distro along the same lines as Ubuntu...
But it would be nice if this issue can be passed along to Valve to change the way the client is reporting networking.
I use Steam in Slackware and yes it does have the NetworkManager that was just added into Slackware 14.1, but I only use wicd.
It would be nice for other distro/network users if something could be changed in the code regarding this.
Also if I go into 'Big Picture' nothing is listed for my Network, so it would be nice to get Steam also working with others Network Clients besides the NetworkManger.
Please add support for wicd, and remove WARNING about the NetworkManager when it's not installed on a distro.
Or no matter what network client you use, it works properly with the Steam.
Thank you for your consideration. :)