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
Created attachment 841805 [details] File: backtrace
Created attachment 841806 [details] File: cgroup
Created attachment 841807 [details] File: core_backtrace
Created attachment 841808 [details] File: dso_list
Created attachment 841809 [details] File: environ
Created attachment 841810 [details] File: exploitable
Created attachment 841811 [details] File: limits
Created attachment 841813 [details] File: maps
Created attachment 841814 [details] File: open_fds
Created attachment 841815 [details] File: proc_pid_status
Created attachment 841816 [details] File: var_log_messages
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.
(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)?
*** Bug 1047873 has been marked as a duplicate of this bug. ***
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.