When I open a file contains a video through menu icon > Local documents > odt file that I want to open, application takes me away to homescreen directly. Version 5.2.0.0.alpha0+ Build ID: 13d4bda
Hello, Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document. (Please note that the attachment will be public, remove any sensitive information before attaching it.) How can I eliminate confidential data from a sample document? https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F Thank you
Created attachment 121599 [details] example odt file
Confirmed. *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Build fingerprint: 'Xiaomi/mocha/mocha:4.4.4/KTU84P/5.11.26:user/release-keys' Revision: '0' pid: 3112, tid: 3142, name: Thread-195 >>> org.example.libreoffice <<< signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- r0 00000000 r1 00000c46 r2 00000006 r3 00000000 r4 00000006 r5 00000002 r6 00000c46 r7 0000010c r8 7c310d18 r9 7c213000 sl 7b9ca4f0 fp 7c310cec ip 7211b5b0 sp 7c310c70 lr 400cb021 pc 400d9f88 cpsr 000f0010 d0 6e6f697470656378 d1 3a3a726174733a3a d2 7065443a3a6f6e75 d3 45746e656d796f6c d4 4026000000000000 d5 4047800000000000 d6 4026000000000000 d7 0000000b00000000 d8 4469400000000634 d9 44990000449f0000 d10 0000000044c68000 d11 0000000000000000 d12 0000000000000000 d13 0000000000000000 d14 0000000000000000 d15 0000000000000000 d16 fffffffffffeae80 d17 3ff0000000000000 d18 4024000000000000 d19 7556d6b57556d6b5 d20 7556d6a17556d6a1 d21 7556d6a17556d6a1 d22 7556d6917556d691 d23 7556d6917556d691 d24 0000005b00000059 d25 0000005f0000005d d26 0707070703030303 d27 017a000001720000 d28 014a005301420051 d29 015a005701520055 d30 016a005b01620059 d31 017a005f0172005d scr 80000010 backtrace: #00 pc 00021f88 /system/lib/libc.so (tgkill+12) #01 pc 0001301d /system/lib/libc.so (pthread_kill+48) #02 pc 00013231 /system/lib/libc.so (raise+10) #03 pc 00011f67 /system/lib/libc.so #04 pc 0002183c /system/lib/libc.so (abort+4) #05 pc 02591f34 /data/app-lib/org.example.libreoffice-2/liblo-native-code.so code around pc: 400d9f68 e8bd00f0 e3700a01 912fff1e e2600000 400d9f78 ea006f79 e92d50f0 e3a07f43 ef000000 400d9f88 e8bd50f0 e3700a01 912fff1e e2600000 400d9f98 ea006f71 e92d50f0 e3a070ee ef000000 400d9fa8 e8bd50f0 e3700a01 912fff1e e2600000 400d9fb8 ea006f69 00000000 e1520003 8a0000ab 400d9fc8 f5d1f040 e92d4001 e3520000 11500001 400d9fd8 08bd8001 f5d1f000 f5d1f040 e3520020 400d9fe8 3a00008f e3520080 3a000084 e2603000 400d9ff8 e213303f 0a000015 e0422003 e1b0cf83 400da008 44d1c001 44c0c001 24d1c001 24c0c001 400da018 24d1c001 24c0c001 e1b0ce83 5a000001 400da028 f4a1030d f480031d 3a000001 f421070d 400da038 f400071d e1b0cd83 5a000001 f4210a0d 400da048 f4000a2d 3a000001 f421020d f400023d 400da058 f5d1f080 f5d1f0c0 e3520902 3a000004 code around lr: 400cb000 447b4b13 42b3e010 4812d10e 44786a1e 400cb010 ec90f7fb e9d8f00d 46224631 efaef00e 400cb020 d00a3001 e00b2400 2b00681b 480ad1eb 400cb030 44782403 ec7ef7fb f001e002 6804fa1b 400cb040 fa18f001 46206005 bf00bd70 0003b3a2 400cb050 0003b396 0003b38e 0003b36a bf7ef7ff 400cb060 4a3e4b3d 43f0e92d 4606b08b 447b460d 400cb070 6823589c 930946a1 f9fcf001 8000f8d0 400cb080 d0482d00 f0104628 280ff80b d8444604 400cb090 ffe4f7ff d1064286 4629200f e8a2f00d 400cb0a0 d03c2800 482ee02e f7fb4478 482debc2 400cb0b0 e0154478 d11342b0 482b6a06 f7fb4478 400cb0c0 4a2aec3a 46332120 447aa801 fc24f013 400cb0d0 a8012101 ff22f01a 46061c42 e011d104 400cb0e0 28006800 e02cd1e6 46294630 f00d4622 400cb0f0 1c43e8de d11e4607 f9bcf001 29046801
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Still reproducible in Version: 6.0.0.0.alpha0+ Build ID: 386fcf9
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
wfm on current master, no crash