sudo kcron problem

[Paul Kaplan]

kcron seems to work fine as a normal user, but not when invoked with sudo or kdesu.

When invoked as sudo kcron, the app starts normally, but when I attempt to add a new task it crashes.

The debugging output is unhelpful (at least to me)

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of
proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

Can anyone help me using the app as a superuser?
TIA
Paul

[claydoh]

Re: sudo kcron problem

try using kdesudo for gui apps, many times running those with sudo doesn't work well, and kdesudo (Gutsy's replacement for kdesu) should handle this well.

[Paul Kaplan]

Re: sudo kcron problem

No luck.

Whether I use kdesu, sudo or kdesudo, kcron launches just fine (after asking for the user password). The problem is that calling for a new task causes the app to crash...and it only crashes if kcron has been invoked via the superuser...works just fine as a normal user.

Paul

[Rog131]

Re: sudo kcron problem

The problem is that calling for a new task causes the app to crash...and it only crashes if kcron has been invoked via the superuser...works just fine as a normal user.

Strange - workaround :

Use kcron as normal user to make crontab file (to me it is easier to use kcron).

Take list from user's crontab (1):

:~$ crontab -u USER -l

(paint and copy it)

Paste it to the root's crontab (2):

:~$ sudo crontab -u root -e

Note
(1) man crontab.
(2) man nano. Default editor is nano (nano - Nano’s ANOther editor, an enhanced free Pico clone.)
USER is your log in name.

[Paul Kaplan]

Re: sudo kcron problem

This worked...thanks.

While doing so, I noticed something about this apparent bug...

Adding a new item only crashes kdesu kcron if no user is selected. Once I select a user (and then the "task" folder, add new item does not cause a crash.

Can anyone confirm on another Kubuntu 7.10 or another distro w/ kde 3.5.8. Is it a kde bug or a kubuntu bug?

Paul