[Solved] Run WICD On Startup

Forum Forums Orphaned Posts antiX-17 “Heather Heyer, Helen Keller” [Solved] Run WICD On Startup

  • This topic has 5 replies, 4 voices, and was last updated Nov 21-3:01 pm by jeb.jr.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #13510
    Member
    jeb.jr

      Running AntiX 17.2: WICD Network Manager sees my wi-fi controller, shows all available network SSIDs, and I can log in to my SSID, all good. However, each time I restart the machine, I must restart WICD and reconnect to my SSID. I’ve tried the fixes described at https://youtu.be/bcSMz-Qj2z8 but the result was WICD not working at all (dbus errors, I think).

      • This topic was modified 4 years, 5 months ago by jeb.jr. Reason: Marked the subject heading as solved

      AntiX Target System:
      Asus EeePC 1015PX
      1.6GHz Intel Atom 2-core 4-thread processor
      2GB RAM
      128GB PNY SSD
      Intel GMA3150 Integrated Graphics, 1024x600

      #13518
      Member
      ohh
        Helpful
        Up
        0
        ::

        Please post the output from user terminal.

        [code]
        inxi -F -x
        [code]

        cheers,
        ohh

        Every matter requires prior knowledge.

        - Du Mu
        The Art of War

        #13519
        Member
        jeb.jr
          Helpful
          Up
          0
          ::
          System:
            Host: antixEEEpc Kernel: 4.9.126-antix.1-amd64-smp x86_64 bits: 64 
            compiler: gcc v: 6.3.0 Desktop: IceWM 1.4.2 
            Distro: antiX-17.2_x64-full Helen Keller 4 October 2018 
            base: Debian GNU/Linux 9 (stretch) 
          Machine:
            Type: Laptop System: ASUSTeK product: 1015PX v: x.x 
            serial: <root required> 
            Mobo: ASUSTeK model: 1015PE v: x.xx serial: <root required> 
            BIOS: American Megatrends v: 1101 date: 02/18/2011 
          Battery:
            ID-1: BAT0 charge: 29.9 Wh condition: 54.0/56.2 Wh (96%) 
            model: ASUS 1015PE status: Discharging 
          CPU:
            Topology: Dual Core model: Intel Atom N570 bits: 64 type: MT MCP 
            arch: Bonnell rev: A L2 cache: 512 KiB 
            flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 13339 
            Speed: 1000 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 1000 2: 1333 
            3: 1000 4: 1333 
          Graphics:
            Device-1: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
            driver: i915 v: kernel bus ID: 00:02.0 
            Display: server: X.Org 1.19.2 driver: intel resolution: 1024x600~60Hz 
            OpenGL: renderer: Mesa DRI Intel Pineview M v: 2.1 Mesa 13.0.6 
            direct render: Yes 
          Audio:
            Device-1: Intel NM10/ICH7 Family High Definition Audio 
            driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
            Sound Server: ALSA v: k4.9.126-antix.1-amd64-smp 
          Network:
            Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet driver: atl1c 
            v: 1.0.1.1-NAPI port: ec00 bus ID: 01:00.0 
            IF: eth0 state: down mac: f4:6d:04:b8:94:8a 
            Device-2: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter 
            driver: wl v: kernel port: ec00 bus ID: 02:00.0 
            IF: wlan0 state: down mac: e0:b9:a5:30:19:1f 
          Drives:
            Local Storage: total: 111.79 GiB used: 3.33 GiB (3.0%) 
            ID-1: /dev/sda vendor: PNY model: CS1311 120GB SSD size: 111.79 GiB 
          Partition:
            ID-1: / size: 23.91 GiB used: 3.33 GiB (13.9%) fs: ext4 dev: /dev/sda3 
            ID-2: swap-1 size: 4.30 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
          Sensors:
            System Temperatures: cpu: 53.0 C mobo: N/A 
            Fan Speeds (RPM): cpu: 3937 
          Info:
            Processes: 182 Uptime: 3m Memory: 1.95 GiB used: 152.9 MiB (7.7%) 
            Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 
            inxi: 3.0.25 
          

          AntiX Target System:
          Asus EeePC 1015PX
          1.6GHz Intel Atom 2-core 4-thread processor
          2GB RAM
          128GB PNY SSD
          Intel GMA3150 Integrated Graphics, 1024x600

          #13524
          Member
          delix02
            Helpful
            Up
            0
            ::

            edit: sorry, should have read your post more carefully

            • This reply was modified 4 years, 5 months ago by delix02.
            • This reply was modified 4 years, 5 months ago by delix02.
            #13531
            Moderator
            caprea
              Helpful
              Up
              0
              ::

              You could look if any of these settings will bring your wicd back to work.
              https://www.antixforum.com/forums/topic/getting-wicd-error-message-when-connecting-to-wifi/

              Just to make you able to connect to the internet in the meantime, did you have a look at ceni ?
              As a last option, if it’s a really new installation and there’s nothing to loose, you could also reinstall and choose wicd with the F5 or F4 -options during live-boot.This setting will stay over to the install and wicd will autostart.

              #13591
              Member
              jeb.jr
                Helpful
                Up
                0
                ::

                This worked, can mark this thread [Solved]:

                1. in /etc/default/wicd file:
                #START_DAEMON=no [line commented]
                2. In controlcentre -> Session -> User Desktop Session:
                wicd-client -t & [line uncommented]
                grep -q “START_DAEMON=no” /etc/default/wicd || wicd-client -t &

                AntiX Target System:
                Asus EeePC 1015PX
                1.6GHz Intel Atom 2-core 4-thread processor
                2GB RAM
                128GB PNY SSD
                Intel GMA3150 Integrated Graphics, 1024x600

              Viewing 6 posts - 1 through 6 (of 6 total)
              • You must be logged in to reply to this topic.