[Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
Sounds like a plan. ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094097 Title: Xorg crashed with SIGSEGV in mieqMoveToNewScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1094097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
I haven't experienced this bug in a while. I think we could mark it as solved and then re-open it if it happens again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094097 Title: Xorg crashed with SIGSEGV in mieqMoveToNewScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1094097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
Could anybody else answer the question from comment #11 ? Thnaks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094097 Title: Xorg crashed with SIGSEGV in mieqMoveToNewScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1094097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
Sorry Bryce, but I could not provide. I have switch some weeks ago with the affected system back to quantal, because one think I want to do was not pssible with raring. I have had known that it works with quantal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094097 Title: Xorg crashed with SIGSEGV in mieqMoveToNewScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1094097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
There haven't been any other reports of a crash like this in raring since we updated to xserver 1.13.1; I'm wondering if the point release update may have solved this issue. Have you seen any further crashes like this in the last month or so? ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Triaged ** Changed in: xorg-server (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094097 Title: Xorg crashed with SIGSEGV in mieqMoveToNewScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1094097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
** Description changed:
The Xorg server crashed after automatically monitor switch off(time
depend). More exactly after reactivating the monitor with a random key
stroke.
Unfortunally I am not able to reproduce until now.
+
+ #14
+ #15 0x7f9d35b64d24 in mieqMoveToNewScreen (screen=0x7f9d371b7510,
dev=0x7f9d373e43a0, event=) at ../../mi/mieq.c:490
+ #16 mieqMoveToNewScreen (dev=0x7f9d373e43a0, screen=0x7f9d371b7510,
event=, event=) at ../../mi/mieq.c:488
+ #17 0x7f9d35b65632 in mieqProcessDeviceEvent
(dev=dev@entry=0x7f9d373e43a0, event=event@entry=0x7f9d35e09540 ,
screen=screen@entry=0x7f9d371b7510) at ../../mi/mieq.c:526
+ handler = 0x0
+ mevent = {any = {header = 255 '\377', type = ET_RawMotion, length =
624, time = 9504392}, device_event = {header = 255 '\377', type = ET_RawMotion,
length = 624, time = 9504392, deviceid = 2, sourceid = 11, detail = {button =
0, key = 0}, touchid = 0, root_x = 3, root_x_frac = 0, root_y = -8005,
root_y_frac = 2.81377125, buttons = "\237\257w\325\314\226N\300", '\000'
, valuators = {mask = "\000\000\000\000", mode =
"\000\000\000\000", data = {0 , 43, -131, 0, 0, 0, 0, 0}},
mods = {base = 0, latched = 0, locked = 0, effective = 0}, group = {base = 0
'\000', latched = 0 '\000', locked = 0 '\000', effective = 0 '\000'}, root = 0,
corestate = 0, key_repeat = 0, flags = 0}, changed_event = {header = 255
'\377', type = ET_RawMotion, length = 624, time = 9504392, deviceid = 2, flags
= 11, masterid = 0, sourceid = 0, buttons = {num_buttons = 3, names = {0,
2744574139, 1077155028, 3581390751, 3226375884, 0 ,
1078296576, 0, 3227541504, 0 , 4, 1222, 5734, 48000, 0, 147,
0, 0, 0, 0, 0, 0, 0, 910, 4974, 95000, 0, 148, 0, 0, 0, 0, 0, 0, 0, 0,
4294967295, 0, 0, 261, 0, 0, 0, 0, 0, 0, 0, 0, 4294967295, 0}}, num_valuators =
0, valuators = {{min = 260, max = 0, resolution = 0, mode = 0 '\000', name = 0,
scroll = {type = SCROLL_TYPE_NONE, increment = 0, flags = 0}}, {min = 0, max =
0, resolution = 0, mode = 0 '\000', name = 0, scroll = {type =
SCROLL_TYPE_NONE, increment = 0, flags = 0}} , {min = 0, max
= 0, resolution = 0, mode = 0 '\000', name = 0, scroll = {type =
SCROLL_TYPE_NONE, increment = 0, flags = -224198896}}, {min = 1, max = 0,
resolution = 903922496, mode = 157 '\235', name = 899849099, scroll = {type =
4070768399, increment = 4.9406564584124654e-324, flags = 0}}, {min = 925659720,
max = 32669, resolution = 0, mode = 0 '\000', name = 0, scroll = {type =
SCROLL_TYPE_NONE, increment = 0, flags = 0}}, {min = 0, max = 0, resolution =
0, mode = 0 '\000', name = 0, scroll = {type = SCROLL_TYPE_NONE, increment = 0,
flags = 0}}}, keys = {min_keycode = 0, max_keycode = 0}}, touch_ownership_event
= {header = 255 '\377', type = ET_RawMotion, length = 624, time = 9504392,
deviceid = 2, sourceid = 11, touchid = 0, reason = 0 '\000', resource = 3,
flags = 0}, dga_event = {header = 255 '\377', type = ET_RawMotion, length =
624, time = 9504392, subtype = 2, detail = 11, dx = 0, dy = 0, screen = 3,
state = 0}, raw_event = {header = 255 '\377', type = ET_RawMotion, length =
624, time = 9504392, deviceid = 2, sourceid = 11, detail = {button = 0, key =
0}, valuators = {mask = "\003\000\000\000", data = {20.081369613967336,
-61.17812603324932, 0 }, data_raw = {43, -131, 0 }}, flags = 0}}
+ #18 0x7f9d35b657b8 in mieqProcessInputEvents () at ../../mi/mieq.c:623
+ screen = 0x7f9d371b7510
+ event = {any = {header = 255 '\377', type = ET_Motion, length = 424,
time = 9504392}, device_event = {header = 255 '\377', type = ET_Motion, length
= 424, time = 9504392, deviceid = 11, sourceid = 11, detail = {button = 0, key
= 0}, touchid = 0, root_x = 56, root_x_frac = 0.842097521, root_y = 171,
root_y_frac = 0.989590883, buttons = '\000' , valuators =
{mask = "\003\000\000\000", mode = "\000\000\000\000", data =
{1409.7536925293261, 1820.111585156938, 0 }}, mods = {base =
0, latched = 0, locked = 0, effective = 0}, group = {base = 0 '\000', latched =
0 '\000', locked = 0 '\000', effective = 0 '\000'}, root = 0, corestate = 0,
key_repeat = 0, flags = 0}, changed_event = {header = 255 '\377', type =
ET_Motion, length = 424, time = 9504392, deviceid = 11, flags = 11, masterid =
0, sourceid = 0, buttons = {num_buttons = 56, names = {1062704052, 171,
1065178580, 0, 0, 0, 0, 0, 0, 0, 0, 3, 0, 0, 0, 3355013832, 1083574019,
1130438418, 1083994226, 0 }}, num_valuators = 0, valuators =
{{min = 0, max = 0, resolution = 0, mode = 0 '\000', name = 0, scroll = {type =
SCROLL_TYPE_NONE, increment = 0, flags = 0}} }, keys =
{min_keycode = 0, max_keycode = 0}}, touch_ownership_event = {header = 255
'\377', type = ET_Motion, length = 424, time = 9504392, deviceid = 11, sourceid
= 11, touchid = 0, reason = 0 '\000', resource = 56, flags = 1062704052},
dga_event = {header = 255 '\377', type = ET_Motion, length = 424, time =
9504392, subtype = 11, detail = 11, dx = 0, dy = 0, screen = 56, state =
37812}, raw_event =
[Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
The crash is occurring in code that handles keyboard and mouse input when the screen is being woken up. For those trying to find out how to reproduce the bug, it must be some combination of keyboard or mouse button input while waking the screen or vt switching. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094097 Title: Xorg crashed with SIGSEGV in mieqMoveToNewScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1094097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094097 Title: Xorg crashed with SIGSEGV in mieqMoveToNewScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1094097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
Yes, the stacktrace top is like the one in bug 1039341 as far as the code lines are affected. The rest differs only a little bit. Unfortunally I have not observed this crasher again. The external monitor was connected with VGA, but to point again on it: At time of the crash there was no figuring arround with an external monitor by me. It was the day befor and the system was shutted down completely between. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094097 Title: Xorg crashed with SIGSEGV in mieqMoveToNewScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1094097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
This looks suspiciously similar to bug 1039341(which is marked fix released - but because the reporter couldn't reproduce) . Melchiaros: Can you reproduce this every time ? How is the monitor connected - VGA?DVI?HDMI? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094097 Title: Xorg crashed with SIGSEGV in mieqMoveToNewScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1094097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
MMh, yesterday I have attached a second screen to my system, but this crasher was without any additional screen today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094097 Title: Xorg crashed with SIGSEGV in mieqMoveToNewScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1094097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
