FS#39038 - [libreoffice-writer] updating from v4.1.5-1 to v4.2.1-1 causes lowriter to fail to start

Attached to Project: Arch Linux
Opened by Myra Nelson (myra) - Tuesday, 25 February 2014, 06:47 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 09 March 2014, 11:20 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Andreas Radke (AndyRTR)
Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After the latest writer upgrade (to version 4.2.1-1), lowriter fails to run.

Additional info:
* 4.1.5-1 to 4.2.1-1
Downgrading to 4.1.5-1 solves the problem.

Steps to reproduce:
Upgrade libreoffice from version 4.1.5-1 to 4.2.1-1
lowriter fails to run.

I get the following error message when trying to start it from a
console.

/usr/lib/libreoffice/program/soffice.bin: error while loading shared
libraries: libtubeslo.so: cannot open shared object file: No such file
or directory

From a thread I started on the arch-general mailing list

pkgfile libtubeslo.so
testing/libreoffice-calc

This would seem to make libreoffice-writer dependent on libreoffice-calc being installed.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 09 March 2014, 11:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in trunk, 4.2.2 will contain a workaround until upstream fixes this.
Comment by Andreas Radke (AndyRTR) - Tuesday, 25 February 2014, 16:23 GMT
I guess it should either not link to libtubeslo.so or this lib should better go into -common pkg.
We use recommended upstream pkg splitting. So please check for a known upstream bug or
file one / talk to the guys in #libreoffice-dev.
Comment by Myra Nelson (myra) - Sunday, 02 March 2014, 23:35 GMT
I think I have this properly reported upstream to the freedesktop bugzilla tracker for libreoffice as id #75506.
Comment by Myra Nelson (myra) - Monday, 03 March 2014, 23:34 GMT
Andreas and all:

Your probably right about this. The initial failure was from the packages in the testing repo. Unfortunately I am to check into the hospital in the morning and won't have time to pursue this for at least another week, assuming the surgery goes well. Might be longer than that.

Loading...