Bug#702509: unattended-upgrades: does not run autonomously, even after it was enabled
control: -1 severity normal 2013/3/8 Arturo Moral amo...@gmail.com: This config was removed in version 0.79.5 and might not work at all: I'm currently using 0.79.4, therefore the config change does not affect me, right? You should not use it, 0.79.5 will migrate to testing on the following days. Anyway, my main issue is that the unattended upgrades don't run. If it would be only a config file problem, they would run but with no upgradable candidates. You didn't show that u-a doesn't work. From what we've seen so far it works as expected, maybe you need to investigate why Cron doesn't run?! Do you know for sure that there are packages to be upgraded? Running apt-get upgrade will tell you. If apt-get doesn't find packages to be upgraded, neither does u-a. Cheers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702509: unattended-upgrades: does not run autonomously, even after it was enabled
2013/3/7 g0to amo...@gmail.com:
-- Configuration Files:
/etc/apt/apt.conf.d/50unattended-upgrades changed:
// Automatically upgrade packages from these origin patterns
Unattended-Upgrade::Origins-Pattern {
// Codename based matching:
// This will follow the migration of a release through different
// archives (e.g. from testing to stable and later oldstable).
o=Debian,n=wheezy;
o=Debian,n=wheezy-updates;
o=Debian,n=wheezy-proposed-updates;
o=Debian,n=wheezy,l=Debian-Security;
This config was removed in version 0.79.5 and might not work at all:
- remove codename based matching example as this needs a newer
python-apt than available in wheezy, thanks to Russell Stuart
// Archive or Suite based matching:
// Note that this will silently match a different release after
// migration to the specified archive (e.g. testing becomes the
// new stable).
// o=Debian,a=stable;
// o=Debian,a=stable-updates;
// o=Debian,a=proposed-updates;
// origin=Debian,archive=stable,label=Debian-Security;
};
Usually this is what you need to enable, plus an extra line if you are
using testing or unstable.
Cheers
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692448: qemu: system crash on 'libaio1' removal
2012/11/6 Michael Tokarev m...@tls.msk.ru: On 06.11.2012 15:40, Teodor wrote: I've just had a system crash a few seconds after I removed 'libaio1 package (declared orphan by deborphan). What kind of crash? Crash of what, exactly? What you were running? Debian Linux 6.0 (amd64) on top of Xen 4.0 hypervisor. reboot system boot 2.6.32-5-xen-amd Tue Nov 6 02:59 - 05:01 (02:02) root pts/2vpn-120.DOMAIN Tue Nov 6 02:27 - crash (00:32) None of qemu-system or qemu-user binaries are linked with libaio. libaio1 is not used and hence not needed. Note that qemu package - against which you filed the bugreport - is a meta-package, it does not use any library at all. # aptitude why qemu i xen-qemu-dm-4.0 Depends qemu-system | qemu # aptitude why libaio1 i libvirt-bin Recommends qemu-kvm | qemu (= 0.9.1) p qemu-kvmDependslibaio1 Maybe qemu is not the right package, then which is the right pkg? On KVM systems this is not a problem because its a dependency of qemu-kvm. But on Xen systems (+libvirtd) this package is useless and 'qemu' is enough. Which package is useless? qemu-kvm is useless on a Xen hypervisor. xen-qemu-dm* packages are not relevant for qemu. Please describe your issue in a bit more details. Currently what you wrote makes no sense, sorry. Do you need more info? Cheers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692448: qemu: system crash on 'libaio1' removal
2012/11/6 Michael Tokarev m...@tls.msk.ru: So, can you start it again when libaio1 is NOT installed? Yes, I was able to start the VMs again after the libaio1 removal. I'm not sure about the full Xen system -- I can't test now. Cheers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682481: gnome-shell: epiphany shouldn't be the default browser
Didn't you forgot to add | www-browser in the Depends: line? Funny upgrade today with 121 new packages although I have at least two packages installed that provide www-browser. Cheers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679728: systemd: diversion removed in postinst, should be removed in preinst
2012/7/2 Tollef Fog Heen tfh...@err.no: That's quite odd. Can you please provide the output of «grep systemd /var/log/dpkg.log»? See below. I've reinstalled «systemd» this morning on my workstation. Cheers -- 2012-07-02 10:55:30 upgrade systemd-gui:i386 44-2 44-3 2012-07-02 10:55:30 status half-configured systemd-gui:i386 44-2 2012-07-02 10:55:30 status unpacked systemd-gui:i386 44-2 2012-07-02 10:55:30 status half-installed systemd-gui:i386 44-2 2012-07-02 10:55:30 status half-installed systemd-gui:i386 44-2 2012-07-02 10:55:30 status half-installed systemd-gui:i386 44-2 2012-07-02 10:55:30 status unpacked systemd-gui:i386 44-3 2012-07-02 10:55:30 status unpacked systemd-gui:i386 44-3 2012-07-02 10:55:31 upgrade libsystemd-daemon0:i386 44-2 44-3 2012-07-02 10:55:31 status half-configured libsystemd-daemon0:i386 44-2 2012-07-02 10:55:31 status unpacked libsystemd-daemon0:i386 44-2 2012-07-02 10:55:31 status half-installed libsystemd-daemon0:i386 44-2 2012-07-02 10:55:31 status half-installed libsystemd-daemon0:i386 44-2 2012-07-02 10:55:31 status unpacked libsystemd-daemon0:i386 44-3 2012-07-02 10:55:31 status unpacked libsystemd-daemon0:i386 44-3 2012-07-02 10:55:32 upgrade libsystemd-id128-0:i386 44-2 44-3 2012-07-02 10:55:32 status half-configured libsystemd-id128-0:i386 44-2 2012-07-02 10:55:32 status unpacked libsystemd-id128-0:i386 44-2 2012-07-02 10:55:32 status half-installed libsystemd-id128-0:i386 44-2 2012-07-02 10:55:32 status half-installed libsystemd-id128-0:i386 44-2 2012-07-02 10:55:32 status unpacked libsystemd-id128-0:i386 44-3 2012-07-02 10:55:32 status unpacked libsystemd-id128-0:i386 44-3 2012-07-02 10:55:33 upgrade libsystemd-journal0:i386 44-2 44-3 2012-07-02 10:55:33 status half-configured libsystemd-journal0:i386 44-2 2012-07-02 10:55:33 status unpacked libsystemd-journal0:i386 44-2 2012-07-02 10:55:33 status half-installed libsystemd-journal0:i386 44-2 2012-07-02 10:55:33 status half-installed libsystemd-journal0:i386 44-2 2012-07-02 10:55:33 status unpacked libsystemd-journal0:i386 44-3 2012-07-02 10:55:33 status unpacked libsystemd-journal0:i386 44-3 2012-07-02 10:55:34 upgrade libsystemd-login0:i386 44-2 44-3 2012-07-02 10:55:34 status half-configured libsystemd-login0:i386 44-2 2012-07-02 10:55:34 status unpacked libsystemd-login0:i386 44-2 2012-07-02 10:55:34 status half-installed libsystemd-login0:i386 44-2 2012-07-02 10:55:34 status half-installed libsystemd-login0:i386 44-2 2012-07-02 10:55:34 status unpacked libsystemd-login0:i386 44-3 2012-07-02 10:55:34 status unpacked libsystemd-login0:i386 44-3 2012-07-02 10:55:34 upgrade libpam-systemd:i386 44-2 44-3 2012-07-02 10:55:34 status half-configured libpam-systemd:i386 44-2 2012-07-02 10:55:35 status unpacked libpam-systemd:i386 44-2 2012-07-02 10:55:35 status half-installed libpam-systemd:i386 44-2 2012-07-02 10:55:35 status half-installed libpam-systemd:i386 44-2 2012-07-02 10:55:35 status half-installed libpam-systemd:i386 44-2 2012-07-02 10:55:35 status unpacked libpam-systemd:i386 44-3 2012-07-02 10:55:35 status unpacked libpam-systemd:i386 44-3 2012-07-02 10:55:35 upgrade systemd:i386 44-2 44-3 2012-07-02 10:55:35 status half-configured systemd:i386 44-2 2012-07-02 10:55:36 status unpacked systemd:i386 44-2 2012-07-02 10:55:36 status half-installed systemd:i386 44-2 2012-07-02 10:55:36 status half-installed systemd:i386 44-2 2012-07-02 10:55:37 status half-installed systemd:i386 44-2 2012-07-02 10:55:37 status unpacked systemd:i386 44-3 2012-07-02 10:55:37 status unpacked systemd:i386 44-3 2012-07-02 11:11:40 status unpacked libpam-systemd:i386 44-3 2012-07-02 11:11:41 remove libpam-systemd:i386 44-3 none 2012-07-02 11:11:41 status half-installed libpam-systemd:i386 44-3 2012-07-02 11:11:41 status half-installed libpam-systemd:i386 44-3 2012-07-02 11:11:41 status config-files libpam-systemd:i386 44-3 2012-07-02 11:11:41 status config-files libpam-systemd:i386 44-3 2012-07-02 11:11:41 status config-files libpam-systemd:i386 44-3 2012-07-02 11:11:41 status not-installed libpam-systemd:i386 none 2012-07-02 11:11:42 status unpacked systemd-gui:i386 44-3 2012-07-02 11:11:42 remove systemd-gui:i386 44-3 none 2012-07-02 11:11:42 status half-installed systemd-gui:i386 44-3 2012-07-02 11:11:42 status half-installed systemd-gui:i386 44-3 2012-07-02 11:11:42 status config-files systemd-gui:i386 44-3 2012-07-02 11:11:42 status config-files systemd-gui:i386 44-3 2012-07-02 11:11:42 status config-files systemd-gui:i386 44-3 2012-07-02 11:11:42 status not-installed systemd-gui:i386 none 2012-07-02 11:11:42 status unpacked systemd:i386 44-3 2012-07-02 11:11:42 remove systemd:i386 44-3 none 2012-07-02 11:11:42 status half-installed systemd:i386 44-3 2012-07-02 11:11:42 status half-installed systemd:i386 44-3 2012-07-02 11:11:43 status config-files systemd:i386 44-3 2012-07-02 11:11:43 purge systemd:i386 44-3 none 2012-07-02 11:11:43 status config-files systemd:i386 44-3 2012-07-02 11:11:43 status config-files systemd:i386
Bug#679728: systemd: diversion removed in postinst, should be removed in preinst
2012/7/3 Tollef Fog Heen tfh...@err.no: Ah, it looks like it never actually got to the configure step of systemd. Does that sound correct, and is the diversion correctly removed now? If not, could you please try downgrading to 44-2 and then upgrading and verifying that the diversion is gone? 1) On package removal (44-3) the diversion is still there. root@frost:~# ls -l /lib/lsb/ total 16 drwxr-xr-x 2 root root 4096 Jul 3 12:29 init-functions.d -rw-r--r-- 1 root root 11433 May 30 17:01 init-functions.systemd root@frost:~# dpkg -S /lib/lsb/init-functions.systemd diversion by systemd from: /lib/lsb/init-functions diversion by systemd to: /lib/lsb/init-functions.systemd ii libsystemd-daemon0:i 44-3i386 ii libsystemd-login0:i3 44-3i386 un systemd none 2) I've downgraded «libsystemd-daemon0 libsystemd-login0» to version 44-2 and installed again «systemd» (all 44-2 via some APT pin). Selecting previously unselected package systemd. Unpacking systemd (from .../archives/systemd_44-2_i386.deb) ... Leaving 'diversion of /lib/lsb/init-functions to /lib/lsb/init-functions.systemd by systemd' The result is that now I have a «/lib/lsb/init-functions» file back (with different content than init-functions.systemd). root@frost:~# ls -l /lib/lsb/ total 20 -rw-r--r-- 1 root root 2370 Jun 5 23:53 init-functions drwxr-xr-x 2 root root 4096 Jul 3 12:29 init-functions.d -rw-r--r-- 1 root root 11433 May 30 17:01 init-functions.systemd 3) Removed APT pin and upgrade. Setting up systemd (44-3) ... Removing 'diversion of /lib/lsb/init-functions to /lib/lsb/init-functions.systemd by systemd' Setting up libpam-systemd:i386 (44-3) ... Now the content is different: -rw-r--r-- 1 root root 11433 May 30 17:01 init-functions drwxr-xr-x 2 root root 4096 Jul 3 12:40 init-functions.d The diversion is gone: lsb-base: /lib/lsb/init-functions I have no clue how previously there was no «init-functions» file on the system. This morning I had to rescue the system due to many many init.d scripts failing because of this. A quickly fixed it by copying the init-functions.systemd file. Cheers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679728: systemd: diversion removed in postinst, should be removed in preinst
Diversion is not removed at all on package removal: | root@frost:~# ls -hl /lib/lsb/ | total 16K | drwxr-xr-x 2 root root 4.0K Jul 2 11:11 init-functions.d | -rw-r--r-- 1 root root 12K May 30 17:01 init-functions.systemd | root@frost:~# dpkg -S /lib/lsb/init-functions.d | lsb-base: /lib/lsb/init-functions.d | root@frost:~# dpkg -S /lib/lsb/init-functions.systemd | diversion by systemd from: /lib/lsb/init-functions | diversion by systemd to: /lib/lsb/init-functions.systemd | | root@frost:~# dpkg -l '*systemd*' | ii libsystemd-daemon0:i 44-3i386 | ii libsystemd-login0:i3 44-3i386 | un systemd none Cheers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679728: systemd: diversion removed in postinst, should be removed in preinst
2012/7/2 Tollef Fog Heen tfh...@err.no: Did you upgrade to 44-3 before removing it or not? Yes, I've upgraded almost all packages (including systemd) and then reported Bug#679873: lsb-base: Can't open /lib/lsb/init-functions. Later I've uninstalled systemd packages to work around the problem, but I've discovered that systemd removal is not enough. Cheers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673185: gnome-shell: segfault in libaccountsservice.so.0.0.0
By following the gdb example below I've obtained a (different) backtrace by unplugging the power cord from laptop. This is the voluntary trigger of this bug for me. BTW, this is now a problem for those that use systemd as well. Up to version 0.6.21-1, when using systemd init, gnome-shell did not crash or respawn itself. Thanks 2012/6/10 ALLurGroceries allurgrocer...@gmail.com: It's not convenient, but switching to another tty, e.g. ctrl+alt+f1 and then running these commands make the desktop usable again for me without having to restart gdm: killall -9 gnome-shell gnome-shell --display :0 disown This works but not completely. For example I don't have any theme, many buttons are not displayed (i.e. retext), non-ASCII characters are not displayed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673185: gnome-shell: segfault in libaccountsservice.so.0.0.0
Attaching the file ... 2012/6/10 Teodor MICU mteo...@gmail.com: By following the gdb example below I've obtained a (different) backtrace by unplugging the power cord from laptop. This is the voluntary trigger of this bug for me. Starting program: /usr/bin/gnome-shell --replace --display :0 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffe443a700 (LWP 4411)] [Thread 0x7fffe443a700 (LWP 4411) exited] [New Thread 0x7fffe443a700 (LWP 4412)] [New Thread 0x7fffe3bb9700 (LWP 4414)] [New Thread 0x7fffe31b0700 (LWP 4415)] [New Thread 0x7fffde7a7700 (LWP 4417)] [New Thread 0x7fffddf86700 (LWP 4418)] Window manager warning: Failed to load theme Wasp: Failed to find a valid file for theme Wasp [New Thread 0x7fffd7be1700 (LWP 4430)] [New Thread 0x7fffcb84c700 (LWP 4437)] [New Thread 0x7fffc858b700 (LWP 4441)] [New Thread 0x7fffc7d8a700 (LWP 4470)] [New Thread 0x7fffc7589700 (LWP 4471)] [New Thread 0x7fffc6d88700 (LWP 4472)] [New Thread 0x7fffc6587700 (LWP 4473)] [New Thread 0x7fffc5d86700 (LWP 4474)] [New Thread 0x7fffc5585700 (LWP 4475)] [New Thread 0x7fffc4d84700 (LWP 4476)] [New Thread 0x7fffc4583700 (LWP 4477)] Window manager warning: Failed to load theme Wasp: Failed to find a valid file for theme Wasp [Thread 0x7fffcb84c700 (LWP 4437) exited] [Thread 0x7fffc7589700 (LWP 4471) exited] [Thread 0x7fffc7d8a700 (LWP 4470) exited] [Thread 0x7fffc4d84700 (LWP 4476) exited] [Thread 0x7fffc5585700 (LWP 4475) exited] [Thread 0x7fffd7be1700 (LWP 4430) exited] [Thread 0x7fffc5d86700 (LWP 4474) exited] [Thread 0x7fffc6587700 (LWP 4473) exited] [Thread 0x7fffc4583700 (LWP 4477) exited] [New Thread 0x7fffc4583700 (LWP 4501)] [Thread 0x7fffc4583700 (LWP 4501) exited] Initializing nautilus-gdu extension ** (nautilus:4500): CRITICAL **: nautilus_menu_provider_get_background_items: assertion `NAUTILUS_IS_MENU_PROVIDER (provider)' failed [New Thread 0x7fffc4583700 (LWP 4514)] [New Thread 0x7fffc5d86700 (LWP 4515)] [New Thread 0x7fffc6587700 (LWP 4516)] [New Thread 0x7fffd7be1700 (LWP 4517)] [Thread 0x7fffc5d86700 (LWP 4515) exited] [Thread 0x7fffd7be1700 (LWP 4517) exited] [Thread 0x7fffc6d88700 (LWP 4472) exited] [Thread 0x7fffc6587700 (LWP 4516) exited] [Thread 0x7fffc4583700 (LWP 4514) exited] Shutting down nautilus-gdu extension [New Thread 0x7fffc4583700 (LWP 4767)] [New Thread 0x7fffc6587700 (LWP 4768)] [New Thread 0x7fffc6d88700 (LWP 4769)] [New Thread 0x7fffd7be1700 (LWP 4770)] [New Thread 0x7fffc7d8a700 (LWP 4771)] [New Thread 0x7fffc7589700 (LWP 4772)] [New Thread 0x7fffc5d86700 (LWP 4773)] [New Thread 0x7fffc5585700 (LWP 4774)] [New Thread 0x7fffc4d84700 (LWP 4775)] [New Thread 0x7fffc3d82700 (LWP 4776)] (gnome-shell:4407): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o) (gnome-shell:4407): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o) (gnome-shell:4407): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o) (gnome-shell:4407): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o) (gnome-shell:4407): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o) (gnome-shell:4407): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o) (gnome-shell:4407): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o) [Thread 0x7fffc7589700 (LWP 4772) exited] [Thread 0x7fffc4d84700 (LWP 4775) exited] [Thread 0x7fffc5d86700 (LWP 4773) exited] [Thread 0x7fffc6587700 (LWP 4768) exited] [Thread 0x7fffc6d88700 (LWP 4769) exited] [Thread 0x7fffc5585700 (LWP 4774) exited] [Thread 0x7fffc7d8a700 (LWP 4771) exited] [Thread 0x7fffd7be1700 (LWP 4770) exited] [Thread 0x7fffc3d82700 (LWP 4776) exited] [New Thread 0x7fffc3d82700 (LWP 4780)] [Thread 0x7fffc4583700 (LWP 4767) exited] [Thread 0x7fffc3d82700 (LWP 4780) exited] [New Thread 0x7fffc3d82700 (LWP 4832)] Program received signal SIGSEGV, Segmentation fault. 0x7fffd1b07070 in unload_new_session (new_session=0x14af990) at act-user-manager.c:965 965 act-user-manager.c: No such file or directory. (gdb) btfu full #0 0x7fffd1b07070 in unload_new_session (new_session=0x14af990) at act-user-manager.c:965 manager = 0x7fffd804e860 #1 0x7fffd1b09d40 in on_get_unix_user_finished (object=0x1502c50, result=0x1e0c820, data=0x14af990) at act-user-manager.c:1029 proxy = optimized out new_session = 0x14af990 error = 0x1537800 uid = optimized out #2 0x7fffef8b13f7 in g_simple_async_result_complete (simple=0x1e0c820) at /tmp/buildd/glib2.0-2.32.3/./gio
Bug#673185: gnome-shell: segfault error 4 in libaccountsservice.so.0.0.0
Although it appeared that the problem is fixed in version 0.6.21-2, after several hours the problem reoccurred. Indeed, the crash is not that frequent and most important I didn't had a full gnome-shell crash (it restarted automatically). I can still reproduce the problem by just unplugging the power cord, and in this case I get a gnome-shell crash that is not recoverable without restarting the session. Another thing to note is that the last crash was not caused by accountsservice but by glib library. Jun 3 21:11:11 r2 kernel: [17404.110514] gnome-shell[3262]: segfault at 2ce062c ip 7fc984153070 sp 7fffe6588400 error 4 in libaccountsservice.so.0.0.0[7fc98413d000+3b000] Jun 3 21:18:02 r2 kernel: [17815.183283] gnome-shell[3581] general protection ip:7fc96d2f00c9 sp:7fffdc3e57c0 error:0 in libglib-2.0.so.0.3200.3[7fc96d28b000+f5000] Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673185: gnome-shell: segfault error 4 in libaccountsservice.so.0.0.0
Apparently, using systemd avoids the crash in gnome-shell. This seems to be a good guess of Michael Biebl in bug#674433, so both problems appear to have the same root. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670097: gnome-shell: random hang causes data loss
severity 670097 important stop I had no other occurrence of this problem for 2-3 weeks. Because there is a workaround (kill gnome-shell) I downgraded the bug severity. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673185: gnome-shell: segfault error 4 in libaccountsservice.so.0.0.0
severity 673185 grave stop This problem affects gnome-shell even more. If I'm on battery the gnome-shell process is killed but not restarted afterwards. The only way to obtain a somehow stable X/gnome session was to restart gdm3. I still get the gnome-shell respawn but I least I'm not forced into logging out after login. Do you know a workaround for this problem? Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673185: Fwd: Bug#673185: gnome-shell: segfault error 4 in libaccountsservice.so.0.0.0
I just read [1] that this problem is caused by «cogl», should I reassign? I've had another occurrence one hour ago (log entries attached). These are all «ocgl» related packages currently installed: ii gir1.2-cogl-1.0 1.10.2-3 ii gir1.2-coglpango-1.0 1.10.2-3 ii libcogl-pango0:amd64 1.10.2-3 ii libcogl9:amd64 1.10.2-3 Thanks [1]: http://lists.debian.org/debian-release/2012/05/msg00103.html -- Forwarded message -- From: Teodor mteo...@gmail.com Date: 2012/5/16 Subject: Bug#673185: gnome-shell: segfault error 4 in libaccountsservice.so.0.0.0 To: Debian Bug Tracking System sub...@bugs.debian.org Package: gnome-shell Version: 3.2.2.1-4+b1 Severity: important Hi, It seems that the upgrade of accountsservice affected gnome-shell and causes gnome-session to restart itself (after kill 11). I've got two of these in less than 15 minutes after upgrade. (I've restarted gdm3 after the upgrade) At this point I cannot judge if this is serious or unpredictable. The first crash was after clicking on en - Show Keyboard Layout, which failed because 'gkbd-keyboard-display' cannot be found. Thanks -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=ro_RO.utf8, LC_CTYPE=ro_RO.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-1 ii gconf-service 3.2.5-1 ii gir1.2-accountsservice-1.0 0.6.18-3 ii gir1.2-atk-1.0 2.4.0-2 ii gir1.2-caribou-1.0 0.4.2-2 ii gir1.2-clutter-1.0 1.10.4-3 ii gir1.2-cogl-1.0 1.10.2-3 ii gir1.2-coglpango-1.0 1.10.2-3 ii gir1.2-folks-0.6 0.6.9-1 ii gir1.2-freedesktop 1.32.1-1 ii gir1.2-gconf-2.0 3.2.5-1 ii gir1.2-gdkpixbuf-2.0 2.26.1-1 ii gir1.2-gee-1.0 0.6.4-1 ii gir1.2-gkbd-3.0 3.4.0.2-1 ii gir1.2-glib-2.0 1.32.1-1 ii gir1.2-gmenu-3.0 3.2.0.1-2 ii gir1.2-gnomebluetooth-1.0 3.2.2-1 ii gir1.2-gtk-3.0 3.4.2-1 ii gir1.2-json-1.0 0.14.2-1 ii gir1.2-mutter-3.0 3.2.2-3 ii gir1.2-networkmanager-1.0 0.9.4.0-4 ii gir1.2-pango-1.0 1.30.0-1 ii gir1.2-polkit-1.0 0.105-1 ii gir1.2-soup-2.4 2.38.1-2 ii gir1.2-telepathyglib-0.12 0.18.1-2 ii gir1.2-telepathylogger-0.2 0.4.0-1 ii gir1.2-upowerglib-1.0 0.9.16-2 ii gjs 1.32.0-2 ii gnome-bluetooth 3.2.2-1 ii gnome-icon-theme-symbolic 3.4.0-2 ii gnome-settings-daemon 3.2.2-3 ii gnome-shell-common 3.2.2.1-4 ii gsettings-desktop-schemas 3.4.2-1 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-32 ii libcairo-gobject2 1.12.2-1 ii libcairo2 1.12.2-1 ii libcamel-1.2-29 3.2.2-3 ii libcanberra0 0.28-4 ii libclutter-1.0-0 1.10.4-3 ii libcogl-pango0 1.10.2-3 ii libcogl9 1.10.2-3 ii libcroco3 0.6.5-1 ii libdbus-1-3 1.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libebook-1.2-12 3.2.2-3 ii libecal-1.2-10 3.2.2-3 ii libedataserver-1.2-15 3.2.2-3 ii libedataserverui-3.0-1 3.2.2-3 ii libffi5 3.0.10-3 ii libfolks25 0.6.9-1 ii libgconf-2-4 3.2.5-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgee2 0.6.4-1 ii libgirepository-1.0-1 1.32.1-1 ii libgjs0b [libgjs0-libmozjs185-1.0] 1.32.0-2 ii libgl1-mesa-glx [libgl1] 8.0.2-2 ii libglib2.0-0 2.32.3-1 ii libgnome-desktop-3-2 3.4.2-1 ii libgnome-keyring0 3.4.1-1 ii libgnome-menu-3-0 3.2.0.1-2 ii
Bug#670097: gnome-shell: random hang causes data loss
2012/4/30 Michael Biebl bi...@debian.org: From time to time the Gnome shell will just freeze/hang and not accept any input How often is from time to time? Is this related to specific actions/circumstances, e.g. running an OpenGL game or something similar. At least once a week. Usually I run these applications: chromium, gnome-terminal, geany, retext, evince. (keyboard or mouse) and all I can do is restart gdm3 or the laptop. So the system does not lock up completely? I.e you can still switch to the console or access the system via e.g. SSH? Yes, the system is responsive but only Gnome is in a deep freeze. Even if I kill the front app from a tty the Gnome shell still displays it — all I can do is restart gdm3. Now I'm in the same situation and the latest changes made in a document I'm writting are going to be lost as I have no way to save them. If you are able to still access the system via the console, you might just kill the gnome-shell process, in which case it should be restarted. I'll do this next time. This is the second most annoying thing for me in Debian 7.0 (wheezy). I cannot tell what causes this, there is nothing in the syslog. I've attached the current process listing - maybe you can spot something. Unfortunately not. Is it possible, that you compile gnome-shell with debug symbols [1] and attach gdb when such a freeze occurs (if you are able to still access the system). Which Xorg driver do you use? Do those freezes also occur with the gnome-shell version from testing or is this something specific in 3.2.2.1-3? This is not specific to current version. I postponed this report until now just to test if Gnome 3.4 has the same problem. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670131: AttributeError: 'Version' object has no attribute 'policy_priority'
2012/4/24 Michael Vogt m...@debian.org: This should work with current sid but it will not work with older version of python-apt. I added a check into do the code to not crash if it runs with older versions of python-apt. Thanks. I realised after sending the report that severity grave was not justified due to the above reason. But still I think its an important fix for those that will want to use u-a 0.76 in squeeze for at least two more years. Afterwards, probably the check could be removed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669583: OSError: [Errno 1] Operation not permitted
2012/4/20 Michael Vogt m...@debian.org: Thanks for your bugreport. I fixed that now. I guess in your case it was already the session-leader for some reason (maybe because of systemd?). Yes, I use «systemd» but I don't know what being session-leader means. Most times u-a is run automatically by Cron, only when I check or debug some problem its run from a tty/pts console. Just for my curiosity, can you shortly explain what problem does os.setsid() fix or avoid? Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669583: OSError: [Errno 1] Operation not permitted
2012/4/20 Michael Vogt m...@debian.org: Sure, the setsid() call makes the process a session leader and removes the controlling tty. The rational is that if you run unattended-upgrades in a shell and then shutdown your tty goes away and unattended-upgrades gets killed even if its in the middle of a operation (like a upgrade). The unattended-upgrades-shutdown script is there to avoid that and keep the system running long enough to finish the upgrade - but for that unattended-upgrades must not be terminated by the tty going away. I think this protection is necessary only if U-A::Automatic-Reboot is set to true, right? If affirmative, why not wait until u-a finish the pkgs upgrade and then do the reboot? Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669583: OSError: [Errno 1] Operation not permitted
One important detail: I use «systemd», so this might not be a bug in U-A. Thaks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666523: libreoffice: upgrade to 1:3.5.2~rc2-1 utterly fails
2012/4/2 Rene Engelhard r...@debian.org:
On Mon, Apr 02, 2012 at 07:06:26PM +0300, Teodor MICU wrote:
I've had this problem on my homestation. I fixed it by setting
LANG=C and run the upgrade again. [..]
I *think* that this is just by chance. I also get a error with just C
the first time.
The error itself might be different, but if one fixes the root cause it will
probably fix both (the cannot determine language is misleading yes, but
afaict
it means I, unopkg and the UNO runtime environment don't work)...
Ok, based on previous experience I was brave to upgrade my laptop this
morning (~200 packages including libreoffice*). Indeed, it didn't work
flawlessly and the culprit is python-uno. And after this I recall
that on the homestation I had to remove the lock file manually and run
the upgrade again. So, it's about two things which make it work for
me: LANG=C and removal of lock file.
Note that I put on hold (via apt_preferences) all *cairo* packages to
avoid the ugliness I've got on my homestation after upgrade.
Thanks
Preparing to replace libreoffice-writer 1:3.4.6-2 (using
.../libreoffice-writer_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice-writer ...
Preparing to replace libreoffice-calc 1:3.4.6-2 (using
.../libreoffice-calc_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice-calc ...
Preparing to replace libreoffice-base 1:3.4.6-2 (using
.../libreoffice-base_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice-base ...
Preparing to replace libreoffice-base-core 1:3.4.6-2 (using
.../libreoffice-base-core_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice-base-core ...
Preparing to replace libreoffice-java-common 1:3.4.6-2 (using
.../libreoffice-java-common_1%3a3.5.2~rc2-1_all.deb) ...
Unpacking replacement libreoffice-java-common ...
Preparing to replace libreoffice-impress 1:3.4.6-2 (using
.../libreoffice-impress_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice-impress ...
Preparing to replace libreoffice-draw 1:3.4.6-2 (using
.../libreoffice-draw_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice-draw ...
Preparing to replace libreoffice-gtk 1:3.4.6-2 (using
.../libreoffice-gtk_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice-gtk ...
Preparing to replace libreoffice-gnome 1:3.4.6-2 (using
.../libreoffice-gnome_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice-gnome ...
Preparing to replace python-uno 1:3.4.6-2 (using
.../python-uno_1%3a3.5.2~rc2-1_amd64.deb) ...
ERROR: Cannot determine language!
Exception details:
(com.sun.star.uno.RuntimeException) { { Message = Cannot determine language!,
Context = (com.sun.star.uno.XInterface) @0 } }
unopkg failed.
terminate called after throwing an instance of
'com::sun::star::uno::RuntimeException'
/var/lib/dpkg/tmp.ci/preinst: line 11: 10033 Aborted
/usr/lib/libreoffice/program/unopkg sync -v --shared
-env:BUNDLED_EXTENSIONS_USER=file:///usr/lib/libreoffice/share/prereg/bundled
-env:UserInstallation=file://$INSTDIR
-env:UNO_JAVA_JFW_INSTALL_DATA=file://$d/share/config/javasettingsunopkginstall.xml
-env:JFW_PLUGIN_DO_NOT_CHECK_ACCESSIBILITY=1
dpkg: error processing
/var/cache/apt/archives/python-uno_1%3a3.5.2~rc2-1_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 134
configured to not write apport reports
Preparing to replace libreoffice-math
1:3.4.6-2 (using .../libreoffice-math_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice-math ...
Preparing to replace libreoffice-style-galaxy 1:3.4.6-2 (using
.../libreoffice-style-galaxy_1%3a3.5.2~rc2-1_all.deb) ...
Unpacking replacement libreoffice-style-galaxy ...
Preparing to replace libreoffice-style-tango 1:3.4.6-2 (using
.../libreoffice-style-tango_1%3a3.5.2~rc2-1_all.deb) ...
Unpacking replacement libreoffice-style-tango ...
Preparing to replace libreoffice-core 1:3.4.6-2 (using
.../libreoffice-core_1%3a3.5.2~rc2-1_amd64.deb) ...
rmdir: failed to remove `/var/lib/libreoffice/basis3.4': Directory not empty
Unpacking replacement libreoffice-core ...
Preparing to replace libreoffice-common 1:3.4.6-2 (using
.../libreoffice-common_1%3a3.5.2~rc2-1_all.deb) ...
Unpacking replacement libreoffice-common ...
Preparing to replace libreoffice 1:3.4.6-2 (using
.../libreoffice_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice ...
Preparing to replace libreoffice-filter-binfilter 1:3.4.6-2 (using
.../libreoffice-filter-binfilter_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice-filter-binfilter ...
Preparing to replace libreoffice-report-builder-bin 1:3.4.6-2 (using
.../libreoffice-report-builder-bin_1%3a3.5.2~rc2-1_amd64.deb) ...
Unpacking replacement libreoffice-report-builder-bin ...
Preparing to replace libreoffice-filter-mobiledev 1:3.4.6-2 (using
.../libreoffice-filter-mobiledev_1%3a3.5.2~rc2-1_all.deb) ...
Unpacking
Bug#666523: libreoffice: upgrade to 1:3.5.2~rc2-1 utterly fails
I've had this problem on my homestation. I fixed it by setting LANG=C and run the upgrade again. On this host I don't have en_US at all but only ro_RO.UTF-8. Hope this helps as this seemed to be a locale problem. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663541: error: alternative path /usr/share/java/swt-gtk-3.7.jar doesn't exist
Hi Debian Release team, The reported problem here appears to be for amd64 only because I was able to install the package libswt-gtk-3-java on i386. Also, looking at the build status page [1] I see that the amd64 package was uploaded directly by the maintainer. Is there any chance that scheduling a rebuild will fix this problem? Thanks [1]: https://buildd.debian.org/status/package.php?p=swt-gtk Selecting previously unselected package libswt-gtk-3-jni. (Reading database ... 284321 files and directories currently installed.) Unpacking libswt-gtk-3-jni (from .../libswt-gtk-3-jni_3.7.2-1_i386.deb) ... Selecting previously unselected package libswt-gtk-3-java. Unpacking libswt-gtk-3-java (from .../libswt-gtk-3-java_3.7.2-1_i386.deb) ... Setting up libswt-gtk-3-jni (3.7.2-1) ... Setting up libswt-gtk-3-java (3.7.2-1) ... update-alternatives: using /usr/share/java/swt-gtk-3.7.jar to provide /usr/share/java/swt.jar (swt.jar) in auto mode. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610333: unattended-upgrades: delaying hibernation until crob job finishes
Hi, There is absolutely *no* relation between unattended-upgrades and pm-utils. Any process running at the time of hibernation could consider itself just as important as unattended-upgrades, thereby preventing the I'm open for better suggestions but it seems preferable to delay hibernation than to potentially break the system. I propose to make this bug a wishlist for the ability to choose at the package installation both to enable U-A (default NO) and to disable hibernation until U-A will finish execution (default YES). I think we're covered for the case of running on low battery because 'cron' doesn't start until (direct) power returns. I personally don't recommend to disable hibernation, but there are people who do. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645919: unattended-upgrades: Unattended-upgrade in progress during shutdown, sleeping for 5s
2011/10/31 Michael Vogt m...@debian.org: I think I found the issue now and fixed it in trunk. The issue is that the init scripts are run on upgrade, but they really should only run on actual shutdown. Its a bit confusing why this is happening as the header of the init script says that it should not run in any runlevel and only stop in runlevel 0 6. So there might be a bug in the init system here as well. Which one do you use? I'm using the default init system in Debian: sysvinit + insserv. With the fix there will be one more hang on upgrade because the old (and buggy) prerm is run that will try to stop unattended-upgrades. But from that point on it should be fixed. Can be fixed by a targetted fix on Debian 6.0 squeeze? Could this create a problem on manual dist-upgrade from Debian 6.0 to 7.0? Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645919: unattended-upgrades: Unattended-upgrade in progress during shutdown, sleeping for 5s
I've forgot to attach the log file. Thanks -- 2011-10-31 06:15:32,683 INFO Initial blacklisted packages: 2011-10-31 06:15:32,684 INFO Starting unattended upgrades script 2011-10-31 06:15:32,684 INFO Allowed origins are: ['o=Debian,a=testing'] 2011-10-31 06:16:18,406 INFO Packages that are auto removed: '' 2011-10-31 06:16:18,406 INFO Packages that are upgraded: dctrl-tools dnsmasq dnsmasq-base ffmpeg gir1.2-clutter-1.0 gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gnome-icon-theme gstreamer0.10-plugins-ugly libavcodec53 libavdevice53 libavfilter2 libavformat53 libavutil51 libclutter-1.0-0 libclutter-1.0-common libcogl-common libcogl-pango0 libcogl5 libgadu3 libgladeui-2-0 libgladeui-common libgmp10 liborbit2 libpostproc52 libquicktime2 libswscale2 libvlc5 libvlccore4 mplayer rsync telepathy-salut unattended-upgrades vlc vlc-nox vlc-plugin-notify vlc-plugin-pulse x11-utils 2011-10-31 06:16:18,407 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg_2011-10-31_06:16:18.407517.log' 2011-10-31 06:40:04,438 ERROR Installing the upgrades failed! 2011-10-31 06:40:04,438 ERROR error message: 'installArchives() failed' 2011-10-31 06:40:04,438 ERROR dpkg returned a error! See '/var/log/unattended-upgrades/unattended-upgrades-dpkg_2011-10-31_06:16:18.407517.log' for details Extracting templates from packages: 76% Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 185575 files and directories currently installed.) Preparing to replace libavutil51 4:0.7.2-1 (using .../libavutil51_4%3a0.7.2-1+b1_amd64.deb) ... Unpacking replacement libavutil51 ... Selecting previously unselected package libx264-118. Unpacking libx264-118 (from .../libx264-118_2%3a0.118.2085+git8a62835-1_amd64.deb) ... Preparing to replace libavcodec53 4:0.7.2-1 (using .../libavcodec53_4%3a0.7.2-1+b1_amd64.deb) ... Unpacking replacement libavcodec53 ... Preparing to replace libavformat53 4:0.7.2-1 (using .../libavformat53_4%3a0.7.2-1+b1_amd64.deb) ... Unpacking replacement libavformat53 ... Preparing to replace libavdevice53 4:0.7.2-1 (using .../libavdevice53_4%3a0.7.2-1+b1_amd64.deb) ... Unpacking replacement libavdevice53 ... Preparing to replace libswscale2 4:0.7.2-1 (using .../libswscale2_4%3a0.7.2-1+b1_amd64.deb) ... Unpacking replacement libswscale2 ... Preparing to replace libavfilter2 4:0.7.2-1 (using .../libavfilter2_4%3a0.7.2-1+b1_amd64.deb) ... Unpacking replacement libavfilter2 ... Preparing to replace libcogl-pango0 1.8.0-1 (using .../libcogl-pango0_1.8.2-1_amd64.deb) ... Unpacking replacement libcogl-pango0 ... Preparing to replace libcogl5 1.8.0-1 (using .../libcogl5_1.8.2-1_amd64.deb) ... Unpacking replacement libcogl5 ... Preparing to replace gir1.2-coglpango-1.0 1.8.0-1 (using .../gir1.2-coglpango-1.0_1.8.2-1_amd64.deb) ... Unpacking replacement gir1.2-coglpango-1.0 ... Preparing to replace gir1.2-cogl-1.0 1.8.0-1 (using .../gir1.2-cogl-1.0_1.8.2-1_amd64.deb) ... Unpacking replacement gir1.2-cogl-1.0 ... Preparing to replace gir1.2-clutter-1.0 1.8.0-1 (using .../gir1.2-clutter-1.0_1.8.2-1_amd64.deb) ... Unpacking replacement gir1.2-clutter-1.0 ... Preparing to replace libclutter-1.0-0 1.8.0-1 (using .../libclutter-1.0-0_1.8.2-1_amd64.deb) ... Unpacking replacement libclutter-1.0-0 ... Preparing to replace libgmp10 2:5.0.2+dfsg-1 (using .../libgmp10_2%3a5.0.2+dfsg-2_amd64.deb) ... Unpacking replacement libgmp10 ... Preparing to replace libpostproc52 4:0.7.2-1 (using .../libpostproc52_4%3a0.7.2-1+b1_amd64.deb) ... Unpacking replacement libpostproc52 ... Preparing to replace dctrl-tools 2.18 (using .../dctrl-tools_2.19_amd64.deb) ... Unpacking replacement dctrl-tools ... Preparing to replace dnsmasq-base 2.58-3 (using .../dnsmasq-base_2.59-2_amd64.deb) ... Unpacking replacement dnsmasq-base ... Preparing to replace dnsmasq 2.58-3 (using .../dnsmasq_2.59-2_all.deb) ... Unpacking replacement dnsmasq ... Preparing to replace ffmpeg 4:0.7.2-1 (using .../ffmpeg_4%3a0.7.2-1+b1_amd64.deb) ... Unpacking replacement ffmpeg ... Preparing to replace gnome-icon-theme 3.2.0-1 (using .../gnome-icon-theme_3.2.1.2-1_all.deb) ... Unpacking replacement gnome-icon-theme ... Preparing to replace gstreamer0.10-plugins-ugly 0.10.18-3 (using .../gstreamer0.10-plugins-ugly_0.10.18-3+b1_amd64.deb) ... Unpacking replacement gstreamer0.10-plugins-ugly ... Preparing to replace libclutter-1.0-common 1.8.0-1 (using .../libclutter-1.0-common_1.8.2-1_all.deb) ... Unpacking replacement libclutter-1.0-common ... Preparing to replace libcogl-common 1.8.0-1 (using .../libcogl-common_1.8.2-1_all.deb) ... Unpacking replacement libcogl-common ... Preparing to replace libgadu3 1:1.11.0+r1184-1 (using .../libgadu3_1%3a1.11.0+r1184-2_amd64.deb) ... Unpacking replacement libgadu3 ... Preparing to replace libgladeui-common 3.10.0-2 (using .../libgladeui-common_3.10.2-1_all.deb) ... Unpacking replacement libgladeui-common ... Preparing to replace libgladeui-2-0 3.10.0-2 (using .../libgladeui-2-0_3.10.2-1_amd64.deb)
Bug#611629: libc6: fail to upgrade with Can't locate auto/Hash/Util/bootstpap.al in @INC
Hi, 2011/1/31 Julian Andres Klode j...@debian.org: Definitely not a libc6 bug, and probably not a bug at all. It looks like your perl-base installation is corrupt. Indeed perl-base was corrupted. The question is how since I didn't modified it manually?! Does perl -e require Hash::Util; work? It didn't worked until I corrected Util.pm. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611629: libc6: fail to upgrade with Can't locate auto/Hash/Util/bootstpap.al in @INC
Hi, 2011/1/31 Adam D. Barratt a...@adam-barratt.org.uk: Looking at the log, it doesn't appear the errors are actually due to libc6, however. This section suggests a broken package; it would be interesting to narrow down which package caused it, so we can determine whether it is a local or mirror issue: I've redownloaded libc6-i686 multiple times with the same effect. However I've performed a second upgrade on another system and it worked in three steps: dpkg, libc6, all remaining. | dpkg-deb (subprocess): data: internal bzip2 read error: 'DATA_ERROR' | dpkg-deb: subprocess decompress returned error exit status 2 | dpkg-deb (subprocess): failed in write on buffer copy for failed to write to pipe in copy: Broken pipe The appearance of this error also points towards a likely local problem: | Can't locate auto/Hash/Util/bootstpap.al in @INC (@INC contains: The copy of /usr/lib/perl/5.10/Hash/Util.pm shipped by perl-base 5.10.1-17 (the version in both squeeze and sid) has line 34 as: bootstrap Hash::Util $VERSION; rather than the bootstpap in your error log. I've manually corrected this and the installation continued without error. I've reinstalled perl-base (from the old downloaded package in /var/cache/apt) and the new Util.pm file is correct. So a broken Debian repository mirror is not the issue. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611629: libc6: fail to upgrade with Can't locate auto/Hash/Util/bootstpap.al in @INC
Hi, 2011/1/31 Julian Andres Klode j...@debian.org: Indeed perl-base was corrupted. The question is how since I didn't modified it manually?! Filesystem bug, system crash? That's the most probable cause due to a power failure last night combined with 'ext4' file systems. However, this shows more possible problems with ext4 than expected. The expected problem until now was to have zero length files on sudden power failure but only for files that didn't had enough time to sync to disk. Maybe reassign and lower severity? Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611283: gnome-commander: segmentation fault at startup
Package: gnome-commander Version: 1.2.8.6-3 Justification: renders package unusable Severity: grave Hi, After todays execution of unattended-upgrade for 'dmsetup libdevmapper1.02.1 libpango1.0-0 libpango1.0-common lvm2' I get segmentation fault at startup of gnome-commander every time. Yesterday it was working properly. I've attached the console output and syslog entry for the segfault. Thanks -- System Information: Debian Release: 6.0 APT prefers squeeze-updates APT policy: (600, 'squeeze-updates'), (600, 'testing'), (2, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-commander depends on: ii libart-2.0-2 2.3.21-1 Library of functions for 2D graphi ii libatk1.0-01.30.0-1 The ATK accessibility toolkit ii libbonobo2-0 2.24.3-1 Bonobo CORBA interfaces library ii libbonoboui2-0 2.24.3-1 The Bonobo UI library ii libc6 2.11.2-9 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libexiv2-9 0.20-2EXIF/IPTC metadata manipulation li ii libexpat1 2.0.1-7 XML parsing C library - runtime li ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.2-2.1 FreeType 2 font engine, shared lib ii libgcc11:4.4.5-8 GCC support library ii libgconf2-42.28.1-6 GNOME configuration database syste ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgnome2-02.30.0-1 The GNOME library - runtime files ii libgnomecanvas2-0 2.30.1-1 A powerful object-oriented display ii libgnomeui-0 2.24.3-1 The GNOME libraries (User Interfac ii libgnomevfs2-0 1:2.24.3-1GNOME Virtual File System (runtime ii libgtk2.0-02.20.1-2 The GTK+ graphical user interface ii libice62:1.0.6-2 X11 Inter-Client Exchange library ii liborbit2 1:2.14.18-0.1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.28.3-1+squeeze1 Layout and rendering of internatio ii libpoppler50.12.4-1.2PDF rendering library ii libpopt0 1.16-1lib for parsing cmdline parameters ii libpython2.6 2.6.6-8+b1Shared Python runtime library (ver ii libsm6 2:1.1.1-1 X11 Session Management library ii libssl0.9.80.9.8o-4 SSL shared libraries ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libtag1c2a 1.6.3-1 TagLib Audio Meta-Data Library ii python 2.6.6-3+squeeze5 interactive high-level object-orie ii python-support 1.0.10automated rebuilding support for P ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime gnome-commander recommends no packages. Versions of packages gnome-commander suggests: ii libgnomevfs2-extra1:2.24.3-1 GNOME Virtual File System (extra m -- no debconf information doru@frost:~$ gnome-commander (gnome-commander:9609): GLib-GObject-WARNING **: invalid cast from `GtkMenuItem' to `GtkCheckMenuItem' (gnome-commander:9609): Gtk-CRITICAL **: gtk_check_menu_item_set_active: assertion `GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed (gnome-commander:9609): GLib-GObject-WARNING **: invalid cast from `GtkImageMenuItem' to `GtkCheckMenuItem' (gnome-commander:9609): Gtk-CRITICAL **: gtk_check_menu_item_set_active: assertion `GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed (gnome-commander:9609): Gtk-CRITICAL **: gtk_check_menu_item_set_active: assertion `GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed Segmentation fault Jan 27 19:18:44 frost kernel: [ 304.428258] gnome-commander[9609]: segfault at 21 ip b6db207f sp bfbe4fc0 error 4 in libgobject-2.0.so.0.2400.2[b6d88000+3d000] (Reading database ... 208098 files and directories currently installed.) Preparing to replace libdevmapper1.02.1 2:1.02.48-4 (using .../libdevmapper1.02.1_2%3a1.02.48-5_i386.deb) ... Unpacking replacement libdevmapper1.02.1 ... Preparing to replace dmsetup 2:1.02.48-4 (using .../dmsetup_2%3a1.02.48-5_i386.deb) ... Unpacking replacement dmsetup ... Preparing to replace libpango1.0-common 1.28.3-1 (using .../libpango1.0-common_1.28.3-1+squeeze1_all.deb) ... Cleaning up font configuration of pango... Cleaning up category xfont.. Unpacking replacement libpango1.0-common ... Preparing to replace libpango1.0-0 1.28.3-1 (using .../libpango1.0-0_1.28.3-1+squeeze1_i386.deb) ... Unpacking replacement libpango1.0-0 ... Preparing to replace lvm2 2.02.66-4 (using .../lvm2_2.02.66-5_i386.deb) ...
Bug#611283: gnome-commander doesn't start due to broken link on start_dir_*
severity 611283 normal retitle 611283 gnome-commander doesn't start due to broken link on start_dir_* quit I've found the cause to be a broken link configured for the start_dir_right parameter. Once the broken link was removed it had no problem to start (with a warning for missing directory). However, the segfault in libgobject-2.0.so.0.2400.2 is mentioned in syslog at every start. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
Hi, 2011/1/24 Harald Jenny har...@a-little-linux-box.at: On Mon, Jan 24, 2011 at 10:40:06PM +0200, Teodor MICU wrote: I can only spot some cosmetic issues, otherwise I see no problem. The change USER - SYSTEMUSER only makes the diff larger and not really necessary. I tend to disagree as USER (as well as USERNAME) is set by the shell and so a [ -n $USER ] || USER=amavis check always evaluates to the user running the init script :-/ - as this is not the desired action I decided to rename USER to SYSTEMUSER (and will also change this in the config file). Good catch. Indeed, $USER is defined on interactive sessions and I was only thinking about starting at boot. Ok, I see how MILTERSOCKET is used now. IMHO it's better to keep the number of command line options as short as possible. I can only agree in principle. Well I don't think this package will make it into Debian Squeeze as for me a prerequisite is a fixed libmilter version... sorry when I kept you from doing other more release-critical work, this was not my intention :-(. I tend to disagree here (as Agustin). If this was the case the package would have the 'squeeze-will-remove' tag at least until now. For what I know amavisd is used in Debian SMTP infrastructure which might be a strong reason to accept this small fix in Debian 6.0. If there are other issues (ie. with libmilter) that's another issue which might indeed cause its removal. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
2011/1/25 Harald Jenny har...@a-little-linux-box.at: On Tue, Jan 25, 2011 at 04:57:42PM +0200, Teodor MICU wrote: Good catch. Indeed, $USER is defined on interactive sessions and I was only thinking about starting at boot. Yes therefor I think this change is also necessary do you agree? Yes. I tend to disagree here (as Agustin). If this was the case the package would have the 'squeeze-will-remove' tag at least until now. For what I know amavisd is used in Debian SMTP infrastructure which might be a strong reason to accept this small fix in Debian 6.0. If there are other issues (ie. with libmilter) that's another issue which might indeed cause its removal. As far as I know there are not many installations using amavisd-new with milter so I guess the impact should be fairly minimal - my main objection currently is that I have seen no amavisd-milter installation which runs stable with the current libmilter version in testing and I do not see any interest of the release team in fixing it. If you're absolutely sure that amavisd-milter is broken due to libmilter (in squeeze) than you should request its removal by the release team. Of course the alternative is to fix libmilter but this might have to wait for r1. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
Hi, 2011/1/24 Harald Jenny har...@a-little-linux-box.at: 7) You should probably add -q for all these executions to avoid unwanted strings during start/stop/restart. `echo $MILTERSOCKET | grep -v ^inet` If MILTERSOCKET is checked to contain text too? Yes, it does cover the case where MILTERSOCKET contains something but not if it is empty. For this I would recommend 'printf' since 'echo -n' is not portable and not working with /bin/dash. It is unclear to me why you need to change the owner of MILTERSOCKET. Because amavisd-milter running as user can't otherwise remove the socket when being stopped. Well, I was thinking that there should be a better way to create the socket with the correct owner and group. This is just an workaround for being created by root. I think spamass-millter does a pretty good job here since I use it in the default configuration (via a socket rather than inet). Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
Hi, 2011/1/24 Agustin Martin agmar...@debian.org: On Mon, Jan 24, 2011 at 02:17:48PM +0100, Harald Jenny wrote: I will have a to check this - this is meant as a guard against accidently setting $MILTERSOCKET to . Good catch on this. I didn't though of this being empty. Damm, seems I wrongly understood Theodor's mail, and my proposed change will not work because of echo newline. Anyway, in the case above, 'echo -n' (allowed by policy 10.4) http://www.de.debian.org/doc/debian-policy/ch-files.html#s-scripts should help with that, if echo -n $MILTERSOCKET | grep -q -v ^inet; then That will still not protect against things like setting $MILTERSOCKET to , but dealing with is a must. I don't recommend to use echo with any parameters since it is not portable. The only reliable call to echo is just echo. These calls are not working reliable: echo -n, echo -e, echo -en. For any of these construction just use printf but very important to guard the strings with . So the recommended check to catch all combinations would be: | if printf $MILTERSOCKET | grep -q -v ^inet; then | ... | fi Also, the echo -n is one of the bashism constructions that don't work with dash behind /bin/sh (aka = squeeze). Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
Hi, 2011/1/24 Julien Cristau jcris...@debian.org: Yes, it does cover the case where MILTERSOCKET contains something but not if it is empty. For this I would recommend 'printf' since 'echo -n' is not portable and not working with /bin/dash. Eh, what? Scripts may assume that `/bin/sh' implements the SUSv3 Shell Command Language[1] plus the following additional features not mandated by SUSv3:[2] * `echo -n', if implemented as a shell built-in, must not generate a newline. Works with dash afaict. Last time I checked I was testing several systems (not only on Debian) and I had some issues with echo -n. Ever since I've replace it with 'printf' but you might be right that echo -n is working fine with dash too. I know for user that I'll stick to this convention since I don't have Debian on all hosts. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
2011/1/24 Harald Jenny har...@a-little-linux-box.at: Well as far as I know Debian currently only supports /bin/bash and /bin/dash as providers of /bin/sh so I guess it's currently safe to use echo -n in init scripts. It's fine. After some digging I guess I had in mind echo -e and echo -en are not working with dash but it seems that echo -n (without -e) has no issues. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
Hi again, 2011/1/24 Harald Jenny har...@a-little-linux-box.at: first thanks to everbody for the valuable input, it helped me a lot to improve this init script. Please take a look at the third version of my patch and comment on it. Overall it seems fine, just a few observations: 1) usually you should enclose with the full path here: +PIDFILE=/var/run/amavis/$NAME.pid +[ -r /etc/default/$NAME ] . /etc/default/$NAME Also, $NAME is not usually quoted with in any init script. 2) You should make sure that you don't get it this situation: +if [ -n $PIDFILE ]; then ... +else + log_failure_msg Error: PIDFILE variable must be defined for correct functionality + exit 1 +fi This is usually done by setting the default values (for example for PIDFILE) after you have sourced the config from /etc/default/$NAME. This is done on a test like this: test -z $VAR || VAR=your default value (I don't recommend test -n $VAR .. not that good with set -e) You should consider all variables essential to amavisd-milter startup and runtime. 3) Replace these to work with set -e: +[ -n $AMAVISSOCKET ] .. with +[ -z $AMAVISSOCKET ] || .. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
2011/1/24 Harald Jenny har...@a-little-linux-box.at: On Mon, Jan 24, 2011 at 06:37:37PM +0200, Teodor MICU wrote: 1) usually you should enclose with the full path here: +PIDFILE=/var/run/amavis/$NAME.pid +[ -r /etc/default/$NAME ] . /etc/default/$NAME You mean like this? PIDFILE=/var/run/amavis/$NAME.pid [ -r /etc/default/$NAME ] . /etc/default/$NAME Yes. Also, $NAME is not usually quoted with in any init script. Well that's true but you may set it to a value with blanks in it too so maybe the defaults should also be changed here? If you think it's not necessary I may also drop in but I wanted to be on the safe side here. I don't think this is a supported configuration. I mean $NAME should probably not be changed in config from /etc/default but as you say it is good to be on the safe side. 2) You should make sure that you don't get it this situation: +if [ -n $PIDFILE ]; then ... +else + log_failure_msg Error: PIDFILE variable must be defined for correct functionality + exit 1 +fi This is usually done by setting the default values (for example for PIDFILE) after you have sourced the config from /etc/default/$NAME. This is done on a test like this: test -z $VAR || VAR=your default value (I don't recommend test -n $VAR .. not that good with set -e) You mean not alerting when PIDFILE is set to in the config file but rather changing it to my default value, correct? Yes. It should be a valid config if /etc/default/$NAME that doesn't contain anything. Actually it should be the default to have only comments with the default values that the SysAdmin should be able to change with custom values. I don't know what you have now in the default config. One more important issue I think we missed so far is to have MILTERSOCKET empty in the config file. I think you covered only to skip chmod+chown but in fact it should abort execution. So this construction: +if [ -n $MILTERSOCKET ]; then should be change to: | if [ -z $MILTERSOCKET ]; then | echo .. abort | exit 1 | else [..] Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
Just ignore this. I probably need some coffee. Having MILTERSOCKET variable empty is also with the case with the proposed configuration where you set your default unix:path/to/socket value. Thanks 2011/1/24 Teodor MICU mteo...@gmail.com: One more important issue I think we missed so far is to have MILTERSOCKET empty in the config file. I think you covered only to skip chmod+chown but in fact it should abort execution. So this construction: +if [ -n $MILTERSOCKET ]; then should be change to: | if [ -z $MILTERSOCKET ]; then | echo .. abort | exit 1 | else [..] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
2011/1/24 Harald Jenny har...@a-little-linux-box.at: Ok although the PIDFILE line can be removed with the below code. I'm don't see where PIDFILE is removed. Yes. It should be a valid config if /etc/default/$NAME that doesn't contain anything. Actually it should be the default to have only comments with the default values that the SysAdmin should be able to change with custom values. I don't know what you have now in the default config. Well it's actually this way but PIDFILE needs to be set explicitly for the --pidfile option in the start-stop-daemon stanza - the binary itself already has the default path hardcoded. One more important issue I think we missed so far is to have MILTERSOCKET empty in the config file. I think you covered only to skip chmod+chown but in fact it should abort execution. So this construction: I was wrong here. MILTERSOCKET can be empty in the config from /etc/default/$NAME and this should be the default. Not really as there is a default value set in the binary which points to /var/lib/amavis/amavisd-milter.sock - I guess I should rather do: if [ -z $MILTERSOCKET ]; then MILTERSOCKETTYPE=pipe else [..] fi as this would allow to also set MILTERSOCKETOWNER and MILTERSOCKETMODE with the default pipe location - what do you think? I think the above test is always false if you correctly initialize MILTERSOCKET after the /etc/default/$NAME has been sourced. [ -z $MILTERSOCKET ] || MILTERSOCKET=/var/lib/amavis/amavisd-milter.sock Later on you don't check if it's empty but only the type: unix vs inet. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
2011/1/24 Harald Jenny har...@a-little-linux-box.at: On Mon, Jan 24, 2011 at 08:59:41PM +0200, Teodor MICU wrote: 2011/1/24 Harald Jenny har...@a-little-linux-box.at: Ok although the PIDFILE line can be removed with the below code. I'm don't see where PIDFILE is removed. Just take a look at the next patch version. I can only spot some cosmetic issues, otherwise I see no problem. The change USER - SYSTEMUSER only makes the diff larger and not really necessary. It was a good idea to get the 'dirname' out on their own, it is cleaner like this. I was wrong here. MILTERSOCKET can be empty in the config from /etc/default/$NAME and this should be the default. Yes but if it's empty the default value is a unix socket. Ok. I think the above test is always false if you correctly initialize MILTERSOCKET after the /etc/default/$NAME has been sourced. [ -z $MILTERSOCKET ] || MILTERSOCKET=/var/lib/amavis/amavisd-milter.sock True but I only want to append to OPTIONS when the default values are overriden because this keeps the command line shorter :-). Ok, I see how MILTERSOCKET is used now. Later on you don't check if it's empty but only the type: unix vs inet. Well seems to me this is just a change in the code flow... Yes. The release team will check too, maybe we missed something. :) Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
[Harald please CC: my address otherwise I could not see your responses] 2011/1/20 Harald Jenny har...@a-little-linux-box.at: I checked with other init scripts an in order to have a consistent coding style in the init script I replaced the with if-clauses - could you take a look at it and tell me if this looks better to you? I had a look at the new patch and I have a few observations. 1) This construction is fine and simple as recommended in /etc/init.d/skeleton: # Read configuration variable file if it is present [ -r /etc/default/$NAME ] . /etc/default/$NAME 2) This construction doesn't work if PIDFILE is empty (not defined): +if [ $PIDFILE != /var/run/amavis/$NAME.pid ]; then For all strings comparison you need to use $VAR. 3) This seems to be valid but I've always used [ -n $VAR ] instead of: +if [ $MILTERSOCKET ]; then 4) This doesn't work if the directory has a space: + if [ ! -e $(dirname $PIDFILE) ]; then +mkdir $(dirname $PIDFILE) You need to use $(dirname $PIDFILE). This is an issue if this variable can be defined to any custom value. 5) This has a mistake: and extra ) character at the end + chown $USER:$(id $USER -g -n) $(dirname $PIDFILE)) The correct execution would be: + chown $USER:$(id $USER -g -n) $(dirname $PIDFILE) 6) I'm not sure this is working properly, I've always used [ -n -a.. ]. +if [ $MILTERSOCKET -a `echo... ]; then Also, there is no need to check if MILTERSOCKET is empty in this case. 7) You should probably add -q for all these executions to avoid unwanted strings during start/stop/restart. `echo $MILTERSOCKET | grep -v ^inet` 8) The same as #5 for this construction: + if [ ! -e $(dirname $MILTERSOCKET) ]; then +mkdir $(dirname $MILTERSOCKET) + fi + chown $USER $(dirname $MILTERSOCKET)) It is unclear to me why you need to change the owner of MILTERSOCKET. Let me know if you need some help to fix this bug. I'm not using amavisd anymore but I could help in this case. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
2011/1/21 Agustin Martin agmar...@debian.org: if [ $MILTERSOCKET ] [ `echo $MILTERSOCKET | grep -v ^inet` ]; then but as Teodor points out (just read it), second check seems to be enough. Only that I realized latter the intention of this construction. My previous suggestion was to use this construction on its own without test: if echo $MILTERSOCKET | grep -q -v ^inet; then ... fi (the return code is set by grep) This works too but there is an extra test for the empty string: if [ $(echo $MILTERSOCKET | grep -v ^inet) ]; then ... fi (the return code is set by 'test') Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609762: amavisd-milter: Init script changes owner of current directory to 'amavis'
Hi Harald, I looked at your patch and I think those multiple checks in chain are prone to mistakes in some conditions. I've reported the same problem with clamav-milter [1] some time ago and I believe that is a cleaner and better implementation for checking SOCKET, SOCKET_TYPE and SOCKET_PATH. I'm writing this to you to check the current script from /etc/init.d/clamav-milter and include something similar for amavisd-milter. Thanks [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=55 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602172: [openvpn] openvpn doesn't start without manually created nobody group
severity 602172 normal tag 602172 + moreinfo unreproducible stop Hi, On Tue, Nov 2, 2010 at 10:50 AM, Matthieu Baechler matthieu.baech...@gmail.com wrote: Package: openvpn Version: 2.1.3-2 Severity: grave A freshly installed openvpn package won't start because it needs nobody group existence but install script doesn't create it. Once this group is created, it starts correctly. First of all I've tested (again) a fresh install and there is no problem during the installation. By default there is nothing to be started after a fresh install. Second, in Debian the user 'nobody' with group ' nogroup' are created by default. There should be no group 'nobody' on a Debian system. The most likely cause of your problem is a custom VPN configuration which enforces low privileges using 'user+group'. Thus the severity change. Please send us the VPN profile (without any sensitive information) or at least the output from this command: $ grep -i -E '(user|group)' /etc/openvpn/*.conf Cheers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600166: openvpn: at start it adds 40 bogus routes not specified in configuration
Hi, On Thu, Oct 21, 2010 at 2:03 PM, Alberto Gonzalez Iniesta a...@inittab.org wrote: I've got a new -2 package (same location) with upstream's solution, instead of mine. Would you mind testing it? That would probably be the one I upload to close this report. I've just tested this package (built on Oct 21) and the problem seems to be fixed. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583371: nut: usbhid-ups failing to communicate with UPS (libusb_get_report: error sending control message)
Hi Arnaud, Since the patch is only a 2 line diff [1], can you upload a targeted fix with this patch for squeeze? I strongly believe that release team will not object to this small fix which is also included in the upstream source. Also, this bug is currently RC. Thanks [1] http://boxster.ghz.cc/projects/nut/changeset/2407 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nut depends on: ii adduser 3.112 add and remove users and groups ii libc62.11.2-6Embedded GNU C Library: Shared lib ii libupsclient12.4.3-1+b1 network UPS tools - client library ii libusb-0.1-4 2:0.1.12-16 userspace USB programming library ii libwrap0 7.6.q-19Wietse Venema's TCP wrappers libra ii lsb-base 3.2-23.1Linux Standard Base 3.2 init scrip ii udev 160-1 /dev/ and hotplug management daemo Versions of packages nut recommends: ii bash-completion 1:1.2-2programmable completion for the ba Versions of packages nut suggests: pn nut-cgi none (no description available) pn nut-dev none (no description available) pn nut-snmp none (no description available) pn nut-xml none (no description available) -- Configuration Files: /etc/nut/nut.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600166: openvpn: at start it adds 40 bogus routes not specified in configuration
Hi, On Fri, Oct 15, 2010 at 2:45 PM, Alberto Gonzalez Iniesta a...@inittab.org wrote: I think I found the bug. But you can help me confirm this (and solve the problem for the time being). Could you try this (on the server config): Change: push route remote_host 255.255.255.255 net_gateway To: push route OPENVPN_REMOTE_PEER 255.255.255.255 net_gateway Yes, it works with this configuration change on the oVPN server. I'll test the deb package too. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600166: openvpn: at start it adds 40 bogus routes not specified in configuration
Hi, On Fri, Oct 15, 2010 at 3:39 PM, Alberto Gonzalez Iniesta a...@inittab.org wrote: Could you try with this package [1]? [1] http://etc.inittab.org/~agi/openvpn_2.1.3-2_i386.deb I've reverted the original config on the oVPN server and with the -2 package it works fine as on v2.1.0. The weird thing about pushing 'remote_host' from the server is that I have another oVPN server which has almost the same configuration but the problem was not for both. The differences on the working oVPN server are: - OPENVPN_REMOTE_PEER host is not from the REMOTE_SUBNET network (it is the external gateway); - using public IP addresses for clients (instead of private); Ok. I've found that on the working oVPN server I'm not using push remote_host because its not needed due to point #1. Mystery solved. :) Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600166: openvpn: at start it adds 40 bogus routes not specified in configuration
Hi, On Thu, Oct 14, 2010 at 11:37 AM, Alberto Gonzalez Iniesta a...@inittab.org wrote: Hi, could you attach (without sensitive data) the server and client configurations? Sure. The real company addresses and names were replaced with generic names. Thanks #== openvpn client options (linux) == client remote OPENVPN_REMOTE_PEER nobind tls-auth keys/ta-sfo.key ca keys/COMPANY_private_CA.crt cert keys/staff.crt key keys/staff.key comp-lzo no dev tun mlock mtu-test mute 6 mute-replay-warnings passtos #available only on Linux ping-timer-rem reneg-sec 0 tls-exit auth-user-pass pw_staff.txt auth-retry interact auth-nocache #mssfix 1400#use only on networks where the MTU test fails tls-remote /C=US/ST=../L=../O=../CN=.. ns-cert-type server verb 4 #route remote_host 255.255.255.255 10.0.0.1 #redirect-gateway def1 ##route network/IP [netmask] [gateway] [metric] COMPANY-sfo-server.conf Description: Binary data
Bug#531546: Bug #531546: empty graphs due to 'A DB Exec Failed' Poller[0] ERROR
Hi,
On Tue, Sep 21, 2010 at 11:56 PM, sean finney sean...@debian.org wrote:
some ideas/questions off the top of my head:
* did you get any sql upgrade errors after the package was updated?
There were no sql upgrade scripts from 0.8.7e-4 to 0.8.7g-1. The
upgrade says clearly that there are no scripts to run. I've checked
manually in the install directory and these two scripts are just
changing the cacti vesion in the database:
- 0_8_7e_to_0_8_7f.php
- 0_8_7f_to_0_8_7g.php
* does the schema seem correct (i.e. a disabled column in the host table)?
I don't know anything related to a 'schema', so probably not the
issue. If you can tell me what to check, I'll do.
* does it work if you disable the spine poller and use the cmd.php one
instead?
Yes, with 'cmd.php' I get the graphs but still at every 5 minutes
there are SQL errors reported (see attached).
No, with 'spine' I still get the SQL errors but also only NaN on all graphs.
* does it start graphing again if you nuke the rrd files or play around
with rrdtool versions?
I'll try to avoid playing around with rrdtool again. I did it for the
conversion from 1.2x to 1.3x and this is the main reason I'm using
cacti from squeeze on a lenny host.
esp for the first two items, if you suspect the problem is in the SQL,
and have time to help with some QA: i think it would be very helpful to
get a db dump of a fresh install vs the db dump of a almost-as-fresh
install of the previous version upgraded after maybe half an hour of
polling... it could be that there's a bug in the update sql logic.
I'll try to do a fresh install, but I don't I'll have the time this week.
Thanks
09/22/2010 10:55:34 AM - PHPSVR: Poller[0] Maximum runtime of 60 seconds exceeded for the Script Server. Exiting.
09/22/2010 10:55:33 AM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('stats_recache','RecacheTime:0.0 HostsRecached:0')'
09/22/2010 10:55:33 AM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT COUNT(*) FROM poller_command
09/22/2010 10:55:33 AM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('stats_poller','Time:0.0022 Method:cmd.php Processes:1 Threads:N/A Hosts:0 HostsPerProcess:0 DataSources:456 RRDsProcessed:0')'
09/22/2010 10:55:33 AM - SYSTEM STATS: Time:0.0022 Method:cmd.php Processes:1 Threads:N/A Hosts:0 HostsPerProcess:0 DataSources:456 RRDsProcessed:0
09/22/2010 10:55:33 AM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:select poller_output.output, poller_output.time, poller_output.local_data_id, poller_item.rrd_path, poller_item.rrd_name, poller_item.rrd_num from (poller_output,poller_item) where (poller_output.local_data_id=poller_item.local_data_id and poller_output.rrd_name=poller_item.rrd_name)
09/22/2010 10:55:33 AM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT count(*) FROM poller_time WHERE poller_id=0 AND end_time'-00-00 00:00:00'
09/22/2010 10:55:33 AM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('date',NOW())'
09/22/2010 10:55:33 AM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:SELECT local_data_id, rrd_name FROM poller_output
09/22/2010 10:55:33 AM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:TRUNCATE TABLE poller_time'
09/22/2010 10:55:33 AM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT count(*) FROM poller_time WHERE end_time='-00-00 00:00:00'
09/22/2010 10:55:33 AM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('path_webroot','/usr/share/cacti/site')'
09/22/2010 10:55:33 AM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:SELECT id FROM host WHERE disabled = '' ORDER BY id
Bug#531546: Bug #531546: empty graphs due to 'A DB Exec Failed' Poller[0] ERROR
Hi, On Wed, Sep 22, 2010 at 9:23 AM, sean finney sean...@debian.org wrote: do you get the same problems if you also upgrade spine from the lenny version to the squeeze version (0.8.7e-2)? i wouldn't be surprised that the poller from lenny is designed for different sql/schema and thus might not do the right INSERT/UPDATE type statements. I didn't upgrade spine because I'll have to upgrade mysql too (and probably other packages from backports). The weird thing about these SQL errors is that running them manually gives no error but sometimes there are no results returned from the query. if upgrading to the squeeze version of spine doesn't solve the problem, you could also try updating to the latest upstream version (i.e. compiling it yourself and replacing the packaged version), but i haven't been lead to believe that the latest version is so different from the squeeze/sid version. There are near zero chances of compiling it myself. I'll probably try a fresh install on a squeeze host with cacti and spine =0.8.7e. Until them I'll stick with cacti=0.8.7e-4. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531546: empty graphs due to 'A DB Exec Failed' Poller[0] ERROR
On Wed, Sep 22, 2010 at 10:57 AM, Teodor MICU mteo...@gmail.com wrote: On Tue, Sep 21, 2010 at 11:56 PM, sean finney sean...@debian.org wrote: some ideas/questions off the top of my head: * did you get any sql upgrade errors after the package was updated? There were no sql upgrade scripts from 0.8.7e-4 to 0.8.7g-1. The upgrade says clearly that there are no scripts to run. This is all that the upgrade process gives: ## Cacti Installation Guide Upgrade results: No SQL queries have been executed. ## Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531546: empty graphs due to 'A DB Exec Failed' Poller[0] ERROR
Hi,
On Wed, Sep 22, 2010 at 10:57 AM, Teodor MICU mteo...@gmail.com wrote:
Yes, with 'cmd.php' I get the graphs but still at every 5 minutes
there are SQL errors reported (see attached).
Ok, the last test reveals that with 'cmd.php' used directly after
upgrade the same SQL errors will appear after the first 5 minutes
cycle (see attached file). See that the 'select' queries in the
database are good with some notes:
- there is a missing in the log at 11:35:34 regarding SQL:REPLACE INTO;
- I've executed only the 'select' queries.
Another problem seems that 'cmp.php' poller is executes more than 60
seconds which leads to overlapping:
09/22/2010 11:35:01 AM - POLLER: Poller[0] WARNING: There are '1'
detected as overrunning a polling process, please investigate
Shall I open a new bug report for this?
I'll revert to 0.8.7e-4 and test a fresh 'cacti=0.8.7g-1' install on a
virtual machine.
Thanks
09/22/2010 11:35:00 AM - SYSTEM STATS: Time:26.1492 Method:cmd.php Processes:1 Threads:N/A Hosts:42 HostsPerProcess:42 DataSources:464 RRDsProcessed:69
09/22/2010 11:35:01 AM - POLLER: Poller[0] WARNING: There are '1' detected as overrunning a polling process, please investigate
09/22/2010 11:35:01 AM - POLLER: Poller[0] WARNING: Poller Output Table not Empty. Issues Found: 4, Data Sources: cpu_user(DS[562]), load_1min(DS[563]), load_15min(DS[564]), load_5min(DS[565])
09/22/2010 11:35:05 AM - CMDPHP: Poller[0] Host[3] DS[33] WARNING: Result from SNMP not valid. Partial Result: U
09/22/2010 11:35:05 AM - CMDPHP: Poller[0] Host[3] DS[33] WARNING: Result from SNMP not valid. Partial Result: U
09/22/2010 11:35:34 AM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:SELECT id FROM host WHERE disabled = '' ORDER BY id
09/22/2010 11:35:34 AM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('path_webroot','/usr/share/cacti/site')'
09/22/2010 11:35:34 AM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT count(*) FROM poller_time WHERE end_time='-00-00 00:00:00'
09/22/2010 11:35:34 AM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:TRUNCATE TABLE poller_time'
09/22/2010 11:35:34 AM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:SELECT local_data_id, rrd_name FROM poller_output
09/22/2010 11:35:34 AM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('date',NOW())'
09/22/2010 11:35:34 AM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT count(*) FROM poller_time WHERE poller_id=0 AND end_time'-00-00 00:00:00'
09/22/2010 11:35:34 AM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:select poller_output.output, poller_output.time, poller_output.local_data_id, poller_item.rrd_path, poller_item.rrd_name, poller_item.rrd_num from (poller_output,poller_item) where (poller_output.local_data_id=poller_item.local_data_id and poller_output.rrd_name=poller_item.rrd_name)
09/22/2010 11:35:34 AM - SYSTEM STATS: Time:0.0023 Method:cmd.php Processes:1 Threads:N/A Hosts:0 HostsPerProcess:0 DataSources:464 RRDsProcessed:0
09/22/2010 11:35:34 AM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('stats_poller','Time:0.0023 Method:cmd.php Processes:1 Threads:N/A Hosts:0 HostsPerProcess:0 DataSources:464 RRDsProcessed:0')'
09/22/2010 11:35:34 AM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT COUNT(*) FROM poller_command
09/22/2010 11:35:34 AM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('stats_recache','RecacheTime:0.0 HostsRecached:0')'
09/22/2010 11:35:35 AM - PHPSVR: Poller[0] Maximum runtime of 60 seconds exceeded for the Script Server. Exiting.
Bug#531546: empty graphs due to 'A DB Exec Failed' Poller[0] ERROR
[really attaching the SQL select queries] mysql use cacti; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql SELECT id FROM host WHERE disabled = '' ORDER BY id; ++ | id | ++ | 1 | | 2 | | 3 | | 4 | | 6 | | 7 | | 8 | | 10 | | 11 | | 12 | | 13 | | 14 | | 15 | | 16 | | 17 | | 18 | | 19 | | 20 | | 21 | | 22 | | 24 | | 25 | | 26 | | 27 | | 29 | | 30 | | 31 | | 32 | | 34 | | 35 | | 36 | | 37 | | 42 | | 43 | | 44 | | 45 | | 48 | | 49 | | 50 | | 51 | | 52 | ++ 41 rows in set (0.00 sec) mysql SELECT count(*) FROM poller_time WHERE end_time='-00-00 00:00:00' - ; +--+ | count(*) | +--+ |1 | +--+ 1 row in set (0.00 sec) mysql mysql SELECT local_data_id, rrd_name FROM poller_output - ; +---+---+ | local_data_id | rrd_name | +---+---+ | 545 | cpu_user | | 546 | load_1min | +---+---+ 2 rows in set (0.00 sec) mysql SELECT count(*) FROM poller_time WHERE poller_id=0 AND end_time'-00-00 00:00:00'; +--+ | count(*) | +--+ |0 | +--+ 1 row in set (0.00 sec) mysql select poller_output.output, poller_output.time, poller_output.local_data_id, poller_item.rrd_path, poller_item.rrd_name, poller_item.rrd_num from (poller_output,poller_item) where (poller_output.local_data_id=poller_item.local_data_id and poller_output.rrd_name=poller_item.rrd_name); Empty set (0.00 sec) mysql SELECT COUNT(*) FROM poller_command; +--+ | COUNT(*) | +--+ |0 | +--+ 1 row in set (0.00 sec)
Bug#531546: empty graphs due to 'A DB Exec Failed' Poller[0] ERROR
Hi, On Wed, Sep 22, 2010 at 12:00 PM, Stephane Dudzinski steph...@cp.dias.ie wrote: We did upgrade a box from Lenny to Squeeze and it indeed kept all its graphs this time, this is what we are currently using: ii rrdtool 1.4.3-1 ii cacti 0.8.7e-4 Ok, this is the last cacti version that works for me too (actually all have worked fine except the last one v0.8.7g). I guess rrdtool=1.4.x you have it from backports or you run Debian 6.0? rc cacti-spine 0.8.7a-2.3 This was not purged, so I guess you are running Debian 5.0 (lenny). We don't use cacti-spine, I have set up the following: Under General: RRDTool 1.3.x (no option for 1.4.x) Support for rrdtool 1.4x is available on cacti 0.8.7g although I didn't test it to see if it works. Uner Poller: cmd.php Right, this is the default settings and works well for a limited number of hosts and graphs. I have 52 hosts and ~500 graphs to update, where the CPU load (by core/processor), load average and CPU usage are configured at 1 minute. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531546: empty graphs due to 'A DB Exec Failed' Poller[0] ERROR
Hi, On Wed, Sep 22, 2010 at 4:48 PM, Stephane Dudzinski steph...@cp.dias.ie wrote: I have just upgraded to 0.8.7g-1, backed up the DB before doing so then did the web interface upgrade steps, it said there was no SQL upgrade. And it is still happily graphing. So I am guessing your problem is probably with cacti-spine (that I am not using). Different bug if you ask me. Yes, it was working for me too (happily graphing) if I used 'cmd.php' which you also use. But also, check the 'cacti.log' file for SQL errors. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531546: Bug #531546: empty graphs due to 'A DB Exec Failed' Poller[0] ERROR
retitle 531546 empty graphs due to 'A DB Exec Failed' Poller[0] ERROR
quit
Hi,
It seems that this old problem has an impact on 'squeeze' too. After
upgrading from v0.8.7e-4 to 0.8.7g-1 all the graphs were with NaN from
this point forward. The error message in cacti.log was like in the
attached file. I've downgraded to the previous version and restored
the database from a backup (cacti refused to continue due to a higher
version 7g than 7e currently installed).
I'll probably attempt a new upgrade soon, do you have any recommendations?
Thanks
09/21/2010 08:00:39 PM - SYSTEM STATS: Time:37.3214 Method:spine Processes:2 Threads:8 Hosts:42 HostsPerProcess:21 DataSources:464 RRDsProcessed:411
09/21/2010 08:01:01 PM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:SELECT id FROM host WHERE disabled = '' ORDER BY id
09/21/2010 08:01:01 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('path_webroot','/usr/share/cacti/site')'
09/21/2010 08:01:01 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT count(*) FROM poller_time WHERE end_time='-00-00 00:00:00'
09/21/2010 08:01:01 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:TRUNCATE TABLE poller_time'
09/21/2010 08:01:01 PM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:SELECT local_data_id, rrd_name FROM poller_output
09/21/2010 08:01:01 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('date',NOW())'
09/21/2010 08:01:01 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT count(*) FROM poller_time WHERE poller_id=0 AND end_time'-00-00 00:00:00'
09/21/2010 08:01:01 PM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:select poller_output.output, poller_output.time, poller_output.local_data_id, poller_item.rrd_path, poller_item.rrd_name, poller_item.rrd_num from (poller_output,poller_item) where (poller_output.local_data_id=poller_item.local_data_id and poller_output.rrd_name=poller_item.rrd_name)
09/21/2010 08:01:01 PM - SYSTEM STATS: Time:0.0020 Method:spine Processes:2 Threads:8 Hosts:0 HostsPerProcess:0 DataSources:464 RRDsProcessed:0
09/21/2010 08:01:01 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('stats_poller','Time:0.0020 Method:spine Processes:2 Threads:8 Hosts:0 HostsPerProcess:0 DataSources:464 RRDsProcessed:0')'
09/21/2010 08:01:01 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT COUNT(*) FROM poller_command
09/21/2010 08:01:01 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('stats_recache','RecacheTime:0.0 HostsRecached:0')'
09/21/2010 08:02:01 PM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:SELECT id FROM host WHERE disabled = '' ORDER BY id
09/21/2010 08:02:01 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('path_webroot','/usr/share/cacti/site')'
09/21/2010 08:02:01 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT count(*) FROM poller_time WHERE end_time='-00-00 00:00:00'
09/21/2010 08:02:01 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:TRUNCATE TABLE poller_time'
Bug#531546: Bug #531546: empty graphs due to 'A DB Exec Failed' Poller[0] ERROR
Hi again,
On Tue, Sep 21, 2010 at 11:02 PM, Teodor MICU mteo...@gmail.com wrote:
It seems that this old problem has an impact on 'squeeze' too. After
upgrading from v0.8.7e-4 to 0.8.7g-1 all the graphs were with NaN from
this point forward.
I've been able to reproduce the problem. So far the problem will
appear any time I'll activate 'spine' poller. One weird thing is that
both CMDPHP and SPINE are present in the cacti.log as if both are
running even if I selected 'spine' to do the polling. Note that I'm
using cacti=0.8.7g with spine=0.8.7a-2.3 on a Debian 5.0 (lenny) host.
So, using 'cmd.php' is an option but brings some important drawbacks:
- there are many U results from the queries, with 'spine' there were
not so many;
- it doesn't have enough time to do all the polling (for all
graphs/data sources).
Update: using 'cmd.php' also gives SQL errors, although it could be
from another polling process. I suspect that 'spine' is causing some
problems to the DB that affects 'cmd.php' too.
Thanks
09/21/2010 11:30:01 PM - POLLER: Poller[0] WARNING: There are '2' detected as overrunning a polling process, please investigate
09/21/2010 11:30:01 PM - POLLER: Poller[0] WARNING: Poller Output Table not Empty. Issues Found: 3, Data Sources: traffic_in(DS[11]), traffic_out(DS[11]), cpu(DS[365])
09/21/2010 11:30:01 PM - SPINE: Poller[0] Host[3] DS[33] WARNING: Result from SNMP not valid. Partial Result: ...
09/21/2010 11:30:01 PM - SPINE: Poller[0] Host[3] DS[33] WARNING: Result from SNMP not valid. Partial Result: ...
09/21/2010 11:30:01 PM - POLLER: Poller[0] Maximum runtime of 298 seconds exceeded. Exiting.
09/21/2010 11:30:01 PM - SYSTEM STATS: Time:59.3551 Method:cmd.php Processes:2 Threads:N/A Hosts:42 HostsPerProcess:21 DataSources:464 RRDsProcessed:301
09/21/2010 11:30:02 PM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:SELECT id FROM host WHERE disabled = '' ORDER BY id
09/21/2010 11:30:02 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('path_webroot','/usr/share/cacti/site')'
09/21/2010 11:30:02 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT count(*) FROM poller_time WHERE end_time='-00-00 00:00:00'
09/21/2010 11:30:02 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:TRUNCATE TABLE poller_time'
09/21/2010 11:30:02 PM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:SELECT local_data_id, rrd_name FROM poller_output
09/21/2010 11:30:02 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('date',NOW())'
09/21/2010 11:30:02 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT count(*) FROM poller_time WHERE poller_id=0 AND end_time'-00-00 00:00:00'
09/21/2010 11:30:02 PM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:select poller_output.output, poller_output.time, poller_output.local_data_id, poller_item.rrd_path, poller_item.rrd_name, poller_item.rrd_num from (poller_output,poller_item) where (poller_output.local_data_id=poller_item.local_data_id and poller_output.rrd_name=poller_item.rrd_name)
09/21/2010 11:30:02 PM - SYSTEM STATS: Time:0.0022 Method:cmd.php Processes:2 Threads:N/A Hosts:0 HostsPerProcess:0 DataSources:464 RRDsProcessed:0
09/21/2010 11:30:02 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('stats_poller','Time:0.0022 Method:cmd.php Processes:2 Threads:N/A Hosts:0 HostsPerProcess:0 DataSources:464 RRDsProcessed:0')'
09/21/2010 11:30:02 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'0', SQL:SELECT COUNT(*) FROM poller_command
09/21/2010 11:30:02 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'0', SQL:REPLACE INTO settings (name,value) VALUES ('stats_recache','RecacheTime:0.0 HostsRecached:0')'
09/21/2010 11:30:03 PM - PHPSVR: Poller[0] Maximum runtime of 60 seconds exceeded for the Script Server. Exiting.
09/22/2010 02:49:43 AM - SYSTEM STATS: Time:96.2642 Method:cmd.php Processes:1 Threads:N/A Hosts:42 HostsPerProcess:42 DataSources:466 RRDsProcessed:412
09/22/2010 02:50:00 AM - POLLER: Poller[0] Maximum runtime of 298 seconds exceeded. Exiting.
09/22/2010 02:50:00 AM - SYSTEM STATS: Time:17.1356 Method:cmd.php Processes:1 Threads:N/A Hosts:42 HostsPerProcess:42 DataSources:466 RRDsProcessed:45
09/22/2010 02:50:02 AM - POLLER: Poller[0] WARNING: There are '1' detected as overrunning a polling process, please investigate
09/22/2010 02:50:02 AM - POLLER: Poller[0] WARNING: Poller Output Table not Empty. Issues Found: 1, Data Sources: cpu(DS[308])
09/22/2010 02:50:06 AM - CMDPHP: Poller[0] Host[3] DS[32] WARNING: Result from SNMP not valid. Partial Result: U
09/22/2010 02:50:06 AM - CMDPHP: Poller[0] Host[3] DS[32] WARNING: Result from SNMP not valid. Partial Result: U
09/22/2010 02:50:43 AM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'0', SQL:SELECT id FROM host WHERE disabled
Bug#481072: dk-filter crash seems to be for a specific use case (-k parameter)
On Wed, Aug 18, 2010 at 12:38 AM, Mike Markley m...@markley.org wrote: On Mon, Aug 16, 2010 at 10:57:35AM +0300, Teodor MICU mteo...@gmail.com wrote: [..] In conclusion, can we downgrade the severity of this bug report so that at least we have the same version from lenny in squeeze too? If there are no objections I can do this at the end of the week, though it is better to be done by Mike Markley. I don't object, either, but I would also like input from the release team. I can chase that, if you'd like. By all means I do prefer to have you as the maintainer of the package to contact the Release team. I'm not sure if this is necessary, but its your call. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#481072: dk-filter crash seems to be for a specific use case (-k parameter)
Followup-For: Bug #481072 Package: dk-filter Version: 1.0.0.dfsg-1+b1 *** Please type your report below this line *** Hello, I've been checking the status of 'dk-filter' for squeeze and it is blocked for inclusion by this RC bug report. As far as I can see this reliable crash is reproduced only if you use the -k parameter. I don't use it (I don't have multiple domains) and I don't have crashes, I had only one this morning but that all for almost a year of working properly. From my point of view development of dk-filter has stopped and only dkim-filter is maintained properly. Thus this bug and the other I reported will have to be avoided as there are specific use cases. In conclusion, can we downgrade the severity of this bug report so that at least we have the same version from lenny in squeeze too? If there are no objections I can do this at the end of the week, though it is better to be done by Mike Markley. Thanks -- System Information: Debian Release: 5.0.5 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dk-filter depends on: ii adduser 3.110add and remove users and groups ii libc6 2.7-18lenny4 GNU C Library: Shared libraries ii libmilter1.0.1 8.14.3-5+lenny1 Sendmail Mail Filter API (Milter) ii libssl0.9.8 0.9.8g-15+lenny7 SSL shared libraries dk-filter recommends no packages. dk-filter suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574832: [security] possible symlink attack against /tmp/ddclient.cache
Hi, On Sun, Mar 21, 2010 at 6:43 PM, Nico Golde n...@debian.org wrote: From what I see it is using /var/cache/ddclient/ddclient.cache. Can you elaborate why you think it's using /tmp/? It doesn't apper to be using that directory. This is what I have on my laptop: | d...@r2:~$ ls -l /tmp/ddclient.cache /var/cache/ddclient/ | -rw--- 1 root root 262 2010-03-21 19:56 /tmp/ddclient.cache | | /var/cache/ddclient/: | total 0 Also, I'm watching syslog quite a lot and I noticed this line at boot: | Mar 21 19:56:39 r2 ddclient[3135]: WARNING: file /tmp/ddclient.cache, line 3: Invalid Value for keyword 'ip' = '' Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572048: tomcat6: fails to start after upgrade to v6.0.24-2
Hello, On Tue, Mar 2, 2010 at 1:07 AM, Ludovic Claude ludovic.claud...@googlemail.com wrote: The changes were motivated by the fact that jscv is unreliable (see #561559) and is hard to use when you need to setup Tomcat with ports 1024. Upstream maintains the catalina.sh script and recommends its use. We were kindly assisted by a Tomcat expert (Jason Brittain from MuleSoft) in this transition. With this script, it is now possible to use authbind easily if the ports are under 1024. Ok, using authbind might be an improvement but I'm not sure about giving up on jsvc (which is also developed by Apache in tomcat project). Can you give me more details about your setup. It looks like an upgrade, so what other packages or webapps have you installed? Can you provide the Tomcat logs in /var/log/tomcat6. I don't have anything configured on this host, it's just a plain default installation and configuration of tomcat6 package. After the upgrade I've seen there are problems and I thought that the upgrade has done something wrong, so I've purged all tomcat packages. The current setup is a fresh install which fails to start! Thanks PS: how can I receive any responses on this bug without CC:me ? -- r...@frost:~# pgrep -fl java r...@frost:~# pgrep -fl tomcat r...@frost:~# r...@frost:~# r...@frost:~# /etc/init.d/tomcat6 status Tomcat servlet engine is not running.. r...@frost:~# r...@frost:~# r...@frost:~# ls -l /var/log/tomcat6/ total 20 -rw-r--r-- 1 tomcat6 tomcat6 2221 Mar 1 09:49 catalina.2010-03-01.log -rw-r--r-- 1 tomcat6 tomcat6 2225 Mar 2 08:39 catalina.2010-03-02.log -rw-r--r-- 1 tomcat6 tomcat6 2225 Mar 3 09:04 catalina.2010-03-03.log -rw-r--r-- 1 tomcat6 root6671 Mar 3 09:04 catalina.out -rw-r--r-- 1 tomcat6 tomcat60 Mar 1 09:49 localhost.2010-03-01.log -rw-r--r-- 1 tomcat6 tomcat60 Mar 2 08:39 localhost.2010-03-02.log -rw-r--r-- 1 tomcat6 tomcat60 Mar 3 09:04 localhost.2010-03-03.log r...@frost:~# cat /var/log/tomcat6/catalina.2010-03-03.log Mar 3, 2010 9:04:13 AM org.apache.catalina.core.AprLifecycleListener init INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/jni:/lib:/usr/lib Mar 3, 2010 9:04:13 AM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Mar 3, 2010 9:04:13 AM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1116 ms Mar 3, 2010 9:04:14 AM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Mar 3, 2010 9:04:14 AM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.24 Mar 3, 2010 9:04:14 AM org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor ROOT.xml Mar 3, 2010 9:04:14 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Mar 3, 2010 9:04:14 AM org.apache.catalina.startup.Catalina start INFO: Server startup in 612 ms Mar 3, 2010 9:04:14 AM org.apache.catalina.core.StandardServer await SEVERE: StandardServer.await: create[8005]: java.net.SocketException: Invalid argument at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336) at java.net.ServerSocket.bind(ServerSocket.java:336) at java.net.ServerSocket.init(ServerSocket.java:202) at org.apache.catalina.core.StandardServer.await(StandardServer.java:373) at org.apache.catalina.startup.Catalina.await(Catalina.java:657) at org.apache.catalina.startup.Catalina.start(Catalina.java:617) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) r...@frost:~# r...@frost:~# r...@frost:~# lsof -i :8080 r...@frost:~# r...@frost:~# lsof -i :8005 r...@frost:~# -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561477: [security] must not RE-add /etc/apache2/conf.d/cacti.conf link on upgrade
severity 561477 wishlist retitle 561477 please improve the debconf question about web server configuration thanks On Thu, Jan 7, 2010 at 11:17 AM, Patrick Schoenfeld schoenf...@debian.org wrote: On Wed, Jan 06, 2010 at 05:44:28PM +0200, Teodor MICU wrote: Ok, now I see that this is a way of disabling that symlink. Still, I would like to have the '/etc/cacti/apache.conf' file for reference to update my custom config which simply restricts the access to Intranet. which should be totally unrelated. Usually the file /etc/cacti/apache.conf should be installed together with the package while the symlink is created because you asked it, to. So sorry for the noise, except that I still not understand why people answer a priority high question with Configure my webserver: apache2 just for removing the symlink, it results into after, that. The debconf question is Which kind of web server should be used by cacti? so I answered apache2. Maybe this question should be updated to better describe its meaning? Well, it also says Select 'None' if you would like to configure your webserver by hand. but I agree that the wording of the question could be more clear. I'm proposing the following clarification. You can modify it as you consider the best since I'm not a native English speaker. Which kind of web server should be used by cacti? Select None if you would like to configure your webserver by hand. replace with Important: the default cacti configuration allows public access from Internet. You can see the default configuration file that can be used for apache/apache2 in /etc/cacti/apache.conf. On which web server should cacti be enabled by default? Select None if you would like to configure your web server by hand. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561477: [security] must not RE-add /etc/apache2/conf.d/cacti.conf link on upgrade
[please don't use -quiet as I didn't received the responses though I want to contribute were I can] 2010/1/4 Patrick Schoenfeld schoenf...@debian.org: I've noticed in the past that cacti RE-adds the symbolic link conf.d/cacti.conf on every upgrade even if the source file was *manually* removed by the sysadmin. This is done to restrict the access to 'cacti' on each virtual web site (the default behaviour in Debian). * cacti/webserver: Apache2 The question is: Why did you ask to do this in the first place? (according to your debconf settings) Ok, now I see that this is a way of disabling that symlink. Still, I would like to have the '/etc/cacti/apache.conf' file for reference to update my custom config which simply restricts the access to Intranet. So sorry for the noise, except that I still not understand why people answer a priority high question with Configure my webserver: apache2 just for removing the symlink, it results into after, that. The debconf question is Which kind of web server should be used by cacti? so I answered apache2. Maybe this question should be updated to better describe its meaning? Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561477: [Secure-testing-team] Bug#561477: [security] must not RE-add /etc/apache2/conf.d/cacti.conf link on upgrade
On Thu, Dec 17, 2009 at 5:51 PM, Michael Gilbert michael.s.gilb...@gmail.com wrote: On Thu, 17 Dec 2009 16:13:36 +0200, Teodor wrote: As it can be seen postinstall already has a check for the existence of the config file /etc/cacti/apache.conf. Please add the same check for creating the symlink. this may very well appear to be an issue, but i don't think removing conf files is a good way of trying to increase security. it is certainly not the debian way, and i think all bets are off when it comes to what packages do when their files have gone missing. I think this is covered by Debian policy, at least for init.d scripts which are also considered configuration files. it is much more optimal to manually edit the conf files to achieve whatever security level you desire. as an added bonus, when you upgrade the package, you will get the option to keep your modified conf files. Yes, I usually do the same but Cacti was the exception due to the apache2 symlink which I have forgotten at one cacti upgrade and the cacti graphs were publicly visible for several weeks until I noticed. I still believe that a check should be added for the symlink. If it was removed, don't RE-add it, it the source conf file /etc/cacti/apache.conf doesn't exist remove the broken symlink. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505065: squid: a previous bad configuration causes start/restart to fail
Package: squid Version: 2.7.STABLE3-1 Followup-For: Bug #505065 I've encountered this problem on both 'etch' and current 'lenny' versions. This is one reproducable scenario: squid was running just fine and I've modified this following line by adding 'tproxy'. http_port 3128 transparent With this change, the squid service cannot be restarted or started: Restarting Squid HTTP proxy: squidFATAL: Bungled squid.conf line 1113: http_port 3128 transparent tproxy Squid Cache (Version 2.7.STABLE3): Terminated abnormally. failed! vision:~# lsof -i tcp:3128; netstat -atnpe | grep 3128; pgrep -fl sq 987 /usr/sbin/squid -D -YC So, the service was stopped but the process just hangs and I had to kill it. But it will not start/restart unless I remove these files: vision:~# rm -fv /var/spool/squid/swap.state* removed `/var/spool/squid/swap.state' removed `/var/spool/squid/swap.state.last-clean' (or maybe the first one is enough) In conclusion, this should be done on restart to fix unclean restarts. At least until a proper fix is found. Thanks -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-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/bash Versions of packages squid depends on: ii adduser 3.110 add and remove users and groups ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-16 GNU C Library: Shared libraries ii libcomerr21.41.3-1 common error description library ii libdb4.6 4.6.21-11 Berkeley v4.6 Database Libraries [ ii libkrb53 1.6.dfsg.4~beta1-4 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.11-1 OpenLDAP libraries ii libpam0g 1.0.1-4+b1 Pluggable Authentication Modules l ii logrotate 3.7.1-5Log rotation utility ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii netbase 4.34 Basic TCP/IP networking system ii squid-common 2.7.STABLE3-1 Internet object cache (WWW proxy c squid recommends no packages. Versions of packages squid suggests: pn logcheck-database none (no description available) pn resolvconfnone (no description available) pn smbclient none (no description available) pn squid-cgi none (no description available) pn squidclient none (no description available) pn winbind none (no description available) -- debconf information: squid/fix_cachedir_perms: false squid/fix_lines: true -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
