Bug#992592: lightdm fails to start after update to bullseye (missing '/var/lib/lightdm/data')

2022-12-06 Thread наб
Hi!

A friend just hit this on a fresh lightdm install on current sid;
she did apt install lightdm; dpkg-reconfigure lightdm,
and on restart she kept getting
  Could not enumerate user data directory /var/lib/lightdm/data: Error opening 
directory '/var/lib/lightdm/data': No such file or directory
from lightdm in the journal.

Inexplicably, repeating the steps from the postinst:
  mkdir -p /var/lib/lightdm
  chown lightdm:lightdm /var/lib/lightdm
  chmod 0750 /var/lib/lightdm
/and then/
  sudo -u lightdm mkdir /var/lib/lightdm/data
made lightdm go on until an unrelated X.org error killed it.

Adding just the latter to the presumably-run-by-the-postinst
bit may've worked as well, but we were hardly in a clinical
environment.

Best,
наб


signature.asc
Description: PGP signature


Bug#992592: lightdm fails to start after update to bullseye (missing '/var/lib/lightdm/data')

2022-10-16 Thread karsten

Am 15.10.22 um 19:21 schrieb Christoph Biedl:

# ... without rendering it completely unusable to everyone
severity 992592 important
tags 992592 moreinfo unreproducible
user debian-rele...@lists.debian.org
usertags 992592 + bsp-2022-10-de-karlsruhe
thank you

Pavel Sanda wrote...

Looking into that issue, I failed to reproduce it. So I started with
stretch and did both dist-upgrades up to bullseye, and still lightdm
starts up as expected.


That's interesting.


This is strange since in postinst, /var/lib/lightdm/ is created if
missing, and permissions are set as needed by lightdm. I'd expect
breakage only in conditions you would have noticed anyway - like
unfinished installation, or full disk.

In case you still have the files around (or still can reproduce the
problem), the content of /var/log/lightdm/ should contain more bits
what's going wrong. Out of curiosity, did you purge packages no longer
needed after the upgrade (as listed by deborphan)?


The problem occured on an PC that is running as a server.

I would say when this is not reproducible then simply close the bug.
When I encounter such a problem again I can reopen the bug.

Best regards and thank you
karsten



Bug#992592: lightdm fails to start after update to bullseye (missing '/var/lib/lightdm/data')

2022-10-15 Thread Christoph Biedl
# ... without rendering it completely unusable to everyone
severity 992592 important
tags 992592 moreinfo unreproducible
user debian-rele...@lists.debian.org
usertags 992592 + bsp-2022-10-de-karlsruhe
thank you

Pavel Sanda wrote...

> updating debian to bullseye killed access to my desktop environment.
> It was actually stretch->buster and then (after appropriate reboots etc.)
> buster->bullseye, so not sure which of two steps broke it.

Looking into that issue, I failed to reproduce it. So I started with
stretch and did both dist-upgrades up to bullseye, and still lightdm
starts up as expected.

> lightdm used to be default DM and was not working anymore after the update.
> Checking logs with
> lightdm --test-mode --debug
> showed critical line about missing /var/lib/lightdm/data like in bugs
> #947319 and #931335.

This is strange since in postinst, /var/lib/lightdm/ is created if
missing, and permissions are set as needed by lightdm. I'd expect
breakage only in conditions you would have noticed anyway - like
unfinished installation, or full disk.

In case you still have the files around (or still can reproduce the
problem), the content of /var/log/lightdm/ should contain more bits
what's going wrong. Out of curiosity, did you purge packages no longer
needed after the upgrade (as listed by deborphan)?

Christoph (not the lightdm maintainer, just trying to help here)



signature.asc
Description: PGP signature


Bug#992592: lightdm fails to start after update to bullseye (missing '/var/lib/lightdm/data')

2021-08-20 Thread Pavel Sanda
Package: lightdm
Version: 1.26.0-7
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: sa...@lyx.org

Dear Maintainer,

updating debian to bullseye killed access to my desktop environment.
It was actually stretch->buster and then (after appropriate reboots etc.)
buster->bullseye, so not sure which of two steps broke it.

lightdm used to be default DM and was not working anymore after the update.
Checking logs with
lightdm --test-mode --debug
showed critical line about missing /var/lib/lightdm/data like in bugs
#947319 and #931335.

apt-get purge lightdm
apt-get install lightdm

fixed the situation (purge was clearly doing bunch of stuff in /etc/
which should be probably part of distro-update procedures(?).


-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Locale: LANG=C, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lightdm depends on:
ii  adduser3.118
ii  dbus   1.12.20-2
ii  debconf [debconf-2.0]  1.5.77
ii  libaudit1  1:3.0-2
ii  libc6  2.31-13
ii  libgcrypt201.8.7-6
ii  libglib2.0-0   2.66.8-1
ii  libpam-systemd [logind]247.3-6
ii  libpam0g   1.4.0-9
ii  libxcb11.14-3
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.8-2
ii  lsb-base   11.1.0

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+22

Versions of packages lightdm suggests:
ii  accountsservice  0.6.55-3
ii  upower   0.99.11-2
pn  xserver-xephyr   

-- debconf information:
* shared/default-x-display-manager: lightdm
  lightdm/daemon_name: /usr/sbin/lightdm