Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#960329: lightdm: Error getting user list from org.freedesktop.Accounts

2,687 views
Skip to first unread message

Allan Wind

unread,
May 11, 2020, 4:10:03 PM5/11/20
to
Package: lightdm
Version: 1.26.0-4
Severity: minor

Dear Maintainer,

accountsservice was using a lot of CPU on my system from time to
time, so I purged it. lightdm does not depend on accountsservice
(like gdm3), but report errors if the package is not installed:

2020-05-11T19:01:03.247+00:00 vent lightdm[639]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
2020-05-11T19:01:06.338+00:00 vent lightdm[746]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
2020-05-11T19:01:11.217+00:00 vent lightdm[1069]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files

I don't see anything in the lightdm configuration files that tells
me how to disable the use of accountsservice to placate the error. There
probably should be. I don't have a use for .dmrc (re #690898) but
presumably that would be a work-around.


/Allan

-- System Information:
Debian Release: 10.4
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lightdm depends on:
ii adduser 3.118
ii dbus 1.12.16-1
ii debconf [debconf-2.0] 1.5.71
ii libaudit1 1:2.8.4-3
ii libc6 2.28-10
ii libgcrypt20 1.8.4-5
ii libglib2.0-0 2.58.3-2+deb10u2
ii libpam-systemd [logind] 241-7~deb10u4
ii libpam0g 1.3.1-5
ii libxcb1 1.13.1-2
ii libxdmcp6 1:1.1.2-3
ii lightdm-gtk-greeter [lightdm-greeter] 2.0.6-1
ii lsb-base 10.2019051400

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

Versions of packages lightdm suggests:
pn accountsservice <none>
ii upower 0.99.10-1
pn xserver-xephyr <none>

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

--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Ryutaroh Matsumoto

unread,
Mar 29, 2021, 11:10:03 PM3/29/21
to
Package: lightdm
Version: 1.26.0-7
Followup-For: Bug #960329
Control: tags -1 + bullseye sid
Control: severity -1 grave

Dear Maintainer,

After insatlling lightdm by
apt-get --install-recommends install task-xfce-desktop/sid task-desktop/sid,
the bug #960329 still persists.

Installing the package accountsservice, and systemctl restart lightdm
does not fix this symptom.

Because of this bug, lightdm keeps failing to start,
and I can make no interaction with keyboard and display
(ssh is OK), so I increase the severity to grave.
The system is Debian bullseye arm64 running on the Raspberry Pi 4B.
All packages are pure Debian.

I hope this issue is fixed before the official Bullseye release.

Best regards, Ryutaroh Matsumoto

-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 5.10.0-5-rt-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), 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 adduser 3.118
ii dbus 1.12.20-2
ii debconf [debconf-2.0] 1.5.75
ii libaudit1 1:3.0-2
ii libc6 2.31-10
ii libgcrypt20 1.8.7-3
ii libglib2.0-0 2.66.7-2
ii libpam-systemd [logind] 247.3-3
ii libpam0g 1.4.0-7
ii libxcb1 1.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 <none>

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

Ryutaroh Matsumoto

unread,
Mar 29, 2021, 11:20:04 PM3/29/21
to
Control: severity -1 normal

I now think that failure of the startup of lightdm is
caused by something other than lightdm.
I keep investigating and lower the severity
until I get a clear picture of the symptom.

Best regards, Ryutaroh

Ryutaroh Matsumoto

unread,
Mar 30, 2021, 12:10:03 AM3/30/21
to
Control: severity -1 minor

Startup failure of lightdm was caused by
GDM_BACKEND=wayland environment variable...

Installing accountsservice removes the error message
reported in #960329.
accountsservice is suggested by lightdm.
Upgrading "suggest" to "recommend" might be a good idea...

Sorry for disturbing... Ryutaroh
0 new messages