[network-admin] UI file not found

Thank you for your bug report, that's not a bug, the new version uses policykit and should be run as a normal user, not using sudo as you are doing

I get the same error as a non-root user user.

Attempting to invoke it through nm-applet prompts for password, and then fails silently.

Me too.
mrashley@cho:~$ network-admin

** (network-admin:20438): CRITICAL **: UI file not found: /usr/share/gnome-system-tools/ui/network.ui

mrashley@cho:~$ sudo network-admin

** (network-admin:20444): CRITICAL **: UI file not found: /usr/share/gnome-system-tools/ui/network.ui

mrashley@cho:~$

Same here:
chrisjan@ubuntu:~$ network-admin

** (network-admin:10708): CRITICAL **: UI file not found: /usr/share/gnome-system-tools/ui/network.ui

Same here:
** (network-admin:20612): CRITICAL **: UI file not found: /usr/share/gnome-system-tools/ui/network.ui

I confirm.

This bug may actually be part of a bigger problem with PolicyKit. I noticed my syslog was much larger than it normally is after rebooting today, and I noticed this:

audio[6595]: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary priviliges:
Dec 7 23:48:17 CSC-KDRAKE-002 pulseaudio[6595]: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID again.
Dec 7 23:48:17 CSC-KDRAKE-002 pulseaudio[6595]: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
Dec 7 23:48:17 CSC-KDRAKE-002 pulseaudio[6595]: pid.c: Daemon already running.
Dec 7 23:48:17 CSC-KDRAKE-002 pulseaudio[6595]: main.c: pa_pid_file_create() failed.
Dec 7 23:48:18 CSC-KDRAKE-002 pulseaudio[6601]: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary priviliges:
Dec 7 23:48:18 CSC-KDRAKE-002 pulseaudio[6601]: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID again.
Dec 7 23:48:18 CSC-KDRAKE-002 pulseaudio[6601]: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
Dec 7 23:48:18 CSC-KDRAKE-002 pulseaudio[6601]: pid.c: Daemon already running.
Dec 7 23:48:18 CSC-KDRAKE-002 pulseaudio[6601]: main.c: pa_pid_file_create() failed.
Dec 7 23:48:23 CSC-KDRAKE-002 NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Dec 7 23:48:25 CSC-KDRAKE-002 pulseaudio[6636]: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary priviliges:
Dec 7 23:48:25 CSC-KDRAKE-002 pulseaudio[6636]: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID again.
Dec 7 23:48:25 CSC-KDRAKE-002 pulseaudio[6636]: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
Dec 7 23:48:25 CSC-KDRAKE-002 pulseaudio[6636]: pid.c: Daemon already running.
Dec 7 23:48:25 CSC-KDRAKE-002 pulseaudio[6636]: main.c: pa_pid_file_create() failed.

Those comments being dumped into the syslog has led to at least 3mb within just the last 6 or 7 hours. If PolicyKit was working properly then so would network-admin, and those users who have been having audio issues as of late would also not be having the issues they are having. IE, PolicyKit appears to be the root cause of all of these issues. I think the Ubuntu Desktop Team is all over it, therefore initially invalidating this bug was likely the proper thing to do. Its not an invalidated bug report but invalidated in respect to network-admin being the problem.

I am also having the same problem with network-admin and also getting same messages in syslogs as Kow has posted.

I also confirm the problem

Problem upon further investigation is not that network-admin doesnt see network.ui, its that there is a patch in gnome-system-tools that adds some lines to network.ui that network-manager does not like. This patch would be 83_network-locations-apply-button.dpatch IE, its an Ubuntu change leading to this trouble. I kind of figured that after searching the initially reported error and found nothing except for the Ubuntu bug reports.

I can confirm that disabling 83_network-locations-apply-button.dpatch makes network-admin start and work successfully.

This is a minimal patch to fix the bug. I think the Apply button should be after the other buttons, like it used to be, but this patch doesn't do that.

thanks for your comments it should be looked by a desktop dev.

Yay thanks Dagfinn, I figured it was something like that but i HATE XML. :)

Thank you for the work there, I've updated the patch to clean the errors, not use an another widget label and use the correct location

gnome-system-tools (2.21.2.1-0ubuntu2) hardy; urgency=low

  * debian/control.in:
    - don't Build-Depends on libglade2-dev the new version use gtkbuild
      (LP: #175922)
  * debian/patches/83_network-locations-apply-button.dpatch:
    - updated the network-admin interface changes (LP: #174512)

 -- Sebastien Bacher <email address hidden> Wed, 12 Dec 2007 18:43:04 +0100