Red Hat Bugzilla – Bug 608912
[abrt] crash in Thunar-1.0.2-1.fc13: Process /usr/bin/Thunar was killed by signal 11 (SIGSEGV)
Last modified: 2011-06-27 15:06:27 EDT
abrt 1.1.1 detected a crash.
reason: Process /usr/bin/Thunar was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: right click in a image
BFD: Warning: /var/cache/abrt/ccpp-1277761347-2353/coredump is truncated: expected core file size >= 68857856, found: 61440.
[New Thread 2353]
[New Thread 24263]
[New Thread 25721]
[New Thread 25722]
[New Thread 25724]
[New Thread 25725]
Failed to read a valid object file image from memory.
Core was generated by `/usr/bin/Thunar --daemon'.
Program terminated with signal 11, Segmentation fault.
#0 0x008d4398 in ?? ()
Thread 6 (Thread 25725):
Cannot access memory at address 0xb0294fa0
Thread 5 (Thread 25724):
Cannot access memory at address 0xb23fe038
Thread 4 (Thread 25722):
Cannot access memory at address 0xb0c96038
Thread 3 (Thread 25721):
Cannot access memory at address 0xb2dff038
Thread 2 (Thread 24263):
Cannot access memory at address 0xb3923140
Thread 1 (Thread 2353):
Cannot access memory at address 0xbfc5a2cc
From To Syms Read Shared Object Library
0x001f2830 0x0020a37f Yes /lib/ld-linux.so.2
No symbol "__abort_msg" in current context.
No symbol "__glib_assert_msg" in current context.
eax 0x822a71 8530545
ecx 0x822a71 8530545
edx 0xd7aa71 14133873
ebx 0x6a3248 6959688
esp 0xbfc5a2cc 0xbfc5a2cc
ebp 0xbfc5a2e8 0xbfc5a2e8
esi 0xa 10
edi 0xba6 2982
eip 0x8d4398 0x8d4398
eflags 0x210216 [ PF AF IF RF ID ]
cs 0x73 115
ss 0x7b 123
ds 0x7b 123
es 0x7b 123
fs 0x0 0
gs 0x33 51
No function contains program counter for selected frame.
Created attachment 427517 [details]
Unfortunately, this backtrace is not very useful. ;(
What were you doing when this happened? Can you duplicate it?
Do you have thunar-vcs-plugin installed? Try removing that and see if it happens again?
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 '13'.
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 13'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 13 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.