After upgrading from gutsy to hardy, all controls in "Network Settings" window are greyed out, making it impossible to configure networking.

Bug #227383 reported by msp3k on 2008-05-06
6
Affects Status Importance Assigned to Milestone
gnome-system-tools (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: gnome-system-tools

After upgrading from gutsy to hardy, (nearly) all controls in the "Network Settings" window are greyed out, making it impossible to make changes to the current network settings (including the active interfaces) or select a different network location. Only the "Help" and "Close" buttons work. This happens consistently every time.

This is true when running as user (and prompted to enter a password) and when running as root.

This is true even when deleting /root/.gnome2/network-admin-locations and forcing network-admin to recreate the directory.

Attached is the gzipped output from strace while running /usr/bin/network-admin as a regular user.

Output from ifconfig -a:
-------------------------------------------------------------------------------
ath0 Link encap:Ethernet HWaddr 00:19:7d:3d:11:f4
          inet6 addr: fe80::219:7dff:fe3d:11f4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ath0:avahi Link encap:Ethernet HWaddr 00:19:7d:3d:11:f4
          inet addr:169.254.6.211 Bcast:169.254.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr 00:16:d3:4f:bd:9b
          inet addr:160.36.47.169 Bcast:160.36.47.255 Mask:255.255.254.0
          inet6 addr: fe80::216:d3ff:fe4f:bd9b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2611 errors:0 dropped:0 overruns:0 frame:0
          TX packets:339 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:711885 (695.2 KB) TX bytes:42868 (41.8 KB)
          Interrupt:219

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:4642 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4642 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:232100 (226.6 KB) TX bytes:232100 (226.6 KB)

wifi0 Link encap:UNSPEC HWaddr 00-19-7D-3D-11-F4-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:50 errors:0 dropped:0 overruns:0 frame:46373
          TX packets:143 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:199
          RX bytes:3733 (3.6 KB) TX bytes:6862 (6.7 KB)
          Interrupt:22
-------------------------------------------------------------------------------

Output from netstat -nr:
-------------------------------------------------------------------------------
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
160.36.46.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 ath0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 160.36.46.1 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ath0
-------------------------------------------------------------------------------

Contents of /etc/resolv.conf:
-------------------------------------------------------------------------------
search knology.net
nameserver 160.36.128.69
nameserver 160.36.0.66
nameserver 160.36.128.66
-------------------------------------------------------------------------------

Contents of /root/.gnome2/network-admin-locations/Cline's House:
-------------------------------------------------------------------------------

[general]
hostname=glitch
domainname=
dns-servers=192.168.1.254,
search-domains=launchmodem.com,
static-hosts=127.0.0.1;localhost,127.0.1.1;glitch,::1;ip6-localhost;ip6-loopback,fe00::0;ip6-localnet,ff00::0;ip6-mcastprefix,ff02::1;ip6-allnodes,ff02::2;ip6-allrouters,ff02::3;ip6-allhosts,

[eth0]
auto=true
active=false
configured=true
config-method=dhcp
ip-address=
ip-mask=
gateway-address=
network-address=
broadcast-address=

[ath0]
auto=true
active=true
configured=true
essid=cline
key=**********
key-type=wep-hex
config-method=dhcp
ip_address=
ip_mask=
gateway-address=
network-address=
broadcast-address=

[ppp0]
auto=false
active=false
configured=false
login=
password=
phone-number=
phone-prefix=
default-gw=false
peer-dns=false
persistent=false
peer-noauth=false
serial-port=
volume=3
dial-type=1
-------------------------------------------------------------------------------

Contents of /root/.gnome2/network-admin-locations/Generic Roaming Mode:
-------------------------------------------------------------------------------

[general]
hostname=glitch
domainname=
dns-servers=192.168.1.254,
search-domains=launchmodem.com,
static-hosts=127.0.0.1;localhost,127.0.1.1;glitch,::1;ip6-localhost;ip6-loopback,fe00::0;ip6-localnet,ff00::0;ip6-mcastprefix,ff02::1;ip6-allnodes,ff02::2;ip6-allrouters,ff02::3;ip6-allhosts,

[eth0]
auto=true
active=true
configured=true
config-method=dhcp
ip-address=
ip-mask=
gateway-address=
network-address=
broadcast-address=

[ath0]
auto=true
active=true
configured=false
essid=peek
key=**********
key-type=wep-hex
config-method=
ip_address=
ip_mask=
gateway-address=
network-address=
broadcast-address=

[ppp0]
auto=false
active=false
configured=false
login=
password=
phone-number=
phone-prefix=
default-gw=false
peer-dns=false
persistent=false
peer-noauth=false
serial-port=
volume=3
dial-type=1
-------------------------------------------------------------------------------

Contents of /root/.gnome2/network-admin-locations/Home:
-------------------------------------------------------------------------------

[general]
hostname=glitch
domainname=
dns-servers=192.168.1.254,
search-domains=launchmodem.com,
static-hosts=127.0.0.1;localhost,127.0.1.1;glitch,::1;ip6-localhost;ip6-loopback,fe00::0;ip6-localnet,ff00::0;ip6-mcastprefix,ff02::1;ip6-allnodes,ff02::2;ip6-allrouters,ff02::3;ip6-allhosts,

[eth0]
auto=false
active=false
configured=true
config-method=dhcp
ip-address=
ip-mask=
gateway-address=
network-address=
broadcast-address=

[ath0]
auto=true
active=true
configured=true
essid=peek
key=**********
key-type=wep-hex
config-method=dhcp
ip_address=
ip_mask=
gateway-address=
network-address=
broadcast-address=

[ppp0]
auto=false
active=false
configured=false
login=
password=
phone-number=
phone-prefix=
default-gw=false
peer-dns=false
persistent=false
peer-noauth=false
serial-port=
volume=3
dial-type=1
-------------------------------------------------------------------------------

Contents of /root/.gnome2/network-admin-locations/Home:
-------------------------------------------------------------------------------

[general]
hostname=glitch
domainname=
dns-servers=160.36.0.66,160.36.128.66,
search-domains=launchmodem.com,
static-hosts=127.0.0.1;localhost,127.0.1.1;glitch,::1;ip6-localhost;ip6-loopback,fe00::0;ip6-localnet,ff00::0;ip6-mcastprefix,ff02::1;ip6-allnodes,ff02::2;ip6-allrouters,ff02::3;ip6-allhosts,

[eth0]
auto=false
active=false
configured=true
config-method=dhcp
ip-address=
ip-mask=
gateway-address=
network-address=
broadcast-address=

[ath0]
auto=true
active=true
configured=true
essid=bruce
key=**********
key-type=wep-hex
config-method=dhcp
ip_address=
ip_mask=
gateway-address=
network-address=
broadcast-address=

[ppp0]
auto=false
active=false
configured=false
login=
password=
phone-number=
phone-prefix=
default-gw=false
peer-dns=false
persistent=false
peer-noauth=false
serial-port=
volume=0
dial-type=0
-------------------------------------------------------------------------------

Contents of /root/.gnome2/network-admin-locations/UTK:
-------------------------------------------------------------------------------

[general]
hostname=glitch
domainname=
dns-servers=160.36.128.69,160.36.0.66,160.36.128.66,
search-domains=
static-hosts=127.0.0.1;localhost,127.0.1.1;glitch,::1;ip6-localhost;ip6-loopback,fe00::0;ip6-localnet,ff00::0;ip6-mcastprefix,ff02::1;ip6-allnodes,ff02::2;ip6-allrouters,ff02::3;ip6-allhosts,

[eth0]
auto=false
active=false
configured=true
config-method=dhcp
ip-address=
ip-mask=
gateway-address=
network-address=
broadcast-address=

[ath0]
auto=true
active=true
configured=true
essid=nomad
key=
key-type=wep-hex
config-method=dhcp
ip_address=
ip_mask=
gateway-address=
network-address=
broadcast-address=

[ppp0]
auto=false
active=false
configured=false
login=
password=
phone-number=
phone-prefix=
default-gw=false
peer-dns=false
persistent=false
peer-noauth=false
serial-port=
volume=3
dial-type=1
-------------------------------------------------------------------------------

Contents of /root/.gnome2/network-admin-locations/Wired Generic:
-------------------------------------------------------------------------------

[general]
hostname=glitch
domainname=
dns-servers=160.36.128.69,160.36.0.66,160.36.128.66,
search-domains=
static-hosts=127.0.0.1;localhost,127.0.1.1;glitch,::1;ip6-localhost;ip6-loopback,fe00::0;ip6-localnet,ff00::0;ip6-mcastprefix,ff02::1;ip6-allnodes,ff02::2;ip6-allrouters,ff02::3;ip6-allhosts,

[eth0]
auto=true
active=true
configured=true
config-method=dhcp
ip-address=
ip-mask=
gateway-address=
network-address=
broadcast-address=

[ath0]
auto=true
active=false
configured=true
essid=nomad
key=
key-type=wpa-psk
config-method=dhcp
ip_address=
ip_mask=
gateway-address=
network-address=
broadcast-address=

[ppp0]
auto=false
active=false
configured=false
login=
password=
phone-number=
phone-prefix=
default-gw=false
peer-dns=false
persistent=false
peer-noauth=false
serial-port=
volume=0
dial-type=0
-------------------------------------------------------------------------------

msp3k (peek-nimbios) wrote :
Pedro Villavicencio (pedro) wrote :

thanks for your report, can you take an screenshot of the dialog? Does the same happens with a new user created on your system? thanks.

Changed in gnome-system-tools:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Sam_ (and-sam) wrote :

Hi,
confirmed.
Open System>Administration>Network and give password, the field to unlock is greyed out.

To verify the problem I went to user and groups in settings.
I'm allowed to see my home user settings the group settings are greyed out.
I'm a single user and also can be root, so I've unlocked and was asked to authenticate, I've typed my password and it failed, see second screenshot (an unexpected error occured).

System: Hardy 8.04 amd_64
Package: gnome-system-t 2.22.0-0ubuntu
uname: Linux myname 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux

Thanks.

Sam_ (and-sam) wrote :
Sam_ (and-sam) wrote :

Here is some information from the auth.log
First attempt when opening the network settings:
May 7 01:30:09 myname sudo: PAM unable to dlopen(/lib/security/pam_smbpass.so)
May 7 01:30:09 myname sudo: PAM [error: /lib/security/pam_smbpass.so: cannot open shared object file: No such file or directory]
May 7 01:30:09 myname sudo: PAM adding faulty module: /lib/security/pam_smbpass.so
May 7 01:30:20 myname sudo: user : TTY=unknown ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/network-admin
May 7 01:30:20 myname sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
May 7 01:30:20 myname sudo: pam_unix(sudo:session): session closed for user root

Second attempt in user and group settings, I can't work on group settings on my home user name, see screenshot no.3
Then marking root and unlock to work on group settings, then password and pressing authenticate, the messages are:
May 7 01:45:17 myname polkit-grant-helper-pam[5966]: PAM unable to dlopen(/lib/security/pam_smbpass.so)
May 7 01:45:17 myname polkit-grant-helper-pam[5966]: PAM [error: /lib/security/pam_smbpass.so: cannot open shared object file: No such file or directory]
May 7 01:45:17 myname polkit-grant-helper-pam[5966]: PAM adding faulty module: /lib/security/pam_smbpass.so
May 7 01:45:28 myname polkit-grant-helper[5963]: granted authorization for org.freedesktop.systemtoolsbackends.set to pid 5933 [uid=1000] [auth=user]

Third attempt to open group settings: success
Why, after typing the password I didn't press authenticate, I just pressed enter and every window from user and root is available to scroll and work with.

Network administration is still not. And I have no idea what therefore has to be changed.

Sam_ (and-sam) wrote :

Output from terminal:
#sudo network-admin
(network-admin:28306): Gtk-WARNING **: Unknown property: GtkComboBox.items
** (network-admin:28306): CRITICAL **: Unable to lookup session information for process '28306'
The last lines from Xorg.0.log:
May 10 22:32:14 myname sudo: name : TTY=unknown ; PWD=/home/name ; USER=root ; COMMAND=/usr/bin/network-admin
May 10 22:32:14 myname sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
May 10 22:32:14 myname sudo: pam_unix(sudo:session): session closed for user root
May 10 22:32:59 myname sudo: PAM unable to dlopen(/lib/security/pam_smbpass.so)
May 10 22:32:59 myname sudo: PAM [error: /lib/security/pam_smbpass.so: cannot open shared object file: No such file or directory]
May 10 22:32:59 myname sudo: PAM adding faulty module: /lib/security/pam_smbpass.so
May 10 22:33:07 myname sudo: name : TTY=pts/0 ; PWD=/home/name ; USER=root ; COMMAND=/usr/bin/network-admin
May 10 22:33:07 myname sudo: pam_unix(sudo:session): session opened for user root by name(uid=0)
May 10 22:33:07 myname sudo: pam_unix(sudo:session): session closed for user root

Sam_ (and-sam) wrote :

Hi,
just an idea. In my view there is something very wrong with usershares that gives outputs like the above. The idea came through the unrelated Bug #223912 from here.
If there are inconcistencies between pam and PolicyKit as a single unfamiliar user I have a big problem with understanding how to use the PolicyKit in a correct way. I've read manuals over and over, but sorry I don't get it. And if I understand the specs/PolicyKitIntegration right it's supposed to be like that "For Hardy we want to gently introduce it".
Is a commercial support also available for individuals or only for companies? For me this is getting outrages complicated and I'm sure not alone with this, e.g. Susan Linton in the newsletter #90. I really want to try my best, but also would like to have fun with my system and instead was busy with filing bugs after upgrading. Sorry for this outgoing, I hope the professionals here have a little understanding and I do appreciate your assistance.

Sam_ (and-sam) wrote :

Hi again,
I've found a related bug #187335.
My user was and is in the admin group. I would like to know the steps which allow me to access network-admin.
In the system monitor are running:
debus-daemon
#/usr/bin/debus-daemon --fork --print-pid 11 print-address 13 --session
debus-daemon
#debus-daemon --fork --print-pid 28 print-address 30 --session
debus-daemon
#debus-daemon --fork --print-pid 28 print-address 30 --session
all with different pids
and
debus-launch

Sam_ (and-sam) wrote :

Hi again,
Outputs from terminal are:
network-admin
(network-admin:2930): Gtk-WARNING **: Unknown property: GtkComboBox.items
** (network-admin:2965): CRITICAL **: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

sudo network-admin
(network-admin:3047): Gtk-WARNING **: Unknown property: GtkComboBox.items
** (network-admin:3047): CRITICAL **: Unable to lookup session information for process '3047'
##Window is greyed out, same with gksudo

gksu network-admin
** (network-admin:3092): CRITICAL **: Unable to lookup session information for process '3092'

gksudo network-admin
** (network-admin:3195): CRITICAL **: Unable to lookup session information for process '3195'

The question is why I'm getting access to e.g. change date+time, hal+mount or users-admin like the output mentioned above:
##granted authorization for org.freedesktop.systemtoolsbackends.set to pid 5933 [uid=1000] [auth=user]
and to network-admin.

Sam_ (and-sam) wrote :

Correct: and n o t to network-admin

tosoth (tosoth) wrote :

Hi. Don't run network-admin with sudo. It doesn't work for me also.

Do you have problems also, when you try to run network-admin immediately after system restart?

tosoth (tosoth) wrote :

Oh, and maybe you know that, but... you can ignore this errors

May 7 01:30:09 myname sudo: PAM unable to dlopen(/lib/security/pam_smbpass.so)
May 7 01:30:09 myname sudo: PAM [error: /lib/security/pam_smbpass.so: cannot open shared object file: No such file or directory]
May 7 01:30:09 myname sudo: PAM adding faulty module: /lib/security/pam_smbpass.so

It's not really an error and it's not related with your problems.
Also Gtk-WARNINGs while running some gnome-system-tools can be ignored. I had them on clean system also, and everything worked.

bsh (bsh) wrote :

i have the same(problem), but, funnily, it only happens when i log on the pc over vnc: unlock is greyed out, can't do anything. (and i have a bunch of other issues, too...). when i log in locally on the pc, it works well, but not over vnc.

Sam_ (and-sam) wrote :

Hi tosoth,
I've just had a restart after updating and tried to open, same procedures, same results.
Thanks for unwarning the warnings :-)
The interesting thing is, when reading the PolicyKit specs and manuals, nowhere is mentioned the use case how to get in the network-manager, they only mention hal, groups and date+time.
To get locked out from a system relevant app like this isn't acceptable.

