Bug 1652642
Summary: | gnome-logs segfault when executed as non-root | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Tomas Pelka <tpelka> | ||||||
Component: | gnome-logs | Assignee: | David King <dking> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 8.0 | CC: | dking, jkoten, lmiksik, mclasen, mmcgrath, modehnal, tpopela, wchadwic | ||||||
Target Milestone: | rc | Keywords: | Triaged | ||||||
Target Release: | 8.2 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
URL: | https://faf.lab.eng.brq.redhat.com/faf/reports/bthash/dc8c5cc9c38a090227b7e6d957dcba0880daa1b1/ | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | gnome-logs-3.28.5-3.el8 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2021-02-01 07:30:43 UTC | Type: | Bug | ||||||
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: | 1681613 | ||||||||
Bug Blocks: | 1701002, 1739559 | ||||||||
Attachments: |
|
Description
Tomas Pelka
2018-11-22 14:13:49 UTC
Created attachment 1507977 [details]
backtrace
Basically gnome-logs segfault when executed as non-root or as non-administrator user when clicking any of "filters" on left panel. 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. Created attachment 1533931 [details]
backtrace
Still segfaulting.
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. |