Your message dated Wed, 11 Sep 2013 00:53:28 +0200 with message-id <20130910225328.GA6623@stro.at> and subject line Re: plymouth: abuse /var/tmp for initramfs creation has caused the Debian Bug report #680669, regarding abuse /var/tmp for initramfs creation 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 owner@bugs.debian.org immediately.) -- 680669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680669 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: plymouth: abuse /var/tmp for initramfs creation
- From: Luca Capello <luca@pca.it>
- Date: Sat, 07 Jul 2012 15:48:39 -0600
- Message-id: <87629z2qfc.fsf@gismo.pca.it>
Package: plymouth Version: 0.8.5.1-4 Severity: important File: /usr/share/initramfs-tools/hooks/plymouth User: events@debian.org Usertags: events-hardware Hi there! I would like to test plymouth with BabelBox, both for the Debian Events Box and to have an automatic way to have everything under KVM, but during some tests on my sid I found out the following: ===== root@gismo:/home/luca# plymouth-set-default-theme -R details update-initramfs: Generating /boot/initrd.img-3.4-trunk-amd64 [...] + [ -f /usr/lib/x86_64-linux-gnu/plymouth//details.so ] + [ -d /var/tmp/mkinitramfs_vv7Yug//usr/lib/x86_64-linux-gnu/plymouth//details.so ] + [ -e /var/tmp/mkinitramfs_vv7Yug//usr/lib/x86_64-linux-gnu/plymouth//details.so ] + mkdir -p /var/tmp/mkinitramfs_vv7Yug//usr/lib/x86_64-linux-gnu/plymouth/ [...] + copy_exec /usr/lib/x86_64-linux-gnu/plymouth//label.so + local src target x nonoptlib + local libname dirname + src=/usr/lib/x86_64-linux-gnu/plymouth//label.so + target=/usr/lib/x86_64-linux-gnu/plymouth//label.so + [ -f /usr/lib/x86_64-linux-gnu/plymouth//label.so ] + return 1 E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1. update-initramfs: failed for /boot/initrd.img-3.4-trunk-amd64 with 1. root@gismo:/home/luca# ls -l /var/tmp/ total 100 -rw------- 1 luca luca 12288 Jun 29 2011 dbus-V0lD9fpsi6,guid=4316c7131d30a5a150c18f0400000049").swp drwx------ 2 118 nogroup 4096 Jul 3 04:44 kdecache-kdm drwxr-xr-x 11 root root 4096 Jul 7 12:18 mkinitramfs_5hcOg0 drwxr-xr-x 10 root root 4096 Jul 7 14:09 mkinitramfs_88CTpg drwxr-xr-x 12 root root 4096 Jul 7 12:56 mkinitramfs_8Nkrz3 drwxr-xr-x 11 root root 4096 Jul 7 12:52 mkinitramfs_aDlFpt drwxr-xr-x 11 root root 4096 Jul 7 12:19 mkinitramfs_bO6SLn drwxr-xr-x 11 root root 4096 Jul 7 15:22 mkinitramfs_CQwieF drwxr-xr-x 11 root root 4096 Jul 7 12:20 mkinitramfs_hDw7Yu drwxr-xr-x 12 root root 4096 Jul 7 12:56 mkinitramfs_HSYvgo drwxr-xr-x 12 root root 4096 Jul 7 12:53 mkinitramfs_i0fHp0 drwxr-xr-x 11 root root 4096 Jul 7 12:20 mkinitramfs_iYMAme drwxr-xr-x 12 root root 4096 Jul 7 12:50 mkinitramfs_K9zl2Q drwxr-xr-x 11 root root 4096 Jul 7 12:58 mkinitramfs_KCWmaK drwxr-xr-x 11 root root 4096 Jul 7 12:28 mkinitramfs_OD8Mfy -rw------- 1 root root 0 Jul 7 12:50 mkinitramfs-OL_1omUSP -rw------- 1 root root 0 Jul 7 12:20 mkinitramfs-OL_2nOirQ -rw------- 1 root root 0 Jul 7 12:58 mkinitramfs-OL_9j1jYJ -rw------- 1 root root 0 Jul 7 15:38 mkinitramfs-OL_BO4Jl2 -rw------- 1 root root 0 Jul 7 12:40 mkinitramfs-OL_dyLpZr -rw------- 1 root root 0 Jul 7 12:18 mkinitramfs-OL_e6gU22 -rw------- 1 root root 0 Jul 7 12:20 mkinitramfs-OL_EO1rvi -rw------- 1 root root 0 Jul 7 15:22 mkinitramfs-OL_IbzEgh -rw------- 1 root root 0 Jul 7 14:09 mkinitramfs-OL_irryDp -rw------- 1 root root 0 Jul 7 14:09 mkinitramfs-OL_J0Kg2W -rw------- 1 root root 0 Jul 7 12:53 mkinitramfs-OL_k0cG4R -rw------- 1 root root 0 Jul 7 12:52 mkinitramfs-OL_k1BFe0 -rw------- 1 root root 0 Jul 7 12:51 mkinitramfs-OL_kk0xj0 -rw------- 1 root root 0 Jul 7 12:28 mkinitramfs-OL_lOiWtj -rw------- 1 root root 0 Jun 30 20:01 mkinitramfs-OL_mNDfyL -rw------- 1 root root 0 Jun 30 20:02 mkinitramfs-OL_Rfupob -rw------- 1 root root 0 Jul 7 12:19 mkinitramfs-OL_t9VJEu -rw------- 1 root root 0 Jul 7 12:53 mkinitramfs-OL_tt3J96 -rw------- 1 root root 0 Jul 7 12:35 mkinitramfs-OL_UCyTcs -rw------- 1 root root 0 Jul 7 12:56 mkinitramfs-OL_UzXrE3 -rw------- 1 root root 0 Jul 7 12:55 mkinitramfs-OL_yXDmxu drwxr-xr-x 12 root root 4096 Jul 7 12:40 mkinitramfs_p8OPK5 drwxr-xr-x 12 root root 4096 Jul 7 12:35 mkinitramfs_tNq6gd drwxr-xr-x 11 root root 4096 Jul 7 12:51 mkinitramfs_UBCvfY drwxr-xr-x 11 root root 4096 Jul 7 15:38 mkinitramfs_vv7Yug drwxr-xr-x 12 root root 4096 Jul 7 12:53 mkinitramfs_xfLuy0 drwxr-xr-x 10 root root 4096 Jul 7 14:09 mkinitramfs_YBp8eU drwxr-xr-x 11 root root 4096 Jun 30 20:01 mkinitramfs_YmevZI drwxr-xr-x 11 root root 4096 Jun 30 20:02 mkinitramfs_ZxDO0D root@gismo:/home/luca# du -sh /var/tmp/mkinitramfs_* 35M /var/tmp/mkinitramfs_5hcOg0 36M /var/tmp/mkinitramfs_88CTpg 35M /var/tmp/mkinitramfs_8Nkrz3 35M /var/tmp/mkinitramfs_aDlFpt 35M /var/tmp/mkinitramfs_bO6SLn 35M /var/tmp/mkinitramfs_CQwieF 35M /var/tmp/mkinitramfs_hDw7Yu 35M /var/tmp/mkinitramfs_HSYvgo 35M /var/tmp/mkinitramfs_i0fHp0 35M /var/tmp/mkinitramfs_iYMAme 35M /var/tmp/mkinitramfs_K9zl2Q 35M /var/tmp/mkinitramfs_KCWmaK 35M /var/tmp/mkinitramfs_OD8Mfy 35M /var/tmp/mkinitramfs_p8OPK5 35M /var/tmp/mkinitramfs_tNq6gd 35M /var/tmp/mkinitramfs_UBCvfY 36M /var/tmp/mkinitramfs_vv7Yug 35M /var/tmp/mkinitramfs_xfLuy0 36M /var/tmp/mkinitramfs_YBp8eU 35M /var/tmp/mkinitramfs_YmevZI 35M /var/tmp/mkinitramfs_ZxDO0D root@gismo:/home/luca# du -sh /var/tmp/ 740M /var/tmp/ root@gismo:/home/luca# rm -rf /var/tmp/mkinitramfs_* root@gismo:/home/luca# du -sh /var/tmp/ 11M /var/tmp/ root@gismo:/home/luca# ===== Can we please use /tmp instead? I guess that /var/tmp is used so in case of any error the future initramfs is available for debugging. However, I do not see why this should be kept over reboots. Thx, bye, Gismo / Luca -- System Information: Debian Release: wheezy/sid Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-amd64 (SMP w/2 CPU cores) 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 plymouth depends on: ii initramfs-tools 0.106 ii libc6 2.13-34 ii multiarch-support 2.13-34 plymouth recommends no packages. Versions of packages plymouth suggests: pn desktop-base <none> pn plymouth-drm <none> -- Configuration Files: /etc/plymouth/plymouthd.conf changed: [Daemon] Theme=details -- no debconf informationAttachment: pgpMHIIOfnMKw.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: 680669-done@bugs.debian.org
- Subject: Re: plymouth: abuse /var/tmp for initramfs creation
- From: maximilian attems <maks@stro.at>
- Date: Wed, 11 Sep 2013 00:53:28 +0200
- Message-id: <20130910225328.GA6623@stro.at>
Sorry for the late reply. /var/tmp is used as it is usually on a bigger partition than /tmp. A failed attempt is kept on disc to have it debuggable. E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1. update-initramfs: failed for /boot/initrd.img-3.4-trunk-amd64 with 1. No idea why plymouth fails for you, if you can reproduce it with a Version newer than 0.8.5.1-4 please report it again against plymouth. Closing the initramfs-tools "bug" as this are design decisions. Thank you for your report. -- maks
--- End Message ---