[Bug 91545] Re: MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo()

2007-05-01 Thread Filofel
I reported a similar error, that was marked as a duplicate of this one. But I didn't mention in my original report that I was running a dual screen configuration. Mine uses a dual-head Matrox G400 PCI board. -- MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo()

[Bug 91545] Re: MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo()

2007-04-30 Thread Simon Edwards
Looking at all of these crash reports I'm getting the feeling that the problem has to do with guidance not handling things when the xrandr X extension is not available. In the past, calling XRRGetScreenInfo() would just return null if the extensions was not available, maybe this behaviour has been

[Bug 91545] Re: MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo()

2007-04-28 Thread Andrew Ash
** Summary changed: - [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo() + MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo() -- MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo()