*** This bug is a duplicate of bug 459376 ***
    https://bugs.launchpad.net/bugs/459376

This is not a bug with auth because upstart will not load gdm,  so level
is same, as per sudo init.d command is controlled by upstart, so this is
either a bug against the commands coming off the friendly-recovery
(which might be if they were assuming instruction as per
https://wiki.ubuntu.com/RecoveryMode)

But that bug (friendly-
recovery)https://bugs.edge.launchpad.net/ubuntu/+source/friendly-
recovery/+bug/459376 is said to be caused by caused by

script
...
    # Check kernel command-line for inhibitors
    for ARG in $(cat /proc/cmdline)
    do
        case "${ARG}" in
            text|-s|s|S|single)
                exit 0
                ;;
        esac
    done
...
end script

or

APT::Update::Post-Invoke-Success:: "[ ! -f
/var/run/dbus/system_bus_socket ] || /usr/bin/dbus-send --system
--dest=org.freedesktop.PackageKit --type=method_call
/org/freedesktop/PackageKit org.freedesktop.PackageKit.StateHasChanged
string:'cache-update'";

in which reported previously in bug
https://bugs.edge.launchpad.net/ubuntu/+source/gdm/+bug/436936 describes
the same bug in source

    # Check kernel command-line for inhibitors
    for ARG in $(cat /proc/cmdline)
    do

        case "${ARG}" in
            text|-s|s|S|single)
                exit 0
                ;;
        esac
    done

because when you load recovery the upstart will not release as per line
and gdm will not auth because previous state no load

menu(friendly recovery), upstart gdm command or upstart seem to be where
the issue is. because the gdm-auth would just be part of the loaded
level.

what the command is startx        /etc/int.d is controlled by upstart it
will not take

And about my writing style versus yours please do not correct me any more. I 
have a different writing style.
I don't know I may eat something different also. Who really cares as long as 
the point can get across.  

I am sorry if this seems like a public lashing , I am just trying to get a 
point across regarding the matter at hand.
Ubuntu bug report 
https://bugs.edge.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/476781

** Attachment added: "Screenshot.png"
   http://launchpadlibrarian.net/35340196/Screenshot.png

-- 
User can't authenticate via PolicyKit after using 'resume normal boot'  
friendly-recovery mode option
https://bugs.launchpad.net/bugs/476781
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to