** Changed in: lightdm/1.10
Importance: Undecided => High
** Changed in: lightdm/1.10
Status: New => Fix Committed
** Changed in: lightdm/1.10
Milestone: None => 1.10.7
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1648637
Title:
handle interruped read and write calls
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Committed
Status in Light Display Manager 1.18 series:
Fix Committed
Status in Light Display Manager 1.2 series:
Fix Committed
Status in Light Display Manager 1.20 series:
Fix Committed
Status in lightdm package in Ubuntu:
New
Status in lightdm source package in Precise:
New
Status in lightdm source package in Trusty:
New
Status in lightdm source package in Xenial:
New
Status in lightdm source package in Yakkety:
New
Status in lightdm source package in Zesty:
New
Bug description:
Use SA_RESTART flag to make sure that interrupted calls to read and/or
write are restarted.
In my case read is interrupted when reading login1_session_id. Result
of not handling EINTR error is that login1_session_id is set to NULL
and console_kit_cookie gets login1 session id.
Related warnings in lightdm.log:
[+0.44s] WARNING: Session pid=617: Error reading from session: Interrupted
system call
[+0.70s] DEBUG: Activating VT 7
[+0.70s] DEBUG: Activating ConsoleKit session c1
[+0.70s] WARNING: Error getting ConsoleKit session:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.ConsoleKit was not provided by any .service files
And because login1_session_id is null fix for 1637758 bug does not
work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1648637/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
