LibreOffice RPM crashes repeatedly after disk migration

jbhughes54enwiler · December 30, 2024, 2:43pm

I am not sure if this is a bug or something arising out of me recently migrating my entire Fedora 41 KDE system over to a new SSD using Clonezilla Live, but now when I attempt to start LibreOffice Writer, about 80% of the time it will crash into document recovery.

I’ve tried reinstalling it twice, and that didn’t fix the issue. The Flatpak version seems to work but doesn’t have the integrations with KDE that I prefer (namely the theme and universal menu)

I am running Fedora 41 with KDE Plasma 6.2.4 on the Linux 6.12.5-200.fc41.x86_64 kernel. The LibreOffice version I have installed is:

Version: 24.8.4.2 (X86_64)
Build ID: 480(Build:2)
CPU threads: 16; OS: Linux 6.12; UI render: default; VCL: kf6 (cairo+wayland)
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

ajlittoz · December 30, 2024, 3:00pm

Have you a “complex” partitioning scheme?

In a terminal, type the following commands and report what they answer:

cat /etc/fstab
df -h | grep -v tmpfs

jbhughes54enwiler · December 30, 2024, 3:45pm

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p3 during curtin installation
/dev/disk/by-uuid/f65e35c4-9d9b-4b3e-a8a0-bb825a96e5fa / ext4 defaults 0 1
# /boot/efi was on /dev/nvme0n1p2 during curtin installation
/dev/disk/by-uuid/3237-02F5 /boot/efi vfat defaults 0 1
/swap.img       none    swap    sw      0       0

Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p1  822G  412G  369G  53% /
efivarfs        268K  127K  137K  49% /sys/firmware/efi/efivars
/dev/nvme0n1p2  1.1G  6.2M  1.1G   1% /boot/efi

I should note that in order for me to be able to get my cloned Fedora installation to boot, I had to install Ubuntu into a small partition to create a new efi partition then I copied the fstab file from Ubuntu into Fedora.

ajlittoz · December 30, 2024, 4:29pm

You seem to have a very basic partitioned scheme. I prefer to have /home in a separate partition so that I can reinstall the OS from scratch without erasing user data.

Mmh! Mixing two distros is a bit hazardous. Fedora and Debian (Ubuntu is a fork from Debian) use different configurations in /etc. It is mainly important for servers but there may quirks for other parts of the system.

I wouldn’t copy fstab from one distro to another without careful analysis of the contents. Your drives are designated by UUID. I had issues in the past when I had to reformat disks or partitions. This causes the UUID to change. I prefer to configure for LABEL= or as an ultimate fallback by device internal name /dev/disk0part1 (but the “0” and “1” may change depending on scanning order in the BIOS/UEFI).

If you can boot, this is not the cause of your problem. However, if you feel brave, make a copy of /etc/fstab and replace the UUID designation by /dev/nvme0n1p1 for / and /dev/nvme/0n1/p2 for /boot/.

What did you exactly transfer? Full disk, OS + user data? Or only user data from /home? It is usually safer to reinstall clean the OS from distro utility, then reload user data. Unfortunately, your /home is not separate which creates links between OS space in / and /home (single partition).

Something may be corrupted in your user profile. Rename it to save it and restart LO:

mv ~/.config/libreoffice/4 ~/.config/libreoffice/saved_user_profile

A new user profile will be created.

Does it improve the situation?

jbhughes54enwiler · December 30, 2024, 4:34pm

That command fixed it, thanks!

As for the very messy move, I wanted to migrate my system completely without having to reinstall anything, fix up all my settings, and sign back into all my accounts. I figured just cloning the partition Fedora was on (My old SSD dual-booted Windows and Fedora) would be enough to move my system over, but things got a little crazy. Other than LibreOffice borking and secure boot being broken, everything works just as it did on the old system, which is more or less exactly what I wanted.