Created attachment 1051875 [details]
File: backtrace

Created attachment 1051876 [details]
File: cgroup

Created attachment 1051877 [details]
File: core_backtrace

Created attachment 1051878 [details]
File: dso_list

Created attachment 1051879 [details]
File: environ

Created attachment 1051880 [details]
File: limits

Created attachment 1051881 [details]
File: maps

Created attachment 1051882 [details]
File: mountinfo

Created attachment 1051883 [details]
File: namespaces

Created attachment 1051884 [details]
File: open_fds

Created attachment 1051885 [details]
File: proc_pid_status

Created attachment 1051886 [details]
File: var_log_messages

Maybe related to nvidia drivers?

Another user experienced a similar problem:

after Login to GNOME I have no Desktop-Icons and when I start 'nautilus' the error achieved.
Following message pop up:
    Hoppla!
    Entschuldigung, Files scheint abgestürzt zu sein. Bitte melden ...legentlich auch mal:

or sometimes:
    Hoppla!
    Entschuldigung, /usr/libexec/dleyna-renderer-service scheint ab ...

Nautilus crashed.
    $ nautilus
    (nautilus:7737): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 34
    (nautilus:7737): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 34
    (nautilus:7737): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 34
    (nautilus:7737): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 34
    **
    ERROR:nautilus-canvas-container.c:6118:finish_adding_new_icons: assertion failed: (!container->details->auto_layout)
    Abgebrochen (Speicherabzug geschrieben)

 GNOME Classic also don't run, Return to Login.


reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell --wayland --display-server
crash_function: _g_log_abort
executable:     /usr/bin/gnome-shell
global_pid:     2983
kernel:         4.1.3-201.fc22.i686
package:        gnome-shell-3.16.3-1.fc22
reason:         gnome-shell killed by SIGTRAP
runlevel:       unknown
type:           CCpp
uid:            1000

Oh, wonder!
After I send this Bug-report and have a Update of my system and this made:
"If you need to disable Wayland for GDM, edit /etc/gdm/custom.conf to reflect the following:
[daemon]
WaylandEnable=false "
 the GNOME and GNOME Classic works fine on my Fedora 22 system in a VirtualBox.

I had this (got here via abrt) but with a different "steps to reproduce"

- Various apps open, including Firefox with several tabs open including one on bug 1248741

- Click on attachment from https://bugzilla.redhat.com/show_bug.cgi?id=1248741#c14

- Firefox app chooser dialog, I choose gedit.

- GNOME shell crashes, killing session/apps.

gnome-shell at 3.16.3-1.fc22

Intel graphics:

00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)

Dualhead:

$ xrandr -q
Screen 0: minimum 8 x 8, current 3360 x 1200, maximum 32767 x 32767
LVDS1 connected 1440x900+1920+0 (normal left inverted right x axis y axis) 261mm x 163mm
   1440x900      50.00*+
   1280x800      50.00  
   1024x768      60.00  
   800x600       60.32    56.25  
   720x450       50.00  
   640x480       59.94  
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200     59.95*+
   1600x1200     60.00  
   1680x1050     59.88  
   1280x1024     60.02  
   1280x960      60.00  
   1024x768      60.00  
   800x600       60.32  
   640x480       60.00  
   720x400       70.08  
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

In my case I tried to start 'filelight' from gnome-terminal (3.16.2). After pressing ENTER I got logged out.

(something like) this just happened again - no ABRT entry so I can't be sure if it's the same bug, so just going by symptom.

In this case I had just resumed the laptop from hibernation - session gone, had to restart everything.  This is quite disruptive, any way I could add debug/extra logging that might help?

I just had this annoying situation as well.

GNOME Shell quit unexpectedly
The application encountered a problem and could not continue.

gnome-shell 3.16.3.1.fc22.x86_64

Everything on the previous desktop gone now!

(In reply to Dimitris from comment #18)
> (something like) this just happened again - no ABRT entry so I can't be sure
> if it's the same bug, so just going by symptom.

abrt has captured this bug #1243011 once for me; but I've had many crashed where Gnome has just disappeared from under me without trace. I filed bug #1250040 for this, but they may be the same. To be honest I am so used to the latter bug happening I can't remember whether the circumstances of the singular bug #1243011 were the same.

> In this case I had just resumed the laptop from hibernation - session gone,
> had to restart everything.  This is quite disruptive, any way I could add
> debug/extra logging that might help?

As noted in the other bug #1250040, I do use suspend, and some occurrences certainly seem to happen quite soon after resuming.

I suspect this bug might only happen when a new instance of gnome-shell is restarting right after a crash: the function is meta_clutter_init(). So that wouldn't be the real cause of the first crash.

Since ABRT doesn't pick up anything, it would be interesting to get the system messages right after a crash. You can put these in a file with
journalctl -ba > journalctl.log

FWIW, I'm seeing similar symptoms (and got this trace a few times), and I suspect systemd-journald might be involved (Bug 1199442). See also Bug 1196485, Bug 1258872.

This happens every time when I'm logged into GNOME-Shell and switch to another TTY (e.g. CTRL+ALT+F2) When I switched back to GNOME-Shell my session was dead and ABRT window popped up.

Thomas: if you can reproduce it, would you file a bug in the GNOME bug tracker? There, gnome-shell developers will take care of debugging this with you. Be sure to copy the backtrace from above, and mention details about your graphics card and driver. Please post the link here once you're done. Thanks!

(In reply to Milan Bouchet-Valat from comment #24)
> Thomas: if you can reproduce it, would you file a bug in the GNOME bug
> tracker? There, gnome-shell developers will take care of debugging this with
> you. Be sure to copy the backtrace from above, and mention details about
> your graphics card and driver. Please post the link here once you're done.
> Thanks!

I'm not sure I can reproduce it any more. It seems that it happened only once and the following behavior was just GNOME-Shell logging me out when switching to another TTY.

Anyway I attached the journal output, but it is private since there are some potentially sensitive information as IP addresses.

My HW is Lenovo T450s with Intel Corporation Broadwell-U Integrated Graphics. I use Also docking station with two external monitors. (not sure if this is helpful)

I encountered the same bug on a Lenovo x201i, a docking station and an external monitor.

Created attachment 1077349 [details]
system log from moment of the crash

(In reply to Milan Bouchet-Valat from comment #21)
> Since ABRT doesn't pick up anything, it would be interesting to get the
> system messages right after a crash.

I'm attaching three syslogs from around the moment of a crash. This the messages from gnome-session:
WARNING: Lost name on bus: org.gnome.SessionManager
are around the critical moment.

The second log includes a resume from suspend shortly before.

Anecdotally I'd say that preceding a crash there is frequently (always?) an above average amount of disk activity and slow responsiveness from the deskop (possibly around Evolution, which seems to pop up notifications at the end of this). It could also be coincidence, of course.

Created attachment 1077350 [details]
system log from the moment of a crash

Created attachment 1077351 [details]
system log from the moment of a crash

I just also hit this and shortly before the crash of gnome-shell SELinux from bug #1245477 was showing up. Maybe that's related?

A shot in the dark.

This just happened to me again. It coincided with laggy respond after a resume from suspend, as it often does.

I happened to have top open and visible, and it was showing a high load, in the 20s.

Is there a possibility that something to do with the shell is being too aggressive in timing out and killing off the shell in response? When actually it's just the system under high load?

The would explain the apparent lack of errors.

(What's causing such a high load is a different question, although it feels consistent with Evolution reconnecting and doing whatever it does)

abrt just caught a crash, although this time gnome-shell restarted. In case it's related:
https://retrace.fedoraproject.org/faf/reports/839702/

Shell has been far more unstable for me in the last week or so, with this crash occurring at least daily.

(In reply to Kevin R. Page from comment #32)
> abrt just caught a crash, although this time gnome-shell restarted. In case
> it's related:
> https://retrace.fedoraproject.org/faf/reports/839702/
> 
> Shell has been far more unstable for me in the last week or so, with this
> crash occurring at least daily.

Unfortunately this bug report is a catch-all for unrelated problems, because *first* the shell crashes, then second the attempt to respawn the shell sometimes hits this bug. There is no reason to think that the *initial* crashes are related.

It's interesting that you are hitting crashes (that particular crash?) so much - from our incoming bug reports this is not typical - so there's probably something about your setup which is making the bug more likely. Are you using any extensions?

(In reply to Owen Taylor from comment #33)

> Unfortunately this bug report is a catch-all for unrelated problems, because
> *first* the shell crashes, then second the attempt to respawn the shell
> sometimes hits this bug. There is no reason to think that the *initial*
> crashes are related.
> 
> It's interesting that you are hitting crashes (that particular crash?) so
> much - from our incoming bug reports this is not typical - so there's
> probably something about your setup which is making the bug more likely. Are
> you using any extensions?

I'd also be interested if your your journalctl output shows any Javascript backtraces - this crash looks like if object initialization fails a subsequent garbage collection might crash like that.

@Owen might be related to dual monitor setups, maybe even to the intel driver bugs in conjunction with a docking station and suspend. Since last week (or a bit longer), the situation stabilized a lot. At least, I do not have to take out the notebook from the docking station and insert it again to get a picture on the monitor.

A "crash" afterwards was quite common. Pretty much happened every other time I resumed from suspend.
Resuming my notebook without docking while being suspended in the docking, still leaves me with a black screen most of the time (needs reboot then), but I guess this is more a kernel bug.

But it should really be worth investigation into the dual monitor (with display port and/or hdmi) and suspend/resume in a docking station.

Oh and there was not striking entry in the journal afterwards. Just the usual startup messages from gnome-shell.

(In reply to Philipp Gampe from comment #35)
> @Owen might be related to dual monitor setups, maybe even to the intel
> driver bugs in conjunction with a docking station and suspend. Since last
> week (or a bit longer), the situation stabilized a lot. At least, I do not
> have to take out the notebook from the docking station and insert it again
> to get a picture on the monitor.
I'm on nvidia proprietary driver with a single monitor, wired with hdmi. Its an Asus VG278.

(In reply to Owen Taylor from comment #33)
> Unfortunately this bug report is a catch-all for unrelated problems, because
> *first* the shell crashes, then second the attempt to respawn the shell
> sometimes hits this bug. There is no reason to think that the *initial*
> crashes are related.
> 
> It's interesting that you are hitting crashes (that particular crash?) so
> much - from our incoming bug reports this is not typical - so there's
> probably something about your setup which is making the bug more likely. Are
> you using any extensions?

OK, I'll move back to putting details of the underlying problem in bug #1250040 

(I have disabled/deleted extensions but it's still happening)

(In reply to Owen Taylor from comment #34)
> I'd also be interested if your your journalctl output shows any Javascript
> backtraces - this crash looks like if object initialization fails a
> subsequent garbage collection might crash like that.

I can't see anything, but what should I search for? I'll report in bug #1250040

There are quite a few different things potentially being combined here - most times Mutter fails to connect to the display server, you get this backtrace. Making Mutter terminate in these cases in a way that does not cause an ABRT report to be filed is definitely possible, but I'd like to as much as possible understand all of what is going on before taking that step.

Things that would be useful to know if you hit this crash.

 * Was the crashing gnome-shell the gnome-shell for the session or the gnome-shell for gdm? (Did the command line for the crashing executable include --mode=gdm ?)

 * Were you attempting to log into a session, or did an existing session crash?

 * If an existing session crashed, is there a message like:

   WARNING: Application 'gnome-shell.desktop' killed by signal ...
   or:
   WARNING: Application 'gnome-shell-wayland.desktop' killed by signal ...
  
   in the systemd journal?

 * If an X session crashed, is there indication of the X server abnormally exiting in the systemd journal?

 * Is your system using the provided Fedora graphics drivers, or with the NVIDIA proprietary drivers?

 > * Was the crashing gnome-shell the gnome-shell for the session or the gnome-shell for gdm? (Did the command line for the crashing executable include --mode=gdm ?)

Think it was the session one.

> * Were you attempting to log into a session, or did an existing session crash?

I tried to login after suspend, thus with an active session and a screenlocker.

> * If an X session crashed, is there indication of the X server abnormally exiting in the systemd journal?

> I have not seen anything, just the logs of the startup.

> * Is your system using the provided Fedora graphics drivers, or with the NVIDIA proprietary drivers?

Intel drivers provided by fedora. Please not that this only happens with external screens being connected and/or removing or inserting the notebook into the docking station.

Actually things seem to work now since about 2 weeks, therefore I guess the latest kernel updates fixed something there.

>  * Was the crashing gnome-shell the gnome-shell for the session or the
> gnome-shell for gdm? (Did the command line for the crashing executable
> include --mode=gdm ?)

I can't find the command line for the crashing executable but as you'll see below, gnome-sessions's crash is preceded by gdm-x-session's crash.

>  * Were you attempting to log into a session, or did an existing session crash?

Existing session crash unexpectedly.

>  * If an existing session crashed, is there a message like:
>    WARNING: Application 'gnome-shell.desktop' killed by signal ...
>    or:
>    WARNING: Application 'gnome-shell-wayland.desktop' killed by signal ...
>   
>    in the systemd journal?

Feb 10 11:54:15 eranr-800 gnome-session[1440]: (org.gnome.Software:1804): Gdk-WARNING **: org.gnome.Software: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Feb 10 11:54:15 eranr-800 gnome-session[1440]: (gnome-shell:1609): Gdk-WARNING **: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Feb 10 11:54:15 eranr-800 gnome-session[1440]: (abrt:1802): Gdk-WARNING **: abrt: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Feb 10 11:54:15 eranr-800 gnome-session[1440]: (evolution-alarm-notify:1797): Gdk-WARNING **: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Feb 10 11:54:15 eranr-800 gnome-session[1440]: xcb_connection_has_error() returned true
Feb 10 11:54:15 eranr-800 gnome-session[1440]: xcb_connection_has_error() returned true
Feb 10 11:54:15 eranr-800 gnome-session[1440]: WARNING: App 'gnome-shell.desktop' exited with code 1
Feb 10 11:54:15 eranr-800 gnome-session[1440]: gnome-session[1440]: WARNING: App 'gnome-shell.desktop' exited with code 1
Feb 10 11:54:15 eranr-800 gnome-session[1440]: (gnome-shell:10436): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to open display ':0'
Feb 10 11:54:15 eranr-800 gnome-session[1440]: (gnome-shell:10436): mutter-ERROR **: Unable to initialize Clutter.
Feb 10 11:54:15 eranr-800 gnome-session[1440]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
Feb 10 11:54:15 eranr-800 gnome-session[1440]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Feb 10 11:54:15 eranr-800 gnome-session[1440]: Unrecoverable failure in required component gnome-shell.desktop
Feb 10 11:54:15 eranr-800 gnome-session[1440]: gnome-session[1440]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
Feb 10 11:54:15 eranr-800 gnome-session[1440]: gnome-session[1440]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Feb 10 11:54:15 eranr-800 gnome-session[1440]: ** (gnome-session-failed:10476): WARNING **: Could not open X display
Feb 10 11:54:15 eranr-800 gnome-session[1440]: Unable to init server: Could not connect: Connection refused
Feb 10 11:54:15 eranr-800 gnome-session[1440]: ** (gnome-session-failed:10476): WARNING **: Cannot open display:
Feb 10 11:54:15 eranr-800 gnome-session[1440]: gnome-session[1440]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Feb 10 11:54:15 eranr-800 gnome-session[1440]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Feb 10 11:54:15 eranr-800 gnome-session[1440]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Feb 10 11:54:15 eranr-800 gnome-session[1440]: gnome-session[1440]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Feb 10 11:54:15 eranr-800 gnome-session[1440]: gnome-session[1440]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

>  * If an X session crashed, is there indication of the X server abnormally
> exiting in the systemd journal?

Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE)
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE) Backtrace:
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59a6a9]
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE) 1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7f6ebade4a4f]
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE) 2: ? (?+0x0) [0x7f6f35aaf8e3]
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE) 3: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0xd64c0) [0x7f6eb5b88680]
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE) 4: ? (?+0xd64c0) [0x7f6ebd3bf4c0]
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE)
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE) Segmentation fault at address 0x7f6f35aaf8e3
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE)
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: Fatal server error:
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE) Caught signal 11 (Segmentation fault). Server aborting
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE)
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE)
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: Please consult the Fedora Project support
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: at http://wiki.x.org
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: for help.
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE) Please also check the log file at "/home/eranr/.local/share/xorg/Xorg.0.log" for additional information.
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE)
Feb 10 11:54:14 eranr-800 /usr/libexec/gdm-x-session[1376]: (II) AIGLX: Suspending AIGLX clients for VT switch
Feb 10 11:54:15 eranr-800 /usr/libexec/gdm-x-session[1376]: (EE) Server terminated with error (1). Closing log file.

>  * Is your system using the provided Fedora graphics drivers, or with the
> NVIDIA proprietary drivers?

The system is using Intel's Graphic Drivers provided by Fedora.

I can't specifically reproduce, but it definitely seems to occur when I ask Chrome browser to do things (open new page, scrolling in a page, etc).

I am using a T440s with the Intel graphics.

When the crash occurs I get dumped back to the login screen.

If someone can suggest what logs to grab or any tweaks to make, let me know.

OK, I am having a similar problem to comment #40. Attachments incoming.

Created attachment 1140890 [details]
journalctl output around time of crash

This is the output of "journalctl" around the time of the crash, in reverse time order (newest message at top).

Created attachment 1140935 [details]
xorg.0.log from the crash

This is the xorg.0.log.old around the time of the crash. It doesn't provide much additional insight over the info in journalctl.

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.