Bug 1046601

Summary: [abrt] pcmanfm: elf_machine_rela(): pcmanfm killed by SIGSEGV
Product: [Fedora] Fedora Reporter: luismokos <maiden_the_iron>
Component: glibcAssignee: Carlos O'Donell <codonell>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: codonell, fweimer, jakub, law, maiden_the_iron, mtasaka, pfrankli, spoyarek
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7a675da37140189cdf6ebbca5a1a210fa83d3398
Whiteboard: abrt_hash:0b168ab443d47cc3ead84ce39eac23104ea149ab
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-03 04:57:13 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 Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description luismokos 2013-12-26 09:43:58 UTC 
Version-Release number of selected component:
pcmanfm-1.1.2-3.D20130830gitfc8adaab77.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        pcmanfm --desktop --profile LXDE
crash_function: elf_machine_rela
executable:     /usr/bin/pcmanfm
kernel:         3.12.5-302.fc20.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 elf_machine_rela at ../sysdeps/i386/dl-machine.h:502
 #1 elf_dynamic_do_Rela at do-rel.h:137
 #2 _dl_relocate_object at dl-reloc.c:294
 #3 dl_main at rtld.c:2196
 #4 _dl_sysdep_start at ../elf/dl-sysdep.c:249
 #5 _dl_start_final at rtld.c:329
 #6 _dl_start at rtld.c:555
Comment 1 luismokos 2013-12-26 09:44:19 UTC 
Created attachment 841805 [details]
File: backtrace
Comment 2 luismokos 2013-12-26 09:44:21 UTC 
Created attachment 841806 [details]
File: cgroup
Comment 3 luismokos 2013-12-26 09:44:28 UTC 
Created attachment 841807 [details]
File: core_backtrace
Comment 4 luismokos 2013-12-26 09:44:35 UTC 
Created attachment 841808 [details]
File: dso_list
Comment 5 luismokos 2013-12-26 09:44:39 UTC 
Created attachment 841809 [details]
File: environ
Comment 6 luismokos 2013-12-26 09:44:46 UTC 
Created attachment 841810 [details]
File: exploitable
Comment 7 luismokos 2013-12-26 09:44:53 UTC 
Created attachment 841811 [details]
File: limits
Comment 8 luismokos 2013-12-26 09:44:58 UTC 
Created attachment 841813 [details]
File: maps
Comment 9 luismokos 2013-12-26 09:45:05 UTC 
Created attachment 841814 [details]
File: open_fds
Comment 10 luismokos 2013-12-26 09:45:10 UTC 
Created attachment 841815 [details]
File: proc_pid_status
Comment 11 luismokos 2013-12-26 09:45:16 UTC 
Created attachment 841816 [details]
File: var_log_messages
Comment 12 Mamoru TASAKA 2013-12-26 12:42:35 UTC 
Looks like this issue happened at the stage of very early startup, before program "starts", and perhaps machine dependent issue(?)

Once switching to glibc to ask for help.
Comment 13 Carlos O'Donell 2013-12-27 15:55:18 UTC 
(In reply to Mamoru TASAKA from comment #12)
> Looks like this issue happened at the stage of very early startup, before
> program "starts", and perhaps machine dependent issue(?)
> 
> Once switching to glibc to ask for help.

The relocation being processed is R_386_PC32 and is within the proprietary nvidia blob /usr/lib/nvidia-304xx/libnvidia-glcore.so.304.117. The fact that this is in NVIDIA's proprietary blob makes it difficult analyze exactly why the relocations may or may not be wrong and how they relate to original source code (which we don't have).

However, the relocation interface is fixed and part of the ABI so it should be possible to analyze the DSO and see if anything is wrong. However, if something *were* wrong we couldn't do anything about it except perhaps consider a workaround in glibc (as long as such a workaround didn't impact all users).

Is this reproducible? Or is it random? Can we get a core file? Can we get a copy of the nvidia DSO attached to this issue (if the license allows it)?
Comment 14 Carlos O'Donell 2014-01-02 14:49:20 UTC 
*** Bug 1047873 has been marked as a duplicate of this bug. ***
Comment 15 Fedora End Of Life 2015-05-29 10:10:25 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.