Processing commands for cont...@bugs.debian.org:
> tag 681796 + patch
Bug #681796 [xserver-xorg] segmentation fault during suspend
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
681796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681796
D
tag 681796 + patch
thanks
On Sat, 28 Jul 2012, Julien Cristau wrote:
> It's helpful, yes, thanks. Could you forward it upstream to
> https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Server/Input/Core
so upstream seems to boiled it down and provided a patch. I have
adopted the
Here is more detailed output but I guess I would just need to setup
remote debugging somehow... :
Program received signal SIGSEGV, Segmentation fault.
0x7fec6053e757 in XIChangeDeviceProperty (dev=0x7fec63c494f0, property=120,
type=19, format=8, mode=0, len=1, value=0x7fff67dc75af, sendevent=
Processing commands for cont...@bugs.debian.org:
> forwarded 681796 https://bugs.freedesktop.org/show_bug.cgi?id=52496
Bug #681796 [xserver-xorg] segmentation fault during suspend
Set Bug forwarded-to-address to
'https://bugs.freedesktop.org/show_bug.cgi?id=52496'.
> thanks
Stopping processing he
forwarded 681796 https://bugs.freedesktop.org/show_bug.cgi?id=52496
thanks
On Sat, 28 Jul 2012, Julien Cristau wrote:
> > and then -- this gesture from gdb while running from a script was not
> > expected:
> > ---Type to continue, or q to quit---
> You can probably avoid this next time with the
On Tue, Jul 24, 2012 at 00:09:43 -0400, Yaroslav Halchenko wrote:
>
> On Mon, 16 Jul 2012, Julien Cristau wrote:
> > > [145698.415] Caught signal 11 (Segmentation fault). Server aborting
> > > [145698.415]
> > > [145698.415]
>
> > Any chance you can get a backtrace from gdb?
>
> Program recei
On Mon, 16 Jul 2012, Julien Cristau wrote:
> > [145698.415] Caught signal 11 (Segmentation fault). Server aborting
> > [145698.415]
> > [145698.415]
> Any chance you can get a backtrace from gdb?
Program received signal SIGSEGV, Segmentation fault.
XIChangeDeviceProperty (dev=dev@entry=0x7f4ba
On Sat, 21 Jul 2012, Yaroslav Halchenko wrote:
> Program received signal SIGSEGV, Segmentation fault.
> XIChangeDeviceProperty (dev=dev@entry=0x7ff24ae17130, property= out>, type=type@entry=19, format=format@entry=8, mode=,
> mode@entry=0, len=len@entry=1, value=value@entry=0x7fff585294cf,
> sen
On Mon, 16 Jul 2012, Julien Cristau wrote:
> > well -- I attached to X with gdb in a screen now... and will hope that I
> > would be able to get there whenever such accident occurs again
> You'll probably need ssh to access it if/when X crashes.
unfortunately by then there were no chance to get r
On Mon, 16 Jul 2012, Julien Cristau wrote:
> > Fatal server error:
> > [145698.415] Caught signal 11 (Segmentation fault). Server aborting
> > [145698.415]
> > [145698.415]
> Any chance you can get a backtrace from gdb?
well -- I attached to X with gdb in a screen now... and will hope that I
wo
On Mon, 16 Jul 2012, Julien Cristau wrote:
> > > Any chance you can get a backtrace from gdb?
> > well -- I attached to X with gdb in a screen now... and will hope that I
> > would be able to get there whenever such accident occurs again
> You'll probably need ssh to access it if/when X crashes.
On Mon, Jul 16, 2012 at 14:02:00 -0400, Yaroslav Halchenko wrote:
>
> On Mon, 16 Jul 2012, Julien Cristau wrote:
> > > Fatal server error:
> > > [145698.415] Caught signal 11 (Segmentation fault). Server aborting
> > > [145698.415]
> > > [145698.415]
> > Any chance you can get a backtrace from
On Mon, Jul 16, 2012 at 12:31:37 -0400, Yaroslav Halchenko wrote:
> Package: xserver-xorg
> Version: 1:7.7+1
> Severity: important
> File: /usr/bin/X
>
> Seems to be happening once in few days (I suspend the laptop ~5-20 times
> a day). I did a recent upgrade of the system to up-to-date mix of
13 matches
Mail list logo
