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 mieqMoveT
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
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 notificat
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, whi
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: Con
** 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
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 notificat
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:
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
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
Bug
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
11 matches
Mail list logo
