| Summary: | [abrt] gnome-screensaver-2.91.91-1.fc15: do_user_switch: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | tuxor <acc-bugz-redhat> | ||||
| Component: | gnome-screensaver | Assignee: | jmccann | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 15 | CC: | chi0541, cschalle, jmccann, jon.dufresne, rlat, rstrode | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:e24fc305188ab2cad99d7e362e96e83f1640d12c | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-03-26 10:28:10 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: |
|
||||||
|
Description
tuxor
2011-03-13 09:14:44 UTC
Created attachment 483966 [details]
File: backtrace
Package: gnome-screensaver-2.91.91-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. Make sure you have two users set up 2. Login as the first one 3. Use "Switch User" and login as the second 4. Lognout the second one 5. Do not input password but click on switch button 6. Login as first user Package: gnome-screensaver-2.91.91-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- This occurred either starting or stopping a screen saver. Not sure exactly. Package: gnome-screensaver-2.91.91-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. ????? Initially described problem seems solved with the latest updates. |