Bug 684578

Are you sure it is not running already in the background? I.e., no LibO application can be started if the presentation wizard is running. If that is not the case, does it help if you move ~/.libreoffice away?

"I especially like the first screen that comes up with all the icons for the
applications in each division." does this mean that it *does* appear, or that it doesn't appear. Please describe your problem without the assumption that we see exactly what you do.

I experienced this bug recently. I had four tabs open in chrome (they were not resource heavy). I downloaded two.ppt documents in chrome, and then attempted to open both of them by double clicking on each. My operating system froze, it seemed like there was some serious memory usage, and then LibreOffice crashed. 

I tried it again, this time only clicking on one file, with only one or two chrome tabs open, to reduce memory useage. The OS froze, and eventually even the mouse pointer stopped moving. I had to reboot.

This was on Fedora 15, x86, with 1 GB of RAM.

Are these two different bug reports or the same one ? e.g the first bug report seemed to describe LibreOffice hanging when simply launched (or maybe only showing the frame window with the embedded launcher buttons, or maybe simply not doing anything at all, its unclear to me), and the second about the system hanging on opening some .ppt files, or are they both actually the same report.

Magellan: Simplify your specific problem by e.g. sticking the .ppt files onto your desktop and just double click the problematic one to see if just launching libreoffice on that .ppt reproduces your problem. If it does, then just attach it here and we'll see if we can reproduce that ourselves.

(In reply to comment #4)
> Are these two different bug reports or the same one ? e.g the first bug report
> seemed to describe LibreOffice hanging when simply launched (or maybe only
> showing the frame window with the embedded launcher buttons, or maybe simply
> not doing anything at all, its unclear to me), and the second about the system
> hanging on opening some .ppt files, or are they both actually the same report.
> 
> Magellan: Simplify your specific problem by e.g. sticking the .ppt files onto
> your desktop and just double click the problematic one to see if just launching
> libreoffice on that .ppt reproduces your problem. If it does, then just attach
> it here and we'll see if we can reproduce that ourselves.

Okay, so I've managed to reproduce it consistently in a very simplified way.

1. Boot into Fedora 15
2. Click on activities, search for Libre Office Impress
3. Click on Libre Office Impress Icon

Actual Result: LibreOffice Crashes
Expected Result: Impress Opens

It's been detected by Automatic Bug Report Tool.

Application: usr/lib/libreoffice/program/simpress.bin

(In reply to comment #4)
> Are these two different bug reports or the same one ? e.g the first bug report
> seemed to describe LibreOffice hanging when simply launched (or maybe only
> showing the frame window with the embedded launcher buttons, or maybe simply
> not doing anything at all, its unclear to me), and the second about the system
> hanging on opening some .ppt files, or are they both actually the same report.
> 
> Magellan: Simplify your specific problem by e.g. sticking the .ppt files onto
> your desktop and just double click the problematic one to see if just launching
> libreoffice on that .ppt reproduces your problem. If it does, then just attach
> it here and we'll see if we can reproduce that ourselves.

Okay, so I've managed to reproduce it consistently in a very simplified way.

1. Boot into Fedora 15
2. Click on activities, search for Libre Office Impress
3. Click on Libre Office Impress Icon

Actual Result: LibreOffice Crashes
Expected Result: Impress Opens

It's been detected by Automatic Bug Report Tool.

Application: usr/lib/libreoffice/program/simpress.bin

Works fine here on F-15 (x86_64). If there was an abrt capture, then running the abrt tool and click through its report process in order to autodownload the debuginfo and get a backtrace is necessary to see where its crashing.

*might* be something like a home dir shared across different architecture ?

(In reply to comment #7)
> Works fine here on F-15 (x86_64). If there was an abrt capture, then running
> the abrt tool and click through its report process in order to autodownload the
> debuginfo and get a backtrace is necessary to see where its crashing.
> 
> *might* be something like a home dir shared across different architecture ?

I have created a youtube channel, just to upload this video showcasing the bug in F15:

http://www.youtube.com/watch?v=o1WCDj8Tjd0

I'm having trouble filing a bug report. I have tried to manually install the debuginfo, but it's still a no go. 

Let me know if you need anymore information, or what I can try to do to file a bug report.

at the end of the video I can see that the abrt dialog says "SIGBUS" which is interesting

open a terminal and 
debuginfo-install libreoffice
gdb /usr/lib/libreoffice/program/soffice.bin
run
wait for it to crash
bt

attach here the output of the bt (backtrace)

if you could at the same time open another terminal and 
tail -f /var/log/messages and see what messages appear in /var/log/messages between launching libreoffice and it crashing there might be some nuggets of into in there as well

[CODE]
Program received signal SIGBUS, Bus error.
_dl_setup_hash (map=0xb7feac98) at dl-lookup.c:870
870	      map->l_nbuckets = *hash32++;

[/CODE]


Backtrace
[CODE]#0  _dl_setup_hash (map=0xb7feac98) at dl-lookup.c:870
#1  0x42b2cec5 in _dl_map_object_from_fd (name=0x44d93d4a "libsfxli.so", 
    fd=-1, fbp=0xbfffeb1c, 
    realname=0xb7feac58 "/usr/lib/libreoffice/program/../basis-link/program/libsfxli.so", loader=0xb7fff910, l_type=1, mode=0, stack_endp=0xbfffed24, nsid=0)
    at dl-load.c:1451
#2  0x42b2e53f in _dl_map_object (loader=0xb7fff910, 
    name=0x44d93d4a "libsfxli.so", type=1, trace_mode=0, mode=0, nsid=0)
    at dl-load.c:2250
#3  0x42b334a8 in openaux (a=0xbffff210) at dl-deps.c:65
#4  0x42b353ef in _dl_catch_error (objname=0xbffff22c, errstring=0xbffff228, 
    mallocedp=0xbffff233, operate=0x42b33460 <openaux>, args=0xbffff210)
    at dl-error.c:178
