Description of problem: When the environment variable LD_LIBRARY_PATH is set to a directory, that does not exist, brasero segfaults. Version-Release number of selected component (if applicable): brasero-3.4.1-1.fc17.x86_64 How reproducible: set environment variable to something not existing e.g. /usr/bla Steps to Reproduce: 1. in a bash or sh do: export LD_LIBRARY_PATH=/usr/bla 2. then: brasero Actual results: in the shell, one just gets the output: Segmentation fault Expected results: brasero starts and the runtime linker does not care about the senseless LD_LIBRARY_PATH setting Additional info: I guess the following bugs are just the same: 859729 834269 814999 It might as well be an ld.so.1 bug Probably it is sufficient to just re-link brasero. the last lines of strace brasero: open("/usr/lib64/tls/libdvdcss.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libdvdcss.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/bla/tls/x86_64/libdvdcss.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/bla/tls/x86_64", 0x7ffff3581a50) = -1 ENOENT (No such file or directory) open("/usr/bla/tls/libdvdcss.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/bla/tls", 0x7ffff3581a50) = -1 ENOENT (No such file or directory) open("/usr/bla/x86_64/libdvdcss.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/bla/x86_64", 0x7ffff3581a50) = -1 ENOENT (No such file or directory) open("/usr/bla/libdvdcss.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/bla", 0x7ffff3581a50) = -1 ENOENT (No such file or directory) --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0x7fc79c0f9db0} --- +++ killed by SIGSEGV +++ Segmentation fault
The 32 bit version (i386 package) is not affected. And it does not help to simply rebuild from the source RPM.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.