Bug 30102 - Jitsi cannot be launched
Summary: Jitsi cannot be launched
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-28 09:41 CET by Michel AUTEM
Modified: 2022-03-01 11:05 CET (History)
1 user (show)

See Also:
Source RPM: Jitsi V2.10.5550 R10.mga8
CVE:
Status comment:


Attachments

Description Michel AUTEM 2022-02-28 09:41:35 CET
Description of problem:
Jitsi can be installed without any problem but it cannot be launched.

In a terminal you get the error message :

[michel@localhost ~]$ jitsi
/usr/bin/jitsi: ligne 52: /usr/lib/jvm/jre-1.8.0/bin/java: Aucun fichier ou dossier de ce type

I put this bug as "critical" in the meaning that Jitsi is *really critical* for a professional use of the system.

Version-Release number of selected component (if applicable): V2.10.5550 R10.mga8


How reproductible:
Install Jitsi and try to launch it.


Steps to Reproduce:
1.
2.
3.
Comment 1 sturmvogel 2022-02-28 11:05:49 CET
How in first place did you install Jitsi? Jitsi pulls in java-1.8.0-openjdk and java-1.8.0-openjdk-headless as dependency. 
Your /usr/lib/jvm/ path is missing links to the java librarys (when i translate your error message right). 

So it should look on a healthy system where only java-1.8.0-openjdk (and not 11) is installed:
file:///usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-2.1.mga8.x86_64
file:///usr/lib/jvm/jre
file:///usr/lib/jvm/jre-1.8.0
file:///usr/lib/jvm/jre-1.8.0-openjdk
file:///usr/lib/jvm/jre-1.8.0-openjdk-1.8.0.312.b07-2.1.mga8.x86_64
file:///usr/lib/jvm/jre-openjdk

How does yours look?

Did a fresh minimal Plasma 64bit VB instllation. Installed Jitsi and its deps. Jitsi starts right away.
Comment 2 Michel AUTEM 2022-02-28 19:27:06 CET
Thanks for your answer.

[michel@localhost ~]$ cd /usr/lib/jvm
[michel@localhost jvm]$ ls
java-1.8.0-openjdk-1.8.0.282.b04-0.0.ea.4.mga8.x86_64/
jre@
jre-1.8.0@
jre-1.8.0-openjdk@
jre-1.8.0-openjdk-1.8.0.282.b04-0.0.ea.4.mga8.x86_64@
jre-openjdk@

My problem is "just" that the path /usr/lib/jvm/jre-1.8.0 is a link
that leads to /etc/alternatives/jre-1.8.0,
which is a link that leads to /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.272-1.b10.1.mga7.x86_64/jre
which ... doesn't exist on my system, as I run java-1.8.0-openjdk-1.8.0.282.b04-0.0.ea.4.mga8.x86_64/
...

I did *never* installed anything on my system outside the default installations, in such a way that if something goes wrong in the configuration, the only explanation is a bug in the distribution or some package installation.
Comment 3 sturmvogel 2022-02-28 19:33:34 CET
It's correct that the directorys link to each other. But that /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.272-1.b10.1.mga7.x86_64/jre is missing is wrong. Reinstall java-1.8.0-openjdk and java-1.8.0-openjdk-headless
Comment 4 sturmvogel 2022-02-28 19:38:29 CET
And it also seems like that your machine isn't properly updated at all. You have Mageia 7 packages/directorys (java-1.8.0-openjdk-1.8.0.272-1.b10.1.mga7.x86_64) and outdated Mageia 8 packages (java-1.8.0-openjdk-1.8.0.282.b04-0.0.ea.4.mga8.x86_64).

Actual is java-1.8.0-openjdk-1.8.0.312.b07-2.1.mga8.x86_64.rpm

So your system is heavily borked.
Comment 5 Michel AUTEM 2022-02-28 19:42:05 CET
I already made this manip three times before creating this ticket.
The last one, I completely uninstalled ALL Java material.
Thanks.
Comment 6 Michel AUTEM 2022-02-28 19:55:47 CET
1) I first used dnfdragora to reinstall java, but dnfdragora doesn't show clearly the version you download and I surely installed 1.8.0.272 in place of 1.8.0.312

2) I used then rpmdrake, but it prevented me to instal 1.8.0.312 because of a dependancy not satisfied.
And very curiously two minutes ago it has suddenly worked ... Some people ask me why Mageia is called like this.

But the Jitsi problem is still the same
Comment 7 sturmvogel 2022-02-28 20:07:54 CET
(In reply to Michel AUTEM from comment #6)
>I surely installed 1.8.0.272 in place of 1.8.0.312

Is your DNF properly setup (mirrors)? What does "dnf --refresh upgrade" do?

> 2) I used then rpmdrake, but it prevented me to instal 1.8.0.312 because of
> a dependancy not satisfied.

