Re: Opera, still functional, 'one cannot make new configs' etc since v9 > v10

2015-01-13 Thread Fred Woods
I installed on FreeBSD 9.3 adm64 p5, with gtk2 off. KDE4 Plasma X server. Radeon xorg driver (ATI 7750 card). Got an error about missing libfreetype.so.9, but the browser seemed to work fine. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd

Re: Opera, still functional, 'one cannot make new configs' etc since v9 > v10

2015-01-12 Thread Jeffrey Bouquet via freebsd-ports
On 01/11/15 22:59, Fred Woods wrote: > If you run opera from a terminal window, do you get something like the > problem described in: > http://stackoverflow.com/questions/2568408/pango-warning-failed-to-choose-a-font-expect-ugly-output > > If yes, then a possible work-around is: > > Move any pango

Re: Opera, still functional, 'one cannot make new configs' etc since v9 > v10

2015-01-11 Thread Fred Woods
If you run opera from a terminal window, do you get something like the problem described in: http://stackoverflow.com/questions/2568408/pango-warning-failed-to-choose-a-font-expect-ugly-output If yes, then a possible work-around is: Move any pango compliant fonts to /usr/local/lib/X11/fonts mv /u

Opera, still functional, 'one cannot make new configs' etc since v9 > v10

2015-01-11 Thread Jeffrey Bouquet via freebsd-ports
II can browser fine with Opera still [mostly] but cannot interact with its dialog. ONLY the lowercase 'a' [and uppercase E] show. For instance, the 'graphics' button (on off toggle) has [ a ] and the 'open in background tab' is [ _ a a ] ... So the prompts and browser action are only by 'wha