xserver-common: X crashed (signal 7) while scrolling in Mozilla

Automatically imported from Debian bug report #280364 http://bugs.debian.org/280364

Message-ID: <email address hidden>
Date: Tue, 09 Nov 2004 06:31:42 +0100
From: Fabio Massimo Di Nitto <email address hidden>
To: Vincent Lefevre <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#280364: xserver-common: X crashed (signal 7) while scrolling
 in Mozilla

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

severity 280364 important
reassign 280364 xserver-xfree86
retitle 280364 [r128] crash on ppc while scrolling in Mozilla.
tag 280364 moreinfo
tag 280364 upstream
stop

Vincent Lefevre wrote:
| Package: xserver-common
| Version: 4.3.0.dfsg.1-8
| Severity: grave
| Justification: causes non-serious data loss
|
| While I was scrolling a Mozilla window, X crashed (signal 7).
| This is the first time this happens, but I usually don't use
| XFree86. I lost all the data that have not been saved by X
| applications.

If X applications are not able to handle data properly on crash,
that's an application problem.
See vi or similar that stores always data on temporary files
while working and offer the option to the user to recover.

This makes the severity important and not grave.
Also reassigning to the proper package.

| I've attached the log file and my XF86Config-4 config file.

|
|
| Section "Device"
| Identifier "ATI Rage 128 M3 (Mobility)"
| #Option "NoAccel"
| #Option "SWcursor"
| #Option "HWcursor"
| #Option "Dac6Bit"
| #Option "Dac8Bit"
| Option "UseFBDev"
| #Option "power_saver"
| Driver "r128"
| #BusID "PCI:0:16:0"
| EndSection

Is there any specific reason for using r128 instead of ati?

Is this problem reproducible constantly? If so please install the debugging version of the server
and provide us a gdb back trace.

Thanks
Fabio

- --
Self-Service law:
The last available dish of the food you have decided to eat, will be
inevitably taken from the person in front of you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBkFY9hCzbekR3nhgRAg5cAJ42kjqwxwHIfiibxU5d1nthhTpxFACdEWen
dOi2H6sQRyvCVyh7aH3/3Co=
=aksS
-----END PGP SIGNATURE-----

Message-ID: <email address hidden>
Date: Tue, 9 Nov 2004 14:45:47 +0100
From: Vincent Lefevre <email address hidden>
To: Fabio Massimo Di Nitto <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#280364: xserver-common: X crashed (signal 7) while scrolling in Mozilla

On 2004-11-09 06:31:42 +0100, Fabio Massimo Di Nitto wrote:
> If X applications are not able to handle data properly on crash,
> that's an application problem.

Hmm... OK. I hope that their maintainers won't say that the X server
shouldn't crash. However, it seems difficult to recover the session
as it was before the crash.

> | Section "Device"
> | Identifier "ATI Rage 128 M3 (Mobility)"
> | #Option "NoAccel"
> | #Option "SWcursor"
> | #Option "HWcursor"
> | #Option "Dac6Bit"
> | #Option "Dac8Bit"
> | Option "UseFBDev"
> | #Option "power_saver"
> | Driver "r128"
> | #BusID "PCI:0:16:0"
> | EndSection
>
> Is there any specific reason for using r128 instead of ati?

Lack of documentation. Since I didn't know what to put in this
file (it was in March 2001), I took the XF86Config of someone
else (that was written for the PowerBook G4). I'll change it
to "ati". If "r128" is deprecated or not better than "ati", it
should be said in the r128(4x) man page.

> Is this problem reproducible constantly? If so please install the
> debugging version of the server and provide us a gdb back trace.

This is the first time it occurred (I couldn't find any other report
in my mail archives). I also looked for a core file (even though it
wouldn't really be useful without the debugging version), but there
was none.

--
Vincent Lef�e <email address hidden> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Message-ID: <email address hidden>
Date: Tue, 9 Nov 2004 06:24:04 -0800
From: Daniel Stone <email address hidden>
To: Vincent Lefevre <email address hidden>, <email address hidden>
Subject: Re: Bug#280364: xserver-common: X crashed (signal 7) while scrolling in Mozilla

--ZrCu0B0FMx3UnjE2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 09, 2004 at 02:45:47PM +0100, Vincent Lefevre wrote:
> On 2004-11-09 06:31:42 +0100, Fabio Massimo Di Nitto wrote:
> > Is there any specific reason for using r128 instead of ati?
>=20
> Lack of documentation. Since I didn't know what to put in this
> file (it was in March 2001), I took the XF86Config of someone
> else (that was written for the PowerBook G4). I'll change it
> to "ati". If "r128" is deprecated or not better than "ati", it
> should be said in the r128(4x) man page.

It makes no difference. ati will just handball to r128 (except for the
cases where it fails to do because it sucks), so this won't actually
impact on anything. So no, r128 is not deprecated (neither are radeon
or atimisc).

> > Is this problem reproducible constantly? If so please install the
> > debugging version of the server and provide us a gdb back trace.
>=20
> This is the first time it occurred (I couldn't find any other report
> in my mail archives). I also looked for a core file (even though it
> wouldn't really be useful without the debugging version), but there
> was none.

If you want to run mozilla under gdb for a while and just wait for a
segfault, that might be rad.

--=20
Daniel Stone <daniels@debian=
=2Eorg>

--ZrCu0B0FMx3UnjE2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBkNMDcPClnTztfv0RApQWAKCNkcbNrnAmO88/b3kvmvEdcLa/lgCfabjE
9ASJ9uNhHexYpzrrqkbApAE=
=cbZh
-----END PGP SIGNATURE-----

--ZrCu0B0FMx3UnjE2--

Doing the needinfo dance. It's probably fixed in xorg, we don't have the log or
anything, and SIGABRTs are ... yeah. Can't solve this without more info,
unlikely to get it, so I don't want it.