Tiny Core Linux

dCore Import Debian Packages to Mountable SCE extensions => dCore X86 => dCore x86 Imported Extensions => Topic started by: jls on July 31, 2014, 03:40:57 AM

Title: network-manager-gnome & wicd
Post by: jls on July 31, 2014, 03:40:57 AM
Hi
Someone could run these packages here on dCore?
Thanks
Title: Re: network-manager-gnome & wicd
Post by: Juanito on July 31, 2014, 04:01:43 AM
networkmanager works on corepure64  ;)
Title: Re: network-manager-gnome & wicd
Post by: Jason W on July 31, 2014, 10:50:07 AM
I will test these in the near future, right now the wireless is out on my laptop but I plan to get a wireless usb adapter.
Title: Re: network-manager-gnome & wicd
Post by: Jason W on August 06, 2014, 03:31:02 PM
Re-import wicd and try it from the applications menu, I will work on network-manager-gnome.
Title: Re: network-manager-gnome & wicd
Post by: jls on August 07, 2014, 05:19:10 AM
Code: [Select]
jls@eeepc:~$ sudo /etc/init.d/wicd start
Starting Network connection manager: wicd failed!
jls@eeepc:~$ sudo wicd -f
Traceback (most recent call last):
  File "/usr/share/wicd/daemon/wicd-daemon.py", line 1859, in <module>
    main(sys.argv)
  File "/usr/share/wicd/daemon/wicd-daemon.py", line 1808, in main
    print 'unable to chown log file to %s' % group[2]
UnboundLocalError: local variable 'group' referenced before assignment
jls@eeepc:~$ jls@eeepc:~$ sudo wicd -feo
---------------------------
wicd initializing...
---------------------------
wicd is version 1.7.2.4 768
did not find backend in configuration, setting default external
setting backend to external
trying to load backend external
successfully loaded backend external
trying to load backend external
successfully loaded backend external
Automatically detected wireless interface wlan0
did not find wireless_interface in configuration, setting default wlan0
setting wireless interface wlan0
automatically detected wired interface eth0
did not find wired_interface in configuration, setting default eth0
setting wired interface eth0
did not find wpa_driver in configuration, setting default wext
setting wpa driver wext
did not find always_show_wired_interface in configuration, setting default False
did not find use_global_dns in configuration, setting default False
setting use global dns to False
did not find global_dns_1 in configuration, setting default None
did not find global_dns_2 in configuration, setting default None
did not find global_dns_3 in configuration, setting default None
did not find global_dns_dom in configuration, setting default None
did not find global_search_dom in configuration, setting default None
setting global dns
global dns servers are None None None
domain is None
search domain is None
did not find auto_reconnect in configuration, setting default True
setting automatically reconn..........[CUT]
At this point the wicd gui starts and shows the netowrks available but when I try to connect I see on the terminal where wicd is running:
Code: [Select]
DHCP connection successful
not verifying
Connecting thread exiting.
Sending connection attempt result success
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Operation failed.
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Starting automatic reconnect process
Autoconnecting...
No wired connection present, attempting to autoconnect to wireless network
Unable to autoconnect, you'll have to manually connect
Starting automatic reconnect process
Autoconnecting...
No wired connection present, attempting to autoconnect to wireless network
Invalid network mode string, ignoring!
Unable to autoconnect, you'll have to manually connect

Title: Re: network-manager-gnome & wicd
Post by: Jason W on August 07, 2014, 08:14:48 AM
Ok, I was able to get the gui to come up, but for those errors I am going to have to wait until I have wireless access to go any further.
Title: Re: network-manager-gnome & wicd
Post by: jls on September 06, 2014, 04:15:08 PM
Hi
I've managed to make network-manager-gnome working as root, this is what I have in /opt/bootlocal.sh:
Code: [Select]
/etc/init.d/dbus start
[ -d /etc/NetworkManager/system-connections ] || mkdir /etc/NetworkManager/s
/bb/addgroup jls netdev
/etc/init.d/network-manager start
and then I created a file in .X.d with the following content:
Code: [Select]
sudo nm-applet &if I start the applet without sudo when I try for example to disconnect I get this error:
Code: [Select]
** (nm-applet:9610): WARNING **: Failed to register as an agent: (32) No session found for uid 1000
** Message: applet now embedded in the notification area
** (nm-applet:9610): WARNING **: disconnect_cb: Device disconnect failed: (32) Not authorized to Disconnect connections

Title: Re: network-manager-gnome & wicd
Post by: sm8ps on July 27, 2015, 06:30:47 AM
I know this thread is already dated but it also does look quite unfinished and I am at the very same point as where it stands now.

I need a more powerful tool to handle wireless networks than 'wifi.sh'. I tried Connman but did not get anywhere with it. Now I am working on Network-Manager but I am stuck.

Opposed to jls_legalize, I work on ub-dCore-trusty. I have performed the following steps:
. import and load network-manager and network-manager-gnome

