With desktop effects enabled when using gksu system gets grey and only responds to keyboard

Bug #106008 reported by António Lima
68
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Fix Released
High
Unassigned

Bug Description

I have a ati graphic card with oss divers. When I activate the desktop effects in feisty and try to make some administrative task (and have to enter my root password), my system stays with all grey and does not respond to mouse. Also the administrative application (for ex. synaptic) apparently does not start. Doing alt+F4 usually closes the application and the makes the system get back to normal but synaptic is not open (of course... I know, i closed it :)).
I have feisty up to date today (12/04/2007).

Revision history for this message
António Lima (amrlima) wrote :
António Lima (amrlima)
description: updated
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

If you go to a VT, and do "killall gksu", does it solve the problem?

Changed in compiz:
status: Unconfirmed → Needs Info
Revision history for this message
António Lima (amrlima) wrote :

Yes, going to a VT and making "killall gksu", when returning to my X session I no longer have the look down. Of course after a reboot, the problem persists.

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Then this is a gksu problem. I have also noticed it sometimes, without compiz.

Changed in compiz:
importance: Undecided → High
status: Needs Info → Confirmed
Revision history for this message
Sebastian Heinlein (glatzor) wrote :

Disabling the desktop effects results in a working gksu?

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Sebastian:

It happens to me when running metacity, not compiz.

Revision history for this message
António Lima (amrlima) wrote :

Sebastian:

With me, disabling desktop effects results in a working gksu.

Revision history for this message
António Lima (amrlima) wrote :

Doing a fresh feisty install solved my problem with gksu/compiz.

Revision history for this message
thomaslz (thomaslzp) wrote :

Think this is a BUG, it happens to me in compiz and gksu. anyone knows how to fix it?
I am on a IBM X60 with i945 card.

regards,

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Moving back to compiz, since everybody have it with it enabled. I should have my profile bad somehow.

Revision history for this message
LKRaider (paul-eipper) wrote :

I have the exact same issue on Feisty + Nvidia legacy driver + Xgl + Compiz

If I instead run Xorg + Metacity, the issue is gone.

My workaround is CTRL+ALT+F1 to switch to a tty and do killall gksu. That returns the system into a responsive state and also opens the app I requested.

Otherwise, if I wait long enough (a few minutes), gksu finishes and the app runs.

Revision history for this message
David Spicer (david-spicer) wrote :

Adding the -g option to gksu, e.g. "gksu -g /usr/sbin/synaptic", works around the problem here.

Revision history for this message
kaptengu (kaptengu) wrote :

Same thing for me.
Greyed out with IBM X41, Feisty, Compiz, Administrative task.
Works well with desktop effects inactivated.
gksu -g works for me.

Revision history for this message
sam tygier (samtygier) wrote :

seem that it is fixed with recent updates (nvidia + compiz)

there are a lot of subscribers, so i don't want to mark fixed, just because it seems ok here

Revision history for this message
Wolf Rogner (war-rsb) wrote :

but still here with the originally posted ati graphics card

Revision history for this message
godDLL (ycherkashin) wrote :

I also had this issue with Feisty, Beryl and ATI Radeon OSS driver. A switch to Compiz-Fusion solved this and many other issues.

Revision history for this message
Peter Würtz (pwuertz) wrote :

For me, a switch to compiz-fusion caused the problem you described. My system is up-to-date, running with nvidia-glx-new drivers and is using a compiz-fusion repository being updated daily.

I just switched from nvidia-glx to nvidia-glx-new on another machine also having compiz-fusion installed. In both cases the bug did not appear.

So I have 2 systems with same drivers and same software, one showing the bug, one without any problems.

Revision history for this message
Travis Watkins (amaranth) wrote :

Is anyone currently seeing this problem on an up-to-date gutsy system? I believe I fixed it (in gksu).

Changed in compiz:
status: Confirmed → Incomplete
Revision history for this message
sam tygier (samtygier) wrote :

seems fixed here.

if anyone is still suffering, they can reopen the bug.

Changed in compiz:
status: Incomplete → Fix Released
Revision history for this message
billytalent (billytalent) wrote :

I get this bug too and my ubuntu is upto date (20th Aug, 2007) with Feisty Fawn. Is there a resolution to this problem ?

Revision history for this message
Travis Watkins (amaranth) wrote :

The fix is only in gutsy.

Revision history for this message
hmsf (heliomsf) wrote :

I was having exactly the same issue, it started suddenly and I couldn't discover the reason. Solved it by running gconf, then apps-->gksu and marking the option 'disable-grab'. It's basically the same as adding the -g option to gksu. But this way makes it automatic for all administrative applications...

Revision history for this message
Gelke (gbroersma-orange) wrote :

I still have the problem with a fully updated gutsy.

I have a nvidia geforce 8400GS

Revision history for this message
Gelke (gbroersma-orange) wrote :

After reading what this bug ment it's not the same as what i have.

This is another bug repport https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/99313, it's says it's a duplicate of this one, but it's not.

Revision history for this message
Gelke (gbroersma-orange) wrote :

Well, the fix you gave worked, so nevermind what i said.

Revision history for this message
Nadir (nad4reg) wrote :

Hi,
I had the same problem and I fixed it by editing /usr/share/menu/synaptic and changing the command to "/usr/bin/gksu -g /usr/sbin/synaptic" (added the -g)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.