Bug#837356: libreoffice-gtk3: Impress is unusably slow on GNOME 3 with libreoffice-gtk3 installed
Package: libreoffice-gtk3 Version: 1:5.2.1-1 Severity: important Dear Maintainer, This might be related to https://bugs.debian.org/836531 but I'm not sure. With 5.2.0 and 5.2.1, running on GNOME 3, Impress is unusably slow if libreoffice-gtk3 is installed. The steps to reproduce on my system are simply * start Impress * open a new document * click on any "Click to add ..." message * wait for a couple of minutes before anything happens (with one core pegged at 100%) Every single interaction with the document takes a couple of minutes to be taken into account, apart from changing slides: typing text, moving elements around... Uninstalling libreoffice-gtk3 fixes the problem. Clearing LibreOffice's configuration doesn't. Regards, Stephen -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice-gtk3 depends on: ii libatk1.0-0 2.20.0-1 ii libc6 2.23-5 ii libcairo-gobject2 1.14.6-1+b1 ii libcairo2 1.14.6-1+b1 ii libdbus-1-3 1.10.10-1 ii libdbus-glib-1-2 0.106-1 ii libgcc1 1:6.1.1-11 ii libgdk-pixbuf2.0-02.34.0-1 ii libgl1-mesa-glx [libgl1] 11.2.2-1 pn libglew1.10 ii libglib2.0-0 2.49.6-1 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libgtk-3-03.21.5-3 ii libice6 2:1.0.9-1+b1 ii libpango-1.0-01.40.2-1 ii libpangocairo-1.0-0 1.40.2-1 ii libreoffice-core 1:5.2.1-1 ii libsm62:1.2.2-1+b1 ii libstdc++66.1.1-11 ii libx11-6 2:1.6.3-1 ii libxext6 2:1.3.3-1 ii uno-libs3 5.2.0-2 ii ure 5.2.0-2 Versions of packages libreoffice-gtk3 recommends: ii libreoffice-style-tango 1:5.2.1-1 libreoffice-gtk3 suggests no packages.
Bug#798788: libreoffice: Config from previous version causes badly-updating display
Le 23/10/2015 01:55, Ben Finney a écrit : Control: retitle -1 libreoffice: Config from previous version causes badly-updating display Control: tags -1 unreproducible moreinfo On 12-Sep-2015, Stephen Kitt wrote: Deleting ~/.config/libreoffice fixes this. It's good that you now have a working application. Without the problematic configuration, though, it seems there is no way for the maintainer to diagnose this bug. I'll leave it up to you to decide what to do with this; there's something missing in the upgrade code, but what... The only way I can see it makes sense for this bug report to remain open is if there is some information that can be given to the maintainer to help reproduce the behaviour. If you no longer have that and can't send it, I'll ask that you please close this report as unreproducible. I still have the old configuration directory; if René is interested I can check there's nothing sensitive there and send him a tarball. Regards, Stephen
Bug#798788: libreoffice: display doesn't update properly (writer and calc)
On Sat, 12 Sep 2015 20:17:42 +0200, Stephen Kitt <sk...@debian.org> wrote: > I've tried deleting ~/.libreoffice and switching off display > acceleration (hardware acceleration, OpenGL, and the anti-aliasing > options) without effect. Deleting ~/.config/libreoffice fixes this. I'll leave it up to you to decide what to do with this; there's something missing in the upgrade code, but what... Regards, Stephen pgp99aJRPL7MS.pgp Description: OpenPGP digital signature
Re: libreoffice, mingw-w64, gcc-mingw-w64 and gnat-4.6 on armhf
Hi Peter, On Fri, Feb 03, 2012 at 02:36:17AM +, peter green wrote: Libreoffice hasn't yet been built on armhf. I consider libreoffice to be a reasonablly important package and one that we need to get in before we can claim we have a reasonablly complete port. [...] This (build-)dependency chain leaves me with a few questions 1: what is the current status of gnat-4.6 on armhf? does an upload look likely any time soon? 2: why does libreoffice need mingw-w64 in the first place? libreoffice uses mingw-w64 to build a DLL, unowinreg.dll, which is provided in the libreoffice-dev package. As I understand it the DLL itself isn't used on Debian, but it is provided by the SDK because it is supposed to be bundled with plugins which need to access the registry, and therefore to be able to correctly build shippable plugins using Debian the SDK packages need to provide the DLL. 3: why are we building an ada cross compiler for windows? is it just for completeness or was/is there an identified requirement? It was requested; see #632375. 4: if we can't get an ada compiler on armhf in the near future would anyone consider it unreasonable to build gcc-mingw-w64 without ada suport on armhf so that libreoffice can be built? I wouldn't; I can definitely upload a new version of gcc-mingw-w64 which drops Ada support on armhf. Regards, Stephen -- To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120203054832.gu5...@sk2.org
Bug#642954: libreoffice: Please support building with mingw-w64 instead of gcc-mingw32
Hi René, Sorry for not getting back to you sooner! On Wed, 5 Oct 2011 10:32:17 +0200, Rene Engelhard r...@debian.org wrote: On Mon, Sep 26, 2011 at 01:10:29AM +0200, Rene Engelhard wrote: On Mon, Sep 26, 2011 at 12:10:13AM +0200, Stephen Kitt wrote: mingw-w64, which is intended to eventually replace mingw32 and the Why is it then cllaed w*64*? And why didn't it replace them yet? Sound like either a broken package name or wishful thinking to me - or even both, That said, the official complete mingw cross-compilation Linux-Windows attempt at http://tinderbox.libreoffice.org/MASTER/status.html uses mingw-w64: [...] --build=x86_64-unknown-linux-gnu --host=i686-w64-mingw32 [...] Looks sane, then :) Thanks for taking the time to investigate! The naming is weird, see http://bugs.debian.org/622276 for the details. The new triplets in use are the reason why the package couldn't simply replace the mingw32 toolchain; the compilers aren't drop-in replacements, so if I had just declared a Replaces relation I would have caused a few FTBFSs. Given that I'm the one driving the change I prefer taking the time to get in touch with the various maintainers involved! Changed it for non-squeeze-backports builds. Thanks! On Fri, 30 Sep 2011 02:06:44 +0200, Rene Engelhard r...@debian.org wrote: On Mon, Sep 26, 2011 at 12:10:13AM +0200, Stephen Kitt wrote: mingw-w64, which is intended to eventually replace mingw32 and the assorted packages, is now available in Debian along with new builds of ^^^ binutils and gcc. To build libreoffice using mingw-w64, all that's Do you want to say with that that I need = 2.0? rene@frodo:~$ rmadison mingw-w64 mingw-w64 | 0~20100125-3 | squeeze | source, all mingw-w64 | 2.0~rc1-1| wheezy | source, all mingw-w64 | 2.0~rc1-1| sid | source, all or is the 20100125 version also ok? (Important for squeeze backports) You need at least version 1.0, which was previously in sid/wheezy; I suppose since no Debian release will ever have 1.0 you might as well specify = 2.0~. The version in squeeze won't work, it uses yet another triplet and was only intended for Win64 programs. Best regards, Stephen signature.asc Description: PGP signature
Bug#642954: libreoffice: Please support building with mingw-w64 instead of gcc-mingw32
Package: src:libreoffice Version: 1:3.4.3-1 Severity: wishlist Dear Maintainer, mingw-w64, which is intended to eventually replace mingw32 and the assorted packages, is now available in Debian along with new builds of binutils and gcc. To build libreoffice using mingw-w64, all that's needed is to replace the 'gcc-mingw32' and 'mingw32-runtime' build-dependencies with 'mingw-w64' (which itself depends on the compilers and libraries) in debian/control, and again in debian/rules, and replace 'i586-mingw32msvc' with 'i686-w64-mingw32' in debian/rules. I would attach a patch but the build dependencies change regularly enough that it doesn't seem particularly useful! I've rebuilt libreoffice successfully using mingw-w64, but I'm not sure what the Windows build environment is actually used for so I haven't been able to check that the resulting build is actually correct. (LibreOffice itself starts up and functions correctly, but I don't know how to determine whether the Windows-targeted build artifacts are being used.) Of course I don't expect you to do the checking for me; if you have the time to point me in the right direction I'd be happy to complete the investigation. Thanks in advance, Stephen -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libreoffice depends on: ii liblucene2-java 2.9.4+ds1-2 ii libreoffice-base1:3.4.3-1 ii libreoffice-calc1:3.4.3-1 ii libreoffice-core1:3.4.3-1 ii libreoffice-draw1:3.4.3-1 ii libreoffice-filter-mobiledev1:3.4.3-1 ii libreoffice-impress 1:3.4.3-1 ii libreoffice-java-common 1:3.4.3-1 ii libreoffice-math1:3.4.3-1 ii libreoffice-report-builder-bin 1:3.4.3-1 ii libreoffice-writer 1:3.4.3-1 ii ttf-dejavu 2.33-2 ii ttf-sil-gentium-basic 1.1-2 Versions of packages libreoffice recommends: ii libpaper-utils 1.1.24+nmu1 ii ttf-liberation 1.07.0-1 ii ttf-mscorefonts-installer 3.3 Versions of packages libreoffice suggests: ii cups-bsd 1.5.0-5 ii default-jre [java5-runtime]1:1.6-40 ii gcj-4.6-jre [java5-runtime]4.6.1-2 ii gcj-jre [java5-runtime]4:4.6.1-2 ii gstreamer0.10-ffmpeg 0.10.12-3 ii gstreamer0.10-plugins-bad 0.10.22-3 ii gstreamer0.10-plugins-base 0.10.35-1 ii gstreamer0.10-plugins-good 0.10.30-1 ii gstreamer0.10-plugins-ugly 0.10.18-3 ii hunspell-dictionarynone ii hyphen-fr [hyphen-hyphenation-patterns]1:3.3.0-3 ii icedove3.1.13-1 ii iceweasel 6.0.2-1 ii imagemagick8:6.6.9.7-5 ii libgl1-mesa-glx [libgl1] 7.11-5 ii libldap-2.4-2 2.4.25-3 ii libreoffice-filter-binfilter 1:3.4.3-1 ii libreoffice-gnome 1:3.4.3-1 ii libreoffice-help-en-gb [libreoffice-help-3.4] 1:3.4.3-1 ii libreoffice-help-en-us [libreoffice-help-3.4] 1:3.4.3-1 ii libreoffice-help-fr [libreoffice-help-3.4] 1:3.4.3-1 ii libreoffice-l10n-en-gb [libreoffice-l10n-3.4] 1:3.4.3-1 ii libreoffice-l10n-fr [libreoffice-l10n-3.4] 1:3.4.3-1 ii libreoffice-officebean 1:3.4.3-1 ii libsane1.0.22-6 ii libxrender11:0.9.6-2 ii menu 2.1.45 ii myspell-en-us [myspell-dictionary] 1:3.3.0-3 ii myspell-fr [myspell-dictionary]1.4-26 ii mythes-en-us [mythes-thesaurus]1:3.3.0-3 ii mythes-fr [mythes-thesaurus] 1:3.3.0-3 ii openclipart-libreoffice0.18+dfsg-12 ii openjdk-6-jre [java5-runtime] 6b23~pre7-1 ii pstoedit 3.60-1 ii sun-java6-jre [java5-runtime] 6.26-3 ii unixodbc 2.2.14p2-3 Versions of packages libreoffice-core depends on: ii fontconfig 2.8.0-3 ii libatk1.0-0 2.0.1-2 ii libc62.13-21 ii libcairo2