Bug 1646345
Summary: | tracker-miner-fs killed by SIGABRT when connected from remote machine with XDMCP | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | jigar <jraising> | ||||
Component: | tracker | Assignee: | Carlos Garnacho <cgarnach> | ||||
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 7.5 | CC: | cww, mclasen, tpelka, yuokada | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | tracker-1.10.5-7.el7 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-03-31 19:39:00 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: | |||||||
Bug Blocks: | 1727111 | ||||||
Attachments: |
|
Description
jigar
2018-11-05 12:33:38 UTC
Created attachment 1617101 [details]
Log from valgrind while reproducing the bug under RHEL 7.6
TEST SETUP 1
Distro: RHEL 7.6
Component version: tracker-1.10.5-6.el7
TEST PROCEDURE 1
1. Create a file with invalid UTF-8 name:
# touch ~/aaa$'\363'
2. Stop the indexing from tracker:
# tracker daemon --terminate
3. Install a tool for checking memory leaks and corruption:
# yum install -y valgrind
4. Start valgrind:
# valgrind /usr/libexec/tracker-miner-fs
5. Open another terminal.
6. Trigger the memory corruption:
# touch ~/bbb$'\363'
TEST SETUP 2 Distro: RHEL-7.8-20190912.3 Component version: tracker-1.10.5-8.el7 TEST PROCEDURE 2 Repeat TEST PROCEDURE 1 (comment #5). RESULT 2 The bug does NOT appear. OUTCOME Upgrading component: tracker from: 1.10.5-6.el7 to: 1.10.5-8.el7 has fixed the bug. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:1021 |