compiz/kwin freezes on login as of xorg-server 1.5.99.902-0ubuntu2

Same here with the same configuration (AMD64, nvidia 180).

Happens with both GNOME/Compiz and KDE/KWin.

Same here, amd64, nvidia 180 also.

x86 and nvidia 180 in my case. Included is Xorg log file (nothing out of the ordinary I can see).

Also lspci.

I've filed a new bug and then marked it as a duplicate of this one in order to provide my apport information: bug 326374. (Note that this is when running the -0ubuntu1 version, since I can't get into the desktop at all with the -0ubuntu2/3 versions.)

Dropping to nvidia 173 didn't change anything.

Not a compiz bug since kwin causes the same behaviour.

There's a workaround in duplicate bug https://bugs.launchpad.net/ubuntu/+bug/326363.

Bornio says:

Actual workaround:

1. Start your session
2. Go to terminal (ctrl+alt+F1) and kill compiz.real via killall compiz.real -s KILL
3. go back to your session (ctrl+alt+F7)
4. remove /dev/nvidiactl (this will be regenerated next time you restart GDM)
5. start compiz

Same behaviour with kwin kde4 (desktop effects enabled).
Kde4 freezes with xorg-server 1.5.99.902-0ubuntu3

With 1.5.99.902-0ubuntu1 kde4 effects works.

hello

Actual workaround:

1. Start your session
2. Go to terminal (ctrl+alt+F1) and kill compiz.real via killall compiz.real -s KILL
3. go back to your session (ctrl+alt+F7)
4. remove /dev/nvidiactl (this will be regenerated next time you restart GDM)
5. start compiz

this does not work here (nvidia 173.xx.xx)
but i managed to start with metacity and setup indirect rendering with fusion-icon .
then i restart the session > compiz and gnome could start normally.

hav a good day

zniavre - try to start a Guest session and enabling desktop affects from there. The guest account does not have permission to /dev/nvidiactl, and this should result in a working Compiz for that session.
If it ends up working in the Guest session, make sure you indeed removed /dev/nvidiactl .
You can try running glxgears which alert you with the following message:
"NVIDIA: could not open the device file /dev/nvidiactl (No such file or directory)."

Make sure, of course, that you are indeed running with the nVidia driver.

Thanks

I can confirm that this happened only after applying the xserver-xorg updates. I've been using nvidia 180.27 + Compiz for a couple of days wiith _no problem_, it wasn't until I rebooted today (after download/installing the xorg updates) that the problems began.

I too can recreate the same problem with KWin (it also freezes if desktop effects are enabled). "Compiz" should probably be removed from the title of this bug.

Kubnut9.04a4 (AMD64) & nvidia 180.27 (9800GTX+).

I have the same problem with nvidia 180.27 and kwin desktop effects enable. I use Kubuntu .04 Alpha-4.

gp

I went through all the recent bug reports and found/marked duplicates for this issue. It is, naturally, affecting a lot of people.

affects me as well. kwin with desktop effects is unusable... And I was just getting used to it too.

I have the same problem with nvidia 180.27 and kwin desktop effects enabled. I use Kubuntu 9.04.
As "workaround" i use nv drivers instead of nvidia.

the same thing at home,
I have graphics acceleration.
but after activation compiz fusion, I log into my session and I have just the wallpaper
I edit the xorg.conf and replacing nvidia with nv driver. and the probleme is solved.

The effect of deleting /dev/nvidiactl is just to force compiz to use indirect binding. You can accomplish this less destructively by running
  export LIBGL_ALWAYS_INDIRECT=1
  compiz &
or by putting this line in your ~/.gnomerc:
  export LIBGL_ALWAYS_INDIRECT=1

Also, I assume the XFIX workaround just switches to the nv driver instead of the nvidia driver. That isn’t very helpful, since then you lose 3D entirely.

@andrew even with compiz (and loose binding) and metacity composite off, I cant login.

Bisecting patches 157 - 160 blames patch 158_raise_maxclients.patch.

Without this patch compiz works fine again on jaunty / nvidia-glx-180.

I have the same issue since the last updates with Kubuntu Jaunty Alpha 4 & Nvidia 180.27.

After login, I see only the grey Splash Screen background picture and can move around the mousecurser. I have also tried to install compiz, and use it as the default window manager. It also don't work.

When I disable the desktop effects it's working without any problem.

Same here with Compiz in Ubuntu (GNOME)

Login freezes at wallpaper and trackpad stops responding on default Jaunty Alpha4 install after enabling either Nvidia driver 180 or 173. Manually killing compiz.real allows login to continue. Disabling Nvidia drivers for now.

The workaround that worked for me with kubuntu was to login with failsafe and install e16. Then exit failsafe and login with e16-kde. This then allowed me to start systemsettings>Desktop>Advanced and uncheck "Enable direct rendering". Then apply and log out. Then log back into kde with full effects.

