greeter log is called "(null)-greeter" when seat type is xlocal and session type is mir
Bug #1590582 reported by
Josh Arenson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Light Display Manager |
Fix Released
|
High
|
Josh Arenson | ||
1.18 |
Fix Released
|
Medium
|
Unassigned | ||
lightdm (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned | ||
Yakkety |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
LightDM uses a strange name for Mir greeter logs - /var/log/
[Test Case]
1. Start LightDM with a Mir greeter
2. Check logs in /var/log/lightdm
Expected result:
Appropriate named log file
Observed result:
Log contains a (null)
[Regression Potential]
Low. We now set the NULL value to something appropriate (the seat name, i.e. seat0-greeter.log).
Related branches
lp:~josharenson/lightdm/fix-null-logname
Rejected
for merging
into
lp:lightdm
- PS Jenkins bot: Pending (continuous-integration) requested
- LightDM Development Team: Pending requested
-
Diff: 14 lines (+3/-1)1 file modifiedsrc/unity-system-compositor.c (+3/-1)
Changed in lightdm: | |
assignee: | nobody → Josh Arenson (josharenson) |
Changed in lightdm: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in lightdm: | |
status: | Triaged → Fix Committed |
milestone: | none → 1.19.1 |
Changed in lightdm (Ubuntu Yakkety): | |
status: | New → Fix Released |
status: | Fix Released → Fix Committed |
importance: | Undecided → High |
Changed in lightdm (Ubuntu Xenial): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in lightdm: | |
status: | Fix Committed → Fix Released |
Changed in lightdm (Ubuntu Xenial): | |
status: | Triaged → Fix Committed |
description: | updated |
To post a comment you must log in.
This bug was fixed in the package lightdm - 1.19.1-0ubuntu1
---------------
lightdm (1.19.1-0ubuntu1) yakkety; urgency=medium
* New upstream release: lightdm. dirs: lightdm. conf.d and etc/guest- session exist HOST_SOCKET instead of MIR_SOCKET to report compositor backend= mir guest-account. sh: guest-session- setup.sh:
* debian/
- Rename "xlocal" seat type to "local". Using "xlocal" will continue to work
but report a warning.
- Ensure user configuration directories /etc/lightdm/
/
- Use MIR_SERVER_
socket to sessions. This used to work but no longer works in Mir 0.21
(LP: #1583624)
- Allow XMir to run on the xlocal seat using the new x-server-
option
- Use only a single compositor on local seats (LP: #1594229)
- Fix Mir greeter log filename having "(null)" in the name (LP: #1590582)
- Copy fcitx/mozc rules so session works when these aren't installed
(LP #1581187)
- Revert lxsession change - it caused the AppArmor to fail to compile
* debian/rules:
- Revert dh_installinit change - we don't want to start LightDM on install
(LP: #1581106)
* debian/
* debian/
- Source prefs.sh as privileged user to allow user modification
(LP: #1581853)
-- Robert Ancell <email address hidden> Mon, 20 Jun 2016 16:18:36 +1200