Bug 1646374 - abrt-applet not launching and not intercepting crashes on Fedora 29
Summary: abrt-applet not launching and not intercepting crashes on Fedora 29
Keywords:
Status: CLOSED DUPLICATE of bug 1641456
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 29
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-05 13:30 UTC by Akarshan Biswas
Modified: 2019-01-19 13:49 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-05 13:46:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Akarshan Biswas 2018-11-05 13:30:34 UTC
Description of problem:
Abrt applet is not lauching throwing some permission error.

Version-Release number of selected component (if applicable):
2.11.0.1.fc29

How reproducible:
Everytime.

Steps to Reproduce:
1. Boot Fedora as normal
2. Do a test using sleep command and issuing a SIGSEGV
3.

Actual results:
Abrt doesn't show notifications and doesn't intercept the crash. Infact abrt-applet is not running at all.

Expected results:
It should throw a notification as normal.

Additional info:
journalctl -xb | grep abrt-applet shows this error:
dbus-daemon[689]: [system] Activating service name='org.freedesktop.problems' requested by ':1.422' (uid=1000 pid=2090 comm="abrt-applet " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023") (using servicehelper)
abrt-applet.desktop[2090]: abrt-applet: Can't connect to system DBus: Error calling StartServiceByName for org.freedesktop.problems: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.freedesktop.problems: Permission denied

Tested and confirmed on two systems.

To be tested:
Booting the computer with setenforce 0 to see if selinux is blocking abrt-applet or not. Will add a comment if I find anything.

Comment 1 Martin Kutlak 2018-11-05 13:46:57 UTC
Thank you for your report!

The problem is caused by a bug in dbus.

*** This bug has been marked as a duplicate of bug 1641456 ***


Note You need to log in before you can comment on or make changes to this bug.