Bug#759339: systemd-cryptsetup-generator: systemd-cryptsetup-generator fails to handle multiple encrypted btrfs volumes in raid1

2014-08-26 Thread Damien Clauzel
Yes. But there is also the problem of assembling the btrfs raid1 arrays after opening the encrypted volumes. Damien Clauzel 2014-08-26 16:41 GMT+02:00 Michael Biebl bi...@debian.org: Am 26.08.2014 15:54, schrieb Damien CLAUZEL: Package: systemd Version: 208-8 Severity: normal File

Bug#739902: apt-listbugs: incorrect warning for Insecure world writable dir /tmp/

2014-02-24 Thread Damien Clauzel
2014-02-24 0:26 GMT+01:00 Francesco Poli invernom...@paranoici.org: Did you by chance modify /etc/apt/apt.conf.d/10apt-listbugs ? Could you please paste its content in your reply? That is what I have been thinking. We didn't change the config of apt-listbugs, but we have several several

Bug#739902: apt-listbugs: incorrect warning for Insecure world writable dir /tmp/

2014-02-23 Thread Damien CLAUZEL
Package: apt-listbugs Version: 0.1.12 Severity: minor When running, apt-listbugs displays a warning: /usr/sbin/apt-listbugs:282: warning: Insecure world writable dir /tmp/. in PATH, mode 041777 My /tmp is indeed in this mode (rwx rwx rwt), but those access permissions are ok. -- System

Bug#739902: apt-listbugs: incorrect warning for Insecure world writable dir /tmp/

2014-02-23 Thread Damien Clauzel
2014-02-23 23:22 GMT+01:00 Francesco Poli invernom...@paranoici.org: I suppose that maybe having the current directory (.) in my PATH triggered this warning, if apt-listbugs runs a script that it wrote in /tmp/. If this is the case, then the warning is also incorrect. I cannot reproduce

Bug#739902: apt-listbugs: incorrect warning for Insecure world writable dir /tmp/

2014-02-23 Thread Damien Clauzel
2014-02-23 23:54 GMT+01:00 Francesco Poli invernom...@paranoici.org: You were in /root as the root user, with the previously quoted PATH. Yes, I was connected as root, in /root. First, remote connection via ssh to a unprivileged user account, then sudo su; cd /root Which command did you issue?

Bug#717776: tmux segfault

2013-12-17 Thread Damien CLAUZEL
Package: tmux Version: 1.8-5 Followup-For: Bug #717776 Tmux segfaults also on my server. No obvious reason. I have those kind of entries in /var/log/kern.log ___ kernel: [429068.871487] tmux[5032]: segfault at 77142b68 ip b7514032 sp bfac5040 error 6 in libc-2.17.so[b74cf000+1ad000] ___ I am

Bug#731386: /usr/sbin/checkrestart: debian-goodies: checkrestart crashes with AttributeError: 'list' object has no attribute 'startswith'

2013-12-04 Thread Damien CLAUZEL
Package: debian-goodies Version: 0.63 Severity: normal File: /usr/sbin/checkrestart checkrestart was working before; it isn't anymore. No idea what changes has been made on the system. Good luck :) ___ # checkrestart Traceback (most recent call last): File /usr/sbin/checkrestart, line 637,

Bug#719276: sockstat: does not provide information on IPv6

2013-08-09 Thread Damien CLAUZEL
Package: sockstat Version: 0.3-1.1 Severity: normal Sockstat does not provide any informations about IPv6. That is a real problem, and is even misleading for the dual network stack systems. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'),

Bug#691839: New upstream version available (4.5.6)

2013-03-03 Thread Damien CLAUZEL
Package: owncloud Version: 4.0.4debian2-3.3 Followup-For: Bug #691839 Release 4.5.7 is now the current one. OwnCloud 4.0.4 is deeply obsolete and has several vulnerabilities. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#657355: pygopherd: fails to bind to an IPv6 address

2012-01-25 Thread Damien CLAUZEL
Package: pygopherd Version: 2.0.18.3+nmu2 Severity: normal I am trying to run a gopher server on IPv6 (don’t ask me why :), but it does look like pygopherd cannot bind on an IPv6 address. o In /etc/pygopherd/pygopherd.conf I tried the following setup, but none work: interface =

Bug#652874: bti: fails to run because of missing lib

2011-12-21 Thread Damien CLAUZEL
Package: bti Version: 031-2 Severity: grave Justification: renders package unusable After doing a normal install, bti is missing some lib required for running. That is bad. ___ $ bti bti: /usr/lib/x86_64-linux-gnu/libcurl-nss.so.4: version `CURL_NSS_3' not found (required by

Bug#647275: ntop segfault with free(): invalid pointer

2011-11-01 Thread Damien CLAUZEL
Package: ntop Version: 3:4.1.0+dfsg1-1 Severity: normal While running ntop, it tend to crash after about 24 hours with this in the log file: ___ Nov 1 00:30:17 serveur ntop[29935]: **WARNING** packet truncated (8754-8232) Nov 1 00:32:49 serveur ntop[29935]: **WARNING** packet truncated

Bug#645916: selinux: segfault in boot

2011-10-19 Thread Damien CLAUZEL
Package: selinux-basics Version: 0.3.8 Severity: normal When I setup SELINUX=permissive in /etc/selinux/config, the computer fails to boot correctly (cannot start X11, but the console is ok). The following entries are written in kern.log The interesting one is « 119 Oct 19 17:30:33 portable

Bug#607441: tracd: doesn't accept to bind to IPv6 address

2010-12-18 Thread Damien CLAUZEL
Package: trac Version: 0.11.7-4 Severity: minor Running trac on standalone mode, via tracd, is not possible on IPv6-only systems. Tracd should be able to bind to an IPv6 address. Example with a fresh trac install on user crapp. ___ # sudo -u crapp tracd --http11 --auto-reload --single-env

Bug#588467: memtest86+: fails to install

2010-07-08 Thread Damien CLAUZEL
Package: memtest86+ Version: 4.00-2.3 Severity: normal Fails to install while updating with apt-get upgrade ___ … Les paquets suivants seront mis à jour : memtest86+ 1 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour. 1 partiellement installés ou enlevés. Il est nécessaire