Description: Package: libreoffice-writer Version: 1:3.5.4+dfsg2-0+deb7u2 Severity: normal Tags: l10n Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? libreoffice-writer suddenly turns off Hangul mode for Korean input whenever it is deactivated. Switching back and forth betwen Google Chrome and libreoffice-writer made me have to do extra steps for reset Hangul mode for Korean writing. For instance, while libreoffice-writer in Hangul mode, switching back to Google Chrome to use English/Korean web dictionary turns off Hangul mode of the writer. Selecting Hangul/English in IBus wouldn't activate Hangul input until the writer's window is minimized and then resized again. This weird, annoying bug does exist from version 3.5.4.2 to 4.1.x in unstable. *** End of the template - remove these lines *** I suspect newer version of libreoffice-writer moves some of codes that handles Xorg Input Method to libreoffice-gnome package. Kernel: Linux 3.11-9.dmz.1-liquorix-amd64 (SMP w/6 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libreoffice-writer depends on: ii libc6 2.17-95 ii libgcc1 1:4.8.2-2 ii libicu48 4.8.1.1-12 ii libreoffice-base-core 1:3.5.4+dfsg2-0+deb7u2 ii libreoffice-core 1:3.5.4+dfsg2-0+deb7u2 ii libstdc++6 4.8.2-2 ii libwpd-0.9-9 0.9.4-3 ii libwpg-0.2-2 0.2.1-1 ii libwps-0.2-2 0.2.7-1 ii libxml2 2.9.1+dfsg1-3 ii uno-libs3 3.5.4+dfsg2-0+deb7u2 ii ure 3.5.4+dfsg2-0+deb7u2 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages libreoffice-writer recommends: ii libreoffice-emailmerge 1:3.5.4+dfsg2-0+deb7u2 ii libreoffice-filter-binfilter 1:3.5.4+dfsg2-0+deb7u2 ii libreoffice-java-common 1:4.1.3-1 ii libreoffice-math 1:3.5.4+dfsg2-0+deb7u2 ii sun-java6-jre [java5-runtime] 6.26-0squeeze1 Versions of packages libreoffice-writer suggests: ii libreoffice-base 1:3.5.4+dfsg2-0+deb7u2 pn libreoffice-gcj <none> Versions of packages libreoffice-core depends on: ii fontconfig 2.9.0-7.1 ii fonts-opensymbol 2:102.2+LibO3.5.4+dfsg2-0+deb7u2 ii libc6 2.17-95 ii libcairo2 1.12.16-2 ii libcmis-0.2-0 0.1.0-1+b1 ii libcurl3-gnutls 7.26.0-1+wheezy4 ii libdb5.1 5.1.29-5 ii libexpat1 2.1.0-1 ii libexttextcat0 3.2.0-2 ii libfontconfig1 2.11.0-1 ii libfreetype6 2.4.9-1.1 ii libgcc1 1:4.8.2-2 ii libglib2.0-0 2.36.4-1 ii libgraphite2-3 [libgraphite2-2.0.0] 1.2.3-1 ii libgstreamer-plugins-base0.10-0 0.10.36-1.1 ii libgstreamer0.10-0 0.10.36-1.2 ii libhunspell-1.3-0 1.3.2-4 ii libhyphen0 2.8.3-2 ii libice6 2:1.0.8-2 ii libicu48 4.8.1.1-12 ii libjpeg8 8d-1 ii libmythes-1.2-0 2:1.2.2-1 ii libneon27-gnutls 0.29.6-3 ii libnspr4 2:4.10.1-1 ii libnspr4-0d 2:4.10.1-1 ii libnss3 2:3.15.2-1 ii libnss3-1d 2:3.15.2-1 ii libpng12-0 1.2.49-1 ii librdf0 1.0.16-1 ii libreoffice-common 1:3.5.4+dfsg2-0+deb7u2 ii librsvg2-2 2.36.1-1 ii libsm6 2:1.2.1-2 ii libssl1.0.0 1.0.1e-2 ii libstdc++6 4.8.2-2 ii libx11-6 2:1.5.0-1+deb7u1 ii libxext6 2:1.3.1-2+deb7u1 ii libxinerama1 2:1.1.2-1+deb7u1 ii libxml2 2.9.1+dfsg1-3 ii libxrandr2 2:1.3.2-2+deb7u1 ii libxrender1 1:0.9.7-1+deb7u1 ii libxslt1.1 1.1.26-14.1 ii uno-libs3 3.5.4+dfsg2-0+deb7u2 ii ure 3.5.4+dfsg2-0+deb7u2 ii zlib1g 1:1.2.7.dfsg-13 -- no debconf information Steps to Reproduce: I found troubleshooting information about libreoffice and ibus related in Chinese on https://wiki.archlinux.org/index.php/IBus It turned out missing libreoffice-gnome caused this error. Because after installed libreoffice-gnome package, Hangul deactivation bug above mentioned disappered. Actual Results: ITS SHOWING AN ERROR Expected Results: The bug is expected to be resolved Reproducible: Sometimes User Profile Reset: No Additional Info: -- System Information: https://wp.me/P9j3pn-8/ Debian Release: 7.2 APT prefers stable APT policy: (700, 'stable'), (600, 'unstable') Architecture: amd64 (x86_64) User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36
Your LibreOffice version has reached end-of-life long time ago. Please report this against Debian and upgrade to a still maintained version of LibreOffice. Do you still encounter same behavior with current versions: 5.4.x, 6.0.x ? Status set to NEEDINFO, please set it back to UNCONFIRMED once requested informations are provided. Best regards. JBF
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20181203
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20190111