Announcement

Collapse
No announcement yet.

Can't access "Administration mode"

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Can't access "Administration mode"

    I've upgraded from feisty to gutsy and everything looks pretty good.

    One big problem however is that when I go to K -> System Settings -> Network Settings and click "Administration mode", I get the prompt to enter my root password (check snapshot attached), and then when I enter the password I return to the window and I'm still in normal user mode.

    If I try again I'm not asked for the password, but I'm still returned to the window in normal user mode. This is really frustrating as I can't change my network settings, I've noticed the same problem in "Monitor & Display", same behavior.
    Attached Files

    #2
    Re: Can't access "Administration mode"

    I think it wants your USER password, not your root one. Ubuntu takes the principle of using sudo (which amongst other things wants the user pw) rather than su to this as well.

    Also, if you're just hitting enter, try actually clicking OK instead. It's possible but unlikely that enter is actually 'clicking' ignore or cancel.
    I am running Ubuntu 8.10 (yes Gnome) with upgrades applied daily about 0900 UK time. Hardware is Dell Precision 420, 2x 800 MHz PIII, 512 MB RDRAM, nVidia GeForce 6800 128 MB AGP graphics, 18GB SCSI and 500GB IDE HDDs, DVD burner, Hauppage TV card.

    Comment


      #3
      Re: Can't access "Administration mode"

      cantab is correct -- there is no such thing as "root password" in *buntu, unless you go to a whole lot of trouble to set up a "root user" with a different password than the user who installed the system, which is not a recommended procedure.

      Comment


        #4
        Re: Can't access "Administration mode"

        I truly can't believe it, enter was choosing something other than yes.

        Now that I've actually chosen yes with the mouse, it worked. And not only that, but now enter seems to choose yes by default again.

        Isn't this something like a very devious bug? I mean there was no way on earth I'd guess that this was the problem. Thanks guys!

        Comment

        Working...
        X