[Bug 411533] Re: users and groups prog blocked on first launch

** Changed in: gnome-system-tools (Ubuntu) Status: New => Confirmed -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubunt

[Bug 411533] Re: users and groups prog blocked on first launch

** Changed in: gnome-system-tools (Ubuntu) Status: New => Confirmed -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubunt

[Bug 411533] Re: users and groups prog blocked on first launch

** Changed in: gnome-system-tools (Ubuntu) Status: New => Confirmed -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubunt

[Bug 411533] Re: users and groups prog blocked on first launch

** Changed in: gnome-system-tools (Ubuntu) Status: New => Confirmed -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubunt

[Bug 411533] Re: users and groups prog blocked on first launch

** Changed in: gnome-system-tools (Ubuntu) Status: New => Confirmed -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubunt

[Bug 411533] Re: users and groups prog blocked on first launch

** Changed in: gnome-system-tools (Ubuntu) Status: New => Confirmed -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubunt

[Bug 411533] Re: users and groups prog blocked on first launch

Does this happen with a more recent version of Karmic? The authentication system has been updated. Thanks! ** Changed in: gnome-system-tools (Ubuntu) Status: Confirmed => Incomplete -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533 You received this b

[Bug 411533] Re: users and groups prog blocked on first launch

Still happening here, yes, but the error dialog box has changed from: "The configuration could not be loaded You are not allowed to access the system configuration" to: "The configuration could not be loaded An unknown error occurred" Other than that, it is the same symptom. Users & Groups runs a

[Bug 411533] Re: users and groups prog blocked on first launch

Hey, glad my recent fixes helped making things clearer... :-p So the explanation to that change is that we now make the distinction between error types, and no longer consider there's an "access denied' issue. This is useful to get more information about your problem, which has visibly nothing to

[Bug 411533] Re: users and groups prog blocked on first launch

Thanks for getting on this. Looks like system-tools-backends is not started by default and should be. Everything works as expected when following the instructions above: m...@galvatron:~$ sudo killall system-tools-backends [sudo] password for marc: system-tools-backends: no process found m...@gal

[Bug 411533] Re: users and groups prog blocked on first launch

Well, the backends should not be started on boot, since they should start automatically when needed. Could you attach here your /var/log/syslog, /var/log/auth.log and /var/log/messages after having tried to run the users config tool (without starting it manually as in the previous post)? Also, the

[Bug 411533] Re: users and groups prog blocked on first launch

I'm sorry to say that absolutely nothing is logged in syslog, auth.log, message, kern.log, debug, daemon.log or user.log. It appears to fail silently (other than the dialog telling me it failed!). Also output when run from the terminal is identical to a successful run, so nothing to gather there:

[Bug 411533] Re: users and groups prog blocked on first launch

You could try the following procedure, which will help but won't really tell us what's the root problem: - run users-admin for the first time - type 'ps ax | grep -i backends' - reproduce the procedure once again This way we would know if the tools are started the first time, possibly with a dela

[Bug 411533] Re: users and groups prog blocked on first launch

>do you experience the same problem with time-admin and services-admin? Yes I do, for time-admin, services-admin, and of course users-admin system-tools-backends is indeed started prior to this error m...@galvatron:~$ ps ax | grep -i backends 3587 ?Ss 0:00 /usr/sbin/system-tools-bac

[Bug 411533] Re: users and groups prog blocked on first launch

The one difference I spot with system-tools-backends is with the process state code. Prior to first attempt, (fresh boot) it is S+ (Interruptible sleep, is in the foreground process group). Subsequently, it is Ss (Interruptible sleep, is a session leader). I am not savvy enough to determine if t

[Bug 411533] Re: users and groups prog blocked on first launch

I guess you meant "prior to second attempt". On fresh boot, before starting users-admin, the stb should not be running (as on your screenshot). A standard way to get information would be to use gdb. Can you try "pidof system-tools-backends; gdb attach " and then "thread apply all bt"? I guess y

[Bug 411533] Re: users and groups prog blocked on first launch

Nope, I meant prior to first attempt. The screenshot is taken upon fresh boot. I can replicate it every time by booting, starting gnome-terminal, then ps ax | grep -i backends always returns what was shown in the screenshot. I'll give the debug symbols a whirl tomorrow. -- users and groups prog

[Bug 411533] Re: users and groups prog blocked on first launch

