Bug 48398

Summary:	CONFIGURATION: LibreOffice fails to start after upgrading to 3.5.2
Product:	LibreOffice	Reporter:	keellambert <keel_lambert>
Component:	Installation	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED NOTABUG
Severity:	critical	CC:	keel_lambert
Priority:	highest
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:	BSA
Crash report or crash signature:		Regression By:

Description keellambert 2012-04-06 14:04:58 UTC

Problem description: 

Steps to reproduce:
1. install from LibO_3.5.2_Linux_x86-64_install-rpm_en-US.tar.gz from LO website
2. start from terminal or icon
3. ....

Current behavior:
welcome screen shows program initializing ...
then just terminates without warning

Expected behavior:
selected program expect to open for use

Platform (if different from the browser): 
Kernel: 3.3.1-1-desktop x86_64 (64 bit) Desktop KDE 4.8.2 Distro: openSUSE 12.1
Mobo: A880G+ Bios: American Megatrends version: 080016 date: 01/25/2011
Quad core AMD Phenom II X4 965
Graphics: Card: ATI RS880 [Radeon HD 4250] X.Org: 1.10.4 driver: fglrx Resolution: 1680x1050@60.0hz
GLX Renderer: ATI Radeon HD 4250 GLX Version: 3.3.11566 - CPC 
              
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0

libreoffice3.5.2 is now installed and working.
it would not run before the package : libreoffice3.5-stdlibs-3.5.2-202.x86_64.rpm was deleted.

a similar issue was encountered installing from LibO_3.5.1_Linux_x86-64_install-rpm_en-US.tar.gz

on all previous installs no problem was encountered

Comment 1 keellambert 2012-04-09 18:14:46 UTC

today another similar machine was upgraded to libreoffice 3.5.2-202.x86_64, 
before libreoffice 3.5.1-102.x86_64 had been installed,
no problems were encountered running any of the programs after installation

hence I returned to the machine which did have problems and did a re-install,
again no problems occurred

so today the problem reported cannot be reproduced,
minor updates have occurred to the os's over the weekend

unless other people report the same difficulty,
it's suggested this bug report be closed

Comment 2 Florian Reisinger 2012-04-10 00:08:09 UTC

OK, good to here, that you do not suffer from such a problem anymore...