@bsh
If it works well when logged in locale could you please provide the settings you have, e.g. is your user added in the group of polkit? (it should be the last one in groups)
And what are the settings for Manage System Configuration in Authorizations of PolicyKit?
Has the user to be granted in Explicit?
Thanks a lot, because I really want to figure out where the problem hides.

Sam_ (and-sam) wrote :

Hi all,
I've won half the way, maybe because of an update which came in. (I didn't change any system settings or settings in polkit)
Working is now:
#network-admin
(network-admin:6335): Gtk-WARNING **: Unknown property: GtkComboBox.items

This "box" is opening and after entering the password surprise surprise I'm not getting locked out anymore. Thanks for whoever fixed this.
And now comes the "but", trying to open it via GUI System+Administration+Network, no way, after entering the pw everything is just for reading greyed out. In these moments one appreciates the console :-)

I hope you all have the same luck and get it at least working from the terminal. I'm sorry not beeing able to provide steps I've made, because I didn't make one, except reading until my head blows off.

tosoth (tosoth) wrote :

Good for you :).
I intended to give you this quite interesting lecture about "how policykit works" :P, but I see you don't need it anymore. That's good.
http://hal.freedesktop.org/docs/PolicyKit/model-theory-of-operation.html
Today was another Hal update, maybe that fixed something, but for now nothing changed in my case. In example I can't Unlock again and I'm too lazy to restart now ;).

