Description of problem:
I can start the program just fine, but when I click on Story Mode at the main menu screen, the program crashes. This has happened four times in a row. I can let the program start and sit there, and it'll be fine. I clicked on Singleplayer, that loaded, then I clicked back and then Story Mode and it crashed again like before.

tailing /var/log/messages:
Apr 22 17:13:22 pmg kwin_x11: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41709, resource id: 10485762, major code: 15 (QueryTree), minor code: 0

I then restarted the program and I got:
Apr 22 17:14:18 pmg kwin_x11: QXcbConnection: XCB error: 3 (BadWindow), sequence: 43524, resource id: 10485760, major code: 18 (ChangeProperty), minor code: 0
Apr 22 17:14:30 pmg audit: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=32007 comm="supertuxkart" exe="/usr/bin/supertuxkart" sig=6
Apr 22 17:14:30 pmg kwin_x11: QXcbConnection: XCB error: 3 (BadWindow), sequence: 46402, resource id: 10485762, major code: 15 (QueryTree), minor code: 0

Looking through journalctl, it looks like from a previous attempt at running the program:
Apr 22 17:10:11 pmg.redhat.com abrt-hook-ccpp[31903]: Process 31519 (supertuxkart) of user 1000 killed by SIGABRT - dumping core
Apr 22 17:10:19 pmg.redhat.com abrt-hook-ccpp[31903]: Failed to create core_backtrace: waitpid failed: No child processes
Apr 22 17:10:19 pmg.redhat.com abrt-server[31912]: Can't load public GPG key /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-primary
Apr 22 17:10:20 pmg.redhat.com abrt-hook-ccpp[31903]: /var/spool/abrt is 3512668084 bytes (more than 1279MiB), deleting 'ccpp-2016-04-22-17:08:00-31383'
Apr 22 17:10:21 pmg.redhat.com kwin_x11[2441]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 564, resource id: 10485762, major code: 15 (QueryTree), minor code: 0
Apr 22 17:10:29 pmg.redhat.com kernel: 
Apr 22 17:10:29 pmg.redhat.com kernel: ======================================================
Apr 22 17:10:29 pmg.redhat.com kernel: [ INFO: possible circular locking dependency detected ]
Apr 22 17:10:29 pmg.redhat.com kernel: 4.6.0-0.rc4.git1.1.fc25.x86_64 #1 Not tainted
Apr 22 17:10:29 pmg.redhat.com kernel: -------------------------------------------------------
Apr 22 17:10:29 pmg.redhat.com kernel: DOM Worker/5840 is trying to acquire lock:
Apr 22 17:10:29 pmg.redhat.com kernel:  (&pipe->mutex/1){+.+.+.}, at: [<ffffffff812a227e>] pipe_lock+0x1e/0x20
Apr 22 17:10:29 pmg.redhat.com kernel: 
                                                    but task is already holding lock:
Apr 22 17:10:29 pmg.redhat.com kernel:  (&(&ip->i_iolock)->mr_lock){++++++}, at: [<ffffffffc03718f6>] xfs_ilock+0x196/0x220 [xfs]
Apr 22 17:10:29 pmg.redhat.com kernel: 
                                                    which lock already depends on the new lock.
Apr 22 17:10:29 pmg.redhat.com kernel: 
                                                    the existing dependency chain (in reverse order) is:
Apr 22 17:10:29 pmg.redhat.com kernel: 
                                                    -> #2 (&(&ip->i_iolock)->mr_lock){++++++}:
Apr 22 17:10:29 pmg.redhat.com kernel:        [<ffffffff81113c1e>] lock_acquire+0xfe/0x1f0
Apr 22 17:10:29 pmg.redhat.com kernel:        [<ffffffff8110c3ee>] down_write_nested+0x5e/0xc0
Apr 22 17:10:29 pmg.redhat.com kernel:        [<ffffffffc03718a2>] xfs_ilock+0x142/0x220 [xfs]
Apr 22 17:10:29 pmg.redhat.com kernel:        [<ffffffffc0363dea>] xfs_file_buffered_aio_write+0x7a/0x350 [xfs]
Apr 22 17:10:29 pmg.redhat.com kernel:        [<ffffffffc0364201>] xfs_file_write_iter+0x141/0x160 [xfs]
Apr 22 17:10:29 pmg.redhat.com kernel:        [<ffffffff81298831>] __vfs_write+0xd1/0x120
Apr 22 17:10:29 pmg.redhat.com kernel:        [<ffffffff812990e5>] vfs_write+0xa5/0x190
Apr 22 17:10:29 pmg.redhat.com kernel:        [<ffffffff8129a5b8>] SyS_write+0x58/0xd0
Apr 22 17:10:29 pmg.redhat.com kernel:        [<ffffffff81004039>] do_syscall_64+0x69/0x190
Apr 22 17:10:29 pmg.redhat.com kernel:        [<ffffffff818cd23f>] return_from_SYSCALL_64+0x0/0x7a
...

Version-Release number of selected component (if applicable):
supertuxkart-0.9.1-5.fc25.x86_64

How reproducible:
100% (that I've noticed today)

Steps to Reproduce:
1. Start supertuxkart
2. click Storymode
3.

Actual results:
program crashes as described above

Expected results:
program not to crash

Additional info: