User can't authenticate via PolicyKit after using 'resume normal boot' friendly-recovery mode option

[Daniel Stone]

Binary package hint: gnome-system-tools

noticed additional lines added to dmesg

[ 15.629592] type=1505 audit(1257530806.004:12): operation="profile_replace" pid=1004 name=/usr/share/gdm/guest-session/Xsession
[ 15.631075] type=1505 audit(1257530806.004:13): operation="profile_replace" pid=1005 name=/sbin/dhclient3
[ 15.631679] type=1505 audit(1257530806.014:14): operation="profile_replace" pid=1005 name=/usr/lib/NetworkManager/nm-dhcp-client.action
[ 15.632014] type=1505 audit(1257530806.014:15): operation="profile_replace" pid=1005 name=/usr/lib/connman/scripts/dhclient-script
[ 15.634948] type=1505 audit(1257530806.014:16): operation="profile_replace" pid=1006 name=/usr/bin/evince
[ 15.644640] type=1505 audit(1257530806.024:17): operation="profile_replace" pid=1006 name=/usr/bin/evince-previewer
[ 15.650276] type=1505 audit(1257530806.024:18): operation="profile_replace" pid=1006 name=/usr/bin/evince-thumbnailer
[ 15.657936] type=1505 audit(1257530806.034:19): operation="profile_replace" pid=1008 name=/usr/lib/cups/backend/cups-pdf
[ 15.658647] type=1505 audit(1257530806.034:20): operation="profile_replace" pid=1008 name=/usr/sbin/cupsd
[ 15.660704] type=1505 audit(1257530806.034:21): operation="profile_replace" pid=1009 name=/usr/sbin/tcpdump

ProblemType: Bug
Architecture: amd64
CheckboxSubmission: c696394865573b188a4fba4b5a7760f2
CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
Date: Fri Nov 6 12:34:28 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/users-admin
NonfreeKernelModules: nvidia
Package: gnome-system-tools 2.28.1-0ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: gnome-system-tools
Uname: Linux 2.6.31-14-generic x86_64

[Milan Bouchet-Valat (nalimilan)]

Well, you're not supposed to start a graphical session from recovery mode. It's meant to be used to reset an administrator password or to fix something badly broken, and because of that it won't load most of the components required for GNOME to work. If you want to change your password, use the commandline: passwd [USERNAME] will do the trick.

See https://wiki.ubuntu.com/RecoveryMode for more informations.

[Daniel Stone (danielstone)]

actually if i go into terminal I can use sudo su
then gdm restart
it gives the menu available even though in maintenance mode so this not invalid
even though it is maintenance mode and this is a serious difference between previous builds
I can add users/groups in the mentioned menu
I believ that in previous builds it had xtart and gdm start differently and it is a hard workaround
but in previous builds the grub recovery mode and the choice boot normally would boot the system normally but the maintenance menu was accessed through the command line w/ or w/o networking options this build acts differently
also the ~beta grub~ needs to have updated message so as to not print ~beta~ if the release is complete
I have the dvd build 9-27 64 and have updates and upgrades

[Daniel Stone (danielstone)]

actually this link https://wiki.ubuntu.com/RecoveryMode does reflect the action that happen if you choose esc at grub load and choose whichever kernel(recovery mode)
What happens is it bring a menu that gives several maintenance options
boot normally>
repair packages>
two maintenance modes one with networking and one without
and a file system checker or something like that
the option to boot normally has always loaded the system normally as it says
and command line options would act as a maintenance mode
When the LiveCD is put in and recover a broken system that may be the normal action but not from the menu described

[Milan Bouchet-Valat (nalimilan)]

The fact that you can do so does not imply that it's a valid use case at all. I guess you'd have to use a command like 'telinit 2' to use a graphical session after booting in recovery mode. Read about runlevels in Unix and Upstart in Ubuntu to understand those issues more deeply.

Do you have a strong reason to do what you're asking for? I can't understand what you're trying to explain about previous builds - it is possible that previous versions did not behave exactly the same way, but that doesn't make the present situation wrong. I don't see what is the maintenance menu that you're talking about, not what command line and network have to do with it.

By the way, I GRUB2 is a beta release in Karmic, which is why it shows that message. This could be fixed, but please open another report against the package grub-pc.

