desktop-packages team mailing list archive

[Bill Danielson <887316@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

While I was trying out different display managers, I removed, then
removed completely and then later reinstalled lightdm.    This ended up
changing the user id of lightdm.   However, the dot files in
/var/lib/lightdm were still owned by the old, now invalid user id and so
lightdm could not read them.   lightdm now did not start because it
couldn't open  its .Xauthority file.   I fixed this by removing all the
dot files in the /var/lib/lightdm directory and then letting lightdm
recreate them.   It looks like the "remove completely" option should
remove the dot files in /var/lib/lightdm so they will be recreated with
the correct userid if lightdm is reinstalled at a later date.

** Affects: lightdm (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/887316

Title:
  /var/lib/lightdm files owned by invalid user after reinstall

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  While I was trying out different display managers, I removed, then
  removed completely and then later reinstalled lightdm.    This ended
  up changing the user id of lightdm.   However, the dot files in
  /var/lib/lightdm were still owned by the old, now invalid user id and
  so lightdm could not read them.   lightdm now did not start because it
  couldn't open  its .Xauthority file.   I fixed this by removing all
  the dot files in the /var/lib/lightdm directory and then letting
  lightdm recreate them.   It looks like the "remove completely" option
  should remove the dot files in /var/lib/lightdm so they will be
  recreated with the correct userid if lightdm is reinstalled at a later
  date.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/887316/+subscriptions