Hello,
I've just stumbled over this report and have to say that the proposed section
in the release notes is suboptimal. This is mainly due because it is unclear
which workaround is actually being referred to in the linked bug reports.
I would prefer it if the actual changes that are needed are documented in the
release notes which would (for startx users) lead to something like:
--- snip ---
Users of display managers other than kdm, gdm and lightdm (e.g. the xdm and
slim display managers) as well as users who start their X session by manually
calling startx from a virtual console will likely be hit by problems with
system services like automounting devices and autoconfiguring network
interfaces.
Due to changes in consolekit, display managers need to update their consolekit
interaction. The displaymanagers kdm, gdm and lightdm in wheezy have been
updated. Others (xdm, slim, a.o.) have not yet been updated. If you're using
a not-yet updated display manager, either switch to an updated one before
starting to upgrade your system, or make sure to apply the following changes
to your configuration (as applicable):
startx
------
Please make sure that the `consolekit` and `dbus-x11` packages are installed
and that both `ck-launch-session` and `dbus-launch` are called in all
$HOME/.xsession files as in:
exec ck-launch-session dbus-launch $WM
That means that if, for example, a user started the awesome window manager
with:
exec awesome
it should be ensured to change this line to:
exec ck-launch-session dbus-launch awesome
to ensure that the aforementioned system services work correctly.
slim
----
...
xdm
---
...
--- snip ---
I know that the actual text needs to be amended and polished, but I simply
wanted to point out that actual instructions in the release notes are much
more helpful than just references to (long!) bug reports.
Have a wonderful day!
--
Wolodja <debian@babilen5.org>
4096R/CAF14EFC
081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC
Attachment:
signature.asc
Description: Digital signature