Mailinglist Archive: opensuse-support (116 mails)

< Previous Next >
Re: [opensuse-support] Libreoffice not start in a newly installed openSUSE Tumbleweed with old user directory
On 24/12/2018 13.25, H Zeng wrote:
On Friday, 21 December 2018 10:02:10 HKT Carlos E. R. wrote:
On 21/12/2018 02.11, H Zeng wrote:

I reinstalled my openSUSE Tumbleweed w/ KDE Plasma because my root
partition failed. After the reinstallation, Libreoffice does not start.
If trying to start it from command line, complaints are like these,
cnzhx@ostp:/home/cnzhx> libreoffice --safe-mode
javaldx: Could not find a Java Runtime Environment!
Warning: failed to read path from javaldx
terminate called after throwing an instance of

And... is java installed?

Anyway, what you did is called "thread hijacking".

You hit reply on a message to this list dated 2018-12-09, Re: "Leap 15
Packman VLC - no drag'n'drop?", changed the subject and erased the
contents, to post your question. But to many of us it appears hidden as
a reply to that VLC question.

You can see your post here, in the archive - last post of the thread:


Next time, please do not use "reply" to start a new thread, it is confusing.

Thank you, Carlos for the heads up and sorry to everyone in this list for my

I have no idea why the last message became a "reply" to an old thread. I
definitely used the "New Message" button in Kmail to start the writing. And I
have been very confused by the fact that I cannot find the message I sent in
my Inbox. I recall that every new message comes up in my own Inbox right
I send it. Anyway, I will try to do better on the mailing list thereafter.

And I do not know you have replied because I have not seen your reply until I
use find in my mailbox. I saw a reply coming from Bruno just now. But after a
while when I ready to read it, I cannot see it. So I search for it. At that
moment, I realised that I have hijacked a thread.

Then, should I start a new thread from now on on this topic? I asked because
received two replies on this topic in this thread.

Well, it would help in finding the post ;-)

Anyway, it seems that java is not the cause of the error. Check the list
of packages (and versions) against that of Bruno. Another resource is
to use strace to try find what the program is doing when it crashes,
there is not enough information.

Just a check. You are using "zypper dup" for the TW updates, not zypper
up or yast?

Cheers / Saludos,

Carlos E. R.
(from 42.3 x86_64 "Malachite" at Telcontar)

< Previous Next >