Description of problem: I attemp to start pymol on Fedora rawhide and get a Mesa7.3-devel error. Version-Release number of selected component (if applicable): rawhide How reproducible: always Steps to Reproduce: 1. enter pymol executable Actual results: failure to start program and the following messages: Mesa 7.3-devel implementation error: radeon_program_pair.c::allocate_input_registers(): Don't know how to handle inputs 0x8 Please report at bugzilla.freedesktop.org pc=0************************************* Hardware program ---------------- NODE 0: alu_offset: 0, tex_offset: 0, alu_end: -1, tex_end: -1, flags: 00000000 *********************************WARN_ONCE********************************* File r300_render.c function r300Fallback line 359 Software fallback:!fp->translated *************************************************************************** Mesa 7.3-devel implementation error: radeon_program_pair.c::allocate_input_registers(): Don't know how to handle inputs 0x8 Please report at bugzilla.freedesktop.org pc=1************************************* Hardware program ---------------- NODE 0: alu_offset: 0, tex_offset: 0, alu_end: -1, tex_end: -1, flags: 00000000 /home/zachcp/Programs/pymol/./pymol: line 14: 4180 Segmentation fault $PYMOL_PATH/pymol.exe "$@"
Note that FlightGear-1.0.0-4.fc10.i386 (latest in Rawhide) crashes on startup because of this bug. Graphics card: Radeon 9550 (RV350). (Smolt profile: pub_98330863-11f8-4b35-9644-1c435c67465a ) It is *NOT* prevented by "export disable_lowimpact_fallback=true". This appears to be https://bugs.freedesktop.org/show_bug.cgi?id=17929 Note also that there is a patch attached to above that might help from Michel Danzer. No point in shipping a broken FlightGear in F10.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Confirmed on x86_64 FC10, R400 (FireGL V7100). Packages : mesa-dri-drivers-7.2-0.14.fc10.x86_64 mesa-libGL-7.2-0.14.fc10.x86_64 This is also triggered by /usr/bin/teapot from mesa-demos. Setting LIBGL_ALWAYS_SOFTWARE="yes" obviously makes the problem go away (at the expense of 3D acceleration, though).
These could be separate bugs... Zachary, could you : * attach the X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments ; * confirm you still see the bug in Fedora 10 with updates ? If yes, could you test the latest Mesa build in Koji : http://koji.fedoraproject.org/koji/buildinfo?buildID=73082
Created attachment 326827 [details] xorg.conf file
Created attachment 326828 [details] xorg log file I had a number of xorg.*.log files. this is the most recent one
Using Fedora 10 with updates. The bug is slightly different now. If I type "pymol" the program will open (did not happen previously - the bug would immedietly crash the program). However when I try to open a file I obtain a similar crash (see below). I will try the new builds you suggest. Also - how/where do I set LIBGL_ALWAYS_SOFTWARE="yes" thanks zach cp ... ... ... OpenGL graphics engine: GL_VENDOR: DRI R300 Project GL_RENDERER: Mesa DRI R300 20060815 x86/MMX/SSE2 TCL GL_VERSION: 1.3 Mesa 7.3-devel Detected 2 CPU cores. Enabled multithreaded rendering. CmdLoad: "lowEmarch27.pdb" loaded as "lowEmarch27". Mesa 7.3-devel implementation error: radeon_program_pair.c::allocate_input_registers(): Don't know how to handle inputs 0x8 Please report at bugzilla.freedesktop.org pc=0************************************* Hardware program ---------------- NODE 0: alu_offset: 0, tex_offset: 0, alu_end: -1, tex_end: -1, flags: 00000000 *********************************WARN_ONCE********************************* File r300_render.c function r300Fallback line 363 Software fallback:!fp->translated *************************************************************************** Mesa 7.3-devel implementation error: radeon_program_pair.c::allocate_input_registers(): Don't know how to handle inputs 0x8 Please report at bugzilla.freedesktop.org pc=1************************************* Hardware program ---------------- NODE 0: alu_offset: 0, tex_offset: 0, alu_end: -1, tex_end: -1, flags: 00000000 /usr/bin/pymol: line 2: 4180 Segmentation fault /usr/bin/python /usr/lib/python2.5/site-packages/pymol/__init__.py $*
just run in a terminal : export LIBGL_ALWAYS_SOFTWARE="yes" pymol if it works, it's a temporary workaround, not a fix, so please don't close the bug.
new mesa drivers from Koji work! program fires up no problem. There is an error message in the terminal (see below) but the program does not crash. *********************************WARN_ONCE********************************* File r300_state.c function r300SetupRSUnit line 1737 Don't know how to satisfy InputsRead=0x00000008 *************************************************************************** thanks francois.
Zachary, You're welcome, nice to hear that. Could you add the exact version of mesa you pulled from Koji ? I've reopened the bug until the fix is in updates not Koji. Thanks in advance.
Installing the following packages fixed the bug: glx-utils-7.2-0.15.fc10.i386.rpm mesa-debuginfo-7.2-0.15.fc10.i386.rpm mesa-demos-7.2-0.15.fc10.i386.rpm mesa-dri-drivers-7.2-0.15.fc10.i386.rpm mesa-libGL-7.2-0.15.fc10.i386.rpm mesa-libGL-devel-7.2-0.15.fc10.i386.rpm mesa-libGLU-7.2-0.15.fc10.i386.rpm mesa-libGLU-devel-7.2-0.15.fc10.i386.rpm mesa-libOSMesa-7.2-0.15.fc10.i386.rpm mesa-libOSMesa-devel-7.2-0.15.fc10.i386.rpm thanks
Closing (the fixed packages are on the mirrors).
Thank you for the bug report. This particular bug was fixed and a update package was published for download. Please feel free to report any further bugs you find. You can obtain the updated package by typing 'yum update <package>' or using the graphical updater.