Description: After kernel update on rolling release Linux, but before reboot. System/i was unable to load vfat/fat support modules. Since the modules directory for current running kernel is deleted, after update. Steps to Reproduce: 1.sudo mv /lib/modules/`uname -r`/kernel/fs/fat ~/. 2.reboot 3.Start LibreOffice. 4.Insert usbstick with fat filesystem. 3.Try to save something to usbstick from LibreOffice (Calc). Actual Results: Crashes when selecting usbmemory on file windows. Opens file recovery dialog. Starts LibreOffice. Expected Results: Something else. Message, something like 'Unable to support/open Device/filesystem'. Back to file dialog window. Reproducible: Always User Profile Reset: No Additional Info: sudo modprobe vfat modprobe: FATAL: Module vfat not found in directory /lib/modules/5.3.12-arch1-1 ls /lib/modules 5.3.13-arch1-1 As you can see the current running kernel 5.3.12 modules has been deleted.
Could you please paste the info from Help - about LibreOffice ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the information has been provided
Version: 6.3.3.2.0+ Build ID: 6.3.3-1 CPU threads: 16; OS: Linux 5.3; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded This release was supplied by Arch Linux. Copyright © 2000–2019 LibreOffice contributors. LibreOffice was based on OpenOffice.org.
Tried the dev build AppImage. Crashes and sent a crash report. Version: 6.4.0.0.beta1 Build ID: 4d7e5b0c40ed843384704eca3ce21981d4e98920 CPU threads: 16; OS: Linux 5.3; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded
(In reply to Markus Liukka from comment #0) > Steps to Reproduce: > 1.sudo mv /lib/modules/`uname -r`/kernel/fs/fat ~/. > 2.reboot > 3.Start LibreOffice. > 4.Insert usbstick with fat filesystem. > 3.Try to save something to usbstick from LibreOffice (Calc). It seems a step is missing. How can I try to save something to a USB stick, when I can't even see it after kernel update? And why do you have "2.reboot" while saying "before reboot" in the description?
(In reply to Buovjaga from comment #4) > (In reply to Markus Liukka from comment #0) > > Steps to Reproduce: > > 1.sudo mv /lib/modules/`uname -r`/kernel/fs/fat ~/. > > 2.reboot > > 3.Start LibreOffice. > > 4.Insert usbstick with fat filesystem. > > 3.Try to save something to usbstick from LibreOffice (Calc). > > It seems a step is missing. How can I try to save something to a USB stick, > when I can't even see it after kernel update? And why do you have "2.reboot" > while saying "before reboot" in the description? The description was the situation how it happened to me. I run pacman -Suy with sudo as usually, new kernel was installed, but not yet running. The Steps to reproduce simulates the situation i had, without updating the kernel (i tried this twice). The the step 2. maybe is unnecessary, but is there to be sure the module can't be loaded (not cached). I don't know why you can't see the device. I'm using Arch Linux with deepin-desktop, i can see the inserted usb device with thunar, deepins filemanager and appears in file-roller (and LibreOffice). Hope this clarifies it better. Do you see your usb memory with dmesg ? dmesg | tail [ 518.368117] usb-storage 3-4.1.2:1.0: USB Mass Storage device detected [ 518.368349] scsi host12: usb-storage 3-4.1.2:1.0 [ 519.392104] scsi 12:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 4 [ 519.392476] sd 12:0:0:0: Attached scsi generic sg4 type 0 [ 519.393110] sd 12:0:0:0: [sdd] 15728640 512-byte logical blocks: (8.05 GB/7.50 GiB) [ 519.393761] sd 12:0:0:0: [sdd] Write Protect is off [ 519.393765] sd 12:0:0:0: [sdd] Mode Sense: 23 00 00 00 [ 519.394406] sd 12:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 519.397970] sdd: sdd1 [ 519.400053] sd 12:0:0:0: [sdd] Attached SCSI removable disk
(In reply to Markus Liukka from comment #3) > Tried the dev build AppImage. Crashes and sent a crash report. Where can we find the report?
Reported replied privately. He did not note down the crash ID, so it would be good to make it crash again and report the ID here (sorry for the trouble).
This is from Version: 6.3.3.2. LibreOffice-fresh.basic-x86_64.AppImage http://crashreport.libreoffice.org/stats/crash_details/08b5f06f-d55d-473e-9a0a-8201d6d62492 Couldn't see the ID anywhere for the LibreOffice-6.4.0.0.beta1.en-GB-x86_64.AppImage Any logs possible ?
Hello Markus, A new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Created attachment 163403 [details] gdb backtrace
Tested with 6.4.5.2 Still crashes.
The bug is still present on 7.0.0.2 Tested with: LibreOffice-7.0.0.2.en-GB-x86_64.AppImage https://gerrit.libreoffice.org/gitweb?p=core.git;a=log;h=c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c (gdb) bt full #0 0x00007fb6fa35987c in read () from /usr/lib/libpthread.so.0 No symbol table info available. #1 0x00007fb6fa135d12 in ?? () from /usr/lib/libfuse.so.2 No symbol table info available. #2 0x00007fb6fa1378ae in ?? () from /usr/lib/libfuse.so.2 No symbol table info available. #3 0x00007fb6fa135fb9 in fuse_session_loop () from /usr/lib/libfuse.so.2 No symbol table info available. #4 0x000000000040e764 in fusefs_main () No symbol table info available. #5 0x0000000000405d6f in main () No symbol table info available.
(In reply to Markus Liukka from comment #12) > The bug is still present on 7.0.0.2 > Tested with: LibreOffice-7.0.0.2.en-GB-x86_64.AppImage > > https://gerrit.libreoffice.org/gitweb?p=core.git;a=log; > h=c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c > > (gdb) bt full > #0 0x00007fb6fa35987c in read () from /usr/lib/libpthread.so.0 > No symbol table info available. > #1 0x00007fb6fa135d12 in ?? () from /usr/lib/libfuse.so.2 > No symbol table info available. > #2 0x00007fb6fa1378ae in ?? () from /usr/lib/libfuse.so.2 > No symbol table info available. > #3 0x00007fb6fa135fb9 in fuse_session_loop () from /usr/lib/libfuse.so.2 > No symbol table info available. > #4 0x000000000040e764 in fusefs_main () > No symbol table info available. > #5 0x0000000000405d6f in main () > No symbol table info available. Hello Markus, You are trying with the AppImage. What about the installers from https://www.libreoffice.org/download/libreoffice-fresh/ ? Do they also crash or is it AppImage crash only ?
(In reply to Xisco Faulí from comment #13) > Hello Markus, > You are trying with the AppImage. What about the installers from > https://www.libreoffice.org/download/libreoffice-fresh/ ? Do they also crash > or is it AppImage crash only ? He wasn't trying with appimage only. It was reported against Arch Linux packages.
Thanks for reporting this issue. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Markus Liukka, 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
Dear Markus Liukka, 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-FollowUp