Red Hat Bugzilla – Bug 961082
[abrt] Thunar-1.6.2-1.fc18: _dbus_header_get_byte_order: Process /usr/bin/thunar was killed by signal 11 (SIGSEGV)
Last modified: 2014-02-05 18:09:21 EST
Version-Release number of selected component:
cmdline: /bin/Thunar file:///home/pawel/Pulpit/film
Thread no. 1 (10 frames)
#0 _dbus_header_get_byte_order at dbus-marshal-header.c:178
#1 _dbus_header_get_field_basic at dbus-marshal-header.c:1370
#2 dbus_message_get_reply_serial at dbus-message.c:1091
#3 _dbus_connection_queue_received_message_link at dbus-connection.c:501
#4 _dbus_transport_queue_messages at dbus-transport.c:1157
#5 do_reading at dbus-transport-socket.c:851
#7 socket_handle_watch at dbus-transport-socket.c:932
#8 _dbus_transport_handle_watch at dbus-transport.c:885
#9 _dbus_connection_handle_watch at dbus-connection.c:1515
#10 dbus_watch_handle at dbus-watch.c:700
Created attachment 745337 [details]
Created attachment 745338 [details]
Created attachment 745339 [details]
Created attachment 745340 [details]
Created attachment 745341 [details]
Created attachment 745342 [details]
Created attachment 745343 [details]
Created attachment 745344 [details]
Created attachment 745345 [details]
Created attachment 745346 [details]
What were you doing when this happened?
Can you duplicate it?
My actions were:
1) I downloaded some zipped file.
2) I unzipped it by command from ?popup? menu.
3) I changed the name of unzipped file (I'm not sure now if I did it before the crash).
4) I try deleted the zipped file.
Then Thunar crashed but the zipped file was deleted.
I wasn't able to duplicate that crash.
There is one more thing.
During my actions, I described in my comment (no. 12), I was downloading an another file to the same directory.
Can you try the update in updates-testing?
'yum --enablerepo=updates-testing update Thunar'
I did the update and repeated my actions but I wasn't able to duplicate that crash.
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.