Month: April 2016

Network Manager shows eth0 and wlan0 unmanaged

After starting the OS, there is no internet connectivity. The network manager shows that eth0 and wlan0 are not managed.

Make sure that the eth0 and wlan0 are discovered. Run the following command.

ifconfig -a

If the ethernet and wlan can be seen in the output but no ip address is allocated to it, check if the dns nameserver exists.

sudo gedit /etc/resolv.conf

If this list is empty then add the following entries in it.

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 8.8.8.8
nameserver 8.8.4.4

These point to the Google DNS.

Try to ping any website. Example:-

ping www.google.com

If the result is successful we have a working conncetion.

If ping fails, then the system doesn’t manage the network drivers.

For the system to manage the network devices, we have to make changes in the /etc/NetworkManager/NetworkManager.conf file

sudo gedit /etc/NetworkManager/NetworkManager.conf file

The displayed output will be in the format:-

[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq

no-auto-default=XX:XX:XX:XX:XX:XX,

[ifupdown]
managed=false

Change the managed value from false to true

[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq

no-auto-default=XX:XX:XX:XX:XX:XX,

[ifupdown]
managed=true

Restart the network service

sudo service networking restart.

Boot Delay due to Wait for Network Configuration

This problem happens sometimes when ubuntu starts up. You can’t really boot to the interface sometimes.

Splash Screen with the 5 dots and a message saying:

waiting for network configuration

followed by:

waiting an additional 60 seconds for network configuration

Solution to this problem is following :

In /etc/network/interfaces this changes all interfaces (except lo) from auto to allow-hotplug. This way the boot is no more waiting for the interfaces to come up first.Example before (look at auto eth0):

auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

Example after (look at allow-hotplug eth0):

auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

auto wlan0
allow-hotplug wlan0
iface wlan0 inet dhcp

 

Install Build-Essential

Informational list of build-essential packages

Other Packages Related to build-essential

  • dpkg-dev (>= 1.17.11)
    Debian package development tools
  • g++ (>= 4:5.2)
    GNU C++ compiler
  • gcc (>= 4:5.2)
    GNU C compiler
  • libc6-dev
    GNU C Library: Development Libraries and Header Files
    or libc-dev
    virtual package provided by libc6-dev
  • make
    utility for directing compilation
    also a virtual package provided by make-guile
    To Install the build-essential package:
    sudo apt-get update
sudo apt-get install build-essential

In the Queue…

GSoC2016Logofever_logoFOSSASIA bring’s people together to share, create, develop and make things with Open Technologies and software. We organize science hack labs, Open Tech events, meetups and coding programs with developers, designers and contributors.
Checkout the FOSSASIA Idea’s page for more information.
(ˢᵒᶜⁱᵉᵗʸserver) aims to be a platform for developing collaborative applications.
sTeam server project repository: sTeam.

The GSOC 2016 unraveled so far…..

The Organizations were declared on 29th March 2016.
The Proposal Submission period was from 15th March-25th March 2016.

TimeLine

sTeam is a project under the organization FOSSASIA mentored by Martin Bähr.

Since then the activities done so far include:-

1.Installing the application on Linux Platform.

sTeam was successfully installed on Ubuntu 12.04, Ubuntu 14.04, Ubuntu 15.04 and CentOS 7.

2.Understanding the workflow of the application.
3.Bonding with the community on the IRC server irc.freenode.net channel #steam-devel and #fossasia.
4.Discussing and planning the enhancement idea’s with Mentor and associates.
5.Finding the possible area’s of application improvement.
6.Searching the archive’s to understand the platform more thoroughly.

The original website http://www.open-steam.org has been closed but the archives can still be accessed at : Archive of http://www.open-steam.org
Archive of http://server.open-steam.org
Archive of http://steamware.open-steam.org
http://societyserver.org/

7.Contributing to the project wiki.
Documenting the extracted information from the archives to the wiki pages categorically.
8.Reposting issues and solving them.

Issue’s reported : Issues.
Pull Requests : Pull Requests.

9.Writing a proposal and submitting it on the Google Dashboard.
10.Help other people to understand the application and guide them through the installation procedure.

After submitting the proposal, it’s the waiting period for the announcement of the students selected for GSOC 2016.
The selected students would be announced on 22nd April 2016.

A period filled with excitement and nervousness.
The one month period should be well utilized for the better understanding of the application by working on small bugs and staying interactive with other colleagues on IRC and work collaboratively.

Hoping to be selected for GSOC’16.
For the love of FOSS I look forward to contribute FOSSASIA organization by the Google summer of code platform or otherwise.
Finger’s crossed.
May the best candidates be selected for the event!!!
All the best to all the contestants participating in the event. :+1: