Debian Bug report logs - #520685
stumpwm: When returning from screensaver, keyboard doesn't respond

version graph

Package: stumpwm; Maintainer for stumpwm is Debian Common Lisp Team <pkg-common-lisp-devel@lists.alioth.debian.org>; Source for stumpwm is src:stumpwm.

Reported by: Antony Gelberg <antony.gelberg@gmail.com>

Date: Sat, 21 Mar 2009 23:21:01 UTC

Severity: normal

Found in version stumpwm/1:20080721-2

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Common Lisp Team <pkg-common-lisp-devel@lists.alioth.debian.org>:
Bug#520685; Package stumpwm. (Sat, 21 Mar 2009 23:21:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Antony Gelberg <antony.gelberg@wayforth.com>:
New Bug report received and forwarded. Copy sent to Debian Common Lisp Team <pkg-common-lisp-devel@lists.alioth.debian.org>. (Sat, 21 Mar 2009 23:21:03 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Antony Gelberg <antony.gelberg@wayforth.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: stumpwm: When returning from screensaver, keyboard doesn't respond
Date: Sat, 21 Mar 2009 23:17:46 +0000
Package: stumpwm
Version: 1:20080721-2
Severity: normal

Hi,

Sometimes when returning from xscreensaver, my xorg session doesn't respond to
/any/ keypresses, either in the active window, or C-t stumpwm commands.  My
workaround is to go to a console window, kill stumpwm, and re-run it.  I
/believe/ that this only happens after a lock and password-type - I think when
the screensaver kicks in, all works fine if I press a key to interrupt the
screensaver before it locks and asks for a password (half an hour later or so
on this box).

This doesn't happen with other WMs, so I'm assuming it's a stump bug.  When it
occurs, the mouse /does/ still work - I can click links in Iceweasel etc.

I know nothing about Lisp, but if you have any ideas how I can assist
debugging this issue, I'll try to help.

Antony


-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages stumpwm depends on:
ii  cl-ppcre                    1.3.2-2      Portable Regular Express Library f
ii  clisp                       1:2.44.1-4.1 GNU CLISP, a Common Lisp implement
ii  common-lisp-controller      6.17         Common Lisp source and compiler ma

stumpwm recommends no packages.

Versions of packages stumpwm suggests:
ii  dillo [www-browser]        0.8.6-3       Small and fast web browser
ii  elinks [www-browser]       0.11.4-3      advanced text-mode WWW browser
ii  emacs22-gtk [info-browser] 22.2+2-5      The GNU Emacs editor (with GTK use
ii  epiphany-gecko [www-browse 2.22.3-9      Intuitive GNOME web browser - Geck
ii  gnome-terminal [x-terminal 2.22.3-3      The GNOME 2 terminal emulator appl
ii  iceweasel [www-browser]    3.0.6-1       lightweight web browser based on M
ii  info [info-browser]        4.11.dfsg.1-4 Standalone GNU Info documentation 
ii  menu                       2.1.41        generates programs menu for all me
pn  rlwrap                     <none>        (no description available)
ii  rxvt-unicode [x-terminal-e 9.05-1+lenny1 RXVT-like terminal emulator with U
pn  slime                      <none>        (no description available)
ii  w3m [www-browser]          0.5.2-2+b1    WWW browsable pager with excellent
ii  x11-utils                  7.3+2+nmu1    X11 utilities
ii  xterm [x-terminal-emulator 235-2         X terminal emulator

-- no debconf information




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Common Lisp Team <pkg-common-lisp-devel@lists.alioth.debian.org>:
Bug#520685; Package stumpwm. (Fri, 08 May 2009 16:18:08 GMT) Full text and rfc822 format available.

Acknowledgement sent to Luca Capello <luca@pca.it>:
Extra info received and forwarded to list. Copy sent to Debian Common Lisp Team <pkg-common-lisp-devel@lists.alioth.debian.org>. (Fri, 08 May 2009 16:18:08 GMT) Full text and rfc822 format available.

Message #10 received at 520685@bugs.debian.org (full text, mbox):

From: Luca Capello <luca@pca.it>
To: Antony Gelberg <antony.gelberg@wayforth.com>
Cc: 520685@bugs.debian.org
Subject: Re: Bug#520685: stumpwm: When returning from screensaver, keyboard doesn't respond
Date: Fri, 08 May 2009 18:16:54 +0200
[Message part 1 (text/plain, inline)]
Hi Antony!

On Sun, 22 Mar 2009 00:17:46 +0100, Antony Gelberg wrote:
> Version: 1:20080721-2

Please, can you check if the latest version I just uploaded,
i.e. 1:20090502.git482df740-1, still has the same bug?  I cannot
reproduce it with 1:20080721-2 on a KVM virtual machine.

> Sometimes when returning from xscreensaver, my xorg session doesn't
> respond to /any/ keypresses, either in the active window, or C-t
> stumpwm commands.  My workaround is to go to a console window, kill
> stumpwm, and re-run it.

If StumpWM is still working, you should be able to use stumpish (the
StumpWM Interactive SHell), thus go to a console window, login and:

  $ DISPLAY=:0.0 stumpish
  Welcome to the STUMPwm Interactive SHell.
  Type commands for a list of commands.
  > version

If the 'version' command above returns something, then StumpWM is still
active, otherwise it has crashed.

> This doesn't happen with other WMs, so I'm assuming it's a stump bug.
> When it occurs, the mouse /does/ still work - I can click links in
> Iceweasel etc.

This is how X11 works:

- if your ~/.xsession (or the Display Manager you use) starts the WM as
  the first process in X11, then if this process crashes your session
  will exit as well

- however, if you have started the WM from an already running X11
  session, then every program already running when the WM crashes is
  still available, thus the mouse still works

> I know nothing about Lisp, but if you have any ideas how I can assist
> debugging this issue, I'll try to help.

Depending how you start StumpWM (see above), it logs to
~/.xsession-errors (first case) or to stdout (second case): if StumpWM
crashes, the log should contain the reason.

Thx, bye,
Gismo / Luca
[Message part 2 (application/pgp-signature, inline)]

Changed Bug submitter to 'Antony Gelberg <antony.gelberg@gmail.com>' from 'Antony Gelberg <antony.gelberg@wayforth.com>' Request was from Antony Gelberg <antony.gelberg@gmail.com> to control@bugs.debian.org. (Sun, 06 Jun 2010 12:18:11 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Fri Apr 18 03:58:09 2014; Machine Name: beach.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.