Bug 84827

Summary: configure toolbars dialog removes selected icon when adding 2 actions
Product: [Unmaintained] kdelibs Reporter: Martin Koller <kollix>
Component: kedittoolbarAssignee: David Faure <faure>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: finex, mattr
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Martin Koller 2004-07-09 20:11:20 UTC
Version:           1.6.82 (using KDE 3.2.91 (CVS >= 20040706), compiled sources)
Compiler:          gcc version 3.2.3
OS:                Linux (i686) release 2.4.22

Using the "configure toolbars" dialog, I see the following bug:
Add a new action to a toolbar, select an icon for it.
Now add a second action (without closing the dialog) to the toolbar => the icon for the first added action disappears.
Comment 1 Waldo Bastian 2004-07-29 23:28:19 UTC
Adding an icon to an action doesn't work at all here.
Comment 2 Matt Rogers 2005-09-18 22:30:54 UTC
Still seeing this with KDE 3.5 from SVN. 

Some more info:
- It doesn't matter if the second action has an icon or not. 
- Be sure to not click apply between changing the icon for the first action and adding the second icon.
Comment 3 Matt Rogers 2005-09-18 22:31:39 UTC
hmm, actually, i'm currently using KDE 3.4.2 not 3.5 from SVN. Will retest
Comment 4 Martin Koller 2006-12-28 19:43:05 UTC
The bug is still present in current 3.5.5 head
Comment 5 FiNeX 2008-03-08 15:56:19 UTC
Bug valid both for KDE 3.5.8 AND KDE 4.0.2.
Comment 6 Martin Koller 2009-07-28 19:35:22 UTC
Still valid in KDE 4.3
Comment 7 David Faure 2010-11-19 02:41:56 UTC
Note that it actually works, i.e. the icon is used when pressing Apply or OK.
But indeed in the active action list the icon is lost for some reason.
Comment 8 Martin Koller 2012-01-29 12:08:30 UTC
Still valid in KDE 4.8.0
Comment 9 Christoph Cullmann 2024-09-14 17:06:46 UTC
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have resolved this bug.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann