Bug 129035 - LO Linux Crash when trying to save to usbmemory (fat).
Summary: LO Linux Crash when trying to save to usbmemory (fat).
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.3.3.2 release
Hardware: All Linux (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Save Crash
  Show dependency treegraph
 
Reported: 2019-11-26 09:29 UTC by Markus Liukka
Modified: 2022-11-30 03:48 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
gdb backtrace (12.17 KB, application/x-troff-man)
2020-07-22 12:44 UTC, Markus Liukka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Liukka 2019-11-26 09:29:19 UTC
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.
Comment 1 Xisco Faulí 2019-11-26 10:59:35 UTC
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
Comment 2 Markus Liukka 2019-11-26 11:15:18 UTC
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.
Comment 3 Markus Liukka 2019-11-26 12:26:16 UTC
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
Comment 4 Buovjaga 2019-12-03 06:40:06 UTC
(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?
Comment 5 Markus Liukka 2019-12-03 07:38:29 UTC
(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
Comment 6 Buovjaga 2019-12-03 10:12:58 UTC
(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?
Comment 7 Buovjaga 2019-12-03 11:32:14 UTC
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).
Comment 8 Markus Liukka 2019-12-03 14:29:42 UTC
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 ?
Comment 9 Xisco Faulí 2020-06-18 10:34:23 UTC
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.
Comment 10 Markus Liukka 2020-07-22 12:44:58 UTC
Created attachment 163403 [details]
gdb backtrace
Comment 11 Markus Liukka 2020-07-22 12:51:50 UTC
Tested with 6.4.5.2
Still crashes.
Comment 12 Markus Liukka 2020-07-22 13:47:47 UTC
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.
Comment 13 Xisco Faulí 2021-07-07 10:42:03 UTC
(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 ?
Comment 14 Buovjaga 2021-07-07 10:47:42 UTC
(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.
Comment 15 Xisco Faulí 2022-05-02 11:57:58 UTC
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.
Comment 16 QA Administrators 2022-10-30 03:47:13 UTC Comment hidden (obsolete)
Comment 17 QA Administrators 2022-11-30 03:48:36 UTC
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