-- Oops! Hit the "Save"-key by accident. Shall add more info here! --
Title: Re: network-manager-gnome & wicd
Post by: Juanito on July 27, 2015, 07:08:40 AM
doesn't network-manager-gnome need the whole gnome environment loaded in order to work?
Title: Re: network-manager-gnome & wicd
Post by: jls on July 27, 2015, 07:24:12 AM
doesn't network-manager-gnome need the whole gnome environment loaded in order to work?
no. It is used for example in bodhi linux which uses e and not gnome. I use connman in dcore trusty via the e connection manager module
Title: Re: network-manager-gnome & wicd
Post by: sm8ps on July 27, 2015, 07:37:10 AM
@juanito: I do not think so. AFAIK it merely provides the nm-applet.

Re-starting my account here!
Initial state: no wireless extension loaded, no Ethernet cable connected.

I was about to state the all the while the NetworkManager-Applet is visible but not functional; it shows a "wrong direction" traffic sign. Upon closer inspection I found out that it IS functional, indeed. It had not been before but by following the above steps I do get a fully functional NetworkManager for wired connections!

Celebration time!  :) I shall continue investigating about wireless connections with it.

Warning (1): NetworkManager
Code: [Select]
(NetworkManager:8410): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Key file does not have group 'connectivity'

Warnings (2): nm-applet
Code: [Select]
** (nm-applet:8444): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files

(nm-applet:8444): nm-applet-WARNING **: Icon nm-no-connection missing: (0) Icon 'nm-no-connection' not present in theme

(nm-applet:8444): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(nm-applet:8444): nm-applet-WARNING **: Failed to register as an agent: (32) Session not found

(nm-applet:8444): nm-applet-WARNING **: Failed to register as an agent: (32) Session not found

(nm-applet:8444): nm-applet-WARNING **: Icon nm-no-connection missing: (0) Icon 'nm-no-connection' not present in theme

(nm-applet:8444): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
nm-applet-Message: using fallback from indicator to GtkStatusIcon

(nm-applet:8444): nm-applet-WARNING **: Icon nm-no-connection missing: (0) Icon 'nm-no-connection' not present in theme

(nm-applet:8444): libnotify-WARNING **: Failed to connect to proxy

(nm-applet:8444): nm-applet-WARNING **: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files

** (nm-applet:8444): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/0: No session found for uid 1000 (unknown)

** (nm-applet:8444): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/0: No session found for uid 1000 (unknown)
Title: Re: network-manager-gnome & wicd
Post by: sm8ps on July 27, 2015, 07:39:26 AM
doesn't network-manager-gnome need the whole gnome environment loaded in order to work?
no. It is used for example in bodhi linux which uses e and not gnome. I use connman in dcore trusty via the e connection manager module
This sounds like you are using Enlightenment desktop, right? Do you have any experience with Connman on Openbox (&LXDE)?
Title: network-manager-gnome & wireless
Post by: sm8ps on July 27, 2015, 07:57:01 AM
Making wireless connections available through NM is easy. After loading the wireless extension it had picked them up instantly. I can selectively en-/disable wifi etc.

There is one major road block, though: upon selecting my network I should enter a WPA-key. However the nm-applet complains about a missing service:
Code: [Select]
** Message: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files

I see the following issues:
The latter two seem minor at this point; the first one is a quite a biggie.

Alternatively, one could of course configure the wireless network connections manually. Indeed, after selecting my WLAN, a corresponding file was created under '/etc/NetworkManager/system-connections/' which contains everything but the WPA-key. It seems to be a matter of adding a line "psk=<KEY>" to the section [802-11-wireless-security]. Yet I would prefer an integrated solution.

I have no experience with Dbus-services. Can anybody please help?
Title: Re: network-manager-gnome & wireless
Post by: sm8ps on July 27, 2015, 08:06:02 AM
Trivial!  8)
Had to add gnome-keyring to it and everything is working just fine. I even got some icons now showing the signal strength. So that seems to have taken care of the issue about missing icons.

Next step is how to automate this process and how to make it persistent.
Title: Re: network-manager-gnome & wicd
Post by: Jason W on July 27, 2015, 08:52:19 AM
Thanks sm8ps, I will look into what I can do on my end to make this just work.
Title: Re: network-manager-gnome & wicd
Post by: sm8ps on July 27, 2015, 09:13:10 AM
Thanks, JasonW! Your support is much appreciated.

Triggering Glib should be handled by a start-up script. For persistence, the folder '/etc/NetworkManager/' should be included into '.filetool.lst'. The sub-folder 'system-connections/' must be initially created.

In addition, I found the following strange behavior. Upon re-boot, the icons have gone missing again. I did not do anything for them to appear but doing the same now does not have any effect.  :o How can icons appear on their own? Is there a way to re-launch LXDE? Calling "Reconfigure Openbox" from the "System"-menu does not have any effect.

There are various "nm-stage*"-files under '/usr/share/icons/{Humanity,Humanity-dark,hicolor}' so it is a question of loading them. Killing 'nm-applet' and re-launching it does not have the desired effect.
Title: Re: network-manager-gnome & wicd
Post by: sm8ps on July 27, 2015, 09:26:38 AM
Okay, progress made! (Can you tell that I am Google-ing my ways along the error messages? ;) )

