Version: (using KDE 4.1.0) Installed from: Mandriva RPMs OS: Linux When you open Kontact, Kmail open in a separate window. As if they were two separate applications. This happens every time and doesn't matter Kontact or Kmail has been running before or not. This only happens with KDE4 desktop. When you open Kontact in Gnome everything is fine.
Didn't you open kmail then close it before running kontact ?
Just did the latest update of Mandriva cooker and all is well! Excellent, good work!
This still happens for me in KDE 4.2 beta 2. However, it does not happen *every* time and so far, I was not able to find a pattern when this problem would always happen or not. One related fact might be that I have parts of my address book lying on an "IMAP server via Kmail", so I think it is possible that when Kontact tries to query for some data, e.g. birthdays for the summary tab, it has to launch Kmail beforehand to be able to access contact data.
I'm having the same problem (except that it happens every time for me), and also like Tobias, I have my address book and calendar on an IMAP server via Kmail.
This bug is still present for me with KDE 4.2.1 also using dimap for calendar and addressbook. BUG 185596 seems to be a duplicate of this bug.
*** Bug 185596 has been marked as a duplicate of this bug. ***
I can no longer reproduce it.
I have this problem as well. Until the update last night, I could get Kmail to open in Kontact if I opened Kontact first. If I closed Kontact, Kmail would automatically reopen. Since the update last night, nothing I do will get Kmail to open in Kontact, it always opens in a separate window of its own. Whether I close it with Kontact open or not, if I click the mail button in Kontact, Kmail opens in its own window. I tried with IMAP Resources both enabled and disabled. If I continue to repeat the procedure of killing Kmail and selecting its icon in Kontact, I can somehow finally get kmail to embed in Kontact. I'm not sure how, there doesn't seem to be any rhyme to it. on the CLI, running Kontact and finally getting Kmail to embed, I got this output. Not sure if its related or not. X Error: BadAtom (invalid Atom parameter) 5 Major opcode: 17 (X_GetAtomName) Resource id: 0x1c000d40 X Error: BadAtom (invalid Atom parameter) 5 Major opcode: 17 (X_GetAtomName) Resource id: 0x1c004240 X Error: BadAtom (invalid Atom parameter) 5 Major opcode: 17 (X_GetAtomName) Resource id: 0x1c004660 X Error: BadAtom (invalid Atom parameter) 5 Major opcode: 17 (X_GetAtomName) Resource id: 0x1c000ca0 kontact(5927) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" kontact(5927) KStatusBar::removeItem: KStatusBar::removeItem: bad item id: 2
@xaos: when kmail is already running(even in system tray) and you open kontact, it won't embed in kontact. If kmail is not running and kontact is opened then it is embedded.
The problem is, it is nearly impossible to close Kmail. A "pkill kmail && kontact" seems to work usually, but if the system tray icon is enabled, it's impossible (afaik) to get Kmail to stay closed long enough to open Kontact (without resorting to opening it in a terminal). If there is a better way of closing Kmail, I'm all ears, or eyes as it were.
@Xaos: You can easily close kmail by right clicking and selecting quit in system tray iconm, isn't it?
@Rushir: It reopens automatically when you do that.
(In reply to comment #12) > @Rushir: It reopens automatically when you do that. In my experience this is a different bug, as it started at a different time for me. I have created bug 188873 for this problem.
This does not happen for me any longer with KDE 4.2.3.
This no longer happens for me, so I assume the problem is fixed.
Yes, seems to be fixed. Hasn't happened in months now...
This bug is still not fixed properly. It used to appear a few months ago, then stopped and now it's back. Since I was fiddling with the configuration recently, it's probably caused by that. I definitely don't remember configuring kmail to open in separate window, though. Since quitting KMail from tray (comment 11) resolves this for the current session, is it possible that something (Akonadi?) launches KMail to display a notification (new mail) instead of launching Kontact as a whole? That even sounds reasonable. Second idea: is the behaviour described in comment 9 correct? I believe in this situation KMail should get embedded in Kontact even if it was already running standalone before. KDE Plasma Version: 5.11.5 KDE Frameworks Version: 5.42.0 Qt Version: 5.10.0 OS: Manjaro
FYI This problem appears for me on clean kontact configuration with previous kmail setup. I solved this by launched one time kontact --module kmailplugin Kontact 6.2.1 (24.08.1) dev 6.6.0 Qt Version 6.7.3 (Compilé avec 6.7.2) wayland on archlinux 6.11.2-arch1-1 x86_64 GNU/Linux systemd-homed some logs : Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/bin/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/qtwebengine_dictionaries' Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) qt.svg.draw: The requested buffer size is too big, ignoring qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/bin/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/qtwebengine_dictionaries' qt.svg.draw: The requested buffer size is too big, ignoring qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 We have an error during reading password "Entry not found" kf.xmlgui: 0x713d2400fcd0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kf.xmlgui: 0x64f4a0880308 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.