THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Jim Pryor (Profjim)
Attached to Project - awesome
Summary - Awesome freezes when switching from console -> back to X
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - High
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - This problem exists for me using either awesome 3.4.2 or git/master
(git describe = v3.4-85-gc4c15db).
I'm using Arch Linux
kernel = 2.6.32.1.
X 1.7.3.901
xf86-video-intel 2.9.99.902. The last was just updated today, but I've
been having this problem for several weeks. Previous video driver version 2.9.1
was also giving me this problem.
To reproduce, I type "startx" in a virtual console. Awesome starts up,
everything is fine. Switch back to a virtual console. Wait a few minutes. (If you switch
back to X immediately, sometimes there's no problem. I don't know why.) After waiting for
say 3 minutes, switch back to X/Awesome. For a moment the screen will look correct, then
the Awesome tag bar will be replaced by an empty block (with the same background color as
the tag bar originally had) and no UI is possible. Awesome doesn't honor keypresses or
mouse clicks. Before the first mouseclick, the cursor will still change appropriately as
it hovers over different regions of the screen (for instance, to an I-bar when it hovers
over an xterm, and to an arrow when it hovers over the desktop). But after the first
mouseclick, the cursor stays stuck in a single shape. It will still move around the
screen. At this point, I can only switch back to a virtual console and kill X (or I can
type my Kill X key combo inside X, that
will
still work).
The problem occurs even when I'm not running any screensaver. Even when I'm
using the factory rc.lua config. I'm surprised not to see any other similar
reports in the awesome mailing list or in my distro's forums. (A lot of Arch
Linux users run Awesome.) So I'm expecting it's something about my specific
setup. But I'm still seeing the problem even when I make everything as vanilla
as possible.
More information can be found at the following URL:
http://awesome.naquadah.org/bugs/index.php?do=details&task_id=705
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to [email protected].
