[Expired for lxsession (Ubuntu) because there has been no activity for
60 days.]
** Changed in: lxsession (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
[Expired for light-locker (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: light-locker (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Changed in: lxsession (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579699
Title:
lxlock terminates/crashes the session instead of screenlocking
To man
** Also affects: lxsession (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579699
Title:
lxlock terminates/crashes the session instead of screenlo
Does "dm-tool switch-to-greeter" trigger the crash also?
** Changed in: light-locker (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579699
Title:
lxl
Hi,
I just wanted to report that the session crashes I was experiencing appear to
have been transitory, and I am no longer able to reproduce. If it returns I
will attempt to gather some further low-level info - I didn't confirm with
strace or anything but all of the system characteristics descr
** Changed in: light-locker (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579699
Title:
lxlock terminates/crashes the session instead of screenlocking
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: light-locker (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579699
Title:
strace revealed how light-locker dies:
16329 write(2, "\n(light-locker:16329): Gdk-WARNING **: light-locker: Fatal IO
error 11 (Die Ressource ist zur Zeit nicht verf\303\274gbar) on X server
:1.\n\n", 134) = 134
16329 exit_group(1) = ?
There's more error messages like that
I've noticed that lxlock is just a script that calls light-locker-
command, so it was wrong to report against lxsession.
** Package changed: lxsession (Ubuntu) => light-locker (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Sorry, I just noticed that I've reported against the wrong package.
lxlock just calls
light-locker-command -l
which causes the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579699
Title:
11 matches
Mail list logo
