** Bug watch added: Debian Bug tracker #1071456
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071456
** Changed in: autopkgtest (Debian)
Status: Fix Committed => Unknown
** Changed in: autopkgtest (Debian)
Remote watch: Debian Bug tracker #1068363 => Debian Bug tracker #1071456
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056461
Title:
autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
To manage notifications about this bug go to:
The Debian ROCm Team has also seen this in their CI instance. One data
point that might be relevant is that in our case, all our failures were
limited to autopkgtests where there was a reboot between tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm afraid that this is by design, to prevent a malicious user from
dumping basically anything into one of the crontab directories.
An attacker once compromised a debian.org host by triggering a crafted
core dump in one of the crontab directories, and the daemon kept trying
to execute lines until
This was fixed in -121.
** Changed in: cron (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110147
Title:
Error in manual
To manage notifications
rumps your
specification of column 3.
The man page contains an example for how to work around this.
--
Christian Kastner
** Changed in: cron (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 2016-08-01 07:40, Jeremy Bicha wrote:
> This was auto-synced to Ubuntu "yakkety" already:
>
> https://launchpad.net/ubuntu/+source/gitinspector/0.4.4+dfsg-4
>
> Until Debian Import Freeze, packages that are not current modified in
> Ubuntu are automatically synced to Ubuntu so there's no need
Public bug reported:
Hi,
I would like to request a sync of gitinspector-0.4.4+dfsg-4 from Debian
unstable. I recently uploaded fixes for two bugs that were initially
reported upstream:
* https://github.com/ejwa/gitinspector/issues/120
* https://github.com/ejwa/gitinspector/issues/121
These
On 2016-01-19 04:01, Humphrey van Polanen Petel wrote:
> Just so you know, it *is* a cron command.
> Gnome Schedule is nothing but a pretty gui to crontab.
And that pretty GUI is from an entirely separate package than package
cron, against which you reported the bug.
> I suggest you be a bit
On 2016-01-15 00:47, Humphrey van Polanen Petel wrote:
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
>
> Gnome _schedule command preview=/usr/local/bin/bup
^^
That's not a cron command, that is some independent Gnome frontend. cron
only
This is a valid request. I've linked this bug to the corresponding bug
in Debian's cron.
** Changed in: cron (Ubuntu)
Status: Invalid = Confirmed
** Bug watch added: Debian Bug tracker #561295
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561295
** Also affects: cron (Debian) via
Hi,
On 2015-03-07 18:16, sgofferj wrote:
On my main server I see unexplainable time jumps backwards in the syslog.
Those jumps affect CRON.
Example:
Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD (
/storage/exec/checkinternet.sh 2/dev/null 1/dev/null)
Feb 10 06:49:01 nostromo
3.0pl1-124.1ubuntu1 contains a fix for this.
** Changed in: cron (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1067779
Title:
cron jobs are started by the cron daemon which is completely unrelated
to your GUI session, or any other session that might be active for the
user.
As ccooke pointed out, if you want access to an unrelated session,
you're going to have to do it manually.
** Changed in: cron (Ubuntu)
Fix
** Changed in: cron (Ubuntu)
Status: New = Fix Released
** Package changed: cron (Ubuntu) = speech-dispatcher (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790173
Title:
Cron
3.0pl1-124.1ubuntu1 contains a fix for this.
** Changed in: cron (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067779
Title:
missing
** Changed in: cron (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794141
Title:
cron needs to re-lookup users when trying to run a job
To manage
*** This bug is a duplicate of bug 826702 ***
https://bugs.launchpad.net/bugs/826702
** This bug has been marked a duplicate of bug 826702
crontab cuts off file names at 100 characters
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 826702 ***
https://bugs.launchpad.net/bugs/826702
** This bug has been marked a duplicate of bug 826702
crontab cuts off file names at 100 characters
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In the mean time, this limit has been raised to 1000 chars.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/826702
Title:
crontab cuts off file names at 100 characters
To manage notifications about
A fix has been prepared that recognizes too long commands and produces
an error message when attempting to create one, both via crontab(1) and
cron(8). Furthermore, this limit has been documented in the man pages.
** Changed in: cron (Ubuntu)
Status: Confirmed = Fix Committed
--
You
Closed as per submitter's request
** Changed in: cron (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985924
Title:
Permission denied for custom entries in
While an interesting concept, I believe cron is the wrong tool for this
job. Fixing this in cron would not ensure mutual exclusion in the cases
where these scripts are called by other means, eg manual calls.
The correct solution for backup_to_media and backup_to_file -- or any
other program that
The man page for crontab(5) states that PATH is initialized with
/usr/bin:/bin, so the tar invocation in the example is correct. Or did I
misunderstand your question?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The feature you are describing is the exact purpose of anacron. Could
you elaborate what you mean by hasn't the precision of cron? What can
cron do that you can't do with /etc/anacrontab?
BTW, it doesn't make sense for anacron to be a full-time daemon, because
when the system is up, you already
Apparently the MTA dependency in Ubuntu's cron has been demoted from
Recommends (as it is in Debian), to a Suggests, so this bug should be
re-assigned to Ubuntu's installation documentation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Could you check your MTA's log files (and /var/log/cron.*, if you have
it) for clues as to what could be going on? I just tried this locally
and it works fine: both mails are sent, and the MAILTO header is
included.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is mandated by POSIX, see
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html
** Changed in: cron (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, closing then. Thank you for your quick reply!
** Changed in: cron (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1148594
Title:
[12.04] crontab -e is not
Perhaps I should have been more clearer: the POSIX standard mandates
that the command field (that's everything in the sixth column of a
crontab file) be passed as arguments to /bin/sh:
| The sixth field of a line in a crontab entry is a string
| that shall be executed by sh at the specified
Re-assigning to dash then.
** Package changed: cron (Ubuntu) = dash (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337576
Title:
dash inability - cron starts binary with /bin/sh
To
I believed that the issue has been resolved since 2.1.0~beta~dfsg-6,
where the examples were moved into the -doc package, which recommends
both libfann-dev and python-pyfann so that all examples can be run.
** Changed in: libfann (Ubuntu)
Status: New = Fix Released
--
You received this
On 10/20/2011 01:23 AM, Steve Langasek wrote:
This brings us in line with the Debian cron package, which links against
libaudit. I was surprised to see that libaudit wasn't already in main.
FYI: by default, cron does not link against libaudit. Support for
libaudit is an optional feature that
*** This bug is a duplicate of bug 794082 ***
https://bugs.launchpad.net/bugs/794082
** This bug has been marked a duplicate of bug 794082
cron ignores /etc/default/cron
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 794082 ***
https://bugs.launchpad.net/bugs/794082
** This bug is no longer a duplicate of bug 79408
Users should be enabled to ignore crashes for certain apps
** This bug has been marked a duplicate of bug 794082
cron ignores /etc/default/cron
--
You
** This bug is no longer a duplicate of bug 79408
Users should be enabled to ignore crashes for certain apps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794082
Title:
cron ignores
cron 3.0pl1-119, recently uploaded to Debian unstable, contains a patch
that forces a rescan of ORPHANed crontabs. Credit for the fix goes to
Fedora cronie, from where it was taken.
I'll try to get this sync'ed over the weekend, together with some other
bugfixes for cron in Ubuntu.
--
You
cron 3.0pl1-119, recently uploaded to Debian unstable, contains a patch
that forces a rescan of ORPHANed crontabs. Credit for the fix goes to
Fedora cronie, from where it was taken.
I'll try to get this sync'ed over the weekend, together with some other
bugfixes for cron in Ubuntu.
--
You
On 06/18/2011 11:29 AM, Matthias Andree wrote:
Am 18.06.2011 03:39, schrieb Christian Kastner:
As I mentioned earlier, I have a fix in mind for the next release which
should resolve the issue in a manner not conflicting with the other goals.
next release doesn't help those running LTS
** Changed in: cron (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing ORPHAN
On 06/07/2011 06:34 PM, Matthias Andree wrote:
Please backport the fix for LP: #27520 to all supported releases. It
breaks, among others, on lucid.
There's a problem here: #27520 was never fixed. As it turned out, there
was a misunderstanding: the LSB init script headers (where the problem
was
On 06/07/2011 06:13 PM, Matthias Andree wrote:
Note that while the trigger is cron starting before the respective user
database (NIS, LDAP, whatever), cron should really re-check each time to
be resilient to temporary network hicc-ups.
In general, cron does not contain a single line of
On 06/08/2011 12:30 AM, Nathan Stratton Treadway wrote:
In the longer term, obviously it would be great for cron better
integrate with network-based user databases, but it would be nice to
hear from some Ubuntu developers whether that sort of change is likely
to get backported to Lucid?
This
On 06/08/2011 01:52 AM, Graeme wrote:
Regardless, it's been my experience that Ubuntu doesn't backport fixes
of this nature to releases that have already shipped. I've found that
the bugs must constitute a clear, widespread problem for a majority of
users before a backport is even considered.
On 06/08/2011 11:12 AM, Matthias Andree wrote:
Am 08.06.2011 01:17, schrieb Christian Kastner:
Theoretically, this could easily be extended to #27520 -- just a few
lines of code, actually -- but it's just not that simple, because there
are cases where ORPHAN is completely valid, ie the user
On 06/08/2011 11:14 AM, Matthias Andree wrote:
- it often takes longer than a year for a bug report to be triaged at
all, not even thinking of looked at by the packagers -- even for
things that are clearly upstream bugs and need to be delegated outside
Ubuntu, which doesn't require packager
No, -Ln only affects logging of jobs. The ORPHAN messages come from
the parsing part of the code, and always appear irregardless of any n
value.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756574
On 06/08/2011 12:53 AM, Graeme wrote:
Nathan: I think that since this bug sat untouched from 2005-2010, you
can guess that the answer is going to be No, don't care.
If you look at the changelog for recent versions of cron, you can see
that somebody does care for bug reports.
I'm just happy if
On 05/30/2011 01:45 PM, Marcel Svitalsky wrote:
The problem is that when run by cron on my newly installed Ubuntu
10.04.2 I don't get the output in mail but only 'expr: syntax error'
line instead.
Obviously I thought there was some error in the script at first, but
after trying and checking
(oops, accidentally hit send)
On 05/30/2011 01:45 PM, Marcel Svitalsky wrote:
The problem is that when run by cron on my newly installed Ubuntu
10.04.2 I don't get the output in mail but only 'expr: syntax error'
line instead.
Obviously I thought there was some error in the script at first,
On 05/30/2011 03:25 PM, Marcel Svitalsky wrote:
No, that's not correct. I do not use this syntax in the script at all.
Besides, as I've mentioned above, not only the script runs OK from
command line, it also runs OK from cron on Ub.-8.04 and it actually runs
OK even here on Ub.-10.04.2 (it
On 05/30/2011 04:16 PM, Marcel Svitalsky wrote:
- and eventually in /etc/profile.d/speechd-user-port.sh the line:
export SPEECHD_PORT=$(expr 6560 + $(getent passwd $USER | cut -f 3 -d :))
So my initial guess fits indeed: broken variable expansion. In this
case, it must be $USER (because it's
On 05/11/2011 12:16 AM, Nathan Stratton Treadway wrote:
I see that LP: #605123 describes a similar situation when cron is
started before the likewise-open daemons, while the Debian BTS 512757
mentioned above relates to NIS users, etc.
I discussed this problem recently with one of the upstart
** Changed in: cron (Ubuntu)
Assignee: (unassigned) = Christian Kastner (ckk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741979
Title:
cron ignores group-writable crontab, with obscure
The pending upload of -117 replaces the WRONG INODE INFO message with
proper messages indicating what exactly went wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741979
Title:
cron ignores
The error comes from the build dependency on swig. Switching to swig2.0
resolves the issue; a fix has been committed for the Debian package.
** Changed in: libfann (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
source: libfann
version: 2.1.0~beta~dfsg-3
where: Debian sid main
This version would fix LP: #712290.
I know it's a bit close to release, but the above upstream change is the
only one since the last upload. Otherwise the release contains only
trivial packaging updates.
On 04/18/2011 07:09 PM, Brian J. Murrell wrote:
On 11-04-18 12:26 PM, Christian Kastner wrote:
With root crontabs (as opposed to non-root), do you mean the system
crontabs /etc/crontab and /etc/cron.d, or root's actual crontab (via
crontab -e as root)?
Both. All crontabs continue to run
With root crontabs (as opposed to non-root), do you mean the system
crontabs /etc/crontab and /etc/cron.d, or root's actual crontab (via
crontab -e as root)?
Is there any possibility of the crontabs temporarily disappearing (eg:
remote filesystem)?
--
You received this bug notification because
*** This bug is a duplicate of bug 741979 ***
https://bugs.launchpad.net/bugs/741979
** This bug has been marked a duplicate of bug 741979
cron ignores group-writable crontab, with obscure message
* You can subscribe to bug 741979 by following this link:
in: cron (Ubuntu)
Assignee: (unassigned) = Christian Kastner (ckk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734693
Title:
Cron does not work for LDAP-users
--
ubuntu-bugs mailing list
ubuntu
On 02/22/2011 11:28 PM, H.-Dirk Schmitt wrote:
If have some symlinks below /etc/cron.d pointing to another directory
(configuration repository).
/etc/cron.d has no recursive support, so any symlinks pointing to
directories won't work.
E.g. /etc/cron.d/c42-dump-fs is such a symlink.
On
I've committed a fix in the Debian package, I hope to upload soon and
will then ask for an Ubuntu sync.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712290
Title:
set_train_data ValueError: Size
Addendum: I wasn't aware that Fedora implemented this differently --
although it is not surprising as /etc/cron.d/ not part of any official
spec but rather an extension that was added by the individual distros.
I have this issue noted for now; perhaps something can be done via log
levels in
This is, in fact, documented. See:
http://manpages.ubuntu.com/manpages/maverick/en/man8/cron.8.html
Quoting (2nd paragraph):
Additionally, cron reads the files in /etc/cron.d [...] Files must conform to
the same naming convention as used by run-parts(8): they must consist solely
of upper- and
OK, closing as Invalid then. This is not to dispute the bug, it's just
to indicate that something went wrong during system upgrade in general.
** Changed in: cron (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been reported and confirmed as a debconf issue in Debian, see:
http://bugs.debian.org/560317
** Bug watch added: Debian Bug tracker #560317
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560317
** Package changed: cron (Ubuntu) = debconf (Ubuntu)
** Changed in: debconf (Ubuntu)
Hello Sharad,
are you still experiencing this problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680024
Title:
package cron 3.0pl1-114ubuntu1 failed to install/upgrade: ErrorMessage:
ad PATH: This is by design, therefore it won't change. For example, by
pulling in PATH from pam_env, the ability to specify different paths for
different crontabs would be lost.
I'm speaking as one of the Debian maintainers here - Ubuntu is of course
free to add a patch on top of our version. I'd
Addendum (hit submit too fast) : by most versions', I meant not only
the Debian/Ubuntu versions, but also those present in BSD, Red Hat, Suse
etc. And the misdirected manpage (bcron) is the one in Lucid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hm, everything should be fine.
Have you tried updating again? Your initial report sounds like something
was wrong during that upgrade, it might have been fixed again. The only
way the pre-dependency error message makes sense to me is your system
having had an older version of dpkg installed
Since version 3.0plq-114, cron Pre-Depends on dpkg (= 1.15.7.2). The
version in 10.10 is 1.15.8.4, so I'm not sure why you are getting this
error. Could you post the output of
$ apt-cache policy dpkg
here?
--
package cron 3.0pl1-114ubuntu1 failed to install/upgrade: ErrorMessage:
The example you mentioned requires libfann2 -- specifically, the
libfann-dev package provided by it. That package is available in 10.10
(Maverick) and above.
--
undefined reference to `fann_create_standard'
https://bugs.launchpad.net/bugs/33136
You received this bug notification because you are
libfann2 is available in Maverick and above.
** Changed in: libfann1 (Ubuntu)
Status: New = Fix Released
--
New upstream version available
https://bugs.launchpad.net/bugs/54240
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
libfann-dev (from libfann2) is now available in Maverick, and should be
used instead.
** Changed in: libfann1 (Ubuntu)
Status: New = Confirmed
--
fann development package missing data for examples
https://bugs.launchpad.net/bugs/261859
You received this bug notification because you are a
I'm not that familiar with transitions in Ubuntu. Could somebody more
experienced take a look at this?
The python bindings are provided by libfann2 as package python-pyfann
since Maverick, however this bug refers to libfann1. libfann1 has
already been removed from Debian (and therefore won't get
Public bug reported:
Upstream and I would appreciate if you would sync pyrit.
Source: pyrit
Version: 3.0-2
Sync From: Debian sid main
Side question: I was hoping for the package to be auto-synced (as other
packages of mine were), but that was not the case. What could be the
reason for this?
**
My bad - I misunderstood the functionality of Related software and
packages, where I expected pyrit 0.3.0-2 to show up. That appears to be
only the case for Debian packages where I am the Maintainer, not just
amongst the Uploaders -- which is why I can't see cron in my package
list as well.
)
Status: New = Confirmed
** Changed in: cron (Ubuntu)
Assignee: (unassigned) = Christian Kastner (ckk)
--
Fix for #151231 leaves tmpfile fd open in actual job
https://bugs.launchpad.net/bugs/665912
You received this bug notification because you are a member of Ubuntu
Bugs, which
(I added that patch, which was provided by Justin Pryzby, to cron)
Strange. On my Debian Squeeze system with cron-115 (diff to -114 is only
in packaging), I get the following results with the test case you
provided:
$ cat /tmp/stdout.log
normal
total 0
dr-x-- 2 chris chris 0 Oct 24 23:43 .
This is actually a problem in debconf, see Debian bugs #596369 and
#560317.
--
dpkg-reconfigure fails on cron
https://bugs.launchpad.net/bugs/658718
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This appears to be a variant of Debian bug #512757 against cron. Can
somebody confirm this for me?
--
cron no longer respects nsswitch.conf
https://bugs.launchpad.net/bugs/27520
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
On 09/02/2010 05:09 PM, Stephane Chazelas wrote:
This appears to be a variant of Debian bug #512757 against cron. Can
somebody confirm this for me?
[...]
Pretty much, though for me reordering the init scripts wasn't enough as
there was some delay between the time nslcd (the LDAP cache
Package libfann-dev (version 2.1.0beta) has the datasets.
--
fann development package missing data for examples
https://bugs.launchpad.net/bugs/261859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The python bindings of libfann-2.1.0beta are available as package
python-pyfann.
--
python bindings are not included from upstream
https://bugs.launchpad.net/bugs/1674
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
85 matches
Mail list logo
