Created attachment 12356 [details]
log

Thank you Holger for the report.

A quick note before trying this on M7 to say that:
 jitsi-2.10.5550-10.mga8.x86_64.rpm   with
 java-1.8.0-openjdk-1.8.0.282.b04-0.0.ea.4.mga8.x86_64.rpm
does work on Mageia 8.

CC: (none) => lewyssmith

Created attachment 12357 [details]
Console O/P of jitsi *not* crashing on Mageia 7

Trying this on M7: jitsi-2.10.5550-6.mga7, it works. The console output is attached for comparison with the reporter's.

Created attachment 12358 [details]
Screenshot of running jitsi

Just to show jitsi running.

@ Holger
You gave this URL presumably as where you got jitsi from:
 https://rpmfind.net/linux/RPM/mageia/7/x86_64/media/core/release/jitsi-2.10.5550-6.mga7.x86_64.html
which I do not see in our Mirrors list. How did you actually install it?
You cannot be the first person to use it on Mageia 7, which is mature.

To see whether the package repo is at fault, can you please UNinstall it (urpme), then re-install it using Add/Remove software (rpmdrake) or as root (or sudo) urpmi jitsi which should use a regular mirror.

Shall leave comparison of the two console outputs until this is done.

Ever confirmed: 1 => 0
Status: NEW => UNCONFIRMED
Severity: enhancement => normal
CC: lewyssmith => (none)
Assignee: bugsquad => lewyssmith
Source RPM: https://rpmfind.net/linux/RPM/mageia/7/x86_64/media/core/release/jitsi-2.10.5550-6.mga7.x86_64.html => jitsi-2.10.5550-6.mga7.src.rpm

