unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: L  p R n  d n    <guix@lprndn.info>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41207@debbugs.gnu.org
Subject: bug#41207: accountsservice daemon lacks dbus interfaces
Date: Tue, 02 Jun 2020 16:46:28 +0200	[thread overview]
Message-ID: <87wo4ppltn.fsf@lprndn.info> (raw)
In-Reply-To: <87367frcgi.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 01 Jun 2020 00:01:17 +0200")

Hello,

Ludovic Courtès <ludo@gnu.org> writes:

> Hello,
>
> L  p R n  d n    <guix@lprndn.info> skribis:
>
>> The accountsservice service hasn't access to dbus' interfaces throwing
>> an error when they're needed.The problem, at least, appears with LightDM.
>> The error looks like:
>>
>> WARNING: Error updating user /org/freedesktop/Accounts/User1000:
>> GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface
>> "org.freedesktop.DisplayManager.AccountsService"
>
> Apparently this error message comes from lightdm, so the issue is that
> lightdm doesn’t find the ‘org.freedesktop.Accounts.service’, right?

Not exactly, my understanding is that *accountsservice* doesn't find
'org.freedesktop.Accounts.service' which is provided (and asked) by
lightdm. (I think the error comes from accountsservice)

> How is lightdm started?  I wonder if there’s something to be done in the
> service definition instead.
>
> Thanks,
> Ludo’.

Have a nice day,

L  p R n  d n




  reply	other threads:[~2020-06-02 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 12:04 bug#41207: accountsservice daemon lacks dbus interfaces L p R n d n
2020-05-31 22:01 ` Ludovic Courtès
2020-06-02 14:46   ` L p R n d n [this message]
2020-06-03  9:39     ` Ludovic Courtès
2020-06-03 12:37       ` L p R n d n
2020-06-11 10:27         ` Ludovic Courtès
2023-07-30 13:21           ` Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wo4ppltn.fsf@lprndn.info \
    --to=guix@lprndn.info \
    --cc=41207@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).