I actually tried a bunch of things to get this working, but I believe what I posted above is what ended up working. I'm also sure there's a better way to do this, but I just needed any functional desktop at first to check email and stuff and randomly picked e16. Was just luck that it had the option of e16-kde for logging in. I'll try to check back here later and see if there's any questions about this.

The easiest/fastest way I found to get the system back workable with Kubuntu is:
- Try to log in
- ctrl-alt-f1 to a console when the login hangs
- kill -9 kwin or compiz.real (depending on which you use)
- Alt-F7 back to the GUI
- Use the cashew to add the Konsole Profiles plasmoid to the desktop.
- Use the plasmoid to start a shell and then run systemsettings
- In SystemSettings, disable desktop effects.

I tried only unchecking "Enable direct rendering", as dlanor78 mentioned above, but that did not work for me on Kubuntu 9.04a4 w/nvidia 180.27 (9800GTX+).

I forgot to mention that I'm not using the nvidia drivers from the repos. I compiled and installed my own and the version I have is 180.22 so maybe that's why disabling the direct rendering works me. Also using 9.04 64 bit (can't remember which one, maybe alpha 3?) and fully updated.

'export LIBGL_ALWAYS_INDIRECT=1' in ~/.gnomerc works for me, thanks. I'm using nvidia 180.27 drivers from the standard restricted drivers package.

Confirming that:

  echo 'export LIBGL_ALWAYS_INDIRECT=1' > ~/.gnomerc

and restarting worked for me, too. I'm using nvidia 180.27 from the repositories.

>Confirming that:
>
> echo 'export LIBGL_ALWAYS_INDIRECT=1' > ~/.gnomerc

>and restarting worked for me, too. I'm using nvidia 180.27 from the repositories.

I can't confirm this. In my Kubuntu with nvidia 180.27 must be disable desktop effects to works fine.
If I insert echo 'export LIBGL_ALWAYS_INDIRECT=1' in ~/.kderc , it's not works.

gp

On Monday 09 February 2009 13:50:25 Giuseppe Pennisi wrote:
> If I insert  echo 'export LIBGL_ALWAYS_INDIRECT=1'  in ~/.kderc , it's not
> works.

the echo 'export LIBGL_ALWAYS_INDIRECT=1' would be run from a
terminal/konsole.

the ~/.kderc file will have:

export LIBGL_ALWAYS_INDIRECT=1

It wont work if ~/.kderc has all of this: echo 'export LIBGL_ALWAYS_INDIRECT=1

I was trying to apply the workaround for kde, but i always got the error "Failed to activate desktop effects".
Here is what i did, to get this working:
1. Turn on "Enable desktop effects"
2. Switch to page "Advanced"
3. Turn off "Enable direct rendering"
4. Switch back to page "General"
5. "Enable desktop effects" is turned off, so turn on "Enable desktop effects" again
6. Press "Apply"

On lunedì 09 febbraio 2009 15:09:59 habtool wrote:
> On Monday 09 February 2009 13:50:25 Giuseppe Pennisi wrote:
> > If I insert  echo 'export LIBGL_ALWAYS_INDIRECT=1'  in ~/.kderc , it's
> > not works.
>
> the echo 'export LIBGL_ALWAYS_INDIRECT=1' would be run from a
> terminal/konsole.
>
> the ~/.kderc file will have:
>
> export LIBGL_ALWAYS_INDIRECT=1
>
> It wont work if ~/.kderc has all of this: echo 'export
> LIBGL_ALWAYS_INDIRECT=1

Yes, I have mistake to write here in launchpad. :-)
In truth I have written to you as.

gp

The only effect of 158_raise_maxclients.patch is raising MAXCLIENTS from 256 to 512. According to this post, that change is incorrect by itself; the XFD_SETSIZE and XFD_ANYSET definitions need to be increased in <X11/Xpoll.h> first (package x11proto-core-dev):

<http://lists.freedesktop.org/archives/xorg/2007-November/030348.html>

I confirmed that removing 158_raise_maxclients.patch in the latest package causes the problem to go away. That package is in my PPA: <https://launchpad.net/~anders-kaseorg/+archive/ppa>.

I then tried to fix the problem by applying this debdiff to x11proto-core, and rebuilding xorg-server against the fixed x11proto-core-dev. That didn’t work. But it is possible that many more things need to be rebuilt against this x11proto-core-dev first.

xorg-server 1.5.99.902-0ubuntu4 still fails

> xorg-server 1.5.99.902-0ubuntu4 still fails

Same results here: Linux mars 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:42:34 UTC 2009 x86_64 GNU/Linux

This bug was fixed in the package xorg-server - 2:1.5.99.902-0ubuntu5

---------------
xorg-server (2:1.5.99.902-0ubuntu5) jaunty; urgency=low

  * Revert 158_raise_maxclients.patch. Breaks -nvidia. Binary drivers FTL.
    (LP: #326344)

 -- Bryce Harrington <email address hidden> Mon, 09 Feb 2009 13:51:04 -0800

>> This bug was fixed in the package xorg-server - 2:1.5.99.902-0ubuntu5

Not for me it wasn't. Only disabling direct rendering has solved it for me. It's also made the desktop much more responsive, so I count it as a good thing.. :)

