[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Frequent crashes whilst using X (try 2)



Debian Squeeze/Testing with kernel 2.6.26 and the nv driver.

A few weeks ago after some packages were updated X applications started 
crashing and sometimes brought X down as well.

I use Balsa as my mailer and often when I click on a mail folder to open 
it Balsa just crashes (disappears). Today I started Qemu and when I 
clicked inside the window to capture the mouse pointer X crashed and I was 
back at the KDM login.

The only error I can find for the Qemu crash is in Xorg.0.log.old:

(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Configured Mouse: ps2EnableDataReporting: succeeded

Fatal server error:
bogus pointer event from ddx

I've assumed that there may be a bug in one of the upgraded packages but 
I've no idea which one. Is anyone else experiencing this?

UPDATE: It does seem to be mouse related. I have also seen this 
in .xsession-errors: balsa: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :0.0.

I would be nice to know if other people *aren't* getting this as it would 
then mean the problem must be on my system. That would at least be a clue 
although I cannot imagine why it started suddenly.

Anyone?

-- 
Barry Samuels
http://www.beenthere-donethat.org.uk
The Unofficial Guide to Great Britain


Reply to: