[SOLVED] wicd don't launch...

gor0 · 02-24-2015, 06:12 PM

howdy folks!

I installed wicd and still NO wi-FI !!!

if I launch wicd from internet nada happens...

tia!

BCarey · 02-24-2015, 07:06 PM

Did make /etc/rc.d/rc.wicd executable and/or run it? Have you confirmed that wicd is running. Have you cleaned out anything you may have put in to /etc/rc.d/rc.inet1.conf?

Brian

gor0 · 02-24-2015, 08:43 PM

Quote:

Originally Posted by BCarey

Did make /etc/rc.d/rc.wicd executable and/or run it? Have you confirmed that wicd is running. Have you cleaned out anything you may have put in to /etc/rc.d/rc.inet1.conf?

HOW to do that ? I'm totally newbie in this system!

Code:

wicd
It seems like the daemon is already running.
If it is not, please remove /var/run/wicd/wicd.pid and try again.

Code:

wicd-gtk --no-tray
Traceback (most recent call last):
  File "/usr/share/wicd/gtk/wicd-client.py", line 63, in <module>
    from wicd import dbusmanager
  File "/usr/lib64/python2.7/site-packages/wicd/dbusmanager.py", line 93, in <module>
    DBUS_MANAGER = DBusManager()
  File "/usr/lib64/python2.7/site-packages/wicd/dbusmanager.py", line 57, in __init__
    self._bus = dbus.SystemBus()
  File "/usr/lib64/python2.7/site-packages/dbus/_dbus.py", line 194, in __new__
    private=private)
  File "/usr/lib64/python2.7/site-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib64/python2.7/site-packages/dbus/bus.py", line 122, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

TIA !!!

gor0 · 02-24-2015, 08:56 PM

Quote:

Originally Posted by BCarey

Have you cleaned out anything you may have put in to /etc/rc.d/rc.inet1.conf?

No...didn't touch nada !

gor0 · 02-24-2015, 08:58 PM

Quote:

Originally Posted by BCarey

Did make /etc/rc.d/rc.wicd executable and/or run it?

Code:

#  /etc/rc.d/rc.wicd 
Usage: /etc/rc.d/rc.wicd {start|stop|restart}
bash-4.3#  /etc/rc.d/rc.wicd start
Wicd appears to already be running.
If this is not the case, then remove 
/var/run/wicd/wicd.pid and try again...

STDOUBT · 02-24-2015, 09:35 PM

run wicd-client and depending on your GUI, you may see an icon appear from which you can select a network.
If you have only a terminal available, try wicd-curses.
Curious how much time you spent searching for a solution. It's been covered many times here.
Good Luck!

gor0 · 02-24-2015, 09:41 PM

[QUOTE=STDOUBT;5322940] wicd-client [/QUOTE
[CODE]

Code:

#  wicd-client
Traceback (most recent call last):
  File "/usr/share/wicd/gtk/wicd-client.py", line 63, in <module>
    from wicd import dbusmanager
  File "/usr/lib64/python2.7/site-packages/wicd/dbusmanager.py", line 93, in <module>
    DBUS_MANAGER = DBusManager()
  File "/usr/lib64/python2.7/site-packages/wicd/dbusmanager.py", line 57, in __init__
    self._bus = dbus.SystemBus()
  File "/usr/lib64/python2.7/site-packages/dbus/_dbus.py", line 194, in __new__
    private=private)
  File "/usr/lib64/python2.7/site-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib64/python2.7/site-packages/dbus/bus.py", line 122, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

Code:

 # wicd-curses
Traceback (most recent call last):
  File "/usr/share/wicd/curses/wicd-curses.py", line 52, in <module>
    from wicd import dbusmanager
  File "/usr/lib64/python2.7/site-packages/wicd/dbusmanager.py", line 93, in <module>
    DBUS_MANAGER = DBusManager()
  File "/usr/lib64/python2.7/site-packages/wicd/dbusmanager.py", line 57, in __init__
    self._bus = dbus.SystemBus()
  File "/usr/lib64/python2.7/site-packages/dbus/_dbus.py", line 194, in __new__
    private=private)
  File "/usr/lib64/python2.7/site-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib64/python2.7/site-packages/dbus/bus.py", line 122, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

gor0 · 02-25-2015, 06:01 AM

no one ?

allend · 02-25-2015, 07:26 AM

Quote:

dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

Hazy guess - is /etc/rc.d/rc.messagebus set executable so that dbus-daemon is started at boot?

