Bug 983142

Summary: [abrt] telepathy-gabble-0.17.4-1.fc19: dconf_shm_open: Process /usr/libexec/telepathy-gabble was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Lubo <lubomir.carik>
Component: selinux-policy-targetedAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Ben Levenson <benl>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bdpepple, dwalsh, misc, sander, shawn_q
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c1f4650e7a7aef418da5ddec2913f6bf965a717d
Fixed In Version: selinux-policy-3.12.1-74.2.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-12 01:53:53 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

Description Lubo 2013-07-10 15:34:28 UTC
Version-Release number of selected component:
telepathy-gabble-0.17.4-1.fc19

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-gabble
crash_function: dconf_shm_open
executable:     /usr/libexec/telepathy-gabble
kernel:         3.9.9-301.fc19.x86_64
runlevel:       N 5
uid:            1000
var_log_messages: Jul 10 17:31:47 sklca abrt[11184]: Saved core dump of pid 11181 (/usr/libexec/telepathy-gabble) to /var/tmp/abrt/ccpp-2013-07-10-17:31:47-11181 (19193856 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 dconf_shm_open at dconf-shm.c:87
 #3 dconf_engine_source_user_reopen at dconf-engine-source-user.c:76
 #4 dconf_engine_source_refresh at dconf-engine-source.c:57
 #5 dconf_engine_acquire_sources at dconf-engine.c:201
 #6 dconf_engine_get_state at dconf-engine.c:311
 #7 dconf_engine_watch_fast at dconf-engine.c:762
 #9 g_object_new_valist at gobject.c:1836
 #11 g_settings_new at gsettings.c:869
 #12 g_proxy_resolver_gnome_init at gproxyresolvergnome.c:157
 #13 g_type_create_instance at gtype.c:1917

Potential duplicate: bug 901552

Comment 1 Lubo 2013-07-10 15:34:35 UTC
Created attachment 771699 [details]
File: backtrace

Comment 2 Lubo 2013-07-10 15:34:38 UTC
Created attachment 771700 [details]
File: cgroup

Comment 3 Lubo 2013-07-10 15:34:41 UTC
Created attachment 771701 [details]
File: core_backtrace

Comment 4 Lubo 2013-07-10 15:34:44 UTC
Created attachment 771702 [details]
File: dso_list

Comment 5 Lubo 2013-07-10 15:34:47 UTC
Created attachment 771703 [details]
File: environ

Comment 6 Lubo 2013-07-10 15:34:50 UTC
Created attachment 771704 [details]
File: limits

Comment 7 Lubo 2013-07-10 15:34:54 UTC
Created attachment 771705 [details]
File: maps

Comment 8 Lubo 2013-07-10 15:34:58 UTC
Created attachment 771706 [details]
File: open_fds

Comment 9 Lubo 2013-07-10 15:35:01 UTC
Created attachment 771707 [details]
File: proc_pid_status

Comment 10 Michael S. 2013-08-04 18:46:00 UTC
juste starting empathy caused the crash

reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-gabble
crash_function: dconf_shm_open
executable:     /usr/libexec/telepathy-gabble
kernel:         3.10.4-300.fc19.x86_64
package:        telepathy-gabble-0.17.5-2.fc19
reason:         Process /usr/libexec/telepathy-gabble was killed by signal 5 (SIGTRAP)
runlevel:       N 5
uid:            500

Comment 11 Shawn Q 2013-08-14 15:07:29 UTC
Just opened the program, I'm not sure if it restarted itself, but it did open.

Something strange happened before this, though, I had performed fedora-upgrade to go from 18 to 19, following all the usual safety steps.  

There were a couple of orphaned rpm's, nothing serious though, netbeans, some old kernels.  I rebooted, everything was running great, no complaints in /var/log/messages during boot time, then maybe an hour later, environment completely locked up.  

I was able to hit Num Lock on the keyboard and see the light turn on and off, but switching console via CTRL-ALT-F2 / etc. did not work, and SysRq combo "REISUB" did not do anything.  

Had to resort to a hard power cycle, and during boot time I'm noticing a couple of strange entries in /var/log/messages:


Before issue:

Aug 14 10:33:32 node159 dbus[487]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Aug 14 10:33:32 node159 dbus-daemon[487]: no kernel backlight interface found
Aug 14 10:33:32 node159 dbus-daemon[487]: dbus[487]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Aug 14 10:33:32 node159 dbus[487]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Aug 14 10:38:19 node159 dbus-daemon[487]: dbus[487]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Aug 14 10:38:19 node159 dbus-daemon[487]: no kernel backlight interface found
Aug 14 10:38:19 node159 dbus-daemon[487]: dbus[487]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Aug 14 10:38:19 node159 dbus[487]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Aug 14 10:38:19 node159 dbus[487]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Aug 14 10:42:58 node159 systemd[1]: Starting Getty on tty2...
\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00Aug 14 10:45:31 node159 rsyslogd: [origin software="rsyslogd" swVersion="7.2.6" x-pid="485" x-info="http://www.rsyslog.com"] start

Note the \00\00\00 in the log here, these are invalid special characters during th etime the system locked up.

After boot:

Aug 14 10:46:26 node159 dbus[486]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Aug 14 10:46:26 node159 dbus[486]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.nm-dispatcher.service' for details.
Aug 14 10:46:26 node159 NetworkManager[589]: <warn> Dispatcher failed: (32) Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.nm-dispatcher.service' for details.

Looking at systemctl, this nm-dispatcher service is legitimately missing...not sure what happened with it.

Lastly, opening something as simple as gedit via konsole shows:

(gedit:1598): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.

I know this isn't specific to telepathy, I think, but in case it is and there's bigger problems as a source, I felt you should know.


reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-gabble
crash_function: dconf_shm_open
executable:     /usr/libexec/telepathy-gabble
kernel:         3.10.5-201.fc19.x86_64
package:        telepathy-gabble-0.17.5-2.fc19
reason:         Process /usr/libexec/telepathy-gabble was killed by signal 5 (SIGTRAP)
runlevel:       N 5
uid:            1000

Comment 12 Michael S. 2013-08-28 23:26:00 UTC
Ok, I finally found the problem :

type=AVC msg=audit(1377732106.491:894): avc:  denied  { getattr } for  pid=23892 comm="telepathy-gabbl" path="/run/user" dev="tmpfs" ino=15266 scontext=staff_u:staff_r:telepathy_gabble_t:s0-s0:c0.c1023 tcontext=system_u:object_r:user_tmp_t:s0 tclass=dir

running empathy with a confined user break , with the message seen before.

using setenfoce 0 make it work, and semodule -DB show me this avc.

Since the error is basically gabble cannot opening /run/user, i assume that either :
- a access that should be given to telepathy_gabble_t, 
- a bug in dconf.

Assigning to selinux, as I think the access is kinda needed.

Comment 13 Daniel Walsh 2013-08-29 12:29:23 UTC
575e5d0cca89268c98ee5132441e2192d7059409 fixes this in git.

Comment 14 Miroslav Grepl 2013-09-02 13:59:24 UTC
Back ported.

Comment 15 Fedora Update System 2013-09-09 07:54:42 UTC
selinux-policy-3.12.1-74.2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-74.2.fc19

Comment 16 Fedora Update System 2013-09-09 23:57:39 UTC
Package selinux-policy-3.12.1-74.2.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-74.2.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-16231/selinux-policy-3.12.1-74.2.fc19
then log in and leave karma (feedback).

Comment 17 Fedora Update System 2013-09-12 01:53:53 UTC
selinux-policy-3.12.1-74.2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.