[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2021-10-13 Thread Steve Langasek 
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: lightdm (Ubuntu Precise)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
  Fix Released
Status in lightdm source package in Precise:
  Won't Fix
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:
  Fix Released

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-12 Thread Launchpad Bug Tracker 
This bug was fixed in the package lightdm - 1.21.3-0ubuntu1

---
lightdm (1.21.3-0ubuntu1) zesty; urgency=medium

  * New upstream release:
- Fix crashes introduced in 1.21.2 due to environment variable changes
- Fix incorrect unref in XDMCP server code
- Fix logging warning

 -- Robert Ancell   Fri, 09 Dec 2016
14:04:49 +1300

** Changed in: lightdm (Ubuntu Zesty)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
  Fix Released
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:
  Fix Released

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Robert Ancell 
** Changed in: lightdm/1.2
   Importance: Undecided => High

** Changed in: lightdm/1.2
   Status: New => Fix Committed

** Changed in: lightdm/1.2
Milestone: None => 1.2.12

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Launchpad Bug Tracker 
** Branch linked: lp:lightdm/1.2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Robert Ancell 
** 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Launchpad Bug Tracker 
** Branch linked: lp:lightdm/1.10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Robert Ancell 
** Changed in: lightdm/1.18
   Importance: Undecided => High

** Changed in: lightdm/1.18
   Status: New => Fix Committed

** Changed in: lightdm/1.18
Milestone: None => 1.18.4

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
  New
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Launchpad Bug Tracker 
** Branch linked: lp:lightdm/1.18

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
  New
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Launchpad Bug Tracker 
** Branch linked: lp:lightdm/1.20

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
  New
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Robert Ancell 
** Changed in: lightdm/1.20
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
  New
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Robert Ancell 
** Changed in: lightdm
   Status: Fix Committed => Fix Released

** Changed in: lightdm
Milestone: None => 1.21.2

** Changed in: lightdm/1.20
   Status: New => Fix Committed

** Changed in: lightdm/1.20
Milestone: None => 1.20.1

** Also affects: lightdm (Ubuntu Zesty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
  New
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Alberts Muktupāvels 
** Description changed:

  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.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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 Committed
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.18 series:
  New
Status in Light Display Manager 1.2 series:
  New
Status in Light Display Manager 1.20 series:
  New
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

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Robert Ancell 
** Changed in: lightdm
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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 Committed
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.18 series:
  New
Status in Light Display Manager 1.2 series:
  New
Status in Light Display Manager 1.20 series:
  New
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

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2016-12-08 Thread Robert Ancell 
** Also affects: lightdm/1.10
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.20
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.18
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.2
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Precise)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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 Committed
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.18 series:
  New
Status in Light Display Manager 1.2 series:
  New
Status in Light Display Manager 1.20 series:
  New
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

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp