Bug 25446

Summary: Paraview crashes at startup
Product: Mageia Reporter: Cyril Levet <cyril.levet0780>
Component: RPM PackagesAssignee: Joseph Wang <joequant>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: Normal Keywords: NEEDINFO
Version: 7   
Target Milestone: Mageia 8   
Hardware: x86_64   
OS: Linux   
URL: https://www.paraview.org/download/
Whiteboard:
Source RPM: paraview-5.6.0-4.mga7.src.rpm CVE:
Status comment:
Attachments: Crash report

Description Cyril Levet 2019-09-15 20:37:39 CEST
Description of problem: Trying to start Paraview under a newly installed Mageia 7 with GNOME wayland induces a MPI fatal error and paraview does not launch. I made te test in VirtualBox not on a physical computer.


Version-Release number of selected component (if applicable): Paraview 5.6.0


How reproducible: Always


Steps to Reproduce:
1. Install Mageia 7 GNOME from the official iso in VirtualBox
2. Install paraview
3. Launch paraview. It crashes
Comment 1 Cyril Levet 2019-09-15 20:38:14 CEST
Created attachment 11283 [details]
Crash report
Comment 2 Lewis Smith 2019-09-15 22:19:20 CEST
See also bug 25444.
Installed to try paraview-5.6.0-4.mga7.x86_64.rpm (it is huge).
Lots of /bin/* including paraview itself.
"Summary     : Parallel visualization application
Description : ParaView is an open-source, multi-platform data analysis and
visualization application."
No man page; it is in the Science sub-menu (Paraview Viewer).

Under MATE desktop, the menu icon does nothing; consistent with:
 $ paraview
[localhost.localdomain:30413] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file ess_singleton_module.c at line 388
[localhost.localdomain:30413] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file ess_singleton_module.c at line 166
--------------------------------------------------------------------------
Sorry!  You were supposed to get help about:
    orte_init:startup:internal-failure
But I couldn't open the help file:
    /usr/share/openmpi/help-orte-runtime: No such file or directory.  Sorry!
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Sorry!  You were supposed to get help about:
    mpi_init:startup:internal-failure
But I couldn't open the help file:
    /usr/share/openmpi/help-mpi-runtime.txt: No such file or directory.  Sorry!
--------------------------------------------------------------------------
*** An error occurred in MPI_Init
*** on a NULL communicator
*** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
***    and potentially your MPI job)
[localhost.localdomain:30413] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed!

which is like Cyril's attachment. So this does *not* seem to be Gnome|Wayland related.
Assigning to Joe as the 'paraview' maintainer.

Assignee: bugsquad => joequant
Summary: Paraview crashes at startup in GNOME Wayland => Paraview crashes at startup

Comment 3 Cyril Levet 2020-08-15 19:05:11 CEST
Still valid on Mageia 8 Beta 1.
Comment 4 Aurelien Oudelet 2020-09-04 23:06:11 CEST
Upstream version available is 5.8 (August, 4th 2020)

@Cyril
Have you ever tried running upstream binaries as they are provided?

URL: (none) => https://www.paraview.org/download/
Target Milestone: --- => Mageia 8
Keywords: (none) => NEEDINFO

Comment 5 Cyril Levet 2020-09-05 11:14:41 CEST
(In reply to Aurelien Oudelet from comment #4)
> Upstream version available is 5.8 (August, 4th 2020)
> 
> @Cyril
> Have you ever tried running upstream binaries as they are provided?

I never tried to run upstream binary. But I had compiled 5.4 and 5.6 on Mageia and it compiles and works well.
Comment 6 Cyril Levet 2020-10-02 20:47:45 CEST
Now it works it Cauldron and Mageia 7. So bug fixed.

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