Bug#414275: xorg: X randomly crashes upon mouse click
Thibaut VARENE wrote:
> On 3/11/07, Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
>> When the X server crashes, the problem is actually located in
>> xserver-xorg-core (reassigning the bug). I assume you were running
>> xserver-xorg-core 2:1.1.1-19 or so ? Could you try xserver-xorg-core
>> currently in experimental (2:220.127.116.111-1) ?
> Correct. I didn't know which package to assign the bug to. As to
> trying the experimental version, I'm not quite comfortable with that:
> this system is my main one, if it's rendered unusable I'm going to be
> /very/ upset.
Well, you know, if X gets broken, the system should be far from being
unusable. Downgrading xserver-xorg-core from a text console is not that
hard :) It shouldn't bring many dependencies (probably only a new
libdrm2, few chances to break anything, and probably no need to
downgrade it later).
The current xserver-xorg-core in experimental is upstream 1.3-rc1, it
may actually be a little bit unstable. It works fine here. But if you're
too afraid of it, you can try xserver-xorg-core 1.2.0 which has been
experimental for a while until last week (grab it from
snapshot.debian.net). It was working very well on my machines. If we
were not close to Etch's release, it would have been in unstable with
the whole Xorg 7.2 for a while.
> The bug is not easy to reproduce, and again, attaching gdb to the
> running X server waiting for the crash to happen is just a no-go,
> given that's my main system.
I can understand that :)
> I've got another bug I'm trying to pin down, this one being easier to
> reproduce: if I enable a screensaver in Gnome's Screensaver panel,
> most of time if I wander off long enough for the screensaver to start,
> when I come back, X has been killed and I'm back to GDM prompt. I'll
> see if I can force myself into doing that again to provide some info.