Mark, are you sure you’re actually running -0ubuntu5? To check, run
  grep ^xorg-server /var/log/Xorg.0.log
The package hasn’t even finished building yet in the Ubuntu archive, so I’m strongly suspicious.

I can confirm this, when I disable direct rendering, desktop-effects are back with 2:1.5.99.902-0ubuntu4. Don't know if it works with ubuntu3 too. I haven't try this.

Both are working, kwin and compiz here on Kubuntu Jaunty.

>> This bug was fixed in the package xorg-server - 2:1.5.99.902-0ubuntu5 <<

Does it mean that with 2:1.5.99.902-0ubuntu5 I can turn on direct rendering again?

On Sun, Feb 08, 2009 at 06:19:48AM -0800, Albert Damen wrote:
> Bisecting patches 157 - 160 blames patch 158_raise_maxclients.patch.
>
> Without this patch compiz works fine again on jaunty / nvidia-glx-180.

MAXCLIENTS is defined in resource.h, which is part of the server's ABI.
You can't just change this number without also changing the ABI version and
recompiling any modules that use it. In particular, this change causes
libglx to overrun some memory, corrupting who knows what. While we can
probably work around this particular problem, I don't think we want to get
into the habit of supporting arbitrary unofficial changes to the server
ABI. If you do think the ABI needs to be changed, please discuss it on
<email address hidden>. There's a discussion in progress right
now about how to properly increase MAXCLIENTS without breaking other apps
that rely on having a lot of resource IDs available:

  http://lists.freedesktop.org/archives/xorg-devel/2009-February/000039.html

This patch needs to be reverted.

We don’t need anyone to confirm this again. The problem is fixed (or will be, as soon as 0ubuntu5 hits the archive—this will take several hours). Yes, you will be able to turn on direct rendering again.

  Adding the line "export LIBGL_ALWAYS_INDIRECT=1" in the ~/.kderc file and rebooting the system solved the problem for me. Desktop effects are enabled and works.
  Thanks.

xorg-server 1.5.99.902-0ubuntu5 fixes it for me

Here too, kwin's effects are back.

My email update from over an hour ago hasn't shown up yet, so reposting through the web interface:

On Sun, Feb 08, 2009 at 06:19:48AM -0800, Albert Damen wrote:
> Bisecting patches 157 - 160 blames patch 158_raise_maxclients.patch.
>
> Without this patch compiz works fine again on jaunty / nvidia-glx-180.

MAXCLIENTS is defined in resource.h, which is part of the server's ABI.
You can't just change this number without also changing the ABI version and
recompiling any modules that use it. In particular, this change causes
libglx to overrun some memory, corrupting who knows what. While we can
probably work around this particular problem, I don't think we want to get
into the habit of supporting arbitrary unofficial changes to the server
ABI. If you do think the ABI needs to be changed, please discuss it on
<email address hidden>. There's a discussion in progress right
now about how to properly increase MAXCLIENTS without breaking other apps
that rely on having a lot of resource IDs available:

  http://lists.freedesktop.org/archives/xorg-devel/2009-February/000039.html

This patch needs to be reverted.

Oh yeah, and I forgot to correct the text: MAXCLIENTS is actually defined in misc.h, not resource.h, but it's still part of the ABI.

Great job getting the fix out - working fine again now. Many thanks to all involved.

Solved for me.

xorg-server 1.5.99.902-0ubuntu5 fixes it for me .
Thanks

Giuseppe

Solved for me... but introduced a new bug. My desktop theme is now partially not working (see the title bar in captures attached), while it was perfectly working with the "export LIBGL_ALWAYS_INDIRECT=1" trick...

Solved for me as well, no problems with title bar so far

Mathieu, that's bug in latest metacity package.

update to xorg-server 1.5.99.902-0ubuntu5 fixed it for me
but there is still a lag between the apperence of the wallpaper and the apearence of the panels and a working desktop

update to xorg-server 1.5.99.902-0ubuntu5 fixed it for me
but there is still a lag between the appearance of the wallpaper and the appearance of the panels and a working desktop

>>Mark, are you sure you’re actually running -0ubuntu5

Whoops. When I saw the post saying it had been fixed, I assumed that the update to x11 I'd received a few minutes previously was that update. It wasn't. My apologies.

Thanks all for your enthusiasm, but this bug has now been confirmed fixed by more people than I can count. Please do not make further comments on this bug unless (1) you are sure you are running 1.5.99.902-0ubuntu5 (check with `grep ^xorg-server /var/log/Xorg.0.log`), and (2) you are seeing the SAME problem (you see only wallpaper when you log in).

Different problems should be reported as different bugs: <https://bugs.launchpad.net/ubuntu/+filebug>

Again, do not comment on this bug. Thanks.