[SOLVED] Dbus and wicd in -current64

manwichmakesameal · 07-05-2009, 12:51 PM

I just did a fresh install of -current64 (current as of this posting, have my own mirror that updates every night), and now wicd will not work. It keeps giving me an error message when I start X about cannot connect to dbus check configuration. Anyone else having this?

TSquaredF · 07-05-2009, 12:57 PM

I had the same problem. Then I found the README.Slackware in the "extra/wicd" directory. It told me to add users to the netdev group & that solved my hassles.
Regards,
Bill

rworkman · 07-05-2009, 01:05 PM

See /usr/doc/wicd-1.6.1/README.SLACKWARE

rworkman · 07-05-2009, 01:06 PM

Incidentally, I anticipated this, and I thought it was addressed in the wicd code. The curses client (wicd-curses) tells the user *exactly* what is wrong, but the gui client doesn't for whatever reason. I'll look into it.

manwichmakesameal · 07-05-2009, 01:19 PM

@ TSquaredF: Thanks. I know I should read the documentation, but didn't even think about it since it worked before without being in that group. Works now though.

Nille_kungen · 07-05-2009, 03:43 PM

I also missed this, should have been an pointer to the problem in slackware-current changelog.
Thanks to XGizzmo that helped me in #slackware

grissiom · 07-06-2009, 02:52 AM

Quote:

Originally Posted by rworkman

Incidentally, I anticipated this, and I thought it was addressed in the wicd code. The curses client (wicd-curses) tells the user *exactly* what is wrong, but the gui client doesn't for whatever reason. I'll look into it.

Yes, I see the info from curses client too. But I think the GUI should give the some information or the users will get confused on the first try.

rworkman · 07-08-2009, 04:39 PM

This is fixed in 1.6.2.