Bug 831563
| Summary: | [abrt] xfce4-panel-4.8.6-3.fc16: XScreenCount: Process /usr/bin/xfce4-panel was killed by signal 11 (SIGSEGV) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Steve Coleman <stepacoleman> | ||||||||||
| 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: | 16 | CC: | alberto.fusari, christoph.wickert, drjohnson1, kevin, maxamillion | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:0241a8fbb49706549a0ce6730f39112be481ebcd | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-02-14 01:45:28 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Steve Coleman
2012-06-13 10:24:49 UTC
Created attachment 591425 [details]
File: maps
Created attachment 591426 [details]
File: dso_list
Created attachment 591427 [details]
File: backtrace
What were you doing when this happened? Can you duplicate it? All I do is boot the machine and try to login, the GUI fails and I wind up back at the xfce login prompt again. Login the second time and it works. I have been looking at this and I think what might be happening is there appears to be an application which *sometimes* appears on the screen just before it restarts. Sometimes it restarts too fast to see it even display. I think that xfce is trying to load a previous session, fails, restarts, and upon logging in the second time it doesn't restart that app, or the app doesn't start with a previous instance already running/shutting down. Not sure which, but ps -ef is not listing it on the second time around. The application I see sometimes appears to be grip 1:3.2.0.31.fc16 x86_64 (from my yum install history), which didn't recognize the CD drive in this machine so I thought I had closed it to go look for something else. Appaently it must have still been running and was saved with the xfce session information. In any case, a user app should not normally be trashing the xfce manager. Thats my best guess for the moment. Can you attach your: ~/.cache/sessions/xfce4-session* and ~/.cache/sessions/xfwm4*.state files? Does grip appear in them? If you move them out of the way does the new fresh session behave as expected? Yes grip was listed, but after moving the cache files it still gave the double login. After removing grip from the system, and everything else I added that same day it still has problems. Below is the current session file: [Session: Default] Client0_ClientId=28c0fd8e4-e1c2-4b31-a362-04d1b9b6de29 Client0_Hostname=local/tux01 Client0_CloneCommand=xfwm4 Client0_DiscardCommand=rm,-rf,/home/scoleman/.cache/sessions/xfwm4-28c0fd8e4-e1c2-4b31-a362-04d1b9b6de29.state Client0_RestartCommand=xfwm4,--display,:1.0,--sm-client-id,28c0fd8e4-e1c2-4b31-a362-04d1b9b6de29 Client0_CurrentDirectory=/home/scoleman Client0_Program=xfwm4 Client0_UserId=scoleman Client0_Priority=15 Client0_RestartStyleHint=2 Client1_ClientId=21134ffaf-e9d5-4d05-be30-a879943abb83 Client1_Hostname=local/tux01 Client1_CloneCommand=xfce4-panel Client1_RestartCommand=xfce4-panel,--display,:1.0,--sm-client-id,21134ffaf-e9d5-4d05-be30-a879943abb83 Client1_CurrentDirectory=/home/scoleman Client1_Program=xfce4-panel Client1_UserId=scoleman Client1_Priority=25 Client1_RestartStyleHint=2 Client2_ClientId=20f9abfe7-b896-4d91-bc48-86f8a967ce09 Client2_Hostname=local/tux01 Client2_CloneCommand=xfdesktop Client2_RestartCommand=xfdesktop,--display,:1.0,--sm-client-id,20f9abfe7-b896-4d91-bc48-86f8a967ce09 Client2_CurrentDirectory=/home/scoleman Client2_Program=xfdesktop Client2_UserId=scoleman Client2_Priority=35 Client2_RestartStyleHint=2 Client3_ClientId=20598bdb1-8e57-4501-9cb0-34eb0f7fc020 Client3_Hostname=local/tux01 Client3_CloneCommand=xfce4-settings-helper Client3_RestartCommand=xfce4-settings-helper,--display,:1.0,--sm-client-id,20598bdb1-8e57-4501-9cb0-34eb0f7fc020 Client3_CurrentDirectory=/home/scoleman Client3_Program=xfce4-settings-helper Client3_UserId=scoleman Client3_Priority=50 Client3_RestartStyleHint=2 Client4_ClientId=27f4f8cec-e267-483e-ac8d-41ac47a67d7c Client4_Hostname=local/tux01 Client4_CloneCommand=xfce4-power-manager Client4_RestartCommand=xfce4-power-manager,--restart,--sm-client-id,27f4f8cec-e267-483e-ac8d-41ac47a67d7c Client4_CurrentDirectory=/ Client4_DesktopFile=/etc/xdg/autostart/xfce4-power-manager.desktop Client4_Program=xfce4-power-manager Client4_UserId=scoleman Client4_Priority=50 Client4_RestartStyleHint=0 Count=5 Legacy0_Screen=0 Legacy0_Command=Terminal,--geometry=179x52,--display,:1.0,--role=Terminal-0x16830a0-2207-1339040521,--show-menubar,--show-borders,--hide-toolbars,--working-directory,/media Legacy0_ClientMachine=tux01 LegacyCount=1 Screen0_ActiveWorkspace=1 LastAccess=1339730706 ok, can you also attach a ~/.xsession-errors file from right after a failed session? "yum update" followed by reboot backtrace_rating: 4 Package: xfce4-panel-4.10.0-2.fc18 OS Release: Fedora release 18 (Spherical Cow) Created attachment 652912 [details]
.xsession-errors first time it loaded after crashing
For reference: [user1@localhost ~]$ more ~/.cache/sessions/xf* [CLIENT] 0x3600004 [CLIENT_LEADER] 0x3600001 [WINDOW_ROLE] Terminal-0x16ba060-1387-1354031555 [RES_NAME] Terminal [RES_CLASS] Terminal [WM_NAME] Terminal - root@localhost:~ [WM_COMMAND] (1) "Terminal" [GEOMETRY] (1,53,1015,479) [GEOMETRY-MAXIMIZED] (1,53,815,479) [SCREEN] 0 [DESK] 0 [FLAGS] 0x10200 Both files requested above are not present. Odd. If you remove the ~/.cache/sessions/xf* file and login does it work? If you create a new user and login as them does it work ok? Not sure if your inquiry is to me or the person that opened this BZ, but I did remove ~/.config/ and was able to login again. I was able to recreate the problem, and then remove ~/.cache/ -- This did not help. (In reply to comment #13) > Not sure if your inquiry is to me or the person that opened this BZ, but I > did remove ~/.config/ and was able to login again. ok. So all was back to normal then... you were able to logout and login and all worked? > I was able to recreate the problem, and then remove ~/.cache/ -- This did > not help. How did you recreate the problem? Any specific steps? This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" 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 Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. |