Red Hat Bugzilla – Bug 980598
When saving crontab: "can't create directory /tmpqroneko-user
Last modified: 2014-02-05 17:03:06 EST
Description of problem:
When saving the cron jobs from the menu, an error message says:
can't create directory /tmpqroneko
Version-Release number of selected component (if applicable):
qroneko Version 0.4.5
Make any changes to any configured cron job and save the changes from the toolbar. Press ok. An error dialog will show with that message.
Steps to Reproduce:
1. Make any changes to any configured cron job.
2. save the changes from the toolbar.
3. Press ok.
4. The error message shows.
An error dialog shows and the crontab is not saved.
The new crontab should be saved.
It seems there is a missing forward slash in front of /tmp. I tracked down the problem to a specific line in the code, which gets the temp directory and concatenates it to "qroneko" + username.
It's in Crontab.cpp line 80.
Here is a link to the file in question: http://qroneko.cvs.sourceforge.net/viewvc/qroneko/qroneko/Crontab.cpp?revision=1.6&view=markup
QString fdir = QDir::tempPath()+"qroneko-"+Clib::uName();
should probably be:
QString fdir = QDir::tempPath()+"/qroneko-"+Clib::uName();
It seems QDir::tempPath() does not always return /tmp with a trailing slash:
*** Bug 980596 has been marked as a duplicate of this bug. ***
Thanks for bug report looks like qroneko again live, will take the latest source and update during this weekend.
Please create a patch for it and test, then I will merge your patch in source.
Created attachment 784510 [details]
Patch for described changes
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.