Package: xscreensaver Version: 5.15-3 Severity: normal
If your system has no or non-working battery-powered clock, time will be incorrect until NTP runs. If you have no network connectivity before xscreensaver starts, this can mean a sudden jump by several years. I guess those who suffer from MS Windows and don't use that undocumented registry hack may see jumps by an hour due to time zone handling too. When a forward jump happens, xscreensaver locks the screen. As I understand, using clock_gettime(CLOCK_MONOTONIC) instead would fix this problem. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: armhf (armv7l) Kernel: Linux 3.0.42 (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xscreensaver depends on: ii libatk1.0-0 2.8.0-2 ii libc6 2.17-92 ii libcairo2 1.12.14-5 ii libfontconfig1 2.10.2-2 ii libfreetype6 2.4.9-1.1 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglade2-0 1:2.6.4-1 ii libglib2.0-0 2.36.4-1 ii libgtk2.0-0 2.24.20-1 ii libice6 2:1.0.8-2 ii libpam0g 1.1.3-9 ii libpango1.0-0 1.32.5-5+b1 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.6.1-1 ii libxext6 2:1.3.2-1 ii libxi6 2:1.7.2-1 ii libxinerama1 2:1.1.3-1 ii libxml2 2.9.1+dfsg1-3 ii libxmu6 2:1.1.1-1 ii libxpm4 1:3.5.10-1 ii libxrandr2 2:1.4.1-1 ii libxrender1 1:0.9.8-1 ii libxt6 1:1.1.4-1 ii libxxf86vm1 1:1.1.3-1 ii xscreensaver-data 5.15-3 Versions of packages xscreensaver recommends: ii libjpeg-progs 8d-1 ii miscfiles [wordlist] 1.4.2.dfsg.1-9 ii perl [perl5] 5.14.2-21 Versions of packages xscreensaver suggests: pn fortune <none> pn gdm3 | kdm-gdmcompat <none> ii iceweasel [www-browser] 23.0-2 pn qcam | streamer <none> pn xdaliclock <none> pn xfishtank <none> pn xscreensaver-gl <none> -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
