On 03/29/2012 12:09 PM, Patrick O'Callaghan wrote:
By no means:
1) It *is* a kludge and is clearly brittle e.g. Chrome makes certain
choices based on the desktop environment, such as which password store
to use. Forcing it to think it's in Gnome when it really isn't means
these factors also need to be worked around.
2) The kludge happens to work for Chrome because the latter is a GTK
app. It's not a general solution.
3) It took a lot of effort to find, i.e. the "solution" is not easily
discoverable, and in fact works by *not* using anything in the KDE
environment. My original comment about this being too hard still stands.
So, you will file a bugzilla with the Chrome folks, right? :-)
With FF, the solution is to edit their settings in about:config, right? It somehow
knew about "transmission" but not about "ktorrent" so the
"fix" (I believe) would
have to go there.
Whose effort found the solution? :-) :-)
Do not condemn the judgment of another because it differs from your own. You may both
be wrong. -- Dandemis