Red Hat Bugzilla – Bug 986868
[abrt] Thunar-1.6.3-1.fc19: gtk_tray_icon_manager_filter: Process /usr/bin/thunar was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-18 09:01:36 EST
Version-Release number of selected component:
cmdline: Thunar --daemon
runlevel: N 5
Thread no. 1 (5 frames)
#0 gtk_tray_icon_manager_filter at gtktrayicon-x11.c:470
#1 gdk_event_apply_filters at gdkevents-x11.c:356
#2 gdk_event_translate at gdkevents-x11.c:946
#3 _gdk_events_queue at gdkevents-x11.c:2336
#9 gtk_main at gtkmain.c:1257
Created attachment 776818 [details]
Created attachment 776819 [details]
Created attachment 776820 [details]
Created attachment 776821 [details]
Created attachment 776822 [details]
Created attachment 776823 [details]
Created attachment 776824 [details]
Created attachment 776825 [details]
Created attachment 776826 [details]
Created attachment 776827 [details]
What were you doing when this happened?
Can you duplicate it?
I just opened Thunar and it crashed before even displaying its window.
Does it crash everytime you try and open it? Or the crash was a one time thing?
It happened only once so far. I'll report if/when it happens again.
Ok, it happened many times more and now I know how to reproduce it. It seems it happens when I'm running AwesomeWM.
Steps to reproduce:
1) run awesome as your window manager
2) open Thunar
3) open new tab in Thunar with Ctrl-T
4) do some copying operation that displays the "File Operation Progress" popup and a tray icon (this is required, the bug doesn't appear when the operation is quick and without the popup/tray icon)
5) wait for the operation to finish or just cancel it
6) try switching to the other Thunar tab - crash should happen
I tried the above procedure under XFCE4 and it works fine so it seems there is something wrong on the line between Awesome's tray implementation and Thunar's use of a tray.
I asked the awesome maintainer to look at this, and he said he was unaware of any issues around this. ;(
Not sure where to go from here. We could try asking upstream awesome folks, or perhaps ask Thunar upstream folks if they can make anything of it.
Any news from this bug?
It is affecting me also, using Thunar with AwesomeWM after an operation creating a thunar tray icon.
Could one of you file a awesomewm upstream bug? They might have seen this before?
I reported the bug on the awesomewm site.
For the awesomewm bug report:
Also reported to thunar team:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.