I agree that, for this bug, nothing needs to be done. Thunar is behaving
properly, provided that xfce is started correctly (that is, in a manner
which sets up consolekit and policykit to behave properly). Thunar was
just the unlucky program which triggered my investigation into
startx/startxfce4/consolekit/policykit.
On 04/28/09 14:44, Yves-Alexis Perez wrote:
Ok, so, in the end, for this issue.
Like xfce4-session, I don't think, in the end, we should Recommends:
libpam-ck-connector.
The rationale is that Thunar already Recommends: hal (and that may
switch to a Depends soon), which Depends on consolekit, which Recommends
libpam-ck-connector anyway.
As per the summary on xfce4-utils bug, if we properly document the
various ways to start Xfce, we shouldn't have any problem anymore.
What do you think (just for stuff related to this bug)?
Cheers,
--
Scott Barker [email protected]
Linux Consultant http://www.mostlylinux.ca/scott
_______________________________________________
Pkg-xfce-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-xfce-devel
