Bug 560614
Summary: | crash detected in noseguy | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Maik Strewe <mstrewe> | ||||||||||||||
Component: | xscreensaver | Assignee: | Mamoru TASAKA <mtasaka> | ||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||||
Priority: | low | ||||||||||||||||
Version: | 12 | CC: | mtasaka | ||||||||||||||
Target Milestone: | --- | ||||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | i686 | ||||||||||||||||
OS: | Linux | ||||||||||||||||
Whiteboard: | abrt_hash:a7b8c37ae1837361b0592e8efd781d8f856345af | ||||||||||||||||
Fixed In Version: | 5.10-5.fc12 | Doc Type: | Bug Fix | ||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2010-02-05 01:38:07 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
Maik Strewe
2010-02-01 11:47:51 UTC
Created attachment 388016 [details]
File: backtrace
Do you see noseguy crash when launching noseguy from the terminal like below? $ /usr/libexec/xscreensaver/noseguy If so are there any messages on the terminal? No I dont start from terminal. I've done an ssh -X session from Desktop to laptop(here the error happands) end start gnome session on laptop. To test the speed of remote X forwarding with encryption i start Screensaver(within gnome session) so i have no error message for you ... sorry Thank you for reply. Then would you - attach the following files (of the machine in which crash happened)? * /etc/xscreensaver/XScreenSaver.ad * ~/.xscreensaver (of the user using screensaver), if any * ~/.xsession-errors - and show the result of the following? $ rpm -qa | grep font | sort Created attachment 388287 [details]
XScreenSaver.ad
Created attachment 388288 [details]
.xscreensaver of home directory
Created attachment 388289 [details]
.xsession-errors
Created attachment 388291 [details]
.xsession-errors.old
Created attachment 388297 [details]
rpm -qa output
(In reply to comment #8) > Created an attachment (id=388291) [details] > .xsession-errors.old Well, may be this crash happened when X session was about to shut down (during logout) or so and X resource was no longer available at that time. So while it seems this is not easily reproducible, I will add a patch which may prevent this from happening. xscreensaver-5.10-5.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/xscreensaver-5.10-5.fc12 xscreensaver-5.10-5.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/xscreensaver-5.10-5.fc11 xscreensaver-5.10-5.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. xscreensaver-5.10-5.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |