Ubuntu
debsecan package

debsecan crashed with IOError in write()

Bug #124468 reported by Svetoslav Stefanov
170
This bug affects 12 people
Affects Status Importance Assigned to Milestone
debsecan (Ubuntu)
In Progress
Medium
Unassigned

Bug Description

Binary package hint: debsecan

Crash after login.

ProblemType: Crash
Architecture: i386
Date: Fri Jul 6 23:04:03 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/debsecan
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: debsecan 0.4.9
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/debsecan --cron
ProcCwd: /usr/sbin
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=/usr/bin:/bin
 LANG=en_US.UTF-8
 SHELL=/bin/sh
PythonArgs: ['/usr/bin/debsecan', '--cron']
SourcePackage: debsecan
Title: debsecan crashed with IOError in write()
Uname: Linux Core2Duo 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux

See original description
Revision history for this message
Svetoslav Stefanov (svetlisashkov) wrote :
Revision history for this message
wawadave (wawadave-gmail) wrote :

Crash crash crash
it does the daily bash
debscan crash crash crash
what a bash.

Revision history for this message
wawadave (wawadave-gmail) wrote :

yuppers did it again

Revision history for this message
patrickdemarta (patrick-demarta) wrote : Re: [Bug 124468] Re: debsecan crashed with IOError in write()

wawadave ha scritto:
> yuppers did it again
>
>
 well, it does serveral times per day... i just stopped notifing it

johnnyba71 (johnny-jbsoft)
description: updated
Revision history for this message
bird (siebesadeq) wrote :

Choosing the option to be notified doesn't work. It just keeps coming back, although I must mention that I hadn't had this crash notification for several days...

Revision history for this message
bird (siebesadeq) wrote :

Excuse me. I meant not to be notified.

Revision history for this message
Hew (hew) 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 Triaged and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in debsecan:
importance: Undecided → Medium
status: New → Triaged
Apport retracing service (apport)
tags: added: bugpattern-needed
Revision history for this message
loicjacquardtest (loicjacquardtest) wrote :

tags: quantal

description: updated
loicjacquardtest (loicjacquardtest)
tags: added: quantal
loicjacquardtest (loicjacquardtest)
tags: added: precise
Changed in debsecan (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Norbert (nrbrtx) wrote :

If I try manually start debsecan from terminal "debsecan --cron", it reports
sendmail: fatal: open /etc/postfix/main.cf: No such file or directory
and then Traceback:
Traceback (most recent call last):
  File "/usr/bin/debsecan", line 1323, in <module>
    rate_system(target, options, fetch_data(options, config), history)
  File "/usr/bin/debsecan", line 1302, in rate_system
    formatter.finish()
  File "/usr/bin/debsecan", line 1134, in finish
    scan_fixed()
  File "/usr/bin/debsecan", line 1118, in scan_fixed
    w(" - %s" % p)
  File "/usr/bin/debsecan", line 1219, in write
    self.sendmail.write(line + '\n')
IOError: [Errno 32] Broken pipe

It happens for me after upgrade to Precise, I have no problems in Natty and Lucid.

Revision history for this message
Norbert (nrbrtx) wrote :

Debsecan crashed on Xenial.
debsecan is useless. I'm removing it.

tags: added: xenial
Norbert (nrbrtx)
tags: removed: precise quantal
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.