| Summary: | [abrt] xfce4-panel-4.6.4-1.fc14: SmcRequestSaveYourself: Process /usr/bin/xfce4-panel was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | deuno_panopticon | ||||
| Component: | xfce4-panel | Assignee: | Kevin Fenzi <kevin> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | cwickert, kevin | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:db8c746f4224b8cd2390350cefecb6fa45bf87ad | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-08-16 21:28:37 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Created attachment 477014 [details]
File: backtrace
Can you attach your ~/.xsession-errors file? Also, if you make a new user and login as them with Xfce, does everything operate normally for them? The above, you are running startxfce4 in a text vty? Or in a X session? You shouldn't really start Xfce that way. Use 'startx' or run gdm and login and choose Xfce as your session type. The ~/.xsession-errors file is now attached. (partial)
if you need to continue on (it mostly repeats after a point) let me know..
/usr/bin/startxfce4: X server already running on display :0
<stdin>:1: error: Unknown #directive "Those"
# Those are fallback settings, use the ui plugin to change it
<stdin>:2: error: Unknown #directive "or"
# or add your overrides to ~/.Xresources
<stdin>:3: error: Unknown #directive "Xft"
# Xft.hintstyle: hintnone/hintslight/hintmedium/hintfull
<stdin>:4: error: Unknown #directive "Xft"
# Xft hinting: 1/0
4 errors in preprocessor.
xrdb: "Xft.hinting" on line 9 overrides entry on line 6
xrdb: "Xft.hintstyle" on line 11 overrides entry on line 7
xfdesktop[1817]: starting up
(xfce4-mixer-plugin:1836): xfce4-mixer-plugin-DEBUG: mixer_plugin->track_label = 'Master'
GNOME_KEYRING_CONTROL=/tmp/keyring-95366s
GNOME_KEYRING_PID=1867
Applet requires SELinux be enabled to run.
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
GNOME_KEYRING_CONTROL=/tmp/keyring-95366s
GPG_AGENT_INFO=/tmp/keyring-95366s/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-95366s
GPG_AGENT_INFO=/tmp/keyring-95366s/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-95366s
GPG_AGENT_INFO=/tmp/keyring-95366s/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-95366s/ssh
(gpk-update-icon:1938): PackageKit-DEBUG: state array add 0xb6d035b0 (0x1)
(gpk-update-icon:1938): PackageKit-DEBUG: refreshing task list
(gpk-update-icon:1938): PackageKit-DEBUG: state array add 0x854eb80 (0x1)
(gpk-update-icon:1938): PackageKit-DEBUG: state array add 0x854e920 (0x2)
(gpk-update-icon:1938): PackageKit-DEBUG: state array add 0x8566950 (0x3)
(gpk-update-icon:1938): PackageKit-DEBUG: refreshing task list
(gpk-update-icon:1938): PackageKit-DEBUG: state array add 0x8566980 (0x2)
(gpk-update-icon:1938): PackageKit-DEBUG: notify::connected
(gpk-update-icon:1938): PackageKit-DEBUG: refreshing task list
(gpk-update-icon:1938): PackageKit-DEBUG: state array add 0x8566b20 (0x3)
(gpk-update-icon:1938): PackageKit-DEBUG: refreshing task list
(gpk-update-icon:1938): PackageKit-DEBUG: state array add 0x8566b50 (0x4)
(gpk-update-icon:1938): PackageKit-DEBUG: notify::mime-types
(gpk-update-icon:1938): PackageKit-DEBUG: notify::distro-id
(gpk-update-icon:1938): PackageKit-DEBUG: notify::version-micro
(gpk-update-icon:1938): PackageKit-DEBUG: notify::version-major
(gpk-update-icon:1938): PackageKit-DEBUG: notify::version-minor
(gpk-update-icon:1938): PackageKit-DEBUG: notify::backend-description
(gpk-update-icon:1938): PackageKit-DEBUG: notify::network-state
(gpk-update-icon:1938): PackageKit-DEBUG: notify::roles
(gpk-update-icon:1938): PackageKit-DEBUG: notify::backend-name
(gpk-update-icon:1938): PackageKit-DEBUG: notify::backend-author
(gpk-update-icon:1938): PackageKit-DEBUG: notify::groups
(gpk-update-icon:1938): PackageKit-DEBUG: notify::filters
(gpk-update-icon:1938): PackageKit-DEBUG: state array remove 0xb6d035b0
(gpk-update-icon:1938): PackageKit-DEBUG: state array remove 0x854eb80
(gpk-update-icon:1938): PackageKit-DEBUG: state array remove 0x854e920
(gpk-update-icon:1938): PackageKit-DEBUG: state array remove 0x8566950
(gpk-update-icon:1938): PackageKit-DEBUG: state array remove 0x8566980
(gpk-update-icon:1938): PackageKit-DEBUG: state array remove 0x8566b20
(gpk-update-icon:1938): PackageKit-DEBUG: state array remove 0x8566b50
(gpk-update-icon:1938): PackageKit-DEBUG: state array add 0x8566e90 (0x5)
(gpk-update-icon:1938): PackageKit-DEBUG: state array remove 0x8566e90
*performing second request: Create a second log-in and test if XFCE start menu loads normally
Previous installation of "auto-login" via accountsdialog/accountservice was used
*auto-login
>yum install accountsdialog accountservice
>restart
This was disabled to allow for a new user : "test1" to be created
Test1 shows no problems with XFCE4 start menu when logging in.
The above, you are running startxfce4 in a text vty? Or in a X session? You shouldn't really start Xfce that way. Use 'startx' or run gdm and login and choose Xfce as your session type. I used startxfce4 / xfce in X terminal (after looking for commands on-line) with auto-log in enabled, I do not have to choose xfce as a session type. I will attempt to use "startx" or gdm... I configured a hot key to allow access to the start menu without it being displayed on the bottom panel. By entering System>Task Manager I killed xfce-session(or one of the variants xfce-??? at this moment I cannot remember) this "restarted?" xfce start menu to re-appear. xfce-panel? xfce-menu?... ok, so your user is back to their normal state and working now? Or the orig autostarting session doesn't work still? This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: xfce4-panel --sm-client-id 234072e23-4610-4f83-815b-0e38728ecd08 component: xfce4-panel crash_function: SmcRequestSaveYourself executable: /usr/bin/xfce4-panel kernel: 2.6.35.10-74.fc14.i686 package: xfce4-panel-4.6.4-1.fc14 rating: 4 reason: Process /usr/bin/xfce4-panel was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1296820937 uid: 500 comment ----- The steps above are what I was doing before the crash occured. And May not produce the same results. However, XFCE is no longer starting up as normal, Terminal has to be used typing "xfce-panel" to start program. below is what is shown when "startxfce4" is run in terminal [name of user~]$ startxfce4 /usr/bin/startxfce4: X server already running on display :0.0 <stdin>:1: error: Unknown #directive "Those" # Those are fallback settings, use the ui plugin to change it <stdin>:2: error: Unknown #directive "or" # or add your overrides to ~/.Xresources <stdin>:3: error: Unknown #directive "Xft" # Xft.hintstyle: hintnone/hintslight/hintmedium/hintfull <stdin>:4: error: Unknown #directive "Xft" # Xft hinting: 1/0 4 errors in preprocessor. xrdb: "Xft.hinting" on line 9 overrides entry on line 6 xrdb: "Xft.hintstyle" on line 11 overrides entry on line 7 ** ERROR **: Another session manager is already running aborting... /etc/xdg/xfce4/xinitrc: line 130: 3311 Aborted (core dumped) $xfcesm [name of user ~]$ xscreensaver: 05:23:00: already running on display :0.0 (window 0xa00001) from process 1798 (name of user). How to reproduce ----- 1.Call session with Skype Ended (LAN) 2.Unplug (LAN) , enable wireless, Restart comupter 3. XFCE start menu (Panel) fails to appear