[Ubuntu-x-swat] [Bug 1165867] Re: Xorg crashed with SIGABRT in raise() Address 0x7f669c3b1e58 out of bounds

2013-05-07 Thread Apport retracing service
** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1165867 Title: Xorg crashed with SIGABRT in raise() Address 0x7f669c3b1e58 out of bounds

[Ubuntu-x-swat] [Bug 1165867] Re: Xorg crashed with SIGABRT in raise() Address 0x7f669c3b1e58 out of bounds

2013-04-22 Thread Bryce Harrington
** Summary changed: - Xorg crashed with SIGABRT in raise() + Xorg crashed with SIGABRT in raise() Address 0x7f669c3b1e58 out of bounds ** Description changed: after every logon, the message appears + + #3 0x7f66a2bf7223 in AbortServer () at ../../os/log.c:655 + No locals. + #4

[Ubuntu-x-swat] [Bug 1165867] Re: Xorg crashed with SIGABRT in raise()

2013-04-12 Thread Jamie Strandboge
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross

[Ubuntu-x-swat] [Bug 1165867] Re: Xorg crashed with SIGABRT in raise()

2013-04-07 Thread Uwe Neubarth
** Information type changed from Private to Public Security -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1165867 Title: Xorg crashed with SIGABRT in raise() To manage