[Wayland-bugs] [Bug 55782] [drm] Keyboard input in terminal crashes client when no pointer device attached
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Oct 9 07:42:34 PDT 2012
https://bugs.freedesktop.org/show_bug.cgi?id=55782
--- Comment #5 from Joe Konno <joe.konno at linux.intel.com> ---
(In reply to comment #4)
> Could you attach the backtrace uncompressed, as text/plain, please?
I did already-- attempting to view shortly after upload gave me an unexpected
internal server error, hence the subsequent bz2 upload. Fortunately, all seems
to be sorted out, and the text/plain version can be viewed here:
https://bugs.freedesktop.org/attachment.cgi?id=68292
>
> Compressed files are impossible to have a quick look in a browser.
>
> FWIW, the x11 backend always provides both kbd and pointer, regardless of
> actual devices, so that's why it doesn't crash there.
>
> When you say Wayland will crash, if the client runs under gdb, do you mean
> Weston? In that case, a backtrace of Weston might be interesting, too.
> Sounds like there is a bug in both. I guess that when the client is under
> gdb, it does not disconnect, and so Weston will have the opportunity to use
> some corrupted data before the client is destroyed.
In the non-gdb case, weston-terminal (the 'client' referred to in bug
description) will crash, and Weston will continue to run. When running gdb on
weston-terminal or weston-terminal + Weston, but not when running on Weston
alone, both terminal and weston will crash.
Attaching bt of Weston in the crashing scenario as well.
>
> Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20121009/4f796314/attachment.html>
More information about the Wayland-bugs
mailing list