Firefox doesn't close properly - gtk-qt-engine

Still happening on KDE 4.2 stable. It affects Swiftweasel, Swiftfox, Songbird and other Firerefox-based browsers too.

I followed this steps:

1) Purged official Ubuntu Intrepid package: gtk-qt-engine;
2) Tested opening and closing browsers: Firefox, Swiftweasel and Songbird quit successfully and no "already running but not responding" is shown on reopening. This meand It SURE is a gtk-qt-engine bug, since all is fine when it's not installed;
3) Installed gtk-qt-engine-kde4 from Debian Experimental Repository which is a snapshot of the 145th revision that *fixes* this bug with Iceweasel 3 (the package Kalinda was talking about);
4) Tested opening and closing browsers: Firefox quits normally and no error message is shown when reopening, but Songbird and Swiftweasel (the browser I'm running all the time) keep on showing the "already running but not responding" dialog.
5) Purged gtk-qt-engine-kde4 (the one I took from Debian experimental repo);
6) Tested browsers: all OK.
7) Installed gtk-qt-engine Ubuntu package again;
8) Firefox quits normally and no dialog is shown on reopening. Swiftweasel still shows that annoying dialog and I have to "pgrep wea |xargs kill -9" everytime I close it.

I can also confirm this bug, running KDE4 (Jaunty) and Firefox up-to-date as of 2009-04-24.

When closing Firefox, the process is still running in the background.
I have to "pkill firefox" to be able to start it again.

Problem was gone as soon as I purged gtk-qt-engine.

I have a workaround for this bug, although I'm unsure if Ubuntu has the needed package for it since it came from the Arch Linux forums.

Anyway, instead of telling the GTK-QT-Engine to "use the same as KDE", download and install the Oxygen GTK theme and set it to that instead. It kills this problem and still looks pretty much the same.

I hope this works for you guys.

Same thing here.

running KDE4 (Jaunty) and Firefox up-to-date as of 2009-04-26.

When closing Firefox, the process is still running in the background.
I have to "pkill firefox" to be able to start it again.

Problem was gone as soon as I purged gtk-qt-engine.

Okay, to follow up now that I'm back at my Arch machine and off of Windows.

The theme you need to use with the GTK-QT engine is called kde4-oxygen and it should come with the engine by default, along with some other GTK themes. If it doesn't then you should be able to get it from here: http://kims-area.com/?q=node/63

It's even got a deb package :) I'm also pretty sure that trying any other GTK theme with the engine will make this problem go away since the bug appears to occur when you tell it to use the same theme as KDE.

Ok here's the way I went around the bug (thanks Kalinda :-) )

Here's the direct link I used for the .deb:
http://kims-area.com/gnome/kde4-oxygen-gnome-theme-1.0-1_all.deb

The package will install as "kde4-oxygen-gnome-theme"

After a few hours of searching I finally found out you also need these packages installed:
(you can verify with: "$ cat /usr/share/themes/kde4-oxygen/gtk-2.0/gtkrc | grep engine")
gtk2-engines-pixbuf
gtk2-engines-murrine

Then you can go in K > System Settings > Appearance -> GTK Styles and Fonts
and choose: "Use another style: kde4-oxygen"

Of course it's only a work around and it doesn't resolve the bug in gtk-qt-engine.

It seems gtk-qt-engine development has stopped several months ago,
you'd rather use gtk-kde4.
http://www.kde-apps.org/content/show.php/gtk-kde4?content=74689

If you can't build it on Jaunty, follow my instructions on latest
comments. Also remember to change /home/apocalypse in the .desktop
file with your home.

2009/4/30 François Letendre <email address hidden>:
> Ok here's  the way I went around the bug (thanks Kalinda :-)  )
>
> Here's the direct link I used for the .deb:
> http://kims-area.com/gnome/kde4-oxygen-gnome-theme-1.0-1_all.deb
>
> The package will install as "kde4-oxygen-gnome-theme"
>
> After a few hours of searching I finally found out you also need these packages installed:
> (you can verify with: "$ cat /usr/share/themes/kde4-oxygen/gtk-2.0/gtkrc | grep engine")
> gtk2-engines-pixbuf
> gtk2-engines-murrine
>
> Then you can go in K > System Settings > Appearance -> GTK Styles and Fonts
> and choose: "Use another style: kde4-oxygen"
>
> Of course it's only a work around and it doesn't resolve the bug in gtk-
> qt-engine.
>
> --
> Firefox doesn't close properly - gtk-qt-engine
> https://bugs.launchpad.net/bugs/306056
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I can confirm that bug
Kubuntu 9.04
KDE 4.2.4
gtk-qt-engine 1:1.1+svn20080816-0ubuntu7
Firefox 3.5 final official

But works with Firefox 3.0.11

Interesting how is that resolved in Karmic? Still there?

Upstream bug report: http://code.google.com/p/gtk-qt-engine/issues/detail?id=39

Sadly, gtk-qt-engine is a quite broken piece of software and has been removed from distribution. (See bug 404930)
Unfortunately this means that the large number of bugs will not be seeing fixes. :(

For now, the best integration option for KDE is the QtCurve style, (gtk2-engines-qtcurve) which offers a theme quite similar to the default Oxygen theme. The configuration module for gtk-qt-engine has been salvaged and is now living in the kcm-gtk package, which will be available and installed by default in Kubuntu 9.10.

Thanks for understanding. This package tried its best, but in the end did not live up to the standards required by anybody who doesn't like looking at a broken Oxygen imitation.