Bug 1483

*** Bug 1582 has been marked as a duplicate of this bug. ***

CC: (none) => herbert

Running a search on "gdmsetup unlock" shows lots of bug reports on other
distributions.  In one case the solution was to start the policykit service,
which Mageia/Mandriva do no have.

In another, https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/617044
the solution was to add a requires on the policykit package.

In Mandriva, the only bug report I found mentioning gdmsetup, was
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/617044
where the op was instructed to use "mcc/boot/Set up display manager"
to switch from kdm to gdm, and "mcc/boot/Set up autologin to automatically login"
which lets you setup auto login, select the user, and the desktop.

What are you trying to use gdmsetup to accomplish?

CC: (none) => davidwhodgins

@Dave Hodgins
"What are you trying to use gdmsetup to accomplish?" 

I want to enable autologin, and yes, I know it's work with mcc

(When a bug is marked as a duplicate of another, all comments should be in the other bug, not in the duplicate).

Bug 1582 was marked as being a duplicate of this one, so I'm not clear
why the comment was added.  There were no comments added to 1582 after it was marked as a duplicate of this one.

Adding the policykit service, and having it running by default would probably
fix gdmsetup, but as there is an easy workaround using mcc, I question if
it's worth it, since the policykit service doesn't seem to be needed for
anything else.

(In reply to comment #5)
> Bug 1582 was marked as being a duplicate of this one, so I'm not clear
> why the comment was added.  There were no comments added to 1582 after it was
> marked as a duplicate of this one.
> 

Yes, you're right; I confused the two reports.

> Adding the policykit service, and having it running by default would probably
> fix gdmsetup, but as there is an easy workaround using mcc, I question if
> it's worth it, since the policykit service doesn't seem to be needed for
> anything else.

A gnome polkit agent is started by default in GNOME, check the output of 'ps aux | grep polkit'.

*** Bug 1632 has been marked as a duplicate of this bug. ***

CC: (none) => Gchoyman

yes polkit is started: 

[manu@vosdook ~]$ ps aux | grep polkit
root       976  0.0  0.1 193168  5260 ?        Sl   02:59   0:00 /usr/lib64/polkit-1/polkitd
manu     25649  0.0  0.1 205416  6448 ?        Sl   10:12   0:00 /usr/lib64/polkit-gnome-authentication-agent-1

OK I understand 
I was able to setup auto login, using MCC

Thanks

Hardware: x86_64 => i586

*** Bug 1906 has been marked as a duplicate of this bug. ***

Sorry Dave
I was doing a new install & forgot I had already filed this bug
thanks for your hard work

This looks similar to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622234
polkitd segfaulting when the unlock button is clicked, no fix though..

I don't have M1, resetting to default assignee.

Assignee: olav => bugsquad

(In reply to comment #13)
> I don't have M1, resetting to default assignee.

So the problem isn't that you think this is not a gdm issue nor that you think you're not the gdm maintainer but that.......

....you only maintain your packages in cauldron?

CC: (none) => olav

I don't have access to M1, so difficult to say where the problem is. Comments suggest maybe buildrequirements, maybe policykit config, maybe policykit crashes. As Cauldron version is completely different than M1 (no gdmsetup), I cannot debug.

Not sure what you mean with "maintain your packages". I have provided a security upgrade. This problem requires someone to figure out what the problem is. Is not clear to me if it is a problem with the packaging or not.

Seems easier to have someone look at it who can look at it, which is why I reassigned it.

(In reply to comment #15)
> 
> Not sure what you mean with "maintain your packages". I have provided a
> security upgrade. 


Well, on this list http://pkgsubmit.mageia.org/data/maintdb.txt

I read: gdm ovitters

Sorry if I misunderstood, but I really thought the maintainers database shows who really grabbed a package with the intention to maintain it, and I never knew maintain means "maintain in cauldron only".

CC: (none) => stormi

I think this bug should be closed as won't fix.

According to section 2.2 of
http://library.gnome.org/admin/gdm/2.91/gdm.html
support for gdmsetup ended with 2.22.  Would have been better
if the program had been completely dropped, which it is in
gnome 3.

As per comment 2 and comment 9, there is a workaround using mcc
that works.

Agreed?

Yep I agree, but first I will try a patch make by Debian

(In reply to comment #16)
> Well, on this list http://pkgsubmit.mageia.org/data/maintdb.txt
> 
> I read: gdm ovitters
> 
> Sorry if I misunderstood, but I really thought the maintainers database shows
> who really grabbed a package with the intention to maintain it, and I never
> knew maintain means "maintain in cauldron only".

I intend to maintain the package (spec file). But I didn't see that as providing support for something I cannot do (I'm not a gdm developer). Further, I just have Cauldron, nothing more. This is fine for almost all packages, but gdm changed a lot. I cannot mark in the database that I only have Cauldron, but usually that doesn't matter. If I can reproduce in Cauldron, I can fix in both.

Anyway, as it seems assisting where I can is not helpful, I've set gdm maintainership to nobody.

Of course assisting where you can is helpful! This was only about confusion.

Thanks for setting the maintainership to nobody, to me that is a lot less confusing.

(In reply to comment #18)
> Yep I agree, but first I will try a patch make by Debian

@ Manuel

Did you find time to do that?

Keywords: (none) => NEEDINFO

no

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX