<div dir="ltr">On 16 June 2016 at 15:44, Gary Thomas <<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>> wrote:<br>><br>> I just tried a build from the latest Poky/Yocto master (2a85038dd)<br>> Overall, I think the switch to GTK+3 is an improvement, but I have<br>> a number of [usability] questions:<br><br>It's a tricky upgrade, essentially upgrading a major part of an operating system from a version five years old version to a current one. I am sorry for the inconvenience.<div><br>> * I built firefox from meta-browser and noticed that on my touch only<br>> device, it does not automatically pop-up the keyboard. However, epiphany<br>> does. I've only done a little testing but that's what I observed. Not<br>> having this happen "on demand" (i.e. when a text field has the focus)<br>> will make using a full screen application impossible on this hardware.<br><br>I assume this is still the Gtk2 firefox? There is a Gtk3 version released recently I believe.<br><br>Before the recent changes, Gtk+2 applications were the only thing supported by the virtual keyboard.<div><br></div><div>Now, the default configuration is to build only support for Gtk+3 but it is possible to support also Gtk+2 by adding "gtk2-im" into the matchbox-keyboard PACKAGECONFIG. This is not done by default to prevent the keyboard from bringing gtk+ into the image if nothing else requires it. </div><div><br>> * Also on firefox, I can't seem to get the vertical scrollbar to work.<br>> Again, with epiphany it at least works.<br><br>This is slightly surprising if firefox is a gtk+2 application. The only thing that really changed with the GTK2 stack is the theme... but the current one (gnome-theme-adwaita from gnome-themes-standard) is the GNOME default so I'd expect it work. I have no suggestions here, Sorry.<br><br>> * The system also doesn't seem to play very nice with my GPU enhanced<br>> i.MX6 and causes the SoC to overheat (didn't happen with GTK+2). Makes<br>> it rather unusable as well.<br><br>Eek. That sounds like a driver problem. The new Gtk is more demanding on graphics drivers but not by a huge difference.<br><br>> * gtk-play ran my 1GB system out of memory, just starting up :-(  This<br>> caused a complete system lockup & I could not even restart the X server.<br>> This application also seemed to run quite well with GTK+2<br><br>gst-player did go through some refactoring (the library parts are now in gst-plugins-bad) so new bugs are not impossible. It's unlikely that the Gtk upgrade itself would have this kind of effects, but maybe this is related to the previous problem -- wherever the root cause is.</div><div><br></div><div>> * There also seem to be a continuous stream of messages like these on the console:<br>><br>>  GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.<br>>  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.<br><br>The messages as such are not problematic, assuming there's no flood of them.</div><div><br></div><div>GSettings is still something we might want to bring in (as a replacement for GConf which is deprecated), but that means a little porting work on matchbox components. The GtkDialog message is probably from gtk-play and should not be an issue.<br><br></div><div>Hope this helps,</div><div> Jussi</div><div><br></div><div><br></div><div><br></div><div>> I know that these firefox vs. epiphany vs. chome vs. ... questions<br>> are not really the responsibility of Yocto or OE-core, but it does<br>> trickle down to those of us trying to use this framework.<br>><br>> Many thanks for any thoughts<br>><br>> n.b. I was torn what mailing list to use for this - it's tightly<br>> tied to OE-core, but isn't really about patches or changes, more<br>> about philosophy. If the OE-core list is more appropriate, please<br>> move the replies there.<br>><br>> --<br>> ------------------------------------------------------------<br>> Gary Thomas         |  Consulting for the<br>> MLB Associates        |   Embedded world<br>> ------------------------------------------------------------<br>> --<br>> _______________________________________________<br>> yocto mailing list<br>> <a href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a><br>> <a href="https://lists.yoctoproject.org/listinfo/yocto">https://lists.yoctoproject.org/listinfo/yocto</a></div></div></div>