Hi Paul,

glxgears
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  129 (Apple-DRI)
  Minor opcode of failed request:  2 ()
  Value in failed request:  0x600002
  Serial number of failed request:  27
  Current serial number in output stream:  27

Unfortunately, it is more likely a macOS / X issue…
Don’t know if a new compilation would fix the issue. Apple has probably changed 
the video driver.

> Le 23 sept. 2025 à 11:20, Paul Emsley <[email protected]> a écrit :
> 
> Does glxgears work?
> 
> If yes, then the problem is more towards my end. If no, then the issues is 
> with the OS/XQuartz.
> 
> Paul.
> 
> I had not heard of Tahoe until this email.
> 
> 
> 
> On 23/09/2025 09:04, Xavier Brazzolotto wrote:
>> 
>> --
>> Others have a similar issue with Coot & macOS Tahoe...
>> 
>> 
>> https://discussions.apple.com/thread/256140259?sortBy=rank
>> 
>> Unfortunately, it was not reported on the coot mailing list.
>> 
>> 
>>> Le 21 sept. 2025 à 09:07, Xavier Brazzolotto <[email protected]> 
>>> <mailto:[email protected]> a écrit :
>>> 
>>> Dear coot users, Dear Paul
>>> 
>>> I’ve just updated to macOS 26 (Tahoe)
>>> 
>>> Unfortunately, I have a bug when launching « old » coot (0.9.8.96 - CCP4-9 
>>> version).
>>> Is anyone experiencing the same issue?
>>> 
>>> I’ve tried to reinstall XQuartz and CCP4, but I’m still facing the same 
>>> error message.
>>> 
>>> The program 'coot-bin' received an X Window System error.
>>> This probably reflects a bug in the program.
>>> The error was 'BadValue (integer parameter out of range for operation)'.
>>>   (Details: serial 310 error_code 2 request_code 129 minor_code 2)
>>>   (Note to programmers: normally, X errors are reported asynchronously;
>>>    that is, you will receive the error a while after causing it.
>>>    To debug your program, run it with the --sync command line
>>>    option to change this behavior. You can then get a meaningful
>>>    backtrace from your debugger if you break on the gdk_x_error() function.)
>>> . ------ Coot crashed - trying to diagnose -----
>>> Guile 1.8.8
>>> Copyright (c) 1995, 1996, 1997, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 
>>> 2007, 2008 Free Software Foundation
>>> Guile may be distributed under the terms of the GNU General Public Licence;
>>> certain other uses are permitted as well.  For details, see the file
>>> `COPYING', which is included in the Guile distribution.
>>> There is no warranty, to the extent permitted by law.
>>> catching the crash log:
>>> coot-exe: "/Applications/ccp4-9/coot_py2/libexec/coot-bin"
>>> /bin/ls
>>> -rwxr-xr-x@ 1 root  admin  9356184 Apr 27 19:06 
>>> /Applications/ccp4-9/coot_py2/libexec/coot-bin
>>> coot-version: 
>>> /Applications/ccp4-9/coot_py2/libexec/coot-bin
>>> Builder_info: CCP4, Oxfordshire, UK
>>> Enabled: Enhanced-ligand-tools C++-11 Threads Boost-based-thread-pool 
>>> Goocanvas GSL LibCurl 
>>> Binary type: Darwin-MacOSX-11.7.10-x86_64-python-gtk2
>>> git commit: 50638a38145722303017be802622d65d83bd7f66
>>> Builder_info: CCP4, Oxfordshire, UK
>>> [with python 2.7.16 embedded]
>>> [with guile 1.8.8 embedded]
>>> 0.9.8.96 (revision-count 10988)
>>> platform: 
>>> /usr/bin/uname
>>> Darwin GRE073859.local 25.0.0 Darwin Kernel Version 25.0.0: Mon Aug 25 
>>> 21:17:51 PDT 2025; root:xnu-12377.1.9~3/RELEASE_ARM64_T6020 x86_64
>>> core: #f
>>> No core file found.  No debugging
>>> 
>>> Fortunately, new coot (homebrew) seems to work even if I am still not used 
>>> to it yet, and I miss the carbohydrate module.
>>> 
>>> Cheers
>>> Xavier
>> 
>> 
>> To unsubscribe from the COOT list, click the following link:
>> https://www.jiscmail.ac.uk/cgi-bin/WA-JISC.exe?SUBED1=COOT&A=1
>> 


########################################################################

To unsubscribe from the COOT list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/WA-JISC.exe?SUBED1=COOT&A=1

This message was issued to members of www.jiscmail.ac.uk/COOT, a mailing list 
hosted by www.jiscmail.ac.uk, terms & conditions are available at 
https://www.jiscmail.ac.uk/policyandsecurity/

Reply via email to