LOwriter freezes in specific account

Asked by Aart Keijzer on 2014-01-08

Hi,

I work with Ubuntu 12.04LTS and LibreOffice installed from the Software Center. All software up to date.

Libre Office is showing in my account (normal user account) problems opening files and working in them since a few days. When opening some .odt files LOwriter freezes and it takes about 5 minutes to come alive again. The rest of the desktop continues to function.

If I take the same file and go to the administrator acccount the file opens without any problem and fast. Same result in another 12.04 machine. File opens without problem.

Deleting Libre Office profile file in my own account does not improve or change the problem.
Tried reinstallation of LO, installation 4.1. No result. Same problem. Re-installed 3 via software center.

So I have the same software and the same file on the same system.
In one account the file opens without any problems and logged in in another account the file opens and LO freezes.

Anybody knows what the problem is?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2014-01-12
Last reply:
2014-01-28

Try renaming the libreoffice config folder, then re-opening

Aart Keijzer (aart-keijzer) said : #2

I imagine that you are talking about the .config/libreoffice folder.

I have done that already. It does not change anything.

Try launching it from the terminal. The output may be useful.

Aart Keijzer (aart-keijzer) said : #4

how do I open a LO document from the terminal?

On 2014-01-08 15:36, actionparsnip wrote:
> Your question #241892 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/241892
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> Try launching it from the terminal. The output may be useful.
>

libreoffice --writer

Will run Writer

Aart Keijzer (aart-keijzer) said : #6

Thanks for your answer.

In the meanwhile I have been working on the problem as it avoided me to
use my computer (a part of my LO files).

When I copied the same file to another account within the same computer
(tested two accounts), the file opened easily (and also other LO files
that gave problems). Than I shared the original file in my account that
gave the problem. I opened the shared file without problem.
So the same LO file that freezes in my account, opens without problem in
another account.
I have concluded that it is related to my account (ubuntu account).
Where I can not tell.

So I have created a new account and copied all my files to this account.
Changed ownership and group with chown. Everything is working again.
Also the LO files that gave problems are running fine.

So far, so good. But it does not diagnose the problem.

The old account still exists as it was and I can do some tests with it
What I would like to know is how I open a specific LO file with writer
from the terminal to share the messages with you on the forum.
(Is this useful?)

On 01/08/2014 07:11 PM, actionparsnip wrote:
> Your question #241892 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/241892
>
> Status: Open => Answered
>
> actionparsnip proposed the following answer:
> libreoffice --writer
>
> Will run Writer
>

Aart Keijzer (aart-keijzer) said : #7

I have launched LO writer in the terminal in the account with a problem
and opened one of the LO files that freezes LO.

below the result:

aart@Haarlem:~$ libreoffice -writer
Warning: failed to read path from javaldx
Warning: -writer is deprecated. Use --writer instead.
aart@Haarlem:~$ libreoffice --writer
Warning: failed to read path from javaldx

(soffice:27962): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed

(soffice:27962): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed

(soffice:27962): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed

(soffice:27962): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(soffice:27962): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed

(soffice:27962): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(soffice:27962): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed

(soffice:27962): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed

(soffice:27962): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed

(soffice:27962): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(soffice:27962): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed

(soffice:27962): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

Afterwards I logged in into my new account and opened LO in the terminal
also.
Below the result of this action:

europar@Haarlem:~$ libreoffice --writer
javaldx: Could not find a Java Runtime Environment!
Please ensure that a JVM and the package libreoffice-java-common
is installed.
If it is already installed then try removing
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
Warning: failed to read path from javaldx

Regards,
Aart

On 01/08/2014 07:11 PM, actionparsnip wrote:
> Your question #241892 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/241892
>
> Status: Open => Answered
>
> actionparsnip proposed the following answer:
> libreoffice --writer
>
> Will run Writer
>

Aart Keijzer (aart-keijzer) said : #8

europar@Haarlem:~$ libreoffice --writer
javaldx: Could not find a Java Runtime Environment!
Please ensure that a JVM and the package libreoffice-java-common
is installed.
If it is already installed then try removing
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
Warning: failed to read path from javaldx

the Java issue has been solved by installing Open JDK Java 7 Runtime

The initial problem still exists (did the tests in the different accounts again).
The same behaviour.

Launchpad Janitor (janitor) said : #9

This question was expired because it remained in the 'Open' state without activity for the last 15 days.