Bug 52479 - : soffice line 162 segmentation fault
Summary: : soffice line 162 segmentation fault
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.5.5.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-25 11:38 UTC by pd
Modified: 2012-10-20 10:09 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pd 2012-07-25 11:38:25 UTC
Problem description: 
LO stops/exits loading just after start splash screen.

Launching from a terminal with -h option returns: "/usr/lib64/libreoffice/program/soffice: line 162:  3794 Segmentation fault"

With no -h option, LO just exits with no message.

The segmentation fault number is different each time "libreoffice -h" is invoked.

Steps to reproduce:
1. At a terminal type "libreoffice -h"
2. .... 
3. ....

Current behavior:

Expected behavior:

Platform (if different from the browser):
LO rpm packages version is 3.5.5.3-0.3.mga2

              
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.6) Gecko/20100101 Firefox/10.0.6
Comment 1 Stephan Bergmann 2012-07-25 12:01:19 UTC
@pd:  Please run soffice.bin within gdb to get some more information about why it crashes.  From a terminal,

  gdb /usr/lib64/libreoffice/program/soffice.bin

then at the gdb prompt

  run

then once it returns to the prompt saying it received a SIGSEGV

  thread apply all bt

and make all the output available.
Comment 2 pd 2012-07-25 13:01:02 UTC
(In reply to comment #1)
> @pd:  Please run soffice.bin within gdb to get some more information about why
> it crashes.  From a terminal,
> 
>   gdb /usr/lib64/libreoffice/program/soffice.bin
> 
> then at the gdb prompt
> 
>   run
> 
> then once it returns to the prompt saying it received a SIGSEGV
> 
>   thread apply all bt
> 
> and make all the output available.

Hello Steve,

Here is the run:

[pd@localhost ~]$ gdb /usr/lib64/libreoffice/program/soffice.bin
GNU gdb (GDB) 7.3.50.20110722-4.mga2 (Mageia release 2)
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 "x86_64-mageia-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/lib64/libreoffice/program/soffice.bin...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/lib64/libreoffice/program/soffice.bin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffed36a700 (LWP 4456)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff61e5dbc in ?? ()
   from /usr/lib64/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
(gdb) thread apply all bt

Thread 2 (Thread 0x7fffed36a700 (LWP 4456)):
#0  0x00007ffff71708fe in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
#1  0x00007ffff7bb728f in ?? ()
   from /usr/lib64/libreoffice/program/../ure-link/lib/libuno_sal.so.3
#2  0x00007ffff716cb99 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff765f0cd in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ffff7fb98a0 (LWP 4452)):
#0  0x00007ffff61e5dbc in ?? ()
   from /usr/lib64/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
#1  0x000000af00000000 in ?? ()
#2  0x000000b1000000b0 in ?? ()
#3  0x000000b200000000 in ?? ()
#4  0xffffdae000000000 in ?? ()
#5  0xffffdb5000007fff in ?? ()
#6  0x0000000d00007fff in ?? ()
#7  0xffffb26000000000 in ?? ()
#8  0xf2b632fe00007fff in ?? ()
#9  0xf7fcd6c800007fff in ?? ()
#10 0xf2b4bf2800007fff in ?? ()
#11 0xf7fc6ec000007fff in ?? ()
#12 0xf7deb17700007fff in ?? ()
#13 0xf7fd35d000007fff in ?? ()
#14 0xf7fd3ae800007fff in ?? ()
#15 0xf7fd205000007fff in ?? ()
#16 0xf7ffa7e000007fff in ?? ()
#17 0xf7fd44d000007fff in ?? ()
#18 0xf7fd49a000007fff in ?? ()
#19 0xf7fd300000007fff in ?? ()
#20 0xf7ff94e800007fff in ?? ()
#21 0x0000000000007fff in ?? ()
#22 0xf2dcccb000000000 in ?? ()
#23 0xb6a0000000007fff in ?? ()
#24 0x0000000dffffffff in ?? ()
#25 0xffffb26000000000 in ?? ()
#26 0xf2b632fe00007fff in ?? ()
#27 0xf7fcd6c800007fff in ?? ()
#28 0x6200000000007fff in ?? ()
#29 0x91960000ffffffff in ?? ()
#30 0x00000003ffffefbd in ?? ()
#31 0xffffb26000000000 in ?? ()
#32 0xf2b6328000007fff in ?? ()
#33 0xf7fcd6c800007fff in ?? ()
#34 0x6260000000007fff in ?? ()
---Type <return> to continue, or q <return> to quit---
#35 0x91960000ffffffff in ?? ()
#36 0x00000000ffffefbd in ?? ()
#37 0x0000000000000000 in ?? ()
(gdb) ^Z
[1]+  Stopped                 gdb /usr/lib64/libreoffice/program/soffice.bin
[pd@localhost ~]$ 

Hope it helps.

PD
Comment 3 Stephan Bergmann 2012-07-25 13:41:59 UTC
(In reply to comment #2)
> Hope it helps.

No, unfortunately not.  For some reason, gdb refuses to even print minimal (exported) symbol information.

What kind of Linux distro is that, and where did you get the rpms from?
Comment 4 Stephan Bergmann 2012-07-25 13:45:11 UTC
(In reply to comment #3)
> What kind of Linux distro is that, and where did you get the rpms from?

Ah, nevermind, looks like its Mageia.  Maybe you can get some help there (or at least clarification whether other Mageia users suffer from the same problem).
Comment 5 pd 2012-07-25 15:41:12 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > What kind of Linux distro is that, and where did you get the rpms from?
> 
> Ah, nevermind, looks like its Mageia.  Maybe you can get some help there (or at
> least clarification whether other Mageia users suffer from the same problem).

Will do.

Thank you for your time.
Comment 6 Julien Nabet 2012-08-05 13:56:46 UTC
Is it a first LO install ?
If not:
- was it the same with the previous version you had ?
- did you try with a brand new LO profile ? (see http://wiki.documentfoundation.org/UserProfile)

Could you give the details of your Java version and details about your distribution ?
Comment 7 pd 2012-08-06 10:10:59 UTC
(In reply to comment #6)
> Is it a first LO install ?
> If not:
> - was it the same with the previous version you had ?
> - did you try with a brand new LO profile ? (see
> http://wiki.documentfoundation.org/UserProfile)
> 
> Could you give the details of your Java version and details about your
> distribution ?

Hello Julien,

No, the machine has not had a clean install for some time now as the /home directory has been kept through a number of upgrades, installations and reinstallations.

Thanks for the link, it must be a mix-up of old/new/multiple/corrupted config files as suggested. This is also indicated by the fact that it is the only machine of 6 with this problem.

I will try with a new LO config file and let you all know of the result.
Comment 8 Julien Nabet 2012-10-19 23:15:53 UTC
pd: any  update about this tracker?
Comment 9 pd 2012-10-20 10:04:23 UTC
(In reply to comment #8)
> pd: any  update about this tracker?

Hello Julien,

No, we have not got around to do a clean install on the machine. At the latest, this will happen with the next distro version/upgrade.

In the meantime if anybody wants me to check/test any config files, please let me know.
Comment 10 Julien Nabet 2012-10-20 10:09:18 UTC
pd: thank you for your feedback. I'll put this tracker to RESOLVED/INVALID for the moment. Of course, when your machine will be cleaned and if you reproduce the problem of course, don't hesitate to reopen the tracker.