Dr. Racket crashes on launch

As the title says, Dr. Racket crashes whenever I try to launch it and I get the following errors. I cannot seem to figure out what is wrong, it crashes regardless of nvidia or nouveau driers.
Direct rendering works (confimed via glxinfo | grep direct).
Currently using nvidia drivers on (new) Tumbleweed.

gum:~/ $ drracket 
NETWM: Warning readIcon() needs buffer adjustment!
NETWM: Warning readIcon() needs buffer adjustment!
NETWM: Warning readIcon() needs buffer adjustment!
NETWM: Warning readIcon() needs buffer adjustment!
NETWM: Warning readIcon() needs buffer adjustment!
NETWM: Warning readIcon() needs buffer adjustment!
NETWM: Warning readIcon() needs buffer adjustment!
NETWM: Warning readIcon() needs buffer adjustment!
NETWM: Warning readIcon() needs buffer adjustment!
NETWM: Warning readIcon() needs buffer adjustment!
NETWM: Warning readIcon() needs buffer adjustment!
NETWM: Warning readIcon() needs buffer adjustment!
The program 'drracket' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 5517 error_code 8 request_code 70 minor_code 0)
  (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.)

Any help would be appreciated.

I seem to also get this error in GIMP when I use the text tool. Any clues as to what is causing this? It is very annoying…


gum:~/ $ gimp
GEGL-geglmodule.c-Message: Module '/usr/lib64/gegl-0.2/matting-levin.so' load error: libblas.so.3: cannot open shared object file: No such file or directory
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 11838 error_code 3 request_code 1 minor_code 0)
(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.)

(script-fu:7488): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error



openSUSE Factory 64 bit
KDE 4.14.1

Graphics card? driver?

oops missed that in first post.

In that case Tumbelweed… Probably need to report it Also should go to the tumbleweed thread

Did a fresh install of 13.1, still get this issue. Using nouveau drivers, the card is a 560Ti. Here are my repos.


gum:~/ $ lr
#  | Alias                     | Name                               | Enabled | Refresh
---+---------------------------+------------------------------------+---------+--------
 1 | KDE:Extra                 | KDE:Extra                          | Yes     | Yes    
 2 | KDE:Unstable:SC           | KDE:Unstable:SC                    | Yes     | Yes    
 3 | devel:languages:python    | devel:languages:python             | Yes     | Yes    
 4 | home:malcolmlewis:TESTING | home:malcolmlewis:TESTING          | Yes     | Yes    
 5 | libdvdcss                 | libdvdcss                          | Yes     | Yes    
 6 | openSUSE-13.1-1.10        | openSUSE-13.1-1.10                 | No      | Yes    
 7 | packman                   | packman                            | Yes     | Yes    
 8 | repo-debug                | openSUSE-13.1-Debug                | No      | Yes    
 9 | repo-debug-update         | openSUSE-13.1-Update-Debug         | No      | Yes    
10 | repo-debug-update-non-oss | openSUSE-13.1-Update-Debug-Non-Oss | No      | Yes    
11 | repo-non-oss              | openSUSE-13.1-Non-Oss              | Yes     | Yes    
12 | repo-oss                  | openSUSE-13.1-Oss                  | Yes     | Yes    
13 | repo-source               | openSUSE-13.1-Source               | No      | Yes    
14 | repo-update               | openSUSE-13.1-Update               | Yes     | Yes    
15 | repo-update-non-oss       | openSUSE-13.1-Update-Non-Oss       | Yes     | Yes    

Any ideas?

Yes report in the Tumbleweed thread. I suspect it is tumbleweed issue. But If you have gone back to vanilla 13.1 ???

But then again you may need to run the NVIDIA driver. Also you may want to try a different user to see if it is a desktop config problem

Note that moving backwards can cause confusion in conifg files. Programs can in general move forward but don’t know how to set configs back

You might be right but that is unlikely because I have never use Dr Racket before. Still, will at least check out the possibility.

OK assuming you are using the same home then going to Tumbleweed may change some config files for your desktop. Going back the applications don’t know how to deal with the changes. Goint to a new user account will show if this is a problem or not.

Okay so it works on a new user :). I tried clearing my .kde folders and using fresh ones but that did not resolve the issue. Any idea what other files/folders in ~ could be causing this? Keep in mind its not just an issue with drracket so it must be something that several programs access.

Not sure but I think that at least some configs for KDE now are in the ~/.config folder.

On 11/12/2014 05:56 PM, gogalthorp wrote:
>
> Not sure but I think that at least some configs for KDE now are in the
> ~/.config folder.
>
>

Moved .config and now the issue is resolved. Thanks a lot, I will
remember in the future that this folder is used! :smiley:


openSUSE Factory 64 bit
KDE 4.14.1

On 11/12/2014 07:42 PM, alanbortu wrote:
> On 11/12/2014 05:56 PM, gogalthorp wrote:
>>
>> Not sure but I think that at least some configs for KDE now are in the
>> ~/.config folder.
>>
>>
>
> Moved .config and now the issue is resolved. Thanks a lot, I will
> remember in the future that this folder is used! :smiley:
>

Figured out the issue, it is caused by a QtCurve theme that is
installed. Forcing GTK to use a different theme solves this issue.


openSUSE Factory 64 bit
KDE 4.14.1