glxinfo crashed with SIGSEGV

Bug #185785 reported by warmrobot
854
This bug affects 61 people
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

just in startup of desktop after yesteday update via update-manager

Tags: apport-crash
Revision history for this message
warmrobot (imfrolov) wrote :
Revision history for this message
warmrobot (imfrolov) wrote :

And again in this moment. System was loaded, but this bug annoying.

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_dl_close () from /lib/ld-linux.so.2
dlclose_doit () from /lib/tls/i686/cmov/libdl.so.2
_dl_catch_error () from /lib/ld-linux.so.2
_dlerror_run () from /lib/tls/i686/cmov/libdl.so.2
dlclose () from /lib/tls/i686/cmov/libdl.so.2

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi imfrolov,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in mesa:
status: New → Incomplete
Revision history for this message
warmrobot (imfrolov) wrote : Re: [Bug 185785] Re: glxinfo crashed with SIGSEGV

Hi, Bryce!

Everything OK for me and issue had been resolved long time ago. Thanks
for your care.

Igor.

Bryce Harrington пишет:
> Hi imfrolov,
>
>
> Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)
>
> If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
> Thanks in advance.
>
>
> The output of lspci -vvnn would also be worth having.
>
>
> ** Changed in: mesa (Ubuntu)
> Status: New => Incomplete
>
>

Revision history for this message
Francesco Usseglio (francescousseglio) wrote :

Hi all,
mee too, I have upgraded and the bug has gone.

Thank you

Il giorno ven, 24/10/2008 alle 06.47 +0000, warmrobot ha scritto:
> Hi, Bryce!
>
> Everything OK for me and issue had been resolved long time ago. Thanks
> for your care.
>
>
> Igor.
>
> Bryce Harrington пишет:
> > Hi imfrolov,
> >
> >
> > Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)
> >
> > If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
> > Thanks in advance.
> >
> >
> > The output of lspci -vvnn would also be worth having.
> >
> >
> > ** Changed in: mesa (Ubuntu)
> > Status: New => Incomplete
> >
> >
>

Revision history for this message
Payteer (prowan) wrote :

This has been resolved with me as well.

thanks,
Payteer

On Fri, 2008-10-24 at 07:15 +0000, Cecco wrote:
> Hi all,
> mee too, I have upgraded and the bug has gone.
>
> Thank you
>
> Il giorno ven, 24/10/2008 alle 06.47 +0000, warmrobot ha scritto:
> > Hi, Bryce!
> >
> > Everything OK for me and issue had been resolved long time ago. Thanks
> > for your care.
> >
> >
> > Igor.
> >
> > Bryce Harrington пишет:
> > > Hi imfrolov,
> > >
> > >
> > > Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)
> > >
> > > If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
> > > Thanks in advance.
> > >
> > >
> > > The output of lspci -vvnn would also be worth having.
> > >
> > >
> > > ** Changed in: mesa (Ubuntu)
> > > Status: New => Incomplete
> > >
> > >
> >
>

Revision history for this message
Rodrigo (rvportugal) wrote :

It happened after system Settings -> Desktop -> Multiple Desktops. I just had a crash a few minutes ago trying to install the proprietary ATI video driver.

Revision history for this message
Bryce Harrington (bryce) wrote :

Great to hear! Thanks for letting us know the issue is resolved, I'll close it.

Changed in mesa:
status: Incomplete → Fix Released
Revision history for this message
MartinB (martin-burman) wrote :

Hi, it's still an issue here.

If I blank the LD_LIBRARY_PATH environment variable all glx apps seems
to work fine (including Compiz).

If I blank out the LD_LIBRARY_PATH in all startup scripts the graphical
performance in X becomes really poor.

Attaching the requested files.

Best regards
Martin

On Fri, 2008-10-24 at 05:40 +0000, Bryce Harrington wrote:
> Hi imfrolov,
>
>
> Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)
>
> If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
> Thanks in advance.
>
>
> The output of lspci -vvnn would also be worth having.
>
>
> ** Changed in: mesa (Ubuntu)
> Status: New => Incomplete
>

jean-marc (jmpain)
description: updated
Revision history for this message
cRoW2k (crow2k) wrote :

After upgrade Intrepid to jaunty and changed the ati driver (now i'm using ati and not fglrx)

Revision history for this message
Leo (leillo1975) wrote :

I have this problem when I try to activate compiz effects in Visual effects

I have a sapphire ATI HD2600 Pro AGP

Revision history for this message
bambou51 (bambou51-gmail) wrote :

FYI I have the same problem on my laptop with an ATI XPress 200M.

It was working flawlessly with intrepid Ibex.

Leo wrote:
> I have this problem when I try to activate compiz effects in Visual
> effects
>
> I have a sapphire ATI HD2600 Pro AGP
>
>

Revision history for this message
Peter Dietz (pdietz84) wrote :

I just ran [update-manager -d] from 8.10, which installed a 9.04 (pre-release). During the first system reboot after install, after grub it tried to load the ubuntu progress meter, then resorted to the shell showing all the daemons loading, took a while for the fglrx portion, then prompted me that the system will run in reduced graphics mode, I tried to reconfigure, but it said to restart. Had to do some ctrl+alt+del or ctrl+bkspce to get the system to restart.

ATI Radeon 4850 with the proprietary drivers loaded :( , Upon reboot I was able to go into display and set my graphical setting via ubuntu and it works now.

Revision history for this message
amoalsale (amol-joyoflinux) wrote :

I received this crash after upgrading to 9.04.

Revision history for this message
Jose.Torres (jose-torres) wrote :

I as well. Please let me know if I can provide any more information.

Revision history for this message
Joachim R. (jro) wrote :

Occurs on Ubuntu 9.04 beta2 amd64 (fresh new install) in VirtualBox with client addition (3D acceleration activated) after each startup.

Revision history for this message
Pedro Fausto R. Leite Jr. (pedrofausto) wrote :

I have the same configuration and enviroment as mentioned by the user Joachim R., but I'm using the free ATI driver by now and is OK until now.

Revision history for this message
Joachim R. (jro) wrote :

After some tests, I see the same error in VirtualBox with Ubuntu 9.04b2 x386.
After some investigation, the cause is (for both 9.04b2 x86 and amd64) the presence of drm modules added by "virtual box guest additions" while the checkbox "3D acceleration" is not ticked in VM preferences.
I also learn that you cannot tick "3D acceleration" on many VM at the same time (even if they are not launched at the same time).

So if 3D acceleration is not ticked (or automatically unticked by vbox), launching Ubuntu with the guest addition modules that enable direct rendering makes glxinfo crash at session start.
If you launch glxinfo "manually" (term) in these conditions, the first lines diplay a warning about driect rendering not possible then you get all glxinfo stuff.

Conclusion : a small bug remain : if glxinfo is able to display a warning without crashing when launched in a term, why does it crash at session start ?

Revision history for this message
Nikolaj Sheller (nikolajsheller) wrote :

Running under Karmic alpha 4 AMD64 in a Virtualbox with compositing enabled I see this issua, and also get bug 321041. Perhaps there is a relation?

To post a comment you must log in.