According to Loïc Minier:
> 
>  Please use the reportbug tool to report bugs.  It would have told me
>  what relevant packages you have installed, and what distribution you
>  are tracking.

ii  galeon         1.3.21-6       GNOME web browser for advanced users
ii  galeon-common  1.3.21-6       GNOME web browser for advanced users
ii  mozilla        1.7.10-1       The Mozilla Internet application suite - meta
ii  mozilla-browse 1.7.10-1       The Mozilla Internet application suite - core
ii  mozilla-dev    1.7.10-1       The Mozilla Internet application suite - devel
ii  libc6          2.3.5-5        GNU C Library: Shared libraries and Timezone d
ii  xlibs          6.8.2.dfsg.1-5 X Window System client libraries metapackage a
ii  libglib2.0-0   2.8.0-1        The GLib library of C routines
ii  libgtk2.0-0    2.6.9-1        The GTK+ graphical user interface library

well, that's an almost fresh sid from a few days ago, that should be enough.

> > When a tab is still loading (some does that almost forever as they
> > contain some weird flash ads) and when you close it, galeon crashes.
> > That's 100% reproducible on different computers.
> 
>  Not reproducible here, with sid.  It would be nice if you could find
>  what pattern is matched by your computers: Nvidia graphic adapter,
>  recent Mozilla upgrade, or newer Xorg packages.

fresh sid, 'nvidia' and 'ati' drivers, at least.
 
> > gdb is not very helpful as it's an exit(1) from galeon itself.
> > Last lines are:
> 
>  Last lines of?  Program output?

galeon running in gdb.

> > The program 'galeon' received an X Window System error.
> > This probably reflects a bug in the program.
> > The error was 'BadShmSeg (invalid shared segment parameter)'.
> 
>  Hi, X Window System errors are frequently caused by X drivers.  Please
>  try running Galeon with the --sync flag and report the backtrace of the
>  failed call.  Your graphic driver would be especially interesting with
>  this.

with --sync inside gdb, there's no more crash and the very same page
loads completely (while I have to stop it manually without --sync).

The output is different.

NP_Shutdown
NP_Initialize
New
SetWindow
SetWindow
SetWindow
NewStream
WriteReady
Write
decoding...
DestroyStream
[New Thread -1314915408 (LWP 4654)]
[Thread -1267172432 (LWP 4651) exited]
Destroy
NP_Shutdown

> > This used to work so it seems like a recent regression (a few weeks ago).
> 
>  Maybe you can identify the software upgrade which caused this?
>  Probably not Galeon, but: Xorg, Mozilla, or Gtk maybe?

I can't. full upgrade each time. Only galeon crashes.

Reply via email to