but does it launch properly in Konsole using DISPLAY? do other gui apps run properly from Kcron? is Kcron or Ktorrent the problem?

have you tried using a command alarm in Kalarm for this, works for me

need to go but will test Kcron later

google01103 wrote:but does it launch properly in Konsole using DISPLAY?

yes

do other gui apps run properly from Kcron?

No Kcron seems to be the problem

have you tried using a command alarm in Kalarm for this, works for me

yes it works but I need to remember to run Kalarm, also Kcrom was working fine and I also would like to know why moving to 64 caused this problem.

Thanks,

Michel

Kalarm has a repetition tab so just set it and forget it

Kcron seems to run Ktorrent fine for me but it doesn't show in the task bar, it starts minimized to the system tray and it is one of the hidden icons

I tried running it again but I get nothing. Not in the tray and not hidden. I guess I will have to use Kalarm (although I would have liked to uncover the problem)

Thank you for your help.

Michel

This morning my Kernel was upgraded from 3.2.0-33 to 3.2.0-34 and that seems to have solved the problem. Ktorrent will now launch with

Code: Select all

env DISPLAY=:0 ktorrent

but not with

Code: Select all

usr/bin/ktorrent

as it used to before this whole saga.

Should someone report a bug or something?

Thanks,

Michel

michelmassoud wrote:This morning my Kernel was upgraded from 3.2.0-33 to 3.2.0-34 and that seems to have solved the problem. Ktorrent will now launch with

Code: Select all

env DISPLAY=:0 ktorrent

but not with

Code: Select all

usr/bin/ktorrent

as it used to before this whole saga.

Should someone report a bug or something?

Thanks,

Michel

you mean "/usr/bin/ktorrent" not "usr/bin/ktorrent" - the preceding / is critical

Yes /usr/bin/ktorrent.

Michel

As KCron is an interface to crontab - this is not really a bug as it is behaviour of the underlying system - and it cannot really be corrected unfortunately, without introducing other unexpected issues (If another user is logged in when the cronjob runs then either the command will fail or the other user will be given control over an application running under your user account - allowing access to your data, and potentially execution of other applications as you, with the possibility of escalation to root if you have sudo access).

There are also other risks - such as the application not being started with the appropriate session environment (so it looks out of place) or other consequences. I would suggest starting it using the following command instead, which will ask your KDE session to run KTorrent:

Code: Select all

qdbus org.kde.klauncher /KLauncher exec_blind ktorrent --

Thanks a lot.

Things are running well now and I have no one else using my computer but I will certainly try this new command.

Michel