[Libreoffice-bugs] [Bug 121356] One CPU used at 100% with no document opened, until mouse passing over window (gtk2)

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Wed Jul 17 03:20:08 UTC 2019


https://bugs.documentfoundation.org/show_bug.cgi?id=121356

Buovjaga <todventtu at suomi24.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|One CPU used at 100% with   |One CPU used at 100% with
                   |no document opened, until   |no document opened, until
                   |mouse passing over window   |mouse passing over window
                   |                            |(gtk2)
             Blocks|                            |103503

--- Comment #8 from Buovjaga <todventtu at suomi24.fi> ---
Thanks for testing.

The good thing is that 4.14 is finally supposed to be released later this
summer: https://simon.shimmerproject.org/2019/07/01/xfce-4-14pre2-released/
"The next release – aka pre3 – is optional, so we may decide to skip it and go
straight for the final release if the release team is confident that there are
no showstoppers."

>From a comment:
"In theory distributions can decide to disable Gtk+2 already. However there are
still some applications that rely on the libraries that are not yet ported to
Gtk+3 (see the Roadmap page, e.g. Ristretto) so those would be broken by that
change.

As soon as we have stable releases of all applications in a Gtk+3 version we
will probably remove Gtk+2 support altogether.
For the panel we will at least disable Gtk+2 support by default upstream as
there are only very few unported plugins."


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103503
[Bug 103503] [META] GTK2 VCL backend bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20190717/1b3f434c/attachment.html>


More information about the Libreoffice-bugs mailing list