Sam_ (and-sam) wrote :

Hi tosoth,

is it now working after the updates?
One announced, that checking #/etc/hosts helped, because the settings were not ok.
Maybe it's a clue for you also.
And yes I've read the specs and the manual from David Zeuthen as I mentioned above :-)
https://wiki.ubuntu.com/DesktopTeam/Specs/PolicyKitIntegration

Sam_ (and-sam) wrote :

For demonstration purposes attached are the different graphical views. After calling network and given the password the button to unlock is greyed out, in services it is not.
Until now any update didn't resolve this difference.

Sam_ (and-sam) wrote :
Jim Tarvid (tarvid) wrote :

System, Preferences, Main Menu, System, Preferences, Administration, Right Click Network, Properties, delete gksu in front of command.

Sam_ (and-sam) wrote :

Hi Jim,
what can I say, the solution is so simple and you are fantastic. Many thanks!

Pedro Villavicencio (pedro) wrote :

Thanks for the report msp3k , It has been a long time without any comment or a duplicate in this bug report and It is possible that the bug has been fixed. May you please try to reproduce it with the latest Stable Release of Ubuntu the Natty Narwhal and add the respective comments to the report? You can learn how to get that release at http://www.ubuntu.com/download . Thanks again and we appreciate your help.

Changed in gnome-system-tools (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
Launchpad Janitor (janitor) wrote :

[Expired for gnome-system-tools (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-system-tools (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions