apport-cli crashed with IOError in delete_report()

Bug #195750 reported by Dmitriy Geels
16
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: apport

here are apport last words, this is enough to determine crash reason:

dmig@dmig-desktop:~$ apport-cli
Traceback (most recent call last):
  File "/usr/bin/apport-cli", line 282, in <module>
    app.run_argv()
  File "/var/lib/python-support/python2.5/apport/ui.py", line 260, in run_argv
    self.run_crashes()
  File "/var/lib/python-support/python2.5/apport/ui.py", line 101, in run_crashes
    self.run_crash(f)
  File "/var/lib/python-support/python2.5/apport/ui.py", line 113, in run_crash
    apport.fileutils.mark_report_seen(report_file)
  File "/var/lib/python-support/python2.5/apport/fileutils.py", line 107, in mark_report_seen
    delete_report(report)
  File "/var/lib/python-support/python2.5/apport/fileutils.py", line 160, in delete_report
    open(report, 'w').truncate(0)
IOError: [Errno 13] Permission denied: '/var/crash/linux.0.crash'
dmig@dmig-desktop:~$ ll /var/crash/linux.0.crash
-rw-r--r-- 1 root root 46256 2008-02-26 14:43 /var/crash/linux.0.crash

ProblemType: Crash
ApportLog:
 apport (pid 14998) Tue Feb 26 14:45:36 2008: called for pid 13661, signal 6
 apport (pid 14998) Tue Feb 26 14:45:36 2008: executable: /home/dmig/eclipse/eclipse (command line "/home/dmig/eclipse/eclipse")
 apport (pid 14998) Tue Feb 26 14:45:36 2008: executable does not belong to a package, ignoring
Architecture: i386
CrashReports:
 600:1017:1000:9496:2008-02-26 14:45:59.000000000 +0300:2008-02-26 14:46:00.000000000 +0300:/var/crash/_usr_bin_apport-cli.1017.crash
 600:1017:1000:29167733:2008-02-21 19:42:59.000000000 +0300:2008-02-21 19:43:00.000000000 +0300:/var/crash/_usr_bin_epiphany.1017.crash
 600:1017:1000:309469:2008-02-21 19:42:35.000000000 +0300:2008-02-21 19:42:36.000000000 +0300:/var/crash/_usr_lib_opera_9.50-20071024.6_operapluginwrapper.1017.crash
 644:0:0:46256:2008-02-26 14:43:31.000000000 +0300:2008-02-26 14:43:32.000000000 +0300:/var/crash/linux.0.crash
 644:1017:1000:44212:2008-02-26 14:43:24.000000000 +0300:2008-02-26 14:43:25.000000000 +0300:/var/crash/linux.1017.crash
Date: Tue Feb 26 14:46:00 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/apport-cli
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: vmvirtualnic vm_bridge vm_main hypervisor nvidia
Package: apport 0.98
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/apport-cli
ProcCwd: /home/dmig
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=ru_RU.UTF-8
PythonArgs: ['/usr/bin/apport-cli']
SourcePackage: apport
Title: apport-cli crashed with IOError in delete_report()
Uname: Linux dmig-desktop 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

Tags: apport-crash
Revision history for this message
Dmitriy Geels (dmig) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Indeed, the linux.0.crash file should not be readable by normal users in the first place, similar to standard crash reports. Do you know how you/what created /var/crash/linux.0.crash?

Changed in apport:
status: New → Incomplete
Revision history for this message
Dmitriy Geels (dmig) wrote :

Actually that was java crash.
I think, that caused by gdb -- I tried to see, where it hangs and attached to it with gdb.

But apport shouldn't die so hard, if current user don't have permissions to read dump.

Revision history for this message
Martin Pitt (pitti) wrote :

Right, it shouldn't die, but I'm interested in the actual cause of the problem instead of just ignoring it.

Revision history for this message
Jayson Rowe (jayson.rowe) wrote :

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and if any additional work should be done on this bug.

Revision history for this message
Martin Pitt (pitti) 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 apport:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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