Bug 91359 - LibO unusable with parameters on Raspberry Pi (segfault)
Summary: LibO unusable with parameters on Raspberry Pi (segfault)
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.6.1.2 release
Hardware: ARM Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-18 12:54 UTC by sendmethat
Modified: 2016-01-01 16:59 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description sendmethat 2015-05-18 12:54:33 UTC 
On the Raspberry Pi B (2015-05-05-raspbian-wheezy), Libre Office (from the Raspberry Pi repositories) won't work or even segfaults, when started with parameters.

Example:
loimpress --show results in "unknown option" and a suggestion to use --help.
loimpress --help or libreoffice --help results in segmentation fault.

from gdb, when using --help parameter:
Program received signal SIGSEGV, Segmentation fault.
0xb6b52c34 in ?? ()
   from /usr/lib/libreoffice/program/../ure-link/lib/libuno_cppu.so.3
Comment 1 Jan 2015-05-19 11:28:20 UTC 
Did you file a bug with raspbian? If not, please do so! In both cases, please provide a reference here. This may also be a raspbian/debian issue and we should at least let them know that it exists.

Additionally, other people there may be able to reproduce the problem. Unfortunately, not everybody in the Libreoffice QA team has a raspberry Pi B with raspbian as a desktop ;-).
Comment 2 tommy27 2015-10-04 15:44:58 UTC 
I see you report the bug agains LibO 3.6.2 release which is obsolete and no longer supported.

I do not have experience about Raspberry Pi repositories... are they now up to date with latest 4.4.5.2 LibO release?

if YES, try that version and tell if issue persists
if NO and they continue offering an obsolete LibO version there's no way we can fix it.

status NEEDINFO
Comment 3 Julien Nabet 2016-01-01 16:59:42 UTC 
No feedback since 6 months anyway.