"Failed to execute child process (input/output error)"

Bug #184618 reported by EPT
12
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: firefox

I don't know what is exactly going on but my Ubuntu crashed at least three times a day now. After I changed to Gutsy Gibbon. When it happens I can't open any programs or do anything any more. Every time I try to open some program it just says "Failed to execute child process NameOfTheProgram (input/output error)" When I try to restart the computer it stucks to closing process "EXT3-fs error (device sda1): etx3_get_inode_loc: unable to read inode block etc etc.

ProblemType: Crash
Architecture: i386
Date: Fri Jan 18 01:13:13 2008
Disassembly: 0xb769d7a6:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/firefox/firefox-bin
NonfreeKernelModules: cdrom
Package: firefox 2.0.0.11+2nobinonly-0ubuntu0.7.10
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/esapekka
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox
Stacktrace: #0 0xb769d7a6 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: firefox-bin crashed with SIGSEGV
Uname: Linux ubuntu 2.6.22-14-386 #1 Tue Dec 18 07:34:24 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
EPT (tuominen-esa-pekka) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
John Vivirito (gnomefreak) wrote :

Sorry but Firefox-2 is getting near EOS and they wont be fixing anything but major issues security issues mainly. Please try to reproduce this with Firefox-3.0 if you can reproduce this bug please click on Help > Report a problem and file the bug that way. This does not mean that it wasn't already fixed.

I am wondering how did you end up with firefox causing this issue?

Changed in firefox:
status: New → Won't Fix
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.