[LightDM] Newer version of lightdm for 14.04.1 -- is this possible?

Mon Sep 29 20:29:59 PDT 2014

(removing the ubuntu-users list since they don't need to be spammed with
technical details of lightdm)

I'm not sure what your issue is without seeing the logs but the lightdm log
from a failed startup should show the issue. Please file a bug against
lightdm. There's no special information that is persisted across reboots
that I know of.

In general, if you have an issue please just file a bug. If you're not sure
what component is causing the problem, just make a guess and we'll reassign
it if incorrect.

--Robert

On 30 September 2014 07:10, Robert Heller <heller at deepsoft.com> wrote:

> At Sun, 28 Sep 2014 23:47:28 -0400 Robert Heller <heller at deepsoft.com>
> wrote:
>
> >
> > At Mon, 29 Sep 2014 16:29:11 +1300 Robert Ancell <
> robert.ancell at gmail.com> wrote:
> >
> > >
> > >
> > > Is this bug 1302491 [1]? If not, then please file a bug using either
> > > "ubuntu-bug lightdm" from the command-line or from
> launchpad.net/lightdm.
> >
> > Yes, this is the bug, which is fixed in 1.11.4, which is why I wanted to
> > install 1.11.4 in Ubuntu 14.04 LTS.
>
> Ok, bug report filed:
> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1375392
>
> I have another issue, but I am not sure if it is a lightdm, Unity, or
> Unity-Greeter issue.
>
> This is what happens: The library personal who shut down the computers for
> the
> day don't bother to 'log out' the guest users -- they simply select 'Shut
> Down' from the gear menu (upper right). When the machines are rebooted the
> next day, the auto login does not always work. There seems to be some
> 'context' stored somewhere that informs Unity or the Unity greeter that the
> user didn't logout. It is behaving similarly to if the user had locked the
> screen (sort of). I think there is some state information stored somewhere
> (and it would *have* to be in $HOME somewhere -- all of the other
> directories/file systems are either NFS mounted readonly (/ and /usr) or
> ramdisks (I am using DRBL and /etc, /var, and /root are ramdisks mounted
> and
> initialized at boot time from tarballs). Where is this state information
> stored and what needs to be done to remove it -- eg insure a proper,
> cleanly
> logged out state? I already have a early morning cron job that clears out
> 'junk' files (eg stuff that might have been downloaded by library patrons
> during the previous day). It would be easy to add a hack to clear the
> logged
> in flag or whatever it is.
>
> >
> > >
> > > [1] https://bugs.launchpad.net/lightdm/+bug/1302491
> > >
> > > On 29 September 2014 12:23, Robert Heller <heller at deepsoft.com> wrote:
> > >
> > > > At Mon, 29 Sep 2014 10:40:09 +1300 Robert Ancell <
> robert.ancell at gmail.com>
> > > > wrote:
> > > >
> > > > >
> > > > >
> > > > >
> > > > > 14.04 LTS will continue to receive updates in the LightDM 1.10
> series
> > > > [1].
> > > > > This series contains important bugfixes and occasional backports
> of new
> > > > > features that can be added without modifying existing behaviours.
> All
> > > > > updates to 14.04 LTS need to go through the Stable Release Update
> process
> > > > > [2] which means features need to be carefully tested.
> > > >
> > > > Ok, what do I need to do to get the failure to autologin 'bug'
> fixed?  Is
> > > > there someplace I should report this bug?  This is the 'bug' where
> LightDM
> > > > 1.10 fails to autologin the Nth time (where N > 1).  Or is this
> really a
> > > > bug
> > > > with the Ubuntu Unity greeter?  (BTW: Ubuntu Unity greeter has
> various
> > > > issues
> > > > all on its own.)
> > > >
> > > > >
> > > > > --Robert
> > > > >
> > > > > [1] https://launchpad.net/lightdm/1.10
> > > > > [2] https://wiki.ubuntu.com/StableReleaseUpdates
> > > > >
> > > > > On 28 September 2014 09:39, Robert Heller <heller at deepsoft.com>
> wrote:
> > > > >
> > > > > > Are there any plans to backport a newer version of lightdm for
> 14.04
> > > > LTS?
> > > > > > The
> > > > > > current version (1.10.1-0ubuntu1) is 'broken' -- specificly it
> does not
> > > > > > auto-re-login (autologin only works the *first* time, never
> after the
> > > > user
> > > > > > logs out).  I believe this is fixed in 1.11 (and later).  I
> don't want
> > > > to
> > > > > > upgrade to 14.10 and land on the upgrade-every-9-months roller
> > > > coaster.  I
> > > > > > would like to stay with 14.04 LTS for its full 5 years and enjoy
> a
> > > > stable
> > > > > > system (except for lightdm being broken).  (There are some
> issues with
> > > > the
> > > > > > Unity greeter, but I suspect using an alternitive greeter will
> fix
> > > > that.)
> > > > > >
> > > > > > --
> > > > > > Robert Heller             -- 978-544-6933
> > > > > > Deepwoods Software        -- Custom Software Services
> > > > > > http://www.deepsoft.com/  -- Linux Administration Services
> > > > > > heller at deepsoft.com       -- Webhosting Services
> > > > > >
> > > > > > _______________________________________________
> > > > > > LightDM mailing list
> > > > > > LightDM at lists.freedesktop.org
> > > > > > http://lists.freedesktop.org/mailman/listinfo/lightdm
> > > > > >
> > > > >
> > > > > MIME-Version: 1.0
> > > > >
> > > > > _______________________________________________
> > > > > LightDM mailing list
> > > > > LightDM at lists.freedesktop.org
> > > > > http://lists.freedesktop.org/mailman/listinfo/lightdm
> > > > >
> > > > >
> > > >
> > > > --
> > > > Robert Heller             -- 978-544-6933
> > > > Deepwoods Software        -- Custom Software Services
> > > > http://www.deepsoft.com/  -- Linux Administration Services
> > > > heller at deepsoft.com       -- Webhosting Services
> > > >
> > > >
> > >
> > >
> >
>
> --
> Robert Heller             -- 978-544-6933
> Deepwoods Software        -- Custom Software Services
> http://www.deepsoft.com/  -- Linux Administration Services
> heller at deepsoft.com       -- Webhosting Services
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/lightdm/attachments/20140930/df4dcc28/attachment.html>