KDE - Commands

[Thor77]

editing the ~/.blueproximityrc the lock and unlock commands ar added with a space bevore so the command sh anything are not recognised by the interpreter

I tryed the folowing: lock_command = xscreensaver-command -activate unlock_command = xscreensaver-command -deactivate

both did not work with the error: command not found

by modifiying the two lines to: lock_command="xscreensaver-command -activate" unlock_command="xscreensaver-command -deactivate"

it worked once but overwrote these lines with the first two.

making the file read only did not work, because the programm did not start at all.

Please Fix this, so kde users could use the programm too.

Thanks Valentin vz1[remove]@gmx.net

[Thor77]

Logged In: YES user_id=114903 Originator: NO

... and since 1.1.8 they actually work :-) (By highno)

[Thor77]

Logged In: YES user_id=114903 Originator: NO

This bug is fixed in SVN and nightly. New Version (>=1.1.7) will include a gui frontend to change the commands to make this editing easier and no need to change the source then... (By highno)

[Thor77]

Logged In: YES user_id=114903 Originator: NO

Please note that your should also use

xscreensaver-command -lock

to securely lock the screen. Refer to Bug #1778306 for more information. (By highno)

[Thor77]

Logged In: YES user_id=114903 Originator: NO

I will check that - that could be a problem with configobj which is used to manage, read and write the config file. (By highno)

[Thor77]

Logged In: NO

Editing the python source solved the problem. I replaced the default strings with the ones i wanted it to usw, deleted the config files and reconfigured the Program.

You might add a Note about this in the readme file.

Thx Valentin (By nobody)

[Thor77]

Logged In: NO

Editing the python source solved the problem. I replaced the default strings with the ones i wanted it to usw, deleted the config files and reconfigured the Program.

You might add a Note about this in the readme file.

Thx Valentin (By nobody)