This bug was fixed in the package lightdm - 1.18.2-0ubuntu1
---
lightdm (1.18.2-0ubuntu1) xenial; urgency=medium
* New upstream release:
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor
soc
Hello Josh, or anyone else affected,
Accepted lightdm into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.18.2-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
** Description changed:
+ [Impact]
+ LightDM reports the system compositor socket to Mir clients using the
MIR_SOCKET variable. This stopped working in Mir 0.21. The Mir team says the
correct variable is MIR_SERVER_HOST_SOCKET and MIR_SOCKET was a fallback to
that.
+
+ [Test Case]
+ 1. Start L
** Changed in: lightdm/1.18
Status: Fix Committed => Fix Released
** Changed in: lightdm (Ubuntu Xenial)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
** Changed in: lightdm/1.18
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583624
Title:
Mir cannot open a tty when started by lightdm
To manage notifica
This bug was fixed in the package lightdm - 1.19.1-0ubuntu1
---
lightdm (1.19.1-0ubuntu1) yakkety; urgency=medium
* New upstream release:
* debian/lightdm.dirs:
- Rename "xlocal" seat type to "local". Using "xlocal" will continue to work
but report a warning.
- Ensur
** 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/1583624
Title:
Mir cannot open a tty when started by lightdm
To manage notification
** Changed in: lightdm
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583624
Title:
Mir cannot open a tty when started by lightdm
To manage notifications
Forgive my incoherent ramble in #9... Keep this open until lp:~robert-
ancell/lightdm/new-mir-socket-variable lands :-p Also, the new issue is
probably best explained by looking at lp:~mterry/lightdm/initialize-
more/+merge/296836
--
You received this bug notification because you are a member of
The root cause is the fd that pipe gives to USC is 0. The compositor
starts and begins drawing frames, and lightdm eventually tries writing
to fd=0 (also known as STDIN) which causes an Opperation not permitted
error (see lp:1590447). I wrote a nasty patch that forces lightdm to
keep obtaining file
There's some VT issues reported in bug 1589550 which I'm working on at
the same time with this issue.
The (null) issue was an ordering bug. Please fix (I've been meaning to
fix it at some point)!
The code I'm working on is (WIP) lp:~robert-ancell/lightdm/local-seat-
refactor. This merges the unit
I got the greeter working, but there are 2 other issues. The following
assumes you are using the unity8 greeter to launch a unity7 session
if (seat-type == unity)
The greeter loads, authenticates, a black screen is briefly shown, and the
greeter comes back up. My theory here is that lightdm is
Here is mir-greeter.log using your instrumented lightdm and changing the
unity8 seat type to unity.
http://pastebin.ubuntu.com/16932129/
Thoughts?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/158362
I get
[+0.01s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)'
failed
in the logs (or when running in test mode). This only happens when
trying to run under Mir. Meaning I can delete 51-unity8-greeter.conf and
lightdm starts just fine. The error happens before usc/mir are able to
log a
Josh, could you try building LightDM from lp:~robert-ancell/lightdm/new-
mir-socket-variable and confirm if that fixes the issue?
** Also affects: lightdm (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: lightdm (Ubuntu Xenial)
Importance: Undecided => High
** Change
What appears to be happening is the greeter is not aware it is running
inside Unity System Compositor and so it trying to directly access the
video drivers. This fails because it is not running as root.
The cause seems to be LightDM is setting MIR_SOCKET to the name of the
U-S-C socket but this no
** Branch linked: lp:~robert-ancell/lightdm/new-mir-socket-variable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583624
Title:
Mir cannot open a tty when started by lightdm
To manage notification
17 matches
Mail list logo
