Dear Maintainer,


I am running Debian Sid and so expect some oddities from time to time.

I found my laptop (Compaq 8710p) unusable after a suspend after an upgrade.
My only recourse was to switch to a console and do an Ctrl-Alt-Delete.
pm-suspend from a console would still suspend and would come back nicely
but not just closing the lid as I was used to.  I found that I could
disable the nvidia
drivers and it would work, but got a double security login and realized
that a new
security program had been installed (light-locker) in addition to
xscreensaver.
By uninstalling light-locker and leaving xscreensaver in place, I was able
to get normal
suspend and resume behavior with the nvidia drivers, but reinstalling
light-locker and
removing xscreensaver recreated the problem so it was not a conflict
between those two
programs.

I suppose that the problem could be related to the legacy nvidia drivers
and that up to date
drivers would be fine, but I have no way of testing that.

My problem seems similar to the known bugs for light-locker but I did not
see any others where disabling
the nvidia drivers had an effect.

Hi,

so can you precisely say what happens when you have only light-locker
installed (making sure you use lightdm as a display manager)?

Regards,

I assume you mean with the nvidia drivers functioning.  I close the lid and
it suspends normally, so far as I can tell.  I lift the lid and press the
power button and it seems to resume, but I get a black screen.  Sometimes
if I mash enough keys, it will give me a screen saying the session is
locked and that I will get an unlock screen shortly (which never happens)
but that is rare.  If I do a Ctrl-Alt-F1, there is a flash of the console
and then a black screen with a flashing cursor in the upper left.  If I do
Ctrl-Alt-F1 again, I get that same flash of console text.  I can do this
repeatedly.  If I then press Ctrl-Alt_Del, it shuts down and reboots.  And
yes, I am using lightdm.

On Fri, Aug 26, 2016 at 1:23 AM, Yves-Alexis Perez <corsac@debian.org> wrote:

Please keep the bug on CC.

I guess it'd help to have some logs (dmesg, Xorg.0.log and stuff from
/var/log/lightdm). I guess nvidia drivers don't like the vt switch but
honestly I won't investigate too much. I don't have an NVidia card and I don't
really support non-free drivers.

Regards.

A bit more information.  It doesn't really have anything to do with
suspend.  If I run "light-locker-command -l" it does the same thing.  I am
able to ssh in to the laptop with no difficulty after locking it, but none
of the other commands have any effect, and if I kill light-locker it does
not help.  I can restart lightdm from ssh, but that doesn't help me a great
deal.

I think I may have some good information from a test I ran though.  I
killed light-locker remotely and then restarted it in debug mode, then
locked it with the command on the laptop.  The result was a whole lot of
dbus error messages.  I found references to similar error messages
resulting from nvidia drivers of a similar age.  I understand your
unwillingness to support a proprietary driver which is buggy anyway, but if
this helps you improve the program, that is great.  If you want me to try
something, I am willing.


[gs_listener_send_lock_session] gs-listener-dbus.c:180 (17:52:47):     Send
lock session
process 3422: arguments to dbus_message_new_method_call() were incorrect,
assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line
1363.
This is normally a bug in some application using the D-Bus library.
[gs_listener_send_lock_session] gs-listener-dbus.c:202 (17:52:47):
 Couldn't allocate the dbus message
[switch_greeter_timeout] gs-manager.c:430 (17:52:56):     Switch to greeter
timeout
[gs_listener_send_switch_greeter] gs-listener-dbus.c:139 (17:52:56):
 Send switch greeter
process 3422: arguments to dbus_message_new_method_call() were incorrect,
assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line
1363.
This is normally a bug in some application using the D-Bus library.
[gs_listener_send_switch_greeter] gs-listener-dbus.c:161 (17:52:56):
 Couldn't allocate the dbus message
[listener_dbus_handle_system_message] gs-listener-dbus.c:1330
(17:52:58):     obj_path=/org/freedesktop/UPower/devices/battery_C1FD
interface=org.freedesktop.DBus.Properties method=PropertiesChanged
destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:1330
(17:54:58):     obj_path=/org/freedesktop/UPower/devices/battery_C1FD
interface=org.freedesktop.DBus.Properties method=PropertiesChanged
destination=(null)
[gs_window_raise] gs-window-x11.c:328 (17:56:48):     Raising screensaver
window




On Fri, Aug 26, 2016 at 11:35 AM, Yves-Alexis Perez <corsac@debian.org> wrote:

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***