Bug 965394

Created attachment 750862 [details]
File: backtrace

Created attachment 750863 [details]
File: cgroup

Created attachment 750864 [details]
File: core_backtrace

Created attachment 750865 [details]
File: dso_list

Created attachment 750866 [details]
File: environ

Created attachment 750867 [details]
File: limits

Created attachment 750868 [details]
File: maps

Created attachment 750869 [details]
File: open_fds

Created attachment 750870 [details]
File: proc_pid_status

Created attachment 750871 [details]
File: var_log_messages

Created attachment 750872 [details]
File: xsession_errors

I had just done a fairly large update.  Before rebooting, I wanted to run xterm, so I pressed the "Windows" key, typed x (which showed) and t (which did not).

Perhaps the running gnome shell didn't get along with the updates.

reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
executable:     /usr/bin/gnome-shell
kernel:         3.9.9-302.fc19.x86_64
package:        gnome-shell-3.8.4-2.fc19
reason:         Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            1104

I just hit a crash in F21 gnome-shell which abrt claims is a dupe of this. The FAF page:

https://retrace.fedoraproject.org/faf/reports/142469/

has 1170 reports from F19, 211 from F20, 42 from F18, 12 from rawhide, and 1 from F17, covering gnome-shell 3.4.1-6.fc17  all the way up to gnome-shell-3.11.2-3.fc21 . So...either there's a longstanding crasher in GNOME which lots of people are hitting, or abrt is doing something wacky.

abrt folks, wdyt?

Created attachment 836891 [details]
the report directory of my 'dupe', minus coredump, which is 449MB

Hi Adam, I'm no longer connected with ABRT team, the new leader is rvokal so he should decide what to do with this bugzilla and he is the person who will answer all your future questions about ABRT.

Got this crash today on rawhide

Just happened to me on F20.

$ rpm -qa gnome-shell
gnome-shell-3.10.3-2.fc20.x86_64

I've the same gnome-shell version as above and it crashed 2 times (yesterday and today). Seems to me there is something wrong with it...

I've also experienced crashes often (for a while now, on different versions of Gnome 3).  Could be extensions though.

My Gnome Shell crashes *OFTEN*.  I have two systems running Fedora 20, one was a fresh install.  I could be any application when it crashes, but most often I think is when I am in Evolution.  I would be working, and then although the mouse can move, it won't select anything.  Pressing keys don't respond, although CTRL-ALT-F3 will take me to another TTY which I can log into - slowly - because the disk is very very busy.  If I run iotop, I see that gnome-shell is hogging 99% disk IO, and eventually it gives way to ABRT.  Then I know I can work again.  I can CTRL-ALT-F1 to get back to the shell session, and have to wait for the screen to bring back all the gnome-shell items.  It is VERY frustrating.

This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

ABRT matched this bug on my F28 installation.  The symptom is that my PC has been idle, and hence locked, for a few hours.  I enter my password.  Gnome-shell crashes, and takes me back to the lock screen.  I enter my password again, and all is good.

See below:

--- Running report_uReport ---
('report_uReport' completed successfully)

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES'
Querying server settings
Retrace server can not be used, because the crash is too large. Try local retracing.
The size of your crash is 1.9 GiB, but the retrace server only accepts crashes smaller or equal to 1.2 GiB.
Do you want to generate a stack trace locally? (It may download a huge amount of data but reporting can't continue without stack trace). 'YES'
Analyzing coredump 'coredump'
Missing build id: libnvidia-glcore.so.390.77
Missing build id: libnvidia-tls.so.390.77
Missing build id: libGLX_nvidia.so.0
Missing build id: libnvidia-egl-wayland.so.1
Missing build id: libnvidia-glsi.so.390.77
Missing build id: libEGL_nvidia.so.0
All debuginfo files are available
Generating backtrace
Backtrace is generated and saved, 99372 bytes

--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla
Duplicate bugzilla bug '#965394' was found
Searching for updates
No updates for this package found