#5  0x42b33a8f in _dl_map_object_deps (map=0x42b468f8, 
    preloads=<optimized out>, npreloads=<optimized out>, trace_mode=0, 
    open_mode=0) at dl-deps.c:247
#6  0x42b2914a in dl_main (phdr=0x8048034, phnum=8, user_entry=0xbffff3b4, 
    auxv=0xbffff4e4) at rtld.c:1805
#7  0x42b3b194 in _dl_sysdep_start (start_argptr=0xbffff420, 
    dl_main=0x42b280e0 <dl_main>) at ../elf/dl-sysdep.c:244
#8  0x42b2b2c4 in _dl_start_final (arg=0xbffff420) at rtld.c:334
#9  _dl_start (arg=0xbffff420) at rtld.c:560
#10 0x42b27197 in _start () from /lib/ld-linux.so.2
[/CODE]

log messages:


Mar 16 16:09:03 magellantwo kernel: [13472.674258] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 16 16:09:03 magellantwo kernel: [13472.674267] ata1.00: BMDMA stat 0x5
Mar 16 16:09:03 magellantwo kernel: [13472.674274] ata1.00: failed command: READ DMA
Mar 16 16:09:03 magellantwo kernel: [13472.674288] ata1.00: cmd c8/00:08:60:79:bc/00:00:00:00:00/e1 tag 0 dma 4096 in
Mar 16 16:09:03 magellantwo kernel: [13472.674292]          res 51/40:08:60:79:bc/00:00:00:00:00/e1 Emask 0x9 (media error)
Mar 16 16:09:03 magellantwo kernel: [13472.674299] ata1.00: status: { DRDY ERR }
Mar 16 16:09:03 magellantwo kernel: [13472.674305] ata1.00: error: { UNC }
Mar 16 16:09:03 magellantwo kernel: [13472.683642] ata1.00: configured for UDMA/100
Mar 16 16:09:03 magellantwo kernel: [13472.683664] ata1: EH complete
Mar 16 16:09:06 magellantwo kernel: [13476.557254] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 16 16:09:06 magellantwo kernel: [13476.557263] ata1.00: BMDMA stat 0x5
Mar 16 16:09:06 magellantwo kernel: [13476.557271] ata1.00: failed command: READ DMA
Mar 16 16:09:06 magellantwo kernel: [13476.557285] ata1.00: cmd c8/00:08:60:79:bc/00:00:00:00:00/e1 tag 0 dma 4096 in
Mar 16 16:09:06 magellantwo kernel: [13476.557288]          res 51/40:08:60:79:bc/00:00:00:00:00/e1 Emask 0x9 (media error)
Mar 16 16:09:06 magellantwo kernel: [13476.557296] ata1.00: status: { DRDY ERR }
Mar 16 16:09:06 magellantwo kernel: [13476.557301] ata1.00: error: { UNC }
Mar 16 16:09:07 magellantwo kernel: [13476.566611] ata1.00: configured for UDMA/100
Mar 16 16:09:07 magellantwo kernel: [13476.566636] ata1: EH complete
Mar 16 16:09:10 magellantwo kernel: [13480.451365] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 16 16:09:10 magellantwo kernel: [13480.451374] ata1.00: BMDMA stat 0x5
Mar 16 16:09:10 magellantwo kernel: [13480.451381] ata1.00: failed command: READ DMA
Mar 16 16:09:10 magellantwo kernel: [13480.451395] ata1.00: cmd c8/00:08:60:79:bc/00:00:00:00:00/e1 tag 0 dma 4096 in
Mar 16 16:09:10 magellantwo kernel: [13480.451399]          res 51/40:08:60:79:bc/00:00:00:00:00/e1 Emask 0x9 (media error)
Mar 16 16:09:10 magellantwo kernel: [13480.451406] ata1.00: status: { DRDY ERR }
Mar 16 16:09:10 magellantwo kernel: [13480.451411] ata1.00: error: { UNC }
Mar 16 16:09:10 magellantwo kernel: [13480.460615] ata1.00: configured for UDMA/100
Mar 16 16:09:10 magellantwo kernel: [13480.460637] ata1: EH complete
Mar 16 16:09:14 magellantwo kernel: [13484.544577] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 16 16:09:14 magellantwo kernel: [13484.544586] ata1.00: BMDMA stat 0x5
Mar 16 16:09:14 magellantwo kernel: [13484.544593] ata1.00: failed command: READ DMA
Mar 16 16:09:14 magellantwo kernel: [13484.544607] ata1.00: cmd c8/00:08:60:79:bc/00:00:00:00:00/e1 tag 0 dma 4096 in
Mar 16 16:09:14 magellantwo kernel: [13484.544611]          res 51/40:08:60:79:bc/00:00:00:00:00/e1 Emask 0x9 (media error)
Mar 16 16:09:14 magellantwo kernel: [13484.544618] ata1.00: status: { DRDY ERR }
Mar 16 16:09:14 magellantwo kernel: [13484.544624] ata1.00: error: { UNC }
Mar 16 16:09:14 magellantwo kernel: [13484.553628] ata1.00: configured for UDMA/100
Mar 16 16:09:14 magellantwo kernel: [13484.553650] ata1: EH complete
Mar 16 16:09:18 magellantwo kernel: [13488.405463] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 16 16:09:18 magellantwo kernel: [13488.405472] ata1.00: BMDMA stat 0x5
Mar 16 16:09:18 magellantwo kernel: [13488.405480] ata1.00: failed command: READ DMA
Mar 16 16:09:18 magellantwo kernel: [13488.405494] ata1.00: cmd c8/00:08:60:79:bc/00:00:00:00:00/e1 tag 0 dma 4096 in
Mar 16 16:09:18 magellantwo kernel: [13488.405497]          res 51/40:08:60:79:bc/00:00:00:00:00/e1 Emask 0x9 (media error)
Mar 16 16:09:18 magellantwo kernel: [13488.405504] ata1.00: status: { DRDY ERR }
Mar 16 16:09:18 magellantwo kernel: [13488.405510] ata1.00: error: { UNC }
Mar 16 16:09:18 magellantwo kernel: [13488.414601] ata1.00: configured for UDMA/100
Mar 16 16:09:18 magellantwo kernel: [13488.414623] ata1: EH complete
Mar 16 16:09:22 magellantwo kernel: [13492.299587] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 16 16:09:22 magellantwo kernel: [13492.299596] ata1.00: BMDMA stat 0x5
Mar 16 16:09:22 magellantwo kernel: [13492.299603] ata1.00: failed command: READ DMA
Mar 16 16:09:22 magellantwo kernel: [13492.299617] ata1.00: cmd c8/00:08:60:79:bc/00:00:00:00:00/e1 tag 0 dma 4096 in
Mar 16 16:09:22 magellantwo kernel: [13492.299621]          res 51/40:08:60:79:bc/00:00:00:00:00/e1 Emask 0x9 (media error)
Mar 16 16:09:22 magellantwo kernel: [13492.299628] ata1.00: status: { DRDY ERR }
Mar 16 16:09:22 magellantwo kernel: [13492.299633] ata1.00: error: { UNC }
Mar 16 16:09:22 magellantwo kernel: [13492.308609] ata1.00: configured for UDMA/100
Mar 16 16:09:22 magellantwo kernel: [13492.308636] sd 0:0:0:0: [sda] Unhandled sense code
Mar 16 16:09:22 magellantwo kernel: [13492.308642] sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 16 16:09:22 magellantwo kernel: [13492.308650] sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
Mar 16 16:09:22 magellantwo kernel: [13492.308660] Descriptor sense data with sense descriptors (in hex):
Mar 16 16:09:22 magellantwo kernel: [13492.308665]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Mar 16 16:09:22 magellantwo kernel: [13492.308686]         01 bc 79 60 
Mar 16 16:09:22 magellantwo kernel: [13492.308695] sd 0:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
Mar 16 16:09:22 magellantwo kernel: [13492.308708] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 01 bc 79 60 00 00 08 00
Mar 16 16:09:22 magellantwo kernel: [13492.308727] end_request: I/O error, dev sda, sector 29129056
Mar 16 16:09:22 magellantwo kernel: [13492.308777] ata1: EH complete

Your disk looks sick I'm afraid. All those I/O errors and "media errors" and "Unrecovered read error" etc. I strongly suggest you make a backup of your data :-)

Its probably because Libreoffice is larger than most things that its the one which is getting hit by a SIGBUS when the attempt to access parts of libsfx2 fail due to the underlying media errors. Nothing I can do about that :-)

You could google for smart/smartd hard disk monitoring to see if those tools can tell you anything about what's going on with that disk

Thanks, I've reinstalled LibreOffice, and now it seems to run fine. I've also downloaded a couple of hard drive monitoring tools, to see what's wrong with my harddisk. My hard drive is 5 years old and seen 20-30 formats from Windows to Ubuntu, Fedora etc. I've made plenty of mistakes when formatting and partitioning in the past.

Sorry to bother you and thanks for the help.