Bug 751922
Summary: | [abrt] tracker-0.12.7-1.fc16: MemStream::getChar: Process /usr/libexec/tracker-extract was killed by signal 11 (SIGSEGV) | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | luavi1 <tiktokoptik> | ||||||||||||
Component: | tracker | Assignee: | Deji Akingunola <dakingun> | ||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 16 | CC: | bobpoljakov, bzf, dakingun, deanrbennett, hpfeil, jcs, johnmargaritopoulos, kaf.laarous, martin.lange.berlin, mishu, mkasik, npajkovs, pavol.ondercin, rtmetz92, s.ali.najafian, ssssam, tcfxfzoi | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | x86_64 | ||||||||||||||
OS: | Unspecified | ||||||||||||||
Whiteboard: | abrt_hash:985128c9e2c6d4177fa5445a916fb6bd9a49e49e | ||||||||||||||
Fixed In Version: | tracker-0.12.8-2.fc16 | Doc Type: | Bug Fix | ||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2011-12-14 23:38:50 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
luavi1
2011-11-08 03:31:11 UTC
Created attachment 532180 [details]
File: dso_list
Created attachment 532181 [details]
File: smolt_data
Created attachment 532182 [details]
File: maps
Created attachment 532183 [details]
File: backtrace
Package: tracker-0.12.7-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- It is happend after a reboot Package: tracker-0.12.4-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- This appeared as soon as ccpp-200-11-08-06:30_55-2005 started sending its core dump for analysis. Package: tracker-0.12.4-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Started adding additional info in dump ccpp-2011-11-08-06:30:55-2005 This look like a bug in poppler-glib, re-assigning. @ luarvik1; Can you possibly attach (or make available) the file causing this crash? "file:///home/margus/Documents/unsorted-old/documents_backup/Misc.%20Literature/Consciousness%20Books%20Collection/John%20Searle%20-%20Mind,%20A%20Brief%20Introduction%20(2004).pdf" (In reply to comment #7) > Package: tracker-0.12.4-2.fc16 > Architecture: x86_64 > OS Release: Fedora release 16 (Verne) > > Comment > ----- > Started adding additional info in dump ccpp-2011-11-08-06:30:55-2005 Removed all new tracker entries from the Application Autostart list. Methinks tracker was trying to track an nfs mount that I use for HPC before it was mounted. (That project is on hold until I figure out how openmpi got so misconfigured that it can't run jobs sent from a slackware box. Will try creating soft links in /usr/bin for /usr/lib64/openmpi/bin/*, but I digress.) This and my abrt on Bug 734011 might be caused by the fact that in XFCE4, the Thunar launcher in my bottom panel had "Use startup notification" checked. After I unchecked that option, one instance of Thunar pops up relatively instantly. Before, it would take 10-20 seconds before the first instance appeared followed by a second instance a short time later. Tips & Tricks: Do not check "Use startup notification" in a Thunar launcher. (In reply to comment #10) > This and my abrt on Bug 734011 might be caused by the fact that in XFCE4, the > Thunar launcher in my bottom panel had "Use startup notification" checked. > After I unchecked that option, one instance of Thunar pops up relatively > instantly. Before, it would take 10-20 seconds before the first instance > appeared followed by a second instance a short time later. > Tips & Tricks: Do not check "Use startup notification" in a Thunar launcher. Red Herring. Not related to startup notification. Methinks there's a bit of nonsense going on with gvfsd. Click thunar launch icon. Two new processes appear while waiting for the first window (15-20 sec): /usr/libexec/gvfsd-network --spawner :1.5 /org/gtk/gvfs/exec_spaw/1 /usr/libexec/gvfsd-smb-browse --spawner :1.5 /org/gtk/gvfs/exec_spaw/2 After the first window appears, two new processes appear in the process list: /usr/libexec/gvfsd-network --spawner :1.5 /org/gtk/gvfs/exec_spaw/3 usr/lib64/tumbler-1/tumblerd A short time later, the second thunar window appears along with a new process: /usr/libexec/gvfsd-dnssd --spawner :1.5 /org/gtk/gvfs/exec_spaw/4 When I close the second thunar window, the gvfsd-smb-browse process and the second gvfsd-network process go away, leaving exec_spaw/1, tumblerd and exec_spaw/4 Sorry, abrt appended my tracker issue here. Should I open a new bug for thunar vs gvfs? *** Bug 756596 has been marked as a duplicate of this bug. *** *** Bug 757323 has been marked as a duplicate of this bug. *** *** Bug 757326 has been marked as a duplicate of this bug. *** *** Bug 757373 has been marked as a duplicate of this bug. *** *** Bug 757467 has been marked as a duplicate of this bug. *** Hi, I'm returning this bug back to tracker. Tracker calls "poppler_document_new_from_data (contents, len, NULL, &error)" with contents = 0xffffffffffffffff. It is probably because the previous "contents = mmap()" failed and returned MAP_FAILED ( = (void *) -1). Regards Marek Created attachment 538504 [details]
check result of mmap
This patch should prevent tracker from crash.
Package: tracker-0.12.4-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- .......... Package: tracker-0.12.4-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- ............ *** Bug 759431 has been marked as a duplicate of this bug. *** *** Bug 759728 has been marked as a duplicate of this bug. *** *** Bug 759878 has been marked as a duplicate of this bug. *** *** Bug 757643 has been marked as a duplicate of this bug. *** *** Bug 758515 has been marked as a duplicate of this bug. *** tracker-0.12.8-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/tracker-0.12.8-1.fc16 Package tracker-0.12.8-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing tracker-0.12.8-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-16804/tracker-0.12.8-1.fc16 then log in and leave karma (feedback). *** Bug 760670 has been marked as a duplicate of this bug. *** *** Bug 760900 has been marked as a duplicate of this bug. *** *** Bug 761496 has been marked as a duplicate of this bug. *** *** Bug 765761 has been marked as a duplicate of this bug. *** *** Bug 766210 has been marked as a duplicate of this bug. *** tracker-0.12.8-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. I have pushed this patch to upstream master: http://git.gnome.org/browse/tracker/commit/?id=008677280d32b6db56483832b143760888c91ad4 It should be fixed in 0.14.3 Thanks! |