Your message dated Thu, 18 Jan 2018 16:02:07 +0100
with message-id
and subject line Re: [kmail] Cannot move folder into upmost folder (Local
Folder)
has caused the Debian Bug report #556145,
regarding [kmail] Cannot move folder into upmost folder (Local Folder)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
556145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmail
Version: 4:4.3.1-2
Severity: normal
--- Please enter the report below this line. ---
When right clicking a folder, activating "move folder", and choosing some
target folder, I can move my mail folders. This seems to work for every
target folder - except the upmost "Local Folder".
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.30-1-686-bigmem
Debian Release: squeeze/sid
50 unstable ftp.uni-kl.de
50 unstable ftp.de.debian.org
150 testing security.eu.debian.org
150 testing ftp.uni-kl.de
150 testing ftp.de.debian.org
150 stable volatile.debian.org
150 stable security.eu.debian.org
150 stable ftp.uni-kl.de
150 stable ftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
=======================================-+-==============
kdebase-runtime (>= 4:4.3.0) | 4:4.3.2-1
kdelibs5 (>= 4:4.3.1) | 4:4.3.2-2
kdepimlibs5 (>= 4:4.3.1) | 4:4.3.2-1
libc6 (>= 2.4) | 2.10.1-5
libgcc1 (>= 1:4.1.1) | 1:4.4.1-4
libkdepim4 (= 4:4.3.1-2) | 4:4.3.1-2
libkleo4 (= 4:4.3.1-2) | 4:4.3.1-2
libkontactinterfaces4 (= 4:4.3.1-2) | 4:4.3.1-2
libkpgp4 (= 4:4.3.1-2) | 4:4.3.1-2
libksieve4 (= 4:4.3.1-2) | 4:4.3.1-2
libmimelib4 (= 4:4.3.1-2) | 4:4.3.1-2
libphonon4 (>= 4:4.3.1) | 4:4.5.3-4
libqt4-dbus (>= 4:4.5.2) | 4:4.5.3-4
libqt4-network (>= 4:4.5.2) | 4:4.5.3-4
libqt4-qt3support (>= 4:4.5.2) | 4:4.5.3-4
libqt4-xml (>= 4:4.5.2) | 4:4.5.3-4
libqtcore4 (>= 4:4.5.2) | 4:4.5.3-4
libqtgui4 (>= 4:4.5.2) | 4:4.5.3-4
libstdc++6 (>= 4.2.1) | 4.4.1-4
phonon (>= 4:4.5.2) | 4:4.5.3-4
perl | 5.10.1-5
Recommends (Version) | Installed
=========================-+-===========
procmail | 3.22-18
Suggests (Version) | Installed
===============================-+-===========
gnupg | 1.4.10-2
gnupg-agent | 2.0.13-1
pinentry-qt4 |
OR pinentry-x11 |
kaddressbook | 4:4.3.1-2
kleopatra | 4:4.3.1-2
spamassassin | 3.2.5-6
OR bogofilter |
OR annoyance-filter |
OR spambayes |
OR bsfilter |
OR crm114 |
clamav |
OR f-prot-installer |
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Dear bug submitter,
Thank you for reporthing this issue. The bug has been determined not to be
Debian specific, and therefore was reported in the KDE bugtracker; see
https://bugs.kde.org/show_bug.cgi?id=197382.
We are sorry it has not been resolved. However, the version in which the
issue was reported is now obsolete and the upstream tracker has closed the
issue. Thus we are also closing the issue in Debian bug tracker.
If you think the bug is still relevant to a KDE Pim version in Debian stable
(aka Stretch) or newer -- i.e. part of KDE Applications 15.08.0 or newer --
then please open a new bugreport upstream and add your new information in the
upstream bugreport.
Again, thank you for reporting the issue. If there are any questions feel free
to ask.
KDE upstream bug tracker closed their bug with following statement:
"This bug has only been reported for versions before 15.08.0, which have been
unsupported for at least two years now. Can anyone tell if this bug still
present?
If noone confirms this bug for a Framework-based version of kontact
(version 5.0 or later, as part of KDE Applications 15.08 or later),
it gets closed in about three months.
Just as announced in my last comment, I close this bug.
If you encounter it again in a recent version (at least 5.0 aka 15.08),
please open a new one unless it already exists. Thank you for all your input."
--- End Message ---
