gksudo launched applications open behind other windows

Bug #31487 reported by Jane Silber
178
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gksu (Ubuntu)
Fix Released
Medium
Michael Vogt

Bug Description

When starting Synaptic (System->Admin->Synaptic), the application window opens *behind* any other open apps. This seems like odd default behavior - most (all?) other apps start on top of open windows, which I think would be the user's desired result from starting an app.

Sebastian:
Some additional keywords so that we hopefully get less duplicates:
focus, background, foreground, maximize

Changed in synaptic:
assignee: nobody → mvo
Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your

This seems to be a gksu bug, we are investigating what exacly caused the problem.

Cheers,
 Michael

Michael Vogt (mvo)
Changed in synaptic:
status: Unconfirmed → Confirmed
Revision history for this message
sam tygier (samtygier) wrote :

this appears to happen with all applications launched with gksudo (ie all the system -> administration programs.)

the new window appears to be drawn on top first, and then push back.

is this related to metacity focus stealing prevention
http://mail.gnome.org/archives/desktop-devel-list/2004-December/msg00306.html

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

this does not occur if using openbox as a windowmanager.

sudo apt-get install openbox
openbox --replace

Revision history for this message
Michael Vogt (mvo) wrote :

Interesstingly this seems to be releated to the startup notification patch. If the startup notification for gksu is disabled (patch removed) it seems to be working. I would be interessted if other people can reproduce this. Please recompile the current gksu package and remove the debian/patches/11_startup_notification.patch before runing "debuild".

Thanks,
 MIchael

Revision history for this message
Joe Barnett (thejoe) wrote :

Michael: seems to work properly with the patch removed here.

Revision history for this message
Michael Vogt (mvo) wrote :

I uploaded gksu_1.3.7-0ubuntu2 that fixes the issue. There was a problem in the event time initialization in the new startup notification code.

Cheers,
 Michael

Changed in gksu:
status: Confirmed → Fix Released
Revision history for this message
Tollef Fog Heen (tfheen) wrote :

I can reproduce this on a dapper beta candidate install (amd64), so it appears not to be fixed.

Changed in gksu:
status: Fix Released → Confirmed
Revision history for this message
psylence519 (psylence519) wrote :

An update within the last couple days has regressed this, I'm getting it again as well. Was definitely fixed for a week at least.

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

> An update within the last couple days has regressed this, I'm getting it again as well.

I can confirm this, too.

description: updated
Revision history for this message
David Planella (dpm) wrote :

I can confirm this behaviour on my system too, and IIRC it has been like that since I upgraded from Breezy to dapper last weekend.

Revision history for this message
Tomi Urankar (tomi0) wrote :

I also confirm it.
Using fresh DAPPER BETA install with all the updates installed

Revision history for this message
Tomi Urankar (tomi0) wrote :

any more news about this bug?

ps. On my friends computer I installed DAPPER BETA 1 and he didnt have this bug. The bug started hapening when we installed latest updates for DAPPER!!

Revision history for this message
psylence519 (psylence519) wrote :

ashrack: That would be because it was broken in early flights, then was fixed, then broke again (in late April). And has sat since...

Revision history for this message
Michael Vogt (mvo) wrote :

Something changed recently that broke the startup notification patch again. I'm debugging it currently. Interesstingly only applications that support startup notification natively seems to be affected. The good old "xdvi", "xemacs" etc applications work as expected.

Revision history for this message
Michael Vogt (mvo) wrote :

metacity (when run with METACITY_DEBUG=1 and METACITY_VERBOSE=1) comes up with a interessting explaination why the window is not focused:

STARTUP: window 0x1000006 (Unsaved Do) focus prevented by other activity; 2896396320 < 413216422

I'm looking at metacity next

Revision history for this message
Michael Vogt (mvo) wrote :

I uploaded gksu_1.3.7-0ubuntu8_source a couple of minutes ago and it should fix the issue. Please let me know if it works for you too.

Cheers,
 Michael

Changed in gksu:
status: Confirmed → Fix Committed
Revision history for this message
Clemens (clast) wrote :

It works for me now :)

Thank you Michael.

clast

Revision history for this message
David Planella (dpm) wrote :

It also works for me now.

Thank you very much, I couldn't wait for this one to be fixed ever since I upgraded... :)

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

Works for me, too.

Thanks :)

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for testing! Closing the bug now.

Changed in gksu:
status: Fix Committed → Fix Released
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.