Unity 3D desktop crashes in Oneiric using ATI Mobility Radeon X1600

By the way, Widgets Layer, and Zoom Desktop are both off. And the extra non-default compiz plugins are not being used at all, although installed.

Last thing, the Window Rules plugin in the CompizConfig Settings Manager was enabled, with the rule "title=Dash" for the Above match. I'm disabling it, because I don't need it.

Thanks for your bug report. I believe xorg is the correct package to report this against, as it involves the user being thrown back to the login screen (https://wiki.ubuntu.com/Bugs/FindRightPackage#Graphical_Environment), but the fact that the problem doesn't occur in an Ubuntu-2d session would seem to suggest Compiz may be at fault. I'm going to file this against xorg for now, though, per the wiki page. Please run the following command in a terminal in order to get additional information relevant to your system attached to this report:
apport-collect 888872

apport-collect 888872

All I get is a Invalid OpenID transaction message.

Could you please try clearing the cache and cookies of your default browser and trying the command again?

I was hoping that the new compiz upgrade would have taken care of the issue I'm describing, but it doesn't.

I don't think it's an X11 issue or else I'd have the same problem with 2d Unity and certainly with Gnome shell or any of the other Gnome desktops (3D or 3D). From my testing, mostly Gnome shell, it's not an issue on any of the Gnome environments. So it stands to reason the problem is with the Unity plugin itself.

The only possible sign of an X issue is when logging out, my screen goes black and momentarily shows a terminal/console before *DM kicks in. I'm not sure if that should happen and if it isn't supposed to it's an instance of X crashing. Having said that, even if this black out is a valid X issue, I don't think it's related to the bug at hand because the bug at hand behaviour does NOT occur in Gnome shell + (as well as not occurring under Unity 2D).

It's clearly a Unity 3D bug.

To avoid confusion, allow me to clarify ...

The possible X bug, NOT the focus of this bug report, occurs while logging out, shutting down, or rebooting.

The bug at hand behaviour is a crash that occurs during normal operation within an running desktop environment, Unity 3D.

It's strange that this problem only manifests itself in a Unity 3d session, yes. However this fits the description of an X problem as described in the Wiki quite well, so I still think we should keep a report against xorg open. When the Unity maintainers get around to looking at this report they can make a final decision regarding what is at fault.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

@ Phil. V (philip.v)

I found that LIBGL_DEBUG=verbose glxinfo reports some errors:

libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/r300_dri.so
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/user/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/user/.drirc: No such file or directory.

I did some digging around and found that http://dri.freedesktop.org/wiki/glxinfo mentions "Surrounding these lines there may be additional messages indicating errors. In particular, if the driver is not found in the mentioned path, OpenGL will try to fall back to the software renderer called swrast_dri.so. This is an indication that the DRI drivers are not installed correctly."

So it seems, although I don't know if it's related to the problem at hand, Ubuntu has a problem correctly installing DRI drivers. If it's not related I could open a bug on the matter.

glxinfo | grep render

direct rendering: Yes
OpenGL renderer string: Gallium 0.4 on ATI RV530
    GL_NV_conditional_render, GL_ARB_draw_elements_base_vertex,

uname -r
3.0.0-13-generic

@Chascon

Huh, it's possible that's related, but to be honest I just don't know enough about the affected systems to determine if those two issues are related, I'm just a bug triager. Feel free to open another report regarding the problem with installing DRI drivers and mention this bug, and hopefully someone more informed can make the determination as to whether these two problems are related. Sorry I couldn't be of more help.

if its a crash you should look into /var/crash directory and look for the file including the name 'compiz' in it, double click it and follow the onscreen instructions to report a new crash report which hopefully will have logs about the crash and could possible turn out to be a duplicate of an already reported crash report.

I found and tried out a fix and made up my own version of it.

I noticed that Xorg.0.log.old gave the following.
Segmentation fault at address 0xb6211008
Caught signal 11 (Segmentation fault). Server aborting

Googling for "Caught signal 11 (Segmentation fault). Server aborting" shows that Archlinux has had this issue too (https://bbs.archlinux.org/viewtopic.php?id=119442). Based on that, the following work-around works for me.

Create /usr/share/X11/xorg.conf.d/10-modules.conf with the following content.

Section "Module"
             Disable "record"
EndSection

Otherwise (my way)
Log out,
then from a tty, kill lightdm, and
issue sudo Xorg -configure or sudo X -configure.

In the resulting xorg.conf, make sure to Disable "record" rather than just comment the line out.
Copy it to /etc/X11/
Restart lightdm
Log into X (although it didn't take for me till I logged out and back into X yet again, so you may just want to reboot).

The result: no more crashes and X seems a little more responsive, although this may be in my mind. There's an error pop up at the start of the X session about the record function not working, but that is expected. So I assume that may the the problematic software.

I also noticed that Xorg.0.log and other logs give me the following error.
(EE) Failed to load module "fglrx" (module does not exist, 0)

I thought it might be unimportant if it weren't for a segmentation fault linked to fglrx reported at http://phoronix.com/forums/showthread.php?22972-Ubuntu-10.04-fglrx-seg-fault.

 I'll write it up as a separate bug, anyway since Ubuntu borked my fglrx install .

So how's that for incomplete? A workaround and potential sources of the bug are ID'd.

A little more on that error popup. It's from GoldenDict and tehy've been aware of Record being broken for sometime now, although from 2009 (so this might not be applicable or it might indicate a regression):
https://github.com/gennady/goldendict/commit/230ab47891283216d3abd43fbb66b8f27125ec1b

There is a fix noted in https://bbs.archlinux.org/viewtopic.php?id=120240
that suggests increasing nproc limits to 1500 (hard). I haven't tried this as I'm not sure what nproc to change. I have various nprocs with low figures listed in/etc/security/limits.conf and I don't know which one to edit, student, faculty or ftp (I doubt it would be this ftp).

In any case, I doubt changing the limits would help considering that the Gnome shell doesn't crash using the same file limits file.

thanks for your bug report. Is that still an issue in Ubuntu 12.04? Can you please test that and let us know?

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.

We couldn't reproduce this bug + oneiric is not supported anymore, therefore I set the status to Invalid. If you experience the same issue in any of the supported Ubuntu releases please feel free to reopen the bug and update the description. Thank you.