Hardy Alpha-3 networking

Richard Mancusi vrman49 at gmail.com
Fri Jan 18 03:53:32 UTC 2008


The problem shown below appears to have been resolved with
tonight's update.

tnx
-rich


On Jan 15, 2008 9:39 PM, Richard Mancusi <vrman49 at gmail.com> wrote:
>
> On Jan 15, 2008 8:40 PM, Richard Mancusi <vrman49 at gmail.com> wrote:
> >
> > On Jan 15, 2008 6:43 PM, Emilio Pozuelo Monfort <pochu at ubuntu.com> wrote:
> > > (``-_-´´) -- Fernando wrote:
> > > > On Monday 14 January 2008 17:14:29 Brian Murray wrote:
> > > >> You should have to authenticate before modifying the network
> > > >> configuration.  On my Hardy systems and a daily build of the Live CD,
> > > >> there is an "Unlock" button and selections remain greyed out until I
> > > >> unlock the application.  If your system is fully up to date and the
> > > >> "Unlock" button is not there then you should submit a bug report.  Your
> > > >> issues regarding changing the network configuration are probably a
> > > >> direct result of your not being authenticated.
> > > >>
> > > >> Thanks,
> > > >
> > > > I'm up to date, and using the menus, I just get a full grayed window and cant manage my networks options.
> > > > If I try the old Network Monitor 2.12.1, it just says that the interface (either and both eth0 and eth1)  doesnt exist.
> > > >
> > > >
> > >
> > > That sounds like bug 176060. Now that gnome-system-tools uses PolicyKit, you
> > > need to run it as a normal user, and not through gksu. Could you verify that you
> > > have network-manager-gnome 0.6.5-0ubuntu11, which fixed this issue, and that
> > > running 'gksu network-admin' keeps it greyed out, and that running
> > > 'network-admin' you can unlock it?
> > >
> > > Regards,
> > > Emilio
> > >
> >
> > Tonight's upgrade included several PolicyKit pkgs and I did verify
> > that I am running network-manager-gnome 0.6.5-0ubuntu11 and
> > network-manager 0.6.5-0ubuntu17.
> >
> > Now clicking on "Unlock" yields a window stating:
> > "Could not authenticate  An unexpected error has occurred."
> > This occurs by simply clicking on the "Unlock" button - not given
> > the chance to enter a password.
> >
> > -rich
> >
>
> I need to reply to my own email to add info.  I attempted to re-start
> a service and received the same error - so it has nothing to do with
> networking but rather authentication.  You had already assumed that,
> I am simply proving it.
>
> System/Administration/Services
> click on "Unlock" and receive the following message
> Could not authenticate
> An unexpected error has occurred.
>
> -rich
>




More information about the Ubuntu-devel-discuss mailing list