rosrun rviz rviz -> Segmentation fault

edit

I've been told that my error is different from the post where I have originally asked this questions. Since I still have this problem I would like to ask for help in this topic then. When I try to run rviz "Segmentation fault" error. I'm using 10.4 (running on vmware) and electric:

user@ubuntu:~/.rviz$ rosrun rviz rviz
[ INFO] [1321935622.778521758]: rviz revision number 1.6.6
[ INFO] [1321935622.778786716]: ogre_tools revision number 1.6.2
[ INFO] [1321935622.778826499]: compiled against OGRE version 1.7.3 (Cthugha)
[ INFO] [1321935622.887818975]: Loading general config from [/home/user/.rviz/config]
[ INFO] [1321935622.888264749]: Loading display config from [/home/user/.rviz/display_config]
[ INFO] [1321935622.966972423]: RTT Preferred Mode is PBuffer.
[ INFO] [1321935623.281105694]: Texture for pass 0: creating with size 1 x 1
Segmentation fault

I tried to remove lines in display_config - it didn't help. I removed both configs and got the same results. I was trying to restart workstation and turtlebot but it didn't help either. One or two times I had different error which actually did come up here as well:

user@ubuntu:~/.rviz$ rosrun rviz rviz -d 'rospack find turtlebot_interactive_markers'/config/interactive_markers.vcg 
[ INFO] [1321935611.525499608]: rviz revision number 1.6.6
[ INFO] [1321935611.525703015]: ogre_tools revision number 1.6.2
[ INFO] [1321935611.525739543]: compiled against OGRE version 1.7.3 (Cthugha)
[ INFO] [1321935611.639785830]: Loading general config from [/home/user/.rviz/config]
[ INFO] [1321935611.640200506]: Loading display config from [/home/user/.rviz/display_config]
[ INFO] [1321935611.700409981]: RTT Preferred Mode is PBuffer.
The program 'rviz' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 21 error_code 9 request_code 55 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 ideas (other than remove files)? Thanks.