Bug#632255: marked as done (kmail: Kmail does not start properly or "close/minimise" to the system tray)
Your message dated Wed, 04 Feb 2015 00:37:50 +0100
with message-id <3246716.dEUXJlQmIB@tabin.local>
and subject line Re: Bug#632255: kmail: Kmail does not start properly or "close/minimise" to the system tray
has caused the Debian Bug report #632255,
regarding kmail: Kmail does not start properly or "close/minimise" to the system tray
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 owner@bugs.debian.org
immediately.)
--
632255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632255
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: kmail: Kmail does not start properly or "close/minimise" to the system tray
- From: Adam Trickett <adam@iredale.net>
- Date: Thu, 30 Jun 2011 23:31:49 +0100
- Message-id: <20110630223149.14182.70776.reportbug@wombat.iredale.net>
Package: kmail
Version: 4:4.4.11.1+l10n-1
Severity: important
When you start KMail it starts to run automatically on login from a saved session,
you can see it in ps aux but nothing appears on the screen. You have to kill it
and manually start it again, before it appears.
If you close the application it vanishes - it doesn't close to the system tray
like it use to, but it is still running, which you can veryify with ps.
Starting the application from a menu, button or command line brings it back
to a visible foreground application.
Trying the differnent "System Tray" integration options doesn't seem to make
any difference.
If you don't know what is going on you'd say it makes the application unsuable
(i.e. IMPORTANT) if you know what is going on it's highly annoying but KMail
is still usable (i.e. NORMAL).
Running Kontact doesn't seem to make it anymore reliable, it's still wobbly.
This all works fine in the Squeeze version. I'm guessing this behaviour is
a manifestation of the same source problem, but feel to split/reassign if
that is more appropiate.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.39-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages kmail depends on:
ii kdebase-runtime 4:4.6.3-1 runtime components from the offici
ii kdepim-runtime 4:4.4.11.1-2 Runtime components for akonadi-kde
ii kdepimlibs-kio-plug 4:4.6.3-1 kio slaves used by KDE PIM applica
ii libakonadi-contact4 4:4.6.3-1 library for using the Akonadi PIM
ii libakonadi-kde4 4:4.6.3-1 library for using the Akonadi PIM
ii libc6 2.13-7 Embedded GNU C Library: Shared lib
ii libgcc1 1:4.6.0-10 GCC support library
ii libgpgme++2 4:4.6.3-1 c++ wrapper library for gpgme
ii libkabc4 4:4.6.3-1 library for handling address book
ii libkcal4 4:4.6.3-1 library for handling calendar data
ii libkcmutils4 4:4.6.3-3 utility classes for using KCM modu
ii libkde3support4 4:4.6.3-3 KDE 3 Support Library for the KDE
ii libkdecore5 4:4.6.3-3 KDE Platform Core Library
ii libkdepim4 4:4.4.11.1+l10n-1 KDE PIM library
ii libkdeui5 4:4.6.3-3 KDE Platform User Interface Librar
ii libkhtml5 4:4.6.3-3 KHTML Web Content Rendering Engine
ii libkimap4 4:4.6.3-1 library for handling IMAP data
ii libkio5 4:4.6.3-3 Network-enabled File Management Li
ii libkldap4 4:4.6.3-1 library for accessing LDAP
ii libkleo4 4:4.4.11.1+l10n-1 certificate based crypto library
ii libkmime4 4:4.6.3-1 library for handling MIME data
ii libknotifyconfig4 4:4.6.3-3 library for configuring KDE Notifi
ii libkontactinterface 4:4.6.3-1 Kontact interface library
ii libkparts4 4:4.6.3-3 Framework for the KDE Platform Gra
ii libkpgp4 4:4.4.11.1+l10n-1 gpg based crypto library
ii libkpimidentities4 4:4.6.3-1 library for managing user identiti
ii libkpimtextedit4 4:4.6.3-1 library that provides a textedit w
ii libkpimutils4 4:4.6.3-1 library for dealing with email add
ii libkresources4 4:4.6.3-1 KDE Resource framework library
ii libksieve4 4:4.4.11.1+l10n-1 mail/news message filtering librar
ii libktnef4 4:4.6.3-1 library for handling TNEF data
ii libmailtransport4 4:4.6.3-1 mail transport service library
ii libmessagecore4 4:4.4.11.1+l10n-1 message core library
ii libmessagelist4 4:4.4.11.1+l10n-1 message list library
ii libmimelib4 4:4.4.11.1+l10n-1 MIME library
ii libnepomuk4 4:4.6.3-3 Nepomuk Meta Data Library
ii libphonon4 4:4.6.0really4.5.0-3 multimedia framework from KDE - co
ii libqt4-dbus 4:4.7.3-1 Qt 4 D-Bus module
ii libqt4-network 4:4.7.3-1 Qt 4 network module
ii libqt4-qt3support 4:4.7.3-1 Qt 3 compatibility library for Qt
ii libqt4-xml 4:4.7.3-1 Qt 4 XML module
ii libqtcore4 4:4.7.3-1 Qt 4 core module
ii libqtgui4 4:4.7.3-1 Qt 4 GUI module
ii libstdc++6 4.6.0-10 The GNU Standard C++ Library v3
ii libthreadweaver4 4:4.6.3-3 ThreadWeaver Library for the KDE P
ii perl 5.12.3-7+b1 Larry Wall's Practical Extraction
ii phonon 4:4.6.0really4.5.0-3 multimedia framework from KDE - me
Versions of packages kmail recommends:
ii gnupg-agent 2.0.17-2 GNU privacy guard - password agent
ii gnupg2 2.0.17-2 GNU privacy guard - a free PGP rep
ii pinentry-qt4 [pinentry-x11] 0.8.1-1 Qt-4-based PIN or pass-phrase entr
Versions of packages kmail suggests:
pn clamav | f-prot-instal <none> (no description available)
ii kaddressbook 4:4.4.11.1+l10n-1 address book and contact data mana
ii kleopatra 4:4.4.11.1+l10n-1 certificate Manager
pn procmail <none> (no description available)
pn spamassassin | bogofil <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4:4.14.2-2
> For my sins I forgot about this... It is working okay in current stable and
> testing. I can't remember how long I had to put up with it, but it's okay
> now...
so let's close the bug than. Feel free to reply if you find the issue again.
Regards,
sandro
--- End Message ---
Reply to: