Hello, I have written the original paraview 2.4 ebuild in collaboration with Markus D. When Paraview 2.6.x came out, Markus and Sebastien took over. So now, I am just a simple user... ;) When I was running Paraview 2.4.4, I had xorg 7.1 on my x86 box. Now I have xorg 7.2 and Paraview 2.6.1 and I have an OpenGL issue that blocks any use of Paraview (the demo crashes on me) So I don't really know if it is a Paraview or an Xorg issue. I report it under Paraview. Reproducible: Always Steps to Reproduce: 1. Start Paraview from a console 2. Get the following message: "libGL warning: 3D driver claims to not support visual 0x4b" 3. Start the demo and see Paraview crash.. Actual Results: A crash... Expected Results: A nice demo... - I have an ATI video card. I do not use the ATI drivers though, I use the xorg driver - At work I have an nvidia card with the nvidia driver and guess what, It does not crash...
Hi Daniel, From what you report it is difficult to say what the culprit is. Since it works with the nvidia card/driver it is likely an issue with the Xorg ati driver/opengl rather than a paraview problem. The libGL warning you report in 2. is a known issue (which the xorg folks will hopefully fix sometime) and should not be the cause for your problems. That said, do you experience problems with other OpenGl apps using the Xorg+ati? Can you provide a backtrace so we can pin down which call causes the crash? Thanks, Markus
How do I generate a backtrace? Daniel
Hi Daniel, The idea is to get a little more information as to what causes paraview to crash since you don't seem to get any sort of output on the command line I assume. You could do to things 1) run paraview using strace, e.g., via strace -o paraview.trace paraview and have a look at that calls made before the crash. 2) Compile paraview with debugging information by turning the -ggdb flag on and run paraview inside gdb. After the crash you can issue "bt" (backtrace) inside gdb to look at the last calls made. This may give us a hint as to what the problem may be. Best, Markus
I promise Markus I will try what you recommended... In any case, here is an ebuild for 2.6.2 I have been using the existing one for 2.6.1 with the following changes: - I tried to reinteger ffmpeg (Did not compile) - I remodified the dependency on mpi (from virtual/mpi back to sci-clusters/mpich). I did that because I read that paraview uses mpich, I am not sure if it works with the other mpi
Created attachment 125731 [details] Ebuild for 2.6.2 I built it on x86 with nvidia video card (it works) I will build it tonight on my amd64 nvidia I will also test it on my x86 ATI box and see if the old crash is still there.
Hi Daniel, Thanks for the ebuild and I'll try to have a look at it soon :) The mpi support in paraview indeed is pretty lame for a supposedly distributed viewing package. You are correct that currently only mpich sort of works; unfortunately, since mpich comes as a static library and paraview links it into an *.so this breaks on amd64. I have a patch somewhere that allows lam-mpi to be used. Overall, I am not too happy with paraview + mpi. Maybe things are better with 3.x or I'll have to have a closer look at mpi support at some point in the future. Best, Markus
I had indeed with 2.6.2 the problem I mentionned with 2.6.1 Using strace (Thanks Markus) I realized that this was due to the interaction of Paraview with a local (and non working... ;) ) installation of OpenFOAM (That also contains references to mpi and paraview). Once I removed this OpenFOAM stuff on my account, everything worked fine... So, problem solved... ;) Daniel
Markus, I have noticed the following while building ParaView 2.6.2: ... -- Check size of short - done -- Check size of uchar -- Check size of uchar - failed -- Performing NetCDF Test HAVE_ST_BLKSIZE -- Performing NetCDF Test HAVE_ST_BLKSIZE - Success -- Performing NetCDF Test HAVE_FTRUNCATE -- Performing NetCDF Test HAVE_FTRUNCATE - Success -- Check if the system is big endian -- Check if the system is big endian - little endian -- Looking for malloc.h -- Looking for malloc.h - found -- Looking for doxygen... -- Looking for doxygen... - found /usr/bin/doxygen -- Looking for dot tool... -- Looking for dot tool... - found /usr/bin/dot -- Looking for glXGetProcAddressARB -- Looking for glXGetProcAddressARB - found .... It seems that ParaView expects NetCDF and Graphviz (/usr/bin/dot) to be there. There are not in the dependency list though. What do you think? Should they be added? Flagged? (Graphviz is a flag, for instance) Two other things: I slotted Paraview-2.6.2 (thinking about Paraview-3). Do you think it could be possible to add a suffix '2' to the binaries produced (the libraries are already put in a ParaView-2.6 directory). How to do that? How can we add ParaView to the KDE/Gnome menus, with a nice icon? Daniel
Hi Daniel, Thanks a lot for your comments! Since your problems are fixed I'll close this bug. I just bumped pararview to 2.6.2 in portage. I changed the dependency for mpi back to mpich since this is the only mpi implementation that seems to work for me (at least on x86). I also added netcdf as a dependency to prevent paraview from building its own implementation. graphviz is only needed by doxygen AFAIKT and is pulled in by the latter anyway so we don't need it. Regarding slotting: Personally, I don't see the need to have paraview slotted. Slotting is only good for libraries or other core packages where users need to have several versions installed simultaneously to have a working system. As soon as paraview 3.x is in the tree I don't see any reason why people need to still have 2.6 around but please let me know if and why you think otherwise. Thanks, Markus
Markus, I am sorry to say that the bug is still there... :( I claimed victory a bit too early. So here is the deal: - As root, everything works fine - As me as a user, the demo crashes: ted@mhordraid ~ $ paraview libGL warning: 3D driver claims to not support visual 0x4b DemoScriptPath: /usr/lib/ParaView-2.6/../../share/paraview-2.6 DemoDataPath: /usr/lib/ParaView-2.6/../../share/paraview-2.6 libGL warning: 3D driver claims to not support visual 0x4b Segmentation fault I thought first that it might be a mesa issue, so I downgraded from 6.5.2 to 6.5.1. No effects This machine is a bit special, it has a radeon video card but I do not use the ati drivers. I use the xorg ones. I send you the results of strace. For me, it's like chinese... :(
Created attachment 126332 [details] Result of strace on Paraview Here, I start paraview and then ask for the demo to be run. It crashes on me then...
Hi Daniel, Since it works as root could you capture the strace there as well and maybe send me the first 60,000 lines by email? Also, just to remind me what box you have could you post your emerge --info as well? Thanks, Markus
emerge --info Portage 2.1.2.9 (default-linux/x86/2007.0/desktop, gcc-4.1.2, glibc-2.5-r4, 2.6.21-gentoo-r4 i686) ================================================================= System uname: 2.6.21-gentoo-r4 i686 Intel(R) Celeron(R) CPU 3.33GHz Gentoo Base System release 1.12.9 Timestamp of tree: Sun, 29 Jul 2007 10:50:01 +0000 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r6 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=prescott -mfpmath=sse -Os -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-march=prescott -mfpmath=sse -Os -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="ftp://trumpetti.atm.tut.fi/gentoo http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X Xaw3d a52 aac aalib acl acpi ada agg alsa amr asf avahi beagle berkdb bitmap-fonts blas boost bzip2 cairo cdparanoia cdr cdrom cli cpudetection cracklib crciprec crypt cups curl dbus directfb divx doc dri dts dvb dvd dvdr dvdread dvi eds emacs emboss encode esd evo examples fam fbcon ffcall ffmpeg firefox flac fortran gcj gdbm gif gmedia gmp gnome gnustep gpm gstreamer gtk gtkhtml hal hdf5 howl hpn iconv imagemagick ipv6 isdnlog ivtv jabber jack java jpeg jpeg2k kerberos lapack lcms ldap libcaca libg++ live lzo mad madwifi midi mikmod mmap mmx mng mono mozbranding mp2 mp3 mp4 mp4live mpeg mudflap mysql nautilus ncurses new-login nls no-seamonkey nptl nptlonly nsplugin objc objc++ ogg openal opengl openmp oss pam pango pcre pdf perl png pnm postgres pppd python qt3 qt3support qt4 quicktime rar readline real realmedia reflection reiserfs sdl session spell spl srt sse sse2 ssl stlport svg svga swig t1lib tcl tcltk tcpd tetex theora threads tiff tk toolkit-scroll-bars truetype truetype-fonts type1-fonts unicode usb vcd vorbis wav wavpack wifi win32codecs wma wmf wmp x264 x86 xanim xft xine xml xorg xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="vesa nv radeon" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Created attachment 126362 [details] Result of strace as 'root' user (No crash) According to your request Markus, here is the strace for Paraview when I am logged in as root. In this case, no libGL message, no crash when I run the demo. Daniel
Daniel, From what I can tell, paraview run by your user uses dri (it loads /usr/lib/dri/r200_dri.so) whereas it doesn't as root. Is the r200 driver the correct one for your card? If not you should add the proper one to your xorg.conf. Markus
This machine indeed has a radeon videocard. I did not want to use the ati-drivers, so I used the xorg ones. From what I can remember, r200 was indeed the one necessary for my card. This problem started to show up (as I wrote in the introduction of this bug report) roughly when I updated to xorg 7.2. However I was not sure it was the origin of the problem. Now the question is : why doesn't root load /usr/lib/dri/r200_dri.so?
More info: 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) (prog-if 00 [VGA]) Subsystem: Connect Components Ltd Unknown device 2801 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18 Memory at d0000000 (32-bit, prefetchable) [size=256M] I/O ports at e800 [size=256] Memory at fbff0000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at fbfc0000 [disabled] [size=128K] Capabilities: [58] AGP version 3.0 Capabilities: [50] Power Management version 2 xorg.conf: Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" Option "AIGLX" "true" EndSection Section "Files" EndSection Section "Module" Load "freetype" # Load "xtt" Load "extmod" Load "glx" Load "dri" Load "dbe" Load "record" Load "xtrap" Load "type1" Load "speedo" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "Auto" Option "Device" "/dev/input/mice" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "se" EndSection Section "Monitor" ### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 31.0 - 81.0 VertRefresh 56.0 - 75.0 Mode "1600x1200" # D: 162.0 MHz, H: 75 kHz, V: 60 Hz DotClock 162.00 HTimings 1600 1664 1856 2160 VTimings 1200 1201 1204 1250 Flags "+HSync" "+VSync" EndMode EndSection Section "Device" Identifier "Card0" Driver "radeon" Card "** ATI Radeon (generic) [radeon]" Option "AGPMode" "8" # Option "AGPFastWrite" "true" Option "XAANoOffscreenPixmaps" "true" Option "DRI" "true" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1600x1200" EndSubSection EndSection Section "DRI" Group 0 Mode 0666 EndSection Section "Extensions" Option "Composite" "Enable" EndSection from make.conf INPUT_DEVICES="keyboard mouse" VIDEO_CARDS="vesa nv radeon"
Well, your xorg.conf specifies the radeon driver but paraview seems to load the r200 dri module which probably won't work. Maybe check your xorg logs and make sure there are no errors in this regard or otherwise. Also, you may want to check if the xorg driver you use can actually handle your card properly. I am still not quite sure why root uses a different setup. There may be a permission issue somewhere.
I've just installed paraview-2.6.2. When I start it and do Help -> Play demo, it crashes (both as me and as root) grozin@gandalf ~ $ paraview DemoScriptPath: /usr/lib/ParaView-2.6/../../share/paraview-2.6 DemoDataPath: /usr/lib/ParaView-2.6/../../share/paraview-2.6 Segmentation fault I have an on-board Intel card, and use the xorg i810 driver. I think the only opengl application I used is ppracer :-), and it works. I can attach the strace log if it is of any use.
Hi Andrey, Thanks for the note! Unfortunately, particularly since I can't reproduce this issue on any of my dev machines, there's not much I can do at this point unless somebody is able to pinpoint the problem. This is probably something that should be reported upstream or posted to the paraview mailing list. Best, Markus
Are these issues still relevant or have they disappeared with paraview-3.2.1? In this case I'd like to close this bug again. Thanks, Markus
Markus, > Are these issues still relevant or have they disappeared > with paraview-3.2.1? In this case I'd like to close this bug > again. I did not find the time yet to build ParaView on the machine that had the problem. I do it as soon as possible and inform you about the results. Daniel
(In reply to comment #22) > Markus, > > > > Are these issues still relevant or have they disappeared > > with paraview-3.2.1? In this case I'd like to close this bug > > again. > > I did not find the time yet to build ParaView on the machine that had the > problem. I do it as soon as possible and inform you about the results. And in the meantime?
Since all paraview 2.* ebuilds have been removed from portage I am closing this bug. Best, Markus
