Bug#605283: marked as done (eeepc-acpi-scripts: Locks login manager with root password if xtrlock is installed and machine is suspended with no user being logged in)

2020-04-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Apr 2020 19:02:55 + with message-id and subject line Bug#955195: Removed package(s) from unstable has caused the Debian Bug report #605283, regarding eeepc-acpi-scripts: Locks login manager with root password if xtrlock is installed and machine is suspended with no

Bug#278190: marked as done (xtrlock unlocks upon very long input)

2005-01-20 Thread Debian Bug Tracking System
25 Oct 2004 20:06:31 +0800 Received: from 202.38.93.205 (SquirrelMail authenticated user muec) by webmail.ustc.edu.cn with HTTP; Mon, 25 Oct 2004 20:07:08 +0800 (CST) Message-ID: <[EMAIL PROTECTED]> Date: Mon, 25 Oct 2004 20:07:08 +0800 (CST) Subject: xtrlock unlocks upon v

Bug#278191: marked as done (xtrlock unlocks upon very long input)

2005-01-20 Thread Debian Bug Tracking System
25 Oct 2004 20:06:27 +0800 Received: from 202.112.113.126 (proxying for unknown) (SquirrelMail authenticated user muec) by webmail.ustc.edu.cn with HTTP; Mon, 25 Oct 2004 20:07:03 +0800 (CST) Message-ID: <[EMAIL PROTECTED]> Date: Mon, 25 Oct 2004 20:07:03 +0800 (CST) Su

Bug#278190: marked as done (xtrlock unlocks upon very long input)

2005-01-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Jan 2005 06:02:02 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#278190: fixed in xtrlock 2.0-9 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#278191: marked as done (xtrlock unlocks upon very long input)

2005-01-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Jan 2005 06:02:02 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#278190: fixed in xtrlock 2.0-9 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#264173: marked as done (xtrlock: FTBFS with gcc-3.4: label at end of compound statement)

2005-01-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Jan 2005 06:02:02 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#264173: fixed in xtrlock 2.0-9 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#278190: xtrlock unlocks upon very long input

2004-10-25 Thread muec
Package: xtrlock Version: 2.0-8 xtrlock can be bypassed by holding down any key for 1 minute and then pressing Enter. I am using Debian GNU/Linux 3.1, kernel 2.6.8-1-686, libc6 2.3.2.ds1-16, xlibs 4.3.0.dfsg.1-7 and Gnome 2.

Bug#278191: xtrlock unlocks upon very long input

2004-10-25 Thread muec
Package: xtrlock Version: 2.0-8 xtrlock can be bypassed by holding down any key for 1 minute and then pressing Enter. I am using Debian GNU/Linux 3.1, kernel 2.6.8-1-686, libc6 2.3.2.ds1-16, xlibs 4.3.0.dfsg.1-7 and Gnome 2.

xtrlock

2004-09-13 Thread Lothar Ketterer
Hi, i just installed xtrlock_2.0-8_i386.deb (on sarge). After typing "xtrlock" in a xterm, it was possible to change to the console (or whatever this may be called) with Ctrl-Alt-F1. With the same user logged in a "killall xtrlock" unlocked the X-Session. So i thought i

Bug#267076: xtrlock: [patch] could use different colors to show status

2004-08-20 Thread Javier Donaire
Package: xtrlock Version: 2.0-8 Severity: wishlist It is confusing to use xtrlock because there is no information of the status of the user's input. With this patch the cursor changes its color to green if a password is being typed, and changes it again to red for a second if a bad try is

Bug#188230: marked as done (bug in xtrlock)

2004-08-08 Thread Debian Bug Tracking System
Your message dated 07 Aug 2004 22:04:19 -0700 with message-id <[EMAIL PROTECTED]> and subject line bug in xtrlock has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibil

Bug#264173: xtrlock: FTBFS with gcc-3.4: label at end of compound statement

2004-08-07 Thread Andreas Jochens
Package: xtrlock Severity: normal Tags: patch When building 'xtrlock' with gcc-3.4 I get the following error: gcc -O2 -g -DSHADOW_PWD -c -o xtrlock.o xtrlock.c xtrlock.c: In function `main': xtrlock.c:207: error: label at end of compound statement make[1]: *** [xtrlock.o]

xtrlock package, patch for pam authorization attached

2004-03-14 Thread emil71se
sting the authorization (it is annoying to accidently lock X while testing). It identifies as "xlock", so the same pam entry can be used, e.g a /etc/pam.d/xlock file containing; #%PAM-1.0 auth required /lib/security/pam_stack.so service=system-auth Best Regards, Lars Ekman dif