Bug#493111: marked as done (kontact: Clicking on "Mail" opens KMail as a seperate window)
Your message dated Thu, 18 Jan 2018 15:54:35 +0100
with message-id
and subject line Re: kontact: Clicking on "Mail" opens KMail as a seperate window
has caused the Debian Bug report #493111,
regarding kontact: Clicking on "Mail" opens KMail as a seperate window
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.)
--
493111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493111
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: kontact: Clicking on "Mail" opens KMail as a seperate window
- From: Arnout Boelens <aboelens@engin.umass.edu>
- Date: Thu, 31 Jul 2008 08:15:23 -0400
- Message-id: <20080731121523.6563.64514.reportbug@localhost.localdomain>
Package: kontact
Version: 4:4.1.0-1
Severity: normal
When I click on the "Mail" icon on the left side in Kontact, KMail opens up in a
seperate window, instead of embeded in the main window.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (700, 'unstable'), (650, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages kontact depends on:
ii kdebase-runtime 4:4.1.0-1 runtime components from the offici
ii kdelibs5 4:4.1.0-1 core libraries for all KDE 4 appli
ii kdepimlibs5 4:4.1.0-1 core libraries for KDE PIM 4 appli
ii korganizer 4:4.1.0-1 KDE personal organizer
ii libc6 2.7-13 GNU C Library: Shared libraries
ii libkdepim4 4:4.1.0-1 KDE PIM library
ii libkholidays4 4:4.1.0-1 holidays calculation library for K
ii libqt4-dbus 4.4.0-4 Qt 4 D-Bus module
ii libqt4-qt3support 4.4.0-4 Qt 3 compatibility library for Qt
ii libqtcore4 4.4.0-4 Qt 4 core module
ii libqtgui4 4.4.0-4 Qt 4 GUI module
ii libstdc++6 4.3.1-8 The GNU Standard C++ Library v3
Versions of packages kontact recommends:
ii kitchensync 4:4.1.0-1 Synchronization framework
ii kmail 4:4.1.0-1 KDE Email client
ii knode 4:4.1.0-1 KDE news reader
ii knotes 4:4.1.0-1 KDE sticky notes
Versions of packages kontact suggests:
ii akregator 4:4.1.0-1 RSS feed aggregator for KDE
ii gnokii 0.6.26.dfsg-2 Datasuite for mobile phone managem
ii knewsticker 4:4.1.0-1 news ticker applet for KDE 4
ii kweather 4:4.0.98-1 weather display applet for KDE
-- no debconf information
--- 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=71408.
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 ---
Reply to: