Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 188415 - x11-misc/xscreensaver crash when using fingerprint scanner authentication
Summary: x11-misc/xscreensaver crash when using fingerprint scanner authentication
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Jamie Zawinski
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-11 00:00 UTC by Jesse Luehrs
Modified: 2009-04-30 14:53 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
debug log from running xscreensaver with the command 'xscreensaver -sync -verbose -no-capture -no-splash -no-capture-stderr' (xscreensaver-bug,13.96 KB, text/plain)
2007-08-11 00:02 UTC, Jesse Luehrs
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Luehrs 2007-08-11 00:00:42 UTC
Using the fingerprint scanner authentication through pam can occasionally cause xscreensaver to lock up or crash. It only happens occasionally, and it happens when I assume it's trying to run the fingerprint scanner input program.

Reproducible: Sometimes

Steps to Reproduce:
I press a key to bring up the password entry box, and press enter with a blank password, and usually it brings up the fingerprint entry program, but every once in a while it either crashes or locks up instead.
Actual Results:  
When it locks up, the mouse is constrained to stay within the password entry dialog while xscreensaver is still running, and even after killing xscreensaver (have to use  -9), the keyboard grab doesn't go away (although the mouse grab partially does). It also occasionally crashes.

Expected Results:  
It should handle the fingerprint auth program failure gracefully... the screen should stay locked if the fingerprint auth program fails to run.

I'll attach the relevant debug log from a crash, and I'll keep it running under gdb for a while in case that turns up any more useful information. Let me know if there's any other info you need.

Portage 2.1.2.11 (default-linux/x86/2006.1, gcc-4.1.2, glibc-2.5-r4, 2.6.21-suspend2-r6 i686)
=================================================================
System uname: 2.6.21-suspend2-r6 i686 Intel(R) Core(TM) Duo CPU T2700 @ 2.33GHz
Gentoo Base System release 1.12.9
Timestamp of tree: Fri, 10 Aug 2007 07:50:01 +0000
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
ccache version 2.4 [enabled]
dev-java/java-config: 1.3.7, 2.0.33-r1
dev-lang/python:     2.4.4-r4
dev-python/pycrypto: 2.0.1-r6
dev-util/ccache:     2.4-r7
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.61
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.17
sys-devel/gcc-config: 1.3.16
sys-devel/libtool:   1.5.23b
virtual/os-headers:  2.6.21
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=pentium-m -O2 -pipe -g"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/init.d /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c"
CXXFLAGS="-march=pentium-m -O2 -pipe -g"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache distcc distlocks metadata-transfer parallel-fetch sandbox sfperms splitdebug strict"
GENTOO_MIRRORS="http://gentoo.cites.uiuc.edu/pub/gentoo"
LANG="en_US"
LC_ALL="en_US"
MAKEOPTS="-j6"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/portage/local/layman/enlightenment"
SYNC="rsync://gentoo.cites.uiuc.edu/gentoo-portage"
USE="X a52 aac aalib acpi aim alsa apache2 audiofile bash-completion berkdb bitmap-fonts blas bzip2 caps cdr cjk cli cracklib crypt cscope cups curl dbus dga dri dvd encode expat fam fastcgi flac ftp gd gdbm gif ginac gpm gtk gtk2 guile hal iconv idn imap imlib isdnlog java javascript joystick jpeg lcms lesstif libcaca lua midi mmap mmx mng mozilla mp3 mpeg mpi msn mudflap ncurses nls nptl nptlonly nsplugin offensive ogg openal opengl openmp oscar oss pam pcmcia pcre pdf perl pic plotutils png ppds pppd python quicktime readline reflection ruby samba sdl session slang speex spell spl sqlite sse sse2 ssl startup-notification svg tcpd tetex theora threads tiff truetype truetype-fonts type1-fonts unicode usb videos vim-syntax vorbis win32codecs x86 xml xorg xosd xpm xv xvid yahoo zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="evdev keyboard mouse synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="fbdev vesa fglrx radeon"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS

xscreensaver-5.02-r2
pam-0.78-r5
pam_bioapi 0.2.1-r1
bioapi 1.2.2
tfm-fingerprint 1.0

On another note, I tried submitting this report to jwz@jwz.org, but the mail bounced with access denied... anyone know what's up?
Comment 1 Jesse Luehrs 2007-08-11 00:02:16 UTC
Created attachment 127705 [details]
debug log from running xscreensaver with the command 'xscreensaver -sync -verbose -no-capture -no-splash -no-capture-stderr'
Comment 2 Jesse Luehrs 2007-08-12 18:01:24 UTC
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
Comment 3 Jesse Luehrs 2007-08-13 21:27:03 UTC
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 ?? ()
Comment 4 Samuli Suominen (RETIRED) gentoo-dev 2008-02-08 14:18:38 UTC
5.04 includes more PAM crash fixes, please try and reopen if it still fails
Comment 5 Jesse Luehrs 2008-02-17 04:23:07 UTC
Crashes seem to be happening less frequently, but they still happen. Let me know if there is any other information that you need.
Comment 6 Samuli Suominen (RETIRED) gentoo-dev 2008-05-08 10:45:19 UTC
(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.
Comment 7 Samuli Suominen (RETIRED) gentoo-dev 2009-04-30 14:53:40 UTC
(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.