https://bugs.documentfoundation.org/show_bug.cgi?id=151917
Bug ID: 151917
Summary: Calc crashes on loading spreadsheet and corrupts user
profile
Product: LibreOffice
Version: 7.4.2.3 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: [email protected]
Reporter: [email protected]
I am trying to open a normal spreadsheet file, and everytime i start
libreoffice (calc) directly (through double clicking the file), the calc just
crashes and the splash (in a very tiny window) remains indefinitely, same
behavior when using `libreoffice --calc /path/to/file`, though when started
through the libreoffice launcher (just `libreoffice`) and clicking on the file
/ starting calc, it just works without problems, same happens when not starting
with any file.
I had already tried to remove "~/.config/libreoffice", where it ran at first
but after a system restart that new profile was also "corrupted".
When started once through the launcher (just `libreoffice`), then it will also
start directly unless the machine is rebooted.
I had also already tried to attach with gdb to the remaining splash, which gave
the following:
```txt
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x00007f4c5781f0bf in __GI___poll (fds=0x5567d8915890, nfds=1, timeout=3000) at
../sysdeps/unix/sysv/linux/poll.c:29
Downloading 0.00 MB source file
/usr/src/debug/glibc/io/../sysdeps/unix/sysv/linux/poll.c
29 return SYSCALL_CANCEL (poll, fds, nfds, timeout);
(gdb) bt
#0 0x00007f4c5781f0bf in __GI___poll (fds=0x5567d8915890, nfds=1,
timeout=3000) at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007f4c506e41df in g_main_context_poll (priority=<optimized out>,
n_fds=1, fds=0x5567d8915890, timeout=<optimized out>, context=0x7f4c44005070)
at ../glib/glib/gmain.c:4543
#2 g_main_context_iterate.constprop.0 (context=0x7f4c44005070, block=1,
dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4233
#3 0x00007f4c5068c132 in g_main_context_iteration (context=0x7f4c44005070,
may_block=1) at ../glib/glib/gmain.c:4303
#4 0x00007f4c4dad750c in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib/libQt5Core.so.5
#5 0x00007f4c4ddc4cae in QtInstance::ImplYield(bool, bool) () at
/usr/lib/libreoffice/program/libvclplug_qt5lo.so
#6 0x00007f4c4ddc4d9f in QtInstance::DoYield(bool, bool) () at
/usr/lib/libreoffice/program/libvclplug_qt5lo.so
#7 0x00007f4c540f3753 in () at /usr/lib/libreoffice/program/libvcllo.so
#8 0x00007f4c540f996e in Application::Execute() () at
/usr/lib/libreoffice/program/libvcllo.so
#9 0x00007f4c57970c8c in () at /usr/lib/libreoffice/program/libsofficeapp.so
#10 0x00007f4c5410711a in ImplSVMain() () at
/usr/lib/libreoffice/program/libvcllo.so
#11 0x00007f4c57987b64 in soffice_main () at
/usr/lib/libreoffice/program/libsofficeapp.so
#12 0x00005567d6649031 in ()
#13 0x00007f4c57747290 in __libc_start_call_main
(main=main@entry=0x5567d6649020, argc=argc@entry=4,
argv=argv@entry=0x7ffc93a66e28)
at ../sysdeps/nptl/libc_start_call_main.h:58
#14 0x00007f4c5774734a in __libc_start_main_impl
(main=0x5567d6649020, argc=4, argv=0x7ffc93a66e28, init=<optimized out>,
fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc93a66e18)
at ../csu/libc-start.c:381
#15 0x00005567d6649065 in ()
(gdb) exit
A debugging session is active.
Inferior 1 [process 56818] will be detached.
Quit anyway? (y or n) y
Detaching from program: /usr/lib/libreoffice/program/soffice.bin, process 56818
[Inferior 1 (process 56818) detached]
```
I had also already tried to run the application through gdb from start to
finish, but could never get it to break for a backtrace.
System Information:
Operating System: Manjaro Linux
KDE Plasma Version: 5.26.2
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Kernel Version: 6.0.6-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX Vega
Manufacturer: MSI
Product Name: MS-7972
System Version: 2.0
It also happens on a completely (aside from also using manjaro) different
system and when using the flatpak version.
PS: there are no reported core-dumps or logs in the console (that are different
than starting through the launcher)
--
You are receiving this mail because:
You are the assignee for the bug.
