Bug 1030948

Summary: [abrt] gnome-shell-3.8.4-14.el7: g_logv: Process /usr/bin/gnome-shell was killed by signal 5 (SIGTRAP)
Product: Red Hat Enterprise Linux 7 Reporter: Petr Sklenar <psklenar>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 7.0CC: amahdal, jscotka, mclasen, psklenar, vbenes
Target Milestone: rc   
Target Release: 7.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:109dea52b3b964f500edabe90e370531e814ed97
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 09:59:37 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:
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

Description Petr Sklenar 2013-11-15 11:40:10 UTC
Description of problem:


Version-Release number of selected component:
gnome-shell-3.8.4-14.el7

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell --mode=classic
crash_function: g_logv
executable:     /usr/bin/gnome-shell
kernel:         3.10.0-50.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_logv at /lib64/libglib-2.0.so.0
 #1 g_log at /lib64/libglib-2.0.so.0
 #2 g_wakeup_new at /lib64/libglib-2.0.so.0
 #3 g_main_context_new at /lib64/libglib-2.0.so.0
 #4 g_dbus_connection_send_message_with_reply_sync at /lib64/libgio-2.0.so.0
 #5 g_dbus_connection_call_sync_internal at /lib64/libgio-2.0.so.0
 #6 g_dbus_connection_call_sync at /lib64/libgio-2.0.so.0
 #7 ffi_call_unix64 at /lib64/libffi.so.6
 #8 ffi_call at /lib64/libffi.so.6
 #9 ?? at /lib64/libgjs.so.0

Comment 1 Petr Sklenar 2013-11-15 11:40:13 UTC
Created attachment 824490 [details]
File: backtrace

Comment 2 Petr Sklenar 2013-11-15 11:40:16 UTC
Created attachment 824491 [details]
File: cgroup

Comment 3 Petr Sklenar 2013-11-15 11:40:19 UTC
Created attachment 824492 [details]
File: core_backtrace

Comment 4 Petr Sklenar 2013-11-15 11:40:22 UTC
Created attachment 824493 [details]
File: dso_list

Comment 5 Petr Sklenar 2013-11-15 11:40:24 UTC
Created attachment 824494 [details]
File: environ

Comment 6 Petr Sklenar 2013-11-15 11:40:27 UTC
Created attachment 824495 [details]
File: limits

Comment 7 Petr Sklenar 2013-11-15 11:40:30 UTC
Created attachment 824496 [details]
File: maps

Comment 8 Petr Sklenar 2013-11-15 11:40:33 UTC
Created attachment 824497 [details]
File: open_fds

Comment 9 Petr Sklenar 2013-11-15 11:40:36 UTC
Created attachment 824498 [details]
File: proc_pid_status

Comment 10 Petr Sklenar 2013-11-15 11:40:39 UTC
Created attachment 824499 [details]
File: var_log_messages

Comment 11 Petr Sklenar 2013-11-15 11:56:31 UTC
what I did:
1, fresh installation of rhel7
2, after few minutes of running it got frozen
3, mouse works but I could click any icon in the gnome-shell
4, after +-5minutes ABRT wrote that catch a error and gnome starts working

Comment 13 Petr Sklenar 2013-11-15 12:51:08 UTC
journalctl shows:

Nov 15 12:42:40 localhost.localdomain gnome-session[2323]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
Nov 15 12:42:40 localhost.localdomain gnome-session[2323]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
Nov 15 12:42:40 localhost.localdomain gnome-session[2323]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
Nov 15 12:42:40 localhost.localdomain gnome-session[2323]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
Nov 15 12:42:41 localhost.localdomain gnome-session[2323]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.

Comment 14 Petr Sklenar 2013-11-15 12:52:55 UTC
ls -la /run/user/1000/dconf/user
-rw-------. 1 root root 2 Nov 15 12:38 /run/user/1000/dconf/user

Comment 15 Matthias Clasen 2013-12-11 18:40:54 UTC
how did you create the user - in anaconda, in firstboot, or in gnome-initial-setup ?

Comment 16 Petr Sklenar 2013-12-12 09:28:36 UTC
Hello,
user was created during installation, so in anaconda

Comment 17 Matthias Clasen 2014-01-08 03:22:58 UTC
This is an fd leak in the search provider loading code.
It should be fixed by 

https://git.gnome.org/browse/gnome-shell/commit/?h=gnome-3-10&id=a3236997bee6eb8b487c9e1d72379751da6ba0ae

Comment 18 Florian Müllner 2014-02-07 15:41:05 UTC
(In reply to Petr Sklenar from comment #11)
> what I did:
> 1, fresh installation of rhel7
> 2, after few minutes of running it got frozen
> 3, mouse works but I could click any icon in the gnome-shell
> 4, after +-5minutes ABRT wrote that catch a error and gnome starts working

Are you sure this is all you did? I have tried several times to reproduce this issue in a RHEL7 VM, without success so far.

Comment 19 Matthias Clasen 2014-02-25 18:22:23 UTC
*** Bug 1069638 has been marked as a duplicate of this bug. ***

Comment 20 Florian Müllner 2014-03-06 18:35:56 UTC
*** Bug 1065951 has been marked as a duplicate of this bug. ***

Comment 21 Florian Müllner 2014-03-06 18:54:10 UTC
(In reply to Florian Müllner from comment #18)
> Are you sure this is all you did? I have tried several times to reproduce
> this issue in a RHEL7 VM, without success so far.

I still haven't been able to reproduce. However as I haven't found similar reports for Fedora 20, let's assume that the rewrite of the loading code that happened for 3.10 fixed the issue ...

Comment 23 Ludek Smid 2014-06-13 09:59:37 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.