Calling ''sudo gtk-update-icon-cache-3.0 -f /usr/share/icons/hicolor/'' before launching nm-applet does provide it with the icons. The option "-f" (force) is necessary from what I can tell.

So I would say that this thing is ready to be wrapped up.  ;)
Title: Re: network-manager-gnome & wicd
Post by: jls on July 27, 2015, 11:16:24 AM


This sounds like you are using Enlightenment desktop, right? Do you have any experience with Connman on Openbox (&LXDE)?
there is a gui for comman. Is it mm-applet supposed to run as root?
Title: Re: network-manager-gnome & wicd
Post by: sm8ps on July 27, 2015, 01:27:31 PM
Is it mm-applet supposed to run as root?
Hm, in principle not; at least that is the way it is on my regular Ubuntu installation. However, if I run it as regular user on dCore then I get an error popping up when trying to connect to a wireless network:
(32) Not authorized to control networking.
Title: Re: network-manager-gnome & wicd
Post by: sm8ps on July 27, 2015, 01:37:40 PM
Found the following which seems to be a work-around:
https://awesome.naquadah.org/wiki/Nm-applet#Running_as_a_non-root_user

This link claims that nm-applet should start automatically; however it does not show up after exiting to the prompt and re-starting the LXDE/Openbox-desktop.
https://wiki.archlinux.org/index.php/NetworkManager#Openbox
Title: Re: network-manager-gnome & wicd
Post by: sm8ps on August 28, 2015, 01:06:08 PM
Sorry to bump this thread but I am at wits' end and must ask for support.

I use the following steps to get Network-Manager going:
Code: [Select]
sce-load wireless
sce-load network-manager
sudo NetworkManager &
sudo /usr/local/postinst/libglib2.0-0 trigger
sudo nm-applet &
sudo gtk-update-icon-cache-3.0 -f /usr/share/icons/hicolor/

Upon launching NetworkManager I get the following warning which seems harmless:
Code: [Select]
(NetworkManager:9506): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Key file does not have group 'connectivity'
There is no group connectivity. Shoudl it be created? My user is in the group "netdev" already but that does not seem to play a role, or does it?  :o

Without gtk-update-icon-cache-3.0 I get tons of icon missing signals.

Launching nm-applet without sudo, it get the same error pop-up as the one described by jls_legalize (http://forum.tinycorelinux.net/index.php/topic,17329.msg104706.html#msg104706) when trying to e.g. change connection.
Code: [Select]
Failed to add/activate connection
(32) Not authorized to control networking.

I would be very glad if Network-Manager worked because it does behave much more stable across suspending then the wpa-script. I would like to have a way to get it started in a more self-contained fashion. Plus I do not really know what I am doing here so some knowledgeable support would be quite comforting. :)

Cheers!
sm
Title: Re: network-manager-gnome & wicd
Post by: Jason W on August 29, 2015, 06:03:15 AM
Add your user to the connectivity group, if that helps we can use that and the other info to proceed.
Title: Re: network-manager-gnome & wicd
Post by: sm8ps on August 29, 2015, 08:37:18 AM
Tried as suggested; created group connectivity, added my user as well as root to that group. -- No noticable changes.

Protocol:
Code: [Select]
sudo groupadd -r connectivity && sudo usermod tc -aG connectivity && sudo usermod root -aG connectivity
sce-load wireless && sce-load network-manager
sudo /usr/local/postinst/libglib2.0-0 trigger && sudo gtk-update-icon-cache-3.0 -f /usr/share/icons/hicolor/
sudo NetworkManager &
sudo nm-applet &

According to one of the resources mentioned above, I had created the following file in order to give my user sufficient credentials to run nm-applet without sudo but that did not work. The applet would start and connect to one of the "system connections" but it is impossible to change the connection due to "(32) Not authorized to control networking." Here is the file for reference:
Code: [Select]
/etc/polkit-1/localauthority.conf.d/50-org.freedesktop.NetworkManager.pkla
[nm-applet]
Identity=unix-group:netdev
Action=org.freedesktop.NetworkManager.*
ResultAny=yes
ResultInactive=no
ResultActive=yes

Warnings upon launching sudo NetworkManager &
Code: [Select]
(NetworkManager:9496): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Key file does not have group 'connectivity'

Warnings upon launching sudo nm-applet &
Code: [Select]
** (nm-applet:9532): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
GConf Error: Configuration server couldn't be contacted: D-BUS error: Message did not receive a reply (timeout by message bus)
[message repeated 32 times]
nm-applet-Message: using fallback from indicator to GtkStatusIcon

Upon that, I do have a fully functional nm-applet (in LXDE/Openbox). So AFAICT this is a working solution; it seems questionable, however, if it is sane. :)
Title: Re: network-manager-gnome & wicd
Post by: Jason W on August 29, 2015, 09:54:30 AM
I will try and spend some time with this too, as there is simply something missing in a startup script, or a user/group, stuff like that.  Pretty much everything is fixable.