Bug 367782 - kcron will only accept "/" as 1st character
Summary: kcron will only accept "/" as 1st character
Status: RESOLVED WORKSFORME
Alias: None
Product: kcron
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Gary Meyer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-24 22:14 UTC by pmb
Modified: 2022-11-23 05:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pmb 2016-08-24 22:14:22 UTC
The version number of my task scheduler is 5.0

I have a number of gui apps that I use in Kcron. In the past I have written entries in my personal kcron as "export DISPLAY=:0 && app_name"

Due to a persistent bug in neon, I reinstalled the os and went to redo my gui apps. It didn't work.

I tried "export DISPLAY=:0 && app_name" but the OK button remained greyed out.

The only thing that worked was putting /home as the first item and entering
"/home/. . ./bin/app_name --display :0"

The OK button was not greyed out but the app would not run.

I used "crontab -u user -e" and manually inserted the export DISPLAY=:0 && in each of the lines. Closing the app updated cron and systemsettings showed the updated information. As a check I Modifyied one of the lines but the OK button remained greyed out. I had to Cancel.

I cannot reproduce this but one of my entries came up as
"/home/... export DISPLAY=:0 && /home/.../bin/app_name"
As I say I don't know how this instance happened.


Reproducible: Always

Steps to Reproduce:
1. insert export DISPLAY=:0 && before an app name in personal (and others ?) cron in SystemSettings
2.
3.

Actual Results:  
OK button is greyed out until a "/" is entered first

Expected Results:  
Kcron should accept a none "/" starting character

The modified entries do not run when "Run Now" is clicked. They do though run as scheduled cron jobs which I am extremely happy about.

Hope this helps.

Thank You
Comment 1 Justin Zobel 2022-10-24 00:46:35 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-08 05:10:25 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-11-23 05:16:51 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!