Bug 747389

Summary: LibreOffice Writer dont start
Product: [Fedora] Fedora Reporter: Miguel <luzemail>
Component: icuAssignee: Eike Rathke <erack>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: caolanm, denis.arnaud_fedora, dtardon, ltinkl, mstahl, oget.fedora, sbergman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-30 17:06:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Miguel 2011-10-19 17:10:34 UTC
Description of problem:
When I click at icon libreOffice, libreOffice boot screen appears but libreoffice writer doen't start

Version-Release number of selected component (if applicable):
LibreOffice 3.3.3 
OOO330m19 (Build:301)
Ver: 3.3.3.1-7.fc15


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
application doesn't start

Expected results:
application starts

Additional info:
oowriter 
/usr/lib/libreoffice/program/soffice: línea 163:  1760 Violación de segmento  (`core' generado) "$sd_prog/$sd_binary" "$@"

Comment 1 Orcan Ogetbil 2011-10-19 22:54:14 UTC
Hi, did you mean to file the bug against libreoffice, or did you select libqxt intentionally? Thanks.

Comment 2 Miguel 2011-10-19 22:57:30 UTC
my fault, i wan to select libreoffice.

Comment 3 Caolan McNamara 2011-10-20 08:44:01 UTC
Doesn't crash for everyone, so something specific to you there.

a) is there no "abrt" icon on your desktop with a crash report in it ?
b) if there isn't then can you try 
gdb /usr/lib/libreoffice/program/soffice.bin
(gdb) run
(gdb) backtrace

and paste the backtrace in here.

Could be a general busted install, there are rpm package verification possibilities to see if that's the case, e.g. http://www.rpm.org/max-rpm/ch-rpm-verify.html

Comment 4 Miguel 2011-10-22 10:01:44 UTC
Abrt doesn't appears 

using gdb , gives me these output:

 gdb /usr/lib/libreoffice/program/soffice.bin
GNU gdb (GDB) Fedora (7.3-43.fc15)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/lib/libreoffice/program/soffice.bin...(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install libreoffice-core-3.3.3.1-7.fc15.i686
(gdb) run
Starting program: /usr/lib/libreoffice/program/soffice.bin 
[Thread debugging using libthread_db enabled]
[New Thread 0xb7facb70 (LWP 1716)]
[New Thread 0xb5ea4b70 (LWP 1717)]
[New Thread 0xb54ffb70 (LWP 1718)]
[New Thread 0xb4affb70 (LWP 1719)]
[Thread 0xb5ea4b70 (LWP 1717) exited]
[New Thread 0xb5ea4b70 (LWP 1720)]
[New Thread 0xb42feb70 (LWP 1721)]
[Thread 0xb42feb70 (LWP 1721) exited]
[New Thread 0xb42feb70 (LWP 1722)]
Detaching after fork from child process 1723.
[New Thread 0xb362db70 (LWP 1725)]
[Thread 0xb362db70 (LWP 1725) exited]
[New Thread 0xb362db70 (LWP 1727)]
[Thread 0xb362db70 (LWP 1727) exited]

Program received signal SIGSEGV, Segmentation fault.
0x4f1cb4c1 in ?? () from /usr/lib/libicui18n.so.44
(gdb) backtrace
#0  0x4f1cb4c1 in ?? () from /usr/lib/libicui18n.so.44
#1  0x4e32f948 in icudt44_dat () from /usr/lib/libicudata.so.44
#2  0x00000000 in ?? ()
(gdb)

Comment 5 Caolan McNamara 2011-10-24 10:43:38 UTC
It's crashing in icu anyway, not LibreOffice itself. Again, because this isn't happening for everyone, there's something specifically wrong for you locally. I wonder if e.g. there's a corrupt library or something of that nature

either way, 
debuginfo-install libicu
to install the debuginfo for icu and try to get the backtrace again should give us a backtrace with line numbers in icu which should help

rpm --verify libicu
should help find out if libicu is ok or not

Comment 6 Fedora Admin XMLRPC Client 2011-10-25 14:11:21 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Miguel 2011-10-25 20:39:59 UTC
 rpm --verify libicu
prelink: /usr/lib/libicudata.so.44.2: prelinked file was modified
?S.......    /usr/lib/libicudata.so.44.2
prelink: /usr/lib/libicui18n.so.44.2: at least one of file's dependencies has changed since prelinking
?S.......    /usr/lib/libicui18n.so.44.2
prelink: /usr/lib/libicule.so.44.2: at least one of file's dependencies has changed since prelinking
?S.......    /usr/lib/libicule.so.44.2
prelink: /usr/lib/libicuuc.so.44.2: at least one of file's dependencies has changed since prelinking
?S.......    /usr/lib/libicuuc.so.44.2


it's ok?

Comment 8 Caolan McNamara 2011-10-27 08:53:56 UTC
prelink: /usr/lib/libicudata.so.44.2: prelinked file was modified

doesn't sound great to me. Try forcibly re-installing libicu, e.g.

rpm -e --nodeps libicu
yum -y install libicu

Comment 9 Miguel 2011-10-30 17:06:59 UTC
solved re-installing libicu

Thank you