]]>
Lone_Wolf - thanks and I will look more at trying to get a trace later when I have a little more time to investigate further.
I have now submitted a bug report for LO at https://www.libreoffice.org/bugzilla/sh … i?id=77400
Please will others seeing this bug add to the upstream reports I have referenced with additional diagnostics.
]]>Look at /usr/share/applications/libreoffice-writer.desktop (it is a symlink to /usr/lib/libreoffice/share/xdg/writer.desktop ) and you'll see the %U is on the exec= line .
if you want to know more about what %U and other options do, check http://standards.freedesktop.org/deskto … atest.html .
I can think of 2 possibilities to add strace :
- run libreoffice-writer.desktop --strace
This should mimic kde menu behaviour and start writer with strace.
- Edit /usr/lib/libreoffice/share/xdg/writer.desktop and temporarily change the exec= line :
Exec=libreoffice --writer --strace %U
Then start writer from KDE menu.
]]>libreoffice --writer --strace
but it does not freeze that way. Only by starting writer from the kde menu which uses the command
libreoffice --writer %U
does it freeze! Why the outcome as to freezing or not should be different starting with these two methods I don't understand as surely they are equivalent? However I could not get it to start from the command line if I added in the %U which again has puzzled me.
Does anyone know how to get a trace from starting libreoffice from the kde menu?
]]>Hopefully this will be fixed before long!
]]>I use also libreoffice-kde4-4.2.3-1 ( integration with kde 4 )
and I notice random freeze at startup when I launch libreoffice ( swriter, calc, draw, impress, math ), the GUI of libreoffice freezes immediatly,
it may related to the libreoffice-kde4 package, because If I uninstall libreoffice-kde4 the bug seems gone,
I use a patched kernel 3.14, Linus Torvald's patch for this bug :
https://bugs.archlinux.org/task/39806
so I'm sure that this bug is not related to the bug 39806
the workaround is to uninstall libreoffice-kde4 package, but I don't know if it's an upstream bug or a problem with archlinux
]]>