Summary: | Kontact toolbars are corrupted on edit | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Nicolas Chevreux <nicolas> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | mail, raphael, wstephenson |
Priority: | NOR | Keywords: | triaged |
Version: | SVN trunk | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nicolas Chevreux
2006-04-02 07:35:48 UTC
I confirm this too on kde 3.4 3.5.0. 3.5.1 and the latest 3.5.2. I use KDE 3.5.2, Gentoo Linux (x86_64) release 2.6.14-gentoo gcc version 3.4.5 (Gentoo 3.4.5, ssp-3.4.5-1.0, pie-8.7.9) I am experiencing the exact similar behaviour. I swap the icons too on startup so that the buttons reappear Original reporter: can you workaround this by using the Navigator toolbar? And here's another report (#74693 at bugzilla.novell.com) How to reproduce: Start Kontact Have the "Navigator" Toolbar visible Switch to the KMail component Select "Settings -> Configure Toolbars..." Choose "Main Toolbar <kmmainwin>" as Toolbar to configure Change something Apply 1. The Toolbar has now the combined "New" icon from Kontact (with popup arrow, offering New Message, New Event, New Todo etc) and a "New Message" (no popup). Switching to another component in Kontact and back to KMail fixes this. 2. The Navigator Toolbar is empty now. Switching components doesn't fix it, only restarting Kontact does. The issue still exists in trunk with the same steps as in the original report. This bug is still current for kontact 4.9.4. This bug has only been reported for versions before 4.14, 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. |