Bug #650
closed
Added by Scott Stagg over 14 years ago.
Updated over 14 years ago.
Category:
Python scripting
Description
pyace.py crashes on my machine. In order to get it to work, I have to disable the " co" option in apParam.py. Lines 482... become:
for rgbfile in filelist:
if os.path.isfile(rgbfile+".txt"):
#hacked out -co option to xvfb
return " "
I only edited locally and have not committed. Moreover, I have had to hack all programs that require Xvfb on my machine. I am using Ubuntu version 9.10.
It is different on every distribution, I added code to check between Fedora and CentOS. See if you can add an automatic check to make it work.
I don't really know what the different options are trying to do. Below is the output from xvfb.log. Can you tell me what I should be trying?
Xvfb :2202 -once -ac -pn -screen 0 1200x1200x24 -fp /usr/share/fonts/X11/misc -co /usr/share/X11/rgb &Unrecognized option: -co
Fatal server error:
Unrecognized option: -co
- Status changed from New to Assigned
- Assignee set to Neil Voss
The options do not matter so much except that on CentOS the rgbfile option is required or it crashes and on Fedora if the rgbfile option is provided it crashes. I do not know why, but I know this is the case, so we have a work around using the getXversion option.
It looks like the rgbfile may not be required anymore on CentOS and we can comment it out. I will test it and get back to you.
- Target version set to Appion/Leginon 2.1.0
- Affected Version set to Appion/Leginon 2.0.1
- Show in known bugs set to Yes
- Status changed from Assigned to In Test
- Assignee changed from Neil Voss to Scott Stagg
Okay, Scott here's how it should work.
The older version of the Xvfb command need a link to the rgbfile, so it can map the color white to '#ffffff', otherwise it has no clue what white is.
I included the the getXversion function to determine which version of X you are running and add the command or not depending on the version.
CentOS v5.2-v5.5 with X v1.1.1 and Fedora v7,v8 requires the rgb file
Fedora v9-v13 with X v1.8 does not have rgb file option
Can you send me the info you get from the command:
X -version
You will need to copy the apParam.py from the trunk to your branch checkout to test.
- Affected Version changed from Appion/Leginon 2.0.1 to Pre-2.0
Your change to apParam.py didn't work for me. Below is the output from X -version:
X.Org X Server 1.6.4
Release Date: 2009-9-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server x86_64 Ubuntu
Current Operating System: Linux zeus 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic root=UUID=2a3ef234-e718-447f-9d59-58c8c9d1ad22 ro quiet splash
Build Date: 26 October 2009 05:19:56PM
xorg-server 2:1.6.4-2ubuntu4 (buildd@)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
BTW, when I tried to run pyace.py from the trunk, it failed with a completely different error. Is the trunk version running now?
I made another change and this one should work with your version of X. Also, now by default it assumes a new version of X.
That did it. It works now. Should I change status to closed now?
- Category set to Python scripting
- Status changed from In Test to In Code Review
- Assignee changed from Scott Stagg to Jim Pulokas
Next step is code review. Since you've tested it, it can be closed after the review.
- Status changed from In Code Review to Closed
Also available in: Atom
PDF