What the screenshot shows is actually that the backends are not running. The only line returned is about the command 'grep -i backends' showing itself (stupid, I know). So the line that shows us that the backends are running is: 3587 ? Ss 0:00 /usr/sbin/system-tools-backends (which may/should be

[Bug 411533] Re: users and groups prog blocked on first launch

Doh! Of course that's the case. Silly of me. I think I am just hoping for something to be obviously wrong. Sorry 'bout that. -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533 You received this bug notification because you are a member of Ubuntu Desktop Bugs,

[Bug 411533] Re: users and groups prog blocked on first launch

No-go so far with debug symbols. Running into this: $ sudo gdebi libc6*.deb Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done Analysing dependencies: 00 /usr/lib/python2.6/dist-packages/GDebi/DebPackage.py:273: Deprecation

[Bug 411533] Re: users and groups prog blocked on first launch

Okay, installed the latest from the repository: $ apt-cache policy libc6-dbgsym libc6-dbgsym: Installed: 2.10.1-0ubuntu8 Candidate: 2.10.1-0ubuntu8 Version table: *** 2.10.1-0ubuntu8 0 500 http://ddebs.ubuntu.com karmic/main Packages 500 http://ddebs.ubuntu.com karmic/main P

[Bug 411533] Re: users and groups prog blocked on first launch

Much thanks for achieving that painful task. Comparing with normal behavior of the backends, it seems that everything is working fine, i.e. it's waiting for calls from D-Bus - which is quite sad for solving this bug... :-p So it could be more of a D-Bus issue. Could you run 'sudo dbus-monitor --sy

[Bug 411533] Re: users and groups prog blocked on first launch

Another question: do you see an important delay when starting users- admin for the first time? It could be that the timeout is reached for some reason, while subsequent calls go faster. If these don't help, we can still go into the gst/liboobs code to get the D-Bus returned error codes more precis

[Bug 411533] Re: users and groups prog blocked on first launch

I don't see any abnormal delay. When it fails, it fails much more quickly than the time it takes to launch successfully. I've attached the dbus information. Not much to glean there, it seems. Also, got nothing from polkitd for either a failed or successful run: $ sudo /usr/lib/policykit/polkitd (

[Bug 411533] Re: users and groups prog blocked on first launch

Sorry, the path to the PolicyKit1 daemon seems to be /usr/lib/policykit-1/polkitd in Karmic (and not /usr/lib/policykit-1/polkitd as in my custom install). You were starting the daemon version 0.9, which did not get any calls (as it should). The D-Bus logs don't show much, but at least we can chec

[Bug 411533] Re: users and groups prog blocked on first launch

hmm... something not quite right with this. $ gdb users-admin GNU gdb (GDB) 6.8.50.20090628-cvs-debian Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it.

[Bug 411533] Re: users and groups prog blocked on first launch

Oh, I forgot to say you need to type 'run' after setting the breakpoint, so that the program is started. It may still not work, but without it we're sure we'll get nothing... (And the break point is in "oobs-session.c", not just "oobs-session".) -- users and groups prog blocked on first launch h

[Bug 411533] Re: users and groups prog blocked on first launch

Right. I've become a little more familiar with backtraces and such due to other issues. Log attached. ** Attachment added: "gdb-users-admin.log" http://launchpadlibrarian.net/31247410/gdb-users-admin.log -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533

[Bug 411533] Re: users and groups prog blocked on first launch

Good catch! Thanks for going until that point in debugging. This extract from the log explains that's going on: "Launch helper exited with unknown return code 0" So the problem is on D-Bus side, it seems that the program responsible for starting the Platform backend exited without returning an er

[Bug 411533] Re: users and groups prog blocked on first launch

It occurred to me just now: is there anything interesting in /var/log/daemon.log that isn't in the other journals? I've just found bug 231180 about users-admin reporting the very same error, but with different symptoms. And even more interestingly, bug 332050 is about a problem with bzr-gtk failin

[Bug 411533] Re: users and groups prog blocked on first launch

Okay, apparently this problem could come from the fact that the backends daemonize when activated from D-Bus. The problem is, I don't think the modules actually daemonize. Could you try to change in /usr/share/dbus-1/system-services/org.freedesktop.SystemToolsBackends.service the line Exec=/opt/

[Bug 411533] Re: users and groups prog blocked on first launch

> Exec=/opt/gnome/sbin/system-tools-backends -n Following this change, I am unable to replicate the issue! I have power cycled and booted 7 consecutive times followed by launching users-admin on 5 occasions and time-admin and services-admin once each. Previously, I could replicate this 100% of the

[Bug 411533] Re: users and groups prog blocked on first launch

** Changed in: gnome-system-tools (Ubuntu) Status: Incomplete => Confirmed -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools i

[Bug 411533] Re: users and groups prog blocked on first launch

Cool! This problem must have appeared in Karmic, since in previous releases the backends were started at boot time before they were actually needed (which is wrong BTW). But I really don't see how it could affect some users and not all of them. And still I don't have seen other reports about that.

[Bug 411533] Re: users and groups prog blocked on first launch

Yes, this bug does indeed affect Karmic Alpha 5. I'm really surprised now that this bug report is so low-key. STR: 1) Boot karmic alpha 5 live CD 2) Launch System > Administration > Users and Groups Fails with same error dialog reported here earlier: "The configuration could not be loaded An un

[Bug 411533] Re: users and groups prog blocked on first launch

Comment #26 fixed it for me :) Thanks Milan -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533 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 l

[Bug 411533] Re: users and groups prog blocked on first launch

#26 worked for me also -- users and groups prog blocked on first launch https://bugs.launchpad.net/bugs/411533 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

Re: [Bug 411533] Re: users and groups prog blocked on first launch

Nope, I meant prior to first attempt. The screenshot is taken upon fresh boot. I can replicate it every time by booting, starting gnome-terminal, then ps ax | grep -i backends always returns what was shown in the screenshot. I'll give the debug symbols a shot tomorrow. On Sun, Aug 30, 2009 at 4: