Bug 1202943

Summary: [abrt] gnome-shell: g_type_check_instance(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: iliketurtlesbro
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: ajax, autarch, awilliam, bnocera, danloomis47, danofsatx, ezwen-redhatbugzilla, fmuellner, guillaumepoiriermorency, hugo.caille, iliketurtlesbro, iscjar, ji.cerny, lray+redhatbugzilla, luya, matteo, Michael-G, mikhail.v.gavrilov, otaylor, robatino, trevor.davenport
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/61e931dcb0cd97d2b36b65b5bf232c02de53390f
Whiteboard: RejectedBlocker abrt_hash:ddf8d7afb344722f5ba4ad2b5fb33790b551fa07
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-10 22:52:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1214119    
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
dmesg gnome-shell segfault
none
journalctl | grep -i portal
none
journal containing relevant issue none

Description iliketurtlesbro 2015-03-17 18:41:10 UTC
Description of problem:
gnome shell crashes randomly during use and usually logs right back into an empty desktop

Version-Release number of selected component:
gnome-shell-3.15.91-1.fc22

Additional info:
reporter:       libreport-2.4.0
backtrace_rating: 4
cmdline:        gnome-shell --mode=gdm --wayland --display-server
crash_function: g_type_check_instance
executable:     /usr/bin/gnome-shell
kernel:         4.0.0-0.rc2.git0.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            42

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 g_type_check_instance at gtype.c:4132
 #1 g_signal_handler_disconnect at gsignal.c:2556
 #2 check_connectivity_cb at nm-client.c:1497
 #3 complete_pending_call_and_unlock at dbus-connection.c:2331
 #10 meta_run at core/main.c:437

Comment 1 iliketurtlesbro 2015-03-17 18:41:18 UTC
Created attachment 1002894 [details]
File: backtrace

Comment 2 iliketurtlesbro 2015-03-17 18:41:20 UTC
Created attachment 1002895 [details]
File: cgroup

Comment 3 iliketurtlesbro 2015-03-17 18:41:22 UTC
Created attachment 1002896 [details]
File: core_backtrace

Comment 4 iliketurtlesbro 2015-03-17 18:41:23 UTC
Created attachment 1002897 [details]
File: dso_list

Comment 5 iliketurtlesbro 2015-03-17 18:41:24 UTC
Created attachment 1002898 [details]
File: environ

Comment 6 iliketurtlesbro 2015-03-17 18:41:25 UTC
Created attachment 1002899 [details]
File: limits

Comment 7 iliketurtlesbro 2015-03-17 18:41:29 UTC
Created attachment 1002900 [details]
File: maps

Comment 8 iliketurtlesbro 2015-03-17 18:41:30 UTC
Created attachment 1002901 [details]
File: open_fds

Comment 9 iliketurtlesbro 2015-03-17 18:41:34 UTC
Created attachment 1002902 [details]
File: proc_pid_status

Comment 10 iliketurtlesbro 2015-03-17 18:41:36 UTC
Created attachment 1002903 [details]
File: var_log_messages

Comment 11 Adam Williamson 2015-03-26 03:26:22 UTC
Another user experienced a similar problem:

Happened multiple times this afternoon; seems to be related to the captive portal login screen, which has been popping up today due to a Fedora infrastructure issue.

reporter:       libreport-2.5.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: g_type_check_instance
executable:     /usr/bin/gnome-shell
global_pid:     369
kernel:         4.0.0-0.rc3.git2.2.fc23.x86_64
package:        gnome-shell-3.15.92-2.fc22
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1001

Comment 12 Luya Tshimbalanga 2015-04-01 03:45:56 UTC
Created attachment 1009441 [details]
dmesg gnome-shell segfault

dmesg shows segfault each times captive portable popped out within Gnome on Wayland.

Comment 13 Luya Tshimbalanga 2015-04-10 23:44:33 UTC
Created attachment 1013309 [details]
journalctl | grep -i portal

Hit his issues while attempting to use a public network.

Comment 14 Fedora Blocker Bugs Application 2015-04-28 22:25:38 UTC
Proposed as a Blocker for 22-final by Fedora user luya using the blocker tracking app because:

 Gnome Shell session on both X and Wayland crashed frequently when captive-portal is in action attempting of access to a public network from say internet cafe. All test are done on all F22 version from alpha to beta with same reason. It will be great to fix that problem before the release.

Comment 15 Luya Tshimbalanga 2015-04-28 23:06:18 UTC
Created attachment 1019910 [details]
journal containing relevant issue

Updated report

Comment 16 Dan Mossor [danofsatx] 2015-05-04 16:53:46 UTC
Discussed at the 2015-05-04 blocker review meeting.[0] Voted as RejectedBlocker AcceptedFreezeException.

RejectedBlocker AcceptedFreezeException - if GNOME is crashing whenever it sees a captive portal that's bad, but probably possible to deal with, can be fixed for installed systems with an update, and we suspect lives aren't commonly used in this scenario. We can always repropose if it turns out we made a bad call, however.

[0] http://meetbot.fedoraproject.org/meetbot/fedora-blocker-review/2015-05-04/f22-blocker-review.2015-05-04-16.00.log.txt

Comment 17 Dan Loomis 2015-05-15 03:30:19 UTC
I correlated the failures on my system to when I connected to a Starbucks using  Google Internet.   I went there today and did not experience this failure.  This never happened at other WiFi locations including a Starbucks that uses attwifi.   Was there a recent fix or did Google clean up something at their end.

Comment 18 Luya Tshimbalanga 2015-05-15 16:03:00 UTC
It looks like the recent update of NetworkManager solves the issue. Using access of public network like Starbucks no longer crash Gnome session.

NetworkManager.x86_64                            1:1.0.2-1.fc22  @System

Comment 19 Adam Williamson 2015-06-10 22:52:33 UTC
Clearing F22 accepted / nominated freeze exception status as F22 has shipped, per https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers . You may nominate as an Alpha, Beta or Final freeze exception for F23 if desired using the web application - https://qa.fedoraproject.org/blockerbugs/propose_bug (though it is not currently set up for F23) - or by marking the bug as blocking AlphaFreezeException, BetaFreezeException, or FinalFreezeException.

Also per #c17 and #c18 I'm gonna mark this as closed, re-open if there still seems to be a problem.