Hi Chris! This is what may seem to be the relevant part of the xtrace
output. If you need anything further back, just let me know and I'll
attach a more complete log.
<lots of stuff>
000:>:4605: Event MotionNotify(6) detail=Normal(0x00) time=0x006d6670
root=0x0000014e event=0x0840008a child=None(0x00000000) root-x=814 root-y=268
event-x=412 event-y=150 state=0 same-screen=true(0x01)
001:<:0009: 24: Request(20): GetProperty delete=false(0x00) window=0x0000014e
property=0x1d7("AT_SPI_IOR") type=0x1f("STRING") long-offset=0x00000000
long-length=0x00002000
000:>:4605: Event MotionNotify(6) detail=Normal(0x00) time=0x006d6678
root=0x0000014e event=0x0840008a child=None(0x00000000) root-x=814 root-y=267
event-x=412 event-y=149 state=0 same-screen=true(0x01)
001:>:0009:644: Reply to GetProperty: type=0x1f("STRING")
bytes-after=0x00000000
data='IOR:010000001f00000049444c3a4163636573736962696c6974792f52656769737472793a312e300000030000000054424f500000000101020005000000554e4958000000000a0000006c6f63616c686f7374000000280000002f746d702f6f726269742d7067672f6c696e632d3835632d302d326637643730646434386463310000000000caaedfba5400000001010200280000002f746d702f6f726269742d7067672f6c696e632d3835632d302d3266376437306464343864633100000000001c000000000000004aeea4304440e8a8c02b2828282828280800000002c65c6801000000480000000100000002000000050000001c000000000000004aeea4304440e8a8c02b2828282828280800000002c65c6801000000140000000100000001000105000000000901010000000000'
001:<:000a: 24: Request(20): GetProperty delete=false(0x00) window=0x0000014e
property=0x1d7("AT_SPI_IOR") type=0x1f("STRING") long-offset=0x00000000
long-length=0x00002000
001:>:000a:644: Reply to GetProperty: type=0x1f("STRING")
bytes-after=0x00000000
data='IOR:010000001f00000049444c3a4163636573736962696c6974792f52656769737472793a312e300000030000000054424f500000000101020005000000554e4958000000000a0000006c6f63616c686f7374000000280000002f746d702f6f726269742d7067672f6c696e632d3835632d302d326637643730646434386463310000000000caaedfba5400000001010200280000002f746d702f6f726269742d7067672f6c696e632d3835632d302d3266376437306464343864633100000000001c000000000000004aeea4304440e8a8c02b2828282828280800000002c65c6801000000480000000100000002000000050000001c000000000000004aeea4304440e8a8c02b2828282828280800000002c65c6801000000140000000100000001000105000000000901010000000000'
software-center: Fatal IO error 11 (Resource temporarily unavailable) on X
server :9.
000:>:4605: Event MotionNotify(6) detail=Normal(0x00) time=0x006d6680
root=0x0000014e event=0x0840008a child=None(0x00000000) root-x=814 root-y=266
event-x=412 event-y=148 state=0 same-screen=true(0x01)
<few more motion_notify events>
** Description changed:
Binary package hint: software-center
When loading details views, I quite frequently get the message
"software-center: Fatal IO error 11 (Resource temporarily unavailable)
on X server :0.". Once this has happened twice/thrice software-center
quits/crashes.
+ To reproduce this issue, I browse to eg the accessories category, double
+ click on the first item, click on 'accessories' in the pathbar, double
+ click on the second item, etc.
+
+ It may or may not be a coincidence, but I have never been able to
+ reproduce this issue whilst using our ReviewLoaderJsonAsync (ie run
+ SOFTWARE_CENTER_GIO_REVIEWS=. PYTHONPATH=. ./software-center --this mode
+ only works in trunk right atm). I have only ever been able to reproduce
+ this whilst using our default ReviewLoaderThreadedRNRClient.
+
I have no idea whether this is a s-c issue, an x issue or whatever.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/743020
Title:
software-center: Fatal IO error 11 (Resource temporarily unavailable)
on X server :0.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
