+++ This bug was initially created as a clone of Bug #655630 +++
abrt version: 1.1.13
Attached file: backtrace
reason: Process /usr/bin/vinagre was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce
1.server switched from 1920*1080 to 640*480. scaling was enabled.
--- Additional comment from email@example.com on 2010-11-21 21:23:12 EST ---
Created attachment 461903 [details]
--- Additional comment from firstname.lastname@example.org on 2010-11-22 16:07:03 EST ---
Please try installing this update of GTK-VNC and let me know if it still crashes when the server switches size. This update includes a fix that checks for the server sending out-of-bounds updates, and disconnects from the server cleanly instead of crashing
What VNC server are you connecting to though ? It could be that your server is buggy in sending VNC resizes.
--- Additional comment from email@example.com on 2010-11-22 19:26:49 EST ---
It still crashes. Bug number for the submitted backtrace: 656068
the crash didn't happen at the first resolution change. The first
changes just killed the connection. Fifth change killed the client. It seems
that it is sensitive to the changes to lower resolution, not to higher.
--- Additional comment from firstname.lastname@example.org on 2010-11-23 05:50:08 EST ---
*** Bug 656068 has been marked as a duplicate of this bug. ***
--- Additional comment from email@example.com on 2010-11-23 05:57:36 EST ---
Can you capture me a trace with 'vinagre --gtk-vnc-debug' from time of initial connection to the VNC server, through the resizes, upto the point it crashes.
Then, do the same running
--- Additional comment from firstname.lastname@example.org on 2010-11-23 08:53:40 EST ---
Created attachment 462335 [details]
output of 'vinagre --gtk-vnc-debug', vinagre crashed after resolution change
--- Additional comment from email@example.com on 2010-11-23 09:15:28 EST ---
Created attachment 462340 [details]
output of 'valgrind vinagre'
output of several 'valgrind vinagre'. I was unable to provoke the crash by resolution changes through at lest 50 resolution changes during half an hour, running with valgrind.
--- Additional comment from firstname.lastname@example.org on 2010-11-29 06:49:56 EST ---
These are the three key log messages at the end
The VNC server does a resize to 800x600 pixels:
(vinagre:21644): gvnc-DEBUG: vncconnection.c FramebufferUpdate type=-223 area (800x600) at location 0,0
And sends an initial framebuffer update for that new desktop
(vinagre:21644): gvnc-DEBUG: vncconnection.c FramebufferUpdate type=16 area (800x600) at location 0,0
But then bizarrely sends an update for a region that it way outside the framebuffer at offset 1166
(vinagre:21644): gvnc-DEBUG: vncconnection.c FramebufferUpdate type=16 area (19x19) at location 1166,695
So there are 2 bugs here
1. gtk-vnc is not doing a correct bounds check on framebuffer updates and thus scribbling over random memory when it gets that out of bounds update
2. vino is sending illegal framebuffer updates for regions outside the current framebuffer
I'm re-assigning this bug to gtk-vnc for resolution of the client side problem, and will clone against vino too.
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: