If you stored the settings without full screen mode checked, start up Pharo, then switch in into full screen mode, it should run at full performance if I’m right. I have an intel integrated card + an NVidia, it can work in either mode or in Optimus mode, where it only goes into NVidia if an app requests it or goes full screen. Pharo is very quick in full screen as a result, since I run it in Optimus mode (Linux has issues with the windowing system using the NVidia drivers in normal mode).
Since Pharo uses SDL2 for the base graphic subsystem, which is one of the main gaming graphics platforms, it wouldn’t be surprising if Wayland assumed it was a game if it starts full screen, and intel graphics aren’t all that great for gaming (so I’ve heard – I have an Xbox with one game – FIFA, lol). Andrew Glynn From: J.F. Rick Sent: Saturday, November 18, 2017 3:06 PM To: Any question about pharo is welcome Subject: Re: [Pharo-users] X11 options on Ubuntu VM / Athens renderingproblems Interesting. Could be. The specific problem came up on an Intel NUC which uses Intel integrated graphics. Cheers, Jeff On Mon, Nov 6, 2017 at 5:24 PM Andrew Glynn <aglyn...@gmail.com> wrote: I don’t have any issues with Linux in full screen mode (Mint 18 KDE and OEL7 UEK KDE) but it sounds like it may be an issue with the Wayland graphics system, and KDE doesn’t use it AFAIK. If so, it may also be driver specific – what graphics card are you using? It is just a guess, but pulling Unity forward switches it out of Wayland graphics mode (used mainly for games etc. that run full screen), if it doesn’t go back into it until a new full screen app starts up it would account for the improvement. Andrew Sent from Mail for Windows 10 From: J.F. Rick Sent: Monday, November 6, 2017 4:57 PM To: Any question about pharo is welcome Subject: Re: [Pharo-users] X11 options on Ubuntu VM / Athens renderingproblems Just a quick follow up: We've found that if we are in fullscreen Pharo mode on Linux and hit the ALT button twice, the Athens-based rendering speeds up significantly. The first ALT brings the Unity launcher to the foreground. The second ALT bring fullscreen Pharo back to the foreground. I'm not sure why this makes Athens rendering faster but it does. Perhaps that offers a clue as to what is slowing Pharo down in fullscreen on Linux. Cheers, Jeff On Wed, Oct 11, 2017 at 2:56 PM Hilaire <hila...@drgeo.eu> wrote: We tested it on P6.1 64bits, and this Cairo crash seems to be gone. It may need more testing though. Is it thanks to P6.1 or the 64bits image/VM? It looks strange because it looked like a lib Cairo crash, but in the other hand the faulty C function did not appear to be called from Pharo image. What need to be done porting to P6.1, is mainly image shrinking, fix of several bugs from P6.1 impacting drgeo, working setup for linux/windows/mac. Still some job. Hilaire Le 02/10/2017 à 15:19, Stephane Ducasse a écrit : > How could we help? > > > On Sun, Oct 1, 2017 at 9:14 PM, Hilaire<hila...@drgeo.eu> wrote: >> I had situation where the system libcairo:i386 does not work with Dr.Geo[1], >> Pharo crashes with what looks like a Cairo crash! Looks like not a Pharo >> fault, but I am definitely stuck. >> >> It is problematic, it is a system (LinuxMint based) used in Geneva primary >> schools and Dr. Geo was expected to be used there:( >> >> Hilaire >> >> [1]http://forum.world.st/Cairo-related-crash-with-Dr-Geo-tt4952023.html >> >> >> Le 01/10/2017 à 19:50, Igor Stasenko a écrit : >>> All these difficulties are good argument to get the appropriate >>> libcairo/libpng shipped with the Linux VM, as done with Windows >>> and MacOSX VM >>> >>> Nah, in my case, there's nothing that can be lableled as "Pharo fault". It >>> is definitely a linux/ubuntu ecosystem fault. - by not providing parallel >>> updates for 32 & 64 bit variant of same library. >> -- >> Dr. Geo >> http://drgeo.eu >> >> >> -- Dr. Geo http://drgeo.eu
