Version: 0.9.6 (using KDE KDE 3.5.1) Installed from: Debian testing/unstable Packages OS: Linux Starting klipper as applet dont read the klipperrc config file properly. Runs fine starting klipper as command.
I dont know exactly what's happen but seems a index problem, they asign descriptions of action x+1 to action x, or something like that.
Step by Step procedure. 1) Config Klipper 2) Add New Actions and commands. 3) No problem using klipper, config in memory is correct. 4) Restart kde or (remove and add klipper to the panel) 5) Begins the problem Anyway, I was try many times and I'm not sure if all the times the config file is writed correctly.
You didn't describe the problem itself. How do you know that the config file isn't being read correctly? It seems fine here: I create an action, remove the klipper applet, start the applet again, and the action I created is still there.
Yes, you rigth, the klipperrc file has all the entries but almost in my computer when you try to use klipper selecting some text who match any regexp the descriptions of the actions in the pop-up menu are wrong displayed, I think then only one wrong is the description, if you click on the item the action is correct even the icon of the program is correct. For example if you select some URL Web text... the menu show the konqueror icon and the description says "Open with kmail" ... etc, all the descriptions are worng, seems a index problem, they get the descriptions of action_commands x_y+1 for the action_command x_y.
Correct descriptions are shown here with SVN r519475 . Could you attach your klipperrc file?
Created attachment 15326 [details] my klipper config file
We are currently hunting a strange crash of klipper on startup in Kubuntu Edgy. See bug; https://launchpad.net/bugs/56377 The interesting part is that we are seeing similar pattern (wrong behaviour when started as applet vs. proper behavior when started from command line) but with different result/outcome (config file wrongly read vs. crash). Since crash in Kubuntu Edgy is only seen for two weeks or two, I suspect that crash may be triggered by some change of compiler in Edgy and that before our users just did not notice original bug as logged here.
KDE3 bug. Marking as UNMAINTAINED