What is the missing dependency? Please name the package and version.
Comment 8 Michel AUTEM 2022-02-28 20:38:35 CET
The DNF question is not about its mirrors but the fact it does not display the detailed version numbers of the packages, because the corresponding columns are completely pushed right outside your screen, so far that I can even no more bring them back in the vision field ...

Sorry for the missing dependency, I did not write its name and now the message is not displayed again .. It was "java-1.8.0-openjdk-headless something".
Comment 9 sturmvogel 2022-02-28 20:55:37 CET
Strange. I have a scrollbar in dnfdragoa so i can scroll to the right and see the version number. You can also set dnfdragora to only show the actual package (latest version) so that you can't install outdated versions (Options->user settings).

Is java-1.8.0-openjdk-headless according the infos shown in dnfdragora installed or not?
Comment 10 Michel AUTEM 2022-02-28 21:33:27 CET
OK for DNFDragora. I just didn't see the scrollbar, or sometimes it's not properly displayed, in such a way I could not drag back the things in the limits of my screen ...

The java-openjdk-headless version installed in my system is now exactly the same that the java-openjdk : 1.8.0.312.bo7 2.1.mga8
Comment 11 Lewis Smith 2022-02-28 22:09:49 CET
[collision, so this comment may be redundant]
All these files come from:
 /usr/lib/jvm/jre-1.8.0 ex java-1.8.0-openjdk-headless:

Tree [worked out from the package]:
/usr/lib/jvm/
 java-1.8.0-openjdk-1.8.0.282.b04-0.0.ea.4.mga8.x86_64
 java-1.8.0-openjdk-1.8.0.292.b10-1.1.mga8.x86_64
 java-1.8.0-openjdk-1.8.0.312.b07-2.1.mga8.x86_64/     tree just this one
  jre/
   bin/*
   lib/*

> '/usr/lib/jvm/jre-1.8.0/bin/java'     is the 'missing' path
> _
> path /usr/lib/jvm/jre-1.8.0 is a link
> that leads to /etc/alternatives/jre-1.8.0,
> which is a link that leads to
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.[version]/jre
here incorrectly (comment 2):
 /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.272-1.b10.1.mga7.x86_64/jre
where it should be:
 java-1.8.0-openjdk-1.8.0.312.b07-2.1.mga8.x86_64/jre

So the linking looks sensible, generic '/usr/lib/jvm/jre-1.8.0' -> specific
'java-1.8.0-openjdk-1.8.0.312.b07-2.1.mga8.x86_64/jre'

which does include the file missing .../bin/java

@Michel: can you say what is in /etc/alternatives/jre-1.8.0 ?

This is another case of mixing DNF & rpmdrake. That apart, there were clearly mixed & obsolete versions. I do not see why that should not be fixed by removing both Java packages, checking (I guess) that /usr/lib/jvm/ is empty, and re-installing them ensuring that the version is the latest. You say you just done this, comment 5, comment 6.

> But the Jitsi problem is still the same
Check that the linking chain you identified is correct. Especially '/etc/alternatives/jre-1.8.0'. If it is, the error should not happen because it would not be true.

CC: (none) => lewyssmith

Comment 12 Michel AUTEM 2022-02-28 22:41:24 CET
In my system /etc/alternatives/jre-1.8.0 is currently a link to /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.272-1.b10.1.mga7.x86_64/jre which doesn't exist anymore.

When I change manually the link value to the correct value (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-2.1.mga8.x86_64/jre) everything (Jitsi) seems working fine again.
Comment 13 Michel AUTEM 2022-02-28 22:47:06 CET
That's not the first time I get problems with DNFDragora.
A couple of months ago, it asked me to do a big update of my system which I launched without looking at it in details. And when it finished my system was become a mess, mixing Mageia V8 and Cauldron, with a lot of things not working anymore. I had to completely reinstall this machine.
Comment 14 Lewis Smith 2022-03-01 11:05:17 CET
(In reply to Michel AUTEM from comment #12)
> In my system /etc/alternatives/jre-1.8.0 is currently a link to
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.272-1.b10.1.mga7.x86_64/jre which
> doesn't exist anymore.
> When I change manually the link value to the correct value
> (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-2.1.mga8.x86_64/jre)
> everything (Jitsi) seems working fine again.
Thank you for doing this. I realised after my last post that the problem probably came down simply to this wrong link, easily corrected as you did.
How it got wrong we cannot know.

(In reply to sturmvogel from comment #1)
> Did a fresh minimal Plasma 64bit VB instllation. Installed Jitsi and its
> deps. Jitsi starts right away.
That was noble; it shows that things work OK 'out of the box'.

"everything (Jitsi) seems working fine again"
I think we can close this; but it can be re-opened if necessary.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.