Red Hat Bugzilla – Bug 972436
[abrt] midori-0.4.7-2.fc18: elf_machine_rel: Process /usr/bin/midori was killed by signal 7 (SIGBUS)
Last modified: 2014-02-05 18:11:20 EST
Description of problem:
On startup either from terminal or from applications menu of XFCE. Occurs every time.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (7 frames)
#0 elf_machine_rel at ../sysdeps/i386/dl-machine.h:339
#1 elf_dynamic_do_Rel at do-rel.h:145
#2 _dl_relocate_object at dl-reloc.c:295
#3 dl_main at rtld.c:2299
#4 _dl_sysdep_start at ../elf/dl-sysdep.c:242
#5 _dl_start_final at rtld.c:336
#6 _dl_start at rtld.c:562
Created attachment 758734 [details]
Created attachment 758735 [details]
Created attachment 758736 [details]
Created attachment 758737 [details]
Created attachment 758738 [details]
Created attachment 758739 [details]
Created attachment 758740 [details]
Created attachment 758741 [details]
Created attachment 758742 [details]
Created attachment 758743 [details]
Created attachment 758744 [details]
Something seems odd with your dynamic library loading.
Can you attach the contents of:
and also the output of:
rpm -V libuuid
Thanks for looking into this;
/etc/ld.so.preload doesn't exist (ld.so.conf and ls.so.cache do exist).
rpm -V libuuid doesn't return anything either as root or as user.
Bit more searching:
#yum install libuuid returns:
Package libuuid-2.22.2-6.fc18.i686 already installed and latest version
and locate libuuid returns
if that helps at all.
This is very odd.
Can you try the scratch build in:
and see if the same problem occurs?
I've deinstalled the old version and installed this version, and the same error occurs; however when the error is flagged in the bug reporting tool within xfce, it states that the error is from the older 0.4x version (I don't know whether this is significant).
To reiterate - I yum unistalled midori, rpm -i the new package that you pointed me to and then ran it.
As it has been suggested that it might be due to something odd re dynamic library linking I might download FC19 and see if it works in that version.
Thanks for your help
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.
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 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.