Bug 1026530

Created attachment 819375 [details]
File: backtrace

Created attachment 819376 [details]
File: cgroup

Created attachment 819377 [details]
File: core_backtrace

Created attachment 819378 [details]
File: dso_list

Created attachment 819379 [details]
File: environ

Created attachment 819380 [details]
File: exploitable

Created attachment 819381 [details]
File: limits

Created attachment 819382 [details]
File: maps

Created attachment 819383 [details]
File: open_fds

Created attachment 819384 [details]
File: proc_pid_status

Occurs every time when I launch game Multiwinia from steam
[21694.709433] gnome-shell[11177]: segfault at 238 ip 00007fc3e95521a2 sp 00007fff18b43590 error 4 in i965_dri.so[7fc3e94a2000+d7000]
[21790.410251] gnome-shell[18813]: segfault at 238 ip 00007fc9a193b1a2 sp 00007fff6ab98b10 error 4 in i965_dri.so[7fc9a188b000+d7000]

reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: gen7_update_renderbuffer_surface
executable:     /usr/bin/gnome-shell
kernel:         3.12.0-2.fc21.x86_64+debug
package:        gnome-shell-3.10.2.1-1.fc20
reason:         Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
runlevel:       N 5
type:           CCpp
uid:            1000

I was playing Bastion and gnome-shell crashed in the process, killing my game altogether.

reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        gnome-shell --sm-client-id 103f6fa7a0cff12205137582940031300000275290000
crash_function: gen7_update_renderbuffer_surface
executable:     /usr/bin/gnome-shell
kernel:         3.11.10-301.fc20.x86_64
package:        gnome-shell-3.10.2.1-3.fc20
reason:         Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

Launch game "Wargame: European Escalation" and shitch between programs.

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: gen7_update_renderbuffer_surface
executable:     /usr/bin/gnome-shell
kernel:         3.12.6-300.fc20.x86_64
package:        gnome-shell-3.10.2.1-3.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Happens sporadically while playing Violett in Steam.

Another user experienced a similar problem:

I was playing a game at Steam before that crash. The game was running fluidly and normally. Probably the error occurs because it's an OpenGL application with full screen

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: gen7_update_renderbuffer_surface
executable:     /usr/bin/gnome-shell
kernel:         3.12.7-300.fc20.x86_64
package:        gnome-shell-3.10.2.1-3.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Are we all using Optimus/Bumblebee?

Bumblebee for me but it's just happening if using primusrun.

(In reply to Pedro Francisco from comment #16)
> Are we all using Optimus/Bumblebee?

No, I'm not.

I have an Ivy Bridge chip and no discrete graphics and this bug happens to me several times every day.

I am using bumblebee with the nvidia driver.

I am just testing with GLXGears.
Optirun works, but when I use primus Gnome-Shell crashes.

I was playing Amnesia - running on Intel HD 4000

I've had a talk about this bug in the #gnome-shell channel on GimpNet. Apparently, this issue is not really related to gnome-shell, it's a bug in the Intel mesa driver.

gen7_update_renderbuffer_surface is in mesa/drivers/dri/i965/gen7_wm_surface_state.c
(NOTE: gen7 means Ivy Bridge and Haswell chips.)

I'm now trying to update to mesa 10 in updates-testing and see if the problem goes away.

Another user experienced a similar problem:

If XBMC is changed from Windowed mode to Full Screen mode, gnome-shell crashes.

reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: gen7_update_renderbuffer_surface
executable:     /usr/bin/gnome-shell
kernel:         3.13.6-200.fc20.x86_64
package:        gnome-shell-3.10.4-2.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

I confirm comment 23. Switching XBMC from window mode to full screen crashes gnome-shell 3.10.4 every time.



Name        : gnome-shell
Arch        : x86_64
Version     : 3.10.4
Release     : 2.fc20


Name        : xbmc
Arch        : x86_64
Version     : 13.0
Release     : 0.10.Gotham_beta3.fc20
S

Happens pretty regularly when I launch Starbound from Steam

I can trigger this by changing the volume using the media-keys while playing Dota 2. As soon as the volume OSD pops up, the game freezes and gnome-shell crashes.

Possible workaround is setting PRIMUS_UPLOAD to 1 or 2 as mentioned here: https://github.com/amonakov/primus/issues/140#issuecomment-45313136

Example: PRIMUS_UPLOAD=2 PRIMUS_VERBOSE=2 optirun -b primus glxgears

Another user experienced a similar problem:

Problem appears to be triggered by running bumblebee's optirun with primus (or plain primusrun) without using PRIMUS_UPLOAD=2 (e.g.: PRIMUS_UPLOAD=2 PRIMUS_VERBOSE=2 optirun -b primus glxgears ) but might be trigger by other means...
See https://bugzilla.redhat.com/show_bug.cgi?id=1026530 

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: gen7_update_renderbuffer_surface
executable:     /usr/bin/gnome-shell
kernel:         3.14.8-200.fc20.x86_64
package:        gnome-shell-3.10.4-5.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

I do not use the discrete graphics at all (no bumblebee/primus), and this bug happens to me, often when switching in fullscreen video players. So I think the Optimus graphics usage is a red herring.

Happens sporadically while playing Dota 2.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.