cron crashed with signal 7

Bug #365834 reported by skrisman on 2009-04-24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
cron (Ubuntu)
Nominated for Jaunty by vincent

Bug Description

Binary package hint: cron

I'm just running Xubuntu Jaunty from the live cd and all of a sudden I recieved this crash. That's pretty much it.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/cron
MediaBuild: Xubuntu 9.04 "Jaunty Jackalope" - Release i386 (20090420.1)
Package: cron 3.0pl1-105ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /USR/SBIN/CRON
 PATH=(custom, no user)
Signal: 7
SourcePackage: cron
 ?? () from /lib/
 ?? () from /lib/
 ?? () from /lib/
 ?? () from /lib/
 ?? () from /lib/
Title: cron crashed with signal 7
Uname: Linux 2.6.28-11-generic i686

skrisman (ssandboxx) wrote :
skrisman (ssandboxx) on 2009-04-24
visibility: private → public

StacktraceTop:memset (dstpp=0xb7c00068, c=<value optimized out>, len=8)
_dl_map_object_from_fd (
_dl_map_object (loader=0x0,
dl_open_worker (a=0xbff7d5ec) at dl-open.c:293
_dl_catch_error (objname=0xbff7d614, errstring=0xbff7d610,

Changed in cron (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
flopano (rubixou) wrote :

Idem during an install of Karmic, during the live session and the install of Karmic...

Charlie Kravetz (charlie-tca) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in cron (Ubuntu):
status: New → Confirmed
tags: added: xubuntu
Jamie Strandboge (jdstrand) wrote :

Upstream (Debian) has suggested that this should be fixed with the latest cron and pam. Can someone test on our development release (Ubuntu 10.10) and report back?

Changed in cron (Ubuntu):
assignee: nobody → Jamie Strandboge (jdstrand)
status: Confirmed → Incomplete
Charlie Kravetz (charlie-tca) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Charlie Kravetz (charlie-tca) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in cron (Ubuntu):
assignee: Jamie Strandboge (jdstrand) → nobody
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers