Bug#998355: samba: Access Time of File is set to the far future: 30828-09-14 04:48:05.477580700 +0200

2022-02-01 Thread Thomas Herrmann
This bug has been resolved upstream. It would be nice to have debian packages of version 4.14.11 or 4.15.3 or higher. https://bugzilla.samba.org/show_bug.cgi?id=14127 Regards Thomas Herrmann

Bug#923377: zfsutils-linux: Updating zfsutils-linux fails with "filesystem already mounted"

2019-02-26 Thread Thomas Herrmann
Package: zfsutils-linux Version: 0.7.12-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Since some zfs updates a while ago, apt cannot set up zfsutils-linux properly: apt-get -f install

Bug#884069: Same problem on Supermicro H8DGi-F

2017-12-11 Thread Thomas Herrmann
Same here with Supermicro H8DGi-F (with only one cpu installed)

Bug#746229: cifs-utils: first attempt at mount.cifs after reboot fails

2014-10-08 Thread Thomas Herrmann
I am seeing exactly the same problem on all my debian clients after migrating the server to samba 4 from backports (4.1.11+dfsg-1~bpo70+1) Things I checked so far: - Using different filesystem on server does not fix the problem. - Updating client to cifs from debian testing or unstable does

Bug#757037: liblzo2-2: Upgrading liblzo2-2 to 2.08 crashes openvpn

2014-08-18 Thread Thomas Herrmann
On 08/18/2014 04:57 AM, Peter Eisentraut wrote: Do you have a reproducible test case for that? Yes, just created one: root@qnap:/etc/openvpn# cat test.conf local 192.168.242.215 port 1194 proto udp dev tun ca ca.crt cert qnap.crt key qnap.key dh dh1024.pem server 192.168.54.0 255.255.255.0

Bug#757037: liblzo2-2: Upgrading liblzo2-2 to 2.08 crashes openvpn

2014-08-04 Thread Thomas Herrmann
Package: liblzo2-2 Version: 2.08-1 Severity: important Dear Maintainer, after upgrading to 2.08-1, openvpn (version 2.3.2-9) fails with the following error message: Cannot initialize LZO compression library Exiting due to fatal error Downgrading to 2.06 fixes the problem for me. -- System

Bug#661008: dovecot-imapd: Corrupted index cache file

2012-07-30 Thread Thomas Herrmann
The parts with the supposedly unread emails is now solved. Here is what happened: - I created public folders with per-user seen flags, granted delete permission but forgot to add expunge rights to the users. - Email clients were configured to delete mails (including expunge) or move mails to

Bug#661008: dovecot-imapd: Corrupted index cache file

2012-07-24 Thread Thomas Herrmann
Some more input on this: Roundcube shows unread messages in some folders in the folder pane, but when I click on it and inspect the folder contents, no new messages can be found. The folder pane continuously shows that the folder contains some unread messages. So this is definitely not a client

Bug#661008: dovecot-imapd: Corrupted index cache file

2012-07-23 Thread Thomas Herrmann
On 03/06/2012 09:26 PM, Jaldhar H. Vyas wrote: On Fri, 24 Feb 2012, Thomas Herrmann wrote: On 02/24/2012 12:42 AM, Timo Sirainen wrote: Anyway, I don't have time to try to debug bugs that may have been fixed already. If this keeps happening with v2.0.18 or v2.1.1 I'm happy to help. Sorry

Bug#661008: dovecot-imapd: Corrupted index cache file

2012-03-07 Thread Thomas Herrmann
completed. I was wondering if this behaviour is related to the one reported in the dovecot mailinglist a few days ago (Subject: LIST-STATUS issue). Regards, Thomas Herrmann -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#661008: dovecot-imapd: Corrupted index cache file

2012-02-23 Thread Thomas Herrmann
Package: dovecot-imapd Version: 1:1.2.15-7 Severity: important Every few hours, I see messages like the following in the logs: Feb 22 09:19:41 mailsrv2 dovecot: IMAP(us...@domain.de): Corrupted index cache file /home/vmail/domain.de/user1/public/.foo/dovecot.index.cache: field header names

Bug#661008: dovecot-imapd: Corrupted index cache file

2012-02-23 Thread Thomas Herrmann
On 02/24/2012 12:42 AM, Timo Sirainen wrote: Anyway, I don't have time to try to debug bugs that may have been fixed already. If this keeps happening with v2.0.18 or v2.1.1 I'm happy to help. The problem occurs on a production server running debian, so which packages do you suggest? I am