[Bug 1218927] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()

2014-01-07 Thread Christopher M. Penalver
Tobiasz Jarczyk, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from

[Bug 1218927] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()

2014-01-07 Thread Tobiasz Jarczyk
Hi, I was not able to reproduce the issue in trusty. Thanks, Tobiasz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218927 Title: Xorg crashed with SIGABRT in mieqMoveToNewScreen() To manage

[Bug 1218927] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()

2014-01-07 Thread Christopher M. Penalver
Tobiasz Jarczyk, thank you for performing the requested test. Would you need a backport to a release prior to Trusty, or may this be closed as Status Invalid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1218927] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()

2014-01-07 Thread Tobiasz Jarczyk
Christopher M. Penalver, I believe backporting is not needed as I was the only one affected. Thanks, Tobiasz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218927 Title: Xorg crashed with SIGABRT

[Bug 1218927] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()

2014-01-07 Thread Christopher M. Penalver
Tobiasz Jarczyk, thank you for your comment. Backporting isn't dependent on the number of people affected, but if the need exists for the person(s) affected. Hence, if the problem is still reproducible in Saucy, would you be using Trusty going forward, or would you need a backport? -- You

[Bug 1218927] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()

2014-01-07 Thread Tobiasz Jarczyk
Christopher M. Penalver, I am using Trusty for my day to day activities. My other machines running Saucy are not affected AFAIK. So I believe we can close the bug with Invalid status. Best regards, Tobiasz -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1218927] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()

2014-01-07 Thread Christopher M. Penalver
Tobiasz Jarczyk, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1218927/comments/12 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in

[Bug 1218927] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()

2013-09-26 Thread Timo Aaltonen
** Changed in: xorg-server (Ubuntu) Importance: Medium = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218927 Title: Xorg crashed with SIGABRT in mieqMoveToNewScreen() To manage

[Bug 1218927] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()

2013-09-07 Thread Launchpad Bug Tracker
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/1218927 Title:

[Bug 1218927] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()

2013-08-30 Thread Tobiasz Jarczyk
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218927 Title: Xorg crashed with SIGABRT in mieqMoveToNewScreen() To manage notifications about