Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#28729 - [paraview] Fails to start

Attached to Project: Community Packages
Opened by Marc A. Kastner (mkasu) - Thursday, 01 March 2012, 14:57 GMT
Last edited by Thomas Dziedzic (tomd123) - Friday, 02 March 2012, 23:29 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Thomas Dziedzic (tomd123)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Since yesterday I am unable to start paraview, not sure if it's according to some system upgrade (last protobuf update should be older).

[marc@markaspc pkg]$ paraview
AutoMPI: SUCCESS: command is:
"/usr/bin/mpiexec" "-np" "4" "/usr/lib/paraview-3.14/pvserver" "--server-port=46048"
AutoMPI: starting process server
-------------- server output --------------
libprotobuf FATAL google/protobuf/stubs/common.cc:72] This program was compiled against version 2.3.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (2.4.1). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "/build/src/build/ParaViewCore/ServerImplementation/vtkPVMessage.pb.cc".)
terminate called after throwing an instance of 'google::protobuf::FatalException'
what(): This program was compiled against version 2.3.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (2.4.1). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "/build/src/build/ParaViewCore/ServerImplementation/vtkPVMessage.pb.cc".)
libprotobuf FATAL google/protobuf/stubs/common.cc:72] This program was compiled against version 2.3.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (2.4.1). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "/build/src/build/ParaViewCore/ServerImplementation/vtkPVMessage.pb.cc".)
terminate called after throwing an instance of 'google::protobuf::FatalException'
what(): This program was compiled against version 2.3.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (2.4.1). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "/build/src/build/ParaViewCore/ServerImplementation/vtkPVMessage.pb.cc".)
--------------------------------------------------------------------------
mpiexec noticed that process rank 2 with PID 4408 on node markaspc exited on signal 6 (Aborted).
--------------------------------------------------------------------------
AutoMPI: server never started.
vtkProcessModuleAutoMPIInternals: Server never started.
ERROR: In /build/src/ParaView-3.14.0-Source/VTK/Common/vtkSocket.cxx, line 481
vtkClientSocket (0x2470800): Socket error in call to connect. Connection refused.


ERROR: In /build/src/ParaView-3.14.0-Source/VTK/Common/vtkClientSocket.cxx, line 53
vtkClientSocket (0x2470800): Failed to connect to server localhost:46048
This task depends upon

Closed by  Thomas Dziedzic (tomd123)
Friday, 02 March 2012, 23:29 GMT
Reason for closing:  Upstream
Additional comments about closing:  http://paraview.org/Bug/view.php?id=1285 2
Comment by Thomas Dziedzic (tomd123) - Thursday, 01 March 2012, 15:14 GMT
What's the output of pacman -Q paraview
Comment by Marc A. Kastner (mkasu) - Thursday, 01 March 2012, 15:15 GMT
paraview 3.14.0-2
Comment by Thomas Dziedzic (tomd123) - Thursday, 01 March 2012, 16:17 GMT
this works for me but I don't have any special configuration set up
Comment by Thomas Dziedzic (tomd123) - Thursday, 01 March 2012, 16:23 GMT
This must have something to do with: http://paraview.org/Bug/view.php?id=12852
Comment by Marc A. Kastner (mkasu) - Friday, 02 March 2012, 21:21 GMT
Ah, I fixed the issue for me. The error appears when I am enabling multicore use in the program options. When it's disabled, paraview starts normally.
Might be a paraview issue rather than arch package. I think you can close the bug report.

Loading...