[Bug 549155] Re: X suddenly closes (abort) with a SIGQUIT

2010-04-06 Thread C de-Avillez
back into New, keeps on happening. There is https://bugs.freedesktop.org/show_bug.cgi?id=26689 matching my symptoms. For the record, this is a Beta2 Lucid. ** Bug watch added: freedesktop.org Bugzilla #26689 http://bugs.freedesktop.org/show_bug.cgi?id=26689 ** Changed in: xorg-server

[Bug 549155] Re: X suddenly closes (abort) with a SIGQUIT

2010-04-06 Thread Bryce Harrington
[Crash bug reports without full backtraces cannot be analyzed] ** Changed in: xorg-server (Ubuntu) Status: New = Invalid -- X suddenly closes (abort) with a SIGQUIT https://bugs.launchpad.net/bugs/549155 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 549155] Re: X suddenly closes (abort) with a SIGQUIT

2010-04-05 Thread Robert Hooker
Please update your system fully, this was a plymouth problem that was fixed quite some time ago and it was pressing enter or 2 that triggered it. If with a fully upgraded lucid environment it is still happening please reopen this bug. ** Changed in: xorg-server (Ubuntu) Status: Incomplete

Re: [Bug 549155] Re: X suddenly closes (abort) with a SIGQUIT

2010-04-05 Thread C de-Avillez
On Mon, 2010-04-05 at 14:01 +, Robert Hooker wrote: Please update your system fully, this was a plymouth problem that was fixed quite some time ago and it was pressing enter or 2 that triggered it. If with a fully upgraded lucid environment it is still happening please reopen this bug.

[Bug 549155] Re: X suddenly closes (abort) with a SIGQUIT

2010-04-03 Thread Bryce Harrington
Hmm, well there is a backtrace so this is definitely an X crash (or maybe libc bug) but the limited backtrace isn't giving us much information. Are you able to reproduce this issue relatively frequently? If so, please collect a full backtrace - see http://wiki.ubuntu.com/X/Backtracing for

[Bug 549155] Re: X suddenly closes (abort) with a SIGQUIT

2010-04-03 Thread Carlos de-Avillez
I will try. Although... it sounds like apport does not trigger on SIGQUITs, or that the X internal trap analysis blocked it. I have been having two, perhaps related, issues: * SIGQUIT followed by an immediate restart of X * full freeze -- in this situation, keyboard is totally unresponsive, and

[Bug 549155] Re: X suddenly closes (abort) with a SIGQUIT

2010-03-30 Thread Bryce Harrington
** Changed in: xorg-server (Ubuntu) Status: New = Confirmed -- X suddenly closes (abort) with a SIGQUIT https://bugs.launchpad.net/bugs/549155 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 549155] Re: X suddenly closes (abort) with a SIGQUIT

2010-03-27 Thread Bryce Harrington
** Package changed: xorg (Ubuntu) = xorg-server (Ubuntu) -- X suddenly closes (abort) with a SIGQUIT https://bugs.launchpad.net/bugs/549155 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 549155] Re: X suddenly closes (abort) with a SIGQUIT

2010-03-26 Thread C de-Avillez
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/42109627/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/42109628/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42109629/Dependencies.txt **