Description of problem: If the whole document is marked [Ctrl]+[A] any mouse-action crashes LO Version-Release number of selected component (if applicable): M1 x86_64 How reproducible: every time Steps to Reproduce: 1. open a document 2.type [ctrl]+[A] 3a. try to correct a mistake (underlined) with the right mouse-tap 3b. try to move text with the left one
I tried to reproduce on Cauldron and can't. The bug seems to be resolved on LO 3.5
CC: (none) => oliver.bgr
can you test LO in update_testing ?
CC: (none) => dmorganec
LibreOffice 3.4.5 OOO340m1 (Build:502) The test is the same as 3.4.4. The same in M1 i586
I can't reproduce in mga1, could you provide a file or attach the debug ? https://wiki.mageia.org/en/Debugging_software_crashes#gdb
Keywords: (none) => NEEDINFO
Jürgen, could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
CC: (none) => marja11
Hello! Now I use: LibreOffice 3.4.5 OOO340m1 (Build:502) You can open LO-writer with a document an press [Strg]+[A] to mark "all". Taking the left mouse-button an push it out of the LO window to the desktop, the document should be in the KDE-klipper. This is possible, if the marked text is very short, a document of a whole A4 page, nothing is in KDE-klipper, but LO-writer is closed. I dont' have Cauldron [quote]I tried to reproduce on Cauldron and can't. The bug seems to be resolved on LO 3.5[/quote] ...perhaps comment 4 (gdb) file /usr/lib64/libreoffice/program/soffice.bin Reading symbols from /usr/lib64/libreoffice/program/soffice.bin...(no debugging symbols found)...done. Missing debug package(s), you should install: libreoffice-debug-3.4.5.2-0.1.mga1.x86_64 (gdb) I have done so: [root@Multimedia:kowalzik program]# urpmi libreoffice-debug-3.4.5.2-0.1.mga1.x86_64 Um die Abhängigkeiten zu erfüllen, werden die folgenden Pakete installiert: Paket Version Release Arch (Medium »Core Updates Testing«) libreoffice-gdb-debug-support 3.4.5.2 0.1.mga1 x86_64 (Medium »Core Updates Testing Debug«) libreoffice-debug 3.4.5.2 0.1.mga1 x86_64 1.4GB Speicher wird frei. 463MB an Paketen wird geholt Fortfahren mit der Installation der 2 Pakete? (J/n) j $MIRRORLIST: media/core/updates_testing/libreoffice-gdb-debug-support-3.4.5.2-0.1.mga1.x86_64.rpm $MIRRORLIST: media/debug/core/updates_testing/libreoffice-debug-3.4.5.2-0.1.mga1.x86_64.rpm 3.4.5.2-0.1.mga1.x86_64.rpm libreoffice-gdb-debug-support-3.4.5.2-0.1.mga1.x86_64.rpm von /var/cache/urpmi/rpms wird installiert Vorbereiten ⦠####################################################################################### 1/2: libreoffice-gdb-debug-support ####################################################################################### 2/2: libreoffice-debug ####################################################################################### [root@Multimedia:kowalzik program]# (gdb) file /usr/lib64/libreoffice/program/soffice.bin Reading symbols from /usr/lib64/libreoffice/program/soffice.bin...Reading symbols from /usr/lib/debug/usr/lib64/libreoffice/program/soffice.bin.debug...done. done. (gdb) but.......... the debug-version of LO dont suffer under this foult :-8 the whole document is in the KDE-klipper sorry...
Keywords: NEEDINFO => (none)
Can not reproduce it under Mageia 2 and LibreOffice 3.5.5.1.
CC: (none) => tolhildan_123
(In reply to comment #7) > Can not reproduce it under Mageia 2 and LibreOffice 3.5.5.1. @ Jürgen Do you still have this bug in Mageia 2? If you don't have it in Mageia 2, do you then agree to close this bug for Mageia 1, because Mageia 2 solved it for you?
(In reply to comment #8) > (In reply to comment #7) > > Can not reproduce it under Mageia 2 and LibreOffice 3.5.5.1. > > @ Jürgen > > Do you still have this bug in Mageia 2? > > If you don't have it in Mageia 2, do you then agree to close this bug for > Mageia 1, because Mageia 2 solved it for you? I never did use Mageia 1, but I know that I can not reproduce it under Mageia 2.
(In reply to comment #9) > > I never did use Mageia 1, but I know that I can not reproduce it under Mageia > 2. Yes, you told us. Thanks a lot for the feedback :) Let's wait for the reporter of this bug to reply whether Mageia 2 solved this issue for him ;)
(In reply to comment #10) > > Let's wait for the reporter of this bug to reply whether Mageia 2 solved this > issue for him ;) Jürgen sent a mail asking to close this bug @ Jürgen Thanks for the feedback. It is impossible to reply to a bugzilla mail other than logging in to Bugzilla, opening the bug report and writing a new comment. Closing as WONTFIX for Mageia 1
Status: NEW => RESOLVEDResolution: (none) => WONTFIX