And, please, use sentences - capitals and periods are here so that your problems can get across. If you want us to care about your problem, you should at least take the time to explain clearly the bug. If you can't afford this minimal effort, I won't spend my free time on it either.

[Daniel Stone (danielstone)]

I am greatly apologetic for my wording and lack of proper punctuation and sorry that I do not write to your standard. I know sometimes the way an issue is presented by an individual can make it harder to understand.
I have recorded video of what is happening and I have posted this on youtube.com so it may be viewed by anyone. The video may be found at this link.
http://www.youtube.com/watch?v=7_6FeYX5gWY

[Daniel Stone (danielstone)]

This may be caused from something else related to
https://bugs.edge.launchpad.net/ubuntu/+source/friendly-recovery/+bug/459376
which sounds similar or
https://bugs.edge.launchpad.net/ubuntu/+source/gdm/+bug/436936
but either way it is a bug that exists because machine command prompt should load OS with proper commands.

[Milan Bouchet-Valat (nalimilan)]

OK, this is clearer now. So bug 459376 explains that GDM is not started as it should, which forces you to run startx manually. But what do you mean with : "gnome user admin not working"? Are you saying that the users-admin program from System->Administration->Users and Groups does not work? Or is your problem exactly the same as bug 459376? Had you explained this precisely in the body of the report instead of doing this in the title, I wouldn't have had to ask you this.

[Daniel Stone (danielstone)]

The title explains how to reproduce the same results. I guess I should have written the title
gnome user-admin not working when using from grub recovery mode boot normal login and command startx

Steps to reproduce
start computer
press escape when grub is loading
choose any of the (recocvery mode) choices
when recovery menu comes up choose "Boot Normally"
machine login will appear
key in username press enter
key in password press enter
key in sudo /etc/init.d/gdm start
Desktop Loads
In Menu System> Administration open Users and Groups (unlock not available)

workaround
from the previous steps
Desktop Loads
Open terminal
gdm restart
or sudo /etc/init.d/gdm restart
Desktop Loads
In Menu System> Administration open Users and Groups (unlock available)

You act very unprofessional in your replies https://edge.launchpad.net/~nalimilan. I do not understand why.

[Milan Bouchet-Valat (nalimilan)]

I'm not "acting unprofessional"; how do you want us to work professionally if you don't start doing so yourself?! A bug title is not here to completely explain a bug, but to make it easy to find. Detailed explanation, in correct English (at least to the extent your mastering of English allows you to express yourself), should then go into the body of the report. I was only asking you to provide form the beginning the details you've just provided now. I didn't mean to be rude, but please understand that working on Ubuntu on my free time, I'd like a little more attention from people I'm trying to help. Some would have closed the report without even explaining why, or let it rot for ages. See https://help.ubuntu.com/community/ReportingBugs#Writing%20a%20useful%20report about more general rules.

Now that we have spent so much words into this debate, here's what we can do to actually debug. What does 'ps ax | grep dbus' reports when you have started GDM for the first time? What about 'ps ax | grep polkit'? What's the output of 'sudo killall polkitd; sudo /usr/lib/policykit-1/polkitd'?

[Daniel Stone (danielstone)]

~And yet again I get a lecture~

I have reported this bug and acted cordially during our conversation.

The method you use to use to converse probably discourages users from reporting bugs
as it sounds more like reprimand than conversation.

The method you give as diagnostic would not prove nor diagnose this bug.

as stated before this looks similar to Bug #459376 and I will mark as a dupe of that bug

[Milan Bouchet-Valat (nalimilan)]

Think what you want about my "lectures", but don't tell me my debugging instructions are useless. If you know better than I what's the problem, please tell me, that will be quicker. Bug 459376 does not seem to be a complete duplicate to me, though I may be wrong. Once GDM has been started manually, D-Bus and PolicyKit should work too, else that's a separate issue.

The commands I gave you should have helped determining that. How do you know they don't? Posting their outputs here is cheap, and may help detecting something wrong.

BTW, please note that I wouldn't have bothered you again, hadn't you stated that I was "acting unprofessional" without any clear reason. My only concern is that in the future you are better aware of what Ubuntu people expect of a bug report in terms of information. Have a look again at your comment #3, you'll understand that it makes very hard for us to catch your problem.

[Daniel Stone (danielstone)]

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

[Milan Bouchet-Valat (nalimilan)]

The point doesn't get across, that's the whole thing. Good luck...