Here's another test script attached; I used it with xscreensaver 5.36. extract from terminal:
$ ./test2.sh && paplay /usr/share/sounds/freedesktop/stereo/complete.oga 31.084305045 xscreensaver-command: activating and locking. 0.00user 0.00system 0:00.02elapsed 15%CPU (0avgtext+0avgdata 2276maxresident)k 0inputs+0outputs (0major+121minor)pagefaults 0swaps 31.387033001 0 31.388224522 31.389247590 $ ./test2.sh && paplay /usr/share/sounds/freedesktop/stereo/complete.oga 49.476176724 49.779119603 49.780295519 xscreensaver-command: activating and locking. 0.00user 0.00system 0:01.63elapsed 0%CPU (0avgtext+0avgdata 2268maxresident)k 0inputs+0outputs (0major+124minor)pagefaults 0swaps I wonder why time of xscreensaver-command -lock varies so much? For a second thing: paplay seems to wait until xscreensaver has faded screen, but if I replace it by beep, it might not wait that long. Why is that? ** Attachment added: "test2.sh" https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1701917/+attachment/4911650/+files/test2.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701917 Title: Slow in locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1701917/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
