[Bug 78002] [855GM] X restarts when moving the mouse cursor back into the LVDS screen area for the third time
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Apr 27 15:32:12 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=78002
--- Comment #4 from CarlEitsger <4607vrfcr84spd21f08 at weg-werf-email.de> ---
I am using KDM. `journalctl _SYSTEMD_UNIT=kdm.service` did not output any
log entries. And in /var/log/kdm.log there is not anything interesting. Not
sure where the stderr of kdm and its childs go to... I will try without kdm:
With a pure startx 2> stderr.log (no kdm not enabled in systemd) and a exec
xterm X crashes on the
third re-entry of the mouse cursor. Content generated by the crash:
> xterm: xinit: connection to X server lost
> fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) or KillClient on X server ":0"
With lxde instead of xterm it even crashes at the first reappear of the mouse
cursor:
> XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
> after 31 requests (31 known processed) with 0 events remaining.
> xinit: connection to X server lost
>
> waiting for X server to shut down XIO: fatal IO error 11 (Die Ressource ist zur Zeit nicht
> verfügbar) on X server ":0"
> after 3514 requests (3511 known processed) with 0 events remaining.
> pcmanfm: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
By the way, X does not "restart" (as I first wrote in the bug title) when not
using KDM. Apparently the restarting is a feature of KDM. Being just on tty1
with startx it crashes and makes the computer not respond to any input.
Accessing by ssh (and rebooting) works.
However, I guess those stderrs are not really useful for you. Please tell me
how to investigate better.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140427/2cdfdaa7/attachment.html>
More information about the intel-gfx-bugs
mailing list