Bug 1652642 - gnome-logs segfault when executed as non-root
Summary: gnome-logs segfault when executed as non-root
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-logs
Version: 8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.2
Assignee: David King
QA Contact: Desktop QE
URL: https://faf.lab.eng.brq.redhat.com/fa...
Depends On: 1681613
Blocks: 1701002 1739559
TreeView+ depends on / blocked
Reported: 2018-11-22 14:13 UTC by Tomas Pelka
Modified: 2021-02-01 07:30 UTC (History)
8 users (show)

Fixed In Version: gnome-logs-3.28.5-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-02-01 07:30:43 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)
backtrace (35.72 KB, text/plain)
2018-11-22 14:15 UTC, Tomas Pelka
no flags Details
backtrace (29.97 KB, text/plain)
2019-02-12 08:15 UTC, Tomas Pelka
no flags Details

Description Tomas Pelka 2018-11-22 14:13:49 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: https://faf.lab.eng.brq.redhat.com/faf/reports/bthash/dc8c5cc9c38a090227b7e6d957dcba0880daa1b1/


Comment 1 Tomas Pelka 2018-11-22 14:15:59 UTC
Created attachment 1507977 [details]

Comment 2 Tomas Pelka 2018-11-22 14:17:42 UTC
Basically gnome-logs segfault when executed as non-root or as non-administrator user when clicking any of "filters" on left panel.

Comment 5 Michal Odehnal 2019-01-09 15:40:50 UTC
I am able to reproduce on root user also.

1. Click Search button or Ctrl+F.
2. Expand Search dialog.
3. Expand When dialog.
4. Click Previous boot.

There is no previous boot log, so perhaps the segfault is not for the same reason.

Comment 10 Tomas Pelka 2019-02-12 08:15:10 UTC
Created attachment 1533931 [details]

Still segfaulting.

Comment 20 RHEL Program Management 2021-02-01 07:30:43 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

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