Package: iceweasel
Version: 3.0.4-1
Iceweasel regularly (though not reproducibly) crashes here. I ran the whole
thing with the '--sync' commandline argument, as it suggests, and the output
is this:
> sh: acroread: command not found
> open dsp: Device or resource busy
> open dsp: Device or resource busy
> Improper call to JPEG library in state 202
> Unable to read JPEG data
> Improper call to JPEG library in state 202
> Unable to read JPEG data
> Improper call to JPEG library in state 202
> Unable to read JPEG data
> Improper call to JPEG library in state 202
> Unable to read JPEG data
> Improper call to JPEG library in state 202
> Unable to read JPEG data
> open dsp: Device or resource busy
> Improper call to JPEG library in state 202
> Unable to read JPEG data
> Improper call to JPEG library in state 202
> Unable to read JPEG data
> open dsp: Device or resource busy
> Improper call to JPEG library in state 202
> Unable to read JPEG data
> Improper call to JPEG library in state 202
> Unable to read JPEG data
> open dsp: Device or resource busy
> The program 'firefox-bin' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadShmSeg (invalid shared segment parameter)'.
> (Details: serial 903 error_code 170 request_code 146 minor_code 2)
> (Note to programmers: normally, X errors are reported asynchronously;
> that is, you will receive the error a while after causing it.
> To debug your program, run it with the --sync command line
> option to change this behavior. You can then get a meaningful
> backtrace from your debugger if you break on the gdk_x_error()
> function.)
Note that running under GDB isn't easy, as 'iceweasel' is just a script. Using
the '-g' commandline argument seems to do the job though. However, after
starting, GDB complains that it "Cannot find new threads: debugger service
failed". I then set the breakpoint ("break gdk_x_error"), acknowledge that it
depends on future shared libraries being loaded and start ("run --sync") the
binary. However, this never actually reaches the breakpoint.
The error isn't always the same, sometimes I also get this:
> The error was 'BadMatch (invalid parameter attributes)'.
> (Details: serial 341 error_code 8 request_code 42 minor_code 0)
Note that I do have flash installed, but it usually works pretty bad. In
particular the colors are messed up, as if the code was missing some
endianess conversion (I'm on a PPC/big endian machine). I wouldn't be
surprised if there were further similar bugs.
I'll keep running iceweasel with --sync, in case I can detect a pattern there.
If you want me to try anything else, just send me a note.
Uli
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