(In reply to Lewis Smith from comment #5)
> @ Holger
> You gave this URL presumably as where you got jitsi from:
>  https://rpmfind.net/linux/RPM/mageia/7/x86_64/media/core/release/jitsi-2.10.
> 5550-6.mga7.x86_64.html
> which I do not see in our Mirrors list. How did you actually install it?
> You cannot be the first person to use it on Mageia 7, which is mature.
> 
> To see whether the package repo is at fault, can you please UNinstall it
> (urpme), then re-install it using Add/Remove software (rpmdrake) or as root
> (or sudo) urpmi jitsi which should use a regular mirror.
> 
> Shall leave comparison of the two console outputs until this is done.

--> OK, i got it  from the repos. I have reinstalled it, but nothing has changed.
Started from the menu and then in terminal: It gave : 

» jitsi                                                                                          
Jitsi is already running and will handle your parameters (if any).
Launch with the --multiple param to override this behaviour.

Now, is working. Will monitor the situation.

(In reply to Holger  Mainz from comment #6)
> (In reply to Lewis Smith from comment #5)
> --> OK, i got it  from the repos. I have reinstalled it, but nothing has
> changed.
I think it *has* changed - for the better. Your original report ended:
 5351 abort (core dumped)  jitsi
which is drastic. You got much further this time:

> Started from the menu and then in terminal: It gave : 
> » jitsi                                                                     
> Jitsi is already running and will handle your parameters (if any).
> Launch with the --multiple param to override this behaviour.
Looks correct. If you start the program from the menu, and then start it again from a terminal - when it implies that one instance is enough - this complaint is quite rational. Why did you try starting it a second time?

Unless I misunderstood, and you wanted to say:
- Started it from the menu
- Ended it
- Tried re-starting it from a terminal -> error in comment 6
This *would* be a fault.
-------------------------------------------------------------
(In reply to Holger  Mainz from comment #7)
> Now, is working. Will monitor the situation.
Thank you. Please report back. If we do not hear anything from you within say 7d, we can close the bug.

(In reply to Lewis Smith from comment #8)
> (In reply to Holger  Mainz from comment #6)
> > (In reply to Lewis Smith from comment #5)
> > --> OK, i got it  from the repos. I have reinstalled it, but nothing has
> > changed.
> I think it *has* changed - for the better. Your original report ended:
>  5351 abort (core dumped)  jitsi
> which is drastic. You got much further this time:
> 
> > Started from the menu and then in terminal: It gave : 
> > » jitsi                                                                     
> > Jitsi is already running and will handle your parameters (if any).
> > Launch with the --multiple param to override this behaviour.
> Looks correct. If you start the program from the menu, and then start it
> again from a terminal - when it implies that one instance is enough - this
> complaint is quite rational. Why did you try starting it a second time?
> 
> Unless I misunderstood, and you wanted to say:
> - Started it from the menu
> - Ended it
> - Tried re-starting it from a terminal -> error in comment 6
> This *would* be a fault.
> -------------------------------------------------------------
> (In reply to Holger  Mainz from comment #7)
> > Now, is working. Will monitor the situation.
> Thank you. Please report back. If we do not hear anything from you within
> say 7d, we can close the bug.

--> Sorry for reporting late. I was  ill some days. I have restarted from terminal, because after the menu launch, the jitsi start screen vanishes within the process. Reinstalling did not solve.

Jitsi is not something I can try easily beyond just launching it.

> I have restarted from terminal, because after the menu launch,
> the jitsi start screen vanishes within the process.
Are you saying that if you launch it from the menu, it does start but 'disappears'? If so, after how long? I need to try it again under M7.
If you launch it initially from a terminal (without trying the menu first), does it:
- disappear like from the menu?
- stay running correctly?
If launched from menu, then disappearing, how does it behave if you re-launch it from the menu:
- disappear again?
- stay running?
We need to ascertain simply whether it behaves differently when launched from menu or terminal; or differently between its initial launch and re-launching it. Maybe carefully thought screenshots (to attach to the bug) might help.

Keywords: (none) => NEEDINFO

Back in Mageia 7, I cannot find any problem with jitsi.
Starting it from the menu, or terminal, it commences with a long start-up window with a progress bar, which gives way to the main application window:
 https://bugs.mageia.org/attachment.cgi?id=12358
In neither case does this terminate: I played with different menu options to keep it going a bit.
In short, answering my own questions above, Jitsi behaves identically and correctly from menu and command line. I could not push it further without any relevant account, contacts etc.

You need to provide a more precise description + some evidence to support your complaint. This does not suffice:
> I have restarted from terminal, because after the menu launch,
> the jitsi start screen vanishes within the process
If it would help to express yourself in German, we can probably find someone to translate it.
Without convincing evidence, we shall close the bug.

(In reply to Lewis Smith from comment #10)
> Jitsi is not something I can try easily beyond just launching it.

PART 1:

> If launched from menu, then disappearing, how does it behave if you
> re-launch it from the menu:
> - disappear again?
> - stay running?
> We need to ascertain simply whether it behaves differently when launched
> from menu or terminal; or differently between its initial launch and
> re-launching it. Maybe carefully thought screenshots (to attach to the bug)
> might help.

When i launch by menu, at the 1st attempt, it just disappears. 
At the second try, the starting screen stays like shown in the picture attached. But it is not frozen. The blue jitse aurora is still wobbling around the symbol

(In reply to Lewis Smith from comment #10)
> Jitsi is not something I can try easily beyond just launching it.
> 
> > I have restarted from terminal, because after the menu launch,
> > the jitsi start screen vanishes within the process.
> Are you saying that if you launch it from the menu, it does start but
> 'disappears'? If so, after how long? I need to try it again under M7.
> If you launch it initially from a terminal (without trying the menu first),
> does it:
> - disappear like from the menu?
> - stay running correctly?

PART 2 : I re logged in. 

From terminal, it started right away. But it does not always so.

Created attachment 12449 [details]
screenshot

(In reply to Holger  Mainz from comment #12)
> When i launch by menu, at the 1st attempt, it just disappears.
Presumably like the initial attached log (core dump).

> At the second try, the starting screen stays like shown in the picture
> attached. But it is not frozen. The blue jitse aurora is still wobbling
> around the symbol
This screenshot looks normal, with a progress bar 'in progress'. You do not say whether it gets stuck here, or goes on to start the main application window.

So we have: when you start it (first time in a session) from the *menu*, it crashes; but not the second time.

> re-logged in. 
> From terminal, it started right away. But it does not always so.
Assigning initially to the Java group (re the attached log); CC'ing neoclust who recently did a java bugfix on jitsi (M8).

Status: UNCONFIRMED => NEW
Assignee: lewyssmith => java
Keywords: NEEDINFO => (none)
Ever confirmed: 0 => 1
CC: (none) => lewyssmith, mageia

(In reply to Holger  Mainz from comment #0)
> Description of problem: Jitsi terminates
> 
> 
> Version-Release number of selected component (if applicable):
> 
> 2.10.5550-6.mga7
> 
> How reproducible:
> 
> Every time I attempt to start
> 
> Steps to Reproduce:
> 1. Terminates directly
> 2. Starting pic freezes

is java 1.8.0 installed ?

don't mind i haven't read all. :-)

(In reply to Nicolas Lécureuil from comment #16)
> (In reply to Holger  Mainz from comment #0)
> > Description of problem: Jitsi terminates
> > 
> > 
> > Version-Release number of selected component (if applicable):
> > 
> > 2.10.5550-6.mga7
> > 
> > How reproducible:
> > 
> > Every time I attempt to start
> > 
> > Steps to Reproduce:
> > 1. Terminates directly
> > 2. Starting pic freezes
> 
> is java 1.8.0 installed ?

Yes, is installed.

Seems, the problem was solved by the upgrade. Thanks to all supporters.

(In reply to Holger  Mainz from comment #19)
> Seems, the problem was solved by the upgrade.

You mean after upgrade to Mageia 8 ?

And still probably broken on mga7 ?
(which this bug is set to)

CC: (none) => fri

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

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