Red Hat Bugzilla – Bug 862912
[abrt] xfce4-session-4.8.3-1.fc17: g_logv: Process /usr/bin/xfce4-session was killed by signal 5 (SIGTRAP)
Last modified: 2013-08-01 13:34:03 EDT
Version-Release number of selected component:
libreport version: 2.0.14
:Thread no. 1 (2 frames)
: #0 g_logv at gmessages.h:101
: #2 xfsm_dbus_init at main.c:182
Created attachment 621152 [details]
Created attachment 621153 [details]
Created attachment 621154 [details]
Created attachment 621155 [details]
Created attachment 621156 [details]
Created attachment 621157 [details]
Created attachment 621158 [details]
Created attachment 621159 [details]
Created attachment 621160 [details]
What were you doing when this happened?
Can you duplicate it?
This happened when I tried to connect to the nxserver, using the following command to initiate the session:
This is also happening when I remotely connect with vnc.
Since the last yum-upgrade the xfwm(4) does not start up automatically in my xfce4 session any more. I tried to launch it by hand with
which yielded this error (and no wm was launched).
Dirk: Try clearing out your session cache in ~/.cache/sessions/
(In reply to comment #14)
> Dirk: Try clearing out your session cache in ~/.cache/sessions/
Thanks for the quick answer, tried it quickly, but no xfwm popped up. Will see later, if the error is reported by abrt.
Note that you may want to not be logged in, so your session without xfwm4 isn't getting saved again on logout.
(In reply to comment #16)
> Note that you may want to not be logged in, so your session without xfwm4
> isn't getting saved again on logout.
I do not completely understand this sentence, but if you mean that the window manager is not started after I logged out and in again, you are right. The solution I found for that is to start it as
from the terminal and log out via the "Log Off" item from the session menu bar. The wm then comes up as usual again.
I meant that if you removed the session cache files, and then logged out, the broken session would have been saved again, so you would not see any change. :) The session files would have to be removed when there is No active session happening for them to not be overwritten.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17'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 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.