Harsh J

Memoirs of a QWERTY Keyboard

The case of the non-exiting Mozilla Firefox

9 comments

Being a KDE user has its ups and downs. The ups are that its beautiful, has a very wide and usable range of applications, updates often for bugfixes, and is generally very customizable. The downs are a few – with the Firefox+GTK integration being one of them. It makes your browser look UGLY! Of course, there are Qt-friendly browsers like Opera and Konqueror, even Arora, but these hardly work well with many sites, especially those of Google (Wave, for example). I’m not gonna delve into that subject, since this post is about using Firefox on KDE 4 (version 4.3.x).

You might have heard of the GTK engine that themes for Qt, known as gtk-engine-qt on most distributions (or with -kde4 suffix, if thats how they’ve integrated). This helps all GTK applications look great on KDE by providing *near* native look and feel. So I install that and smile, happy that my entire K Desktop is as I want it – dark, without gloss and perfectly usable with certain plasma widgets. That is until I notice my Firefox simply does not close itself when asked to, and hangs instead.

At first one would think its due to a plugin, or an extension, probably something added on that is causing it to hang when its supposed to terminate. Even the KB article at Mozillazine supports that fact. Perhaps its a popular reason, but I tried and it didn’t solve the issue for me. I jumped a few steps out of frustration and went on to move my .mozilla directory to a different name, just to see if it was a profile-related issue, and it still refused to close, driving me mad having to `killall firefox` it each time since it always hung at exit. So I switched to Opera and used it with horrible colors – Pages appeared normally as they would be rendered but the forms and other things just didn’t go well with my dark color scheme (Eclipse), making it appear like the image below, unreadable and thus untypable upon.

Unreadable, Unseeable - The form elements as they appear in my Opera (While using a dark color scheme in the DE)

Unreadable, Unseeable - The form elements as they appear in my Opera (While using a dark color scheme in the DE)

The browser’s great otherwise, its fast and very customizable, but I couldn’t make any changes to these colors. I suppose one can achieve it by writing their own userstyle.css file but that is too much work. Used Opera until today, when I finally found this (pretty old) bug in the gtk-engine-qt project tracker. Uninstalled gtk-engine-qt and lo, all was normal again, closed fine and opened fine. Re-installed all plugins and extensions, and said bye-bye to Opera.

All I now miss is a native-looking dark theme with Oxygen icons, as my K Desktop contains. I’m making do with the Black Stratini theme as of now, it’s beautiful but I like the Oxygen icons better. 440 words for just the choice of browser on a dark theme, tch.

Written by Harsh

October 9th, 2009 at 10:02 am

9 Responses to 'The case of the non-exiting Mozilla Firefox'

Subscribe to comments with RSS or TrackBack to 'The case of the non-exiting Mozilla Firefox'.

  1. Kalpik

    9 Oct 09 at 10:42 am

  2. But Qt Curve is something that needs to be done at both sides, it would make me shift to Curve from Oxygen on KDE as well as GTK. I guess that GTK OxygenRefit + KDE4 look theme combo might do it, thanks for the link!

    Edit: Just tried those gtk-kde42-oxygen-theme and OxygenRefit icons, and they actually work wonders – but for my color scheme, doesn’t adapt to that :(

    Harsh

    9 Oct 09 at 1:44 pm

  3. Awesome post!! By the way, I’ve got a question for you. How do you add source code to your website? Like the ones you’ve posted for Python?

    I tried the same with my WordPress blog, and all the double quotes and angled brackets were all converted to their HTML counterpart i.e., the HTML code for those symbols.

    How did you manage to post the code as is?

    Manikandan S

    10 Oct 09 at 8:02 pm

  4. @Manikandan S – There is a WordPress FAQ entry that covers this query here. I use the Syntax Highlighter Evolved plugin, which is pretty much the same thing WordPress.com provides for its users. Basically, one has to enclose the code in tags, where lang is a passed parameter for the language (as a string). The plugin handles the rest, including indentation and angled brackets, etc..

    Harsh

    11 Oct 09 at 1:37 pm

  5. I did that. Enclosing the source code with in the tags and it returned the same result. And I’m using the free wordpress blog. Not the hosted one. Thanks for your reply. :)

    Manikandan S

    11 Oct 09 at 5:56 pm

  6. Thanks for the information, Harsh. Got it working now. I had included the “sourcecode” tag in the HTML editor, instead of the Visual editor. Thanks for your helps. :)

    Manikandan S

    11 Oct 09 at 7:09 pm

  7. Did you use the qt4 version of opera? Much better looking than the qt3 version.

    Ekeluo

    12 Oct 09 at 6:26 pm

  8. Hello Ekeluo,
    I was using the Qt4 version of Opera all this while – specifically the opera-qt4 package in AUR. And yes, it does look way better than its Qt3 counterpart! :)

    Harsh

    14 Oct 09 at 1:20 am

  9. @Manikandan S – Glad to be of assistance :)

    Harsh

    15 Oct 09 at 10:50 pm

Leave a Reply