Thanks Jörn, that explains it. I'll stay with my own version of Firefox then as I can easily deploy the script that sets the path with it.
With reference to "Please never have two packages with the same name in different repositories" - are you meaning that this is why my attempt to have a package called "firefox" didn't work? I can understand why it would cause problems if two packages have the same name, but I thought all the existing Firefox packages had the version on the end (-3, -5, -17). Is there another one that isn't visible from the Package management tree and is called just "firefox"? All the best, Mark On 11/03/13 10:42, Jörn Frenzel wrote: > Hi Mark, > > Firefox needs some newer GTK version than the base packages delivers. So > the newer one ist installed under /opt/gtk/ and must be used with > LD_LIBRARY_PATH. > > In the base version of "experimantal" the separate GTK was joined into the > base. > > Please never have two packages with the same name in diffenrent repositories. > > Regards, > > Jörn > > On 09.03.2013 23:25, Mark D-B wrote: >> Dear All, >> >> This problem is due to library paths. I've now got my own Firefox 17 >> package with a script to set LD_LIBRARY_PATH so that the correct version >> of GTK (/opt/gtk/lib) gets loaded but I'd ideally like to use the one >> from the OTC server. Does anyone know why it doesn't set the library >> path itself? >> >> All the best, >> >> Mark >> >> On 16/02/13 18:43, newsgroup account wrote: >>> When I try and run Firefox 17 on the client, I get an error saying >>> that Firefox needs GTK+ 2.10 but I only have GTK+ 2.8. This seems >>> strange, as the server package manager says the installed package is >>> 0.4.5-2.16-2, which I infer to mean GTK+ 2.16. Is there something >>> wrong with paths? >> >> ------------------------------------------------------------------------------ >> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester >> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the >> endpoint security space. For insight on selecting the right partner to >> tackle endpoint security challenges, access the full report. >> http://p.sf.net/sfu/symantec-dev2dev >> _______________________________________________ >> The Open Source Thin Client Solution http://openthinclient.org >> openthinclient-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/openthinclient-user >> > ------------------------------------------------------------------------------ > Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester > Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the > endpoint security space. For insight on selecting the right partner to > tackle endpoint security challenges, access the full report. > http://p.sf.net/sfu/symantec-dev2dev > _______________________________________________ > The Open Source Thin Client Solution http://openthinclient.org > openthinclient-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openthinclient-user > ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ The Open Source Thin Client Solution http://openthinclient.org openthinclient-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openthinclient-user
