Package: icedove
Version: 1:45.8.0-2
Severity: important
Dear Maintainer,
* What led up to the situation?
There has been a symlink called .icedove that pointed to the actual
profile. The whole thing happened on an nfs.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Icedove was started with the command icedove for the first time after
the lasted patch icedove:amd64 1:45.6.0-2 1:45.8.0-2.
* What was the outcome of this action?
Icedove behaved strangely and attempted to walk directories unrelated
to icedove iteself and finally got confused when entering the .wine directory
in which it got stuck indefenitly. The errorlog shows it going through the same
files in the .wine-dir again and again but also visiting other directories
before that.
* What outcome did you expect instead?
-
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.8-1-cip-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/dash
Init: systemd (via /run/systemd/system)
Versions of packages icedove depends on:
ii thunderbird 1:45.8.0-2
icedove recommends no packages.
icedove suggests no packages.
-- no debconf information
