Ubuntu
consolekit package

Screensaver does not start

Bug #274926 reported by Khashayar Naderehvandi on 2008-09-26

Affects		Status	Importance	Assigned to	Milestone
	consolekit (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

For some reason gnome-screensaver doesn't start. The screen starts fading out but then immediately returns me to the desktop. This is true when the screensaver should be activated automatically, as well as when I manually run gnome-screensaver-command -a.

I have attached the output of gnome-screensaver --no-daemon --debug.

EDIT: Forgot to mention, this is on intrepid ibex.

See original description

Revision history for this message

Khashayar Naderehvandi (khashayar) wrote on 2008-09-26:

gnome-screensaver-output Edit (9.7 KiB, text/plain)

description:

updated

Revision history for this message

Chris Coulson (chrisccoulson) wrote on 2008-09-26:

Thank you for taking the time to report this bug and help make Ubuntu better. This looks like a D-BUS policy issue with ConsoleKit, so I'm reassigning it. Could you please attach your /etc/dbus-1/system.d/ConsoleKit.conf file to this bug report?

Thanks

Changed in gnome-screensaver:
status:	New → Incomplete

Revision history for this message

Khashayar Naderehvandi (khashayar) wrote on 2008-09-26:

ConsoleKit.conf Edit (4.3 KiB, text/html)

Thanks for reassigning. Here's the attachment:

Revision history for this message

Chris Coulson (chrisccoulson) wrote on 2008-09-26:

Thanks for the information. As suspected, the D-BUS policy is blocking the SetIdleHint method.

Changed in consolekit:
importance:	Undecided → Medium
status:	Incomplete → Triaged

Revision history for this message

James Westby (james-w) wrote on 2008-09-26:

consolekit_0.2.10-1ubuntu6.diff Edit (1.8 KiB, text/plain)

Hi,

Here is a proposed patch to allow access to the SetIdleHint method by default,
as is now done upstream.

Thanks,

James

Revision history for this message

Khashayar Naderehvandi (khashayar) wrote on 2008-09-28:

Thanks for the patch. I rebuilt consolekit with the patch applied, but I still seem to have the same problem. Awkwardly, though, the problem doesn't seem to surface regularly as I'm sure I saw the screensaver active at least at one point (just by chance, that is). Now, however, running "gnome-screensaver-command -a" exhibits the same behavior as before. Should I attach a new output of gnome-screensaver --debug --no-daemon?

Revision history for this message

Chris Coulson (chrisccoulson) wrote on 2008-09-28:

Khashayar - it would be good for you to collect the output of `gnome-screensaver --no-daemon --debug` again with this change to the D-Bus policy.

Thanks

Revision history for this message

Khashayar Naderehvandi (khashayar) wrote on 2008-09-28:

output of gnome-screensaver after consolekit upadate Edit (8.1 KiB, text/plain)

The output of dpkg -l consolekit shows version 0.2.10-1ubuntu6.

I've attached the output of gnome-screensaver --no-daemon --debug.

Regards, K.

Revision history for this message

James Westby (james-w) wrote on 2008-09-29:

Hi,

There don't seem to be any problems with consolekit in the output
you provide.

Would you please file a new bug report against gnome-screensaver
with this output, as the current bug must remain against consolekit
so the first fix can be uploaded.

Thanks,

James

Revision history for this message

Sebastian Breier (tomcat42) wrote on 2008-10-04:

#10

See Bug #278112.

Revision history for this message

Khashayar Naderehvandi (khashayar) wrote on 2008-10-04:

#11

Thanks.
I've been meaning to do this, but have been too busy the last few days...

Revision history for this message

Steve Langasek (vorlon) wrote on 2008-10-08:

#12

If changing the permissions on the SetIdleHint method doesn't fix the problem, could it be that this is a red herring entirely? Is upstream confident that the permission change is a necessary and correct fix?

Revision history for this message

James Westby (james-w) wrote on 2008-10-08: Re: [Bug 274926] Re: Screensaver does not start

#13

On Wed, 2008-10-08 at 07:23 +0000, Steve Langasek wrote:
> If changing the permissions on the SetIdleHint method doesn't fix the
> problem, could it be that this is a red herring entirely? Is upstream
> confident that the permission change is a necessary and correct fix?
>

Yes, it does seem that this is a red herring for this problem. However,
upstream made the change in git after the 0.3 release, so I thought
it was worthwhile backporting.

As I can't make a convincing case for including it at this point of the
release I don't mind it being rejected.

Thanks,

James

Revision history for this message

Chris Coulson (chrisccoulson) wrote on 2008-10-12:

#14

I don't think I can make a convincing case for including it either really, other than not including it will make it a regression from Hardy, when SetIdleHint was not blocked.

Revision history for this message

Martin Pitt (pitti) wrote on 2008-10-15:

#15

I unsubscribed -sponsors, since it seems there is nothing to sponsor after all. Instead I mark this as invalid, since the real bug is discussed in bug 278812. Please shout if there is still a problem with ConsoleKit.