Mir

XMir crash - "wrong event type 0"

Bug #1195722 reported by Gerry Boland
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Won't Fix
Medium
Chris Halse Rogers

Bug Description

Possible trigger was going to Spread, but cannot reproduce now.

Relevant part of Xorg.0.log

[ 591.105] dix: invalid event type 0
[ 591.105] 00 00 00 00 00 00 00 00
[ 591.105] 00 00 00 00 00 00 00 00
[ 591.105] 00 00 00 00 00 00 00 00
[ 591.105] 00 00 00 00 00 00 00 00
[ 591.106] (EE)
[ 591.106] (EE) Backtrace:
[ 591.106] (EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x7f9cac3a453d]
[ 591.106] (EE) 1: /usr/bin/X (0x7f9cac202000+0x6ed0e) [0x7f9cac270d0e]
[ 591.106] (EE) 2: /usr/bin/X (mieqProcessDeviceEvent+0x35) [0x7f9cac386835]
[ 591.106] (EE) 3: /usr/bin/X (mieqProcessInputEvents+0xf7) [0x7f9cac386ae7]
[ 591.106] (EE) 4: /usr/bin/X (ProcessInputEvents+0x9) [0x7f9cac293b89]
[ 591.107] (EE) 5: /usr/bin/X (0x7f9cac202000+0x54bb2) [0x7f9cac256bb2]
[ 591.107] (EE) 6: /usr/bin/X (0x7f9cac202000+0x444da) [0x7f9cac2464da]
[ 591.107] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f9ca9f4eea5]
[ 591.107] (EE) 8: /usr/bin/X (0x7f9cac202000+0x44821) [0x7f9cac246821]
[ 591.107] (EE)
[ 591.107]
Fatal server error:
[ 591.107] Wrong event type 0. Aborting server
[ 591.107]

Revision history for this message
Gerry Boland (gerboland) wrote :
Changed in mir:
importance: Undecided → Medium
status: New → Triaged
assignee: nobody → Chris Halse Rogers (raof)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

XMir 1.0 is no longer supported.

Changed in mir:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.