Package: upgrade-reports
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
A simple dist-upgrade:
$ sudo apt-get update
$ sudo apt-get dist-upgrade
* What was the outcome of this action?
pm-powersave called journalnal-commit which called mount which called
mount.crypt which called mount which called mount.crypt which called mount ...
until ten thousands instances of mount and mount.crypt were started, before I
could call "chmod -x mount"
* What outcome did you expect instead?
An updated system
* Some files:
$ cat /etc/security/pam_mount.conf.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE pam_mount SYSTEM "pam_mount.conf.xml.dtd">
<!--
See pam_mount.conf(5) for a description.
-->
<pam_mount>
<!-- debug should come before everything else,
since this file is still processed in a single pass
from top-to-bottom -->
<!-- debug enable="1" / -->
<!-- Volume definitions -->
<!-- pam_mount parameters: General tunables -->
<!--
<luserconf name=".pam_mount.conf.xml" />
-->
<volume user="cryptuser" fstype="crypt" path="/dev/sda7"
mountpoint="/home/crypt" />
<!-- Note that commenting out mntoptions will give you the defaults.
You will need to explicitly initialize it with the empty string
to reset the defaults to nothing. -->
<mntoptions
allow="nosuid,nodev,loop,encryption,fsck,nonempty,allow_root,allow_other" />
<!--
<mntoptions deny="suid,dev" />
<mntoptions allow="*" />
<mntoptions deny="*" />
-->
<mntoptions require="nosuid,nodev" />
<logout wait="0" hup="0" term="0" kill="0" />
<!-- pam_mount parameters: Volume-related -->
<mkmountpoint enable="1" remove="true" />
</pam_mount>
$ cat /etc/pam.d/gdm
#%PAM-1.0
#auth requisite pam_nologin.so
#auth required pam_env.so readenv=1
#auth required pam_env.so readenv=1 envfile=/etc/default/locale
@include common-auth
#auth optional pam_gnome_keyring.so
@include common-account
#session required pam_limits.so
@include common-session
#session optional pam_gnome_keyring.so auto_start
@include common-password
#@include common-mount
$ cat /etc/crypttab
# <target name> <source device> <key file> <options>
# /dev/mapper/crypt-home /dev/sda7 none luks,noauto
cswap /dev/sda5 /dev/urandom swap
/dev/mapper/crypt-home UUID=<you don't need this> none luks,noauto
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1 / ext3 errors=remount-ro 0 1
UUID=<you don't need this> / ext3 errors=remount-ro 0
1
# /dev/sda5 none swap sw 0 0
#UUID=<you don't need this> none swap sw 0
0
/dev/mapper/cswap none swap sw
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
# /dev/sda6 /mnt/backup ext3 user,noauto 0 0
UUID=e7515235-dcf3-4e1e-8e4f-fb557736e757 /mnt/backup ext3
user,noauto 0 0
# /dev/sda7 /home/crypt crypt user,noauto
UUID=<you don't need this> /home/crypt crypt user,noauto
tmpfs /ramdisk tmpfs size=300M,user,noauto 0 0
$ vdir -R /etc/pm/
/etc/pm/:
insgesamt 12
drwxr-xr-x 2 root root 4096 Aug 3 2008 config.d
drwxr-xr-x 2 root root 4096 Aug 3 2008 power.d
drwxr-xr-x 2 root root 4096 Nov 17 22:15 sleep.d
/etc/pm/config.d:
insgesamt 0
/etc/pm/power.d:
insgesamt 0
/etc/pm/sleep.d:
insgesamt 8
-rwxr-xr-x 1 root root 580 Nov 9 09:25 10_unattended-upgrades-hibernate
-rwxr-xr-x 1 root root 1177 Mär 14 2011 novatel_3g_suspend
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