gor0 · 02-25-2015, 08:53 AM

Code:

#!/bin/sh
#
# messagebus:   The D-BUS systemwide message bus
#
# description:  This is a daemon which broadcasts notifications of system events \
#               and other messages. See http://www.freedesktop.org/software/dbus/
#
# processname: dbus-daemon
# pidfile: /var/run/dbus/pid

# This is a modified version of the rc.messagebus script distributed with the
# dbus sources.  Thanks to Don Tanner of the GWare <http://gware.org> Project
# for most of the work involved      --Robby Workman <rworkman@slackware.com>


PIDFILE=/var/run/dbus/dbus.pid

start() {
  mkdir -p $(dirname $PIDFILE)
  if ! ps -u messagebus -c | grep -wq dbus-daemon; then
    rm -f $(dirname $PIDFILE)/*
    if [ -x /usr/bin/dbus-uuidgen -a -x /usr/bin/dbus-daemon ] ; then
      echo "Starting system message bus:  /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system"
      /usr/bin/dbus-uuidgen --ensure
      /usr/bin/dbus-daemon --system 1> /dev/null
    fi
  fi
}

stop() {
  if [ -e "$PIDFILE" ]; then
    echo "Stopping system message bus..."
    pid=$(cat $PIDFILE)
    kill $pid 1> /dev/null 2> /dev/null
    # Just in case:
    killall dbus-daemon 1> /dev/null 2> /dev/null
    rm -f $PIDFILE
  fi
}

reload() {
  echo "Reloading system message bus configuration..."
  if [ -e "$PIDFILE" ]; then
    pid=$(cat $PIDFILE)
    kill -HUP $pid
  else
    killall -HUP dbus-daemon
  fi
}

status() {
  if ps -u messagebus -c | grep -wq dbus-daemon; then
    echo "System dbus-daemon is running."
  else
    echo "System dbus-daemon is stopped."
  fi
}

# See how we were called.
case "$1" in
  start)
    start
    ;;
  stop)
    stop
    ;;
  restart)
    stop
    start
    echo "You may need to restart your Window Manager to reconnect to the system dbus."
    ;;
  reload)
    reload
    ;;
  status)
    status
    ;;
  *)
    echo $"Usage: $0 {start|stop|restart|reload|status}"
    ;;
esac

gor0 · 02-25-2015, 08:57 AM

gor0 · 02-25-2015, 09:25 AM

Code:

 iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          
lo        no wireless extensions.

bassmadrigal · 02-25-2015, 09:45 AM

Quote:

Originally Posted by gor0

Need help or sadly goin to quit!!

where are the 'pseudoexperts' ???

something as simple no one help...

I'm newbie to this system!

again...need my WI-FI working...

can someone 'EXPERT' or no too expert take some 'minutes' to get WICD setup ?

is not a rant but ... ... ...

tia!

You seem too hurried for this. Help on forums can take time. Forums are international and not everyone is on at every time. Not everyone who is on is going to have knowledge of your error, so that can take time. Then, when someone does post a response requesting additional information, you provide something else. You need to be able to answer other peoples' questions. I'm not posting this trying to belittle you or anything like that, just trying to let you know that help can take time, and if you're pushy, it can prevent some people from attempting to help you resolve your problem.

allend asked if your /etc/rc.d/rc.messagebus is executable. The contents of that file should not matter, because they should be the same on any Slackware (unless you modified them, and unless you know what you're doing, you shouldn't do that). Can you post the results of the following command?

Code:

ls -l /etc/rc.d/

This should tell us whether rc.messagebus is executable and might get some other insight on what's going on with your system.

Is there a reason why you're wanting to use wicd over NetworkManager? NetworkManager is built into Slack whereas wicd is a separate program you need to install from extra/.

allend · 02-25-2015, 09:47 AM

is not a rant but ... ... ...

Quote:

is /etc/rc.d/rc.messagebus set executable

i.e. what is the output of 'ls -l /etc/rc.d/rc.messagebus'?

Your post #10 shows the contents of the script. That script needs to be run at boot.

gor0 · 02-25-2015, 09:59 AM

Quote:

Originally Posted by allend

what is the output of 'ls -l /etc/rc.d/rc.messagebus'?

Code:

# ls -l /etc/rc.d/rc.messagebus
-rw-r--r-- 1 root root 1893 Jul  9  2013 /etc/rc.d/rc.messagebus