| Summary: | Xscreensaver not properly started and crashes sometimes | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | hannes <johannes.lips> |
| Component: | xscreensaver | Assignee: | Mamoru TASAKA <mtasaka> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | mtasaka |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-05-12 06:36:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
hannes
2011-04-24 07:45:17 UTC
Just to make it sure, would you post the output of the following? $ rpm -qa | grep screensaver rpm -qa | grep screensaver xscreensaver-base-5.13-1.fc15.x86_64 If the crash is reproducible with $ xflock4 (it seems that xflock4 just does $ xscreensaver-command -lock actually), would you try the following? - launch xscreensaver (maybe with -debug option is more helpful) from gdb - type $ xflock4 on another terminal - get backtrace by gdb Do you see the issue even if you create a new user? Didn't try with a new user but tried to hunt it down further. First of all it only crashes with the xscreensaver session started together with Xfce when calling xflock4. If I restart it afterwards it mostly works and it doesn't crash. (In reply to comment #5) > First of all it > only crashes with the xscreensaver session started together with Xfce when > calling xflock4. If I restart it afterwards it mostly works and it doesn't > crash. Then can you attach the running xscreensaver process with gdb and get backtrace when xscreensaver crashes when you call xflock4? Sorry I am not able to create a proper backtrace and it's working after restarting it a second time. I don't have time to dig deeper into that issue at the moment. The latest update solved this issue for me! |