| Summary: | x11-misc/xscreensaver crash when using fingerprint scanner authentication | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jesse Luehrs <jluehrs2> |
| Component: | Current packages | Assignee: | Jamie Zawinski <jwz> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | critical | CC: | ssuominen |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | debug log from running xscreensaver with the command 'xscreensaver -sync -verbose -no-capture -no-splash -no-capture-stderr' | ||
|
Description
Jesse Luehrs
2007-08-11 00:00:42 UTC
Created attachment 127705 [details]
debug log from running xscreensaver with the command 'xscreensaver -sync -verbose -no-capture -no-splash -no-capture-stderr'
As it turns out, it doesn't look like gdb is all that helpful: (gdb) bt #0 0xb7fd6410 in __kernel_vsyscall () Cannot access memory at address 0xb50e44f0 Alright, I've found a few actual backtraces now, but they don't look all that useful:
(gdb) bt
#0 0xb7f1e410 in __kernel_vsyscall ()
#1 0xb7c3c721 in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0xb7c3de58 in *__GI_abort () at abort.c:88
#3 0x08052da1 in saver_exit (si=0xbfd69be4, status=-1,
dump_core_reason=0x8069e64 "because of synchronous X Error")
at windows.c:886
#4 0x0804f602 in saver_ehandler (dpy=0x81ea938, error=0xb602f91c)
at xscreensaver.c:333
#5 0xb7dbee5f in _XError (dpy=0x81ea938, rep=0xb602f9c4) at XlibInt.c:2905
#6 0xb7dc1734 in _XReadEvents (dpy=0x81ea938) at XlibInt.c:1060
#7 0xb7dad90a in XNextEvent (dpy=0x81ea938, event=0xb6030320)
at NextEvent.c:50
#8 0xb7048a0b in ?? () from /usr/lib/libtfmessbsp.so
#9 0x081ea938 in ?? ()
#10 0xb6030320 in ?? ()
#11 0x00000000 in ?? ()
and
(gdb) bt
#0 0xb7fb2410 in __kernel_vsyscall ()
#1 0xb7cd0721 in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0xb7cd1e58 in *__GI_abort () at abort.c:88
#3 0x08052da1 in saver_exit (si=0xbf821e94, status=-1,
dump_core_reason=0x8069e64 "because of synchronous X Error")
at windows.c:886
#4 0x0804f602 in saver_ehandler (dpy=0x80ea100, error=0xb70c56cc)
at xscreensaver.c:333
#5 0xb7e52e5f in _XError (dpy=0x80ea100, rep=0xb70c575c) at XlibInt.c:2905
#6 0xb7e54269 in _XWaitForWritable (dpy=0x80ea100, cv=0x0) at XlibInt.c:351
#7 0xb7e545f4 in _XSend (dpy=0x80ea100, data=0x818c000 "ÿÿÿ", size=179784)
at XlibInt.c:1462
#8 0xb7e4748e in PutSubImage (dpy=0x80ea100, d=52428812, gc=0x80ea640,
image=0x8152118, req_xoffset=0, req_yoffset=0, x=<value optimized out>,
y=<value optimized out>, req_width=<value optimized out>,
req_height=<value optimized out>, dest_bits_per_pixel=32,
dest_scanline_pad=32) at PutImage.c:804
#9 0xb7e4766c in XPutImage (dpy=0x80ea100, d=52428812, gc=0x80ea640,
image=0x8152118, req_xoffset=0, req_yoffset=0, x=0, y=0, req_width=198,
req_height=227) at PutImage.c:1027
#10 0xb70dd093 in ?? () from /usr/lib/libtfmessbsp.so
#11 0x080ea100 in ?? ()
#12 0x0320000c in ?? ()
#13 0x080ea640 in ?? ()
#14 0x08152118 in ?? ()
#15 0x00000000 in ?? ()
5.04 includes more PAM crash fixes, please try and reopen if it still fails Crashes seem to be happening less frequently, but they still happen. Let me know if there is any other information that you need. (In reply to comment #5) > Crashes seem to be happening less frequently, but they still happen. Let me > know if there is any other information that you need. > Try again with 5.05 or 5.05-r1 (no difference regarding this issue) Jamie, can you look at the issue? Thanks. (In reply to comment #5) > Crashes seem to be happening less frequently, but they still happen. Let me > know if there is any other information that you need. > Try 5.08, reopen if it's still a prob. |
