https://bugs.kde.org/show_bug.cgi?id=416706
Ahab Greybeard <ahab.greybe...@hotmail.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO
CC| |ahab.greybe...@hotmail.co.u
| |k
--- Comment #1 from Ahab Greybeard <ahab.greybe...@hotmail.co.uk> ---
I was initially unable to reproduce this on 4.2.6 to 4.2.9(Stable) appimages
The kritarc entry for me was FilterSelector/LastUsedFilter=gaussian blur and
was unchanged no matter which filter I used.
I found filterdialog/rememberlastpreset=false and changed it to true and was
unable to reproduce the fault.
The entry for FilterSelector/LastUsedFilter= did not change no matter which
filter I used.
If I changed it to FilterSelector/LastUsedFilter=halftone then I could not
reproduce the fault.
However, if I deleted kritarc and restarted with fresh configuration the entry
for FilterSelector/LastUsedFilter= did not get recorded in kritarc.
I manually made filterdialog/rememberlastpreset=true and the
FilterSelector/LastUsedFilter= line did not appear in kritarc after filter uses
and restarts.
Then I manually entered FilterSelector/LastUsedFilter=halftone and then the
fault appeared exactly as described in the initial report.
There are probably other entries in kritarc which I'm not aware of that may be
significant in this matter.
Maybe if you edit kritarc to have filterdialog/rememberlastpreset=false (if it
is set to true for you)?
Does your FilterSelector/LastUsedFilter= entry ever change after using the
filters?
--
You are receiving this mail because:
You are watching all bug changes.
