[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2010-01-20 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu/lucid/apport/ubuntu -- glxgears crashed with SIGSEGV due to no GLX on display :0 https://bugs.launchpad.net/bugs/327673 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu.

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2010-01-20 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 1.12-0ubuntu1 --- apport (1.12-0ubuntu1) lucid; urgency=low * New upstream release: - launchpad.py: Add options 'escalation_subscription' and 'escalation_tag' for handling bugs with more than 10 duplicates. - crashdb.conf:

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2010-01-14 Thread Martin Pitt
I just tested this here by moving away libglx.so, and glxinfo does not crash any more, so I am closing the original bug. I also determined that extension GLX missing on display is just written to stderr by Xlib, it does not appear in Xorg.0.log. Thus the apport hook can't grep for that. Instead,

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2010-01-14 Thread Launchpad Bug Tracker
** Branch linked: lp:apport -- glxgears crashed with SIGSEGV due to no GLX on display :0 https://bugs.launchpad.net/bugs/327673 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2010-01-14 Thread Martin Pitt
trunk r1697 ** Changed in: apport (Ubuntu) Status: In Progress = Fix Committed -- glxgears crashed with SIGSEGV due to no GLX on display :0 https://bugs.launchpad.net/bugs/327673 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2010-01-03 Thread Martin Pitt
OK, will add a check like in comment 7 to the ubuntu general hook. ** Changed in: apport (Ubuntu) Status: Incomplete = In Progress ** Changed in: apport (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- glxgears crashed with SIGSEGV due to no GLX on display :0

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2009-12-24 Thread Bryce Harrington
** Changed in: mesa (Ubuntu) Importance: Undecided = Low -- glxgears crashed with SIGSEGV due to no GLX on display :0 https://bugs.launchpad.net/bugs/327673 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu.

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2009-12-23 Thread Martin Pitt
Still waiting for an answer from Bryce to comment 7 ** Changed in: apport (Ubuntu) Milestone: lucid-alpha-1 = None -- glxgears crashed with SIGSEGV due to no GLX on display :0 https://bugs.launchpad.net/bugs/327673 You received this bug notification because you are a member of Ubuntu-X,

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2009-12-23 Thread Bryce Harrington
pitti, yes these crashes can be ignored when GLX is missing. Certainly it's an issue that glxgears isn't checking for GLX, but this is an uncommon corner case, and glxgears is sort of just a test program anyway, so this isn't a priority to get fixed. We can just ignore these crashes. --

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2009-11-09 Thread Brian Murray
** Changed in: apport (Ubuntu) Milestone: None = lucid-alpha-1 -- glxgears crashed with SIGSEGV due to no GLX on display :0 https://bugs.launchpad.net/bugs/327673 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu.

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2009-09-16 Thread Kees Cook
** Description changed: I believe that glxgears crashed because I don't have glx running at the moment: Xlib: extension GLX missing on display :0.0. However, if this is the case it'd make much more sense if apport, in the form of a per package hook, did not allow these crash

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2009-09-02 Thread Martin Pitt
But should a program really crash if it relies on glx and it's not available? It should handle this condition more gracefully IMHO. Bryce, what should apport do here? Is it safe to say that it should ignore _all_ crashes which end in libGL if 'extension GLX missing on display' occurs in

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2009-09-02 Thread Bryce Harrington
** Tags added: jaunty -- glxgears crashed with SIGSEGV due to no GLX on display :0 https://bugs.launchpad.net/bugs/327673 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list:

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

2009-08-21 Thread Bryce Harrington
Okay, well the stacktrace is not analyzable but rather than closing the bug I'll bump it over to apport to look into improving support for this class of bug. ** Package changed: mesa (Ubuntu) = apport (Ubuntu) -- glxgears crashed with SIGSEGV due to no GLX on display :0