Your message dated Sun, 06 Apr 2008 16:22:55 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#447563: xscreensaver: leaves a zombie process running
for each invocation by powersaved
has caused the Debian Bug report #447563,
regarding xscreensaver: leaves a zombie process running for each invocation by
powersaved
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
447563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447563
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: xscreensaver
Version: 5.03-3
Severity: normal
It appears that there is a zombie process left each time a
suspend/resume cycle completes:
$ ps -Ao uname,pid,stat,start,cmd | grep \\\[do_screen_saver\\\]
root 918 Z 13:07:10 [do_screen_saver] <defunct>
root 3898 Z 16:05:37 [do_screen_saver] <defunct>
root 4019 Z Oct 19 [do_screen_saver] <defunct>
root 4309 Z 16:24:56 [do_screen_saver] <defunct>
root 5250 Z Oct 19 [do_screen_saver] <defunct>
root 6159 Z Oct 19 [do_screen_saver] <defunct>
root 6678 Z Oct 19 [do_screen_saver] <defunct>
root 8822 Z Oct 19 [do_screen_saver] <defunct>
root 9155 Z 21:49:54 [do_screen_saver] <defunct>
root 9851 Z Oct 20 [do_screen_saver] <defunct>
root 11162 Z Oct 20 [do_screen_saver] <defunct>
root 13508 Z Oct 20 [do_screen_saver] <defunct>
root 13766 Z 00:19:45 [do_screen_saver] <defunct>
root 14195 Z Oct 20 [do_screen_saver] <defunct>
root 14400 Z 01:53:21 [do_screen_saver] <defunct>
root 16263 Z 03:27:25 [do_screen_saver] <defunct>
root 18179 Z Oct 20 [do_screen_saver] <defunct>
root 18611 Z Oct 20 [do_screen_saver] <defunct>
root 26309 Z Oct 20 [do_screen_saver] <defunct>
root 26992 Z Oct 20 [do_screen_saver] <defunct>
root 30831 Z 09:07:32 [do_screen_saver] <defunct>
root 32560 Z 11:24:39 [do_screen_saver] <defunct>
Oddly:
$ last
jacob :0 Wed Oct 10 23:24 still logged in
reboot system boot 2.6.22-2-k7 Wed Oct 10 23:24 - 03:47 (11+04:23)
jacob :0 Wed Oct 10 09:33 - crash (13:50)
reboot system boot 2.6.22-2-k7 Wed Oct 10 09:33 - 03:47 (11+18:14)
jacob :0 Mon Oct 1 17:44 - crash (8+15:49)
root tty1 Mon Oct 1 17:43 - 06:45 (13:01)
root tty1 Mon Oct 1 17:43 - 17:43 (00:00)
root tty1 Mon Oct 1 17:43 - 17:43 (00:00)
root tty1 Mon Oct 1 17:43 - 17:43 (00:00)
root tty1 Mon Oct 1 17:42 - 17:42 (00:00)
root tty1 Mon Oct 1 17:42 - 17:42 (00:00)
so they don't go back to my last reboot. I wonder if this is due to a
library upgrade, or if they are, in fact, getting reaped after some
period.
Laptop is a standard Acer Aspire 3000 series, x86, running Debian/Sid.
Using ratpoison as my window manager.
Jacob
wtmp begins Mon Oct 1 17:42:10 2007
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-2-k7 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages xscreensaver depends on:
ii libatk1.0-0 1.20.0-1 The ATK accessibility toolkit
ii libc6 2.6.1-6 GNU C Library: Shared libraries
ii libcairo2 1.4.10-1 The Cairo 2D vector graphics libra
ii libfontconfig1 2.4.2-1.4 generic font configuration library
ii libglade2-0 1:2.6.2-1 library to load .glade files at ru
ii libglib2.0-0 2.14.2-1 The GLib library of C routines
ii libgtk2.0-0 2.12.0-3 The GTK+ graphical user interface
ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library
ii libjpeg62 6b-14 The Independent JPEG Group's JPEG
ii libpam0g 0.99.7.1-5 Pluggable Authentication Modules l
ii libpango1.0-0 1.18.2-2 Layout and rendering of internatio
ii libsm6 2:1.0.3-1+b1 X11 Session Management library
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxcomposite1 1:0.3.2-1+b1 X11 Composite extension library
ii libxcursor1 1:1.1.9-1 X cursor management library
ii libxdamage1 1:1.1.1-3 X11 damaged region extension libra
ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar
ii libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio
ii libxi6 2:1.1.3-1 X11 Input extension library
ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library
ii libxml2 2.6.30.dfsg-2 GNOME XML library
ii libxmu6 1:1.0.3-1 X11 miscellaneous utility library
ii libxpm4 1:3.5.7-1 X11 pixmap library
ii libxrandr2 2:1.2.2-1 X11 RandR extension library
ii libxrender1 1:0.9.4-1 X Rendering Extension client libra
ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library
ii libxxf86misc1 1:1.0.1-2 X11 XFree86 miscellaneous extensio
ii libxxf86vm1 1:1.0.1-2 X11 XFree86 video mode extension l
ii netpbm 2:10.0-11 Graphics conversion tools
Versions of packages xscreensaver recommends:
pn libjpeg-progs <none> (no description available)
ii perl [perl5] 5.8.8-11.1 Larry Wall's Practical Extraction
ii wamerican-huge [wordlist] 6-2.1 American English dictionary words
pn xli | xloadimage <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.15.20-1
Oscon wrote:
> Workaround for this bug:
>
> /Sorry, I don't speak good english /
>
> If you do suspend_event (stanby/suspend_to_ram/suspend_to_disk) and you are
> not logged on X screen! / powersave -u from tty or an acp_button_event (SLEEP
> button) /, then you have got
> a zombie process after resume (do_screen_saver), because the screensaver
> can't run, if you are not logged.
>
> If you are logged, and you make suspend with "kpowersave", then the
> do_screen_saver can run, and you haven't got zombi process after resume.
>
> Workaround:
>
> you have to delete "screen_saver" from the /etc/powersave/events file:
>
> EVENT_GLOBAL_SUSPEND2DISK="prepare_suspend_to_disk do_suspend_to_disk"
> EVENT_GLOBAL_SUSPEND2RAM="prepare_suspend_to_ram do_suspend_to_ram"
> EVENT_GLOBAL_STANDBY="prepare_standby do_standby"
>
> If you want use screensaver, then you have to use DIRECT xscreensaver's
> settings (example), or other screen saver program.
>
> Don't use powersaved's screen_saver()!
>
>
powersaved 0.15.x has been completely redesigned to be simple power
management policy daemon for the console.
If you are running a desktop session, you should run a graphical desktop
policy daemon such as kpowersave or gnome-power-manager, which will take
care of the screen locking then themselves.
so_screen_saver in powersaved is more or less obsolete. It contains the
following notice:
#####################################################################
# kde_screen_saver and xscreensaver_screen_saver are no longer used #
# use a graphical frontend like kpowersave instead #
# these are only here for your hacking pleasure... #
#####################################################################
So I'd say it's safe to close this bug for 0.15.20-1.
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
