After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 374829 - dialog doesn't always appear right away
dialog doesn't always appear right away
Status: RESOLVED INVALID
Product: gnome-screensaver
Classification: Deprecated
Component: dialog
CVS HEAD
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-13 19:21 UTC by William Jon McCann
Modified: 2007-02-06 21:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description William Jon McCann 2006-11-13 19:21:18 UTC 
Possibly a result of the patch that just landed...

1. Lock screen
2. Move mouse
3. Click cancel
4. Move mouse
5. Click cancel
6. Move mouse

The dialog takes a few seconds to appear where it normally appears immediately.
Comment 1 Bruno Boaventura 2006-11-21 03:23:32 UTC 
Here, I have been noted dialog taking a few seconds to DISAPPEAER.
Comment 2 William Jon McCann 2007-01-05 18:35:00 UTC 
When I turn off user-switching I still see this problem.  The bt from:
gdb --pid `pgrep -f 'gnome-screensaver-dialog'`
at the time of the hang.

(gdb) bt

+ Trace 99662

  • #0 __kernel_vsyscall
  • #1 send
    from /lib/libc.so.6
  • #2 __vsyslog_chk
    from /lib/libc.so.6
  • #3 __syslog_chk
    from /lib/libc.so.6
  • #4 pam_vsyslog
    from /lib/libpam.so.0
  • #5 pam_syslog
    from /lib/libpam.so.0
  • #6 pam_sm_authenticate
    from /lib/security/pam_unix.so
  • #7 _pam_dispatch
    from /lib/libpam.so.0
  • #8 pam_authenticate
    from /lib/libpam.so.0
  • #9 gs_auth_verify_user
    at gs-auth-pam.c line 413
  • #10 auth_check_idle
    at gnome-screensaver-dialog.c line 281
  • #11 g_idle_dispatch
    at gmain.c line 4083
  • #12 IA__g_main_context_dispatch
    at gmain.c line 2049
  • #13 g_main_context_iterate
    at gmain.c line 2681
  • #14 IA__g_main_loop_run
    at gmain.c line 2885
  • #15 IA__gtk_main
    at gtkmain.c line 1135
  • #16 main
    at gnome-screensaver-dialog.c line 546 






Comment 3


Ray Strode [halfline]





          2007-01-05 19:52:41 UTC
        



is the backtrace consistently in syslog or does it move around in pm_sm_authenticate a bit?

I wonder if pam_unix is doing some sort of rate control to prevent bruteforce attacks.






Comment 4


William Jon McCann





          2007-02-06 21:08:21 UTC
        



Probably some pam thing...