Bug#770937: needrestart: Kills wdm session on system running systemd g (maybe via dbus restart)
Package: needrestart
Version: 1.2-5
Severity: grave
Justification: data loss
Hi Thomas and Patrick,
recently, it happened twice that needrestart killed my X session which
was started by wdm and is running the awesome window manager via
~/.Xsession.
I don't think it's the new upload but rather the recent dbus updates. I
can't exactly remember if the second-last case was at the time when dbus
was updated (and if so, needrestart would have been at version 1.2-4),
but the case today definitely had a dbus update included.
According to the logs it also restarted systemd itself.
Despite there is
$nrconf{override_rc} = {
# DBus
q(^dbus) = 0,
[…]
}
in the (used) default config, systemd restarted dbus:
Nov 25 11:18:57 c-cactus systemd[1]: Stopping D-Bus System Message Bus...
A more verbose log excerpt of what seems relevant to me:
Nov 25 11:18:57 c-cactus systemd[1]: Reexecuting.
Nov 25 11:18:57 c-cactus systemd[1]: systemd 215 running in system mode. (+PAM
+AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP
-APPARMOR)
Nov 25 11:18:57 c-cactus systemd[1]: Detected architecture 'x86-64'.
Nov 25 11:18:57 c-cactus systemd[1]: Started ACPI event daemon.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /var.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /home.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /boot.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /.
Nov 25 11:18:57 c-cactus systemd[1]: Started File System Check on
/dev/disk/by-uuid/….
[…]
Nov 25 11:18:57 c-cactus systemd[1]: Activated swap /dev/…/swap.
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Accounts Service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Bluetooth service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Regular background program
processing daemon...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Regular background program
processing daemon...
Nov 25 11:18:57 c-cactus systemd[1]: Started Regular background program
processing daemon.
Nov 25 11:18:57 c-cactus systemd[1]: Stopping D-Bus System Message Bus...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Accounts Service...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Bluetooth service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping OpenBSD Secure Shell server...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Journal Service...
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Default.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Default.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Basic System.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Basic System.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Paths.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Paths.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Timers.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Timers.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Sockets.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Sockets.
Nov 25 11:18:57 c-cactus systemd[1641]: Starting Shutdown.
Nov 25 11:18:57 c-cactus systemd[1641]: Reached target Shutdown.
Nov 25 11:18:57 c-cactus systemd[1641]: Starting Exit the Session...
Nov 25 11:18:57 c-cactus systemd[1]: Starting OpenBSD Secure Shell server...
Nov 25 11:18:57 c-cactus systemd[1]: Started OpenBSD Secure Shell server.
Nov 25 11:18:57 c-cactus systemd[1641]: Received SIGRTMIN+24 from PID 12082
(kill).
Nov 25 11:18:57 c-cactus systemd[1]: Started Trigger Flushing of Journal to
Persistent Storage.
Nov 25 11:18:57 c-cactus systemd[1]: Starting Daemon for power management...
Nov 25 11:18:57 c-cactus systemd[1]: Starting LSB: Starts and stops Wicd...
Nov 25 11:18:57 c-cactus systemd[1]: Starting D-Bus System Message Bus...
Nov 25 11:18:57 c-cactus systemd[1]: Started D-Bus System Message Bus.
Nov 25 11:18:57 c-cactus systemd[1]: Started Bluetooth service.
Nov 25 11:18:57 c-cactus systemd[1]: Starting Hostname Service...
Nov 25 11:18:57 c-cactus systemd[1]: Started Accounts Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started Daemon for power management.
Nov 25 11:18:57 c-cactus systemd[1]: Starting User Manager for UID 1000...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Login Service...
Nov 25 11:18:57 c-cactus systemd[1]: Started Hostname Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started Login Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started User Manager for UID 1000.
Nov 25 11:18:58 c-cactus systemd[1]: Starting Session c1 of user abe.
Nov 25 11:18:58 c-cactus systemd[1]: Started Session c1 of user abe.
Nov 25 11:18:59 c-cactus systemd[1]: Starting LSB: start or stop the WINGs
display manager...
Nov 25 11:18:59 c-cactus systemd[1]: Started LSB: start or stop the WINGs
display manager.
Nov 25 11:18:59 c-cactus systemd[1]: Starting X11 Display Manager.
Nov 25 11:18:59 c-cactus systemd[1]: Reached target X11 Display Manager.
I can send an even more complete journal log by private e-mail.
-- Package-specific
Bug#770937: needrestart: Kills wdm session on system running systemd g (maybe via dbus restart)
Hi Axel, restarting dbus kills any graphical user session. On 11/25/2014 11:58 AM, Axel Beckert wrote: recently, it happened twice that needrestart killed my X session which was started by wdm and is running the awesome window manager via ~/.Xsession. sorry :-( I don't think it's the new upload but rather the recent dbus updates. I can't exactly remember if the second-last case was at the time when dbus was updated (and if so, needrestart would have been at version 1.2-4), but the case today definitely had a dbus update included. According to the logs it also restarted systemd itself. This happens if needrestart detects systemd using outdated libs. needrestart suggests to run `systemctl daemon-reexec` if it detects that pid 1 uses outdated binaries (if systemd was detected). in the (used) default config, systemd restarted dbus: Are you able to kill your X session by calling `systemctl daemon-reexec` manually? Nov 25 11:18:57 c-cactus systemd[1]: Reexecuting. Nov 25 11:18:57 c-cactus systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR) Nov 25 11:18:57 c-cactus systemd[1]: Detected architecture 'x86-64'. Nov 25 11:18:57 c-cactus systemd[1]: Started ACPI event daemon. Nov 25 11:18:57 c-cactus systemd[1]: Mounted /var. Nov 25 11:18:57 c-cactus systemd[1]: Mounted /home. Nov 25 11:18:57 c-cactus systemd[1]: Mounted /boot. Nov 25 11:18:57 c-cactus systemd[1]: Mounted /. Nov 25 11:18:57 c-cactus systemd[1]: Started File System Check on /dev/disk/by-uuid/…. […] Nov 25 11:18:57 c-cactus systemd[1]: Activated swap /dev/…/swap. At this point `systemctl reexec` should have been finished. Nov 25 11:18:57 c-cactus systemd[1]: Stopping Accounts Service... Nov 25 11:18:57 c-cactus systemd[1]: Stopping Avahi mDNS/DNS-SD Stack... Nov 25 11:18:57 c-cactus systemd[1]: Stopping Bluetooth service... Nov 25 11:18:57 c-cactus systemd[1]: Stopping Regular background program processing daemon... Nov 25 11:18:57 c-cactus systemd[1]: Starting Regular background program processing daemon... Nov 25 11:18:57 c-cactus systemd[1]: Started Regular background program processing daemon. Nov 25 11:18:57 c-cactus systemd[1]: Stopping D-Bus System Message Bus... Nov 25 11:18:57 c-cactus systemd[1]: Starting Accounts Service... Nov 25 11:18:57 c-cactus systemd[1]: Starting Bluetooth service... Nov 25 11:18:57 c-cactus systemd[1]: Stopping OpenBSD Secure Shell server... Nov 25 11:18:57 c-cactus systemd[1]: Stopping Journal Service... Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Default. Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Default. Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Basic System. Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Basic System. Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Paths. Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Paths. Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Timers. Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Timers. Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Sockets. Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Sockets. Nov 25 11:18:57 c-cactus systemd[1641]: Starting Shutdown. Nov 25 11:18:57 c-cactus systemd[1641]: Reached target Shutdown. Nov 25 11:18:57 c-cactus systemd[1641]: Starting Exit the Session... Nov 25 11:18:57 c-cactus systemd[1]: Starting OpenBSD Secure Shell server... Nov 25 11:18:57 c-cactus systemd[1]: Started OpenBSD Secure Shell server. Nov 25 11:18:57 c-cactus systemd[1641]: Received SIGRTMIN+24 from PID 12082 (kill). Nov 25 11:18:57 c-cactus systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. Nov 25 11:18:57 c-cactus systemd[1]: Starting Daemon for power management... Nov 25 11:18:57 c-cactus systemd[1]: Starting LSB: Starts and stops Wicd... Nov 25 11:18:57 c-cactus systemd[1]: Starting D-Bus System Message Bus... Nov 25 11:18:57 c-cactus systemd[1]: Started D-Bus System Message Bus. Nov 25 11:18:57 c-cactus systemd[1]: Started Bluetooth service. Nov 25 11:18:57 c-cactus systemd[1]: Starting Hostname Service... Nov 25 11:18:57 c-cactus systemd[1]: Started Accounts Service. Nov 25 11:18:57 c-cactus systemd[1]: Started Daemon for power management. Nov 25 11:18:57 c-cactus systemd[1]: Starting User Manager for UID 1000... Nov 25 11:18:57 c-cactus systemd[1]: Starting Login Service... Nov 25 11:18:57 c-cactus systemd[1]: Started Hostname Service. Nov 25 11:18:57 c-cactus systemd[1]: Started Login Service. Nov 25 11:18:57 c-cactus systemd[1]: Started User Manager for UID 1000. Nov 25 11:18:58 c-cactus systemd[1]: Starting Session c1 of user abe. Nov 25 11:18:58 c-cactus systemd[1]: Started Session c1 of user abe. Nov 25 11:18:59 c-cactus systemd[1]: Starting LSB: start or stop the WINGs display manager... Nov 25 11:18:59 c-cactus systemd[1]: Started LSB: start or stop the WINGs display manager. Nov 25 11:18:59 c-cactus systemd[1]: Starting X11 Display Manager. Nov 25
Bug#770937: needrestart: Kills wdm session on system running systemd g (maybe via dbus restart)
Hi Thomas,
Thomas Liske wrote:
restarting dbus kills any graphical user session.
I wouldn't say that. But it's probably true for most modern desktop
environments and systemd -- unfortunately.
in the (used) default config, systemd restarted dbus:
Are you able to kill your X session by calling `systemctl
daemon-reexec` manually?
Nope, can still work in that session. :-)
Nov 25 11:18:57 c-cactus systemd[1]: Activated swap /dev/…/swap.
At this point `systemctl reexec` should have been finished.
That's also where the log ended after the manual systemctl
daemon-reexec.
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Accounts Service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Bluetooth service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Regular background program
processing daemon...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Regular background program
processing daemon...
Nov 25 11:18:57 c-cactus systemd[1]: Started Regular background program
processing daemon.
Nov 25 11:18:57 c-cactus systemd[1]: Stopping D-Bus System Message Bus...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Accounts Service...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Bluetooth service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping OpenBSD Secure Shell server...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Journal Service...
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Default.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Default.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Basic System.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Basic System.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Paths.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Paths.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Timers.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Timers.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Sockets.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Sockets.
Nov 25 11:18:57 c-cactus systemd[1641]: Starting Shutdown.
Nov 25 11:18:57 c-cactus systemd[1641]: Reached target Shutdown.
Nov 25 11:18:57 c-cactus systemd[1641]: Starting Exit the Session...
Nov 25 11:18:57 c-cactus systemd[1]: Starting OpenBSD Secure Shell server...
Nov 25 11:18:57 c-cactus systemd[1]: Started OpenBSD Secure Shell server.
Nov 25 11:18:57 c-cactus systemd[1641]: Received SIGRTMIN+24 from PID 12082
(kill).
Nov 25 11:18:57 c-cactus systemd[1]: Started Trigger Flushing of Journal to
Persistent Storage.
Nov 25 11:18:57 c-cactus systemd[1]: Starting Daemon for power management...
Nov 25 11:18:57 c-cactus systemd[1]: Starting LSB: Starts and stops Wicd...
Nov 25 11:18:57 c-cactus systemd[1]: Starting D-Bus System Message Bus...
Nov 25 11:18:57 c-cactus systemd[1]: Started D-Bus System Message Bus.
Nov 25 11:18:57 c-cactus systemd[1]: Started Bluetooth service.
Nov 25 11:18:57 c-cactus systemd[1]: Starting Hostname Service...
Nov 25 11:18:57 c-cactus systemd[1]: Started Accounts Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started Daemon for power management.
Nov 25 11:18:57 c-cactus systemd[1]: Starting User Manager for UID 1000...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Login Service...
Nov 25 11:18:57 c-cactus systemd[1]: Started Hostname Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started Login Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started User Manager for UID 1000.
Nov 25 11:18:58 c-cactus systemd[1]: Starting Session c1 of user abe.
Nov 25 11:18:58 c-cactus systemd[1]: Started Session c1 of user abe.
Nov 25 11:18:59 c-cactus systemd[1]: Starting LSB: start or stop the WINGs
display manager...
Nov 25 11:18:59 c-cactus systemd[1]: Started LSB: start or stop the WINGs
display manager.
Nov 25 11:18:59 c-cactus systemd[1]: Starting X11 Display Manager.
Nov 25 11:18:59 c-cactus systemd[1]: Reached target X11 Display Manager.
It might be an dependency issue... X11 Display Manager depends on
something that needrestart did suggest to restart.
Compared to modern login managers, wdm's dependencies are rather lightweight:
Depends: libc6 (= 2.11), libpam0g (= 0.99.7.1), libselinux1 (=
1.32), libwings2 (= 0.95.0), libwraster3 (= 0.95.0), libwutil2 (=
0.95.0), libx11-6, libxau6, libxdmcp6, libxinerama1, libxmu6, debconf
(= 1.5.20) | debconf-2.0, libpam-runtime (= 0.76-13.1),
libpam-modules, psmisc, x11-apps, x11-common, x11-xserver-utils,
x11-utils
Are you able to remember which service were selected?
Not at all, because I had set $nrconf{restart} = 'a' and systemd
doesn't care to tell me what it does -- compared to needrestart on a
system with good old sysvinit. Meh.
If you did not run needrestart in the meanwhile you might find your
selection still in debconf:
$ grep -A 8 'needrestart/ui-query_pkgs$' /var/cache/debconf/config.dat
This looks very suspicious:
→ grep -A 8 'needrestart/ui-query_pkgs$'
Bug#770937: needrestart: Kills wdm session on system running systemd g (maybe via dbus restart)
Re,
On 11/25/2014 08:53 PM, Axel Beckert wrote:
Hi Thomas,
Thomas Liske wrote:
restarting dbus kills any graphical user session.
I wouldn't say that. But it's probably true for most modern desktop
environments and systemd -- unfortunately.
I'm afraid so!
in the (used) default config, systemd restarted dbus:
Are you able to kill your X session by calling `systemctl
daemon-reexec` manually?
Nope, can still work in that session. :-)
Phew!
Nov 25 11:18:57 c-cactus systemd[1]: Activated swap /dev/…/swap.
At this point `systemctl reexec` should have been finished.
That's also where the log ended after the manual systemctl
daemon-reexec.
OK
It might be an dependency issue... X11 Display Manager depends on
something that needrestart did suggest to restart.
Compared to modern login managers, wdm's dependencies are rather lightweight:
Depends: libc6 (= 2.11), libpam0g (= 0.99.7.1), libselinux1 (=
1.32), libwings2 (= 0.95.0), libwraster3 (= 0.95.0), libwutil2 (=
0.95.0), libx11-6, libxau6, libxdmcp6, libxinerama1, libxmu6, debconf
(= 1.5.20) | debconf-2.0, libpam-runtime (= 0.76-13.1),
libpam-modules, psmisc, x11-apps, x11-common, x11-xserver-utils,
x11-utils
I meant the systemd services dependencies. I did just take a short look
on my local systemd+kdm+kde environment... but I've no idea how it works
at all :-(
Are you able to remember which service were selected?
Not at all, because I had set $nrconf{restart} = 'a' and systemd
doesn't care to tell me what it does -- compared to needrestart on a
system with good old sysvinit. Meh.
If you did not run needrestart in the meanwhile you might find your
selection still in debconf:
$ grep -A 8 'needrestart/ui-query_pkgs$' /var/cache/debconf/config.dat
This looks very suspicious:
Value: dbus.service, lxc
Variables:
PKGS = dbus.service, lxc, wdm.service
Value: dbus.service, lxc
PKGS = dbus.service, lxc, wdm.service
So why the heck are there wdm and dbus listed?
The Value field it the important one, the PKGS variable is just used
to build the list. If dbus was restarted this was the cause of killing
your session :-(
with only one exception:
→ cat /etc/needrestart/conf.d/abe.conf
#$nrconf{restart} = 'a';
$nrconf{ui} = 'NeedRestart::UI::stdio';
Maybe the problem is within the code path of the auto restart mode. This
might not be tested as extensive as the list mode... I'll need to dig
into it...
Thx HTH,
Thomas
--
:: WWW: http://fiasko-nw.net/~thomas/ ::
::: Jabber: xmpp:tho...@jabber.fiasko-nw.net :::
:: flickr: http://www.flickr.com/photos/laugufe/ ::
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#770937: needrestart: Kills wdm session on system running systemd g (maybe via dbus restart)
Processing commands for cont...@bugs.debian.org: tags 770937 upstream fixed-upstream Bug #770937 [needrestart] needrestart: Kills wdm session on system running systemd g (maybe via dbus restart) Added tag(s) upstream and fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 770937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770937: needrestart: Kills wdm session on system running systemd g (maybe via dbus restart)
tags 770937 upstream fixed-upstream
thanks
Re,
On 11/25/2014 09:17 PM, Thomas Liske wrote:
Are you able to remember which service were selected?
Not at all, because I had set $nrconf{restart} = 'a' and systemd
doesn't care to tell me what it does -- compared to needrestart on a
system with good old sysvinit. Meh.
If you did not run needrestart in the meanwhile you might find your
selection still in debconf:
$ grep -A 8 'needrestart/ui-query_pkgs$' /var/cache/debconf/config.dat
This looks very suspicious:
sorry, I was a little bit confused... the debconf template
needrestart/ui-query_pkgs is not used in auto mode but only in
interactive mode.
Maybe the problem is within the code path of the auto restart mode. This
might not be tested as extensive as the list mode... I'll need to dig
auto
into it...
...and I've found the bug - the override_rc option was never evaluated
in auto mode. Upstream have been patched to respect the defno and
override_rc settings in auto mode, too.
https://github.com/liske/needrestart/commit/62d07dc271a89cf1584cc3ee2a13b4fae47dc6bc
Sorry for the trouble caused by killing your sessions.
HTH,
Thomas
--
:: WWW: http://fiasko-nw.net/~thomas/ ::
::: Jabber: xmpp:tho...@jabber.fiasko-nw.net :::
:: flickr: http://www.flickr.com/photos/laugufe/ ::
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770937: needrestart: Kills wdm session on system running systemd g (maybe via dbus restart)
Hi Thomas, looking forward to get that fix soonish as a Debian package. :-) Thomas Liske wrote: sorry, I was a little bit confused... the debconf template needrestart/ui-query_pkgs is not used in auto mode but only in interactive mode. Ah, ok. So that stuff was probably older. Maybe the problem is within the code path of the auto restart mode. This might not be tested as extensive as the list mode... I'll need to dig auto into it... No, I think list was correct here: not … tested as extensive as the list mode refers to the auto mode. :-) BTW: It will be tested. I switch nearly all my machines into auto mode as list mode usually made sane choices... ...and I've found the bug - the override_rc option was never evaluated in auto mode. I'm surprised. I'd have really expected that this is completely independent of the actually mode of interaction. I thought modes are just either ask what to restart or just restart those which would be checked by default without asking. That's also the reason why I didn't mention my local config file initially as I expected that these symptoms are _only_ influenced by changing the blacklists -- which I didn't change. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
