Bug 868164
| Summary: | xscreensaver/maze was killed by signal 11 (SIGSEGV) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | caluml |
| Component: | xscreensaver | Assignee: | Mamoru TASAKA <mtasaka> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | mtasaka |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | xscreensaver-5.21-7.fc17 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-06-07 23:53:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
caluml
2012-10-19 07:59:46 UTC
virt-manager is not related to this issue (I don't know why abrt says so). * At least full backtrace is needed to investigate this issue. Would you gain the information from core file (perhaps located uder ~/.abrt/spool)? * Also the line 1230 in maze.c is really complicated. Can you take the real value of st, st->maze *(st->maze), ss, *ss? * And do you have some idea about when this issue occurred? Currently I don't have x86_64 machine so I cannot analyze your core file... Yes, I was very surprised to see that the bug had virt-manager for the resolution. It didn't seem that it could be related, but who knows. I think abrt correctly identifies it as bug 766769, but maybe the resolution given in that bug is wrong. I only have one thing under ~/.cache/abrt/spool/ : ccpp-2012-10-17-19:00:08-1151 $ cat core_backtrace 299dc351ed4bf6ab068452328b2873f27205ea34 0x4942 - /usr/libexec/xscreensaver/maze bfed8be0a2dc26612a3c3c6bdb3971c058100fa4 299dc351ed4bf6ab068452328b2873f27205ea34 0x297d - /usr/libexec/xscreensaver/maze f914286b73387cc3323a5b47e4eb98189d60d713 df54c88ec91ef43fa6225e34d46e847dd76e1348 0x21735 __libc_start_main /lib64/libc.so.6 075acda5d3230e115cf7c88597eaba416bdaa6bb 299dc351ed4bf6ab068452328b2873f27205ea34 0x326d - /usr/libexec/xscreensaver/maze - $ cat var_log_messages Oct 17 19:00:08 4gbl10280 kernel: [207476.582494] maze[1151]: segfault at 7ff96db588e0 ip 0000000000404942 sp 00007fffc6c62b60 error 4 in maze[400000+17000] Oct 17 19:00:09 4gbl10280 abrt[1238]: Saved core dump of pid 1151 (/usr/libexec/xscreensaver/maze) to /var/spool/abrt/ccpp-2012-10-17-19:00:08-1151 (20742144 bytes) $ cat cmdline maze -root This issue occurs pretty much randomly, but not that often. I will lock my screen (either to go to a meeting, lunch, or home), and when I come back, it is unlocked, which is obviously not a great situation. I am running XFCE. I have to run xscreensaver & after it has crashed to get it locking again. I might write a little script in cron to start it if it isn't already running - that way, there'll only be a little window where my machine is unlocked until the bug is fixed. Let me know if you need anything else. (gdb) print ss->x $3 = -1 (gdb) print ss->y $4 = 22 ss->maze produces a lot of output - I can send it if you need it. (In reply to comment #3) > (gdb) print ss->x > $3 = -1 This is difinitely an issue. Would you tell also me the following value? * ss->i * dir * st->path[ss->i].y * st->path[ss->i].x * st->path[ss->i -1].y * st->path[ss->i -1].x * st->maze[st->path[ss->i].x][st->path[ss->i].y] * st->maze[st->path[ss->i].x + 1][st->path[ss->i].y] * st->maze[st->path[ss->i].x - 1][st->path[ss->i].y] * st->maze[st->path[ss->i].x][st->path[ss->i].y + 1] * st->maze[st->path[ss->i].x][st->path[ss->i].y - 1] Some values may be invalid. (In reply to comment #3) > ss->maze produces a lot of output - I can send it if you need it. For now I want to see the value in comment 4. If some other values are needed, I will ask you again. Arrrgh, I've absentmindedly clicked Delete in the abrt tool, and have lost the coredump. :/ I'll wait for the next crash (shouldn't be too long - a few days), and I'll give you the values from that one. Thanks for your help on this, by the way. Hello: Were there any change that you could reproduce this issue? xscreensaver-5.21-7.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/FEDORA-2013-9679/xscreensaver-5.21-7.fc19 xscreensaver-5.21-7.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-9712/xscreensaver-5.21-7.fc18 xscreensaver-5.21-7.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2013-9690/xscreensaver-5.21-7.fc17 I think 5.21-7 should fix this issue. xscreensaver-5.21-7.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. xscreensaver-5.21-7.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. xscreensaver-5.21-7.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |