Bug#404346: vino-server segmentation fault

[Loïc Minier]

        Hi,

On Sun, Dec 24, 2006, Guy Roussin  wrote:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1224267552 (LWP 15831)]
> vino_input_init (display=0x808f098) at vino-input.c:132
> 132                   if (global_input_data.keycodes [keysym] != 0)
> (gdb) bt
> #0  vino_input_init (display=0x808f098) at vino-input.c:132
> #1  0x080501e0 in main (argc=1, argv=0xbfba5f64) at vino-main.c:78

 Weird but interesting.  The crash happens very near this upstream
 change:
    <http://bugzilla.gnome.org/attachment.cgi?id=77801>
 (from GNOME #369884 http://bugzilla.gnome.org/show_bug.cgi?id=369884)

 Could you try this upstream patch?  If it fixes the segfault, I can
 pull it easily.  If it doesn't and you have the time to, you can try
 building the upstream CVS of vino to see whether your bug is already
 fixed upstream (I don't experience it myself), and if it is extract a
 patch: this might make it possible to push the change in Debian before
 the release of etch.

   Bye,
PS: I'll be on holidays for a week starting tonight.
-- 
Loïc Minier <lool at dooz.org>
 "Forget your stupid theme park! I'm gonna make my own! With hookers!
  And blackjack! In fact, forget the theme park!"          -- Bender