[Bug 158761] Re: [gutsy] x sometimes crashes on resume from suspend

2008-05-25 Thread unggnu
We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future. To reopen the bug report you

[Bug 158761] Re: [gutsy] x sometimes crashes on resume from suspend

2008-03-26 Thread Bryce Harrington
Bram, your backtrace also does not match up to Ryan's so is likely an unrelated bug. Please report it separately. It would be great if you could get a 'full backtrace'. You can ssh into the box when it has crashed from another system and attach gdb to Xorg to get it. (see

[Bug 158761] Re: [gutsy] x sometimes crashes on resume from suspend

2008-02-11 Thread Bram Borggreve
Here is my backtrace, on a HP/Compaq nx6110 laptop. 00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03) Backtrace: 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c95d1] 1: [0xe420] 2: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b46022] 3:

[Bug 158761] Re: [gutsy] x sometimes crashes on resume from suspend

2008-02-06 Thread Bryce Harrington
Shiv, your issue looks to be unrelated to Mario's (the backtraces dont' match up). If you're running on Gutsy, the xserver we shipped in it didn't support EXA with -intel. Please re-test against Hardy, which should allow loading exa. Mario, could you also test against Hardy to see if the crash

[Bug 158761] Re: [gutsy] x sometimes crashes on resume from suspend

2008-01-20 Thread Shiv V
I have a very similar issue ... X crashes on resume from suspend-to-RAM, so I lose my session and end up at the login screen. This only seems to happen when compiz is running. Here is the backtrace from /var/log/Xorg.0.log. I'm running gutsy on a MacBook Pro Core 2 Duo with the fglrx driver

[Bug 158761] Re: [gutsy] x sometimes crashes on resume from suspend

2008-01-20 Thread Shiv V
Seems related to https://bugs.launchpad.net/ubuntu/+source/linux- restricted-modules-2.6.22/+bug/165093 -- [gutsy] x sometimes crashes on resume from suspend https://bugs.launchpad.net/bugs/158761 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug

[Bug 158761] Re: [gutsy] x sometimes crashes on resume from suspend

2008-01-08 Thread Bryce Harrington
Backtrace: 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581] 1: [0xe420] 2: /usr/lib/xorg/modules//libfb.so(fbFillRegionSolid+0xd5) [0xb7afbd75] 3: /usr/lib/xorg/modules//libfb.so(fbPaintWindow+0xb3) [0xb7afbed3] 4: /usr/lib/xorg/modules//libxaa.so(XAAPaintWindow+0x150) [0xb7aa11a0] 5: /usr/bin/X

[Bug 158761] Re: [gutsy] x sometimes crashes on resume from suspend

2008-01-08 Thread Bryce Harrington
Please test against Hardy alpha2 or newer to see if the crash still occurs. Fwiw, XAA acceleration (which appears to be involved in this crash) will be deprecated in favor of EXA. So I suspect this crash will not be present as of Hardy alpha2. If you can confirm that, it'd be a great help. **

[Bug 158761] Re: [gutsy] x sometimes crashes on resume from suspend

2007-12-30 Thread Timo Aaltonen
** Changed in: xserver-xorg-video-intel (Ubuntu) Sourcepackagename: xorg = xserver-xorg-video-intel -- [gutsy] x sometimes crashes on resume from suspend https://bugs.launchpad.net/bugs/158761 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact

[Bug 158761] Re: [gutsy] x sometimes crashes on resume from suspend

2007-10-30 Thread Ryan Lortie
** Attachment added: x-is-unhappy.log http://launchpadlibrarian.net/10216105/x-is-unhappy.log -- [gutsy] x sometimes crashes on resume from suspend https://bugs.launchpad.net/bugs/158761 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for

[Bug 158761] Re: [gutsy] x sometimes crashes on resume from suspend

2007-10-30 Thread Mario Young
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW]