kontact toolbar always forgets the "new mail" button

[ronny]

Binary package hint: kdepim

I use kontact for email and want to have the "new mail" button in the toolbar. I can configure to have it there, it also appears but after restarting kontact the "new mail" button is gone again. A real hassle...
Please see the attached video for a demonstration.

ProblemType: Bug
Architecture: i386
Date: Mon Nov 2 22:24:37 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kontact
NonfreeKernelModules: nvidia
Package: kontact 4:4.3.2-0ubuntu6
ProcEnviron:
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: kdepim
Uname: Linux 2.6.31-14-generic i686
XsessionErrors: (polkit-gnome-authentication-agent-1:1659): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Jonas Pedersen (jonasped)]

Thanks for the report. I am running Karmic as well and is also using Kontact. I am not able to reproduce the problem. Every time I start Kontact the "new mail" button is available in the toolbar.

Could you please try to clear all your KDE settings and configure Kontact again or create a new user and configure Kontact and see if the problem persists.

[ronny (ronny-standtke)]

I can reproduce the problem now:
Because I use the "Check Mail" button much more often than the "New Message" button, I wanted to have this order in the toolbar:
Check Mail | New | ...
Therefore I removed the "New Message..." button from the kontact main toolbar. That's all. Now the issue is always reproducible (see attached demo video).

[Jonas Pedersen (jonasped)]

Tried to play a bit more around and followed your video and now I am able to reproduce this error.

[ronny (ronny-standtke)]

OK, thanks for confirming this issue. How do we proceed now? Do we report this bug upstream (bugs.kde.org) or is it enough to have this bug report here for Kubuntu in Launchpad?

[Jonas Pedersen (jonasped)]

On Saturday 07 November 2009 14:02:11 ronny wrote:
> OK, thanks for confirming this issue. How do we proceed now? Do we
> report this bug upstream (bugs.kde.org) or is it enough to have this bug
> report here for Kubuntu in Launchpad?

First of all we should try the new KDE 4.3.3 and see if the error is
corrected. If that is not the case we should submit an upstream bug. I am not
at home right now, but if I get the time I will try the new KDE 4.3.3
(http://www.kubuntu.org/news/kde-4.3.3) a bit later today or tomorrow.

--
Jonas Pedersen - jonas - at - jope.eu / http://jope.eu
Online picture gallery at http://pictureshow.dk

[ronny (ronny-standtke)]

> First of all we should try the new KDE 4.3.3 and see if the error is
> corrected. If that is not the case we should submit an upstream bug.

I just tested KDE-4.3.3 and the issue is still there. To prevent double bug reports I let you decide who of us is going to do the upstream report.

[Jonas Pedersen (jonasped)]

On Sunday 08 November 2009 21:07:22 you wrote:
> > First of all we should try the new KDE 4.3.3 and see if the error is
> > corrected. If that is not the case we should submit an upstream bug.
>
> I just tested KDE-4.3.3 and the issue is still there. To prevent double
> bug reports I let you decide who of us is going to do the upstream
> report.
>

I think you have the most details about this bug, so suggest you create it
upstream. After you have created it upstream you can link the newly created
bug to this one.

--
Jonas Pedersen - jonas - at - jope.eu / http://jope.eu
Online picture gallery at http://pictureshow.dk

[ronny (ronny-standtke)]

Done:
https://bugs.kde.org/show_bug.cgi?id=215655

[Jonathan Thomas (echidnaman)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at: http://bugs.kde.org/show_bug.cgi?id=215655
Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.

Thanks!