Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (2 frames)
#0 XScreenCount at Macros.c:108
#1 panel_application_load at panel-application.c:1206
Potential duplicate: bug 831563
Created attachment 917641 [details]
Created attachment 917642 [details]
Created attachment 917643 [details]
Created attachment 917644 [details]
Created attachment 917645 [details]
Created attachment 917646 [details]
Created attachment 917647 [details]
Created attachment 917648 [details]
Created attachment 917649 [details]
Created attachment 917650 [details]
Created attachment 917651 [details]
What were you doing when this happened?
Can you duplicate it?
(In reply to Kevin Fenzi from comment #12)
> What were you doing when this happened?
> Can you duplicate it?
I've walked through the scenarios that I think may have caused it, and none have recreated the segfault.
I normally run a vncserver with xfce, since that windowing system doesn't require accelerated graphics. Unfortunately, I cannot get systemd to start the vncserver, so I start it by hand once the system comes up.
I occasionally try to get systemd to bring up the vncserver, but I've not been successful, and I've not spent enough time on it to track down the problem. I may have tried using systemd to bring up the vncserver at that time, but I just tried to do that, and no segfault.
I also thought that I could have accessed the system via vnc after the xauth update on the 9th of July, but the time is from after I would have rebooted the system due to a kernel update on the 12th.
We haven't had a kernel update since then, and I've rebooted the box (and used xfce) with no issues.
In short, I've got no good idea. I'll think about this some more and see if there are other triggers that could have caused a segfault with the xfce panel.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version'
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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.