I see the same behavior as Manuel. In Ubuntu 10.04, utmp.ut_host is
filled in with the X display name (such as :0), but in the proposed
update utmp.ut_host is left empty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have scripts that send graphical messages to logged-in users using the
display names printed by 'w' or 'who'.
I have been using them, for more than a decade, with different Linux distros,
but they would fail with this lightdm setup. :-(
--
You received this bug notification because you are a
Hello ToZ, or anyone else affected,
Accepted lightdm into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/lightdm/1.2.1-0ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/precise-proposed/lightdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about this bug go
After applying the precise-proposed upgrade, The 'w' and 'who' commands
now show an entry upon logging into a session via lightdm.
But the 'last' command still does not show that user as logged in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm Gerry's observations with precise-proposed:
toz@xubi:~$ who
toz tty7 2012-07-19 14:34
toz@xubi:~$ w
14:35:15 up 3 min, 1 user, load average: 6.23, 4.33, 1.80
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
toz tty7 14:34
Yes, same results with last in quantal. Sorry, but didn't check last
earlier.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage
setting verification-done, while it's not perfect it's an improvement
and verification-failed would make the upload be rejected until the
whole issue is fixed, it's better to get part of it fixed and the
remaining issues sorted later rather than getting nothing
** Tags removed:
The 'last' issue is simple to fix: lp:~lotheac/lightdm/utmpx
Should I propose a merge to lp:ubuntu/precise-proposed/lightdm or
somewhere else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Sorry, that should've been lp:~lotheac/lightdm/wtmp_precise -- I'm too
tired.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage
From ToZ (toz) message:
{
toz@xubi:~$ w
14:35:15 up 3 min, 1 user, load average: 6.23, 4.33, 1.80
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
toz tty7 14:34 3:22 0.98s 0.00s /bin/sh /etc/xd
}
Display name (':0' or whatever ) is missing! It should be:
{
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
toz
** Changed in: lightdm (Ubuntu Precise)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage
@Kevin: There's been no fix for Precise on this yet, so please don't
mark it fix released yet.
** Changed in: lightdm (Ubuntu Precise)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
elfy, that looks like it's not working for you - you should see two
entries (see the bug description). I've just uploaded this to quantal
now and precise-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The package in precise-proposed works for me.
lightdm 1.2.1-0ubuntu1.1
ltirkkon tty7 2012-07-17 10:33
10:34:34 up 37 min, 1 user, load average: 0.55, 0.53, 0.49
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
ltirkkon tty7 10:33 37:24 1.13s
In Quantal - fully updated
w gives
09:15:03 up 3 min, 1 user, load average: 0.92, 0.79, 0.34
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
hob tty7 09:123:06 11.00s 0.02s /bin/sh /etc/xd
who gives
hob tty7 2012-07-17 09:12
I confirm. Quantal, fully updated:
toz@quantalU:~$ w
09:44:08 up 7 min, 2 users, load average: 1.03, 0.83, 0.41
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
toz tty7 09:426:50 11.24s 0.55s gnome-session -
toz pts/2:0
Well, I checked and it didn't seem to be working at all. I've prepped
the SRU but I'll upload the fix to Quantal next week and check it works
there first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: lightdm
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about
Working here on 12.10.
07:25:14 up 3:03, 1 user, load average: 2.31, 1.66, 1.60
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Robert: This landed a few weeks ago in Quantal, assuming this worked
fine, can you please prepare the SRUs and upload them now?
** Changed in: lightdm (Ubuntu Precise)
Status: Confirmed = Triaged
** Changed in: lightdm (Ubuntu Oneiric)
Status: Confirmed = Triaged
--
You received
** Changed in: lightdm (Ubuntu)
Status: Fix Released = Fix Committed
** Changed in: lightdm
Status: Fix Released = Fix Committed
** Description changed:
- When logged into a graphical session, I get no acknowledgement from who,
- w or last that I am logged in:
+ Impact:
+ Systems
** Changed in: lightdm
Status: Fix Committed = Fix Released
** Changed in: lightdm (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/870297
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Support for utmp has been added to lighdm 1.3.1 and will be backported
to 1.2.x when it is confirmed it works correctly.
** Changed in: lightdm
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks a lot Lauri, is there any chance you could also open a merge
request against lp:lightdm (i.e the upstream project)? I'm not sure the
upstream maintainers are watching the Ubuntu branches as regularly as
they watch the work going on the project
--
You received this bug notification because
Okay. I moved the branch based on ubuntu/precise/lightdm to
lp:~lotheac/lightdm/utmpx_precise and the one based on upstream is
lp:~lotheac/lightdm/utmpx. Upstream doesn't have debian/lightdm.pam
though (since it's packaging stuff), so that should still be merged to
the Ubuntu branch.
--
You
** Branch linked: lp:~lotheac/lightdm/utmpx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about this bug go to:
@Lauri: thanks for your work there, is there any issue left with your
patch? Is the issue that the greeter sessions are counted as logins with
it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Sebastien, yeah, that's the issue. I'm working on skipping PAM for user
sessions right now, actually, but it's probably going to be a little
ugly since I'm trying to keep the changes small.
On a side note, does lightdm have an IRC channel this could be discussed
in? I couldn't seem to find a
... sorry, that should be skipping PAM for non-user sessions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about this
@Lauri: I don't think lightdm has an IRC channel but you can find most
of people working on it on #ubuntu-desktop @ irc.ubuntu.com,
robert_ancell is usually there during .nz work hours but you should find
people online during european or american work hours as well
--
You received this bug
Ok, now that I've finally figured out how exactly lightdm works in this
regard, I've pushed my changes to lp:~lotheac/lightdm/utmpx.
At first, I was trying to check for XDG_SESSION_CLASS_USER, but it seems
that is never set. The authentication session (which talks to the
greeter) has no class,
** Branch linked: lp:~lotheac/lightdm/utmpx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about this bug go to:
i have this issue on xubuntu 12.04. lightdm version 1.2.1-0ubuntu1
i'm only half year old in linux world but in very beginning i remember being
very confused when who and w didn't produse output. didn't consider this as a
bug back then but more like un-fully-thought-about function or my lack of
Quantal is the same here. Though it might be premature to comment on
that at the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To
** Changed in: lightdm (Ubuntu Precise)
Milestone: None = ubuntu-12.04.1
** Changed in: lightdm (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Ok, but what about PAM? Greeters should run as the same user lightdm
does, so authentication is already skipped for them (do_authenticate is
false), but do pam_open_session or pam_acct_mgmt make sense? If we skip
pam_open_session for greeters, we can use pam_lastlog for actual user
sessions, but
Lauri, great work! You should move the code to the same location as
ck_open_session and check if the record shouldn't be written for
greeters then skip if class is XDG_SESSION_CLASS_GREETER.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Robert, but that wouldn't help for wtmp/lastlog, since pam is still
used. Is there a reason it is for greeters, though, and should greeters
really have a consolekit session either? Couldn't we just simply fork
without doing most of the stuff in session_child_run if we're starting a
greeter?
--
Unfortunately greeters need to have a console kit session as they access
console kit to perform shutdown/restart and that requires a session to
be open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A fresh install of the definitive release of precise (Ubuntu 12.04) still shows
this bug :-(
Venerable commands like 'w' and 'who' should work correctly in each and every
distro!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've written a patch that updates utmp and uses pam_lastlog for wtmp. It seems
to work:
root@test-precise:~# w
18:22:27 up 1:16, 2 users, load average: 2.44, 1.03, 0.68
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/0remotehost 17:060.00s
The attachment update utmp on session start and use pam_lastlog to
record wtmp/lastlog of this bug report has been identified as being a
patch. The ubuntu-reviewers team has been subscribed to the bug report
so that they can review the patch. In the event that this is in fact
not a patch you can
For what it's worth, I get no utmp/wtmp love here either. Martin wanted
me to comment in case Robert wanted to use me or my laptop as a guinea
pig. :P
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Wed, 18 Apr 2012, Adam Conrad wrote:
For what it's worth, I get no utmp/wtmp love here either. Martin wanted
me to comment in case Robert wanted to use me or my laptop as a guinea
pig. :P
I wonder if the person who are not affected are using a session that's not
the default one?
Maybe
I'm running precise in a computer lab, so maybe I can shed some light on your
theory:
We have roughly 10 different desktop environments installed
current statistics:
host 1: gnome-session --session=buntu, no user in w
host 2: gnome-session --session=ubuntu, no user in w
host 3: gnome-session
On Wed, 18 Apr 2012, Alex Bachmeier wrote:
In the two cases where the user shows up, both users have a gnome-
terminal open.
That doesn't count. We're interested in lines that correspond
to the main login. They have a local TTY like this (here paste
from my debian unstable box but it should be
The reason that issue seems to be stucked is the lack of clear
documentation about wtmp, why it's useful, how it's managed and if
lightdm is the right place that handling should be done (compared to
i.e pam or some other place).
Does anyone have some specs or clear documentation on the topic
I looked into this a bit. There is a pam module that updates lastlog and
wtmp (pam_lastlog(8)), which could be stacked in the lightdm pam config.
It doesn't update utmp, however, and utmp is what w(1) and who(1) look
at -- see the discussion at http://bugs.debian.org/cgi-
Sebastian, that sums it up exactly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about this bug go to:
** Also affects: acpi-support (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: acpi-support (Ubuntu Precise)
** No longer affects: acpi-support (Ubuntu Oneiric)
** No longer affects: acpi-support (Ubuntu)
--
You received this bug notification because you are a member
Dropping milestone. Not reproducible easily, and this is SRUable.
** Changed in: lightdm (Ubuntu Precise)
Milestone: ubuntu-12.04 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
I'm on an updated Ubuntu 12.04 (as opposed to Xubuntu), and can still
confirm this issue..
`ck-list-sessions` does show the session properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Clean install of Xubuntu Beta 2 and updated.
hobgoblin@hobgoblin:~$ w
09:49:18 up 1 min, 0 users, load average: 2.41, 0.75, 0.26
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This works fine for me on current precise. Can you confirm that you can
still reproduce this?
** Changed in: lightdm (Ubuntu Precise)
Milestone: ubuntu-12.04-beta-2 = ubuntu-12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can still reproduce this on my lab machines with all updates
installed.
Mar 26 12:05:28 $HOSTNAME lightdm: pam_unix(lightdm:session): session opened
for user $USER by (uid=0)
Mar 26 12:05:28 $HOSTNAME lightdm: pam_ck_connector(lightdm:session): nox11
mode, ignoring PAM_TTY :0
Mar 26 12:05:32
I confirm Alex's findings. Fully updated, no logging.
It worked briefly for me (see post #17), but after an update it stopped
again. Its interesting that it works sometimes for some people but not
others. Not sure if it might be helpful, but attached is a listing of
all the installed versions of
I too can confirm the issue.
I have 3 machines all running completely updated 12.04 Xubuntu.
None show any users.
2 of the machines are upgraded from 11.10 Xubuntu - the other was a
clean install of 12.04
This one has also got a 12.04 Ubuntu partition - when this is booted it
show's 1 user as
** Tags added: rls-mgr-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about this bug go to:
** Tags removed: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about this bug go to:
Bob,
Sorry for the delayed response.
In Oneiric, 'who' and 'w' report the logged in user, but only from an
active open terminal. What this means for example, is that the asus-
touchpad.sh script provided by acpi-support only works properly when run
from a terminal. When the script is run by
More updates - no change
$ apt-cache policy lightdm
lightdm:
Installed: 1.1.7-0ubuntu1
Candidate: 1.1.7-0ubuntu1
Version table:
*** 1.1.7-0ubuntu1 0
500 http://gb.archive.ubuntu.com/ubuntu/ precise/main i386
Packages
100 /var/lib/dpkg/status
$ w
20:29:37 up 4:16, 0
** Tags removed: rls-mgr-p-tracking
** Tags added: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about
I attempted to build and install debian packages for updated lightdm +
lightdm-gtk-greeter 1.1.4 yesterday, which went fine; I'm expert enough
APT user and prefer installing software as packages.
I found that plain old /bin/login also stopped updating /run/utmp
/var/log/btmp and, or
And its gone (after some updates).
$ apt-cache policy lightdm
lightdm:
Installed: 1.1.6-0ubuntu1
Candidate: 1.1.6-0ubuntu1
Version table:
*** 1.1.6-0ubuntu1 0
500 http://ca.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
100 /var/lib/dpkg/status
$ w
21:57:39 up 3
Oliver, if the fix is due to the changes made in the precise version
then no, this change will not be done in Oneiric (too complex to
backport).
forestpiskie, did you restart lightdm before checking?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Numerous reboots since.
w
07:21:15 up 27 min, 0 users, load average: 1.44, 0.91, 0.56
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
After a login on tty1
w
07:22:25 up 28 min, 1 user, load average: 0.65, 0.80, 0.55
USER TTY FROM LOGIN@ IDLE
Here on up-to-date Oneiric.
I rely on this feature to display remote messages to the logged-in user.
On networked Ubuntu stations this is very important to my programs, else the
user won't know his workstation will shutdown !!
With this bug, my program sees no-one connected and no message can be
Interesting. Just installed the new precise beta 1 and it seems to work
again (but lightdm=1.1.3)
$ apt-cache policy lightdm
lightdm:
Installed: 1.1.3-0ubuntu1
Candidate: 1.1.3-0ubuntu1
Version table:
*** 1.1.3-0ubuntu1 0
500 http://ca.archive.ubuntu.com/ubuntu/ precise/main i386
** Changed in: lightdm (Ubuntu)
Milestone: ubuntu-12.04-beta-1 = ubuntu-12.04-beta-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To
Still no users here.
07:23:26 up 5 min, 0 users, load average: 0.36, 0.84, 0.47
Installed: 1.1.3-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being
Matthias said above, ...the login logs are rather unimportant on
single-user desktop systems,
This is not entirely correct. Those who still use acpi-support for their
machines depend on logins being properly logged in utmp/wtmp. If
/usr/bin/who does not report the logged in user, then
With lightdm 1.1.4 I am getting who/w records (and wasn't in 1.1.3).
This version has a major restructuring in the way PAM is accessed and
may have fixed it?!
bob@alchemy:~$ who
bob pts/02012-03-02 09:22 (:0)
bob@alchemy:~$ w
09:22:06 up 20 min, 1 user, load average: 1.06, 0.56,
** Tags added: rls-mgr-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about this bug go to:
Ok, some pointers in case that's useful, gdm has code in gdm-session-
record.c
void
gdm_session_record_login (GPid session_pid,
...
/* Handle wtmp */
g_debug (Writing wtmp session record to
GDM_NEW_SESSION_RECORDS_FILE);
#if defined(HAVE_UPDWTMPX)
** Changed in: lightdm
Importance: Undecided = High
** Changed in: lightdm (Ubuntu Precise)
Importance: Low = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins
Is this going to be fixed in Oneiric? While the login logs are rather
unimportant on single-user desktop systems, they are very important on
computers used by many people. This is one of the problems that
currently blocks deployment of Xubuntu 11.10 at our university. (We'd
rather not wait for
We are also an educational org and this affects us too. We are unable to
use our utmp/wtmp-based tools to monitor lab-usage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm
** Also affects: lightdm (Ubuntu Precise)
Importance: Low
Status: Confirmed
** Changed in: lightdm (Ubuntu Precise)
Assignee: (unassigned) = Robert Ancell (robert-ancell)
** Changed in: lightdm (Ubuntu Precise)
Milestone: None = ubuntu-12.04-beta-1
** Also affects: lightdm
This may be the underlying cause of bug #896663.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about this bug go to:
Is lightdm really using accountsservice? It's not listed as a
dependency nor even recommends. gdm behaves correctly and depends on
accountsservice.
liblightdm-gobject-1-0 Recommends it, and it's used over dbus yes
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 871070 ***
https://bugs.launchpad.net/bugs/871070
** This bug has been marked a duplicate of bug 871070
LightDM does not update btmp, wtmp and, or utmp records
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** This bug is no longer a duplicate of bug 871070
LightDM does not update btmp, wtmp and, or utmp records
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being
could somebody try with the new version?
** This bug is no longer flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in
I just did. It did not work. Sadly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about this bug go to:
The idea might be good, but a preliminary glance makes me wonder whether
installing that library is sufficient.
% dpkg-query -S /usr/lib/libaccountsservice.so.0.0.0
libaccountsservice0: /usr/lib/libaccountsservice.so.0.0.0
%ldd /usr/lib/accountsservice/accounts-daemon | grep libaccount
I compiled it all and made sure that code was there and installed it and
it still doesn't show up. Then I got the source from git and tried it
again. No love. I guess I'll try gdm and see if it does it too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Is lightdm really using accountsservice? It's not listed as a
dependency nor even recommends. gdm behaves correctly and depends on
accountsservice.
I'm inclined to believe that it's behaving incorrectly with regards the
dbus interaction, but that's all way over my head. Let me know if you
want
89 matches
Mail list logo
